labofsahil/github-event-dataset-2012 huggingface dataset:
I see what you mean. 

Well, I have some points (electromagnetic simulation data) that with a little zoom are in the order of femto  (and zooming-in is an important feature for our application), so might be a good idea to keep them. Also, since we work with small scale data, adding zetta and yotta wouldn't be necessary.

On the other hand, from the point of view of consistency, yes. If we add zepto and yocto, might be a good idea to add them too. New pull-request?
is this the right name (and place) for this function? it seems to have some arbitrary logic that couples open/closed with whether you care about the start date and end date. might be better bundled into the view access if that's the only place it makes sense.
Actually this file should not be part of this pull request. I'll remove it.
Well, if we want to test XML, we definitely should!
@mikesherov I think we can remove the `--no-commit` since --squash will not commit directly anyway.
http://linux.die.net/man/1/git-merge

`--squash`:
> Produce the working tree and index state as if a real merge happened (except for the merge information), **but do not actually make a commit** or move the HEAD, nor record $GIT_DIR/MERGE_HEAD to cause the next git commit command to create a merge commit. This allows you to create a single commit on top of the current branch whose effect is the same as merging another branch (or more in case of an octopus).
You can create a new set of test cases instead of removing existing ones.
Setting `MF_NO_TRANSLATE` because I didn't find instructions regarding adding a new translation item.
Remove dead code, unless there's a good reason to leave in?
Yes and no respectively. Database ENGINE has to be defined even if it is not used.
Empty line between CSS blocks.
Do I put 
pip install svn+http://code.djangoproject.com/svn/django/trunk/#egg=django
in requirements.txt file? I'm not sure how to do this.
https://bugzilla.mozilla.org/show_bug.cgi?id=745011#c8 seems to say this should be `ru_confirmation_email_2`
This should definitely be removed
And hm, maybe have clean re-create the DIST_DIR as well?
height = math.min( minHeightPix, height );
Make sure you cache this value somewhere in this file. This function needs to run as fast as possible. You can probably store this when `update` happens.
Does this mean 'large'?
So, this slugifies the tag names, right? It causes me a bit of trouble because it changes the URLs for each tag's page. Could you make it an option? You can even make it active by default, but I need to be able to disable it.
Codenames are cute, but I'm not particularly fond of them.
Perhaps creating a more specific ConfigurationException here so in this case it can be logged as INFO?
这里的显示不对。另外，中文请用全角字符。
```js
return base64
    .replace(...)
    .replace(...)
    .replace(...);
```
bebin in too ie 8 kar mikone ?
yani niyaz be oon mode -ms-filter nist ?
It's my bad. I tried to contact the project author to check if he forgot to push version tag, and will update the this podspec later.
fyi: https://github.com/nicklockwood/WebContentView/issues/1
Maybe change to "is an error object (instance of Error)` to be more clear.
Actually, this is bad and not needed the way I ended up implementing the assignment on L60. Consider it removed.
Some tests needs a bit more that that start but I guess each test can do that itself. This is much better than our old appready hack.
`deleteButton`
I also think some of this stuff is valuable as a summary for using conesearch, but other stuff is more advanced (particularly the stuff on using different databases and looking at their properties) and probably should be moved into its own section.  Plus, I think the database management stuff will probably be the same for all of the services we implement (not just conesearch) and probably should be documented in `vos_catalog.py` and not here.
``Time`` has not yet been imported.
好吧。。。我理解在这里合并是可以解决掉adid重复出现两个结果里面的问题，但是这事情真心觉得应该外面考虑，在searchResult自己支持，还是觉得比较怪异。 因为理解这个方法为什么这样要绕个弯，而且没有注释，用的人可能不小心会掉坑。
To be clear, are you suggesting we don't even have a start rate (eg. 16), but just continue to re-send the message each iteration if the list is non-empty? I'm somewhat partial to the temporal aspect of a tick-based approach, as it throttles starts overtime. Which is useful if we eventually move all vnodes (even primaries) to a rolling start model. How about going with your suggestion, but having a something like `vnode_start_tokens` that is set to 16 or whatever on management ticks, decremented each forced vnode start, and stops sending the continuation message when there are zero tokens. Until next tick, that is.
this should probably called `_is_valid_remote_url` (unless you want it as part of the public interface for some reason)
vRecvMsg.last();
How so? Indentation is 4 spaces...
Space missing after comma `,`
Reminder - to be moved to test asset instead of mock, since this creeps the hell out of @beberlei  :P
All tests in one file is not a good solution here.
Separate test classes for each resolution unit will replace these comments just fine.
Have to revert this
OK, that was a bit misleading. Let me try again: If the collection has rel="dcterms:hasPart" and rev="dcterms:partOf", then hasPart will be sent with the collection's parent and contain a list of child IDs (gathered from the DOM). partOf will be sent with the collection's children and contains the ID of the collection's parent entity.
Hitting a URL is simple enough. Think of it as a webhook and don't build any functionality in. It is only an event notice.
Why comment out?
On Android and other platforms with different DPI, there are good reasons that I have these three different sizes. Need to write a big comment about it though I guess...
`function (name) {` here and below...
I really like your usage of these events here.  Nice!
my mistake
Thanks & Regards
Sankaranarayanan .E


On Mon, Sep 24, 2012 at 10:36 PM, Steve Klabnik <notifications@github.com>wrote:

