labofsahil/github-event-dataset-2012 huggingface dataset:
@mrmattf I was able to simplify the logic in this class a lot.  It was easier to just use EventSource directly in all cases, rather than sometimes use incrementalGet.  It was also simpler to decouple switching event stream URLs from switching event names, since they don't have much to do with each other.

I'm still going through the system, but it seems like dynamicObjectCollection shouldn't be passed in here.  It implies that the collection could change from update to update, but it really can't: the event listeners on the event source close over the parameter at the time they're created.  Really, updaters have to be one-to-one with the dynamicObjectCollections that they update.  Thoughts?
Rather than pretend "private" functions on the prototype, just make `checkForTemplateErrors` an actual local private function and pass in the Material as a parameter.
These should be column-major arrays of size 4, 9, and 16, respectively (or our `Matrix` types).  Throwing an error otherwise, would be good.  The schema validates this to some extent, but is not used in Cesium.
Can be safely removed now.
Can we avoid another java event? It should be safe to close the window once the "windowCreated" is fired.
Calling add/remove won't refresh the table layout automatically. But if we call table.data = [sectionFruit, sectionVeg] to trigger a re-layout, we can see that the table has been already changed.
Trailing comma!
You can get rid of "num".
What about the compiled version of the Dart? Have you tried Dartium and dart2js?
You should search for all the uses of writeOutput and make sure you are properly escaping anything that is string interpolated.
interesting. how did you decide on `3` for the multiplier?
I didn't realize that `hasSlicing` and `save` had to have the same type until I was working on this. It made me rethink how I was going to handle slices. And actually, they _don't_ have to be the same type. They just have to be implicitly assignable to the original type. And in the case of arrays, a slice _doesn't_ have the same type (though not due to that proposal). Rather, the slice is a tail-const version of the array. However, the tail-const version is assignable to the fully const version, so it works.

The problem is that you _can't_ do that with user-defined types (at least not as far as I've been able to figure out). You can make `opSlice` and `save` return the exact same type, but then you can't operate on `const` user-defined ranges at all. Or you could make them return tail-const versions, but then the assignment fails, because the tail-const version is a completely different type (e.g. `Range!(const int)` instead of `const Range!int`). And I have been unable to figure out how to make `Range!(const int)` be implicitly assignable to `const Range!int`. I believe that the problem is that in implementing `alias this` or `opAssign`, you end up with a recursive template definition (certainly, the compiler gets OOM-ed for taking up too much memory when it tries to compile it). So, `const` and ranges continue not to get along very well. But that whole discussion really should be discussed in the newsgroup. I've been meaning to, after trying to solve the issues in relation to this, but I haven't gotten around to it yet. I'l have to remember to post on that soon.
I'm not sure if the dirty details of how the objects are constructed should appear in the documentation outside of the example given.
Noted, but the original code was not mine. Here, I merely changed the ordering.

That said, I <i>am</i> planning on doing an upkeep regarding enforce vs assert in container, but that's in another pull.
Please add few more lines. Also, be specific with the commit messages.
Just a thought: Couldn't we invoke `createInstance(InjectingConstraintValidatorFactory.class)`? That way it would be managed by CDI and we could use CDI's pre-destroy hook to release everything. The `BeanManager` would be injected by DI, and `InjectingConstraintValidatorFactory` could even be specified via `validation.xml`.

We could have:

    public class InjectingConstraintValidatorFactory implements ConstraintValidatorFactory {

        public <T extends ConstraintValidator<?, ?>> T getInstance(Class<T> key) {
            //...
        }

        @PreDestroy
        public void close() {
            //release all created validators
        }
    }

`ValidatorFactoryBean#destroy()` is our hook for closing everything, here we would do:

    InjectionTarget<InjectingConstraintValidatorFactory> injectionTarget = ...;
    injectionTarget.preDestroy( validatorFactory );
    injectionTarget.dispose( validatorFactory );

And the same for all other managed object we create. That way we wouldn't actually need to have `ConstraintValidatorFactory#releaseInstance()` and maybe not even `ValidatorFactory#close()`.

In other words, `ValidatorFactoryBean` provides a `Validator` configured with all sorts of managed colloborators and would be in charge to release them properly. If one of those collaborators creates managed objects itself (as the constraint validator factory does) it is in charge to release them when itself is closed.

That way we would rely on the lifecycle of the objects to be managed by CDI and wouldn't have to care for this within the BV provider implementation. WDYT?
... ah, actually it seems to be from the future :)
License blocks.
Nope, those *are* the updated paths.
Can some parts of this logic be consolidated into a util method so we have less duplication with the group dataload?
Can you just change this line to:

    if ( ! $this->_smtp_connect() OR ! $this->_smtp_authenticate())

