labofsahil/github-event-dataset-2012 huggingface dataset:
Passing through the column here doesn't make it very readable from the test perspective :( 

I think we should treat it like a region rather than a list. Then refer to the sort type explicitly in the method eg `sort_by_plugin_filename` 

Theoretically it would cause duplication but there is only one test that uses it so there's only one function to write :)
Maybe also state it's not necessary
can you explain a bit more what is meant by "absolute tile bounds calculation is possible" ?
@bp323 sure, should be fixed
if `border_size` is a number can we just do `{if border_size}` and drop the `> 0`?
Why did you delete this space?
Why not copy directly to `.env`?
experiment.save is being called in an iteration here as well; it's just in the same block as the file loading. I wouldn't remove it just to be safe. We can ask the Vanity authors when we do the pull req
Please review __rec_page_modified() and __rec_page_deleted(), they are the guts of the reconciliation changes.
Should this try to drop anything in the old_chunks list?
What is the case where we have a btree handle with special flags or discard set, but we don't have the schema lock?
Query layout
aswell as type should be castet to int
Are you sure ``0`` has the correct type as "integer" is not a sub-type of "string"?
Are you sure ``$type`` has the correct type as ``object<Symfony\Component...TypeWithParentInstance>`` is not a sub-type of ``string``?
right now 'make simpleinstall' should be run for other browsers and 'LD_PRELOAD' set by the user
Gibts in Java keine statischen Klassen?
Did you see any change in behavior when changing from set_variable_values2() to set_variable_values()?
Good catch.  This variable is redundant - I removed it in the next commit.  Thanks!
This should be `Model#defaults`, right?
Relevant: http://twitter.com/ajpiano/statuses/148842137751003136
Sorry, this gem should be installed along with `ruby-debug-base19`, I will drop this commit and rebase PR.

```
$ gem install ./ruby-debug-base19-0.11.26.gem -- --with-ruby-include=/Users/user/.rvm/rubies/ruby-1.9.3-p125/include/ruby-1.9.1/ruby-1.9.3-p125/
Fetching: columnize-0.3.6.gem (100%)
Building native extensions.  This could take a while...
Successfully installed columnize-0.3.6
Successfully installed ruby-debug-base19-0.11.26
2 gems installed
```
JEventDispatcher
incomplete return tag
Como é que se trata dos IDs de notícias internas neste modelo?
Ou seja, quando é importada uma notícia do SI-PUB ela já tem um ID (que assumo que seja mantido pois não está a ser guardado de outra forma), mas quando se introduz uma notícia pelo gestor do SI-M, qual vai ser o ID dado? Não é possível que haja colisão de IDs?
Its kinda a standard to have one new line at the end of your file but this doesnt really matter if you're working alone
Hmmm

While this works,  I don't think this belongs in the Knapsack recipe. 
More likely one of the configuration files.

Maybe creating a class to determine download `url`s based off whether we need the `x64` or `x86` version. Probably more work, but possibly less maintenance.

... 

I'm over-thinking things again, gonna take a look at #70. At least I have my thoughts down.
Online = on-line = na-vezi. Closer to "povezani" then "prijavljeni" (which is "logged in", which is not that).
No. This should should be OS independent. You do not need or even do not want to use OS-dependent or OS-language dependent things.
`disconnectUser` -> `userDisconnected`.
Here you should fix the if, if e-mail is defined and if it was not confirmed, then display the link.
´´´Exception Type:	TypeError
Exception Value:	
can't compare offset-naive and offset-aware datetimes
Exception Location:	c:\Users\Crystal\git\abbb\piplmesh\panels\horoscope\panel.py in get_context, line 56´´´

