labofsahil/github-event-dataset-2012 huggingface dataset:
"Добрый вечер. Действительно, забыл проверку. Спасибо."

http://www.artlebedev.ru/tools/decoder/ -- рулит :)
По поводу сторонней документации, я на Objective-C до этого курса не писал, так что я думаю очевидно, что приходится смотреть сторонии источники, но по очевидным аспектам, в любом случае большое спасибо, уже прочитал на stackoverflow про assign, readwrite и nonatomic. Я понимаю, что чтение и самостоятельные изыскания 50% обучения. 

За примечания и пожелание большое спасибо, обязательно внесу изменения, по большому счету все по делу и make sense.
1) Странно создавать геттер для переменной, которая используется только внутри класса. Все таки (на мой взгляд) property нужно использовать для организации доступа извне, а это обычные переменные.
2) Опять же, на мой взгляд, это константы, а не переменные. Да еще и общие для всех объектов класса.
3) readonly в @property NSMutableArray *nucleotides не запретит изменение массива (запретит только изменение указателя на массив).
извините, я только учусь. но почему вы определяете *DNA как NSMutableSet, а потом его инициализируете как NSMutableArray?
Лучше бы это определение было в отдельном файле Cell+Mutator.h
а как именно ломается?
Замена этому варианту выбора случайного элемента с исключением повтора
Посмотрите как вариант https://github.com/Hexlet/osx-project-1/pull/17 - очень красивое и изящное решение
или создание копии списка всех элементов, исключение повторяющегося и дальше выбор случайного из оставшихся

Данный вариант тоже работает ;)
assigning width = 30px didn't do anyting, because it inherits a property min-width = 100 from .label I believe.

I had to add min-width = 30px to override that, then add max-width = 30px to set the width to 30px.

Is there a better way? I thought it was kinda weird too
Please add a space: "%{short_id}: %{description}"
This line is causing a compile error in the appshell_helper_app target on the Mac.
That would not fix the issue, the problem is that `Image` triggers the __destruct method, and that this method triggers  the two destructive call on an object tracked in the `Layers`

```php
    public function __destruct()
    {
        if (null !== $this->gmagick && $this->gmagick instanceof \Gmagick) {
            $this->gmagick->clear();
            $this->gmagick->destroy();
        }
    }
```
I wonder if this comment could just be a `describe` statement that wraps the appropriate specs related to testing the API signature (or just be the title of the spec below, if it only applies to that)..
Use the "if key in dict" syntax instead, looks prettier.
semantically a div has content, whereas this thing doesn't. <hr> made sense from a traditional HTML styling point of view, although using its HTML5 semantic interpretation makes it perhaps a less suitable element. Do we have any "not div" elements that represent a bar of some sort?
Right, a one-line method only used in a single action doesn't deserve a ```before_filter```.
should be http://repo.jenkins-ci.org/public/
用base里的check-arg替代。
Missed that one, sure thing.
You might want to add a comment here saying that you make the window slightly larger than what you'll eventually be interested in ([-0.05, 0.3]) to avoid edge effects.
SourceEstimate
var currentDate. Also change currentDate to hour
As discussed, "email" is not in the chef_db query and we're not using it right now, taking this out.
Don't really need this, @ack_ids is declared in Smpp::Base
This arg doesn't exist.
@jeanmonod yes, but some of this should go in 2.0 and some of this in 2.1. The PR to master should only add the 2.2 specific doc
Thats a good point! Will look into it.
But thats the way it was: https://github.com/typhoeus/typhoeus/blob/v0.3.3/lib/typhoeus/easy.rb#L128.
The problem here is that, in a mixed setup, when someone uses both Workspaces and WikiManager to create workspaces and subwikis, the regular subwiki templates will be listed here as workspace templates. Obviously, if you use a regular subwiki template to create a workspace, things will get a bit mixed up.

One solution would be that, whenever you create a workspace template, you also mark the wiki template descriptor as a workspace (adding a WorkspaceManager.WorkspaceClass object). This way we can differentiate between subwiki templates and workspace templates.

