labofsahil/github-event-dataset-2012 huggingface dataset:
I find another Japanese IME Mozc. Its license is BSD. 
The dictionaries it uses are IPAdic and Okinawa.
The licenses of both dictionaries are quite open. A more detail can be found in
https://code.google.com/p/mozc/source/browse/trunk/src/data/dictionary/README.txt

Is it OK to use the dict in Mozc?
no problem good idea
move up?
remove "===" too.
Are we ever going to offer predictions after the user has only typed one character?  Would 2 be better here?
what about multiple (more than 1) arguments to the function?
That' s a good point as well. The contents of this file are largely taken from the Chef Omnibus installer bootstrap script that ships with Chef (https://github.com/opscode/chef/blob/master/lib/chef/knife/bootstrap/chef-full.erb). What if we made the curl case an `elif` and the `else` block prints an error ("curl or wget required") and exits non-zero? That would fail the broker (`@current_state = :broker_failed`) and be useful at least.
I guess that snuck in
@filipewl, removed id title and added class hide-title 4f9a2688be
believe me, I wouldn't add something like that if was "unnecessary". But I will add a comment for this line
Why?
Yes hrtime has nanosecond resolution. Do we need it here instead of milliseconds?
Also hrtime itself is 2x slower than Date.now() according to <a href="https://github.com/AlexeyKupershtokh/node-perf-time/blob/master/bench/b.js">this benchmark</a>:
```
Date.now() x 1,269,385 ops/sec ±0.69% (95 runs sampled)
process.hrtime() x 645,542 ops/sec ±0.21% (99 runs sampled)
```
so I'd measure its resolution as microseconds at its best.

Also using hrtime leads to a buggy code as you see :)
Fold the if into the assert and keep it all as one line.
#report_timing also messages the channel, this probably isn't what you want.
I think we need to start changing uses of `this` in factory functions to directly use `factory` so that we can remove the `bind`s and just assign the function directly into the `hd` namespace.
Our ruby style guide calls for a two-space indent: https://github.com/alphagov/styleguides/blob/master/ruby.md

This could be cleaned up in a subsequent branch/pull request but it must be done.
The tags removal is protected by a transaction. If database supports transactions, everything will work fine unless I'm missing something; there is no racing condition.

If we do support DBs with no transactions, I agree, we better just keep tags, and maybe remove them as a maintenance task.
I don't know :) I mainly adopted AD7six' version of it @ https://github.com/AD7six/mi_development/blob/master/views/helpers/tidy.php - we might need some additional refactoring then. Although it works on windows and linux.
I think `.to.be.an('object')` should work but i’m not sure. Is underscore’ `Object(stuff) == stuff` a direct equivalent to `typeof stuff === 'object' && stuff != null` or I miss something?
Why is this information needed on rule?
Why that? The Git protocol works way better/faster for many people, so that'd be quite annoying.
The ``$preferSource`` param is missing
It's actually a list of lengths... I should call it `multi_bulk_lengths`
セミコロンないんですけど。。。
@daithiocrualaoich is this okay to do? I need access to `premierleague` from `football/premierleague` in tag page templates.
Could be useful to include an example snippet of code here?
Do we need to explicitly call parameter-less parent class constructor? It's called automatically
why if mark > 0
self.answers.each_with_index{|item, index| item.display_order ||= index+1}
This is seems not necessary true. To me "deprecating" means "mark as deprecated", but we don't necessary have a full alternative ready yet, even if the module has this stability flag. In this sentence it seems more like "before remove a module marked as deprecated". So it's probably depends by my English, but to me it seems vague.
this check is actually unnecesary, it should be removed - we verify that api.args is an object inside validate.js
oh wow, that's very cool.  I'd never used zip before.  thanks!  yeah, just use it in one place, so I removed the const.
The docstring should probably be clear that this decorator must be used on views that take a `project` kwarg.
Why these changes? And, I think this class no more exist (renamed to SchemaParser)
Puoi aggiornare questo pezzo con i contenuti di `application.config.php` dell'ultimo stato della ZendSkeletonApplication?
```e configurare diverse `route` e servizi.```
CS: one argument per line, if you're going to have them on separate lines.
My bad. @bakura10 simply update the docs to say ```@return string|FormCollection```
This "if" is not present anymore in the source code. Anyway, the input must be a file with extensions .xml or .dbk, this is the standard of DocBook.
Do you mean both file and filter or just filter?
This setting is all that's needed to enable Emulator deployment.
I think I'd pass in two arguments: `$initializer($meta[$key], $meta)` so its possible to advocate just reading the first unless you need to do the transformation based on a different meta key.

I think this looks quite slick for basic customization:

