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/0pdd20190413-4-cmcjhd/pchmielowski/dotfiles && pdd -v -f /tmp/20190413-12522-1gb6jit [1]: bash: warning: setlocale: LC_ALL: cannot change locale (UTF-8) + set -e + set -o pipefail + cd /tmp/0pdd20190413-4-cmcjhd/pchmielowski/dotfiles + pdd -v -f...

Please, copy and paste this stack trace to GitHub:

```
UserError
set -x && set -e && set -o pipefail && cd /tmp/0pdd20190413-4-cmcjhd/pchmielowski/dotfiles && pdd -v -f /tmp/20190413-12522-1gb6jit [1]:
bash: warning: setlocale: LC_ALL: cannot change locale (UTF-8)
+ set -e
+ set -o pipefail
+ cd /tmp/0pdd20190413-4-cmcjhd/pchmielowski/dotfiles
+ pdd -v -f /tmp/20190413-12522-1gb6jit

My version is 0.20.4
Ruby version is 2.6.0 at x86_64-linux
Reading /tmp/0pdd20190413-4-cmcjhd/pchmielowski/dotfiles
11 file(s) found, 67 excluded
Reading .gitignore...
Reading .zshrc...
ERROR: .zshrc; puzzle at line #161; 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'
```


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/0pdd20190413-4-cmcjhd/pchmielowski/dotfiles && pdd -v -f /tmp/20190413-12655-13cp4n6 [1]: bash: warning: setlocale: LC_ALL: cannot change locale (UTF-8) + set -e + set -o pipefail + cd /tmp/0pdd20190413-4-cmcjhd/pchmielowski/dotfiles + pdd -v -f...

Please, copy and paste this stack trace to GitHub:

```
UserError
set -x && set -e && set -o pipefail && cd /tmp/0pdd20190413-4-cmcjhd/pchmielowski/dotfiles && pdd -v -f /tmp/20190413-12655-13cp4n6 [1]:
bash: warning: setlocale: LC_ALL: cannot change locale (UTF-8)
+ set -e
+ set -o pipefail
+ cd /tmp/0pdd20190413-4-cmcjhd/pchmielowski/dotfiles
+ pdd -v -f /tmp/20190413-12655-13cp4n6

My version is 0.20.4
Ruby version is 2.6.0 at x86_64-linux
Reading /tmp/0pdd20190413-4-cmcjhd/pchmielowski/dotfiles
10 file(s) found, 73 excluded
Reading .gitignore...
Reading .zshrc...
ERROR: .zshrc; puzzle at line #161; 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'
```


How much can CELL_EMAIL_BCON hold? (string length)


I probably meant owner then, feel free to change it


Successfully aliased the URL <https://legesher-cqtmw0d44.now.sh> to the following alias.

* https://legesher.now.sh


в данном случае лучше сделать через if, тогда можно избавится от неочевидного флага в методе. Т.е. проверить права и на основе них вызывать метод showAllCommands


Also merges #55


Sam ich znalazłem :smile:.


этот класс используется один для всех? или для каждого клиента создается свой объект?