Adding a java method in the workspace component for listing workspace templates would probably be useful to (in order to avoid writing queries on the velocity side each time).
The files are not empty, but after removing them all tests still pass. They're not used.

How about removing those .dat files and fixing the Bento error by removing line 73 in the top-level bento.info file? Can you confirm that that works Scott?
No debería ser `yyyy-mm-dd`?
Ups, como lo hice desde el mail me olvidé que estaba en github.

Estoy de acuerdo con lo de register, como verás lo hice medio apurado para
subirlo rápido. Gracias.

On Wed, Mar 21, 2012 at 9:58 PM, Alpha <
reply@reply.github.com
> wrote:

> > @@ -0,0 +1,48 @@
> > +﻿@model CommonJobs.Mvc.UI.Controllers.LogOnModel
> > +
> > +@{
> > +    ViewBag.Title = "Log On";
> > +}
> > +
> > +<h2>Log On</h2>
> > +<p>
> > +    Please enter your user name and password.
> @Html.ActionLink("Register", "Register") if you don't have an account.
>
> Parece que falta esta acción. No lo vamos a estar usando realmente así que
> yo sólo removería estas líneas.
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/CommonJobs/CommonJobs/pull/42/files#r588805
>
I'm pretty sure the locator you replaced was the correct one for katello/master.  please don't commit this. Yours is the old locator.
could have just added validate-content-search-results to the end of the thread:

```
    (->> "JSON.stringify(window.comparison_grid.export_data());"
         (browser getEval)
         json/read-json
         validate-content-search-results))) 
```
Excellent Answer! Concise yet descriptive!
use class="form-inline" instead  of inline css would be great here
cxczczxcxz
Please remove the +1 offset after removing the selectMapSourceMenuId. Java developers expect everything to be zero based, so we should avoid potential confusion.
This change does most of the optimzing
Wouldn't this break existing repos that simply update the target? They set a value of 'true'.
I agree w this Tim. 

Sent from my digital shackles. 

On Mar 30, 2012, at 11:05 AM, Tim Simpson<reply@reply.github.com> wrote:

>> +        return self.flavor.name
>> +
>> +    @property
>> +    def ram(self):
>> +        return self.flavor.ram
>> +
>> +    @property
>> +    def vcpus(self):
>> +        return self.flavor.vcpus
>> +
>> +    @property
>> +    def links(self):
>> +        return self._build_links()
>> +
>> +    def _build_links(self):
>> +        if self.req is None:
> 
> Rather than attach "req" to Flavors in the model, which brings a WSGI component into the controller/view agnostic model code, just return flavor.links from the links property.  Then put this more complex code into view and force it to always use the req property which is required in that item's constructor.
> 
> --- 
> Reply to this email directly or view it on GitHub:
> https://github.com/hub-cap/reddwarf_lite/pull/49/files#r626784
"device_path" and "mount_point" can be removed from this class.
Opps.
Got it. Gonna fix that.
Presumably this has been done as it wouldn't be possible to access the "sans-serif" attribute due to Python naming conventions. That makes me a little nervous: are there other keys which contain unsupportable keys?
They are intentional, if not helpful for discussion.
This line looks suspicious. I don't think it should be there.
I'd move this to cleanUp, but looks good to me.
I confess to not having paid too much attention to the code. This was @ahocevar's [patch](trac.osgeo.org/openlayers/attachment/ticket/3554/openlayers-3554.patch), which I modified to use OpenLayers.Util.isElement() instead of the previously used "div instanceof HTMLelement". 

That's not an excuse, it's a confession of fault. I have now run the tests subsituting line 499 with  `var isDOMElement = isElement`, and the tests are successful. However, I am not sure they would be on all platforms. Is there an automated system that can check against many browsers and many versions?

And, should the inline conditional test of `window.HTMLElement` be necessary, then it would have to be moved to `OpenLayers.Util.isElement`, right?
Apparently IE < 9 does not support `children`. See https://developer.mozilla.org/en/DOM/Element.children.
Yeah, the way to do it is to create an adjust protocol with different implementations for different things:

```clojure
(defprotocol Trimmable
    (adjust [& series]))

(extend-protocol Trimmable
   ISeq
   (adjust [& series] (reduce min (map count series)))

   TimeseriesStruct
   (adjust [& series] (apply adjust-timeseries series)))
```
The occasional singular matrix that should really just be ignored. I'm not sure what the best way to do it is, but these changes are hacks to get around the problem - I'm trying to minimize downtime for this huge cluster processing trends. If the solution is to return to `singular?`, let's do it! I don't remember when/why this changed.

 
On Aug 3, 2012, at 10:25 AM, Dan <reply@reply.github.com> wrote:

>> -            focsum-mat (i/mmult focsum (i/trans focsum))]
>> -        (-> (i/solve (i/mult foc-mat (i/nrow ts-mat)))
>> -            (i/mmult focsum-mat)
>> -            (i/trace)))
>> -      (catch Exception e))))
>> +        foc-mat (i/mmult foc (i/trans foc))
>> +        output (try
>> +                 (let [focsum (map i/cumulative-sum foc)
>> +                       focsum-mat (i/mmult focsum (i/trans focsum))]
>> +                   (-> (i/solve (i/mult foc-mat (i/nrow ts-mat)))
>> +                       (i/mmult focsum-mat)
>> +                       (i/trace)))
>> +                 (catch Exception e))]
>> +    (if (string? output)
>> +      nil
>> +      [output])))
> 
> Wait.  All this is incorrect.  We shouldn't be checking to see if the output is a string -- that distracts from the point of the conditional in the first place.  There are much better ways to do this, given that we know exactly what sort of issue will arise at this step.  We can revert back to the old code with the `singular?` function, and then return two `nil` values.  This need not check for general errors.  
> 
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/reddmetrics/forma-clj/pull/193/files#r1303649
You're right, I think dateutil is probably necessary. And the more I think about it, the more I want to put dateutil into the GPX code to improve consistency there. I'll have to benchmark that though, I'll only make that switch if it's faster. And it could very well be faster if it's written in C, since it would be replacing not just a regex but 6 invocations of `int()` and also `calendar.timegm()`.

I'll fuss around with that after the merge though, as it'll probably only complicate the merge if I add it at this stage. I'll just go update the documentation in anticipation of the merge.

Thanks for all your effort, this is great stuff!
For filling with zeros you may use zero() method and loop for (j,j) elements
On Thu, Aug 2, 2012 at 7:35 PM, Michael Cahill <
reply@reply.github.com
> wrote:

> > +             for (i = 0, cp = (ctable)->cg_cursors;
> > +                 i < WT_COLGROUPS(ctable->table); i++, cp++)
> > +                     if (*cp != NULL)
> > +                             ((WT_CURSOR_BTREE *)*cp)->btree->
> > +                                 cache_resident = cval.val ? 1 : 0;
> > +
> > +             /* Open the indices so we configure those cursors as well.
> */
> > +             WT_ERR(__curtable_open_indices(ctable));
> > +             if (ctable->idx_cursors != NULL)
> > +                     for (i = 0, cp = (ctable)->idx_cursors;
> > +                         i < ctable->table->nindices; i++, cp++)
> > +                             if (*cp != NULL)
> > +                                     ((WT_CURSOR_BTREE *)*cp)->btree->
> > +                                         cache_resident = cval.val ? 1
> : 0;
> > +     }
> > +
>
> This will usually be wasted work: if we're just reading from a table, we
> don't need to open the index cursors at all.


Agreed, but the only alternative I thought of was to look for information
in the table cursor when we open the indexes -- is there a better
alternative?


