labofsahil/github-event-dataset-2012 huggingface dataset:
> further, it's currently unclear on what basis algorithms are chosen for inclusion. even by crude metrics such as citations, "diffusion maps" has many more citations compared to ltsa.

Because it has been documented (including complexity analysis) and the example scripts used to generate the documentation plot show that it's no slower that modified / hessian LLE and yields same level of reconstruction error on the digits dataset with the complexity / scalability:

http://scikit-learn.org/stable/modules/manifold.html

With this level of documentation the user can have a clue about it's potential practicality and why LTSA can potentially be a nice alternative to (H)LLE for his/her problem.

Also the fact that the new code is short and that Jakes is a regular maintainer-type of contributor who helps reviewing other people stuff, refactor infrastructure issues such as the arpack bindings in scipy and fix inconsistencies in code and documentation also makes me confident that this specific contrib will not bitrot.

To be more specific with respect to the current PR, I am not against the inclusion of diffusion map embedding at all (I am not knowledgeable enough on those matters to know whether or not ). Number of citations is a very important clue about a method potential usefulness but it should not  alone be enough cred for inclusion in the project: documentation integration and usage examples and comparison with other methods in examples is more important (at least to me). Number of citations alone won't help maintainers not very familiar with this code deal with users questions or potential bug reports more than one year from now.
!!!! These changes are ... not correct.
This method is used, when trying to insert a new downloaded tile from internet to sqlite db, if it is not there. But this code now checks for parent tile,
not the tile to be inserted, which causes error when inserting a tile that is already in db and OsmAnd crashes.
This must be corrected before merge.
Please, rename
Shouldn´t the following 4 test be functional test instead of unit test as they ensure the correct workflow from application to screen factory?
As a unit test it would be enough to test if e.g. '@screenFactory.getBuildScreen' was called.
```
S36.init[] = { void** vtbl, void* monitor, int a; }
A36.init[] = { void** vtbl, void* monitor, int a, int b, int c, int d; }
```
Again, the rules of D_LP64 apply to the start of the .init[] array (will either be 8 or 16 in size).  The rest assumes that int's (32bit integers, to be specific) are *always* aligned to 4 bytes, and as there's 5 of them, their accumulative size is 20.  The result - .length will either be (8+20) or (16+20).
> Why is int*(&x) illegal? Is this a limitation, or intended?

`int*(&x)` is rejected in parse phase. Certainly, it would be able to improve (of cause `int*` is always a type!). However `T*(&x)` would be kept disallowed so `T` is an identifier and it is parsed to a MulExp(`T` `*` `(&x)`). To keep consistency with the latter, the former would not be allowed, then it is intended. 

> As for (int*)(&x): Wouldn't it be more consistent to make it legal, but to not cast?

