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

```
cd /tmp/0pdd/extsoft/insight && pdd -q -f /tmp/pdd.xml20170412-1444-rnphx1: 256 (not zero):
/app/vendor/bundle/ruby/2.2.0/gems/pdd-0.17.3/lib/pdd/source.rb:143:in `rescue in puzzles': ["in /tmp/0pdd/extsoft/insight/git/git-utils.bash", #<PDD::Error: Space expected>] (PDD::Error)
	from /app/vendor/bundle/ruby/2.2.0/gems/pdd-0.17.3/lib/pdd/source.rb:141:in `puzzles'
	from /app/vendor/bundle/ruby/2.2.0/gems/pdd-0.17.3/lib/pdd.rb:97:in `block (3 levels) in xml'
	from /app/vendor/bundle/ruby/2.2.0/gems/pdd-0.17.3/lib/pdd.rb:96:in `each'
	from /app/vendor/bundle/ruby/2.2.0/gems/pdd-0.17.3/lib/pdd.rb:96:in `block (2 levels) in xml'
	from /app/vendor/bundle/ruby/2.2.0/gems/nokogiri-1.6.8.1/lib/nokogiri/xml/builder.rb:391:in `call'
	from /app/vendor/bundle/ruby/2.2.0/gems/nokogiri-1.6.8.1/lib/nokogiri/xml/builder.rb:391:in `insert'
	from /app/vendor/bundle/ruby/2.2.0/gems/nokogiri-1.6.8.1/lib/nokogiri/xml/builder.rb:375:in `method_missing'
	from /app/vendor/bundle/ruby/2.2.0/gems/pdd-0.17.3/lib/pdd.rb:95:in `block in xml'
	from /app/vendor/bundle/ruby/2.2.0/gems/nokogiri-1.6.8.1/lib/nokogiri/xml/builder.rb:293:in `initialize'
	from /app/vendor/bundle/ruby/2.2.0/gems/pdd-0.17.3/lib/pdd.rb:93:in `new'
	from /app/vendor/bundle/ruby/2.2.0/gems/pdd-0.17.3/lib/pdd.rb:93:in `xml'
	from /app/vendor/bundle/ruby/2.2.0/gems/pdd-0.17.3/bin/pdd:90:in `<top (required)>'
	from /app/vendor/bundle/ruby/2.2.0/bin/pdd:23:in `load'
	from /app/vendor/bundle/ruby/2.2.0/bin/pdd:23:in `<main>'

/app/objects/exec.rb:38:in `run'
/app/objects/git_repo.rb:60:in `xml'
/app/objects/puzzles.rb:46:in `deploy'
/app/objects/job.rb:42:in `proceed'
/app/objects/job_starred.rb:35:in `proceed'
/app/objects/job_recorded.rb:33:in `proceed'
/app/objects/job_emailed.rb:36:in `proceed'
/app/objects/job_commiterrors.rb:36:in `proceed'
/app/objects/job_detached.rb:51:in `block in exclusive'
/app/vendor/ruby-2.2.2/lib/ruby/2.2.0/timeout.rb:89:in `block in timeout'
/app/vendor/ruby-2.2.2/lib/ruby/2.2.0/timeout.rb:34:in `block in catch'
/app/vendor/ruby-2.2.2/lib/ruby/2.2.0/timeout.rb:34:in `catch'
/app/vendor/ruby-2.2.2/lib/ruby/2.2.0/timeout.rb:34:in `catch'
/app/vendor/ruby-2.2.2/lib/ruby/2.2.0/timeout.rb:104:in `timeout'
/app/objects/job_detached.rb:49:in `exclusive'
/app/objects/job_detached.rb:39:in `block in proceed'
/app/objects/job_detached.rb:39:in `fork'
/app/objects/job_detached.rb:39:in `proceed'
/app/0pdd.rb:201:in `block in <top (required)>'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1611:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1611:in `block in compile!'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:975:in `[]'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:975:in `block (3 levels) in route!'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:994:in `route_eval'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:975:in `block (2 levels) in route!'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1015:in `block in process_route'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1013:in `catch'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1013:in `process_route'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:973:in `block in route!'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:972:in `each'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:972:in `route!'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1085:in `block in dispatch!'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `block in invoke'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `catch'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `invoke'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1082:in `dispatch!'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:907:in `block in call!'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `block in invoke'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `catch'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `invoke'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:907:in `call!'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:895:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/rack-protection-1.5.3/lib/rack/protection/xss_header.rb:18:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/rack-protection-1.5.3/lib/rack/protection/path_traversal.rb:16:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/rack-protection-1.5.3/lib/rack/protection/json_csrf.rb:18:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.5/lib/rack/logger.rb:15:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.5/lib/rack/commonlogger.rb:33:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:219:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:212:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.5/lib/rack/head.rb:13:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.5/lib/rack/methodoverride.rb:22:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:182:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:2013:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1487:in `block in call'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1787:in `synchronize'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1487:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.5/lib/rack/handler/webrick.rb:88:in `service'
/app/vendor/ruby-2.2.2/lib/ruby/2.2.0/webrick/httpserver.rb:138:in `service'
/app/vendor/ruby-2.2.2/lib/ruby/2.2.0/webrick/httpserver.rb:94:in `run'
/app/vendor/ruby-2.2.2/lib/ruby/2.2.0/webrick/server.rb:294:in `block in start_thread'
```


The sfSkeleton.py is the file where the code is written.
The testcases are in the swLab05Work.py file, that is why this last import and reload the first file as sf.


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

```
cd /tmp/0pdd/extsoft/insight && git reset --hard --quiet && git clean --force -d && git fetch --quiet && git rebase --strategy-option=theirs origin/master: 256 (not zero):
First, rewinding head to replay your work on top of it...
fatal: Could not parse object '23420d66a62b6fc4863442fe66d4d3d42d0b0c18^'
Unknown exit code (128) from command: git-merge-recursive 23420d66a62b6fc4863442fe66d4d3d42d0b0c18^ -- HEAD 23420d66a62b6fc4863442fe66d4d3d42d0b0c18

/app/objects/exec.rb:38:in `run'
/app/objects/git_repo.rb:90:in `pull'
/app/objects/git_repo.rb:67:in `push'
/app/objects/job.rb:41:in `proceed'
/app/objects/job_starred.rb:35:in `proceed'
/app/objects/job_recorded.rb:33:in `proceed'
/app/objects/job_emailed.rb:36:in `proceed'
/app/objects/job_commiterrors.rb:36:in `proceed'
/app/objects/job_detached.rb:51:in `block in exclusive'
/app/vendor/ruby-2.2.2/lib/ruby/2.2.0/timeout.rb:89:in `block in timeout'
/app/vendor/ruby-2.2.2/lib/ruby/2.2.0/timeout.rb:34:in `block in catch'
/app/vendor/ruby-2.2.2/lib/ruby/2.2.0/timeout.rb:34:in `catch'
/app/vendor/ruby-2.2.2/lib/ruby/2.2.0/timeout.rb:34:in `catch'
/app/vendor/ruby-2.2.2/lib/ruby/2.2.0/timeout.rb:104:in `timeout'
/app/objects/job_detached.rb:49:in `exclusive'
/app/objects/job_detached.rb:39:in `block in proceed'
/app/objects/job_detached.rb:39:in `fork'
/app/objects/job_detached.rb:39:in `proceed'
/app/0pdd.rb:201:in `block in <top (required)>'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1611:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1611:in `block in compile!'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:975:in `[]'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:975:in `block (3 levels) in route!'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:994:in `route_eval'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:975:in `block (2 levels) in route!'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1015:in `block in process_route'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1013:in `catch'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1013:in `process_route'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:973:in `block in route!'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:972:in `each'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:972:in `route!'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1085:in `block in dispatch!'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `block in invoke'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `catch'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `invoke'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1082:in `dispatch!'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:907:in `block in call!'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `block in invoke'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `catch'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `invoke'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:907:in `call!'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:895:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/rack-protection-1.5.3/lib/rack/protection/xss_header.rb:18:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/rack-protection-1.5.3/lib/rack/protection/path_traversal.rb:16:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/rack-protection-1.5.3/lib/rack/protection/json_csrf.rb:18:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.5/lib/rack/logger.rb:15:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.5/lib/rack/commonlogger.rb:33:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:219:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:212:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.5/lib/rack/head.rb:13:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.5/lib/rack/methodoverride.rb:22:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:182:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:2013:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1487:in `block in call'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1787:in `synchronize'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1487:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.5/lib/rack/handler/webrick.rb:88:in `service'
/app/vendor/ruby-2.2.2/lib/ruby/2.2.0/webrick/httpserver.rb:138:in `service'
/app/vendor/ruby-2.2.2/lib/ruby/2.2.0/webrick/httpserver.rb:94:in `run'
/app/vendor/ruby-2.2.2/lib/ruby/2.2.0/webrick/server.rb:294:in `block in start_thread'
```


IMAD Simple Blog App made using nodejs & Angularjs frameworks. In database used postgress DBMS. Which loads articles as user scrolls down.
User can add article comment on it. for adding article and commenting user must be logged In.


It's unclear why it does not work (and I think it did work for be when doing the change), but I've reverted this in 413849e32.


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

```
cd /tmp/0pdd/extsoft/insight && git reset --hard --quiet && git clean --force -d && git fetch --quiet && git rebase --strategy-option=theirs origin/master: 256 (not zero):

It seems that there is already a rebase-merge directory, and
I wonder if you are in the middle of another rebase.  If that is the
case, please try
	git rebase (--continue | --abort | --skip)
If that is not the case, please
	rm -fr "/tmp/0pdd/extsoft/insight/.git/rebase-merge"
and run me again.  I am stopping in case you still have something
valuable there.

