Hello, the "en línea stuff" is perfect now and the issue with the editor is almost. Just there still some things that I think you didn't see and a few details. Please find attached a file. Thanks

[correcciones 2.docx](https://github.com/citation-style-language/styles/files/1411834/correcciones.2.docx)


*[Hook UI build recap](http://ci.perseids.org/repo/PerseusDL/canonical-greekLit/3156)*


Ok j'ai trouvé la solution, un ehistoire de ; je recommit


No, i dont dont think this is a good idea. Those big assets do not belong into the codebase.
Better to put them anywhere else (On a server, on a dedicated mandelbulber-assets git repo, ...)
This will highly increase the git checkout time, also bad for the CIs. Also these files are only used for these examples. We cannot force the users to download a huge archive just to get the mandelbulber executable because everything is packed in.

BTW: I am not completely sure how to rollback this change, if we just remove the files, they are still in the git. We would need to manipulate the git history somehow...


There's nothing in this commit (or the previous) that changed locale handling. In fact test00 wasn't changed at all, nor anything test00 tests. Locale handling is an interesting point though, I did not consider that when I wrote the test.


Not working yet


.vscode, а не ./vscode


Test avec une seule liste et uniquement sur taskid pour le POC mais ne fonctionne pas :

app.js:44 Uncaught TypeError: Cannot read property 'focus' of null
    at HTMLButtonElement.<anonymous> (app.js:44)
    at Rf (angular.min.js:36)
    at HTMLButtonElement.d (angular.min.js:36)
(anonymous) @ app.js:44
Rf @ angular.min.js:36
d @ angular.min.js:36


@leifei87 that's correct, currently the `set_password` job will only succeed if the user already exists.


Why this class is abstract??? Why??


This is the class that should be abstract... in a perfect world...


When I run it on my system it produces no output. What version of python and weechat are you using? (Also, if it's easier I can open an issue if you'd rather converse there?)


watch this wizardry

On Tue, Oct 24, 2017 at 1:40 PM, Sebastian Jennen <notifications@github.com>
wrote:

> No, i dont dont think this is a good idea. Those big assets do not belong
> into the codebase.
> Better to put them anywhere else (On a server, on a dedicated
> mandelbulber-assets git repo, ...)
> This will highly increase the git checkout time, also bad for the CIs.
> Also these files are only used for these examples. We cannot force the
> users to download a huge archive just to get the mandelbulber executable
> because everything is packed in.
>
> BTW: I am not completely sure how to rollback this change, if we just
> remove the files, they are still in the git. We would need to manipulate
> the git history somehow...
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/buddhi1980/mandelbulber2/commit/9f9f6cd5ce5f84c62f6b33266406776faaed893a#commitcomment-25163323>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AGtt7dAhq2rm1t7c_swBNv37QY01fKhPks5sviDzgaJpZM4QEtMR>
> .
>


Glad you got it to build, but you could have just cherry picked this commit to fix the build... https://review.lineageos.org/#/c/190342/

Not sure why they only did a 1/2, but not the 2/2 for the t9 dialer? There is a pull request for it, but it hasn't been merged yet in android_packages_apps_PhoneCommon.


While that may be true for the desktop entry specification the same cannot be said for AppStream: "**The ID must follow a reverse-DNS scheme, consisting of {tld}.{vendor}.{product}**".

If you want real examples, take a look at every application on [Flathub](https://github.com/flathub). Also no Gnome and Freedesktop apps (that I can find), that have made the change to a reverse-DNS scheme does it this way.

Additionally I just tried to validate this with `appstream-util validate-relax org.keepassxc.appdata.xml`:

```
org.keepassxc.appdata.xml: FAILED:
• tag-invalid           : <icon> not allowed in desktop appdata
• tag-invalid           : stock icon is not valid [keepassxc]
```


This commit has been mentioned on **Discourse Meta**. There might be relevant details there:

https://meta.discourse.org/t/read-time-misreporting/72370/5


añadir imagen


An intf can have multiple addr family, so this line should be:
`+            os.environ['ADDRFAM'] = ','.join(ifaceobj.addr_family) if ifaceobj.addr_family else ''`

Sorry for asking you more changes, I don't want to accept it as this then make the modification myself, i'm trying to keep the repo clean and that way all the changes belong to you :)


When you want to comment for a post you see only the comment textarea. I deleted the name and email input


asasadasa


Except this file because there are also other files in that directory.


I'm not sure if this layer is needed. There is already the `activation` layer which can apply any function, e.g. log, and there is also `safe_log` which does sth like this, or you can even use any custom string, like `"safe_log(input)/log(base)"` and it will also work.


all tests pass:
success: https://travis-ci.org/stellar/stellar-core/builds/292190607?utm_source=github_status&utm_medium=notification


thank you :)


Yes, sorry. The problem is client opens `/` with session policy at `/foo/bar` and gets '/foo/bar/', which is not valid. But `/baz` -> `/foo/bar/baz` is fine.


Cc: @cvzi

We are breaking one of your userscripts with this... please change `register` search to `login`.

Also there is an issue with your account that I am going to twiddle with... you seem to have two GH auths... I'm going to kill the older one. If you have any issues logging in I'll restore the older one and get rid of the newer one. Please give me a mention here if you are having issues with logging in after I clean it up.

Thanks.


oh, actually it _was_ tested, but it was misspelled below too 😆


Delete this file


you don't need OpenAPITypeWriter anymore. Here is the place we need to have a list of types implementing an interface that can do the validation. Or something like that. Think about parameters you want to pass to that. It could be just type and we add more later.


I think the error handler wont be called according to this macro (the macro just throws). please fix it too and i will merge


@jorlowitz are you aware that this will only show when looking at all edits proposed for a given page? If you want to change the instructions that most people will see, you need to edit `templates/one-edit.html`


Could you open an issue for that, please?


so no need for snippetwriter anymore. You can just keep errors in a struct and initilize it in Init, fill it in generate and validate it here. SnippetWriter is useful for outputing go source code which is not the case here.


Esto se implementará más adelante ya que se hará en el modelo más avanzado con el cliente servidor. Ahora es para tenerlo como referencia


Hmmm, weird, I will fix that up, thank you for bringing it to our attention.


See fix here: https://github.com/facelessuser/sublime-markdown-popups/blob/master/tests/validate_json_format.py#L183


we don't need this function too, Namers are useful in generating go files. If there is a default implementation for Namers and we can remove this function do it, otherwise just return an empty namer.


I originally took this from my C comment stripper code, but JSON doesn't allow single quoted strings, so this line can be removed.


also no need for boilerplate. we are not generating any code.


fast-forwarding master to auto = 13b7e378


O upgrade unifica os dbs UTILS e LUX, facilitando manutenções da tabela de feriados de forma permanente, sem penalização do desempenho.


we can integrate it in this way: https://github.com/buddhi1980/mandelbulber2/issues/402
No need to ship those files with the software...


Again, this line can be removed as single quotes are not valid in JSON.


no need for this too.


delete or return empty if you can't delete this.


.I reworked this but I don't think I've found the most efficient way of doing things....


Have you already seen the PR: https://github.com/geometalab/Vector-Tiles-Reader-QGIS-Plugin/pull/102?

That should work exactly how you describe it.

I think most users don't start by reading the documentation, when they can try it hands on. To make that as simple as possible, the sample folder is offered for the beginning.

Another improvement could be, to replace the text field with a drop down, showing recently used folders.


interesting, why would we need this to be set to Never?


C'est quoi ça !?


[R/cat_names.R:5:18:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/R/cat_names.R#L5) *style:* **Commas should always have a space after.**
```r
  cat(paste(",'",names(x), "'",'\n', sep = ''))
                 ^
```
[R/cat_names.R:5:32:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/R/cat_names.R#L5) *style:* **Commas should always have a space after.**
```r
  cat(paste(",'",names(x), "'",'\n', sep = ''))
                               ^
```
[R/cat_names.R:5:32:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/R/cat_names.R#L5) *style:* **Only use double-quotes.**
```r
  cat(paste(",'",names(x), "'",'\n', sep = ''))
                               ^~~~
```
[R/cat_names.R:5:44:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/R/cat_names.R#L5) *style:* **Only use double-quotes.**
```r
  cat(paste(",'",names(x), "'",'\n', sep = ''))
                                           ^~
```
[R/cat_names.R:7:1:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/R/cat_names.R#L7) *style:* **Trailing blank lines are superfluous.**
```r

^
```
[R/cat_names.R:8:1:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/R/cat_names.R#L8) *style:* **Trailing blank lines are superfluous.**
```r

^
```
[R/cat_names.R:9:1:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/R/cat_names.R#L9) *style:* **Trailing blank lines are superfluous.**
```r

^
```
[R/clusDropVar2.R:21:13:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/R/clusDropVar2.R#L21) *style:* **Commas should never have a space before.**
```r
  vte = c() ,
           ~^
```
[R/clusDropVar2.R:41:29:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/R/clusDropVar2.R#L41) *style:* **Commas should always have a space after.**
```r
        ddm1 <- dudi.mix(x[,vtu1[-i]], add.square = FALSE, scannf = F, nf = ncol(x))
                            ^
```
[R/clusDropVar2.R:51:34:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/R/clusDropVar2.R#L51) *style:* **Commas should always have a space after.**
```r
          pam1 <- clara(ddm1$li[,1:length(ddm1$eig[ddm1$eig > 1])], k = j, samples = 50)
                                 ^
```
[R/clusDropVar2.R:57:44:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/R/clusDropVar2.R#L57) *style:* **Commas should always have a space after.**
```r
            print(paste("i: ", i, " | k: ",j," | sil: ",sil1, " | var: ",vtu1[i], sep = ""));flush.console()
                                           ^
```
[R/clusDropVar2.R:57:46:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/R/clusDropVar2.R#L57) *style:* **Commas should always have a space after.**
```r
            print(paste("i: ", i, " | k: ",j," | sil: ",sil1, " | var: ",vtu1[i], sep = ""));flush.console()
                                             ^
```
[R/clusDropVar2.R:57:57:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/R/clusDropVar2.R#L57) *style:* **Commas should always have a space after.**
```r
            print(paste("i: ", i, " | k: ",j," | sil: ",sil1, " | var: ",vtu1[i], sep = ""));flush.console()
                                                        ^
```
[R/clusDropVar2.R:57:74:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/R/clusDropVar2.R#L57) *style:* **Commas should always have a space after.**
```r
            print(paste("i: ", i, " | k: ",j," | sil: ",sil1, " | var: ",vtu1[i], sep = ""));flush.console()
                                                                         ^
```
[R/clusDropVar2.R:71:109:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/R/clusDropVar2.R#L71) *style:* **Commas should always have a space after.**
```r
      print(paste("Dropping var: ", varToDrop, " | Best Score : ", max(scores1Df$score), " | vtu1 length: ",length(vtu1) , sep = ""));flush.console()
                                                                                ^
```
[R/clusDropVar2.R:71:122:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/R/clusDropVar2.R#L71) *style:* **Commas should never have a space before.**
```r
      print(paste("Dropping var: ", varToDrop, " | Best Score : ", max(scores1Df$score), " | vtu1 length: ",length(vtu1) , sep = ""));flush.console()
                                                                                ~^
```
[R/cnn.R:13:19:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/R/cnn.R#L13) *style:* **Commas should always have a space after.**
```r
    print(paste(i,": ", colnames(dataset)[i], " | ", class(dataset[,i]), sep=""))
                  ^
```
[R/cnn.R:13:69:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/R/cnn.R#L13) *style:* **Commas should always have a space after.**
```r
    print(paste(i,": ", colnames(dataset)[i], " | ", class(dataset[,i]), sep=""))
                                                                    ^
```
[R/cnn.R:13:77:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/R/cnn.R#L13) *style:* **Put spaces around all infix operators.**
```r
    print(paste(i,": ", colnames(dataset)[i], " | ", class(dataset[,i]), sep=""))
                                                                           ~^~
```
[R/ls.objects.R:26:49:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/R/ls.objects.R#L26) *style:* **Put spaces around all infix operators.**
```r
    out <- out[order(out[[order.by]], decreasing=decreasing), ]
                                               ~^~
```
[R/lsos.R:18:26:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/R/lsos.R#L18) *style:* **Put spaces around all infix operators.**
```r
  lsObjects(..., order.by="Size", decreasing=TRUE, head=TRUE, n=n)
                        ~^~
```
[R/lsos.R:18:45:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/R/lsos.R#L18) *style:* **Put spaces around all infix operators.**
```r
  lsObjects(..., order.by="Size", decreasing=TRUE, head=TRUE, n=n)
                                           ~^~
```
[R/lsos.R:18:56:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/R/lsos.R#L18) *style:* **Put spaces around all infix operators.**
```r
  lsObjects(..., order.by="Size", decreasing=TRUE, head=TRUE, n=n)
                                                      ~^~
```
[R/lsos.R:18:64:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/R/lsos.R#L18) *style:* **Put spaces around all infix operators.**
```r
  lsObjects(..., order.by="Size", decreasing=TRUE, head=TRUE, n=n)
                                                              ~^~
```
[R/rankTab.R:12:34:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/R/rankTab.R#L12) *style:* **Commas should always have a space after.**
```r
  tab1 <- tab1[order(-tab1$Freq),]
                                 ^
```
[tests/testthat/test-clusDropVar2.R:7:81:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/tests/testthat/test-clusDropVar2.R#L7) *style:* **Put spaces around all infix operators.**
```r
  d <- clusDropVar(iris, 3:5, threshold = .6, vte = "Species", xLoopsBeforePrint=1)
                                                                               ~^~
```
[tests/testthat/test-lint.R:5:5:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/tests/testthat/test-lint.R#L5) *style:* **Variable and function names should not use underscores.**
```r
    my_linters <- list(
    ^~~~~~~~~~
```
[tests/testthat/test-lint.R:6:28:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/tests/testthat/test-lint.R#L6) *style:* **Put spaces around all infix operators.**
```r
      absolute_paths_linter=absolute_paths_linter,
                          ~^~
```
[tests/testthat/test-lint.R:7:24:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/tests/testthat/test-lint.R#L7) *style:* **Put spaces around all infix operators.**
```r
      assignment_linter=assignment_linter,
                      ~^~
```
[tests/testthat/test-lint.R:8:26:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/tests/testthat/test-lint.R#L8) *style:* **Put spaces around all infix operators.**
```r
      closed_curly_linter=closed_curly_linter,
                        ~^~
```
[tests/testthat/test-lint.R:9:20:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/tests/testthat/test-lint.R#L9) *style:* **Put spaces around all infix operators.**
```r
      commas_linter=commas_linter,
                  ~^~
```
[tests/testthat/test-lint.R:11:26:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/tests/testthat/test-lint.R#L11) *style:* **Put spaces around all infix operators.**
```r
      infix_spaces_linter=infix_spaces_linter,
                        ~^~
```
[tests/testthat/test-lint.R:12:25:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/tests/testthat/test-lint.R#L12) *style:* **Put spaces around all infix operators.**
```r
      line_length_linter=line_length_linter,
                       ~^~
```
[tests/testthat/test-lint.R:13:20:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/tests/testthat/test-lint.R#L13) *style:* **Put spaces around all infix operators.**
```r
      no_tab_linter=no_tab_linter,
                  ~^~
```
[tests/testthat/test-lint.R:14:26:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/tests/testthat/test-lint.R#L14) *style:* **Put spaces around all infix operators.**
```r
      object_usage_linter=object_usage_linter,
                        ~^~
```
[tests/testthat/test-lint.R:15:24:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/tests/testthat/test-lint.R#L15) *style:* **Put spaces around all infix operators.**
```r
      snake_case_linter=snake_case_linter,
                      ~^~
```
[tests/testthat/test-lint.R:16:27:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/tests/testthat/test-lint.R#L16) *style:* **Put spaces around all infix operators.**
```r
      multiple_dots_linter=multiple_dots_linter,
                         ~^~
```
[tests/testthat/test-lint.R:17:27:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/tests/testthat/test-lint.R#L17) *style:* **Put spaces around all infix operators.**
```r
      object_length_linter=object_length_linter,
                         ~^~
```
[tests/testthat/test-lint.R:18:24:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/tests/testthat/test-lint.R#L18) *style:* **Put spaces around all infix operators.**
```r
      open_curly_linter=open_curly_linter,
                      ~^~
```
[tests/testthat/test-lint.R:19:27:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/tests/testthat/test-lint.R#L19) *style:* **Put spaces around all infix operators.**
```r
      single_quotes_linter=single_quotes_linter,
                         ~^~
```
[tests/testthat/test-lint.R:20:27:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/tests/testthat/test-lint.R#L20) *style:* **Put spaces around all infix operators.**
```r
      spaces_inside_linter=spaces_inside_linter,
                         ~^~
```
[tests/testthat/test-lint.R:22:34:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/tests/testthat/test-lint.R#L22) *style:* **Put spaces around all infix operators.**
```r
      trailing_blank_lines_linter=trailing_blank_lines_linter,
                                ~^~
```
[tests/testthat/test-lint.R:23:33:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/tests/testthat/test-lint.R#L23) *style:* **Put spaces around all infix operators.**
```r
      trailing_whitespace_linter=trailing_whitespace_linter
                               ~^~
```
[tests/testthat/test-lint.R:25:36:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/tests/testthat/test-lint.R#L25) *style:* **Put spaces around all infix operators.**
```r
    lintr::expect_lint_free(linters=my_linters)
                                  ~^~
```
[tests/testthat/test-lint.R:25:37:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/tests/testthat/test-lint.R#L25) *style:* **Variable and function names should not use underscores.**
```r
    lintr::expect_lint_free(linters=my_linters)
                                    ^~~~~~~~~~
```
[tests/testthat/test-naHandler.R:15:7:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/tests/testthat/test-naHandler.R#L15) *style:* **Commas should always have a space after.**
```r
  x[1,] <- NA
      ^
```
[tests/testthat/test-naHandler.R:17:18:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/tests/testthat/test-naHandler.R#L17) *style:* **Only use double-quotes.**
```r
  expect_is(nas, 'list')
                 ^~~~~~
```
[tests/testthat/test-rankTab.R:10:28:](https://github.com/barrenWuffet/convPkg/blob/3a75d5a14d194af94ed5c5c6f3c81dee1f59ebea/tests/testthat/test-rankTab.R#L10) *style:* **Commas should always have a space after.**
```r
  expect_equal(dim(d), c(3,2))
                           ^
```


![](https://github.trello.services/images/mini-trello-icon.png) [L: Umfeld des Kunden](https://trello.com/c/fT0Mu1PJ/2-l-umfeld-des-kunden)


formatting


Looks good


Here is the place that you can return a constant package list with one package in it as empty as possible (no header text, package path of current folder or something, package name a default constant, etc.)


@ellieking17 scripts like this should be stored in another repo. This repo should be the vanilla image, with run.sh supplied as an example.


They have the same hash. Is this right?


Bluemix [toolchain](https://console.bluemix.net/devops/toolchains/fa51d227-7223-448a-b32d-3f4359bb48e5 "simple-toolchain-20171024180003118"): [Delivery Pipeline](https://console.bluemix.net/devops/pipelines/4163f4e0-4148-49dc-ae9b-00382c838d73 "simple-toolchain-20171024180003118") deployed [simple-toolchain-20171024180003118](https://github.com/RicardoFideles/simple-toolchain-20171024180003118/releases/tag/deploy-ibm-yp-us-south-ricardo.fideles-ibm.com-dev-20171024-180628 "deploy-ibm-yp-us-south-ricardo.fideles-ibm.com-dev-20171024-180628") to [dev](https://console.bluemix.net/apps/eb6d7dce-b6c3-46d3-ada4-3431e0b54378?env_id=ibm:yp:us-south "ibm:yp:us-south:ricardo.fideles@ibm.com:dev"), including this commit


Test également en utilisant un second bouton pour forcer le mode edition puis cliquer sur le bouton d'auto focus . Toujours pareil. Test également avec  <button id='btn' set-focus='item.taskid'>click</button>. Toujours pareil. Test avec un span pour voir si item.taskid est bien reconnu et il le calcule bien.


dropped this commit from the repo. I still feel we need at least two fully operation animation by sound examples to ship with the opencl package.  gpu+animation+audio (core features) are unique to mandelbulber and are well worth a couple megabytes in the long run.


I added the Registration button in the navigation


Bluemix [toolchain](https://console.bluemix.net/devops/toolchains/c74f8248-fea8-440b-bfd4-822ecb10c7be "emma-toolchain"): [Delivery Pipeline](https://console.bluemix.net/devops/pipelines/0811a336-3049-4159-ba04-aaf43efd0023 "emma") deployed [leave](https://github.com/goyal-sidd/leave/releases/tag/deploy-ibm-yp-us-south-sid22-leave-20171024-181000 "deploy-ibm-yp-us-south-sid22-leave-20171024-181000") to [leave](https://console.bluemix.net/apps/0e816a54-7da8-4450-8e72-70dc537dc333?env_id=ibm:yp:us-south "ibm:yp:us-south:sid22:leave"), including this commit


what is this jsjsjs? it makes no sense @Domixx
http://gif-finder.com/wp-content/uploads/2015/08/Leonardo-DiCaprio-OMG.gif


It Work For Me Like FFS Server
164.132.203.192:22003


incorrect spelling, should be seppuku


cloneladim, cok tesekkurler 😄


yes, you are right


When a client disconnects, this method will try to read from a broken pipe


I wasn't able to retrieve PDD puzzles from the code base and submit them to GitHub. If you think that it's a bug on your our side, please submit it to [yegor256/0pdd](https://github.com/yegor256/0pdd/issues)):

> 534-5.7.14 <https://accounts.google.com/signin/continue?sarp=1&scc=1&plt=AKgnsbsd

Please, copy and paste this stack trace to GitHub:

```
534-5.7.14 <https://accounts.google.com/signin/continue?sarp=1&scc=1&plt=AKgnsbsd

/home/irbuch/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/net/smtp.rb:977:in `check_auth_response'
/home/irbuch/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/net/smtp.rb:741:in `auth_plain'
/home/irbuch/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/net/smtp.rb:733:in `authenticate'
/home/irbuch/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/net/smtp.rb:568:in `do_start'
/home/irbuch/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/net/smtp.rb:521:in `start'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/mail-2.6.6/lib/mail/network/delivery_methods/smtp.rb:111:in `deliver!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/mail-2.6.6/lib/mail/message.rb:253:in `deliver!'
/home/irbuch/Documents/projects/0pdd/objects/job_emailed.rb:72:in `block in proceed'
/home/irbuch/Documents/projects/0pdd/objects/job_emailed.rb:44:in `each'
/home/irbuch/Documents/projects/0pdd/objects/job_emailed.rb:44:in `rescue in proceed'
/home/irbuch/Documents/projects/0pdd/objects/job_emailed.rb:35:in `proceed'
/home/irbuch/Documents/projects/0pdd/objects/job_commiterrors.rb:36:in `proceed'
/home/irbuch/Documents/projects/0pdd/objects/job_detached.rb:49:in `block in exclusive'
/home/irbuch/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:91:in `block in timeout'
/home/irbuch/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:33:in `block in catch'
/home/irbuch/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:33:in `catch'
/home/irbuch/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:33:in `catch'
/home/irbuch/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:106:in `timeout'
/home/irbuch/Documents/projects/0pdd/objects/job_detached.rb:47:in `exclusive'
/home/irbuch/Documents/projects/0pdd/objects/job_detached.rb:37:in `block in proceed'
/home/irbuch/Documents/projects/0pdd/objects/job_detached.rb:37:in `fork'
/home/irbuch/Documents/projects/0pdd/objects/job_detached.rb:37:in `proceed'
0pdd.rb:347:in `block in <main>'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1632:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1632:in `block in compile!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:991:in `block (3 levels) in route!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1010:in `route_eval'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:991:in `block (2 levels) in route!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1037:in `block in process_route'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1035:in `catch'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1035:in `process_route'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:989:in `block in route!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:988:in `each'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:988:in `route!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1094:in `block in dispatch!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `block in invoke'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `catch'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `invoke'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1091:in `dispatch!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:923:in `block in call!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `block in invoke'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `catch'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `invoke'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:923:in `call!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:913:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-protection-2.0.0/lib/rack/protection/xss_header.rb:18:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-protection-2.0.0/lib/rack/protection/path_traversal.rb:16:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-protection-2.0.0/lib/rack/protection/json_csrf.rb:26:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-protection-2.0.0/lib/rack/protection/base.rb:50:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-protection-2.0.0/lib/rack/protection/base.rb:50:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-protection-2.0.0/lib/rack/protection/frame_options.rb:31:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-2.0.3/lib/rack/logger.rb:15:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-2.0.3/lib/rack/common_logger.rb:33:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:231:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:224:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-2.0.3/lib/rack/head.rb:12:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-2.0.3/lib/rack/method_override.rb:22:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/show_exceptions.rb:22:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:194:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1955:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1499:in `block in call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1726:in `synchronize'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1499:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/thin-1.7.2/lib/thin/connection.rb:86:in `block in pre_process'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/thin-1.7.2/lib/thin/connection.rb:84:in `catch'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/thin-1.7.2/lib/thin/connection.rb:84:in `pre_process'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/thin-1.7.2/lib/thin/connection.rb:50:in `block in process'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/eventmachine-1.2.5/lib/eventmachine.rb:1076:in `block in spawn_threadpool'
```


How about `2.0.0-alpha.1`? We are bumping the react version.


Not that it matters much, but I won't upgrade. I can live with a fixed version of an excellently engineered library.

This was an unfortunate decision - we're reaching a point where mentioning genders becomes taboo.


@mclarekin @buddhi1980 @zebastian
regarding https://github.com/buddhi1980/mandelbulber2/issues/337, how large do we want all examples rendered to verify all images?


saw approval from MonsieurNicolas
at https://github.com/MonsieurNicolas/stellar-core/commit/17786c449e101606667abbafbfac1c279e2d49cf


merging MonsieurNicolas/stellar-core/scpValidate = 17786c44 into auto


MonsieurNicolas/stellar-core/scpValidate = 17786c44 merged ok, testing candidate = e55d2dce


Cheers for the commit


Exercise with Constructor Methods, Constants and Bidirectional Associations


hi pro I from Egypt and I can't use the  Syntax-highlighting-for-Sass please  tell me how can I use this  excitation by anyway like video or anything... thank you I waiting for your reply just for a note I use sublime text 3


Ah - I missed the commit there - sorry about that!


You love give me newer job !!
Pff, After the one in course ;-)


When would you want to use a remote repository rather than keeping all your work local?
I guess it would be a good idea to use the remote repository from a shared computer.


Are you using version 13.8 of Autorunsc.exe? I see that _-nobanner_ is no longer an option on the [https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns](usage page,) but when I run it locally it is still an option in the usage output. Also if I do not have  _-nobanner_ specified the banner messes up the CSV output. I ran into this with sigcheck.exe as well. I was thinking about making a pull request for it. Let me know if you are getting different results. If not we may need to put the  _-nobanner_ flag back in.


man this lazyload for the main slider works :D it deserved:
a) a standalone commit :P
b) the front js _parts to be updated :P :P
'dad


Minimum version is 2.11.8


I wasn't able to retrieve PDD puzzles from the code base and submit them to GitHub. If you think that it's a bug on your our side, please submit it to [yegor256/0pdd](https://github.com/yegor256/0pdd/issues)):

> 554 Message rejected: Email address is not verified. The following identities failed the check in region US-EAST-1: no-reply@0pdd.com, admin@0pdd.com, 0pdd <no-reply@0pdd.com>

Please, copy and paste this stack trace to GitHub:

```
554 Message rejected: Email address is not verified. The following identities failed the check in region US-EAST-1: no-reply@0pdd.com, admin@0pdd.com, 0pdd <no-reply@0pdd.com>

/home/irbuch/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/net/smtp.rb:965:in `check_response'
/home/irbuch/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/net/smtp.rb:919:in `data'
/home/irbuch/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/net/smtp.rb:664:in `block in send_message'
/home/irbuch/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/net/smtp.rb:859:in `rcptto_list'
/home/irbuch/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/net/smtp.rb:664:in `send_message'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/mail-2.6.6/lib/mail/network/delivery_methods/smtp.rb:112:in `block in deliver!'
/home/irbuch/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/net/smtp.rb:522:in `start'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/mail-2.6.6/lib/mail/network/delivery_methods/smtp.rb:111:in `deliver!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/mail-2.6.6/lib/mail/message.rb:253:in `deliver!'
/home/irbuch/Documents/projects/0pdd/objects/job_emailed.rb:72:in `block in proceed'
/home/irbuch/Documents/projects/0pdd/objects/job_emailed.rb:44:in `each'
/home/irbuch/Documents/projects/0pdd/objects/job_emailed.rb:44:in `rescue in proceed'
/home/irbuch/Documents/projects/0pdd/objects/job_emailed.rb:35:in `proceed'
/home/irbuch/Documents/projects/0pdd/objects/job_commiterrors.rb:36:in `proceed'
/home/irbuch/Documents/projects/0pdd/objects/job_detached.rb:49:in `block in exclusive'
/home/irbuch/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:91:in `block in timeout'
/home/irbuch/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:33:in `block in catch'
/home/irbuch/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:33:in `catch'
/home/irbuch/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:33:in `catch'
/home/irbuch/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:106:in `timeout'
/home/irbuch/Documents/projects/0pdd/objects/job_detached.rb:47:in `exclusive'
/home/irbuch/Documents/projects/0pdd/objects/job_detached.rb:37:in `block in proceed'
/home/irbuch/Documents/projects/0pdd/objects/job_detached.rb:37:in `fork'
/home/irbuch/Documents/projects/0pdd/objects/job_detached.rb:37:in `proceed'
0pdd.rb:347:in `block in <main>'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1632:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1632:in `block in compile!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:991:in `block (3 levels) in route!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1010:in `route_eval'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:991:in `block (2 levels) in route!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1037:in `block in process_route'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1035:in `catch'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1035:in `process_route'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:989:in `block in route!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:988:in `each'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:988:in `route!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1094:in `block in dispatch!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `block in invoke'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `catch'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `invoke'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1091:in `dispatch!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:923:in `block in call!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `block in invoke'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `catch'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `invoke'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:923:in `call!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:913:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-protection-2.0.0/lib/rack/protection/xss_header.rb:18:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-protection-2.0.0/lib/rack/protection/path_traversal.rb:16:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-protection-2.0.0/lib/rack/protection/json_csrf.rb:26:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-protection-2.0.0/lib/rack/protection/base.rb:50:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-protection-2.0.0/lib/rack/protection/base.rb:50:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-protection-2.0.0/lib/rack/protection/frame_options.rb:31:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-2.0.3/lib/rack/logger.rb:15:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-2.0.3/lib/rack/common_logger.rb:33:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:231:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:224:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-2.0.3/lib/rack/head.rb:12:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-2.0.3/lib/rack/method_override.rb:22:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/show_exceptions.rb:22:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:194:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1955:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1499:in `block in call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1726:in `synchronize'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1499:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/thin-1.7.2/lib/thin/connection.rb:86:in `block in pre_process'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/thin-1.7.2/lib/thin/connection.rb:84:in `catch'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/thin-1.7.2/lib/thin/connection.rb:84:in `pre_process'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/thin-1.7.2/lib/thin/connection.rb:50:in `block in process'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/eventmachine-1.2.5/lib/eventmachine.rb:1076:in `block in spawn_threadpool'
```


Bluemix [toolchain](https://dev-console.stage1.bluemix.net/devops/toolchains/5d253847-4ee8-487a-9362-0472a3c0f77a "UI-clienv-SimpleTC1024T141525"): [Delivery Pipeline](https://dev-console.stage1.bluemix.net/devops/pipelines/42acb5a9-7689-42ba-a5d4-e719c11203f6 "UI-clienv-SimpleTC1024T141525") deployed [UI-clienv-SimpleTC1024T141525](https://github.com/pickforc/UI-clienv-SimpleTC1024T141525/releases/tag/deploy-ibm-ys1-us-south-donuds-gmail.com-dev-20171024-182152 "deploy-ibm-ys1-us-south-donuds-gmail.com-dev-20171024-182152") to [dev](https://console.stage1.bluemix.net/apps/662cfc59-530e-4118-be7e-253c28e58e53?env_id=ibm:ys1:us-south "ibm:ys1:us-south:donuds@gmail.com:dev"), including this commit


rica ederim :D


This line makes me a little nervous.  It looks like PaginatableObjects is used by a bunch of places -- for at least some of the other cases, is using the ES search order correct?  (I'm particularly concerned about the call from `app/services/search_translations_finder.rb`.)  Can you take a look?

It may be that we need to use DB order here and ES order in other cases, which means either passing a flag to `initialize()` or doing some refactoring.


Don't forget about PHP's `DIRECTORY_SEPARATOR` constant.


We were debating where it should be, but now that I'm thinking about it special modes would be a better place indeed.


This was mostly a heads up. And I don't disagree, that this should be fixed in the Node Tools. However we won't be able to fix this until 15.5 ships... which means customers will be broken for a while.

And hopefully you can include my scenario in your testing for future fixes.


The name `filteredVersion` is adding anything to the code. Just yield `version.presentation`


Large volume of diff spam from what looks like a pgdump behavior change; it doesn't bother me but they may ask us to remove it when we submit.  I guess we'll see.


@neilbrown, any chance you can prep a patch adding this back in then, with an explanatory comment about the situation?


Hay un error aquí es js/js-dom.js


The above fields can be `private`


oh wait, but we already had the loader:
https://github.com/presscustomizr/customizr/blob/v4.0.8/inc/assets/less/tc_custom.less#L1524

we might want to remove that now


tem com ver se esta certo?


Hello, can I ask you to customize the development of a source code for me? I pay you dollars


Bluemix [toolchain](https://console.td.ca-east.bluemix.net/devops/toolchains/199b7b87-0060-4066-8c34-aba9022dcf2f "curtispd-toolchain-20171024182327975"): [Delivery Pipeline](https://console.td.ca-east.bluemix.net/devops/pipelines/fc66caf8-19ca-463a-9c8b-3baa677032c1 "curtispd-toolchain-20171024182327975") deployed [curtispd-toolchain-20171024182327975](https://github.com/curtispd/curtispd-toolchain-20171024182327975/releases/tag/deploy-td-prod-ca-east-BluemixDevOpsORG-temp-20171024-182540 "deploy-td-prod-ca-east-BluemixDevOpsORG-temp-20171024-182540") to [temp](https://console.td.ca-east.bluemix.net/apps/64641857-2166-43ab-ae6e-ed9451457858?env_id=td:prod:ca-east "td:prod:ca-east:BluemixDevOpsORG:temp"), including this commit


Попытайтесь разобраться в структуре этого файла. Он, конечно, большой и сложный для понимания. Но по крайней мере по аналогии с другими действиями можно заметить, что изменений должно быть больше.

И запустите, пожалуйста, веб-приложение локально. Иначе вы делаете изменения вслепую, не понимая что они означают.

В предыдущем сообщении всего три подготовительных шага. Далее - Из IDEA нужно только запустить Main class: ru.naumen.perfhouse.PerfhouseApplication Без указания дополнительных опций виртуальной машины и без всяких аргументов.

Далее открыть в браузере localhost:8080


Nice catch, will fix soon


I wasn't able to retrieve PDD puzzles from the code base and submit them to GitHub. If you think that it's a bug on your our side, please submit it to [yegor256/0pdd](https://github.com/yegor256/0pdd/issues)):

>

Please, copy and paste this stack trace to GitHub:

```

/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/aws-sdk-s3-1.4.0/lib/aws-sdk-s3/object.rb:262:in `rescue in exists?'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/aws-sdk-s3-1.4.0/lib/aws-sdk-s3/object.rb:258:in `exists?'
/home/irbuch/Documents/projects/0pdd/objects/s3.rb:38:in `load'
/home/irbuch/Documents/projects/0pdd/objects/logged_storage.rb:31:in `load'
/home/irbuch/Documents/projects/0pdd/objects/safe_storage.rb:33:in `load'
/home/irbuch/Documents/projects/0pdd/objects/versioned_storage.rb:31:in `load'
/home/irbuch/Documents/projects/0pdd/objects/cached_storage.rb:34:in `load'
/home/irbuch/Documents/projects/0pdd/objects/once_storage.rb:30:in `load'
/home/irbuch/Documents/projects/0pdd/objects/puzzles.rb:37:in `deploy'
/home/irbuch/Documents/projects/0pdd/objects/job.rb:40:in `proceed'
/home/irbuch/Documents/projects/0pdd/objects/job_starred.rb:33:in `proceed'
/home/irbuch/Documents/projects/0pdd/objects/job_recorded.rb:32:in `proceed'
/home/irbuch/Documents/projects/0pdd/objects/job_emailed.rb:35:in `proceed'
/home/irbuch/Documents/projects/0pdd/objects/job_commiterrors.rb:36:in `proceed'
/home/irbuch/Documents/projects/0pdd/objects/job_detached.rb:49:in `block in exclusive'
/home/irbuch/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:91:in `block in timeout'
/home/irbuch/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:33:in `block in catch'
/home/irbuch/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:33:in `catch'
/home/irbuch/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:33:in `catch'
/home/irbuch/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:106:in `timeout'
/home/irbuch/Documents/projects/0pdd/objects/job_detached.rb:47:in `exclusive'
/home/irbuch/Documents/projects/0pdd/objects/job_detached.rb:37:in `block in proceed'
/home/irbuch/Documents/projects/0pdd/objects/job_detached.rb:37:in `fork'
/home/irbuch/Documents/projects/0pdd/objects/job_detached.rb:37:in `proceed'
0pdd.rb:347:in `block in <main>'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1632:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1632:in `block in compile!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:991:in `block (3 levels) in route!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1010:in `route_eval'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:991:in `block (2 levels) in route!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1037:in `block in process_route'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1035:in `catch'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1035:in `process_route'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:989:in `block in route!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:988:in `each'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:988:in `route!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1094:in `block in dispatch!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `block in invoke'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `catch'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `invoke'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1091:in `dispatch!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:923:in `block in call!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `block in invoke'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `catch'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `invoke'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:923:in `call!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:913:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-protection-2.0.0/lib/rack/protection/xss_header.rb:18:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-protection-2.0.0/lib/rack/protection/path_traversal.rb:16:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-protection-2.0.0/lib/rack/protection/json_csrf.rb:26:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-protection-2.0.0/lib/rack/protection/base.rb:50:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-protection-2.0.0/lib/rack/protection/base.rb:50:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-protection-2.0.0/lib/rack/protection/frame_options.rb:31:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-2.0.3/lib/rack/logger.rb:15:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-2.0.3/lib/rack/common_logger.rb:33:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:231:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:224:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-2.0.3/lib/rack/head.rb:12:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-2.0.3/lib/rack/method_override.rb:22:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/show_exceptions.rb:22:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:194:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1955:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1499:in `block in call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1726:in `synchronize'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1499:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/thin-1.7.2/lib/thin/connection.rb:86:in `block in pre_process'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/thin-1.7.2/lib/thin/connection.rb:84:in `catch'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/thin-1.7.2/lib/thin/connection.rb:84:in `pre_process'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/thin-1.7.2/lib/thin/connection.rb:50:in `block in process'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/eventmachine-1.2.5/lib/eventmachine.rb:1076:in `block in spawn_threadpool'
```


eikliw


Analizador léxico (ciclos)


开题报告和开题PPT


The monotonic start time is needed to handle changes in time. If a time change occurs, some time domains are no longer useful and will result in scheduling/deadline failure.


just changed the author to be my github user instead of my gitlab user :)


Hi @atrol
Would you be willing to provide a translation for this line?
Kind regards
SL-Gundam


![](https://github.trello.services/images/mini-trello-icon.png) [Get familiar with Rake](https://trello.com/c/bU4gda2T/8-get-familiar-with-rake)


I tried these changes with 1.6.1.  No other changes other than this one.

`Fatal error: Call to undefined method AsgarosForumProfile::getCurrentTitle() in /public_html/wp-content/plugins/asgaros-forum/includes/forum.php on line 330`

We will update automatically anyways so I changed line 330 for now
`$mainTitle = __('My Profile', 'asgaros-forum');`

I don't think I missed anything, what do you think? Next update probably takes care of it I bet though.

Will R.


@Dan9er correct. I don't see why the reader should stop just because it hit an empty line.


Created multidev environment [ciccweb#pr-flyswatt](https://dashboard.pantheon.io/sites/cbc91b53-e053-4c27-8ad4-7502151a02ed#pr-flyswatt).

[![Visit Site](https://raw.githubusercontent.com/pantheon-systems/ci-drops-8/0.1.0/data/img/visit-site-36.png)](https://pr-flyswatt-ciccweb.pantheonsite.io/)


I have personal reasons to don't like this commit.


yeah!


this should be reverted


Bluemix [toolchain](https://console.bluemix.net/devops/toolchains/c74f8248-fea8-440b-bfd4-822ecb10c7be "emma-toolchain"): [Delivery Pipeline](https://console.bluemix.net/devops/pipelines/0811a336-3049-4159-ba04-aaf43efd0023 "emma") deployed [leave](https://github.com/goyal-sidd/leave/releases/tag/deploy-ibm-yp-us-south-sid22-leave-20171024-183606 "deploy-ibm-yp-us-south-sid22-leave-20171024-183606") to [leave](https://console.bluemix.net/apps/0e816a54-7da8-4450-8e72-70dc537dc333?env_id=ibm:yp:us-south "ibm:yp:us-south:sid22:leave"), including this commit


Associate issue #22


iret should be handling this for all cases


Thanks buddy !


Not many. Maybe 75-100?

I'll submit the PR. Thanks for taking the time to help look into this.

Glenn Waldron

On Mon, Oct 23, 2017 at 7:42 PM, scrawl <notifications@github.com> wrote:

> That's odd. How many Drawables are we talking? If you there are thousands
> of Drawables with only a few vertices each then I could see how scene graph
> management overheads could start to pop up during the merging.
>
> Feel free to make a PR for reintroducing the 'take a reference' code then
> - shouldn't be a controversial addition as it was already there in the last
> release,
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/openscenegraph/OpenSceneGraph/commit/e0f7d3241af56751fa8e70922c1a17511aeb16cc#commitcomment-25145567>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AAT72tBU9jewzbhkq9Y1zx0yAYnNoA45ks5svSRwgaJpZM4P_363>
> .
>


blabla


Explicit assignment is error prone. I forgot, for example to initialize `filename` which would not happen if struct was zeroed. Why should I, besides adding struct member, also set it to `0`, and even crazier, to define some garbage `define` or `enum` to `0` to set it just once...


payload generated from simple-ducky


You mean the additional issue? Or one for both? In any case sure, I was about to ask if you preferred me to do that way.


Yeah, now if I could figure out to cherry pick commits from the GitHub UI, as I don't want to disable registration...  o.O


*[Hook UI build recap](http://ci.perseids.org/repo/PerseusDL/canonical-greekLit/3158)*


Thanks for the update!


Both.


No longer float version :)


Update


*[Hook UI build recap](http://ci.perseids.org/repo/PerseusDL/canonical-greekLit/3159)*


"api/soap/mc_file_api.php" no se puede encontrar. EmailReporting requiere este fichero para funcionar.


Got it, I will open a new issue when I get the opportunity.


```
<a href="#top1">Биография
 +                	</a>
```
Тут не обязательно так делать


*[Hook UI build recap](http://ci.perseids.org/repo/PerseusDL/canonical-greekLit/3160)*


```
$s_plugin_EmailReporting_apisoap_error = 'Die Datei "api/soap/mc_file_api.php" ist nicht vorhanden. EmailReporting benötigt diese Datei zum Betrieb.';
```


*[Hook UI build recap](http://ci.perseids.org/repo/PerseusDL/canonical-greekLit/3161)*


Please feel free to choose one approach or the other: set `CONTENT_DEFAULT = 0` and then stay with the `memset()` (or maybe `calloc()`), or don't include the `= 0` on the `enum`, but then add explicit `entity->disposition = CONTENT_DEFAULT;` so that you don't rely on the specific enum values/order.


@rduivenvoorde - sorry the new label bar probably [needs-docs]. Fixes https://issues.qgis.org/issues/9405.


Niepotrzebna spacja po i.


"Helper fucntion -- checks if there is an opponent's piece ajacent to your piece."
def opponent_ajacent(pos1, pos2, BOARD):
    # if two coordinates are in the same row and the ajacent spot is not blank
    if (pos1[0] == pos2[0]):
        if ((abs(pos1[1]-pos2[1])) == 1 and (BOARD[pos2[0]][pos2[1]] != blank)):
            return True

    # if two coordinates in the same column
    elif (pos1[1] == pos2[1]):
        if ((abs(pos1[0]-pos2[0]) == 1) and (BOARD[pos2[0]][pos2[1]] != blank)):
            return True
    return False

"Generates all possible moves."
def generate_moves(X_or_O, BOARD):
    possible_moves = []
    jump_to = (0, 0)
    up, down, left, right = 2

    for row in BOARD:
        for col in BOARD:
            "Specify whether looking for Dark/Light moves."
            if (BOARD[row][col] == X_or_O):

                # current position
                current_pos = (row, col)

                "Can this piece move North?"
                # is move within scope of the board?
                while ((row - up) > 0):
                    jump_to = (row - up, col)

                    # is there an opponent's piece ajacent to this piece?
                    if (opponent_ajacent(current_pos, jump_to) == True):
                        # is there a blank space where we need to jump?
                        if (jump_to == blank):
                            possible_moves.append((row, col), jump_to)

                    # update how far up you'll jump
                    current_pos = jump_to
                    up = up - 2

                "Can this piece move South?"
                # is move within scope of the board?
                while ((row + down) < num_rows+1):
                    jump_to = (row + down, col)

                    # is there an opponent's piece ajacent to this piece?
                    if (opponent_ajacent(current_pos, jump_to) == True):
                        # is there a blank space where we need to jump?
                        if (jump_to == blank):
                            possible_moves.append((row, col), jump_to)

                    # update how far up you'll jump
                    current_pos = jump_to
                    down = down + 2

                "Can this piece move East?"
                # is move within scope of the board?
                while ((col + right) < num_cols+1):
                    jump_to = (row, col + right)

                    # is there an opponent's piece ajacent to this piece?
                    if (opponent_ajacent(current_pos, jump_to) == True):
                        # is there a blank space where we need to jump?
                        if (jump_to == blank):
                            possible_moves.append((row, col), jump_to)

                    # update how far up you'll jump
                    current_pos = jump_to
                    right = right + 2

                "Can this piece move West?"
                # is move within scope of the board?
                while ((col - left < num_cols+1):
                    jump_to = (row, col - left)

                    # is there an opponent's piece ajacent to this piece?
                    if (opponent_ajacent(current_pos, jump_to) == True):
                        # is there a blank space where we need to jump?
                        if (jump_to == blank):
                            possible_moves.append((row, col), jump_to)

                    # update how far up you'll jump
                    current_pos = jump_to
                    left = left - 2

    return possible_moves


damn it, here it is again.
@mancoast I have not pulled before commiting, can you remove it again please?
@buddhi1980 @mclarekin make sure you pull from github as soon as the commit is purged again, otherwise it will be added again.


@rduivenvoorde I'm sorry, doesn't this new label bar require [needs-doc]? It fixes  https://issues.qgis.org/issues/9405


Will roll out changes to documentation and other media and communication over the week.


Skoro i tak piszesz petle do dodawania to dlaczego inicjalizacji graczy nie umiescisz w petli ?

for (int i =0; i<Numofplayers; i++)
{
       Player* player = new Player();

       player ->setCash(1000);
       player->setPosition(0);
       player ->setNrPlayer(0);
       players.push_back(player);
}

Ponadto.. Iterujesz do Numofplayers a ZAWSZE odwolujesz sie do indeksow 0 i 1. Co jesli jest jeden gracz? Wyjscie poza tablice. Co jak jest 3 ? Niezainicjalizowany obiekt trzeciego gracza.


так не добре
це потрібно в циклі перебирати


Tak sie nie dodaje plikow wlasnych. Skoro wyzej masz #include "card.h" to czemu potem piszesz z <> ?


hm. I'm running 5.6 and activated the multiply option but somehow I still see the not-multiplied price. Does it work for you?


@mancoast can you try and replace your local ogg resources in your examples with a URL pointing to those files? Should be a trustful source, something like wikimedia or so.
When you load it the file should be automagically downloaded to a cache folder.
Please let me know, if you experience any issues.


Not sure why you changed the pattern from `as` to `is` + cast here.


A skąd niby ten pomysl że NumOfPlayers zawsze wynosi 2?

Zły styl. Inne pola piszesz z małych liter tutaj nagle się wyrwałeś z dużą literą na początek.


це варто перебирати в циклі


A te 120 to niby skad? Magiczna liczba? Nie lepiej przekazać wymiary całej tablicy do konstruktora i liczyć proporcjonalnie? Poza tym czy liczenie czegokolwiek powinno być w konstruktorze czy w odzielnej metodzie skoro przy resize powinno się wszystko zmieniać ? W tym wypadku raz utworzone nigdy się nie zmieni. Na monitorze 4k i na 1024x768 ma to mieć takie same wymiary ?


10/10 best code


all tests pass:
success: https://travis-ci.org/stellar/stellar-core/builds/292222983?utm_source=github_status&utm_medium=notification


I skąd te 16? Takie liczby nie powinny pojawiać się w kodzie bo potem szukanie błędu to koszmar. Jak masz już coś wpisać na stałe to robisz to w pliku h.


Change this to
```cpp
if (joy_paths.size() != 0 && std::find(joy_paths.begin(), joy_paths.end(), path) == joy_paths.end())
```


можна в класі Bird перевизначити метод toString() і тоді тут
System.out.println(birds[i])


I tried several settings. It seems like the multiplier from currencyA is used for all currencies, while all the other multiplier settings are getting ignored


[Core/ContextMenu] ContextMenu respects dark theme (#1722)

Preview: documentation
Coverage: core | datetime


Why so small amount of time ?
If file has 4GB it will stop downloading it or streaming.


0 komentarza.

Po cholere odwolujesz sie do pozygu do tego cardsUI[i] ? Nie lepiej na samym początku pętli ustawić sobie wskaźnik?

CardUI* mojPieknyZajebistyWskaznikKtoregoBedeUzywalINieBedeMusialZaKazdymRazemWpisywacIndexu = cardsUI[i];

i potem. Juz w normalna nazwa

wsk -> setCard(...
wstk -> setPixmap(...

etc.


Bluemix [toolchain](https://console.stage1.bluemix.net/devops/toolchains/8884bbc1-17f4-44f2-8c58-e0835f220383 "UI-ys1int-SimpleTC1024T144451"): [Delivery Pipeline](https://console.stage1.bluemix.net/devops/pipelines/a9fcf18c-167f-4230-be5a-f47bacd1074c "UI-ys1int-SimpleTC1024T144451") deployed [UI-ys1int-SimpleTC1024T144451](https://github.com/idsb3t1/UI-ys1int-SimpleTC1024T144451/releases/tag/deploy-ibm-ys1-us-south-idsb3t3-us.ibm.com-dev-20171024-185312 "deploy-ibm-ys1-us-south-idsb3t3-us.ibm.com-dev-20171024-185312") to [dev](https://console.stage1.bluemix.net/apps/9ed58328-ca4c-41f6-b378-de2c4f58ad3f?env_id=ibm:ys1:us-south "ibm:ys1:us-south:idsb3t3@us.ibm.com:dev"), including this commit


Znowu z dupy założenia, że graczy jest ZAWSZE 2. Dlaczego nie przekazujesz liczby graczy do Board?


Oh, crap. Thanks for catching that.
It was a copy & pasta fail 😅
https://github.com/lfhbento/timeboxed-watchface/blob/master/src/js/app.js#L912

These should've been `B`, `C` and `D`.

I'll fix that tonight.


Tu veux parler du BT ?

Le 24 oct. 2017 20:19, "Bracame" <notifications@github.com> a écrit :

> You love give me newer job !!
> Pff, After the one in course ;-)
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/Ingwie/OpenAVRc_Dev/commit/3f7201880bda920ed984d27ccdc3bce4d278c0e5#commitcomment-25164289>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AHz4Eq_l4YvrzsZghPjPlB64tISQfLbVks5svioggaJpZM4QE33L>
> .
>


No i fajnie. Tu masz se te NumOfCards (znowu inna konwencja nazw niz wszystkie inne pola...) ustawiasz na 16 ale w ogole nie korzystasz z tej zmiennej w cpp ?!


I had to add a
```cpp
		if (value == 0)
			return -1;
```
After this line, otherwise other buttons would want to randomly map, instead of the button I was actually pressing.


I wasn't able to retrieve PDD puzzles from the code base and submit them to GitHub. If you think that it's a bug on your our side, please submit it to [yegor256/0pdd](https://github.com/yegor256/0pdd/issues)):

> set -x;set -e;set -o pipefail;cd /tmp/0pdd20171024-9709-hbajp2/irbuch/codequiz-master && pdd -q -f /tmp/pdd.xml20171024-9756-y1dbo5: pid 9781 exit 255 (not zero): + set -e + set -o pipefail + cd /tmp/0pdd20171024-9709-hbajp2/irbuch/codequiz-master + pdd -q -f /tmp/pdd.xml20171024-9756-y1dbo5 ...

Please, copy and paste this stack trace to GitHub:

```
set -x;set -e;set -o pipefail;cd /tmp/0pdd20171024-9709-hbajp2/irbuch/codequiz-master && pdd -q -f /tmp/pdd.xml20171024-9756-y1dbo5: pid 9781 exit 255 (not zero):
+ set -e
+ set -o pipefail
+ cd /tmp/0pdd20171024-9709-hbajp2/irbuch/codequiz-master
+ pdd -q -f /tmp/pdd.xml20171024-9756-y1dbo5

ERROR: there are 14 duplicate(s) of the same puzzle: app/jobs/application_job.rb:2-2, app/controllers/application_controller.rb:4-4, app/controllers/application_controller.rb:8-8, app/controllers/application_controller.rb:9-9, app/controllers/application_controller.rb:13-13, app/controllers/application_controller.rb:14-14, app/controllers/application_controller.rb:15-15, app/controllers/application_controller.rb:16-16, app/controllers/application_controller.rb:17-17, app/controllers/application_controller.rb:18-18, app/controllers/application_controller.rb:19-19, app/controllers/application_controller.rb:20-20, app/controllers/application_controller.rb:21-21, app/models/account.rb:2-2, while maximum 1 duplicate is allowed
ERROR: 1 errors, see log above
If you can't understand the cause of this issue or you don't know how to fix it, please submit a GitHub issue, we will try to help you: https://github.com/yegor256/pdd/issues. This tool is still in its beta version and we will appreciate your feedback. Here is where you can find more documentation: https://github.com/yegor256/pdd/blob/master/README.md.

/home/irbuch/Documents/projects/0pdd/objects/exec.rb:41:in `block in run'
/home/irbuch/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/open3.rb:205:in `popen_run'
/home/irbuch/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/open3.rb:95:in `popen3'
/home/irbuch/Documents/projects/0pdd/objects/exec.rb:39:in `run'
/home/irbuch/Documents/projects/0pdd/objects/git_repo.rb:62:in `xml'
/home/irbuch/Documents/projects/0pdd/objects/puzzles.rb:37:in `deploy'
/home/irbuch/Documents/projects/0pdd/objects/job.rb:40:in `proceed'
/home/irbuch/Documents/projects/0pdd/objects/job_starred.rb:33:in `proceed'
/home/irbuch/Documents/projects/0pdd/objects/job_recorded.rb:32:in `proceed'
/home/irbuch/Documents/projects/0pdd/objects/job_emailed.rb:35:in `proceed'
/home/irbuch/Documents/projects/0pdd/objects/job_commiterrors.rb:36:in `proceed'
/home/irbuch/Documents/projects/0pdd/objects/job_detached.rb:49:in `block in exclusive'
/home/irbuch/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:91:in `block in timeout'
/home/irbuch/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:33:in `block in catch'
/home/irbuch/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:33:in `catch'
/home/irbuch/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:33:in `catch'
/home/irbuch/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:106:in `timeout'
/home/irbuch/Documents/projects/0pdd/objects/job_detached.rb:47:in `exclusive'
/home/irbuch/Documents/projects/0pdd/objects/job_detached.rb:37:in `block in proceed'
/home/irbuch/Documents/projects/0pdd/objects/job_detached.rb:37:in `fork'
/home/irbuch/Documents/projects/0pdd/objects/job_detached.rb:37:in `proceed'
0pdd.rb:347:in `block in <main>'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1632:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1632:in `block in compile!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:991:in `block (3 levels) in route!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1010:in `route_eval'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:991:in `block (2 levels) in route!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1037:in `block in process_route'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1035:in `catch'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1035:in `process_route'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:989:in `block in route!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:988:in `each'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:988:in `route!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1094:in `block in dispatch!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `block in invoke'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `catch'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `invoke'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1091:in `dispatch!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:923:in `block in call!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `block in invoke'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `catch'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `invoke'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:923:in `call!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:913:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-protection-2.0.0/lib/rack/protection/xss_header.rb:18:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-protection-2.0.0/lib/rack/protection/path_traversal.rb:16:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-protection-2.0.0/lib/rack/protection/json_csrf.rb:26:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-protection-2.0.0/lib/rack/protection/base.rb:50:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-protection-2.0.0/lib/rack/protection/base.rb:50:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-protection-2.0.0/lib/rack/protection/frame_options.rb:31:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-2.0.3/lib/rack/logger.rb:15:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-2.0.3/lib/rack/common_logger.rb:33:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:231:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:224:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-2.0.3/lib/rack/head.rb:12:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-2.0.3/lib/rack/method_override.rb:22:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/show_exceptions.rb:22:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:194:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1955:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1499:in `block in call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1726:in `synchronize'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1499:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/thin-1.7.2/lib/thin/connection.rb:86:in `block in pre_process'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/thin-1.7.2/lib/thin/connection.rb:84:in `catch'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/thin-1.7.2/lib/thin/connection.rb:84:in `pre_process'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/thin-1.7.2/lib/thin/connection.rb:50:in `block in process'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/eventmachine-1.2.5/lib/eventmachine.rb:1076:in `block in spawn_threadpool'
```


Brak odstępu.


Was my guess as well :) Have a nice day and thanks for that quick implementation! :)


I saw that. I wasn't sure if that meant what it sounded like it meant. There are mentions in earlier commits for updating to a new API and changing from Postgres to My SQL.


C'est quoi l'intérêt  de créer une variable ?


fast-forwarding master to auto = e55d2dce


To na pewno nie powinno być public...


test


woot!


I wasn't able to retrieve PDD puzzles from the code base and submit them to GitHub. If you think that it's a bug on your our side, please submit it to [yegor256/0pdd](https://github.com/yegor256/0pdd/issues)):

> set -x;set -e;set -o pipefail;cd /tmp/0pdd20171024-9709-hbajp2/irbuch/codequiz-master && pdd -q -f /tmp/pdd.xml20171024-10126-18002f2: pid 10217 exit 255 (not zero): + set -e + set -o pipefail + cd /tmp/0pdd20171024-9709-hbajp2/irbuch/codequiz-master + pdd -q -f /tmp/pdd.xml20171024-10126-18002f2...

Please, copy and paste this stack trace to GitHub:

```
set -x;set -e;set -o pipefail;cd /tmp/0pdd20171024-9709-hbajp2/irbuch/codequiz-master && pdd -q -f /tmp/pdd.xml20171024-10126-18002f2: pid 10217 exit 255 (not zero):
+ set -e
+ set -o pipefail
+ cd /tmp/0pdd20171024-9709-hbajp2/irbuch/codequiz-master
+ pdd -q -f /tmp/pdd.xml20171024-10126-18002f2

ERROR: there are 2 duplicate(s) of the same puzzle: app/jobs/application_job.rb:2-2, app/models/account.rb:2-2, while maximum 1 duplicate is allowed
ERROR: 1 errors, see log above
If you can't understand the cause of this issue or you don't know how to fix it, please submit a GitHub issue, we will try to help you: https://github.com/yegor256/pdd/issues. This tool is still in its beta version and we will appreciate your feedback. Here is where you can find more documentation: https://github.com/yegor256/pdd/blob/master/README.md.

/home/irbuch/Documents/projects/0pdd/objects/exec.rb:41:in `block in run'
/home/irbuch/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/open3.rb:205:in `popen_run'
/home/irbuch/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/open3.rb:95:in `popen3'
/home/irbuch/Documents/projects/0pdd/objects/exec.rb:39:in `run'
/home/irbuch/Documents/projects/0pdd/objects/git_repo.rb:62:in `xml'
/home/irbuch/Documents/projects/0pdd/objects/puzzles.rb:37:in `deploy'
/home/irbuch/Documents/projects/0pdd/objects/job.rb:40:in `proceed'
/home/irbuch/Documents/projects/0pdd/objects/job_starred.rb:33:in `proceed'
/home/irbuch/Documents/projects/0pdd/objects/job_recorded.rb:32:in `proceed'
/home/irbuch/Documents/projects/0pdd/objects/job_emailed.rb:35:in `proceed'
/home/irbuch/Documents/projects/0pdd/objects/job_commiterrors.rb:36:in `proceed'
/home/irbuch/Documents/projects/0pdd/objects/job_detached.rb:49:in `block in exclusive'
/home/irbuch/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:91:in `block in timeout'
/home/irbuch/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:33:in `block in catch'
/home/irbuch/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:33:in `catch'
/home/irbuch/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:33:in `catch'
/home/irbuch/.rvm/rubies/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:106:in `timeout'
/home/irbuch/Documents/projects/0pdd/objects/job_detached.rb:47:in `exclusive'
/home/irbuch/Documents/projects/0pdd/objects/job_detached.rb:37:in `block in proceed'
/home/irbuch/Documents/projects/0pdd/objects/job_detached.rb:37:in `fork'
/home/irbuch/Documents/projects/0pdd/objects/job_detached.rb:37:in `proceed'
0pdd.rb:347:in `block in <main>'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1632:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1632:in `block in compile!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:991:in `block (3 levels) in route!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1010:in `route_eval'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:991:in `block (2 levels) in route!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1037:in `block in process_route'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1035:in `catch'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1035:in `process_route'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:989:in `block in route!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:988:in `each'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:988:in `route!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1094:in `block in dispatch!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `block in invoke'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `catch'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `invoke'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1091:in `dispatch!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:923:in `block in call!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `block in invoke'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `catch'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `invoke'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:923:in `call!'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:913:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-protection-2.0.0/lib/rack/protection/xss_header.rb:18:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-protection-2.0.0/lib/rack/protection/path_traversal.rb:16:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-protection-2.0.0/lib/rack/protection/json_csrf.rb:26:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-protection-2.0.0/lib/rack/protection/base.rb:50:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-protection-2.0.0/lib/rack/protection/base.rb:50:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-protection-2.0.0/lib/rack/protection/frame_options.rb:31:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-2.0.3/lib/rack/logger.rb:15:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-2.0.3/lib/rack/common_logger.rb:33:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:231:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:224:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-2.0.3/lib/rack/head.rb:12:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/rack-2.0.3/lib/rack/method_override.rb:22:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/show_exceptions.rb:22:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:194:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1955:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1499:in `block in call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1726:in `synchronize'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/sinatra-2.0.0/lib/sinatra/base.rb:1499:in `call'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/thin-1.7.2/lib/thin/connection.rb:86:in `block in pre_process'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/thin-1.7.2/lib/thin/connection.rb:84:in `catch'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/thin-1.7.2/lib/thin/connection.rb:84:in `pre_process'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/thin-1.7.2/lib/thin/connection.rb:50:in `block in process'
/home/irbuch/.rvm/gems/ruby-2.3.3@0pdd/gems/eventmachine-1.2.5/lib/eventmachine.rb:1076:in `block in spawn_threadpool'
```


I do pożygu to boards.players[Tura] zamiast ustawienie jakiegoś tymczasowego wskaźnika na to.


Przez getter a nie rżnąć bezpośrednio z pola.


Need to add some deadzone handling. My Xbox 360 controller will randomly send EV_ABS inputs.


Szkoda odstępu tutaj ? Board* boardPTR=&board;

Zresztą linia jest z dupy po co ona niby robi ? W każdym momencie i tak masz dostęp do adresu board więc po cholerę tworzysz zmienną która jest SKŁADNIKIEM Twojej klasy a jest totalnie bezsenswona.


To be sure what is happening,  it seems to me that 3-threaded test should be started too. NCM tests with 2 cores.


@mdbenjam typo, though all uses are consistent, so nothing appears to be broken


heck off xtreme this shitcode is not for your eyes!


i need help please


Przez getter

Board* Game::GetBoardPtr() {
   return &board;
}


Znowu założenie, że 2 graczy.


brak odstępu.


ah, thank you!  i will change that one too!


コメントを追加
可読性の向上


I po polsku jakieś pozz zamiast chociażby _pos.

Znowu nazwa składowej z dużej litery. Piszemy z małych.


@tbosch let's talk about maybe changing the title of this commit. Brad says it's not a refactor.


public masz napisane ok. Signals już wplecione jakby było metodą. Chodzi o odstęp.


Для чого нам двічі переписувати однакову реалізацію одного і того самого методу? Може варто її додати в клас-предок?


wcięcie.


Oui, In engish un nouveau boulot

Le Frsky S.PORT en premier (et l'implementation en driver SPI)

Vous allez adorer , si j'y arrive (Rich a bien avancé, je tente de terminer sur la télémétrie que je n'ai pas non plus)

----- Original Message -----
From: pierrotm777 <notifications@github.com>
To: Ingwie/OpenAVRc_Dev <OpenAVRc_Dev@noreply.github.com>
Cc: Bracame <theingwie@gmail.com>,  Comment <comment@noreply.github.com>
Date: Tue, 24 Oct 2017 18:54:12 +0000 (UTC)
Subject: Re: [Ingwie/OpenAVRc_Dev] Update cabling documentation (3f72018)

> Tu veux parler du BT ?
>
> Le 24 oct. 2017 20:19, "Bracame" <notifications@github.com> a écrit :
>
> > You love give me newer job !!
> > Pff, After the one in course ;-)
> >
> > —
> > You are receiving this because you are subscribed to this thread.
> > Reply to this email directly, view it on GitHub
> > <https://github.com/Ingwie/OpenAVRc_Dev/commit/3f7201880bda920ed984d27ccdc3bce4d278c0e5#commitcomment-25164289>,
> > or mute the thread
> > <https://github.com/notifications/unsubscribe-auth/AHz4Eq_l4YvrzsZghPjPlB64tISQfLbVks5svioggaJpZM4QE33L>
> > .
> >
>
>
> --
> You are receiving this because you commented.
> Reply to this email directly or view it on GitHub:
> https://github.com/Ingwie/OpenAVRc_Dev/commit/3f7201880bda920ed984d27ccdc3bce4d278c0e5#commitcomment-25165102
>


whats the reason behind setting the foldmethod to expr?

i am getting the following error when i try to fold -
```
E350: Cannot create fold with current 'foldmethod'
```


For keys imported before this change, these fields will be NULL.  How does this affect the sorting of these legacy imported jobs?  It looks like the fallback is based on `original_key`, which looks like it would be pretty arbitrary.

Also, is always having `updated_at` an ActiveRecord-ism?  It doesn't seem like it adds much in this case.


цей обєкт нам взагалі не потрібний. Може краще зробити метод SalarySorting(workers); статичним?


Created multidev environment [electronil#pr-emulsify](https://dashboard.pantheon.io/sites/17d8094e-ddfb-4032-83e4-771bdf4a36d2#pr-emulsify).

[![Visit Site](https://raw.githubusercontent.com/pantheon-systems/ci-drops-8/0.1.0/data/img/visit-site-36.png)](https://pr-emulsify-electronil.pantheonsite.io/)


[DateTime] Fix code smells left from #1647 (#1744)

Preview: documentation
Coverage: core | datetime


Allright, let's start editing


This is a C++ program used to convert hexadecimal numbers to decimal.


Wanted to add these NPCs in a later commit aswell, thanks for doing it for me 😄


Created multidev environment [dgreat#pr-barrio](https://dashboard.pantheon.io/sites/41cad7fe-472d-43a9-a470-d391b9622376#pr-barrio).

[![Visit Site](https://raw.githubusercontent.com/pantheon-systems/ci-drops-8/0.1.0/data/img/visit-site-36.png)](https://pr-barrio-dgreat.pantheonsite.io/)


The following doc(s) have been deployed to the [2843create](https://2843create-static-docs.pantheonsite.io/docs) Multidev environment:
- [/docs/wordpress-site-networks](https://2843create-static-docs.pantheonsite.io/docs/wordpress-site-networks)


if you accidentally pulled this commit, simply do a "git reset --hard HEAD~25"  then do another "git pull", then make your new changes.  that will roll back the history and pull the rewritten history.


Here is some code for a new homepage based on something similar to the Mark Twain site (per my e-mail to you).  I'll also try to upload a possible image file for the header later today, time willing.


Just pushed an update to `develop`, NuGet package on its way.


@MichaelMraka
Isn't it better to do it that way rather than changing release number with every release?
```bash
#first enable optional repo on RHEL7
yum -y install -y yum-plugin-copr
yum -y copr enable @spacewalkproject/nightly-client
yum -y install spacewalk-repo
yum -y copr disable @spacewalkproject/nightly-client
```
Our automation uses these steps.
Sadly on RHEL6 and CentOS 6, it should remain to do that way because yum-plugin-copr is not available there and probably won't be.


Oui, In engish un nouveau boulot

Le Frsky S.PORT en premier (et l'implémentations en driver SPI)

A première vu, on le fera.

----- Original Message -----
From: pierrotm777 <notifications@github.com>
To: Ingwie/OpenAVRc_Dev <OpenAVRc_Dev@noreply.github.com>
Cc: Bracame <theingwie@gmail.com>,  Comment <comment@noreply.github.com>
Date: Tue, 24 Oct 2017 18:54:12 +0000 (UTC)
Subject: Re: [Ingwie/OpenAVRc_Dev] Update cabling documentation (3f72018)

> Tu veux parler du BT ?
>
> Le 24 oct. 2017 20:19, "Bracame" <notifications@github.com> a écrit :
>
> > You love give me newer job !!
> > Pff, After the one in course ;-)
> >
> > —
> > You are receiving this because you are subscribed to this thread.
> > Reply to this email directly, view it on GitHub
> > <https://github.com/Ingwie/OpenAVRc_Dev/commit/3f7201880bda920ed984d27ccdc3bce4d278c0e5#commitcomment-25164289>,
> > or mute the thread
> > <https://github.com/notifications/unsubscribe-auth/AHz4Eq_l4YvrzsZghPjPlB64tISQfLbVks5svioggaJpZM4QE33L>
> > .
> >
>
>
> --
> You are receiving this because you commented.
> Reply to this email directly or view it on GitHub:
> https://github.com/Ingwie/OpenAVRc_Dev/commit/3f7201880bda920ed984d27ccdc3bce4d278c0e5#commitcomment-25165102
>


I don't understand what you are doing here.  Everytime I do a Pull, I get a conflict because of the way you are overwriting your previous changes?  This is really hard to track your changes.