labofsahil/github-event-dataset-2012 huggingface dataset:
Ok I've been meaning to get around to it sooner, but I really need to add in proper comments. Late last night even I was having trouble understanding what I wrote. Next opportunity I get I'll add in some explanations
Can we get this upped to 1024?  Heap overflows if adding a few more items during final zip sign/creation.
Yes, when running python2.7. http://code.google.com/appengine/docs/python/python27/using27.html#Configuring_WSGI_Script_Handlers
I think that this should probably actually just try to delete (and return the not found if it doesn't exist).  You can rescue the error in your own code, but others may rely on this to know whether it existed or not (also, raising not found is more consistent with other providers).
What is an obscure way to reference hazard input? 
I believe the same approach that was used in the loss maps is being followed here.
Why do you use px instead of em?
I think I just forgot about that case.
Fixed in f501d62
This is to be used with the failure detectors. Do you think we should hide  
it? Optionally we can move them to something like remote.util and leave  
them public if people have the irresistible urge to use failure detectors.
/**
   * Should return the current number of messages held in this queue; may
   * always return 0 if no other value is available efficiently. Do not use
   * this for testing for presence of messages, use `hasMessages` instead.
   */
  def numberOfMessages: Int
this blows up toString and everything else; see comment above
I think you should have a separate CircuitBreakerHalfOpenException. perhaps extends CircuitBreakerOpenException
PR-675-merge: here you will remove lazy and the comment
Why is this version needed? (Also, it doesn't escape the given `actorPath` potentially creating invalid URIs.
If you feel uncertain about those fallback thingies you should take a look at this (closed) pull request, because similar is also in non-experimental RemoteRouterConfig.
https://github.com/akka/akka/pull/650/files

There I wrote test that fails without this.

ticket #2433
it looks like you have some auto line break setting that doesn't match our conventions, 120 char lines are ok
No need for extra braces
No other thing can arrive. This looks stupid now, but payload and control  
message deserialization will be split in two -- and then this match could  
go away. I need to change the protobuf though, and I do not want to touch  
it before you say OK to the overall architecture.
I wanted to ByteStringCompact next to ByteString1 and ByteStrings, to keep the three implementations together, and so that ByteStringCompact has access to things which are private[ByteString] (though currently, the critical stuff is all private[akka].
created ticket for that, since ensuring is an assert, https://www.assembla.com/spaces/akka/tickets/2798
step in the right direction, but we really need to fix this more deeply in the model somehow.  tricky one.
I think you could collapse these 4 lines into:

```
checksum_type = repo_scratchpad.get('checksum_type', DEFAULT_CHECKSUM)
```
Good catch.  I've added a NULL check around the for loop.
yup, that's the one :)
As a start, try making this a singleton instead of all static methods
Var väldigt osäker på hur jag skulle gör med just detta, för saken är den att jag innan jag ens hade funderat att forka svtget såg ett svtget phyton script som använde sig an en json parser.
Så då slog mig tanken att om man använder en html parser och en json parser så borde man kunna skriva ett mer robust script, vilket jag gjorde i ruby efter som jag kan det bättre än python.
När jag sedan forkade svtget för att föra till baka de ändringar av bash scriptet som jag gjort, kändes det rätt att också lägga upp mitt ruby script.
När jag bestämt mig för det, så gjorde jag några för ändringar av mitt script för att anpassa comando rads flaggor till vad som användes i Simons script så att en användare inte skulle känna sig helt vilse. På några ställen där det inte var någon funktionell skillnad valde jag att ta några rader frän Simons script för att behålla något av historiken.
Det enda funktionella som kommer från Simons script är raden som testar dependencies.
För övrigt är det bara saker som måste vara samma för att hålla interaktionen med användaren lika och de 5 sista raderna av scriptet.
Anledningen till att jag satte mig som author och skrev att jag blivit inspirerad av Simons script är att det inte kändes rätt att Simon ska behöva stå till svars för mina design beslut att använda htnl och json  parser, men ändå ge honom någon form av erkännande.
Men det spelar ingen egentlig roll för mig vem som står som original author, det bara kändes mer ärligt att sätta mig själv som det.
We're going to need to recalculate what `timeout` should be here (if it took time for the `cond.wait(timeout)` to complete).
`.join(', ')` here and above.
Actually, P is to see the physical path (as opposed to L with the logical path), but the default is P, so puting P is the same as not puting it if you don't use P (ie. P only exists to provide an "alternative" to L).

pwd does the same, but with the default being L.
Also rather in cvmfs_check than here
"when when"
All GNU projects use `LICENSE`, `INSTALL` and `README` to avoid prefix conflicts with code file names. Case-sensibility is a property of all Unixes.

Windows' issue was that it didn't have case sensibility at all. It capitalized the names because it looked pretty, that's all.
`static CGFloat const TUINavigationControllerAnimationDuration = 0.5f;` :panda_face:
Hah, you're right. Guess who wrote that code, then promptly forgot about it? :-)
s/Multi byte/Multibyte/
s/4bytes/4 bytes/
`String::NewSymbol("slice")`
Less is more. :thumbsup:
Why does this need to be a method returning a function, instead of just `def wrapRDD(rdd: RDD[T]): This`? Haven't looked into it much so maybe I'm missing something. If I am, then add a comment for it too.
Callbacku by možná slušela statická metoda. funkce <code>callback()</code> by pak byla jejím aliasem.
wrong coding standard
I used all lc due to additional functions in etc/openssl/openssl.c using all lc for warnings
Should take the minimum of ```v[1]*num_comps``` and 1.0 for the p-value.
переменную лучше именовать со строчной буквы
ну и тут тоже
Perhaps it could be a bit expanded, like:

```
The default inheritance column name is +type+, which means it's a reserved word inside Active Record. 
To be able to use single-table inheritance with another column name, or to use the column +type+ in 
your own model for something else, you can override this method to return a different name:

  def self.inheritance_column
    'inheritance_type
  end
```

Wdyt?
I'd rather not change this. I want the constructor to do *less* work.  We need to be more restrictive about how our objects are constructed.  Data should be scrubbed in the factory methods (`[]=` and `add`).
The docs are pretty good, but there's no mention of `instance` in `CustomClass::Deprecator`, this may confuse people. Perhaps you can just use `new` instead of `instance`, or add the method or singleton there to show how it'd look like?
Please squash your commits and remove this blank line, thanks!
<joke>  Can we but ZERO in a constant to avoid this magic number? </joke>
Perhaps as documentation:

`assert(same.lengthCompare(2) > 0, same)`
I think I'm with Philipp on this one. Though I don't feel too strongly about it. 

If we go with Philipp's suggestion, all I'd then do is update the docs to reflect what we actually catch (as well as this distinction between what users and library writers should catch) before this could be pulled in-- yay or nay?
Could this instead be spree/address/form? Would make more logical sense (at least, to me)
-> `Nlhs = sign(diff.n(1))`
Here there are also a couple of lines with spaces
The DCPU-16 is unsigned, so I think this only works because the assembler passes along the memory directly to the emulator. If it's dumped to a file, it will be parsed as unsigned and this will probably fail.
why have you added it then? :-) to push messages locks are not needed as Session is by design (with exceptions) thread-safe
I'm killing this section because it's documented in the $all operator page, and it's orthogonal in a page on indexes.
rewrite to avoid parentheticals
"In earlier versions"... can you be more specific?
this can be more clear, my fault.
The namespace url's in mindtouch seem to follow /<namespace>:<locale>/<Title> convention. e.g., https://developer.mozilla.org/Project:en/Existing_Content

E.g., Talk:en/Basic_Introduction_to_using_Color_Management is migrated to en-US/docs/en-US/Talk:en/Basic_Introduction_to_using_Color_Management but the redirect goes to http://developer-dev.mozilla.org/en-US/docs/en-US/Talk:Basic_Introduction_to_using_Color_Management (note it's missing Talk:en/)

Not sure if we should change the redirect logic, or change the migration script to remove the en/ bit.
I suspect this was more my playing and not cleaning up, I shall fix!
Setting this to false and checking === false would be better than using isset to check if it's equal to null I think.
I'm pretty sure that PATH_INFO does still exist when that is done locally, but I see your point.

It was agreed [on the RFC](https://area51.phpbb.com/phpBB/viewtopic.php?f=108&t=42731&start=10) that we would not use the type in the URL, but would instead use the Accept header.
Maybe it's just $_GET that doesn't error on isset() then. But yes, is_set_post() should be used.
I would prefer using a default value in `$action = ` above to using default.
Hello,

They are to-do items

Sincerely your's
Captain Obvious
Rather than nesting the conditionals:

``` ruby
if blah
else
  if other_blah
  else
  end
end
```

...what do you think about using `elsif`?

``` ruby
if blah
elsif other_blah
else
end
```

Seems like `elsif` is meant exactly for cases like these.
Duplicate. Just remove this file
Возможно разделить было правильным решением, но есть несколько проблем, которые появились после такого разделения, как у тебя. Во-первых, огромное количество одинакового кода(да, это критично). Во-вторых, если, например, соединение с базой продадет после получения баннеров, но до получения bindings. В этом случае у тебя нода прейдет в неконсистетное состояние и скорее всего упадет.
Это плохо - опять пытаешься обойти pdo, при этом делая запросы нечитаемыми. Лучше обновляй все поля, вставляя в ненужные null. Да, и лучше стараться чтобы строки были не такими длинными.
Thanks!
Fixed.
Can you clarify: Is 25 correct or 27?
Would be nice to test the indexing here.
把这个数据的编码转为utf8吧
把paper.set()用起来吧。
I believe that we solved the left/right normalization problem, so you should just return null (for now) if you don't have a TVE on the left.
In the future, there will be cases where there is no TVE on the left and taking the left expression as the end key will be seriously wrong.
Done. I will make a unit test for it.
again ?  :)
Здесь не копипаст из тестов про bem make?
this won't work most likely. how about 

```coffeescript
appPaths = @config.paths.app.join('|')
///^(#{appPaths})\////
```
Why `or`? Won't it be better to merge both hashes to one?
s/correl_model/cm/ in order to make the line < 79 chars?
This should use `uri.host` rather than `uri.hostname` (which is undefined).
Don't know how often this is called, but would it be worth it to just call jQuery.expr.filters.hidden( elem ) directly?
parentOffset belongs on the next line.
Apparently @n1mmy was just about to make a similar change. I'll let you know when that change gets in.
Moved up, to give more time for virus scanners to scan what's happening.
Please indent with spaces, not tabs (see https://github.com/meteor/meteor/wiki/Meteor-Style-Guide )
I like this idea. :metal:

Maybe we should additionally have explicit urls to each form making it easier for us to test them without having the exactly correct browser/form-factor/whatever.
Need a versioned download.
Watch the indentation here (2sp).
Speaking of which - can oiio not detect this on its own?
Same comment as above.

Also, this repetition should be extracted into something like the `extract_*` helpers commented on above.
Ok, in this case a :+1: from my side.
What additional information do you think we can add here?
Hmm inhaltlich mach die vererbung wenig sinn? Es macht ja keinen sinn die ganzen methoden die rex-path bereitstellt ueber rex-url aufzurufenn oder?
Why is this necessary rather than just looking at `user.name` later?
actually the implicit subject is not exactly `described_class.new`. I tried it but I guess since i override the `described_class` method it gets confused and tries to instantiate a `Virtus::ValueObject::InstanceMethods` object.
Instead of making `isPrevented` a closure variable, just make it a property on the event object.

`error =
  type: '404'
  isPrevented: false
  preventDefault: -> @isPrevented = true

Batman.currentApp?.fire 'error', error
return params if error.isPrevented`
I added "padding: 0 0 0 0;" to the ".codehint-menu" selector on line 281 to fix the extra padding issue.
Note that VERSION no longer seems to be used in any of the dialogs directly (it's only used within other strings, and gets substituted into them in src/strings.js).
That bash expression hurts my brain.
The comments that were previously on lines 130-131 should be pasted here. It took me a minute to figure out the intended behavior here :-)
Bugfix (typo): String -> Strings
Can you pass a promise to pipe() like this? I only see the signature that accepts functions (see http://api.jquery.com/deferred.pipe/)
I don't see a `_verify_dd_loc()` method ...
Two questions:
1.  you are operating on an stl::deque without holding a lock on the queue.  Are the operations guaranteed to be thread safe?  I thought the answer was always no.
2.  Next line does nothing ... what is deleting items from deque?
Never an error returned from a write operation?
Aha.

While this isn't really my domain, I would drop zepto and yocto (unless you currently need them, in which case add zetta and yotta)
Missing space after comma (twice in the previous 3 lines).
#osom :) I've already pushed the fix. If you accept the coverage pull request #GH-48 you will easily see what parts require more coverage ;)

Have a look at the Development docs for the command line that I use to check the coverage report, it's a bit long to memorize! :D
Not sure which approach you prefer, but it seems like the docs for this and Show should follow the same general format, right?
Well, but supplying the raw entry moves application logic into the template, which is a big no-no.
```
item['visible'] = getattr(entity, 'visible', 'None')
```
should provide the desired interface, shouldn't it?
Also I'm not really convinced that I introduced the issue. I just fixed the path to mcf_extract which wasn't found before.
that's probably my fault btw ;)
Looks like there's a lack of space at the beginning of this line.
looks like we missed another case, when there was a previous tag and no new tag.
so could you add the case !bGotCurrentTag && bGotPreviousTag. thanks
CreateApplication gives you more flexibility. E.g. it lets you specify a name that will appear in the debugger. If you have multiple instances of magpie running this is pretty useful to distinguish them.
This should actually probably go into Hails eventually. Every application will need this, plus abstracting it gives the hails deployer more flexibility in choosing how to keep track of users internally.
我是说在freebsd上你不需要在configure的时候，使用--with-jemalloc的选项
This is already covered in the description, so I think I'd nix this one because otherwise we've just got it twice.
Basically this ensures that `katello_configure` can be loaded before/after Rails or as stand-alone lib.
Not sure if this is the best place, I have created boot_util for utility functions which are executed before Rails3 boots up. But should not hurt it.
Copyright headers are missing here.
I know it was there already but while you're at it: s/define/defines/
Dobro je emrgano, izbrisao sam bio konflikt ali ostao head slucajno.


Date: Wed, 17 Oct 2012 15:02:06 -0700
From: notifications@github.com
To: uskoci@noreply.github.com
CC: vatavuk1@hotmail.com
Subject: Re: [uskoci] Eventi komunikacija + još par evenata (#39)

In design/backend/src/test/java/com/randombit/uskoci/game/GameControllerImplTest.java:
> @@ -388,11 +388,14 @@ public void testGetPlayersPoints() throws Exception {
>      }
>  
>      /*  Specificno pravilo 3
> +<<<<<<< HEAD

Meni ovo zgleda kao neuspjelo rješeni conflict. Nebi <<<HEAD trebao bit ovdje. Probaj ovo zbuildati

            
              —

              Reply to this email directly or view it on GitHub.
Yes, liek that we will remove users dependency. I will back to this later in the week
I guess I can claim it as my trick, I searched "python static variables" thinking that I'd have to use some sort of generator or something to hold state in a function, because I really didn't want to add a configuration piece JUST to keep the damn thing in memory. That said, I'm ASSUMING that this stays in memory across multiple requests, but I'm not positive. The next few weeks will be the "test writing era" but like so many in the age of copper that were overthrown by bronze I believe we will soon be in the "age of profiling".
Probably not a big deal, but couldn't this reference be a "scientific publication", for example SOFA manual (or IAU publications referenced there in)? Presumably the wikipedia values ware taken from there; still quoting the original seems more appropriate here.
I've changed ``catch_warnings`` and ``catch_exceptions`` to ``log_warnings`` and ``log_exceptions``
Hm, I think because (as @demitri says) this is really just a convenience function, we should either:
* Do an "all" search by default, and just return _something_, maybe just the first entry (if someone really needs a particular measurement for an object, they should create the coordinates object themselves!)
* OR, disallow "all" and make them specify the database

Personally, I think the first option is fine because, as I said, this is really just a convenience thing and as long as we document the behavior I think it's ok...
GNU Make at least is smart enough; does BSD Make not have $(shell ...)?
Well yes but we're trying to improve. IMO it'd be best to completely get rid of the macros, if possible. But making them less "magical" would already be good.
Of course a much nicer approach, thanks.
This was fixed on 91de801
The decision was to split the Bootstrapper in two phases

* PreAppStart: container initialization
* PostAppStart: setup routes, hubs, etc 

In that way other initializers (like FederatedLogin can use the container). See 14e8cd8 as well
BTW this commit is messy, leaving the unused local variable $found in place.
I think there is a code smell when you have something like Group#create_discussion. I expect that discussions controller creates discussions.
I am thinking that the above three lines should probably be condensed down to a single step called "Given I am an admin of a group". That step can create the user, log them in, create the group, and add the user as an admin of the group. 

And all of the steps I just mentioned can be done without using capybara (as in, use factories and rails code to do this particular step instead of using the actual website functionality).

The main point is: we already have a create_group feature which manually tests creating a group on the website and making sure it works. So for the rest of our tests we can just use Rails to create the group behind-the-scenes (we don't need to test the same thing twice). Creating a group with Rails code will be much faster than with capybara.

The main rule of thumb I'm taking away from this actually is... "Given" steps should probably mostly be using straight Rails code (since they are setting up for the test). "When" and "then" steps should probably mostly be using Capybara.
so, this is somewhat worrisome. In the Qt and Wx implementations, the pipe is asynchronous (using queued signal connections on  Qt, and posted events on Wx). 

Enaml Signals are synchronous, so this may affect how the tests execute. We may need to mockup a small event loop.
This is unrelated to the rest of the changes, but was a quick tweak to correct the wording.
Let's not change the default value.  This PR makes the SVGs sharper, but does not actually fix the many problems with SVG figures that prompted us to change to PNG from SVG in the first place.
This change seems unintentional.
How is the CPU load with a 1ms sleep? It looks like the Qt inputhook has a 50 ms sleep, and the pyglet & glut ones have a variable rate.
Does it really make sense to have temporary urls for removal? Removal can happen only once. I think we should delay this until we have a blob store that offers this feature.
So, basically, I'd like to keep all this as `static` inside of `mwindow.c`. The `ctl` struct is a non-issue, it'll be just zero'ed out and ready to use.

The static mutex is going to be trickier... It can be simply set to `PTHREAD_MUTEX_INITIALIZER`, and that will get us a working global mutex that doesn't need to be destructed. However, I'm not entirely sure we have a Windows equivalent for this. Let me research.
4k on the stack? We're trying to move away from this. Is there any way we can stick this in the heap, inside `stream`, and re-use it between calls?
This was the copy as provided, but you're right, official style guide says sentence case for headings. I'll fix that.
Yeah, we could add checks in the product_details library, but let's see if anyone ever hit this. If it comes up, we can fix it.
This should be `http://www.mozilla.org/firefox` to let mozilla.org decide which version the user is using.
To clarify, we need to be able to link to specific answers with the fragment identifier. Like:

https://support.mozilla.org/en-US/questions/935476#answer-363195
Typo: safely
So go ahead with it. :)
It doesn't look like this code gets used either. Perhaps because you moved the caller to that separate "open devtools" branch? If so, then maybe this should get moved to that branch as well.
Can I get a line break before the `class`?
Out of interest in there a reason that this was not made an embedded document on the Instance model?
I think admin is an optional field. But gets added during normalization so this should be OK. I suppose we might as well use `andalso`. `and` evaluates both args always.
`ShouldNotTriggerError`? :)
One thing that's unfortunate is that in general this isn't as symmetric as you'd want it to be. The problem is that there's two different ways to represent `String[]`. If you have this field:
   String[] stringArray;
Then the type of that field will be a `Class` that returns true for `isArray`. If you have this field:
  List<String[]> listOfStringArrays;
... and you ask for the first type parameter (the `String[]`), then I believe you get a `GenericArrayType` whose element type is String.class. For this reason you need to canonicalize types before you can call `equals` on 'em.

It's gnarly.
@bschussek what the purpose of modifying this files (seems unused) ?
Missing test for it.
@Crell but this UrlGenerator would simply be broken without a RequestContext. It needs it and so it needs to implement the interface
@Tobion when you rebase, you need to use ``--force`` when pushing as rebasing rewrites the history.
oO are you sure? properties are almost never public, there are dozens of `@var` to remove!
I would just name it `sort()`.
nope, I'm an idiot
If we move has_metrics to the aggregator, this could be written in one place. Also, do we need has_metrics? When is a check _not_ going to produce a metric? Why not just call get_metrics?
Well, here's no point to cast, I agree. But just for uniformity... :) And one function less in call chain.
You'll probably want to wrap this in a rescue with an ensure that ejects the cassette from prior experience.
The constructor of DynamicStringProperty is package private. The reason is that we want people to use DynamicPropertyFactory to create instances where DynamicPropertyFactory will lazily install a default configuration source and attach to the dynamic properties, if none is explicitly installed. You might also want to make this constructor package private and provide a factory method in DynamicPropertyFactory. Or, try call DynamicPropertyFactory.getInstance() in a static block at initialization of this class.
The return type should be Box[Int], it could fail
This line should not be modified.
Что-то с отступами не то. Вынеси `.filter()` и `.map()` на один уровень. Как-то так:

```js
return items
    .filter(function(item) {
        // ...
    })
    .map(function(item) {
        // ...
    });
```
Here should be called a method to actually process collisions.
I can agree to dependency hell... I changed everything but `tornado` to be `requires` and I put the `ujson` imports into try except blocks.
Что, простите? Что оно тут делает?
Is there a particular reason you test membership in the keys list instead of the dictionary?
Please use non-recursive variant.
Im still not sure where to report. Sorry :-)
I think a `teardown` section should be used for that. This is [what I did](https://github.com/fschopp/testsuite/blob/b16151586bd8a7039ec216595efe34a969aef1c9/testspec/casespec/kmeans_new.xml#L2501).
Thanks for creating this, I've been meaning to for a while. xD
The building block for input areas has already landed in `shared`, please use this one.
TimeManager -> this
Sorry, I misunderstood. This is resolved now (moved to setup/teardown).
Yeah I am not sure I want to do something like this in reality `apps/**/test/integration/**/*_test.js` which works in some places with this grep if someone has a unit test named my_foo_integration.js it will also run in the integration step and fail horribly =/
add a test for the initial state where there is no sync-able account?
Looking at this again, I think you should just use img.width and img.height here. Let's return the wallpaper images completely undistorted and not risk scaling them to a canvas of a different size.  The image may get scaled when it is used as the homescreen wallpaper, but let's be sure not to do that now.
It's only a "copy&paste" from above. Im gonna add your comment suggestion. Thanks!
Move this outside of the `switch`
same here — the rest of this patch is just a rebased version of #5726.
can we move this to a separate function instead of an inline function?
You don't need `this` within the function I think.
odd quite space IMO:

````js
this._referencesArray.splice(
  ...
);
````

would be better I think.
(follow up)

Use the parent element of both `this.caption` and `this.coverControl` elements to toggle it's display, instead of changing the class of both of them.
Spaces around the parens plz.
B je správně ;-). Mám to tu spíš jako připomínku, že to je potřeba udělat (neboli chybí tam TODO).
:+1:  @davydotcom...
保守性と再利用性のバランスです。
↓
保守性と再利用性のバランスを考えて決めます。

のほうが自然な気がする。
Just using join() so I don't have to mess with commas and loop counters.
Code was taken from a previous version. Will leave like this because it works.
This could actually be 2 things:
 1. Your BlackBerry's user agent string doesn't match any of these (which would be odd considering that BlackBerry is on that list).
 2. Your device does not support localStorage (it's HTML5), resulting in an error. I have never seen anything like that, but I'll try to see how a device that doesn't support HTML5 behaves. We still have two options: cookies instead of localStorage, and then to put the whole thing in an if-statement: if (localStorage) { /*Check userAgent*/ }. I'll do some testing to find out.
that is debatable, I would assume you will get some other games where you can loose health, and perhaps even hunger.

so where do we draw the line? I agree that canHunger is more borderline than canLooseHealth
Another +1.  
Using Foreman is pretty well explained in Heroku's doc: https://devcenter.heroku.com/articles/config-vars#using-foreman
@alext's point is a really important one.

At some point soon we hope to move away from using email for Exception alerting. The work of moving from ExceptionNotifier to a new option is pretty clear and easy to assess. If we have other methods for Exception notification in place then there is a good chance they'll be overlooked and that exceptions will then be lost.
There is some weird scoping with with_config. How about you just change the assertion to:

```ruby
data_store.client.should == Curator.config.client
```

Or add this as an additional assertion.
no. the method itself does not.
Naughty them.  Happy to do this if you're sure it's a good idea.

How is best to do this?

e.g. width = !isNaN(params.width)? +params.width: null
and then change the checks to ...width !== null?
@DeadSuperHero indentation :)
Sorry but I really can't understand what you mean. The only time afterAppend needs to be called is when handling with bindings, which happens in compile.coffee and only after calling node.append. Could you please provide me a template, involving collections if you want, where you think the problem might appear? I could send you a new patch if I understand what you're talking about.
This was in inv.c. For some reason I moved it here and now it's only used in hijack.c Comment added.
You shouldn't need to define this class. It should be generated by compass
attr_protected for survey_section#survey_id
> Hum I forgot about similar exported methods resolve and reject ... they are identical to these methods but with the high level API, right?

Yes they are identical with a difference that return value is non-standard compliant promise. As `then` won't return a promise. This is mainly for internal bootstrap, where `then` chaining is irrelevant.
We can treat this as push :D
Of course you're right and I'll add the CLI, but I've got no idea how we're gonna setup the cron on the VM.
This makes us able to have an update "on demand" which is good before production will be ready. I'll just add a comment to delete the route before pushing to production
actually this comment is now incorrect and I need to update it
Just use the two argument version of fetch.
Sure, no worries, I'll move it now
Unless I'm not reading this correctly, the only place `get_watcher` is called is on [line 55](https://github.com/slyphon/zookeeper/blob/master/lib/zookeeper/common.rb#L55), so by changing the definition to take two arguments, but not changing the caller, that's gonna raise an exception.
The comment on this line is old.
document > body tho
This can be replaced by: `return ($object instanceof $type)`
use ternary when possible.
This file don't have the header block.
you should use the [redirect controller](http://symfony.com/doc/current/cookbook/routing/redirect_in_config.html) instead of letting people continue using the deprecated url. This will avoid people creating new links to this url:

```yaml
defaults:
    _controller: FrameworkBundle:Redirect:redirect
    route: faq_scoring
    permanent: true
```
`autofocus=true` -> `autofocus`
Ne la laisse pas, elle pose plein de probleme d'installation...
yep, let's do that, I'll merge in the change if you've got that

Thanks!
should be ``'POST' === $req->getMethod()``
I meant my local fork built. My fault, I didn't notice it  failed. Anyway I wonder how to fix indentation for json in vim. 
autocmd FileType json set tabstop=4 shiftwidth=4 softtabstop=4 expandtab doesn't seem to work
kill this println, I should not have committed this
no, laser scanner is not working yet!
the origin in the mesh has a wrong orientation -> needs to be fixed (I will tell my student!)
Same thing with loading `_` from `deps`, I'll add it.
protected methods should be defined after public ones, not before them
Yup, this is where src gets used in error msgs
I can't tell what's changed here..
At this point Popcorn.js can assume that all platforms that it supports also support `Function.prototype.bind` (it can be added to the IE8 shim if necessary), so this doesn't need to create an upvar for `this`:

```js
setTimeout(function() {
  callback.call( this, event );
}.bind(this), 0 );
```
Yeah that's what Tim G suggests.
I think you mean `1.9.3?`
While you're in here: "When all is said and done" is flowery verbiage. Could you rewrite it to be clearer?
Why the new imports, when the code is unchanged?
I'm curious why you changed this to use auto-boxing (which is slower than manually creating the Long object). But in truth, couldn't this just be:

    return ((Integer)value).longValue();
You don't have to declare this 4 variables, use directly firewall['ipv4']['UDP']
This still needs to be updated once `armstrong.apps.related_content` is released at 2.0.
Not sure if the name really reflects the behavior but I can't find a better one right now.
Each DOM node processed with `$.fn.breakpoint(...)` will have a serial number attached to it so we have a way to override a node's breakpoint configuration options and to unregister its breakpoint event handlers.
updated Alex css to contain no _ delimiters (except for twig classes)
@grimradical : is this what you were referring to in the IRC conversation a little earlier?  If so, I completely agree... this pattern isn't going to scale.  Was just discussing this with Nick yesterday.
I'll make a follow up ticket to have this use the `getValue` function in oae-config once that gets merged in.
I'm not sure I fully understand this. Wouldn't this always be true? You'd either be on the global tenant, in which case the left hand side will be true, or you'll be on an actual tenant, in which case the right hand side will be true.
Does this need to be an externally exposed function. It feels like it's an internal utility function.
Although we have nothing that sets anything on Object.Prototype, we should probably protect against it.
ie: Doing Object.keys and iterating trough the array.
Just an aside, this is why a plugin system for Context rather than putting functionality into oae-context/lib/api.js will be useful.
I think >10 is fine for now. I think labelling contrib/core may work as well, but lets maybe wait until we have widgets implemented to see how these properties may or may not work together.
Can be ``private`` (as it is called by the companion object)
Any reason why this can't be using the ``scala-ide`` organization name? (instead of ``skyluc``)
``s/jList/JList/``
Ch. 6 v
Ch. 6
little helper method to grab the call in case it gets more complicated
I'll remove this as it's unneeded, we can't edit it so no need to send it through
Tenzij iedere character de zelfde side heeft kan dit ook weg
corrected according to the style guide
Looking forward to this.
On Nov 12, 2012 8:24 AM, "Jonathon Hill" <notifications@github.com> wrote:

> In system/libraries/Migration.php:
>
> >
> >  		// If the migrations table is missing, make it
> >  		if ( ! $this->db->table_exists($this->_migration_table))
> >  		{
> >  			$this->dbforge->add_field(array(
> > -				'version' => array('type' => 'INT', 'constraint' => 3),
> > +				'version' => array('type' => 'BIGINT', 'constraint' => 3),
>
> Yes, good catch. Thanks.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/EllisLab/CodeIgniter/pull/1949/files#r2097094>.
>
>
Забыли сделать проверку: в текущей реализации можно передать методу как отрицательное, так и число больше 100
do we not need to add the following to the sqlite3 configs?
  pool: 5
  timeout: 5000
Isn't that in kwargs?
On Oct 30, 2012 7:58 PM, "Jon Parise" <notifications@github.com> wrote:

> In redis/client.py:
>
> >
> > -        # Extract the database ID from the path component if hasn't been given.
> > -        if db is None:
> > -            try:
> > -                db = int(url.path.replace('/', ''))
> > -            except (AttributeError, ValueError):
> > -                db = 0
> > -
> > -        return cls(host=url.hostname, port=url.port, db=db,
> > -                   password=url.password, **kwargs)
> > +            return cls(host=url.hostname, port=url.port, db=db,
> > +                       password=url.password, **kwargs)
> > +        else:
> > +            return cls(unix_socket_path=url.path,password=url.password, **kwargs)
>
> I think you still want to pass db=db in this call, allowing the caller to
> explicitly specify a database value.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/andymccurdy/redis-py/pull/294/files#r1983993>.
>
>
Can you please move this paragraph to the end and change it to a "Returns …" section, like so:

> Returns a signal which sends a single `NSArray` when the receiver completes.

Also, in TomDoc style, each paragraph should be separated by a blank line in the comment.
I'd switch these to methods too.
@codyhoag Is this the user's iGoogle directory or a an iGoogle directory shared by everyone on iGoogle?
This should probably specify the project, otherwise it will try to collect all projects which might not be production-dependent or not specifically related to the main project.

```./firebreath/prepmake.sh webpgPlugin build``` is more concise.
Oh.. I see.. what I can do is simply call mne.extract_label_time_courses from inside the method and pass "self" as the first parameter. That way we won't have duplicate code :-)
so i don't have to set this explicitly?
great,
thanks!

On 19.10.2012, at 21:09, Martin Luessi <notifications@github.com> wrote:

> In mne/fiff/raw.py:
> 
> > +        existing raw instance
> > +    data : instance of numpy.core.ndarray
> > +        processed data matching the data contained by raw
> > +
> > +    Attributes
> > +    ----------
> > +        See __doc__ of mne.fiff.Raw
> > +    """
> > +    def __init__(self, raw, data, picks=None, info=None):
> > +
> > +        print 'Initializing raw object from merge with custom data.'
> > +
> > +        if not raw._preloaded:
> > +            raw._preload_data(True)
> > +            raw._preloaded = True
> > +
> raw._preloaded = True, my comment above was implemented in #146
> 
> —
> Reply to this email directly or view it on GitHub.
>
When you have an error like this one (invalid argument), you can set the status code of the response to 400.
Also when you have a long statement or line of code, separate it into more than one line (better readability).
If @selsemore doesn't get to it first I'll (hopefully) update the code myself this weekend.
remove the comments from this line
This empty line isn't needed and I don't like line 34, there should be a description there no 'title'.
Change this to `// ... handle the config values`
referers => referer

size翻译出来，这里作参数对应而保留size的英文没有意义，因为只有一个参数。
所以翻译出来作为解释反而更好。
=>
桶容量
"is"
Given the comment in the discussion it seems like this assertion might not be warranted and that a future improvement to SymPy might cause this assertion to fail. Perhaps "is not False" would be better?
The Klang works in mysterious ways.
So this is evidence of the incorporation problem. f is an Expr and Expr doesn't have your __call__ method so you are putting it all in one place. But is seems that each of these things should sublcass the sympy object and have their individual __call__ method. @asmeurer may have a better suggestion for how to handle this. I'm like you -- I would put it all in one place, but I would do it because my oop is not that advanced.
Habría alguna objeción con llamarlo simplemente "Hash"? O representa algo más que eso que no logro ver?
That's great idea. Will you do it yourself or you wants me to add the fix?
It can be futhur simplified to one zero instead of four.
I often want to see diff for composer.lock, and this can be configured for user local repo, I do not want that to be a default.
Hmm maybe I should change that. I've been on the fence about it but mainly I figure I don't need $timeout if I'm not triggering anything with AngularJS (and yes I should probably just do `$timeout(fn, 0, false);` instead).

Elsewhere though, if `$timeout` wasn't injected and I don't need a `$scope.$apply()` I sort of figured it's not worth the additional overhead. I'm happy to change it though (I'm not entrenched in this).
这段写成这样有什么特别的原因么？

if ($node->modifiedTime ?: $node->createdTime > $last_modified) {
$this->saveLastModified($last_modified = $node->modifiedTime ?: $node->createdTime );
}

??
Maybe I should reorganize to check local only and else everything vs. not local only and else.
Nicely spotted, the createByteOutput() does a check within it.
the year should also be updated
remove time and base64
Should really be send_sms instead of subscribe, considering the optin argument.
"quel que soit"  a la place de "n'importe" or "qu'importe" ?
This should be "partie" instead of "jeu."
No need to keep the function above. It can live in its own user.js file.
missing license block
It's a struct, usable with thrift/pack, that encapsulates a supplied missing value (really a nodata value). For rain, for example, the value is -999. For MODIS, it's -3000. I'm not sure why we use -9999 [here](https://github.com/reddmetrics/forma-clj/blob/05dce62c92f9c054674e478676088d79111e9240/src/clj/forma/hadoop/jobs/timeseries.clj), but it doesn't seem to hurt anything.

Anyway, by passing this into sparse expander, we get a ts of missing values that is then filled in with good values as they appear.

N.B. that we never ran these preprocessing steps using feature/deliver bc everything was preprocessed with develop before feature/deliver existed. I doubt this timeseries preprocessing actually works.
@gsilver Can we add this into the `addBinding` method instead of the `renderMenu` method? Or is there a specific reason to do it in here?

Could you also update the format to the new styleguide? (`.on()`, spaces, single quotes, ...)
couldn't you equivalently use if (l1->get_int_label(i) != m1 || l2->get_int_label(i) != m2) and rename find_match_count -> find_mismatch_count to really create positive costs?
How does that save any typing? ;)
Is it possible to add a ``@param`` annotation for parameter ``$defaultValue`` which defines a more specific range of types; something like ``string|array``, or ``null|MyObject``?
Are you sure the variable ``$domain`` exists, or did you maybe forget to declare it?
AHA! :)
This should be `(model, error, options)`.
```
int getId();
```
I actually think it does make sense to split them, as one should be a POST and the other should be DELETE (to conform with REST)
Sadly, this is a 4 years [old bug](https://code.djangoproject.com/ticket/9762) in Django. It is really how some simple bugs do not get merged upstream soon enough and then patches get obsolete and then ticket hangs around ...

Use [this function](https://github.com/django/django/blob/master/django/utils/feedgenerator.py#L38). Please make a pull request to Tastypie which fixes its `format_datetime` function to use `rfc2822_date` and explain to them what is wrong.
I don't understand what to do. You said I should put it like this :)
And sorry about the misplaced space in process_channel_subscribe. It happens always when I copy-paste. Will change it in next commit.
OK, then leave it as it is.
I don't think it's invalid but I agree with you that using sequence would ensure the verbatim code is evaluated as a single expression in those cases. I'll change the code a provide an additional test for it.
didn't find it used anywhere else either actually
spell script
this isn't going to be called or needed anywhere, does it really to be added?
This line needs to be updated, as I believe the tests and benchmarks are no longer installed with the package.
Thanks, trailing whitespace is evil : )!
Secretly non-optional positional arguments smell pretty bad to me.

```python
def default_request_encoder(method, *args, **kwargs):
```

since it's not optional and has a name.
Yep changed it ;) Fixed some other issues
Shall the two providers URLs be configurable from pf.conf?
Changed relative link to the format used at the end of Chapter04.
this is done internally and if it's empty `Utilities::tryGetArray` will handle that.
Makes sense, at worst the color representation would only impact the painting, but that's the lesser problem.
Also there's whitespace at the end of docstrings.
This part can be left out ``#statsmodels.stats.diagnostic.linear_rainbow``.
L1 is the L1 norm for infinite dimensional function spaces.  l1 (called "little L 1") is the norm in discrete spaces (including finite dimensional vector spaces...which is the case here).
Seems like you should be able to combine this and line 6 into a simple jquery selector.
Although this line will likely change, the convention used at Twitter (and in these specs) is to use a lambda and .should raise_error:

```ruby
lambda { subject.format(2, patterns) }.should raise_error(ArgumentError, "Missing pattern for :few.")
```
type: boolean
Use `'` for constant strings (also dict keys).
same, vmguest
For now this is ok, but I'd guess we would basically do the mapping server side.

Basically allow the user to specify a translation map between the incoming user query and the datastore filters.  That sound reasonable?
It might be worth checking a few of the stickier invalid initializations to make sure they raise an exception.  e.g.:
```
numpy.testing.assert_raises(TypeError,galsim.Shear,0.3)
numpy.testing.assert_raises(TypeError,galsim.Shear,g1=0.3,e2=0.2)
numpy.testing.assert_raises(TypeError,galsim.Shear,eta1=0.3,beta=0.*galsim.degrees)
numpy.testing.assert_raises(TypeError,galsim.Shear,q=0.3)
numpy.testing.assert_raises(ValueError,galsim.Shear,q=1.3,beta=0.*galsim.degrees)
numpy.testing.assert_raises(ValueError,galsim.Shear,g1=0.9,g2=0.6)
```
(I'll add that these all do in fact pass.)
I'm far from a C++ expert, as you know :) so I am curious to hear more details, will wait to see what Mike says.
Pretty ugly having all this junk hardcoded in here.  Open to suggestions for better ways to do this.
Huh? Where?

If you're talking about amount = params[:donation][:amount] , that is a user-entered string. the Donation model's readable_amount= will take care of parsing and conversion.
Unused imports added.
This is a compiled re object, use URL_PLACEHOLDER.sub rather than re.sub?
Yes, the initial plan was to have all `free` calls as `git__free()` in case we ever needed to plug in a custom allocator or do internal leak debugging. Let's try to keep it consistent.
@AdrianGaudebert To be honest, I do not know PHP well enough to decide on these kinds of things so, I sorta use what works ;) With that said, I am all for consistency and using the best option at hand, so I will change these to use classic style.
Yes, I think we better stick to our naming convention. It will have the same meaning.
Assigning a name to `this.stack[this.counter-1]` would make the code more readable.
No, it's not, I checked. In fact, I had a version where I had completely removed it, but I decided that if someone had written it they probably had a reason once upon a time and might go looking for it again.
It's because I can't quite understand where the 0.25 comes from although I see they are puttign the bisector on a right angle triangle and using the pythagoreans theory.  Anyway since I couldn't figure it out I pointed to someone else who didn't explain it.

But good point, will remove :)
not sure how to do this. commit again with new message and offer a new pull?
This seems like a good example. Perhaps the earlier examples could be part of the same theme and each could incrementally build upon the previous. That would give a new reader an easy walk through of how each relates and where/when to use each paradigm.
Зачем эта проверка? Она делается в supports.
Перед каждым изменением есть проверка на текущее значение - так что, если mode == ERR, то он уже не изменится.
Подчёркиваний в названии переменных быть не должно.
Нет отступа.
Looking for the window flag doesn't exclude the document flag (if I am not mistaken), but the I would note the flags being used in the previous code would not catch all the page nav/reloads, hence these changes. Still, if you find any mistakes in the flags I picked, please point me to. I don't exclude the possibility of missing something subtle here. Any suggestions?
no because we construct the locator using ._root_element  and in is_element_present we use a (By.xxx, "locator")
I think we should just return a ZLS here as otherwise the return value suggests that "No error message available" is the text on the page!
This should probably be ```core.add(jpeg[i].getCoreMetadata().get(0))```, as calling ```set(int, Object)``` with an index greater than the ```List``` size will throw an ```IndexOutOfBoundsException```.