labofsahil/github-event-dataset-2012 huggingface dataset:
You are right, I have tried to reproduce the problem in a small test case and I could not do it.

I am totally lost… ☹


From: Eric Torreborre [mailto:notifications@github.com]
Sent: samedi 13 octobre 2012 01:12
To: etorreborre/specs2
Cc: Edmondo Porcu
Subject: Re: [specs2] 1.12.3 debug - recursive mkdir + pom with changeable scala version (#112)


In src/main/scala/org/specs2/io/FileWriter.scala:

> @@ -69,9 +69,12 @@ trait FileWriter {

>    /** @return true if the file exists */

>    def exists(path: String) = path != null && new File(path).exists

>    /** creates a new directory */

> -  def mkdirs(path: String) = {

> -    println("trying to create directory "+path)

> -    println("the current dir is "+new File(".").getAbsolutePath)

> +  def mkdirs(path: String):Boolean = {

> +    // Recursive fix

> +    val file = new File(path)

> +    val parentFile = file.getParentFile

> +    if(!parentFile.exists())

> +      mkdirs(parentFile.getAbsolutePath)

>      new File(path).mkdirs

I don't get why this fixes the problem. The call to the mkdirs function in Java is already recursively creating all the parent directories if necessary.

—
Reply to this email directly or view it on GitHub<https://github.com/etorreborre/specs2/pull/112/files#r1834904>.

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
and right you are, sir!
Ono tu vlastne vobec nemusime cakat, lebo v hlavnom threade bude videplayer stale prehravat playlisty.
This is checked somewhere else already in resolveDependencies, no?
I'd rather you write a new import line then to split it like this.
Humm, weird, not sure how it happened.  Will fix.
Do you need the `ul` bit?
Also, as # declares an ID, I don't think that you need the 'form' part. 
#search > button 
should suffice as well, unless we're using the ID part more than once in the source, which would be against HTML standards.
In my opinion the positive case should be first and we shouldn't use a ternary. For example:

```ruby
if found
  found.tap { |f| f.translations.reload }
else
  super
end
```
Thats a great point will add that!
Denied because of this.
Is this merging in 0.7.1 upstream?

If so, we should probably maintain that in the version number. eg, 0.7.1.PL or some such
The dependency constraint should become '~> 1.3.0'  and not be removed as this extension is not compatible with older versions of spree.
OK, I just tested this out, and now I know why I wrote it the way I did.  The VM gets destroyed, and has no 'ready' function, or something similar to that - you get the error message "Failed to stop my.hostname.com: undefined method `ready' for #"
For testing I have changed it to '* * * * *'. There are no new jobs added to the queue/history. Does it mean that the job only gets executed and listed in the history if a change happened to the repository?
I think you should add an assertion to the end of this test somewhere otherwise it has none.

I would assert that some of the text on the UI represents the account that you've just added.
A few places where you have changed these around. Having the comment on the same line as the statement is against the drupal coding standards.
http://drupal.org/node/1354#inline
I think it gives the implementors a tiny bit less rope to hang themselves. :-)
Sorry, missed it. Will fix shortly.

2012/8/16 Randall Hauch <notifications@github.com>

> In modeshape-common/pom.xml:
>
> > @@ -20,6 +20,19 @@
> >           Define the dependencies. Note that all version and scopes default to
> >           those defined in the dependencyManagement section of the parent pom.
> >       -->
> > +    <build>
> > +        <plugins>
> > +            <plugin>
> > +                <groupId>org.apache.maven.plugins</groupId>
> > +                <artifactId>maven-compiler-plugin</artifactId>
> > +                <version>2.3.2</version>
> > +                <configuration>
> > +                    <source>1.6</source>
> > +                    <target>1.6</target>
> > +                </configuration>
> > +            </plugin>
> > +        </plugins>
> > +    </build>
>
> This still seems wrong, and shouldn't be in the commit since it's defined
> in our parent POM.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/ModeShape/modeshape/pull/471/files#r1392387>.
>
>
Try n.destroy() instead?
We have a compatibility issue here. We need css element set to empty object or null by default, and in this case css rules applied will be default css rules of the slider. You see what I mean ?
this only assumes the last one is without reviews so I think it should be labelled  'get_last_addon` or somesuch
I am going to update this test and another to do that (i.e., check for visibility of the section), but simply making this method wait for '''s.find_element(*self._devs_comments_message_locator)''' won't be ok because this is a click method and therefore should work when clicking whatever the current state of the section is.  I hope to push some changes soon.
Why was this changed back to Firebug?
`func*` is the convention for a helper function for `func`. These don't really fall into that category, so they probably shouldn't be *ed. Or maybe `query-param->str*` is okay because it's a helper for `query-params->str`. But the rest don't really seem to make sense.
What about Radio- or List fields?
I agree that it's out of scope for this PR though
A check to the Me feed for `auth: logout` would be a good assertion after logout as well.
Added a bit more information to the JSDoc.
Just to confirm that all tenants will always have local authentication enabled, as opposed to only supporting, for example, the external ID providers?
if our matcher is a Url matcher, we should let it match with the pathinfo of the request. symfony will always call this over match() as we are a RequestMatcher
I think the logic here should be tidied up.

if (have tv)
  return parse tv
elsif (have xmltv-lineups)
  return parse xmltv-lineups
return -1
I don't think all this checking is needed - the model validation will pick this up so this can be simplified to just:

@phenotype_attempt = Public::PhenotypeAttempt.new(:mi_attempt_colony_name => @mi_attempt.colony_name,
  :consortium_name => @mi_attempt.consortium_name,
  :production_centre_name => @mi_attempt.production_centre_name)
Enige wat ik nu nog vind is dat het springen een beetje sloom is. Kunnen we dat versnellen? Ik moet nu de `w` of `spacebar` best lang indrukken, voelt een beetje vreemd.
Nitpick: can this be more readable?
I'd rather scroll this one than split with concatenation just to fit it on the screen.
Thats from the older version Phil. I just copy/paste this xml, and only tweak the test directory, since CI did not have some phpunit.xml generator :) . I think we need some console interface, to auto-generate the phpunit.xml file, based by what dev want to test. Maybe from spark interface?

Back to this file, since we already complete most of system testing, including database testing (#1324), then you can remove completely those hardcoded reference from all *.phpunit.xml files within travis directory. And you may also want to update the README.md within `tests` folder.
прокомментируйте, пожалуйста, этот метод поподробнее. что-то я не въезжаю.
Ой, строка очень сильно запутывает... Зачем использовать переменную, в которой всегда хранится 0? А ещё интересно, зачем тогда нужен дубль константы NUMBER_OF_ELEMENTS.

В любом случае, не понимаю, зачем из одной строки
NSUInteger randomlyGeneratedMutatedIndex = arc4random_uniform(NUMBER_OF_ELEMENTS);
делать три.

Ещё один момент, при мутации, допустим, в 100% по-любому в массиве setOfMutatedIndexes будут повторяющиеся индексы, тогда условие, чтобы элемент менялся только один раз - не выполнено.
Если не пожалеть строчек 10 на этот метод, то можно написать без цикла, зависящего от генератора рандомных чисел.
Please clarify this "other" by "The Techniques in /var/rudder/configuration-repository/techniques/ will not be..."
...but in any case the port needs to be different from the server port.
what's the backslash at the end here for?
Doesn't work on OS X Lion, the equivalent command is simply `date -u +"%H:%M"`. If you can add some if-statements to check which platform it's running on and do the different commands accordingly, I'll pull in the changes :)

You can check if running on OS X with a call to the function `shell_is_osx` which is available to the segments.
The 2 trailing spaces acts as a line break for markdown.
It's dangerous for the same reason that an operation queue would be. If scheduled blocks can be arbitrarily canceled, you could lose some of a signal's messages without the signal itself having been disposed of.
Command blank here too, but description says it's more of a listener.
Good point. I changed that.
This variable is not defined here, yet. (same problem for the other three “unit test” scripts)
Why do you `order_by('id')`?
Probably want to mention that when this MLT is evaluated, it generates a list of dict results.
Look to me like this test is similar to the one above, is this intentional? If yes, why?
Are we using fs anywhere?
Looks like there were some files that should have been ignored that weren't in it.
I think this is more compliant to the standards:

    $response = $httpKernel->forward(
        'AcmeHelloBundle:Hello:fancy',
        array(
    // ...
I was under the impression that in this part of the docs, only the symfony core is used, not the full-stack framework?
please typehint the interface
I don't know how to deal with ...configuration-block.. do you have any clue ?
'"called from another node child process" had leaked from my consideration. 
It changes so that you may say.
http://www.assembla.com/spaces/akka/tickets/1879-rewrite-the-long-running-tests-so-that-they-only-take-as-long-as-they-need---use--awaitcond--inst---
The item needs to be shared to obtain the URL. Do you want to share it?
И вообще у нас теперь же шаред_либа.
You don't need this if you remove the "You have access..." part from the widget.
Sorry about that. Rarely put things into the title attribute I guess. All better now and tested. :+1:
As a related issue, I think is it is important to have a separation between the notion of  x- and y-axis and the notion of two coordinates in world coordinate system (e.g., R.A & Dec., l & b, etc). 

x- and y-axis are more likely coupled with reactangular pixel coordinates. And each of x- and y-axis (we have 4 axis in fact, top, bottom, left, right) should be able to represent (for the purpose of tick labeling) either of two sky coordinates (e.g., RA or Dec). However, this is quite difficult to implement with current matplotlib implementation (this is one of the reason why I created axisartist toolkit although it breaks the api compatibility with matplotlib).

To me, tick labeling (e.g., location of ticks, etc) is actually coupled with sky coordinate not with x- and y-coordinate. So, if we say

```python
ax.set_xticks([242.2, 242.3, 242.4])
```

as we do below, sometimes its meaning becomes ambiguous. Say, x-axis represent Dec and y-axis represent RA, which coordinate does the above command affects? RA or DEC? It becomes more complicated for the case like 

![]( http://www.atnf.csiro.au/people/mcalabre/WCS/PGSBOX/pgsbox4.gif)

In pywcsgrid2, I decided to use number 1 & 2 to represent 1st and 2nd sky coordinate, instead of x and y. So, I use something like below (there is no such command in fact).

```python
ax.set_ticks1(...) # work on 1st coordinate of sky coordinates.
ax.set_ticks2(...)  # work on 2nd coordinate
```

And x- or y-axis just respect the tick parameters of the coordinate it is supposed to represent.
Of course there is pros and cons, this needs to be discussed further.
We try to use the "guard style" pattern in c:geo. Basically that is to avoid all nested if conditions and instead to have multiple return statements in the beginning:
if (intent.getExtras()==null) {
return default;
}
if (intent.getExtras().getString(EXTRA_GEOCODE)== null) {
return default;
}
...
Wouldn't `arcT s (e + ceiling (s - e))` be better in the (admittedly rare) case when s and e differ by much more than 1?
@tristantarrant  +1. I guess a better time for such changes is 6.0
The topology id is actually updated when rebalance starts and when rebalance ends. There can be more than one node joining/leaving before rebalance ends, and most of the time there is no joiner/leaver between rebalance start and rebalance end.
Plus, on top of wanting to change the current values, you also wanna find out which are the currently configured values, so you need some getters too.
I think that maybe we should be using time-based UUIDs (http://en.wikipedia.org/wiki/Universally_unique_identifier#Version_1_.28MAC_address.29) in general in Infinispan (and this is as good a place as any to introduce them). Cassandra uses the library at http://johannburkard.de/software/uuid/ but maybe we can concoct our own. @maniksurtani ?
Yes, I plan on moving over a significant portion of Axes's docstring over to here, and have Axes's docstring be built partly from it.
I thought you might mention this. :-)
My unicode knowledge is weak at best, but I will try to figure out a suitable unicode string which can go in the label.
Actually, thinking about it, that wouldn't fix current scripts...
I had the same thoughts.  The post-hoc functions are copied from Matlab (except `spectral()`), but Matplotlib has a lot more built-in colormaps now, so it wouldn't make sense to give them all functions.  

Maybe something shorter like `cmap('hot')`, since it's primarily used interactively?
is this code generated?
we should at least make this configurable
is there any instruction for the user to use WGS84?
Forgot to update this - it has less properties now anyway. Fixed with 0eb8949.
Checkout Issue #90.  This test will change dramatically.  In fact, the whole namespace will.  Later pull request again.
Note to self - we should check whether `getJqueryObject` is used anywhere else + check whether doing $($test) will refetch the jQuery object.
Can you add 4 spaces the above three lines to make it more readable?
@bp323 We should tackle the cause of this instead of fixing this here.
SG_ADD for inner / outer degree missing
Me either...
We haven't worked out what to do with IE7 yet. IE8 down are being pretty difficult with this split view thing (they don't support responsive, so things don't work as they should). We may end up turning off a lot of this extra functionality for those browsers.
I agree. It was that way in 3.0 templates table, but it doesn't have to be the same in 3.1.

It will be changed to style_parent_id and style_parent_tree.
_tree instead of _path is because it might contain more than one parent path, separated with /
Are you sure ``array($i)`` has the correct type as "array<integer,object<FilesystemIterator>>" is not a sub-type of "array"?
Stimmt, habe ich übersehen.
Not needed.  Will remove.
Super bonus points to wrap all these lines at 80 chars.
How about putting`acl`, `expires` and `policy` on their own lines too? It's a bit confusing with them mixed in.
mutliple-select boxes are terrible UX imo - a set of checkboxes would be preferrable. having to use modifier keys to fill out a form is ugh.
oh right, fixing now
Yes I tried to get the base url, but there were some kind of errors, so I left it like this for now.
This is not good. Please just make one regex to match date out of the text, don't do it like you are doing it now. Removing parts. This crazy. Can you provide me with an example string and I can help you make regex.
It is better to use `translation.get_language()` to get language code. It is used also in `django.core.context_processors.i18n`, where template's `LANGUAGE_CODE` is set. So we should probably use the same. `request.LANGUAGE_CODE` is also set from `translation.get_language()`, so the value is the same, but it assumes that we always be using `django.middleware.locale.LocaleMiddleware` which sets it. So it is better to have one less assumption/dependency.

Also, put comma before last `)`, because you want to force tuple.
`...timezone.now()`.
Done - added method-level documentation to explain this.
@creisman check here please
Those are not enumerated because it is quite obvious they are the level-dependant spells that get cast.
ok,so let's say a dead npc would cast a spell with triggered flag,then what about KilledMonsterCredit(NPC_BLOOD_CREDIT_BUNNY, 0)? doubt a dead one would do that.
they are right, i have sniff checked
Should I change now, or wait until after you test?
done, all @var annotations on private properties are reverted
is it mandatory to pass the ``with`` part when it is empty ?
same for this command than the other one
checking env is a dev environment
May want to move any repo config, plugin or otherwise, to parent pom.xml
thanks. will get this into 2.2.0.

these options are visible in a pig script. shorter the, better. how about
 '-nestedLoad=true|false' & '-fields=fields'
I believe the .asScala is not expensive, it should only create a wrapper with the Scala API around the Java container...
Or are you asking about another call?
If you'd like to force things to be encapsulated a bit better, don't declare these functions on `this` in the constructor.  Instead, do something like this:

```javascript

// heatmap manipulator
var Heater = function(map) {
  // constructor

  // initialize stuff
  this.top = ...;
  // ...
};

Heater.prototype.addLocationsInView = function(density) {
  // ...

  // this.top, etc. will access the instance var as before
};
```

This won't affect most functions, but it may force you to change variables that were previously local to the constructor (such as `elevHeatMap` in `showNewHeatMap()`) into instance variables.
Can this be simplified to "A slot or deployment name must be provided."? The term "locate" is throwing me off; I just want to delete it, I don't care about its location.
this sounds like a misnomer to me, It doesn't just assume an ordering, it actually assumes discrete variables with "uniform scale", fully metric. uses absolute distance as measure.
Yeah, I think that's the same thing.  We don't have it yet - it will require adding and loading a few more resources.
Indenting is a bit off for the first `:ago` hash.
Done, also changed it for strokeWidth from which I had copied it :-)
Why is this part of your public-facing API?
In particular, the absence of these methods would make more sense if CorrFunc _is not_ a GSObject, but merely had one as a member.
Matt: I am concerned that when HELGRIND is defined, we don't lock at all. It seems like instead of turning off the line that does locks, we'd want to get the order right. Do you agree?
Im not "checking for null". Im using the value if it is not null.
you have something against 58768 ?
Yes, I so ought to do.
There are a lot of similar cast.
I will fixes it in future.
These methods should log something so that you'll see which parts were initialized.
Futhermore, since we want to be able to deploy the application to different hosts without rebuilding the source,
Its a zend_fcall_info struct, not something we decide :)
should be `config_paths`
Missing class documentation.
Edited myself to be clear. Good catch.
The scope is different. 

the way node.js works, make a function "private" inside a file. i couldn't use it for example here: https://github.com/cbotsikas/Webinos-Platform/commit/64d353a4eaa430bee2ca8299b7affc04b04852d6#L4R63

So i made those functions global. i don't really like that way, we propably should have a "webinos" global variable/object to carry that sort of information
do you mean, the time in milliseconds?
I don't think we should keep this.  But if we do you're right.  We would also move it into a plugin.
Nu e bine sa inlocuiesti toate spatiile cu nimic. Se vor pierde pathurile care contin spatii.
Если здесь (в конструкторе FileReader произойдёт исключение -- будет что-то страшное.
What's up with all the repeated lines in the gitignore here?
On which cases will this branch be taken? If it is supposed to be taken in the global console case, then there wouldn't be any tab actors then.
Here we will need to call the `destroy()` method of each tool instance.
ちなみにリンクも原文にはないのですが、内容から言ってあるべきだろうと考えて入れちゃいました。
Those are mostly historical reasons. The current codebase still uses boost for:
- shared_ptr (which should be header only, I'd like to keep this, if ok)
- unorderd_map (can be easily replaced by the slightly slower std::map)
- bimap (for epg categories, should be replaceable by stl containers) 
- regexp (here we could add CRegExp to platform, and copy pcre from xbmc/lib (needed for win32))
Is this the way to go?
A couple small things here:

1. The `:max_time` can be passed without a `:min_time` if you want to search backwards from a specific point — it would be nice to support that too
2. We don't need to pass a `:max_time` parameter if it wasn't specified (leaving it out should do the Right Thing on the server), which means we shouldn't need to do that defaulting logic at all.
i think we should redirect to links_path, not root. if we ever change the homepage to, say, a marketing page, we'd want successful link submission to go to the links index, not the home page.
The name of this function should be more explicite: 'test_connectivity_fixing_non_lil' for instance.

Also, it's better if you don't use docstrings on tests but rather comments, because when there are docstrings, nose will use them as function name (which is useless).
I'll also replace the ``precomputed`` keyword in affinity with a ``affinity`` keyword.
Bad android
hm you did this to clear gpx layer when displaying gpx plan, but, will you clear gpx plan when gpx track is loaded? Or it was meant so, you could have both loaded? (I don't know if it happens, I just assume from the code)
Agree...i'd do it, but that'll put multiple commits in my PR right now, and i suck at squashing them :P
We can remove this blank line before the code block ends.
I'm not sure that NarrowFormat maps to the 'short' from the Ti API.  Have you validated the output of each format on another platform?
They should be there unless there is a good reason not to be there. What I'm talking about is the following:
```
    : TiObject(name)
    , callback_(NULL)
    , getCallback_(NULL)
```
Done (I thought it more natural to keep max with min, and maxDate with minDate)
The studio team is coding to the spec in jira, so we can't just change it.
It appears that this class still has a bunch of old style setters.  some rendered obsolete by your addition of setHeight and setWidth in the NativeControlObject and others that need to be updated to take in a TiObject* and also be added to NativeControlObject.

Can you make these changes or make sure that a Jira issue exists to do that cleanup task.  You could also check with DavidC as he might be going over and fixing these for the UI.View work.
Yes, it must always be true (unless something has gone wrong elsewhere. I did debate whether to put the check in, and did so as much for symmetry (and avoiding having two sets of variables with the same names at nested levels) as anything else. An assert could be added (or I can put an else throwUnexpected()).
@tdesvenain I didn't understand this. It seems you just commented out the code which shows the title and description. Could you explain why you did that ?
+1 pour l'espace insécable en attendant de voir ce que ça donne dans l'édition PDF.

@gregquat tu en penses quoi ?
sona boş satır ekle, yoksa git sorun çıkartıyor.
Might be nice to add some additional error handling for when hooks fail; ditto for entry_points.
typo: consol.log instead of console.log
已经看过你最新的 push 了，在这里回帖似乎比较容易追踪上下文：

1. 『能够』比较强调『可以做某件事』的能力，比『可以』的态度更明确一些，但是『能够』稍微没有『可以』那么好读。个人觉得差别不大，按心情决定了。

2. 我也的确觉得 loop 这里是代表循环这个『动作』，而不是『loop 宏』，从上下文中可以看出来。而且假如作者想表示『loop 宏』的话，他应该会直接说『loop macro』而不是单独一个『loop』。
Per our quick sync, if the else code can be simplified the code will look more clean and understandable.
I like the extra lines, jerk wad
You can't look-up the value for `:authors` from the `books` vector.
ignoring .project seems wrong.
Is there any reason to use this over the variadic class constructor?
Move this above Auxiliary::Scanner so it doesn't re-register RHOST
When I insert here:

````ruby
			print_debug message.inspect
			print_debug message.type.inspect
			print_debug (message =~ /password/).inspect
			print_debug (message.to_s =~ /password/).inspect

````

I get a failed match on the `message =~ /password/`

I think you want the string form of message version.
Except for the check for SYSTEM, is there really a reason to restrict this to meterpreter?
The required parameter for USERNAME, PASSWORD and CLIENT should be true, right?
This looks like a typo. To reference part of the packet, you need a start and a length offset, not just a start
Yeah I forgot the $, good catch

-Josh

On Nov 19, 2012, at 19:28, Brandon Perry <notifications@github.com> wrote:

> In plugins/alias.rb:
> 
> > +				# if using -f or -c, they must be the first arg, because -f/-c may also show up in the alias
> > +				# value so we can't do something like if args.include("-f") or delete_if etc
> > +				# we should never have to force and clear simultaneously.
> > +				if args[0] == "-f"
> > +					force = true
> > +					args.shift
> > +				elsif args[0] == "-c"
> > +					clear = true
> > +					args.shift
> > +				end
> > +				name = args.shift
> > +				# alias name can NEVER be certain reserved words like 'alias', add any other reserved words here
> > +				# We prevent the user from naming the alias "alias" cuz they could end up unable to clear the aliases,
> > +				# for example you 'alias -f set unset and then 'alias -f alias sessions', now you're screwed.  The byproduct
> > +				# of this is that it prevents you from aliasing 'alias' to 'alias -f' etc, but that's acceptable
> > +				reserved_words = [/^alias/i]
> This will match more than just alias, sch as aliasa, aliases, etc. I would actually have the reserved words arrary be an array of string, then below
> 
> if name =~ /^#{regex}$/
> 
> The $ is important.
> 
> —
> Reply to this email directly or view it on GitHub.
>
yesh.. it should be self.delete(key). already fixed in my repo.
This looks like it should be 'include ActiveRecord::Import::PostGISAdapter'
This line is unnec. :)
What are `child1` and `child2`?  What is more descriptive?  left and right?
Why does this throw an exception if t is undefined instead of defaulting to zero?
Did you intend to address these TODOs now or later?
Looks like these were converted to instance a little overzealously .. this block of privates should probably be static (they are ALL_CAPS)
Should this log be removed?
This will be a problem if and only if the user path is /Users/foo, and they somehow call this from /Users/foobar/... This is a major edge case. I think you're reading the function backwards, as this is NOT to expand ~ but to compress the expansion of ~ back into ~. Try the following in Python:

>>> sdk_dir = "/Users/bhamon/Library/Application Support/Titanium/mobilesdk/osx/2.0.0"
>>> string.replace(os.path.split(sdk_dir)[0],os.path.expanduser('~'),'~',1)
'~/Library/Application Support/Titanium/mobilesdk/osx'

Also, look closely at the replace docs. The 1 is to do only one replacement into '~'. This is the optional maxreplace argument.
oups! my bad, will correct that right away
i think you ment `[cancel](Titanium.UI.OptionDialog.cancel)`
You have a constructor, a setup, and an install. Does it make sense for all three of these to be separate? Perhaps a docstring above each might help to explain their separate responsibilities.
That doesn't play well with i18n. Why not simply raise an exception here and convert it into an HTML error in the calling function? That would also mean that you can return more meaningful error messages to the user.
Maybe the warning should be part of the first screen, so that sending signals is not necessary.
That comment is confusing. What do you mean by connection dies at the "right place"?
I was going to suggest changing it to `findByUrl` so as to make it more sensible when only returning one route, but yeah, I think it makes sense to pass in the request. What about "getRouteCollectionForRequest" ?
Ok for ordering, but the example don't respect the Line wrapping rule of _Generic Code Style And Convention_ http://maven.apache.org/developers/conventions/code.html#Generic_Code_Style_And_Convention
it doesn't need, min task is already defined
This change is to the `isSomeChar` overload?
Mkay, will update
Thanks seconded.  ```auto``` corrected to ```bool``` by Jerro's recent patch.
at some point we will have to specify what the best way is to do this: through environment or through toolchain instance
Added in https://github.com/hpcugent/easybuild-framework/pull/297, will change SLEPc easyblock accordingly when it gets merged in.
Again, log and `delegateQueue`.
this profile is normally added if you run the integration tests and abort them, or any other situation where the running tests get aborted. Just delete this generated profile. If you merge the recent master, this shouldn't happen any more.
Seems like a reasonable change. I don't see any reason why you would want to further examine the match result. I'll update the branch.
This is not a reliable way to detect whether the message is an i18n string.
This will be inherited from CmdbEvent
Zweierlei;

1)
Kann der Proofreader selber über seine Active-Flag entscheiden? (Eine Art... Ich nehme jetzt Ferien)
Oder ist die für die Administratoren gedacht?

2)
Updaten der Abilities entspricht dem erstellen oder löschen neuer Entitäten.
Du kannst das aber problemlos offen lassen... Und es dann je nach Umsetzung im Controller anpassen.
I don't think there's a reliable way to determine which tabindex to give it.
Commit collision here too
Let's throw an `Error`.
Now the problem seems to be in Phobos, so not much you can do now until that is resolved first.

Yes, you can add version (Posix) without sacrificing the static asserts.  Afterall there are a few more platforms that haven't been ported yet (AIX, SysV3, SySV4, BSD, Hurd ...)
searchterms.xml isn't used anymore.
Yes, so let's revert back to using only one markdown lib to avoid any further confusion of formatting, or other divergence.
same - also split into 2 lines - it's longer than github's review pane is.
аналогично, перенос строки
Missing a semicolon here. I know a lot of the examples omit semicolons, but since there's one on the jQuery side of this example, it should probably be consistent.
Контроллер не может иметь о чём-либо понятие. Лучше написать «В данном случае контроллер не выполняет действий, связанных с загружаемыми файлами, напрямую.»
This method is useless, you can do the check inside the CrudController
the `=` line must be the length of the upper line
Ok, I'll revert it as public.
There's a few things not implemented yet, like LinearRings, Model, gx:Multitrack, gx:Track. Some Cesium doesn't support yet and some I haven't run into yet and I'm not sure how to implement it.
This is so that if we ever want to in the future, we'll be able to tell that calls coming into Azure are from the Python Azure libraries.  This could give us an idea of our library usage.
tastypie and mongoengine use pk, because the id field may be set to something other than id in mongoengine.
Is hide() and show() really necessary?

As we discussed, "en" might not always be the language the scenario is originally written in. Please try to find a way to check for that language, or if it's really not easily doable, you might add a TODO mentioning it.
oh, and please use standard markdown for command lines.
Would save a bit of code and processing if its wrote as
return $element.data(PLUGIN_NS + '_intouch') ;
because its being converted into a boolean when its being set, making it pointless to do not not and the check

apart from that good improvements =:3
Участник сообщества/редколлегии? @pepelsbey призывается
### Project Tokens 
I guess we'll have to make it clearer.
These are generated on the server for existing projects for identification purposes. New projects coming from plugins arrive with coordinates. In maven projects we use the GAV. In freestyle projects we try to figure it out from the build properties or an explicit parameter (For Example the ant task). For freestyle projects put the build / job / task  name in artifactId and build number in version.

### Automatic Project Creation
You should be able to create new projects. Any technical difficulty is a bug to us. Moreover, the docs should be clear which apparently is not so. We would love your suggestions if any.

### Organization Token vs. API Key
Yep. 
Any new insights on the maven functionality ?
Is the following equivalent?:

ENV['parameters'].split(',').map do |param|
  key, param = parse_and_test_param(param)
  group.parameters << Parameter.new :key => name, :value => parameter
end

If so, that's a lot more readable to me and slightly more efficient since parameters that already exist don't need to be recreated.
The block below comes from private/qcore_unix_p.h
const Node* (const node&  не лучше?)
const T&
This is actually not quite accurate. `horizontalBounce` and `verticalBounce` are not mutually exclusive, and `disableBounce` does seem to take precedence. Looking at the apple docs, here is how this actually works:

* If `disableBounce = true` then all bouncing is disabled, regardless of `horizontalBounce` and `verticalBounce` settings
* If `disableBounce = false` and `horizontalBounce` / `verticalBounce` is `false`, dragging in the appropriate direction is not allowed _only_ if the content in the appropriate direction is smaller than the scrollview bounds, and larger content bounces when you drag to it
* If `disableBounce = false` and `horizontalBounce` / `verticalBounce` is `true`, dragging in the appropriate direction is always allowed, and bounces.

You may want to confirm these interactions in JS, but this is what the Apple documentation indicates.
The -2 was specifically reserved for when you want to re-place the actionsheet on orientation NOT for disposal. Instead, the intended behavior that a hide triggers the same as if an iPad user tapped outside of a popover. And that behavior is to simulate a press on the cancel button.
/**
 * The base class for Titanium services. To learn more about Services, see the
 * <a href="http://developer.android.com/reference/android/app/Service.html">Android Service documentation</a>.
 */
I love how clean this is now!  :+1:
Yes I agree.   I will move his to app/filters.
If you're going to update the Framework hash, it should be the latest on next.
@jeffheifetz we run the git submodule update --init command manually and push the sub modules directly to the productization repo. We do not however run configure manually, it is still run from the Maven build scripts. If we don't have any maven build scripts to run configure on the webplatform then we need to ensure we always run it (i.e. outside the if as per @nukulb ), whether we are in CI, SCM or a dev environment.
Shouldn't this be in the test case?
HE sucks!!!
Could you please clarify issue here? Or you mean switch to self.viewControllers[0]?
Getting more feedback of the statement execution
:-D...