labofsahil/github-event-dataset-2012 huggingface dataset:
This should be CoordinatesDegrees, too.  And mention degrees in the doc.
I'm going to go ahead and merge this branch into master, so feel free to make this change there.
Hmm... these tests were just updated in commit 7b3e6ccb74 (pull request no. 63). Not sure why they're excluded again?
Ok, I'm working on it.
[do away with](http://idioms.thefreedictionary.com/do+away+with) is an idiom I've learned recently.

Good point about `super`, I forgot about it. I'll add an example of its usage.
Designer? =)
I'm not a huge fan of this shortcut. I don't see why using ::URI.to_s isn't appropriate.
I think I understand you now, and I guess it comes down to the philosophy and purpose of this category. My aim as a developer is to have every query complete successfully regardless whether I generated the query or hand-wrote it. I would personally find QueryBuilder far less useful if it threw errors when I passed it a typo, rather than returning a properly-formatted query even if it did have to make some assumptions in cleaning my data.
do we need data attributes for this? could it be simply a class?
indentation should be 4 not 2.
I know it's the exact same instance, that's not the point.

The point is that the action.reset, which clears the linked version +unlock(unlockProperties), doesn't clear the lock..
That's not what unlockProperties does.

A IDistributedFile from DFS is associated with a read-lock.
lockProperties() performs a changeMode to gain an exclusive lock (write).
unlockProperties() reverts the lock back to a read-lock.

i.e. it's still locked.

As long as their's a IDistributedFile hanging around, i.e. in dflist, the file is still locked.
And nothing else will be able to gain an exclusive lock on it, although many can have a non-exclusive lock (read lock) on it.

So you will get deadlock.

The dflist.kill() was wrong, and needs fixing, but this isn't the way afaics.
i.e. you need to avoid this deadlock.
Reverted the changes to clone.c, as they broke Phobos std.algorithm unittests.
The container only define a default set of 'known supported enrichers'.
I think I'd rather see `prepareMutation` and `performMutation` implemented as a single function that takes a callback to generate the bits in the middle, but maybe I just have callbacks on the brain right now. Thoughts?
Is there any specific reason to disable the default sprockets processor? In principle, you could mix and match default Rails logic with closure - although, not sure if I would recommend this. :)
This should be 1.9.0
We should also probably log a "not implemented message here" for these unimplemented but safe methods.
These spaces are there from older versions of the files.
Preferably this URL should not start with a forward slash. On Mobile Web, if a user puts there app at http://mysite.com/myapp/, then the background URL with the forward slash will point to http://mysite.com/images/refresh_icon.png, which is not where the image resides. Removing the first forward slash makes the URL relative.
Sure will change that.
I talked to @nukulb he thinks we should add it to the json extension, maybe rename it to something else like utils not sure, but generally keep all of that in a library that all of the extensions can use. Change the common.mk inside of the json folder to include the new class
Each of the existing calls did a rm -fr, which removes the contents recursively and ignore nonexistent files [won't error out]

I assumed this was done for a reason, so when i was converting the code to node, i made sure to maintain this behavior.

If i had to guess, i would guess that this was used to avoid errors when deleting folders that did not yet exist.
If this is the case then we can likely do a path.existsSync call before trying to remove each folder.

At any rate, it would probably be best to ask the original implementer why this is in place.
Sorry to go back on what I said so quickly, but thats not entirely true about the event framework. We set the trigger function when we build the event actionMap. We could use a separate trigger function if we wanted, I just don't know what the benefits would be. 

But perhaps instead of having convention named fields, we add a third parameter to the trigger function - blobArgs. That would at least seem less hacky to me.
Is it an idea to put this in a const variable?
You can also use `not`: `(not (teen? age))`
Can you just change that help method to `!tea double_or_nothing` and then this looks good to go, nice one!
formulation non idéale ? "ne reste plus qu'à" ?