/app/objects/exec.rb:38:in `run'
/app/objects/git_repo.rb:90:in `pull'
/app/objects/git_repo.rb:67:in `push'
/app/objects/job.rb:41:in `proceed'
/app/objects/job_starred.rb:35:in `proceed'
/app/objects/job_recorded.rb:33:in `proceed'
/app/objects/job_emailed.rb:36:in `proceed'
/app/objects/job_commiterrors.rb:36:in `proceed'
/app/objects/job_detached.rb:51:in `block in exclusive'
/app/vendor/ruby-2.2.2/lib/ruby/2.2.0/timeout.rb:89:in `block in timeout'
/app/vendor/ruby-2.2.2/lib/ruby/2.2.0/timeout.rb:34:in `block in catch'
/app/vendor/ruby-2.2.2/lib/ruby/2.2.0/timeout.rb:34:in `catch'
/app/vendor/ruby-2.2.2/lib/ruby/2.2.0/timeout.rb:34:in `catch'
/app/vendor/ruby-2.2.2/lib/ruby/2.2.0/timeout.rb:104:in `timeout'
/app/objects/job_detached.rb:49:in `exclusive'
/app/objects/job_detached.rb:39:in `block in proceed'
/app/objects/job_detached.rb:39:in `fork'
/app/objects/job_detached.rb:39:in `proceed'
/app/0pdd.rb:201:in `block in <top (required)>'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1611:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1611:in `block in compile!'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:975:in `[]'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:975:in `block (3 levels) in route!'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:994:in `route_eval'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:975:in `block (2 levels) in route!'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1015:in `block in process_route'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1013:in `catch'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1013:in `process_route'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:973:in `block in route!'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:972:in `each'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:972:in `route!'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1085:in `block in dispatch!'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `block in invoke'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `catch'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `invoke'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1082:in `dispatch!'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:907:in `block in call!'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `block in invoke'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `catch'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1067:in `invoke'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:907:in `call!'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:895:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/rack-protection-1.5.3/lib/rack/protection/xss_header.rb:18:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/rack-protection-1.5.3/lib/rack/protection/path_traversal.rb:16:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/rack-protection-1.5.3/lib/rack/protection/json_csrf.rb:18:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.5/lib/rack/logger.rb:15:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.5/lib/rack/commonlogger.rb:33:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:219:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:212:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.5/lib/rack/head.rb:13:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.5/lib/rack/methodoverride.rb:22:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:182:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:2013:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1487:in `block in call'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1787:in `synchronize'
/app/vendor/bundle/ruby/2.2.0/gems/sinatra-1.4.7/lib/sinatra/base.rb:1487:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.5/lib/rack/handler/webrick.rb:88:in `service'
/app/vendor/ruby-2.2.2/lib/ruby/2.2.0/webrick/httpserver.rb:138:in `service'
/app/vendor/ruby-2.2.2/lib/ruby/2.2.0/webrick/httpserver.rb:94:in `run'
/app/vendor/ruby-2.2.2/lib/ruby/2.2.0/webrick/server.rb:294:in `block in start_thread'
```


I'm working on it. Should have it done this afternoon.

Sincerely,
Mikaella Dallal
(210)-846-1248
mik.edgerley@gmail.com

On Apr 12, 2017 12:52 PM, "Kara A Carrell" <notifications@github.com> wrote:

> did you get this solved @medgerle <https://github.com/medgerle> ?
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/medgerle/code-club/commit/0fbb0730644ccea1f51ee96dae3b60443ec4219f#commitcomment-21738018>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AZiiUqbGfVD3KJm5NGL1sMPiSJ6En5uQks5rvQ9ZgaJpZM4M7weJ>
> .
>


Yes it's veeery unlikely but `getActiveNetworkInfo(context).isRoaming()` is the only place in this method where we can get null pointer exception.
`#isUnmetered()` doesn't check anything related with `NetworkInfo` - it calls only `ConnectivityManager` method.


Correct file will be uploaded shortly after class


on large meshes too? strange..


Fixes #876


Commit message: Updated*.
And edit crontab once to what?


Yep.