> In lib/draper/view_context.rb:
>
> > @@ -1,3 +1,4 @@
> > +require 'pry'
>
> I don't want to include pry here.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/jcasimir/draper/pull/281/files#r1675202>.
>
>
Duplicated call to StringBuilder.toString.
I'm not following... You've defined `struct addrinfo` before, why don't you use it here?
Was this meant to be a bitfield too?
Hm, why can't the newsletter form POST to a specific view that just processes newsletter signups?
Yes, that's the cool part.
The name and docstring here are backwards - it's actually the prefix from cv1's case and the id from cv2's case. It'd be better to reword the name and docstring anyway so they reflect the general concept (prefix from one case, id from another) rather than specifically mentioning cv1 and cv2, since without looking at this code you wouldn't know what those are anyway.
may be "elements" not to change to many things in this PR
@stof thanks for the tip. @bschussek suggest to implement a class, but this is easier.
I don't remember now as to why this was needed. Can revert back for the time being.
Plugins do not contain any Gemfile, it is in the main package (webyast-base).

Actually the require is not needed (because of Rails autoloading).
文件最后不应有空行
Isn't this making dy equal in length to dx?
Rummaging around in the can of worms a little more...

Page 15 of the WMS 1.1.1 spec (http://portal.opengeospatial.org/files/?artifact_id=1081&version=1&format=pdf) states:

> When the SRS parameter specifies a Geographic Coordinate Reference System, e.g.,
"EPSG:4326", the returned image is implicitly projected using a pseudo-Plate Carrée
projection that plots Longitude along the X-axis and Latitude along the Y-axis.

So... if this method was called `as_wms_srs` then you *could* justify EPSG:4326 as the return value (when the `central_longitude` is zero).
I have tried that, but the panel pane checks if the string in empty, so I have to return an non-empty string.
In case we end the "links" loop without returning, we should return None so that we don't keep looping over all nodes, like proposed for minitoring-virt
There are two problems with this solution: 
Not catching any file errors (and possibly leaving the handle open), and opening and writing to the file even though we don't want to change the content.
A much better solution is [os.utime](http://docs.python.org/library/os.html#os.utime):

```python
with file(filename, 'a'):
        os.utime(filename, times)
```
There are two randomizations: on this line, and on line the next line. That's one too many...
No need to override this method, it's already in the parent class.
Do not reject the JIRA. Whether stack traces get pruned or not (in this particular case I find them to be of little value), the JIRA shows a general problem that we need to improve upon. The temptation to suppress ERROR logging from org.apache.coyote shows that there's a problem beyond how the AS code itself handles this.

See also https://issues.jboss.org/browse/JBWEB-232.
The ServiceController needs to be added to the passed in "controllers" set, as is done with dataSourceServiceBuilder.

Also, the handler for the "remove" op will need to remove this service.
I'm happy to help and get involved, just trying to understand more.
Ah, no I see what you're saying now @kabir . This could break in Windows. I'll test with just removing it as it wasn't there to begin with.
job>run.
The version has to stay 1.2.0-SNAPSHOT.
Oops! Fix in the next PR.
The new dialog is for this kind of things

http://imageshack.us/a/img254/5479/addtohomescreen.png
No need for bind.
could this be move to the `handleFirstIncomingCall` function?
Its a display problem I think, those will not be available until the view is actually displayed...
if fileNameExtension is "mp3", then fileType will become "audio/mp3".
That's a incorrect MIME type, it should be "audio/mpeg".
For the other audio mime types, maybe you cannot just put it after audio/.
you can reference to this link:
http://en.wikipedia.org/wiki/Mimetype
`typeToSkip` ?
My maybe wasn't clear enough.
`var length = items.length` is fine, but then `count` == `length`, so we do not need the `var count` I think.
yes, by spec
overrides width in day_view.css:105 which breaks conflict display!
To make it clear: if for some reason you want to have the default checkbox / radio button on some document (despite the fact it will very likely be too small), you can just use:
```html
<label for="myCheckbox"> foo </label>
<input id="myCheckbox" type="checkbox">
```

… and it won’t be targeted by this stylesheet. We don’t *need* this class, and we don’t *want* it. Trust me to always do what it takes to keep the number of arbitrary class names as low as possible. :-)
It can be either, but the MDN article I stole this from didn't use it, although the more popular MDN articles I just checked do use it, so I'll add it in.
@elia i have create a new pull request with better code formatting :-)
These 5 lines might look a bit cleaner (and might perform a bit better) as a list comprehension or using the "filter" builtin, but it's not a big deal.
Not following this block
line for debug? I think it could be removed here.
This still feels a bit repetitive. I'm sure there's a much nicer way to do this and I'm not sure it covers the various devices well enough. Perhaps we can have a catch up about this in the morning...
..successful exit statuses..
I was planning to use http://livedocs.dojotoolkit.org/build/buildSystem, this comes with dojo, and is very powerful. Just tell if you want me to prioritize of PoC
It's officially discouraged form, and, well, it's ugly. But most of all, we've already refactored chaplin code from standalone `@` to `this` in April, so for the consistency sake we should do it again..
seems that space is unneseaary here
Oh I see...  Yeah I can see that now, the budget stuff is part of what I scrapped because again, the cost per instance data was outdated and this wasn't easy to maintain... that without taking into account that instance costs vary from region to region and then new instances are created all the time... plus that's not the only thing you get charged for these days, i.e. EBS transfers and etc etc etc.... I think the summary of my changes would be "Change EC2VMManager from a budget resource manager to an AWS connection manager".
pushed to not-approved
the old version patched `Grit::GitRuby::Internal::RawObject`, this is the Raw object of Grit. 

'Raw' means  'commit, blob, diff, etc.'

But the new version of patch does not patch the `RawObject`.  just patched `Grit::(Blob Diff and Commit) Object`. 

