labofsahil/github-event-dataset-2012 huggingface dataset:
This addresses the issue of force_clear_output_dir. I talked to Dave Marin about it. The idea is that you can debug jobs by forcefully clearing the output directory when using a flag. Useful when you are testing out jobs.

Shiv

On Feb 23, 2012, at 5:53 PM, Steve Johnson wrote:

>> +           # Don't even bother running the job if the output is already there,
>> +           # since it's costly to spin up instances. Similar logic to checking for presence of input dir.
>> +           # In this case, we check for the absence of the output dir.
>> +           if self.path_exists(self._output_dir) and not self._opts[FORCE_CLEAR_OUTPUT_DIR]:
>> +               raise AssertionError(
>> +                   'Output directory %s already exists, this will cause the job to fail midway!'
>> +                   ' Enable the %s option to force delete output-dir.' % (self._output_dir, FORCE_CLEAR_OUTPUT_DIR))
>> +           if self._opts[FORCE_CLEAR_OUTPUT_DIR]:
>> +            if self.path_exists(self._output_dir):
>> +                self.rm(self._output_dir)
>> +                time.sleep(WAIT_FOR_S3_COMMAND)
>> +            if self.path_exists(self._output_dir):
>> +               raise AssertionError(
>> +                   'Output directory %s already exists, and could not be deleted on a force delete!'
>> +                   % self._output_dir)
>> +
> 
> Some part of this may be necessary, but I'm generally confused as to the purpose of this block of code.
> 
> --- 
> Reply to this email directly or view it on GitHub:
> https://github.com/Yelp/mrjob/pull/378/files#r483514
Well since non-objects are returned by value couldn't we have the segment and rsegment methods do the n - 1 and when a caller calls the segments or rsegments accessor we could create a new array that actually starts from 1.

Something like:
    $oneIndexedArray = array_combine(range(1, count($this->segments)), array_values($this->segments));
    return &$oneIndexedArray;
Вот если бы было бы не 100 элементов и если бы пользователь задавал бы количество елементов в масиве вот тогда бы мы такую проверку и организовали бы, а поскольку у нас 100 элементов и проценты мы задаем сами, то тут уже другой разговор.
Можно углубиться в проверки. Если нам передали не число (20 или 30) а проценты (20%, 30%). А если нам передали не целое число а типа Float ('19,5%')... + еще кучу если. Пока у нас лабораторные условия. Проверки я думаю следует включать такие если большой проект и работают несколько людей над проектом или есть поступления данных от пользователей.
Да. Условие задачи таково, что от метода требуется **заменить строго Х %**. Проверить корректную работу метода довольно легко: выводим ДНК до мутации, мутируем 100%, снова выводим ДНК. Если метод работает корректно, в каждой ячейке должен быть иной от исходного результат. Иначе метод заменил не 100%
Ага, и тут еще усложнится логика — сколько элементов мутировать
разве автоматическое освобождение памяти не освободит NUCLEO_COUNT  число элементов?
The purpose of `sorted` (sort by argument name) is to return the arguments in a predictable order.
It's more idiomatic and should be faster to use `+[NSValue valueWithNonretainedObject:]` here.
The `Party.all` call should be moved to the controller.
>if you still prefer it gone I'll remove it.

Please do so.
funciton -> function 
remove "the sources"
if you update to the following this will work:

```ruby
assert_raise ActiveRecord::RecordNotFound do
  Post.find_by_title! 'non existing'
end
```
最新的英文文档有 rev 属性，请对应加上。其他的文档也是一样。谢谢
Where? (hint: URL)
node.delay and node.duration might be better here?
сделал. 5 поставил
If you want, after the ros.js pull request is merged, you can reference rosjs/dist/ros_bundle.js and not need to include eventemitter2 and ros.js. You can also [link to eventemitter2's raw file directly](https://raw.github.com/hij1nx/EventEmitter2/master/lib/eventemitter2.js).
I'd rather you used ActiveRecord to limit the number of shows returned.

```
Show.where(day_of_week: user_input).each do |show|
  puts show
end
```
`array('class' => 'show')`

A new feature ?
we should check if the function exists in the delegate before invoking it. perhaps some users won't implement this function
@jcmuller It feels strange to have modified the signature of `define_cattr_methods` just to get the boolean method and passing in the same value for both params to `define_getter_variable` some times but not in all cases. I thought that you'd get this kind of thing for free if we instantiated the settings hashes from yaml as [Hashie::Mash](https://github.com/intridea/hashie/#mash)
Ok, well it's causing a test failure, so something has to change for it to merge.
Let's update the comment so it's not left stale
In my defense, I had been using some debug logs while I worked on this.
+1.

Sent from my mobile phone

On 30 May 2012, at 18:36, Sanne Grinovero
<reply@reply.github.com>
wrote:

>> @@ -143,7 +144,12 @@ private Object handleAll(InvocationContext ctx, VisitableCommand command) throws
>>                   // and they not really exceptional (the originator will retry the command)
>>                   boolean logAsError = !(th instanceof StateTransferInProgressException && !ctx.isOriginLocal());
>>                   if (logAsError) {
>> -                     log.executionError(th);
>> +                     if (th instanceof WriteSkewException) {
>> +                        // We log this as DEBUG rather than ERROR - see ISPN-2076
>> +                        log.debug("Exception executing call", th);
>
> rather than slowing down the process for such a minimal change, I've merged it as it's correct and solves the issue.
>
> If you think you agree that we should removed the log or move this logic into the _logAsError_ variable, that can be a different push.
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/infinispan/infinispan/pull/1151/files#r901868
Shouldn't this close be on a finally section for remove?
Style: explicitly compare against `NULL`, and wrap the entire ternary expression in parentheses

See https://github.com/github/objective-c-conventions#expressions.
This should be of type `GTDiffFileFlag`.
System.out.printlnは使用しないでください。
m11/AndroidUtilsのLoggerクラスを使用してください。
Pedantic: to be consistent with the majority of the rest of the documentation, US English spelling, please.
I know this was in snippets but I don't like it so let's nuke it :)

We'll put the assert into the test as we do with the other test suites.
yep we can merge them 
I will update the pull
yeah as @w00t said, no problem I will
good suggestion @elemoine will incorporate
+1 : `if (! isMiss)` is less readable than `if (! isAvailable)` (avoid double negatives)
These `{box}`es should have size declared.
Sweet, so maybe just a mention of that in the docs and we're gold.
`mk-timeseries` is unsafe in the presence of missing values. We're using `consolidate-timeseries` now, which can handle missing values appropriately.
use _.isUndefined
Judging by the `sakai.api` namespace, I'm guessing refactoring of this file is still pending? Just curious because lastName / firstName is no longer valid.
Can the above be translated? If not it should be removed from this bundle to avoid duplicates.
@dooremont Can you translate this?
@gsilver It seems like this line is an exact copy as the one above it
The encrypt*() methods are not following our coding conventions (camel case) - Andy, can you please fix this?
This conditional can't run because children is always undefined?  Should be children = this.get('childViews')?
Jo takhle, uz chapu, jak to myslis. 

No jo, to by bylo asi vhodnejsi, mas pravdu. Ja nad tim planovacem zas tak moc nepremyslel, proste jsem ho jenom nejjednodusim zpusobem predelal tak, aby vyuzival timer.

Klidne to tak udelat muzu, jestli ti to pomuze. Protoze ale ty ten scheduler predelavas podstate vic, tak by mozna bylo lepsi, kdyby sis to udelal podle obrazu sveho, nez to tahal z nejakyho myho commitu. A pri zaverecnem merge se pouzije tvoje verze. Ja to pak uz jenom zkritizuju :)

Ale jak rikam, klidne to predelam, jenom dej vedet.
Done here : https://github.com/aoduor/Ushahidi_Web/commit/9e3a3d74651fef9439ea2cda0ce6939878cb32cf
why should you not reset if you are not collecting data?
Is this the right default?
You can't just copy+paste the wrapper code like this and expect it to work. useBaseDir isn't defined. You need to pass "DATA" as the second argument.
That's a nice separation; +1 for `.art-connections` _and_ `.art-exercise`
It's implementing an abstract method, so yes, I'll add override. Seems not to be needed here though, as no implementation is hidden.
Are you sure ``$validator->getStrict()`` has the correct type as "Boolean|integer" is not a sub-type of "Boolean"?
I see that this is add a small overhead when runtime info doesn't used. As well for splitting tests to groups we use more complex strategy with those changes. I hope that those overheads could be eliminated in more broad refactoring.

For now, I like you changes, because they do not spread isolation feature through several files an parallel tests parts.
compare this code block to the one below. How are they currently being parsed?
This todo is still valid. Although you're visiting the descendent DOM nodes now, we aren't iterating over all the elements matched within this jquery object. Consider the case of $('img').render({}) -- No img tag contains anything else, but the jquery object contains many nodes
Isn't this supposed to be file:// ?
There is the same, if want to use `i18n` we shoudl not fallback to general view. I guess
OK. I will check this later. Please fix the dependency on the map.
Nope, doesn't work :-)
Are those functions used anywhere? I don't think there is a reason for them to be in the templates anyway. This should go somewhere else (to Facebook API code or to User class methods).
Import only modules!
Spaces around arithmetic operations.
That values you have computer are still in the bounds of the displayed map.
Please move error_messages for this error to this class. There is no use of having it somewhere else.
Nope this was Ubuntu trick. :) It happened by accident. But I set git configuration to ignore mode changes so I don't know why it was there.
We have like:

```
<input type="checkbox" id="alphabet_order" /><label for="alphabet_order">A-Z</label>
```
initial page -> initiator page.
Could you be more specific? I think you'll have to run the tests. Basically return to the webroot and have phpunit run through the testserver. Adding this to the tests, however, is not the problem. The problem was a complaint that the AssetManager didn't work on php 5.4 test servers. So I'm unsure on how to test this.
Looks like there is a typo here, I don't think this line should be changed at all.
How about adding something like `addStepHistory()` or `addStepToHistory()` to `ProcessContextInterface`?
have you mistaken?
I guess we can't predict the optimal size to initialize the ArrayList at this point?
> To limit the memory consumption of the precious heap space you can activate a passivation or an eviction policy; 

what now _passivation_ or _evication_ and if it either of them what's the difference. I find this unclear (remember I am also a Infinispan novice ;-))
We should really slam home the fact that the literal is *strongly* preferred
Hmm, I could go either way. I think I'd side with simplicity and vote for removing the boolean and letting users implement that in their visitor (as a boolean in the constructor perhaps) if they need it.
I think it's better to remove it
yeah that's better, will fix
If we added description for the optional parameters that would make the API header comment very big. The best thing for that is to open the optional parameters class and read the comments of their members there.
The method `this._service.get_request_context(this._service.CONTEXT_TYPE_CRAFTER)` should IMO return a context of type CRAFTER. The according method should IMO take the returned context as argument, e.g. `var crafter_ctx = this._service.get_request_context(this._service.CONTEXT_TYPE_CRAFTER) ` and to remove it `this._service.remove_request_context(crafter_ctx)`.
Just call this ngx_http_pagespeed_get_query_options to keep names aligned?
This change seems unrelated
keep it sparse ?
The docstring should be updated then, and state what the function is doing.
This could use a class-level comment.
Doesn't `Float#round` use 0.5 as the cutoff point?  Why do you say it always rounds down?
Well , partly true - cluster is in textmining/datamining clustering has a different meaning. But you're definitly right, that there have to be a link to the google documentation
if you don't want to merge the pull request I based my development on I can do a git rebase to remove 'em but I need a new branch and all conversation we've had in this pull request won't be on other one. but if you gonna merge the other one having those commits in this branch won't cause any harm. also doing git revert is not a good idea to have 'em removed from my branch (it may cause these commits get removed from master after merging my branch)
Please follow the coding style. https://github.com/ArchipelProject/Archipel/wiki/Developer%3A-Coding-guidelines

