labofsahil/github-event-dataset-2012 huggingface dataset:
Too many descriptors for `rect` property in the doc. For `rect` we have frame, size and position at various places.
Ugh! Noted, thanks.
According to the documentation, the callback is invoked with the error object being not null.  Until there is reason to think otherwise, this should be sufficient for handling fail cases and getting the desired output.
Yes, eg. a view in the window, only window has the listener, when we click the view, the window's listener should be invoked.
declare as static inside fireApplicationAnalyticsIfNeeded:
I haven't checked the cell textLabel code but isn't it already set to default font before configureTitle call?
psh. semicolons.
Why import this (it's in the same package)?
Yah usually, but I like fence in this case.
@scottgonzalez @jzaefferer Improved error handling if you run the server without preparing it first. It checks if all necessary releases are present and valid.
Why don't I just change those in a separate PR for all demo files?
I would much rather this was a simple "x or y or z" construct, rather that this meta-programming.  It would make it much easier to see what was happening to read:

    return discover_by_pxe or discover_by_dns or discover_by_dhcp
Ruby has functions for checking if a path is absolute. That would be much clearer than a hand-rolled regex here (and also more compatible - on Windows an absolute path doesn't look like this)
Я буду счастлив, если ты не будешь коммитить трейлинг вайтспейс.
space after your colon
Can we stick to 1.8 hash syntax?
nit: `<code>` tags around the `=`

I'll stop pointing these out... you get the idea :)
By restricting types `isNested` can accept we reduce a potential to use it incorrectly as using `isNested` not inside `static if(is(T == struct) ...)` is dangerous. I.e. we unsure `isNested` will be used *only* if a user has a `struct` or `union` he'd like to test and `hasNested` will be used otherwise.

I hope in the future we will be able to check if a `class` is nested. Probably you can help with this by adding a new `__trait`. And `isNested` will also be able to check classes. For now if it will accept class it will silently work incorrect. And, illustrating my point in the first paragraph, we will have to carefully rewrite `hasNested` to not make a mistake.
I think `std.conv` might be the place to put these, seeing as `emplace` is there.
typo s/kept/keep
You do all of this to speed up this function, and you always decode the characters at the front of the string? Wouldn't it be faster to check whether they're ASCII before decoding them (and then use std.ascii.isWhite or std.ascii._fastIsWhite for ASCII characters)? Even if you made `std.uni.isWhite` faster, you're still decoding here. Or is `decode` actually fast enough to make it not worth checking whether the character is ASCII first?
Would be good if this also added a note to the edition so editors can see why the edition is archived.
I don't think we really need this test, all you're testing here is an object's `save` method (which you're not actually calling). Given there's no extra functionality included or hooks, I don't think it's worth it.
I just wonder if it would be more helpful to direct people straight to the tests? Tell them they can't actually deploy the app in a meaningful way at all.
I only know that if this isn't added, the graph database doesn't work. I havn't investigated any further
We should def make it not set pixel format after video is loaded. 
I'll try that for now and then lets see if that fixes things.
please use ``{@inheritdoc}`` instead of duplicating the phpdoc of the interface
Indeed. Sorry for that.

What about `Il contient un lien sur lequel il vous faudra cliquer [...]`?

Also, I suppressed the circumflex of `s'il vous plait` (1990's Reform of French orthography). Any thought?

PS: Now the pull has been requested, is it possible after that to rebase the branch in order to have a unique commit? I think there is no problems, but I am new in Github. I have no idea how to do this without deleting the remote branch before rebasing. Maybe rebasing is not necessary, and the submitted branch can be safely deleted after merging into the master branch. Thank you.
is this sorting still happening api side? As we dont want the origin when sorting measures so UK measures are inline with the EU (on third country measures)
classmethod calling a staticmethod, are both needed?
ContentType is not used in this file. Why this import?
I just saw that the current code don't respect pep8. I'm going to fix it.
This function is only used in the following way:
`.bind("click", collectionClicked);`

Because of that, the use of this is valid to me. However, we should change the function arguments so they include (ev, ui). This also makes it clearer that it's a normal even handler.
`std::shared_ptr`
Hey @samvincent,

could you create two posts here, so that we can see the count going down from 2 to 1 when filtering?
This one is easier to read. I consider this.
For a non-parameterized map, where i>0, I wonder if we should spin through the keys and, if they are all Strings, map to headers instead?
mixed leading spaces and tabs on these 2 lines

    git log -p --check
Why this method takes **String** parameter?
Take a look, please, into `UpdatingJpaOutboundGatewayParser` & `JpaExecutor`. I'm about `persistMode`
Good catch. Changing it
ок. заменил
`needs to bee well thought out.` -> `needs to be well thought out.`
Since you patch `ActiveRecord`, shouldn't you have a dependency on `activerecord` as well?
这个补丁我用实际数据测试了，工作得很好。但是又发现了一个问题，就是所有类型的文件都会调用copy_content_to函数，这太低效了。

能否用更优雅的方式实现这个流程？
Where is this statement? Is it in a file? If so we should mention it.
keys and values are the same
Right. At this stage the propagation of errors isn't complete, so it's not fully reliable. But it's probably getting close enough that we can start doing them properly.
BTW, it's been a great strategy. The quality of errors messages now is fantastic, I hardly ever see spurious ones any more. Probably something we could market more, especially to C++ people.
Sí esto lo agregué así como para tener un modelo para cuando el tema este esté más cerrado.
Let's nix this and adjust the `get_backend` below to `get_backend()` that references the `PublishedItemFilter` instead of the function.  Properly worthwhile doing the same for `find_related_models` by leaving it with a note that it's deprecated.
just don know what to do
`Indicates whether the scroll event occurred while the user was dragging.`
Can you expand just a little further here? This is not just "general" but specifically focused on UI operations and Views
`navController` is actually a misleading name for this since it indicates the modal controller is always a nav controller (not necessarily true)
Again, leave out the constant stuff.   Also, "mimeType as the file's path" doesn't make sense.  Maybe "and sets the mimeType based on the file name".
Please follow the existing style and use the braces (if (...) { foo... });
We actually should have documentation for this method, so that developers are aware that this (and other `TiBase` methods (and macros?)) are available for their use.

On the other hand these APIs are incredibly volatile and may change, so...
I brought it into full alignment with #3.
assertEquals is deprecated; please use assertEqual
You don't really need a service anymore as the service is now private.
Typo in comments, fixed in last commit
Should there als obe validates_length_of :summary? Or perhaps some computed fields for frontpage Drafts, and top ideas (title + summary).size > 2?
Removing this condition will fix the bug? I just do not understand why it was added here.
That was specifically done for TomEE, so maybe not all embedded container are working the same way?
I'll add a comment that the dependencies below that are test dependencies, most maven poms look like this, and someone familiar with maven would notice scope=test below the blank line, I'll make it more clear though why the space is there.
I'm sure there's some nicer way to make this a parameterised injector, but I didn't understand how to use it from the injector.md docs, so this was easier ;)
http://en.wikipedia.org/wiki/Whitespace_character#Definition_and_ambiguity

Personally I've always preferred "white space": I can't stand when words are randomly concatenated...

I don't have any strong preference, though. Just saying that it was correct before, either way.