Comment on 3327fd6e79b3503627bc65853bb77bc59651d089.

There are 141 results for the section python spacing. They have been shortened and will not be shown inline because they are more than 10.

| Message | File | Line |
|---|---|---|
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 3 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 12 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 13 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 20 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 21 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 22 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 23 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 24 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 25 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 27 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 29 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 30 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 31 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 32 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 33 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 35 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 36 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 39 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 41 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 43 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 44 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 47 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 48 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 50 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 51 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 53 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 54 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 56 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 57 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 58 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 60 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 62 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 66 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 68 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 75 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 77 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 86 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 89 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 90 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 91 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 92 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 93 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 94 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 95 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 96 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 98 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 101 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 102 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 103 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 104 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 105 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 106 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 107 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 108 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 109 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 110 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 112 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 113 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 114 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 118 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 120 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 121 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 122 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 123 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 125 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 126 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 127 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 132 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 133 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 134 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 138 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 139 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 140 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 142 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 143 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 144 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 146 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 148 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 150 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 152 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 153 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 154 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 155 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 156 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 158 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 160 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 161 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 162 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 163 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 165 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 167 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 168 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 171 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 173 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 174 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 175 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 177 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 178 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 179 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 180 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 181 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 182 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 184 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 186 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 187 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 188 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 189 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 192 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 193 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 194 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 195 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 196 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 199 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 201 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 202 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 205 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 206 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 209 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 210 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 211 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 213 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 214 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 219 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 220 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 221 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 222 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 228 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 229 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 231 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 232 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 233 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 237 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 242 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 247 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 249 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 251 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 255 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 257 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 258 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 259 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | avl_tree/avl .py | 262 |

