labofsahil/github-event-dataset-2012 huggingface dataset:
I try to use both type of expression : relative or absolute one. It's because in IDNFI, the case to find a province is an absolute one.
User must first enter a province, which is always reside in /cluster/province. 
And, the level of a taxon, is not always the same, which cause different relative expression to get the province.
We have the same for Postgres and MS SQL
http://www.postgresql.org/docs/8.3/static/functions-matching.html
http://databases.about.com/od/sqlserver/a/PatternMatching.htm
Can't this just be inlined?  Does it add *any* value, anywhere?
I think the wording here should probably change. The term here "equal" is different from what Ruby defines as "equal", so that could be confusing. Consider the wording "returns an equal string" and the spec saying "should_not equal(str)". Maybe rewording it in something like it "returns a duplicate string when given a single argument" would be better.

Also it is probably enough to just verify a single case here. So something like:

str = "usr"
File.join(str).should == "usr"
File.join(str).should_not equal(str)
i dont remember off hand where this binding is, in overlay? if so maybe it should be moved there
It took me a moment to work out what this function does. I think until we have more keys that affect the display, we should keep it simple and write:

```clojure
(defn- var-class [var]
  (if (:protocol var) "protocol"))
```
Same as forms -- the idea is that users / modules attach listeners to the init event of an input filter and are able to all additional filters or update/remove existing filters. For example, let's say one module removes the "verify password" field from the ZfcUser registration form. More than likely they're also going to want to remove the validator associated with that field as well.

See:

* https://github.com/ZF-Commons/ZfcUser/issues/74
* https://github.com/ZF-Commons/ZfcBase/pull/34
* https://github.com/ZF-Commons/ZfcUser/pull/104
Please follow coding standards; all conditionals require braces:
```php
if ($this->class !== $class) {
    return array();
}
```
Rename to `assertNotResponseHeaderContains`
Why are you undoing this?
If you expect escapeHtmlAttr() to be called lots of times within a request, it might make sense to do this:

    static $matcher = function ($matches) {...}

then ...

    $result = preg_replace_callback(.., $matcher);

This will alleviate PHP from creating a new closure per call to escapeHtmlAttr.
This don't match with the `@return` signature, should return `bool|array` not a `AbstractFieldValuePart` object.
You should use the final values with a comment explaining the origin instaed of use pow()
Some of these don't have a `$` so that they match `IPBoard_foobar` as well. There is no advantage adding it.
Will be good to add test for this.
Wędkowanie, ę doesn't work.
Use the OrdinalIgnoreCase comparer
Good catch. Swap the method names.
You don't need the path here:

```ruby
<%= link_to inventory_item.title, inventory_item %>
```
Right, then it's clear what needs to be done ...

Am 31.08.2012 um 14:21 schrieb Christophe Coevoet <notifications@github.com>:

> In lib/Doctrine/ODM/PHPCR/UnitOfWork.php:
> 
> > @@ -631,6 +637,26 @@ public function scheduleMove($document, $targetPath)
> >          $this->setDocumentState($oid, self::STATE_MOVED);
> >      }
> >  
> > +    public function scheduleReorder($document, $srcName, $targetName, $before)
> > +    {
> > +        $oid = spl_object_hash($document);
> > +
> > +        $state = $this->getDocumentState($document);
> > +        switch ($state) {
> > +            case self::STATE_NEW:
> > +                unset($this->scheduledInserts[$oid]);
> > +                break;
> > +            case self::STATE_REMOVED:
> > +                unset($this->scheduledRemovals[$oid]);
> > +                break;
> > +            case self::STATE_DETACHED:
> > +                throw new \InvalidArgumentException('Detached document passed to move(): '.self::objToStr($document, $this->dm));
> > +        }
> the point is, you cannot have 2 states at the same time. So it cannot be STATE_MOVED and STATE_REORDERED at the same time.
> 
> —
> Reply to this email directly or view it on GitHub.
>
Actually the problem was that by default the value of "$parentClass->Versionable" is empty string, and setting `$subClass->setVersioned("")` throws an error (as the value should be "simple" or whatever).
You should mention this class is based on the Symfony HttpCache\Store class.
> 1) eZ\Publish\Core\REST\Server\Tests\Output\ValueObjectVisitor\TrashTest::testTrashVisitsChildren
> Expectation failed for method name is equal to <string:visitValueObject> when invoked 2 time(s)
> Parameter 0 for invocation eZ\Publish\Core\REST\Common\Output\Visitor::visitValueObject(eZ\Publish\Core\REST\Server\Values\RestTrashItem Object (...)) does not match expected value.
> Failed asserting that eZ\Publish\Core\REST\Server\Values\RestTrashItem Object (...) is an instance of class "eZ\Publish\API\Repository\Values\Content\TrashItem".

Fix is in line 116:

> ->with( $this->isInstanceOf( 'eZ\\Publish\\API\\Repository\\Values\\Content\\TrashItem' ) );

Needs to be instance of RestTrashItem.
@dpobel Fixed.
Then, this `code:add_patha("ebin")` is redundant, isn't it?
or
```python
eq_(r.status_code, 200, 'Search view query should return 200')
```
Should be indented two spaces.
So the list will be:
 * mozmill-crowd
 * mozmill-addons
 * mozmill-ci
 * mozmill-ondemand
 * mozmill-release

mozmill-crowd is first so that it's the default. Happy with this?
normally its not a good idea to have more than one action in one orchestration step, as it would not allow a proper rollback
If you're going to use the nose tools, also use `ok_` instead of `self.assertTrue`
Does it make sense to include the tests from PTP? In any case, there should probably be a test for multiples.
I don't like seeing this go away.  We don't have regression tests for removing this kind of high level ID - there might be something programmed against it.  That said I don't think there is in this case, but still - it's a concern that shouldn't be taken lightly.
We only uses spaces in our code, not tabs. Also, if you could make sure that all of these `<var>` tags are aligned, that would be great.
This is a non-trivial calculation, so it might be better to pre-calculate this and store it in a final field so that multiple calls are much faster.
add indetions for this block
This is all well and fine in internals, but it is so god awful to try and read. Do you think theres anyway we can get this back in the FileUtils class use extract this into a private named function on Berksfile itself?
I've always recommended a 1:1 mapping between paths, resources, and classes. This should be extracted out into a ``PersonResource`` class with a single ``GET`` method.
Yes, but I believe that you can generate a new AST on setting the code, and set that into the Block.  Not that I'm necessarily advocating this case, since it really depends on your mental model of what you're trying to do.
Coloring - раскраска. Мы каждую компоненту сильной связности красим в свой цвет.
The client doesn't need to receive an access_token, because it is stored in an instance variable (token) inside the client. So, I think this documentation change is not correct, right?
I pushed up some rebased commits for this but the comments above are still apropos; haven't had a chance to look into it further just yet.
This should be using the `clone` module.
This comment should still be addressed.
Probably need to get the principal first to see if it exists and whether or not we have access to it?
This should still be using require I think
This is now using the `jqueryExtend` function based on the original jquery functionality. I placed it in `util.js` inside of the oae-config lib.
It would be good to create a ticket for this. 

If I remember correctly, the reason why this has to be disabled is that it involves UI code, so Mr. Jenkins is not happy (but it was working before?!). I think we need a ticket which remind us that we need to

* Enables Mr. Jenkins to run UI tests.
* Add ``TestScalaIdenter`` to the UITests suite.
The comment is on the wrong line.
Hmm why do we care if there are jobs in queue? Why not something like:

```ruby 
if queued? && !working?
  mark_failure
  "Resque is DOWN. No workers are working the queue."
else
  "Resque is working."
end
```
Please use `||` instead of `or`.
Use size_t instead of int here. It avoids a warning, and makes the code clean.

In general never compare signed and unsigned values. size_t is unsigned, as it expresses only positives sizes. int is signed.
не описан метод -(NSString*) randomProtein, у меня из-за этого не компилировался Cell Mutator.m
У меня такая же конструкция используется, она перечисляет множество индексов все по порядку
Согласен, можно добавить такую проверку, но т.к. percent  в данной функции используется в цикле for, c проверкой i < percent, и i не может быть больше нуля то никаких последствий от отрицательного значения процента не будет.
Question to all. Is 5000 too much as default?
fixed in ``CloseLiveBrowserFireCallback``
Do not use a factory girl thing here.  Just fill in the fields with data.
I don't like a catch-all exception, just let it be thrown for debugging and show the stacktrace
I don't really see a case where this would be exceeded.  This is a per user rate limit.  It does serve the purpose of verifying the auth worked....

K

On Oct 15, 2012, at 5:26 AM, Jesse Goodall <notifications@github.com> wrote:

> In boilerplate/tests.py:
> 
> > @@ -161,7 +185,7 @@ def read(self):
> >              self.assertTrue(urlopen.call_args_list[1][0][0].
> >                              startswith('https://api.twitter.com/oauth/access_token?'))
> >              self.assertTrue(urlopen.call_args_list[2][0][0].
> > -                            startswith('https://twitter.com/account/verify_credentials.json?'))
> > +                            startswith('https://api.twitter.com/1/account/verify_credentials.json?'))
> awesome, please disable it
> …
> —
> Reply to this email directly or view it on GitHub.
>
At this point, the identifier is an array, yeah. I'd apply this conversion in the exception class itself, instead of casting before hops :) JSON is a good solution to catch both, but for now I patched to allow array params.
hmm, this driver can indeed be removed but in favor of the Common StaticPHPDriver class :)