well i dropped all databases and i still have this problem (also tried manually clean data/db folder
In another ticket or this one?
Oops that certainly wasn't on purpose... someone fix this please...
Does not really work. So there is still a race condition. What you want to do here is called upsert (insert or update) and MongoEngine supports this natively. This would do the trick:

```
models.Horoscope.objects(language=language, sign=sign).update(set__forecast=horoscope['forecast'], set__date=horoscope['date'], upsert=True)
```

And of course this line does not need its own function.
Oh, here I see that there are single `'` around translatable strings. It should be `"`.
rename this ffs.
pls for 4.3.4 branch sql in 2012_12_02_00_world_spell_group_misc_434.sql rename
I prefer longer variables names that are more descriptive and easier to find using grep.
Dafür gibts im Res eine Methode....
I just integrate scale_out*ci.x+0.5 upstream to reduce the number of parameters passed to kernels (line 720 in process_cl)
join нужно делать всегда. Если is_alive() == False он отработает мгновенно, вот и всё.
`related_name` seems ambiguous to me: is it the forced name overriding the default related field name (here, "group")? Nope.
So what about `reverse_related_name` ? Or maybe `reverse_name` ?
It seems odd to have one parameter ($label) be base-64 encoded when the other one is not ($configuration). 

It also makes me wonder if we should auto-encode the $label.

On the other hand, perhaps we should not auto-encode anything, to let the user have more control over the API. Or we should have two versions of the API, one that auto-encodes, the other that takes base-64 strings.
I don't necessarily agree that having randomly changing id in here helps user with anything but if you think so.

Having 'Runtime' in one case and not the other is a little bit inconsistent also.
I assume this should be including <vector>, since that's the type that's actually used below?
I think you meant `bbf-error` here
nit: I would add a blank line after the return statement.
``vect`` is not really informative as part of a name, most of our things are vectors (i.e. arrays)
This line isn't needed, nor is line 1 (commented-out import).
...missing javadoc
On Jun 5, 2012, at 2:03 AM, Mike Jarvis wrote:

>>          */
>>         virtual void fillKGrid(KTable& kt) const;
>> 
>>         /** 
>> -         * @brief Utility for drawing an x grid into FFT data structures - not intended for public 
>> -         * use, but need to be public so that derived classes can call them.
>> +         * @brief Utility for drawing an x grid into FFT data structures 
>>          */
>>         virtual void fillXGrid(XTable& xt) const;
> 
> There are currently a lot of doxy comments for private and protected functions/members.  This question probably deserves a separate issue so people can comment on whether we want them or not.  (I usually only write doxygen stuff for the public interface, but I see some text in doxygen_readme.txt recommending doxygen stuff for private functions too.)  So for now I just left this in as a doxygen comment.  (Although I did humor you and make it a single line.)

Yes, maybe worth a separate issue.  My take is that while we're developing it's useful to have private functions documented because we might be changing some of them, but once we release the code we won't want the documentation cluttered with lots of private functions.
oh!  maybe defaultVal should be an object?
Rather than just use an empty list in Solo, it would probably be better to raise an error. As I write this, it can probably be more generalized to either solo or client that finding 0 servers should be an error. What do you think of this logic?

```ruby
servers = if !node[:collectd][:servers].empty?
  node[:collectd][:servers]
elsif !Chef::Config[:solo]
  search(:node, 'recipes:"collectd::server"').map {|n| n['fqdn'] }
else
 []
end
raise "something" if servers.empty?
```
Those actually **are** matched single-quotes.  :)  I think it’s just an oddity of whatever monospace font Github is using.  

