labofsahil/github-event-dataset-2012 huggingface dataset:
I thought it was using lazy, on demand column wise kernel evaluations using the libsvm cache. But I might be mistaken.
or better import the log from math

```
form math import log
log_like -= .5 * (fast_logdet(self.covariance_) + n_features * log(2 * np.pi))
```
I'd rather use the name `rbf` to be consistent with `SVC` and `KernelPCA`.
Is there a reason to keep this code around? If I'm not mistaken, it would be completely wrong after the language change.
Same as above (both things from line 229).
Change this once, affects all 9 build configurations :)
$namingStrategy here.
Removed calls to removeRowBuffer()
I thought the append would do that automatically...
Does this need to be 1.38 ?
Makes sense. That exact text could be in the form of a comment just before that.
You can only call rows.flush() from the writing thread, not the reader.
Please add this to your [global gitignore](https://help.github.com/articles/ignoring-files), there's no need to litter all projects with such specific rules.
That's what line 59 is about, ``\n`` becomes ``%0A`` once encoded.
Juste une lettre en trop, en héritage de la VO ;)
is_element_visible is our own method, it is situated in page.py.
Well, the plan Toby and I came for this was to have this read methods with little/no synchronization footprint.

That is why we came up with a scala like approach, so every time we change anything on roles collection (create, update or delete operations) we just replace the local roles cache with a copy of the new roles List.  This shall make read operations faster and impervious to concurrency exceptions.
It doesn't seem to return a string anymore. Could you write a bean describing the return object?
Apparently it contains a url an an optional method
I don't think that this makes sense - why is `<article>` nested underneath `<aside>`? `<aside>` is for sidebars or marginal annotations. The `<article>` element is supposed to represent a block of content such as a comment on a post or a news article. Here it only contains the title?

Also there seems to be no need for a `<ul>` here - the content isn't logically a list. Perhaps a dictionary list would make more sense?
Good catch. That should not have been changed. Updated with commit ddda39a
0.upto(output.length-1) do |i|
0.upto(error.length-1) do |i|
Can be just:

'uri' => datastore['URI']
Sorry to be thick, but I don't understand why moving it to inside the block is a good idea?
@bagnell this file too please.
Perhaps "The distance to the near plane in meters."  Enough though meters is implied throughout the API, I usually explicitly say it in the reference doc.
@bagnell can you review this file?  Perhaps step through some of the code too.
We provide sensible defaults when sensible defaults exists.  WGS84 for ellipsoids is a great example of a sensible default.

Is zero sensible here?  if we saw calling code like `var p = ray.getPoint();`, would we think that the function returns the origin?  Or perhaps, we would incorrectly think that `time` is state with the Ray object, and it returns the point at the current time?  Perhaps an exception is the most sensible thing in this case.
yeah, it probably is. it's a remnant of when I was using the visual studio developer server and for some stupid reason i had to do this for it to work. I'll take it out.
No.  Actually, I would have known that if I read a comment I wrote a while back:
```
// Not actually pickable, but render depth-only so primitives on the backface of the globe are not picked.
```
If it were pickable we'd need a check here, but we don't have to worry about it now.  What we really care about later is mousing over terrain and getting back the position.
Yea, I do think it will make for better packing. Probably going to affect some of the tests so I'll make sure to fix them.
Now cleaning up the server and priting Pass or fail is moved to function.
Fixed in 140d80f430283552bb1f260168c35050c64807ac
I'm a bit partial to keeping the flexibility.  We incur 2 lines in MetricsService.__init__ and 2 lines in the api() method to support the flexibility.  Having a hardcoded list of decorators would still need 1 line in the MetricsService.__init__.  

Maybe we can make a trade off and supply a non-empty list of default decorators in the MetricsService.__init__ so that people usually get the right thing?
I can't seem to figure out why this line is here. I don't see it being referenced inside of the template outside of the for loop which is where this will apply.
Never use static_cast. This is in almost all cases a sign that something is wrong with your class design.
you want to say cmf-sandbox here, not standard. also below...
лучше передавать сконструированный T, так как он может не иметь дефолтного конструктора.
Да, копирование можно запретить. Раньше просто реализовывали явно конструктор в private зоне. Это просто синтаксическое украшение.