... it would be a bit more readable. Otherwise it's great - we'll merge it in.
Can investigate.  Again took lead from other CLI calls (network perhaps?)
Drop the newline
Алсо, локальных переменных не так обзываются. Читай код стайл
Even if you try to enforce tabs, it _will_ end up in a mix of both tabs and spaces for indentation. Then you can allow a mix of `\r\n`/`\n` too, because `grep` will become a mess anyway.
@croby Where would you like to centralize this?
Ты уверен, что оно работает как надо?
Yey, a bit overzealous copy/paste from the YUI compressor. That also seemed to make Travis build for 5.2. Wierd.
Missing semicolon threw a jslint error here
"Receive a stack trace in the form of an address list." I'd say.
I meant 5794c22.
s/~~thru-put~~/throughput/

s/s.Most/s. Most/

allows us to use __an__ optimized value...

If you have __a__ Spring JMS consumer


Same changes JavaDoc in JOG.
Yep - good point - will change.
I think we need to spell this out more clearly...

An implemantation of {@link PlatformTransactionManager} that provides transaction-like semantics to {@link MessageSource}s sources that are not inherently transactional. It does &lt;b&gt;not&lt;b&gt; make such sources transactional; rather, together with the &lt;transaction-synchronization&gt; element, it provides the ability to synchronize operations after a flow completes, via onSucess and onFailure expressions.
пропущен `
This allows developers to further extend the logic of  Carrington Core alternate template hierarchy.
Might be nice to have a prefix/label like "Unix time conversion: ..."
Returns `nil` or a session
This issue has been fixed in Wiakowe/SonataAdminBundle@9449bfa879dd6f45f32faeee51b1b9822f7e1706

Thanks for the info.
Write your schema descriptions so that the generator produces good documentation, or change the generator to work better with what you wrote.
This may be helpful: http://msdn.microsoft.com/en-us/library/system.bitconverter.islittleendian.aspx
`apt-packages-update` should be included in the provisioning script to allow for batch updates, e.g., adding several PPAs and doing a single update. I've also updated `apt-packages-repository` to use `add-apt-repository` so keep the two functions aligned. See 5b46a36d72a869d7cae197ee1b9be920d674a0d8.
`window.onload` получит `undefined` ибо тут IEFE (тутжевызванная функция), которая ничего не возвращает. Убери вызов функции и будет все хорошо.

А еще лучше делать так:

```javascript
window.addEventListener('load', function () {
    'use strict';
    document.getElementById('arr').innerHTML = arr;
    document.getElementById('btn').addEventListener('click', function () { 
        document.getElementById('sarr').innerHTML = sBubble(arr); 
    }, false);
}, false);
```
Ну и назови arr и sarr каким-нибудь красивым и понятным всем именем. result или sort-result или еще как. sarr == http://www.footballtop.ru/players/mohamed-sarr
Wanted to say `interval will be this many seconds **less** than specified to account for latency at different layers.`?
I believe it CAN happen (and be valid) or I would not have coded it this way.

I suspect what you need is

```
if (subFiles.ordinality())
{
    IFileDescriptor *fdesc = subFiles.item(0);
    if (fdesc)
    {
   ...
```

Though even then, I'm not sure that it is correct. I think that the assert (isItem) that you are seeing and trying to avoid is indicative of an error elsewhere, and that the code here should be able to assume there is at least one element in subFiles.
Ya this was a debugging thing - gonna remove the block
плохое название
Note that "setRequestHeader" is not a method that I have touched. Are you referring to setWithCredentials? That is a property. If it is not, then again, please show me in code what you want. A link to an existing one will suffice. I modeled after the "timeout" property in this file.
I might add these in, perhaps we can rename the functions to `ft.mirror.x()` and `ft.mirror.y()`. I don't think it's obvious what `flop()` means. :)
There is a bug here, you can have 2 queues with empty key and as the definition is private the id will be never used, however the stack will be broken when the DIC is generated.  So $id = 'sonata.notification.backend.rabbitmq.' . uniqid(true); or increment a number.
I don't understand this change - taking out the test for URL  seems like a bad idea - you may e.g. end up with a citation that only has an access date and no URL (true e.g. for many journal articles).
If that is the case, then all of this isn't needed.  A merge conflict existed here and I just took the union of the two.  It will be changed.
cannot change versions here, must occur in the root pom.xml
This is a question, should be an explanation.
The line `However, the standard perks that come with 'CGridView' also apply to 'CListView'.` can be removed
La version d'origine avait raison : on écrit bien "quel que soit" et pas "quelque soit".