labofsahil/github-event-dataset-2012 huggingface dataset:
The current implementation allows two levels of control, basically like a master switch (log level) and a detailed switch (verbose). This allows for pretty straightforward of recording, say, no processing when inputting raw files and doing projection, but then recording processing when doing covarinace and inverse calculation.

The alternative, as I see it, is to remove all "verbose" arguments. This will also work, but will require more lines for the user when they go to change what gets logged. For example, if there is one command they don't want outputted to the log, they will have to do:
```
set_log_level('WARNING')
... command ...
set_log_level('INFO')
```
Instead of just doing `command(verbose=False)'. This works, but seems less convenient to me.
Not sure why these used to be in np.arrays. I'm pretty sure I wrote that line. In any case, it's not necessary, and elsewhere we assume it's going to be an int instead of an array, so I axed it.
... mutatis mutandis, so this applies to all the tests, right?
Perhaps using different paths for each route, eg routes1, routes2, routes3 etc would fix this.  Not sure.
Did you mean er.extensions.appserver.projectBundleLoading? I can't see that a property ERXApplication.Loader is used in ERXApplication.
Will this comment show up in the compiled version?
Can we rename this argument to make it clearer that it's a Matrix instance rather than an array.
You're missing the `var` before the `i` here which makes it a global variable.
using `case` here is kind of weird: it’s probably better to make to use the total function syntax:

    future onSuccess { reply =>
      println(reply)
    }
removed.  Using connection ! PoisonPill
Add explicit return types for all of these
This function no longer exists.  Please direct users to use ClassName.help() here and in other docstrings.
Ah, of course: http://www.youtube.com/watch?v=gRdfX7ut8gw
This code assumes that you want , instead of . all the time. Obviously this is not the case. You should just transform the data with a custom behavior on the model using afterFind() and beforeSave()
fantastic!! +1
No entendí bien qué significa este punto. ¿A qué se refiere?
This should be imported properly
@nlegoff already created the 370a7 patch, you overwrite its patch.
Please revert his patch and rename yours to 370a8
I prefer split, then strip each item because I think it more clearly expresses that we want to ignore the whitespace as we parse a comma-separated list of values. Within the constraints of this use case, I think either way of doing the parsing is functionally the same, so for now changing it won't give us better results.
i like. i had no idea about the tree() function
Why not add this to the error itself and pass that param as a kwargs?
Now here is where I would have suggested a rename ;)
This should be `STAssertEqualObjects`.
just ``mixed`` seems enough.
I don't believe that you can have setup or teardown run for a single test case (or selected test cases) in a class, but I would think that just moving the test into its own file would be an option.

You could look into using a global variable to control the behaviour of teardown, but that seems overly complicated to me.
8-bit, 16-bit, 12-bit
Rather rename them to "Stop()", and "Delete()"
You do not need this since you have OpenLayers/SingleFile.js as dependency.
We added this media query not to have `translate3d(0,0,0)` on Android because it caused pan performance problem. I don't have any example showing it, nor do I know if it still applies.
This looks weird since we won't remove a pin on `$ensure=='absent'`, but I've confirmed that apt doesn't seem to care.
Great.  Done.
Are you referring to the `sakaiGroupsAPI.groupData`? If you are I think we can lose the `_`
Please refactor MatrixFeatures to use SGMatrixList underneath and allow arbitrary matrix sizes (not just matrices that have same #cols). Please note that we had this  type*, int, int mess for quite a while and it really did no good so this really is an important change.
I will rename this parameter, it actually doesn't cope with computational thread, but with the number of cutting plane models
Can we throw an exception here if no component was found? Might make debugging a bit easier.
Parameter name must be $entity to match the actual name
This change actually breaks functionality in the commercial editions, where the role controls for Users and Teams is shared.
Hmm, so I dug through the commit log, and there's a commit 638017 that explicitly adds saving the experiments here. I get the feeling that there's something else going on. idk what though...
Please don't do this. The deprecated tag in the doc is enough. This will just needlessly break output.
Are you sure the method ``query`` can be called on ``$this->dbAdapter`` (of type ``string``)? Please also check line 86.
Are you sure that ``$i`` (of type "object<PHPUnit_Framework_MockObject_MockObject>") is traversable?
Which makes me think, that the way the plugin works at the moment we won't be able to automagically convert objects to json.
Ah, so minifier minifies window, document and undefined to 1 letter variables. Thnx.
Ну и, конечно, всему этому коду не место в контроллере
Is there any way your service can accept a bulk payload of multiple commits?  I'd love to lower the number of HTTP calls if possible.
I get compile warnings for all of these warning:
conversion to 'float' alters 'double' constant value.

Feel free to just make it an array of doubles, if we dont want a million 'f's on every line.
It could be int, or BOOL. Anything defined as acceptable by JSON standards. Yes its trivial to convert to string, but do we need to?
Hah. Nope. Good call.
Like the case of "lock" I removed this one.
No need for `?` at the end of the URL.
Why `object` suffix?
This is not good. You are creating this form multiple times on the page. DOM forbids having the same ID on multiple elements. And you assign constant/same string to all of them.
Hm, somewhere should also be displayed the date of the horoscope. For people to really know for which "today" this is. So this header is good, but somewhere in the body of panel should be a more precise date.
Это закрывающий тег php. :)
Why not `self.defaults.update(defaults)`?
As it turned out, it was more tricky than I originally though.. I have just added a commit [with support for System.Int64](https://github.com/moodmosaic/AutoFixture/commit/3a67037cfd25a82ef1dc82208897905cc2a059c1).
This was not supposed to be here 0.o
I'm confused by this recursion. Could you add some comments to explain what the purpose is?
I think I didn't understand how objects are "mapped" on Mongo..
I like this name better:  isCurrentRowForSameEntity(). That's what I'll use.
No worries at all :) glad you're happy, thanks.
So, I take it you do not like the recommended mozilla-central style I suggested in your previous pull request?
I believe it is the other way around. Even though the SQL bus does not allow multiple out of process subscription, the single subscription always reads the messages in order, across all partitions (it does not do physical partitions, as it is a sample bus at this point).
> reinterpret_cast? 

Done, but ugly.

> cache the results of Name() and Value()

Done.
switched from `ngx_pnalloc` to `ngx_palloc`.
Out of curiosity, why is GoogleString a std::string typedef?
But it is not a big deal just add it to .gitignore and remove from gitindex thats all :)

We dont have to implement the instalation script right now because you already have it
Come on, aren't we at at least 0.0.0.4 now?  ;)
why deprecate this?  this method makes it easy for subclasses to add/remove/reorder the fields which get included in tostring.
the ToStringHelper approach looks like more work.  (although in the usual case we are adding fields it's fine, so no strong feelings.)
you could use this instead:
exec { "Test lens ${name}":
  [...]
  subscribe => File[$lens_dest].
}
Will that harm ? I guess if you have new columns then south will ask for `defaults` and if you don't want to use the added functionality you will leave them with the default values and not use it in your interface !

Isn't it ?
It is because this abstract private package method used only be matcher.
The abstract class should not have an access to run().
The call1() calls either run() or call() depending on implementation Block/Callable.

Then the evaluate() evaluates call1(), and toString() returns actual status of invoked block on call1.
Vis nyheden live <br /><em>(åbner i et nyt vindue)</em>
No. Change must have been made by one of the commits I merged. I'll revert it.
Wouldn't it be easier just to check the format when they add a to, from, or bcc?
This cast worries me. There's an explicit type in C99,  `ptrint_t` that should be used in these cases.
Starting with // -- is that a shorthand for something? It's missing the protocol, so it's not a complete url, so I'm puzzled.
Please add this file to your .gitignore.
Remove it.
commit again and push.
Ah, that function. It was originally there just to test. I'll move it to its own header and add the missing merge-base-finding functions.
You sure it compiles without the W?
Removed this require with the latest commit (and a couple of others).  Thanks for mentioning the irb tip.
Do we have some usage to the method below?
`var Collection = `!
@christianv passing the global window seems a little excessive. We might as well knock out the scope variable and treat window like the ominous global that it is.
s/submited_apps/submitted_apps
Please remove the space before the parentheses :-)
I see. *Thanks* for pointing this out. Will do the needed corrections and push a further commit for review.
Unless I'm mistaken, we should divide by `len(self._y)` (instead of `len(self._classes)`), which will give us the proportion of points in each class.
good to have a link here to the GMM documentation :v:
`at` should be `as`?
Same remark as before for `alpha`.
An `<a href="#">` should be a `<button>` for a better semantic.
Makes handler member
You could have here !ifs, which will check the bad & fail bits.
d''identification
This needs to be in the context for the user's repo list.
Seems to be. Where are you looking that makes you think otherwise?
Can't you just do `self.fields['product'].choices = products` ?
Well to be fair PHP supports both double and single quotes :P fixed anyway, I am just habituated to single quotes.
If I change the other occurences of package_names to common_package_name, this seems to work brilliantly. Thanks!
хм. ну назвіть його просто user
Will this package still work with 0.8.9?
Not within this patch. But it will be a follow up work for the already filed issue 48.
We do not put comments like this into the code, because they easily get out of sync with the update the code. For SDK, cleanness is important. If you really want to comment, you can put them in the description of the method.
cleaned_data is django forms magic, all django forms return a cleaned_data dictionary after validation
not sure I see how to do this, the logic doesn't fit the pattern very well, to my eyes
Just for consistency I added empty param objects to the value_dicts that are affected. I think it's a little more future-proof this way.
no () needed
Same comment as above about static methods. Applies throughout.
You shouldn't create functions instead of other functions without good reason.  It looks like `combineTwo` should be moved outside of `combine` and be a local function instead.  Also, `combineTwo` is a bad name and should be changed to something more descriptive.
These are actually not basic types and will be instances of DynamicProperty (or other dynamic properties similar to it).  So this code is "safe".  I just wrote issue #89 so that we address the entire code-base sometime soon.
虽然只是个小问题……逗号后面忘记空格了
I have added a note to the Jira ticket that explains some of the likely behavior.
Spacing is off for braces
Correct, textContent is the DOM3 method, text isn't in any DOM spec.
Can we use single quotes instead of double quotes so we stay consistent with the rest of the file?
don't user setters
I'm not sure about this "current" variable, it seems unnecessary. It's only ever used inside the if statement to assign to cumulative anyway, so you should put it there if you keep it at all.
Ok, totally pedantic, but can you capitalize "using"?
This doesn't look like it's used anywhere?
I'm nitpicking, but I don't really like to set a value to null, and then null check it on the next line.
How about:

```scala
if (v == null) {
  None
} else {
  val value= v.trim
  if (value.isEmpty)
    None
  else
    Some(value)
}
```
Yes please - we don't care for allegiance to SESE. Thanks.
Please add explanatory text with static assert.
Shouldn't we have them figure out the corresponding eigenvector? That's half of the problem.
I normally prefer ' over " just because it looks shorter :) and we use it more often. But I agree, the preference is not important, but I think it reads better to use one or the other consistently across a file (unless there is a nesting of the other quote within it).

True that " within """  is not a problem, it unfortunately is not handled correctly by the syntax highlighting in github, so it is easier to read the code here if we alternate them.
supprime ->assert à cette ligne et la suivante

essaye de garder la même façon d'écrire des tests que dans le reste de la doc, s'il te plait :)
Thanks, I was not aware.  Changed this back to a string.
XLinkUrlBlueprint
Yeah. Patch ideas?
:(.. just installed vim-flake8.. so the code will be pep8ified :)
Make sure that none of the things you added in your branch are getting clobbered in the merge here. I'd expect to see no SB changes in this request, as only the non-SB stuff changed in the Dev branch
Would it be sensible to define a config key for this resource path, so that someone can override it with a custom config template file?
@_current_page || 1
Эти поля добавляются методом ``t.timestamps`` и будут называться ``updated_at`` и `created_at` -- это стандартный Rails Way
Please add a doc comment like was suggested, ``array<string>``.
Verwende:
return $this->grade == null;
`Result.getDuration()` is currently in nanoseconds. I'm not sure what the JUnit report contract is, but I assume millis.

What do you think - should I rename this to `getDurationNanos()` ? That would make it more obvious that people who want millis (you?) have to divide by 1000000.
or maybe just `add_tags`, or even just `add`
Can we combine some of these lines in a separate function to avoid code duplication?
Can we add the source for this file?

From irc it seems to be http://stackoverflow.com/questions/3233991/jquery-watch-div
We should use `sakai.api.Util.hideOnClickOut` for this
why is this in the `shift` method instead of the main if/then switch? `shift` should only check if there's an argument that follows, nothing more.
But it's inferred?
So it does :(
Hardcoded versions ;-)
Change no longer needed?
Here it's easy to see how +1 row and +1 indentation changes a lot of rows in diff. Too bad, the change seems clear. Thanks!
+1 to a mibbit link
You need to update the file resource in tftp.pp to use tftp_dirs instead of tftp_dir
I think you want to start all these URLs just with ``//`` (same goes for html5shim). This way they work with http and https equally.
Sorry I forgot to remove that code starting from line 99 to 101.
Small note: please do not do multiple assignments on one line; I was looking really hard where the $this->tags[] call went :)
(please correct me if this is done for performance)
Cool. We could have both controllers though. One for the provider and one for the API, so some clients could benefit from this endpoint (like: http://doorkeeper-sinatra.herokuapp.com/)
‌‽
Exactly, the test 'Query\\QuerySql2OperationsTest::testQueryJoin' and 'Query\\QuerySql2OperationsTest::testQueryJoinReference' are failing if I unskipp them. 

I just opened an issue about it: https://github.com/jackalope/jackalope-doctrine-dbal/issues/15

Should I still remove both failing tests from this file?
Is done now in my new commit
the status is necessary, it says info abou the file that was dragged and dropped in. keep one of them, but its up to you which one...
I think that for readability purposes, I would prefer if decomposition could be expanded in the code, i.e. written `v, U, UT_y`
There are already so many parameters... do you have specific use case where one strategy is better than the other?
inja ham hamoon kari k goftin ro kardam vali vaghti az rooye yek li b li kenari mirim img rotate nemishe . hatman bayad az biroon har li brim roosh ta bcharkhe vali ghablan dorost kar mikard ..alan chikar konam k moshkelesh hal she ??????
awesome, please update this PR and let me know so I can merge it
Why did you change the quote type?
don't need that `´` in there.
why doesnt this use our simple smalltalk test harness?
You can update it by pushing to your fix_namespace branch.
When you call stopLoading(true), Mobile Web's WebView will destroy the inner <iframe>. The WebView itself is NOT destroyed. It still occupies the same layout space. It still can be reloaded or pointed to a different URL. Make sense?
IOS currently does not have a hide method. It will be available once PR #1454 is merged. Perhaps this PR should wait till 1454 is accepted.
please remove the extra space between the method name and the brace
I think it should be:
```php
return substr($queryString, 0, strlen($queryString) - strlen($separator));
```
`innrHTML` + регексы быстрее, чем `innerText`.
This test does the exact same thing as the test above. Accidental copy?
Hmm, I agree it would be good to keep conventions, but I think it's more readable this way, since there are other publsih remote functions. Moving it doesn't really get rid of the dependency since we need to "initialize" this method for the entire application anyways. We would have to do the init from the controller anyhow.
you should never be modifying protected or private properties directly from outside the class, inherited or not, why is this needed? add public getters/setters or some utility functions to handle this
Interface with no comment on the method?!?!?!?
Since we _always_ need `og:image` we shouldn't include it in a conditional block.
Instead of repeating the same line three times, let's break it out of all the conditional stuff.
这里的font-face声明可不可以省略呢，因为已经在style.css中声明过一次了
Je trouve plus naturel de dire "deux façons principales" que "deux principales façons". 
Un peu comme dire "problème suivant" est plus naturel que "suivant problème".