--keith

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Keith Bostic
keith.bostic@wiredtiger.com
Ah, but this is in the `.less` file ; )
[My linter](http://www.jshint.com/) was getting fussy so I obliged. Everything below is for the same reason.
If it's 'allowed' as in 'able', well then yes it does work to do that.

If it's 'allowed' as in 'authorized', your call :-) but then here I'm only doing that if I can't get whatever amount of memory is specified in self::$memoryAllowedOnShutdown.
Yes. As above, pointless browser compatibility reflex going on here.
Всё верно. Это типа __DATA__ в Перле. Полный аналог.
How does this work? If they all have the same name I'd think only one would get send to the server.
Couldn't hurt! And would certainly be better than mixing it with OutOfKitchenError which is intended to be what's thrown when knife solo commands are executed outside of a kitchen directory.
I find this description somewhat misguiding.  It suggests that multiple numbers are returned, while in reality only a single value for a set of samples distributes linearly/logarithimically is returned (here and in the func below).
The symfony DI does the validation for us. Adding a validate here is just for changing the validation error message.
And [here](https://mongoengine-odm.readthedocs.org/en/latest/guide/defining-documents.html#field-arguments).
Rename this to `comment_message`. There is no need for `attribute` because this is not attribute on the document! So you specify attribute if you want field to be mapped to document field. And you are not doing that. You are populating it manually.
Facebook's scope is also here, although it's not really URL. Should I then put it in google backend as a constant?
There is punishment for everything and everybody!
Not use generic names as `value`. Use something with meaning. For example, `comment` in this case.
Если этот парсер не скушает тег smarty, то что он сделает? Споткнется или просто проигнорирует? Если проигнорирует, то давай лучше оставим, т.к на самом гитхабе код светится, и многие пользователи (в частности я) в первую очередь смотрят инфу там (актуальность чаще бывает выше чем на зеркалах). 

И пусть хоть там будет синтаксис различимый.
Please refere to the http://docs.jquery.com/JQuery_Core_Style_Guidelines
This is done as part of the normal Homebrew link step, no need to do it manually.
Do you know why taglib stores a copy the description() in the actual text() part of TXXX frames? This is what makes this check necessary, and is a bit ugly since it forbids writing a tag where the value equals the key ...
The assertion here is weak, and it was a difficult trade-off to confront..

The assertion was initially stronger, similar to `Assert.Empty(intersection)` However, that way the test will behave erratically at some point. After all, there is always a 1/255 chance that, for example, we return 3 on position 3.

The code, as it is right now, asserts that the `intersection` contains fewer elements from the `initial` sequence (the result set is not predictable).
Yes, thanks, should be pictures_model instead document_model in this controller
char const*
Müsste man sich mal überlegen...
Thos comment shoud:

1. Have a single space after the `//` that marks the beginning of the comment string.
2. Start with a capital letter.
3. End in a period.

These also apply to the comment on line 102.
Would make sense to rename this to ATTR_NAME, but I guess it can wait to a proper cleanup.
No, maybe not. Moving it to cls.HTTPHeaderTokenizer.TokenStateholder for now, I think that's better. It's an asset that only makes sense to use with the tokenizer.
Would we benefit here from using the mutex abstractions from psol here if we end up using plain mutexes? E.g.  pass it in from driver_factory->thread_system()->NewMutex()?
Again, bugfixing?
Haha.. you can tell them on the readme file or a wiki page about deploying development environment. Later we can develop a script for bootstrapping environments by now the only thing you have to do is to add the path of this files to gitignore ;) its not such a great idea isn't it? hehe

The great idea is to have something like `NPM` to handle javascript dependencies and let the web server to find libraries on `/usr/local/lib/` or something but remember by now the only what i say we can do is to add the full path of the js libraries to `.gitignore` **;)**
Should have a `call` in there, too, if I'm not mistaken.
I haven't actually touched the phpcr or doctrine deps inside composer.json, so I'm not even sure why it went over to the master repo.
Exact. We cannot mutualize.
Stable version of nodewatcher uses an older Django version (1.2) which has not yet had support for [static files](https://docs.djangoproject.com/en/dev/howto/static-files/). You should uncomment those back (and remove empty lines).
I don't think it matters at all when _array is of type `T*`, but I can change it if you want.  (I actually find the std library versions of things harder to read, since the order of parameters isn't super consistent among different stl functions, so I usually avoid them unless they are clearly superior for some reason.)
Revision pushed.
Oh, and my use of `is` above is [wrong](http://stackoverflow.com/questions/1504717/python-vs-is-comparing-strings-is-fails-sometimes-why).  Stick with `==`.
What about if we returned a List of pairs of addresses.

List<Original, Normalized>

That would be easier for the UI to display the correction.
If there's actually an error, this warning gets hidden/redrawn over...

Maybe better to just use echoerr instead? But that's kind of ugly and makes it look like there's a fault in latexmk.vim
+1 ^ what @mjallday said. there's also an example of how we're deprecating stuff here: https://github.com/jrus/balanced-python/blob/aa3399afa252ede433e0cbaaf4c02d9adc9afafc/balanced/resources.py#L696
Should be `--force-confnew`
Used @Inject in HelpCommand
Why commented out?
If definitely not used and definitely not useful, then we should delete...
I would replace %{HTTP_HOST} by <%= name %>, because this will be what is hardcoded in the SSL certificate. If we redirect to any random alias, there is the risk users will have a "certif name mismatch" error in the browser.
Honestly, I find this to be less readable and succinct than what you had before.  I don't have a preference for `color(text, red)` over `red(text)` as an API (both seem equally fine to me), but using a hash and `define_method`  adds extra indirection over what you had before.  If you want the separate methods for each color, I'd prefer:

``` ruby
def red
  color(text, 31)
end

def green
  color(text, 32)
end

def blue
  color(text, 34)
end
```

I know on 1.8 that methods defined with `define_method` are slower when called than methods defined with `def`.  Not sure about 1.9 (I haven't benchmarked it), but I expect it's still slower.  So that's another reason to prefer `def` over `define_method` for this case.
Why delete the breadcrumbs?
What will happen if `thing_to_get` doesn't exist?
Could you clarify the reason for adding the "LIMIT 1" to all of these UPDATEs? Given that they all specify "source_id = ? AND destination_id = ?", and (source_id, destination_id) is a unique key, this doesn't really change anything, but kind of muddles the understanding of the query (i.e. the human reading may think that this could match multiple rows and only the first should be updated).
@levjj I think together with the recent changes in `apply` for removing doits this can introduce a very hard to track bug: `equals` is used for merging chunks. Since two chunks are equal when `!this.doit && !other.doit` they will be merged. But what if `this.doit` is still a "own property"? Then it is marked for removal... However, when merging, this information may be lost, resulting in a chunk with no doit info attached but with a DOM node that still has the corresponding properties set.

I guess having an explicit removal state that is reflected in `equals` would be the cleaner solution here.
Это нужно что бы "выбить" сервер из бесконечного цикла. Послать ему фейк коннект.
Конкатенацию строк в цикле надо делать через StringBuilder.
И будет баг, если передадутся такие аргументы "1" "1" "+" "1", в таком случае должна быть ошибка.
Если произойдёт исключение в конструкторе BufferedReader, то FileReader не закроется.
array - весьма непонятное название для переменной.
Вынеси в отдельный метод эти 4 строки. И далее везде по программе.
extends не нужен. Достаточно сделать static import:
```
import org.junit.Assert.*
```
Какая странная лестница.
You're right. As part of an earlier review with Paul, I gave up on the concept of isChrome - What are we actually asking by saying isChrome?
* This was read from a chrome uri
* This has chrome privilages
* This is a XUL document

And which of these questions are actually what someone needs to ask.

I removed the isChrome test.
同じくglossary 側に引数に相手の glossary を受けて同じかどうかを判定するメソッドを用意すると良いですかねぃ
When we are adding the theme to the assets path we are ensuring that the path those themes are added under are prefixed by their theme_name. This allows us to use the tfr helpers and request "styles.css" in our code, the helpers prepend the theme_name and the rest is handled by the default rails asset pipeline.

We maintain ability to separate themes by doing this.

The code could certainly be cleaned up a bit, but I /think/ this is the best approach as the underlying "hike" doesn't allow us to define a prefix as being separate from the actual asset at this point.

Does this make more sense?
I will recode the logic. 

Regarding the name, while it's true that it's the same html page, it _is_ a different logical page, which is why it is a different page object (EditListing vs. BasicInfo), so I thought it did make sense to override is_the_current_page for it. I can change this if you want, but I wanted to raise it for discussion as it does make sense to me to treat logical pages as separate pages.
Too much complexity. Why not use switch statement and simple call specific method calls that will make this complex if/else statement more readable and simpler?
way better this.
``` :class:`sklearn.cluster.KMeans' ```
2012/9/3 Gilles Louppe <notifications@github.com>

> In sklearn/ensemble/gradient_boosting.py:
>
> >          for i in range(self.n_estimators):
> >              predict_stage(self.estimators_, i, X, self.learn_rate, score)
> >              yield score
> >
> > +    @property
> > +    def feature_importances_(self):
> > +        if self.estimators_ is None or len(self.estimators_) == 0:
> > +            raise ValueError("Estimator not fitted, " \
> > +                             "call `fit` before `feature_importances_`.")
> > +        total_sum = np.zeros((self.n_features, ), dtype=np.float64)
> > +        for stage in self.estimators_:
> > +            stage_sum = sum(tree.compute_feature_importances(method='gini')
>
> I am curious, what make you change your mind? :)
>
The fact that you were right and I was wrong :-) - I've misread/interpreted
the prose in ESL: "improvement in squared error risk over that for a
constant fit in the entire region" - the original publication is much more
specific about that.

I've noticed though, that feature rankings were remarkably stable despite
the weighting by n_left and n_right.


>  —
> Reply to this email directly or view it on GitHub<https://github.com/scikit-learn/scikit-learn/pull/1088/files#r1516452>.
>
>



-- 
Peter Prettenhofer
it's recommended to use linalg from scipy

from scipy import linalg
linalg.pinv(...)
@ekohl Yep, that works too.  It was a copy and paste from the line above :)
Sorry for dragging this on so long, but could you please add a test corresponding to Kenji's comment 4. Eg, right here add:

 void function(int) shouldbeok = &f1;

