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 our side, please submit it to [yegor256/0pdd](https://github.com/yegor256/0pdd/issues):

> set -x && set -e && set -o pipefail && cd /tmp/0pdd20190509-4-mj84kv/heytitle/thai-word-segmentation-benchmark && pdd -v -f /tmp/20190510-8357-6nc0pj [1]: bash: warning: setlocale: LC_ALL: cannot change locale (UTF-8) + set -e + set -o pipefail + cd...

Please, copy and paste this stack trace to GitHub:

```
UserError
set -x && set -e && set -o pipefail && cd /tmp/0pdd20190509-4-mj84kv/heytitle/thai-word-segmentation-benchmark && pdd -v -f /tmp/20190510-8357-6nc0pj [1]:
bash: warning: setlocale: LC_ALL: cannot change locale (UTF-8)
+ set -e
+ set -o pipefail
+ cd /tmp/0pdd20190509-4-mj84kv/heytitle/thai-word-segmentation-benchmark
+ pdd -v -f /tmp/20190510-8357-6nc0pj

My version is 0.20.4
Ruby version is 2.6.0 at x86_64-linux
Reading /tmp/0pdd20190509-4-mj84kv/heytitle/thai-word-segmentation-benchmark
2 file(s) found, 75 excluded
Reading pythainlp/benchmarks/word_segmentation.py...
ERROR: pythainlp/benchmarks/word_segmentation.py; puzzle at line #2; @todo found, but puzzle can't be parsed, most probably because @todo is not followed by a puzzle marker, as this page explains: https://github.com/yegor256/pdd#how-to-format
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.
Exit code is 1

/app/objects/git_repo.rb:66:in `rescue in block in xml'
/app/objects/git_repo.rb:63:in `block in xml'
/app/vendor/ruby-2.6.0/lib/ruby/2.6.0/tempfile.rb:295:in `open'
/app/objects/git_repo.rb:62:in `xml'
/app/objects/puzzles.rb:36:in `deploy'
/app/objects/job.rb:38:in `proceed'
/app/objects/job_starred.rb:33:in `proceed'
/app/objects/job_recorded.rb:32:in `proceed'
/app/objects/job_emailed.rb:35:in `proceed'
/app/objects/job_commiterrors.rb:36:in `proceed'
/app/objects/job_detached.rb:48:in `exclusive'
/app/objects/job_detached.rb:36:in `block in proceed'
/app/objects/job_detached.rb:36:in `fork'
/app/objects/job_detached.rb:36:in `proceed'
/app/0pdd.rb:354:in `block in <top (required)>'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1635:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1635:in `block in compile!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:992:in `block (3 levels) in route!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1011:in `route_eval'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:992:in `block (2 levels) in route!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1040:in `block in process_route'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1038:in `catch'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1038:in `process_route'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:990:in `block in route!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:989:in `each'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:989:in `route!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1097:in `block in dispatch!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1076:in `block in invoke'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1076:in `catch'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1076:in `invoke'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1094:in `dispatch!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:924:in `block in call!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1076:in `block in invoke'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1076:in `catch'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1076:in `invoke'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:924:in `call!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:913:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-protection-2.0.4/lib/rack/protection/xss_header.rb:18:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-protection-2.0.4/lib/rack/protection/path_traversal.rb:16:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-protection-2.0.4/lib/rack/protection/json_csrf.rb:26:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-protection-2.0.4/lib/rack/protection/base.rb:50:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-protection-2.0.4/lib/rack/protection/base.rb:50:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-protection-2.0.4/lib/rack/protection/frame_options.rb:31:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-2.0.6/lib/rack/logger.rb:15:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-2.0.6/lib/rack/common_logger.rb:33:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:231:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:224:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-2.0.6/lib/rack/head.rb:12:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-2.0.6/lib/rack/method_override.rb:22:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:194:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1957:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1502:in `block in call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1729:in `synchronize'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1502:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-2.0.6/lib/rack/handler/webrick.rb:86:in `service'
/app/vendor/ruby-2.6.0/lib/ruby/2.6.0/webrick/httpserver.rb:140:in `service'
/app/vendor/ruby-2.6.0/lib/ruby/2.6.0/webrick/httpserver.rb:96:in `run'
/app/vendor/ruby-2.6.0/lib/ruby/2.6.0/webrick/server.rb:307:in `block in start_thread'
```


fix the problem of article background not cover the whole space, by setting the outer div width to 100%;


Proszę przekaż sesję w konstruktorze. W zależności od tego, gdzie będzie odpalana binarka, sesja może być zupełnie inaczej budowana, więc nie ma sensu ograniczać się na siłę do jednej implementacji na poziomie biblioteki.


ecco


And what about the emit inside the if clause? Should I emit an event in any case too?


Jeśli będziesz mieć tu klienta to będzie to bardzo ciężko przetestować, chyba że z lokalnym mockiem DynamoDB. Wolałbym jednak, żeby użyć mocka, więc tu proponowałbym [`dynamodbiface.DynamoDBAPI`](https://docs.aws.amazon.com/sdk-for-go/api/service/dynamodb/dynamodbiface/#DynamoDBAPI).


![](https://github.trello.services/images/mini-trello-icon.png) [REST авторизации](https://trello.com/c/sgjbyTDR/20-rest-%D0%B0%D0%B2%D1%82%D0%BE%D1%80%D0%B8%D0%B7%D0%B0%D1%86%D0%B8%D0%B8)


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 our side, please submit it to [yegor256/0pdd](https://github.com/yegor256/0pdd/issues):

> set -x && set -e && set -o pipefail && cd /tmp/0pdd20190509-4-mj84kv/heytitle/thai-word-segmentation-benchmark && pdd -v -f /tmp/20190510-8480-11j0blk [1]: bash: warning: setlocale: LC_ALL: cannot change locale (UTF-8) + set -e + set -o pipefail + cd...

Please, copy and paste this stack trace to GitHub:

```
UserError
set -x && set -e && set -o pipefail && cd /tmp/0pdd20190509-4-mj84kv/heytitle/thai-word-segmentation-benchmark && pdd -v -f /tmp/20190510-8480-11j0blk [1]:
bash: warning: setlocale: LC_ALL: cannot change locale (UTF-8)
+ set -e
+ set -o pipefail
+ cd /tmp/0pdd20190509-4-mj84kv/heytitle/thai-word-segmentation-benchmark
+ pdd -v -f /tmp/20190510-8480-11j0blk

My version is 0.20.4
Ruby version is 2.6.0 at x86_64-linux
Reading /tmp/0pdd20190509-4-mj84kv/heytitle/thai-word-segmentation-benchmark
3 file(s) found, 84 excluded
Reading pythainlp/benchmarks/word_segmentation.py...
ERROR: pythainlp/benchmarks/word_segmentation.py; puzzle at line #2; @todo found, but puzzle can't be parsed, most probably because @todo is not followed by a puzzle marker, as this page explains: https://github.com/yegor256/pdd#how-to-format
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.
Exit code is 1

/app/objects/git_repo.rb:66:in `rescue in block in xml'
/app/objects/git_repo.rb:63:in `block in xml'
/app/vendor/ruby-2.6.0/lib/ruby/2.6.0/tempfile.rb:295:in `open'
/app/objects/git_repo.rb:62:in `xml'
/app/objects/puzzles.rb:36:in `deploy'
/app/objects/job.rb:38:in `proceed'
/app/objects/job_starred.rb:33:in `proceed'
/app/objects/job_recorded.rb:32:in `proceed'
/app/objects/job_emailed.rb:35:in `proceed'
/app/objects/job_commiterrors.rb:36:in `proceed'
/app/objects/job_detached.rb:48:in `exclusive'
/app/objects/job_detached.rb:36:in `block in proceed'
/app/objects/job_detached.rb:36:in `fork'
/app/objects/job_detached.rb:36:in `proceed'
/app/0pdd.rb:354:in `block in <top (required)>'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1635:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1635:in `block in compile!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:992:in `block (3 levels) in route!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1011:in `route_eval'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:992:in `block (2 levels) in route!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1040:in `block in process_route'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1038:in `catch'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1038:in `process_route'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:990:in `block in route!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:989:in `each'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:989:in `route!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1097:in `block in dispatch!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1076:in `block in invoke'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1076:in `catch'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1076:in `invoke'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1094:in `dispatch!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:924:in `block in call!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1076:in `block in invoke'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1076:in `catch'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1076:in `invoke'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:924:in `call!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:913:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-protection-2.0.4/lib/rack/protection/xss_header.rb:18:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-protection-2.0.4/lib/rack/protection/path_traversal.rb:16:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-protection-2.0.4/lib/rack/protection/json_csrf.rb:26:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-protection-2.0.4/lib/rack/protection/base.rb:50:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-protection-2.0.4/lib/rack/protection/base.rb:50:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-protection-2.0.4/lib/rack/protection/frame_options.rb:31:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-2.0.6/lib/rack/logger.rb:15:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-2.0.6/lib/rack/common_logger.rb:33:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:231:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:224:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-2.0.6/lib/rack/head.rb:12:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-2.0.6/lib/rack/method_override.rb:22:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:194:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1957:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1502:in `block in call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1729:in `synchronize'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1502:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-2.0.6/lib/rack/handler/webrick.rb:86:in `service'
/app/vendor/ruby-2.6.0/lib/ruby/2.6.0/webrick/httpserver.rb:140:in `service'
/app/vendor/ruby-2.6.0/lib/ruby/2.6.0/webrick/httpserver.rb:96:in `run'
/app/vendor/ruby-2.6.0/lib/ruby/2.6.0/webrick/server.rb:307:in `block in start_thread'
```


we don't need this since steering is via hardware


clreq -> jlreq


need to set this to a negative value because mixed up the wheels/dc motors when we mounted them


actually use `SPEED_COEFFICIENT`


Tutaj mutex Ci zupełnie nic nie da. Jeśli chcesz osiągnąć spójność, to sugerowałbym to zrobić na poziomie bazy danych, ustawiając `ConsistentRead` na `true` w strukturze [`GetItemInput`](https://docs.aws.amazon.com/sdk-for-go/api/service/dynamodb/#GetItemInput). [Tu](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/HowItWorks.ReadConsistency.html) możesz poczytać trochę więcej na temat semantyki zapytań do DynamoDB.


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 our side, please submit it to [yegor256/0pdd](https://github.com/yegor256/0pdd/issues):

> set -x && set -e && set -o pipefail && cd /tmp/0pdd20190509-4-mj84kv/heytitle/thai-word-segmentation-benchmark && pdd -v -f /tmp/20190510-8680-dcj89r [1]: bash: warning: setlocale: LC_ALL: cannot change locale (UTF-8) + set -e + set -o pipefail + cd...

Please, copy and paste this stack trace to GitHub:

```
UserError
set -x && set -e && set -o pipefail && cd /tmp/0pdd20190509-4-mj84kv/heytitle/thai-word-segmentation-benchmark && pdd -v -f /tmp/20190510-8680-dcj89r [1]:
bash: warning: setlocale: LC_ALL: cannot change locale (UTF-8)
+ set -e
+ set -o pipefail
+ cd /tmp/0pdd20190509-4-mj84kv/heytitle/thai-word-segmentation-benchmark
+ pdd -v -f /tmp/20190510-8680-dcj89r

My version is 0.20.4
Ruby version is 2.6.0 at x86_64-linux
Reading /tmp/0pdd20190509-4-mj84kv/heytitle/thai-word-segmentation-benchmark
3 file(s) found, 84 excluded
Reading pythainlp/benchmarks/word_segmentation.py...
ERROR: pythainlp/benchmarks/word_segmentation.py; puzzle at line #2; @todo found, but puzzle can't be parsed, most probably because @todo is not followed by a puzzle marker, as this page explains: https://github.com/yegor256/pdd#how-to-format
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.
Exit code is 1

/app/objects/git_repo.rb:66:in `rescue in block in xml'
/app/objects/git_repo.rb:63:in `block in xml'
/app/vendor/ruby-2.6.0/lib/ruby/2.6.0/tempfile.rb:295:in `open'
/app/objects/git_repo.rb:62:in `xml'
/app/objects/puzzles.rb:36:in `deploy'
/app/objects/job.rb:38:in `proceed'
/app/objects/job_starred.rb:33:in `proceed'
/app/objects/job_recorded.rb:32:in `proceed'
/app/objects/job_emailed.rb:35:in `proceed'
/app/objects/job_commiterrors.rb:36:in `proceed'
/app/objects/job_detached.rb:48:in `exclusive'
/app/objects/job_detached.rb:36:in `block in proceed'
/app/objects/job_detached.rb:36:in `fork'
/app/objects/job_detached.rb:36:in `proceed'
/app/0pdd.rb:354:in `block in <top (required)>'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1635:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1635:in `block in compile!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:992:in `block (3 levels) in route!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1011:in `route_eval'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:992:in `block (2 levels) in route!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1040:in `block in process_route'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1038:in `catch'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1038:in `process_route'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:990:in `block in route!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:989:in `each'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:989:in `route!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1097:in `block in dispatch!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1076:in `block in invoke'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1076:in `catch'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1076:in `invoke'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1094:in `dispatch!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:924:in `block in call!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1076:in `block in invoke'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1076:in `catch'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1076:in `invoke'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:924:in `call!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:913:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-protection-2.0.4/lib/rack/protection/xss_header.rb:18:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-protection-2.0.4/lib/rack/protection/path_traversal.rb:16:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-protection-2.0.4/lib/rack/protection/json_csrf.rb:26:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-protection-2.0.4/lib/rack/protection/base.rb:50:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-protection-2.0.4/lib/rack/protection/base.rb:50:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-protection-2.0.4/lib/rack/protection/frame_options.rb:31:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-2.0.6/lib/rack/logger.rb:15:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-2.0.6/lib/rack/common_logger.rb:33:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:231:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:224:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-2.0.6/lib/rack/head.rb:12:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-2.0.6/lib/rack/method_override.rb:22:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:194:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1957:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1502:in `block in call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1729:in `synchronize'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1502:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-2.0.6/lib/rack/handler/webrick.rb:86:in `service'
/app/vendor/ruby-2.6.0/lib/ruby/2.6.0/webrick/httpserver.rb:140:in `service'
/app/vendor/ruby-2.6.0/lib/ruby/2.6.0/webrick/httpserver.rb:96:in `run'
/app/vendor/ruby-2.6.0/lib/ruby/2.6.0/webrick/server.rb:307:in `block in start_thread'
```


Wonderful ! 👍


Noice


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 our side, please submit it to [yegor256/0pdd](https://github.com/yegor256/0pdd/issues):

> set -x && set -e && set -o pipefail && cd /tmp/0pdd20190509-4-mj84kv/heytitle/thai-word-segmentation-benchmark && pdd -v -f /tmp/20190510-8776-njbqdw [1]: bash: warning: setlocale: LC_ALL: cannot change locale (UTF-8) + set -e + set -o pipefail + cd...

Please, copy and paste this stack trace to GitHub:

```
UserError
set -x && set -e && set -o pipefail && cd /tmp/0pdd20190509-4-mj84kv/heytitle/thai-word-segmentation-benchmark && pdd -v -f /tmp/20190510-8776-njbqdw [1]:
bash: warning: setlocale: LC_ALL: cannot change locale (UTF-8)
+ set -e
+ set -o pipefail
+ cd /tmp/0pdd20190509-4-mj84kv/heytitle/thai-word-segmentation-benchmark
+ pdd -v -f /tmp/20190510-8776-njbqdw

Found 1 lines in /tmp/0pdd20190509-4-mj84kv/heytitle/thai-word-segmentation-benchmark/.pdd
My version is 0.20.4
Ruby version is 2.6.0 at x86_64-linux
Reading /tmp/0pdd20190509-4-mj84kv/heytitle/thai-word-segmentation-benchmark
Excluding README.md
3 file(s) found, 187 excluded
Reading .pdd...
Reading pythainlp/benchmarks/word_segmentation.py...
ERROR: pythainlp/benchmarks/word_segmentation.py; puzzle at line #2; @todo found, but puzzle can't be parsed, most probably because @todo is not followed by a puzzle marker, as this page explains: https://github.com/yegor256/pdd#how-to-format
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.
Exit code is 1

/app/objects/git_repo.rb:66:in `rescue in block in xml'
/app/objects/git_repo.rb:63:in `block in xml'
/app/vendor/ruby-2.6.0/lib/ruby/2.6.0/tempfile.rb:295:in `open'
/app/objects/git_repo.rb:62:in `xml'
/app/objects/puzzles.rb:36:in `deploy'
/app/objects/job.rb:38:in `proceed'
/app/objects/job_starred.rb:33:in `proceed'
/app/objects/job_recorded.rb:32:in `proceed'
/app/objects/job_emailed.rb:35:in `proceed'
/app/objects/job_commiterrors.rb:36:in `proceed'
/app/objects/job_detached.rb:48:in `exclusive'
/app/objects/job_detached.rb:36:in `block in proceed'
/app/objects/job_detached.rb:36:in `fork'
/app/objects/job_detached.rb:36:in `proceed'
/app/0pdd.rb:354:in `block in <top (required)>'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1635:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1635:in `block in compile!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:992:in `block (3 levels) in route!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1011:in `route_eval'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:992:in `block (2 levels) in route!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1040:in `block in process_route'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1038:in `catch'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1038:in `process_route'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:990:in `block in route!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:989:in `each'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:989:in `route!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1097:in `block in dispatch!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1076:in `block in invoke'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1076:in `catch'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1076:in `invoke'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1094:in `dispatch!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:924:in `block in call!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1076:in `block in invoke'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1076:in `catch'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1076:in `invoke'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:924:in `call!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:913:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-protection-2.0.4/lib/rack/protection/xss_header.rb:18:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-protection-2.0.4/lib/rack/protection/path_traversal.rb:16:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-protection-2.0.4/lib/rack/protection/json_csrf.rb:26:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-protection-2.0.4/lib/rack/protection/base.rb:50:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-protection-2.0.4/lib/rack/protection/base.rb:50:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-protection-2.0.4/lib/rack/protection/frame_options.rb:31:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-2.0.6/lib/rack/logger.rb:15:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-2.0.6/lib/rack/common_logger.rb:33:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:231:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:224:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-2.0.6/lib/rack/head.rb:12:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-2.0.6/lib/rack/method_override.rb:22:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:194:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1957:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1502:in `block in call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1729:in `synchronize'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1502:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-2.0.6/lib/rack/handler/webrick.rb:86:in `service'
/app/vendor/ruby-2.6.0/lib/ruby/2.6.0/webrick/httpserver.rb:140:in `service'
/app/vendor/ruby-2.6.0/lib/ruby/2.6.0/webrick/httpserver.rb:96:in `run'
/app/vendor/ruby-2.6.0/lib/ruby/2.6.0/webrick/server.rb:307:in `block in start_thread'
```


1. `Runtime.x` from /home/mingfeim/pytorch/pytorch-mingfei/aten/src/ATen/mkldnn should be useless now, remove them.

2. your commit should not include submodule diff...
use `git submodule update` on pytorch git root directory will fix this.

3. perhaps we should remove `at::` namespace from this file, e.g. `at::Tensor` -> `Tensor`


Ja bym tutaj tego nie używał jeśli potrzebujesz wyciągnąć tylko jedno pole. Taki helper jest fajny jeśli masz jakąś ogromną strukturę, ale jeśli nie masz, to możesz po prostu wziąć `*result.Item["Value"].S` i kod jest bardziej czytelny.


Sugerowałbym przekazanie nazwy tabeli jako zmiennej.


I'll probably pick up here next time by switching this out. The proper way to implement spacing between list items in RecyclerView is ItemDecorator. This is temporary.


Puzzle `1-b0e6fbde` discovered in   [`pythainlp/benchmarks/word_segmentation.py`](  https://github.com/heytitle/thai-word-segmentation-benchmark/blob/master/pythainlp/benchmarks/word_segmentation.py)   and submitted as #2. Please, remember that the puzzle was not   necessarily added in this particular commit. Maybe it was added earlier, but   we discovered it only now.


Please pretty please. Put the error codes here explicitly, without defines


SDK dla AWS-a wspiera [konteksty](https://blog.golang.org/context). Te metody zawsze kończą się na `...WithContext` i w tym przypadku będzie to `GetItemWithContext`. Będę dzisiaj mówił więcej o kontekstach i o co w ogóle chodzi, ale bardzo polecam zapoznać się z artykułem.


@RunninglVlan For readability purposes, it's better to leave the index as is.


模組壓縮包


add"go and suit"


I'm just trying to think what custom priors they would pass here... But if we leave the documentation unchanged (saying that the `prior` arg is ignored for `stanreg` objects), this should be fine.


AppDelegate.swift = Vers. 1.0


Good one! Combination of templates Pierre likes and my macros I like!


This test fails for me:
../src/C++/test/FieldMapTestCase.cpp:56: error: Failure in setMessageOrder: Expected 3 but was 1
../src/C++/test/FieldMapTestCase.cpp:57: error: Failure in setMessageOrder: Expected 3 but was 2
also the actual and expected values also seem to be swapped around.


Configuration.swift = Vers. 1.0


Successfully aliased the URL <https://lab9-pu7diw80w.now.sh> to the following aliases.

* https://lab9.thaon.now.sh
* https://lab9-git-master.thaon.now.sh


Add Line


The diff looks a bit meesed (did you change the ``if... else`` order?) but as far as I can see it looks fine 😉


ViewController.swift = Vers. 1.0


this is not good, @lundman . Why not tag with 1.9.1? We have a commit with 1.9 that is no longer tagged 1.9.0 and would have to force-push to get this commit to the top, don't know how many people would be affected by the force-push but it's not nice. What do you think?


randint


Cartographie.swift = Vers. 1.0


Menu.swift = Vers. 1.0


Or tag it as it is, i.e. 1.9.0-rc1 and then 1.9.0 when it's released?  At worst, you tag the same revision twice unless of course there's a commit to bump the version number from rc1 to final any.


Why is there a space in front of this string?


Size Checks (0 failures)

| Label                                                           | Value     | Threshold | Success |
| ----                                                            | :---:     | :---:     | :---:   |
| .../build/precache-manifest.48d992494cdeb7759c67d7acd8397cec.js | 161 B     | 500 B     | ✓       |
| .../build/static/js/0.d380aa34.chunk.js                         | 2.32 KB   | 1 MB      | ✓       |
| .../build/static/js/105.bd62a519.chunk.js                       | 2.34 KB   | 1 MB      | ✓       |
| .../build/static/js/106.4cc0519d.chunk.js                       | 2.35 KB   | 1 MB      | ✓       |
| .../build/static/js/119.2f6bb797.chunk.js                       | 1.53 KB   | 1 MB      | ✓       |
| .../build/static/js/120.cf302828.chunk.js                       | 1.53 KB   | 1 MB      | ✓       |
| .../build/static/js/133.b589ce25.chunk.js                       | 2.09 KB   | 1 MB      | ✓       |
| .../build/static/js/134.c737c00d.chunk.js                       | 2.1 KB    | 1 MB      | ✓       |
| .../build/static/js/135.6804b8b8.chunk.js                       | 2.51 KB   | 1 MB      | ✓       |
| .../build/static/js/136.239f62b4.chunk.js                       | 2.51 KB   | 1 MB      | ✓       |
| .../build/static/js/149.7017eeff.chunk.js                       | 2.07 KB   | 1 MB      | ✓       |
| .../build/static/js/150.f3e6630a.chunk.js                       | 2.09 KB   | 1 MB      | ✓       |
| .../build/static/js/151.2f5e88ef.chunk.js                       | 2.35 KB   | 1 MB      | ✓       |
| .../build/static/js/152.588e03fc.chunk.js                       | 2.35 KB   | 1 MB      | ✓       |
| .../build/static/js/155.bf5a1d54.chunk.js                       | 2.51 KB   | 1 MB      | ✓       |
| .../build/static/js/156.c929adef.chunk.js                       | 2.51 KB   | 1 MB      | ✓       |
| .../build/static/js/165.2ed68d40.chunk.js                       | 1.94 KB   | 1 MB      | ✓       |
| .../build/static/js/166.1e492146.chunk.js                       | 1.94 KB   | 1 MB      | ✓       |
| .../build/static/js/170.5be62ff6.chunk.js                       | 1.03 KB   | 1 MB      | ✓       |
| .../build/static/js/171.5b05d322.chunk.js                       | 537 B     | 1 MB      | ✓       |
| .../build/static/js/172.53fee252.chunk.js                       | 714 B     | 1 MB      | ✓       |
| .../build/static/js/174.beb11445.chunk.js                       | 956 B     | 1 MB      | ✓       |
| .../build/static/js/173.39e99156.chunk.js                       | 721 B     | 1 MB      | ✓       |
| .../build/static/js/178.a222287f.chunk.js                       | 559 B     | 1 MB      | ✓       |
| .../build/static/js/179.bba2bb2f.chunk.js                       | 389 B     | 1 MB      | ✓       |
| .../build/static/js/177.09cd830f.chunk.js                       | 2.52 KB   | 1 MB      | ✓       |
| .../build/static/js/180.c1397075.chunk.js                       | 1.5 KB    | 1 MB      | ✓       |
| .../build/static/js/2.71e608f6.chunk.js                         | 2.53 KB   | 1 MB      | ✓       |
| .../build/static/js/3.c70d6963.chunk.js                         | 462 B     | 1 MB      | ✓       |
| .../build/static/js/4.7fcfd17e.chunk.js                         | 932 B     | 1 MB      | ✓       |
| .../build/static/js/5.6d4070cb.chunk.js                         | 321 B     | 1 MB      | ✓       |
| .../build/static/js/6.68ac3cd1.chunk.js                         | 1.59 KB   | 1 MB      | ✓       |
| .../build/static/js/7.ed71608d.chunk.js                         | 538 B     | 1 MB      | ✓       |
| .../build/static/js/maps.fb7e84f2.chunk.js                      | 1.26 KB   | 1 MB      | ✓       |
| .../build/static/js/page-modites.5540dee2.chunk.js              | 1.11 KB   | 1 MB      | ✓       |
| .../build/static/js/1.f974ec6a.chunk.js                         | 3.21 KB   | 1 MB      | ✓       |
| .../build/static/js/100.5ac51ca9.chunk.js                       | 4.39 KB   | 1 MB      | ✓       |
| .../build/static/js/101.2a857671.chunk.js                       | 4.39 KB   | 1 MB      | ✓       |
| .../build/static/js/104.57691b64.chunk.js                       | 5.4 KB    | 1 MB      | ✓       |
| .../build/static/js/108.f8c7a5ac.chunk.js                       | 3.07 KB   | 1 MB      | ✓       |
| .../build/static/js/107.bb9eb09a.chunk.js                       | 3.08 KB   | 1 MB      | ✓       |
| .../build/static/js/109.b073447f.chunk.js                       | 3.91 KB   | 1 MB      | ✓       |
| .../build/static/js/111.7758fb4a.chunk.js                       | 3.4 KB    | 1 MB      | ✓       |
| .../build/static/js/112.04dd0807.chunk.js                       | 3.4 KB    | 1 MB      | ✓       |
| .../build/static/js/113.1e69f920.chunk.js                       | 2.79 KB   | 1 MB      | ✓       |
| .../build/static/js/114.11e8f60a.chunk.js                       | 2.79 KB   | 1 MB      | ✓       |
| .../build/static/js/115.2e859aaf.chunk.js                       | 3.5 KB    | 1 MB      | ✓       |
| .../build/static/js/116.1e508a68.chunk.js                       | 3.51 KB   | 1 MB      | ✓       |
| .../build/static/js/117.695022f4.chunk.js                       | 3.5 KB    | 1 MB      | ✓       |
| .../build/static/js/118.a276a861.chunk.js                       | 3.51 KB   | 1 MB      | ✓       |
| .../build/static/js/123.a7db2314.chunk.js                       | 3.87 KB   | 1 MB      | ✓       |
| .../build/static/js/125.86620ad9.chunk.js                       | 2.79 KB   | 1 MB      | ✓       |
| .../build/static/js/126.a355e627.chunk.js                       | 2.79 KB   | 1 MB      | ✓       |
| .../build/static/js/127.128c7e13.chunk.js                       | 2.64 KB   | 1 MB      | ✓       |
| .../build/static/js/128.be5e2ee2.chunk.js                       | 2.67 KB   | 1 MB      | ✓       |
| .../build/static/js/129.cf6be7bc.chunk.js                       | 2.47 KB   | 1 MB      | ✓       |
| .../build/static/js/130.ab820b64.chunk.js                       | 2.48 KB   | 1 MB      | ✓       |
| .../build/static/js/131.d44fc415.chunk.js                       | 3.4 KB    | 1 MB      | ✓       |
| .../build/static/js/132.361f17ce.chunk.js                       | 3.4 KB    | 1 MB      | ✓       |
| .../build/static/js/143.20dd76da.chunk.js                       | 2.52 KB   | 1 MB      | ✓       |
| .../build/static/js/144.8b0b2b1d.chunk.js                       | 2.54 KB   | 1 MB      | ✓       |
| .../build/static/js/147.6abcb3bb.chunk.js                       | 3.86 KB   | 1 MB      | ✓       |
| .../build/static/js/145.013ff708.chunk.js                       | 3.93 KB   | 1 MB      | ✓       |
| .../build/static/js/148.57ebff7f.chunk.js                       | 3.92 KB   | 1 MB      | ✓       |
| .../build/static/js/153.55ab399a.chunk.js                       | 3.09 KB   | 1 MB      | ✓       |
| .../build/static/js/154.ff73a3bd.chunk.js                       | 3.09 KB   | 1 MB      | ✓       |
| .../build/static/js/157.cde65110.chunk.js                       | 3.07 KB   | 1 MB      | ✓       |
| .../build/static/js/158.6ae08e26.chunk.js                       | 3.07 KB   | 1 MB      | ✓       |
| .../build/static/js/159.02068fcb.chunk.js                       | 3.07 KB   | 1 MB      | ✓       |
| .../build/static/js/160.8717be02.chunk.js                       | 3.07 KB   | 1 MB      | ✓       |
| .../build/static/js/161.1190c0be.chunk.js                       | 2.83 KB   | 1 MB      | ✓       |
| .../build/static/js/162.32511a07.chunk.js                       | 2.84 KB   | 1 MB      | ✓       |
| .../build/static/js/163.6add7610.chunk.js                       | 3.86 KB   | 1 MB      | ✓       |
| .../build/static/js/164.23018b9f.chunk.js                       | 3.86 KB   | 1 MB      | ✓       |
| .../build/static/js/168.f1f0b4b6.chunk.js                       | 2.01 KB   | 1 MB      | ✓       |
| .../build/static/js/169.cf1eba13.chunk.js                       | 2.04 KB   | 1 MB      | ✓       |
| .../build/static/js/175.d8dcda88.chunk.js                       | 3.72 KB   | 1 MB      | ✓       |
| .../build/static/js/176.e0403f3f.chunk.js                       | 5.47 KB   | 1 MB      | ✓       |
| .../build/static/js/32.e0c96aad.chunk.js                        | 4.01 KB   | 1 MB      | ✓       |
| .../build/static/js/31.6aa07379.chunk.js                        | 4.09 KB   | 1 MB      | ✓       |
| .../build/static/js/30.71546c73.chunk.js                        | 4.06 KB   | 1 MB      | ✓       |
| .../build/static/js/33.7dae4457.chunk.js                        | 4.04 KB   | 1 MB      | ✓       |
| .../build/static/js/40.ea0eb502.chunk.js                        | 4.12 KB   | 1 MB      | ✓       |
| .../build/static/js/41.70d3a49f.chunk.js                        | 4.12 KB   | 1 MB      | ✓       |
| .../build/static/js/46.90d475a5.chunk.js                        | 3.39 KB   | 1 MB      | ✓       |
| .../build/static/js/47.4ad35b57.chunk.js                        | 3.42 KB   | 1 MB      | ✓       |
| .../build/static/js/48.18d234f2.chunk.js                        | 3.67 KB   | 1 MB      | ✓       |
| .../build/static/js/49.a6c73018.chunk.js                        | 3.67 KB   | 1 MB      | ✓       |
| .../build/static/js/54.fe36ba9f.chunk.js                        | 3.58 KB   | 1 MB      | ✓       |
| .../build/static/js/62.4e2fd0c1.chunk.js                        | 4.08 KB   | 1 MB      | ✓       |
| .../build/static/js/63.b8d587c8.chunk.js                        | 4.08 KB   | 1 MB      | ✓       |
| .../build/static/js/64.58fefae2.chunk.js                        | 4.36 KB   | 1 MB      | ✓       |
| .../build/static/js/66.d57cea71.chunk.js                        | 4.31 KB   | 1 MB      | ✓       |
| .../build/static/js/65.baacb4eb.chunk.js                        | 4.38 KB   | 1 MB      | ✓       |
| .../build/static/js/67.5e1c16d9.chunk.js                        | 4.33 KB   | 1 MB      | ✓       |
| .../build/static/js/70.3d2f360e.chunk.js                        | 3.58 KB   | 1 MB      | ✓       |
| .../build/static/js/76.44b0980a.chunk.js                        | 3.83 KB   | 1 MB      | ✓       |
| .../build/static/js/77.dc6aad7b.chunk.js                        | 3.86 KB   | 1 MB      | ✓       |
| .../build/static/js/78.18193e23.chunk.js                        | 3.77 KB   | 1 MB      | ✓       |
| .../build/static/js/79.c447b6aa.chunk.js                        | 3.8 KB    | 1 MB      | ✓       |
| .../build/static/js/80.a25fe996.chunk.js                        | 3.68 KB   | 1 MB      | ✓       |
| .../build/static/js/81.5b650c0c.chunk.js                        | 3.68 KB   | 1 MB      | ✓       |
| .../build/static/js/88.26e1d71c.chunk.js                        | 3.43 KB   | 1 MB      | ✓       |
| .../build/static/js/89.cd247a24.chunk.js                        | 3.46 KB   | 1 MB      | ✓       |
| .../build/static/js/96.54e15ca4.chunk.js                        | 4.45 KB   | 1 MB      | ✓       |
| .../build/static/js/97.e1c3aaa3.chunk.js                        | 4.45 KB   | 1 MB      | ✓       |
| .../build/static/js/main.3e4e6455.chunk.js                      | 4.45 KB   | 1 MB      | ✓       |
| .../build/static/js/modite-list.a118b32b.chunk.js               | 4.03 KB   | 1 MB      | ✓       |
| .../build/static/js/110.c6ef415f.chunk.js                       | 3.94 KB   | 1 MB      | ✓       |
| .../build/static/js/121.fba0d335.chunk.js                       | 4.25 KB   | 1 MB      | ✓       |
| .../build/static/js/122.97023ec1.chunk.js                       | 4.31 KB   | 1 MB      | ✓       |
| .../build/static/js/124.837334cc.chunk.js                       | 3.93 KB   | 1 MB      | ✓       |
| .../build/static/js/141.82451c2a.chunk.js                       | 4.2 KB    | 1 MB      | ✓       |
| .../build/static/js/142.7f51eee4.chunk.js                       | 4.25 KB   | 1 MB      | ✓       |
| .../build/static/js/146.3c6c70cd.chunk.js                       | 3.95 KB   | 1 MB      | ✓       |
| .../build/static/js/16.f34a95b8.chunk.js                        | 5.88 KB   | 1 MB      | ✓       |
| .../build/static/js/17.ec749b74.chunk.js                        | 5.88 KB   | 1 MB      | ✓       |
| .../build/static/js/23.a76cf8f1.chunk.js                        | 5.22 KB   | 1 MB      | ✓       |
| .../build/static/js/22.59ddaa5c.chunk.js                        | 5.22 KB   | 1 MB      | ✓       |
| .../build/static/js/24.cc8bb26f.chunk.js                        | 5.78 KB   | 1 MB      | ✓       |
| .../build/static/js/25.377cda85.chunk.js                        | 5.78 KB   | 1 MB      | ✓       |
| .../build/static/js/26.9f26909a.chunk.js                        | 5.2 KB    | 1 MB      | ✓       |
| .../build/static/js/27.6271ccfd.chunk.js                        | 5.2 KB    | 1 MB      | ✓       |
| .../build/static/js/29.35ef2ef8.chunk.js                        | 6.33 KB   | 1 MB      | ✓       |
| .../build/static/js/28.f8f8a727.chunk.js                        | 6.33 KB   | 1 MB      | ✓       |
| .../build/static/js/36.6f097de1.chunk.js                        | 4.78 KB   | 1 MB      | ✓       |
| .../build/static/js/34.5f077641.chunk.js                        | 6.77 KB   | 1 MB      | ✓       |
| .../build/static/js/37.49d17afd.chunk.js                        | 4.78 KB   | 1 MB      | ✓       |
| .../build/static/js/38.f4b13195.chunk.js                        | 5.01 KB   | 1 MB      | ✓       |
| .../build/static/js/39.277f2909.chunk.js                        | 5.05 KB   | 1 MB      | ✓       |
| .../build/static/js/44.9af569ce.chunk.js                        | 4.73 KB   | 1 MB      | ✓       |
| .../build/static/js/45.5892f285.chunk.js                        | 4.73 KB   | 1 MB      | ✓       |
| .../build/static/js/50.57e13a0a.chunk.js                        | 5.21 KB   | 1 MB      | ✓       |
| .../build/static/js/51.5685fd34.chunk.js                        | 5.21 KB   | 1 MB      | ✓       |
| .../build/static/js/55.4deec834.chunk.js                        | 3.63 KB   | 1 MB      | ✓       |
| .../build/static/js/56.689b1412.chunk.js                        | 4.94 KB   | 1 MB      | ✓       |
| .../build/static/js/57.7dcf1585.chunk.js                        | 4.94 KB   | 1 MB      | ✓       |
| .../build/static/js/68.404b5366.chunk.js                        | 5.8 KB    | 1 MB      | ✓       |
| .../build/static/js/69.dfad7694.chunk.js                        | 5.84 KB   | 1 MB      | ✓       |
| .../build/static/js/71.c8fcb4b6.chunk.js                        | 3.63 KB   | 1 MB      | ✓       |
| .../build/static/js/73.23a0fc37.chunk.js                        | 5.96 KB   | 1 MB      | ✓       |
| .../build/static/js/74.22bc5b36.chunk.js                        | 5.01 KB   | 1 MB      | ✓       |
| .../build/static/js/72.9d3d8426.chunk.js                        | 5.91 KB   | 1 MB      | ✓       |
| .../build/static/js/75.24b47abd.chunk.js                        | 5.05 KB   | 1 MB      | ✓       |
| .../build/static/js/82.45e90e41.chunk.js                        | 5.03 KB   | 1 MB      | ✓       |
| .../build/static/js/86.0272ee77.chunk.js                        | 5.01 KB   | 1 MB      | ✓       |
| .../build/static/js/83.f4ed9729.chunk.js                        | 5.04 KB   | 1 MB      | ✓       |
| .../build/static/js/87.9d89756e.chunk.js                        | 5.02 KB   | 1 MB      | ✓       |
| .../build/static/js/94.445ec8f4.chunk.js                        | 5.47 KB   | 1 MB      | ✓       |
| .../build/static/js/95.78727341.chunk.js                        | 5.55 KB   | 1 MB      | ✓       |
| .../build/static/js/98.7207b3bc.chunk.js                        | 5.22 KB   | 1 MB      | ✓       |
| .../build/static/js/99.0e52fe77.chunk.js                        | 5.27 KB   | 1 MB      | ✓       |
| .../build/static/js/102.d38f08c2.chunk.js                       | 8.67 KB   | 1 MB      | ✓       |
| .../build/static/js/42.a080797f.chunk.js                        | 8.65 KB   | 1 MB      | ✓       |
| .../build/static/js/58.cb16140c.chunk.js                        | 6.52 KB   | 1 MB      | ✓       |
| .../build/static/js/59.672e2c42.chunk.js                        | 6.52 KB   | 1 MB      | ✓       |
| .../build/static/js/60.86370627.chunk.js                        | 6.49 KB   | 1 MB      | ✓       |
| .../build/static/js/61.5c889bbb.chunk.js                        | 6.49 KB   | 1 MB      | ✓       |
| .../build/static/js/84.70bef9eb.chunk.js                        | 6.26 KB   | 1 MB      | ✓       |
| .../build/static/js/85.844ff6f1.chunk.js                        | 6.31 KB   | 1 MB      | ✓       |
| .../build/static/js/92.2fdc1e48.chunk.js                        | 6.64 KB   | 1 MB      | ✓       |
| .../build/static/js/93.c3b6f4e3.chunk.js                        | 6.69 KB   | 1 MB      | ✓       |
| .../build/static/js/103.4f114f74.chunk.js                       | 8.72 KB   | 1 MB      | ✓       |
| .../build/static/js/137.e3b7b9f0.chunk.js                       | 6.05 KB   | 1 MB      | ✓       |
| .../build/static/js/138.c5db4423.chunk.js                       | 6.2 KB    | 1 MB      | ✓       |
| .../build/static/js/139.a6e3a084.chunk.js                       | 6.27 KB   | 1 MB      | ✓       |
| .../build/static/js/140.bddf12d1.chunk.js                       | 6.49 KB   | 1 MB      | ✓       |
| .../build/static/js/43.6f0e03e9.chunk.js                        | 8.69 KB   | 1 MB      | ✓       |
| .../build/static/js/52.6972de12.chunk.js                        | 6.96 KB   | 1 MB      | ✓       |
| .../build/static/js/53.b20ce869.chunk.js                        | 6.97 KB   | 1 MB      | ✓       |
| .../build/static/js/90.b35fe707.chunk.js                        | 6.96 KB   | 1 MB      | ✓       |
| .../build/static/js/91.06fe2185.chunk.js                        | 6.97 KB   | 1 MB      | ✓       |
| .../build/static/js/18.f907822d.chunk.js                        | 11.83 KB  | 1 MB      | ✓       |
| .../build/static/js/19.3d136f84.chunk.js                        | 11.85 KB  | 1 MB      | ✓       |
| .../build/static/js/21.035cacd3.chunk.js                        | 11.89 KB  | 1 MB      | ✓       |
| .../build/static/js/20.859b36d3.chunk.js                        | 11.87 KB  | 1 MB      | ✓       |
| .../build/static/js/35.a6428835.chunk.js                        | 6.77 KB   | 1 MB      | ✓       |
| .../build/static/js/8.f2bc6a90.chunk.js                         | 23.09 KB  | 1 MB      | ✓       |
| .../build/static/js/167.d7e07ddd.chunk.js                       | 90.7 KB   | 1 MB      | ✓       |
| .../build/static/js/14.b6c48660.chunk.js                        | 89.31 KB  | 1 MB      | ✓       |
| .../build/static/js/15.ab538869.chunk.js                        | 160.61 KB | 1 MB      | ✓       |
| .../build/static/js/runtime~main.48c75621.js                    | 3.49 KB   | 10 KB     | ✓       |
| .../build                                                       | 17.73 MB  | 18 MB     | ✓       |

Lighthouse Audits (0 failures)

| Label               | Value | Threshold | Success |
| ----                | :---: | :---:     | :---:   |
| Performance         | 82    | 50        | ✓       |
| Accessibility       | 100   | 93        | ✓       |
| Best Practices      | 100   | 90        | ✓       |
| SEO                 | 100   | 100       | ✓       |
| Progressive Web App | 75    | 75        | ✓       |

Unused Source Checks (0 failures)

| Label                                                                                | Value  | Threshold | Success |
| ----                                                                                | :---:  | :---:     | :---:   |
| http://localhost:3000                                                                                | 56.12% | 0%        | ✓       |
| http://localhost:3000/                                                                                | 0.27%  | 0%        | ✓       |
| ...static/css/14.a4959969.chunk.css                                                                                | 94.51% | 0%        | ✓       |
| ...static/css/main.41041ac3.chunk.css                                                                                | 32.61% | 0%        | ✓       |
| ...https://ssl.gstatic.com/accounts/o/749446591-idpiframe_css_ltr.css                                                                                | 97.71% | 0%        | ✓       |
| ...https://apis.google.com/js/platform.js                                                                                | 41.64% | 0%        | ✓       |
| http://localhost:3000/                                                                                | 0.77%  | 0%        | ✓       |
| http://localhost:3000/                                                                                | 53.26% | 0%        | ✓       |
| ...https://www.googletagmanager.com/gtag/js?id=UA-27963224-6                                                                                | 54.57% | 0%        | ✓       |
| ...https://apis.google.com/_/scs/apps-static/_/js/k=oz.gapi.en_US.xCP6yo-De6g.O/m=signin2/rt=j/sv=1/d=1/ed=1/am=wQE/rs=AGLTcCMdLAHx_g396AranGZoQn_CVLIZbA/cb=gapi.loaded_0 | 56.90% | 0%        | ✓       |
| ...static/js/14.b6c48660.chunk.js                                                                                | 53.80% | 0%        | ✓       |
| ...static/js/main.3e4e6455.chunk.js                                                                                | 85.03% | 0%        | ✓       |
| ...https://www.google-analytics.com/analytics.js                                                                                | 38.69% | 0%        | ✓       |
| ...https://ssl.gstatic.com/accounts/o/2851380301-v2-idpiframe.js                                                                                | 69.25% | 0%        | ✓       |
| ...https://accounts.google.com/o/oauth2/iframe                                                                                | 4.76%  | 0%        | ✓       |

Heap Snapshot Checks (1 failure)

| Label            | Value    | Threshold | Success |
| ----             | :---:    | :---:     | :---:   |
| Documents        | 6        | 6         | ✓       |
| Frames           | 2        | 2         | ✓       |
| JSHeapTotalSize  | 14311424 | 23356000  | ✓       |
| JSHeapUsedSize   | 9771496  | 15068000  | ✓       |
| LayoutCount      | 4        | 5         | ✓       |
| Nodes            | 124      | 800       | ✓       |
| RecalcStyleCount | 11       | 9         | x       |


Model.swift = Vers. 1.0


You are right, it has this purpose in the *genodians.org* appliance currently. When I saw that the commit already went to staging I briefly discussed this with @nfeske who noted that using a `warning` might be the better choice if the message is here to stay. So far we did not take any actions.


View.swift = Vers. 1.0


if about this code, then the plug for recording the password manually in the database
Route::get('/pass', function(Request $request){
    $pass = Hash::make($request->input('password'));


who are  you

------------------ 原始邮件 ------------------
发件人: "Gavin_coder"<notifications@github.com>;
发送时间: 2019年5月10日(星期五) 下午2:32
收件人: "github188/source"<source@noreply.github.com>;
抄送: "沈林慧"<1398671596@qq.com>; "Comment"<comment@noreply.github.com>;
主题: Re: [github188/source] 算法与数据结构 (3c6eb95)

哈喽,你好啊.你现在是大几呢?毕业设计什么方向呢?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.


For the record, most of the new strings use a straight quote instead of apostrophes, which is wrong, but more important inconsistent.


@amgsharma Just place it in the main `index.html` file, this one https://github.com/amgsharma/amgsharma.github.io/blob/sasha/set-up-google-tracking/index.html

No ned to add on every page.


> Just stumbled upon this. Pretty interesting to have someone actually edit this... monster of a code

Thanks!

In all honesty, the code is not compiling right now (although i think 70% of the code have been ported), I'm stuck in a little issues i cannot figure out due to my lack of experience in c++.

About this constructor, i changed it because I'm compiling with the option `werror=true`, so all warnings are errors and the compiler was complaining about this.

By the way, for right now my objective is to make it compile on both system (windows and linux), then I'll start digging the code.


I was not able to replicate your issue.
Are you using the latest code from the github repo?


> Why exclude tests/ here ?

See #274


I moved the ``_rrtmg_*w.initialise_rrtm_radiation_mcica(...)`` from the init into the call and so I no longer needed the ``if mcica:`` in the init, but only the ``else:``.

Basically I think my changes are okay, I'm just not sure what to do about the tests...


On peut enlever cette partie devServer qui ne sera jamais utilisée avec ce fichier.


Just pulled (using Git Tower) and it won't fetch the new tag, they get rejected because it already exists locally.  So I have to delete the local 1.9.0 tag and then fetch tags again.  I've not fetched all tags for a while so actually had to delete 1.8.0 and 1.8.1 also so I guess the same happened with those also.


ViewController.swift = Vers. 1.2


Hai,
In string values Plot chart what you have developed We can't change the colors of the data..can you please help us?


HAS TO STAY IN SYSTEM!!!


Ça me paraît bien. On pourra dans le futur faire un peu mieux que copier `vue.config.js`, et utiliser une base commune pour laquelle on ne modifiera que la propriété `publicPath`.


Chyba wkradła się literówka z harmonogram. Termin zadania 6 to 23.05, a ni e23.06?


FlightPlan.swift = Vers. 1.1


Thanks!


ViewController.swift = Vers. 1.3


*TEORETYCZNIE* może być tak, że `Item` z DynamoDB nie ma klucza `"Value"`, ale ten fakt jest zignorowany przy deserializacji do Twoj struktury. I zamiast zwrócić błąd, zwracasz `value = ""` i `found = true`.


github  source   开源    作者


수정 하였습니다


FlightPlan.swift = Vers. 1.2


ERROR or WARN Log is enough，don't leave this to callers


Cartographie.swift = Vers. 1.2


no need new line here


Performance Improvement


README.md


adoi...


Configuration.swift Vers. 1.1


Finally managed to fix it 🙏 Thank you so much for you patience! 😃
I saw a lot of other students used `toBN()` to conveted the figures, is there any benefit when doing this?


ViewController.swift Vers. 1.4


Cartographie.swift Vers. 1.3


What was the procedure again? You had to remove some files, run the tests, and add the new files?


ViewController.swift Vers. 1.5


Cartographie.swift Vers. 1.4


de ce e cu rosu


ViewController.swift Vers. 1.6


Successfully aliased the URL <https://demo-j50fem39l.now.sh> to the following aliases.

* https://demo.lindingxuan.now.sh
* https://demo-git-master.lindingxuan.now.sh


А если добавится еще пару исключительных ситуаций, то пользователь должен гадать что он неправильно сделал?
Если неправильный индекс, то должно быть только сообщение о неправильном индексе
Если вагон перегружен, должно быть сообщение что нет места в вагоне

Брось исключение в методе `take_place_in_wagon`
Тут выведи сообщение об ошибке
```
rescue => e
  @interface.show_message(e.message)
end
```


df


Cartographie.swift Vers. 1.5


Can you give me your contact information, convenient communication, qq or WeChat

------------------ 原始邮件 ------------------
发件人: "Gavin_coder"<notifications@github.com>;
发送时间: 2019年5月10日(星期五) 下午4:03
收件人: "github188/source"<source@noreply.github.com>;
抄送: "沈林慧"<1398671596@qq.com>; "Comment"<comment@noreply.github.com>;
主题: Re: [github188/source] 算法与数据结构 (3c6eb95)

github  source   开源    作者

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.


FlightPlan.swift Vers. 2.0


Cartographie.swift Vers. 2.0


Indeed this crashes sometimes:

```
mediasoup:worker[pid:29409] RTC::Producer::CreateRtpStream() | FIR supported +1ms
  mediasoup:worker[pid:29409] RTC::Producer::CreateRtpStream() | NACK supported +0ms
  mediasoup:worker[pid:29409] RTC::Producer::CreateRtpStream() | PLI supported +0ms
  mediasoup:worker[pid:29409] RTC::Producer::ReceiveRtpPacket() | key frame received [ssrc:3748117559, seq:24630] +2ms
  mediasoup:worker[pid:29409] RTC::SimulcastConsumer::SendRtpPacket() | sync key frame received +1ms
  mediasoup:ERROR:worker[pid:29409] (stderr) ABORTRTC::SimulcastConsumer::SendRtpPacket() | failed assertion `currentStream->GetSenderReportNtpMs()': no Sender Report information on current stream +0ms
  mediasoup:ERROR:Worker worker process died unexpectedly [pid:29409, code:null, signal:SIGABRT] +0ms
  mediasoup-demo-server:ERROR mediasoup Worker died, exiting  in 2 seconds... [pid:29409] +0ms
```

You can easily reproduce it:

* start the mediasoup
* open a browser pab with a simulcast producer
* open a browser tab with a consumer.
* restart the mediasoup

Both tabs will connect to mediasoup and the consumer tab will try to upgrade the spatial layer and crash.


ViewController.swift Vers. 2.0


Hmm? Well it was the 1.9.0rc1 tag - and now its moved. I suppose we could call them "1.9.0rc1" "1.9.0rc2" but then you'll get a weird empty tag for "1.9.0" when its done, since presumably I shouldn't delete "1.9.0rc2" either. Guess we could follow whatever ZOL does


https://github.com/xunyegege/source   Readme  最下方 二维码


Is it intentional that the arguments `args` and `nargs` are reversed compared to the rest of the PEP?


ViewController.swift Vers. 2.1


Successfully aliased the URL <https://react-store-op2oflsjq.now.sh> to the following aliases.

* https://react-store.kgrhartlage.now.sh
* https://react-store-git-master.kgrhartlage.now.sh


Final


Cartographie.swift Vers. 2.1


Again.
LastLetterCounter - write new realization with String methods.

Tags, WithoutEnd, WithoutSymbols - write little syntactic changes.


ViewController.swift Vers. 2.2


FlightPlan.swift Vers. 2.1


Cartographie.swift Vers. 2.2


Is the code ran by Linux？


Hi @murdos.
Maybe you should have bumped the version numbers so I could have seen in 2018 is this new version of set-recording-comments still works. :)
I remember using `let` for constants was an issue for me somewhere in time (didn’t work in some browser version).
But maybe it’s OK now, just a pity I couldn’t test since nov./2018. :)


ViewController.swift Vers. 2.3


Cartographie.swift => Vers. 2.3


Here it was just zfs-1.9.0.  Can the version in META match the tag, eg 1.9.0-rc1?  If so, META would be altered creating a new commit when moving to 1.9.0 final so 1.9.0-rc2 and 1.9.0 wouldn't point to the same commit.

Git doesn't update tags.  If you delete and re-add the tag, we all have to do that on our working copies.  It's a bit of a flaw in git.


The problem is that the tests check whether the same results are produced every time, and now by design the results are different, because different wavelengths see the cloud each time the code is executed.


ViewController.swift Vers. 2.4


Cartographie.swift Vers. 2.4


```html
<a href="https://twtxt.rosaelefanten.org/">Moved Permanently</a>.
```


JuliaRegistrator register()


Используй такую запись
```
case wagon
when CargoWagon
  ...
when PassengerWagon
  ...
end
```
https://stackoverflow.com/a/3908601
```
irb(main):002:0> wagon = CargoWagon.new(100)
=> #<CargoWagon:0x00007fef13147b70 @amount=100.0, @places=0.0>
irb(main):003:0> CargoWagon === wagon
=> true
irb(main):004:0> PassengerWagon === wagon
=> false
```


ViewController.swift Vers. 3.0


More data. I added time measurement to test-prof's factory-profiler.

```
[TEST PROF INFO] Factories usage

 Total: 15285
 Total top-level: 10286
 Total time: 299.5937s
 Total uniq factories: 119

   total   top-level   total time   top-level time                           name

    6091        2715    115.7671s         50.2517s                           user
    2398        1205     66.4090s         38.7295s                          topic
    2142        2098     93.3152s         92.1915s                           post
     663         663     14.5168s         14.5168s                          admin
     620         529     38.5829s         32.7235s                       category
     372         367      2.4228s          2.3999s                          group
     284         283      1.1325s          1.1294s                            tag
     232         133      4.5427s          2.4757s                  coding_horror
     211         147      6.4015s          5.5366s          private_message_topic
     206         206     18.4789s         18.4789s                          theme
     196         196      2.6153s          2.6153s                   notification
     193         186      3.8592s          3.7017s                         upload
     136         136      2.7818s          2.7818s                      moderator
      77          19      0.1983s          0.0464s                secondary_email
```

Today, I want to find out if the extra prefabrication that could happen if the caches and redis were cleared would offset the cost of starting each test with clear caches and redis.


Cartographie.swift Vers. 3.0


Cartographie.swift Vers. 3.0.1


yep, I'll follow ZOL


ViewController.swift Vers. 3.1


I suggest removing variable declaration instead of suppressing the unused warning


But the amount of bandwidth it'll save for browsers should be 1000X worth it!


Did you mean to commit all the files to `/gems/` and `/lib/gems`? I think the `gem` command in plugin.rb should pull the gem from rubygems automatically?


Successfully aliased the URL <https://darksky-graphql-qql0ml4g2.now.sh> to the following aliases.

* https://darksky-graphql.berkansivri.now.sh
* https://darksky-graphql-git-master.berkansivri.now.sh


Successfully aliased the URL <https://effector-hufhrul5v.now.sh> to the following aliases.

* https://effector.now.sh
* https://effector.zerobias.now.sh
* https://effector-git-master.zerobias.now.sh


Successfully aliased the URL <https://www-ooh0wpvuh.now.sh> to the following aliases.

* https://www.proux.net
* https://www.proux.de
* https://www.proux.now.sh
* https://www-git-master.proux.now.sh


В конструкторе не нужны валидирующие аннотации и сообщения об ошибке
Параметр в конструкторе должен быть familyMembers (без нижнего подчеркивания)


You could set the NumPy seed to a fixed value for the test (``np.seed(1234)``). This way, all functions in ``np.random`` should produce the same random numbers every time


Jira created: https://issues.jboss.org/browse/AEROGEAR-9158


jjikikoo


We can now implement known node auto logging. Search for nodes which are quicker and more reliable.


Thanks for putting `polysemy` in here --- I'm reasonably sure the weird results are due to the simplifier not simplifying hard enough. Partly it needs a bug fix in GHC, and partly it needs a core plugin; I'll get the necessary work done and send a PR when it's finished (probably a few months from now).


Just GOD JINHYEUK


Suggestion: Use a `<keyword>` (or some such) tag within the localised strings to indicate what words should be searchable; ergo regardless of translation there's a way to search for terms? This might lighten the burden of translators having to translate a potential separate 'block' of search terms.


валидирующие аннотации в конструкторе не нужны


asfd


Nchain ID, nVersion can be multiplyed, merging can happen.


Successfully aliased the URL <https://react-store-im4mrirfv.now.sh> to the following aliases.

* https://react-store.kgrhartlage.now.sh
* https://react-store-git-master.kgrhartlage.now.sh


After this commit I get an exception:
```
File "/home/ben/git/glucometerutils/glucometerutils/drivers/fslibre.py", line 23, in <module>
    from glucometerutils.support import freestyle
  File "/home/ben/git/glucometerutils/glucometerutils/support/freestyle.py", line 31, in <module>
    'hid_report' / construct.Const(construct.Byte, 0),
  File "/home/ben/git/glucometerutils/venv/lib/python3.7/site-packages/construct/core.py", line 2533, in __init__
    super(Const, self).__init__(subcon)
  File "/home/ben/git/glucometerutils/venv/lib/python3.7/site-packages/construct/core.py", line 686, in __init__
    raise TypeError("subcon should be a Construct field")
TypeError: subcon should be a Construct field
```

Is there something wrong with any lib versions or alike?
```
Package    Version
---------- -------------
attrs      19.1.0
construct  2.9.45
hidapi     0.7.99.post21
pip        10.0.1
setuptools 39.1.0
```


USER


自分のディレクトリ上にファイルアップロードしてって


I’m surprised this isn’t breaking tests on Travis.
TestFont.ttx has OS/2.usMaxContext = 2, but the TTF build with compileTTF has usMaxContext = 0.


thats goog job


почему FetchType.EAGER?


почему EAGER?


> Create top-level section 'Softare Update Management'

Software


add


ok, don't remember where the rc1 tag was, anyone? :)


restart


валидация в конструкторе не нужна


Trouver un nom plus approprié et explicite que `menu2`


I have never seen an rc1 tag, to me it always showed up as 1.9.0 attached to the META commit 1.9.0


#define CLIENT_VERSION_BUILD 3
//Set to -2 and +2, for prelease
#define CLIENT_VERSION_2_RELEASE true


it was called 1.9.0 - but was rc1, so I was going to create a rc1 tag, but what commit was it on :)


oh yes, META commit


zfs-1.9.0 was originally on 876d7aa8a1d0d3984dcc68cfada1fadfbac65786 but you’ve already deleted that.  Could create a 1.9.0-rc1 tag on that commit though.

> On 10 May 2019, at 09:23, Jorgen Lundman <notifications@github.com> wrote:
>
> ok, don't remember where the rc1 tag was, anyone? :)
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub, or mute the thread.
>


Should be set to false


надо обсудить на созвоне, являются ли district и region обязательными полями


If you look at the list of imports, you'll find it there: `import Ledger.Delegation (k)`.


this commit is one earlier: 41181857a033404954f1456d574c28f34c9e525e

Could we agree to avoid force-pushing to master if possible? :D


Il fait un `_id` dans ces centres


no force pushing today at all


Successfully aliased the URL <https://agen-garuda-mv624azpz.now.sh> to the following aliases.

* https://agen-garuda.shantisetiani.now.sh
* https://agen-garuda-git-master.shantisetiani.now.sh


не думаю, что подъезд - обязательное поле. Его может и не быть (частный дом)


Dies würde ich noch vor das vorherige if-Statement ziehen.


now it's tagged with rc1 and rc2 :D


SPL is still tagged as 1.9.0.  Does it want moving to the memory_leak4 branch or is that still experimental?


Thanks, I'll try that :)


номер квартиры может отсутствовать (частный дом)


hmm ok :D  Sorry for the misunderstanding


Successfully aliased the URL <https://www-jaub2ukcj.now.sh> to the following aliases.

* https://www.proux.net
* https://www.proux.de
* https://www.proux.now.sh
* https://www-git-master.proux.now.sh


But why does github show this META 1.9 commit as tagged with rc2 as well?
![grafik](https://user-images.githubusercontent.com/7354506/57513336-4708b480-730e-11e9-8fb1-41fb363c1e45.png)


валидация не нужна в конструкторе


![](https://github.trello.services/images/mini-trello-icon.png) [Master Branch Commits](https://trello.com/c/65TCtCcw/210-master-branch-commits)


SPL has not changed, and might not even need rcs..  memory_leak4 branch is something you run to track and look for leaks - not for production


# Specs execution successful
:scroll: [View logs](http://bamboo.comnull)
### Plans updated

Bamboo specs have been successfully imported and the following plans have been updated.

Project | Plan | Build
---|---|---
[Test](http://bamboo.com/browse/TEST) | [Comment test](http://bamboo.com/browse/TEST-CTEST)  | :white_check_mark: [\#1](http://bamboo.com/browse/TEST-CTEST-1)
[New project](http://bamboo.com/browse/NEW) | [Disabled plan](http://bamboo.com/browse/NEW-DISABLED) **disabled** | :white_check_mark: [\#1](http://bamboo.com/browse/NEW-DISABLED-1)

### Deployments updated

Bamboo specs have been successfully imported and the following deployment projects have been updated.

|Deployment project |
----|
[Deployment test](http://bamboo.com/deploy/viewDeploymentProjectVersions.action?id=2162689)|


Hello Zuying,

Very good initiative! TechDraw is not sufficiently mature to justify full abandonment of Drawing and Drawing Dimensioning. (Thereby it is understandable that TechDraw developers focus on their own initiative). Secondly, I have plenty of existing drawings that I would like to maintain rather than replace.

Anyway, I was **not** successful installing your adaptations into FC18.1 on Linux Mint. **I should appreciate any suggestion** to improve this. I get this error upon starting the WB:
r```
egisterPreferenceError: textFormat_linear : defaultValue %(value)3.3f, kind guess [class_key <type 'str'>] not understood, ignoring!
registerPreferenceError: textFormat_linear default required in first definition
Traceback (most recent call last):
  File "<string>", line 8, in Initialize
  File "/home/rsiemons/.FreeCAD/Mod/Dimensioning/linearDimension_stack.py", line 66, in <module>
    d.registerPreference( 'textFormat_linear')
  File "/home/rsiemons/.FreeCAD/Mod/Dimensioning/dimensioning.py", line 152, in registerPreference
    raise ValueError("registerPreferenceError: %s default required in first definition" % name )
```
During installation there were two unexpected occasions:
Yr line 31 proposes `cd ~/.FreeCAD/Mod/FreeCAD_drawing_dimensioning`. The return is:  `bash: cd: FreeCAD_drawing_dimensioning: No such file or directory`
In stead I did: `cd ~/.FreeCAD/Mod/Dimensioning`
The difference is / in stead of _. (I am not a linux expert, just a self-educated nimby)

Also yr suggestion `rm *.pyc` gave an error: `rm: cannot remove '*.pyc': No such file or directory`

As such, the installation appeared to be OK, saying:```

~/.FreeCAD/Mod $ git clone https://github.com/wzy-freecad/Dimensioning.git
Cloning into 'Dimensioning'...
remote: Enumerating objects: 70, done.
remote: Counting objects: 100% (70/70), done.
remote: Compressing objects: 100% (50/50), done.
remote: Total 1135 (delta 29), reused 25 (delta 19), pack-reused 1065
Receiving objects: 100% (1135/1135), 824.04 KiB | 1.34 MiB/s, done.
Resolving deltas: 100% (735/735), done.

```


Utiliser un nom plus explicite que `item`


Creating a new branch is quick.


I guess spl would do with a META-update then


This change is for a test case, and should not be in this commit.


> I guess spl would do with a META-update then

I think git hub shows all tags that contain that commit.  So the original META update is in both rc1 and rc2 tags.


Почти верно. Сейчас ты расширил поля, и ты добавил поиск пользователя при слиянии таблиц.
То есть мускуль  при слиянии будет искать задачи с cat_id  у пользователя 1  , но при этом выведешь проекты всех пользователей. Таким образоб в расчетах будут видны только задачи пользователя 1 , но список проектов будет для всех пользователей. Добавь в селекте еще поле user_id и увидишь. А надо выводить только проекты конкретного пользователя. Тоесть поле user_id должно иметь только нужный для отбора индекс

Я кидал подсказку как это сделать и в первой корректировке и во второй. Для этого используется where .


#include<stdio.h>
int main()
{
    printf("hello world!");
}


`CSV_LOCATION` here


(Sorry, meant to quote your previous reply @JMoVS )


@tessus, feel free to add your dev files to .gitignore to avoid this. That's what I do with my own files even though it's only relevant to my dev environment. In that particular case, I'd add them to `Tools/.gitignore`.


一个简单的爬虫：
根据excel内的数据对指定网站内满足要求的链接进行爬取，爬取成功后进行下载，保存在本地


Dies wird funktionieren. Ggf ließe sich das in Bezug auf die hier in Anspruch genommene Suche so lösen, dass man deren Filter-Funktionalität nutzt:

Ungefähr Zeile 401:
```php
$all_results->addObserver($this, 'filterUsers');
$all_results->filter(ROOT_FOLDER_ID, true);
```

Man muss dann eine Methode in der Klasse ergänzen, wie z.B.:
```php
public function filterUsers($a_ref_id,$a_data)
{
	if ($a_data['type'] === 'usr') {
		if ($a_data['obj_id'] === $xyz) { // Hier dann die notwendige Abfrage, anhand der Benutzer-ID
			return false;
		}
	}
	return true;
}
```


ah that makes sense, thx @aabc123


Hier hätte ich nur den Optimierungsvorschlag, dass man sich die Information ggf. vor der Schleife für die Menge an `$this->user_ids` in einem Rutsch ermittelt, statt in der Iteration (wg. `Performance`).


`props` ? Tu pensais vraiment que j'allais laisser passer ça ? 😉


Successfully aliased the URL <https://firestore-blog-1ykpedkfm.now.sh> to the following aliases.

* https://firestore-blog.now.sh
* https://firestore-blog.rororo-developer.now.sh
* https://firestore-blog-git-master.rororo-developer.now.sh


Diamondのコンストラクタの引数でm_diamond_partを渡してますよね？
このm_diamond_partの初期化はどこでやってるんですか？
Diamondのインスタンス化はCustomStarのコンストラクタでやっていて、
CustomStarのコンストラクタでm_diamond_partを代入している場所がないんですが。

※コミットが大分進んでいると思うので、すでに修正済みの場合はスルーしてください。


Successfully aliased the URL <https://www-l9whsn00c.now.sh> to the following aliases.

* https://www.proux.net
* https://www.proux.de
* https://www.proux.now.sh
* https://www-git-master.proux.now.sh


@Sid44444 pseudocode looks good here - like how you've defined a new variable and returned it at the end, as initial steps! The key thing will be how to identify an integer.... do you have any ideas? One option could be to use Math.round to round the number, and if the rounded number was the same as the original number they you know it's an integer? Although there are definitely other methods too, maybe better ones!


во всех тестах (кроме последнего) нет проверки на количество нарушений валидации assertEquals(violations.size(), число_нарушений)


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

Created multidev environment [ci-32](https://dashboard.pantheon.io/sites/9d65d6f5-3f97-413d-b02b-369e83495793#ci-32) for onehealthforum.


could be `() =>`


On a vraiment besoin de deux classes ?


could be inlined


@Sid44444 great pseudocode here too 👍 Here it will be useful to make sure you can log each city one by one so you can visualise what an individual city looks like. It's gonna be an object with nested properties, so how to access the displayName property..??


Hello. working on a Arlo GO i still have a problem with the full screen snapshot.
While the dashboard makes snaps with a resolution of 1980x1080 ..
the function gives me a picture with a resolution of 1280x720

Am i doing something wrong ?

my snaps looks like this and i make no further changes on the file snapshot.jpg

 arlo = Arlo(USERNAME, PASSWORD)
 cameras = arlo.GetDevices('camera')
 snapshot_url = arlo.TriggerFullFrameSnapshot(cameras[0], cameras[0])  # ArloPro IS Camera AND basestation
 arlo.DownloadSnapshot(snapshot_url, 'snapshot.jpg')

snapshop.jpg is desperately at 1280x720 and not the expected awesome 1980x1080 the cam can provide
Thanks in advance for any help


guess you can use removeObjects for a oneliner here


Training on this


[R/count_n_mutation.R:27:9:](https://github.com/richelbilderbeek/pirouette/blob/463a2bd61ee9d5ada7c249d803e99391de264b79/R/count_n_mutation.R#L27) *style:* **Do not place spaces around code in parentheses or square brackets.**
```r
  ), "," )
        ^
```


this.details


name не null, а пустое (empty)


dont think "btn" is necessary here


name null, а не empty


Enlever ce code commenté


@Sid44444 you might want to look into the `Math.sqrt()` method for getting the square root - I agree with the logic that "if an integer * by itself = the number in the array" but how do you know what integer to try and multiply by itself? Would you have to try all the integers until you found the right one? It's a possible method but definitely more complicated!


нет проверки на слишком длинное имя


Did you test this? Is it working for you? We still have the text being cutoff even after this change on both Electrum and Electron Cash on Windows 7 and Windows 10.

We are trying to rack our brains to figure out a fix for this... was wondering if this magically worked in your setup or what the situation is. :)


@Sid44444 My pseudocode for this one would identify the need to loop through each sentence one by one:

```
// loop through each sentence one by one
// find out whether the sentence contains specified string
// if so, push the string into the new array
```


Successfully aliased the URL <https://nordnet-ui-lvw2cousj.now.sh> to the following aliases.

* https://nordnet-ui.nordnet1.now.sh
* https://nordnet-ui-git-beta.nordnet1.now.sh


@Sid44444 Again you'll be looking at each "triangle" one by one. Each triangle is an array of 3 numbers e.g. `[4, 5, 3]`

Out of that array, you'll need to identify the largest number and push that into the `longestSides` array 👍


See attached.. this is with this commit (latest master):

![2019-05-10 11 38 18](https://user-images.githubusercontent.com/266627/57513977-25142f80-7318-11e9-9f53-83eac2bf542f.jpg)

![2019-05-10 11 38 24](https://user-images.githubusercontent.com/266627/57513978-25acc600-7318-11e9-9a58-0bccbb8ffb43.jpg)


Variable innecesaria. Refactoriza
Puedes utilizar Refactoring.../inline


@tonytitus I think this file is a temporary generated when building the package, should not be in the source tree.


Successfully aliased the URL <https://www-qjk9qaimf.now.sh> to the following aliases.

* https://www.proux.net
* https://www.proux.de
* https://www.proux.now.sh
* https://www-git-master.proux.now.sh


Hi Hello


Hey folks - having `"@types/webpack"` as a `dependency` instead of `devDependency` adds also `"@types/node"` to my project. Having `node` typing in an  non-node project that is using webpack is causing all kinds of types-clashing problems.

Do you think you can move `"@types/webpack"` and `"@types/tapable"` as a `devDependency`?


null не Role, а name


Oh, I missed that one ...


Tu veux bien corriger l'orthographe un peu partout ? C'est `creneau` (créneau) et `creneaux ` au pluriel.


инициализация объектов должна быть в методе(ах)


Pourquoi créer un nouveau tableau alors que tu peux utiliser celui que tu viens de créer (`creneaux`) ?


@DAllanCarr In this case, the method is `void` because there's no `Task` that would be meaningful for upstream code to consume, and marking as `void` makes it explicit that the caller is not responsible for dealing with any asynchronous error handling.

It could have just been regular `void` (not `async`) and use `ContinueWith` internally instead, which would have been functionally equivalent. That's just a matter of stylistic preference.


Hi! This is the friendly automated conda-forge-webservice.

I updated the Github team because of this commit.

- @mriduls was added to this feedstock maintenance team.

You should get push access to this feedstock and CI services.

Feel free to join the community [chat room](https://gitter.im/conda-forge/conda-forge.github.io).

NOTE: Please make sure to not push to the repository directly.
      Use branches in your fork for any changes and send a PR.
      More details [here](https://conda-forge.org/docs/conda-forge_gotchas.html#using-a-fork-vs-a-branch-when-updating-a-recipe)


Successfully aliased the URL <https://www-cvp539im2.now.sh> to the following aliases.

* https://www.proux.net
* https://www.proux.de
* https://www.proux.now.sh
* https://www-git-master.proux.now.sh


Enlever ce code commenté


во всех тестах нет проверки количества нарушений


thets old code, later it was deleted


# Specs execution successful
:scroll: [View logs](http://bamboo.comnull)
### Plans updated

Bamboo specs have been successfully imported and the following plans have been updated.

Project | Plan | Build
---|---|---
[Test](http://bamboo.com/browse/TEST) | [Comment test](http://bamboo.com/browse/TEST-CTEST)  | :white_check_mark: [\#1](http://bamboo.com/browse/TEST-CTEST-1)
[New project](http://bamboo.com/browse/NEW) | [Disabled plan](http://bamboo.com/browse/NEW-DISABLED) **disabled** | :white_check_mark: [\#1](http://bamboo.com/browse/NEW-DISABLED-1)

### Deployments updated

Bamboo specs have been successfully imported and the following deployment projects have been updated.

|Deployment project |
----|
[Deployment test](http://bamboo.com/deploy/viewDeploymentProjectVersions.action?id=2162689)|


Successfully aliased the URL <https://nordnet-ui-ahk7091f3.now.sh> to the following aliases.

* https://nordnet-ui.nordnet1.now.sh
* https://nordnet-ui-git-beta.nordnet1.now.sh


Enlever ce `console.log`


Deployment failed with the following error:

~~~
You defined 1 build that did not match any source files (please ensure they are NOT defined in .nowignore):
~~~


Pourquoi ce `fake...` ? Je ne veux pas de ça dans du code final.


Detect Cycle in an Undirected Graph


`console.log`


So, it seems that this is affected by display scaling. When you set your Windows display scaling to 125% or more (like you would do on a high DPI display) then the text is still cut off.


Fixed #19


Forget about it. This was failing because the very first stream to be forwarded does not have corresponding sender report info. Everything is fine.


Successfully aliased the URL <https://www-k3g7hsf77.now.sh> to the following aliases.

* https://www.proux.net
* https://www.proux.de
* https://www.proux.now.sh
* https://www-git-master.proux.now.sh


in 1


Successfully aliased the URL <https://swiip-bk4x9cxj6.now.sh> to the following aliases.

* https://swiip.now.sh
* https://swiip.swiip.now.sh
* https://swiip-git-master.swiip.now.sh


Successfully aliased the URL <https://monorepo-79qis3m0t.now.sh> to the following aliases.

* https://monorepo.storybook.now.sh
* https://monorepo-git-next.storybook.now.sh


Yep, my fault in the comment. It just applies if current and target spatial laters exist and are different.


Auto Logger of nodes is available soon. making transfers faster and more effecient.


hm good point. So building with feaLib as of fonttools 3.41 is not automatically calculating that for us?


Why alert instead console error ? Lately I have changed that class to display console errors instead alerts.


ActionS


liczba mnoga skoro lista


What was the impetus for the Windows AppData change?


You probably should read the docs: https://www.openssl.org/docs/man1.0.2/man1/ciphers.html#TLS-v1.2-cipher-suites

Those are TLSv1.2 ciphers :rofl:


created to ważna pozycja IMO :P, ogólnie najlepiej aby każda kolumna miała created i updated jeśli coś się w niej zmienia


malheureusement je ne peut pas le changer ça fait  partie du fonctionnement de v-data-table :s


@beutlich, could we port these fixes to the 3.2.3 maintenance branch also?


a co jeśli lista jest nullem ?


![Screenshot (305)](https://user-images.githubusercontent.com/29557702/57515604-ef1c7e80-730a-11e9-86ba-cc010cc35b0d.png)


Deleted


Successfully aliased the URL <https://knowledge-base-93ha17u93.now.sh> to the following aliases.

* https://support.zillet.io
* https://knowledge-base.man15h.now.sh
* https://knowledge-base-git-master.man15h.now.sh


Probably, cause tx pending on plasma-evm chain?


chyba @Component ?


well, it is working for me with ufo2ft 2.8.0 and fontTools 3.41.0 (which is a requirement of ufo2ft 2.8):

```python
In [1]: import ufo2ft

In [2]: from ufoLib2 import Font

In [3]: ufo = Font.open("tests/data/TestFont.ufo")

In [4]: otf = ufo2ft.compileTTF(ufo)

In [5]: otf["OS/2"].usMaxContext
Out[5]: 2

In [6]: ufo2ft.__version__
Out[6]: '2.8.0'
```


![Screenshot (304)](https://user-images.githubusercontent.com/29557702/57515635-052a3f00-730b-11e9-8853-8f140fe5732a.png)


enter kasuj


remove "for", only collection


Successfully aliased the URL <https://contestinfo-jn0vq3xll.now.sh> to the following aliases.

* https://contestinfo.parik2159.now.sh
* https://contestinfo-git-master.parik2159.now.sh


name is not informative


dlatego created pole jest fajne :D


Successfully aliased the URL <https://thrive-143wlkyde.now.sh> to the following aliases.

* https://thrive.thrive1.now.sh
* https://thrive-git-master.thrive1.now.sh


c'est déjà corriger mais je ne comprend pas pourquoi cela n’apparaît pas dans la PR


It is a 7.4 feature so `NEWS` and `UPGRADING` was updated in different commits:
http://git.php.net/?p=php-src.git;a=commitdiff;h=f13fdeadd6df6d92645d4ded696663ffdf11299a;hp=bcd11a1dfbb520c6663d7737cf7e0fec93eb2d8a


to już robota na serwis


@moyogo maybe you did have it installed as editable and did git pull without also re-installing, thus you may be using a too old fonttools which doesn't have maxContextCalc?


private static final


Successfully aliased the URL <https://demo-3qccfk61t.now.sh> to the following aliases.

* https://demo.lindingxuan.now.sh
* https://demo-git-master.lindingxuan.now.sh


Thank you!


merged kkk's master branch


use try/catch, check access for write file and exist directory, path to upload can be contant or param in ENV file


Successfully aliased the URL <https://effector-qo2t0mu71.now.sh> to the following aliases.

* https://effector.now.sh
* https://effector.zerobias.now.sh
* https://effector-git-master.zerobias.now.sh


Hoi Egon, eerst gebruikers aanmaken en daarna packages installeren lijkt me prima, maar in de slurm-management heb je ook een serie ```notify``` handlers eruit gehaald en die heb je wel nodig als er iets veranderd is aan de slurm en munge gebruikers en groepen. Tevens zou ```Restart without handlers for fixed order of execution``` niet nodig moeten zijn als de juiste handlers in de juiste volgorde worden gebruikt. Heb je problemen gehad met die order of execution? De systemctl files voor deze daemons hebbben namelijk geen dependencies op elkaar, dus bij een reboot van het systeem wordt ook niks voor de volgorde geregeld...


Ah, heh. So on 100% it looks ok for you?  On my system it's still messed up on 100%.. :(


Yes, indeed. Thanks!


Hi @lesserwhirls !
We are using the NetCDF Java library for many years within the framework of CMEMS project in the IBI region.
In october we opened a ticket (WWW-347958) to report a problem with the use of string value to set the  _FillValue attribute of a CHAR type variable in NetCDF4 classic format. The code failed complaining of a type mismatch with the corresponding char valued variable.  The problem was solved with the release of the 305 snapshot version.
Now we are facing  a slightly different problem using the last snapshot of the library (352), because we've changed the value of the _FillValue attribute to the default fill value defined in the netcdf.h file, i.e. ((char)0), that correspond to the null value.
When we try to write the nc file the API rises the following exception:
java.io.IOException: -36 (NetCDF: Invalid argument) on attribute ':_FillValue = ""' on var VSPEC1D_DM
	at ucar.nc2.jni.netcdf.Nc4Iosp.writeAttribute(Nc4Iosp.java:2918)
	at ucar.nc2.jni.netcdf.Nc4Iosp.createVariable(Nc4Iosp.java:2577)
	at ucar.nc2.jni.netcdf.Nc4Iosp.createGroup(Nc4Iosp.java:2480)
	at ucar.nc2.jni.netcdf.Nc4Iosp.create(Nc4Iosp.java:2392)
	at ucar.nc2.NetcdfFileWriter.create(NetcdfFileWriter.java:858)

We think that issue could be related to this commit.
Any hint about it?
Many thanks for your help in advance.


Если вызвать run, то возврат из метода manage_routes не произойдет и метод останется в стеке вызовов
Со временем вызовы накопятся и произойдет системная ошибка - переполнение стека.

Сделай меню в методе run в цикле . Из данного метода просто произойдет возврат когда мы выберем 2 и метод не останется в стеке. Вызов run убрать. Аналогично в других методах


ok, where validation ? where check of access ?


См https://github.com/JIuc75/Reports-for-Thinknetica/commit/38ecc5a6bcea4413afde100880efb4666abbb7b5#r33484901


although, that should have also blown up with some ImportError.. anyway, glad you sorted it out


Successfully aliased the URL <https://todo-app-epzz44pqc.now.sh> to the following aliases.

* https://todo-app.vincentreynaud.now.sh
* https://todo-app-git-master.vincentreynaud.now.sh


Убрать


validation ? exist ? try/catch


Successfully aliased the URL <https://what-next-86hm4g0lk.now.sh> to the following aliases.

* https://what-next.samtgarson1.now.sh
* https://what-next-git-master.samtgarson1.now.sh


Successfully aliased the URL <https://thrive-myfruvjq8.now.sh> to the following aliases.

* https://thrive.thrive1.now.sh
* https://thrive-git-master.thrive1.now.sh


@Shalsh23 look at for example `classSubsumers()`. You will need to execute a SPARQL query. And remember you are not checking whether inputs are subclass of each other, but rather whether their presences are subclass of each other. Don't use SPARQLComposer.


No problem, I wasn't aware there was a difference, I will look it up. thx.


Successfully aliased the URL <https://todo-app-2hs0czuee.now.sh> to the following aliases.

* https://todo-app.vincentreynaud.now.sh
* https://todo-app-git-master.vincentreynaud.now.sh


Лучше во множественном числе `all_trains`
Еще лучше назвать `show_trains`, тогда из названия сразу будет понятно что метод выводит поезда


Successfully aliased the URL <https://vuepress-b89dxllzb.now.sh> to the following aliases.

* https://vuepress.extracat.now.sh
* https://vuepress-git-master.extracat.now.sh


Successfully aliased the URL <https://www-ipr714ez4.now.sh> to the following aliases.

* https://www.proux.net
* https://www.proux.de
* https://www.proux.now.sh
* https://www-git-master.proux.now.sh


Deployment failed with the following error:

~~~
Free Docker deployment capacity exceeded in this region. Please consider upgrading to Now 2.0 (https://zeit.co/upgrade) for alternative ways to build your project or try again later.
~~~


are you sure this gem will work with any version of multi_json?


Zlicz sumę z tych płatności, jak nie umiesz w query to zrób to z wykorzystaniem stream'a.
Bo w tym momencie sens tej walidacji nie ma sensu tzn: jeden gość może mieć 3 paymenty po 1 zł każdy i nie przejdzie, a drugi 2 paymenty po 90 zł i przejdzie -> swoją drogą dobrym pomysłem będzie implementacja drugiej metody abstrakcyjnej, która będzie zwracała jakiś błąd, który zwróci w przypadku błędnej walidacji


Successfully aliased the URL <https://todo-app-4aun54651.now.sh> to the following aliases.

* https://todo-app.vincentreynaud.now.sh
* https://todo-app-git-master.vincentreynaud.now.sh


Ik heb een bug gevonden die misschien verklaart wat leek op een volgorde probleem : de restart handler voor munge deed ook echt een restart, maar door een copy-paste error deden de restart handlers voor de slurmctld en slurmdbd een reload i.p.v. restart...


This problem also affects FMOD 1.x Unity integration.


niepotrzebne ? to wywal


Diana
Rika
Nini
Rini


nama teman wanita


Not Orders.getContents, but OrdersWriter.getContents


This is perfect for any work based on the LXX. Can't wait to finish mine.


nazywaj to jakoś z sensem co to za lista ? co ona przechowuje ? jakie książki ? wyszukane na podstawie czego ?


Successfully aliased the URL <https://what-next-h6v20ew6n.now.sh> to the following aliases.

* https://what-next.samtgarson1.now.sh
* https://what-next-git-master.samtgarson1.now.sh


The original PR changed `M-\` (`delete-horizontal-space`) to `cycle-spacing` in the `better-defaults` layer.

But since `M-SPC` calls `just-one-space` by default in Emacs.  We thought that it might be better to extend `M-SPC` by calling `cycle-spacing` instead. It's original behavior doesn't change the first time it's pressed.


pretty much.
but this whole gem is pretty much broken.
so ignore this.


Таким образом: java -cp MyJUnit.jar;math.jar Runner <число потоков> [MyMathTests]+


Checkmarx scan results 10 May 2019 17:17 UTC +08:00

High
Medium
Low
Info

New
13
143
370
0

Recurrent
0
0
0
0

Fixed
0
0
0
0

 Open Viewer
Included commits

Commit ID	Owner

0f679a00e2140442b1812cbad1bc4dbae8b8ff0f	@web-flow


opis


FYI; the typo `caluclate` has survived from `ncrack_smb.cc`.


private static final


popraw formatowanie


Successfully aliased the URL <https://hello-next-9tx5fp8y6.now.sh> to the following aliases.

* https://hello-next.vc121356.now.sh
* https://hello-next-git-master.vc121356.now.sh


Лучше назвать `show_stations`


a jak przedłużył ? trzeba pomyśleć o tej opcji


tylko amount zapisujesz ?


Successfully aliased the URL <https://demo-65kirpjnn.now.sh> to the following aliases.

* https://demo.lindingxuan.now.sh
* https://demo-git-master.lindingxuan.now.sh


@sethhillbrand is this the right date for 16.04? April 2019 is the end of support for 14.04 LTS, 16.04 LTS doesn't reach end of support until 2021.

https://wiki.ubuntu.com/Releases


swoją droga to jest robota dla serwisu przy zwrocie książki -> BookReturnService


Test용 넌센스문제 업데이트


akurat metoda z Payment może być zawarta w PaymentService aby było ładnie i poukładane


Все методы, кроме run должны быть private, т.к они не должны вызываться извне


descent


Ok, then you're not reusing the child process? In my experience, spawning a process is really expensive on macOS and Windows (interestingly not on Linux). It roughly takes 0.5s (depending on your hardware of course). You should consider to recycle the child process.


dalej nie wiem co ma robić ta metoda


a rok przestępny ?


а зачем тут в аргументах передается dealer если он не используется?


Lesson 13


do parametrów wyciągać


Seems like this drawable is missing, was this intentional?


`Remove the 2`


i jak już nie chce Ci się robić nowych testów dla każdego query - co byłoby zalecane to przynajmniej to jakoś opisz w komentarzu. Dla każdego query powinny być 3 przypadki:
- zgadza się i wyświetla rezultat
- brak takiego przypadku
- 2 takie przypadki co się zgadzają dla 2 różnych użytkowników


do parametru


Создается один маршрут за раз, поэтому метод лучше назвать `create_route`


czemu save'ujesz usera wyciągniętego z bazy ?


reta


So much easier ;) not sure why didn't I think to make it that way. Anyway. Best regards. Gracie


upsi sorry


Maybe we need some generic method to get new outputs/inputs on `Block`?


So maybe add a comment ss ot sounds like a special case.


wyciągnij z bazy i sprawdź czy się zgadza, a nie porównujesz dwa obiekty co stworzyłeś i zapisałeś, na dobrą sprawę w tym teście nie wykorzystujesz bazy.


* jest zła :P


This is not needed any more. I've changed the dependency to hdf5@1.10 on master as it is the version officially required by HAL and I have checked that it works locally


We have not yet introduced some of those user guides and docs as they were fairly outdated.
Feel free to open an issue with kube-prometheus about what user guides you would like to see return.


Will need to Delete this i have created a new Update function using the Patch request method works better for for validation


parametryzuj i skoro książka ma tytuł wiedźmin to to pokaż w teście - w tym momencie muszę się domyślać. Po za tym jak zmienisz w utilsie to ten test padnie. book.setTitle("wiedzmin");


to napraw


This test is actually about special regex characters, not long prefix


I really need this in my own project 🎉


może dodaj, aby tytuł książki testowej był = nazwatestu + godzina i minuta


Successfully aliased the URL <https://hellonow-49y9j0rnd.now.sh> to the following aliases.

* https://hello-now.oscarryz.now.sh
* https://hello-now-git-master.oscarryz.now.sh


ale w parametrze abyś tylko wpisywał nazwę testu -> czas miałby sam się dodać.


DeepCode analyzed this commit.
There are 1 new warning and 1 new info report.

[Click](https://www.deepcode.ai/app/gh/embark-framework/embark/84439cb6fe176c02b8df649894aaa7cf6ab95b46/embark-framework/embark/e154b8661f6d5eff964163aba7594f1d0bf37f16/_/%2F/code/) to see more details.


DeepCode analyzed this commit.
There is 1 new info report.

[Click](https://www.deepcode.ai/app/gh/embark-framework/embark/fd09488e4be2f4dbecf2cd3b11611f5e14fd75ca/embark-framework/embark/a22d8fc6c456f7a5c76c5b1a51e6a1f56e2b629e/_/%2F/code/) to see more details.


Помести все константы в модуль, например `InterfaceConstants`
Файл переименуй на `interface_constants.rb`
В Main можно обращаться к константам так `InterfaceConstants::DIVIDER`
Или подключи их в класс. Тогда внутри класса можно обращаться просто по имени константы(DIVIDER)

```
class Main
  include InterfaceConstants

  ...
  puts DIVIDER
end
```


assertTrue / assertFalse


Successfully aliased the URL <https://task-mdb-ifjjhjife.now.sh> to the following aliases.

* https://task-mdb.cezary-walczak.now.sh
* https://task-mdb-git-master.cezary-walczak.now.sh


Successfully aliased the URL <https://hellonow-kqwo8e0ur.now.sh> to the following aliases.

* https://hello-now.oscarryz.now.sh
* https://hello-now-git-master.oscarryz.now.sh


Successfully aliased the URL <https://www-5xzykxh5v.now.sh> to the following aliases.

* https://www.proux.net
* https://www.proux.de
* https://www.proux.now.sh
* https://www-git-master.proux.now.sh


parametr i tak jak mówiłem 3 przypadki testu query


Jest lepiej :)


Successfully aliased the URL <https://shuding-1g0pibnhi.now.sh> to the following aliases.

* https://shud.in
* https://shuding.shuding1.now.sh
* https://shuding-git-master.shuding1.now.sh


Лучше просто `@number` назвать


Remove the first `now`?


Successfully aliased the URL <https://what-next-rdzhyq0mj.now.sh> to the following aliases.

* https://what-next.samtgarson1.now.sh
* https://what-next-git-master.samtgarson1.now.sh


Successfully aliased the URL <https://alpaca-ui-cs6eoi2ge.now.sh> to the following aliases.

* https://alpaca-ui.now.sh
* https://alpaca-ui.snowdog1.now.sh
* https://alpaca-ui-git-develop.snowdog1.now.sh


I think this should be ++index and not --index here?


Why is this not optional? We want to disable this