maybe it would be better if there is a dictionary with commands as keys and handlers as values.

`var commands = {
   'forward': function() {
      // code
   }
}`

Then to execute given command you would just execute function like this:
`commands[cmd.cmd]()`


[R/iri.R:20:1:](https://github.com/vsimko/rroad/blob/fa9861040a53c2530db14383dc488e05956a79ed/R/iri.R#L20) *style:* **Variable and function names should be all lowercase.**
```r
CalculateIRIperSegments <- function(profile, iri_coef, segment.length = 100) {
^~~~~~~~~~~~~~~~~~~~~~~
```
[R/iri.R:23:1:](https://github.com/vsimko/rroad/blob/fa9861040a53c2530db14383dc488e05956a79ed/R/iri.R#L23) *style:* **lines should not be more than 80 characters.**
```r
  K <- max(2, as.integer(.5 + .25 / DX) + 1)  # number of profile points used to compute mvg avg slope input (window)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/iri.R:24:3:](https://github.com/vsimko/rroad/blob/fa9861040a53c2530db14383dc488e05956a79ed/R/iri.R#L24) *warning:* **local variable ‘BL’ assigned but may not be used**
```r
  BL <- (K - 1) * DX  # baselength
  ^~
```
[R/iri.R:26:1:](https://github.com/vsimko/rroad/blob/fa9861040a53c2530db14383dc488e05956a79ed/R/iri.R#L26) *style:* **lines should not be more than 80 characters.**
```r
  # split profile into segments by defining starting and ending indices (e.g. per 100m segment)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/iri.R:29:19:](https://github.com/vsimko/rroad/blob/fa9861040a53c2530db14383dc488e05956a79ed/R/iri.R#L29) *style:* **Commas should always have a space after.**
```r
  starts <- seq(1,length(profile)-buffer_look_ahead,by=num_samples_per_segment)
                  ^
```
[R/iri.R:29:34:](https://github.com/vsimko/rroad/blob/fa9861040a53c2530db14383dc488e05956a79ed/R/iri.R#L29) *style:* **Put spaces around all infix operators.**
```r
  starts <- seq(1,length(profile)-buffer_look_ahead,by=num_samples_per_segment)
                                ~^~
```
[R/iri.R:29:53:](https://github.com/vsimko/rroad/blob/fa9861040a53c2530db14383dc488e05956a79ed/R/iri.R#L29) *style:* **Commas should always have a space after.**
```r
  starts <- seq(1,length(profile)-buffer_look_ahead,by=num_samples_per_segment)
                                                    ^
```
[R/iri.R:29:55:](https://github.com/vsimko/rroad/blob/fa9861040a53c2530db14383dc488e05956a79ed/R/iri.R#L29) *style:* **Put spaces around all infix operators.**
```r
  starts <- seq(1,length(profile)-buffer_look_ahead,by=num_samples_per_segment)
                                                     ~^~
```
[R/iri.R:30:1:](https://github.com/vsimko/rroad/blob/fa9861040a53c2530db14383dc488e05956a79ed/R/iri.R#L30) *style:* **lines should not be more than 80 characters.**
```r
  # if there is exactly one sample missing for calculating initial IRI for next segment, delete last segment
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/iri.R:31:7:](https://github.com/vsimko/rroad/blob/fa9861040a53c2530db14383dc488e05956a79ed/R/iri.R#L31) *style:* **Place a space before left parenthesis, except in a function call.**
```r
  if ((length(profile)-buffer_look_ahead-1) %% num_samples_per_segment == 0) {
      ^
```
[R/iri.R:31:23:](https://github.com/vsimko/rroad/blob/fa9861040a53c2530db14383dc488e05956a79ed/R/iri.R#L31) *style:* **Put spaces around all infix operators.**
```r
  if ((length(profile)-buffer_look_ahead-1) %% num_samples_per_segment == 0) {
                     ~^~
```
[R/iri.R:31:41:](https://github.com/vsimko/rroad/blob/fa9861040a53c2530db14383dc488e05956a79ed/R/iri.R#L31) *style:* **Put spaces around all infix operators.**
```r
  if ((length(profile)-buffer_look_ahead-1) %% num_samples_per_segment == 0) {
                                       ~^~
```
[R/iri.R:34:1:](https://github.com/vsimko/rroad/blob/fa9861040a53c2530db14383dc488e05956a79ed/R/iri.R#L34) *style:* **lines should not be more than 80 characters.**
```r
  ends <- sapply(starts, function(x){ min(length(profile), x+num_samples_per_segment-1+buffer_look_ahead) })
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/iri.R:34:37:](https://github.com/vsimko/rroad/blob/fa9861040a53c2530db14383dc488e05956a79ed/R/iri.R#L34) *style:* **Opening curly braces should never go on their own line and should always be followed by a new line.**
```r
  ends <- sapply(starts, function(x){ min(length(profile), x+num_samples_per_segment-1+buffer_look_ahead) })
                                    ^
```
[R/iri.R:34:61:](https://github.com/vsimko/rroad/blob/fa9861040a53c2530db14383dc488e05956a79ed/R/iri.R#L34) *style:* **Put spaces around all infix operators.**
```r
  ends <- sapply(starts, function(x){ min(length(profile), x+num_samples_per_segment-1+buffer_look_ahead) })
                                                           ~^~
```
[R/iri.R:34:85:](https://github.com/vsimko/rroad/blob/fa9861040a53c2530db14383dc488e05956a79ed/R/iri.R#L34) *style:* **Put spaces around all infix operators.**
```r
  ends <- sapply(starts, function(x){ min(length(profile), x+num_samples_per_segment-1+buffer_look_ahead) })
                                                                                ~^~
```
[R/iri.R:34:87:](https://github.com/vsimko/rroad/blob/fa9861040a53c2530db14383dc488e05956a79ed/R/iri.R#L34) *style:* **Put spaces around all infix operators.**
```r
  ends <- sapply(starts, function(x){ min(length(profile), x+num_samples_per_segment-1+buffer_look_ahead) })
                                                                                ~^~
```
[R/iri.R:34:107:](https://github.com/vsimko/rroad/blob/fa9861040a53c2530db14383dc488e05956a79ed/R/iri.R#L34) *style:* **Closing curly-braces should always be on their own line, unless it's followed by an else.**
```r
  ends <- sapply(starts, function(x){ min(length(profile), x+num_samples_per_segment-1+buffer_look_ahead) })
                                                                                ^
```
[R/iri.R:47:22:](https://github.com/vsimko/rroad/blob/fa9861040a53c2530db14383dc488e05956a79ed/R/iri.R#L47) *style:* **Variable and function names should be all lowercase.**
```r
    segm_iri_cont <- CalculateIRIContinuously(profile_segment, iri_coef)
                     ^~~~~~~~~~~~~~~~~~~~~~~~
```
[R/iri.R:47:22:](https://github.com/vsimko/rroad/blob/fa9861040a53c2530db14383dc488e05956a79ed/R/iri.R#L47) *warning:* **no visible global function definition for ‘CalculateIRIContinuously’**
```r
    segm_iri_cont <- CalculateIRIContinuously(profile_segment, iri_coef)
                     ^~~~~~~~~~~~~~~~~~~~~~~~
```
[R/iri.R:76:1:](https://github.com/vsimko/rroad/blob/fa9861040a53c2530db14383dc488e05956a79ed/R/iri.R#L76) *style:* **Variable and function names should be all lowercase.**
```r
CalculateIRIContinuously <- function(profile, iri_coef) {
^~~~~~~~~~~~~~~~~~~~~~~~
```
[R/iri.R:79:1:](https://github.com/vsimko/rroad/blob/fa9861040a53c2530db14383dc488e05956a79ed/R/iri.R#L79) *style:* **lines should not be more than 80 characters.**
```r
  K <- max(2, as.integer(.5 + .25 / DX) + 1)  # number of profile points used to compute mvg avg slope input (window)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/iri.R:87:1:](https://github.com/vsimko/rroad/blob/fa9861040a53c2530db14383dc488e05956a79ed/R/iri.R#L87) *style:* **lines should not be more than 80 characters.**
```r
  # sliding window of profil elevations for calculating mvg avg slope (buffer of length K)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/iri.R:100:3:](https://github.com/vsimko/rroad/blob/fa9861040a53c2530db14383dc488e05956a79ed/R/iri.R#L100) *warning:* **local variable ‘iri_df’ assigned but may not be used**
```r
  iri_df <- data.frame()  # df for colleteing return values
  ^~~~~~
```
[R/iri.R:123:10:](https://github.com/vsimko/rroad/blob/fa9861040a53c2530db14383dc488e05956a79ed/R/iri.R#L123) *style:* **Put spaces around all infix operators.**
```r
      y[j-1] <- y[j]
        ~^~
```
[R/iri.R:131:29:](https://github.com/vsimko/rroad/blob/fa9861040a53c2530db14383dc488e05956a79ed/R/iri.R#L131) *style:* **Commas should always have a space after.**
```r
        z[j] <- z[j] + ST[j,jj] * z_last[jj]
                            ^
```
[R/iri.R:134:24:](https://github.com/vsimko/rroad/blob/fa9861040a53c2530db14383dc488e05956a79ed/R/iri.R#L134) *style:* **Put spaces around all infix operators.**
```r
    rs <- rs + abs(z[1]- z[3])
                      ~^
```
[R/iri.R:139:1:](https://github.com/vsimko/rroad/blob/fa9861040a53c2530db14383dc488e05956a79ed/R/iri.R#L139) *style:* **lines should not be more than 80 characters.**
```r
    # determine avg rs by dividing by number of considered samples and attach to result vector
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/rroad-package.R:30:1:](https://github.com/vsimko/rroad/blob/fa9861040a53c2530db14383dc488e05956a79ed/R/rroad-package.R#L30) *style:* **Trailing blank lines are superfluous.**
```r

^
```
[tests/testthat/test-iri.R:7:10:](https://github.com/vsimko/rroad/blob/fa9861040a53c2530db14383dc488e05956a79ed/tests/testthat/test-iri.R#L7) *style:* **Variable and function names should be all lowercase.**
```r
  iri <- CalculateIRIperSegments(profile, IRI_COEF_100, 20)
         ^~~~~~~~~~~~~~~~~~~~~~~
```


`༼ つ ◕_◕ ༽つ`


What are the allowed values for allergyStatus? Anything?


It has something to do that I am used to writing sourceable scripts (which makes them more versatile) lately. Admittedly the whole body would have to be wrapped in a function first and guard to detect if the script is sourced or not.  Would that be preferred, should I just use exit, or is the hybrid OK for now?


Why do you need this variable at all. It seems to me that you can just use `dummyNode` and that's going to be enough, won't it?


Please don't commit tarballs to the repo. If you're going to do this,  have it extracted already, and if needed you can tell people to copy it somewhere else. Tarballs are completely opaque in the history; I can't even look at the contents on github.


Don't we want to ensure the following: Given a `localDate` (in the account timezone), and a `referenceTime`, compute a dateTime in such a way that:
* If converted back to a localDate (in the account timezone) we would end up with the original `localDate`
* Its time period is the `referenceTime` provided

Isn't it the method in [ClockUtil](https://github.com/killbill/killbill-commons/blob/master/clock/src/main/java/org/killbill/clock/ClockUtil.java#L43) -- maybe without the [part whether we are in present time](https://github.com/killbill/killbill-commons/blob/master/clock/src/main/java/org/killbill/clock/ClockUtil.java#L47) ?


This line and the one above are tricky to read because it only includes 7 arguments, but CheckInputs is defined with 8 arguments. Thus, to feeble human minds (like mine), it may seem that the NULL here is being used for pvChecks (the last argument) instead of costTracker (the 7th argument).

(Note: I deleted a comment I made a few minutes ago stating that the arguments were mixed up.)


already actually mentioned in that issue!


No big deal :+1:


I broke up the first viewAttach test into several smaller, more descriptive tests.


Have considered Socket.io as socket library?


Remove this please.


You are right, but its better than completely without it.
Drop down menu entries can be implemented in a second step.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 15119](https://teamcity.mesosphere.io/viewLog.html?buildId=130150&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 225 Build time: 00:04:33


Remove newlines.


Ah, I see it doesn't technically need variable substitution because of the way the screen is structured.  But since it wants separate styling, it presumably wants to be a third string.


Какой номер строки?

2016-02-09 22:19 GMT+02:00 Vladimir Obrizan <notifications@github.com>:

> Здесь лучше
>
> self.redirect('/')
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/belyiy/simple-blog/commit/92b451ac4b275e7fa4d2c9c282ffa475baf827bf#commitcomment-15988279>
> .
>


And why not use a regular ternary in any case?

```python
log_type = ((lambda: NodeLog.PREREG_CHALLENGE) if "Prereg" in draft.registration_schema.name else (lambda: NodeLog.PROJECT_REGISTERED))()
```

Or:

```python
log_type = NodeLog.PREREG_CHALLENGE if "Prereg" in draft.registration_schema.name else NodeLog.PROJECT_REGISTERED
```


I'd prefer to use the style of defining a hook for inserting Jasmine spys instead of defining them all in the view class because it's both more flexible and allows you to import this class outside of a Jasmine define block


I can't change that without changing the file name. it looks like a few newer files (post new style guide) are still doing that. maybe we could all sync and decide for sure before I change anything.


TeamCity MonoGame :: Develop (Win) [Build 3.5.0.1356](http://teamcity.monogame.net/viewLog.html?buildId=14709&buildTypeId=MonoGame_DevelopWin&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 584, ignored: 6 Build time: 00:18:36


This is probably a stupid question, but where is `v` defined? What is `v` here?


Ok i see that logic is kept outside of date calculation -- it 's annoying to repeat it all over but it does make things clearer.


@SubJunk that was missing. You reverted thumbnail padding only for videos. :smiley:


Thanks, I'll merge this in, but will probably still use the display in https://github.com/T00rk/bootstrap-material-datetimepicker/issues/54


You might want to add a test for non-ascii values.


Of course, that's a pretty long line, so maybe ...

```python
is_prereg = "Prereg" in draft.registration_schema.name
log_type = NodeLog.PREREG_CHALLENGE if is_prereg else NodeLog.PROJECT_REGISTERED
```

Or just:

```python
if "Prereg" in draft.registration_schema.name:
    log_type = NodeLog.PREREG_CHALLENGE
else:
    log_type = NodeLog.PROJECT_REGISTERED
```

Or maybe:

```python
log_type = NodeLog.PROJECT_REGISTERED
if "Prereg" in draft.registration_schema.name:
    log_type = NodeLog.PREREG_CHALLENGE
```


I'm not sure how Parquet stats work, but in Presto you can have a range and a separate flag that says if the domain contains null.


as in no extensions ? hmm..


I personally am all in favor of removing the HMG... haha


searching by regex with i modifier allows you search case insensitive


regex search option


FYI Bazel 0.1.5 does not needs anymore the base workspace. that's why this lines are deleted


The original construction looks to me like a classic case of being too clever, which makes the code hard to read and understand. The fact that we had to comment it is a pretty clear giveaway. ;-)

I'd prefer to see one of those last three forms.


TeamCity Open-source Libraries :: ConfigInjector :: CI [Build 2.0.502.0](http://build01:8888/viewLog.html?buildId=14174&buildTypeId=ConfigInjector_CI) is now running


Sure. I'll do.


Why aren't you using MunqContext?


TeamCity Open-source Libraries :: ConfigInjector :: CI [Build 2.0.502.0](http://build01:8888/viewLog.html?buildId=14174&buildTypeId=ConfigInjector_CI) outcome was **SUCCESS**
Summary: Tests passed: 38 Build time: 00:00:35


Nice job! The interesting thing is that for Tasks 3-5, the `if` conditional does not appear to work...out of curiosity I altered your Task 3 program to satisfy that condition (i.e. feed it `getting_e(800)`  in the `main()` function) and that gives you the answer 1.0. But your `else` conditional works beautifully. In Tasks 4, your user input functions like a boolean, where if you enter 800 it is true and prompts the program to run `getting_e(1)` from the `main()` function, instead of feeding it the integer value the user inputs. In Task 5, the user input doesn't even matter because you don't `return` the value and use it anywhere, and you again run  `getting_e(1)` from the `main()` function. So technically, your Task 4 and 5 programs do not actually accept **and use** the user input value to do the calculations.


Nessun problema :)


Good objection.


I bet it was added to pacemaker-%.rng in case of local changes to best-match.sh; the newer timestamp would cause it to regenerate. That wouldn't be necessary for phony targets like diff/fulldiff.


You will see that slowly changing during the commits.

If I understand your question wrong, you can ignore the next line.
http://haxe.org/manual/type-system-typedef.html

Helps with autocompletion, and what should and should not be optional


this function takes too many arguments. Refactor it to take only one object, that way it would be more understandable what each argument means on any function call.

`Hexapod.prototype.generatePacket = function(options) {
}`

example call then would be:

`this.generatePacket({
power: 0,
angle: 0,
rotation: 0,
staticTilt: 0
})`

even better, maybe default value to every option should be set inside the function, that way you would pass only options you want to override. That would improve code readability.


I see in the commit message of this commit that here you're implementing a workaround for what's potentially a clang bug. Please insert this information directly here, into the code, and provide details. This is precisely the kind of code that will be incredibly difficult to debug/fix if something goes bad later, and we need all the information we can get directly next to the problematic area.


Test should explain what conditions they are testing, otherwise when you have an error, you can't understand which specific part has error


fast-forwarding 2.0 to borshop-integration-92-dr/upgrade_to_eleveldb_2.0.13 = 00151548


Your point is made and I will implement it into my script. I will say this once, I am not doing this to spite you or make you angry or anything. Next time I will make more research before making such a claim. Have a nice day.


you need to throw exceptions to trigger a failure in behat.


Ich würde my $hash = pop; machen :) Und vermutlich gleich den Namen und nicht den hash übergeben, denn in log3 wird ja dann auch nur wieder der name aus $hash extrahiert.


5382_PoolMakeUpWater (mitchute) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (959 of 959 tests passed, 0 test warnings)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-100.0%25-green.svg) ![Coverage Badge](http://img.shields.io/badge/coverage%20status-28.69%25-green.svg)


This commit should be dropped with rebase (I'll work on cleaning this up)


## Task 1

- [ ] Program is correctly formatted with shebang, description, code (0.5 pt)
- [ ] Program includes `main()` function and "ifmain" statement (0.5 pt)
- [ ] Program correctly demonstrates the use of **chained conditionals** to accomplish a task (2 pt)

## Task 2

- [ ] Program is correctly formatted with shebang, description, code (0.5 pt)
- [ ] Program includes `main()` function and "ifmain" statement (0.5 pt)
- [ ] Program correctly uses recursion to sum 0 to 1000 [inclusive] (2 pt)

## Task 3

- [ ] Program is correctly formatted with shebang, description, code (0.5 pt)
- [ ] Program includes `main()` function and "ifmain" statement (0.5 pt)
- [ ] Program correctly uses recursion to compute `e` (2 pt)

## Task 4

- [ ] Program is correctly formatted with shebang, description, code (0.5 pt)
- [ ] Program includes `main()` function and "ifmain" statement (0.5 pt)
- [ ] Program correctly accepts (and uses) the user input value for the maximum of the range over which to compute `e` using the `input()` function (2 pts)

## Task 5

- [ ] Program is correctly formatted with shebang, description, code (0.5 pt)
- [ ] Program includes `main()` function and "ifmain" statement (0.5 pt)
- [ ] Program correctly accepts (and uses) the user input value for the maximum of the range over which to compute `e` using the "argparse" module (2 pts)


I agree, lets merge the commit into the master, thanks! Feels like I'm talking to myself...


This commit is prima-facie related to an issue I just experienced: https://github.com/commercialhaskell/stack/issues/1770


This commit should also be dropped with rebase (I'll handle it)


I know this is pretty common, but you are abusing logical operator to write shorthand to ternary operation. Use ternary `test ? true : false` operator


[I create this](https://github.com/VictorTomaili/Sanity/blob/master/Sanity.Core.Test/Authorization/TransientGrantingPermissionServiceTest.cs#L21) :smile:


I have no idea if you you are still using this plugin but unfortunately I am still have to deal with Accurev. I pulled the orginal accurev plugin from here https://teamcity.jetbrains.com/viewLog.html?buildId=84494&buildTypeId=bt138&tab=artifacts and notice that this version appears to be newer. We kept getting Accurev hist errors so i was hoping this version would not have that problem.  I compiled this github version using maven and all seemed well until someone noticed that we are getting triggered builds from stream that are not the watch stream. Any help with this would be appreciated.


Maybe DependencyContext.With or DependencyContext.Using? Didn't like naming much


Is this for the email piping or a seperate issue?


- [ ] Rename test names


Thanks Igor, I have tried the 2.0 snapshot, it seems this works quite well (though I have not checked the results, just checked whether it can read the files without exceptions). I am not sure I can share the test files, but will ask for permissions in case they produce problems.


(Moving this comment from the commit to the PR diff for easier linking ...)


I think it would benefit everyone if all newcomers were required to open a dummy/fake pr or even a real pr to add their name to the list of users that have begun the journey.  Something that is somewhat of a hand holding "step this way to interact with this documentation" to encourage the real time updates and feedback.  I know I'm a git N00b and this is the first time I'm interacting with a git repo.  I'm sure if I knew how to as I started the journey, I would have provided more feedback along the way.  I still plan on going through the whole process again and seeing where I might be able to contribute more.  I know there is a pointer to a git how-to or something like that, but an actual 3-5 step demo in action would be cool.


The following doc(s) have been deployed to the [aeligature](http://aeligature-static-docs.pantheon.io/docs) Multidev environment:
- [docs/articles/sites/code/unsupported-modules-plugins](http://aeligature-static-docs.pantheon.io/docs/articles/sites/code/unsupported-modules-plugins)


Hey Mike,

Change `self::` to `$this->` as you are referring to the instance of this object.  `self::` calls a `static` method. `$this->` calls the instance of the object within the class itself.


TeamCity Xbim :: Xbim Geometry :: XbimGeometry [Build 152](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=772&buildTypeId=Xbim_XbimGeometry_XbimGeometry) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:39:40


I see, its nice, but why everything has to be fakes in tests? Doesn't that mean testing more than one thing?


Positive value when not equal, negative on error.


> Have you checked that all the places that previously returned -1 were supposed to return err_code values?

It's unclear what they're "supposed" to return, but returning `err_code` values is not inconsistent with what the callers expect (I did check how the callers used the return values).  I'll add something to the commit message to explain this.


Better but every second error message will be ignored.


It's fine. Some functionizing would be nice, and would avoid the need for ret(), but I think source guards would be overkill for these purposes.


So indeed I needed a [small change](https://github.com/ocaml/ocamlbuild/pull/50/files#diff-329b2e708262534068b960569612dcebR27) to the bootstrap compilation setup because of this change in behavior. I updated the PR ( #50 ).


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 15121](https://teamcity.mesosphere.io/viewLog.html?buildId=130155&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 225 Build time: 00:04:08


Typo!


После этого div, закрываем li! Потом открываем новую li


Ahh, of course! :)


I had to change textures location from assets to assets/resources to load in the texture2D. That's why there are lots of useless additions showing in this commit


Great job! :+1:


Empty controller actions are not necessary, but it is recommended to make them single lines if you do want to include them:

```ruby
def show; end
```


well, parse_login_data actually generates the csv and json files, so it's not a backend function at all, that's why I said it can be moved to generaterunes.py plugin. BUT, the rune_effect, rune_set_id, monster_names, rune_map, etc.. functions would remain in the SWParser package, so they can be used by both GenerateRunes and GenerateVisitFriend.
I can fix things myself, no worries. I'm just waiting to finish work then I'll merge+fix pull #34 which will probably cause conflicts with your branch, then try to do yours.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 15120](https://teamcity.mesosphere.io/viewLog.html?buildId=130154&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 225 Build time: 00:04:48


Этот класс должен идти внутри блока .main-header, сразу за ним, а внутри уже идет навигация


I was just learning about the difference here. But, if we only ever want one instance of this class to run, isn't that why I would use `self::`?


Absolute-ly agree here.  :-)


@mauritsvanrees Jenkins CI reporting about code analysis
See the full report here: http://jenkins.plone.org/job/package-plone.subrequest/3//violations
```
ERROR: /home/jenkins/workspace/package-plone.subrequest/plone/subrequest/__init__.py Imports are incorrectly sorted.
plone/subrequest/__init__.py:0:1: I001 found unsorted imports
plone/subrequest/__init__.py:31:5: E301 expected 1 blank line, found 0
plone/subrequest/__init__.py:66:20: Q000 Remove bad quotes.
plone/subrequest/__init__.py:69:1: C901 'subrequest' is too complex (21)
plone/subrequest/__init__.py:70:29: Q000 Remove bad quotes.
plone/subrequest/__init__.py:76:9: Q000 Remove bad quotes.
plone/subrequest/__init__.py:92:25: S001 found %s formatter
plone/subrequest/__init__.py:94:22: S001 found %s formatter
plone/subrequest/__init__.py:150:9: B901 blind except: statement
plone/subrequest/__init__.py:151:30: Q000 Remove bad quotes.
plone/subrequest/__init__.py:151:60: S001 found %s formatter
ERROR: /home/jenkins/workspace/package-plone.subrequest/plone/subrequest/interfaces.py Imports are incorrectly sorted.
plone/subrequest/interfaces.py:0:1: C101 Coding magic comment not found
plone/subrequest/interfaces.py:0:1: I001 found unsorted imports
plone/subrequest/interfaces.py:3:1: E302 expected 2 blank lines, found 1
ERROR: /home/jenkins/workspace/package-plone.subrequest/plone/subrequest/subresponse.py Imports are incorrectly sorted.
plone/subrequest/subresponse.py:0:1: I001 found unsorted imports
plone/subrequest/subresponse.py:20:12: P002 found "hasattr", consider replacing it
plone/subrequest/subresponse.py:21:16: P002 found "hasattr", consider replacing it
plone/subrequest/subresponse.py:22:12: P002 found "hasattr", consider replacing it
plone/subrequest/subresponse.py:48:16: P002 found "hasattr", consider replacing it
ERROR: /home/jenkins/workspace/package-plone.subrequest/plone/subrequest/testing.py Imports are incorrectly sorted.
plone/subrequest/testing.py:0:1: I001 found unsorted imports
plone/subrequest/testing.py:51:23: S001 found %s formatter
plone/subrequest/testing.py:87:25: Q000 Remove bad quotes.
plone/subrequest/testing.py:88:17: Q000 Remove bad quotes.
plone/subrequest/testing.py:163:10: Q000 Remove bad quotes.
plone/subrequest/testing.py:167:10: Q000 Remove bad quotes.
plone/subrequest/testing.py:169:1: W391 blank line at end of file
ERROR: /home/jenkins/workspace/package-plone.subrequest/plone/subrequest/tests.py Imports are incorrectly sorted.
plone/subrequest/tests.py:0:1: I001 found unsorted imports
plone/subrequest/tests.py:22:5: Q000 Remove bad quotes.
plone/subrequest/tests.py:23:5: Q000 Remove bad quotes.
plone/subrequest/tests.py:42:61: S001 found %s formatter
plone/subrequest/tests.py:50:61: S001 found %s formatter
plone/subrequest/tests.py:58:61: S001 found %s formatter
plone/subrequest/tests.py:147:13: Q000 Remove bad quotes.
plone/subrequest/tests.py:147:51: S001 found %s formatter
plone/subrequest/tests.py:160:13: Q000 Remove bad quotes.
plone/subrequest/tests.py:161:13: Q000 Remove bad quotes.
plone/subrequest/tests.py:172:13: Q000 Remove bad quotes.
plone/subrequest/tests.py:173:13: Q000 Remove bad quotes.
plone/subrequest/tests.py:184:13: Q000 Remove bad quotes.
plone/subrequest/tests.py:185:13: Q000 Remove bad quotes.
plone/subrequest/tests.py:231:46: Q000 Remove bad quotes.
plone/subrequest/tests.py:241:46: Q000 Remove bad quotes.
plone/subrequest/tests.py:251:46: Q000 Remove bad quotes.
```
Follow [these instructions](https://github.com/plone/jenkins.plone.org/blob/master/docs/source/run-qa-on-package.rst) to reproduce it locally.


PCB ver0.1


Ah, yup, here's the line


Выпадающее меню - это опять ul > li - это не список)))


Mmh, is this fixing the issue?  I would rather have expected that different versions of size-solver are compiled with different suffixes, like for Agda, where we have agda-2.4.2.6 and agda-2.5.


Sorry guys!


@davisagli Jenkins CI reporting about code analysis
See the full report here: http://jenkins.plone.org/job/package-plone.autoform/1//violations
```
plone/__init__.py:0:1: C101 Coding magic comment not found
ERROR: /home/jenkins/workspace/package-plone.autoform/plone/autoform/base.py Imports are incorrectly sorted.
plone/autoform/base.py:0:1: C101 Coding magic comment not found
plone/autoform/base.py:0:1: I001 found unsorted imports
plone/autoform/base.py:9:1: E302 expected 2 blank lines, found 1
plone/autoform/base.py:16:1: W293 blank line contains whitespace
plone/autoform/base.py:19:1: W293 blank line contains whitespace
plone/autoform/base.py:22:1: W293 blank line contains whitespace
plone/autoform/base.py:23:1: C901 'AutoFields.updateFieldsFromSchemata' is too complex (11)
plone/autoform/base.py:24:1: W293 blank line contains whitespace
plone/autoform/base.py:28:1: W293 blank line contains whitespace
plone/autoform/base.py:30:1: W293 blank line contains whitespace
plone/autoform/base.py:33:1: W293 blank line contains whitespace
plone/autoform/base.py:46:1: W293 blank line contains whitespace
plone/autoform/base.py:50:1: W293 blank line contains whitespace
plone/autoform/base.py:52:1: W293 blank line contains whitespace
plone/autoform/base.py:57:1: W293 blank line contains whitespace
plone/autoform/base.py:63:1: W293 blank line contains whitespace
plone/autoform/base.py:64:71: W291 trailing whitespace
plone/autoform/base.py:66:1: W293 blank line contains whitespace
plone/autoform/base.py:68:1: W293 blank line contains whitespace
plone/autoform/base.py:69:75: W291 trailing whitespace
plone/autoform/base.py:74:1: W293 blank line contains whitespace
plone/autoform/base.py:83:1: W293 blank line contains whitespace
plone/autoform/base.py:92:1: W293 blank line contains whitespace
plone/autoform/base.py:93:80: E501 line too long (113 > 79 characters)
plone/autoform/base.py:94:1: W293 blank line contains whitespace
plone/autoform/base.py:96:72: W291 trailing whitespace
plone/autoform/base.py:102:1: W293 blank line contains whitespace
plone/autoform/base.py:108:31: W292 no newline at end of file
ERROR: /home/jenkins/workspace/package-plone.autoform/plone/autoform/directives.py Imports are incorrectly sorted.
plone/autoform/directives.py:0:1: C101 Coding magic comment not found
plone/autoform/directives.py:0:1: I001 found unsorted imports
plone/autoform/directives.py:11:80: E501 line too long (81 > 79 characters)
plone/autoform/directives.py:22:80: E501 line too long (83 > 79 characters)
plone/autoform/directives.py:54:80: E501 line too long (87 > 79 characters)
plone/autoform/directives.py:74:26: Q000 Remove bad quotes.
plone/autoform/directives.py:74:27: S001 found %s formatter
plone/autoform/directives.py:89:80: E501 line too long (94 > 79 characters)
plone/autoform/directives.py:98:80: E501 line too long (93 > 79 characters)
ERROR: /home/jenkins/workspace/package-plone.autoform/plone/autoform/form.py Imports are incorrectly sorted.
plone/autoform/form.py:0:1: C101 Coding magic comment not found
plone/autoform/form.py:0:1: I001 found unsorted imports
plone/autoform/form.py:10:1: E302 expected 2 blank lines, found 1
plone/autoform/form.py:16:1: W293 blank line contains whitespace
plone/autoform/form.py:19:80: E501 line too long (109 > 79 characters)
plone/autoform/form.py:26:1: W293 blank line contains whitespace
ERROR: /home/jenkins/workspace/package-plone.autoform/plone/autoform/interfaces.py Imports are incorrectly sorted.
plone/autoform/interfaces.py:0:1: C101 Coding magic comment not found
plone/autoform/interfaces.py:0:1: I001 found unsorted imports
plone/autoform/interfaces.py:11:12: E221 multiple spaces before operator
plone/autoform/interfaces.py:12:12: E221 multiple spaces before operator
plone/autoform/interfaces.py:13:10: E221 multiple spaces before operator
plone/autoform/interfaces.py:14:10: E221 multiple spaces before operator
plone/autoform/interfaces.py:16:21: E221 multiple spaces before operator
plone/autoform/interfaces.py:27:1: E302 expected 2 blank lines, found 1
plone/autoform/interfaces.py:31:1: E302 expected 2 blank lines, found 1
plone/autoform/interfaces.py:38:1: W293 blank line contains whitespace
plone/autoform/interfaces.py:39:80: E501 line too long (89 > 79 characters)
plone/autoform/interfaces.py:41:1: W293 blank line contains whitespace
plone/autoform/interfaces.py:44:1: W293 blank line contains whitespace
plone/autoform/interfaces.py:45:80: E501 line too long (108 > 79 characters)
plone/autoform/interfaces.py:46:80: E501 line too long (99 > 79 characters)
plone/autoform/interfaces.py:47:75: E127 continuation line over-indented for visual indent
plone/autoform/interfaces.py:47:80: E501 line too long (93 > 79 characters)
plone/autoform/interfaces.py:50:1: E302 expected 2 blank lines, found 1
plone/autoform/interfaces.py:54:1: W293 blank line contains whitespace
plone/autoform/interfaces.py:57:39: E127 continuation line over-indented for visual indent
plone/autoform/interfaces.py:57:39: Q000 Remove bad quotes.
plone/autoform/interfaces.py:58:80: E501 line too long (91 > 79 characters)
plone/autoform/interfaces.py:59:80: E501 line too long (88 > 79 characters)
plone/autoform/interfaces.py:62:31: E128 continuation line under-indented for visual indent
plone/autoform/interfaces.py:62:80: E501 line too long (85 > 79 characters)
plone/autoform/interfaces.py:63:31: E128 continuation line under-indented for visual indent
plone/autoform/interfaces.py:63:80: E501 line too long (97 > 79 characters)
plone/autoform/interfaces.py:63:98: W292 no newline at end of file
ERROR: /home/jenkins/workspace/package-plone.autoform/plone/autoform/supermodel.py Imports are incorrectly sorted.
plone/autoform/supermodel.py:0:1: C101 Coding magic comment not found
plone/autoform/supermodel.py:0:1: I001 found unsorted imports
plone/autoform/supermodel.py:3:1: F401 'WidgetValidatorDiscriminators' imported but unused
plone/autoform/supermodel.py:11:80: E501 line too long (84 > 79 characters)
plone/autoform/supermodel.py:12:80: E501 line too long (81 > 79 characters)
plone/autoform/supermodel.py:19:1: E302 expected 2 blank lines, found 1
plone/autoform/supermodel.py:23:1: W293 blank line contains whitespace
plone/autoform/supermodel.py:26:1: W293 blank line contains whitespace
plone/autoform/supermodel.py:31:34: Q000 Remove bad quotes.
plone/autoform/supermodel.py:32:21: E128 continuation line under-indented for visual indent
plone/autoform/supermodel.py:32:21: S001 found % formatter
plone/autoform/supermodel.py:36:1: W293 blank line contains whitespace
plone/autoform/supermodel.py:41:1: W293 blank line contains whitespace
plone/autoform/supermodel.py:51:25: Q000 Remove bad quotes.
plone/autoform/supermodel.py:51:26: S001 found %s formatter
plone/autoform/supermodel.py:51:47: E225 missing whitespace around operator
plone/autoform/supermodel.py:56:1: W293 blank line contains whitespace
plone/autoform/supermodel.py:61:17: Q000 Remove bad quotes.
plone/autoform/supermodel.py:62:17: S001 found % formatter
plone/autoform/supermodel.py:64:13: E128 continuation line under-indented for visual indent
plone/autoform/supermodel.py:70:1: W293 blank line contains whitespace
plone/autoform/supermodel.py:71:15: E221 multiple spaces before operator
plone/autoform/supermodel.py:71:35: E201 whitespace after '('
plone/autoform/supermodel.py:71:67: E202 whitespace before ')'
plone/autoform/supermodel.py:72:13: E221 multiple spaces before operator
plone/autoform/supermodel.py:72:35: E201 whitespace after '('
plone/autoform/supermodel.py:72:67: E202 whitespace before ')'
plone/autoform/supermodel.py:73:16: E221 multiple spaces before operator
plone/autoform/supermodel.py:73:35: E201 whitespace after '('
plone/autoform/supermodel.py:73:67: E202 whitespace before ')'
plone/autoform/supermodel.py:74:15: E221 multiple spaces before operator
plone/autoform/supermodel.py:74:35: E201 whitespace after '('
plone/autoform/supermodel.py:74:67: E202 whitespace before ')'
plone/autoform/supermodel.py:75:14: E221 multiple spaces before operator
plone/autoform/supermodel.py:75:35: E201 whitespace after '('
plone/autoform/supermodel.py:75:67: E202 whitespace before ')'
plone/autoform/supermodel.py:76:35: E201 whitespace after '('
plone/autoform/supermodel.py:76:67: E202 whitespace before ')'
plone/autoform/supermodel.py:91:1: C901 'FormSchema.write' is too complex (12)
plone/autoform/supermodel.py:93:1: W293 blank line contains whitespace
plone/autoform/supermodel.py:94:15: E221 multiple spaces before operator
plone/autoform/supermodel.py:95:13: E221 multiple spaces before operator
plone/autoform/supermodel.py:95:22: E231 missing whitespace after ','
plone/autoform/supermodel.py:95:31: E231 missing whitespace after ','
plone/autoform/supermodel.py:95:33: E231 missing whitespace after ','
plone/autoform/supermodel.py:95:80: E501 line too long (90 > 79 characters)
plone/autoform/supermodel.py:96:22: E231 missing whitespace after ','
plone/autoform/supermodel.py:96:31: E231 missing whitespace after ','
plone/autoform/supermodel.py:96:33: E231 missing whitespace after ','
plone/autoform/supermodel.py:96:80: E501 line too long (92 > 79 characters)
plone/autoform/supermodel.py:97:14: E221 multiple spaces before operator
plone/autoform/supermodel.py:97:22: E231 missing whitespace after ','
plone/autoform/supermodel.py:97:31: E231 missing whitespace after ','
plone/autoform/supermodel.py:97:33: E231 missing whitespace after ','
plone/autoform/supermodel.py:97:80: E501 line too long (91 > 79 characters)
plone/autoform/supermodel.py:98:1: W293 blank line contains whitespace
plone/autoform/supermodel.py:101:26: Q000 Remove bad quotes.
plone/autoform/supermodel.py:101:27: S001 found %s formatter
plone/autoform/supermodel.py:103:1: W293 blank line contains whitespace
plone/autoform/supermodel.py:107:25: Q000 Remove bad quotes.
plone/autoform/supermodel.py:107:26: S001 found %s formatter
plone/autoform/supermodel.py:110:55: Q000 Remove bad quotes.
plone/autoform/supermodel.py:111:1: W293 blank line contains whitespace
plone/autoform/supermodel.py:115:25: Q000 Remove bad quotes.
plone/autoform/supermodel.py:115:26: S001 found %s formatter
plone/autoform/supermodel.py:118:58: Q000 Remove bad quotes.
plone/autoform/supermodel.py:118:80: E501 line too long (82 > 79 characters)
plone/autoform/supermodel.py:126:1: E302 expected 2 blank lines, found 1
plone/autoform/supermodel.py:130:1: W293 blank line contains whitespace
plone/autoform/supermodel.py:133:1: W293 blank line contains whitespace
plone/autoform/supermodel.py:136:1: W293 blank line contains whitespace
plone/autoform/supermodel.py:138:80: E501 line too long (80 > 79 characters)
plone/autoform/supermodel.py:139:1: W293 blank line contains whitespace
plone/autoform/supermodel.py:142:1: W293 blank line contains whitespace
plone/autoform/supermodel.py:146:1: W293 blank line contains whitespace
plone/autoform/supermodel.py:153:1: W293 blank line contains whitespace
plone/autoform/supermodel.py:154:80: E501 line too long (91 > 79 characters)
plone/autoform/supermodel.py:155:80: E501 line too long (93 > 79 characters)
plone/autoform/supermodel.py:156:1: W293 blank line contains whitespace
plone/autoform/supermodel.py:158:80: E501 line too long (81 > 79 characters)
plone/autoform/supermodel.py:160:80: E501 line too long (83 > 79 characters)
plone/autoform/supermodel.py:160:84: W292 no newline at end of file
ERROR: /home/jenkins/workspace/package-plone.autoform/plone/autoform/utils.py Imports are incorrectly sorted.
plone/autoform/utils.py:0:1: C101 Coding magic comment not found
plone/autoform/utils.py:0:1: I001 found unsorted imports
plone/autoform/utils.py:24:80: E501 line too long (84 > 79 characters)
plone/autoform/utils.py:25:80: E501 line too long (81 > 79 characters)
plone/autoform/utils.py:34:1: E302 expected 2 blank lines, found 1
plone/autoform/utils.py:83:1: E302 expected 2 blank lines, found 1
plone/autoform/utils.py:93:1: E302 expected 2 blank lines, found 1
plone/autoform/utils.py:100:1: W293 blank line contains whitespace
plone/autoform/utils.py:102:80: E501 line too long (87 > 79 characters)
plone/autoform/utils.py:103:1: W293 blank line contains whitespace
plone/autoform/utils.py:107:1: W293 blank line contains whitespace
plone/autoform/utils.py:115:80: E501 line too long (103 > 79 characters)
plone/autoform/utils.py:116:80: E501 line too long (100 > 79 characters)
plone/autoform/utils.py:117:21: E128 continuation line under-indented for visual indent
plone/autoform/utils.py:118:1: W293 blank line contains whitespace
plone/autoform/utils.py:120:1: W293 blank line contains whitespace
plone/autoform/utils.py:125:1: C901 'processFields' is too complex (20)
plone/autoform/utils.py:125:80: E501 line too long (85 > 79 characters)
plone/autoform/utils.py:128:63: W291 trailing whitespace
plone/autoform/utils.py:136:1: W293 blank line contains whitespace
plone/autoform/utils.py:137:80: E501 line too long (88 > 79 characters)
plone/autoform/utils.py:138:1: W293 blank line contains whitespace
plone/autoform/utils.py:139:12: E221 multiple spaces before operator
plone/autoform/utils.py:139:80: E501 line too long (89 > 79 characters)
plone/autoform/utils.py:140:10: E221 multiple spaces before operator
plone/autoform/utils.py:140:80: E501 line too long (98 > 79 characters)
plone/autoform/utils.py:141:12: E221 multiple spaces before operator
plone/autoform/utils.py:141:80: E501 line too long (103 > 79 characters)
plone/autoform/utils.py:142:1: W293 blank line contains whitespace
plone/autoform/utils.py:143:80: E501 line too long (100 > 79 characters)
plone/autoform/utils.py:144:1: W293 blank line contains whitespace
plone/autoform/utils.py:145:80: E501 line too long (81 > 79 characters)
plone/autoform/utils.py:146:1: W293 blank line contains whitespace
plone/autoform/utils.py:147:20: E221 multiple spaces before operator
plone/autoform/utils.py:149:20: E221 multiple spaces before operator
plone/autoform/utils.py:150:1: W293 blank line contains whitespace
plone/autoform/utils.py:152:24: E221 multiple spaces before operator
plone/autoform/utils.py:152:80: E501 line too long (105 > 79 characters)
plone/autoform/utils.py:153:80: E261 at least two spaces before inline comment
plone/autoform/utils.py:153:80: E501 line too long (105 > 79 characters)
plone/autoform/utils.py:154:24: E221 multiple spaces before operator
plone/autoform/utils.py:155:1: W293 blank line contains whitespace
plone/autoform/utils.py:157:1: W293 blank line contains whitespace
plone/autoform/utils.py:164:1: W293 blank line contains whitespace
plone/autoform/utils.py:168:1: W293 blank line contains whitespace
plone/autoform/utils.py:174:80: E501 line too long (98 > 79 characters)
plone/autoform/utils.py:175:1: W293 blank line contains whitespace
plone/autoform/utils.py:178:1: W293 blank line contains whitespace
plone/autoform/utils.py:180:1: W293 blank line contains whitespace
plone/autoform/utils.py:184:1: W293 blank line contains whitespace
plone/autoform/utils.py:196:80: E501 line too long (127 > 79 characters)
plone/autoform/utils.py:199:1: W293 blank line contains whitespace
plone/autoform/utils.py:201:1: W293 blank line contains whitespace
plone/autoform/utils.py:203:25: W291 trailing whitespace
plone/autoform/utils.py:204:1: W293 blank line contains whitespace
plone/autoform/utils.py:209:1: W293 blank line contains whitespace
plone/autoform/utils.py:211:1: W293 blank line contains whitespace
plone/autoform/utils.py:214:1: W293 blank line contains whitespace
plone/autoform/utils.py:219:1: W293 blank line contains whitespace
plone/autoform/utils.py:221:1: W293 blank line contains whitespace
plone/autoform/utils.py:223:1: W293 blank line contains whitespace
plone/autoform/utils.py:224:62: W291 trailing whitespace
plone/autoform/utils.py:225:45: E127 continuation line over-indented for visual indent
plone/autoform/utils.py:226:49: E127 continuation line over-indented for visual indent
plone/autoform/utils.py:226:80: E501 line too long (88 > 79 characters)
plone/autoform/utils.py:227:1: W293 blank line contains whitespace
plone/autoform/utils.py:228:31: W291 trailing whitespace
plone/autoform/utils.py:230:1: W293 blank line contains whitespace
plone/autoform/utils.py:234:80: E501 line too long (81 > 79 characters)
plone/autoform/utils.py:238:1: W293 blank line contains whitespace
plone/autoform/utils.py:239:1: W293 blank line contains whitespace
plone/autoform/utils.py:245:1: W293 blank line contains whitespace
plone/autoform/utils.py:246:80: E501 line too long (96 > 79 characters)
plone/autoform/utils.py:247:1: W293 blank line contains whitespace
plone/autoform/utils.py:249:1: W293 blank line contains whitespace
plone/autoform/utils.py:259:1: W293 blank line contains whitespace
ERROR: /home/jenkins/workspace/package-plone.autoform/plone/autoform/view.py Imports are incorrectly sorted.
plone/autoform/view.py:0:1: C101 Coding magic comment not found
plone/autoform/view.py:0:1: I001 found unsorted imports
plone/autoform/view.py:16:1: E302 expected 2 blank lines, found 1
plone/autoform/view.py:20:1: W293 blank line contains whitespace
plone/autoform/view.py:22:1: W293 blank line contains whitespace
plone/autoform/view.py:24:1: W293 blank line contains whitespace
plone/autoform/view.py:27:1: W293 blank line contains whitespace
plone/autoform/view.py:29:1: W293 blank line contains whitespace
plone/autoform/view.py:41:1: W293 blank line contains whitespace
plone/autoform/view.py:43:1: W293 blank line contains whitespace
plone/autoform/view.py:49:1: W293 blank line contains whitespace
plone/autoform/view.py:53:1: W293 blank line contains whitespace
plone/autoform/view.py:57:1: W293 blank line contains whitespace
plone/autoform/view.py:62:1: W293 blank line contains whitespace
plone/autoform/view.py:65:1: W293 blank line contains whitespace
plone/autoform/view.py:69:1: W293 blank line contains whitespace
plone/autoform/view.py:72:1: W293 blank line contains whitespace
plone/autoform/view.py:74:1: W293 blank line contains whitespace
plone/autoform/view.py:77:1: W293 blank line contains whitespace
ERROR: /home/jenkins/workspace/package-plone.autoform/plone/autoform/tests/test_directives.py Imports are incorrectly sorted.
plone/autoform/tests/test_directives.py:0:1: C101 Coding magic comment not found
plone/autoform/tests/test_directives.py:0:1: I001 found unsorted imports
plone/autoform/tests/test_directives.py:10:80: E501 line too long (84 > 79 characters)
plone/autoform/tests/test_directives.py:11:80: E501 line too long (81 > 79 characters)
plone/autoform/tests/test_directives.py:17:1: E302 expected 2 blank lines, found 1
plone/autoform/tests/test_directives.py:22:1: W293 blank line contains whitespace
plone/autoform/tests/test_directives.py:25:1: W293 blank line contains whitespace
plone/autoform/tests/test_directives.py:34:1: W293 blank line contains whitespace
plone/autoform/tests/test_directives.py:36:1: W293 blank line contains whitespace
plone/autoform/tests/test_directives.py:38:1: W293 blank line contains whitespace
plone/autoform/tests/test_directives.py:49:1: W293 blank line contains whitespace
plone/autoform/tests/test_directives.py:54:1: W293 blank line contains whitespace
plone/autoform/tests/test_directives.py:56:1: W293 blank line contains whitespace
plone/autoform/tests/test_directives.py:57:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_directives.py:60:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_directives.py:65:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_directives.py:68:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_directives.py:71:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_directives.py:73:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_directives.py:75:1: W293 blank line contains whitespace
plone/autoform/tests/test_directives.py:77:1: W293 blank line contains whitespace
plone/autoform/tests/test_directives.py:80:1: W293 blank line contains whitespace
plone/autoform/tests/test_directives.py:84:1: W293 blank line contains whitespace
plone/autoform/tests/test_directives.py:85:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_directives.py:85:80: E501 line too long (86 > 79 characters)
plone/autoform/tests/test_directives.py:86:19: E128 continuation line under-indented for visual indent
plone/autoform/tests/test_directives.py:87:1: W293 blank line contains whitespace
plone/autoform/tests/test_directives.py:89:1: W293 blank line contains whitespace
plone/autoform/tests/test_directives.py:91:1: W293 blank line contains whitespace
plone/autoform/tests/test_directives.py:106:1: W293 blank line contains whitespace
plone/autoform/tests/test_directives.py:111:1: W293 blank line contains whitespace
plone/autoform/tests/test_directives.py:112:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_directives.py:115:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_directives.py:118:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_directives.py:121:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_directives.py:124:53: E231 missing whitespace after ','
plone/autoform/tests/test_directives.py:126:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_directives.py:126:80: E501 line too long (97 > 79 characters)
plone/autoform/tests/test_directives.py:128:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_directives.py:128:80: E501 line too long (90 > 79 characters)
plone/autoform/tests/test_directives.py:130:1: W293 blank line contains whitespace
plone/autoform/tests/test_directives.py:132:1: W293 blank line contains whitespace
plone/autoform/tests/test_directives.py:141:1: W293 blank line contains whitespace
plone/autoform/tests/test_directives.py:152:1: W293 blank line contains whitespace
plone/autoform/tests/test_directives.py:155:1: W293 blank line contains whitespace
plone/autoform/tests/test_directives.py:159:1: W293 blank line contains whitespace
plone/autoform/tests/test_directives.py:160:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_directives.py:160:51: E231 missing whitespace after ','
plone/autoform/tests/test_directives.py:160:80: E501 line too long (87 > 79 characters)
ERROR: /home/jenkins/workspace/package-plone.autoform/plone/autoform/tests/test_doctests.py Imports are incorrectly sorted.
plone/autoform/tests/test_doctests.py:0:1: C101 Coding magic comment not found
plone/autoform/tests/test_doctests.py:0:1: I001 found unsorted imports
plone/autoform/tests/test_doctests.py:10:13: E128 continuation line under-indented for visual indent
plone/autoform/tests/test_doctests.py:11:13: E128 continuation line under-indented for visual indent
plone/autoform/tests/test_doctests.py:12:13: E128 continuation line under-indented for visual indent
plone/autoform/tests/test_doctests.py:12:53: E227 missing whitespace around bitwise or shift operator
plone/autoform/tests/test_doctests.py:14:13: E128 continuation line under-indented for visual indent
plone/autoform/tests/test_doctests.py:15:13: E128 continuation line under-indented for visual indent
plone/autoform/tests/test_doctests.py:16:13: E128 continuation line under-indented for visual indent
plone/autoform/tests/test_doctests.py:16:53: E227 missing whitespace around bitwise or shift operator
plone/autoform/tests/test_doctests.py:18:13: E128 continuation line under-indented for visual indent
plone/autoform/tests/test_doctests.py:19:13: E128 continuation line under-indented for visual indent
plone/autoform/tests/test_doctests.py:20:13: E128 continuation line under-indented for visual indent
plone/autoform/tests/test_doctests.py:20:53: E227 missing whitespace around bitwise or shift operator
plone/autoform/tests/test_doctests.py:21:11: W292 no newline at end of file
ERROR: /home/jenkins/workspace/package-plone.autoform/plone/autoform/tests/test_supermodel_handler.py Imports are incorrectly sorted.
plone/autoform/tests/test_supermodel_handler.py:0:1: C101 Coding magic comment not found
plone/autoform/tests/test_supermodel_handler.py:0:1: I001 found unsorted imports
plone/autoform/tests/test_supermodel_handler.py:12:80: E501 line too long (84 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:13:80: E501 line too long (81 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:16:1: E302 expected 2 blank lines, found 1
plone/autoform/tests/test_supermodel_handler.py:17:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:19:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:22:27: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:22:54: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:22:80: E501 line too long (101 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:23:27: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:23:52: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:24:27: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:24:55: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:25:27: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:25:54: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:26:27: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:26:57: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:26:80: E501 line too long (104 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:27:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:30:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:33:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:34:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_supermodel_handler.py:34:80: E501 line too long (85 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:35:13: E128 continuation line under-indented for visual indent
plone/autoform/tests/test_supermodel_handler.py:36:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_supermodel_handler.py:36:80: E501 line too long (93 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:37:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_supermodel_handler.py:37:80: E501 line too long (93 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:38:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_supermodel_handler.py:38:80: E501 line too long (96 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:39:80: E501 line too long (90 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:45:28: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:45:55: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:45:80: E501 line too long (102 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:46:28: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:46:53: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:47:28: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:47:56: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:48:28: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:48:55: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:49:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:51:28: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:51:53: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:52:28: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:52:56: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:53:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:57:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:61:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:62:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_supermodel_handler.py:62:80: E501 line too long (86 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:63:13: E128 continuation line under-indented for visual indent
plone/autoform/tests/test_supermodel_handler.py:64:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_supermodel_handler.py:64:80: E501 line too long (88 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:66:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_supermodel_handler.py:66:80: E501 line too long (94 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:68:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_supermodel_handler.py:68:80: E501 line too long (97 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:69:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:72:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:78:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:79:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_supermodel_handler.py:80:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_supermodel_handler.py:81:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_supermodel_handler.py:82:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_supermodel_handler.py:83:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:86:28: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:86:53: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:86:80: E501 line too long (87 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:87:28: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:87:56: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:87:80: E501 line too long (88 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:90:28: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:90:53: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:90:80: E501 line too long (125 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:91:28: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:91:56: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:91:80: E501 line too long (124 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:92:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:101:80: E501 line too long (120 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:102:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_supermodel_handler.py:103:80: E501 line too long (116 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:104:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_supermodel_handler.py:104:80: E501 line too long (81 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:105:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:108:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:111:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:116:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:119:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:120:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_supermodel_handler.py:120:27: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:120:59: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:120:80: E501 line too long (85 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:121:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_supermodel_handler.py:121:27: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:121:53: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:121:80: E501 line too long (80 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:122:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_supermodel_handler.py:122:27: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:122:55: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:123:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_supermodel_handler.py:123:27: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:123:58: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:123:80: E501 line too long (84 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:124:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:127:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:130:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:133:80: E501 line too long (108 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:135:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:138:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:139:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_supermodel_handler.py:139:27: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:139:59: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:139:80: E501 line too long (85 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:140:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_supermodel_handler.py:140:51: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:141:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_supermodel_handler.py:141:27: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:141:56: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:141:80: E501 line too long (80 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:142:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_supermodel_handler.py:142:51: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:146:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:149:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:152:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:153:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_supermodel_handler.py:153:51: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:154:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_supermodel_handler.py:154:51: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:155:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_supermodel_handler.py:155:51: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:156:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_supermodel_handler.py:156:51: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:166:80: E501 line too long (118 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:168:80: E501 line too long (114 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:175:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_supermodel_handler.py:175:27: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:175:80: E501 line too long (106 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:175:82: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:176:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_supermodel_handler.py:176:27: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:176:80: E501 line too long (107 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:176:80: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:178:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_supermodel_handler.py:178:27: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:178:80: E501 line too long (99 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:179:46: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:180:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_supermodel_handler.py:180:27: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:180:80: E501 line too long (95 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:181:46: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:183:1: E302 expected 2 blank lines, found 1
plone/autoform/tests/test_supermodel_handler.py:184:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:186:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:189:27: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:189:63: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:190:27: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:190:64: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:191:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:194:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:197:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:198:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_supermodel_handler.py:198:80: E501 line too long (96 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:199:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_supermodel_handler.py:199:80: E501 line too long (98 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:200:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:203:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:209:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:210:14: D001 found failIf( replace it with assertFalse
plone/autoform/tests/test_supermodel_handler.py:211:14: D001 found failIf( replace it with assertFalse
plone/autoform/tests/test_supermodel_handler.py:212:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:215:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:218:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:221:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:224:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:225:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_supermodel_handler.py:225:27: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:225:59: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:225:80: E501 line too long (94 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:226:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_supermodel_handler.py:226:27: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:226:60: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:226:80: E501 line too long (96 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:227:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:230:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:233:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:235:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:238:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:239:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_supermodel_handler.py:239:51: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:239:80: E501 line too long (86 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:240:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_supermodel_handler.py:240:51: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:240:80: E501 line too long (87 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:244:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:247:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:250:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:251:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_supermodel_handler.py:251:51: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:251:80: E501 line too long (86 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:252:14: D001 found assertEquals replace it with assertEqual
plone/autoform/tests/test_supermodel_handler.py:252:51: Q000 Remove bad quotes.
plone/autoform/tests/test_supermodel_handler.py:252:80: E501 line too long (87 > 79 characters)
plone/autoform/tests/test_supermodel_handler.py:253:1: W293 blank line contains whitespace
plone/autoform/tests/test_supermodel_handler.py:254:1: E302 expected 2 blank lines, found 1
ERROR: /home/jenkins/workspace/package-plone.autoform/plone/autoform/tests/test_utils.py Imports are incorrectly sorted.
plone/autoform/tests/test_utils.py:0:1: C101 Coding magic comment not found
plone/autoform/tests/test_utils.py:0:1: I001 found unsorted imports
plone/autoform/tests/test_utils.py:14:1: E302 expected 2 blank lines, found 1
plone/autoform/tests/test_utils.py:15:1: W293 blank line contains whitespace
plone/autoform/tests/test_utils.py:18:23: Q000 Remove bad quotes.
plone/autoform/tests/test_utils.py:22:1: W293 blank line contains whitespace
plone/autoform/tests/test_utils.py:26:1: W293 blank line contains whitespace
plone/autoform/tests/test_utils.py:29:13: E301 expected 1 blank line, found 0
plone/autoform/tests/test_utils.py:34:1: W293 blank line contains whitespace
plone/autoform/tests/test_utils.py:38:1: W293 blank line contains whitespace
plone/autoform/tests/test_utils.py:42:9: E301 expected 1 blank line, found 0
plone/autoform/tests/test_utils.py:46:1: W293 blank line contains whitespace
plone/autoform/tests/test_utils.py:53:9: E301 expected 1 blank line, found 0
plone/autoform/tests/test_utils.py:57:1: W293 blank line contains whitespace
plone/autoform/tests/test_utils.py:63:9: E301 expected 1 blank line, found 0
plone/autoform/tests/test_utils.py:64:53: E251 unexpected spaces around keyword / parameter equals
plone/autoform/tests/test_utils.py:64:55: E251 unexpected spaces around keyword / parameter equals
plone/autoform/tests/test_utils.py:65:80: E501 line too long (103 > 79 characters)
plone/autoform/tests/test_utils.py:67:1: W293 blank line contains whitespace
plone/autoform/tests/test_utils.py:69:80: E501 line too long (95 > 79 characters)
plone/autoform/tests/test_utils.py:70:1: W293 blank line contains whitespace
plone/autoform/tests/test_utils.py:75:9: E301 expected 1 blank line, found 0
plone/autoform/tests/test_utils.py:76:53: E251 unexpected spaces around keyword / parameter equals
plone/autoform/tests/test_utils.py:76:55: E251 unexpected spaces around keyword / parameter equals
plone/autoform/tests/test_utils.py:79:1: W293 blank line contains whitespace
plone/autoform/tests/test_utils.py:80:80: E501 line too long (95 > 79 characters)
plone/autoform/tests/test_utils.py:81:1: W293 blank line contains whitespace
plone/autoform/tests/test_utils.py:86:9: E301 expected 1 blank line, found 0
plone/autoform/tests/test_utils.py:87:52: E251 unexpected spaces around keyword / parameter equals
plone/autoform/tests/test_utils.py:87:54: E251 unexpected spaces around keyword / parameter equals
plone/autoform/tests/test_utils.py:87:73: E251 unexpected spaces around keyword / parameter equals
plone/autoform/tests/test_utils.py:87:75: E251 unexpected spaces around keyword / parameter equals
plone/autoform/tests/test_utils.py:87:80: E501 line too long (99 > 79 characters)
plone/autoform/tests/test_utils.py:90:1: W293 blank line contains whitespace
```
Follow [these instructions](https://github.com/plone/jenkins.plone.org/blob/master/docs/source/run-qa-on-package.rst) to reproduce it locally.


From what I can tell, the type is only referenced in [hawkular](https://github.com/kubernetes/heapster/blob/master/sinks/hawkular/driver.go#L345) and [gcm](https://github.com/kubernetes/heapster/blob/master/sinks/gcm/driver.go#L35). In the former, there is no equivalent to `delta` and it fallsback to `gauge`, which I believe is correct. In the latter, it registers with the string value, which is the same value recognized by the [gcm API](https://cloud.google.com/monitoring/api/metrics#metric-types). So, I think this should be safe.


Its hard question. Give me time for think.


ok makes sense; that part just needs to be separated a little better.


i wonder if i turned off my style checker.


@Vivalldi I'll add the user access permissions (+ groups permissions) directly in the Login plugin, in the  `User Registration` section.

Currently you can add a default access level, but I'll make it more explicity. OAuth can use them too, as it's a user registration too, just with a different authentication.


Странный href))) href - это куда ведет ссылка, например href=""google.com'


Commit message here lacks sufficient detail and correct formatting/content.

> Add subject line < 50 chars, use imperative verb
>
> Second line blank. Remaining lines should be <= 72 characters and have
> details about *WHY* the changes were made and *WHAT* changes were
> made. Also, any pertinent issues should be linked, like #119

Please see https://robots.thoughtbot.com/5-useful-tips-for-a-better-commit-message and http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html


Compare quarks.


When you use the `new` keyword, you are creating an object (or instance of this class).  When you call `$ouby->run();`, you are using its (the object) methods.  Therefore, within the class itself, you refer to `$ouby` using `$this`.

Only use `static::` then the function is static.


Картинка не нужна


In the future, please use more descriptive commit messages to aid in reviewing and source code archaeology. For example, this commit message could be: `Replaces hard tabs with soft tabs` (Assuming that was the only change)


Got tons of
> EXCEPTION: Attempt to use a dehydrated detector.

when reloading `ag-grid` component using `angular/router`

<img width="1175" alt="2016-02-10 2 08 56" src="https://cloud.githubusercontent.com/assets/1942271/12930683/8e56983a-cf9b-11e5-85c8-87365744d3f6.png">


So much to learn! Thank you! I'm so new to OOP but loving the learning process.


.container - оборачивает все содержимое!


Thanks Brandon. I didn't know about the single line thing. I'll remember
that.

I added all the actions at once because I figured they will be needed as
the project grows.

On Tue, Feb 9, 2016 at 4:07 PM, Brandon Conway <notifications@github.com>
wrote:

> Empty controller actions are not necessary, but it is recommended to make
> them single lines if you do want to include them:
>
> def show; end
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/holdenhinkle/myflix/commit/a3fac6aafb7479fb2635bd6c80c9035913e94ef5#commitcomment-15989415>
> .
>

--
Holden Hinkle
O: (802) 489-6333 ext 101
M: (917) 608-8623
www.webzio.com


Описал ранее - это список ul>li>a, а не select


No worries.  I'll teach it to you!  Good job :+1:


Is this test implemented in the testing mixin?  I couldn't find one similar.


On 2016-02-09 16:06, Richard Hansen wrote:
>> Have you checked that all the places that previously returned -1
>> were supposed to return err_code values?
>
> It's unclear what they're "supposed" to return, but returning
> err_code
> values is not inconsistent with what the callers expect (I did check
> how the callers used the return values). I'll add something to the
> commit message to explain this.

Ok, that's good enough for me.


I *think* you can use try with resources to simplify this logic.


This pull should have updated the README


Каждая форма должна иметь атрибут name=""


Mostly good message and clear commit.

> Rename LOPe/CAFe to OCAF


This name is used as a header in the auto-generated type system documentation. It should IMHO be "Discourse".


probably can be squashed into previous commit.


check out the final typedef: https://github.com/MatthijsKamstra/butterfly/blob/master/Main.hx#L192-L201


Это надо разбирать на консультации


Nicht ausgeschlossen, dass ich mich vertan habe, ich werde das ganze gleich nochmal testen
Ich habe leider gerade erst bemerkt, dass ich das falsche Zeichen gesetzt habe, ich meinte naturlich <4.x bzw >0.12.x, in den offiziellen Debian Repo's gibt es im Moment leider nur die version 0.10.29, die ES6 noch nicht wirklich unterstützt, wenn du die lange Version der Spezifikationen von ES6 haben möchtest: http://www.ecma-international.org/ecma-262/6.0/ alles neue zusammengefasst findest du zB hier: https://github.com/lukehoban/es6features - natürlich musst du nicht auf ES6 verzichten, es wäre aber ganz praktisch, wenn man vor dem starten noch eine Benachrichtigung bekommen würde, dass man bitte auf ES6 upgrade sollte :)


This is not asserted in the refactored test mixin.  Does it no longer apply?


Хлебные крошки не входят в header - это часть content


TeamCity MonoGame :: Develop (Win) [Build 3.5.0.1357](http://teamcity.monogame.net/viewLog.html?buildId=14713&buildTypeId=MonoGame_DevelopWin&guest=1) is now running


The same local test with unvaried bonus for second matrix cycle ended in this way:
Score of variax2 vs base: 840 - 865 - 3295  [0.497] 5000
ELO difference: -2
Thus vary the bonus calculation for the second matrix cycle is necessary to make the whole thing work.


Do you want to propagate the raw IOException out of here or wrapper it with a `PrestoException`


Ik heb uiteindelijk gevonden waar het font probleem aan lag en Ik heb extra code moeten toevoegen om het op te lossen.


Вынеси заголовок перед формой


Toto je OK,  ale premennú files už odteraz nepoužívaš - nechceš to pridať do input?

Alebo VLAN_count (files) použiť tu v cykle
Files je dosť zle meno - to nie sú súbory ale obsah jedného súboru :)


Это не хлебные крошки - этот блок не нужен


Этот блок тоже не нужен


too late, it is released ;)


restoring line 110 of rxtools/source/features/firm.c,

aes_decrypt(hdr->ext.s.keyX_0x16, key, NULL, 1, AES_ECB_DECRYPT_MODE);

seems to fix the installation issues on the O3DS.
I have no idea of what side effects it will have though, hue


yes, that makes more sense.


Broken HintPath to PacketDotNet.dll


Есть тег legend - его применяй


For line in input [1:-1]:
   ...


Maybe add this block as a static helper to HdfsParquetDataSource, so you don't have to repeat it here (and the other place above)


Quoting @hallyn: "Shouldn't this be "d->size - total_len" ?" :) :)
Refer: https://lists.linuxcontainers.org/pipermail/lxc-devel/2016-January/013326.html


Best thing to do here might be to search the environment variables and only set this if needed:

`OFP_HOME ?= $HOME/ofp-sdf # no hardcoding user names`

Probably can be squashed as well.


там еще есть по жирности


ok. fixed again :)


Thank you for your prompt response!
PR: https://github.com/angular-slider/angularjs-slider/pull/258


I believe this is that pattern we want for svg plot types.

- Have a filter function that remove non-visible traces from the data **before** joining them to the selections (instead of having duct-tapy `trace.visible !== true` blocks inside the `.each()`).
- Update the view using `enter().append()` and `exit().remove()`
- Keep everything in sync with a key function returning the trace `uid`.


Same comment as before... do you want to wrapper with a `PrestoException`?


i don't know how add new repo with LGA package 4 LSM303D. pls help


Это всё legend, а внутри него span. Причем каждая цена в своем span


This change should not be committed


Keď to je list, použi množné číslo - vlans?
Veľké písmena sa používajú na konštanty,  používaj malé.


It should be basically none. The biggest differences for now would be:
- old api is missing volume metrics, silghtly different filesystem metrics
- new api does not report pod infra container stats (network & volumes are scoped to the pod)

Since these are all scoped to a node, if there were a mixture of node versions, the above differences would be present between the metrics from the old & new nodes.


a fixed


This should definitely be fixup-ed/amend-ed into the previous commit


I know the solutions have it, but I don't believe the `nil` is necessary here.


Тег legend


This commit can be dropped


Yes ;)  Fixing...


fixup/amend into previous non-dropped commit


Maybe add a `FileParquetDataSource` and switch the tests to use that


The first paper seems to agree with the previous equation:
![First paper equation](https://s0.wp.com/latex.php?latex=%5Cdisplaystyle+%5Csum_i+%5Clog%281%2Br_i%29+%3D+%5Clog%281+%2B+r_1%29+%2B+%5Clog%281+%2B+r_2%29++%2B+%5Ccdots+%2B+%5Clog%281+%2B+r_n%29+%3D+%5Clog%28p_n%29+-+%5Clog%28p_0%29&bg=ffffff&fg=333333&s=0)

Then applying the logarithm identity to the right side of the equation gives us the current equation in the master branch.

I skimmed the second paper and couldn't readily find the equation you're referencing.


Ak budeš mať VLAN 1 a 3, iba 1 ti to overí - 2 nenájde a skončí.


113360729_HumidifierOASys (Nigusse) - i386-Windows-7-VisualStudio-12: OK (2077 of 2077 tests passed, 0 test warnings)

 * 6 tests had: AUD diffs.

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-100.0%25-green.svg)


amend/fixup into previous commit


What about the Windows Version? Is this used anywhere? I'm not sure what it's for but is it intended to show up in the properties of RoR.exe?


@DevVersion definitely. When I read the source for `phantomjs2-ext` I didn't see the reference to the `PHANTOMJS_BIN`. Definitely looks like a better way. Expect to see a commit reflecting it shortly.


Будет легче, если обернуть блоки: Сортировка + Цена + Жирность в 1 общий блок, и Наполнители + Применить тоже обернуть в другой блок


Make sure you don't leave debug statements in your final code. That will cause hiccups when deploying.


Never mind :)
I will add more features in the GP module this year. (eg, Andrew's work and our method)


Would it have been safer to separate the shown changes by several commits for different issues?


`_` should be reserved for unused variables, you are using this one.


Добавить везде после закрывающего span - "/кг"


Nice work! In Task 2, you included  `import sys` and `sys.setrecursionlimit(1001)` but I had to set it even higher (1500) to get it to run. Not sure if this is only a problem on my end, but presumably since it was included in the program it should be set high enough (but I didn't take off points, I'll let Brant decide what to do about that). Very cool how you call your `e_recursive()` function inside your `parser()` function...I hadn't thought about that!


Ang commit-standard: Borde inte status vara INIT ( :large_orange_diamond: ) ifall enbart initierad, ej färdig?


Why not use `create` instead of `new` then `save`?


Yes, librabbitmq depends on ampq:
```
(refinery-platform)vagrant@refinery:/vagrant/refinery$ pip show librabbitmq
---
Metadata-Version: 1.1
Name: librabbitmq
Version: 1.6.1
Summary: AMQP Client using the rabbitmq-c library.
Home-page: http://github.com/celery/librabbitmq
Author: Ask Solem
Author-email: ask@celeryproject.org
License: MPL
Location: /home/vagrant/.virtualenvs/refinery-platform/lib/python2.7/site-packages
Requires: amqp
```


please look at https://github.com/KiCad/SMD_Packages.pretty


Hi


The <track> tag is not showing up in Firefox. It is showing up in Chromium (flash not enabled).


We can add CFURLComponents to the compiler's database while we wait for it to get a proper CF_BRIDGED_TYPE(id).


Is sudo still required? If not it should be removed to make use of the container based infrastructure, see https://github.com/RigsOfRods/rigs-of-rods/issues/267


Oh, never mind. This is a `save` spec. I guess that makes sense :-)


@jpkrohling could you please review and eventually merge?


@NevilleS Thanks again for this! The only change I made after importing was to rebase and adjust the test comments to fit within our 80-char limit.


I see you had something different in mind. Note that we don't use suffixes in master (i.e. agda-2.5 doesn't exists). Does using size-solver-2.4.2.6 in maint-2.4 would be enough?


@rschmukler Just saw you created a new commit :+1: Nice! Just here for you (https://github.com/gskachkov/karma-phantomjs2-launcher/blob/master/index.js#L101) That's the source from the phantomjs2 launcher.


@rouson could you elaborate on the commit log text means? Add support for sync images stat=?


- Add more text information to the email.
- Log all the requests.


:+1: Thanks


Commented code is unnecessary code. Don't get in the habit of leaving it behind in your production code.


Looks good to me. Might tweak message:

> Add `caf_init` and `caf_finalize` calls to Scope


Ссылка не надо оборачивать в div class="hit"


Добавить "/кг"


@ryancole This was the main change after importing - I realized that equivalent but non-`===` input object arg values would cause the alias to be the same but would still end up with different variables. The alias is derived from `JSON.stringify`-ing the value so I used that here to de-dupe.


@ryancole Thanks for working on this!


Thanks Brandon. I guess I should always do a project-wide search for binding.pry just in case?


looking good so far


It's not a public type, which is why it didn't get one the first time around. So this only affects the corelibs version of CF.


Doesn't this return true if none of the args or return type are calculated? So, it would be the opposite of what the method name implies.


This looks like it resolves the back-and forth battle of where OFP_HOME is :smile:


great job


I'll leave it as it was for now.


У тебя в этом блоке лишняя обертка .news-field и в блоке .mailing - лишняя .mailing-field. Т.е. блоки .news и .mailing - должны иметь общую обертку!!!


Looks like this could also be squashed... and maybe a fallback `OFP_HOME ?= $HOME/ofp-sdf` or similar might be useful.


Thanks for this pull request. Looks like you've found a bug.

As an aside, it appears you're not using the same formatting style as us which is leading to an excessive amount of changes. Also, your proposed fix doesn't make use of the Java7+ try-with-resources syntax. Perhaps an alternative would be:

```
    try (Socket clientSocket = new Socket(InetAddress.getLoopbackAddress(), MULTIBIT_HD_NETWORK_SOCKET);
         OutputStream out = clientSocket.getOutputStream()) {

        // Write out the raw external data for parsing by the other instance
        out.write(MESSAGE_START.getBytes(Charsets.UTF_8));
        out.write(message.getBytes(Charsets.UTF_8));
        out.write(MESSAGE_END.getBytes(Charsets.UTF_8));

        log.debug("Successful write to external data listening service.");

    } catch (IOException e) {
      log.error(e.getMessage(), e);
    }

```


good job
add some images


Gotcha. Could probably revert from `Map` back to the plain `Object` from before, now.


you don't have align `=` signs in javascript. :)


Use a manual vtable AGAIN.


После .map идет .container


Definitely don't code ahead, you will end up rewriting the code or never using it. YAGNI (you ain't gonna need it) is the principle which covers this. Since empty actions are unnecessary, you won't necessarily need the explicit actions even if you use those actions.


In a recent live session, Kevin talked about adding an underscore to a variable name that was the same as the method name. There's css class called video here so I thought it might be a good idea to user _video to avoid confusion with the css class name .video.

How would you have handled this? Maybe I should have just left it alone?


(nit) I think this got line-wrapped wrong.


Проверил - отписал!


`ret`


https://github.com/bbatsov/ruby-style-guide#no-single-line-methods for the single line method rule.


Did you notice that you define `g:airline*` multiple times?


And bridged is incorrect semantics on Linux anyhow since there is no objc: however we were getting ARC on the Ref types (hence why we have had to make objc stubs for some RR functions)


Error appears even in case of jumping from initialized `ag-grid` to empty dumb component.


These lines changes should be part of the next commit...


или :last-child если знаешь что их точно три, или уж :nth-child(3n) для каждого третьего если их может быть больше


well done keep it up


Nice good call


Why are firstname and lastName not part of CustomerInfo? Seems like they should belong there.

Also, firstName and lastName always occur together so how about a Name class containing firstName and lastName


Interesting. I have never heard of that approach. The Ruby style guide recommends using `_` to signify an unused variable, so I am not sure how I feel about that. I think I would rather change the variable name completely.


Do you need to resolve `src/core/geometry/qgsgeometryfactory.cpp` too? I'm looking at your [previous, temporary commit](https://github.com/dwadler/QGIS/commit/1c0ea8b80049c965ad8c022e05aa013568fed05d?diff=split) and it looks like you might be missing that.


ширина 390, они должны соприкасаться (на макете разделяющая их тень)


Why not just
```
throw new Error('Could not parse jison grammar,reason: ' + String(e))
```


YAVT


That's definitely an option. Whatever you find necessary to make sure you don't leave them in. The best approach is cleaning them up right after using them.


firstName, lastName and customerInfo are occurring together again!


5382_PoolMakeUpWater (mitchute) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (2092 of 2093 tests passed, 0 test warnings)

 * 6 tests had: AUD diffs.
 * 1 test had: ESO big diffs.
 * 1 test had: Table big diffs.

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-99.95%25-yellow.svg)


а почему правая колонка не равна левой?


Very well written, you are good to go !