labofsahil/github-event-dataset-2012 huggingface dataset:
Это, кстати, по coding style тоже надо б разбить на строчки, т.к. слишком длинное. Просто забыл еще сделать.
Ломается BC
don't get what this line should do...
use "dec"
All of those should have a common "root" selector (like `.cms-preview`), this makes it clear that the scope of this SCSS definition is limited. Particularly stuff towards the bottom of the file like a global `input.hide` rule is undermining the SCSS file hierarchy, and makes things very hard to follow and debug.
Lines 3177, 3180 and 3185 can be merged for `dataset` emulation:

    if (Object.isUndefined(value))
      value = null;
    element.writeAttribute("data-"+datalabel.underscore().dasherize(), value);
> We could treat a parent name+category name as unique, except thats not currently enforce in the application or DB

So you're saying - top level categories, and subcategories under the same top level category should have unique names, BUT subcategories under different top level categories can have similar names ? (this would definitely work)
直接加buffer会导致问题。参见 <http://cnodejs.org/topic/4faf65852e8fb5bc65113403>
Trivial: Some values use the scale* vars and some don't try to be consistent.  This block is blackberry specific so they could all use the scale* vars or all set the exact value.
probably just named 'replies'? since personal messages is more like 'private messages' maybe?
I actually think adding `|| required_props.code == 0` to this test will have the intended effect.

Then all new Exceptions WILL require `e.name` to be set correctly. It'll work even if the implementation doesn't set the type of the exception at all.
I'm unclear as to why this is necessary instead of just using `json_encode()`
It probably could be.  What would the win be in that case?
Put this in src/rviz/geometry.cpp and src/rviz/geometry.h, to make it callable by anyone using librviz.  Looks like a very handy function.
no spaces after ( and before ), spaces around +
Then use empty value `""`.
well it is like that now. What do you want me to cahnge (appart from account url) ?
request would be passed here (see comment below)
But this is already in the file. :-) At the top.
Usually the executable, if the formula provides one; many just do `foo --version` to check that the executable actually works, though some actually have nice tests that actually exercise program functionality.