Until GitMate provides an online UI to show a better overview, you can run [coala](https://coala.io/) locally for more details.


Comment on 3327fd6e79b3503627bc65853bb77bc59651d089.

There are 28 results for the section pep8. They have been shortened and will not be shown inline because they are more than 10.

| Message | File | Line |
|---|---|---|
| The code does not comply to PEP8. | avl_tree/avl .py | 3 |
| The code does not comply to PEP8. | avl_tree/avl .py | 8 |
| The code does not comply to PEP8. | avl_tree/avl .py | 12 |
| The code does not comply to PEP8. | avl_tree/avl .py | 20 |
| The code does not comply to PEP8. | avl_tree/avl .py | 39 |
| The code does not comply to PEP8. | avl_tree/avl .py | 47 |
| The code does not comply to PEP8. | avl_tree/avl .py | 62 |
| The code does not comply to PEP8. | avl_tree/avl .py | 66 |
| The code does not comply to PEP8. | avl_tree/avl .py | 75 |
| The code does not comply to PEP8. | avl_tree/avl .py | 85 |
| The code does not comply to PEP8. | avl_tree/avl .py | 89 |
| The code does not comply to PEP8. | avl_tree/avl .py | 101 |
| The code does not comply to PEP8. | avl_tree/avl .py | 118 |
| The code does not comply to PEP8. | avl_tree/avl .py | 132 |
| The code does not comply to PEP8. | avl_tree/avl .py | 138 |
| The code does not comply to PEP8. | avl_tree/avl .py | 173 |
| The code does not comply to PEP8. | avl_tree/avl .py | 186 |
| The code does not comply to PEP8. | avl_tree/avl .py | 192 |
| The code does not comply to PEP8. | avl_tree/avl .py | 199 |
| The code does not comply to PEP8. | avl_tree/avl .py | 205 |
| The code does not comply to PEP8. | avl_tree/avl .py | 209 |
| The code does not comply to PEP8. | avl_tree/avl .py | 219 |
| The code does not comply to PEP8. | avl_tree/avl .py | 228 |
| The code does not comply to PEP8. | avl_tree/avl .py | 237 |
| The code does not comply to PEP8. | avl_tree/avl .py | 242 |
| The code does not comply to PEP8. | avl_tree/avl .py | 247 |
| The code does not comply to PEP8. | avl_tree/avl .py | 255 |
| The code does not comply to PEP8. | avl_tree/avl .py | 262 |

Until GitMate provides an online UI to show a better overview, you can run [coala](https://coala.io/) locally for more details.


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

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

Please, copy and paste this stack trace to GitHub:

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

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

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


TY ♥


i think this was fine.


Hi Osha,
Please code as much of the page information as you can. For example does your page have only one contact, Jane Doe, listed? Aren't there any others? Please list a few more others.and in that case you will need a root node which yu can call it <contacts> if you like.


@zebastian please do a git reset --hard HEAD~25 && git pull


Thank you


I think it should be the same for `supportsRtl`, not sure about it...


![screenshot from 2017-10-25 00-41-04](https://user-images.githubusercontent.com/3840535/31963166-709850c8-b91d-11e7-8a2d-c22cb689a6e2.png)


Why is the interceptor necessary on the civic?


LGTM


haha.... this is a brilliant update


a


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

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


Как всё это выглядит:

![webmtitleloading](https://user-images.githubusercontent.com/1059874/31963235-b2bbaf28-b908-11e7-83fb-725fa5733344.gif)


Do you have to change `kubeadm_checksum` value as well? Otherwise kubeadm download will fail.


@nolimits4web
Amazing!!!! Thank you soooo much!!!!


`git submodule update --init --recursive` and try again :) Looks like README is missing this information, will update it.


Map.Entry entry;
 краще винести перед циклом, а тут лишити
entry = (Map.Entry) i.next();


test w /login


new credentials required also (not setup on heroku yet) - ask for local credentials


Hi Laura,
Yes, we'd like the final xml to look as realistic as possible. It needs to capture as much of the data on your web page as possible.


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

> set -x;set -e;set -o pipefail;cd /tmp/0pdd20171024-12140-1ssxubb/irbuch/codequiz-master && pdd -q -f /tmp/pdd.xml20171024-12185-1i1gkx8: pid 12209 exit 255 (not zero): + set -e + set -o pipefail + cd /tmp/0pdd20171024-12140-1ssxubb/irbuch/codequiz-master + pdd -q -f...

Please, copy and paste this stack trace to GitHub:

```
set -x;set -e;set -o pipefail;cd /tmp/0pdd20171024-12140-1ssxubb/irbuch/codequiz-master && pdd -q -f /tmp/pdd.xml20171024-12185-1i1gkx8: pid 12209 exit 255 (not zero):
+ set -e
+ set -o pipefail
+ cd /tmp/0pdd20171024-12140-1ssxubb/irbuch/codequiz-master
+ pdd -q -f /tmp/pdd.xml20171024-12185-1i1gkx8

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

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


Unset broker user and password isn't supposed to be a failure case--it is a way to signal to the test suite that the service broker is already registered with CF elsewhere, and does not need to be registered by DRATS.

I recommend to revert this change, otherwise you'll hit issues later on when you try to get the nfs tests to work in P-DRATS.


@mancoast can you check by setting the ogg file as an http ressource?
Just set the value to the source where you got the file from.


i did that, works now, thanks


I restricted the possibility to edit only for the logged In users.
I did other few modifications in this website


не дуже добре використовувати конкретні числа. Краще вичитувати рік з поточної дати


😎

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

> Oui, In engish un nouveau boulot
>
> Le Frsky S.PORT en premier (et l'implémentations en driver SPI)
>
> A première vu, on le fera.
>
> ----- Original Message -----
> From: pierrotm777 <notifications@github.com>
> To: Ingwie/OpenAVRc_Dev <OpenAVRc_Dev@noreply.github.com>
> Cc: Bracame <theingwie@gmail.com>, Comment <comment@noreply.github.com>
> Date: Tue, 24 Oct 2017 18:54:12 +0000 (UTC)
> Subject: Re: [Ingwie/OpenAVRc_Dev] Update cabling documentation (3f72018)
>
> > Tu veux parler du BT ?
> >
> > Le 24 oct. 2017 20:19, "Bracame" <notifications@github.com> a écrit :
> >
> > > You love give me newer job !!
> > > Pff, After the one in course ;-)
> > >
> > > —
> > > You are receiving this because you are subscribed to this thread.
> > > Reply to this email directly, view it on GitHub
> > > <https://github.com/Ingwie/OpenAVRc_Dev/commit/
> 3f7201880bda920ed984d27ccdc3bce4d278c0e5#commitcomment-25164289>,
> > > or mute the thread
> > > <https://github.com/notifications/unsubscribe-auth/AHz4Eq_
> l4YvrzsZghPjPlB64tISQfLbVks5svioggaJpZM4QE33L>
> > > .
> > >
> >
> >
> > --
> > You are receiving this because you commented.
> > Reply to this email directly or view it on GitHub:
> > https://github.com/Ingwie/OpenAVRc_Dev/commit/
> 3f7201880bda920ed984d27ccdc3bce4d278c0e5#commitcomment-25165102
> >
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://github.com/Ingwie/OpenAVRc_Dev/commit/3f7201880bda920ed984d27ccdc3bce4d278c0e5#commitcomment-25165465>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AHz4EjTMxpkJlkKzJgnErsSpbnIVxSlkks5svjXRgaJpZM4QE33L>
> .
>


Ok I have been trying to figure this out for a while and need some help.  Why can 't rlog.Data decode into fsm.op if the committed operation is a rollback but rlog.Data can apparently be decoded into consensus.Op(consensusOp{fsm.state}) when the later is itself of the same type as fsm.op.  I am guessing this has something to do with my earlier confusion about `h.ErrorIfNoField = true`.


Aah, that did the trick. Stellar support, thanks Marcin. Things are _so_ much nicer with `idle-time-limit` :)


. WTF Is That?


Thanks for adding in this explicit documentation. This really helps speed up dev time.


yea looks awesome!  I will test asap


cdewewdewdwe


нам сканер полем класу не потрібний, він не є частиною персона
В методи класу його краще передавати параметром, наприклад
public void changeName(Scanner scanner)


need to fix so it uses string from GeoJSON


Hi Mai,
OK. But it is not necessary to have a CSS file along with our XML and DTD files? (We won't be deducted points for not having one?)


This was much simpler than what I considered doing.


sounds good!


need to fix this so it uses string from GeoJSON also


The following doc(s) have been deployed to the [thomasthac](https://thomasthac-static-docs.pantheonsite.io/docs) Multidev environment:
- [/docs/rsync-and-sftp](https://thomasthac-static-docs.pantheonsite.io/docs/rsync-and-sftp)


можна просто
return numder<=5 && numder>=-5;


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

> set -x;set -e;set -o pipefail;cd /tmp/0pdd20171024-12603-ce75ob/irbuch/codequiz-master && pdd -q -f /tmp/pdd.xml20171024-12670-ct6cg3: pid 12694 exit 255 (not zero): + set -e + set -o pipefail + cd /tmp/0pdd20171024-12603-ce75ob/irbuch/codequiz-master + pdd -q -f /tmp/pdd.xml20171024-12670-ct6cg3...

Please, copy and paste this stack trace to GitHub:

```
set -x;set -e;set -o pipefail;cd /tmp/0pdd20171024-12603-ce75ob/irbuch/codequiz-master && pdd -q -f /tmp/pdd.xml20171024-12670-ct6cg3: pid 12694 exit 255 (not zero):
+ set -e
+ set -o pipefail
+ cd /tmp/0pdd20171024-12603-ce75ob/irbuch/codequiz-master
+ pdd -q -f /tmp/pdd.xml20171024-12670-ct6cg3

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

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


Yeah... recordings suddenly become less boring, more straight to the point :)


Shouldn't use geocoding to perform autocomplete and map recentering


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

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


@mancoast confirmed


false


L'intéret c'est de pouvoir faire un inspect dans Eclipse facilement ;-)

Mais j'avais pas capté qu'en fait UIContext.get().getObject() est accessible de l'extérieur.
Donc on peut getter facilement n'importe quel PObject de l'extérieur.


@ale-rt Jenkins CI reporting about code analysis
See the full report here: http://jenkins.plone.org/job/package-plone.app.contentlisting/22/violations
```
plone/app/contentlisting/catalog.py:136:23: T000 Todo note found.
```
Follow [these instructions](https://github.com/plone/jenkins.plone.org/blob/master/docs/source/run-qa-on-package.rst) to reproduce it locally.


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

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


Подразумевал уже номер буквы


[R/plotOutlierProbabilities.R:12:23:](https://github.com/mlr-org/mlr/blob/7960c722d415ffad9bd19c2109a9d71d936f82e3/R/plotOutlierProbabilities.R#L12) *warning:* **Unneded concatenation of a constant. Remove the "c" call.**
```r
  if (task.type %nin% c("oneclass"))
                      ^
```
[R/plotOutlierProbabilities.R:16:44:](https://github.com/mlr-org/mlr/blob/7960c722d415ffad9bd19c2109a9d71d936f82e3/R/plotOutlierProbabilities.R#L16) *style:* **Commas should always have a space after.**
```r
  prob = getPredictionProbabilities(pred)[,1]
                                           ^
```
[R/plotOutlierProbabilities.R:28:23:](https://github.com/mlr-org/mlr/blob/7960c722d415ffad9bd19c2109a9d71d936f82e3/R/plotOutlierProbabilities.R#L28) *style:* **Commas should always have a space after.**
```r
  df = df[order(prob),]
                      ^
```
[R/plotOutlierProbabilities.R:29:27:](https://github.com/mlr-org/mlr/blob/7960c722d415ffad9bd19c2109a9d71d936f82e3/R/plotOutlierProbabilities.R#L29) *warning:* **Avoid 1:length(...) expressions, use seq_len.**
```r
  df = data.frame(index = 1:length(prob), df)
                          ^
```
[R/plotOutlierProbabilities.R:38:124:](https://github.com/mlr-org/mlr/blob/7960c722d415ffad9bd19c2109a9d71d936f82e3/R/plotOutlierProbabilities.R#L38) *style:* **Put spaces around all infix operators (except exponentiation).**
```r
    aes(shape = factor(truth, levels = c("TRUE", "FALSE"), labels = c("21", "24")), fill = predictedResponse) + guides(fill=FALSE) +
                                                                                ~^~
```
[R/plotOutlierProbabilities.R:43:76:](https://github.com/mlr-org/mlr/blob/7960c722d415ffad9bd19c2109a9d71d936f82e3/R/plotOutlierProbabilities.R#L43) *style:* **Commas should always have a space after.**
```r
  p = p + geom_point(data = sub, aes(x = index, y = probability), size = 2,stroke = 1, color = "white") +
                                                                           ^
```


Calvin, I am unsure of the problem right now. I'm on a road trip for work,
but can investigate afterwards.

On Oct 24, 2017 14:02, "Calvin Wong" <notifications@github.com> wrote:

> whats the reason behind setting the foldmethod to expr?
>
> i am getting the following error when i try to fold -
>
> E350: Cannot create fold with current 'foldmethod'
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/hashivim/vim-hashicorp-tools/commit/9ab028f4bd0754585ef64fc2a90f1f2f118add32#commitcomment-25165311>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ACRa5R5il7YUsNKmdAdx0xieL1Jye388ks5svjQ0gaJpZM4QE7nX>
> .
>


:heart:


It seems I missed it last time. I can see it now. Thanks!


For consistency "... an op"


myLine=myLine.replace("  ", " ");
і не потрібно додаткової локальної змінної


If the abstract class is empty, remove it.


може краще зробити це масивом?


I basically just copied this from the examples on the pygame wiki haha.


Needs [-m flag](https://github.com/oscar-broman/pawn/blob/master/source/compiler/sc1.c#L1064-L1067) to work perfectly


Here the issue: https://github.com/spring-cloud/spring-cloud-consul/issues/365


тоді в нас буде лише  один цикл, нам не потрібно буде дублювати код


Bit too inappropriate IMO - it's also a pretty strong word(in the US)


можна просто
if(m.matches()){


Correct, Laura, you do not need a css file for this assignment. All we need is the xml and dtd files.


hey phil. thanks for the quick reply. ya. no rush at all. i actually just noticed that when i updated the repo. thanks


Can you also make "kali" a debian synonym? Is there any way to work around this in the meantime?


Thanks, makes sense. So, if there are a bunch of different boards from different manufacturers that all use the same BF target (for example, the many that all use the OMNIBUSF4 target), they all would have the same board ID? For some reason, I thought the board ID would differentiate different actual boards, even if they use the same target. Learn something every day... :)


Hm, documentation isn't always 100% up to date. But if it works it works.


Now thats what i call a TEST!
:D


##src


You don't want to have this here.
`get_working_if` calls directly `read_routes` which means, on windows, to re-do the powershell procedure from scratch


If you still have the info from before your git pull, what commit did you
have?

On Oct 24, 2017 14:33, "Calvin Wong" <notifications@github.com> wrote:

> hey phil. thanks for the quick reply. ya. no rush at all. i actually just
> noticed that when i updated the repo. thanks
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/hashivim/vim-hashicorp-tools/commit/9ab028f4bd0754585ef64fc2a90f1f2f118add32#commitcomment-25165973>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ACRa5Yk7kW25jzocg5P4ikyQJQxIC1f2ks5svjuVgaJpZM4QE7nX>
> .
>


@yelizariev just a simple tip. All commits which are fixing an issue, should reference the fix in the Title, like: https://help.github.com/articles/closing-issues-using-keywords/ this way it will keep the issues section a bit cleaner.


Problems with anchors, there are no anchors on the demonstration website, but where you give to the download there are anchors


one file says 3, the other says 4?


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

> set -x;set -e;set -o pipefail;cd /tmp/0pdd20171024-13963-3eav1n/irbuch/codequiz-master && pdd -q -f /tmp/pdd.xml20171024-14012-1b0mujm: pid 14036 exit 255 (not zero): + set -e + set -o pipefail + cd /tmp/0pdd20171024-13963-3eav1n/irbuch/codequiz-master + pdd -q -f...

Please, copy and paste this stack trace to GitHub:

```
set -x;set -e;set -o pipefail;cd /tmp/0pdd20171024-13963-3eav1n/irbuch/codequiz-master && pdd -q -f /tmp/pdd.xml20171024-14012-1b0mujm: pid 14036 exit 255 (not zero):
+ set -e
+ set -o pipefail
+ cd /tmp/0pdd20171024-13963-3eav1n/irbuch/codequiz-master
+ pdd -q -f /tmp/pdd.xml20171024-14012-1b0mujm

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

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


Got it, thanks!


Откуда здесь столько анимешников? Что происходит? ААААААААААААААААААААААААА!!
Why are there so many anime fans? What is going on?
なぜそんなにアニメファンが多いのか。どうなっているのですか。?
为什么有这么多动漫迷？这是怎么回事？


![](https://github.trello.services/images/mini-trello-icon.png) [[3pt] Enabling caching service](https://trello.com/c/PY8do0ss/60-3pt-enabling-caching-service)


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

> set -x;set -e;set -o pipefail;cd /tmp/0pdd20171024-13963-3eav1n/irbuch/codequiz-master && pdd -q -f /tmp/pdd.xml20171024-14375-18icy83: pid 14403 exit 255 (not zero): + set -e + set -o pipefail + cd /tmp/0pdd20171024-13963-3eav1n/irbuch/codequiz-master + pdd -q -f...

Please, copy and paste this stack trace to GitHub:

```
set -x;set -e;set -o pipefail;cd /tmp/0pdd20171024-13963-3eav1n/irbuch/codequiz-master && pdd -q -f /tmp/pdd.xml20171024-14375-18icy83: pid 14403 exit 255 (not zero):
+ set -e
+ set -o pipefail
+ cd /tmp/0pdd20171024-13963-3eav1n/irbuch/codequiz-master
+ pdd -q -f /tmp/pdd.xml20171024-14375-18icy83

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

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


i had this
```
bfed7d02586139e12ba009cc1695ded4de88677c | 2016-07-27 13:44:05 -0400 | [Mark Cornick] (HEAD -> master, origin/master, origin/HEAD) Updating nomad, terraform and vault
fba2218814be31022ad0a88ad9e074371593f1a7 | 2016-05-11 15:12:33 -0400 | [Mark Cornick] Tweak Credits graf slightly
3528db54917fb3d1024d60676e2cfd1142c3d394 | 2016-05-11 14:56:34 -0400 | [Mark Cornick] Rework assemble.sh script
5379d46b2cb760205c599f9c44614f2bd2f9c36b | 2016-05-11 12:24:34 -0400 | [Mark Cornick] Pull in recent vim-terraform changes
```


Bluemix [toolchain](https://dev-console.stage1.bluemix.net/devops/toolchains/ccab4f26-e0fa-4a60-8a8f-ef7c81eb9f2d "UI-clienv-SimpleTC1024T153329"): [Delivery Pipeline](https://dev-console.stage1.bluemix.net/devops/pipelines/4333dfc1-ba01-43b5-b536-1f37df9ad17c "UI-clienv-SimpleTC1024T153329") deployed [UI-clienv-SimpleTC1024T153329](https://github.com/pickforc/UI-clienv-SimpleTC1024T153329/releases/tag/deploy-ibm-ys1-us-south-donuds-gmail.com-dev-20171024-194029 "deploy-ibm-ys1-us-south-donuds-gmail.com-dev-20171024-194029") to [dev](https://console.stage1.bluemix.net/apps/f3fdfa9c-346d-4147-b16e-1bdf8d78cd04?env_id=ibm:ys1:us-south "ibm:ys1:us-south:donuds@gmail.com:dev"), including this commit


@Gounlaf yes, I’m already fixed this, thanks


Ohhh man, that's some old code. Ok :)

On Oct 24, 2017 14:40, "Calvin Wong" <notifications@github.com> wrote:

> i had this
>
> bfed7d02586139e12ba009cc1695ded4de88677c | 2016-07-27 13:44:05 -0400 | [Mark Cornick] (HEAD -> master, origin/master, origin/HEAD) Updating nomad, terraform and vault
> fba2218814be31022ad0a88ad9e074371593f1a7 | 2016-05-11 15:12:33 -0400 | [Mark Cornick] Tweak Credits graf slightly
> 3528db54917fb3d1024d60676e2cfd1142c3d394 | 2016-05-11 14:56:34 -0400 | [Mark Cornick] Rework assemble.sh script
> 5379d46b2cb760205c599f9c44614f2bd2f9c36b | 2016-05-11 12:24:34 -0400 | [Mark Cornick] Pull in recent vim-terraform changes
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/hashivim/vim-hashicorp-tools/commit/9ab028f4bd0754585ef64fc2a90f1f2f118add32#commitcomment-25166096>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ACRa5e4g_nruM6XKZ82n3xt4Pg_9eNdeks5svj0mgaJpZM4QE7nX>
> .
>


`g:test#last_command` seems to be used in tests only, right?
Might be useful to expose in general after all?!


Should be `buffer_appends(dst, "@...");` to be consistent with what we have in `buffer_append_html_generic()`. This check is non-perfect, but let's keep it and the action on it consistent in these two places - or maybe even move them to a separate function (to be called from both places) later.


Didn't mean to push "lumina-fileinfo" yet. It needs more information.


Images aren't bzipped in the build directory, and can't be bzipped when uploading.


Bluemix [toolchain](https://console.bluemix.net/devops/toolchains/059610e3-f56f-4a5e-83d6-339b0e9ee986 "bluemix-event-houston"): [Delivery Pipeline](https://console.bluemix.net/devops/pipelines/6a0b736f-57cb-4546-9111-9fd4cdee8c91 "handouts") deployed [handouts](https://github.com/optimumsun/handouts/releases/tag/deploy-ibm-yp-us-south-NA-COM-CSI-Hybrid-Cloud-Workshops-20171024-194433 "deploy-ibm-yp-us-south-NA-COM-CSI-Hybrid-Cloud-Workshops-20171024-194433") to [Workshops](https://console.bluemix.net/apps/679429d4-47a3-44e8-a6e4-3be3d6da1674?env_id=ibm:yp:us-south "ibm:yp:us-south:NA COM-CSI Hybrid Cloud:Workshops"), including this commit


Thanks for keeping up updated. #794


This commit is unnecessary...

Here is a simple implementation for adding support to PQGrid for an auto Column (rather than just the last column):

// add this override before setting up your grids

        $.widget("paramquery.pqGrid", $.paramquery.pqGrid, {
            // override the pqGrid function that determines what the last visible column is
            _getLastVisibleColIndx: function() {
                var idxColumn;

                // if autoColumn is not defined then call the original function to get the last column
                //  if autoColumn is defined then use it
                if (this.options.scrollModel.autoColumn === undefined)
                    {idxColumn = this._super();}
                else
                    {idxColumn = this.options.scrollModel.autoColumn;}
                return idxColumn;
            }
        });

// then when the scrollModel is defined, include the preferred column index for the value of ‘autoColumn’

objSearch.scrollModel = { autoFit: false, horizontal: false, lastColumn: 'auto', autoColumn: 2}


1º - fixed placing a torch where already was one
2º - improved loading animation
3º - made quit work


thanks, @khaledhosny !


Do we want to call it "panview" or just "pan"?


The following doc(s) have been deployed to the [2304wpred](https://2304wpred-static-docs.pantheonsite.io/docs) Multidev environment:
- [/docs/wordpress-redis](https://2304wpred-static-docs.pantheonsite.io/docs/wordpress-redis)


It's very nice idea. The same could be done for textures. What you think about it?


Hey Melak, good job on the git hub account and repository. in future don't use .zip files in your repositories.


T'es sympa avec des rajouts de tests mais c'est mon taf' ça Alexis..


title case (sorry)


It was only because i'm tagged in this commit and was curious if recent fixes were picked up :slightly_smiling_face:.


* All these points are regarding Redux, you can check out the official documentation [here](http://redux.js.org/) it is really well specified and you can get up and running in almost no time.


The OCI API requires the object data to be in memory?


Fala Marcus, bakana esta idéia e contribuição aí, já alterei no meu aqui, valeu


So do the unlanded adult males in the Nights Watch also get the trait?


![](https://github.trello.services/images/mini-trello-icon.png) [(3) Projects as Filterable Cards [5]](https://trello.com/c/cxUlByB2/44-3-projects-as-filterable-cards-5)


Wow what a USELESS project! You should really just STOP!

<3


Awesome. What's important is that you have a  clear direction defined, and you most definitely do, so please keep moving forward!

On October 24, 2017 11:01:41 AM MDT, Zach Spangler <notifications@github.com> wrote:
>Thanks for the feedback Rochelle, I appreciate the thoroughness and
>thoughtfulness of your feedback. I do have a few ideas for initial
>business projects based on my work experience which I am happy to
>define further. Should I do that in the Milestone 1 html file or just
>keep that in mind moving forward?
>
>Additionally, your insight into what the website should look like will
>definitely be included in the build out of Skapa Development. Front-end
>design is definitely a skill so please continue to let me know if you
>have thoughts on how the UI/UX can be improved. Thanks a billion!
>
>--
>You are receiving this because you are subscribed to this thread.
>Reply to this email directly or view it on GitHub:
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fzachspangler%2Fskapa-development%2Fcommit%2F76e574f2e97f230954cfca630f95d45ce4155a3c%23commitcomment-25162565&data=02%7C01%7Crlewis37%40cnm.edu%7Cc25b67dc8a6f42234fe408d51b00e890%7Cf50e076b86a545f387b03f4d0ec5e94e%7C1%7C0%7C636444613094947663&sdata=Pd4F%2BdCeIaDjuroQoQjxQsEWr4qLSXdT6jYVnHuYVNM%3D&reserved=0

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


Each command should reference a subsystem right? Do I call commands in the OI, which would be the equivalent of the hardware map, or do I do it in robot?


There is no react-dom 15.6.2. The most recent 15.x react-dom is 15.6.1.


what is this shit


Pour les sons audio sur la 1.15 plus tard désolé, Pierre : J'ai bien compris pour le bluetooth ...

Trouve un module compatible 5V et stable avant de me refiler le travail STP.

Il y a une jungle de module : Faire le bon chois dés le début est primordial.

Bonne nuit la Team ?

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

> ??
>
> Le 24 oct. 2017 21:09, "Bracame" <notifications@github.com> a écrit :
>
> > Oui, In engish un nouveau boulot
> >
> > Le Frsky S.PORT en premier (et l'implémentations en driver SPI)
> >
> > A première vu, on le fera.
> >
> > ----- Original Message -----
> > From: pierrotm777 <notifications@github.com>
> > To: Ingwie/OpenAVRc_Dev <OpenAVRc_Dev@noreply.github.com>
> > Cc: Bracame <theingwie@gmail.com>, Comment <comment@noreply.github.com>
> > Date: Tue, 24 Oct 2017 18:54:12 +0000 (UTC)
> > Subject: Re: [Ingwie/OpenAVRc_Dev] Update cabling documentation (3f72018)
> >
> > > Tu veux parler du BT ?
> > >
> > > Le 24 oct. 2017 20:19, "Bracame" <notifications@github.com> a écrit :
> > >
> > > > You love give me newer job !!
> > > > Pff, After the one in course ;-)
> > > >
> > > > —
> > > > You are receiving this because you are subscribed to this thread.
> > > > Reply to this email directly, view it on GitHub
> > > > <https://github.com/Ingwie/OpenAVRc_Dev/commit/
> > 3f7201880bda920ed984d27ccdc3bce4d278c0e5#commitcomment-25164289>,
> > > > or mute the thread
> > > > <https://github.com/notifications/unsubscribe-auth/AHz4Eq_
> > l4YvrzsZghPjPlB64tISQfLbVks5svioggaJpZM4QE33L>
> > > > .
> > > >
> > >
> > >
> > > --
> > > You are receiving this because you commented.
> > > Reply to this email directly or view it on GitHub:
> > > https://github.com/Ingwie/OpenAVRc_Dev/commit/
> > 3f7201880bda920ed984d27ccdc3bce4d278c0e5#commitcomment-25165102
> > >
> >
> > —
> > You are receiving this because you commented.
> > Reply to this email directly, view it on GitHub
> > <https://github.com/Ingwie/OpenAVRc_Dev/commit/3f7201880bda920ed984d27ccdc3bce4d278c0e5#commitcomment-25165465>,
> > or mute the thread
> > <https://github.com/notifications/unsubscribe-auth/AHz4EjTMxpkJlkKzJgnErsSpbnIVxSlkks5svjXRgaJpZM4QE33L>
> > .
> >
>
>
> --
> You are receiving this because you commented.
> Reply to this email directly or view it on GitHub:
> https://github.com/Ingwie/OpenAVRc_Dev/commit/3f7201880bda920ed984d27ccdc3bce4d278c0e5#commitcomment-25165694
>


Criando o método "send_mail_template", para enviar e-mail com template


updatwd successfully


Imports necessários para o envio do e-mail


Assunto do e-mail


Why?


@jjfeng @dawahs would this have cleared things up for ya?


Thank you! I have not noticed.


Cool


(I had forgotten about this code when we "talked" before)


Os dados do contato são passados como objeto para o "context"


No, the 'board ID' is a bit of a misnomer, as it is flashed onto the MCU as part of the firmware. (I.e. if you flashed a BLUEJAYF4 firmware onto a OMNIBUSF4 board, the board Id would identify it as 'BLUEJAYF4'...)


Definição do "template_name", caminho do Template


kod v App class sa nevykona, pretoze nie je deklarovana v application elemente. Application class funguje rovnako ako Aktivita, len je o uroven vyssie


Absolutely, but i would like to wait till after the release, to implement this correctly for all resources.


@basarat do you get notifications for commits like this? If not I can raise issues in the future (presumably you get notifications for those).


I just test it and I got that error.

./now.py
Traceback (most recent call last):
  File "./now.py", line 281, in <module>
    main(sys.argv)
  File "./now.py", line 276, in main
    inventory.generate()
  File "./now.py", line 211, in generate
    self.add_group(target, record[k])
KeyError: 'os'


This function is original code, we didn't touch it. Will squash with related commits so that this change will not be shown.


Bluemix [toolchain](https://console.bluemix.net/devops/toolchains/4c4b2a35-4cfe-4a14-a7b5-99bd64408333 "simple-toolchain-20171023-kho"): [Delivery Pipeline](https://console.bluemix.net/devops/pipelines/8201ceda-63e4-4658-9516-182f83490335 "simple-toolchain-20171023-kho") deployed [simple-toolchain-20171023-kho](https://github.com/wilbertkho/simple-toolchain-20171023-kho/releases/tag/deploy-ibm-yp-us-south-wilbert-us.ibm.com-dev-20171024-020348 "deploy-ibm-yp-us-south-wilbert-us.ibm.com-dev-20171024-020348") to [dev](https://console.bluemix.net/apps/d4892070-1acb-41c4-b8b4-7a39b132e642?env_id=ibm:yp:us-south "ibm:yp:us-south:wilbert@us.ibm.com:dev"), including this commit


Actually working with the request would probably be a lot easier if you switched to the Requests library.


test


##This is a markdown file


Commit should say "remove" not add


TravisCI complains, the link https://.... seems fine, maybe it was temporally down? Run again?
Also, it seems I couldn't approve the pull request as I don't have 'write' access, please check. Are they branch specific?


What's the UITabBarViewController bug?


We always want the content insets to be reset when the safe area insets change.


You might be interested in #1206. After this patch I get the following error:
```
./Expected_trivial.fst(17,4-17,12): (Error) Inferred type of pattern (FStar.Pervasives.Native.option u#0
  ((off:((i:Prims.int{ i >= 0 == true })){ off <= (let Expected_trivial.BSlice len = buf in len) ==
        true }))) is incompatible with the type of the scrutinee (FStar.Pervasives.Native.option u#0
  ((off:((i:Prims.int{ i >= 0 == true })){ off <= (let Expected_trivial.BSlice len = buf in len) ==
        true })))
1 error was reported (see above)
```
instead of "Expected a trivial pre-condition".
(the two types differ only in the bound variable index, I believe).


Added the computation of critical threshold and warning threshold and also the usedthreshold


signal thing doesn't seem to work


# Importing bitcoind database


@metabsd can you share your config file sn_groups and sn _fields lines? They must not contain quotes or spaces. Check the now.ini example in this commit.


#10 closes #10


![](https://github.trello.services/images/mini-trello-icon.png) [fix sprite outlines](https://trello.com/c/cZTd794f/257-fix-sprite-outlines)


using the example config file, i get the following output back.

```
[mittell:~/git/ansible-sn-inventory]$ ./now.py | jq 'del(._meta) | keys[]'                                                                            (master✱)
"dell_inc_"
"esx"
"esx_server"
"foxconn"
"gnu_linux"
"hp"
"linux"
"linux_centos"
"linux_fedora"
"linux_server"
"linux_ubuntu"
"mac_os_10__os_x_"
"os_x_server"
"solaris"
"solaris_server"
"storage_server"
"windows"
"windows_2008_r2_datacenter"
"windows_2008_r2_enterprise"
"windows_2012_r2_standard"
"windows_server"
"xen"
```


- Force trigger is good now. The probably was it accelerating you downwards as well as upwards
.
- Lee made an amazing creature and came up with the idea for the effect of its touch: if it touches you, you jump continually for five seconds.

- Triggers cooldown properly.


Ok


0.0.12 released.


Is it necessary to pass `$this->basename`?


FYI, there was only one place where I deleted the "d", but the diff shows the whole line.


Here for example we are not passing base name.


better


So are you running puppy on android devices? 😮
(or is needed to access them?)


Because it's like we use graphviz so much we need an alias right?


Information like version and authentication is typically handled via headers.  So I would remove this and return it as a response header.


测试


Should this be an array instead of imploded string?


Fixing spacing inside `()`.


Why do we need to push/pop the base name?


consider adding a comment at the top of the method with a link to the problem statement. It will be helpful if you ever need to refer to it in the future.

Something like:

```
Solution to cs50 greedy problem.
https://docs.cs50.net/problems/greedy/greedy.html

Implement a program that calculates the minimum number of coins required to give a user change.
```

(Also, it will help reviewers who may want to follow along 😉 .)


Will do, thanks. I actually didn't know negative zero printed with a minus sign!


@dregad Seems generally on the right track.  I added some comments.


Hey thanks for looking at this! So the only change required to make the script work with Tower was to hard code the path to the config file? I'd like to have the base repo version working with Tower. Is it possible to set environment variables for an external inventory script in Tower? If so couldn't we just use NOW_INI environment variable set to /etc/ansible/now.ini to make it work rather than hard coding the config path?

I've made some updates to fix the additional group and field selections, check out latest commits in: https://github.com/ServiceNowITOM/ansible-sn-inventory


@marcusgilson noted.


🐑  maybe add a newline at the end here so it doesn't run up against the next `printf`?


my first resume


Should CMAKE_POSITION_INDEPENDENT_CODE be default for zlib?
I have issues building OpenCV without specifying this in the toolchain for the same reason.


Any reason to have this be a function rather than a `const`? Or a local variable within the `fileChanged` handler?


Released with 1.4.5


Don't need this anymore, have get_success_url()


This makes sense to me. You need to `openOrReveal` to get the document on the page for the first time. Thereafter you probably want to call `context.revert()` to reload the updated contents from disk.


Hello, I just wanted to start by saying you did a great job designing this feeder and thanks for posting. Second please forgive me if this is the wrong place to post this as I have never used GitHub and couldn't find out how to send you a private message.

I would like to try this project someday but for a Dillon xl650 for just the upper area and not the shuttle parts that feed into the shell plates. I did however notice in the .stl files there was a printed part missing which I believe you called a "hobber" hub. This is the part that connects the plate area to the motor shaft. If you have the file I would be grateful or perhaps dimensions? I am VERY new to 3d printing. Thank you


Integrated compressed_rtf module from https://github.com/delimitry/compressed_rtf


PIC may be enabled everywhere but should not. Discussion and links are here https://github.com/ruslo/hunter/issues/64.


What was this for again?


Hmm, didn't know about that.

Just to confirm, the regex before this change works, right?


coding style: typically variable names are lowercase. Stylistically, I think `change_left` is more conventional.

Here is the coding style guide that Google uses for C++: http://google.github.io/styleguide/cppguide.html#Variable_Names


doing so made the "Failed to start loading" error come up less often?


Hi Osha,
The XML code is flawless. However, it seems that it captures only a small part of your website. Can you incorporate more data elements which reflect a broader coverage of the data that your website handles?


coding style: The starting brace should be on the same line as the `while` or on its own line:

```
while (change_left >= 0.25) {
...
}
```

or

```
while (change_left >= 0.25)
{
...
}
```

http://google.github.io/styleguide/cppguide.html#Conditionals


@hmlnarik does something like this make sense to you at the form?

```
<div class="form-group">
            <label class="col-md-2 control-label" for="actionTokenGeneratedByAdminLifespan" class="two-lines"> Operations: </label>
            <div class="col-md-6 time-selector">
            <select name="actionTokenAttributeSelect" id="actionTokenAttributeSelect" ng-model="actionTokenAttribute">>
                <option ng-repeat="(actionTokenId, value) in actionTokenProviders" value="{{actionTokenId}}">{{actionTokenId}}</option>
            </select>
                <input class="form-control" type="number" required min="1" max="31536000" data-ng-model="realm.attributes[actionTokenId].time"
                       id="{{ 'actionTokenGeneratedByUserLifespan.' + actionTokenId}}" name="{{ 'actionTokenGeneratedByUserLifespan.' + actionTokenId}}">
                <select class="form-control" name="{{ 'actionTokenGeneratedByUserLifespanUnit.' + actionTokenId}}" data-ng-model="realm.attributes[actionTokenId].unit">
                    <option value="Minutes">{{:: 'minutes' | translate}}</option>
                    <option value="Hours">{{:: 'hours' | translate}}</option>
                    <option value="Days">{{:: 'days' | translate}}</option>
                </select>
                <button data-ng-click="unsetDefaultToken(actionTokenId)">Unset and use default value</button>
            </div>
            <kc-tooltip>
                {{:: ('action-token-generated-by-user-override-lifespan.' + actionTokenId + '.tooltip') | translate}}
            </kc-tooltip>
        </div>
```


readmeでコンフリクト


Please make sure to do a PR from your fork of the feedstock in the future. The main reason being you can be sure all the packages will build correctly before they deploy. When pushing a commit some builds may fail and packages will not deploy for them and it will be more work to cleanup than having opened a PR initially.


:sheep: this can be more concisely written as:

```
change_left -= 0.25;
```


The dtd file seems descriptive of the xml data.
In the case you make changes to the xml file, make sure that the dtd file stays in sync with those changes.


Thank you.


Got it, thanks @jakirkham.


This looks great to me! (LGTM!)


@lubien yes, I use a lot.


# # @i was right...

- [ ]

-

`

> [1. ](_**

> url

**_)

`


Yes, I ported it from deoplete's base.py.


Great. I will revert this change then.


Thanks.


notes for refactor: do you think we need a Topic Model?  For db relationship, "an instructor has many courses, and a course can be taught by many instructor (many to many).  "a course can have many comments, but each comment can only belong to one course (one to many)", then "topics can have many comments"


@bradleyayers I trust you. I don't get notifications and don't want them :) :rose:


Bluemix [toolchain](https://console.bluemix.net/devops/toolchains/930db1e5-72cc-42ad-961e-c2ad5a252d2b "simple-toolchain-pkjm"): [Delivery Pipeline](https://console.bluemix.net/devops/pipelines/02b06a5e-f85c-45dc-96e7-f57bc04138d1 "simple-toolchain-pkjm") deployed [simple-toolchain-pkjm](https://github.com/pelanimix/simple-toolchain-pkjm/releases/tag/deploy-ibm-yp-us-south-pelaniMix-Pex-20171024-025557 "deploy-ibm-yp-us-south-pelaniMix-Pex-20171024-025557") to [Pex](https://console.bluemix.net/apps/c8018513-d416-4700-8b6f-972cd5364ee7?env_id=ibm:yp:us-south "ibm:yp:us-south:pelaniMix:Pex"), including this commit


LGTM


and i can't figure it out AAAHHH


@antonmedv :angry: how did that get in there!

`ajv` => `json-stable-stringify` => `jsonify`

ugh!


paging: @epoberezkin


d


Envio do e-mail, juntamente com os parâmetros especificados no método "send_mail_template" que criamos no arquivo "mail.py" do app "core"


I get error.   How fixed this problem ?
Note: I using python 3

Traceback (most recent call last):
  File "C:\Python34\lib\site-packages\imageio\plugins\ffmpeg.py", line 82, in get_exe
    auto=False)
  File "C:\Python34\lib\site-packages\imageio\core\fetching.py", line 102, in get_remote_file
    raise NeedDownloadError()
imageio.core.fetching.NeedDownloadError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:/Users/YuSuF/PycharmProjects/ins/deneme.py", line 1, in <module>
    from InstagramAPI import InstagramAPI
  File "C:\Python34\lib\site-packages\instagram_api-0.1-py3.4.egg\InstagramAPI\__init__.py", line 30, in <module>
    from moviepy.editor import VideoFileClip
  File "C:\Python34\lib\site-packages\moviepy\editor.py", line 22, in <module>
    from .video.io.VideoFileClip import VideoFileClip
  File "C:\Python34\lib\site-packages\moviepy\video\io\VideoFileClip.py", line 3, in <module>
    from moviepy.video.VideoClip import VideoClip
  File "C:\Python34\lib\site-packages\moviepy\video\VideoClip.py", line 21, in <module>
    from .io.ffmpeg_writer import ffmpeg_write_image, ffmpeg_write_video
  File "C:\Python34\lib\site-packages\moviepy\video\io\ffmpeg_writer.py", line 11, in <module>
    from moviepy.config import get_setting
  File "C:\Python34\lib\site-packages\moviepy\config.py", line 35, in <module>
    FFMPEG_BINARY = get_exe()
  File "C:\Python34\lib\site-packages\imageio\plugins\ffmpeg.py", line 86, in get_exe
    raise NeedDownloadError('Need ffmpeg exe. '
imageio.core.fetching.NeedDownloadError: Need ffmpeg exe. You can download it by calling:
  imageio.plugins.ffmpeg.download()

Process finished with exit code 1


Criação do Template


Where do I put the files?


Braucht man wirklich diese antike Version von binutils? Ginge das nicht mit einer aktuelleren?


Definições necessárias para o envio de e-mails


OK. Agree.


Due to architectural differences between the two frameworks, setup and teardown for unittest based tests is performed during the call phase of testing, instead of in the pytest standard.


At least in the SDK they only take a `[]byte` for content (https://github.com/coreos/mantle/blob/master/vendor/github.com/oracle/bmcs-go-sdk/object_storage_objects.go#L195).


From what I'm reading, there's no real way so download files with AJAX. I know @howardav wants a flash message if the download doesn't work, but I'm not sure we can do that right now. It would be good to not deliver bad PDFs though, so how about adding a check in the `download_file` action like this:

```ruby
if File.size(tempfile.path) != 0
  send_file tempfile.path, disposition: :attachment
else
  'Unable to download the file from Phaxio. It may be deleted due to your fax settings.'
end
```


Move Ubuntu rar package


Warum "i686"? Entweder überall x86 oder (auch überall) i386.


> Anyway to another topic.. Jolla's SailfishOS is officially supporting Sony Xperia X phone

Wow, good news :)

---

> Also if you do test kde (...)

Checked right now on Manjaro unstable, 4k display with wallpaper, selecting desktop icons:
- Plasma 5: 250 MiB on startup, when selecting icons - up to 550 MiB of RAM, over 100% (max 800%, 4C8T) CPU core usage and not smooth, ~20% GPU usage 😆,
- Caja (GTK2): ~14 MiB of RAM and ~ 5% CPU usage, ~1% GPU usage (probably Wallpaper is on X-server side),
- My own experimental desktop (Qt5Widgets): ~15% CPU usage, 45 MiB RAM, ~2% GPU usage (wallpaper on application side).

Moreover, Plasma is using ~2% CPU on idle - only clock with seconds and systemoloadviewer on panel. It also reallocates memory too much.


The following doc(s) have been deployed to the [3020drupal](https://3020drupal-static-docs.pantheonsite.io/docs) Multidev environment:
- [/docs/https](https://3020drupal-static-docs.pantheonsite.io/docs/https)


The first commit, a blank readme file.


lo que se hace por una camiseta eh @sephirot47 ? #hacktoberfest #pullRquestsADojo


Couldnt not start project with fresh clone. (Was missing .Host packages)

Reproduce:

Fork/Clone
exec buildAll.cmd
exec start.cmd

Works on fresh clone with thoose additions.


These changes break my build for re-arm


@dsyme Thanks a lot for your work!


This comment line can be removed too, I think


Meant board on the bottom of the screen in my description


`version_aware_buck.py` was the migration path for folks using `.buckversion` - did you guys intend to remove it?


ninja


@ElForastero I think you too forgot something :D


teste de comentario


**Note:** This migration hadn't made it through the pipeline yet so it wasn't applied in any environments.


nice


This can also be private, or an I missing something?


Shouldn't the function signatures here and in the function return type (line 222) match?


I'm using clang. My impression is that compilers normally don't define ``__cplusplus`` as a new version until that language version is essentially fully supported. which means msvc still (or at least for a long time) didn't declare to support c++11. I believe it's common to have small bits appear in versions before the ``__cplusplus`` macro is updated


This is a leftover mention of "DISABLED" - we use "UNPATCHED" nowadays, so this comment should be updated accordingly.

Plus, the #define DISABLED a few lines up can be removed too.


That's more of a runtime thing than a docker thing, this should probably be opened as an issue on Slice's original repo - but if I get this running, I'll do any changes if Slice is too busy!


Latest merge.


another aspect of this is that clang can use both libc++ and libstdc++, which means that the same compiler may sometimes support string_view and sometimes not.


Why the extra `?:`?


Load times before optimizations were on average 20s. Load times after optimizations are now within 500ms on average


pPfp


Can you rename this to parseXYCoordinatesFromName for clarity?


[USF Deployment Guide.xlsx](https://github.com/USF-IT/Archivum-USF/files/1412386/USF.Deployment.Guide.xlsx)

Gac task report is added in the new version


Also, return true if it succeeds and false if it doesn't.


The following doc(s) have been deployed to the [wipedb](https://wipedb-static-docs.pantheonsite.io/docs) Multidev environment:
- [/docs/guides/drupal-8-commerce](https://wipedb-static-docs.pantheonsite.io/docs/guides/drupal-8-commerce)
- [source/docs/assets/images/guides/drupal-8-commerce/git-status.png](https://github.com/pantheon-systems/documentation/commit/3cd8452d98e95f847f285d55c9d2933c84c5c986/source/docs/assets/images/guides/drupal-8-commerce/git-status.png)


branch maybe


Good work, although it's a pity indentation changes obfuscate the actual fix.

We should settle for a indentation style, apply it fully once, and apply it from then on.


Isn’t there a way to call processData only once?


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


My whole architecture is failing with Consul, and I'm starting to have doubt this is caused by this upgrade. I'm testing, but if this fails I will need to rollback.


Should be fixed now


This version is working under Windows (Compiled with Visual Studio)


OK this is confirmed... I lost one hour because of this :-(
So we need to rollback, this just doesn't work


Hooray! It's in!! Thanks guys!


Problem: Files synced on unRAID are unwriteable via samba file sharing. This is due to the umask of 022 instead of 000.


Reverted


Impressive! And in record time!


ugh...yes..


Created multidev environment [d8-commerce-ii#pr-wipe-db](https://dashboard.pantheon.io/sites/70e20c56-bc58-4b4f-96eb-dcbc2356a874#pr-wipe-db).

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


**Issue considerations**

- On project load the menu does not show any tab selection till one is clicked.
- If tab content is set to collapse. On project load the collapse arrow does not point to the right direction .


Hello i'm new here


Snrak!


haha. ya... i know. :-\


P.S. Thank you for the best template :)


Heh, no worries, at least it's fixed. There might be more to pick over to master btw. Might be cool if you could take a peek.


Es cierto. Logré hacer lo que indicas, no fue complejo.
Tengo una duda si me puedes orientar:

El Tag: <xades:SigningCertificate> cuando firma deja un TAG <xades:Cert> que corresponde a la entidad que provee el certificado, pero quiero poner otras entidades que autorizaron el certificado. Es decir, en total 3 tag <xades:Cert> con sus respectivos interiores.
¿Cómo es posible definir más entidades (el certificado las trae)?


Очепятка во втором пункте содержания


doc/Спецификация требований.md

Очепятка


Can I suggest a small change?

> +To render this image it's **highly** recommended to use fast graphics card by enabling OpenCL.
> +Rendering using CPU can be **enormously** long.


Nothing :) When the application is ready, consider adding it to the list in my repository so you can help other users to create their own :smile:


There is a issue regarding sepolicy into BoardConfig.mk
BOARD_SEPOLICY_DIRS := $(LOCAL_PATH)/sepolicy
Please try to replace  $(LOCAL_PATH) with your real path .