which shouldn't generate any new errors.
Use `NULL` instead of `0`.
Maybe we're talking about different things :) This is what I mean:
```
vector<NATIVE_PROPGET_CALLBACK> vect(N_PLATFORM_PROP_LAST);
```
this try except code has no use, get() never raises a KeyError.

You should probably check for a None value being returned though as this will cause an exception in the code at the bottom of the method.
volumetric source spaces are already available
Why are you not using the more readible `springf` here?
Same. The inputSpecification is already defined in the Select element (however, you should check the validator attach to it, I'm not sure it validates against multiple values, so you may need to override it).
what is "fine" ? referring to small radius?
What's this? Would be good to have some more information on why this exists and why it's commented out by default.
I am expecting there could be other cases in the future.
Now using attach/detach, which is safer (since there is no window between calls that the file can be locked by another process) and better (since the file connection is created, which was the main grief of making create superfile within transactions).
dont just reformat files for no reason. obiously this one is using 2 spaces in XML -- or are 4 spaces a standard for jenkins?
Current version includes a Setup.hs.  Seems this file is only for older versions of cabal, but I included it since it seems common place.
Can we use curl instead of wget?  It is available with a default installation of any unix and wget requires and install via brew or another way.  Here ist he example.

curl -o tmp/Crimes_-_2001_to_present.csv https://data.cityofchicago.org/api/views/ijzp-q8t2/rows.csv?accessType=DOWNLOAD
This needs some explaining otherwise it's too blunt (the missing detail will cause confusion). It needs to be said that there are reasons why member groups may not be able to adopt the standards, due to legacy and BC concerns of the member project. We covered all the aspects of this on the list already. Basically, the answer is "no" but we do need to qualify it a little.
This seems premature. Looks like you may have simply copied code from Pinax. Would be best to get rid of this entirely and put it on the subclasses. I don't think this level of abstraction is needed.
Ah merci je savais que c'était pas bon mais je n'arrivais pas à voir ce qui n'allait pas (c'était tard ;-))