Libraries are harder to test. It would be nice to compile a test program to ensure the lib can be linked, though I don't think any formula do this currently. We usually just skip the test on things that only build libraries.
Ahh, sorry. My mistake. I had forgotten that I used it in both places originally.
@Vincent-Michael, why ?
hmm Duplicate?
Sure I could. But I just swapped the array for the utility class I created. I did not want to refactor your code.
Wozu? In dieser Activity gibts ja nur einen AsyncTask parallel :)
Same ```def``` remark here.
You can use `get_data_path` inside test_utils (https://github.com/gem/oq-eqcatalogue-tool/blob/master/tests/test_utils.py#L23)
Radius -> RADIUS as it is an acronym
because I know what this is made for, I don't really had a hard time to understand, but I'm not sure this explanation helps a lot. Maybe we should tell that this value should be used in order to use this plugin?
/!\ This is legacy code.
Space after "if".
I've had time to review the figures..

```` 
Scale height = R/G*(T0/((Mass body/r^2)*M)) 
````

As the code follows the equation, the constant must be **R/G** where G is the gravitational constant.

Molar mass is given in g/Mol instead of the SI unit kg/Mol so the constant should be multiplied by 10^3.

Line 1348 should read
```` 
const float atmosMolarMass = 0.02897f; // in kg/mol
````
for clarity.

Mass in sbody is in Earths for planets, which means the constant needs to be divided by mass earth (or sbody::GetMass used which makes it slightly more expensive).

Radius r is in Earth radii so the constant needs to be multiplied by square of the earth radius (or sbody::GetRadius used).

G = 6.67384e-11 from [here](http://physics.nist.gov/cgi-bin/cuu/Value?bg|search_for=gravitational) libs say 6.67428e-11, maybe there was a typo on the 2
R=8.3144621 from [here](http://physics.nist.gov/cgi-bin/cuu/Value?r|search_for=gas+constant)
Mass Earth = 5.9742e24 kg (from libs.h)
Radius earth = 6378135.0 m (from libs.h)

Constant = ((R/G)/Mass Earth)* Radius Earth^2 * 1e3 = ((8.3144621/6.67384e-11)/5.9742e24)*(6378135.0^2)*1e3 = 8.483323e2

848 is very close to 855. Perhaps Tomm rounded something to a significant figure too low or something minor.

***
Now we know where that 855 came from:)

The mass/radius should be converted in the equation for clarity and, a constant named R/G or something, used.

k, as referred in Tomm's comments, is the energy needed to heat up a particle by 1 Kelvin, whereas R is the energy needed to heat up 1 mole of particles. Depending on which you use the mass of air needs to be in kg/mole (molar mass) or kg/particle. The molar mass is quoted very often since it's easy to convert the atomic weight of a molecule to molar mass so we should stick to moles-R and specify I guess (eventually, as Tomm mentioned, each atmosphere should have it's own different average molar mass).
Don't do a bare print, we have a logging system in place, see PyInstaller.log.
Can you fix this check and use QDir::operator==() please? :)
that is just the normal composer behaviour. if the commit is exactly the one of a tag it puts the tag name, otherwise it says the branch and the hash. i thought i was reading composer.json, sorry for the confusion
The `listBodyToInfo` method with an `OriginAccessIdentity` class should be used so that the API is the same as the rest. I have not read the API documentation in detail, but I would think it should go fine.
It sure does.  In fact, it doesn't compile.  It's from 1b5c89e - your commit.  I'll see what
This is correcting a mistake that was made earlier.
Tests not DRY.  Abstract common code into helper methods.
What does the `{}` do here?
I vote for help(galsim.Sersic) too.
I think e,beta are defined in a previous demo.  Demo 10 comes out of order in the github listing.
I have a habit of using a "texit.sh" script in for building latex.  I like to have .ps output as gv automatically updates the image with its watch file option, and .pdf is more generally preferred for output.  The dvips I have installed makes a4 format by default, and it's just a pain to have to write `dvips -t letter atmos_factfinding.tex -o atmos_factfinding.ps` every time I want to check how an equation got built.


On 23 Jun 2012, at 19:21, Mike Jarvis wrote:

>> @@ -3,3 +3,4 @@
>> *.log
>> *.ps
>> *.pdf
>> +*.sh
> 
> What is the reason for this?  I don't have a problem with it.  Just curious.
> 
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/GalSim-developers/GalSim/pull/202/files#r1038533

--
Barnaby Rowe

Jet Propulsion Laboratory
California Institute of Technology
MS 169-237
4800 Oak Grove Drive
Pasadena CA 91109
United States of America

Department of Physics & Astronomy
University College London
Gower Street
London WC1E 6BT
United Kingdom
Ok. Let me write a more declarative comment.
Given it needs to be non-null later... checkNotNull(command, "command")
why are there two different styles ('.' vs '-')?
It seems like it'd be more helpful to either default to something here or print a warning that cache_type must be specified with cache_servers.
Tönd die matter befehl nöd de vom book überschriibe? und wenn nid chamesi sicher mit irgendemne renewcommand überschriibe.
I weiss eifach no dasi recht problem gha han mitem fancyheadings i de bachelorarbet... weiss au nüme gnau wieso.
Não seria melhor simplesmente apagar o usuário caso ele exista?
I don't understand why that wasn't done in the first place. Makes more sense to import the `routing.yml` from the AcmeDemoBundle.
For this and the above, can we remove the self param now?
Why are we assigning the parameter to an instance variable before processing it?  I would expect this method to be side-effect free.
Would it work to simply reduce this method to a single line:
```
response.xpath("//xmlns:#{thing_to_get}").text
```
I think "recent contributors" is not specific enough. It's really "recent contributors for contributions that weren't approved" or something like that, though I'm still coming to terms with SUMO lingo and maybe "recent contributors" is sufficient.
Don't leave commented-out code in your source files. We can see what used to be there with git diff, if necessary. Commented-out code just makes it harder to read.
This comment reads a little awkwardly. (and it should be "states")
Actually all targets have that constant together with that comment. The define is being used at pios_sys.c.
@zghorn this broke UMD. merchant should not be a user right? merchant is merchant
Locale.getDefault() можно не писать.
test still has caching disabled, but I don't think it should be. Instead it should have caching on but use the null store. I'll push that change.
I tested locally and found this File.expand_path is not necessary. You can just do "require 'spec_helper.rb'". Is there a reason for the extra noise?
Corrected on 450783b768df6 commit
`/var/log/xhprof` should be prefixed with the homebrew prefix.
sometimes when we click submit a new app the developer agreement is cleared by default because it was accepted in a previous submit.
if that is true then the clicking continue and accepting the developer agreement  will be invalid because we are in the wrong pge
I think it could be something like `get_test_app_data` or something to imply that you're just getting a list of data.
hiddenは英語の分を隠す目的でツールが使っており、日本語のコメント用には使わないほうが良いかも。書くならnoteのほうに書いて良いと思います。
over 100 rather than dozens?
It is indeed still a bug case on 10.12.0.
It would be useful to have `multiclass_classification`, `binary_classification` and `regression` markers.

For instance ROC AUC is binary only (no multiclass) while `f1_score` can deal with both binary and multiclass. Later we migh also have new scorers or refactored existing scorers that can deal with multilabel and ranking problems.
This constant (and the lines below) seem to me to be for internal use, do you think they should be exposed in `__all__`?
And Numpy 1.3? It's in my Numpy 1.4.1, but I believe we should support 1.3...
if such a big figure is included in the doc it's likely to screw up the layout.
>  >  from .stop_words import ENGLISH_STOP_WORDS

>    Should this constant be exposed here?

I think so
This will still need to be properly validated
See below, the clas is called `IllegalStateException`.
Tomorrow, I will change it do explicit checks against the 7 http methods. Bit cleaner.
Sounds like a good plan!

I'm sympathetic to the change. The timing of it, not so much. ;)
How about "turn"? Better?
should the function really return OK when when we end up here?
what's the reason for not having it as part of this patch?
@dlifshitz-maca : Done
Put assert(calculatedValue != NULL)
With the new rails version, you dont need this line!
Ok. Then we should update the release notes of 3.1 to write this as one of the non backward compatible changes.
Some confusion about whether talking about CXX compiler or C compiler?
1) The HT is never added to once the spilling of the HT starts - it is used as a filter to dedup as much as possible only.
All non-filtered rows (complete) to go disk.

So the comment re. duplicate entries doesn't apply..

2) Original pre-Richard's observation, N elements were removed, leaving 'holes' in the HT, where clashed entries would be missed.
The 'remove entries that follow' is there to deal with that.
However even before -ve matches are 'ok' here, it is a filter only, it would merely mean that it misssed a possible filter and sent the row to disk.
The change means it spills those rows up to the next diff hash (or NULL) also, because they can't be matched.
Gavin good idea, I added the test for numCommited
Jake, that got lost in my GitHub disaster yesterday morning. Just added it back in  (so much easier the second time around)
I don't see any comment saying you should remove -legacy.  If there is a problem with createrow that needs investigating.