```php
<?php
'source' => function($value, $meta) {
  return $value ?: Inflector::tableize($meta['name']);
}
```
Missing parenthesis around the condition
Just to give you an idea of how much it slows it down, it goes from 5 seconds to .2 seconds on my machine :)
Fixed in b224c9ef30c5c68d9fa4e6fdca371970c389acd3
Perhaps make the user pass the variables they want auto selected as an array to the method instead of trying to get them from the string?
logging a warning as info?
Also, you can create a 'nagios' logger and let this one log to screen and log to a file, this way you don't need to print and log....
This should be outside the if (afterward) cause we still want to update the branch, even if it's the current branch.
I think you need to make it clearer that using jboss-ejb.xml is an alternative used in when you package using an EAR or a standalone EJB jar. I'm not sure you should even mention jboss-ejb.xml as it's outside the scope of this quickstart (which uses wars).
Never heard of that. Personally I put dependencies down because it tends to be longer than <build>, therefore it's harder to find the start of <build> if it's under.  But... you're the boss :)
fully agree - I was religiously mimicking the mle-class.Rd style
Oops, thanks for the hint.
I'll change this group back on my fork and set it up on Travis ci
What about calling this just `send`?
Type datetime??

Name should maybe also be create_date, or what is this date??

What's the difference between this date and signdate?
Even if I add them on the class level?

Could you point me to a page explaining the versioning syntax or paste it here?
No need for the extra space before the full stop, MarkDown is clever.
Leave this blank (or link to a Twitter account or something)
My, this isn't good looking :-)

But I'm not sure I have anything better...
Тут он не нужен, мы его наружу не отдаем.
сколько параметров у конструктора?
i think the reason here is that there is no definition for a child with that name at all.
Try `badge_id` instead of `badge`, and see if that works any better
It's possible but I don't think it will ever happen
When we implement this For Realz, I actually think we should retain the replace-catalog! function, and supplement it with a separate add-catalog! function. I can see legitimate users for both commands.
It probably makes sense to create a _rowToComment function that transforms the row into a proper Comment object.
Too many spaces after return. Should have only 1
This is a bit ugly. Do we have to keep track of the original value inside of the HTML ?
``tpt.symbol`` can trigger side-effects (i.e., lazy typechecking), you should wrap this in a ``askOption``, i.e., replace ``List(tpe.symbol -> tpe.namePosition)`` with ``global.askOption(() => (tpe.symbol, tpe.namePosition)).toList``
I prefer to have error-definitions on one line:

```ruby
class UnknownFieldError < RuntimeError; end
```
After https://github.com/spree/spree/commit/8b3c5c7f7190a952c6b437766d7e3d7a2a73a78d this is indeed no longer needed :)
node always lowercases so this could be a false-positive so I'd change this one to `'etag'`
This was a solution for getting the sub-header partial to render the correct active 'pill' around the link the user is currently on. The sub-header uses the current url to detect whether one of its link's pills should be active. When rendering a view again with errors with the render method, rails does so with an index url, e.g. /cohabitants instead of /cohabitants/new. This renders the 'All Cohabitants' link's pill on the subheader as active on a New cohabitant page :-(. So @error is passed in when there are errors on new actions, and the sub-header uses its value to see whether the the 'All #{klass.pluralize}' or the 'New #{klass}' links should be active pills. See app/views/cohabitants/new, app/views/shared/_sub_header, and app/helpers/shared_helper for the logic.

That said, @error  isn't in the update action because there's no edit link in the subheader.

Is there a better way to do this?

:neckbeard:
А что будет если кто-то сделает вызов этой процедуры с параметром больше 100?
Надо обязательно делать проверку на диапазон больше 0 и меньше или равно 100.
И действительно в этом проекте так замечательно совпало что кол-во элементов в массиве 100 и надо делать максимум сто операций замены, но как отлаживать алгоритм? Надо обязательно вводить или константу, или через #define - длина основного массива.
А здесь после проверки на диапазон допустимых значений для параметра процент изменений, делать расчет кол-ва изменений исходя из длины основного массива и процента необходимых изменений
Не очень оптимальный алгоритм...

Так, вроде разобрался, вы заполняете сначала массив int уникальными значениями, которые присвоит великий рандом. Если выпало такое же значение, какое уже есть в массиве (что решается перебором всего массива) - пытаемся снова. При мутации 100% будут некоторые сложности, так как вероятность выпадения уже имеющегося значения будет расти. 

В алгоритме замены символа тоже полагаетесь на рандом, который может выдать подряд неизвестное количество раз одинаковое значение, что будет проверять.
Если внимательней посмотреть на мою реализацию, то можно понять, что мой метод mutate принимает не процент, а количество совпадающих клеток, в процент это число уже пересчитывается в самом методе. Отсюда и Ваше неверное толкование метода. ТЗ не прописывает, что метод должен ПРИНИМАТЬ в качестве параметра процент, там написано что он должен ЗАМЕНИТЬ процент, мой метод заменяет СТРОГО нужное количество процентов. Советую все же повнимательней посмотреть мой проект.
Переменная i используется только здесь, так что есть резон объявить её для этого цикла. Вообще, мне язык C/C++ очень нравится тем, что можно объявлять переменные непосредственно перед их использованием, это очень удобно. Pascal/Object Pascal такого не позволяет, например.
Ну это так, рекомендация, не более того.
Спасибо, добавлю проверку
This applies to a few other tests too. We can't always rule 100% of false positives but keeping separate counters should help.
I'd guess `RACBehaviorSubject` needs a similar treatment. Would you mind taking care of that as well?
Seems correct, but you've lost two "setDebug" and a quote on $clientId.
Out of curiosity, why do you think that absolute pathnames are safer than relative ones? Relative pathname inode lookup is faster, so I don't see why we have things like "./clipboard" instead of just "clipboard". As long as the current working directory does not change from /mnt/us/kindlepdfviewer I see no danger in using relative pathname.
I think downsample=None would be more consistent with what we usually do, then make your check below "if downsample is not None:"
do you need this when everything comes from raw files with the same sfreq?
I agree that it's not a good idea to duplicate functionality in two places, since it can lead to some confusion for users and some difficulty for package maintainers as it doubles the potential bug load and places code needs to be updated, etc.

The reason I think we need something like this is to maintain backward compatibliity.

However, it just occurred to me that we can actually extend the functionality of the new raw() to deal with each raw instance having different projectors, in which case we wouldn't need this code to maintain backward compatibility.

Specifically, if raw1_fname and raw_2fname have different projectors proj1 and proj2, in raw=Raw([raw1_fname, raw2_fname]) what we could do is make it so that raw.info['projs']=[], and apply proj1 to raw1_fname and proj2 to raw2_fname whenever their data are accessed (i.e., on preload or in read_raw_segment). It's not the most glorious solution, but then again including different projectors for different runs isn't that glorious. I think this would still function the same way as the C code, since you could still specify cov.save(projs=proj1) and epochs.average(projs=proj1)---not that this should matter much, since the projectors have already been applied to the data themselves. We could even throw a warning to the user when (not proj1 == proj2) so that they know this is happening, and it's only safe if you're really sure you know what you're doing. How do you think on it?
Yes because the id is supposed to be database generated. So when we supplied one, the data access layer did a hibernate merge which resulted into trouble.
Was handling deathdateEstimated just like birthdateEstimated as instructed. But I agree it is not needed. Removed it.
This is really bad i18n. Not all the languages have the same sentence constructs as English. This must go within a single translation unit. Probably a ``{% blocktrans with foo="bar" %}`` block is the best way to go.
You are right. We should set the socket to non-blocking mode, or with a very short timeout.
Small detail either way, but what I'd love the most is to use the `# ...` in this spot:

    assetic:
        # ...
        bundles:    [ AcmeFooBundle ]
        filters:
            # ...

Also, is this new note actually correct yet? My impression is that you don't need to add your bundle to the `bundles` configuration until you place a `stylesheets` or `javascripts` tag into a template that lives inside that bundle. If your `stylesheets` or `javascripts` tags are only in a template in `app/Resources/views` (even if you're referencing CSS/JS files that are in some bundle), then you don't need to add the bundle to the `bundles` key.

