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

> set -x && set -e && set -o pipefail && cd /tmp/0pdd20191206-11-1osqikf/monomonedula/kicksbot && pdd -v -f /tmp/20191209-16823-8obszd [1]: + set -e + set -o pipefail + cd /tmp/0pdd20191206-11-1osqikf/monomonedula/kicksbot + pdd -v -f /tmp/20191209-16823-8obszd  My version is 0.20.5 Ruby version is...

Please, copy and paste this stack trace to GitHub:

```
UserError
set -x && set -e && set -o pipefail && cd /tmp/0pdd20191206-11-1osqikf/monomonedula/kicksbot && pdd -v -f /tmp/20191209-16823-8obszd [1]:
+ set -e
+ set -o pipefail
+ cd /tmp/0pdd20191206-11-1osqikf/monomonedula/kicksbot
+ pdd -v -f /tmp/20191209-16823-8obszd

My version is 0.20.5
Ruby version is 2.6.0 at x86_64-linux
Reading /tmp/0pdd20191206-11-1osqikf/monomonedula/kicksbot
139 file(s) found, 141 excluded
/tmp/0pdd20191206-11-1osqikf/monomonedula/kicksbot/utils/__init__.py is a binary file (0 bytes)
/tmp/0pdd20191206-11-1osqikf/monomonedula/kicksbot/persistence_layer/pg/__init__.py is a binary file (0 bytes)
/tmp/0pdd20191206-11-1osqikf/monomonedula/kicksbot/persistence_layer/search/__init__.py is a binary file (0 bytes)
/tmp/0pdd20191206-11-1osqikf/monomonedula/kicksbot/persistence_layer/__init__.py is a binary file (0 bytes)
/tmp/0pdd20191206-11-1osqikf/monomonedula/kicksbot/search/filters_menu/size_filter_menu/__init__.py is a binary file (0 bytes)
/tmp/0pdd20191206-11-1osqikf/monomonedula/kicksbot/search/filters_menu/sorting_menu/__init__.py is a binary file (0 bytes)
/tmp/0pdd20191206-11-1osqikf/monomonedula/kicksbot/search/filters_menu/__init__.py is a binary file (0 bytes)
/tmp/0pdd20191206-11-1osqikf/monomonedula/kicksbot/search/filters_menu/updates_filter/__init__.py is a binary file (0 bytes)
/tmp/0pdd20191206-11-1osqikf/monomonedula/kicksbot/search/main_menu/__init__.py is a binary file (0 bytes)
/tmp/0pdd20191206-11-1osqikf/monomonedula/kicksbot/search/__init__.py is a binary file (0 bytes)
/tmp/0pdd20191206-11-1osqikf/monomonedula/kicksbot/subs_monitoring/__init__.py is a binary file (0 bytes)
/tmp/0pdd20191206-11-1osqikf/monomonedula/kicksbot/subscriptions/__init__.py is a binary file (0 bytes)
/tmp/0pdd20191206-11-1osqikf/monomonedula/kicksbot/recommendations/__init__.py is a binary file (0 bytes)
/tmp/0pdd20191206-11-1osqikf/monomonedula/kicksbot/tests/test_search/test_main_menu/__init__.py is a binary file (0 bytes)
/tmp/0pdd20191206-11-1osqikf/monomonedula/kicksbot/tests/test_search/test_filters_menu/__init__.py is a binary file (0 bytes)
/tmp/0pdd20191206-11-1osqikf/monomonedula/kicksbot/tests/test_search/__init__.py is a binary file (0 bytes)
/tmp/0pdd20191206-11-1osqikf/monomonedula/kicksbot/tests/utils/__init__.py is a binary file (0 bytes)
/tmp/0pdd20191206-11-1osqikf/monomonedula/kicksbot/tests/test_recommendations/__init__.py is a binary file (0 bytes)
/tmp/0pdd20191206-11-1osqikf/monomonedula/kicksbot/tests/test_templates.py is a binary file (0 bytes)
/tmp/0pdd20191206-11-1osqikf/monomonedula/kicksbot/tests/test_subs_monitoring/__init__.py is a binary file (0 bytes)
/tmp/0pdd20191206-11-1osqikf/monomonedula/kicksbot/tests/test_persistence/__init__.py is a binary file (0 bytes)
/tmp/0pdd20191206-11-1osqikf/monomonedula/kicksbot/tests/__init__.py is a binary file (0 bytes)
/tmp/0pdd20191206-11-1osqikf/monomonedula/kicksbot/__init__.py is a binary file (0 bytes)
/tmp/0pdd20191206-11-1osqikf/monomonedula/kicksbot/tbot/__init__.py is a binary file (0 bytes)
Reading recommendations_list_handlers.py...
Reading recommendations_search_handlers.py...
ERROR: recommendations_search_handlers.py; puzzle at line #208; @todo found, but puzzle can't be parsed, most probably because @todo is not followed by a puzzle marker, as this page explains: https://github.com/yegor256/pdd#how-to-format
If you can't understand the cause of this issue or you don't know how to fix it, please submit a GitHub issue, we will try to help you: https://github.com/yegor256/pdd/issues. This tool is still in its beta version and we will appreciate your feedback. Here is where you can find more documentation: https://github.com/yegor256/pdd/blob/master/README.md.
Exit code is 1

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


Trailing whitespace on this line.


Trailing whitespace here and the next two lines.


Successfully deployed to following URLs:

* https://nextjs-l6ef3lbin.now.sh
* https://nextjs.okandvn.now.sh
* https://nextjs-git-master.okandvn.now.sh


Congrats!


Deploy preview for _website_ ready!

Built with commit de58ec919fbe48261cc2acfd94ee43c61dc32579

https://twiso-55c96b5ki.now.sh


Deployment failed with the following error:

~~~
The domain used as an alias flexstar.tech is not verified yet. Please verify it.
~~~


> ... what happens if we wrap lucene/SearchGroups _always_ into a SolrSearchGroup ...

Yes, I'd actually wondered about it too. :-)

Just pushed another commit to the https://github.com/cpoerschke/lucene-solr/commits/github-bloomberg-SOLR-11831-cpoerschke-13 branch and the FirstPassGroupingCollector vs. SolrFirstPassGroupingCollector differentiation doesn't seem to be too bad?

`ant precommit` passes but not yet opened a PR into the ticket PR since still wanna explore about `SolrSearchGroup` vs. `SkipSecondStepSearchGroup` (which could entail `SolrFirstPassGroupingCollector` vs. `SkipSecondStepFirstPassGroupingCollector` too).

On an unrelated note, from plumbing in the `SolrFirstPassGroupingCollector` vs. `FirstPassGroupingCollector` I started to wonder if exclusion of `group.func` would be needed, superficially it seemed it might not be.


Successfully deployed to following URLs:

* https://baseweb-fgmj6hsrh.now.sh
* https://baseweb.uber-ui-platform.now.sh
* https://baseweb-git-master.uber-ui-platform.now.sh


`srd`-> `std`


If memory serves, the reason for the javascript is to get directly to a pretty URL without a redirect. There might be a better way to handle it in the new Pico, which I haven't familiarised myself with much.


Hi, I am interested in hiring someone who can help me get this piece working on my POS. Can someone point me where to start? Thanks!


Successfully deployed to following URLs:

* https://excitedcornsilkpackages-4sofj6hmq.now.sh
* https://excitedcornsilkpackages.now.sh
* https://excitedcornsilkpackages.maxwofford.now.sh
* https://excitedcornsilkpackages-git-master.maxwofford.now.sh


`tht`-> `that`