And yes, the BC break is already done for other classes. See the chain driver.
I think we might need the same associative array detection here, in case we're dealing with an array with both numeric and string keys. Otherwise, we could end up setting the `$propertyPath` field to an array and setting object keys in the same update, resulting in a "have conflicting mods in update" error.
Hm, doesn't Sidekiq insert it's own ExceptionHandler middleware into the chain first? https://github.com/mperham/sidekiq/wiki/Middleware
The documentation for the `streams` parameter here should be updated to not say "array."
Yeah, that behavior is probably better. It'll be easier to get the other behavior if need be.
I think we should escape the opening braces in the look-ahead. Also, are you sure positive lookahead is supported in Ruby 1.8?

If not (and even if it is), would it also work to add a word break there, e.g.: `/comment\b/` – that may be a little bit easier to understand.

Other than that, that's a quite subtle issue indeed, kudos for spotting that one!
Actually, I'm not sure if it is correct. Assume you have activity at only a single vertex in a label. In this case, U[0,0] will be 1.0 (rest all-zero), s[0] will be 1/norm(x) (x=time course of vertex) and V[0] will be x / norm(x). If you then double the label size by adding more all-zero vertices, s[0] and V[0] will remain the same (and they should).
Oh wait, right, in case someone already has some data saved with an event_id as integer or something I should keep it in. Nevermind...
I just read through the values_list docs for Django and I think I'm changing my mind. Maybe it's better to nix the exception I added for user-friendliness and instead have it return all the fields. It's not clear what order the fields are in, so I think it's kind of useless, but it does nix the exception which makes the code and documentation easier.

Would that be ok?
same comment here as above -- if the plugin was used, the @Verifies, @should and method name would all match (e.g. "should return empty collection when some given form fields do not belong to the form" --> getForms_shouldReturnEmptyCollectionWhenSomeGivenFormFieldsDoNotBelongToTheForm).
"coarse grained" should probable be "coarse-grained"
You know you can just end the sentence with a double colon 

```
the file `views/hello.php` and returns the output text::
```

Then you can drop the `.. code-block::php` directives.
Probably we don't want a bare `print` in the source -- I know they happen in other places, but it'll just end up in the Apache logs and make them harder to read. Can we take this out?
Turn this into one log line maybe? Going to be hard when there are multiple request handlers at some point to figure out which lines belong together, might as well just make it one line.
semi-colon-cancer
why copy if its already seen?
Выгоднее было бы итерироваться по всей мапе, а не в цикле делать так, потому что у тебя здесь лишние лукапы, а при итерации бы ты тупо последовательно шел.
Но это так, на будущее, можно и не менять, на этих объемах данных это незначительно.
Creo que este archivo no debería ser parte del proyecto.
Could you also be kind enough to remove the whitespace that exists around the `()`? Those are not needed. 

This:
`final SSLContext sslContext = SSLContext.getInstance( sslConfig.getProperty( "protocol", "SSL" ) );`