Try copy-pasting it into somewhere with another font.  You’ll see…all is well.
oui, mais je pense que Internet va amener une diminution de la valeur totale de cette industrie, un peu comme l'arrivee de free detruit 10000 emplois chez les autres. Je ne rentre pas dans les details car je trouve que c'est trop vaste comme sujet.
`${2:Base_}`, so if possible to use global \Controller without the need to remove `_`
Why do you need to `preventDefault` here and manually go to the href in `onlogout`? Can't you just do the thing and then let nature take its course?
It'd be good to document what this plugin provides.
I am going to take these issues per module and sort them all out. I have wanted to do this for the longest time anyway
debugging left in?
Would also need to update the `FrameworkBundle\Resources\config\schema\symfony-1.0.xsd` I believe.
Document the node key format with an example.
From a code-structuring standpoint, I think it is better to handle success and then handle failures rather than worrying about nesting levels. Also, having the error case below puts it closer to the onerror handler on the lines that follow it.
Please revert this  change. Let Lauren fix the indentation.
If it's single digits, it now shows up like "4:1:36" instead of "4:01:36", now.
Erm.  Can you readd this, but convert the checks to the correct type?  That is probably what was borking it.
use traits for that :) "utils" static classes are here because traits were not available yet :)
Why the function renaming?
These updates are now in.
Just to be on the safe side, you should set the detailViewController delegate to nil before releasing. If something else is retaining it, it could try to send messages to the a deallocated reader controller and crash
@Haofei have you verified that on a fulfilled deal, but with inventory left for the user to purchase, now still is "available" to buy? I was also expecting a spec to be updated as part of this, is that WIP?
Да. Понял в чем ошибка.
Зачем одинарную кавычку экранировать?
А можно без StringBuilder писать сразу в System.out (print/println)
Ох, не заметил. Ты закоммитил некомпилирующуюся версию.
И здесь это могла быть одна строка.
Debug logging was overkill!
Not sure if on_demand is the best name, if you want to make this optional and improve it at the same time may I suggest:

    request_listener: 
        enabled: true|false
        parameter: anything (default to existing apidoc)

    request_listener: false should be the same as marking enabled: false ideally.
This will, in other words, only work for your own profile?
This call should go in the 'configureReaderPreInit()' method.
There is "broadcasting" along axis. You don't need to repeat.  ``Y /= np.sum(Y,1)`` should work I think. 
+1 for not normalizing
I was starting to panick when I though of all the code needed to remove the duplicates. Fortunately Scipy caters to lazy bums like me :)
Do we really need a _pairwise property in the base estimator? That seems like a code smell to me: subclass-specific code coming up in the base class. It seems to me that a simple test in the code where this is called could replace this property and not add any lines of code. Something like:
<pre>
if getattr(estimator, 'pairwise', False):
   blah