I suspect the majority of the examples in the internal regression suite would fail to compile if legacy isn't enabled.
This is not threadsafe
builder is a bit of a generic name.  loopInputBuilder might be better.
Instead of making these methods lazy, we should consider setting these values ( list of roles, privs, users, mappings, etc) when the config changes.
This could reduce the amount of locking code.  In most cases we need all of these collections to function. ( EnhancedConfiguration works this way )
This option is very specific for MBP users (and maybe only your 2009 model? BB has been reported to work for other MBPs). The comment could be more clear (less technical, more to-the-point).

Alternatively, this config can be split in a new xorg.conf.nvidia-mbp and use a different `XorgConfFile=` value. This "works" but is a less out-of-the-box experience for MBP users since they have to edit bumblebee.conf. Is that acceptable?
this is only 5.4 right?
use log instead of sys println
just style nitpicking here but using unless is much more readable in these instances
typo - dtabase -> database
While we are in here can you assign node[:db][:dns][:master][:fqdn] to a variable and node[:db][:dns][:master][:fqdn] == "localhost" into a variable since they are used in more than one place?

For example:
my_fqdn = node[:db][:dns][:master][:fqdn]
is_localhost = (node[:db][:dns][:master][:fqdn] == "localhost")

This will clean things up a little.
The group name should be based on the name of the redis_failover root node, right?
Actually, since you use this consistently throughout, I'm happy if you just keep it ``(width, height) ndarray`.
It would definitely be a good idea to also support passing a function object as `method` parameter.
It's useful because people get use to seeing properties set in a certain order (or at least I do; I did notice).  Of course our code doesn't care what order they are set, but it is one less barrier if they are the same.