If I'm wrong, some please shout at me! :) I just wanted to make sure we were clear on that before merging.

Thanks!
共享内存限制域
basic's version says this is for pickling support.
Не надо. Оно только хуже будет. И вызовет кучу недоумения у пользователей.
¿No convendría usar `DateTime?` en estos casos?
mmm, si, y con AppHarbor se podría hacer un request periódico para que
revise si hay tareas pendientes


On Mon, Nov 26, 2012 at 11:05 AM, Alpha <notifications@github.com> wrote:

> In source/CommonJobs/CommonJobs.Mvc.UI/Global.asax.cs:
>
> > @@ -70,6 +74,41 @@ protected void Application_Start()
> >  #else
> >              CommonJobsAuthorizeAttribute.AuthorizationBehavior = new PrefixFromSettingsAuthorizationBehavior("CommonJobs/ADGroupsPrefix");
> >  #endif
> > +
> > +            StartTimer();
> > +        }
> > +
> > +        private System.Threading.Timer timer;
> > +        private void StartTimer()
>
> Creo que una app de consola sería mejor y más fácil de manejar y hacer. Ya
> que hay que hacerlo, ¿no preferís mover la lógica a esa app en lugar de
> dejarla en la web? Alpha.-
> … <#13b3d09a59db4237_>
> On Mon, Nov 26, 2012 at 5:35 AM, andresmoschini <notifications@github.com>wrote:
> In source/CommonJobs/CommonJobs.Mvc.UI/Global.asax.cs: > @@ -70,6 +74,41 @@
> protected void Application_Start() > #else >
> CommonJobsAuthorizeAttribute.AuthorizationBehavior = new
> PrefixFromSettingsAuthorizationBehavior("CommonJobs/ADGroupsPrefix"); >
> #endif > + > + StartTimer(); > + } > + > + private System.Threading.Timer
> timer; > + private void StartTimer() Buh, es cierto, voy a tener que
> iniciar un servicio de windows (o aplicación de consola), aunque por ahora
> yo programaría un request diario. Que opinás? — Reply to this email
> directly or view it on GitHub<
> https://github.com/CommonJobs/CommonJobs/pull/225/files#r2220688>.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/CommonJobs/CommonJobs/pull/225/files#r2221829>.
>
>
Were you trying to test user input here and had trouble?
I was thinking this could be refactored as...

