labofsahil/github-event-dataset-2012 huggingface dataset:
Okay. I fixed the null dereference issue and added documentation to `opAssign` to clarify its behavior.

As for assigning a slice to the original, `hasSlicing` doesn't check for that, but it seems quite common that code assumes that a slice is assignable to the original. The same goes with `save`, though it actually tests the assignment. So, at present, it wouldn't work at all to use std.range or std.algorithm with a type that returned something different for a slice. And given the fact that it's quite common to assign a slice to the original, and that behavior is very much needed in general, I don't see how we could make it work otherwise. `hasSlicing` should probably be updated to reflect that requirement however.
i will assume this was a simple typo ...
... that is, unless they're already documented on the superclass
didn't the serviceacl connector also need an update of the parent?
@chillu, the main reason for these API changes is to make SiteTree->getTreeTitle() extensible and reusable.

Recalling that we talk about how the original code make that devs have to replace almost every single line of the code for entire function (ie. parent::getTreeTitle() was always unnecessary and useless) if they like to extend the method, we have to reduce the method's granularity by splitting it out.

However, the method after all needs to check the node current status to pick up one right class=>title mapping from a bunch of mappings, so I didn't see anywhere we could avoid from using the conditional checking. And because the return value - the html raw code of the SiteTree->getTreeTitle() uses the both the mapping key and value for the css class and the lozenge label, why don't we make both the key and the value extensible in different method?

I guess, what I am trying to say is we could not remove the conditional statements at all, but we could maintain them in a very simple method and override least methods if necessary. Thoughts?
Maybe abstract this away to

```Then I should see 2 patients to assign```?
@schmittjoh `void` is useless ;-)
Renaming `setup` -> `configure_with` also breaks existing client's assumptions.
Ok, Good Idea, I will change it.
ticks get lost here too, when rendering markdown
I think it would make more sense to use caller's thread here, as the only thing we do is pass the pass the the load from the same thread to the same thread, using e..g SameThreadExecutorService.
As discussed earlier this needs to be in `config/` relative to the current working dir of the app that is using `travis-core`
yeah, this strikes me as something that can go away as long as prepareSite is still called during testmode (although, with the changes external to this diff, i don't know what exactly the khan_exercise chrome looks like, but i would assume that there are ample opportunities for)
The addObserverForName:object:queue:usingBlock: will return the observer object. We must use it to remove it from observing later.
I did understand that. I was just trying to *also* look at it from the different angle.
It seems there are two white space between "applications in" and the following "Java". I think one is sufficient.
Because it is neat.
Im a little concerned about this version of stdlib. Can you use something older?
Nice, I like! and I will change
Yeah for sure.  Figured it would be useful
the variable is assigned in all branches of the if statement that i suggested
Are the locations and what needs to change very obvious?  If so great, if not you might want to explain a little more.
as we just plugged wro4j into maven lifecycle, the default is to generate the minified assets too.
I believe this is needed, actually. resolveClassName only throws IOException but we need to catch the exceptions thrown by newInstance.
I vote wait until we actually duplicate, rule of three and all that.
s/gets regenerate/get regenerated/
ah yea, overlooked this. also, update it to `0.5.5`
Still waiting to see if we get a django-filter release before deciding on exactly how we manage this. :)
Please add a comment why the commented-out code is left here and not removed completely (or remove it completely :-).
Strong reference cycle between MSClient and MSLogin
This should be resolved now
This should ideally be a non-routing email address like admin@example.com
this is the only change to LingPipeSpotter: File->InputStream
times is not times anymore, its numberOfContacts
I removed these initializers. The values such as 'brushColor' did not exist so I am not sure why it was not asserting.
add warn / error "use launch with options"
That's not true, unfortunately. Gmail uses "Mail:DEFAULT" as the CollectionId for the inbox.
Cool. I considered adding the instance variable to optimize (so it is only loaded once).  I will use this pattern.
Ok fine. I need this pull merged though before I can get that one switched. Merge #650, then once this is merged, Ill open another pull
Please use single quotes instead of double quote. There are many places where you use double instead of single
Remove this line, or you'll get a checkstyle complaint.

(You could also define it, but it's pretty obvious IMO…)
looks more idiomatic, yes. Needs to update the _list partials.
Should end with `.`, a couple more.
Plase, give those 3 lines inline comments on what this preg_replace does.
btw - just realised - this isn't even my code it's an extra library maybe i should add it only as dll? - i just thought it would be easier if it could be just one .exe