![](https://github.trello.services/images/mini-trello-icon.png) [GitHub](https://trello.com/c/d5toC1Uq/5-github)


I’ll try that next. Need to finish income tax.


C++ std::wstring is just too expensive. It its short-string optimization is just 2, meaning that every string of length > 2 requires a heap allocation. A COW value-type string seems right to me: less error prone, cheap to copy, with reasonable performance.

A reasonable roadmap:

1. Create an API-compatible wrapper around `std::wstring`. Change `wcstring` from the typedef to this new wrapping type.
2. Modify the API to fix the COW-unfriendly bits, in particular mutable `operator[]` and `at()`. There should be a separate function for modifying the string, `mut_at()` or something.
3. Switch to a COW implementation under the hood, probably using `shared_ptr`.
4. Long-term make the implementation polymorphic (ASCII strings, constant strings, etc).

Anyways step 1-3 should go a long way to reduce our memory usage and make this stuff less error prone.


A jest to możliwe? Bo ja nic tam takiego dobrego do zablokowania nie zauważyłem.


Now could not deploy this pull request since the `now.json` file does not contain valid JSON.

	Click here to see the contents of `now.json`

{
  "version": 2,
  "name": "outfoxis",
    "builds": [
      { "src": "./public/**", "use": "@now/static" }
    ],
    "routes": [
      { "src": "/(.*)", "dest": "public/$1" }
    ]
}
I

For more information on now.json visit https://zeit.co/docs/features/configuration#now.json.


Successfully aliased the URL <https://100daysofsketches-ghuhkpniio.now.sh> to the following alias.

* https://100daysofsketches.com


@hawkeye116477 sprytnie `z-index` ukrył widoczność ale stopka już była niżej.


![](https://github.trello.services/images/mini-trello-icon.png) [fix JdbcConnector](https://trello.com/c/ntorqVhh/64-fix-jdbcconnector)


April 13th

Starting today, I will be starting and finishing the snake game on Qt.


v.0.1.1 is different from v.0.1.0 in that it correctly changes User instance data in ChangeNameDialogFragment rather than changing a static variable in its host activity. There has also been some code cleanup/refactoring to remove extraneous code. Modified classes have had their dates changed to 4/13/19.


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/0pdd20190413-4-cmcjhd/pchmielowski/dotfiles && pdd -v -f /tmp/20190413-12866-z9oe2y [1]: bash: warning: setlocale: LC_ALL: cannot change locale (UTF-8) + set -e + set -o pipefail + cd /tmp/0pdd20190413-4-cmcjhd/pchmielowski/dotfiles + pdd -v -f...

Please, copy and paste this stack trace to GitHub:

```
UserError
set -x && set -e && set -o pipefail && cd /tmp/0pdd20190413-4-cmcjhd/pchmielowski/dotfiles && pdd -v -f /tmp/20190413-12866-z9oe2y [1]:
bash: warning: setlocale: LC_ALL: cannot change locale (UTF-8)
+ set -e
+ set -o pipefail
+ cd /tmp/0pdd20190413-4-cmcjhd/pchmielowski/dotfiles
+ pdd -v -f /tmp/20190413-12866-z9oe2y

My version is 0.20.4
Ruby version is 2.6.0 at x86_64-linux
Reading /tmp/0pdd20190413-4-cmcjhd/pchmielowski/dotfiles
10 file(s) found, 82 excluded
Reading .gitignore...
Reading .zshrc...
ERROR: .zshrc; puzzle at line #161; 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'
```


This is the instruction book~~


How can you see this ? I only see 1 crash but don't know the reason. Perhaps I should limit one more the loops ...


Materials is lagging sometimes (as seen on (x, y, z) = (29, 1, 5) in the starting dungeon)


![](https://github.trello.services/images/mini-trello-icon.png) [ACC java model](https://trello.com/c/xXtA0OZG/61-acc-java-model)


`validate_presence(var_value, _option)`


```
method_name = "validate_#{rule[:validation_type]}"
send(method_name, var_value, rule[:option])
```


Good catch! I have changed the condition in the next commit.


I am sorry, but I don know How I could have changed this file. I never intended it. Agai, I have to conclude GIT is too difficult for me.


Add a method which will allow additional functions/methods to be run once every Tick, something like addOnTick and will be run here


moved this file from data to see if creation date remained


See also https://github.com/kubernetes/kubernetes/issues/76231


@bgoodri @avehtari sorry I’m late to this but we can we call this argument `approx_draws` instead of `draws`, since it doesn’t apply to mcmc? Or at least some name that is more clear than `draws.

Also shouldn’t this argument also allow specifying the number of draws when using VB? (Maybe that’s what Aki already did in his other PR)


С конца парсим выражение считываем число пока не знак. первый символ всегда знак


Certyfikat chyba im wygasł, Vivaldi ostrzega.


Look here, the other patch's stats:

http://tests.stockfishchess.org/tests/view/5cb0ded10ebc5925cf013866

user named mlang is showing a crash too


Используй массив для каждого поля, а не хеш для всех полей
В историю нужно помещать не текущее значение, которое присваиваем переменной, а только старое значение. Т.е. в первый раз история пустая (пустой массив), присвоили новое значение, старое перешло в историю, новое - это текущее значение переменной.


The same: 99


*uploaded


I intentionally made it internal, so that I would be able to use it in kill function of the Stoppable contract.


Czyli wywalamy o raz dziennie sprawdzamy czy wygasła domena lub kupili certyfikat na dalszą "pracę"?


Może da się to do playgrounda wrzucić czy domeny są tylko po https i czy certyfikat ważny.


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

* https://critresult.com
* https://website-git-master.critresult.now.sh
* https://critrace.com


@djc , thanks but this is already in your master branch, I pinched it from there.  I'm using quinn for a client/server project and I'm using the 0.2.0 release available on crates.io.   I found an issue on the client side (embedded ARM device) and I found this fixed it..


One last thing:
Asegurarse que quede centrado en todos los dispositivos
![Capture](https://user-images.githubusercontent.com/14225515/56085018-3d208e00-5e02-11e9-85c7-7e3c6a672911.PNG)


just... why.


Flying birdy


Do you think ASI2 Capture is exist or just kanged something?


The cause of the crash is not tallied in those stats. I just managed to catch the cutechess message on my end.


Well I thought if it would be possible to modify owner if it is public, then the same thing would apply to funds (e.g. someone would make an entry for his account).
Am I wrong?


Stolen from Stackoverflow:

“The reason that entropy is important is to avoid clustering of salt values. If the salt is based on username and you know that most systems will have an account named either "root" or "admin", then you can make a rainbow table for those two salts and it will crack most systems. If, on the other hand, a random 16-bit salt is used and the random values have roughly even distribution, then you need a rainbow table for all 2^16 possible salts.” -https://stackoverflow.com/questions/536584/non-random-salt-for-password-hashes

So avoid sequences or username as salt.

Random ensures good distribution of salts.

And if you’re going to use Random...

...might as well use the best Random since it’s available.

Aloha,
--
Jim Manico
@Manicode

> On Apr 13, 2019, at 9:03 AM, Jim Manico <jim@manicode.com> wrote:
>
> Well a counter would be a poor salt. The first value, 1, is small and would likely fall into potential dictionary or precomputed rainbow table space. Salts need to be •large• enough to support your user base and large enough to make sure rainbow tables are not possible - which they are for small salts. And yes, salts need to be unique for each credential.
>
> But I think you’re right. As long as the salt is large (128+ bits?) and unique, it should be enough. Let me dig into this a bit more before we change anything. I’ll be back.
>
> --
> Jim Manico
> @Manicode
> Secure Coding Education
> +1 (808) 652-3805
>
>> On Apr 13, 2019, at 8:34 AM, portilha <notifications@github.com> wrote:
>>
>> Hi Jim, thank you, but why it is weakness at all? That's what I don't
>> understand yet, why we should use the SecureRandom instead of Random?, just
>> because it is a true random?, what are the benefits in terms of security
>> that it brings to the salting of hashing passwords? Will it take more time
>> to generate a Rainbow table to crack the password (random vs securerandom),
>> the salt is visible in the finished hash so that shouldn't be the reason.
>> So, what are the benefits? We could use a counter to generate the salt with
>> the same security strength as SecureRandom.
>>
>> Jim Manico <notifications@github.com> escreveu no dia sábado, 13/04/2019
>> à(s) 16:49:
>>
>> > I would flag it as a “weakness” not a major vuln. It’s a low level issue
>> > at best, but you might as well use the more secure random generator since
>> > it’s available natively in Java.
>> >
>> > --
>> > Jim Manico
>> > @Manicode
>> > Secure Coding Education
>> > +1 (808) 652-3805
>> >
>> > > On Apr 13, 2019, at 1:01 AM, portilha <notifications@github.com> wrote:
>> > >
>> > > The only reason I am asking is, should the use of normal Random to
>> > generate
>> > > Salt be considered insecure?, In my point of view right now is not.
>> > > Performance is not a concern, if we have code that works with Random for
>> > > the Salt, should we change it to SecureRandom? (this is what I am trying
>> > to
>> > > understand).
>> > >
>> > > Thank you
>> > >
>> > > -- Pedro
>> > >
>> > > Jim Manico <notifications@github.com> escreveu no dia sábado, 13/04/2019
>> > > à(s) 04:30:
>> > >
>> > > > Can you explain to me why you would NOT want to use SecureRandom? Is
>> > > > there a performance or other concern?
>> > > >
>> > > > - Jim
>> > > >
>> > > > > Thank for taking the time to answer, i understand the need for
>> > > > uniqueness,
>> > > > > but i dont see the need for True randomness. Can you explain why we
>> > need
>> > > > > True random?.. Once again Thank you.
>> > > > >
>> > > > > A sexta, 12/04/2019, 22:24, Jim Manico <notifications@github.com>
>> > > > > escreveu:
>> > > > >
>> > > > > > More important than random is UNIQUE since salts are meant for
>> > > > > > de-duplication purposes only. But in general java.url.Random is not
>> > > > > Random
>> > > > > > in Java but sequential once you learn the seed. SecureRandom is
>> > > > > closer to
>> > > > > > true random.
>> > > > > >
>> > > > > > --
>> > > > > > Jim Manico
>> > > > > > @Manicode
>> > > > > > Secure Coding Education
>> > > > > > +1 (808) 652-3805
>> > > > > >
>> > > > > > > On Apr 12, 2019, at 10:59 AM, portilha <notifications@github.com
>> > >
>> > > > > wrote:
>> > > > > > >
>> > > > > > > Hi righettod, I'm a student in security and I don't understand
>> > why
>> > > > you
>> > > > > > need a strong credential-specific salt like SecureRandom, can you
>> > > > > explain
>> > > > > > me why you new something like SecureRandom and why Random is not
>> > > > enough.
>> > > > > > Thank you, Pedro
>> > > > > > >
>> > > > > > > —
>> > > > > > > You are receiving this because you are subscribed to this thread.
>> > > > > > > Reply to this email directly, view it on GitHub, or mute the
>> > thread.
>> > > > > >
>> > > > > > —
>> > > > > > You are receiving this because you commented.
>> > > > > > Reply to this email directly, view it on GitHub
>> > > > > >
>> > > > > <
>> > > >
>> > https://github.com/OWASP/CheatSheetSeries/commit/f7e6532fd65021725ccad47f5b897b0be98fa5cf#commitcomment-33163415
>> > > > >,
>> > > > > > or mute the thread
>> > > > > >
>> > > > > <
>> > > >
>> > https://github.com/notifications/unsubscribe-auth/ABvJbT8oSI_dXXpgzuUNiAqNqePz2Mnmks5vgPmYgaJpZM4ctPZg
>> > > > >
>> > > > > > .
>> > > > > >
>> > > > >
>> > > > > —
>> > > > > You are receiving this because you commented.
>> > > > > Reply to this email directly, view it on GitHub
>> > > > > <
>> > > >
>> > https://github.com/OWASP/CheatSheetSeries/commit/f7e6532fd65021725ccad47f5b897b0be98fa5cf#commitcomment-33165158
>> > > > >,
>> > > > > or mute the thread
>> > > > > <
>> > > >
>> > https://github.com/notifications/unsubscribe-auth/AAgcCVUrIhYndo33xbdrT69tfNG1tAQ7ks5vgTangaJpZM4ctPZg
>> > > > >.
>> > > > >
>> > > > --
>> > > > Jim Manico
>> > > > Manicode Security
>> > > > https://www.manicode.com
>> > > >
>> > > > —
>> > > > You are receiving this because you commented.
>> > > > Reply to this email directly, view it on GitHub
>> > > > <
>> > https://github.com/OWASP/CheatSheetSeries/commit/f7e6532fd65021725ccad47f5b897b0be98fa5cf#commitcomment-33165381
>> > >,
>> > > > or mute the thread
>> > > > <
>> > https://github.com/notifications/unsubscribe-auth/ABvJbeEW9gSPeSXP70421RE44qa45pgHks5vgU87gaJpZM4ctPZg
>> > >
>> > > > .
>> > > >
>> > >
>> > >
>> > > --
>> > > Cumprimentos,
>> > >
>> > > Pedro Portilha
>> > > —
>> > > You are receiving this because you commented.
>> > > Reply to this email directly, view it on GitHub, or mute the thread.
>> >
>> > —
>> > You are receiving this because you commented.
>> > Reply to this email directly, view it on GitHub
>> > <https://github.com/OWASP/CheatSheetSeries/commit/f7e6532fd65021725ccad47f5b897b0be98fa5cf#commitcomment-33167585>,
>> > or mute the thread
>> > <https://github.com/notifications/unsubscribe-auth/ABvJbdz-zs9rsOmqC9D2TLgkdFimMY0oks5vgfyDgaJpZM4ctPZg>
>> > .
>> >
>>
>>
>> --
>> Cumprimentos,
>>
>> Pedro Portilha
>> —
>> You are receiving this because you commented.
>> Reply to this email directly, view it on GitHub, or mute the thread.


@baarsrj You didn't, no worries. It just shows that you have not "rebased" before pushing, or someone as added a commit between your pull command and your push of your changes.
It you want to avoid this kind "recap/merge" commits, you can check the 'rebase' and the 'only fast-forward' options in your IDE/git GUI, or if you are using the commandline do: `git pull --rebase` followed by `git push` each time you commit changes.


closes #10 and #11


Орфографических*


Hi!
I think your way to show how to create a react app is very good and clear.
So I have followed your video from 1-19 and then I got problem because the store enhancer (reactReduxFirebase) as you showed in the videos is not part of the v3 APIv3.0.0-alpha...
Is this possible for you to update your video and index.js & app,js ect with V3 API?


Fixes https://github.com/sahana/eden/issues/1498


The second argument of find method of std::string is the "first character in the string to be considered in the search"

[http://www.cplusplus.com/reference/string/string/find/](http://www.cplusplus.com/reference/string/string/find/)

The initialization or the re-initialization was intentional :
- With -O3 compiler optimization the does not initialize variable : the start seach can occurred anywhere.
or:
- The start search need to re-start at the beginning of the string.

I recommend to revert this change on vPreprocessor.cpp


Isn't that kind of silly to make such a check, every time someone calls this function. I think that users would more of waste their gas on that check than benefit from additional safety.
If someone would call it with his address then I guess that he would be the one to blame.


new functionalities added


Sin querer guarde la practica 10 de clase en el de casa, pero lo entregué en la fecha establecida.
:)


Successfully aliased the URL <https://styled-react-boilerplate-12qzgqf5o.now.sh> to the following aliases.

* https://styled-react-boilerplate.now.sh
* https://styled-react-boilerplate-git-master.akepinski.now.sh


Done https://github.com/xmrig/xmrig/commit/a3b303e885acbf79240c200e92659674a30720ec#diff-f629e4232ba9ee52032f9ef75224b9c6R171
First miner will try use `GET /getheight` and if `hash` field not available, will switch to `GET /getinfo`.


Może coś się da => `https://unix.stackexchange.com/a/234975`


Nice typo, idiot.


Added servo movement for searching


Successfully aliased the URL <https://state-matters-2gkmn6jwp.now.sh> to the following aliases.

* https://state-matters-git-master.state-matters.now.sh
* https://www.statematters.org


DeepCode analyzed this commit.
There are no new issues. 1 info report was fixed.

[Click](https://www.deepcode.ai/app/gh/michaelKurowski/lokim2/a0ddfd695efae99ec800a303eab5eeacd05f2922/michaelKurowski/lokim2/81b35bce0fb9bb6c331b61ab42d8ff083552fdbe/_/%2F/code/) to see more details.


DeepCode analyzed this commit.
There are no new issues. 1 info report was fixed.

[Click](https://www.deepcode.ai/app/gh/michaelKurowski/lokim2/a5694eea23f2e129360f9d433067e09bbaec7db6/michaelKurowski/lokim2/a0ddfd695efae99ec800a303eab5eeacd05f2922/_/%2F/code/) to see more details.


A "DNSy" wytrzymają podwojoną liczbę zapytań bez banów na CircleCI?


Its not true


![](https://github.trello.services/images/mini-trello-icon.png) [Create add/edit resume work experience section layout](https://trello.com/c/mZW1bo8B/60-create-add-edit-resume-work-experience-section-layout)


![](https://github.trello.services/images/mini-trello-icon.png) [Create add/edit resume education section layout](https://trello.com/c/r3zS2SRY/57-create-add-edit-resume-education-section-layout)


![](https://github.trello.services/images/mini-trello-icon.png) [Create add/edit resume languages section layout](https://trello.com/c/Bvin6t4j/66-create-add-edit-resume-languages-section-layout)


refact


![](https://github.trello.services/images/mini-trello-icon.png) [Create add/edit resume hobbies section layout](https://trello.com/c/TJIyZqbi/69-create-add-edit-resume-hobbies-section-layout)


OK, lets revert it. I was busy to fixing the windows build and making the cpp code to be interruptible (by using the https://cysignals.readthedocs.io/en/latest/ which somehow does not work with skbuild) so I did not noticed that there was an error.


![](https://github.trello.services/images/mini-trello-icon.png) [Create add/edit resume details section layout](https://trello.com/c/y6EPfEbO/73-create-add-edit-resume-details-section-layout)


![](https://github.trello.services/images/mini-trello-icon.png) [Create add/edit resume skills section layout](https://trello.com/c/4vjubhSA/63-create-add-edit-resume-skills-section-layout)


![](https://github.trello.services/images/mini-trello-icon.png) [Create add resume screen logic](https://trello.com/c/2uUEOAb2/24-create-add-resume-screen-logic)


Successfully aliased the URL <https://website-9eraxdojt.now.sh> to the following aliases.

* https://critresult.com
* https://website-git-master.critresult.now.sh
* https://critrace.com


ここがsidebarを直したところ
具体的にはhoverしたときの色をふんわり白色に変えた


![](https://github.trello.services/images/mini-trello-icon.png) [Create add/edit resume skills section logic](https://trello.com/c/9ZLx00KX/64-create-add-edit-resume-skills-section-logic)


![](https://github.trello.services/images/mini-trello-icon.png) [Create add/edit resume work experience section logic](https://trello.com/c/lZvv8Loz/61-create-add-edit-resume-work-experience-section-logic)


It is more a comment on gas saving for such a simple operation.


![](https://github.trello.services/images/mini-trello-icon.png) [Create add/edit resume languages section logic](https://trello.com/c/QFkZlqQi/67-create-add-edit-resume-languages-section-logic)


![](https://github.trello.services/images/mini-trello-icon.png) [Create add/edit resume hobbies section logic](https://trello.com/c/Kbh9AhCO/70-create-add-edit-resume-hobbies-section-logic)


![](https://github.trello.services/images/mini-trello-icon.png) [Create add/edit resume details section logic](https://trello.com/c/zW8p3Bt6/72-create-add-edit-resume-details-section-logic)


![](https://github.trello.services/images/mini-trello-icon.png) [Create add/edit resume education section logic](https://trello.com/c/WcHD2E0s/58-create-add-edit-resume-education-section-logic)


@mkhorton This update is causing tests to fail with a segmentation fault. Pls look into it.


![](https://github.trello.services/images/mini-trello-icon.png) [Create resume screen logic](https://trello.com/c/0aTpAKUj/20-create-resume-screen-logic)


A nie wiem. Podwojoną? Znaczy chcesz sprawdzać razem z wygasłymi. Zawsze można certyfikaty innego dnia sprawdzać. Ale lepszy do tego raczej będzie GitLab CI, bo można parę list na raz robić, a w Circle za darmo są tylko 4 kontenery.


nice


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

* https://critresult.com
* https://website-git-master.critresult.now.sh
* https://critrace.com


Because it is an unsigned int, `uint`, it cannot be `< 0`.
Funny business should be caught, but you should also assume that some scatterbrained users are going to make honest mistakes. These need not be punished.

```solidity
function deposit() payable {
    require(msg.value > 0); // It is a deposit function my friend!
    assert(this.balance >= msg.value); // Whaaat? of course this is always true.
}

function withdraw() {
    uint toSend = balances[msg.sender];
    require(toSend > 0); // Why withdraw if there is nothing my friend?
    balances[msg.sender] = 0;
    msg.sender.transfer(toSend);
    assert(balances[msg.sender] == 0); // Why would this ever be false??
}
```


![](https://github.trello.services/images/mini-trello-icon.png) [RunBrain_STT warmup](https://trello.com/c/UMaNykFk/20-runbrainstt-warmup)


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):
~~~


RA rate changes depending on declination


Yes, wishful thinking when it comes to balances, but a practice to learn now.


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

* https://critresult.com
* https://website-git-master.critresult.now.sh
* https://critrace.com


Also make alice more prominent. This account is not like the 2 others. `members[0]` is not as explicit as `aliceTheBoss`.


I notice that later indeed.
I will correct your "The EOA who deployed the contract...". Not EOA but the account who...
A contract can deploy another contract.


Upstream is also good. I think for most of the users WAN is clearer than upstream, but I'm fine with both :)


@rddim
please specify, if possible with a screenshot, thanks


So the contract can accumulate Ether for its own benefit? And the Ethers that enter this function are never to be withdrawn? Money pit?


My point is, if the member is not enrolled, how would this member have any balance? Only the balance check is relevant.


This looks great, brief and concise. I would probably just change a few things here and there.

"Use the Zowe Desktop personalization panel to open the Languages setting, which allows you to change the desktop language. After selecting a language and restarting the desktop, menus and other texts will display in the newly specified language. Applications will also translate, assuming that translations exist for that particular application."


![](https://github.trello.services/images/mini-trello-icon.png) [Rewrite complète (v2)](https://trello.com/c/Qg4RWbBp/15-rewrite-compl%C3%A8te-v2)


![Логика бота](https://user-images.githubusercontent.com/49037254/56085339-00788500-5e4a-11e9-9a0b-bd13e8d160df.jpg)


hay


s


1. Click the Settings & Personalization icon in the app tray, in the bottom right corner of the desktop.
2. Select **Languages**.
3. In the **Languages** menu, select a language, and click **Apply**.
4. Follow the prompt to restart the desktop so your changes take effect.


I like bananas


Uncertain what this code was supposed to do but it throws an eo error:

`ERR<13713>:eo lib/edje/edje_object.eo.c:102 edje_obj_signal_emit() Eo ID 0x560b71692fd0 is not a valid object. Current thread: main. This ID has probably been deleted or this was never a valid object ID. (domain=2, current_domain=0, local_domain=0, available_domains=[0 1    ], generation=3d0, id=a4b, ref=1)`


Good work :)


Why just delete readme?


This means your child contract like the Splitter can do `owner = msg.sender`. Are you comfortable with that?


Same here.


`require(isPaused, "The contract must be paused to perform this action.");` is enough.


`require(!isPaused, "The contract is paused at the moment. Please contact the administrator.");` is enough.


There is (at least) a "who cares?" level of this concern and an "on the merits" level. I'm going to try to argue this case on the merits.

What governs the version numbers of a shared library? [Changes to the ABI.](https://akkadia.org/drepper/dsohowto.pdf#page=35) When does an ABI change? Not when *any* function changes prototypes or *any* incompatible change is introduced. Only when the "contract" the ABI represents (however abstract) is altered, which includes any prototype change or addition in the "public" functions.

What is FontForge's ABI? As those who keep complaining about the multitude of separate shared libraries keep pointing out, FontForge doesn't really have an ABI. There's no "customer", nor is there any documented library interface beyond some ancient remnants from GW days and the code itself. The build makes shared objects partly out of inertia (which explains the number of them) and partly because there are two places the code needs to link into: the executable and the python modules.

Any distro with a concern can therefore be accurately informed of the following: All the changes to the shared libraries relate to private intra-FontForge contracts, not the (null) public interface, and accordingly the project didn't bump the version number.


self-destruct transforms the address into a money pit. Perhaps it is better to brick it so that users who did not get the memo don't send more money.


![](https://github.trello.services/images/mini-trello-icon.png) [Raspberry Si7021 sensor driver](https://trello.com/c/eKkh3eUP/17-raspberry-si7021-sensor-driver)


This can go into its own file.


Whoa @charlierudolph - this is very exciting!!

I'm on easter holiday for 10 days or so - will get back to you when I have a chance to review this.


I would put those over 2 lines for clarity.


Updating storage, `SSTORE` is the most expensive operation. Now that you can start optimising, it would be good if you `SSTORE` only when necessary. The `if(remaining > 0) {` was good in this regard.


An important state change like that warrants its own event.


```py
#FIXME: Do not make commits while sleepy
```


Hmm, ok, will take a look. They were passing locally.


You set both beneficiaries in 1 go. Before that the contract is not ready. Why do you deploy a contract that is not ready.
What you should do is that these 2 addresses are part of the constructor. As long as you don't know who those 2 addresses will be, you do not deploy the contract.
That will remove some complexity from your strict contract.


Hi Jim, thank you for taking the time to answer, but don't you think
that is wrong saying that using Random is a weakness, because the
values for salt for me are equality valid even if they are not true
random. I agree with what you said, that the salt should be big and
unique so that even if the user password is weak the hash generated
will be hard to crack.

If the database is comprised and the db table is accessible to the
attacker he will be able to see the salt and generate a rainbow table
to crack the passwords.

I only disagree with the statement "...might as well use the best
Random since it’s available." being the reason to say that it makes
the hash more secure.

SecureRandom should be used and recommended for cases like SessionIDs
because of predictability, "The general thought seems to be that
entropy is important so that the salt will be difficult for an
attacker to guess. This is incorrect and, in fact, completely
irrelevant. " -
https://stackoverflow.com/questions/536584/non-random-salt-for-password-hashes

But thank you for your answer :)

Jim Manico <notifications@github.com> escreveu no dia sábado,
13/04/2019 à(s) 21:46:
>
> Stolen from Stackoverflow:
>
> “The reason that entropy is important is to avoid clustering of salt values. If the salt is based on username and you know that most systems will have an account named either "root" or "admin", then you can make a rainbow table for those two salts and it will crack most systems. If, on the other hand, a random 16-bit salt is used and the random values have roughly even distribution, then you need a rainbow table for all 2^16 possible salts.” -https://stackoverflow.com/questions/536584/non-random-salt-for-password-hashes
>
> So avoid sequences or username as salt.
>
> Random ensures good distribution of salts.
>
> And if you’re going to use Random...
>
> ...might as well use the best Random since it’s available.
>
> Aloha,
> --
> Jim Manico
> @Manicode
>
> > On Apr 13, 2019, at 9:03 AM, Jim Manico <jim@manicode.com> wrote:
> >
> > Well a counter would be a poor salt. The first value, 1, is small and would likely fall into potential dictionary or precomputed rainbow table space. Salts need to be •large• enough to support your user base and large enough to make sure rainbow tables are not possible - which they are for small salts. And yes, salts need to be unique for each credential.
> >
> > But I think you’re right. As long as the salt is large (128+ bits?) and unique, it should be enough. Let me dig into this a bit more before we change anything. I’ll be back.
> >
> > --
> > Jim Manico
> > @Manicode
> > Secure Coding Education
> > +1 (808) 652-3805
> >
> >> On Apr 13, 2019, at 8:34 AM, portilha <notifications@github.com> wrote:
> >>
> >> Hi Jim, thank you, but why it is weakness at all? That's what I don't
> >> understand yet, why we should use the SecureRandom instead of Random?, just
> >> because it is a true random?, what are the benefits in terms of security
> >> that it brings to the salting of hashing passwords? Will it take more time
> >> to generate a Rainbow table to crack the password (random vs securerandom),
> >> the salt is visible in the finished hash so that shouldn't be the reason.
> >> So, what are the benefits? We could use a counter to generate the salt with
> >> the same security strength as SecureRandom.
> >>
> >> Jim Manico <notifications@github.com> escreveu no dia sábado, 13/04/2019
> >> à(s) 16:49:
> >>
> >> > I would flag it as a “weakness” not a major vuln. It’s a low level issue
> >> > at best, but you might as well use the more secure random generator since
> >> > it’s available natively in Java.
> >> >
> >> > --
> >> > Jim Manico
> >> > @Manicode
> >> > Secure Coding Education
> >> > +1 (808) 652-3805
> >> >
> >> > > On Apr 13, 2019, at 1:01 AM, portilha <notifications@github.com> wrote:
> >> > >
> >> > > The only reason I am asking is, should the use of normal Random to
> >> > generate
> >> > > Salt be considered insecure?, In my point of view right now is not.
> >> > > Performance is not a concern, if we have code that works with Random for
> >> > > the Salt, should we change it to SecureRandom? (this is what I am trying
> >> > to
> >> > > understand).
> >> > >
> >> > > Thank you
> >> > >
> >> > > -- Pedro
> >> > >
> >> > > Jim Manico <notifications@github.com> escreveu no dia sábado, 13/04/2019
> >> > > à(s) 04:30:
> >> > >
> >> > > > Can you explain to me why you would NOT want to use SecureRandom? Is
> >> > > > there a performance or other concern?
> >> > > >
> >> > > > - Jim
> >> > > >
> >> > > > > Thank for taking the time to answer, i understand the need for
> >> > > > uniqueness,
> >> > > > > but i dont see the need for True randomness. Can you explain why we
> >> > need
> >> > > > > True random?.. Once again Thank you.
> >> > > > >
> >> > > > > A sexta, 12/04/2019, 22:24, Jim Manico <notifications@github.com>
> >> > > > > escreveu:
> >> > > > >
> >> > > > > > More important than random is UNIQUE since salts are meant for
> >> > > > > > de-duplication purposes only. But in general java.url.Random is not
> >> > > > > Random
> >> > > > > > in Java but sequential once you learn the seed. SecureRandom is
> >> > > > > closer to
> >> > > > > > true random.
> >> > > > > >
> >> > > > > > --
> >> > > > > > Jim Manico
> >> > > > > > @Manicode
> >> > > > > > Secure Coding Education
> >> > > > > > +1 (808) 652-3805
> >> > > > > >
> >> > > > > > > On Apr 12, 2019, at 10:59 AM, portilha <notifications@github.com
> >> > >
> >> > > > > wrote:
> >> > > > > > >
> >> > > > > > > Hi righettod, I'm a student in security and I don't understand
> >> > why
> >> > > > you
> >> > > > > > need a strong credential-specific salt like SecureRandom, can you
> >> > > > > explain
> >> > > > > > me why you new something like SecureRandom and why Random is not
> >> > > > enough.
> >> > > > > > Thank you, Pedro
> >> > > > > > >
> >> > > > > > > —
> >> > > > > > > You are receiving this because you are subscribed to this thread.
> >> > > > > > > Reply to this email directly, view it on GitHub, or mute the
> >> > thread.
> >> > > > > >
> >> > > > > > —
> >> > > > > > You are receiving this because you commented.
> >> > > > > > Reply to this email directly, view it on GitHub
> >> > > > > >
> >> > > > > <
> >> > > >
> >> > https://github.com/OWASP/CheatSheetSeries/commit/f7e6532fd65021725ccad47f5b897b0be98fa5cf#commitcomment-33163415
> >> > > > >,
> >> > > > > > or mute the thread
> >> > > > > >
> >> > > > > <
> >> > > >
> >> > https://github.com/notifications/unsubscribe-auth/ABvJbT8oSI_dXXpgzuUNiAqNqePz2Mnmks5vgPmYgaJpZM4ctPZg
> >> > > > >
> >> > > > > > .
> >> > > > > >
> >> > > > >
> >> > > > > —
> >> > > > > You are receiving this because you commented.
> >> > > > > Reply to this email directly, view it on GitHub
> >> > > > > <
> >> > > >
> >> > https://github.com/OWASP/CheatSheetSeries/commit/f7e6532fd65021725ccad47f5b897b0be98fa5cf#commitcomment-33165158
> >> > > > >,
> >> > > > > or mute the thread
> >> > > > > <
> >> > > >
> >> > https://github.com/notifications/unsubscribe-auth/AAgcCVUrIhYndo33xbdrT69tfNG1tAQ7ks5vgTangaJpZM4ctPZg
> >> > > > >.
> >> > > > >
> >> > > > --
> >> > > > Jim Manico
> >> > > > Manicode Security
> >> > > > https://www.manicode.com
> >> > > >
> >> > > > —
> >> > > > You are receiving this because you commented.
> >> > > > Reply to this email directly, view it on GitHub
> >> > > > <
> >> > https://github.com/OWASP/CheatSheetSeries/commit/f7e6532fd65021725ccad47f5b897b0be98fa5cf#commitcomment-33165381
> >> > >,
> >> > > > or mute the thread
> >> > > > <
> >> > https://github.com/notifications/unsubscribe-auth/ABvJbeEW9gSPeSXP70421RE44qa45pgHks5vgU87gaJpZM4ctPZg
> >> > >
> >> > > > .
> >> > > >
> >> > >
> >> > >
> >> > > --
> >> > > Cumprimentos,
> >> > >
> >> > > Pedro Portilha
> >> > > —
> >> > > You are receiving this because you commented.
> >> > > Reply to this email directly, view it on GitHub, or mute the thread.
> >> >
> >> > —
> >> > You are receiving this because you commented.
> >> > Reply to this email directly, view it on GitHub
> >> > <https://github.com/OWASP/CheatSheetSeries/commit/f7e6532fd65021725ccad47f5b897b0be98fa5cf#commitcomment-33167585>,
> >> > or mute the thread
> >> > <https://github.com/notifications/unsubscribe-auth/ABvJbdz-zs9rsOmqC9D2TLgkdFimMY0oks5vgfyDgaJpZM4ctPZg>
> >> > .
> >> >
> >>
> >>
> >> --
> >> Cumprimentos,
> >>
> >> Pedro Portilha
> >> —
> >> You are receiving this because you commented.
> >> Reply to this email directly, view it on GitHub, or mute the thread.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub, or mute the thread.

--
Cumprimentos,

Pedro Portilha


`const [ acc0, acc1... ] = accounts;` I think.


Contribute to #58


It is bad practice to reuse your unique deployed instance. It makes your different `it` tests dependent on each other.
Instead, deploy a new one in a `beforeEach`.


Yep for gogo too https://github.com/uber/prototool/blob/dev/internal/wkt/wkt.go


There is value in testing the presence of a `.deployed` and that it has been deployed with expected values. Nothing more.


Not directed to you, but whoever wrote that crazy stuff inside the memorymap. Can't it use a trampoline function there? I guess it used to be a short macro.


<img width="900" alt="state react" src="https://user-images.githubusercontent.com/185555/56085496-625fdb80-5e98-11e9-9a25-352d185dddb4.png">


This could go outside the `it` so that you do not repeat that in every `it`


Avoid `.toNumber`. Use `.toString(10)` instead.
Also use `assert.strictEqual(` instead.


Also you could increase legibility by using `async` / `await`.


^ I agree with this. As mentioned in the previous release, we've already gone through multiple releases without ever bumping the soversion, so I doubt they care much at this point.

It's also all the more reason I want to get rid of shared libraries in FontForge; there's no good reason for them, and are a leading cause of why the build takes so long. As noted, there will need to be some thought around how the python hooks are handled, but it's not an impossible problem to solve.


thanks to @humrochagf


It is common practice to capitalise event names.


Nunca iria atingir este ponto pois esta verificação está antes do else.


Do you know what happens when someone has omitted to add parameters in the function call?


Since you decided to make the constructor `payable`, who is entitled to the Ether sent at deployment?


<img width="900" alt="hyperdb types" src="https://user-images.githubusercontent.com/185555/56085540-19f4ed80-5e99-11e9-9903-1b711eadd0b9.png">


Änderung des Intervalls zum Messen der Werte


you call `getBalance` inside the function `getBalance`?


I have made most of the code changes requested following my first PR to the original repo. I did not, however, edit the README accordingly. I still need to of course fix the README as well as get `setup.py`, `requirements.txt`, `bundle.sh`, and `__init__.py` written and tested.


This contract can be DoS'ed. What if Carol is a contract or a wallet contract and it decides to revert? Would Bob get paid? The issue worsens with scale. Imagine 1,000 people expecting refunds and one bad actor can DoS everyone.

There are two patterns that will help keep everything safe:

Never talk to more than one stranger at a time. Whoever signed the transaction counts as one because it could be anyone. Therefore, the payable function is limited to receiving funds and doing some accounting. It's not possible to forward the funds in one move without breaking this rule and inviting all sorts of trouble. You'll need a separate withdraw function that knows how much money is owed to the msg.sender claiming it. The idea is to limit the damage a user can do strictly to their own concerns.

This is re-entrance vulnerable because the transfers are actually handing over flow control to the receiving contracts. Their callbacks will fire (if they are contracts) and this appoach is hoping that control will be returned as expected. What if the attacker has other ideas? The issue is that flow control might not come back right away and that could lead to a situation in which the money is sent and the accounting is not taken care of.

A solution to this problem is to do "optimistic" account first. Then try the transfer, and if necessary, revert the accounting. The transfer method will actually revert for you if something goes wrong. Keep the idea in mind for cases where a failed communication could result in a false response and/or you want processing to continue for some reason.


This comments?


<img width="900" alt="hyperdb types" src="https://user-images.githubusercontent.com/185555/56085553-4dd01300-5e99-11e9-8897-eb394f88cfd8.png">


Personally I don't see a need for more than one but I don't understand the worry over having any at all. It's a pretty established and mundane technology at this point, and makes sense for the split. Why not dump more or less everything into a single shared object and link it into two tiny shells? (Maybe that's what @jtanx has in mind ... )


How difficult do you think it is for someone to put a number in `aliceEther`?
Is it really what it means to "send money"?
When you send money to someone, is the number in the email subject that matters or something else?


I did the three images wrong because I forgot how HTML works oops. I will fix this later but not a priority


Is carol entitled to half of what you sent bob??


Everything looks good.
We need to go in and document the code for future updates.


<img width="900" alt="hyperdb types" src="https://user-images.githubusercontent.com/185555/56085569-ae5f5000-5e99-11e9-973d-f882de4e4b50.png">


This line is incorrect. In *nix, there is a convention to negate switches by specifying `--no-`, eg. `--no-shouldSetSpoSiteReadOnlyForMembers`. In this case `siteReadOnlyForMembers` would be true while it should be false.


![](https://github.trello.services/images/mini-trello-icon.png) [Registration test](https://trello.com/c/ItuiKDY3/1-registration-test)


Missing indenting


Created initial structure. Created window with button.


This is taken verbatim from the MS Graph docs. In the context of the CLI, it should be changed to `This command...`


naravno kod mene je  ProbnaAgencijaEntities1  i treba promeniti webcofig da bi radilo, mada će biti pravo čudo ako uspe ;)


More often than not, dynamic linking just causes more pain than it's worth. Perhaps a single shared library is ok, but what I was thinking of was to just statically link (in terms of all internal code) the executable, and do the same for the pyhook. Sure, you end up with some duplication because of that, but I think that's fine.

If I did do that though, what I would like to avoid (if possible) is more than one dll for the pyhook. I'm thinking some sort of (Python) wrapper to the dll, so you have say `fontforge.py` and `psMat.py` that then internally link to the single dll. Not exactly sure how that will pan out though.

If not that, then yeah the single shared dll is always an option.


Listing sort function implemented; distance and rating.


Did you leave your personal client_id hardcoded in here?


Spr:
- brak schematu blokowego dla szukania ścieżki
- równoległościanu używamy tylko do uwidocznienia operacji wejścia/wyjścia
- pętla powinna być rozpisana na inicjalizację, sprawdzenie warunku (do tego używamy rombu), inkrementację
- nie wiem jak interpretować złożoność O(n,m)
- nie jestem przekonany, że podobieństwo powyżej 40% i niewielki procent przerw świadczą jednoznacznie o braku powiązania ewolucyjnego sekwencji...


beautiful


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

[Click](https://www.deepcode.ai/app/gh/michaelKurowski/lokim2/afd16e438ad2f32c5d7ecff225b7828bf90f5e2c/michaelKurowski/lokim2/c1ca2099609924eff751f6663247d66d51d1bbf3/_/%2F/code/) to see more details.


Nope, it’s taken from the python version of the unofficial rh lib


Thanks for fixing this Pantelis. It has been too long since I checked the GitHub notification.


Part of me wants to make a caching case for shared libraries, but we live in the docker age of totally separate stacks all the way down and I'd just come across as the old fogey I am.


Zadania z linii 27-39 mozna wykonac przed petla.


re "It's not entirely clear when this situation happens"

just having a difficult time imagining how the empty stable case could come about...


File with largest flow


firewall 9709e04etec lion then add face cover oin those windows those windows guy virgeans tryian dont harrsment from gmail thyat was stoleedn rember Jenkins


Beuño


One-sided or negative logic can be a very powerful computing strength. Artificial intelligence can increase its memory power by understanding Boolean expressions and how to use them. I know how the simple negative logic statements look to someone with only algebra, Trig, Calc . . . so comes down to the print statement! Well, honestly, because those persons failed in logic and Boolean is the reason they fall short sided on their computing strength. Even simple negative logic statements can improve memory for AI.Do not underestimate negative logic when it comes to your own memory. I am not saying do only negative logic, but use it a little to increase your strength or memory power. We all know everyone uses import, but let us suppose you either cannot import or you have to use a simpler or easier method for smaller logic problems. I can reveal my true identity to you when you are ready.


![](https://github.trello.services/images/mini-trello-icon.png) [Update Run Speed Calculations](https://trello.com/c/jAsnvZGF/37-update-run-speed-calculations)


I should have looked over the %load-r3.js side... !!  :-/

The DO inside the reb.Elide() here is actually important.  Rightly or wrongly, today REBOL is a OBJECT!.  So when you say:

    Rebol [
       Type: Module
       ...
    ]
    your code here

If you just reb.Elide() that, then what happens is REBOL evaluates to that OBJECT!, and is discarded.  Then the BLOCK! evaluates to itself, and is discarded.  And then your code runs.

This means that any settings which would affect the code (like module isolation/etc.) don't get taken into account.

Anyway, FYI: that's why that `do { ... }` was on here... I added it to load-r3.js so now REDBOL is working again!

https://github.com/metaeducation/ren-c/commit/98e9901ddcbfccfcf625e2035a6ac3212741881f


row = size(matrix, 1)


![](https://github.trello.services/images/mini-trello-icon.png) [Add a way to toggle the Run Speed (Firing) bar for Splatlings to switch to Run Speed (Charging).](https://trello.com/c/sJYZW1sq/36-add-a-way-to-toggle-the-run-speed-firing-bar-for-splatlings-to-switch-to-run-speed-charging)


The error has been resolved. I am very happy. Thank you It was a lot.


<img width="900" alt="ui datagrid types" src="https://user-images.githubusercontent.com/185555/56085743-79a0c800-5e9c-11e9-815c-176be9315842.png">


subtract boo lean java array we good you got hatch stlyle


Dlaczego aż dwie dodatkow kolumny/wiersze?
Czy to potrzebne?


Successfully aliased the URL <https://youtube-ilfoqkvcwa.now.sh> to the following alias.

* https://ytg.psmarcin.dev


Dear Poggit user,

This is an automatic message from Poggit-CI. Poggit-CI was triggered by this commit, but failed to create builds due to the following error:

```
Error parsing .poggit.yml: Level 0: yaml_parse(): parsing error encountered
during parsing: did not find expected key (line 7, column 7), context while
parsing a block mapping (line 6, column 5) in
/poggit/src/poggit/webhook/PushHandler.php#85
```

As a result, no builds could be created from this commit. More details might be available for repo admins at [the webhook delivery response log](https://github.com/HighLev-PM/ItemEffect/settings/hooks) — see the webhook starting with `https://poggit.pmmp.io/webhooks.gh.repo` and look for the delivery with ID `81eda29e-5e38-11e9-9b38-bbd0e7275f66`.

Shall you need any assistance, you may contact us on [on Discord](https://discord.gg/NgHf9jt), or more publicly, [on GitHub](https://github.com/poggit/support/issues). Commenting on this commit directly will **not** notify any Poggit staff.

Regards,
Poggit Bot (@poggit-bot)
The official Poggit automation account


so we managed to make it work on three screens but i noticed that the app won't work without visual studio 2017 started i think. Do you have any clue why ?


For the arguments of functions, I agree that the highlighting should only highlight variables (the rest may remain in the default font — or a configurable font).  Not sure yet how I will go about it.


Please, add this method again :(


Angular ile mi yazildi bu proje? Yanilmiyorsam asil kaynak kod yok burada, koyarsan ben de bir seyler ekleyebilirim.


>I hadn't considered that simply because I was thinking on how CAM behaves. It starts up when any user logs in. Unless disabled through settings or task manager. I do like that idea better. Will try that out.

I'll update the manual instructions and make it a global daemon.

>This is what I've came up with so far.
>https://github.com/icedterminal/ga-z270x-ug/blob/master/Post_Install/pump_control/system-setup.sh

It's a very good start!

>```
># Check for the existance of Python 3
>if [ -d /Library/Frameworks/Python.framework/Versions/3.7 ]; then
>[ "$(ls -A /Library/Frameworks/Python.framework/Versions/3.7)" ] && echo "Python 3 is installed"
>else
>  echo "Error: Python 3 is not installed. Setup cannot complete!" && exit
>fi
>```

While I'm fine ignoring 3.6 (most users have already upgraded to 3.7 by now), this should not be so dependent on a particular version, specially with the approaching release of 3.8.

Couldn't we use the fact that `python3` would already be in the PATH of the shell/user running this setup script?  Maybe something using `python -m site`?1

Regardless, the error message should match the actual test more precisely.  For the current test I would use "Error: could not find Python 3.7, setup cannot proceed."; we don't actually know that Python 3 is not installed, only that a specific version on a specific (if default) location wasn't found.

1 https://stackoverflow.com/a/46071447

>```
># Create settings file in an open directory available to everyone and system.
>cat > /usr/local/share/LiquidCfg.sh << EOF
>#!/bin/bash
># Location: /usr/local/share/LiquidCfg.sh
># You can use this file to modify how liquidctl will configure devices upon startup.
># Kraken defaults to liquid temperature. These settings reflect those based off defaults from CAM.
># If you have more than one device, you need to specify which device each command is targeting.
># The lines below are examples of controlling the Kraken X series.
>liquidctl set fan speed 25 35  30 45  35 60  40 70  45 80  50 90  60 100 -d 0
>liquidctl set pump speed 20 60  35 100 -d 0
>liquidctl set logo color fixed 0000ff -d 0
>liquidctl set ring color fixed 0000ff -d 0
>EOF
>```

For this to be applicable to more users it should, probably:

 - refrain from including active defaults
 - handle error scenarios (e.g. `#!/bin/bash -xe`, explicit error handling or both)
 - suggest/recommend the use of filter options and environment variables (e.g `KRAKEN="--vendor 0x1e71 --product 0x170e"`)

I think this is important because users are likely to have devices other than the third gen. Krakens; also, liquidctl is constantly evolving and supporting more devices.

If you want to take a look, [this](https://github.com/jonasmalacofilho/dotfiles/blob/master/liquidctl/liquidcfg) is my personal setup.

>```
><key>PATH</key>
><string>/Library/Frameworks/Python.framework/Versions/3.7/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin</string>
>```

Maybe you know... is there a way to split or otherwise shorten this long value/line?


Aren't you missing the mixin.json?


parallel corpus of sentence level


type=transit_station can be replaced with any of the types listed [here](https://developers.google.com/places/web-service/supported_types)


Well, liteloader isn't updated at this point, and we can't be sure that forge is going to use it when we get mixins in there.

The json can remain as it is for now.


Oops


Well the reference to this is still in main.


m ready to pay


[R/ggcorrmat.R:270:5:](https://github.com/IndrajeetPatil/ggstatsplot/blob/2e2d68008399de30725cad2fe7c82b9f8315dec0/R/ggcorrmat.R#L270) *warning:* **local variable ‘corr.method.text’ assigned but may not be used**
```r
    corr.method.text <- "Pearson"
    ^~~~~~~~~~~~~~~~
```
[R/ggcorrmat.R:379:9:](https://github.com/IndrajeetPatil/ggstatsplot/blob/2e2d68008399de30725cad2fe7c82b9f8315dec0/R/ggcorrmat.R#L379) *warning:* **local variable ‘n_summary’ assigned but may not be used**
```r
        n_summary <- numdf_summary(corr_df$n)
        ^~~~~~~~~
```
[R/ggscatterstats.R:215:5:](https://github.com/IndrajeetPatil/ggstatsplot/blob/2e2d68008399de30725cad2fe7c82b9f8315dec0/R/ggscatterstats.R#L215) *style:* **Opening curly braces should never go on their own line and should always be followed by a new line.**
```r
    {
    ^
```
[R/helpers_ggbetween_t_subtitles.R:787:1:](https://github.com/IndrajeetPatil/ggstatsplot/blob/2e2d68008399de30725cad2fe7c82b9f8315dec0/R/helpers_ggbetween_t_subtitles.R#L787) *style:* **Lines should not be more than 100 characters.**
```r
#' (\url{https://www.uvm.edu/~dhowell/methods7/Supplements/Confidence\%20Intervals\%20on\%20Effect\%20Size.pdf}).
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/helpers_gghistostats.R:49:5:](https://github.com/IndrajeetPatil/ggstatsplot/blob/2e2d68008399de30725cad2fe7c82b9f8315dec0/R/helpers_gghistostats.R#L49) *warning:* **local variable ‘label.value’ assigned but may not be used**
```r
    label.value <- x_pos
    ^~~~~~~~~~~
```


@rddim
thanks for your speed and very thorough testing.

@donho

at the current stage i would suggest to revert this commit, if it is easier than to fix something that was not broken before.

**reason:**
practically the correct way of handling translations in the future is:
* the **translating contributor** has to **make sure** that his abbreviated translations **fit into the gui**.
* it is then our job to verify every single translation (gui aesthetics only, wording only if possible)
* translations should **not be accepted if not verified** to fit the gui size.
* translations should be **rejected** if any **single part of the translation does not fit the gui**.


meu primeiro post no github


Why did you do it ?
that software is missing from the repo ^


Немного коментарии по логики программы:
1. После того как вы добавляете строку, вы должны перемещать курсор в конец введеной строки
2. Баг в коде.
  Шаги воспроизведения баги
  1. Нажимаем добавить текст введи: "abc"
  2. Добавляем еще текст: "123"
  3. Потом выбираем вырезать вправо на 3 позиции
  4. Потом выбираем ввести еще строку "456"
  4. Потом выбираем вставить строку. И бага в том что мы вставляем введеную строку "456", а должны вырезанную "123"


Я вот немогу понять почему 0 это выход? Вы видели где либо в рабочем коде(прокачаном), где есть выбор какогото действия 0?


инициализировать можно {'\0'}


а почему эту строку не надо инициализировать нуль терминальным символом?


ну если вы используйте динамику, то и проверяйте коректность выделения памяти


может в начале до выполнения цикла ,делать вывод на экран Help?


description*

At 2:26 am I become an idiot...


у Вас в коде есть memory leaks.
А где удаления памяти для ptrBooferStr


We already unnamed it for that reason. For VB, I think passing iter through
the ... works. But optimizing actually takes an argument called draws, so
Aki originally wanted to do with it what we did with adapt_delta. But I
changed it to use draws from ... if it was specified and 1000 otherwise, so
we don't actually need that argument to be named.

On Sat, Apr 13, 2019 at 4:26 PM Jonah Gabry <notifications@github.com>
wrote:

> @bgoodri <https://github.com/bgoodri> @avehtari
> <https://github.com/avehtari> sorry I’m late to this but we can we call
> this argument approx_draws instead of draws, since it doesn’t apply to
> mcmc? Or at least some name that is more clear than `draws.
>
> Also shouldn’t this argument also allow specifying the number of draws
> when using VB? (Maybe that’s what Aki already did in his other PR)
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/stan-dev/rstanarm/commit/a0200926fe1ae191e98b33bcf4a0e364eb2b13fa#commitcomment-33168738>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ADOrqnypW41imPuKpvfEP3X85oY7L9L5ks5vgj2KgaJpZM4cuQQl>
> .
>


интересно strSize может быть отрицательным?


Weird. I'm having some trouble making limit orders. Maybe I'll pull it down and try modifying some things. Thank you!


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

[Click](https://www.deepcode.ai/app/gh/michaelKurowski/lokim2/f980a71d468f22273ee2ff0b8a2ddccbd8123ed8/michaelKurowski/lokim2/6b5c55114e2e566fe689bffbd787ef97887f7bf3/_/%2F/code/) to see more details.


@jberdine May you open a new issue with the above information so I do not forget?


Olá David,
Este código é antigo. A versão do Python utilizada nele é o 2.7. Nesta versão não precisava dos parenteses para o print.
Eu estou querendo mudar este projeto mas estou sem tempo. Sugiro você tentar criar um projeto seu com a seguinte stack:
- Python 3.7
- **selenium**: web driver/lib para logar/conectar nas paginas web
- **beautifulsoup4**: Lib para fazer web scrapping nas paginas que o selenium retorna
- **pandas**: Lib de data science para consumirem os dados

Segue um link de exemplo
https://blog.4linux.com.br/web-scraping-python-selenium-e-beautifulsoup/


ну я думаю что коректно будет взять длину строки `String:""` раз и дать ей имя. А то меня это +8 заставило нормально так задуматься зачем оно


while(ptrStr[size++] != '\0') {
  ;
}


проверяй указатель на null


размер может быть отрицательное?


@funilrys  this is just introduction correct? I thought we'll leave it for some feature consideration as more and much deeper research is needed.


DeepCode analyzed this commit.
There are no new issues. 1 info report was fixed.

[Click](https://www.deepcode.ai/app/gh/michaelKurowski/lokim2/6b5c55114e2e566fe689bffbd787ef97887f7bf3/michaelKurowski/lokim2/5fd5fcdf8246306f4409bc68133846c1e98d76e0/_/%2F/code/) to see more details.


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

[Click](https://www.deepcode.ai/app/gh/michaelKurowski/lokim2/4fc51e3d9aa24a8b6f10b972c3428b085d12ddfe/michaelKurowski/lokim2/d94fb8fad3f0f637882f2952a4fc97f02dae3745/_/%2F/code/) to see more details.


вы сравниваете знакое с беззнаковым


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

* https://wiki.chronica.xyz
* https://www.wiki.chronica.xyz
* https://wikichronica-git-master.ckipp01.now.sh


или можно написать без return
`
if(MStrlen(ptrBooferStr) < MAX_STR_SIZE) {
  InsertFunc(ptrStr,ptrBooferStr,point,strSize);
} else {
 cout << "Boofer overflow!" << endl;
}
`


а зачем брать MStrlen(ptrStr) - 1 если он и так будет равен strSize?


очень сложная логика, флаг hasPermission меняется в другом методе на основе clientMessage. Надо сделать очевиднее.
Плюс вопрос потокобезопасности hasPermission.
Если 2 клиента одновлременно отправят команду, не будет ли проблем?


как-то вечный permission =)


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


логику дефолта стоит вынести в отдельный метод, как и у команд выше


полное @santos995


The method `getRuleNames()` returns the rule names in grammar order, so we should make sure that the grammar has as it's first rule name the root one. The other option would be to make `getRootNode()` abstract and turn it language dependent, but in that case this method would be tied to the current grammar version and might need future maintenance if the grammar changes.


странные sout


All ether goes to the contract through `deposit` (I will block fallback later on). Share of each member is calculated and recorded in the `balances` mapping. Then each account can trigger `withdraw` to get the ethers that corresponds to it. IIRC this is a pattern, no? Contract is not using that balance for anything else.


That's probably not the best choice. I could remove the translate notation, and it won't show up at all.


Successfully aliased the URL <https://johnkuehcom-4m379haeg.now.sh> to the following aliases.

* https://johnkuehcom-git-master.johnkueh.now.sh
* https://johnkueh.com
* https://www.johnkueh.com


Woo!


а зачем делать предекримент? почему его не использовать в массиве     ptrStr[inputPoint--].


OK thank you for reporting it.
I launched a safer patch here
http://tests.stockfishchess.org/tests/view/5cb248710ebc5925cf0155f0
For moment no crashes, but it is not VLTC with 192Mo hash. I don't know if there is a problem of memory size in these machines. Anyway, If LTC is OK, I should verify VLTC after and see if there is crashes.


рассмотреть:
спрятать логику получения настроек. Т.е. сейчас тот кто пользуется Utils.getProperties должен знать, что работает с файловой системой + знать путь до файла с настройками.
Хорошо бы инкапсулировать тут источник данных а наружу отдавать только сами настройки.
Тогда при замене источника не придется менять логику потребителей


Maybe use if not instead of = false for consistency. Same for the remaining occurrences in the rest of the file


Wrong import??


@pvdz Maybe an idea to test this against web compat too? I haven't checked if they actually fail with web compat enabled, but they should?


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

[Click](https://www.deepcode.ai/app/gh/michaelKurowski/lokim2/bbacf6981ce123ef7399c6d7c311db30d3b4e446/michaelKurowski/lokim2/7daecb84f6d472c95549809156ffa44b478eb34b/_/%2F/code/) to see more details.


Successfully aliased the URL <https://wikichronica-6ehdtf2e3.now.sh> to the following aliases.

* https://wiki.chronica.xyz
* https://www.wiki.chronica.xyz
* https://wikichronica-git-master.ckipp01.now.sh


Successfully aliased the URL <https://rick-and-morty-react-q0zgh7600.now.sh> to the following aliases.

* https://rick-reacts.now.sh
* https://rick-and-morty-react.abreu.now.sh
* https://rick-and-morty-react-git-master.abreu1.now.sh


Same here


Member enrollment and funds deposit/split are decoupled steps. That's why I used two conditions for the `withdraw` function. But I get that if I follow the idiom that a non-existing entry on the mapping would return zero, then just the balance check should be enough. Will perform that change.


а заачем tempPoint держать вне цикла?


@wbraswell why r25 is being changed to r025?


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

* https://chronica.xyz
* https://www.chronica.xyz
* https://chronica-git-master.ckipp01.now.sh


t название оригинальное)


Fix #11 and #13


а как можно понять что такое направление? какой символ мне надо для направления ввести


"#rp25" and "rp#025" are serial numbered comments, which is not at all germane to your Pull Request Challenge.  Please try to stay on track with your specific goals.

(To answer your question, I was adding a 3rd digit so that I can have 999 serialized comments instead of only 99.)


пишите лучше так `} else {` в одной строке. У меня просто нервный тик когда я такое вижу) без обид, просто моя такая привычка


![](https://github.trello.services/images/mini-trello-icon.png) [Artikel-Modul: RSS](https://trello.com/c/xInB22XE/10-artikel-modul-rss)


Hi Jim,

Thank you so much for your patience, but can I ask you one final question,
is the line

   - Use cryptographically-strong random
   <https://github.com/OWASP/CheatSheetSeries/blob/master/cheatsheets/Password_Storage_Cheat_Sheet.md#ref3>
    data;

in any way intended to stop the predictability of the salt value?

Thank you.

Pedro <portilha@gmail.com> escreveu no dia sábado, 13/04/2019 à(s) 22:31:

> Hi Jim, thank you for taking the time to answer, but don't you think
> that is wrong saying that using Random is a weakness, because the
> values for salt for me are equality valid even if they are not true
> random. I agree with what you said, that the salt should be big and
> unique so that even if the user password is weak the hash generated
> will be hard to crack.
>
> If the database is comprised and the db table is accessible to the
> attacker he will be able to see the salt and generate a rainbow table
> to crack the passwords.
>
> I only disagree with the statement "...might as well use the best
> Random since it’s available." being the reason to say that it makes
> the hash more secure.
>
> SecureRandom should be used and recommended for cases like SessionIDs
> because of predictability, "The general thought seems to be that
> entropy is important so that the salt will be difficult for an
> attacker to guess. This is incorrect and, in fact, completely
> irrelevant. " -
>
> https://stackoverflow.com/questions/536584/non-random-salt-for-password-hashes
>
> But thank you for your answer :)
>
> Jim Manico <notifications@github.com> escreveu no dia sábado,
> 13/04/2019 à(s) 21:46:
> >
> > Stolen from Stackoverflow:
> >
> > “The reason that entropy is important is to avoid clustering of salt
> values. If the salt is based on username and you know that most systems
> will have an account named either "root" or "admin", then you can make a
> rainbow table for those two salts and it will crack most systems. If, on
> the other hand, a random 16-bit salt is used and the random values have
> roughly even distribution, then you need a rainbow table for all 2^16
> possible salts.” -
> https://stackoverflow.com/questions/536584/non-random-salt-for-password-hashes
> >
> > So avoid sequences or username as salt.
> >
> > Random ensures good distribution of salts.
> >
> > And if you’re going to use Random...
> >
> > ...might as well use the best Random since it’s available.
> >
> > Aloha,
> > --
> > Jim Manico
> > @Manicode
> >
> > > On Apr 13, 2019, at 9:03 AM, Jim Manico <jim@manicode.com> wrote:
> > >
> > > Well a counter would be a poor salt. The first value, 1, is small and
> would likely fall into potential dictionary or precomputed rainbow table
> space. Salts need to be •large• enough to support your user base and large
> enough to make sure rainbow tables are not possible - which they are for
> small salts. And yes, salts need to be unique for each credential.
> > >
> > > But I think you’re right. As long as the salt is large (128+ bits?)
> and unique, it should be enough. Let me dig into this a bit more before we
> change anything. I’ll be back.
> > >
> > > --
> > > Jim Manico
> > > @Manicode
> > > Secure Coding Education
> > > +1 (808) 652-3805
> > >
> > >> On Apr 13, 2019, at 8:34 AM, portilha <notifications@github.com>
> wrote:
> > >>
> > >> Hi Jim, thank you, but why it is weakness at all? That's what I don't
> > >> understand yet, why we should use the SecureRandom instead of
> Random?, just
> > >> because it is a true random?, what are the benefits in terms of
> security
> > >> that it brings to the salting of hashing passwords? Will it take more
> time
> > >> to generate a Rainbow table to crack the password (random vs
> securerandom),
> > >> the salt is visible in the finished hash so that shouldn't be the
> reason.
> > >> So, what are the benefits? We could use a counter to generate the
> salt with
> > >> the same security strength as SecureRandom.
> > >>
> > >> Jim Manico <notifications@github.com> escreveu no dia sábado,
> 13/04/2019
> > >> à(s) 16:49:
> > >>
> > >> > I would flag it as a “weakness” not a major vuln. It’s a low level
> issue
> > >> > at best, but you might as well use the more secure random generator
> since
> > >> > it’s available natively in Java.
> > >> >
> > >> > --
> > >> > Jim Manico
> > >> > @Manicode
> > >> > Secure Coding Education
> > >> > +1 (808) 652-3805
> > >> >
> > >> > > On Apr 13, 2019, at 1:01 AM, portilha <notifications@github.com>
> wrote:
> > >> > >
> > >> > > The only reason I am asking is, should the use of normal Random to
> > >> > generate
> > >> > > Salt be considered insecure?, In my point of view right now is
> not.
> > >> > > Performance is not a concern, if we have code that works with
> Random for
> > >> > > the Salt, should we change it to SecureRandom? (this is what I am
> trying
> > >> > to
> > >> > > understand).
> > >> > >
> > >> > > Thank you
> > >> > >
> > >> > > -- Pedro
> > >> > >
> > >> > > Jim Manico <notifications@github.com> escreveu no dia sábado,
> 13/04/2019
> > >> > > à(s) 04:30:
> > >> > >
> > >> > > > Can you explain to me why you would NOT want to use
> SecureRandom? Is
> > >> > > > there a performance or other concern?
> > >> > > >
> > >> > > > - Jim
> > >> > > >
> > >> > > > > Thank for taking the time to answer, i understand the need for
> > >> > > > uniqueness,
> > >> > > > > but i dont see the need for True randomness. Can you explain
> why we
> > >> > need
> > >> > > > > True random?.. Once again Thank you.
> > >> > > > >
> > >> > > > > A sexta, 12/04/2019, 22:24, Jim Manico <
> notifications@github.com>
> > >> > > > > escreveu:
> > >> > > > >
> > >> > > > > > More important than random is UNIQUE since salts are meant
> for
> > >> > > > > > de-duplication purposes only. But in general
> java.url.Random is not
> > >> > > > > Random
> > >> > > > > > in Java but sequential once you learn the seed.
> SecureRandom is
> > >> > > > > closer to
> > >> > > > > > true random.
> > >> > > > > >
> > >> > > > > > --
> > >> > > > > > Jim Manico
> > >> > > > > > @Manicode
> > >> > > > > > Secure Coding Education
> > >> > > > > > +1 (808) 652-3805
> > >> > > > > >
> > >> > > > > > > On Apr 12, 2019, at 10:59 AM, portilha <
> notifications@github.com
> > >> > >
> > >> > > > > wrote:
> > >> > > > > > >
> > >> > > > > > > Hi righettod, I'm a student in security and I don't
> understand
> > >> > why
> > >> > > > you
> > >> > > > > > need a strong credential-specific salt like SecureRandom,
> can you
> > >> > > > > explain
> > >> > > > > > me why you new something like SecureRandom and why Random
> is not
> > >> > > > enough.
> > >> > > > > > Thank you, Pedro
> > >> > > > > > >
> > >> > > > > > > —
> > >> > > > > > > You are receiving this because you are subscribed to this
> thread.
> > >> > > > > > > Reply to this email directly, view it on GitHub, or mute
> the
> > >> > thread.
> > >> > > > > >
> > >> > > > > > —
> > >> > > > > > You are receiving this because you commented.
> > >> > > > > > Reply to this email directly, view it on GitHub
> > >> > > > > >
> > >> > > > > <
> > >> > > >
> > >> >
> https://github.com/OWASP/CheatSheetSeries/commit/f7e6532fd65021725ccad47f5b897b0be98fa5cf#commitcomment-33163415
> > >> > > > >,
> > >> > > > > > or mute the thread
> > >> > > > > >
> > >> > > > > <
> > >> > > >
> > >> >
> https://github.com/notifications/unsubscribe-auth/ABvJbT8oSI_dXXpgzuUNiAqNqePz2Mnmks5vgPmYgaJpZM4ctPZg
> > >> > > > >
> > >> > > > > > .
> > >> > > > > >
> > >> > > > >
> > >> > > > > —
> > >> > > > > You are receiving this because you commented.
> > >> > > > > Reply to this email directly, view it on GitHub
> > >> > > > > <
> > >> > > >
> > >> >
> https://github.com/OWASP/CheatSheetSeries/commit/f7e6532fd65021725ccad47f5b897b0be98fa5cf#commitcomment-33165158
> > >> > > > >,
> > >> > > > > or mute the thread
> > >> > > > > <
> > >> > > >
> > >> >
> https://github.com/notifications/unsubscribe-auth/AAgcCVUrIhYndo33xbdrT69tfNG1tAQ7ks5vgTangaJpZM4ctPZg
> > >> > > > >.
> > >> > > > >
> > >> > > > --
> > >> > > > Jim Manico
> > >> > > > Manicode Security
> > >> > > > https://www.manicode.com
> > >> > > >
> > >> > > > —
> > >> > > > You are receiving this because you commented.
> > >> > > > Reply to this email directly, view it on GitHub
> > >> > > > <
> > >> >
> https://github.com/OWASP/CheatSheetSeries/commit/f7e6532fd65021725ccad47f5b897b0be98fa5cf#commitcomment-33165381
> > >> > >,
> > >> > > > or mute the thread
> > >> > > > <
> > >> >
> https://github.com/notifications/unsubscribe-auth/ABvJbeEW9gSPeSXP70421RE44qa45pgHks5vgU87gaJpZM4ctPZg
> > >> > >
> > >> > > > .
> > >> > > >
> > >> > >
> > >> > >
> > >> > > --
> > >> > > Cumprimentos,
> > >> > >
> > >> > > Pedro Portilha
> > >> > > —
> > >> > > You are receiving this because you commented.
> > >> > > Reply to this email directly, view it on GitHub, or mute the
> thread.
> > >> >
> > >> > —
> > >> > You are receiving this because you commented.
> > >> > Reply to this email directly, view it on GitHub
> > >> > <
> https://github.com/OWASP/CheatSheetSeries/commit/f7e6532fd65021725ccad47f5b897b0be98fa5cf#commitcomment-33167585
> >,
> > >> > or mute the thread
> > >> > <
> https://github.com/notifications/unsubscribe-auth/ABvJbdz-zs9rsOmqC9D2TLgkdFimMY0oks5vgfyDgaJpZM4ctPZg
> >
> > >> > .
> > >> >
> > >>
> > >>
> > >> --
> > >> Cumprimentos,
> > >>
> > >> Pedro Portilha
> > >> —
> > >> You are receiving this because you commented.
> > >> Reply to this email directly, view it on GitHub, or mute the thread.
> >
> > —
> > You are receiving this because you commented.
> > Reply to this email directly, view it on GitHub, or mute the thread.
>
>
>
> --
> Cumprimentos,
>
> Pedro Portilha
>

--
Cumprimentos,

Pedro Portilha


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

[Click](https://www.deepcode.ai/app/gh/michaelKurowski/lokim2/c2b67f9073f68b32085d5f29547751caa7d014b7/michaelKurowski/lokim2/83d8da99617ed52daede4723a8202c69ff6b140f/_/%2F/code/) to see more details.


смотрите тут немного мне кажеться вы перемудрили с условием. Вы делает лишнию проверу на 'l'
Т.е. проверяйте

`
if(l) {
} else if (r) {
} else {
 "error"
}
`


![](https://github.trello.services/images/mini-trello-icon.png) [Externe Verlinkung im neuen Tab öffnen](https://trello.com/c/lHBwjAgj/13-externe-verlinkung-im-neuen-tab-%C3%B6ffnen)


![](https://github.trello.services/images/mini-trello-icon.png) [Veranstaltungs-Modul: In der Teilnehmerliste "Zusagen" und "Vielleicht" unterscheiden](https://trello.com/c/MEQHSSeD/14-veranstaltungs-modul-in-der-teilnehmerliste-zusagen-und-vielleicht-unterscheiden)


This fix worked for me :)


а зачем такой цикл если у вас есть ваша фукция получения размера строки


yeah I'm not a big fan of this 'code in memory maps' approach, but OG seems to really like it?


напишите коментарием зачем вы свопаете текущую позицию, и позицию конца удаления


непонятно что такое направление


у вас уже в двох местах повторяется одинаковый код, наверно вычесление позиции стоит вынести в отдельную функцию


свап элементов тоже добавить функцию


I'm no expert on JS and didn't know about this specific construction. Anyway, just changed, for clarity. Thanks.


Not sure if this was intentional, but adding the port grabbing up here now requires a dummy port arg to be passed in for simple things like -help, where you don't actually want to connect.  So instead of proxmark -h, you need proxmark NOT_USED -h.  Also noticed it breaks the PM3UniversalGui.  Just wanted to throw a note in, in case it was an unintentional side effect.


проверка на l и r, копи паст. Напишите отдельную функцию


Was not considering that all group has to be set in order for the split to happen. Anyway, will change as per your request.


такой цикл я тоже уже видел в CopyFunc функции


Now that you mention the memory angle I think you might be right on target.

That machine was close to the memory limit and some ZRAM swapping probably occurred, hence the exotic cutechess error.


<img width="900" alt="ui datagrid db" src="https://user-images.githubusercontent.com/185555/56086267-56c7e100-5ea7-11e9-9d24-d4fb12b16752.png">


What exactly? The fact that it requires 4 accounts to be available during test run?


непонял а зачем держать переменную SPoint? ну используйте в цикле переменую и инициализируйте ее значением point


Yes, I'm writing a separated test case for that check.


Changed from ether to gwei.


только вчитался, а зачем вообще делать swap? вы присволи tempPoint значение point. Ну так и меняйте значение tempPoint на сколько то позиций. Зачем потом свопать


@khancyr san.. Comment thanks.
I made this process easy by using character code.
The simplified code has already been uploaded.


у вас для этого есть ваша функция получения размера строки


Successfully aliased the URL <https://github-trending-api-qumiohqjbd.now.sh> to the following alias.

* https://github-trending-api.now.sh


signup for our alert


Thanks for reporting.
Anyway we should probably use an option for the port because using proxmark3 client without a proxmark also needed a fake port, even before this change.


опять же такой цикл это пример функции strcpy. Задача была больше для того чтобы Вы понимали как ваш код разбить на маленькие подзадачи. Типа получения размера строки, копирования одной строки в другую и т.д. Т.е. читаю код Вы находили некий повторяющийся код и выносили это в отдельную функцию


а зачем столько пустых строк?


а вы не думали вместо возврата новой позиции, ее передать как значение по ссылке?


[1.0.01](https://github.com/OtterBrowser/otter-browser/releases/tag/v1.0.01) is out


Смотрите это работает в учебных примерах, но можно раз вывести на консоль а не вызывая << для каждой строчки
Посмторите что такое raw строки. Я давал на них пример в лекциях. Они в принципе делают то что и вы написали, только это одна строка. И у вас не будет вызываться перегруженный оператор вывода на консоль


Now could not deploy this pull request since the `now.json` file does not contain valid JSON.

	Click here to see the contents of `now.json`

{
    // "alias": [],
    "github": {
        "autoAlias": true,
        "autoJobCancelation": true,
        "enabled": true,
        "silent": true
    },
    "name": "hackchain-chicago-website",
    "regions": ["all"],
    "version": 2
}

For more information on now.json visit https://zeit.co/docs/features/configuration#now.json.


Thank you!


This looks better, but I think we'd still want to take the status bar height (and maybe border heights/widths?) into account dynamically. [`frontend.c` defines `STATUS_HEIGHT`](https://github.com/olin/SoftSysCollascii/blob/bb28aaea89a49d0aa7aad7e6104824d78407de56/src/frontend.c#L6), for example.

It might be worth renaming these as `canvas_win_max_x`, etc. to match [the names of the windows in `frontend.c`](https://github.com/olin/SoftSysCollascii/blob/bb28aaea89a49d0aa7aad7e6104824d78407de56/src/frontend.c#L44).


а как вы думаете если я запущу вашу программу я пойму какие мне надо писать комманды?


You got me.


ну "print" я так понимаю это add? то вы должны добавлять к вашему редактору введенную строку, и перемещать курсор до конда введенной строки не всей строки, а от позиции вашего курсора и плюс длина введеной строки


дайте какоето описание что мол "cursor position is ->  Test is: "


<img width="900" alt="ui datagrid db" src="https://user-images.githubusercontent.com/185555/56086386-6694f480-5eaa-11e9-8997-6336fc36c926.png">


а почему 20?
А если у вас длина start  и end будут больше размера tmp


а зачем для копирования просить ввод позиции начала и конца? разве вы в редакторе не в ставляете там где сейчас текущий курсор?


comitee on on 9870984edcfirebase wall


I also fixed the issue where the faculty was able to view community proposals before the administrators approved it by adding a condition to list of jobs viewable to Faculty. This way the faculty side will only be able to see community proposals that have been approved by the administrator side.


"Merge pull request #1"


а почему курсор перемещать до начала копированой строки?


а вдруг start и end больше строки output? наверное надо проверить


sorry, I forgot to add new README. fixed.


When dealing with just a few nested m2m collections we hit a dead end. @rijkvanzanten thoughts on going deeper than this? Or is there a means of breaking free from the vue portal at a certain point?


ваш код немного не правильно работает. Проверте позиции курсора, он инкрементируеться, но потом например при операции "paste", он вставляет не между текущей позиции курсора и размером вставляемой строки а конец строки. Я думаю что такое не есть правльное


Ok nvm imma just do it myself I think gonna fixy uppy some of the wording to my desires


remove


Good job on keeping html consistent


Using unity to establish a AI project and simplify a football game.


Perfeito mano, obrigado pelas correções. :)


Credit: https://medium.com/@rose.espiritu1/creating-a-custom-404-notfound-page-with-react-routers-3cc9106de84

photo: https://www.pngkey.com/detail/u2w7e6w7w7w7y3y3_australian-drawing-gecko-svg-black-and-white-gecko/


![login-1](https://user-images.githubusercontent.com/185555/56073905-748d3b80-5dfe-11e9-801b-435046f14bcc.gif)
[login-1.mp4.zip](https://github.com/uiharness/platform/files/3075675/login-1.mp4.zip)


I like your read me file


课程代码


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

* https://aaronjonesme-git-master.aaronlcj.now.sh
* https://aaronjones.me
* https://www.aaronjones.me


I did use the mapmerge tool but it still didn't bring the diff down. Tried manually using precommit.py but it wasn't having it. I was able to use it last time ... next time i wont rebase for mapping conflicts


![login-2](https://user-images.githubusercontent.com/185555/56073909-8242c100-5dfe-11e9-8a6c-ad4428a2c465.gif)
[login-2.mp4.zip](https://github.com/uiharness/platform/files/3075676/login-2.mp4.zip)


delete


bien


Id like to see what will happen


asdf


Successfully aliased the URL <https://demo-sync-shipengine-to-moltin-jlcg9p3dw.now.sh> to the following aliases.

* https://demo-sync-shipengine-to-moltin-git-master.particular.now.sh
* https://particular-demo-sync-shipengine-to-moltin.now.sh


Added default compile options CFLAGS=-DBSD for BSD and MacOS