labofsahil/github-event-dataset-2012 huggingface dataset:
The event will bubble up if and only if (event.bubbles === true && event.cancelBubble !== true && view.bubbleParent === true && view.getBubbleParent() != null). So if the user wants to cancel an event, cancelBubble has to be set to true (exactly boolean true).
Another alternative is to point this to a remote image so that we receive correct results for both platforms. http://placekitten.com/ is the recommended remote resource for testing.
can we break up these calls to `msg.getData()` and `getString(..)` for clarity?
Please add type annotations for the parameters.
Use "/**" or "///" for docstring comments. I don't mind if you drop this comment.
Why are you wrapping this in a block?
Good. Cleans up a lot of shit.
Agreed.  Updating now.
Opened https://github.com/jquery/download.jqueryui.com/issues/66
" with `gwt:run` and `jetty:start` by not requiring a restart when a change to `shared` is made"
this test corresponds with litmus 22920, so you should change it as it was before.
Just because you can use it doesn't mean that it's the correct solution.

I'd strongly argue that it's fundamentally wrong to have a trait which gives the base type of a static array give a valid type for something which is not a static array. That would be like having `isFile` return `false` because it failed to stat the file instead of throwing. It's fundamentally wrong. `std.range.ElementType` results in `void` when given something which isn't a range. It would be completely inconsistent for this trait to give a valid element type when `ElementType` does not.
Actually it's more comfy to call `xyz!T` than `xyz!T()`, so never mind that.
Kind of cool
Why declare `c2` but not do the same with `p[index+2]`? Either save both of them or don't declare a variable. It's inconsistent as it is. Both of them get used 1 or 2 times, depending on the result of the first condition, so they should be treated the same, especially when the whole point of writing this function is speed (though I don't know whether it's faster to declare the variable or not).
This is invalid. It looks like you're behind current master, where the entire templating method was changed. We now use github-style fenced code blocks, and < is the correct way to do this.
^_^ sorry guys! lmk if i can help at all @ofTheo

On Fri, Aug 31, 2012 at 10:29 PM, Theodore Watson
<notifications@github.com>wrote:

> In libs/openFrameworks/video/ofVideoPlayer.cpp:
>
> > @@ -21,6 +22,9 @@ void ofVideoPlayer::setPlayer(ofPtr<ofBaseVideoPlayer> newPlayer){
> >  //--------------------------------------------------------------------
> >  void ofVideoPlayer::setPixelFormat(ofPixelFormat pixelFormat) {
> >  	internalPixelFormat = pixelFormat;
> > +	if( player != NULL ){
> > +		player->setPixelFormat(internalPixelFormat);
> > +	}
>
> yup - I just did that. but unearthing some more potential bugs. this is
> like a gift that keeps on giving ;)
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/openframeworks/openFrameworks/pull/1478/files#r1506496>.
>
>



-- 
- James
Maybe a candidate for a library function? then we could train ourselves to notice if there is a bare .forEach.
It's not necessarily every patient ever, but the ones in the hospital right now.  Judging from what I remember of their own app, they have these patients (or at least numbers) organized in a way we can use them.  They already have a system that shows the number of patients a certain doctor has in their queue that allows screeners to assign new patients to the doctors form the screener's own set.
I'm not sure what kind of tolerance would be best, but I assumed we could just mask out anything beyond a certain point when checking, in order to make 66% match 66.66666666667%
Oh, I see, the docs were just wrong.  Nevermind my previous comment.
Handlebars outputs an empty string if the value is null.
For example, ```<span>{{myNullValue}}</span>``` will produce ```<span></span>```
So, ```<span>{{formatDate myNullDate}}</span>``` will also produce ```<span></span>```
not sure that I understand you right. I should write own Compiler Pass? If not, could you give me an example?
нет. Придется делать костыли в separate tab widget для этого.
Good point, I removed the separate tracking for "gets".
Декларации в самом внутреннем неймспейсе отбиваются одним табом все же.
I did use the MonochromeFormat in order to reuse the StepPrinter for printing Steps and their corresponding arguments.
I can't test with provider, because we run tests against 1.8.x so I made it optional here. How do we want to handle this?
Just for safety, maybe we should add POX tests for DOMSource and Document inputs too?
commit a3b3615 addresses this. I kind of like having this kind of information in place as it provides some background information to user regarding where properties are set and it also provides some hint regarding the actual implementation. Combined with links to the respective JavaDocs I believe this adds value.
"Document" doesnt exist anymore. It has been renamed to "AbstractDocument", i think. "Document" doest work anyway
опечатка, " ту же"

"или удалить из", "можно" лишнее
Nit: we tend to prefer single quotes in Python; there are lots of doubles here.
don't use ``else`` as the ``if`` throws an exception
Probably it would make sense to wrap in a describe with a beforeEach and after. I will do so.
Is there a particular reason for keeping this method public?
hatman div. slide ro barash zekr kona
ta kamelan isole beshe
```get_filtered``` is named so only because of the use of its "filters" parameter.  As another reference on what it means in this app to "filter", see the "Filter" class on the ObjectManager class.

To my knowledge, what the authorizer does is never intentionally referred to as filtering.  While it is technically correct to call it filtering, I think it is valuable to reserve that term for what happens while forming a queryset.  Any action taken by the authorizer should be called "authorization" or "censorship" as appropriate.  While I don't think the word "censorship" has been used thus far, it does seem to be the most accurate and unambiguous term here.

Like you, I was trying to come up with wording that avoided implying that the authorizer would be used in both classes.  I considered "Authorized/Unauthorized", but that could imply incorrect meaning.  "Authorized/NonAuthorized" may be usable.  However, I think the most accurate term for what the authorizer does is "censorship", so lets go with that.  I think it will be clear what it means.
Same again, this shouldn't need qualification.
This is stub project that will be removed shortly - it uses the same package names as upstream checkstyle and ugly copy&pasted pom.xml with much rubbish. The reason for its existence is to ease creating patches for upstream checkstyle, but from my experience it does not serve good for this purpose.
Don't need the `;`
Agreed -- some packages may come via git submodules or pyrus still.
autoloads in development but not test. What am I missing?
This should probably say: the base trait <tt>OverridesEquals</tt>, correct?
@geihsler could I ask the reason why do you decide to move it into shared?
(possibly important) This look's bad.  

* sign maing be the string literal "+" or  numeric 1  or numeric -1
Could the TC not be simplified so that we stop instantly on the target line so that no more user interaction is required except typing 'foo'?
Енто в случае, ежели снят чекбокс "Заклинания", и не открывались настройки.
detectImgOgg, например
Is this just a safeguard to make sure we remove the CONTEXT_ALL and all other contexts? Is there a reason why we don't just remove from the "CONTEXT_ALL". In theory we will never have an item subscribed to more then one "context" since the actionID defined above is unique to only a single context OR all.
These don't need to be scoped to the entire file. In fact you could put everything inline with GLOBAL.window.qnx =
why passing an empty argument (i.e. an empty string) ? Remove the tag entirely as there is no constructor argument anymore.
this will go away as a sub-project
Please keep the warning
I only put it in to make it look nicer.  And since it is a different thought from the previous sentence. Can you removed if you want.