This lines `def data...` , just patched `blob.data`. and others monkey patch patched diff and commit.

Grit Memory Max for big commits maybe caused by the old version of patch. because the old version does not care binary file.

The new one did on this commit efd9a71 .
why  `src: font-url` ?
I think we can actually do without these. I originally added the same for other outputs, but no runmode ever uses it.
There is an unhandled case here, whereby `outfile_dir` is actually not a valid path on the filesystem, and thus an OSError will be raised by `mkdir`. `os.makedirs` can do the recursive `mkdir -p` style creation, but I'm not sure we want that. I will defer to @fperez on what he thinks.

It may be wise to wrap a lot of these kinds of calls in a `try/except` that catches the OSError, writes the error message to stderr and calls `sys.exit()` with a non-zero error code, though I'm unsure where the best place is to catch such exceptions and recover from them -- probably higher on the stack than this.
Probably not but just to be on the safe side. `<pre>` allows HTML tags so anything that's not a tag but starts with `<` might confuse the parser.
At a minimum, the name of this test case should describe what is being tested.
Sure, just was trying to come up with a better name, no rush though.
I knew that operating on iterators was slower than regular array operations and your comment above irritated my curiosity so I tried following https://gist.github.com/2714933 as it turns out `.filter(...).forEach(...)` is indeed faster. That not to say I changed my mind, you still can go ahead with internal utility function & utility functions I suggested earlier can be added in a future. 


