labofsahil/github-event-dataset-2012 huggingface dataset:
I agree, the util.js in the driver and hub should be renamed to avoid confusion with the standard util module.  Unless this is seen as critical for this PR though, I will push this to the next PR along with several other clarity changes.  At this point, I would like to avoid making large impact clarity changes unless we really need to.
@BlainHamon these used not only for counts, but actual iterations too.
`$('<section/>')`?
You can probably delete this comment, and the comment on line 83.
Please escape this.
For some reason, I'd like to see a new VideoExample().run() here.
I'll go with source.
why is this code needed?
We actually use jshint (which uses jslint underneath).

Although I'm not sure if we want to disable this check. I think this check is good because it's easy to make scope mistakes inside loops.
I don't know that we want to fail the test. I think maybe it should pass with a message. Otherwise every time we run this on 4, we'll have to check what test failed.
this should go into your global git config, its ide specific, not project specific ;-)
Если будет много диалогов одновременно, то нет. Но вроде не будет.

Это добавляется для энд-юзера; можем сделать классом.
Тут замысел такой, что этот флажок можно включить атрибутом `data-multiple=''` (аналогично как хтмл5 атрибут `multiple` у файл инпутов), поэтому пустая строка тоже считается как **on**.
нужно поизучать функции из allgorithm
I see how that works now. I'll fix it (tomorrow).
I'd suggest flipping the `if` and `else` blocks so that you don't need to use a negation in the `if`'s condition. It's generally less error prone to arrange your conditions so that fewer negations are needed, and when it's a simply a matter of flipping the `if` and `else` blocks, then I think that it's definitely a good idea to flip them.
Why all of the capitalized names? If they represent reified concepts you'd need to define them. (I don't think that's necessary though.)
Except it's not always there. In fact, it's often not there. This is very OS and distro dependent, unfortunately :-/

Maybe something like:

> If you are using Git < 1.7.1, you will need to edit git completion (usually `/etc/bash_completion.d/git` or `git-completion.sh`) and add the following line to the `$command` case in `_git`:
not sure how @sigmundch feels about this, but IMO we could remove the "listener" prefix, seeing the element id and the event name should be enough to know it's a listener
I agree, But this is how kenneth likes it...
It would be nice to have an instruction about how to restart the domain.
Our coding conventions actually would want an array formatted like the following:
<pre>
$default = array(
    'target' => 'helpdesk',
    'bot' => 'browser-agent/1.1'
);
</pre>
This file has been reviewed..
two comments on these lines.
- undef does not equal false, so these class params need to default to false (and not undef_
- you dont need the - in -%>, that is only needed when you want to ignore a trailing newline in the compiled file
shouldn't this be ``{}`` ?
double meh.
Nit: The line length is really long, it'd be much easier for reviewing to keep it around ~100 characters/line
I'm not sure that type can be accessible - it's a build in override.
Move the `metalink_*`stuff to metalinkerHelpers.js?
The query is limited to 5 results, I don't really know what the policy is.
We should just make sure that the bundles behave properly, so I suggest we improve the validation on that value to allow only a boolean value or the string 'auto'. I think you can do that with the configuration classes (just don't know it by heart). 'auto' is then fine for me (it would be the default any way if I specify nothing in the config ...)
könnte man entfernen, ist aber eher unwichtig
i'd also remove this comment
Not sure about this. There are great projects (like SabreDAV) that doesn't make the public keyword explicit.
Can you remove the extra spaces from `[   ]`
We've got a ticket for api-ifying this across the system. Given where we are in the release, we should hold off and do this in one fix, as it will touch lots of places in the UI.
Is there a reason to keep this since it is empty?
Not exactly

Let me try it differently. 
At this moment no-one can have a reference to the same session since this session either a new instance or the one from the pool. If its the one from the pool it was removed from it until its put back via session.close call.

However, when you look at line 512 you'll see where  it is actually being put back into the map selectively. It used to be the way you explained, but then I realized that i had a memory leak since there was no point of storing references to temporary queues that will be removed since the underlying session is not a cached session. So i've modified 'deleteDestinationIfTemporary' method to return boolean if deletion is succeeded and if it did I still attempt to remove such queue from the map, otherwise its added to the map.

THis keeps this map as big as the amount of temporary queues which is typically the amount of cachedSessions.
That was a copy'n'paste error. Removed in *pollMessageFromGroup*.
Right; see the commit comment; this code invokes the pseudo commit in the case where we don't have a transaction. _if_ we are running in a transaction, the transaction interceptor further down the stack will do the pseudo commit _after_ the database commit. So, if the db rolls back, the mail won't be deleted; if it commits, it will.

I will, however add this as a comment to the code, to make it clear because it might look odd to a casual observer.
This is not true in the case of the JMS Inbound Channel Adapter - in that case, it is passed into one of the 

    JmsTemplate.receiveSelected()

methods.

I am not sure this &lt;para/&gt; adds much value anyhow - maybe just remove it?
Compare against full name
Use `{@inheritDoc}`
That sounds like a better solution. Let's hope there won't be more groups because you can't append to arrays ;)
I'm not sure how widespread support is for RFC5861 but good geek points!
日本語。
A note to the reviewer of any admin related ticket, we shouldn't be focusing on design too much. Showing an alert is something we don't do for user interfaces but as an admin interface it really doesn't make a difference.
same as above, you do not have to save this encounter.
Nitpick (meaning feel free to ignore, it won't block merging): it's probably more explicit to say `$config_ensure = file` here.
Also in this section (and probably other where in the document) - we keep talking about method-**level** validation. I think 'level' is superfluous. We should just talk about method or constructor validation/constraints. More concise imo.
My general policy has been to keep all the monkey patches in initializers so that they're all together and I can find them to review them periodically (and especially on rails upgrades) to see if they are still needed.

Given that this is test code, and that we're patching the main class used in the file, it probably makes reasonable sense to do it this way though.

I hate the rails version check though - can we at least do that as a check on whether the `options` method is already defined?
It aligns with all the columns in the recipe.
la identación está mal
i played around with having the date selector thing disappear.. it just didnt look good though.

technically i think the only one here that matters is the click.
We don't have this constant in Android.
thnak you
The check is trivial, but it is a best practice to do all of your data prep / queries in the controller.
If you look at the version before, you'd see that this test is already commented out. I just make sure beforeEach is also commented out, b/c those code was causing tests to fail.
`Selection`  should be lower case.