```ruby
scope :since, lambda { |date| where("created_at >= ?", date) if date.present? } 
```

Then in your controller...

```ruby
def index
  #...
  @stories = Story.since(params[:date]).order(set_order).paginate(:page => params[:page])
  #...
end

private

def set_order
  if %w(score created_at).include?(params[:order])
    "#{params[:order]} DESC"
  else
    'score DESC'
  end
end
```

Then get rid of what is in your `routes.rb` file and use the `link_to` helper like:

```erb
<%= link_to 'Today', stories_path(:date => 1.day.ago, :page => 1) %>
<%= link_to 'This week', stories_path(:date => 1.week.ago, :page => 1) %>
<%= link_to 'This month', stories_path(:date => 1.month.ago, :page => 1) %>
<%= link_to 'Newest', stories_path(:order => 'created_at', :page => 1) %>
```

You may need to play with the pagination stuff and also be wary of the formatting of the date helpers (`1.day.ago`, `1.week.ago`, and `1.month.ago`).

What do you think?
Angelina is lead ATM.
Please escape
prefix with ``\``
I'm not sure I agree that this is a deprecation warning (which is hidden by default since python 2.7). It is not the case that this functionality used to work and some structural/procedural change it will mean it will removed in future versions; instead it is a warning to a user to tell them that what they have passed as arguments indicates that they are probably doing the wrong thing.
I understand the concept of this, but doing validation for attributes on initial parse and then changing the attributes seems very strange and I haven't seen HTML ever behave this way.  It seems that validation should be done when you're going to use the value.  Maybe place it on the getter?  But even then, you wouldn't want getAttribute to return this "validated" and/or possibly changed value.  It should return what was set.   I guess this brings into question the relationship between getters/setters and mapping to corresponding attributes.   Maybe getters will return validated values or defaults and the corresponding attribute will be left alone.
хех! удобно не то слово. я бы даже в Женин( @stev ) make schema sql впилил 
```
 COMMENT ON COLUMN "person"."name" IS 'КО заявляет, что сие -- есть имя';
 ```
 исходя из твоих изменений! это здорово, но вот слишком часто от программиста требуют в одной вьюшычке вот так, а в другой вот эдак. И мультиязычность затрудняет с этим ихним poedit.
Я вот еще не уверен что понял почему их два, т.е. в чем принципиальное отличие? Не забывай что default посеяли и в сущностях он есть, а вот форма рождается без него ;) Мне не жалко конечно но на prodaction версии у меня уже 13 параметров (там еще formAlias), еще 2 твоих возможно скоро прикачуют ;)
Да и самое главное -- сделать это отдельным пулом! Отдельный пулл с тестами Form у меня уже зреет.
Creating new classes to wrap every primitive type it's java like style. Why the LoggerInterface self can't contain this constants? PHP framework grows very fast, and consuming more and more memory.  And one more thing, we already have defined log constants (http://php.net/manual/en/function.syslog.php) whats the need of dups?

Also I sont see goo thing in using log types as strings. In example I need to store logs for periods of time, size of logs is prefered, so I decide to store logs type as integer.
These methods were copied verbatim from MeManagerViewerSearchPropertyProvider, which is now deleted. I can't tell if you're recommending that we resurrect this class (i.e., effectively leaving RelatedContent's code alone as you mention), or stick this method statically onto AbstractContentSearchQueryHandler -- I'm not convinced that either of these options are better than a Utility class. I think that AbstractContentSearchQueryHandler already has a big job on its hands, and these two methods don't seem to provide behaviour that is specifically related to "querying content". I do think that in the future they may find a home on some utility method in another bundle (e.g., in the Search bundle, to standardize how to specify userid's across searches), but I don't exactly know where that home is yet. The short-term goal for this decision was to avoid unnecessarily bloating the AbstractContentSearchQueryHandler.
Coding conventions: Please use camelCase
This change doesn't show up in the scss?
Ah, yeah.. forgot that I added the option of checking for existence of attribute/element in get_node_text - added this when I was doing the unit tests. Will change that.
i wouldn't call this `ab_add_metric_count`, since there it could be confused with creating a new `VanityMetricCount` record.  I'd say instead `ab_increment_metric_count`.
No I am not a native speaker and can't think of a good name here !
Are you sure ``$this->getToken()`` has the correct type as ``*`` is not a sub-type of ``string``?
This code forbids to use segments really starting with ':' and it search for ':' which is useless. Could we consider a route beginning with a double ':' for this case:

```php
<?php

if ($segment[0] == ':')
{
    if ($segment[1] == ':')
    {
        if (substr($segment, 1) != $route[$i])
        {
            continue 2;
        }
    }
    else
    {
        $vars[substr($segment, 1)] = $route[$i];
    }
}
elseif ($segment != $route[$i])
{
    continue 2;
}
```
One more case to fix up, just // Remove should do
Can you please be more precise on these parameters, like so

```php
<?php
// Here 5 and 3 are "owner" type.
$userGroup = 5; 
$userType = 3;
$phpbbuserman->addUser('sf2_username', 'hashed_password_from_sf2_user', 
    'email@email.com', $userGroup, $userType);
```
> I'm not even sure if this really is a bug or is a feature? Because maybe you want your date localized?

It is a bug. Because here we are talking about serialization. And serialization of date into a standardized format when doing this serialization. And you don't want to localize this, because you want to use this serialization to transport the datetime value from server to the client. If you want to localize it there, you do it in JavaScript there.

> And I think waiting for the Tastypie to approve this can take a while, so maybe this should be in another issue.

I am not saying that it has to be approved. Just that you make a pull request. Furthermore, Tastypie does not look like a project where they are quick at pulling things in, just look at the number of pull request pending.

So, for now I think you can just make a pull request for Tastypie, then in requirements.txt you provide URL to your repository/branch with that bugfix, and here where you are doing your own serialization, you can use that format function directly.

Do you think we have to wait that bugfix is pulled in? No. We are already using some libraries which I have fixed and then we are installing it from my forks. You do the same now.
One more. :-)
Helper functions for `update_all_horoscope` also move to tasks.
Not really a need for temporary variable.
If you want to compare with `None`, always do `if user.birthdate is None`.
Also, we want to create a new one, so even if old one exists, user should get a new channel id.
`<br>`? This often means you could simply use `div` and have a newline effect. No need for `<br>` to influence how something is rendered.
you don't need check for owner->HasAura(darkEssence) and owner->HasAura(lightEssence), you still have this aura
same some lines below with unleashed dark/light
This isn't the default way to disable the XML documentation requirement, is it?
So true, I will do it like that ;-)
Well not really, since he copy paste this part, it should state `2010-2012`
Variables should always represent their MIB counterpart. In this case: brcdDot1xAuthPortConfigPortControl
According to the handbook:
"Any simple, non-script font may be used, and this same typeface must be used throughout the thesis."
Utility also lies with the specification of the conventional name of the protobuf generated static `getDescriptor` method. No similar util method seems to be exposed within protobuf APIs which defines this name, besides the javadoc for the `Descriptors` class.