I see the intent with repeating the heading numbering pattern with the paragraph elements, but [there is only one `<p>` tag](https://developer.mozilla.org/en/docs/Web/HTML/Element#Text_content).

The idea is that `<h1>` through `<h6>` are [headings](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/Heading_Elements) of different levels:

# `<h1>`
## `<h2>`
### `<h3>`
#### `<h4>`
##### `<h5>`
###### `<h6>`

Meanwhile, `<p>`s are all just [paragraphs](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/p).

The numbering in the classes (`.summary-paragraph-1` and `.summary-paragraph-2`) is valid. The question is, is it necessary – meaning: will the two paragraphs receive different styling?

If yes, perfect. One could still argue that `-1` and `-2` are not the most semantic of class name endings (something like `-description` or `-bananas` would be more helpful to our future selves and other devs).

If not, you're good with just assigning both a class of `.summary-paragraph`, and then using the power of [DRY code](https://en.wikipedia.org/wiki/Don%27t_repeat_yourself) by writing one CSS class rule which styles all the paragraphs with that class!

Love the Smarties in a bowl with milk joke.


This could be done with a more specific HTML element.


This could also be done with a more specific element – you could even make it so that it opens your mail program when clicked, [like so](mailto:info@boucher.ch).


Get Life !


+1 as a config file property. Directly accessing DB is non starter in prod environments


Hello @neoeno

We called self on the method as a way of passing the test. It also passed when calling the Class before the method. I realised today that was not needed when I went through my code again and reviewed every step.
Thank you for your feedback as it made me ponder over the self call...


great plugin!


RIP... get the kernel source first xD xD


please update the `test/functional/roles_controller_test.rb` for this one and then verify that the `test/unit/roles_test.rb` is still valid


RE:  05a-python.md
Hello @Dangaia
cc:  @reshama @aramnath @zwmiller @sethhweidman

---

Good job in completing the Python 2 section!  👍
And great job with the markdown!

A link to solutions will be sent out soon.

If you have time, give Markov a try... will prob come in handy later in the course.


says the guy using laos kernel for bullhead


@VanillaSalt what do you last commits do? and how will be these functions used now?


Thought there was only 1 test failing here? Let me give this a full run myself...


Olol

On Apr 12, 2017 11:44 PM, "Kuba Schenk" <notifications@github.com> wrote:

> says the guy using laos kernel for bullhead
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/AOSiP-Devices/device_xiaomi_mido/commit/da4d47a94a3979b9d7e8b90c4452a19472c502b2#commitcomment-21738370>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AJpnfXlPW8lJAPPHBrnrgh9lDK9Y1zdDks5rvRSggaJpZM4M7yCO>
> .
>


that's a very good solution!


example


excellent! Please update the `test/unit/plans_test.rb` so that its working with this changed logic. It should just be a matter of uncommenting the lines that check these permissions. I had initially assumed that they were inclusive.


i am learning git hub bit by bit....as soon as i learn i will teach you


The following doc(s) have been deployed to the [925drupal](https://925drupal-static-docs.pantheonsite.io/docs) Multidev environment:
- [docs/composer-drupal-8](https://925drupal-static-docs.pantheonsite.io/docs/composer-drupal-8)
- [app/config/sculpin_site.yml](https://github.com/pantheon-systems/documentation/commit/db6f9073e7ac9b5691c9c3fc8bb372f97b638422/app/config/sculpin_site.yml)
- [docs/drupal-console](https://925drupal-static-docs.pantheonsite.io/docs/drupal-console)


fix redelivre/delibera#152, esqueci de referenciar o projeto.


Added Core Functions:
* CF03: Plugin can insert an element accurately based on the number of elements and its index. We completely abandoned the old method which uses a built it PHP function to search for a media attachment. The reason for this is it is inconsistent, instead we create an array with a list of video embed criteria (which we can loosely add our custom criteria for ConvertPlayer, Instagram, Facebook, etc)
* CF04: The plugin should be able to search a video and social media embed; with the option to add/filter other media sources (in our case, media added via ConvertPlayer) which is stored in an array.
* CF05: If Video is found, the plugin should be able to find the index of the media from the DOM elements. This index will then later be processed.


RE:  Stats
Hello @joelpaustian
cc:  @reshama @aramnath @zwmiller @sethhweidman

---

Good job in completing the stats section and big 👍  on completing the bonus questions!!!

A link to solutions will be sent out soon.

---

General Comments

Q5: The basic formula for calculating the probability Elvis had an identical twin brother is to estimate the probability of having an identical twin brother and the probability of having a fraternal twin brother. The probability of having an identical twin brother is:
(1/2)(1/300)

The probability of having a fraternal twin brother is:
(1/4)(1/125)

The probability of having an identical twin is the probability of having an identical twin brother over the probability of having a twin brother:
[(1/2)/(1/300)]/[(1/4)(1/25)+(1/2)(1/300)]

This reduces to: 5/11 = 45%

***Key piece of information in this problem is that Elvis Presley had a twin brother. So for fraternal twins, the probability of getting two boys is .5 *.5 = .25 (assuming equal likelihood of getting boy/boy, girl/girl, boy/girl, and girl/boy). The probability of getting twin boys is .5. So it's slightly more likely that Elvis Presley's brother was fraternal (as it's much more likely to be a fraternal twin than an identical one)

Pls see solutions for more detail on Q6


Interesting, never though about this actually. I'll consult with QtNetwork people


Only 1 test failed for me on the rebased branch.


AFN_duct_update (mitchute) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (2527 of 2528 tests passed, 0 test warnings)

 * 1 test had: EIO diffs.
 * 1 test had: ESO big diffs.
 * 1 test had: MTR big diffs.
 * 1 test had: Table big diffs.

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


Yes, the 403 v 404 stuff is not 2.13-specific. Will enter an issue about that one. Thanks.


total 16
-rw-r--r-- 1 jenkins docker 2169 Apr 12 18:22 Jenkinsfile
-rw-r--r-- 1 jenkins docker  244 Apr 12 18:15 main.tf
-rw-r--r-- 1 jenkins docker 3813 Apr 12 18:18 plan
-rw-r--r-- 1 jenkins docker   68 Apr 12 03:35 README.md


It seems to be not working.

```php
$now = Carbon::now();
Carbon::setWeekStartsAt(Carbon::MONDAY);
Carbon::setWeekEndsAt(Carbon::SUNDAY);
$calendar = new Calendar($now->year, $now->month);
```

And in my view:

```php
<?php
$strDays = [
    'Mon' => 'Lun',
    'Tue' => 'Mar',
    'Wed' => 'Mer',
    'Thu' => 'Jeu',
    'Fri' => 'Ven',
    'Sat' => 'Sam',
    'Sun' => 'Dim'
];
?>

<div class="clearfix">
    <?php foreach($calendar->getWeeks()[0]->getDays() as $days): ?>
        <div class="calendar-days-of-week">{{ $strDays[$days->format('D')] }}</div>
    <?php endforeach; ?>
</div>

<div class="calendar-container-content clearfix">
    <?php foreach($calendar->getWeeks() as $week): ?>
        <?php foreach($week->getDays() as $day): ?>
            <div class="calendar-container-content-day">{{ $day->day }}</div>
        <?php endforeach; ?>
    <?php endforeach; ?>
</div>
```


total 16
-rw-r--r-- 1 jenkins docker 2171 Apr 12 18:24 Jenkinsfile
-rw-r--r-- 1 jenkins docker  244 Apr 12 18:15 main.tf
-rw-r--r-- 1 jenkins docker 3813 Apr 12 18:18 plan
-rw-r--r-- 1 jenkins docker   68 Apr 12 03:35 README.md


You need to call `setWeekStartsAt` and `setWeekEndsAt` before using Carbon.

```php
Carbon::setWeekStartsAt(Carbon::MONDAY);
Carbon::setWeekEndsAt(Carbon::SUNDAY);
$now = Carbon::now();
$calendar = new Calendar($now->year, $now->month);
```


I've addressed all of these with https://github.com/KhronosGroup/glTF/pull/910.

@lexaknyazev @McNopper Please review.


May i ask who you are? And what you did here?


Should this key be on GitHub? will it cause it to be abused or should it be hidden or does it matter with this key


This implementation isn't prepared for that at all - this just clarifies the existing implementation to make it very obvious that it takes unquoted names. There's currently no way to provide already quoted identifiers.


AFN_duct_update (mitchute) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed, 0 test warnings)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.png)


RE:  Stats
Hello @mpetuk
cc:  @reshama @aramnath @zwmiller @sethhweidman

---

Good job in completing the stats section  👍

A link to solutions will be sent out soon.

--

General Comments

Great work on Q5, that was was very tricky for most!

Take a look at the solution for Q3, Random Distribution: the distribution looks uniform


Carbon's default is to use Monday as the start of the week, so you won't need to change it at all as far as I can tell (unless it's been set somewhere else in your application).


wtf?


total 16
-rw-r--r-- 1 jenkins docker 2205 Apr 12 18:28 Jenkinsfile
-rw-r--r-- 1 jenkins docker  244 Apr 12 18:15 main.tf
-rw-r--r-- 1 jenkins docker 3813 Apr 12 18:18 plan
-rw-r--r-- 1 jenkins docker   68 Apr 12 03:35 README.md


that is default commit msg when you update on github directly.
made the 2nd change.

On Wed, Apr 12, 2017 at 11:33 PM, Hemant Kumar <notifications@github.com>
wrote:

> Commit message: Updated*.
> And edit crontab once to what?
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/nams05/system_load_cron/commit/3702e01a33a1ddd632ecbd7a45da53ce07b58116#commitcomment-21738219>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AJT1cs3zVUC1NS5cEDggTxcBK2jSlcAtks5rvRHZgaJpZM4M7xSV>
> .
>


Please consider to use %#x instead of %x such that it's clear that the printed numbers are in hexadecimal format instead of in decimal format.


Created multidev environment [demo4-11-2017-3#pr-1dwaynem](https://dashboard.pantheon.io/sites/c654b0e6-f60a-4394-b7fa-d0e0030a68ec#pr-1dwaynem).

[![Visit Site](https://raw.githubusercontent.com/pantheon-systems/ci-drops-8/0.1.0/data/img/visit-site-36.png)](https://pr-1dwaynem-demo4-11-2017-3.pantheonsite.io/)


good point. done... thanks!


done...


Useful information on coode


Hi Endre. As you probably gathered we found the root cause of our problem which was the number of concurrent ECL queries being issued by the template service. When there were over 100 queries running at the same time as classification we experienced a deadlock situation. We have updated the template service with a much kinder strategy and also included the 1 minute timeout on ECL requests. Thank you for your help with this 😺


Complete queries:

UPDATE dbscripts_on_creature_death SET datalong2=1,data_flags=data_flags&~8 WHERE data_flags&8 AND command=15;
UPDATE dbscripts_on_creature_movement SET datalong2=1,data_flags=data_flags&~8 WHERE data_flags&8 AND command=15;
UPDATE dbscripts_on_event SET datalong2=1,data_flags=data_flags&~8 WHERE data_flags&8 AND command=15;
UPDATE dbscripts_on_go_template_use SET datalong2=1,data_flags=data_flags&~8 WHERE data_flags&8 AND command=15;
UPDATE dbscripts_on_go_use SET datalong2=1,data_flags=data_flags&~8 WHERE data_flags&8 AND command=15;
UPDATE dbscripts_on_gossip SET datalong2=1,data_flags=data_flags&~8 WHERE data_flags&8 AND command=15;
UPDATE dbscripts_on_promo_code_use SET datalong2=1,data_flags=data_flags&~8 WHERE data_flags&8 AND command=15;
UPDATE dbscripts_on_quest_end SET datalong2=1,data_flags=data_flags&~8 WHERE data_flags&8 AND command=15;
UPDATE dbscripts_on_quest_start SET datalong2=1,data_flags=data_flags&~8 WHERE data_flags&8 AND command=15;
UPDATE dbscripts_on_spell SET datalong2=1,data_flags=data_flags&~8 WHERE data_flags&8 AND command=15;


done... I also fixed a lot of other spelling mistakes... thanks :)


It looks like this changed in RN 0.42 -- I added a mention of this breaking change to the release notes. I think the release maintainers didn't encounter this issue because they (and the test suites) are using the latest version of Xcode.

Generally speaking, the latest major version of Xcode (e.g. the 8.x releases) is the only supported version. Sometimes when a new version of Xcode has just come out, the older version is supported for awhile but you should upgrade in a timely manner.


total 16
-rw-r--r-- 1 jenkins docker 2177 Apr 12 18:35 Jenkinsfile
-rw-r--r-- 1 jenkins docker  244 Apr 12 18:15 main.tf
-rw-r--r-- 1 jenkins docker 3813 Apr 12 18:18 plan
-rw-r--r-- 1 jenkins docker   68 Apr 12 03:35 README.md


![](https://github.trello.services/images/mini-trello-icon.png) [Nova integração - Prime Consolidadora](https://trello.com/c/cI5quMiO/1233-nova-integracao-prime-consolidadora)


Ops, maybe "translation" is better...


That's hope so


total 16
-rw-r--r-- 1 jenkins docker 2183 Apr 12 18:38 Jenkinsfile
-rw-r--r-- 1 jenkins docker  244 Apr 12 18:15 main.tf
-rw-r--r-- 1 jenkins docker 3813 Apr 12 18:18 plan
-rw-r--r-- 1 jenkins docker   68 Apr 12 03:35 README.md


Should we also be updating https://github.com/mfem/mfem/blob/master/doc/CodeDocumentation.conf.in#L41?


Todos os mecânicos disponível no merca de aeronaves e sua localização.


Why did you drop support for Racket 6.0?


It's not working :/. For 2017-05 is working because the first day for the month is `1` but every other mont start à sunday.


total 16
-rw-r--r-- 1 jenkins docker 2175 Apr 12 18:40 Jenkinsfile
-rw-r--r-- 1 jenkins docker  244 Apr 12 18:15 main.tf
-rw-r--r-- 1 jenkins docker 3813 Apr 12 18:18 plan
-rw-r--r-- 1 jenkins docker   68 Apr 12 03:35 README.md


it is the full code


total 16
-rw-r--r-- 1 jenkins docker 2176 Apr 12 18:42 Jenkinsfile
-rw-r--r-- 1 jenkins docker  244 Apr 12 18:15 main.tf
-rw-r--r-- 1 jenkins docker 3813 Apr 12 18:18 plan
-rw-r--r-- 1 jenkins docker   68 Apr 12 03:35 README.md


I added an option to disable the use of SRI. Use `disable_sri = true` in your config. Have fun. 😄


total 16
-rw-r--r-- 1 jenkins docker 2165 Apr 12 18:43 Jenkinsfile
-rw-r--r-- 1 jenkins docker  244 Apr 12 18:15 main.tf
-rw-r--r-- 1 jenkins docker 3813 Apr 12 18:18 plan
-rw-r--r-- 1 jenkins docker   68 Apr 12 03:35 README.md


@dmadisetti how dost thou like this?


Does killServers() kill everything off?  At first I was thinking it wouldn't kill anything kicked off in the background by users, but maybe having proot die kills all of them, since everything is being ptraced by proot.  If that works, that is great.  The only gotcha will be that we need to kill the servers and go kill the vnc client if running and the terminal windows if open.


Primer ejercicio básico de una Activity
========================

En este ejercicio se pueden observar la construcción de una Activity desde el manejo de los diferentes Layouts, TextViews, ImageViews, EditText

Captura
---------


my Leave a comment


My bad, try-except


You can actually leverage on `context.request.path` ([HTTP::Request#path](https://crystal-lang.org/api/0.21.1/HTTP/Request.html#path-instance-method))and avoid the Regex entirely.


xomment


In startServers() you probably need to handle sshLaunch and vncLaunch in the same function, because you will need to kick off proot with either or both enabled via the same script.


It's not working because the first day of the month is not a monday everytime so I don't know how to display my calendar like this with monday as the first column.

In my screenshot `Avril` is `April` and `Dim` is `Sunday`, `Lun` is `Monday`

![image](https://cloud.githubusercontent.com/assets/1011503/24973949/ec74e4f0-1fc0-11e7-88e6-d4e25676d032.png)


nice cleanup


Hello.

Could you please explain to us what is the rationale to enforce this behaviour? Right now this is causing huge issues in some of our production systems as new periods can be blocked if the have cancel some entries for example and don't want to delete them due to auditing concerns.

Could you please revert this commit? This is new business logic that shouldn't be ported to stable branches such as 9.0 or 10.0.

Thanks!


komentarz


This is based on the suggestion from minefold/hubot-minecraft#1


Have/can you update the build rootfs script, or similar, to take care of generating these?  This will be important if/when I need to recompile these.


Thanks @mcslao! Was having trouble with passing earlier, and thought I might have been in the wrong directory. It's cleared up now.


[Иконка](http://www.flaticon.com/free-icon/calendar-spring-and-squares-interface-symbol_42455)


Убрать дубль


Created multidev environment [demo4-11-2017-3#ci-4](https://dashboard.pantheon.io/sites/c654b0e6-f60a-4394-b7fa-d0e0030a68ec#ci-4).

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


It broke when I refactored the objectives component for record books

-Ben

> On Apr 12, 2017, at 7:54 AM, kyle shay <notifications@github.com> wrote:
>
> Interesting, how did this crop up now? Did a blame, and it looks like the display property wasn't there as of 3 months ago?
>
> ―
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub, or mute the thread.
>


How odd. I am able to reproduce in the tests, so I will work on a fix.


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

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


я тут ничего не понял))


Agree on this. Thanks for the changes,


It was a choice between Known Criminal and Known Crazy. We chose Known Crazy on the ever-so-slim hope that it might just be crazy enough to work. Looks like, once again, Hope isn't a strategy and it's business as usual.

I came here because the political comment at the end of BFG's output surprised me and left a poor taste in my mouth, but I recognize it's @rtyley's (highly useful) project and, like @cphoover says, any one of us is free to maintain a fork.


this method is missing its `self` parameter, so neither this nor its counterpart in the `Net` class (which calls this) can succeed in all cases


This currently only works by coincidence. `packed` is just a modifier, not a representation of its own. Should be`#[repr(C, packed)]`.


A few times too many, I've felt embarrassed that one of my packages shows up as "has dependency problems". So I wanted my day-to-day local development, as well as Travis CI checks, to check for mistakes in under- or over-declaring `deps` and `build-deps`.

To do that, I need to use `--check-pkg-deps` and `--unused-pkg-deps`, which were introduced in 6.1.

6.0 and 6.0.1 are old enough now that I didn't think too hard about this.

But was I too cavalier -- does this break something for you?

If so, (a) sorry! and (b) I could try to make the deps check optional based on `RACKET_VERSION` in the Makefile.


To make the implication of that last sentence explicit: And therefore restore support for 6.0 and 6.0.1.


Honestly, this is such a messy topic that I'd prefer someone who is an expert in these flesh it out.


Beware that the configuration needs to point to the redis sentinels, not the redis servers.
predis will talk to the sentinels and automatically update the config.

This should be made clear in the docs, IMHO.

Thanks for the merge!!


@BobDoguko2016, if you mean that you'd like to have that output from the controller without calling the View, it's Content(). (I think!  :) )


I'm getting build issues unrelated to this branch. Some recently implemented cards were using the old way I presume and just need to be adjusted as well.


If this was instead:

```r
format = "html_document",
output_options = list(
   toc = TRUE,
   self_contained = FALSE,
   theme = NULL,
   template = path
)
```

Then users would be able to add additional options (e.g. df_print, include HTML before/after the body, etc.) either inside the document YAML or in an "_output.yml" file in the same directory. If you pass a fully constructed  format (as you do here) rather than a format name then none of these user options can be specified.

Note that I believe that anything you specify in `output_options` will override whatever the user has specified so this wouldn't be a back door way to do things you don't want them to do (e.g. include a theme, set `toc = FALSE`, etc.)


![](https://github.trello.services/images/mini-trello-icon.png) [Includer: testa](https://trello.com/c/IJRQB0JU/10-includer-testa)


Adding these 2 flags seem to make the cluster unhealthy according to `kubectl get componentstatuses`
```
NAME                 STATUS      MESSAGE                                                                     ERROR
scheduler            Healthy     ok
controller-manager   Healthy     ok
etcd-0               Unhealthy   Get https://172.27.19.229:2379/health: remote error: tls: bad certificate
etcd-2               Unhealthy   Get https://172.27.19.231:2379/health: remote error: tls: bad certificate
etcd-1               Unhealthy   Get https://172.27.19.230:2379/health: remote error: tls: bad certificate
```
Maybe related to this: https://github.com/kubernetes/kubernetes/pull/39716 ?


You're absolutely right! I would be happy to accept a PR for this :).


Homework Lecture 2


по заданию функция должна возвращать площадь и периметр.


this fixes #40.


![](https://github.trello.services/images/mini-trello-icon.png) [Alterações na emissão de seguro](https://trello.com/c/15o6Hj3s/1177-alteracoes-na-emissao-de-seguro)


As I mentioned in the chat:

all, I can not build the current master, due to the move change of ComparisonType and the removal of CountType
obviously this happened due to the fact that development was done on the master branch while the PR was pending
thus is was not rebased on the HEAD
pushing a branch to resolve this. recompiling and running all tests now.


![](https://github.trello.services/images/mini-trello-icon.png) [Danmaku font](https://trello.com/c/3CamX85d/11-danmaku-font)


Both `902221` and `QuoteNode(902221)` are valid IR. Unless we want to change that, which one we produce is an implementation detail and people have to handle both.


Sure; I'll update that patch shortly. Thanks.

On Wed, Apr 12, 2017 at 2:28 PM, Bart Van Assche <notifications@github.com>
wrote:

> Please consider to use %#x instead of %x such that it's clear that the
> printed numbers are in hexadecimal format instead of in decimal format.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/linux-rdma/rdma-core/commit/080863af7acdb0b03c00d253800a9a1195edc307#commitcomment-21738578>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AC2_GO3k9NLjfY18XP6O11_TIPSVf9BZks5rvRfigaJpZM4M7zHl>
> .
>


@killerwife
You should have broken this commit down into many parts.
Now it's kind of difficult for someone who reads the code, to understand what changes are related to which point from the description.

Also, would be nice to see some examples for the changes that you implemented. That would also help us understand it better.


Another ten lines or so.. Because we don't store gasp table the same was as the spec `gaspRange[7].rangeMaxPPEM`.  So need custom code; otherwise some use of eval could do it. Will get on it soon.  Would be nice if we can get some tests for these.


These changes have been overwritten


Hi. Don't you remember why you've added this version of libdbd-mysql-perl?
It is available only in xenial repository of Ubuntu. And I'm wondering what features will I loose if I'll use 4.025 version of this package.


These Changes have been overwritten


Hopefully this addresses the coverage concern. I reorganized slightly, and added one more scenario for when `replace_<type>?` is undefined.


@redpixr https://unsplash.com/photos/E4944K_4SvI


is appveyor enabled here?


You can check heroku URL of my project to see if it is works.


I guess it got missed. I just enabled it and added the badge.


As the guys who introduced the bug, first of all sorry !
Frankly I don't really know how I could pay so little attention (indent, p letter, and not best solution to problem !). Probably because I did it a more direct (dirty) hack on my work Windows machine when stumbling on the problem and only later suggested a change from home (not Windows)...

The reason for the change is:
If you run ptrepack on a windows machine with absolute source and destination filenames, say F:\path\to\this\folder and F:\path\to\that\folder, then the command will fail as the args.src.split(':') will separate the F from the rest of the path.
On Windows the .split(':') is irrelevant as it cannot separate file names, so a change could be something like:

`````
[instead of lines 429-430]
import sys
if 'win' in sys.platform():
    # the file separator for windows is deemed ','
    src = args.src.split(',')
    dst = args.dst.split(',')
else:
    # the file separator for osx, linux for  is deemed ':'
    src = args.src.split(':')
    dst = args.dst.split(':')
`````

Would that make sense ?


Finally!


Refer this [link](http://askubuntu.com/a/145626/412917) for source and more instruction.


It was broken into many parts. This is on @cyberium .


Well, `curl/fetchurl` can optionally depend on it, instead of our default `openssl`.  Still, I think bootstrapping should always be able to avoid `gnutls` – even if it would mean using lighter than default configurations for the bootstrap-intermediate packages.


Hmmm, this seems wrong... Are we absolutely sure the structure layout is correct? As is, 64b fields in the ELF64 section table are misaligned, which feels like a very wrong thing to do.


Answer to myself: I think it is because of ipv6.
Found this https://metacpan.org/changes/distribution/DBD-mysql
```
2014-08-01 Patrick Galbraith, Michiel Beijen, DBI/DBD community (4.028)
<...>
* Update mysql.pm to work with ipv6 and ipv4 addresses (katyavoid)
```


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


@matt-the-wizard There should also be an update to the `yarn.lock` file committed with this. Did you install it via `npm install material-ui` instead of `yarn add material-ui`. We should add dependencies with yarn and commit the `yarn.lock` file also.


TeamCity Glyssen :: Glyssen pull requests [Build *.*.538.e30580ddd781e175cbe6ee29c4e2751c164eb4e4](http://build.palaso.org/viewLog.html?buildId=87803&buildTypeId=Glyssen_GlyssenPullRequests) outcome was **SUCCESS**
Summary: Tests passed: 1674, ignored: 18 Build time: 00:07:38


I think this was added for support of ipv6 addresses.
https://rt.cpan.org/Public/Bug/Display.html?id=70640


This should be fixed now.

It turns out that package-lock violations can be triggered by the expansion of inline functions, not just macros.


Change from localhost to static IP address


add namespace API in routing


Bluemix toolchain: An unknown tool deployed [testRepo-Traceability](https://github.com/idsdev/testRepo-Traceability/releases/tag/deployed-2-env-w3ibm-prod-us-south-user-ibm.com-prod-20170412-193133 "deployed-2-env-w3ibm-prod-us-south-user-ibm.com-prod-20170412-193133") to [prod](http://localhost:3100/apps/6e3bc311-c83d-4cd1-a457-99d9a5f20f19 "w3ibm:prod:us-south:user@ibm.com:prod"), including this commit


Bluemix toolchain: An unknown tool deployed [testRepo-Traceability](https://github.com/idsdev/testRepo-Traceability/releases/tag/deployed-2-env-w3ibm-prod-us-south-user-ibm.com-prod-20170412-193138 "deployed-2-env-w3ibm-prod-us-south-user-ibm.com-prod-20170412-193138") to [prod](http://localhost:3100/apps/6e3bc311-c83d-4cd1-a457-99d9a5f20f19 "w3ibm:prod:us-south:user@ibm.com:prod"), including this commit


Bluemix toolchain: An unknown tool deployed [testRepo-Traceability](https://github.com/idsdev/testRepo-Traceability/releases/tag/deployed-2-env-Prod-20170412-193141 "deployed-2-env-Prod-20170412-193141") to [Prod](http://localhost:3100/apps/6e3bc311-c83d-4cd1-a457-99d9a5f20f19 "There was a problem retrieving the space name"), including this commit


I'm seeing this same failure on master


Hello Daniel.
I'm thinking about to write own class for illumination sensor. I'm not strong in python. I have one question. There is property should_poll. It can be true or false. But I can't find polling function. Is it on HASS side? This is something part of sensor platform?


I'm not sure… It's been a long time since I wrote this code. It seems to work though.

I just saw that you opened #28, let's move discussion there.


Sorry but this is slightly incorrect. What has changed is the HSTS headers are now always getting setting in the subprocesses. Because they are ignored in HTTP when a plain HTTP subproc serves them on `80`. Notably they will never be sent on a tor connection.


Hi Vidya,

You have overwritten all my changes in index.ejs as you can see above. Please stop using force push and always do a pull request to get the latest code from github to merge your changes into.


Distortions?


Just curious: what's the reason for the ` @SuppressWarnings("nullness")` on each of these fields?


Hey Felix,
Sorry for the delay and no problem at all. I'm not sure whether finding
such a small typo warrants me earning the title of contributor. So, perhaps
you change this one and if I find another then I'll take you up on your
offer :-)

Let's catch up for a coffee when you have time.

Have a nice Easter,
Andy

On 7 April 2017 at 20:28, Felix Henninger <notifications@github.com> wrote:

> This is a great find, thank you for not only going through the
> documentation, but also checking for typos! Would you like to make a pull
> request? (Please also be invited to add yourself to the contributor list
> while you're at it) If you'd rather not, I'm happy to make the changes and
> credit you if it saves you trouble.
>
> Thanks again for your help, I really appreciate it!
>
> -Felix
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/shiroandy/lab.js/commit/2d346caabe7dadfc3b148a107c94dda58a8f8d81#commitcomment-21680649>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AD2cWYgcJI8sWO64yvpF143pAuFVaIwfks5rtoA0gaJpZM4M3PFa>
> .
>


Bluemix toolchain: An unknown tool deployed [testRepo-Traceability](https://github.com/idsdev/testRepo-Traceability/releases/tag/deployed-2-env-w3ibm-prod-us-south-user-ibm.com-prod-20170412-193354 "deployed-2-env-w3ibm-prod-us-south-user-ibm.com-prod-20170412-193354") to [prod](http://localhost:3100/apps/6e3bc311-c83d-4cd1-a457-99d9a5f20f19 "w3ibm:prod:us-south:user@ibm.com:prod"), including this commit


Bluemix toolchain: An unknown tool deployed [testRepo-Traceability](https://github.com/idsdev/testRepo-Traceability/releases/tag/deployed-2-env-w3ibm-prod-us-south-user-ibm.com-prod-20170412-193400 "deployed-2-env-w3ibm-prod-us-south-user-ibm.com-prod-20170412-193400") to [prod](http://localhost:3100/apps/6e3bc311-c83d-4cd1-a457-99d9a5f20f19 "w3ibm:prod:us-south:user@ibm.com:prod"), including this commit


Bluemix toolchain: An unknown tool deployed [testRepo-Traceability](https://github.com/idsdev/testRepo-Traceability/releases/tag/deployed-2-env-Prod-20170412-193404 "deployed-2-env-Prod-20170412-193404") to [Prod](http://localhost:3100/apps/6e3bc311-c83d-4cd1-a457-99d9a5f20f19 "There was a problem retrieving the space name"), including this commit


Bluemix toolchain: An unknown tool deployed [testRepo-Traceability](https://github.com/idsdev/testRepo-Traceability/releases/tag/deployed-2-env-w3ibm-prod-us-south-user-ibm.com-prod-20170412-193412 "deployed-2-env-w3ibm-prod-us-south-user-ibm.com-prod-20170412-193412") to [prod](http://localhost:3100/apps/6e3bc311-c83d-4cd1-a457-99d9a5f20f19 "w3ibm:prod:us-south:user@ibm.com:prod"), including this commit


> But was I too cavalier -- does this break something for you?

Yes. Pollen depends on Markdown, and heretofore has supported 6.0. So if `markdown` drops support for 6.0, Pollen must also. (And this will be true for any package that depends on `markdown`)

If there were a good user-facing reason for it, I’d say fine, that’s the price of progress, etc.

But if it’s strictly Hendershott-facing, then yes I would agree with making your deps check optional.

FWIW I hear from people who use Racket 6.0 — released [Feb 2014](http://blog.racket-lang.org/2014/02/racket-v60.html) — so it does have an audience.


This is Task 65 and 66.


`_(:з」∠)_` sorry


We can talk about this, but not sure I agree with the class names added throughout the file.


This was helpful testing code. I am fine for the cleanup. Will archive locally....


Hi Vidya,

You have overwritten all my changes in index.ejs as you can see above line 1003 from old file and 1047 new file after your changes. Please stop using force push and always do a pull request to get the latest code from github to merge your changes into.


This is tasks 102.


![](https://github.trello.services/images/mini-trello-icon.png) [Address console errors](https://trello.com/c/ivL8KgbO/69-address-console-errors)


Thanks :octocat:


Can you please enable issues on this repository?


Should session variables be handled on the client side and not the server?


This is not really a NavBar; it is too specific in the case it is being used. We should consider renaming it to something like MainApplicationBar or something more appropriate to what it actually represents.


OK. I already went ahead and started to work on this, just in case. [This commit](https://github.com/greghendershott/rackjure/commit/a24ad046e7acb1d21b3abb7f25b1c7668efcdab0) is for rackjure, because markdown depends on that. If Travis approves I'll merge that in rackjure, then do similar for markdown.


Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.

The Terraform execution plan has been generated and is shown below.
Resources are shown in alphabetical order for quick scanning. Green resources
will be created (or destroyed and then created if an existing resource
exists), yellow resources are being changed in-place, and red resources
will be destroyed. Cyan entries are data sources to be read.

Your plan was also saved to the path below. Call the apply subcommand
with this plan file and Terraform will exactly execute this execution
plan.

Path: plan

+ aws_instance.example
    ami:                         ami-a58d0dc5
    associate_public_ip_address: <computed>
    availability_zone:           <computed>
    ebs_block_device.#:          <computed>
    ephemeral_block_device.#:    <computed>
    instance_state:              <computed>
    instance_type:               t2.micro
    ipv6_addresses.#:            <computed>
    key_name:                    <computed>
    network_interface_id:        <computed>
    placement_group:             <computed>
    private_dns:                 <computed>
    private_ip:                  <computed>
    public_dns:                  <computed>
    public_ip:                   <computed>
    root_block_device.#:         <computed>
    security_groups.#:           <computed>
    source_dest_check:           true
    subnet_id:                   <computed>
    tenancy:                     <computed>
    vpc_security_group_ids.#:    <computed>

Plan: 1 to add, 0 to change, 0 to destroy.


y


" Ввод условий


Ok think I get it now... good work!


Don't want to jinx it, but this seems strong enough to be an ELO improvement patch.


I see. The limitation makes sense. I think I'd prefer a no-op over an arbitrary translation, though.


[0mRefreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.

The Terraform execution plan has been generated and is shown below.
Resources are shown in alphabetical order for quick scanning. Green resources
will be created (or destroyed and then created if an existing resource
exists), yellow resources are being changed in-place, and red resources
will be destroyed. Cyan entries are data sources to be read.

Your plan was also saved to the path below. Call the apply subcommand
with this plan file and Terraform will exactly execute this execution
plan.

Path: plan

+ aws_instance.example
    ami:                         ami-a58d0dc5
    associate_public_ip_address: <computed>
    availability_zone:           <computed>
    ebs_block_device.#:          <computed>
    ephemeral_block_device.#:    <computed>
    instance_state:              <computed>
    instance_type:               t2.micro
    ipv6_addresses.#:            <computed>
    key_name:                    <computed>
    network_interface_id:        <computed>
    placement_group:             <computed>
    private_dns:                 <computed>
    private_ip:                  <computed>
    public_dns:                  <computed>
    public_ip:                   <computed>
    root_block_device.#:         <computed>
    security_groups.#:           <computed>
    source_dest_check:           true
    subnet_id:                   <computed>
    tenancy:                     <computed>
    vpc_security_group_ids.#:    <computed>

Plan: 1 to add, 0 to change, 0 to destroy.


Most likely this reverts low hissing sound when sound is played.


Okay, that definitely seems important to address since those are two very common paths to go with using React. However, I am torn about formally including it, as it not only begins to make the boilerplate a bit opinionated (which may not be a bad thing), but also adds some potentially confusing complexity that could throw off a newcomer. I'm leaning towards leaving this as is, and then including some documentation for using react-router/Redux. Thoughts?


good-call, and welcome back to es5 lalaland ; )


Does Redbox support entail more than just the Red Screen of Death errors? Because even without those, the Red Screen of Death still shows for runtime errors.


We need to track down why this did not trigger and error/warning and see how NC+ handles such actions.


Not sure why this let me push directly to the main repo but that's fine.


Bluemix toolchain: An unknown tool deployed [testRepo-Traceability](https://github.com/idsdev/testRepo-Traceability/releases/tag/deployed-2-env-w3ibm-prod-us-south-user-ibm.com-prod-20170412-194720 "deployed-2-env-w3ibm-prod-us-south-user-ibm.com-prod-20170412-194720") to [prod](http://localhost:3100/apps/6e3bc311-c83d-4cd1-a457-99d9a5f20f19 "w3ibm:prod:us-south:user@ibm.com:prod"), including this commit


Bluemix toolchain: An unknown tool deployed [testRepo-Traceability](https://github.com/idsdev/testRepo-Traceability/releases/tag/deployed-2-env-w3ibm-prod-us-south-user-ibm.com-prod-20170412-194726 "deployed-2-env-w3ibm-prod-us-south-user-ibm.com-prod-20170412-194726") to [prod](http://localhost:3100/apps/6e3bc311-c83d-4cd1-a457-99d9a5f20f19 "w3ibm:prod:us-south:user@ibm.com:prod"), including this commit


Bluemix toolchain: An unknown tool deployed [testRepo-Traceability](https://github.com/idsdev/testRepo-Traceability/releases/tag/deployed-2-env-Prod-20170412-194728 "deployed-2-env-Prod-20170412-194728") to [Prod](http://localhost:3100/apps/6e3bc311-c83d-4cd1-a457-99d9a5f20f19 "There was a problem retrieving the space name"), including this commit


Bluemix toolchain: An unknown tool deployed [testRepo-Traceability](https://github.com/idsdev/testRepo-Traceability/releases/tag/deployed-2-env-w3ibm-prod-us-south-user-ibm.com-prod-20170412-194738 "deployed-2-env-w3ibm-prod-us-south-user-ibm.com-prod-20170412-194738") to [prod](http://localhost:3100/apps/6e3bc311-c83d-4cd1-a457-99d9a5f20f19 "w3ibm:prod:us-south:user@ibm.com:prod"), including this commit


need to launch these activities using handler.post(new Runnable ...


@copumpkin: what (temporary) approach do you suggest now on staging so we don't block it?


Is this declaration necessary?


ShiftControl

C#, CleanCode, MVC, UnitTest, DDD, TDD, Moq,, EntityFramework, Migrations, SQL Server


It makes sense!

To really fix this, we need;
 - An issue that describes the problem as above (so this issue does not get forgotten).
 - A PR that fixes this, including a testcase that actually tests this behaviour so we are sure it does not break windows/linux/OSX builds.


TeamCity Code :: 1. Development :: DDK :: Feature [Build 252](http://mp-ci.centralus.cloudapp.azure.com/viewLog.html?buildId=20080&buildTypeId=Code_Development_Ddk_Feature) is now running


I wasn't getting Red Screen of Death runtime errors on hot reload?


I probably didn't make it clear, sorry!

The following is how it works if you need to log errors, messages can't use %s and such and have to be concat'ed if you pass an error.

logging.Error("Error deleting pufferd template folder, stored in " + config.Get("templatefolder"), err)


AFN_duct_update (mitchute) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: OK (1895 of 1895 tests passed, 0 test warnings)

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


Nothing to see here, folks. Just move along.


TeamCity Code :: 1. Development :: DDK :: Feature [Build 252](http://mp-ci.centralus.cloudapp.azure.com/viewLog.html?buildId=20080&buildTypeId=Code_Development_Ddk_Feature) outcome was **SUCCESS**
Summary: Tests passed: 51 Build time: 00:01:16


AFN_duct_update (mitchute) - x86_64-Linux-Ubuntu-14.04-custom_check: OK (0 of 0 tests passed, 0 test warnings)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.png)


Letiltottam a buildCachet mert a c:\users\felhasználónév mappába rakja a buildCache mappát a felhasználónevem meg ékezetes ésez kiakasztja :(


Change to regex
regex101


Interesting. If I run through the setup with this branch, and call ```notAFunction()``` in ```main.js``` or even ```app.jsx```, I get the RSoD.


OK so for 6.0 it's not merely you have to use `#lang setup/infotab`, it's also that the Racket version requirement can't be on `base`, it has to be on `racket`.  With that change, [6.0 passes again](https://travis-ci.org/greghendershott/rackjure/jobs/221482779).


something
 something else


It's up to you. I included it because I figured that `App` would inevitably contain routes. I'm not sure if this is required for React Router V4 but I have no experience with that version. It's substantially different from V2.


I may as well as just do that -- roll that `info.rkt` all the way back to where it works again on 6.0 -- for both rackjure and markdown.


I will wait your fix ;)


I would do it another way. I find this way dangerous, because someone may use `ncGenesisLeaders <$> getNodeContext` instead of `genesisLeadersM`. Why not change initialization?


Just realized, this won't work on linux, so it can't be in the root code.

For now, I'll let it work, but we'll have to make a note to fix this.


Thank you


good example for using built-in functions. 👍


That doesn't look right. It assumes the prefix length is a multiple of 8. The subnet/host boundary does not necessarily lie on a byte boundary.


I am tempted to go with using react-router by default, and then this would definitely make sense. For now, I think I am going to go with the simpler setup.


Use consistent spacing, either all spaces or all tabs.


👍 /o/


Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.

The Terraform execution plan has been generated and is shown below.
Resources are shown in alphabetical order for quick scanning. Green resources
will be created (or destroyed and then created if an existing resource
exists), yellow resources are being changed in-place, and red resources
will be destroyed. Cyan entries are data sources to be read.

Your plan was also saved to the path below. Call the apply subcommand
with this plan file and Terraform will exactly execute this execution
plan.

Path: plan

+ aws_instance.example
    ami:                         ami-a58d0dc5
    associate_public_ip_address: <computed>
    availability_zone:           <computed>
    ebs_block_device.#:          <computed>
    ephemeral_block_device.#:    <computed>
    instance_state:              <computed>
    instance_type:               t2.micro
    ipv6_addresses.#:            <computed>
    key_name:                    <computed>
    network_interface_id:        <computed>
    placement_group:             <computed>
    private_dns:                 <computed>
    private_ip:                  <computed>
    public_dns:                  <computed>
    public_ip:                   <computed>
    root_block_device.#:         <computed>
    security_groups.#:           <computed>
    source_dest_check:           true
    subnet_id:                   <computed>
    tenancy:                     <computed>
    vpc_security_group_ids.#:    <computed>

Plan: 1 to add, 0 to change, 0 to destroy.


simple, undersatnable parameter an variable names and works well in addition. Well done. 👍


Oh, btw is the current code ok?


To jest do zrobienia jednym requestem. Endpoint przyjmuje Set<ProductType>.


Ah, good point. I've fixed the issue around calling these elements paragraphs vs. headings.

Re: the paragraphs having different names- I was mostly concerned about these paragraphs needing to be seperated, but realized I could name them the same thing and add a margin to both.


Does it make sense to rename these files too?  nextcloud-restore.sh and nextcloud-unlockadmin.sh


Modificaciones al modulo de Mesa de control. Estas modificaciones se hicieron del martes 4 de abril al martes 11 de abril. Comprenden 6 tareas:
1.-En editar ticket, se cambiaron los campos, información tcket Información usuario y promociones por Información general.
2.-En editar ticket, Se cambió el botón guardar para que ahora autorice y guarde.
3.-En Mesa de control, se agregaron las columnas promos declaradas y otorgadas asi como montos declarados y otorgados
4.-En Mesa de control, a estas columnas se les asigno un criterio con respecto a la busqueda echa en las tablas: pgs_recibos_detalles_pagastar, pgs_productos, pgs_recibos de la base de datos.
5.-En los archivos crud_add y crud_upd se resolvio el problema que había al guardar comillas en base de datos
6.-En los archivos lst_mesa_control upd_mesa_control y upd_recibos_mc se cambió el tamaño de la foto del recibo, y se modificaron las proporciones de los contenedores de estas.


Okay, but closing the file is needed. If you forget this step, you can cause a lot of confusion in your next, more complicated projects.


Test on #57 added while adding folders


meh./ sloppy crap. ill fix it


Add newline @EOF to the "new file" template in intellij so I don't have to see these in the file viewer.


hello


this is a great commit


hey can you unban me on twitch


For future reference, there is a statement in python called `pass` for situations like this that does nothing.


用这种方式去比较和直接依赖没有本质区别


Nice idea. Congrats!!


Petite faute : "Aucun membre à supprimer"


To clarify, the file should be:
```
 # extra requirements for globus
  -r ./requirements.txt
globus_sdk[jwt]>=1.0.0,<2.0.0
```
or do we still need the python-jose dependency?


cdscdscdscdscdscds


Recommitted multi sonar code


do this require updates to scripts?


part of #21


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/c5be0172-0fbd-4057-9d32-b4df1614ce28 "php-mysql-crud"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/bdfa1059-204d-41a8-934c-bdb19de0b024 "php-mysql-crud") deployed [php_mysql_crud](https://github.com/gportillo94/php_mysql_crud/releases/tag/deploy-ibm-yp-us-south-gportill-dev-20170412-021256 "deploy-ibm-yp-us-south-gportill-dev-20170412-021256") to [dev](https://console.ng.bluemix.net/apps/6dcdd5a4-a14b-459b-981c-7e5490a8bd0a "ibm:yp:us-south:gportill:dev"), including this commit


now* not "not"


fixed in next 2 commits


good


Reviewed.  This all seems good to me.


dd


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/c5be0172-0fbd-4057-9d32-b4df1614ce28 "php-mysql-crud"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/bdfa1059-204d-41a8-934c-bdb19de0b024 "php-mysql-crud") deployed [php_mysql_crud](https://github.com/gportillo94/php_mysql_crud/releases/tag/deploy-ibm-yp-us-south-gportill-dev-20170412-022135 "deploy-ibm-yp-us-south-gportill-dev-20170412-022135") to [dev](https://console.ng.bluemix.net/apps/6dcdd5a4-a14b-459b-981c-7e5490a8bd0a "ibm:yp:us-south:gportill:dev"), including this commit


'const info'랑 'const {info}'가 어떻게 다른건가요?


Removing validatelineedit was a mistake and reverted back in in a future commit.


I think this is a bug and you need to check the codeUnit at i+1 instead?


Ok, new version sets velocity to 0, then quickly boosts them in a direction. I like it... so far im keeping it


@NasrinJaleel93 - Why are we setting parameter name to "" ?


first


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/c5be0172-0fbd-4057-9d32-b4df1614ce28 "php-mysql-crud"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/bdfa1059-204d-41a8-934c-bdb19de0b024 "php-mysql-crud") deployed [php_mysql_crud](https://github.com/gportillo94/php_mysql_crud/releases/tag/deploy-ibm-yp-us-south-gportill-dev-20170412-022702 "deploy-ibm-yp-us-south-gportill-dev-20170412-022702") to [dev](https://console.ng.bluemix.net/apps/6dcdd5a4-a14b-459b-981c-7e5490a8bd0a "ibm:yp:us-south:gportill:dev"), including this commit


This has been fixed [here](https://github.com/BrandonKelly90/bloc-jams/commit/41febd10187fedcab482ad8779d87880cabdcb88).


As mentioned [in issue 231](https://github.com/pypa/python-packaging-user-guide/issues/231#issuecomment-286447009), there is a typo in the commit message, and #238 is the relevant issue.


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/c5be0172-0fbd-4057-9d32-b4df1614ce28 "php-mysql-crud"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/bdfa1059-204d-41a8-934c-bdb19de0b024 "php-mysql-crud") deployed [php_mysql_crud](https://github.com/gportillo94/php_mysql_crud/releases/tag/deploy-ibm-yp-us-south-gportill-dev-20170412-023023 "deploy-ibm-yp-us-south-gportill-dev-20170412-023023") to [dev](https://console.ng.bluemix.net/apps/6dcdd5a4-a14b-459b-981c-7e5490a8bd0a "ibm:yp:us-south:gportill:dev"), including this commit


Apparent fix:

```diff
diff --git a/stdlib/public/core/UnicodeViews.swift b/stdlib/public/core/UnicodeViews.swift
index 53936076798..71dce5fce9d 100644
--- a/stdlib/public/core/UnicodeViews.swift
+++ b/stdlib/public/core/UnicodeViews.swift
@@ -903,7 +903,7 @@ public struct Latin1CharacterView<
     // code-unit-is-single-grapheme?
     _sanityCheck(nextIdx.base == i.base+2)
     _sanityCheck(getCU(at: i) == _CR)
-    _sanityCheck(getCU(at: nextIdx) == _LF)
+    _sanityCheck(codeUnits[codeUnits.index(atOffset: i.base + 1)] == _LF)
     return Character("\u{0D}\u{0A}")
   }

```


@ereator, I had modified the file to the original version and made a commit. 👶


Main Jupyter Notebook File


**Yes，Installation of luaraocks command is not supported ：**
./luarocks install https://raw.github.com/noahdesu/lua-rados/master/rockspecs/lua-rados-0.0.1-1.rockspec
**But manual compilation is successful**

**But still failed to work on openresty like this：**
        _location /api {
        content_by_lua_block {
        local rados = require "rados"
        local cluster = rados.create()
        cluster:conf_read_file()
        --cluster:conf_read_file('/etc/ceph/ceph.conf')
        cluster:connect()
        --Next, open a client I/O context for a particular pool:
        local ioctx = cluster:open_ioctx('data')
        --Now the Lua client can interact with objects, such as setting an extended attribute:
        local name = 'xattr key'
        local data = 'i am some important data'
        ioctx:setxattr('my_obj', name, data, #data)
        }
        }_
**My CEPH does exist in data pool**
_[root@ceph-ca1 nginx]# ceph df
GLOBAL:
    SIZE       AVAIL      RAW USED     %RAW USED
    40871M     40569M         302M          0.74
POOLS:
    NAME     ID     USED     %USED     MAX AVAIL     OBJECTS
    rbd      0         0         0        13513M           0
    data     1         0         0        13513M           0
[root@ceph-ca1 nginx]#_

_2017/04/12 02:18:15 [error] 24365#0: *16 lua entry thread aborted: runtime error: content_by_lua(nginx.conf:72):11: calling 'open_ioctx' on bad self (not connected to cluster)
stack traceback:
coroutine 0:
        [C]: in function 'open_ioctx'
        content_by_lua(nginx.conf:72):11: in function <content_by_lua_


This is not a good description. Please explain the format and don't mention Airlift as end users don't care. Also, avoid using "Presto" in documention when possible as it's usually redundant. "Interval" should not be capitalized.


ok


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/c5be0172-0fbd-4057-9d32-b4df1614ce28 "php-mysql-crud"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/bdfa1059-204d-41a8-934c-bdb19de0b024 "php-mysql-crud") deployed [php_mysql_crud](https://github.com/gportillo94/php_mysql_crud/releases/tag/deploy-ibm-yp-us-south-gportill-dev-20170412-023730 "deploy-ibm-yp-us-south-gportill-dev-20170412-023730") to [dev](https://console.ng.bluemix.net/apps/6dcdd5a4-a14b-459b-981c-7e5490a8bd0a "ibm:yp:us-south:gportill:dev"), including this commit


Content is not showing up in production.


This is just the script text.  You need to compile it using 'Script Editor/AppleScript.

Open 'Script Editor'.app --> 'New Document' --> Paste the text above -->
Then,
 Save As: SWTORLaunch
 Where: Applications
 File Format: Application

--> Hit 'Save' Button

*Voila - application to launch the above commands on OS X automatically.


p


Ahh, glad you got it compiled. I think to fix rockspec I need to cut a new release. That's pretty easy. The error your are getting suggests that `cluster::connect` failed. Can you check the return value? It should tell us more about what went wrong.


Should say 'Launches SWTOR 5.1.3 in Wine 2 on OS X'. (Should say 'OS X' rather than 'LSBs. E.g, FreeBSD')


And taking out '|| json_store.objects === undefined', everything loads fine for you? That's really weird.

However, in thinking about it you're right. json_store.objects isn't related to collections.json. It's really strange why this seemed to fix the problem on my laptop.

A simpler fix is just to address line 269 and change it to this:

				if (json_store.objects !== undefined && json_store.objects[nav_name] !== undefined && json_store.objects[nav_name].label !== undefined) nav_name = (json_store.objects[nav_name].label);

I recall doing that but there was a follow-up issue. However I just tried it now and it seemed to fix my problem. Can you give this a try?  I'd upload the fix to github, but I'm in the middle of updating weather station rrd to get live data, and don't want to interrupt that.


From what I could see, horst.prack gave a mismatch between the bench and what his client got, and this has interrupted the test.  From what I could see, against horst.prack there are 15 other workers that benched the test and matched my bench.  So I know who the outlier is.  But what can I do?


total 20
-rw-r--r-- 1 jenkins docker 1941 Apr 12 02:45 Jenkinsfile
-rw-r--r-- 1 jenkins docker 3692 Apr 12 01:37 main.tf
-rw-r--r-- 1 jenkins docker   57 Apr 12 01:37 outputs.tf
-rw-r--r-- 1 jenkins docker   68 Apr 12 01:37 README.md
-rw-r--r-- 1 jenkins docker  743 Apr 12 01:37 variables.tf


OK so this doesn't fix the problem in yarn anyway. I'll leave this commit in for now, as I'd be keen to just go over which scripts are best for   what situation, but will probably have to revert 😞


Un poco tarde no?)


@tomasmussi Recién cambia el readme a vos te parece?


this one is getting better and better - congrats for a very nice patch @snicolet ...


@matthoward1013  You'll want to change this to `ASCII`. In Visual studio when you click on the project and edit properties it should be one of the options under General. Near that area should also be something to add Arguments or Debug something. It should be an empty text box. Looks like you haven't anything to it yet since the XML tags aren't in here yet. Here is a picture: https://social.msdn.microsoft.com/Forums/getfile/718788


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/c5be0172-0fbd-4057-9d32-b4df1614ce28 "php-mysql-crud"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/bdfa1059-204d-41a8-934c-bdb19de0b024 "php-mysql-crud") deployed [php_mysql_crud](https://github.com/gportillo94/php_mysql_crud/releases/tag/deploy-ibm-yp-us-south-gportill-dev-20170412-025145 "deploy-ibm-yp-us-south-gportill-dev-20170412-025145") to [dev](https://console.ng.bluemix.net/apps/6dcdd5a4-a14b-459b-981c-7e5490a8bd0a "ibm:yp:us-south:gportill:dev"), including this commit


Fixed Issue #1


COMMITED VIA GITHUB LOL


total 20
-rw-r--r-- 1 jenkins docker 1256 Apr 12 02:54 Jenkinsfile
-rw-r--r-- 1 jenkins docker 3692 Apr 12 01:37 main.tf
-rw-r--r-- 1 jenkins docker   57 Apr 12 01:37 outputs.tf
-rw-r--r-- 1 jenkins docker   68 Apr 12 01:37 README.md
-rw-r--r-- 1 jenkins docker  743 Apr 12 01:37 variables.tf


total 20
-rw-r--r-- 1 jenkins docker 1256 Apr 12 02:54 Jenkinsfile
-rw-r--r-- 1 jenkins docker 3692 Apr 12 01:47 main.tf
-rw-r--r-- 1 jenkins docker   57 Apr 12 01:47 outputs.tf
-rw-r--r-- 1 jenkins docker   68 Apr 12 01:47 README.md
-rw-r--r-- 1 jenkins docker  743 Apr 12 01:47 variables.tf


/.jklh


total 20
-rw-r--r-- 1 jenkins docker 1267 Apr 12 02:55 Jenkinsfile
-rw-r--r-- 1 jenkins docker 3692 Apr 12 01:37 main.tf
-rw-r--r-- 1 jenkins docker   57 Apr 12 01:37 outputs.tf
-rw-r--r-- 1 jenkins docker   68 Apr 12 01:37 README.md
-rw-r--r-- 1 jenkins docker  743 Apr 12 01:37 variables.tf


total 20
-rw-r--r-- 1 jenkins docker 1267 Apr 12 02:55 Jenkinsfile
-rw-r--r-- 1 jenkins docker 3692 Apr 12 01:47 main.tf
-rw-r--r-- 1 jenkins docker   57 Apr 12 01:47 outputs.tf
-rw-r--r-- 1 jenkins docker   68 Apr 12 01:47 README.md
-rw-r--r-- 1 jenkins docker  743 Apr 12 01:47 variables.tf


That lasted a long time...


total 20
-rw-r--r-- 1 jenkins docker 1275 Apr 12 02:58 Jenkinsfile
-rw-r--r-- 1 jenkins docker 3692 Apr 12 01:37 main.tf
-rw-r--r-- 1 jenkins docker   57 Apr 12 01:37 outputs.tf
-rw-r--r-- 1 jenkins docker   68 Apr 12 01:37 README.md
-rw-r--r-- 1 jenkins docker  743 Apr 12 01:37 variables.tf


This method is a new method, you do a good job


Hola compañero no me has realizado el envio a mi solo lo dejaste en tu repositorio


Kernel config for X2 are needed too :)


Bluemix toolchain: An unknown tool deployed [testRepo-Traceability](https://github.com/idsdev/testRepo-Traceability/releases/tag/deployed-2-env-w3ibm-prod-us-south-user-ibm.com-prod-20170412-200120 "deployed-2-env-w3ibm-prod-us-south-user-ibm.com-prod-20170412-200120") to [prod](http://localhost:3100/apps/6e3bc311-c83d-4cd1-a457-99d9a5f20f19 "w3ibm:prod:us-south:user@ibm.com:prod"), including this commit


Bluemix toolchain: An unknown tool deployed [testRepo-Traceability](https://github.com/idsdev/testRepo-Traceability/releases/tag/deployed-2-env-w3ibm-prod-us-south-user-ibm.com-prod-20170412-200124 "deployed-2-env-w3ibm-prod-us-south-user-ibm.com-prod-20170412-200124") to [prod](http://localhost:3100/apps/6e3bc311-c83d-4cd1-a457-99d9a5f20f19 "w3ibm:prod:us-south:user@ibm.com:prod"), including this commit


Bluemix toolchain: An unknown tool deployed [testRepo-Traceability](https://github.com/idsdev/testRepo-Traceability/releases/tag/deployed-2-env-Prod-20170412-200127 "deployed-2-env-Prod-20170412-200127") to [Prod](http://localhost:3100/apps/6e3bc311-c83d-4cd1-a457-99d9a5f20f19 "There was a problem retrieving the space name"), including this commit


Bluemix toolchain: An unknown tool deployed [testRepo-Traceability](https://github.com/idsdev/testRepo-Traceability/releases/tag/deployed-2-env-w3ibm-prod-us-south-user-ibm.com-prod-20170412-200136 "deployed-2-env-w3ibm-prod-us-south-user-ibm.com-prod-20170412-200136") to [prod](http://localhost:3100/apps/6e3bc311-c83d-4cd1-a457-99d9a5f20f19 "w3ibm:prod:us-south:user@ibm.com:prod"), including this commit


Hooh, sorry, this morning I was more confused than other times...


Refreshing Terraform state


Why not?


@doomsayer2: you have started later so you can't know - @julianaus was co-applicant and member of the VALiD project team until last year


Oh no. Let's keep that in there. Sorry for the confusion.


hello~


the main bundle should have EVERYTHING


Hi, can you help me understand what is happening when I try to run the new code in my IDE? The game doesn't play and it executes for 1/10th of a second and displays this in the Debug I/O:

ShitClown({'_Sprite__g': {}, 'image_prefix': 'shit_clown', 'level': 1, 'speed': 4, 'hp': 1000, 'stamina': 10, 'fear': 90, 'image': <Surface(30x20x32 SW)>, 'rect': <rect(0, 0, 30, 20)>, 'surf': <Surface(30x20x32 SW)>, 'image_dir': 'res\\img\\chars', 'name': 'Shit Clown 1'})
JackScrapper({'_Sprite__g': {}, 'image_prefix': 'jack_scrapper', 'level': 1, 'speed': 4, 'hp': 2000, 'stamina': 15, 'fear': 85, 'image': <Surface(30x20x32 SW)>, 'rect': <rect(0, 0, 30, 20)>, 'surf': <Surface(30x20x32 SW)>, 'image_dir': 'res\\img\\chars', 'name': 'Jack Scrapper 1'})
JackScrapper({'_Sprite__g': {}, 'image_prefix': 'jack_scrapper', 'level': 1, 'speed': 4, 'hp': 2000, 'stamina': 15, 'fear': 85, 'image': <Surface(30x20x32 SW)>, 'rect': <rect(0, 0, 30, 20)>, 'surf': <Surface(30x20x32 SW)>, 'image_dir': 'res\\img\\chars', 'name': 'Jack Scrapper 2'})


Nice. But some more explanation is needed. How does this code work? Which command represents which funcionalty?


Should be called in the upload function to replace the filename.


Generates the key that the filemap is encrypted with, before uploading it to the DHT


PR is still here ;) -> https://github.com/cmangos/mangos-wotlk/commit/7142ba290b9cc506614c7d5758f25ff76f09975a#commitcomment-21739355 for anyone who need to go more in deep on it. I merged them to make it easier for fast review on my side and not polute commit history. But you are right next pr commits will not be merged. At least not the main one. For backport and upport i still prefer to do it its faster.


- rackjure: done
- markdown: Had to wait for pkg.r-l-.org to refresh rackjure for <6.1, for markdown to be able to build <6.1.


@barsh These aren't real keys are they? Also, it was set up as such to avoid exposing anything sensitive in plain text on the disk. Setting the env vars is a bit less convenient, but much more secure.


Good, leave it out then, I guess. (=


The solution is simple and accurate. The commit message is correct. 👍


I am not sure, but it should be generated after the user is has newly joined the network (first time)


@barsh what is this?


maybe in the broker?


The never ending balance between simplicity and completeness.

"Okay I'm doing Redux but I want to keep it simple."
"Okay I need to do async so I'm going to do Sagas and I give up on keeping it simple."


Don't worry!


Another potential suggestion... ESLint in the JS loader chain with the airbnb presets?


Restored.


Следующим коммитом перенес между строками 5 и 6, чтобы пропадала надпись Best Answer при удалении соответствующего флага


Could you elaborate?
Eg would it be better to write `<a href="tel:+(insert phone number here)">+(insert phone number here)</a>`'?

I've found:
- Mail-To link
- phone link for mobile devices, but it seems more prudent to make it a link that works for all devices, eg mobile and desktop


Looks like it did parse as if there had been a space between: https://github.com/NoCheatPlus/NoCheatPlus/blob/master/NCPCore/src/main/java/fr/neatmonster/nocheatplus/actions/AbstractActionFactory.java#L65

All that will get redone some day anyway.


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/f16f22e0-b746-41b7-bc64-4dab667e629e "topawanawan"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/3ea60619-dd43-4e18-b21d-c4ba6742dd70 "topawanawan") deployed [topawanawan](https://github.com/moinawan1212/topawanawan/releases/tag/deploy-ibm-yp-us-south-saltanatparween786102-prod-20170412-201117 "deploy-ibm-yp-us-south-saltanatparween786102-prod-20170412-201117") to [prod](https://console.ng.bluemix.net/apps/8f9e5364-e0b3-4ed5-925b-bc659850f6d1 "ibm:yp:us-south:saltanatparween786102:prod"), including this commit


OK markdown is done, too.

I nudged pkg.r-l.org to refresh markdown. It may take c. 30 minutes. As soon as [this page](https://pkgd.racket-lang.org/pkgn/package/markdown) shows commit 04a52a3d835c2fd7e24aca4fe07ceb375e9ec741 you should be all set.


Refreshing Terraform state


Bluemix toolchain: An unknown tool deployed [testRepo-Traceability](https://github.com/idsdev/testRepo-Traceability/releases/tag/deployed-2-env-w3ibm-prod-us-south-user-ibm.com-prod-20170412-201159 "deployed-2-env-w3ibm-prod-us-south-user-ibm.com-prod-20170412-201159") to [prod](https://dev-console.stage1.ng.bluemix.net/apps/6e3bc311-c83d-4cd1-a457-99d9a5f20f19 "w3ibm:prod:us-south:user@ibm.com:prod"), including this commit


Bluemix toolchain: An unknown tool deployed [testRepo-Traceability](https://github.com/idsdev/testRepo-Traceability/releases/tag/deployed-2-env-w3ibm-prod-us-south-user-ibm.com-prod-20170412-201204 "deployed-2-env-w3ibm-prod-us-south-user-ibm.com-prod-20170412-201204") to [prod](https://dev-console.stage1.ng.bluemix.net/apps/6e3bc311-c83d-4cd1-a457-99d9a5f20f19 "w3ibm:prod:us-south:user@ibm.com:prod"), including this commit


Bluemix toolchain: An unknown tool deployed [testRepo-Traceability](https://github.com/idsdev/testRepo-Traceability/releases/tag/deployed-2-env-Prod-20170412-201207 "deployed-2-env-Prod-20170412-201207") to [Prod](https://dev-console.stage1.ng.bluemix.net/apps/6e3bc311-c83d-4cd1-a457-99d9a5f20f19 "There was a problem retrieving the space name"), including this commit


This should be called during uploading a new file, as the newly generated key will be used to encrypt each shred of this file


Bluemix toolchain: An unknown tool deployed [testRepo-Traceability](https://github.com/idsdev/testRepo-Traceability/releases/tag/deployed-2-env-w3ibm-prod-us-south-user-ibm.com-prod-20170412-201216 "deployed-2-env-w3ibm-prod-us-south-user-ibm.com-prod-20170412-201216") to [prod](https://dev-console.stage1.ng.bluemix.net/apps/6e3bc311-c83d-4cd1-a457-99d9a5f20f19 "w3ibm:prod:us-south:user@ibm.com:prod"), including this commit


reading the file is correct, but you need to close the file at some point. Otherwise, skipping this step could cause confusion in your future, more complicated projects.


preloader


essa linha cria uma biblioteca


Thank you, I must have overlooked it. I appreciate the help.


![](https://github.trello.services/images/mini-trello-icon.png) [adaaa](https://trello.com/c/64TxFDwG/4-adaaa)


wow thanks for your work ! this is very helpful!


.input__search — **Э**лемент search **Б**лока input. Компонент не может быть и блоком, и элементом одновременно. Предвидя, что поле поиска многосоставное (иконка, поле ввода, кнопка), правильнее сделать блок-родитель с элементами, например:
```
<form class="search" action="search.html" method="get">
  <span class="search__icon"></span>
  <input type="search" class="input input_type_search search__input">
  <button type="submit" class="search__button">Найти</button>
</form>
```


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/f16f22e0-b746-41b7-bc64-4dab667e629e "topawanawan"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/3ea60619-dd43-4e18-b21d-c4ba6742dd70 "topawanawan") deployed [topawanawan](https://github.com/moinawan1212/topawanawan/releases/tag/deploy-ibm-yp-us-south-saltanatparween786102-prod-20170412-201409 "deploy-ibm-yp-us-south-saltanatparween786102-prod-20170412-201409") to [prod](https://console.ng.bluemix.net/apps/8f9e5364-e0b3-4ed5-925b-bc659850f6d1 "ibm:yp:us-south:saltanatparween786102:prod"), including this commit


fs.stat(path) throws on symlinks that had their originals removed, so this wont quite work.


ami:"ami-a58d0dc5"
associate_public_ip_address: "<computed>"


Instead of 'i' maybe 'letter' would be a better name. 'i' represents an index in general, but in this case you use the actual item of the list.


Пропустил пробел * 3


Perhaps its better to add rimraf as dependency and use `rimraf.sync` ?


It refreshed.


«drop-down» имеет отношение скорее ко всему списку, т. е. к `ul`, а не к каждому элементу.


can multiply 2 numbers of any size.. yes can be very very very very big


This should be true.


I'm going to remove `release`, use an explicit version number


AFN_duct_update (mitchute) - i386-Windows-7-VisualStudio-14: OK (2494 of 2494 tests passed, 0 test warnings)

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


aqui eu chamei a funcao main


ai o twist


Replace 'example.com' with 'testpilot.env'


Those are still being ironed out: https://review.lineageos.org/#/c/168429/


not a good idea to assume this is always installed, at this path or at all


ami:"ami-a58d0dc5"associate_public_ip_address: "<computed>"


spicy


The CRC hacks are required to fix the brightness and contrast. That's why they're here in the first place 😛


The code is wonderful. One thing: instead of parameter name 'l' it would be better to use a word. Maybe group, pirates, people or something.. :)


Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.

The Terraform execution plan has been generated and is shown below.
Resources are shown in alphabetical order for quick scanning. Green resources
will be created (or destroyed and then created if an existing resource
exists), yellow resources are being changed in-place, and red resources
will be destroyed. Cyan entries are data sources to be read.

Your plan was also saved to the path below. Call the apply subcommand
with this plan file and Terraform will exactly execute this execution
plan.

Path: plan

+ aws_instance.example
    ami:                         ami-a58d0dc5
    associate_public_ip_address: <computed>
    availability_zone:           <computed>
    ebs_block_device.#:          <computed>
    ephemeral_block_device.#:    <computed>
    instance_state:              <computed>
    instance_type:               t2.micro
    ipv6_addresses.#:            <computed>
    key_name:                    <computed>
    network_interface_id:        <computed>
    placement_group:             <computed>
    private_dns:                 <computed>
    private_ip:                  <computed>
    public_dns:                  <computed>
    public_ip:                   <computed>
    root_block_device.#:         <computed>
    security_groups.#:           <computed>
    source_dest_check:           true
    subnet_id:                   <computed>
    tenancy:                     <computed>
    vpc_security_group_ids.#:    <computed>

Plan: 1 to add, 0 to change, 0 to destroy.


lol so true! I am almost certain that I will inevitably make this boilerplate more opinionated at and accept the complexity, but I want to get there at a safe slow pace haha. Not sure if you saw the Reddit discussion, but you all win the SASS vs LESS battle.


Not sure where I can create a new issue but I will list it here.  Looking at the speeds.csv file, all the measurements are 0.  Not sure how to debug this.  This is on a Raspberry Pi running Raspbian.


TeamCity Platform Services :: Environment Manager 2 :: Package [Build 3.40.0-pre-8-g63de09f](http://infra.teamcity.ci.ttldev/viewLog.html?buildId=58265&buildTypeId=PlatformServices_EnvironmentManager2_Package) outcome was **SUCCESS**
Summary: Running Build time: 00:01:02


It seem like a perfect answer! 👍


Glad to help, feel free to ask me for any further help


Refreshing Terraform state in-memory prior to plan...\nThe refreshed state will be used to calculate this plan, but will not be\npersisted to local or remote state storage.\n\nThe Terraform execution plan has been generated and is shown below.\nResources are shown in alphabetical order for quick scanning. Green resources\nwill be created (or destroyed and then created if an existing resource\nexists), yellow resources are being changed in-place, and red resources\nwill be destroyed. Cyan entries are data sources to be read.\n\nYour plan was also saved to the path below. Call the \"apply\" subcommand\nwith this plan file and Terraform will exactly execute this execution\nplan.\n\nPath: plan\n\n+ aws_instance.example\n    ami:                         \"ami-a58d0dc5\"\n    associate_public_ip_address: \"<computed>\"\n    availability_zone:           \"<computed>\"\n    ebs_block_device.#:          \"<computed>\"\n    ephemeral_block_device.#:    \"<computed>\"\n    instance_state:              \"<computed>\"\n    instance_type:               \"t2.micro\"\n    ipv6_addresses.#:            \"<computed>\"\n    key_name:                    \"<computed>\"\n    network_interface_id:        \"<computed>\"\n    placement_group:             \"<computed>\"\n    private_dns:                 \"<computed>\"\n    private_ip:                  \"<computed>\"\n    public_dns:                  \"<computed>\"\n    public_ip:                   \"<computed>\"\n    root_block_device.#:         \"<computed>\"\n    security_groups.#:           \"<computed>\"\n    source_dest_check:           \"true\"\n    subnet_id:                   \"<computed>\"\n    tenancy:                     \"<computed>\"\n    vpc_security_group_ids.#:    \"<computed>\"\n\n\nPlan: 1 to add, 0 to change, 0 to destroy.\n


I'd use clientIsAliveFlagFile? instead - it is not critical if the file will be null here, but NPE in this place will be highly blocking.
The same below.


Interesting. I like the idea. I was considering adding some Elixir linting stuff too. I'll definitely be playing with that stuff soon. Again, thank you for the contributions! Super appreciated! And any more PRs would be greatly appreciated, haha :).


Refreshing Terraform state in-memory prior to plan...The refreshed state will be used to calculate this plan, but will not bepersisted to local or remote state storage.The Terraform execution plan has been generated and is shown below.Resources are shown in alphabetical order for quick scanning. Green resourceswill be created (or destroyed and then created if an existing resourceexists), yellow resources are being changed in-place, and red resourceswill be destroyed. Cyan entries are data sources to be read.Your plan was also saved to the path below. Call the "apply" subcommandwith this plan file and Terraform will exactly execute this executionplan.Path: plan+ aws_instance.example    ami:                         "ami-a58d0dc5"    associate_public_ip_address: "<computed>"    availability_zone:           "<computed>"    ebs_block_device.#:          "<computed>"    ephemeral_block_device.#:    "<computed>"    instance_state:              "<computed>"    instance_type:               "t2.micro"    ipv6_addresses.#:            "<computed>"    key_name:                    "<computed>"    network_interface_id:        "<computed>"    placement_group:             "<computed>"    private_dns:                 "<computed>"    private_ip:                  "<computed>"    public_dns:                  "<computed>"    public_ip:                   "<computed>"    root_block_device.#:         "<computed>"    security_groups.#:           "<computed>"    source_dest_check:           "true"    subnet_id:                   "<computed>"    tenancy:                     "<computed>"    vpc_security_group_ids.#:    "<computed>"Plan: 1 to add, 0 to change, 0 to destroy.


TeamCity Platform Services :: Environment Manager 2 :: Package [Build 3.40.0-pre-2-g106279d](http://infra.teamcity.ci.ttldev/viewLog.html?buildId=58269&buildTypeId=PlatformServices_EnvironmentManager2_Package) outcome was **SUCCESS**
Summary: Running Build time: 00:00:45


Never been a fan of scenecut=0.. I understand how it can be useful for a smoother pipeline overall, but forbidding x264 from efficient keyframe placement is detrimental to the quality.


Refreshing Terraform state in-memory prior to plan...The refreshed state will be used to calculate this plan, but will not bepersisted to local or remote state storage.The Terraform execution plan has been generated and is shown below.Resources are shown in alphabetical order for quick scanning. Green resourceswill be created (or destroyed and then created if an existing resourceexists), yellow resources are being changed in-place, and red resourceswill be destroyed. Cyan entries are data sources to be read.Your plan was also saved to the path below. Call the apply subcommandwith this plan file and Terraform will exactly execute this executionplan.Path: plan+ aws_instance.example    ami:                         ami-a58d0dc5    associate_public_ip_address: <computed>    availability_zone:           <computed>    ebs_block_device.#:          <computed>    ephemeral_block_device.#:    <computed>    instance_state:              <computed>    instance_type:               t2.micro    ipv6_addresses.#:            <computed>    key_name:                    <computed>    network_interface_id:        <computed>    placement_group:             <computed>    private_dns:                 <computed>    private_ip:                  <computed>    public_dns:                  <computed>    public_ip:                   <computed>    root_block_device.#:         <computed>    security_groups.#:           <computed>    source_dest_check:           true    subnet_id:                   <computed>    tenancy:                     <computed>    vpc_security_group_ids.#:    <computed>Plan: 1 to add, 0 to change, 0 to destroy.


@seancarr, this is the commit that resets auto commit after transactional execution.


Hi, Could you please let me know the steps for using a spring boot executable jar as a non executable dependency jar with all the third party dependencies in it.


Wywoływanie 2 razy tego samego requesta tylko po to, aby wyciągnąć pozycję ostatniego elementu a potem sam element jest zupełnie nie optymalne. Poza tym ID przychodzi w response na post.