Je corrige de suite !
Add a list item for the strategies?
use can strncmp($version, 'dev-', 4); for another 2 opcodes saved :)
Just realized this is misspelled throughout. Awesome.
`return false;` to end iteration?
better to rename these arguments to what they represent, like v1 and v2 rather than "arg".
You could use the read_file method from the Post::File mixin
Really minor: I tend to avoid stating defaults in docstrings (both on this line and in lines below) because the function signature already shows the default.
I still don't want these guys to be in _warp.
It is not, those are used independently. Mapper::extractContentFromRows() has to be updated as well then.
So what is a more descriptive name for it?  `coastlineColor`?  `blendColor`? etc.
Does this function deserve to be public in Cesium?
I'm not sure what the convention has been elsewhere in Cesium, but these tests aren't named in the spec style at all.
Yeah, we do test for this use case, this is done by the [construct](https://github.com/danbev/aerogear-controller/blob/AEROGEAR-426/src/test/java/org/jboss/aerogear/controller/router/DefaultRouteTest.java#L29) test.
The same concern here. Do we have any reason to have a RouteDescriptor without a path? Just for my understanding.
If you're moving the example to the new namespace, should probably add a line to the description, like:

"For a code sample, see <Titanium.UI.iOS.DocumentViewer>."
Might be better structured by putting this in an `else` block and instead checking for `"local"` to start local mode. I think it's unlikely we'll add more modes but this makes the code a bit clearer.
We can't expose a ghost API like this.  You need to add code changes to proxy.cpp, and proxy.java to do it properly
hehe, I use the same name as documented in iOS :)
`>=` check instead of `>` check
it is not guaranteed that locations array will contain 2 or more objects, so [locations objectAtIndex:0] will fail with an exception
Это плохо воспринимается - фактически это if-стейтмент.
HTML5 Rocks uses window.alert. If we update an element with an error, we'd need to add more code so that the user could close the error once he looks at it. Since a) this error is unlikely to happen b) it doesn't have much to do with what I'm really trying to show c) this is just a simple tutorial, I think we should just stick with window.alert. However, I can be convinced otherwise.