I'll clarify this in the javadoc.
thats right. didn't notice the annotation in the other test.
I'd keep service bus as two words.
override the function, do not delete it
There are several whitespace changes. Can you please submit these in a separate pull request?
> I did a bit of testing to confirm and [super canBecomeKeyWindow] was always YES.

Strange, since borderless windows (see the [QSBorderlessWindow class](https://github.com/quicksilver/Quicksilver/blob/master/Quicksilver/Code-QuickStepEffects/QSWindow.m#L477) supposedly [don't accept key events](http://www.cocoabuilder.com/archive/cocoa/97238-makekeyandorderfront-and-nsborderlesswindowmask.html#97236)

Thanks for the extra testing :)

> Hopefully you got it via e-mail, because it never showed up here.

No :(
this looks wrong, there is no more MultilangContentBundle anymore
Are you intentionally swallowing the exception here instead of re-throwing it? If so, why?
Or alt=1-alt; since the original value of alt is guaranteed to be 1. Unlike the above code, this code breaks for values of alt that aren't 1 or 0.
It's a new definition.  In particular, the inverse of the old definition.  CDD gain is normally e-/ADU, so we're ignoring the quantum efficiency and such, but basically this new definition is the normal definition of gain.

You had the definition of gain correct in CCDNoise, but when I had added it here previously, I got it wrong.  In fact, I almost pointed out "your error" when I noticed it in CCDNoise recently.  But I checked wikipedia first and your definition is right, and what I had in my head was wrong.

Anyway, I switched all the usage of gain in the code to conform to this definition.
maybe as template files that don't take any parameters and are just dumped back.
Does this now call stop asynchronously, rather than previously doing a blocking call?
Should we do a `.getUnchecked()` as well? Or return the task?
I'm not convinced by the CLI syntax for these extra commands (that aren't in the spec).
e.g. should it instead be something like `brooklyn list catalog-entities`.

But let's come back to that as really want to get to merging this pull request...
+1, will do that.
Could use `Byte.parseByte(addrSI[k])`
The points of Watermelon is:
 - Shows that It can run both on JSB and HTML5
 - Shows that It runs super fast on JSB  (it runs at 60 FPS on iPad 1)
 - Shows the best practices of cocos2d + chipmunk in JSB.


The HTML5 scroller code is good for HTML5, but a very bad example for JSB.  Users are going to copy & paste the code of our examples, and we need to teach them how to code efficiently for our platform.


So a comment like this one could be useful:
```js
// scroller code
if( platform == html5 ) {
// This code runs both on HTML5 and JSB
// But since JSB runs on top of OpenGL, there is a much more efficient way to create scroller (see below)
   ...html5 code here...
} else {

// JSB + OpenGL code here
}
```
plone.folder registers an IExplicitOrdering adapter for IOrderable so the folder can be ordered. Pretty sure there was a reason it was added.
encore une fois "these industries"...pas clair
I rewrote auto to cocoa.id.
I would prefer `key in obj` behaviour.
Still there is an `email!`. It should be `@resource.email`.

It is a good practice to test the code (at least with a request from the browser) before a commit.
That didn't change in this patch.. But yeah, you are right.
Use the error variable?
I didn't want to change the interface of the API in my tidying, I was going to merge the two methods and add another `alias_method` here but they seem to be doing slightly different things.

I'd probably leave it as URL though because things like `fooXml` and `barHtml` instead of `fooXML` / `barHTML` always looks a bit weird to me. Although to be honest, camel cased naming isn't particularly ruby-like anyway.
Regardless of what HTML5's allowance in this case, we are a public institution and need keep some important things in mind.  

Screen Readers shart with multiple H1's.  Because this mobile app will also be accessible via desktop browsers and whatnot, we need to pay attention to  things like this: http://www.456bereastreet.com/archive/201106/on_using_h1_for_all_heading_levels_in_html5/
OO --> object-oriented
It looks like `post_name` is always `name`, so that variable isn't necessary.
that would maybe be more explicit but also require much more code. Currently a Requirement is immutable that would also get lost. Do you really want me to do that?
Put advertisement into update function doesn't work.
Maybe better we change this to
let mbox = aElement.getTag("t:Mailbox");
Surprised it wasn't 42!
Tests should actually go first because it's more specific, prevents the autoloader from looking in the first entry for tests.

Also, we should nest this one more so we don't interfere with webapp test namespaces.

`AllPlayers\Tests\Client`?
In this method undeclared vars / functions are used which will clearly end up in a runtime error.
Necessary to have a Makefile.osx per target?
Зачем здесь close?
Просмотр в total comander, Блокнот, CodeBlocks сказали что это 1 табуляция, т.е. 4 пробела, я не знаю почему браузер отображает это как 2 пробела... Вы можете пожалуйста проверить пока так...
Обращение по индексу? Хрупкое решение.
Я так понимаю, что массив используется для того, чтобы хранить одну ссылку? Для этого логичнее использовать AtomicReference.
Didn't we just pull `message` off `reason` above?
What problems can it lead to?
I'd recommend using already defined constants for public access in `PublicAccessType` that would help folks knowing how to use the SDK
i am not sure, but why te twig bridge is required ?
there is no form, neither use of path()
We should remove the # here.
We should use triple double quotes(" " ") when writing docstring, according to http://www.python.org/dev/peps/pep-0257/#one-line-docstrings
sure, fine with me.
Thanks! I included your suggestion in commit fb79a0d.
That should not be to hard if I can choose alpha. Otherwise I don't know. I'm not sure if one should not conciser the sequential strong rule aka enet_path use case at the same time.
Remove the lines above. Instead, could you provide an example in a separate file?
I'm not sure if set() is the right container for the ever_active_set but I need something that can grow dynamically.
я в себе додав, а push забус зробити (
Hmmm...I didnt think I changed that at all

--Joe Burgess
CMU Information Systems '12
(703) 402-9206
On Feb 19, 2012 10:44 AM, "Mickey Reiss" <
reply@reply.github.com>
wrote:

> > @@ -7,9 +7,8 @@
> >  #  invoice_id :integer(11)     not null
> >  #  memo       :string(255)     not null
> >  #  category   :string(255)     not null
> > -#  price      :float
> > +#  price      :integer(11)     not null
>
> This downcast of price from float to integer is scary
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/mickeyreiss/abtt/pull/19/files#r465413
>
Consider splitting this parse routing into a separate function.
Should also specify that we value should be a Number.  String currently also work but only if not followed by unit specifier (either we have it ignore the unit specifiers like for iOS or update the doc to specify that it only takes a number).
Are you sure that's the right value? I can't find anything in the docs. Perhaps you could leave it with the default constructor and then when setControl is called you can do the following (forgive my formatting):
```
if(controlEnabled_) {
    if(!disabledBackgroundColor_.isValid()) disabledBackgroundColor_ = container_->getBackground();
    if(!backgroundColor_.isValid()) backgroundColor_ = container_->getBackground();
    else container_->setBackground(backgroundColor_);
}
else {
    if(!backgroundColor_.isValid()) backgroundColor_ = container_->getBackground();
    if(!disabledBackgroundColor_.isValid()) disabledBackgroundColor_ = container_->getBackground();
    else container_->setBackground(disabledBackgroundColor_);
}
```
That way we use the container's default instead of making up our own.
what happend if user is not save because not pass a validation?. You must perform and: 
else
   render 'new'
end
It's a shame that the `Markup` monad doesn't have an `Eq` instance... so I have no better ideas here :( We could use `blaze` to generate the expected tree, and then say `render expected == renderBullet bullet`?
Sounds good to me! Will be working on this the next few days!
imaginary numbers? ;)
nope, good catch.
Nothing. As is what's going to happen on Unity Ubuntu systems.

This is just a launcher that gets added to a list of possible things you can add to your launcher. It's only added if the directory is there (which I think it's only Linux) and it's not added automatically.

Can you check on MacOSx if ```/usr/share/applications``` exists? And what's in there?
This also needs to be protected with a rowarraylock, otherwise it could spill after index is freed but before index,indexCapacity is updated.
s/common_package/common_package_name/
Should this be `...to run fallback update tests`?
Please place sys to the list of global packages
This needs to be updated to ArrayUtils (since I merged #880 earlier). See more below.
this one might be miss named :P
What about case when an exception will be thrown by a next node in chain?
`start` relies on the fact the `install` does a package. This script should be modified as well
remove all hard coded ip addresses. please use properties.config
We could even revert this change but I would leave it in here so we avoid confusion in the future.
No, this module and ssh_creds both fail with the following stack trace.

```
[-] Post failed: NoMethodError undefined method `file' for nil:NilClass
[-] Call stack:
[-]   /code/metasploit/lib/msf/core/post/file.rb:321:in `_read_file_meterpreter'
[-]   /code/metasploit/lib/msf/core/post/file.rb:221:in `read_file'
[-]   /code/metasploit/lib/msf/core/post/unix.rb:64:in `enum_user_directories'
[-]   /code/metasploit/modules/post/multi/gather/ssh_creds.rb:42:in `run'
```

The next time I tried to run the post modules, I did not get a stack trace at all. Instead, the session died,

```
*] Finding .ssh directories
[*] 127.0.0.1 - Meterpreter session 2 closed.  Reason: Died
```

I can remove 'meterpreter' from SessionTypes. Same should be done for ssh_creds module.
oh LOL, well that's easy :)
I'm in favor of removing the `build_` prefix above, but I'm -1 on switching to `_up`/`_down`. I'm assuming `_expand` --> `_down` and `_reduce` --> `_up` (since a pyramid reduces in size as you move up), but this could be confused with `upscale` and `downscale`. Also, I think `_expand` and `_reduce` are more explicit.
No advantage to xrange.
polylines are organized by width and outlineWidth. This is done using a map. This is needed because whenever the update method is called, it needs to make sure the renderstate for each vertexArray(created by the polylines with the same width and outlineWidth) has the correct linewidth set for the correct renderstate(rsOne, rsTwo and rsThree). The render method then can draw things correctly. The array would be faster, no doubt, but there still would be two data structures being used.
If this is a bounding volume, shouldn't we name the argument `boundingVolume`?
I think this is optimal if the common case is that axis is already normalized. If not, the magnitude is computed twice. After talking with @shunter, a better approach would be to check for a magnitude of one in the normalize method of Cartesian3 and always normalize here.
> Given get2DMercatorYPositionFraction in CentralBodyVS.glsl, couldn't we create a general czm_ GLSL function?

Excellent idea.  Done.
Any reason why implement this by yourself instead of using the Intersection.js?
Is there a rationale for continuing to use preprocessor definitions for this, vs. `[[UIDevice currentDevice] userInterfaceIdiom]`?
in builder.py it's indirectly set to 'development' via deploy_type var.
I checked the function impl and it mainly excludes non-production modules from production builds. So technically we could even specify None.
I'm open to your suggestions.
In the next PR update the issue is solved anyways by removing the property in question from the cfg file since it really shouldn't be a user config item anyways.
Could you explain the purpose of this method on Mobile Web and thus why it is supported, please?
As in the previous comment, this queries the button and the if check is querying the canvas.  I then pass the string name to restoreContent because I need it there anyway to replace the text in the button element.  Can I extract a string name from the value returned by query?
Do something like: ... == 38 /* Name of key */ || ...
Alternatively, use constants.
months*
is there a reason to depend on py here rather than mkdtemp() in python's stdlib tempfile module?

http://docs.python.org/library/tempfile.html#tempfile.mkdtemp
Only JUnit is supported. I would have preferred TestNG (mainly out of consistency) as well, but in this case some more dirty work is needed.
wfm! :D
just now the id is generated in the EKB. TBH I don't know whats the better way here. I'll think about that
the Poco docs are vague about `toString()`, specifically what happens when a Path's `isRelative()` returns true. vagueness means one can't make assumptions about it. again '/usr/local/bin' == '/usr/local/../local/bin'. and if i have a symlink, `/home/damian/linky' perhaps == '/usr/local/bin'. 

to be completely robust we can't simply compare strings. 

but, if we choose to ignore the existence of symlinks, i think this can work if all the paths in question have `.resolve()` called on them.
is there any way that we can not rely on something being in the 0th index?
Time to remove the temporary developer stuff :-)
I like "trust proxy", more terse. :)
This name and the name above sound very similar.