- put space between "=="
- use double quotes
- do not put space before ":" (`if bla:` not `if bla :`)
You don't need vnc.pem :)
over excited deleting. will fix.
It's for readability, bro. How else would you be able to quickly scan and modify files? You need to learn a lesson from DR ZERO AND MR ALEX7.
After reading through the rest of the source code this particular line of code seems more constant-ish (uppercase with underscores)... anywho
One of the points of this (#165) was to warn about a significant amount of flux missing off the edge of the image.  Should we add that here?  Or should we leave this functionality as our way of letting the user check for it themselves with whatever they decide "significant" is?

Also, do we want to have draw() do the same thing, so the outputs are parallel?  As Gary pointed out in the comments to #165, it's not as useful for the regular draw() since flux outside the image can be folded back onto the main image.  But it might be nice to have both functions return the same tuple, rather than have different signatures.
I agree that a note about the approximation is useful, and whiel I was at it I switched to 0.999 and 1.001.
we are creating a campaign now, so how can the template exists?
I don't think the id has to be exposed to the user
i think you're right, we modify flags, but not arguments passed to invoke in this way.  but not sure.  caller doesn't care if it is mutated.
I understand. I will change it to cast.
Should be `JobDescription`.
I concur with Chris on this one - the setCheckable is part of what is needed to create a toggling pushbutton in Qt.
This hard-codes the realm which used to be in settings. Do webtrends things change often?
This must be in the controller. Please move it there.
Scuze, nu inteleg exact la ce te referi
No worries, Jose: what do you suggest as an alternative for supporting
multiple types of hardware coming from multiple vendors, without requiring
to touch the GCS? I'm not sure at all my architecture is the best answer to
this problem, so if you have alternatives, please share :)


On Tue, Dec 11, 2012 at 1:05 PM, PTDreamer <notifications@github.com> wrote:

> In ground/openpilotgcs/src/plugins/boards_openpilot/coptercontrol.cpp:
>
> > @@ -0,0 +1,71 @@
>
> "Board configuration panel for instance? Like the pipx configuration?
> That's not possible to put into a config file, and adding it to the xonfig
> gadget is just dirty..."
> It is possible to use ui files at runtime, and if used with the object to
> widget relation framework it would just work. Also if using qml the same
> goal can be achieved.
> I'm not going to turn this into an argument. For the record I'm against
> this infrastructure, but it is 2 against 1 so let us continue.
>
>  —
> Reply to this email directly or view it on GitHub<https://github.com/PhoenixPilot/PhoenixPilot/pull/79/files#r2384699>.
>
>
Достаточно одного параметра типа Closeable.
These will all be called at parse time, so there's not much point in the defineLazyGetter. If we're still stuck for time, we could fix this.
Then again, bugs crop up every now and then where estimators that are supposed to handle any sparse format turn out to only handle CSR. It's a good defensive strategy to produce CSR by default (and it's unfortunate that `sparse.hstack` doesn't do this already).
why the splice here?
Il faudrait idéalement englober tout ca dans une transaction. Mais crée une issue pour ça.
should merge into one addAttribution call?
Ok. Not sure, of other options, will explore.
OK, I opened #1405 to fix the `TEST_OUTPUT` problem.
https://github.com/D-Programming-Language/dmd/pull/1170
Fair enough. Could use an empty line to separate it though.
Do we need to put this file in repo?
I don't think we need a repository in the example :)
Not sure about this either, but it's not related to the PR. @bakura10 any idea why we're instantiating the resolver in here?
I've written my own fgetln implementation, see updated diffs. Hopefully it's OK and threadsafe.
Still prefer to keep it simple, especially since the logic for how the revision to update to is calculated may well change as a result of other issues & pull requests, such as support for bookmarks, tags, explicit changesets, subrepos, etc. If there is an advantage to partial cache updates and it can interoperate nicely with other potential changes to the plugin, that should be a separate pull request - it does not belong here.
Let it be `datetime` instance objects. The template should be responsible for how it wants to display the date format.
Put it to private section below
If Zend\Uri\Http or Zend\Uri\UriFactory are used anywhere in the code, please import them; you can then use just the classnames or aliases you use when importing.
you should also mention that package names are case insensitive
why did you take these away?
Remove the word "linked" - it's clumsy and not needed as the link is right here.
You should be doing a hasOwnProperty(key) check in here.
This doesn't support the new `attrs` features, it should. The same is true for `EmailColumn`. We should support specifying HTML attributes for the `<a>` tag.
We do not put the reason of each piece of code in the code. They belong to the spec review/design discussion.
I just resolved conflict issue in D8LoginPage. These are just cosmetic changes
I understand the reason for using @before it's wrong annotation to use. We are using maven and testng and this is not a testng annotation. Secondly, I think for a timeout @beforeclass is actually what you are looking for. If your goal is to have the timeout run before each test class is run then you need to use @beforeclass.
Alright, since Eclipse-CS seems broken enough to not allow enough useful configuration on package import order, it's probably time to harmonize around IntellijIdea. Do you mind taking a look at how it's configured when I get in to see if there's anything I should be aware of?
OK, leave as is for the time being then.
can this be removed before merging
The mobile vesion should be 1.2.0 and the jquery version should be 1.8.2 (lines 7-9 need to be updated) Thank you
This constructor doesn't seem to be used anywhere. (Also, `MessageExpr` supports variadic arguments.)
Oh, "screw"
What about the function `_skimage.transform.rotate` as a wrapper around SimilaryTransform and warp?
Why did these change to double quotes?  Style guide says to prefer single quotes.
tnx, fix a typo
As we discussed, we can also do more tightly fit bounding spheres for all sensor types by adjusting the center point.  For complex conic, we need to consider the outer angle, which can be greater than 180 degrees.  For custom sensors, we can just put a sphere around the computed points.

