labofsahil/github-event-dataset-2012 huggingface dataset:
Yeah, I was just moving around what was already there without researching better ways to do it.

I still think IsIPad() is nice to have so I guess we just change the implementation?
We use uglify which does strip out {}
combine var decs at top
This isn't read only on android. We have a setter for it.
Sounds like a bug in JSHint. Can you file an issue and just add it as a global?
You probably just did it this way because you were using `SList` before, but the `[]`s are completely unnecessary now. It doesn't really matter that they're there (since `filter` happens to have `opSlice`) , but they're likely to confuse anyone reading the tests, since it's normally unnecessary, and many forward ranges don't define `opSlice` like that (I believe that `filter` is a bit of an oddity in that regard).
Sorry for silence. Could you give an example where the existing checks are insufficient? I must be missing something, because now I can't think of anything besides a struct S with no this(S s), for which the function works.
Can you change this key to just "ignore"
Need to check that it is an ```Array```, ```forEach``` is not available on anything else and will throw an error.
`require` statements at the top seem easier to manage..
you should remove this. We don't want extra copyright for each file of the library depending of who contributed it (we keep extra copyright header only when the code is copied from an existing library)
ah right .. merging.
this is totally useless (and will output ``vendor//bundles/FOS/UserBundle`` as path during the installation)
Okay - so FYI - I had to add:

    Facter.fact(:iptables_version).stubs(:value).returns("1.4.2")

To the before :each for the type and provider for this to test properly on a Mac. So, currently the code only tests on a Linux box where there is a version of iptables. If you're going to add stubs, can you add this as well while you are at it?
Не хватает тестов на этот метод
You STOLE Fizzy Lifting Drink!
Bug right there. Also, it would be more efficient to do ```kwargs.pop('n', 50)```.
I don't see anything wrong in the Box handler. Are you sure this commit is responsible?
You could use a oneliner.
```d
rt.tlsgc.scan(t.m_tlsgcdata, (p1, p2) => scan(ScanType.tls, p1, p2));
```
No, default args are not reflected in the ABI.
No, that is a breaking change that we going to live with.
The valid commands are hard coded in the error message. Prone to error if a new command is added. Better to do something like:

private static List<String> validCommands = Arrays.asList(new String[] {COMMAND_LS, COMMAND_RM, COMMAND_GET, COMMAND_MGET})

Assert.isTrue(validCommands.contains(this.command),"command must be one of  " + StringUtils.ArrayToCommaDelimitedString(validCommands).
`datastreamexceptions` -> `datastream_exceptions`
missing one ^
this is not for a property but to map a single child node. name is the nodename of the child document to map.
The docs concerning ntrights will have to be re-evaluated after https://trac.openmicroscopy.org.uk/ome/ticket/9967
I notice you don't self dismiss the view controller? I think this makes using this API infinitely easier, and since the only way we recommend/support displaying is with [self presentViewController ... we should [self dismiss ... on completion/error/cancel etc to save the developer writing this code.
perhaps reformat this comment so it's a little cleaner ... like:

/**
 * UserLocation methods ...
 **/
Was this missed before, or did you look at it and decide not to change it?
Please remove the dash here. there is no reason to put this sentence in a list
especially as it is breaking everything
Better to automatically use the version from the manifest file (which is built from the POM metadata)
changed this.
I don't think the very first sentence needs its own <p>. That's happening automatically afasik
You should tidy up the console.logs
Should we remove the "Created by"?
(We remove them on the Android side)
>Killing the cache doesn't clear the locks, since the actions still have them linked, so it doesn't even alleviate the deadlock problem. It was just legacy from long ago...

I'm not convinced, or you haven't convinced me yet anyway.

2 jobs, both at this point, both have:

a) look up some file A, add to a action file list (lockedFiles) and to cache (dflist)
b) both go through the 'prepare' loop for action and fail to get exclusive lock (because both processes have non-exclusive read lock)
c) retry called for all, any exclusive lock's gained are released and lockedFiles cleared

[ at this point both processes still have file A in their dflist ]

d) both sleep a random amount of time, 1 wakes up first.

Repeat.

Neither can win, both have permanent read lock, because of cache holds file, and hence read-lock.
The retry cleared action 'lockedFiles' and call unlock (unlockProperties)
but that doesn't give up the read locks, it only gives up any exclusive lock that may have been gained in a successful prepare()

As long as something holds a IDistributeFile it is read-locked. (e.g. dflist)


Am I missing something?
I always hated these guys, and tried to get rid of them once before. I did a big purge of all calls to them at one stage, but they keep creeping back.
It seems to work for method parameters (childOrientationControllerChangedFlags:). Changing to NSObject< TiOrientationController> * also works. Probably a bug.
IMO disallow null. Add assertion.
Not sure it matters right now. We can check with the OpenEJB team if they are interested in reusing this impl or if they might need a special transactionprovider. As long as they can provide a Context and a JNDI name I guess it should work?
param tags should be self-closing, to avoid the warnings showing in the border in Studio.

<param name="movie" value="http://www.youtube.com/watch?v=Y-mv6_YVqto" />