</pre>
>
> > +    def transform(self, v):
> > +        """
> > +        Computes the probabilities P({\bf h}_j=1|{\bf v}).
> > +
> > +        Parameters
> > +        ----------
> > +        v: array-like, shape (n_samples, n_visibles)
>
> n_visibles is n_samples, right? If so, then this should just be called X,
> not v.
>
Here n_visibles is actually n_features (has been renamed in a more recent
commit). v is indeed the input samples, but I use the notation that is
common when dealing with rbms to make things more clear.



>  —
> Reply to this email directly or view it on GitHub<https://github.com/scikit-learn/scikit-learn/pull/1200/files#r1755791>.
>
>
I prefer it the way it is, as getting the features out is not the important part, the important part is formulating it as an estimator.
please add docstring
You could do `del self.random_state` at the end of fit then.
In general I agree. Tying the "threshold" and multiclass is bad design.
The reason I'm doing this is because of the interface of the loss functions that need continuous predictions.
They want a single number.

I could just try to find out whether there are two classes and then do what I currently do, or otherwise just give the full decision function or probability to the score function (because they have the same shape in that case).

Do you have any use-case for having more markers? I think in the end the user has to know what they are doing. Adding a string that describes the loss doesn't hurt but I don't really see how it could be used.
```python
XX[ii] = 0
``` 
->
```c
__pyx_t_10 = __pyx_v_ii;
*__Pyx_BufPtrStrided1d(__pyx_t_7sklearn_7metrics_14euclidean_fast_DOUBLE *, __pyx_pybuffernd_XX.rcbuffer->pybuffer.buf, __pyx_t_10, __pyx_pybuffernd_XX.diminfo[0].strides) = 0.0;
```

versus

```python
(<DOUBLE *>(XX.data))[ii] = 0
```

->
```c
(((__pyx_t_7sklearn_7metrics_14euclidean_fast_DOUBLE *)__pyx_v_XX->data)[__pyx_v_ii]) = 0.0;
```
as you don't use op, you can ommit its name, which make it clear that it is only used for typing
why is this necessary... why not use body[dir=rtl] { ?
Why are you downcasing these?
Braces should be placed in their own line.
This can be static const
La liste des métadonnées du document sélectionné
To notify where Accessors begin, but above there already things.
Also, for the micro-bosh, we use the stemcell with "micro-bosh" in the name.
If you ever manage to get AA working on such an IDE, I'll buy you a couple of pints :)
in the <programlisting> tags could you remove initial whitespace? If we respect the XML indentation, that whitespace is included in the formatted code, so the end result isn't very readable.
@stuartort in gh-2057 explicitly requests that "Any users that have the file open with write access should not be notified."
I find this line hard to read - I've scanned it several times.  

I think it is something like

if (canSpill() && hasRowsOnDisk())

Is the canSpill() required now that the collector->setup parameter has changed?
How did this compile in 3.8.6? Or it never compiled with MSVC?

I was talking to Richard, and he said that it's possible that newer versions of MSVC support this... Anyway, I can use OwnedMalloc...
Did you mean to also delete this call?
Is this restriction going to cause problems?
You do not consistently check `rev` for null when creating tags; either do so, or make it nullable.
Oh, I didn't remember that one :P
Left a puts in here
Move that on same line and add a space after `if` please.
Please use `strsplit()` from `common.h` instead of `strtok_r()`.
remove from smoke test so that it only works on d8.
update all your spacing to match the correct line spacing. Eclipse will do this for you.
Yes, if left alone Spring's default RestTemplate FormHttpMessageConverter will automatically decide between that or multipart depending on what parameters it finds:

http://static.springsource.org/spring/docs/3.0.x/javadoc-api/org/springframework/http/converter/FormHttpMessageConverter.html

Of course it took me <embarrassing amount of time redacted> to figure out why I wasn't seeing the documented behavior in my testing.  :)
Nyt jää huomioimatta tapaus `[2 3]`. Lisäksi `vals` palauttaa jo sekvenssin, joten `seq` kutsu on tarpeeton.
Typo: "namet" instead of "namnet".
this belongs in the private, not the public. see filterType for an example

also, call it "searchPattern" as that's a little more descriptive
We should really just allow a ```URI``` object for this and not have to monkey around with converting to ```String```.  Another day.
Can MSF_LICENSE be used? of you would like to use BSD_LICENSE?
I would just suppose that the keyword argument was correctly written (usually we don't allow for case/whitespaces flexibility)
Is a `magnitude` of zero allowed?  No?
any reason this was uncommented? IIRC we left it in for debugging purposes. In some cases we may not actually want to print these exceptions (since there are cases where JS will want to handle exceptions that aren't actually bugs)
"cancelBubble" is set to default value only when the user or the JAVA side does not explicitly set that property. If the user already set it to some value, even it's a garbage, we should keep it instead of overriding it. Then at the time we need to use this value, if it's not a boolean we just use the default value - false. The difference between keeping it and overriding it is if the user set event.cancelBubble="unknown", it will always return "unknown" when the user try to retrieve this property later.
Would it make more sense for `AndroidModule` to set `GeolocationModule.androidModuleInstance` from the `AndroidModule` constructor?
Given that this code is included both here and in the module build template, couldn't it be placed in `support/iphone/tools.py` and then loaded as an external module in the builder template (which already loads the compiler)?
One  last set of stray single quotes.
Indentation is incorrect
this should probably be in a ruby_block
This is the part I dislike the most about my change, but I think it is a necessarily evil.

The reason I don't think it can go down into the `Http` object directly is that we need several pieces of information that we don't know about:

1. How to regenerate the headers
2. How to login

The `Http` layer is Splunk-agnostic to some degree, as noted by `test_http.js`, which doesn't even hit a splunkd instance.

One option is to actually have `get`/`post`/`del` all bottom out to a single method in `Context`, and then have the wrapper happen just there. However, that would mean basically duplicating the logic in `Http.get`, etc.

Thoughts?
OK, great.  S, V, X and U have all been lowercased; the Vprimes have been left alone for reasons described.
Why? In contrast to `l` postfix for integers it doesn't cause any ambiguity.
I like that `minification` :-)
Right. I always put it and forgot to remove it. With the new API, it won't be necessary anymore :-)
Sande, for this one, we should update the guide as well. Do you want to try doing that, so you get familiar with it?
I don't think it's a good idea to set this to true by default. Should we really force every dev to use this?
could you translate this message too (and uncomment it once done) ?
My reason was to minimize # of lines I am chaning - this pull request is big enough even already. Also, unless there's a restriction on length of constants/variables, you can never predict how much space you should allow between a variable and a value. I personally think that such formatting is definitely nice to have, but it should not be required because in case of long variable names it actually reduces readability of the code instead of improving it.
Please follow the style conventions of the project and indent with spaces, not tabs.
This is temporary, as the code migrates.
Also, this is indeed a per environment setup, since the production setup is required to fully install an admin node for some of the testing efforts.
Great, will do it as soon as the related pull-requested is merged in (which I'm hoping will happen in a matter of hours/days :))

Don't close this pull-request, I'll add stuff on top of what you have right now.
Das selbe hier....
Das LobBuch wird geschrieben... und nicht editiert....
Zudem kannst du LogTime wahrscheinlich weglassen 
(Da alle Entitäten eine created_at Spalte haben)

Ein getLogTime(){ return $this->created_at; }  wird wohl reichen
Аналогично - предложение не выкидывать исключение, если пытаются подвинуть вниз последний элемент
Меньше писанины, по определению не может быть конфликтов, компилятор может это соптимизировать, нет ебли с переименованием файлов.
can't we determine the value of this field from the isChanged() method?
This is wrong.  The cids are not the callback functions themselves, they are the integers returned by the call to mpl_connect().
cool, fixed
Like with `skipped`, this would be a more useful API if the list of warnings were a list of two-tuples, where one item is a constant from a list of constants comprising the possible reasons for a warning, and the other item is the model instance that generated the warning (e.g. a Case object). This differs a bit from `skipped`, because here you'd actually have a model instance, with `skipped` you didn't create one so you just have the original import data.
Oh, and here you use both CommandError and new-style string formatting, so clearly you already know about them :-)
I thought doing a brute force find on the id on a single table would be better than a join to pull the companies for the given user. Yet with caching it's possible that the cost of self.companies is negligible. I'll change it.
To @blackwhale:
> OT: There is one question (I'm no expert in inner details or R-T). What would GC do when it tries to collect the object that was explicitly finalized by user? I'd suspect finalizes it again.

It calls `rt_finalize2`. And `rt_finalize2` do nothing if the object is already finalized (`vptr` is zero).
Alternative to double negative: "with nontrivial destroy". And you can change "static assert to ensure" to "Ensure", we can see there's a static assert in code.
Pretty sure this should be: `-z,noexecstack`
MINOR: would be nice to have in { } brackets, and maybe sort out turning off IDE tabbing?
Could you maybe add some JavaDoc here, like a short summary?
I think you need to protect this from concurrent access, to prevent it wiping out a new connection after a failure.

Consider 2 threads sitting on receive; the first comes in here and nulls this.replyDestination. Say a third thread comes in and establishes a new this.replyDestination; subsequently the second receiving thread comes in here and, again, nulls this.replyDestination.
Similar to line 13, perhaps take the emphasis off tests and change this to something like:

And in case we didn't emphasize it enough: we love contributions!
this is grabbing a floating IP, but when you create one with "nova floating-ip-create" it returns this tabular response. So I was just looking for the line that  was the un-associated IP, as in:
root@sdu-os-1:~# nova floating-ip-create
+----------------+-------------+----------+------+
|       Ip       | Instance Id | Fixed Ip | Pool |
+----------------+-------------+----------+------+
| 192.168.100.66 | None        | None     | nova |
+----------------+-------------+----------+------+
something went wrong squashing the commits, will fix it
No, xaxis. This is a parameter of the flot.navigate extension.

On 14. 09. 12, at 09:22, Mitar <notifications@github.com> wrote:

> selectmetric
Add a "the" between "matches" and "request"; add a "the" in front of "respective".
This sentence is also from Colin Percival I think? If so, shouldn't we attribute him (or the name of the paper it's from)?
@christianv "The Widget API section" text should ink to /sdk/api

Also, change 3rd party "library" to "libraries".
Не было.
I don't see the point of this method, can you remove it ?
It can be removed.  I updated the pull request.

On Mon, Sep 10, 2012 at 2:30 PM, Jim Klo <notifications@github.com> wrote:

> In LR/lr/util/decorators.py:
>
> > @@ -368,6 +369,7 @@ def create_user(name, password, roles=[]):
> >              except:
> >                  pass
> >              finally:
> > +                print user_doc
>
> This is my only complaint... can we change this to log.info or log.debug?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/LearningRegistry/LearningRegistry/pull/230/files#r1569029>.
>
>
search queries return more than one node. as do getNodes queries. but i don't fully understand when this is called, so not sure if the function will return more than 1 row.
it looks like StartEvents is being called every time purchase is called, it would be better to check a flag rather than call this each time
Although I am not sure I understand the code above: +1 for raising a `ValueError` if the size of the smallest class is less than 2 (which AFAIK is the only kind of invalid data that break SSS). The error message of `StratifiedKFold` has been fixed / improved recently. It could be reused this this class.
I tend to prefer just importing modules when ever I can. Which matches the code style I need to follow at work better and it's more obvious where things come from. But since this is consistent with other existing imports I'm fine with not switching as consistency wins. Also this is more in line with django's own code style.
extra spaces from suffix removal throughout
And this. :)
do you understand why this was ever here in the 1st place?

Looks like clearFiles is no longer used at all, should it also be removed at this juncture?
What about using `wcf\data\language\item\LanguageItemList`?
On 02/24/2012 11:54 AM, minty wrote:
> So autocheck() should return the current state, and autocheck(1|0)
> would set it?

Exactly. :)
if we're not *really* using these, we need to gut them and dependent code. they can be added back in a second pull req. Same for the requires/includes/etc...

If the plan is to stow them away until the need arises, again, I'd urge you to consider losing the code for now (or cherry picking it out to another branch, etc) until we can merge it in and it makes sense to do so.
These are meta tags. You can have a single set apply to all the events.
iOS5.1 just uses the regular backup/restore, nothing extra to do here.
we _could_ send real dates, right?  can you think of a benefit of sending just string representations besides being pre-serialized?
Thanks for the awesomely quick turnaround!  And thanks for writing the
module in the first place - I'm finally writing some useful Dancer
tests :-)

Cheers
Grant
same as 404
Assume 'something' is the id
Табуляция поехала.
> node
> note

Простите, що?
unnecessary comments in line 298, 300 and 302.
Reading the expect statement is just as easy as reading the comments.
Unfolding will be in it's own changeset.
Couldn't think of a better way to get the group uuid, so i stored it in a GP for later use, is this correct?
all tests should check for explicit counts
So, I don't think the QUnit.start() on line 217 is hurting anything because if the onSuccess doesn't run, the test will just timeout without any tests being run and it will fail.  Although, it really doesn't make any sense to have two start() calls in this case so I removed it.
I'm ok with `section_id` being capable of taking an `id`, but I don't think it should take one by default.  If you already have a `section` object, you shouldn't have to run another `get` to fetch it.  What about something to the effect of:

    if not isinstance(section, Section):
        section = self.get_query_set().get(pk=section)

It could actually be wrapped in a decorator so each of these methods doesn't have to repeat the same boilerplate code.
Thanks. Silly me.
the expression (= (mod n divisor) 0) returns a boolean