In real code, I wouldn't use window.alert. In real code, I'd have a notification system. However, I think a notification system is out of scope for this example.
It can't realistically be anything other than a String.
Why aren't you creating the right widget right away instead of creating both and deleting one?
Ruby is passing almost everything as reference to an object, therefore you cannot call Array#delete directly on "original_array" as it will change this array as well for later use in Puppet (without its knowledge) which might not be an appropriate thing to do. Therefore, you could call Object#clone on given array prior to the loop body. This said, for a large data sets, both cloning an object and then iterating over its elements might not be desirable.
or skip that. `customParameters` is just fine. It's about the upload after all
бесконечная рекурсия?
I don't think it really matters. Looks good now, thanks!
Yeah. For a moment, I was surprised that `min` and `max` didn't just use `<`, then I remembered that `opCmp` guarantees that that you always have both (unlike C++). So, checking for `<`, makes checking for `>`, `<=`, and `>=` always unnecessary. So, I just checked `<` and didn't worry about the ordering.
should be half_float
Safe string equality, not `==`.
I'm ok with having them separate because the different log messages are useful - if you really don't like the code clutter, I'll find a way to extract the message for logging and combine. Made some changes to the engine-changed MetaGlobalException, so it's no longer combinable.
Er, no reason, my mistake. Fixed that in the newest commit - hand-tested reusing the entity, with no problems.
This is in `wipe`; we're blowing away all the data. That means we can just discard any pending insertions.
All looks good.
Never mind, you already had that check in dexterity.zcml
Move the file out, and see what happens :P Are you referencing it anywhere?
except you don't need the router :)
test/modelhelpers.py:26:69: E251 no spaces around keyword / parameter equals
(start_end_range=None)
Namespacing again.. Either place these into the function-scopes, namespace them or (prefered) move these to runner.js
oh, so it will always be the entity class name, not the proxy class name ?
Agreed, fixed with https://github.com/openlayers/openlayers/commit/cf9cc27279beaa54d5d9cf9224265428edc9aa92
It's used to disable certain functionality on hover of cells and rows.
`bind` -> `on`
@nsfmc There's nothing critical to make it live in this context. The only reason I hesitated on this is b/c when trying to get a handle on the khan-exercises code, there's a lot of "load"ing, "render"ing, "prepare"ing, "make"ing and such going on, and it's hard to know which functions to call. Part of me thought that keeping finishRender hidden from all client APIs except the one in which it must be used made sense -- but I'm willing to go back on that if you think otherwise.
This line isn't changed while it should be.
The issue with JMX was not about "wrapping" but the idea of "cloning" properties.