да, но только те, что есть в g++4.6.
начиная с марта начнем по-тихоньку использовать остальные фичи.
The problem is that this in a mixin template, so std.algorithm needs to be imported at the scope that it's mixed into. Right now, that means that the module mixing it in needs to import it. But if we have a local import, then they don't have to worry about it (which is a great example of how local imports can be useful).
Perfect.
I myself just wait when this -property bell finally rings and breaks what it should break :)
But it's an expression. Can you actually do something like `$(D $(LREF takeExactly)(r1, n))`? Also, if we do the vibe documentation bit that has been being discussed in the newsgroup, we'd have to go and remove all of those links later. I generally use macros like `LREF` and `XREF` when the function is mentioned by itself, but I didn't think that you could use those inside of an expression using the `D` macro.
As you find fit. I'd be thankful.
next() is >=2.6 only. we can create our own next function based on a check for next()'s existence or the python version.
See issue #298 for a discussion on this.
Using isAdmin() allows anyone in the Admin group to triggerRefreshAll(), versus the obsolete code which only allowed the Admin user.
Relié au configurateur... devrait pas être dans org.vaadin...
well I didn't think about such pattern, I will fix it.
according to .NET framework design guideline, the variable name should be stringBuilder.
A few things: 

1.` XmlSerializer` implements `ISerializer`.
2. `dataSerializer` comes from the base `RestProxy` class, and the comments declare that it is an `ISerializer`.
3. The `ServicesBuilder` has this code, for calling the ServiceBusRestProxy constructor, where it is clear that the `dataSerializer` parameter is given a new `XmlSerializer` instance:

    private function _buildServiceBus($config)
    { 
        $httpClient        = new HttpClient();
        $xmlSerializer     = new XmlSerializer();
        $serviceBusWrapper = new ServiceBusRestProxy(
            $httpClient,
            $config->getProperty(ServiceBusSettings::URI),
            $xmlSerializer
        );

I have run the unit tests and the functional tests.
You really should put a very strong warning in here, like the one you put in your commit message:

WARNING
Using critical regions is extremely error-prone. For instance,
using a lock inside a critical region will most likely result in
an application deadlocking because the stop-the-world routine will
attempt to suspend and resume the thread forever, to no avail.
That is fine to me. It can definitively be changed.
stack frame, stack trace (also please use proper casing and punctuation and such)
It cannot be that much shortened. It is necessary to handle the specific case where the memory access is done to execute the code. IE :

function() foo = null;
foo();
We can, but i've simplified the code there a little bit
POST is still the default, right?
Most of the other changes leave just one blank line between the description and the parameters. but after this point an additional blank line is added. For consistency there should be just one blank line.
oh yeah, 4 space indent instead of 2.  :-)
thanks @celibec!!
Comma after robust.
More extra trailing newlines
This method should be rename to #debug?
Can we remove this change?
it adds the BooleanTransformer. Shuld added in other whay?
yeah, makes sense. i guess in real world its unusual that this template would not get overridden.
How much of this public code needs reference doc?  Given that most people won't use these types (they'll use the converter through a web server or whatever) and that we are looking at GeoServer for conversion, I am OK with not adding extra reference doc right now.  @kring thoughts?
take care about this as it is a 2.1 method
argh, that should be | tee file

this is what I get for hand-transplanting from the bunker
ie6 supports it, it is very old method
I tried to run `composer require --dev symfony/framework-bundle:dev-master symfony/serializer:dev-master`
Yes, I should not have removed the max. I put it back in.
I think you can now remove the eof variable + simplify the code.
Same for roxie.
For thor I would be tempted to do something similar, but have a firstRow and LastRow, curRow = firstRow - which coiuld then be adapted to allow distributed generation.
don't use `+` please

btw, this is pretty wrong IMO
what's the problem with `setAllowedGrantTypes()` in the constructor? It never hydrates the attribute?
This needs to be updated with the default variable as well.
Should this be phonegap-1.8.1?
Have you checked the order of TransactionMiddleware complies with Reversion doc?
import in the middle of a file
I would suggest not to add it here, basically everyone has view permission
This doesn't seem to be used in this file.