labofsahil/github-event-dataset-2012 huggingface dataset:
Названием метода со строчной. Аббревиатуры надо писать как обычное слово -- Rpn
И по этому исключению нельзя понять, что имено не так.
Сделай unit-тест лучше
There is a patch against smack to connect to jmdns, but jmdns itself is a separate jar.
Still typo here in 'paypall'
I can't see restmail in this commit!
I would rename this to `sample_without_replacement` to make it more explicit.
Yea I noticed it too, any suggestions how to fix this?
I could add an additional parameter like max_number_of_strong_rule_iteration, but I don't really like this.
I think these sanity checks are done by incorrect way.
`{ __traits(isPOD, 123, 456); }` will always fail to compile, because it will report `has no effect in expression` error.
Instead, you should write as: `static assert(!__traits(compiles, __traits(isPOD, 123, 456) ));`
Currently, the time it takes the full test suite to run is a significant bottleneck.

I've been doing this style for a long time, and having a few files filled with large numbers of tests works out pretty good.
symfony-bundle
Should also validate the that the string actually represents a valid IP address at the same time and fail if not.  You can use socket.inet_aton for that purpose
Agreed. These were copied from the WebServiceManager. Could probably be consolidated in that category.
Space/tabs
Why does this case have one more parameter than all the others?
(Note, The code generator would almost certainly only evaluate it once because you are calling buildSimpleExpr(), but it wouldn't be guaranteed.)
I think I don't get that problem because I have set 

eclIncludePath=

in my local eclcc.ini file.
If I got it right, the empty array will not be used, since at the time of read, a local file will be read (via ```jfile```). This might, however, be a side effect and not the original intention.

Another problem is that, with the current behaviour of ```jfile```, a local file might be returned successfully, but not necessarily exist. Normally, it'll be created on demand, but if errors occur, it might be difficult to understand what's going on. If we are to use IFileDescriptor and IResolvedFiles, there might be code inside that assumes the file was guaranteed to exist (I believe IResolvedFile do that when it's a Dali file).

Since Roxie code was mainly tested with Dali files, I'm not sure how stable it'll be with local files. I have the feeling that some things are working out of re-use (and a bit of luck), which is not necessarily planned ahead.

Maybe it'd be best to leave this for after the URI naming system is implemented...
shouldn't it be ``$fileInfo['error']`` here ?
I changed the url in urls.py but was basing the URLs in the original commit off of @rhelmer's comment on issue #51, which uses that url format. I'm not sure where on the site that's used, though -- I only references to builds.rss on the production site.
I'm probably not understanding you Rob but the caching stuff is done by URL so it wouldn't cause any extra roundtrips. 
One cached value for the just products and one cached value products + versions. The versions rarely change and it gets baked into the cache key.
Just a style nit, but can we move these declarations to where they're defined? It'll be more consistent with the rest of the code, and we can always "use strict" if it's a problem
This doesn't need to be a sorted dict anymore.
Add message to assert
Isn't css/js cached by the browser throughout the site?
after a quick discussion; we are going to skip this for now.
Should this default to "WORKGROUP" instead?
Not sure what the preferences are, but I am not sure of anyone that puts a space before and after the asterisk here.
error = [ res.body.scan(%r{<faultstring>(.*?)</faultstring>})) ]
Can be simplified like this:
```ruby
ni_packet = type + [0,version,cmd,0,0].pack("c*")
```
We are using db_provider to differentiate between mysql and postgres. We set it in recipe "db_postgres::default", only then recipe "db::install_client" will get into appropriate provider and install appropriate packages. Also the recipe "db::install_client" gets executed independently later.
JFYI- We have already set "db_mysql" as default provider in cookbook db attributes file.
Check for the first positional argument.  If that doesn't exist, use the first keyword parameter instead.

One thing I'm worried about with a decorator like this is that it returns a modified signature and docstring.  I remember this package takes care of that:

http://pypi.python.org/pypi/decorator/

But perhaps we can just "transplant" those attributes by hand.
I've run these many times.  All of the tests which assert regions of labels == 2 randomly fail on my box.  There's no pattern to it.  Perhaps try running a few times, and seeing if the 2Ds fail the same way?  The behavior of 2D is equivalent to 3D on my box - I've seen both pass, both fail, and subsets pass or fail.  Of note, I observe the exact same behavior from the most up-to-date version without my changes, but not from the 0.6 stable branch.
Yeah we didn't change the base driver class unlike volumes, so using it with another driver breaks. I'd go with check hasattr and raise UnsupportedDriver
I think you also should "css namn" one word, like "css-namn" / "CSS-namn".
Me and @shunter discussed the reason this code was changed and he ended up making further changes (see 41c8e7f)  which improves Jasmine testing overall and ensure our `equals` methods are always called when available.
1. Yes, JSON needs quotations, but technically you are not using JSON here, you are simply defining a JavaScript object.  If you were defining JSON as a giant text string and calling JSON.parse, you would be correct, but that's now what's going on here.  I stand by my statement that the left hand property names don't need quotations and it would be cleaner to remove them.  @shunter will probably back me up on this, but if he disagrees, then I will cede the point.

2. Same as 1, you are not using JSON here, you are writing JavaScript.  They are different things.

3. Right, but when you are in JSON you have no choice but to use the string name, in the code we have better options.
Yep, once again, old code.
Same comment applies to all the other CzmlTypes too.  Seems like they all work that way.  Are there any that don't?  Do we need both functions?
I'm actually shying away from code like `this.updateForPick = function(context) {};` now.  This code is from my earlier JavaScript experimenting days.

As you can see, one PIA in our graphics code is some changes to a primitive (material changes are probably the best example) require a shader recompile, and we need to carefully track these changes, and only recompile when need be.  Another strategy that I want to explore is compiling shaders on load - at least the ones we know we will use.  This will also help us help the driver compile them asynchronously.
If we get it for free, then sure, but I'm not sure how often jitter will matter during morphing.  How often will the viewer be close to the tile?  Given the morph, will the jitter even be seen?
Let's also use the bounding volume to avoid the wrap longitude code in 2D and Columbus view if the polylines do not cross -180/180, e.g., check if the sphere intersects the plane y = 0 and is in the half-space x < 0.  I have some code in the polygonidl [branch](https://github.com/AnalyticalGraphicsInc/cesium/compare/master...polygonidl).
It improved the performance, the reason is that here is a query performed around the DOM of the page now works only on the branch of the DOM that contains the table.
Doesn't this lead to unnecessary memory usage?  Are we ever disposing the channelfactories?
You could use FirstOrDefault from LINQ.
Similarly, can't this entire method go away, now that > iOS 4 is the minimum support bar?
So no "since" at all?  (I guess the since is kinda irrelevant -- it's either deprecated or not, and what's more important is when it ain't gonna work no mo.)
Right.  I think we need to make the language clearer then.  Maybe more conversational... like... "Implementing markdown in your project?  Check this out" or something.
A much more complete list already exists in the wiki here: https://github.com/markdown/markdown.github.com/wiki/Implementations We should simply link to that page rather than reproduce an incomplete list here.
I can't be sure this fixes for all version/platforms. But latest Mac Arduino version requires this name.
Давай не использовать отсуп в 4 пробела. Ниже по файлу тоже.
Да. Существующие неймспейсятся, и неймспейс точно нужен. `uploadcare.dialog.open`, наверное.

Давай, может, отрефакторим ивенты вместе со всем остальным? Схему предварительно можно нарисовать — так взрослые делают, я видел.
I used it during development, but since it may become useful, I'll leave it in.
Need to delete one more `</div>` tag here
`<var>furniture</var>` should be `<var>furniture()</var>` towards the end of the question
Since you do leave a space after "for", please also leave after "if". Thanks.
There's a fair amount of uses for `stack[stackLen - 3]`, `stack[stackLen - 2]`, and `stack[stackLen - 1]`. How about defining locals `third`, `second`, and `top`?
Change is here
Well, I have to agree here, but @boegel has other views
it's a dependency already, no?
i would assume that specifying it further as builddependency is overkill, isn't it?

If this was required, it would have to apply for all deps I guess...
Reverse these two cases, early exit.
Pass. I can see cases where they would be useful (and where going via a dataset will not work).

```
theNaughtyWordFilter := IF(inUSA, AmericanFilter, UKfilter);

isNaughty := name in theNaughtyWordFilter;

output(theNaughtyWordFilter[name].euphemism;
```
You're checking if you should send an update before you schedule. That means if the updates arrive in a different order on the schedulers you'll be executing them in the wrong order, and end up updating with old values.
The target schedulers are different, so even though each scheduler is serial on it's own, this can happen.
che, que onda, hay un test xD la puta madre ¬¬
both inlined
It's looks nicer in github
Have you looked at the compass reset function? http://compass-style.org/reference/compass/reset/

I don't know what specifically it does, but it might be worth looking into.
That's indeed an issue noone noticed before ;)
will be fixed in the next push
I don't think the normalization section is necessary, could you elaborate why it is here?
Fixed. However, the composer autoloader did not pick up the rest of the bundle so I left the next section of code as well.
@KingCrunch 

The problem is, though, that you can't use a decent IDE (e.g., PhpStorm, which highlights variable substitution) in all circumstances. Thus, I agree with not being to strict with  enforcing *concatenation* vs. *variable substitution*.

On a separate note, one has to ask what's the point in coming up with a standard that's just a redundant backup of existing standards, e.g. PEAR.
This should be a `{Number}`
How much do we care about graceful failure in the case of bad data? For instance, if the `name` or `description` key is missing from a particular case, should we gracefully log that error and continue with the rest of the cases? Or should we just die and have the transaction rolled back?
Yes good point, I added the event to the `$rootel` and changed it to mouseout as well.
I don't know if this has been committed over the top of yet, but this is NOT the way to call other templates.

Drop these two lines to the service.

Change line 332 to:
<% print func.callTemplate("Default Patient Identifier", { "identifier", identifier }) %>
Good point. Fractional Time is actually supported in MySQL 5.6.4:

http://dev.mysql.com/doc/refman/5.6/en/fractional-seconds.html

but since we aren't doing any time calculations, I agree and we should store the time in ms as a long value. For 3.0 we may consider using sequential ids.
Won't fix. The primary use case for this MD file is to be converted to HTML for display in the browser.
Nope, you only have to call done() if there’s outstanding async work that has to finish first. Since this is all synchronous, no need.
It feels it would be cleaner to first catenate the string then call length once. And maybe even just use string interpolation instead of catenate with +.
That's true.  Well the post event show be enough in this case.  Thanks man, I'll go ahead and merge it in.
This seems unnecessary. Why not just always delegate to the `item` for checked state?
That object seems to be non-writeable. That's way view.settings() is there.
For anonymous functions, spaces around `()` works better.
As an example of embedding the version unnecessarily, could this not simply read "To obtain the development version of OMERO.server, clone the git repository from <URL>"?  Note the "src" typo here also.
action already translated in Admin->getBatchAction():
https://github.com/benoitpointet/SonataAdminBundle/blob/08f46affe3e9dacb60fc8994612fdf11532219c2/Admin/Admin.php#L846
Can you put parens around the arguments in all the method defs?
can you explain to me how this will be implemented in tables?  I think you might need another table just to keep track of the UserLocation links to Locations.  I would prefer you make this a single Location, and use service methods to search for multiple UserLocation objects for a given User.
Yes, I understand that completely; but when we discussed this a couple of weeks ago, we agreed it was not the approach we were going to take, instead we would have a single URI string with markers for where data would be replaced.  

For example, say I have a REST style API that supports multiple formats and it's designed for data to be requested in one day increments, the date is build into the URL and not a query parameter, so for August 17, 2012, the URI looks like: http://myapp/2012/08/17/?f=czml

My URI in the CZML would look something like: http://myapp/{Year}/{Month}/{Day}/?f=czml

And then the client would replace the TIME tags with the simulation clock data.  This isn't possible in the currently proposed schema.  The example above can be used for all kinds of URIs.
use ``<2.2-dev`` as ``2.2.0-alpha`` is lower than ``2.2``
move this to public static and unit test individually
NGUTPR
Python 2 only style print?
/mnt/sw_jobs/u8989/user_dir/prawn_worker.rb:27:in `run': PDF::Reader::UnsupportedFeatureError (PDF::Reader::UnsupportedFeatureError)
       from /mnt/sw_jobs/u8989/user_dir/runner.rb:363:in `<main>'
Are we sure this loop is correct? What are the possible values of extra_parameter_count? I think it will be > 0 right? If so the loop will never be entered.
@etiennesegonzac  just pushed a detailed information:
https://github.com/telefonicaid/Gaia-UI-Building-Blocks/commit/d62dce8fa3eab08b335254c47e0909562480696b
this file should be called valueselector/single.html to denote the fact that it demonstrates the use of the single selector. we can have an index.html to provide an entry point for the demo of the different components.
do we have a better way rather than depending on a static block to do this?
_IndexingInterceptor_ and _EntityIndexingInterceptor_ both work for me. Undecided which one is better. I like _IndexingInterceptor_, because it is short and crisp and _EntityIndexingInterceptor_ , because it defines the feature even more accurately. so + 1/2 for each :-)
Should I go ahead and change this message for all the other tasks too?
а почему в листе много элементов хранится?
T operator() const (size_t n, const T& obj);
We should also state that using the image loader is the preferred method for getting images from a remote source, as it interacts with the image cache and may result in better performance.
looks like a start of answer: http://stackoverflow.com/questions/3874422/developing-with-djangocelery-without-running-celeryd
Better to use instead 2 lines 53 and 54 ony 1
```php
$language_file = array('ucp', 'mods/socialnet', 'mods/socialnet_acp');
```
reading the return statement is just as easy as the comment
unnecessary comment
Solution is {{ '{%' }}
So `(self, request, view)`  [Yes, I know]
I am little confused, we already had a test/functional/automation/blackberry.app.js file, right?
what happened to that file?  I was expecting this file to be appended to the existing file.
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 122880
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq 800000

this too, because its on kernel now
We need to extract the GFK code out of arm_wells rather than pull in the entire project.