```js
Fixed in 77441f1
Ah wait. I reverted some of my changes I had before. So yes, you are right.
Also please add brackets for single statements within an if/else/for section.
Please remove the section tags in order list.
Same concern as above, the block passed to setcode should refresh it's data from the system instead of using previously cached data.
I don't disagree with this, but would prefer not to alter this behavior relative to the previous/existing behavior as part of this changeset... I'll file a ticket about revisiting the config file reloading in general.
Use SemVer and `if ... >= 0.6.7`
Remove implements clause
a constructor returns an object. Remove this @return
The main idea of jQuery is that [about] every action returns self as its result, so you can effectively chain your actions:
container.html(...).attr(...)
I didn't even realize there was a tuple with three items. Yeah, I'll change it back.
now we have two `.seperator`'s here
Why not just drop the equals variable and simply replace equals = false with
 
    
    kickInvalidUser(session);
    return
Great idea -- I like the sound of "bind-modules". Changing now...
Yeah, the other changes look great. I'll merge this in, and tweak that one thing.
Eli funkkarin tarkotuksena on populoida $_POST:sta kassalippaan täsmäytys luvut kassalipas kohtaiseen arrayhyn

$_post

 array(61) {
  ["rivipointer1"]=>
  string(0) ""
  ["tyyppi_pohjakassa1"]=>
  string(11) "Kassalipas2"
  ["pohjakassa1"]=>
  string(1) "1"
  ["maksutapa1"]=>
  string(25) "kateinen#1905#Kassalipas2"
  ["solu1"]=>
  string(1) "2"
  ["solu11"]=>
  string(1) "3"
  ["solu111"]=>
  string(1) "4"
  ["erotus1"]=>
  string(2) "38"
  ["soluerotus1"]=>
  string(6) "-29.00"
  ["kateisotto1"]=>
  string(1) "5"
  ["kateisotto11"]=>
  string(1) "6"
  ["kateisotto111"]=>
  string(1) "7"
  ["kateistilitys1"]=>
  string(1) "8"
  ["kateistilitys11"]=>
  string(1) "9"
  ["kateistilitys111"]=>
  string(2) "10"
  ["yht_lopkas1"]=>
  string(3) "-35"
  ["rivipointer2"]=>
  string(0) ""
  ["tyyppi_pohjakassa2"]=>
  string(11) "Kassalipas7"
  ["pohjakassa2"]=>
  string(2) "11"
  ["maksutapa2"]=>
  string(25) "kateinen#1905#Kassalipas7"
  ["solu2"]=>
  string(2) "12"
  ["solu22"]=>
  string(2) "13"
  ["solu222"]=>
  string(2) "14"
  ["kateisotto2"]=>
  string(2) "15"
  ["kateisotto22"]=>
  string(2) "16"
  ["kateisotto222"]=>
  string(2) "17"
  ["kateistilitys2"]=>
  string(2) "18"
  ["kateistilitys22"]=>
  string(2) "19"
  ["kateistilitys222"]=>
  string(2) "20"
  ["yht_lopkas2"]=>
  string(3) "-55"
  ["erotus2"]=>
  string(2) "84"
  ["soluerotus2"]=>
  string(6) "-45.00"
  ["loppukassa2"]=>
  string(6) "-90.00"
}


 $kassalippaat

array(2) {
  ["Kassalipas2"]=>
  array(16) {
    ["rivipointer"]=>
    string(0) ""
    ["tyyppi_pohjakassa"]=>
    string(11) "Kassalipas2"
    ["pohjakassa"]=>
    string(1) "1"
    ["maksutapa"]=>
    string(25) "kateinen#1905#Kassalipas2"
    ["solu1"]=>
    string(1) "2"
    ["solu2"]=>
    string(1) "3"
    ["solu3"]=>
    string(1) "4"
    ["erotus"]=>
    string(2) "38"
    ["soluerotus"]=>
    string(6) "-29.00"
    ["kateisotto1"]=>
    string(1) "5"
    ["kateisotto2"]=>
    string(1) "6"
    ["kateisotto3"]=>
    string(1) "7"
    ["kateistilitys1"]=>
    string(1) "8"
    ["kateistilitys2"]=>
    string(1) "9"
    ["kateistilitys3"]=>
    string(2) "10"
    ["yht_lopkas"]=>
    string(3) "-35"
  }
  ["Kassalipas7"]=>
  array(17) {
    ["rivipointer"]=>
    string(0) ""
    ["tyyppi_pohjakassa"]=>
    string(11) "Kassalipas7"
    ["pohjakassa"]=>
    string(2) "11"
    ["maksutapa"]=>
    string(25) "kateinen#1905#Kassalipas7"
    ["solu1"]=>
    string(2) "12"
    ["solu2"]=>
    string(2) "13"
    ["solu3"]=>
    string(2) "14"
    ["kateisotto1"]=>
    string(2) "15"
    ["kateisotto2"]=>
    string(2) "16"
    ["kateisotto3"]=>
    string(2) "17"
    ["kateistilitys1"]=>
    string(2) "18"
    ["kateistilitys2"]=>
    string(2) "19"
    ["kateistilitys3"]=>
    string(2) "20"
    ["yht_lopkas"]=>
    string(3) "-55"
    ["erotus"]=>
    string(2) "84"
    ["soluerotus"]=>
    string(6) "-45.00"
    ["loppukassa"]=>
    string(6) "-90.00"
  }
}

	 */
why ? I'm on windows, but all my code uses ``\n``, not ``\r\n``. Commiting different line-endings according to the platform leads to a mess in the project.
Btw, PSR-2 tells to use ``\n`` for newlines, and the PHP-CS-Fixer will enforce it (and my git config will enforce it too by converting them before commiting).
Why did you add both versions instead of only latest?
With the prefixing, and certainly with the encoding of class names, wer'e violating (http://www.python.org/dev/peps/pep-0008/#class-names)[the PEP008 class naming rule].
But, since we have a good technical reason for that, that's OK (we just need to document our motivation).

However, I think I prefer the change the prefix to `EB_` (I don't think we discussed upper vs lowercase prefixes?).

Having class names start with a capital letter makes more sense to me.

Your thoughts?
No spaces before and after the list comprehension data afaik
block below basically duplicates code above

should use a double for loop instead, with outer loop iterating over a list of tuples: `[('bin', ['bcftools/vcfutils.pl', ...]), ('lib', ['libbam.a'])]`
Should remove the argument as not all backends require IDs. And it breaks the AmazonSQSTest.
Do we need to remove them? We could just leave them offline with no jobs running against them...
Less code duplication -> Less chance missing something when changing fetch() or address handling.
Tiny, tiny thing: as we're moving closer to having translations, would you have time to edit this string to be surrounded by the translation function? That's the ts() that you might have noticed around other strings. *g* <3!
Added some helpful desc lines -- also changed filename to the more standard `Rakefile`
Typo :) "accelerometer"
For now I have fixed 1 channel in the type. I am not really sure of what we want here: if you have multiple channels then you don't necessarily want to have them all filtered. What's the policy?
Емм, щось завтикав. upload_root переіменувати в web_root
А upload_dir використовується для побудови публічного шляху (URL).

Що скажеш?
OK returning just domain_ids, for more info there is domain API available.
I see your point.
Will have to dig more in order to know whether it is a security issue.
Anyway, have two technical questions about the proposed solution:
1. I saw that files under the bundler.d directory, contain groups. Is a jsonp.rb file containing:
group :jsonp do
  gem 'rack-jsonp', :require => 'rack/jsonp'
end

okay here?
Where/When is this group taken into account?

2. In the current implementation, I added "require 'rack/jsonp'" to the config/application.rb file.
If I understood you correctly, I need to add an option such as ":support_jsonp: false" to the config.
a. Should I add it only to config/settings.yaml.example (as example for the user), and take it into account in the config/application.rb ?
b. Currently, in config/application.rb, I use "require 'rack/jsonp'". How can I make it a conditional require, to only require it in case the flag is on? (can I do a "conditional require"?).
For the index method, the instance variable is @environments (plural)
For the show, edit, update, delete methods, the instance variable is @environment (singular)
I just added a comment above in the show method to document that @environment is returned by the find_resource method in the before_filter callback which is defined in base_controller.  The instance variable is defined on line 102.

        return instance_variable_set(:"@#{resource_name}", resource)

Why do you suggest that this fits in the view?
single quotes for these
Yes we can. It is a new staff for me, I will have a look at the document process
Is there a reason you create an extra variable for this?
This eq is temp. When we have a correct value to compare, i chaged it (name for exemple)
Maybe use ``(*args, **kwargs)`` here so the args are always in sync with the `Injector` constructor. If not, please do remove spaces surrounding ``=``.
I just visited Gatherer, viewed a card, and ran this in Chrome's console:

```javascript
document.getElementById('aspnetForm').action
// "http://gatherer.wizards.com/Pages/Card/Details.aspx?multiverseid=222911"
```

So this should work, though I haven't verified that it does:

```javascript
jQuery('#aspnetForm')[0].action
```
We should check if the file exists first as they may or may not have `.json` in their path name, some people just use `index.json_builder`. It should also raise an error much like partials do right now if there is a missing template.
Especially since pulling up the real ezdb classes can not be done without them connecting to the db / doing extra stuff (there are other issues in wit about that)
see documentControllerAlias for configuration
just checked out the branch and changed this test to something more specific than this but it fails

```
      some_survey.update_attributes :title => "new title 1", :current_page => 1
      some_survey.update_attributes :title => "new title 2", :current_page => 2
      some_survey.update_attributes :title => "new title 3"
      some_survey.last_change_of("current_page").should == [1, 2]