这个名字跟那个名字一样！
Actually, I did not rewrite this, I think I commented out the whole calculation for now.
Another hard coded directory.
Good catch; this is just a leftover exception. Fixed.
I think we should call this buildQueueService or, better yet, createQueueService to align to node.js
Renaming `config` -> `configuration` is unnecessary and also breaks existing client's assumptions.
Is this WARNING_DAYS different than the waringPeriod on entitlementCert orders? (aka entitlement.getOrder().getWarningPeriod()
as used in rhsm_d.py)
these routes should be in a 'users' scope block
Das Fläg würde dann obsolte, da $grade = null  AutoBewertung bedeutet....
should it be closing after this?
```public string Serialize(object obj)``` ?
I think the only relevant assertion for this test is the one about the steps.
why two functions doing the same thing?
Not sure what is the purpose of this class that has 2 no-op methods
Ok, actually should be an easy fix
Right and there is nothing we can do about it once we gone dynamic since it could change on every request
I believe we could make this package-protected since the only subclasses are in the current package. If so, we probably don't even need to deprecate it in the future, we could just modify the JavaDoc here to mention that it's not public for that reason and will be removed in 3.0 refactoring.
Ok, I'll add nanoseconds, that would make it impossible. But I really want to avoid UUID
A-ha! Now I see your opinion about 
> case insensitive manner
However, what is the reason to wrap `FileExistsMode.values()` into `List` and don't iterate just over this `FileExistsMode.values()` 
and also don't use below `StringUtils.arrayToCommaDelimitedString` for the same array?

