labofsahil/github-event-dataset-2012 huggingface dataset:
It would be better to avoid dash (`-`) in class names now, as it prevents from refering to their variables and it might get deprecated soon.
AdditionalTest1 - не очень удачное название для теста.
Для этого есть какие-то инструменты, или нужно делать посимвольный append? И если да, то можно набор экранируемых символов?
Зачем replaceFirst class?
s/instance/panel. There are several references to "instance" in this patch. We renamed "instance" to "panel".
This loop isn't very pretty. Can we do something like we have done on Addon-tests and have a method called `click_first_unpurchased_app` ?
No issue, but I don't see the advantage of that added complexity. A list of categories is simpler, no?
Usually, yes--but in this case the fit is often done via `estimate_transform`, so we need some docs there (is what I meant--sorry for being vague).
I would write:

```
log_like -= .5 * (fast_logdet(self.covariance_) + n_features * np.log(2 * np.pi))
```
I think, if latent_cov is a covariance matrix, this can be optimized as: 
    
    loadings = linalg.solve(latent_cov.T, np.dot(latent.T, X), sym_pos=True).T
same here about allocating full dense Id matrix
`svenfuchs` is a lame name, I'd prefer `sparkling_unicorn`
JACC spec has all the http methods which are equal to 7.  delete,trace,put,head,post,get,options.
Is this just a tidy up?  Can we clean it out?
Don, what do you think?
should be 'aud_l' instead of unknown, my bad
1 ou 32 ?
Cette méthode évite le besoin d'avoir à stocker le jeton d'autorisation d'accès.
com CANCELLATION_TION as mina π-RA
This is wrong, should be += matchLen... fixing...
You can avoid manually filtering like this, via getDebugValues f
i.e. 

Owned<IStringIterator> debugs(&cw->getDebugValues("thorlog*"));
yes, I misremembered
(would need an extra if !shortfall outside the loop I think)
It has nothing to do with Dali, the comment was wrong and outdated. It's to do with the fact that the stand alone unit exists or not. All I'm doing here is telling that, if the run is stand alone, use dynamic resolution. Other places are testing to see if the run is also form a workunit, covering the remaining case for dynamic resolution.

Dynamic resolution must also work with local files (will not yet, but that's a required change I'll do next). In fact, I'd argue that dynamic resolution is mandatory for local files, since (I guess) you'd never be using local files with deployed queries... right?
This line is a copy&paste of what was there before.
Agreed, removing it. I just put it in order to mimic the same approach already found at lines 593 or 552
remove till the end
Write this as:
```
response = api.get(
    product=product, 
    version=version,
    start_date=start_date, 
    end_date=end_date
)
```
@peterbe I don't think the service should assume that much what it's being used for ... this could be used for other reports that might want to sort differently so it would be better to be explicit I think.
arh! I spoke too soon. 
Then you can just use

```
{{ product_versions|join(', ') }}
```
Ooh, we really need to hammer down an explicit list of exceptions to catch here. Naked ``except`` makes my eyes bleed (when they are not needed.)
I suppose it should be put in IOEncoder. If the IO object doesn't support `#stat` an unspecified exception is raised.
@pborreli merci d'avance ;)
That's ok for now but we should make this configurable via a cli option.
These "available_getters", "no_cache_getters", and so on, are becoming more and more ugly to me.
We should refactor this later on. I don't mean in the current PR, as it's structural.
you should add a note about coding standards, linking to the Sf2 doc
cf. https://github.com/WoltLab/com.woltlab.wcf.acl/pull/40/files#L1R3 (and there may not to be a blank line between line 2 and 4).
This feels a duplicate of line 575, maybe you can rewrite that line as
`if (!url || !url.url) `
No - for some reason, on 2.2.2 getMethod returns null, so I replaced it by
getting all of the methods and iterating through them until I find
initialize

On Thu, Sep 20, 2012 at 2:10 PM, dmansen <notifications@github.com> wrote:

> In src/main/java/com/cloudmine/api/CMApiCredentials.java:
>
> > @@ -47,11 +48,14 @@ public static synchronized CMApiCredentials initialize(String id, String apiKey,
> >                  throw new CreationException("Running on android and application context not provided, try passing getApplicationContext to this method");
> >              }
> >
> > -            Class.forName("com.cloudmine.api.DeviceIdentifier").getMethod("initialize", contextClass).invoke(null, context);
> > +//            Class.forName("com.cloudmine.api.DeviceIdentifier").getMethod("initialize", contextClass).invoke(null, context);
>
> accidental comment-out?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/cloudmine/cloudmine-javasdk/pull/18/files#r1653717>.
>
>
I think you should add "| nothing" here just in case"
Yeah, I guess I've been doing too much Javascript recently where it's so common that stuff replaces itself and so on...
@christianv NM, looks like you're removing these links systematically.
I'll update my settings, thanks.
i'd rather `DELETE /repos/:owner/:repo/notifications` to clear all notifications for a repo.
```ruby
1.9.3-p194 :021 > YAML.parse({:key => :value}.to_s).to_ruby
Psych::SyntaxError: (<unknown>): found unexpected ':' while scanning a plain scalar at line 1 column 3
````
There's one problem with that: the plugin will become sfPropelOrmPlugin instead of sfPropelORMPlugin.
Why put this variable in a quote?
Point taken about the variance! We should indeed normalize by the variance. However, I just realized that we normalize the square of gradients by data.std() and not by its square (the variance). This very much sounds like a bug. Also, we should get rid of the ugly `10` factor. 

Anyway, this is not really related to your PR, so we can postpone this fix to a future PR, but I'm really glad that we can discover these problems by working together on your PR.
I have noticed that in this example the coordinates did not match exactly the feature, and also using different wavelet levels produced different number of features. Seems the algorithm works better with natural images than sparse images like this.
this won't fail, just won't use the database option. so the return from this will just be the username and password
Since JulianDates only represent TAI, all methods assume TAI.  However, you're right, this method appears to be backwards (and so is the code that uses it so that's why everything works).  I'm going to rename it to getUtcOffset and it will return the number of seconds that need to be added to this (TAI) date to make it UTC.
Then is the documentation wrong, or am I just illiterate?  Because it reads to me like it's going to tell me the lower left corner.
Missing space between `if` and `(`, missing space between `)` and `{`.  Try selecting just these new lines and running the Eclipse formatter.
I use a dirty list in `BillboardCollection`.  It is great for static data and when a small (10-30% ?) percentage of billboards are dynamic, but is a bit slower when everything is dynamic since the dirty list becomes an extra step at that point.  When looking at the entire system, I'm not sure that the overhead matters.  However, I am up for brainstorming other ideas if you want.
By configurable, do you mean that this catchall route should this be @injected?
It appears that composite actually fixed this behavior, probably by how it does the bounds restriction when drawing. There are still bugs with image sizing but they're not this severe and are definitely due to something else.
ditto re get()
Considering events propagation, we should use proxy.hierarchyHasListener().
Actually this only gets values from self.model_instance, if we do not pass an instance the `set_form_field` method gets the default value for the field.
Pergunta filosófica: seria este o local ideal para estes métodos? E a questão das responsabilidades?
Details is too generic as name. Call it RepositoryWidget or something like that.
Easy enough to fix.
It could; the two are equivalent forms.  Do you really care?
@hunner I don't understand. Should I take action with this?
Why are you deleting this?
Yes and for the delete too.
Why have you added a slash a the end?
Tentei assemelhar com os comentários do JavaDoc e PHPDoc
I think that's static, since it's private to the module
> `popFront` clearly describes a function, from my viewpoint, it is a clear cut case that it should be `@property`

Huh? Properties are intended to emulate variables, so the fact that `popFront` is clearly a function rather than a variable means that it's clearly _not_ supposed to be a property. That's `@property`'s entire purpose, and -property is intended to enforce that. In fact, the fact that a void function with no parameters even compiles with `@property` and -property is bound to be a bug.

But regardless of all that, as for `isBidirectionalRange` compiling with `popFront` being a property, it's not a bug with `isBidirectionalRange` (or `isInputRange` where `popFront` is actually tested - `isForwardRange` checks it so, `isBidirectionalRange` does as well by checking `isForwardRange`), it's a bug in the compiler and the implementation of -property. The two primary reasons why -property even exists rather than simply making it the normal behavior are to give people a chance to fix their code first and to give the compiler devs a chance to iron out strict property enforcement (since previously, `@property` wasn't necessary for using property call syntax, and `@property` has been being phased in rather than immediately breaking code when adding it). So, it's not exactly shocking if -property doesn't work perfectly.
>  apologize, I must be dense

May be... But definitely not denser than me.

> but I still don't understand. Could you illustrate with an example how "moveOver" would not work ? :/

If some struct store its pointer somewhere. And when (I hope) GC will become "moving", such struct will just add a check if it is allocated in GC heap and if not, still consider itself unmovable.
But it's not `$(D dchar)-qualified`, it is `$(D dchar) qualified like $(D T)`. I can't imagine `dchar` as a qualifier.
```enforce``` is better in this case because this is not an error of logic.
I think 'or' is misused here. 
The point is to show the sequence of actions. Meaning "Matches A, failing that, matches B". 
'or' only blurs the picture
e_1 is not defined anywhere
`element["append_to_tag"] = true`が、特に目立たせたいという意図がある(たとえば例外投げる場合とか)なら後置でもいいと思うんですが、そうでないなら普通の`if`の方がいいかなーと思います。
> You say API 1.1 expects the header to be in seconds. I'm confused, what changed here?

Sorry, you're right. I'd just been having a conversation with my API 2.0 hat on :D

You should be using `Utils.millisecondsToDecimalSecondsString(ms)` here.
+1 then, just wanted to make sure

On Thu, Mar 29, 2012 at 13:02, Christoph Gritschenberger
<reply@reply.github.com>
wrote:
>> @@ -47,10 +47,6 @@
>>      <property name="bundleContext" ref="blueprintBundleContext" />
>>      <property name="taskbox" ref="taskbox" />
>>    </bean>
>> -
>> -  <bean class="org.openengsb.core.workflow.internal.TaskboxConfigurator" init-method="init">
>
> this bean is never exposed anywhere.
> The class is internal.
> I think it's OK in 2.x.y
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/openengsb/openengsb-framework/pull/656/files#r620458
should this be >= ?
Whoah, TImeframe knows *way* too much about Iso8601's implementation/internals!
The task will fail with the NullReferenceException. However, according to the docs, this will never happen; a successful get request should return either an atom feed or an atom item.
can this use a variable?
looks more like `def` to you.

har har
nothing we can assert here?
Same as with get_file.
If you do not see a general purpose here, you need to prefix this function like "metalink_strictFilter", so that other test will not collide with it if they create functions of the same name
We should really use ClassSection.preregister_student(), because otherwise students won't get added to mailman lists (MIT only).

If we don't want to do that (it would take at least three database hits, which would be a problem), here are some other possibilities:
 * We can override StudentRegistration.save() to give it the mailman functionality that it should have. We've been talking about doing this for a while, but haven't gotten around to it yet. We would also have to double-check that .create() calls .save() (I believe it does, but I'm not 100% sure).
 * We can add a few lines at the very end of save_assignments() (so after all students have been added to classes), which loops through all of the ClassSections, and runs the appropriate mailman functionality.
что бы никто не мог установить текст на пин таб
Requiring a numeric code is rather unfriendly and harms readability of user code.  It would be nice to have location specifications and codes factored out, and encourage use of names.  Even in mpl code, names would be better where possible.  One concise naming method for such location is map-oriented: e.g. NE is upper right, CE is center right, C is center, etc.  Or one could use T for top, B for bottom, L for left, R for right, and C for center.
Wouldn't an actual round trip be accessing the rels-int with bdrxml rather than xpath?
Just for a `WARNING` comment.
Want to wrap these in backticks while you're here?
I would suggest that you name also the option `nmetrics` (`dest`).
Thanx, i changed it.
This is nitpicky, but can you please fix the layer name ;)
heh, no, it's actually

if search['multiple']


man, I need more sleep

-Tom
On Thu, Nov 1, 2012 at 2:29 PM, Walt Askew <notifications@github.com> wrote:

> In providers/app.rb:
>
> > @@ -86,7 +86,23 @@
> >          end
> >
> >      end
> > -    Mustache::template_path = ::File::join(version_dir, 'gbtemplate')
> > +
> > +    context = node.to_hash
> > +
> > +    gearbox_data_bag = data_bag_item('gearbox', name)
> > +
> > +    (gearbox_data_bag['searches'] || []).each do |search|
> > +            matching_nodes = search(:node, "roles:#{search['role']} AND chef_environment:#{node.chef_environment}")
> > +            results = matching_nodes.map do |result|
> > +                { search['attribute'] => result[search['attribute']] }
> > +            end
> > +            if (search['multiple'] || false)
>
> is that just "if (! search['multiple'])" ?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/NarrativeScience/gearbox-cookbook/pull/3/files#r2009026>.
>
>



-- 
Tom Howe
Senior Software Engineer
Distributed Systems Lab
University of Chicago/Argonne National Laboratory
这些都是怎么回事呢？
je tournerais peut être juste un poil différemment "mal l'intêret que peut avoir l'utilisation du pattern *visitor* notamment lorsque l'on travaille avec JPA". Cela fait un peu moins abrupt :-)
Why is separating the `name` from all of the other donation type information useful?
should = must?
Right, we're mixing two dependency management systems here, which is dangerous territory.  

Option (a): force the user to stick with closure. There is something to be said for consistency and not trying to mix the paradigms.
Option (b): allow Rails deps management to run prior to closure. Specifically, I think the simplest way to make this work is not try to mix closure and rails, but serialize them. The rails deps management should run first, which will output a concatenated file (which we can write to a tmp file or similar), and then point closurebuilder at that file and let it do its thing. 

P.S. http://bolinfest.com/coffee/ - that actually points towards option (a), I think.
Actually, I get an "invalid application" error which seems to originate due to the file is not downloaded. That means the exception never occurred, which I am investigating now. It may be the same with the error you get(or they may be related).
I prefer to change the checking for conf parameter in constructor as it is always called before the other functions
"to delete a ... directory in the file system."
There's already a public ServiceBusService class which is actually a factory for instantiating the service. Also, this is similar to what we did in Java SDK.
We can create an expected return object and check that success() was called with that object
Why is this file necessary if it only exports another module?
If download is not being implemented yet, this should not be here
Just one comment here..Is that really needed, to assign this to that?
Maybe it could be done directly above.
Shouldn't this eventually also reflect the $env style? Also, what is the correct order? Can't this also be packed in a single glob?