If we need all the position code together  - which is not a bad thing - we can move the assignment to `position` down.  I organized the code like this because I like the constructor function to do whatever processing and then assign to all of its members in one shot so it is obvious when the object is fully initialized.  Constructor functions that set some properties, read from them, set some more, etc. are harder to follow.  However, this constructor function is trivial enough that the grouping is less important here.
Okay, ignore everything I said so far in this thread because I clearly haven't had any caffeine yet today.  You are completely correct.  It's a bug and a happy accident that everything was working because of I'm wrong twice and they are cancelling each other out.  I'll fix it.
@kring perhaps this was here to account for a swizzle at some point?
Usings inside namespace ?
I have been struggling for hours on this - tableview touch events don't fire for me on android. I will to speak to the platform team.
Can't inline it, it's recursive. I called it "scan", but it's basically the replacement for the "walk" function. I was testing them side-by-side, hence the name difference.
it would be simpler to name it ``ornicar/message-bundle``
If the casted type is a pointer, the pointed object is checked whether it is the requested base class. If the check succeeds, pointer to the requested base class is returned, otherwise NULL pointer is returned.
If the casted type is a reference, the pointed object is checked whether it is the requested base class. If the check succeeds, reference to the requested base class is returned, otherwise std::bad_cast is thrown.

Вообще предполагается, что это редко будет происходить (а если пользователь не мудак(такого не бывает, но все же), то никогда). Насколько дорого юзать try блок, ничего не кидая? Может быть пробросить наружу bad_cast

Можно, конечно пошаманить к сведению к указателям, но выглядит, ИМХо, вообще не красиво.
Please add an explanatory comment (instead of the bug reference).
redundant control flow, remove
Thanks. Actually, that comment is out of date and can be removed; Slice does manage the Appender's reference count correctly now.
agree. maybe we can change it to use mirrors in a follow up?
Compile scope is default, no need to specify it,
I'm fine with this, but are we calling shard_name() enough to make this worth it?
This function also needs to push this information into the $person->data array. You can see examples of this in some of the other loaders. This is because before the load function is called, the data array is checked first to see if the data has already been retrieved and set.
@willdurand I copied it from the UserProxy. Is there a better way to achieve it when being in the model itself ?
this one should not be removed. It is an extension point to allow people changing the redirection url if they want to use the changePasswordcontroller without using the ProfileController
could you add also `waitGui` and `waitAjax` ?
the `url` is not needed
This shouldn't be here. The extension class already aliases the default DM to this service ID.
The preceding four lines are commented out - why are they here?
Using _.isFunction() should be more appropriate.
Ah, I see. Because you need this in the controller and as helper in the views.
Forget what I said ;)
Since we already do this with all our jQuery plug-ins (even the none sakai-edited ones) - can we wrap this in

```javascript
require(['jquery'], function (jQuery) {
```
If output is redirected to a different stream of errors, then the two flows warn of the problem. There are other points in `build.py` where I have introduced the same scheme with the same goal, see `closure` and `closure_ws`