This will be a nice optimization because sensors tend to be large, so a loose bounding sphere would lead to lots of drawing in other frustums.
This can just initialize all the indices to zero directly, rather than creating an array and throwing it away.
use wrench.js here instead.
Is this really the property name? It's not very descriptive.
Do you mean the "properties" parameter?

If so, the answer is that we don't support platform-specific parameters in the TDoc format, or in the JSCA format we use for content assist.
Naw. People can Google them. Besides, nobody is going to read this file.
OS X specific, should either make it generic or include paths for Windows and Linux
Good point. I think somewhere between 1 hour and 8 hours would be a good threshold for freshness. In that time you could hop a plane or drive far enough to significantly alter the declination. And if the app can't get a fix once an hour, either the fix is unavailable, or they aren't trying very hard.
Attached = Attached to the DOM.
Mucho better-o!
Sure. Fine by me.
Not related to your change, but the method called appears to be overloaded. I think there should really be two here: *cleared_to_deploy?* and *clear_for_deployment* or *clear_deployment_lock* or something like that. I'll add a separate issue for this.
Typo: "sets it to 1"
Originally it was valueExists. I switched to keyOf in analogy with indexOf for Arrays.
No virtual :)
Хм, а как же это работало? Я проверю.

Но, ок, будем в любом случае создавать `$('<input type="file">')` сразу.
https://github.com/uploadcare/uploadcare-widget/commit/62cc166cc8805e52ac80e462cfdb4c7bd50de55e
никаких идей. следующий рефакторинг будет "убрать settings из аплодеров, назвать их файлами и сделать тупыми value-объектами"
TODO: refactor this

This violates single responsibility.

You have an method in the Item model that is calling building a purchase object and then passing the item to the new purchase. This could probably be handled by a method in the Purchase model.

Also, I'm not sure if ```:item => this.id``` would work. Is this method being called anywhere?
No. Javascripts go at the bottom of the page. Modernizr is the one exception.
yep, tell me about it :) The idea for the moment was to have the minimum amount of change that makes it work. Of course there is a lot to be improved here.
А зачем этого кода избегать?
It doesn't work yet, see the convo above with Jakob.
but actually I should use modulegenerator  everywhere.
wouldn't it be better to use guava for hsahcode and equals?
Why not using here the Constructor where you only pass the RuleBaseElement?
L185-191: I need to see these in the GUI, but in principle a case needs to be made for all of these. The MEncoder engine is deprecated and will be removed. As a general rule, "MEncoder did it" is a reason to ***not*** repeat its "features" in a new engine.
ghalat kardam,pashimun shodam,dge az in kara nemikonam !!!!!
Please add four spaces before ($this->_apiResponseCode == ' in order to maintain similar styling
When I remove my own RouteVoter, the 'current' value is not being set on the MenuItems, which means my MenuItem aren't being highlighted as active when I'm in that menu. And since my breadcrumb is build on that value, that also no longer works.

Do I need to set the request at another location or how do I incorporate the default RouteVoter in my menu ?
You can replace the loop with this:

            foreach ($responseHeaders as $headerKey => $value) {
                $value = json_decode($value);
                if (is_scalar($value)) {
                    $brokeredMessage->setProperty(
                        $headerKey, 
                        $value
                    );
                 }
            }
I had no failures but some skipped tests.
.gets(nil) same as .gets ?
well its different there imho .. because i modify the url because i change the url .. not because i parse it ..
I can accommodate your personal preferences.
Misread snippet. Read line replacement as still existing.

No fault at this location.
http://www.stack.nl/~dimitri/doxygen/commands.html#cmdtparam
As this is a specific implementation for MessageChannels I guess the main user of this class would be MessageGroupQueue? The return of a MessageGroup here (even though required by the interface) turns out to be a major performance bottleneck in itself - imagine a queue with several hundred or thousand messages. However, the MessageGroupQueue - while using only one group anyway -  doesn't even check the return value of this method. 

As this implementation is driven by the need for better performance on queue channels, would it make sense to intentionally break the interface contract here and return null or an empty MessageGroup to avoid returning the complete database table content on every insert?
s/~~over~~/from/
I guess i have to
hmm..................................................................................................................................................................... I'm usually in favor of letting the Jenkins magic do its work and elevate most of the unnecessary form parsing but ......................................... hmm .................................................................. ok , if you insist ;)
you removed one $ ? :)

