labofsahil/github-event-dataset-2012 huggingface dataset:
The one downside to that that I can think of is that if `commonPrefix` is used by another function which takes a predicate, then it'll take a performance hit, because it'll have to pass in the predicate, even if it's the default predicate. Given what `commonPrefix` does, I'm not sure that that scenario is all that likely, but it's definitely a case where efficiency would be harmed. It _would_ make `commonPrefix` a bit less ugly internally, since it wouldn't have to check the predicate, but all that saves you from is the last part of the `static if` - `is(typeof(pred == "a == b")) && pred == "a == b"` - so the ugliness averted is minimal. So, I'm not completely against dividing the function, but it seems to me that we'd be incurring a potential performance hit just to save ourselves one line of ugliness in a `static if`. Given that this is the standard library, I would have thought that we'd consider that extra efficiency to be more important.
The problem is that a lot of the times what we do is a bit complex for lint. It may be useful to just suppress a few overall. @SimonVT is right about the `invalidateOptionsMenu` call, we override it so that it will technically work for all API levels. I find lint highly useful for applications but it's hard to shove into a library where we rely on certain behavior.
Mac drops these files everywhere. We should keep.
nit: 80 col
Seems kinda redundant to compute this unnecessarily. Why not have `getStagesToSyncFromBundle` return `null` and do this conditionally?

Or, more cleanly, move `getStagesToSync*` into `Stage`, so it knows about the named stages, and you can avoid some of the generality and complexity.
hmm I'm not sure. 
tex_t and tex_u are only set in ofTexture::allocate or ofTexture::loadData, neither of which are being called for depthBufferTex . 

where do you see these getting set by ofTexture?
@dbu I'll have a crack at it, soon
Haha... not joking.
Replaced method comment with:

  /**
   * Handles the refresh of the document content when an annotations is deleted from the comments tab.
   * It applies only to the case when annotations are merged with (and stored as) comments. Custom annotations will not use this.
   */

Coupled with the comment on the listener registration (where it is used) and with the fact that this should be the new default (merged annotations), it should be ok now.
Updated Bootstrap and checked for regressions.

Then, updated the badge to use the fixed badge-warning class from updated Bootstrap.
What is a "non-enrolled class"? Is this a lottery preference?
@schmittjoh JMSBot should handle the case of partial subpaths (like PHP-CS-Fixer does) to avoid complaining for every class in all bundles (you could use the composer.json ``target-dir`` if you want to be strict).
magic names... the only real requirement is that each name is unique
Не нужно переопределять op= и copy ctor.
Кстати, copy ctor'ы так не пишут.
We should make this calculation on a different line to make debugging it easier and improve readability
Ok, one major thing here - this cov/mean thing is being called each time compute is called.. Please move matrices part into the init
as mentioned in a previous comment, I would really prefer to see the arg order follow the typical "key" before "value" practice...

this seems more readable IMO:

    *receiveCorrelatedReplyMessage(MessageConsumer messageConsumer, String correlationKey, String messageCorrelationIdToMatch)*
Should factor out this line into its own method and override getMessageCount() to use that method.

Otherwise, we go through the prefix stripping unnecessarily for getMessageCount().
Why are we removing this? Don't we need a local install any more?

Gunnar, 

Given the nature of this change, I think you need to make a much more comprehensive commit commit - at least to provide a pointer as to why each of these changes is being made. I don't have the benefit of the knowledge you gained while making this change so you need to give me some help understanding it.

Thanks.
This comment means nothing ;)
Hopefully Gary won't find anything else and remove it as he is merging or else I'll remove it during polishing
True, and all I am saying give me the Region instance. That is an advanced requirement and i believe it is a reasonable request from us. We can talk more about region name in M2/3 etc, but this is what i believe is appropriate for M1. In other words we expose the required functionality but may be not in the most convenient way and that would leave some room to wiggle
Same comment as previous
Yeah, I know, but it was only one line.
It's available, you can read more about it there : http://about.travis-ci.org/docs/user/languages/php/ "http://about.travis-ci.org/docs/user/languages/php/"
This is a comment on an individual line: Nice and informative comment.
Does this need a double slash? Current print out says ``c:omero_dist``
On my local Django installation i get the following

````
>>> from django import VERSION as django_version
>>> django_version
(1, 4, 0, 'final', 0)
````

Therefore this wouldn't evaluate to True for me. Maybe something like

````
django_version[:2] > (1, 3)
````
would cover all cases?
Should `attname` be `name` instead here?:

    attrs[field.name] = getattr(instance, field.name)
Thank you my friend. Here is your reward...
This documentation was generated automatically? It is in reST?
okay. so It will be `...\Client\Client` class?
Don't use a CreateAPIView - (very slightly different behavior to what I'd expect)
Something like this...

    class AuthTokenView(APIView):
        throttle_classes = ()
        permission_classes = () 
        parser_classes = (parsers.FormParser, parsers.MultipartParser, parsers.JSONParser)
        renderer_classes = (renderers.JSONRenderer, )        

        def post(self, request):
            serializer = AuthTokenSerializer(data=request.DATA)
            if serializer.is_valid():
                return Response({'token': token.key})
            return Response(serializer.errors, status=status.HTTP_400_BAD_REQUEST)

Note that we need to explicitly specify no throttles, no permissions, and which renderers/parser,
so that the developer's REST_FRAMEWORK default settings won't be used.
由于 => 犹豫
A constructor should be passed instead of a method.
Since these values get re-used, I've found it convenient in other tests to do something like this:

```
self.RIGHT_NOW = datetime.now()
self.TOMORROW = self.RIGHT_NOW + timedelta(days=1)
```

And then you can use those values in the code.  It's especially nice when you need to convert them to an ISO8601 string, but I think it's worth considering here as well.  There are already at least four places where you could use ```self.TOMORROW``` instead of the timedelta business.
why one notification per notification manager? same issue as before :(
Probably should also make end_request a link:

:meth:`end_request`
can't this be written like this
```
string.split("\,|\|")
```
and just simply avoid all this ugly logic?
Added ticket https://jira.appcelerator.org/browse/TIMOB-7823
My preference is to always have even simple logic blocks contained with curly braces.
Не знаю. Но без этого исправления для меня пользоваться менюшками на ычане практически невозможно. Быть может дело в мышке, ибо я её всегда настраиваю помедленней.
just return the new id