```

```
     Failure/Error: some_survey.last_change_of("current_page").should == [1, 2]
       expected: [1, 2]
            got: [nil, 2] (using ==)
       Diff:
       @@ -1,2 +1,2 @@
       -[1, 2]
       +[nil, 2]
```

thoughts?
independent of the concrete implementation: what would be the case you want a sort on an empty array to fail?
there may be a check needed but not in a order/sort method. it will be never critical anyway.
Should this be `(is (not (authorized? ...)))`? Is there a reason authorized? must return nil and not false?
This function is really hard to read. It feels like using objects instead of arrays would help make it simpler.
The \# is normally used to denote an actual function, so I don't think we really need that here.

Unless it translates to an actual anchor on the coverage UI?
There is already a wrapping of the JDI model inside the Scala debugger (`ScalaDebugElement` and subtypes), but it was less fun to add the method there than creating implicits and playing with Manifests :smiley: 
I will move most of the code to it.
All the doc references to lookup should be fetch to match the code.
Instead of doing the comparison here, use the existing lang_code_get routine, that will do the conversion from either -1, -2t or -2b to the internal format.

Then simple compare that directly to the configuration. If you wan to save the lookup, then simply put a comparator routine in the lang_codes stuff.
Well... I understand but I thought it was a "good" way to test exceptions and to have 100% code coverage. But I agree, it makes code less readable :/
Check this concatenation, it is wrong...
'prevent_update' column doesn't exist in the current session DB schema. This has caused some problems if using DB-enabled sessions. Please verify.
Don't have any position on this.

You think integer would be better ?
Допустим, что на вход mutate принимается количество ячеек (хотя самая очевидная реализация предусматривает, что на выход подается процент мутаций, и комментарий в этом месте позволил бы избежать недопонимания). Также допустим, что в нашем массиве DNA 500 элементов, а hammingDistance, подающийся на вход mutate, равен 200. Тогда получается, что percent = 200 * (500 / 100) = 1000, что никак не может являться ПРОЦЕНТОМ замены.
Можно было бы написать это цикл нипример как: for (int i = 0; i < _dna.count; i++) {, и тогда метод стал бы более универсальным)
Это должно быть в if-е ниже. Зачем что-то делать, если обьекту не удалось создаться?
Лучше уж при наличии DNA_LENGTH именно её и передавать для инициализации массива.
I tried to run this script again and ``build_mac.sh`` was missing because since I got switched back to master. Maybe not for this pull request, but later it would be nice to pass in an option to stay with the current HEAD instead of always switching to master.
Not anymore since Vengeance was removed.
The 1E-300 term is a cheap way to enforce 0log0 = 0 instead of NaN.
These tests are seriously cray. Surely there's a clearer way to write them.
I'd write a test using test_raw.py and make a layout saves it and reloads it?
nevermind forget it
Use "@verbose" and replace print statements with logger in function body
np.int

instead of int64
I think info should always be a dict and empty if tags are absent. Less branching.
I would say "makes the solution reproducible" instead of "helps.."
You did not defined twig in this section.
And twig is not present in `composer.json`

Is translattion really coupled to twig ?
存储的内存
限制域的存储空间
This is still true if you want django support.
И здесь не `const auto&`?
Сделай, пожалуйста, предупреждение, типа, вы действительно хотите пометить все как прочитанное?
А то захочет чувак фид добавить, дернется у него рука, и все, пизда непрочитанному. FFFFFFFFFFFUUUU
Локальные переменные и параметры с маленькой буквы.
Creo que la clause Assembly tiene un método estático que te deja acceder al current assembly.
Why are you explicitly returning nil here?
According to the documentation, `createScaledBitmap` cannot throw an exception anyway.
This is needed so that web_py could load smart_client, for example. I have no idea why it wouldn't work without this, but I like how these two lines of code resolve the issue without any need to mess around with external configuration.
inheritance? can then make namespace `Payments` ? to be able to `class ChargesController < Payments::ChargesController`
the return of the time function only happens one time when the module gets required.
so after `require('Stopwatch.js')` it's either `Stopwatch.prototype._getTime = Date.now` or `Stopwatch.prototype._getTime = function() { var hrtime..... }` depending if process.hrtime is available or not.
Good question. Haven't actually tested posting really. Will test in a sec
@Sanne ok, I'll change the way we store the entries. From an insert() to an update() with insertion if it does exist.
On Friday, October 5, 2012, Damon McDougall wrote:

> In lib/matplotlib/cbook.py:
>
> > @@ -1583,9 +1674,10 @@ def isvector(X):
> >      # deprecated from cbook in 0.98.4
> >      warnings.warn('isvector has been moved to matplotlib.mlab -- please import it from there', DeprecationWarning)
> >      import matplotlib.mlab as mlab
> > -    return mlab.isvector( x, y, xi, extrap=extrap )
> > +    return mlab.isvector(x, y, xi, extrap=extrap)
>
> I am a new core developer, so I'm really not the best person to ask here.
> One of the other developers probably has more insight. I defer to @efiring<https://github.com/efiring>,
> @mdboom <https://github.com/mdboom> or @WeatherGod<https://github.com/WeatherGod>
> .
>
>
> Keep this a pure pep8 PR. Have a separate PR to completely remove this for
1.2. Maybe add a note to api_changes.rst.

>
Need spaces around mathematical operators
style nit -- use <code>signatures</code> instead of <code>sigs</code>.
you can try to insert something before this line:
import pdb; pdb.set_trace()
It will trigger a python prompt for you to debug.
And you can try to do:
> print output_text
> print self._test_string
or anything you want to see in the python prompt

In this case, you can see if your result is right or do some other tests you need.
Needs explicit parameter name in call. Well, in every related calls.

In this case, it will pass ``stats`` parameter instead.
why what? :O
I removed it. Wasn't necessary anymore
Yes, because we don't want to share the description objects among processes. We send a modified description object to the Execute format, and we do not want other processes to pick up the inputs this way. Another option would be to create deep clones of the description, but I found it more convenient to just store the raw description.
Well, I'm actually wondering if `unpack-feature-vec` is needed. Like, what about just mapping `unpack` over the sequence?

```clojure
(map thrift/unpack seq)
```

Maybe?
Let's not comment these out, I can't imagine they're causing problems -- if anything, you need to either upgrade to leiningen2 or change lein-midje to 1.0.8.
Do you want to update the pull request or leave it for me to change later this weekend?
We can absolutely spin up EC2 instances to update the sizes. That can be done async after this change is merged in.
I am pretty certain that you don't want that.
please call base constructor
I measured Felipe's design and that's how big the dropzone was. It would probably do no harm to make it 410px, but I usually just use whatever the designers have put in the design.
Minor: Why does this have to be an ID-based selector?
no output would be better it will be cron job
The same goes with the current exceptions in the generic filelib exception namespace. I don't like it. Exception refactoring is necessary.
Fair point. We should instead be modifying the function call to change the max length argument input instead of the default parameter here. If the function is receiving no input for that paramter, we should add it and remove this change to the signature line.
Yes I think a separate folder and copying them over would be the right way to do this. And yes I will try and debug that sql_escape problem later today, so you can properly continue your work.
`` catch (\Doctrine\Common\Persistence\Mapping\MappingException $e) {
    
}`` seems not to be reachable. Are you sure this is correct?
Are you sure ``$url`` has the correct type as ``*`` is not a sub-type of ``string``?
这里也是。
Changed comment to '//TODO remove this when Jira task TIMOB-9980 will be implemented'
This is actually not the case. The **master-prequel** task is only run when there are changes from upstream. Does that mean we can simplify things? Let me know if I can help.
I think "iterationModulus" is a better name for the "iterationOfChange" variable. That's also the term used in other dynamic implementations in cilib, if I recall correctly. Obviously this will have to change in the code too.
I think we should avoid adding this - it's easy enough to re-add during development, don't need to have it checked in.
Voi olla niin, että `pred` ei palauta boolean arvoja, vaan arvoja jotka vain tulkitaan boolean arvoiksi. Predikaatti `true?` palauttaa `true` kuitenkin vain ja ainoastaan arvolle `true`. Kaikki toimii kuitenkin kivasti jos annat predikaation `pred` suoraan `filter`:lle:
~~~clojure
(filter pred a-seq)
~~~
This will probably cause a check style problem just looking at it.
could you remove the space between `)` and `{` so it matches the code style?
See here: http://technology.customink.com/blog/2012/06/04/mvt-foodcritic-and-travis-ci/
Added a note in 2f57476.
This should be `all_warnings.select...`. Sorry for the terrible API :cry:
I tried that, but I had issues getting the value of "ip" (when successful) into the ensure block - it was coming up nil. I thought I'd handled the scope correctly, so I took it out. I'll try again with an instance variable tomorrow
I wanted to do that but notice that config is being passed at different nesting levels. I didn't know how to express this more concisely.
Damn it :D
A bug in our Tastypie implementation? Don't workaround. Fix (or at least make a test there which fails and I will fix it).
Why are you settings `widget` from outside and not through the constructor? Set it through the constructor, it is much cleaner (and it might be better handled, you never know if there is some special handling when passed through constructor which you are bypassing now).
Fixed. Why is GET better than POST in this example?
I provided you already with an [example](https://github.com/wlanslovenija/PiplMesh/blob/master/piplmesh/account/forms.py#L60).
Use the context as I described above.
(Maybe `node_location` is not good because we have location in node for something else.)
Whaaat? You are admitting to copy-pasting in front of my eyes? Be careful!!!
Yeah, this is an unfortunate bit of code right here. In one of the most annoying decisions of all time, Apple made setting the stringValue of a control to nil raise an exception. This was my preventative measure. The other option is to ensure that all keys have values (even just empty strings) in the model layer, which seems like a better idea, I'm just not sure where to take care of that.
I think it might be clearer and more direct to replace "This database" with "#{db[:name]}" or some other direct reference, especially if the info is already readily available.
there is no space between the username and "has"
Need to update the log message to reflect an actual error.
ok -- will change that
Change this back to ```private``` please.
-if (target && target->GetEntry() == NPC_CRYSTAL_SPIKE_INITIAL || target->GetEntry() == NPC_CRYSTAL_SPIKE_TRIGGER)
+if (target->GetEntry() == NPC_CRYSTAL_SPIKE_INITIAL || target->GetEntry() == NPC_CRYSTAL_SPIKE_TRIGGER)
Magic numbers!
The problem with your implementation is that it copies the references of the matches from the default priority group, instead of creating new match objects. As a side effect, if you change the score of a match in the default priority group, it would change the score in the other priority group too. This is not the behavior what we want.
What about ``HAVING``, ``LEFT JOIN``, ``RIGHT JOIN`` and ``INNER JOIN``  ?
prefix with `\`
Yup, I've missed that. Same goes for the } before catch statement. I'm fixing it.
Or use your favorite SFTP Client.
to make these exceptions really nice, see how the Infinispan module is using 
_log.unableToInitializeInfinispan( e )_

There is a significant benefit from using that: we're able to internationalize the error messsages! so it's particularly useful for cases like this, as people will do this mistake often.

You can add an extension of the org.hibernate.ogm.util.impl.Log interface in your mogodb module and add all messages you want.
> vectorial space of term occurrence statistics

gee, where did you dig this one out :-) cool. Is 'vectorial' a real word or is it 'vector based'?
This should probably use the exact snippet from the generated config file (i.e. with comments, etc.) instead of something similar.
I think the context should be passed through unconditionally. There's no way we can know how the function will be called at the time when it is defined.
So that things are clear: while I do not like the `shift`, my biggest problem is the double-`shift`.
I strongly suspect that readers of the code don't want to know that it is "automatic". They want to know how it works. If you do not want the comments I suggested in your previous pull request, please find something else that actually explains how it works, rather than telling readers that they should not care.
this looks like an off-by-one. you don't allocate enough room for the terminator and the next snprintf will succeed, but clip the last digit off the port.

Instead of printf'ing twice, why not just:

char hkeybuf[1024];
snprintf(hkeybuf, sizeof(hkeybuf), "%s:%d", ns, port);
hk = strdup(hkeybuf);
Yes, that would be better. I didn't believe that svetlyak40wt will merge my changes anytime soon.
Call it `HasAtmosphere` for consistency.
docstrings, I guess Skipper's type of docstring concatenation or templating would pay off in this module and not be too messy.
done above. also this.media now defaults to an empty object in toura.components._MediaPlayer instead of here
Pul all urls in the main urls file. We are not making independent Django applications and it is easier to maintain all in one place, I think.
This is probably not needed anymore, yes?
This feels hacky to me. Basically here I'm tracking how many filters are in the list that can be added. If there aren't any I won't show the drop down and add button to save some space. The other option would be to use a jquery select. I was trying to avoid that here for a performance gain but I wonder if it is much of one. Any ideas @robertkluin ?
If you think this is not a significant time sink compared to other parts of the code (like draw()), then probably best to leave it as is.  If it ever becomes a tall pole for optimization, we can address it then.
clarify: the random rotation, shear mag are *before* the convolution with the desired PSF.  (Right now comments go in the wrong order of operations.)  Also mention resampling to final pixel scale.  All this applies to the yaml, json scripts as well.
@JoeCianflone this will flag if the shipping fee needs to be calculated per item.
OK, thanks for opening the issue [#1561].
cleaner, thanks
I think we can improve a little bit the error message with "it appeared" :
 `"expecting:\n<%s>\n to appear only once in:\n<%s>\n but it appeared %s times"`
This was a mistake. Fixed now.
Yes. You can check the history who to blame :)
all operations, if they fail, leave the pool in an odd state, sadly, currently.  have added note.
excellent, great to deprecate special cases and stuff that allows fuzzy spec definitions.
??? again, qu'est ce que tu veux dire ?
Other then shipping Vagrant manifest that will provision the machines we expect these tests to execute on..
Most of our latests tests require very specific environment..
How about something like `ConfirmPin` or `CheckResult` here?
is |null| on purpose or do you want to return |false|?
As @Seldaek said in an topic, the handler isn't responsible to open the MongoDB Connection. In that case, do he need to be responsible to close it ?
From what I can tell, the opposite is true. Running apt-add-repository multiple times adds the deb lines to /etc/apt/sources.list repeatedly. The way the code currently works it only ever writes the deb lines to /etc/apt/sources.list.d/percona.list which would already be there on percona servers (and therefore simply overwritten on bootstrap) or created for mysql servers.
Do we really need to define `$options` here if we are just going to pass it into a method call and never use it again?
Are the ||= necessary here? I think that viewDidLoad is only called once.
Everything but this one line makes sense, but that may well be taking I too far. Just because PSR is talked about, does not mean EVERYTHING has to be in a namespace, especially when it is an example, potentially of only a fragment of a file.
Why are you setting the post_status as 'future' here?
В противном случае NullPointerException?
Вынеси запись в BufferedWriter строки в отдельный метод.
Пустую строку на вход StringBuilder совсем необязательно задавать.
Что это за магическая константа 4? Надо просто вычислять максимальную длину названия дня и отплясывать от неё.
Not sure how they all got there.
This is not used anywhere. We should remove it.
I get this error in my console:

```
Error in parsing value for 'background'.  Declaration dropped.
```

Is this property set correctly?
+1 for `valid_framework?`
@mblondel I don't think this is true. Only for performing checks maybe. The transform in ``predict `` is simply ``classes_[pred]``, The inverse transform is not so trivial but that is not needed here. This is one of the reasons I liked the the version without the ``LabelBinarizer``.
I agree with @agramfort that the user should rather have access using ``LDA.classes_``. So do we copy ``label_encoder_.classes_`` to ``LDA.classes_`` and keep the ``label_encoder``? Or destroy the ``label_encoder``? Or do we add an property?
Please have a look at the [diff](https://github.com/amueller/scikit-learn/commit/53c1126c80fa5093477a54cb9c2356389b81118c) to see what is looks like with and without ``label_encoder``.
2012/12/20 Noel Dawe <notifications@github.com>

> In doc/modules/ensemble.rst:
>
> > +
> > + * :ref:`example_ensemble_plot_adaboost_classification.py`
> > + * :ref:`example_ensemble_plot_adaboost_regression.py`
> > + * :ref:`example_ensemble_plot_adaboost_error.py`
> > +
> > +.. topic:: References
> > +
> > + .. [FS1995] Y. Freud, and R. Schapire, "A decision theoretic generalization of online learning and an application to boosting", 1997.
> > +
> > + .. [ZZRH2009] J. Zhu, H. Zou, S. Rosset, T. Hastie. "Multi-class AdaBoost", 2009.
> > +
> > + .. [D1997] H. Drucker. "Improving Regressor using Boosting Techniques", 1997.
> > +
> > + .. [HTF2009] T. Hastie, R. Tibshirani and J. Friedman, "Elements of Statistical Learning Ed. 2", Springer, 2009.
> > +
> > +
> >  .. _gradient_boosting:
> >
>
> Agreed. The reverse approach seems more reasonable.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/scikit-learn/scikit-learn/pull/522/files#r2474908>.
>
>

I'm +1 for a separate PR;

regarding the reverse approach: we might consider both; in some cases its
quite handy - and people coming from R's gbm expect similar functionality...

-- 
Peter Prettenhofer
fixed

@vene can you send me a PR on the store_path / return_path thing?
I'm quite busy in the next few days sorry
Because we want better user displayed labels than "Yes", "No" and "-----". I think that "Allow" and "Deny" are more precise.
What is `rt`?
This is why I've been trying to explicitly state patch versions in Publisher with `~>` when I can. Then running `bundle update` should update all your dependencies to the latest patch version without incrementing minor versions or major versions. Technically minor versions shouldn't break anything, but many projects (Rails, Faraday, etc.) are bad about that.

Basically we want our libraries to have as loose constraints as possible (like here, you can use any Rack ≥ 1.3 but < 2.0 and any Rails ≥ 3.1 but < 4.0) and our apps to have as tight constraints as possible (to make `bundle update` painless to get patch/security fixes).
Yes it does. If it is outside the function, the Id::property etc. bits aren't initialized yet and segfaults occur.
Need probably to have also derefencing operator *
Use new ruby hash sintax:       null: false
I use it currently from command line to drive the Nexus repository: close staging repository, drop it or promote it can be done from command line.

I still want to do it manually from commandline for now, and eventually attach it to some release phase when we feel confident about it.
Right. Sounds better.
Yeah, it would be nice if that before filter didn't get executed for every context in this spec file.
Whoops. Having CI setup will help catch these mistakes.
A lot of this stuff is due to the local cache... which is a dangerous thing in limpyd as i always said (and absolutely no thread safe)

So no problem to clean this later, let start a issue/discussion about this.
Extracting this into a helper method would improve readability.
``message`` a provided arg: https://github.com/RyanBalfanz/django-sendgrid/blob/develop/sendgrid/signals.py#L3
Does it also make sense to call .open() on the handle returned from .open() ?
The same "error" occurs in LinkColumn. I will change this too
s/mulitlpe/multiple/
my question is, dude, is why all the extra new lines?  Come on!
Is the indent off by one here?
Implement interface IDFUploadHistoryPage
As suggested, I had considered restricting what could be supplied to the `addOpenIDMixins` method. The reason I decided not to was because in addition to the mixins allowed by [node-openid](https://github.com/havard/node-openid/) for [storing association state](https://github.com/havard/node-openid/#storing-association-state), mixins can also be provided to [cache discovered information](https://github.com/havard/node-openid/#caching-discovered-information). It felt like adding restrictions might eventually become a maintenance headache (albeit a minor one). I also felt that anyone using this feature would be responsible enough not to pile in methods and data needlessly.

That said, if we wanted to be more restrictive, instead of having one generic method to pass mixins to [node-openid](https://github.com/havard/node-openid/) we could create something like...

```javascript
Strategy.prototype.useAssociationStorage(save, load) {
  (typeof save == 'function') && (openid.saveAssociation = save);
  (typeof load == 'function') && (openid.loadAssociation = load);
}
```

...and create another for caching. I think we start to run into the back into the maintenance headache this way though.
yes, it'd be good to know why this helps
http://docs.puppetlabs.com/guides/style_guide.html#quoting
"All strings that do not contain variables should be enclosed in single quotes.  Double quotes should be used when variable interpolation is required.  Quoting is optional when the string is an alphanumeric bare word and is not a resource title."

What about the third sentence?  Paraphrase: Quoting is not optional when the string is not an alphanumeric bare word (ie a variable) and is a resource title.

Please note that I am not trying to be a PITA.  I thought the Style Guide was pretty clear and that I understood it.  Either way, I can resubmit the pull request without the format "fixes".
General ruby parlance to instantiate a new array is

array = [] (two brackets)
Would be nice to keep a max line length "constant" int he description. No more than 100 columns please.
You can remove the star, it's not needed, as well as the \\IPC$. A simple 'net use \\targethost' will invoke the authentication
There is a typo, should be GetLoginScreen.uevent according to my testing ('x' out)
Are you sure this is correct? Because in my opinion this misses the fact that the 0th pixel is actially at position 0.5.

Also you could replace `h_out_grid.max()` with `h_out - 1` (same applies for w_out).
This should probably not be our standard reference text :)
I assume you're resetting the messages that you stubbed in the `before` block to their original values? In that case, this should reset `activerecord.errors.messages.too_short`, not `.too_long`.
should be `not_yet_ready` to be the same as in `Entity\Bundle`
yip looks alot better than mines, give me 1 min to update it
I suppose we need to do some validation to ensure we do not divide by zero.  Same comment for `getLevelMaximumGeometricError` below.
Yeah, I admit that I'm pretty lazy when it comes to adding examples, I'll add a few here though.