It is more subtle case. In current, C-style cast is kept for the convenience of code porting from C. So, it is parsed as such, and rejected.
In this case no copy called. Returns the newly create buffer.
Update the data property.
I'm not sure this is the correct behaviour.  if fontstyle is default then set to default, but if it's anything else then it may be better to just not change it.
for all the previously implemented controllers (e.g. slider, button , label) it returns TiUIBase, so we don't need to cast
just add the complexity field before hints and I will merge it.
And finally, the copy username-to-email handler.
The module only does 2D pseudo planar search on the earth surface, for now.
most of the time, there won't be that many. I think a dynamic array with lower bound of about 10 concurrent events is probably a better choice.
Could have invalid tracing if packageSetSpec was NULL.  (Could id attribute be NULL)
Anonymous files can't be attached, but they shouldn't fail either. The only guarantees we need here is that the file cannot be already attached, and have to be after connecting (see below).
I don't think newSize() is needed any more.
I'm fine either way
Would be better to not change the positional arguments to ``__init__`` and simply ``pop`` it from ``kwargs``.
It would be good to show the separate view scripts here and then the result.
Not sure if we have translation for this one, you should look. :)
Thanks for the reply. Can you please replicate the empty-password login?
The behavior I replicated in Bug #10 was the lack of HTTP Redirect in case of nonexistent user. The login was still failing as expected and to cookie was set.
Good catch.  I'll do that.
@shacker Can we check for spaces here and everywhere else in the commit?
why not just have it be forge-distribution-*/ ?
It is defined at the module level, so I added it as a parameter to the function and the caller is responsible to handle the datastore.
Heh, cute :)
This sentence does not parse.
This is basically just a copy and pasted version of the designated initializer. Why not just call that & set the session delegate.
Or even better: set the session delegate via a property only, without adding a new init method
I suggest we leave this in place, but wrap it in a config check. Well... Actually, what does it do here? I suggest we move this logic into `log_client` and strip messages right over there if necessary.
No `if`s without `{}`.
Weird alignment.
In `imagery_layers`, the project method clamps the coordinates to the valid range for the projection, so you can just use PI/2 rather than this hard-coded latitude.  There's also a property on WebMercatorProjection that gives you the maximum latitude in that projection, in case you do want to use that specifically, regardless of the projection.
Is there a technical reason as to why I should make this change made?  I'll make it in either case just because it's not something worth arguing over, but I personally think the nested version is easier to read and more compact than the un-nested version and I was curious if this is just style on your part. (I also tend to favor single-return functions, which leads to code like this).  While consistency is important, style can get very bike shed-y very quickly.
I would just assign `Material.DefaultImageId` to this and change the Sandcastle example to assign `Assets/Imagery/waterNormals.jpg` to this.
Good point actually, I take back what I said previously.
@mstepanov ignore my comment, I get it now after talking to Opie
Whoops, fixed now.
The 3.x notation is incompatible with Librarian :(

On Nov 15, 2012, at 1:54 PM, Chris Price <notifications@github.com> wrote:

> In Modulefile:
> 
> > @@ -7,5 +7,5 @@ summary 'PostgreSQL defined resource types'
> >  license 'Apache'
> >  project_page 'https://github.com/puppetlabs/puppet-postgresql/issues'
> >  
> > -dependency 'puppetlabs/stdlib', '3.x'
> > +dependency 'puppetlabs/stdlib', '>= 2.0.0'
> @etiennep : how did we end up back at this? (Again, I'm ok with using the > instead of ".x" if we need to, but would like to make sure that I understand what got us into that situation.)
> 
> —
> Reply to this email directly or view it on GitHub.
> 
>
Ну етож синглетон. А что делать?

Да, с загрузкой я погорячился, можно было оставить как было.
в смысле? если на странице уже есть jquery, и он не очень стар, мы должны использовать его а не грузить жкуери из интернета ж?
Good idea. I just copied the ones above (Signed/Unsigned), and they are pretty weak.
`nothrow`(?)
I need to handle these Exceptions. E.g. for the File support, there is a property accessed which isn't existing, but the setter exists. In this setter, the given value will be converted and the corresponding file property is set. Or if a security manager is set which doesn't allow to change private fields, than the setting of values through the field wouldn't work.
hmmm ... again something I need to think about how to make that properly. I mean the interesting point here is: what makes sense to be put in this EOModel class. And also it will be a little bit harder in the enhancer to do bookkeeping which models are EOModels so that they can be casted to that or if they were already enhanced like shown by you. Or maybe I just think the wrong way and you don't mean it at all like I imagine : D
this lets me inject behavior deep into the stack -- I can put a param "foo_force_drop", ensure intervening proxies and middlewares preserve that parameter, and only when it hits the 'foo_' layer does it go from param into the environment (and thus trigger the middleware in question).
as mentioned below, maybe these should default to false
ok, I'll make them false.  Will also do this in the controller in openstack.
Iesi does not support passing in a comparer so I had to roll my own subclass.
"6 days"
http://www.lukeredpath.co.uk/blog/demeters-revenge.html
Done in 8595910732c20fbf11ff01c866d1b31185e1edbe
hmmm...maybe should be loggers
@saem In Symfony2, @fabpot prefers keeping the short name everywhere and adding the needed use statement for this. I don't know what @beberlei prefers for this bundle though. But in any case, it should be resolvable (which was indeed not the case here previously)
Actually, disregard the previous comment.
Remove the metaurl parsing entirely. We don't want URIs to torrents and such showing up as mirrors ;)
We should capture using it for method arguments too.
Fixed long line, let's not care too much about line lengths in a plain text file though...
Yes, changing this parameter breaks backward compatibility, but at least it doesn't cause a misconfiguration.  For example, if I had reclaimed "port" for the HTTP port parameter then existing configs could have potentially set the HTTP port to 8081 which is most likely not the desired effect.  Breaking seems like a better option.  Let me know if you have any concerns about this.
Shouldn't _.DS_Store_ be excluded in all directories in the module? Can you change it to `.DS_Store` instead of `images/.DS_Store`?
Can we split this up into 2 lines?
I've hardcoded the minimum counts to 1 for amount of facet fields within a facet. Should have discussed at the committers meeting, but forgot.
OK, i think Suranga also commented on the ticket about this, so which is the one encounter to add here since the patient has many or is it always a new one?
technically shouldn't this just say "Removing empty group:" ? (the remove(..) method will be called not expireGroup(..))
Used to be `timeout.Milliseconds` -- NOT `timeout.TotalMilliseconds`. The input `timeout` was 3 seconds exactly, so the value of `Milliseconds` was always 0. I'm now passing in the entire timeout TimeSpan.
booleans should always be lowercased. And you should use ``null``, not ``false`` for a non-existent object.
docblock is missing
This implementation is a bit weird as I would expect an empty array to return an empty collection not ``null``
This also was not supposed to be committed...
You can also attribute this beautiful class to you ^^
Yes you are totally right for the implicit type conversion. I will change this.
But unfortunately the range is 0~1023, so it is really 1023 and not 1024.
Thats fine, i see it now.
чому прибрали?
Also  wonder if we could further speed things up with sklearn's `fast_svd` instead.
Used by https://github.com/felixge/node-formidable which is used for processing uploaded photos
jamesladd - this appears to be a question for you.
"buddyid" string extra should be a constant field in the activity, in this case ChatBox.
This is to avoid errors like typos, etc and also to guard against future changes in the key
It's similar to that one: http://www.velocityreviews.com/forums/t373426-fatal-error-after-re-installing-python-2-3-4-a.html
should probably read "if the user cancells" or "presses cancel on the contact picker"
Right now the locale is being hardcoded to en_US. Perhaps we should add the ability to choose a language in the skeleton to illustrate how to change the locale?
Perhaps change the comment to something like `// returns the String "U go now.***********"`?
The ID we are referring to denotes which webview instance the event is intended for.  I think this is where the confusion lies.
There is an ID for the webview, and the event type denoting which event is being fired.
I chose to loop here instead of using a mutex because there's only an extremely small chance that the event variables will not be initialized by this point.  The only situation where we would enter this loop would be if removeEventListener is called immediately after addEventListener and if the thread scheduler does not choose the secondary thread for some time.  Since the likelihood of both those happening seemed low, I thought the resources required by a mutex didn't seem worth it.

A mutex would be cleaner in the code and my assumptions may be incorrect, so if it's preferred, I can change the loop to a mutex easily.
why is this value "this." ?
Its not an instance in any way, for a given version it will always be the same, it should be static value.
Is this the way we are doing JNEXT now? If this is the case we should update all the previous JNEXT based extensions to follow the same format.
It appears that these were renamed?  Where reasonable, following a [TestDox] naming convention like these are preferred.

[TestDox]: http://agiledox.sourceforge.net/
It's still free. Just like some Canadian banks where they want to start you off with a non-zero balance.
As there is no WebTestCase in example code you should copy code from default app here and extend CWebTestCase so it is more clear what's going on.