it has to double $$
Wouldn't it be better if you would initialize this as:

```
$('#placeholder').datastream.plot($('#selectmetric').val());
```

or maybe even:

```
$('#placeholder').datastream($('#selectmetric').val());
```
Can you format this paragraph adding styles?

http://sphinx.pocoo.org/rest.html#inline-markup
This is invalid markup for a :ref: entity.
Probably better to use present tense, "We use" instead of "We used"
I think Americans would put a comma after the 10.
I think the problem with this one was that I put myself as a translator and the script could not find my user in the users dict. Maybe this solution is not good because it fails afterwards trying to render the page (I did not connect the dots until I chatted with Aslak). Maybe a better solution is to raise an intelligible exception (instead of NullPointer scary Ruby equivalent :-P ).
delete メソッドの戻り値によって処理を変えているところですが、間違いではないですしそういう設計もありだとは思いますが、
私が思うに false が返る場合は NOT_FOUND になる理由がソースを見るだけではわかりません。
サービスの修正内容になりますが、まず、delete メソッドの戻り値を Unit にしましょう。Boolean だと true/false がどういう状況かというのが
コメントか中身の実装を読まないと分からないです。
Unit の場合、delete 処理を実行したということだけ分かり、それさえ分かれば良いのです。
次に、DAO から返ってくる情報の"影響した行"の値によって(もし返らないようなら返るようにしましょう)、0 ならば例外を投げるようにしましょう。
リソースでその例外をキャッチした場合に NOT_FOUND となるようにすると、表現力が高まります。
The reason I did this is because I copied the ORM docs. But can change if you want.
Not to over-engineer this on you, but it seems like all of this configuration code would love to live in an object somewhere. But maybe that isn't necessary right now. I could just see this code being reused in the future, but that's probably the best time to revisit this idea.
no need to repeat what's in the code
did you forget to change the if back?
what is this comment related to? is the test on the line below failing? then it should be commented out...
Isn't the MavenProject the object we are interested in instead of the mojo? Or do you expect we might need the mojo here in future?
shoudln't you return after applying the named converter ?
Let me split this

1) having a general *get_response_headers* method, returning headers by status_code
* i think the advantage is, that now very easily headers can be added depending on the status code. You can overwrite this method in a some Mixin and this *can* cover everything regarding headers. Without this method, you would need to go into every Generic view and customize it manually
* and even then, you would need to copy&paste most methods, because by using super() you wont have access to the serializer e.g.

2) supporting serializer, object, ...
* thats confusing, right. As an example: 
 * the Delete Mixin has no serializer. But it handles an object. So this object can be passed to this method.
 * the List Mixin or the others use a serializer, that can be used.
 * by supporting both, this *generic method* will be able to do the best with the kwargs given in a specific situation.
* e.g. when this method is used by some view, that uses no serializer:
 * now it would be possible, by just passing the object that might have been created, and the 201 code to this function, and a Location header would being set.