On the other hand `print` is used heavily in `build.py` and `mergejs.py` , so I thought it would not be a problem.
Such a warning applies to all Windows C file functions that take a char*, not just these 5.
This is likely controversial. Shouldn't we better leave it to the user to do this inside their own @trusted code?
See my comment below about what should be in this template
How critical to you regard this? I could fix it later this evening.
I hate to make this even longer, but the above sentence about the correlationID is not true for the temp-queue case where no selector is needed at all.
I guess its an English thing. Yes, what I meant to say is that its slower since we are going to be creating/deleting consumers. Any better way of phrasing it?
Does this fix work both with all other browsers, and also fixes IE? Has it been tested with those browsers?
I would recommend using just this (which works in Composer since about an hour:)

```json
    "autoload": {
        "classmap": ["Dailymotion.php"]
    }
```
OMFG, fucking rookie mistake, why does I need to git add first? :P
sorry, what file i have to change ? because int validator is not in zend\validator namespace. i can't find file of ToC
Actually no, there's no data bag, at least not now.

Look at the README for each cloudfoundry-* cookbook for more attributes.
the minimal example should not even have a repository as its optional too. just to avoid people writing useless boilerplate repositories because of misunderstanding, i would remove it here
I think it should at least check if all required fields are provided
Use the ..note syntax:

```
developers/Build.txt:.. note::
```
I don't know -- I didn't change that line -- I just added the Description and Comment tags.
I think the original way was correct ...
Add the polylines layer.
I am not sure if we should be doing any sorting ourselves. It is enough that original mongoengine document has fields defined like that. django-tastypie-mongoengine fields are used to define tastypie resources. Some resource fields can be automatically defined from document definition. But for some you have to help django-tastypie-mongoengine a bit. And then you define the field manually. And this is why you have EmbeddedSortedListField. But you define resource field, not document field. And resource field does not care about "ordering" or "reverse" (or at least I hope it does not have to care).
чистити автоматично
Of course, but after looking at it, the code in question doesn't strike me as so complex that is would take hours to reimplemented this functionality.
D'oh! Good catch. This made it's way into later code and I've just fixed the mixup: https://github.com/mozilla/django-browserid/commit/bc9ea86874aab7ab2f52adb86be5703538583507
See other review for actual feedback.
"if (itemId) {"?
Lint error!!! `testLocallAccess` must be defined before `testLocalAccessFails`.
в плагінах для LiveStreet ми дотримуємось CodeStyle саого ЛС. а там дужки не з нової стрічки
module Citation
      def self.map *args
         Base.new *args
      end

      class Base
         def initialize item
            @item = item
         end
      end
    end
IMO the 'close' action should not 'remove', the idea being that if you call open again, it should simply open the dialog as we created, and not have to manipulate the DOM all over again. Does that not make sense to you !?
Yeah, I was talking about validating the syntax of the fields themselves, e.g. for each field in fieldList : field must match `/^[a-zA-Z0-9]+(\.[a-zA-Z0-9]+)*$/` -- or whatever it is that defines the proper syntax of a field.  And if it fails, generate an error to the user.  We shouldn't be making assumptions about and corrections in user-defined data, behind the scenes.
This and getVersion feel like class-level methods.  There's nothing specific about the instance contained within these methods.
Don't need the version protection. Titanium supports 4.0 + only
Suggested rename ?
Why \\Redis? Class definitions through string are already Fully Qualified Class Names.
You can use Redis alone.
We use getQnxNamespace everywhere with the twofold purpose of handling if the namespace changes and more easily mocking it in our unit tests.
Скажу честно - даже с супер-модными лисьими моз-костылями постоянно приходилось 150 раз кликать по вкладке, чтобы сбросить ее счетчик. Разницы никакой.
Should probably also do a;

`data["rim:permissions"] = {}; //ensure no run_when_backgrounded permission exists`