What we did agree on the call is that we *cannot* have a new CCF implementation of our own that users would be required to configure. If so, we would have to maintain that even after the boolean flag for temp destinations is added to core Spring's CCF. The idea was to wrap and to pass thru anything unrelated to temp destinations.
Change to Live diagnostic log.   It is the diagnostic log (hence the term) and it is consistent with existing download diagnostic log feature.  What term do you have in mind?
Broken link. Should be `http://rsbweb.nih.gov/ij/download.html`
I prefer this magic debug value to be false by default
Probably! `pi_lua_dofile_recursive` might be even better in this case.
Check the node repo : https://github.com/WindowsAzure/azure-sdk-for-node/blob/master/lib/azure.js for examples.
I'd think so, good catch.
sql.execute uses an older format where it takes the query with and then a series of args and plugs them in
But that format string should throw a TypeError as soon as we try it out, unless text() is handling that in a way I don't understand.
Smal but have some spaces here... see other comment, much more important than this
When you call event.trigger, the object you send must be a valid JavaScript object, e.g.
```JavaScript
_event.trigger("fontchanged", {'fontFamily': fontFamily, 'fontSize': fontSize});
```

Your current code at line 62 for sure will not work because the string you pass to JSON.parse is not valid JSON.
I'm going to handle this by adding appropriate enums in the jsas repo and then using them in this repo. I'll handle that in a followup (probably after I get the basics of marking read/unread working).
No, that's not equivalent.  Turns out my code didn't handle it sufficiently either so I'm glad you brought this up. We need to be able to change any existing parameters as well as create new ones.  My code had a merge at the end of the Hash generation but  of course the merge was the wrong direction.  Essentially we need to create a hash of user given parameters, change the associating parameter in the node/group if one exists and remove it from the user's hash.  Then take whatever is left over and make new node/group parameters.  This is better reflected in 0108c04
I've removed these, and will raise a ticket to have them added.
This is going to happen anywhere there isn't enough content to push the footer all the way down. Once the layouts fill up it shouldn't be a problem.
I agree. There is already a create method, I would not expect `getWebview` to create one if it does not exist, I would expect it to callback with null (or something). This is redundant, extra complex, and confusing IMO.
Тут можно было бы упростить ещё сильнее: `setTimeout(this.send.bind(this), 200, url, fn);`. Жаль что опера не поддерживает `bind` вплоть до версии 11.60.
Your right, I updated it.
Its in there because some calls inside of index.js call qnx.webplatform instead of window.qnx.webplatorm. I am going to remove it because I think its better to use window.qnx.webplatform. I will also update the other functions in index.js.
Doesn't this mean the event will fire if level is < 15. But this means that the event will fire on every level change below 15% and not just on the threshold (i.e. the point where it changes to 15% or below).

Which is the desired behaviour, once or every change below threshold?
The same for this
Mag wel weg
This is now completed