And out of topic: for some time I stopped getting GitHub notifications. Not only on email but my notification bar is empty too... :-(
We shall leave this to some native English speaker. :)
`analyzes HTTP request` -> `analyzes the HTTP request`
Done -> `google_authentic?`
the value is that index doesn't mutate...
other than that, no.
change it if you desire.

I don't assume what the compiler will do or not. also that code is extremely easy for a compiler to optimise as it has no state. i haven't profiled the code, i don't know how valuable that area of code is, i assume it's execution frequency will be measured in seconds, so the overhead isn't important.

personally i find that defining a variable and not assigning it to be confusing.
запятая после «с файлами»
Yikes! fixed that missing super().
Didn't know about `latest()`, nice to learn something new. I'm not sure it's really a big change here. It's already a value-list, and taking a slice gives the desired `SELECT id FROM ... LIMIT 1`

There is a `test_last_child_doesnt_delete_parent()` that came with the merge I did.
I didn't write other tests yet, if you see something let me know!
Let's stick with the font based icon set instead of loading images. We currently have all this icons available http://kyleledbetter.com/icomoon/
But `%r` creates something like `<Person>` no?

And what is that *d* in *not be d in a*?
I was just running it and when I closed the other end unexpectedly I get 

[SchedulerProtocolet|INFO|4:06:14]: A message has been received
[SchedulerProtocolet|INFO|4:06:14]: Message dropped due to invalid header version
[SchedulerProtocolet|INFO|4:06:14]: Parsing header null
[SchedulerProtocolet|INFO|4:06:14]: A message has been received
[SchedulerProtocolet|INFO|4:06:14]: Message dropped due to invalid header version
[SchedulerProtocolet|INFO|4:06:14]: Parsing header null
...