Would become:
`final SSLContext sslContext = SSLContext.getInstance(sslConfig.getProperty("protocol", "SSL"));
Could it be replaced by a `Process` ?
It could improve testability.

By the way, what do you mean by `$app->json(true)` ?
Shouldn't this be "Breakout session" too not "CODESTRONG Breakout" to keep it consistent?
In case we introduce an object that wraps grid-related parameters, we may do this as

```python
wcs=WCS('cube.fits')
grid_param = GridParam(wcs, slice=['x', 3, 'y'])
ax = wcs.subplot(111, projection=grid_param)
```
@campbeb Do you mean 'does not work' before or after? I think it is not related to the mapsforge version, but either to the display size, pixel density or something similar. So for me it fits exactly with the current implementation. What are the respective specs of the device you tested?
Tässäkin `cond` näyttäisi kivemmalta:
~~~clojure
(fn check? [s1 s2]
  (cond (empty? s1) true
        (empty? s2) false
        :else (check? (rest s1) (rest s2))))
~~~
All this should be wrapped in a try/finally and close the streams.
True, but what are you gonna do when you have to add new options? You're gonna have to modify that method to add a parameter which would break existing clients?

Or are you gonna add another method that takes these two parameters plus an extra one (-1 to this btw)?

Or, you can forget about this amend method and simply have a setter for the new option, without causing issues to existing management clients.

If people want to modify multiple settings in one go, they can compose their own composed operations.

So, -1 to this amend method.
Can you change the publish channel from "capture." to "capture/"?  We're delimiting our channels with slashes now.
a nice copy paste mistake ...
wierd, I didn't have that. Maybe something went wrong and I forgot to add that fix to the commit
Can we call this `lookupObjectByRefspec:error:` instead? I think "refspec" makes more sense as the noun.
Style: asterisk with the variable name instead of the type: `const char *path ...`
It's not that i really need the warnings. I just removed everything in the latest commit.
This is a little bit of a magic number. Would using the actual machine epsilon work? sys.float_info.epsilon is your friend.
Weird that these have mixed quotation types.
Isn't that the kind of thing that could be done in a unit test?

It sounds pretty edge case for a UI test.
This api changed yesterday so now it's just `self.lockscreen.unlock()` :)
I think it is better to inherite from IComparible<IProtocol>. WDYT?
"sous-tiret" n'est pas très commun, préférer "underscore".
This needs to be: "nova_cert_packages" => ["openstack-nova-cert"],
This method is only used in the tests. I think it should be removed.
please dont use stdio but rather SG_PRINT SG_SPRINT
Looks to me like this is not really affecting the state of anything, so the name "update..." is confusing. Is the intended usage of this that the frontend dev is supposed to provide his own custom response handler?
There's no need to set `first_id` here because it starts at `WT_TXN_NONE` (aka zero), but no harm either.

It seems fine to allocate the modify structure: this should be a rare case, and usually we will need it.
Please undo this before we merge
I didn't know about that regarding the AS3 compiler. According to your tests, it is safe to move the variable declaration. If that bugs you, I can move that line down ;)
size.text = (isBlackberry) ? l2.getHeight() + ' ' + l2.getWidth() : 
										l2.size.height + ' ' + l2.size.width;
Replacing the schema object didn't work because callers pass in their own schema object and we just modify that.
This conditional should be indentation-aligned with the next one, if (value.getVclock()...)
Test code creates an index, deletes it, then tries to read from it. The assertions expect there to be errors
should we discuss with the others?
Environment is required to call twig_date_converter on line 46.
См выше, - только рубли, никаких копеек
You are right.

Removed by 3be930cf81e06cecc391487ac3113aa59379e77f.
Yet it is.
I just want to find something to solve the pb for everyone or a workaround.
I went back in the commit because there are lots of modifications and I
wanted the guy to retest like that and see if the pb is really there and if
we can find another way.
I quite agree about the fact that using test config is not really good. Is
there a better way to do that?

Pascal

On Mon, Mar 12, 2012 at 11:53 PM, Brian Henk <
reply@reply.github.com
> wrote:

> >  import play.Play;
> >  import play.mvc.Http;
> >  import play.mvc.Scope.Session;
> >  import play.server.Server;
> >
> > +import java.io.File;
> > +import java.util.HashMap;
> > +import java.util.Map;
> > +
> >  public class PlayDevEnvironment implements Environment,
> LocalServerEnvironment {
> >
> >      public static PlayDevEnvironment create() {
> >          PlayDevEnvironment instance = new PlayDevEnvironment();
> >          ApiProxyLocalFactory factory = new ApiProxyLocalFactory();
> >          ApiProxyLocal proxy = factory.create(instance);
>
> Unfortunately, that is the meat of this commit. Behind the scenes, the
> test config works very similarly to what was being set before, but
> apparently something is being set that wasn't before. Is this referring to
> #44?
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/guillaumebort/play-gae/pull/39/files#r548904
>
To check if any attributes have been changed.

2012/9/7 John Nunemaker <notifications@github.com>

> In lib/mongo_mapper/embedded_document.rb:
>
> > @@ -12,6 +12,7 @@ module EmbeddedDocument
> >      include Plugins::Equality
> >      include Plugins::Inspect
> >      include Plugins::Keys
> > +    include Plugins::Dirty # for now dirty needs to be after keys
>
> Why this addition?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/jnunemaker/mongomapper/pull/439/files#r1555198>.
>
>



-- 
Karol Ciba :: tel: +48 508288029
:: skype: karol.ciba :: gg: 3365539
:: jabber: karol.ciba@gmail.com
:: http://www.karolciba.pl/
You should rely on the autoloader where possible.
That's an API change, why do we wanna do that?
normally I use the in form because on IE, with external object (ActiveX) sometimes just accessing a property or a method can throw an error, since in just check for existence without really access the object it doesn't throw any error, and is just a little faster, in this case I can safely switch to your notation.
a `)` too much.
This one is in the friend view (an event > friends tab > tap on a friend)
Can this app be installed automatically? Or perhaps the necessary inputs created automatically?
No need to provide default value for `verbosity` key. It is already `'1'` by default.
Heh, you respond fast, before I can change myself finding the error. :)
Yes, this seems to work.
This should go into a view. You use class-based view for forms and things will fall in place. Don't go against framework.

In registration we have save because it is a ModelForm form.
You added some unnecessary space here?
Move this function and registration bellow to external file.
Hm, `self.request.node` should contain node? You do not have to manually access that again.
This is another magic value that should be put in a "constant" somewhere.
Shouldn't this call `cancel_call`, in case someone calls it directly?
Consider, for a moment, `NSubstituteBuilder` as a black box. It implements `ISpecimenBuilder` where the only method has this signature:

```C#
object Create(object request, ISpecimenContext context)
```

There's a request coming in, and that's an `object`.

Now, via one of the constructor overloads, the class now informs the user that it accepts a Specification. Right now, that Specification is expressed in terms of `Type`. Don't you think that obscures the source of the `Type` instance?

Would it be fair to say that given that the class already implements `ISpecimenBuilder`, taking `IRequestSpecification` as a dependency more clearly communicates the collaboration between these two abstractions?

```C#
bool IsSatisfiedBy(object request)
```

Personally, I can almost visually *see* a line connecting those two `request` arguments.

---

Here's another question: when the Specification is provided as a Func, how would you ever use the `SubstitutionSpecification` property for structural testing? Yes: it's possible to test that the injected Specification is equal to the property, but what if you wanted to test that the default Specification exhibits certain, desired behavior? What if, in the future, you have a third party that creates an instance of `NSubstituteBuilder` and you want to unit test that it created the instance with an appropriate Specification?

Testing like this is *really* difficult. For the record, I had to do a lot of testing like this when I implemented the 3.0 kernel because `Postprocessor<T>` has an `Action` property of the type `Action<T, ISpecimenContext>`. Just look at [Ploeh.AutoFixtureUnitTest.Kernel.NodeComparer.PostprocessorEquatable<T>.GetActionMethod](https://github.com/AutoFixture/AutoFixture/blob/master/Src/AutoFixtureUnitTest/Kernel/NodeComparer.cs#L262) and the big, ugle [Apology](http://butunclebob.com/ArticleS.TimOttinger.ApologizeIncode) that accompanies it. I consider it one of the less fortunate design decisions in the AutoFixture code base.

AutoFakeItEasy may do something similar, but I see no reason to perpetuate a bad design decision.
Why are we allowing up to nine characters if we only want a 5-digit zip code?
I don't think it's necessary to pass a template context here. We only get to the view by raising exceptions so that context will always be empty.
Comment says it all. I'd like a newline at the end of the file.
Because I don't want users to suffer from bc breaks in mayor versions.
fixtures.yml definitely shouldn't be ignored. You can copy it to ~/.active_merchant/fixtures.yml if you want to maintain your own, customized version.
Remember: Arrays sind böse!
Yes definitely. Sorry, I didn't notice it.
Cause I'm a noob.
Woops, I need to fix that :P
Note that number/string literals also work.
Please don't change the import order, these are intentionally:

```python
stdlib

