labofsahil/github-event-dataset-2012 huggingface dataset:
This is most likely a bug in the Nexus 4; I don't think this conforms with the WebGL spec.

Shouldn't we remove the uniforms in the array from `allUniforms`?
Actually this probably isn't land.  What is it?
it against our styling guide
Update: I learned that node normalizes path's in require and it's FS commands, so it's only necessary when calling command line methods. Ignore this and similar comments.
1)  providerName can only be null if the Android OS calls either onStatusChanged, onProviderEnabled or onProviderDisabled with a null provider argument which I think is impossible.  If provider cannot be null, I would argue for removing this change entirely in order to avoid the cost of checking and keep things as simple as possible. 

2)  In the case we do want to check for the providerName being null, I would argue that we just log the error and break from the method rather than continuing.  Firing a event to javascript with a status change when we cannot report what the provider is has little value IMO and could likely lead to future bugs.  I think no data in this case would be better than bad data.
Since when has this been the case? Can we discuss this to clarify, before I make this change?
Thanks
This section specifically describes the IOS behavior. I am not sure Android follows the same behavior. 
On IOS when the layout parameter is specified as `horizontal` children are placed starting from the top left corner irrespective of whether a top parameter is specified. Android on the other hand will start placing them at the center if no top is specified. Also am not sure if Android actually wraps the views as the documentation states. Will verify and update the PR with findings.
Why not fDotUp?
...*never* do it this way in real life...
Meanwhile add a TODO here.
@fernandezpablo85  I needed to modify this to get the an access token from our API. The [OAuth2 spec](http://tools.ietf.org/html/rfc6749#page-30) says to that grant_type=authorization_code is a required parameter.
You're not actually checking anything here...

Suggestion:

```python
exts_list = ['ext1', 'ext2']
exts_filter = "if [ %(name)s == ext2 ]; then exit 0; else exit 1; fi"
```

(`%(name)s` will get replaced with the actual name of the extension)

and then check whether only `ext1` is still in the list of extensions
systemType can return null - is this method ok with that or is there a  missing assert ?
A line! Neato dorito!
It times out. Wasn't sure how to make it fail outright.
this whole case (instanceof PropertyInterface) seems to be a premature code implementation. from ObjectManager::getPropertyByPath i think we never even store properties in the node array. are you sure this line was ever called? getValue on a deleted item should lead to an exception about trying to access a deleted item.

oh, and isDeleted and isModified are mutually exclusive states of the node, so it will never happen. basically the call to getValue / isDeleted can be completely removed.
Add documentation (and make private since it's not publicly documented).
Formatting function pointer types should be supported.
@andralex I'm well aware of the check that was there before, but upon seeing that core.bitop _always_ defines `bsr`, I saw no point in leaving the check in. It's just dead code if `bsr` is always defined.

@dawgfoto Are you aware of any reason why Phobos couldn't assume that `core.bitop.bsr` was defined when `core.bitop` is not in a `version` block and is therefore always defined?
Indeed. I don't think there are any downsides here
Let's include it. We're soooo close :)
feedback, please.

Cursor does not advancing to the position correctly. The debug lines print the same foundRecord.encryptedUsername for all cursor positions, until the for loop terminates.

Results in not finding the existing record.
Even here; you want to grab all of the records for both cursors with a shared upper bound.
Unnecessary declaration of variable
it is updated if the ``addXXX`` and ``removeXXX`` setters of your class take care to update the owning side (which should be done otherwise you have issues everywhere you use the object).

And regarding the deletion, ``$object->removeTag($tag)`` and ``$em->remove($tag)`` are **not** equivalent. The first one removes the *relation* to the tag whereas the second one removes the tag itself. This second case is not what you want, especially when the relation is a ManyToMany as it means that other objects were using the Tag too.
That's a good question that I don't know the answer, this pattern is commonly used by gwt widgets. You would maybe remove the If if you have more than one ctor and I think that in that case, it would prune what isn't used.
I'm a little apprehensive about this line. I think this will hinder future development of this module, especially when we want to display ```n``` patients left for ```n \ne 7```
please remove the extra empty line
I think you should have an interface for the QueryParamReader, allowing people to have another implementation reading from another source than annotations
breaks on "foo.com_branding.py" or './path/to/branding.py', etc but that probably will
break the following __import__ statement anyway.
So we should not be able to import the torrents or am I missing something in the standard?
@clemherreman Others have argued, and I now agree, that namespace, use, and class should all have a line of separation.
If you get rid of the `self` vars, this will need to take a suite map as an argument.
.in(Scopes.SINGLETON);
that doesn't even seem to use 1099 ?
Not sure what type of polishing you are implying for Tuple, may be you can clarify.
In any event if this code already supports List why limit back to Map only? The only way to find out if there is anything else needed is to get it out there.
Just it final with f6cff6b
MSDN documentation says it supports select and filter, with no specificity about whether from is supported or not. Even if it doesn't support right now, leaving it in sdk may still be valuable for future scenarios. 

http://msdn.microsoft.com/en-us/library/windowsazure/dd179421.aspx
Looks good.  That should quite logging down.
May I suggest to split up thise line, around 'which call'? Otherwise it will be one sentence with two fairly large enumerations.
Also, "Java Web Start" is the appropriate spelling.
@apex13 Why exactly did we need that?
imo we should try to avoid it when possible.
I would like to see the row that we're currently viewing in bold
Hmm, maybe all these tests could have their enabled property set by "not test_config.values['openvz_disabled'] given the filename. But my point was since its a white box test you could guard it with that var too.
From the code: 

        list($phpcr, $tests, $chapter, $case) = explode('\\', $fqn);
        $case = "$chapter\\$case";

Should still work ;)
I will not repeat this elsewhere. But it is the same. ;-)
I think it's more of a state.  Both sailthru and stormpost have variables that indicate whether or not someone has globally opted out.
I'd suggest shortening that to just "There are some unread news for you! Please make sure to read them, as they may contain important updates."
We could (but that's outside the scope of this PR) make the link to the vector space model explicit by showing a toy search engine with cosine similarity in a doctest example.
you should add a note saying it is not needed when using composer
Alex, the rules do not preclude the use of a resful API for auth or for any other goal.
Fixed in 3c4af61
I think I'd rather have `unless object.redacted?` around the next block rather than an early return, which is generally considered bad form.
May be it's due to the empty "raise" line? I mean may be using "raise e" instead of only using "raise" will sovle the problem?
This seems to be a duplicate of line 81.  If there is no good reason for this, please remove one of these lines.
We should also do this check earlier so we don't end up generating a bar.xml that we won't end up using (if the user provided one).
That's a possibility, but it follows the same structure as the context menu, and when moved into web platform will need to be in the structure dialog/index.js contextmenu/index.js since we also have other fies. If you can convince me I'll change it, otherwise I might leave it.
Oops sorry looks like a dummy comment! Thanks!
:) will do.
EquipletID is defined in the messages. Could add the ID to the name but thats important when we have more then 5 equiplets.
I usually default on using comprehension when the only thing I do is `map`, but you're free to do what you want :)