Maybe I try to solve too much with this method ? but i thought it might be helpful because of not being to specific in what needs to be passed in.

i think 1) is very helpful
regarding 2) - I could somehow understand if you consider this to be just *too much*.. though i see a real benefit
Was this necessary in an old version of Python or something?
Not for now , but if something may be extending building and disable the health regeneration fully ...
An second pause field used for the Out-Of-Focus-Pause .
"Provides a wrapper for easily adding and removing menu items in a restartless fashion."
ya... I see that. sorry. Will fix it.
I like this. That way we aren't hard coding which attributes support diffs but allow any attribute to add in the more_link option to get diff support.

Ideally this would allow passing in a url too. Right now if I recall the JournalsController#diff is hardcoded too so it's not possible to add diffs of other fields. If `more_link` allowed a url a plugin could provide a url override. E.g.

```
:more_link => true # use JournalsController#diff
:more_link => some_plugin_restful_route_path # use the generated path
```
I deleted this file as it seemed to be fixes for Rails 3 compatibility and the latest version of the gem is rails 3 compatible, but I don't really know what else this file might do... please let me know if this file should be kept around.
Ha, looking at where this comes from (the decode method), I understand your choice, and I agree that it seems more reasonnable.
(Admittedly, numberOfRows does make the conditional a bit more intuitive to read. I still prefer the convention.)
due to "load_and_authorize_resource ", I get an error because : 

" 
NameError in HomeController#index
uninitialized constant Home
"
ReadOnlyProxyTest is not using the `TextHolder` class, so this mapping can be just excluded
I would rename this class to `WarpRuntimeInitializer` or similar.

I think that we should not retrieve `WarpRuntime` service directly, but rather obtain `HttpFilterBuilder` and `ClientActionBuilder` services which would be setup independently - it would allow better extensibility and independence of those.
So, the most obvious thing to me right now is to add an attribute on slices that is something like _ignoreHeaders that causes all of addMessageHeader/updateMessageHeader/deleteMessageHeaderAndBody to not tell the slice anything.

In the ActiveSync case for "sync, then show headers" we generally set this _ignoreHeaders to true because we just want to wait for the sync to complete and then just ask for INITIAL_FILL_SIZE headers.  For a better server implemenation like gmail's activesync, for initial sync we could leave this set to false so that headers get added as we synchronize (and older headers get ignored because of desiredHeaders throwing them away).  Ideally your discovery mechanism could tell when we are using gmail, even if it's gmail for a vanity domain, and set that flag safely...
The options handling is a cool improvement - seeing this semantic duplication makes me wonder again, whether doing the cross region 'backend' with the AWS SDK for Ruby instead (rather than Python/boto scripts/modules) might have been the better choice, allowing inline usage for our main use case Chef specifically, alas ...
Have raised the following ticket to address this on platform:
https://jira.appcelerator.org/browse/TIMOB-7893

I have removed the canCancelEvents property for the time being, in the following update.
<string name="general_settings_title">Opećito</string> - Opećito is a typo. It should be like this: <string name="general_settings_title">Općenito</string>
@CircleCode test et une copie @eric-brison
Added link to chat page.
Why don't specify exception?
I feel like I should just make the change in the webplatform to JSON parse this. what do you think?
Few different problems to consider-
1. Do you want this to run on the CI server? I suspect the answer is yes, in which case you need to do nothing more. If no, then you should add a flag like -ci
2. There are no submodule updates during the SCM build which means someone will have to run these steps manually - @jkeshavarzi - please note that once this branch is folded in you will have to do these steps manually on the webplatform submodule.
3, ./configure will not work on a windows machine, you should change it. The problem is that the only other option is doing a "source configure" which fails on the CI server when it gets called through Hudson which is a possible environment problem but its very to trace and then possibly harder to fix. So you will need to do something about this. Try it on a windows machine and you will see that ./configure does not work. Talk to @jkeshavarzi for more details on how to run it
@Krastanov 
- about skipped/abstained: I didn't spend a lot of time choosing the right word here, but abstained definitely fits the meaning better :) 
- and about the fourth group of people: why do you think so?
- it was a namedtuple in the beginning but seemed too complicated to me (long and visually unappealing). What are the advantages of it being a namedtuple?