django

ratelimit
```
And presumably if you're passing a null reporter, you're not going to try to access its counters or use this for anything real. I suppose the code should have been structured to just handle `null`, rather than a special null reporter.
FWIW a page object should not return locators or elements. It would be something like an `is_thank_you_visible` property.
Grammar: not "it's", "its".
So for a while all updates are avoided? Is that for when you don't know the to-be-blocked uid yet? Probably explains why you need "this._suppress_updates", okay then.
Yes, makes sense, will fix.
Without this we get segfaults when we try to work with the request in our event callback.  It seems to tell nginx to keep the request around.  But I don't fully understand it.

An example backtrace without it:

#0  memset () at ../sysdeps/x86_64/memset.S:330
#1  0x000000000040cfd1 in ngx_pcalloc (pool=<optimized out>, size=80)
    at /usr/include/bits/string3.h:86
#2  0x0000000000472293 in net_instaweb::NgxBaseFetch::CollectAccumulatedWrites (
    this=0x1079520, link_ptr=0x7ffff7744b00)
    at /home/jefftk/ngx_ps/ngx_pagespeed/src/ngx_base_fetch.cc:98
#3  0x0000000000470eb8 in ngx_http_pagespeed_update (ev=<optimized out>, 
    ctx=<optimized out>)
    at /home/jefftk/ngx_ps/ngx_pagespeed/src/ngx_pagespeed.cc:260
#4  ngx_http_pagespeed_connection_read_handler (ev=0x10988c8)
    at /home/jefftk/ngx_ps/ngx_pagespeed/src/ngx_pagespeed.cc:302
#5  0x000000000042a1e9 in ngx_epoll_process_events (cycle=0x107a2d0, 
    timer=<optimized out>, flags=<optimized out>)
    at src/event/modules/ngx_epoll_module.c:683
#6  0x00000000004214a3 in ngx_process_events_and_timers (cycle=0x107a2d0)
    at src/event/ngx_event.c:247
#7  0x0000000000428a5f in ngx_worker_process_cycle (cycle=0x107a2d0, 
    data=<optimized out>) at src/os/unix/ngx_process_cycle.c:808
#8  0x00000000004270ec in ngx_spawn_process (cycle=0x107a2d0, 
    proc=0x428964 <ngx_worker_process_cycle>, data=<optimized out>, 
    name=0x93e2b6 "worker process", respawn=0) at src/os/unix/ngx_process.c:198
#9  0x0000000000429483 in ngx_reap_children (cycle=<optimized out>)
    at src/os/unix/ngx_process_cycle.c:622
#10 ngx_master_process_cycle (cycle=0x107a2d0)
    at src/os/unix/ngx_process_cycle.c:181
#11 0x000000000040c01a in main (argc=<optimized out>, argv=<optimized out>)
    at src/core/nginx.c:410
Copy/paste error. Should be `display` in the second test.
"edit-copy" would make sense I believe.
Where is the callback?
BTW, translatable string.
Oh, there is also:

Do not use relative names in imports. Even if the module is in the same package, use the full package name. This helps prevent unintentionally importing a package twice.
Why don't you store this in archipel.conf, that you would name archipel-guest.conf?
COuld we imagine a scenario where the user might want to say "you choose a sensible size that includes all pixels with intensity >0.001*peak intensity" instead of having the user choose the size themselves?  It seems like it would eventually be useful, though a larger project than we'd want to get into now (possibly something to open an issue about for the future?).
Well, I gave it a try, but I don't think it's worth it for these particular files.  There are a lot of conflicts, and I'm worried I'd just make matters worse if I try to resolve them.
I like the explicit parameter name references.  But this first sentence reads a little funny.  Like either it will create an image or it will shoot photons.  :)  Suggest: "The drawShoot() method is used to draw an image of an object by shooting a number of photons to randomly sample the profile of the object.  The resulting image will thus have Poisson noise due to the finite number of photons shot.  It can create a new Image or use an existing one, depending on ..."
Sure.  That's a good idea.
There's no ```y``` any more.
Hmm. if we want to include surveys maybe we can have

` exam = Exam.objects.filter(course_id=common_page_data['course'].id, exam_type__in=["invideo", "survey"]) ` ?
As above: should this be `Strings.isEmpty(ssl.keyDestination)`
the initial position is only being applied to scrollLeft
Hey, you point to your manifest file! XD
No.. We don't have any real slaveOkay tests, and they aren't trivial to create.. need to figureout how to test it automatically.
I do have some pending slaveOkay fixes coming up, will figure out how to test it as part of that work.
Yea. I shouldn't be querying the selector that many times, especially. Will change.
i changed code style and one minor mistake. Can you look now, please.
Any reason why `jasmine` is being passed as an arg here even though the global variable is referenced from within the function?
Please extends OBController
Нет. new FormatterException("...", t)
@ctweney and the fresh_vcr rake env param, should catch it here if all paths failed till this point.
With list-style-image, you don't need background-position & background-repeat
Use a more descriptive variable name than <code>el</code>.
Optional: Call super.dataUrl to get the same warning if data URL isn't defined. That way if the message needs to be changed you only have to do it in one place.
This should return moneyfield to then.
everything in this repos is under gpl2 unless otherwise mentioned. if we don't have a copy top level, then please add it there instead of in this dir.
this same code is present in 2 other add-ons. i'll move it to /lib/platform (as i already intended to do)
you can include platform/os.h instead
Could be a numbered list?
Shouldn't be. `cur_class` is an integer, and the equivalence test will give [True, False, True...], which is true for the correct class. Summing this is the number of Trues.
May of the tests in test-common are duplicated. I didn't have time to work on it and it is not very high on my priority list. I wouldn't mind much either way.
It was testing that a warning is issued when a `LinearSVC` is copied, and there's no more warning. I could put in a simple test for copying, but there's no longer any magic going on, so I didn't bother.
@ogrisel Declaring the type of the variables in Cython allows for static typing. This basically circumvent a lot of Python overhead.
I would call this `clustering_solver` instead.
thanks bertrand.
 
and one more:  $\lambda_i^t \psi_i(x)$ to allow for diffusion

but both can be taken care of fairly easily. my plan is to just derive a class from the spectral embedding class that is being refactored currently. i don't think i need to change the mechanics a whole lot at all :)
yes

the import from standard lib should go first, then numpy, then scipy, then
pylab then sklearn
We can indeed postpone this to when we implement hashed features cross products.
Should this be throw an error?
This would be executed by application code during SessionFactory construction for native hibernate (i.e. non-JPA) applications.  Users will typically perform this in bootstrap code - typically this will happen in a deployer thread.
Frankly, I don't see how this is any different from what we do for resolving JNDI binding service dependencies in ServiceReferenceObjectFactory.
Yes, just a decent number of retries to increase chance of getting a working ZK cluster up and running if one or two should fail before it.
Should really clear all the new members - even if they're guaranteed to be set in start()
There are assumptions in a number of places that resize only ever expands.
Ok, it won't play catchup, but it's not playing nice, asking for +1 bytes...
if you ensure rowsToArray was expanded first and _then_ asked for it's capacity and checked, you can expand to the exact amount.

It wouldn't have been just +1 byte of course, it will be an extra page required.
The main point though, is the code will look cleaner if you flip and do after: CSimpleSorterBase::addRow(next)
why ``false`` ? I don't see why you should use the ``false`` boolean for this
why not using ``getSingleScalarResult()`` instead ?
No. The structure of the test hasn't been changed.
An implementation of PuppetOptionParser built on trollop.  This is the implementation that is currently enabled.
Same as above, isset is useless.
Please replace this by `} elseif (null !== $parentFile) {`
you should not change the file permissions of the files
s/Node/Node.js/, s/Browser/browser/, s/OSX/OS X/
List implies plural, might want to rename to getEmailMessages
`(not (== (count a-seq) (count (set a-seq))))`
i renamed the file cause name was to common I think
I don't think this change is necessary with the aapt file already provided for windows. Same for the line below.
send_request_cgi can be used here too. I'll update by myself when merging, no prob :)
I think would be nice to do a realport_disconnect after the report_service to close the tcp connection.
I attempted to clean this up like  you had recommended however the detect will not return the custom value, it only returns the current item in the iteration.  Also this sytntax: 
````ruby
found_outside_item || raise Exception
````

Does not work at all.  Ideas are welcome.
happy to hear that, please do so
If we openly want to admit that we don't care about the doc for now, and we want this in master and make that decision as a team, that's okay with me.  However, this branch is absolutely the place for documentation to be done and we shouldn't pretend otherwise.  We refactored a major part of the code, therefore all code relating to it should be documented.  Part of our "completeness criteria" for Cesium is that new code gets documented.  This isn't the first revision of some prototype code, this is the move to the "right" architecture and code base.  If someone made a branch off of this branch, they are saying they are okay with waiting for this branch to be done before it comes into master.  "Because other people decided to depend on it" is not a good reason to overlook our completeness criteria.
Not I that want to be able to do it, but from an API perspective, shouldn't this class be able to return the camera position just like it can return the ellipsoid?

Isn't this whole class design a bit awkward with the camera position as state?  I see that it is an optimization for making several calls to `isPointVisible` and `isScaledSpacePointVisible`, but perhaps these should be static functions that the user passes their cached position-plus-whatever to?
Right now there is no good way for users to destroy textures held by materials.  Let's have materials follow the `destroy`/`isDestroyed` pattern used by all other objects that hold WebGL resources, e.g., textures; however, let's also have the texture cache reference count its textures.  So when `destroy` is called for a material, if the material has any textures, the reference count for each is decreased.  Once the count reaches zero, a texture can actually be destroyed since no other materials are referencing it.
The width of the thumb is hard coded? Don't love it, but don't hate it either.
May be better to encode the expanded path as a var, so that it can be refed later during the variable set.
I don't consider this bad code.  The style is consistent with how the driver and hub handle modules across the board.  Furthermore, this is not end user facing.  If we change this then all the other modules on both the hub and the driver need to be changed and that is not happening within the scope of this PR.
Phrasing is a little confusing. 

On iPad devices with retina display, the `density` property is `high` and the `dpi` property is `260`.
For other iPad devices, `density` is `medium` and `dpi` is `130`. Although if we make this change, should make it for the 'iPhone' line above.
NSDictionary* properties = nil
ENSURE_ARG_OR_NIL_AT_INDEX(properties,args,0,NSDictionary);

If you do this the cast below is not required
did you check this one is optional?
тут точно всё правильно? в __setLoaded передается массив, а он кажется ожидает что в него передадут объекты по одному. Т.е. может быть нужно добавить здесь многоточие `fis...` или убрать ниже `__setLoaded: (uploadedFiles) ->`?
почему у тебя он всегда неориентированный? может сделать два разных метода?
Awwe, thanks guys. For the record, I learned that trick by reading refinery's specs. ;)
declaration at the top of the block. you can assign while declaring, if it's safe
do not mix them up though
I suggest that the isnan check be made non-platform specific and avoid this problem for future platforms.
hrm, I'd have hoped this default loop works as well as the specialized implementation
Not sure what `IFTI` is. The main problem is that `lockstep` is designed to work with `foreach`, and foreach works with immutable arrays:

```D
    immutable(int[]) a = [1, 2, 3];

    foreach(ref v; a)
        v.writeln();
```

which means we want:
```D
    immutable(int[]) a = [1, 2, 3];
    immutable(int[]) b = [4, 5, 6];

    foreach(ref u, ref v; lockstep(a, b))
        writefln("%s & %s", u, v);
```

The problem is that since sequence is a template, then the actual type that is passed to sequence is `immutable(int[])`.

This all worked well up to the point where I refined `hasLvalueElements` to at least check input range, which is only the case when the array is unqualed.

Truth is (I'd say), that the conditions to sequence are not tight enough, and should be:
`isInputRange!R || isArray!R`

This way, we accept either of actual mutable ranges, or arrays (mutable, or not). Once there, I guess the internal cast becomes irrelevant. In any case, the whole thing should be better documented.

I'll see if I can't get this fixed in another pull.
Do not indent an example code in ddoc comment. This change will insert unnecessary indentation to the generated html.
I know it's not related to your changes, but think you could turn these duplicated functions into one function using `inout`?
I grant you that we don't have enough on dlang.org explaining ranges, but the documentation in std.range shows what calls have to work for each range type, and they clearly show `popFront` being called with parens in all cases. Also, it would make no sense whatsoever for `popFront` to be a property, because it could never be a variable. Properties are intended to emulate variables. Whether a particular function fits that criteria can be debatable at times (e.g. `save` should never have been a property, but that's what Andrei picked, and the only way to know that is from its usage in the documentation), but `popFront` is a clear cut case because it doesn't take any arguments or return anything, so it doesn't have the proper signature at all.
ここだけちょっと気になりました。「モデル保存の一環としてファイルセーブされるので、保存が終わるまでファイル名は信用できない」みたいなことかなと思いましたが、どうでしょうか？
起動しなくなりますね。
でも、該当する場合は未来永劫emitしないruleなわけですからね・・・
what about routes having a requirement looking like ``GET|POST`` ?
.suo is not needed there. SUO files reside with SLN files, and you don't have a solution in the FunctionalTests directory.
aren't these just resources :node ?
Does this actually work? I didn't realize you could put `None` in an `__in` list like that. If it doesn't work, you can do the same query with `Q` objects, you can look at how I do it in the `cc.view.manage.tags.views.tag_autocomplete` view.
I think you have to find this from the domain to the time coordinates vector to the Coordinate Axis to the bounds... Can't assume it is called time_bounds
Should be `debug.error` and the error should be descriptive
Здесь та же хрень про init list'ы, что и вчера.
Зачем тебе тут iostream?
»Specifies the memory ordering semantics of an atomic operation« or something along the lines? »Memory model« to me means much more than ordering constraints.
The fix has been done to dmd (thanks dawgfoto!) so please remove the hacks.
Can you add a little comment explaining what exception might be happening here and why its OK to continue
Is there a reason you also call hashCode() on the resulting String as opposed to using the hex string itself as the ID? (or even dropping to System.identityHashCode(session) directly)?
All that could be done with this
````
Assert.isInstanceOf(ExtendedSession.class, session);
````
you don't even need a log message since proper message is going to be constructed for you
Yuck - this should be on the setter
add this as a method of the DataSet class in database.py
roles is misspelled
it's fine like it is. I am happy to keep that file sole purposed for unit testing for now
Well, ``AbstractActionController`` and ``AbstractRestfulController`` extends that one, so didn't wrote about that one to avoid additional confusion and explanation.
The above was actually correct -- it's one use case for using basePath(). Also, we typically use camelCase, not MixedCase, to refer to helpers.
this might be fine, it depends what that method implements, I'll check it out later
New interface orientation method in iOS 6. The old one is deprecated.
properties should be camel cased
@jamesturk - are we using a standard key for "phone"?
it says color names, but msdn is a liar. it works with #color values including alpha as well. the only I wasn't sure about though is if kml's color tag which is aabbggrr is what microsoft expects. so just to be safe, i switched it to parse the hex string and use the Color.FromArgb call to give better confidence.
Unless explicitly disabled, the client will try to reconnect after the following events:

* downstream exception
* channel disconnect
* channel closed
Table links are now broken...  ($key no longer exists).
Is this a concern if you assert 2 lines above that the length is 1?
Sounds like there is only a single entry in the list and it should be `test_SERVER_ERROR`.
Right?
Created a new suite of appp, the user app and its router to be used to load only the user's prefs profile an d links to switch between corpora
See comments on the api pull request
nit: might be nice to add a :desc for this option.
This has moved here, previously in thbufdef.hpp, but no longer used by Thor.
Used here, by resourced, should also disappear soon hopefully.
esto es un error: News Item no está habilitado en nuestros sitios...
I would put some spaces here, so that it becomes: x += 1
maybe 

`if current == thread
  "thread waiting for own mutex to be unlocked"
else
  "external waiting for thread's mutex to be unlocked"`

does this help? hmm.
You will have to update the hash values below. The plugin splits the vmstat output on spaces, expecting certain values at specific indexes. Almost there ;)
Should be `if (session.appdesc) {`
I agree. More user feedback than we've had in the past would be good. I would keep the log message, though. It'll let users look for when a problem started, or look up the error if it disappeared before they read it fully.
The module docstring should be at the top of the file, just after the encoding declaration (`#-*- coding: utf-8 -*-`).
Vastaluvun -x saa myös helpommin näin: `(- x)`