Repeated multiple times

BufferedReaders readLine can return null, not sure though it might just be a windows thing.
FOllowing convention of other winston sub libs
Yeah, I believe that is the case.
I forgot to mention - then hook this option up to the command line.
You could use a do-while loop in this case so that you wouldn't have to use a break
should be <ol role="spinbutton">
Ah, gotcha - thanks.
This was from my previous commit, it can be ignored.

I probably should have branched better.
Good idea. I've added the blackberry.io.file.saveFile method to this example.
My understanding is that those are iOS specific and are going to move to the Ti.Geolocation.ios namespace as part of https://wiki.appcelerator.org/display/spe/Geolocation+platform+additions Since I am already implementing that spec, I wanted to avoid sharing constants that are going away.
KrollProxySupport represents a Proxy, so we can use that language in the description.. i.e.

`Set the Proxy associated with this object`
This is a whole lot of magic, right here.  It should have some comments to explain what it is all about.
Default typo.
hu, big big switch, array with method call wouldn't be better ?
Probably this should be an agreed version, for example jackalope/jackalope would define the current API as 1.0.0 and would require a jackalope-transport 1.0.0, then the packages would provide that version if they do indeed support it. dev-master will work too, but it's a bit blurry and risks being forgotten.
My thinking is yes because the baseline is already protected by tcp wrappers, but we should chat about it.
Добавьте данный функционал в исключение nav.noBlob
nit: `def __init__(self, phrasesFile):`

Let's stick to PEP-8 for the most part.. http://www.python.org/dev/peps/pep-0008/
perhaps this need to go now
We could...but should we make this change just to satisfy the unit tests?
I think setSessionFactory is a better place to set this, because it will be run only once when the bean is created. The hasDateRetiredColumn field doesn't need to be static as well, because it's a singleton bean.
``$this->getMock('Symfony\Component\Routing\Generator\UrlGeneratorInterface')`` instead of mocking the implementation
This surrounding if is not necessary. Plain `(= (mod n divisor) 0)` already evaluates to the wanted boolean value
Definitely ignore all the other extraneous changes.  It's really annoying that the metadata changes between instances can't just be ignored in some easy way.