Zlib:StreamErrors on versions < 7 of Puppet. Works on Puppet >= 7.

Description of problem
I'm unable to compile a catalog successfully when using octocatalog-diff -v 2.1.0 (installed via the gem). The raised error is due to Zlib::StreamError and fails the catalog build.

What did you do?

I'm using the puppet/puppetserver Docker images to create a testing container. The Puppet environments are deployed via r10k and then octocatalog-diff is then instructed to run against the newly deployed environments by collecting facts from a working PuppetDB installation.
On versions of Puppetserver less than 7, the catalog fails due to zlib stream errors (depicted below). On versions of Puppetserver greater than 7 - the catalogs build 100% fine and works as expected. Unfortunately, I cannot just use Puppetserver 7+ because of other unrelated issues (deprecation issues in our internal code, and we need to mimic our current installation as this is for CI).

What happened?

When running octocatalog-diff, the catalog builds fail due to zlib:stream errors. This issue is only present on versions of Puppet less than 7. If I use the exact same Dockerfile, commands, etc on Puppet 7 and above - compilation passes successfully.
My environment:
Using puppet/puppetserver:6.10.0 Docker image -
/opt/puppetlabs/bin/puppetserver --version
puppetserver version: 6.10.0

/opt/puppetlabs/bin/puppet --version
6.14.0

Using ruby 2.5.1 -
ruby -v
ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-linux-gnu]

With the following installed gems:
*** LOCAL GEMS ***

bigdecimal (default: 1.3.4)
cmath (default: 1.0.0)
colored2 (3.1.2)
cri (2.15.10)
csv (default: 1.0.0)
date (default: 1.0.0)
dbm (default: 1.0.0)
did_you_mean (1.2.0)
diff-lcs (1.3)
diffy (3.4.0)
etc (default: 1.0.0)
faraday (0.17.4)
faraday_middleware (0.14.0)
fast_gettext (1.1.2)
fcntl (default: 1.0.0)
fiddle (default: 1.0.0)
fileutils (default: 1.0.2)
gdbm (default: 2.0.0)
gettext (3.2.9)
gettext-setup (0.34)
hashdiff (1.0.1)
httparty (0.18.1)
io-console (default: 0.4.6)
ipaddr (default: 1.2.0)
json (default: 2.1.0)
locale (2.1.3)
log4r (1.1.10)
mime-types (3.3.1)
mime-types-data (3.2021.0704)
minitar (0.9)
minitest (5.10.3)
multi_json (1.15.0)
multi_xml (0.6.0)
multipart-post (2.1.1)
net-telnet (0.1.1)
octocatalog-diff (2.1.0)
openssl (default: 2.1.1)
parallel (1.20.1)
power_assert (0.2.7)
psych (default: 3.0.2)
puppet_forge (2.3.4)
r10k (3.10.0)
rake (12.3.1)
rdoc (default: 6.0.1)
rspec (3.7.0)
rspec-core (3.7.1)
rspec-expectations (3.7.0)
rspec-mocks (3.7.0)
rspec-support (3.7.1)
rugged (1.1.1)
scanf (default: 1.0.0)
sdbm (default: 1.0.0)
semantic_puppet (1.0.4)
stringio (default: 0.0.1)
strscan (default: 1.0.0)
test-unit (3.2.5)
text (1.3.1)
thread_order (1.1.0)
webrick (default: 1.4.2)
zlib (default: 1.0.0)

What did you expect to happen?

Octocatalog-diff to compile successfully without zlib:stream errors.

How can someone reproduce the problem?

Start a docker container using the puppet/puppetserver:6.10.0 image
Run gem install r10k octocatalog-diff to install r10k and octocatalog-diff
Connect to a PuppetDB or retrieve a fact file from Puppetserver to be used to compile with
Deploy an environment/branch using r10k into /etc/puppetlabs/code/environments including a feature branch to compare against.
Run octocatalog-diff octocatalog-diff -n <random_node_in_puppetdb> --bootstrapped-from-dir /etc/puppetlabs/code/environments/production --bootstrapped-to-dir /etc/puppetlabs/code/environments/<feature_branch> --from-environment production --to-environment <feature_branch> -f production -t <feature_branch> --hiera-config /etc/puppetlabs/code/hiera.yaml -d

You might not need to specify hiera.yaml - in my case, my puppet code requires hiera-lookups hence why I've included it.

Command used and debugging output

D, [2021-08-04T13:36:58.132143 #30589] DEBUG -- : Running octocatalog-diff 2.1.0 with ruby 2.5.1
D, [2021-08-04T13:36:58.132221 #30589] DEBUG -- : Command line arguments: ["-n", "puppetserver3.jnb1.host-h.net", "--bootstrapped-from-dir", "/etc/puppetlabs/code/environments/production", "--bootstrapped-to-dir", "/etc/puppetlabs/code/environments/sc_jb_octocatalog", "--from-environment", "production", "--to-environment", "sc_jb_octocatalog", "-f", "production", "-t", "sc_jb_octocatalog", "--hiera-config", "/etc/puppetlabs/code/hiera.yaml", "-d"]
D, [2021-08-04T13:36:58.132384 #30589] DEBUG -- : Running on host gitlab-puppet-ci (x86_64-linux-gnu)
D, [2021-08-04T13:36:58.132431 #30589] DEBUG -- : Compiling catalogs for puppetserver3.jnb1.host-h.net
D, [2021-08-04T13:36:58.132687 #30589] DEBUG -- : Initialized OctocatalogDiff::Catalog::Computed for from-catalog
D, [2021-08-04T13:36:58.132802 #30589] DEBUG -- : Initialized OctocatalogDiff::Catalog::Computed for to-catalog
D, [2021-08-04T13:36:58.132869 #30589] DEBUG -- : Initialized parallel task result array: size=2
D, [2021-08-04T13:36:58.135080 #30589] DEBUG -- : Launched pid=30591 for index=0
D, [2021-08-04T13:36:58.135308 #30591] DEBUG -- : Begin build_catalog for production
D, [2021-08-04T13:36:58.135615 #30591] DEBUG -- : Setting up Puppet catalog build for production
D, [2021-08-04T13:36:58.135740 #30591] DEBUG -- : Catalog for production will be built with OctocatalogDiff::Catalog::Computed
D, [2021-08-04T13:36:58.135938 #30591] DEBUG -- : Calling build for object OctocatalogDiff::Catalog::Computed
D, [2021-08-04T13:36:58.136420 #30591] DEBUG -- : Start retrieving facts for puppetserver3.jnb1.host-h.net from OctocatalogDiff::Catalog::Computed
D, [2021-08-04T13:36:58.136559 #30591] DEBUG -- : Retrieving facts from PuppetDB
D, [2021-08-04T13:36:58.136961 #30589] DEBUG -- : Launched pid=30594 for index=1
D, [2021-08-04T13:36:58.137465 #30594] DEBUG -- : Begin build_catalog for sc_jb_octocatalog
D, [2021-08-04T13:36:58.137845 #30594] DEBUG -- : Setting up Puppet catalog build for sc_jb_octocatalog
D, [2021-08-04T13:36:58.137909 #30594] DEBUG -- : Catalog for sc_jb_octocatalog will be built with OctocatalogDiff::Catalog::Computed
D, [2021-08-04T13:36:58.138238 #30594] DEBUG -- : Calling build for object OctocatalogDiff::Catalog::Computed
D, [2021-08-04T13:36:58.138418 #30594] DEBUG -- : Start retrieving facts for puppetserver3.jnb1.host-h.net from OctocatalogDiff::Catalog::Computed
D, [2021-08-04T13:36:58.138565 #30594] DEBUG -- : Retrieving facts from PuppetDB
D, [2021-08-04T13:36:58.326536 #30594] DEBUG -- : Failed build_catalog for sc_jb_octocatalog: Zlib::StreamError stream error
D, [2021-08-04T13:36:58.326548 #30591] DEBUG -- : Failed build_catalog for production: Zlib::StreamError stream error
D, [2021-08-04T13:36:58.330227 #30589] DEBUG -- : PID=30594 completed in 0.1933659 seconds, 11847 bytes
Traceback (most recent call last):
	52: from /usr/local/bin/octocatalog-diff:23:in `<main>'
	51: from /usr/local/bin/octocatalog-diff:23:in `load'
	50: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/bin/octocatalog-diff:34:in `<top (required)>'
	49: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/cli.rb:126:in `cli'
	48: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/cli.rb:152:in `run_octocatalog_diff'
	47: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/api/v1.rb:19:in `catalog_diff'
	46: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/api/v1/catalog-diff.rb:34:in `catalog_diff'
	45: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/catalogs.rb:29:in `catalogs'
	44: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/catalogs.rb:92:in `build_catalog_parallelizer'
	43: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/parallel.rb:94:in `run_tasks'
	42: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/parallel.rb:114:in `run_tasks_parallel'
	41: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/parallel.rb:114:in `each_with_index'
	40: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/parallel.rb:114:in `each'
	39: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/parallel.rb:117:in `block in run_tasks_parallel'
	38: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/parallel.rb:117:in `fork'
	37: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/parallel.rb:119:in `block (2 levels) in run_tasks_parallel'
	36: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/parallel.rb:197:in `execute_task'
	35: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/parallel.rb:34:in `execute'
	34: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/parallel.rb:34:in `call'
	33: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/catalogs.rb:241:in `build_catalog'
	32: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/catalog.rb:96:in `build'
	31: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/catalog/computed.rb:109:in `build_catalog'
	30: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/catalog-util/facts.rb:27:in `facts'
	29: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/catalog-util/facts.rb:83:in `compute_facts'
	28: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/catalog-util/facts.rb:50:in `facts_from_puppetdb'
	27: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/catalog-util/facts.rb:50:in `new'
	26: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/facts.rb:31:in `initialize'
	25: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/facts/puppetdb.rb:40:in `fact_retriever'
	24: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/facts/puppetdb.rb:40:in `times'
	23: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/facts/puppetdb.rb:42:in `block in fact_retriever'
	22: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/puppetdb.rb:81:in `get'
	21: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/puppetdb.rb:101:in `_get'
	20: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/puppetdb.rb:101:in `each'
	19: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/puppetdb.rb:118:in `block in _get'
	18: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/httparty.rb:18:in `get'
	17: from /var/lib/gems/2.5.0/gems/httparty-0.18.1/lib/httparty.rb:627:in `get'
	16: from /var/lib/gems/2.5.0/gems/httparty-0.18.1/lib/httparty.rb:508:in `get'
	15: from /var/lib/gems/2.5.0/gems/httparty-0.18.1/lib/httparty.rb:594:in `perform_request'
	14: from /var/lib/gems/2.5.0/gems/httparty-0.18.1/lib/httparty/request.rb:145:in `perform'
	13: from /usr/lib/ruby/2.5.0/net/http.rb:1458:in `request'
	12: from /usr/lib/ruby/2.5.0/net/http.rb:910:in `start'
	11: from /usr/lib/ruby/2.5.0/net/http.rb:1460:in `block in request'
	10: from /usr/lib/ruby/2.5.0/net/http.rb:1467:in `request'
	 9: from /usr/lib/ruby/2.5.0/net/http.rb:1505:in `transport_request'
	 8: from /usr/lib/ruby/2.5.0/net/http/response.rb:166:in `reading_body'
	 7: from /usr/lib/ruby/2.5.0/net/http/response.rb:229:in `body'
	 6: from /usr/lib/ruby/2.5.0/net/http/response.rb:204:in `read_body'
	 5: from /usr/lib/ruby/2.5.0/net/http/response.rb:283:in `read_body_0'
	 4: from /usr/lib/ruby/2.5.0/net/http/response.rb:261:in `inflater'
	 3: from /usr/lib/ruby/2.5.0/net/http/response.rb:261:in `new'
	 2: from /usr/lib/ruby/2.5.0/net/http/response.rb:358:in `initialize'
	 1: from /usr/lib/ruby/2.5.0/net/http/response.rb:358:in `new'
/usr/lib/ruby/2.5.0/net/http/response.rb:358:in `initialize': stream error (Zlib::StreamError)

Platform and version information

Your OS: Linux Ubuntu 18.04.4 LTS (Running in Docker. Image: https://hub.docker.com/r/puppet/puppetserver/tags
Your Ruby version: ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-linux-gnu]
Your version of Puppet: Puppet agent: 6.14.0 && Puppetserver version: 6.10.0. Opensource Puppet
Your version of octocatalog-diff: octocatalog-diff 2.1.0

Do the tests pass from a clean checkout?

--config-test indicates no problems (the same config works fine on > 7 of Puppet).
root@gitlab-puppet-ci:/etc/puppetlabs/code/environments/production# octocatalog-diff -d -n puppetserver3.jnb1.host-h.net
D, [2021-08-04T14:03:15.524924 #32629] DEBUG -- : Running octocatalog-diff 2.1.0 with ruby 2.5.1
D, [2021-08-04T14:03:15.524993 #32629] DEBUG -- : Command line arguments: ["-d", "-n", "puppetserver3.jnb1.host-h.net"]
D, [2021-08-04T14:03:15.525062 #32629] DEBUG -- : Running on host gitlab-puppet-ci (x86_64-linux-gnu)
D, [2021-08-04T14:03:15.525652 #32629] DEBUG -- : Cached master dir: bootstrapped=eca4c263ed3d9a554ef6d4876dcb6e998e1fcfba; current=eca4c263ed3d9a554ef6d4876dcb6e998e1fcfba
D, [2021-08-04T14:03:15.525741 #32629] DEBUG -- : Setting --bootstrapped-from-dir=/root/.octocatalog-diff-cache
D, [2021-08-04T14:03:15.525801 #32629] DEBUG -- : Compiling catalogs for puppetserver3.jnb1.host-h.net
D, [2021-08-04T14:03:15.525980 #32629] DEBUG -- : Initialized OctocatalogDiff::Catalog::Computed for from-catalog
D, [2021-08-04T14:03:15.526046 #32629] DEBUG -- : Initialized OctocatalogDiff::Catalog::Computed for to-catalog
D, [2021-08-04T14:03:15.526081 #32629] DEBUG -- : Initialized parallel task result array: size=2
D, [2021-08-04T14:03:15.527634 #32629] DEBUG -- : Launched pid=32631 for index=0
D, [2021-08-04T14:03:15.527952 #32631] DEBUG -- : Begin build_catalog for origin/master
D, [2021-08-04T14:03:15.528200 #32631] DEBUG -- : Setting up Puppet catalog build for origin/master
D, [2021-08-04T14:03:15.528364 #32631] DEBUG -- : Catalog for origin/master will be built with OctocatalogDiff::Catalog::Computed
D, [2021-08-04T14:03:15.528684 #32631] DEBUG -- : Calling build for object OctocatalogDiff::Catalog::Computed
D, [2021-08-04T14:03:15.529003 #32631] DEBUG -- : Start retrieving facts for puppetserver3.jnb1.host-h.net from OctocatalogDiff::Catalog::Computed
D, [2021-08-04T14:03:15.529155 #32629] DEBUG -- : Launched pid=32634 for index=1
D, [2021-08-04T14:03:15.529091 #32631] DEBUG -- : Retrieving facts from PuppetDB
D, [2021-08-04T14:03:15.529273 #32634] DEBUG -- : Begin build_catalog for .
D, [2021-08-04T14:03:15.529402 #32634] DEBUG -- : Setting up Puppet catalog build for .
D, [2021-08-04T14:03:15.529479 #32634] DEBUG -- : Catalog for . will be built with OctocatalogDiff::Catalog::Computed
D, [2021-08-04T14:03:15.529631 #32634] DEBUG -- : Calling build for object OctocatalogDiff::Catalog::Computed
D, [2021-08-04T14:03:15.529800 #32634] DEBUG -- : Start retrieving facts for puppetserver3.jnb1.host-h.net from OctocatalogDiff::Catalog::Computed
D, [2021-08-04T14:03:15.529882 #32634] DEBUG -- : Retrieving facts from PuppetDB
D, [2021-08-04T14:03:16.072946 #32634] DEBUG -- : Failed build_catalog for .: Zlib::StreamError stream error
D, [2021-08-04T14:03:16.074788 #32631] DEBUG -- : Failed build_catalog for origin/master: Zlib::StreamError stream error
D, [2021-08-04T14:03:16.078770 #32629] DEBUG -- : PID=32634 completed in 0.549616 seconds, 11691 bytes
Traceback (most recent call last):
	52: from /usr/local/bin/octocatalog-diff:23:in `<main>'
	51: from /usr/local/bin/octocatalog-diff:23:in `load'
	50: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/bin/octocatalog-diff:34:in `<top (required)>'
	49: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/cli.rb:126:in `cli'
	48: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/cli.rb:152:in `run_octocatalog_diff'
	47: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/api/v1.rb:19:in `catalog_diff'
	46: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/api/v1/catalog-diff.rb:34:in `catalog_diff'
	45: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/catalogs.rb:29:in `catalogs'
	44: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/catalogs.rb:92:in `build_catalog_parallelizer'
	43: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/parallel.rb:94:in `run_tasks'
	42: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/parallel.rb:114:in `run_tasks_parallel'
	41: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/parallel.rb:114:in `each_with_index'
	40: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/parallel.rb:114:in `each'
	39: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/parallel.rb:117:in `block in run_tasks_parallel'
	38: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/parallel.rb:117:in `fork'
	37: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/parallel.rb:119:in `block (2 levels) in run_tasks_parallel'
	36: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/parallel.rb:197:in `execute_task'
	35: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/parallel.rb:34:in `execute'
	34: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/parallel.rb:34:in `call'
	33: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/catalogs.rb:241:in `build_catalog'
	32: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/catalog.rb:96:in `build'
	31: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/catalog/computed.rb:109:in `build_catalog'
	30: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/catalog-util/facts.rb:27:in `facts'
	29: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/catalog-util/facts.rb:83:in `compute_facts'
	28: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/catalog-util/facts.rb:50:in `facts_from_puppetdb'
	27: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/catalog-util/facts.rb:50:in `new'
	26: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/facts.rb:31:in `initialize'
	25: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/facts/puppetdb.rb:40:in `fact_retriever'
	24: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/facts/puppetdb.rb:40:in `times'
	23: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/facts/puppetdb.rb:42:in `block in fact_retriever'
	22: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/puppetdb.rb:81:in `get'
	21: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/puppetdb.rb:101:in `_get'
	20: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/puppetdb.rb:101:in `each'
	19: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/puppetdb.rb:118:in `block in _get'
	18: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/httparty.rb:18:in `get'
	17: from /var/lib/gems/2.5.0/gems/httparty-0.18.1/lib/httparty.rb:627:in `get'
	16: from /var/lib/gems/2.5.0/gems/httparty-0.18.1/lib/httparty.rb:508:in `get'
	15: from /var/lib/gems/2.5.0/gems/httparty-0.18.1/lib/httparty.rb:594:in `perform_request'
	14: from /var/lib/gems/2.5.0/gems/httparty-0.18.1/lib/httparty/request.rb:145:in `perform'
	13: from /usr/lib/ruby/2.5.0/net/http.rb:1458:in `request'
	12: from /usr/lib/ruby/2.5.0/net/http.rb:910:in `start'
	11: from /usr/lib/ruby/2.5.0/net/http.rb:1460:in `block in request'
	10: from /usr/lib/ruby/2.5.0/net/http.rb:1467:in `request'
	 9: from /usr/lib/ruby/2.5.0/net/http.rb:1505:in `transport_request'
	 8: from /usr/lib/ruby/2.5.0/net/http/response.rb:166:in `reading_body'
	 7: from /usr/lib/ruby/2.5.0/net/http/response.rb:229:in `body'
	 6: from /usr/lib/ruby/2.5.0/net/http/response.rb:204:in `read_body'
	 5: from /usr/lib/ruby/2.5.0/net/http/response.rb:283:in `read_body_0'
	 4: from /usr/lib/ruby/2.5.0/net/http/response.rb:261:in `inflater'
	 3: from /usr/lib/ruby/2.5.0/net/http/response.rb:261:in `new'
	 2: from /usr/lib/ruby/2.5.0/net/http/response.rb:358:in `initialize'
	 1: from /usr/lib/ruby/2.5.0/net/http/response.rb:358:in `new'
/usr/lib/ruby/2.5.0/net/http/response.rb:358:in `initialize': stream error (Zlib::StreamError)

 Here is an example of running on a Puppetserver version 7.1.0. Agent version 7.5.0 to show you that it does actually work (using the exact same octocatalog-cfg, r10k deployment, hiera configs, PuppetDB, etc):
Same version of r10k and octocatalog-diff installed on both containers.
root@ci-ps2:/etc/puppetlabs/code/environments/production# octocatalog-diff -d -n puppetserver3.jnb1.host-h.net
D, [2021-08-04T14:07:23.259501 #17644] DEBUG -- : Running octocatalog-diff 2.1.0 with ruby 2.7.2
D, [2021-08-04T14:07:23.259575 #17644] DEBUG -- : Command line arguments: ["-d", "-n", "puppetserver3.jnb1.host-h.net"]
D, [2021-08-04T14:07:23.259615 #17644] DEBUG -- : Running on host ci-ps2 (x86_64-linux)
D, [2021-08-04T14:07:23.260563 #17644] DEBUG -- : Cached master dir: bootstrapped=eca4c263ed3d9a554ef6d4876dcb6e998e1fcfba; current=eca4c263ed3d9a554ef6d4876dcb6e998e1fcfba
D, [2021-08-04T14:07:23.260687 #17644] DEBUG -- : Setting --bootstrapped-from-dir=/root/.octocatalog-diff-cache
D, [2021-08-04T14:07:23.260822 #17644] DEBUG -- : Compiling catalogs for puppetserver3.jnb1.host-h.net
D, [2021-08-04T14:07:23.261207 #17644] DEBUG -- : Initialized OctocatalogDiff::Catalog::Computed for from-catalog
D, [2021-08-04T14:07:23.261343 #17644] DEBUG -- : Initialized OctocatalogDiff::Catalog::Computed for to-catalog
D, [2021-08-04T14:07:23.261405 #17644] DEBUG -- : Initialized parallel task result array: size=2
D, [2021-08-04T14:07:23.263264 #17644] DEBUG -- : Launched pid=17645 for index=0
D, [2021-08-04T14:07:23.263596 #17645] DEBUG -- : Begin build_catalog for origin/master
D, [2021-08-04T14:07:23.263744 #17645] DEBUG -- : Setting up Puppet catalog build for origin/master
D, [2021-08-04T14:07:23.263873 #17645] DEBUG -- : Catalog for origin/master will be built with OctocatalogDiff::Catalog::Computed
D, [2021-08-04T14:07:23.264265 #17645] DEBUG -- : Calling build for object OctocatalogDiff::Catalog::Computed
D, [2021-08-04T14:07:23.264520 #17645] DEBUG -- : Start retrieving facts for puppetserver3.jnb1.host-h.net from OctocatalogDiff::Catalog::Computed
D, [2021-08-04T14:07:23.264565 #17644] DEBUG -- : Launched pid=17646 for index=1
D, [2021-08-04T14:07:23.264676 #17645] DEBUG -- : Retrieving facts from PuppetDB
D, [2021-08-04T14:07:23.264890 #17646] DEBUG -- : Begin build_catalog for .
D, [2021-08-04T14:07:23.265110 #17646] DEBUG -- : Setting up Puppet catalog build for .
D, [2021-08-04T14:07:23.265223 #17646] DEBUG -- : Catalog for . will be built with OctocatalogDiff::Catalog::Computed
D, [2021-08-04T14:07:23.265432 #17646] DEBUG -- : Calling build for object OctocatalogDiff::Catalog::Computed
D, [2021-08-04T14:07:23.265588 #17646] DEBUG -- : Start retrieving facts for puppetserver3.jnb1.host-h.net from OctocatalogDiff::Catalog::Computed
D, [2021-08-04T14:07:23.265664 #17646] DEBUG -- : Retrieving facts from PuppetDB
D, [2021-08-04T14:07:23.583392 #17646] DEBUG -- : Success retrieving facts for puppetserver3.jnb1.host-h.net from OctocatalogDiff::Catalog::Computed
D, [2021-08-04T14:07:23.583392 #17645] DEBUG -- : Success retrieving facts for puppetserver3.jnb1.host-h.net from OctocatalogDiff::Catalog::Computed
D, [2021-08-04T14:07:23.584659 #17646] DEBUG -- : Symlinked /tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17646-1fvvocu/environments/production -> /etc/puppetlabs/code/environments/production
D, [2021-08-04T14:07:23.584713 #17645] DEBUG -- : Symlinked /tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17645-3tj8ch/environments/production -> /root/.octocatalog-diff-cache
D, [2021-08-04T14:07:23.584916 #17646] DEBUG -- : Installed puppetdb.conf file at /tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17646-1fvvocu/puppetdb.conf
D, [2021-08-04T14:07:23.585061 #17645] DEBUG -- : Installed puppetdb.conf file at /tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17645-3tj8ch/puppetdb.conf
D, [2021-08-04T14:07:23.585888 #17646] DEBUG -- : Installed routes.yaml file at /tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17646-1fvvocu/routes.yaml
D, [2021-08-04T14:07:23.586117 #17645] DEBUG -- : Installed routes.yaml file at /tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17645-3tj8ch/routes.yaml
D, [2021-08-04T14:07:23.586852 #17646] DEBUG -- : Installed hiera.yaml from /etc/puppetlabs/puppet/hiera.yaml to /tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17646-1fvvocu/hiera.yaml
D, [2021-08-04T14:07:23.587372 #17645] DEBUG -- : Installed hiera.yaml from /etc/puppetlabs/puppet/hiera.yaml to /tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17645-3tj8ch/hiera.yaml
D, [2021-08-04T14:07:23.596561 #17645] DEBUG -- : Installed fact file at /tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17645-3tj8ch/var/yaml/facts/puppetserver3.jnb1.host-h.net.yaml
D, [2021-08-04T14:07:23.596561 #17646] DEBUG -- : Installed fact file at /tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17646-1fvvocu/var/yaml/facts/puppetserver3.jnb1.host-h.net.yaml
D, [2021-08-04T14:07:23.597463 #17646] DEBUG -- : Installed SSL client certificate in /tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17646-1fvvocu/var/ssl/certs/ci-ps2.pem
D, [2021-08-04T14:07:23.597484 #17645] DEBUG -- : Installed SSL client certificate in /tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17645-3tj8ch/var/ssl/certs/ci-ps2.pem
D, [2021-08-04T14:07:23.597602 #17645] DEBUG -- : Installed SSL client key in /tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17645-3tj8ch/var/ssl/private_keys/ci-ps2.pem
D, [2021-08-04T14:07:23.597602 #17646] DEBUG -- : Installed SSL client key in /tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17646-1fvvocu/var/ssl/private_keys/ci-ps2.pem
D, [2021-08-04T14:07:23.597816 #17645] DEBUG -- : Installed CA certificate in /tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17645-3tj8ch/var/ssl/certs/ca.pem
D, [2021-08-04T14:07:23.597852 #17646] DEBUG -- : Installed CA certificate in /tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17646-1fvvocu/var/ssl/certs/ca.pem
D, [2021-08-04T14:07:24.518748 #17645] DEBUG -- : (from) Try 1 executing Puppet 7.5.0: /opt/puppetlabs/puppet/bin/puppet catalog compile puppetserver3.jnb1.host-h.net --no-storeconfigs --factpath=/tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17645-3tj8ch/var/yaml/facts --facts_terminus=yaml --no-daemonize --color=false --environment=production --hiera_config=/tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17645-3tj8ch/hiera.yaml --environmentpath=/tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17645-3tj8ch/environments --vardir=/tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17645-3tj8ch/var --logdir=/tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17645-3tj8ch/var --ssldir=/tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17645-3tj8ch/var/ssl --confdir=/tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17645-3tj8ch
D, [2021-08-04T14:07:24.519359 #17645] DEBUG -- : ["Execute: /tmp/ocd-ipc-20210804-17644-muckvt/ocd-scriptrunner20210804-17645-ujvtc1/puppet.sh catalog compile puppetserver3.jnb1.host-h.net --no-storeconfigs --factpath\\=/tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17645-3tj8ch/var/yaml/facts --facts_terminus\\=yaml --no-daemonize --color\\=false --environment\\=production --hiera_config\\=/tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17645-3tj8ch/hiera.yaml --environmentpath\\=/tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17645-3tj8ch/environments --vardir\\=/tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17645-3tj8ch/var --logdir\\=/tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17645-3tj8ch/var --ssldir\\=/tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17645-3tj8ch/var/ssl --confdir\\=/tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17645-3tj8ch"]
D, [2021-08-04T14:07:24.519711 #17646] DEBUG -- : (to) Try 1 executing Puppet 7.5.0: /opt/puppetlabs/puppet/bin/puppet catalog compile puppetserver3.jnb1.host-h.net --no-storeconfigs --factpath=/tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17646-1fvvocu/var/yaml/facts --facts_terminus=yaml --no-daemonize --color=false --environment=production --hiera_config=/tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17646-1fvvocu/hiera.yaml --environmentpath=/tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17646-1fvvocu/environments --vardir=/tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17646-1fvvocu/var --logdir=/tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17646-1fvvocu/var --ssldir=/tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17646-1fvvocu/var/ssl --confdir=/tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17646-1fvvocu
D, [2021-08-04T14:07:24.520401 #17646] DEBUG -- : ["Execute: /tmp/ocd-ipc-20210804-17644-muckvt/ocd-scriptrunner20210804-17646-mauv76/puppet.sh catalog compile puppetserver3.jnb1.host-h.net --no-storeconfigs --factpath\\=/tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17646-1fvvocu/var/yaml/facts --facts_terminus\\=yaml --no-daemonize --color\\=false --environment\\=production --hiera_config\\=/tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17646-1fvvocu/hiera.yaml --environmentpath\\=/tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17646-1fvvocu/environments --vardir\\=/tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17646-1fvvocu/var --logdir\\=/tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17646-1fvvocu/var --ssldir\\=/tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17646-1fvvocu/var/ssl --confdir\\=/tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17646-1fvvocu"]
D, [2021-08-04T14:07:25.733573 #17645] DEBUG -- : ["STDERR: Error: Evaluation Error: Error while evaluating a Function Call, Could not find class ::profiles::apt::base for puppetserver3.jnb1.host-h.net (file: /tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17645-3tj8ch/environments/production/manifests/sites.pp, line: 21, column: 1) on node puppetserver3.jnb1.host-h.net"]
D, [2021-08-04T14:07:25.733681 #17645] DEBUG -- : ["STDERR: Error: Evaluation Error: Error while evaluating a Function Call, Could not find class ::profiles::apt::base for puppetserver3.jnb1.host-h.net (file: /tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17645-3tj8ch/environments/production/manifests/sites.pp, line: 21, column: 1) on node puppetserver3.jnb1.host-h.net"]
D, [2021-08-04T14:07:25.733831 #17645] DEBUG -- : ["STDERR: Error: Could not call 'find' on 'catalog': Evaluation Error: Error while evaluating a Function Call, Could not find class ::profiles::apt::base for puppetserver3.jnb1.host-h.net (file: /tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17645-3tj8ch/environments/production/manifests/sites.pp, line: 21, column: 1) on node puppetserver3.jnb1.host-h.net"]
D, [2021-08-04T14:07:25.733893 #17645] DEBUG -- : ["STDERR: Error: Could not call 'find' on 'catalog': Evaluation Error: Error while evaluating a Function Call, Could not find class ::profiles::apt::base for puppetserver3.jnb1.host-h.net (file: /tmp/ocd-ipc-20210804-17644-muckvt/ocd-builddir-20210804-17645-3tj8ch/environments/production/manifests/sites.pp, line: 21, column: 1) on node puppetserver3.jnb1.host-h.net"]
D, [2021-08-04T14:07:25.734031 #17645] DEBUG -- : ["STDERR: Error: Try 'puppet help catalog compile' for usage"]
D, [2021-08-04T14:07:25.734087 #17645] DEBUG -- : ["Exit status: 1"]
W, [2021-08-04T14:07:25.734322 #17645]  WARN -- : Puppet command failed: STDOUT:

While there may still be errors, it's OK because it at least compiles and runs fine when I pass my original command in (Related to 7.5.0):
root@ci-ps2:/etc/puppetlabs/code/environments/production# octocatalog-diff -n puppetserver3.jnb1.host-h.net --bootstrapped-from-dir /etc/puppetlabs/code/environments/production --bootstrapped-to-dir /etc/puppetlabs/code/environments/sc_jb_octocatalog --from-environment production --to-environment sc_jb_octocatalog -f production -t sc_jb_octocatalog --hiera-config /etc/puppetlabs/code/hiera.yaml
I, [2021-08-04T14:09:45.909317 #17907]  INFO -- : Catalogs compiled for puppetserver3.jnb1.host-h.net
W, [2021-08-04T14:09:45.956924 #17907]  WARN -- : Resource File[/tmp/ocd-ipc-20210804-17907-1em95pc/ocd-builddir-20210804-17908-k90fjg/routes.yaml] appears to depend on catalog compilation directory. Suppressed from results.
I, [2021-08-04T14:09:45.994797 #17907]  INFO -- : Diffs computed for puppetserver3.jnb1.host-h.net
diff production/puppetserver3.jnb1.host-h.net sc_jb_octocatalog/puppetserver3.jnb1.host-h.net
*******************************************
- Anchor[apt_key 126C0D24BD8A2942CC7DF8AC7638D0442B90D010 present]
*******************************************
- Anchor[apt_key 46095ACC8548582C1A2699A9D27D666CD88E42B4 present]
*******************************************
- Anchor[apt_key 5921BC1D903D6E0353C985BB9F89253B1E83EA92 present]
*******************************************
- Anchor[apt_key 641A1497F1B11BEA945F840FE5D882B28657AE28 present]
*******************************************
- Anchor[apt_key 84FAA9983B24AEF24D6C87F1FEBB7D1812576482 present]
*******************************************
- Anchor[apt_key A1848F5352D022B9471D83D0082AB56BA14FE591 present]
*******************************************
- Anchor[apt_key D6811ED3ADEEB8441AF5AA8F4528B6CD9E61EF26 present]
*******************************************
- Anchor[apt_key E4F0322E098979EDCBD808A5F43E3F9AA388F110 present]
*******************************************
- Anchor[apt_key ED6D65271AACF0FF15D123036FB2A1C265FFB764 present]
*******************************************
- Anchor[apt_key FE516C8A46A7D43A6741C0E3CEBBD0E85262FCF5 present]
*******************************************
- Anchor[ipmi::begin]
*******************************************
- Anchor[ipmi::end]
*******************************************
- Anchor[kernelcare::begin]

Bootstrap on Puppetserver 6.10.0:
root@gitlab-puppet-ci:/etc/puppetlabs/code/environments/production# /usr/local/bin/octocatalog-diff -d --bootstrap-then-exit --bootstrapped-from-dir=/tmp/octo-test
D, [2021-08-04T14:11:01.279265 #33238] DEBUG -- : Running octocatalog-diff 2.1.0 with ruby 2.5.1
D, [2021-08-04T14:11:01.279340 #33238] DEBUG -- : Command line arguments: ["-d", "--bootstrap-then-exit", "--bootstrapped-from-dir=/tmp/octo-test"]
D, [2021-08-04T14:11:01.279384 #33238] DEBUG -- : Running on host gitlab-puppet-ci (x86_64-linux-gnu)
D, [2021-08-04T14:11:01.279718 #33238] DEBUG -- : Cached master dir: bootstrapped=eca4c263ed3d9a554ef6d4876dcb6e998e1fcfba; current=eca4c263ed3d9a554ef6d4876dcb6e998e1fcfba
D, [2021-08-04T14:11:01.279769 #33238] DEBUG -- : Begin bootstrap_then_exit
D, [2021-08-04T14:11:01.279823 #33238] DEBUG -- : Begin 1 bootstrap(s)
D, [2021-08-04T14:11:01.279889 #33238] DEBUG -- : Initialized parallel task result array: size=1
D, [2021-08-04T14:11:01.281435 #33238] DEBUG -- : Launched pid=33240 for index=0
D, [2021-08-04T14:11:01.281563 #33240] DEBUG -- : Begin bootstrap from_dir /tmp/octo-test for origin/master
D, [2021-08-04T14:11:01.281785 #33240] DEBUG -- : Begin git checkout /etc/puppetlabs/code/environments/production:origin/master -> /tmp/octo-test
D, [2021-08-04T14:11:01.297885 #33240] DEBUG -- : ["Exit status: 0"]
D, [2021-08-04T14:11:01.297994 #33240] DEBUG -- : Success git archive /etc/puppetlabs/code/environments/production:origin/master
D, [2021-08-04T14:11:01.298054 #33240] DEBUG -- : Success git checkout /etc/puppetlabs/code/environments/production:origin/master -> /tmp/octo-test
D, [2021-08-04T14:11:01.298130 #33240] DEBUG -- : Success bootstrap from_dir /tmp/octo-test for origin/master
D, [2021-08-04T14:11:01.301887 #33238] DEBUG -- : PID=33240 completed in 0.0204592 seconds, 6236 bytes
D, [2021-08-04T14:11:01.301974 #33238] DEBUG -- : All child processes completed with no exceptions raised
D, [2021-08-04T14:11:01.302015 #33238] DEBUG -- : Success bootstrap_directory for from_dir
D, [2021-08-04T14:11:01.302062 #33238] DEBUG -- : Success bootstrap_then_exit
I, [2021-08-04T14:11:01.302115 #33238]  INFO -- : Successfully completed --bootstrap-then-exit action

Testing catalog compilation on Puppetserver 6.10.0:
oot@gitlab-puppet-ci:/etc/puppetlabs/code/environments/production# /usr/local/bin/octocatalog-diff -d -n puppetserver3.jnb1.host-h.net -o /tmp/catalog.json --bootstrapped-to-dir=$PWD --catalog-only
D, [2021-08-04T14:11:49.636732 #33315] DEBUG -- : Running octocatalog-diff 2.1.0 with ruby 2.5.1
D, [2021-08-04T14:11:49.636863 #33315] DEBUG -- : Command line arguments: ["-d", "-n", "puppetserver3.jnb1.host-h.net", "-o", "/tmp/catalog.json", "--bootstrapped-to-dir=/etc/puppetlabs/code/environments/production", "--catalog-only"]
D, [2021-08-04T14:11:49.636893 #33315] DEBUG -- : Running on host gitlab-puppet-ci (x86_64-linux-gnu)
D, [2021-08-04T14:11:49.636922 #33315] DEBUG -- : Compiling catalog for puppetserver3.jnb1.host-h.net
D, [2021-08-04T14:11:49.637094 #33315] DEBUG -- : Initialized OctocatalogDiff::Catalog::Noop for from-catalog
D, [2021-08-04T14:11:49.637649 #33315] DEBUG -- : Initialized OctocatalogDiff::Catalog::Computed for to-catalog
D, [2021-08-04T14:11:49.637713 #33315] DEBUG -- : Disabling --compare-file-text; not supported by OctocatalogDiff::Catalog::Noop
D, [2021-08-04T14:11:49.637854 #33315] DEBUG -- : Initialized parallel task result array: size=2
D, [2021-08-04T14:11:49.640559 #33315] DEBUG -- : Launched pid=33317 for index=0
D, [2021-08-04T14:11:49.640616 #33317] DEBUG -- : Begin build_catalog for origin/master
D, [2021-08-04T14:11:49.640798 #33317] DEBUG -- : Setting up Puppet catalog build for origin/master
D, [2021-08-04T14:11:49.640926 #33317] DEBUG -- : Catalog for origin/master will be built with OctocatalogDiff::Catalog::Noop
D, [2021-08-04T14:11:49.641027 #33317] DEBUG -- : Calling build for object OctocatalogDiff::Catalog::Noop
D, [2021-08-04T14:11:49.641440 #33317] DEBUG -- : Catalog for origin/master successfully built with OctocatalogDiff::Catalog::Noop in 0.0003801 seconds
D, [2021-08-04T14:11:49.641629 #33317] DEBUG -- : Success build_catalog for origin/master
D, [2021-08-04T14:11:49.642952 #33315] DEBUG -- : Launched pid=33320 for index=1
D, [2021-08-04T14:11:49.643011 #33320] DEBUG -- : Begin build_catalog for .
D, [2021-08-04T14:11:49.643144 #33320] DEBUG -- : Setting up Puppet catalog build for .
D, [2021-08-04T14:11:49.643224 #33320] DEBUG -- : Catalog for . will be built with OctocatalogDiff::Catalog::Computed
D, [2021-08-04T14:11:49.643334 #33320] DEBUG -- : Calling build for object OctocatalogDiff::Catalog::Computed
D, [2021-08-04T14:11:49.643518 #33320] DEBUG -- : Start retrieving facts for puppetserver3.jnb1.host-h.net from OctocatalogDiff::Catalog::Computed
D, [2021-08-04T14:11:49.643580 #33320] DEBUG -- : Retrieving facts from PuppetDB
D, [2021-08-04T14:11:49.644053 #33315] DEBUG -- : PID=33317 completed in 0.0034251 seconds, 6663 bytes
D, [2021-08-04T14:11:49.860288 #33320] DEBUG -- : Failed build_catalog for .: Zlib::StreamError stream error
D, [2021-08-04T14:11:49.865634 #33315] DEBUG -- : PID=33320 completed in 0.2227229 seconds, 11780 bytes
Traceback (most recent call last):
	52: from /usr/local/bin/octocatalog-diff:23:in `<main>'
	51: from /usr/local/bin/octocatalog-diff:23:in `load'
	50: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/bin/octocatalog-diff:34:in `<top (required)>'
	49: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/cli.rb:103:in `cli'
	48: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/cli.rb:209:in `catalog_only'
	47: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/api/v1.rb:15:in `catalog'
	46: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/api/v1/catalog-compile.rb:35:in `catalog'
	45: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/catalogs.rb:29:in `catalogs'
	44: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/catalogs.rb:92:in `build_catalog_parallelizer'
	43: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/parallel.rb:94:in `run_tasks'
	42: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/parallel.rb:114:in `run_tasks_parallel'
	41: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/parallel.rb:114:in `each_with_index'
	40: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/parallel.rb:114:in `each'
	39: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/parallel.rb:117:in `block in run_tasks_parallel'
	38: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/parallel.rb:117:in `fork'
	37: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/parallel.rb:119:in `block (2 levels) in run_tasks_parallel'
	36: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/parallel.rb:197:in `execute_task'
	35: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/parallel.rb:34:in `execute'
	34: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/parallel.rb:34:in `call'
	33: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/catalogs.rb:241:in `build_catalog'
	32: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/catalog.rb:96:in `build'
	31: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/catalog/computed.rb:109:in `build_catalog'
	30: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/catalog-util/facts.rb:27:in `facts'
	29: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/catalog-util/facts.rb:83:in `compute_facts'
	28: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/catalog-util/facts.rb:50:in `facts_from_puppetdb'
	27: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/catalog-util/facts.rb:50:in `new'
	26: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/facts.rb:31:in `initialize'
	25: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/facts/puppetdb.rb:40:in `fact_retriever'
	24: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/facts/puppetdb.rb:40:in `times'
	23: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/facts/puppetdb.rb:42:in `block in fact_retriever'
	22: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/puppetdb.rb:81:in `get'
	21: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/puppetdb.rb:101:in `_get'
	20: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/puppetdb.rb:101:in `each'
	19: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/puppetdb.rb:118:in `block in _get'
	18: from /var/lib/gems/2.5.0/gems/octocatalog-diff-2.1.0/lib/octocatalog-diff/util/httparty.rb:18:in `get'
	17: from /var/lib/gems/2.5.0/gems/httparty-0.18.1/lib/httparty.rb:627:in `get'
	16: from /var/lib/gems/2.5.0/gems/httparty-0.18.1/lib/httparty.rb:508:in `get'
	15: from /var/lib/gems/2.5.0/gems/httparty-0.18.1/lib/httparty.rb:594:in `perform_request'
	14: from /var/lib/gems/2.5.0/gems/httparty-0.18.1/lib/httparty/request.rb:145:in `perform'
	13: from /usr/lib/ruby/2.5.0/net/http.rb:1458:in `request'
	12: from /usr/lib/ruby/2.5.0/net/http.rb:910:in `start'
	11: from /usr/lib/ruby/2.5.0/net/http.rb:1460:in `block in request'
	10: from /usr/lib/ruby/2.5.0/net/http.rb:1467:in `request'
	 9: from /usr/lib/ruby/2.5.0/net/http.rb:1505:in `transport_request'
	 8: from /usr/lib/ruby/2.5.0/net/http/response.rb:166:in `reading_body'
	 7: from /usr/lib/ruby/2.5.0/net/http/response.rb:229:in `body'
	 6: from /usr/lib/ruby/2.5.0/net/http/response.rb:204:in `read_body'
	 5: from /usr/lib/ruby/2.5.0/net/http/response.rb:283:in `read_body_0'
	 4: from /usr/lib/ruby/2.5.0/net/http/response.rb:261:in `inflater'
	 3: from /usr/lib/ruby/2.5.0/net/http/response.rb:261:in `new'
	 2: from /usr/lib/ruby/2.5.0/net/http/response.rb:358:in `initialize'
	 1: from /usr/lib/ruby/2.5.0/net/http/response.rb:358:in `new'
/usr/lib/ruby/2.5.0/net/http/response.rb:358:in `initialize': stream error (Zlib::StreamError)

I'm hoping someone can shed some light or provide some insight - I'm a bit stumped..

@JoshuaSmeda, have you found the fix for the issue? I have faced the similar one.

Unfortunately not.
I moved to puppet-catalog diff instead and that worked without issues.
On Tue, 19 Apr 2022, 18:14 sergiik, @.***> wrote:

@JoshuaSmeda https://github.com/JoshuaSmeda, have you found the fix for
the issue? I have faced the similar one.
—
Reply to this email directly, view it on GitHub
https://github.com/github/octocatalog-diff/issues/256#issuecomment-1102838814,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJRBWDT5JDFWHIDFMPP52F3VF3LVLANCNFSM5BRABKUA
.
You are receiving this because you were mentioned.Message ID:
@.***>


Emoji ending in 20E3 have incomplete first byte.

The unicode values ending in 20E3 appear in twemoji as 39-20E3 for 9⃣ for example. The first byte should be complete: 0039-20E3 for consistency.

appear in twemoji as ...

in the documentation? in the assets files? in the JS library? any code example? what would be solved?

Ah sorry. The asset names (all .ai, .svg, and .png files) and any code that references them all have incomplete first bytes. This only affects the 10 emoji ending in 20e3.

The asset names (all .ai, .svg, and .png files) and any code that references them all have incomplete first bytes.

that makes them all consistent, right?
what are you trying to solve? it's easier for us to ignore prefixed zeroes, as these have effectively no meaning whatsoever for our needs.


Is it only Pexels?

Hi all,
So, it's only Pexels stock videos not AI generated like the sample featured video?

The pexels api can be replaced with any image generation api and it will work the same way


Adds ability to filter journeys by destination station

Provides a new optional parameter by which to filter by destination station. This enables you to get a list of journeys from station AAA that will also be stopping at BBB. Destination doesn't have to be the final destination of the train.

Excellent - Thanks

Did you consider adding an arrivals option ?
Similar to above but shown from the perspective of station BBB.


Claimable Balances Query slow on Horizon

Issue:
Claimable Balances query performing slow on SDF Horizon instance sporadically (50% of the time):
Query:
https://horizon.stellar.org/claimable_balances/{balance_id}/transactions?limit=1&order=asc
Issue:
This query is being used by a Customer to locate a transaction which created a claimable balance and retrieve its memo (since they can’t store a memo with claimable balance itself). While this call was not terribly fast, it got really bad this week, with the call taking approximately 8 seconds to either complete or error out with the following:
{

  "type": "https://stellar.org/horizon-errors/service_unavailable",

  "title": "Service Unavailable",

  "status": 503,

  "detail": "The request cannot be serviced at this time."

}

It works about 50% of the time with a 503 occurring the other 50%.
Sample URL:
https://horizon.stellar.org/claimable_balances/0000000028b32c721976af53fa0419eba129f3da70168f1e39822a25886375abad9599da/transactions?limit=1&order=asc

Curious if the database optimization changes in Core 19 may have impacted this or if anyone has observed issues with this query. Also, is there an easier way to get original transaction which created claimable balance?

Note that this query returns pretty fast on an ingestion filtered instance.

Could this be related (ie: performance degradation from accumulated unreaped CB history): https://github.com/stellar/go/issues/4396

@jcx120 , this appears to be duplicate, reporting slow query response situation on cb API path as reported on #4455 , which had a PR merged for fix - https://github.com/stellar/go/pull/4477, so I think this one can be moved to closed/done same as #4455, I think it will be in next release after 2.19.0.


Pre-commit hook instructions on Windows

Updated from https://github.com/godotengine/godot/issues/37431#issuecomment-606224542

Thanks!


Change camel case field names to snake case in process package

As the test failures show. This is a breaking change so the release notes should include a "what your code looked like before, what it looks like after" explanation.

Hi @emreoztr,
The changelog - changed label was added to this pull request; all PRs with a changelog label need to have release notes included as part of the PR. If you haven't added release notes already, please do.
Release notes are added by creating a uniquely named file in the .release-notes directory. We suggest you call the file 3821.md to match the number of this pull request.
The basic format of the release notes (using markdown) should be:
## Title

End user description of changes, why it's important,
problems it solves etc.

If a breaking change, make sure to include 1 or more
examples what code would look like prior to this change
and how to update it to work after this change.

Thanks.

This should be rebased against main to pick up changes.
Also, this is a breaking change because those fields are public, so... there are at least some tests that will need to be updated.

@emreoztr it says this is your PR! Awesome! Let us know if you need any assistance.

@emreoztr this will need to be rebased against main. Once that happens, you'll find that an additional field that needs to be changed was added that also needs to be changed.

I just realized that the fields in question are on a package private class so no release notes are needed, you can delete them. Sorry about that.

There's an extra file that needs to be removed.

Sorry @SeanTAllen , I removed it

Thanks @emreoztr. Awesome first contribution!


AWS Linux aware haproxy-marathon-bridge

Check for AWS Linux.  If lsb_release does not exist check /etc/system-release to see if the OS is Amazon Linux.  If it is, set OS to AmazonAMI.
I chose not to install the redhat-lsb package on AWS because of the 59 dependencies.  Another solution could be to detect AWS Linux, install redhat-lsb and use the output from it.  The value if you do that is the same, AmazonAMI.

@lloesche Can you please take a look?

lgtm


Live diagnostics can cause multiple incorrect NuGet package restore attempts

In a new cell start slowly typing #r "nuget: Newtonsoft.Json".  When you finally commit the cell, multiple NuGet packages are added to the restore list.  E.g.,
Installing package Newtonsoft.Json.....
Installing package Newtons.....
Installing package Newt.....

Resubmitting the cell has the same effect.
Workaround: restart the notebook kernel and execute a cell with the text already present.

This is probably related to anonymous commands generated during submission splitting.

Fixed by #635.


I tried copying the garage-door-controller in /home/pi/

When i open the index.html..i am not able to see the anything except "My Garage"..not able to see any icons to select so not sure whether I need to copy the pictures anywhere else along with the folder
Also when i am running the python controller.py..i am getting the below error
pi@sandeep-pi ~/garage-door-controller $ python controller.py
Traceback (most recent call last):
File "controller.py", line 330, in
controller = Controller(json.load(config_file))
File "/usr/lib/python2.7/json/init.py", line 290, in load
**kw)
File "/usr/lib/python2.7/json/init.py", line 338, in loads
return _default_decoder.decode(s)
File "/usr/lib/python2.7/json/decoder.py", line 366, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python2.7/json/decoder.py", line 382, in raw_decode
obj, end = self.scan_once(s, idx)
ValueError: Expecting , delimiter: line 28 column 20 (char 459)
pi@sandeep-pi ~/garage-door-controller $
can you please help here ???

I did not provide any details for the below one
"openhab" :
{
"server" : "<SERVER_IP_ADDRESS>",
"port" : "<OPENHAB_SERVER_PORT>"
}
then I am getting the below
pi@sandeep-pi ~/garage-door-controller $ python controller.py
Unhandled error in Deferred:
Unhandled Error
Traceback (most recent call last):
File "controller.py", line 332, in
controller.run()
File "controller.py", line 195, in run
task.LoopingCall(self.status_check).start(0.5)
File "/usr/lib/python2.7/dist-packages/twisted/internet/task.py", line 173, in start
self()
File "/usr/lib/python2.7/dist-packages/twisted/internet/task.py", line 218, in call
d = defer.maybeDeferred(self.f, *self.a, **self.kw)
---  ---
File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 139, in maybeDeferred
result = f(*args, **kw)
File "controller.py", line 116, in status_check
self.update_openhab(door.openhab_name, new_state)
File "controller.py", line 175, in update_openhab
conn = httplib.HTTPConnection("%s:%s" % (config['server'], config['port']))
File "/usr/lib/python2.7/httplib.py", line 712, in init
(self.host, self.port) = self._get_hostport(host, port)
File "/usr/lib/python2.7/httplib.py", line 754, in _get_hostport
raise InvalidURL("nonnumeric port: '%s'" % host[i+1:])
httplib.InvalidURL: nonnumeric port: '<OPENHAB_SERVER_PORT>'
Traceback (most recent call last):
File "controller.py", line 332, in
controller.run()
File "controller.py", line 212, in run
reactor.listenTCP(self.config['site']['port'], site)  # @UndefinedVariable
File "/usr/lib/python2.7/dist-packages/twisted/internet/posixbase.py", line 495, in listenTCP
p.startListening()
File "/usr/lib/python2.7/dist-packages/twisted/internet/tcp.py", line 979, in startListening
raise CannotListenError(self.interface, self.port, le)
twisted.internet.error.CannotListenError: Couldn't listen on any:8002: [Errno 98] Address already in use.

I tried changing the port to different ones but none of them are working.
my config files are here are
/etc/webiopi/config
[GPIO]
Initialize following GPIOs with given function and optional value
This is used during WebIOPi start process
#21 = IN
#23 = OUT 0
#24 = OUT 0
#26 = OUT 1
7 = OUT 0
8 = OUT 0
[HTTP]
HTTP Server configuration
enabled = true
port = 8081
/home/pi/garage-door-controller/config.json
"openhab" :
{
"server" : "<SERVER_IP_ADDRESS>",
"port" : "<OPENHAB_SERVER_PORT>"
},
"site" :
{
"port":7001,
"username":"xxxxx",
"password":"xxxxx"
},
"doors" :
{
"left" :
{
"name" : "LEFT",
"relay_pin" : 24,
"state_pin" : 17,
"approx_time_to_close" : 10,
"approx_time_to_open" : 13,
"openhab_name" : "g_door_left"
},
"right" :
{
"name" : "RIGHT",
"relay_pin" : 26,
"state_pin" : 27,
"approx_time_to_close" : 10,
"approx_time_to_open" : 13,
"openhab_name" : "g_door_right"
}
}
}

What was the fix for the issue from the first post?

My suspicion is that your config file is not valid json.  Can you post the raw config file?

Seems to be the result of forgetting quotes in the JSON file.

I think I;m having the same issue although slightly different (char#).  I simply copied (cloned) from the links provided ... is there a config that NEEDS to be changed specific to each install that we missed?

Three is the config.json file that should be changed to your needs.  What is the issue you're having?


Slow compilation using sparse diagonal matrices in a quadratic form

Describe the bug
When attempting to minimize a quadratic form (similar to the factor covariance model found at https://colab.research.google.com/github/cvxgrp/cvx_short_course/blob/master/applications/portfolio_optimization.ipynb) with a large (~18k entries) sparse diagonal matrix I run into an extremely slow (+10 minutes) compilation time when using MOSEK.
Below I include minimal code to reproduce the issue. Notice that obj_func and obj_func2 are mathematically equivalent. obj_func compiles quickly with both MOSEK and OSQP. Whereas obj_func2 compiles quickly with OSQP but stalls with MOSEK.
To Reproduce
import numpy as np
import cvxpy as cp
from scipy import sparse as sp

n = 18000
m = 80
np.random.seed(42)
sigma_tilde = np.random.randn(m, m)
sigma_tilde = sigma_tilde.T.dot(sigma_tilde)
D = sp.diags(np.random.uniform(0, 0.9, size=n))
F = np.random.randn(n, m)
w = cp.Variable(n)
f = cp.Variable(m)

obj_func = cp.quad_form(f, sigma_tilde) + cp.sum_squares(np.sqrt(D)@(w))
obj_func2 = cp.quad_form(f, sigma_tilde) + cp.quad_form(w, D)

prob = cp.Problem(cp.Minimize(obj_func2),
                     [cp.sum(w) == 1,
                      f == F.T@w,
                      0 <= w,
                      w <= 1])

#prob.solve(verbose=True, solver='OSQP')
# Using MOSEK leads to a +9 minute compilation time
prob.solve(verbose=True, solver='MOSEK')

Expected behavior
Fast (under a few seconds) compilation.
Output
===============================================================================
                                     CVXPY
                                    v1.1.13
===============================================================================
(CVXPY) Aug 04 05:08:21 PM: Your problem has 18080 variables, 4 constraints, and 0 parameters.
(CVXPY) Aug 04 05:08:21 PM: It is compliant with the following grammars: DCP, DQCP
(CVXPY) Aug 04 05:08:21 PM: (If you need to solve this problem multiple times, but with different data, consider using parameters.)
(CVXPY) Aug 04 05:08:21 PM: CVXPY will first compile your problem; then, it will invoke a numerical solver to obtain a solution.
-------------------------------------------------------------------------------
                                  Compilation
-------------------------------------------------------------------------------
(CVXPY) Aug 04 05:08:21 PM: Compiling problem (target solver=MOSEK).
(CVXPY) Aug 04 05:08:21 PM: Reduction chain: Dcp2Cone -> CvxAttr2Constr -> ConeMatrixStuffing -> MOSEK
(CVXPY) Aug 04 05:08:21 PM: Applying reduction Dcp2Cone

Process remains at this step for about 10 minutes and all the cores in my machine are maxed out.
Version

OS: macOS Big Sur Version 11.3.1 (20E241)
CVXPY Version: 1.1.13

Additional context
My intuition is that the issue is related to the internal representation of the problem and a specific step in the reduction chain. An equivalent problem (included above) is solved in under a second and indicates that the reduction chain "path" leads to a different representation which perhaps avoids a dense representation of the sparse matrix.

The problem is line 192 of quad_form.py, in decom_quad. We need the factorization to work for sparse matrices (without conversion to dense).

@SteveDiamond we could check if MOSEK is installed, and if so, use https://docs.mosek.com/latest/pythonapi/optimizer-env.html#mosek.env.computesparsecholesky to compute the sparse Cholesky decomposition. I also looked at SciPy but it seems they don't support sparse Cholesky factorization. We can determine if we need Cholesky for A or -A (posdef and negdef respectively) by looking at any nonzero diagonal entry of A (a matrix A is positive definite only if its diagonal is elementwise positive).

In the first model it only needs to factorize of a small matrix, and in the second a huge matrix. So the first one is closer to the direct conic model of
https://docs.mosek.com/modeling-cookbook/qcqo.html#example-factor-model
and goes to show that if you have the factor model and a conic solver then it pays off to work directly in conic form, rather than spending time to form the QP just to have someone (CVXPY of MOSEK internally) spend even more time later undoing that work by computing Cholesky.
Apologies for a slight offtopic.

@aszekMosek agreed! In practice we solved this issue with a reformulation. It would be better though if the naive quadratic formulation also worked well.

Follow-up. A few comments back I suggested we use sparse Cholesky to determine positive definiteness, but pointed out that SciPy has no such functionality. We could consider using Eigen's SparseCholesky module. We already rely on Eigen for cvxcore, so this doesn't add a dependency.
@akshayka @SteveDiamond what do you think? If using some of Eigen's sparse linear algebra functionality is on the table, then we could even use it as part of canonicalization, rather than just checking if something is DCP.

I'd be open to using Eigen in this way.

Resolved by #2125! To appear in CVXPY 1.4.


Scrum 6

Scrum Report Steps
Post a comment in this issue with:

Your Name
Answer these 3 questions

What did you work on this past iteration (2 weeks)?
What were any major issues/challenges you ran into?
What do you plan to work on for this coming iteration (2 weeks)?

Ensure answers are 5 sentences MAX

Grading Rubric:
2:
Includes all 3 points. Demonstrates a bit of meaningful reflection on at least one item in the report.
1:
Simplistic, or no meaningful, specific information.
0:
Missing or Late.

Scrum Report for Kevin Chung
What did you work on this past iteration (2 weeks)?

Styling and aligning the color scheme throughout the entire application, identifying / fixing bugs, improving responsiveness of the overall application and preparing for the final demo.

What were any major issues/challenges you ran into?

Nothing at this time.

What would you have planned to work on if you were to continue on the project?

Implement the frontend design for fitness/meal plans, as well as the statistics, after the backend implementation of dynamically updating fitness/meal plans based on users' logged progress history and user feedback has been completed.

Scrum Report for Kenny Cheng
What did you work on this past iteration (2 weeks)?
Fixing SO many bugs with responsiveness, accessibility, UI aesthetics, errors, and edge cases. Styling accessibility and consistency across the entire platform. Small features such as browser notifications when plans are generates and Google login.
What were any major issues/challenges you ran into?
Styling and finding an accessible color combination was an enormous challenge especially since we initial decided on a color scheme everyone liked. Additionally, because we are using a UI library, styling was particularly difficult as there were many ways to style, with only a few method working which required a lot of guess and check. Finally, constantly running into bugs or edge cases that may have been out of scope to fix as we wrapped up the project, although we found ways to work around it.
What would you have planned to work on if you were to continue on the project?
I would like to create our own LLM or AI model that can create more accurate fitness and meal plans for the user to improve the value our application can give customers. Additionally, I want to deploy our infrastructure on a cloud platform such as AWS and set up CI/CD pipelines, with dev and production environments. Finally, I want to work on a cool computer vision feature we discussed, a posture checker that adds onto the personal assistant features of our app.

Scrum Report for Jack Ji
What did you work on this past iteration (2 weeks)?
Mostly manual testing , bug report, minor bug fixes and overall final product adjustment. Also preparing for demo.
What were any major issues/challenges you ran into?
I was mostly working on the backend, any bugs or adjustments related to frontend was less familiar to me, and felt less productive during the final stretch except for QA.
What would you have planned to work on if you were to continue on the project?
Purchase a public domain for our product. With changes to Google Domains, a new alternative is probably needed. Add AdSense to webpage. Depending on the monetization method, we could implement different features, but I want to try AdSense and see just by marketing as a free service, how much can we generate with ads alone. Find a marketing strategy could also be an interesting area to explore. Just want to see how far can we take the product

Scrum Report for Davis Song
What did you work on this past iteration (2 weeks)?

Solo development of guided workouts, including all styling
Adding voice control feature
UI fixes all over the application
Created the presentation slides
Helped organize presentation structure and script

What were any major issues/challenges you ran into?

Rushed development of my guided workouts feature, I cut it close to the deadline
DId not implement a polyfill for voice control in time, for accessibility purposes it would have been best if I could have universal browser support
UI fixes were rushed, but did turn out well (we were lucky to have all members testing and improving different areas of the product)

What would you have planned to work on if you were to continue on the project?

Further improvements to site responsiveness
Add computer vision
Restyle guided workouts to be in line with rest of product, while maintaining visibility
Build a subscription service that securely collects payment data

Scrum Report for Kevin Wu
What did you work on this past iteration (2 weeks)?

Added accessibility support for screen readers
Bug fixes for the home page loading and schedule history
Merged in a PR that improves the efficiency of the schedule history API endpoint
Demo prep

What were any major issues/challenges you ran into?

As bugs came up near the deadline it made it more challenging to fix as we needed to fix the bug with ideally, small changes that are unlikely to introduce more bugs
Getting the whole application to support screen reader was tricky as some parts were hard to add keyboard support or be read in a manner that is understandable

What would you have planned to work on if you were to continue on the project?

Make the chat bot accessible. The chat bot was left out of the screen reader accessibility changes as I had concerns the responses in the bot would become spammy for use with a screen reader. Ideally, this can be resolved and also support voice input to make it easier to use.
Do some more investigations into the prompt engineering such that we can guard against all ways a user may try to adversely modify their schedule.


Workflow Config YAML Parser

Summary

[ ] add unit tests

Fixes #686
Checklist

[x] My code follows the code style of this project and passes ./lint-and-format.sh format.
[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] My change has adequate unit test coverage.

@homanp
why do we need the last part?
  @@unique([workflowId, createdAt])


dashing start error

i got this error with dashing start
bundler: failed to load command: thin (/usr/local/bin/thin)
NameError: uninitialized constant PGError
Did you mean?  TypeError
/home/mwb/PostgreSQL-Dashboard/jobs/pg_buffers.rb:66:in rescue in <top (required)>'   /home/mwb/PostgreSQL-Dashboard/jobs/pg_buffers.rb:16:in <top (required)>'
/var/lib/gems/2.3.0/gems/backports-3.11.3/lib/backports/std_lib.rb:9:in require'   /var/lib/gems/2.3.0/gems/backports-3.11.3/lib/backports/std_lib.rb:9:in require_with_backports'
/var/lib/gems/2.3.0/gems/dashing-1.3.7/lib/dashing/app.rb:171:in block in require_glob'   /var/lib/gems/2.3.0/gems/dashing-1.3.7/lib/dashing/app.rb:170:in each'
/var/lib/gems/2.3.0/gems/dashing-1.3.7/lib/dashing/app.rb:170:in require_glob'   /var/lib/gems/2.3.0/gems/dashing-1.3.7/lib/dashing/app.rb:181:in <top (required)>'
/var/lib/gems/2.3.0/gems/dashing-1.3.7/lib/dashing.rb:3:in require'   /var/lib/gems/2.3.0/gems/dashing-1.3.7/lib/dashing.rb:3:in <top (required)>'
config.ru:1:in require'   config.ru:1:in block in '
/var/lib/gems/2.3.0/gems/rack-1.5.5/lib/rack/builder.rb:55:in instance_eval'   /var/lib/gems/2.3.0/gems/rack-1.5.5/lib/rack/builder.rb:55:in initialize'
config.ru:1:in new'   config.ru:1:in '
/var/lib/gems/2.3.0/gems/thin-1.6.4/lib/rack/adapter/loader.rb:33:in eval'   /var/lib/gems/2.3.0/gems/thin-1.6.4/lib/rack/adapter/loader.rb:33:in load'
/var/lib/gems/2.3.0/gems/thin-1.6.4/lib/thin/controllers/controller.rb:182:in load_rackup_config'   /var/lib/gems/2.3.0/gems/thin-1.6.4/lib/thin/controllers/controller.rb:72:in start'
/var/lib/gems/2.3.0/gems/thin-1.6.4/lib/thin/runner.rb:200:in run_command'   /var/lib/gems/2.3.0/gems/thin-1.6.4/lib/thin/runner.rb:156:in run!'
/var/lib/gems/2.3.0/gems/thin-1.6.4/bin/thin:6:in <top (required)>'   /usr/local/bin/thin:23:in load'
/usr/local/bin/thin:23:in `<top (required)>'

addressable (2.5.2)
backports (3.11.3)
bigdecimal (1.2.8)
buftok (0.2.0)
bundler (1.16.1, 1.11.2)
coffee-script (2.2.0)
coffee-script-source (1.12.2)
daemons (1.2.6)
dashing (1.3.7)
did_you_mean (1.0.0)
domain_name (0.5.20180417)
equalizer (0.0.11)
et-orbi (1.1.0)
eventmachine (1.2.5)
execjs (2.0.2)
hike (1.2.3)
http (3.2.1, 3.2.0)
http-cookie (1.0.3)
http-form_data (2.1.0)
http_parser.rb (0.6.0)
io-console (0.4.5)
json (1.8.3)
memoizable (0.4.2)
minitest (5.8.4)
molinillo (0.4.3)
multi_json (1.13.1)
multipart-post (2.0.0)
mustermann (1.0.2)
naught (1.1.0)
net-http-persistent (2.9.4)
net-telnet (0.1.1)
pg (1.0.0)
power_assert (0.2.7)
psych (2.0.17)
public_suffix (3.0.2)
rack (2.0.5, 1.5.5)
rack-protection (2.0.1, 1.5.5)
rack-test (1.0.0)
rake (10.5.0)
rdoc (4.2.1)
rufus-scheduler (3.4.2, 2.0.24)
sass (3.2.19)
simple_oauth (0.3.1)
sinatra (2.0.1, 1.4.8)
sinatra-contrib (1.4.7)
sprockets (2.10.2)
test-unit (3.1.7)
thin (1.7.2, 1.6.4)
thor (0.20.0, 0.19.1)
thread_safe (0.3.6)
tilt (2.0.8, 1.4.1)
twitter (6.2.0)
tzinfo (1.2.5)
unf (0.1.4)
unf_ext (<IP_ADDRESS>)

Hi !
Can you try to remove line 27 from the dashboard file (postgresql.erb) to check if the same errors occurs on other widgets ?
https://github.com/daamien/PostgreSQL-Dashboard/blob/master/dashboards/postgresql.erb#L27
Thanks,

Same Error
dashing start
bundler: failed to load command: thin (/usr/local/bin/thin)
NameError: uninitialized constant PGError
Did you mean?  TypeError
/home/mwb/PostgreSQL-Dashboard/jobs/pg_buffers.rb:66:in rescue in <top (required)>'   /home/mwb/PostgreSQL-Dashboard/jobs/pg_buffers.rb:16:in <top (required)>'
/var/lib/gems/2.3.0/gems/backports-3.11.3/lib/backports/std_lib.rb:9:in require'   /var/lib/gems/2.3.0/gems/backports-3.11.3/lib/backports/std_lib.rb:9:in require_with_backports'
/var/lib/gems/2.3.0/gems/dashing-1.3.7/lib/dashing/app.rb:171:in block in require_glob'   /var/lib/gems/2.3.0/gems/dashing-1.3.7/lib/dashing/app.rb:170:in each'
/var/lib/gems/2.3.0/gems/dashing-1.3.7/lib/dashing/app.rb:170:in require_glob'   /var/lib/gems/2.3.0/gems/dashing-1.3.7/lib/dashing/app.rb:181:in <top (required)>'
/var/lib/gems/2.3.0/gems/dashing-1.3.7/lib/dashing.rb:3:in require'   /var/lib/gems/2.3.0/gems/dashing-1.3.7/lib/dashing.rb:3:in <top (required)>'
config.ru:1:in require'   config.ru:1:in block in '
/var/lib/gems/2.3.0/gems/rack-1.5.5/lib/rack/builder.rb:55:in instance_eval'   /var/lib/gems/2.3.0/gems/rack-1.5.5/lib/rack/builder.rb:55:in initialize'
config.ru:1:in new'   config.ru:1:in '
/var/lib/gems/2.3.0/gems/thin-1.6.4/lib/rack/adapter/loader.rb:33:in eval'   /var/lib/gems/2.3.0/gems/thin-1.6.4/lib/rack/adapter/loader.rb:33:in load'
/var/lib/gems/2.3.0/gems/thin-1.6.4/lib/thin/controllers/controller.rb:182:in load_rackup_config'   /var/lib/gems/2.3.0/gems/thin-1.6.4/lib/thin/controllers/controller.rb:72:in start'
/var/lib/gems/2.3.0/gems/thin-1.6.4/lib/thin/runner.rb:200:in run_command'   /var/lib/gems/2.3.0/gems/thin-1.6.4/lib/thin/runner.rb:156:in run!'
/var/lib/gems/2.3.0/gems/thin-1.6.4/bin/thin:6:in <top (required)>'   /usr/local/bin/thin:23:in load'
/usr/local/bin/thin:23:in `<top (required)>'

se this is any miising info
PostgreSQL Dashboard config file
{
Connection
'host' 		=> 'localhost',
'port' 		=> '5432',
'options' 	=> '',  # Backend options
'tty'  		=> '',     # Obsolete
'dbname' 	=> 'pgdb',
'user'   	=> 'sa',
'password'	=> '*****',
Scheduler
'freq' 		=> '60s',
Twitter
Get your twitter keys & secrets:
https://dev.twitter.com/docs/auth/tokens-devtwittercom
'tw_consumer_key' 	 => 'YOUR_CONSUMER_KEY',
'tw_consumer_secret' 	 => 'YOUR_CONSUMER_SECRET',
'tw_config.access_token' => 'YOUR_OAUTH_TOKEN',
'tw_access_token_secret' => 'YOUR_OAUTH_SECRET'
}


unblock returns Task

This PR makes it so that the unblock function returns a Task (which implements Future) instead of an opaque Future. This gives the application more opportunity for optimization knowing the exact type of the future to be returned.
This also re-exports the Task type from async_task to make this easier to use.

Published in 1.2.0


"build-restler.py" fails on windows machine on line 127, i.e. when subprocess.run is executed

Description
In build-restler.py script, when the following function is executed:
completed_process = subprocess.run(f'{dirs.python_path} -m compileall -q {dirs.engine_build_dir}', shell=True, capture_output=True, check=True)
the build might fail if there is a space in the python executable full path.
Steps to reproduce
The build might fail if the "python_path" var has spaces in the python path. For example, my python executable was in "Program Files" dir, so it was failing due to the space in dir name and giving the following error:
Build failed!
Exit code: 1
b"'C:\\Program' is not recognized as an internal or external command,\r\noperable program or batch file.\r\n"
Removing engine compilation build directory...

Solution:
I modified the script as follows to make it work:
completed_process = subprocess.run([str(dirs.python_path), '-m', 'compileall', '-q', str(dirs.engine_build_dir)], shell=True, capture_output=True, check=True)
Expected results
No response
Actual results
No response
Environment details
Windows

I'm running into this as well.

can you share the error output of the script? If its the same error, can you try the solution in the post.

Hello @killswitch-2434,
Thank you for reporting this.  The fix will be merged shortly.
Thanks,
Marina


Logs screen has no buttons rendered

In the last version of vscode the logging screen is suddenly not working anymore (no buttons at all):

I looked in the webview console errors on what happens and this is the output when I try to get the logs of a pod:
logserrors.txt

(first one in text, second one as image in webview).

I have the same issue.

This error is the same as https://github.com/vscode-kubernetes-tools/vscode-kubernetes-tools/issues/1116 . It was fixed and merged but still not published. If you want you can use https://github.com/lstocchi/vscode-kubernetes-tools/blob/master/vscode-kubernetes-tools-1.3.6.vsix in the meantime. I hope to publish everything beginning of next week. Sorry for the trouble

Ok, I must have missed that issue (I did a search on logging, but I must have missed it somehow). The linked vsix indeed solves the issue.


Refactors the binary building process

Sets the GOBIN environment variable so that the binary is built
directly into the binary layer as opposed to being built and moved
Simplifies some structures in the code

After reviewing this PR and taking a look at https://github.com/paketo-buildpacks/go-mod/pull/57, it is clear that they solve the same problem, but in different ways. I'd like to merge this PR as it results in a simpler implementation, but I'd like to include the integration tests from @tylerphelan's PR. Does that sound reasonable?

@ryanmoran Doesn't the other PR have additional functionality on top of the refactor? If we want to roll that into this PR we can, or maybe I am just misunderstanding the other PR.

@ryanmoran I just realize I never pinged you telling you that the testing had been added. My bad!


ESP8266 Support

Firstly, thanks for a great tool for slot car tinkerers.  The library works great on an Arduino Uno.  I tried it on a ESP8266 NodeMCU and unfortunately the board starts rebooting and I get this in the serial monitor:
ets Jan  8 2013,rst cause:2, boot mode:(3,6)
load 0x4010f000, len 3424, room 16
tail 0
chksum 0x2e
load 0x3fff20b8, len 40, room 8
tail 0
chksum 0x2b
csum 0x2b
v00047aa0
~ld
I am assuming it has something to do with the ESP8266 and its ability to handle the CU read.  I was wondering if you had any suggestions.  Thanks in advance.

@darnold64: Thanks for your interest!
I tested the library with Arduino Uno/Nano and Raspberry Pi Pico, but not with ESP8266.
I have a NodeMCU board lying around somewhere, so I might give it a try, but it will take a while.
In the mean time, if you find a way to make this work on ESP8266, your input will surely be welcome!

Thomas, Thank you for the quick response.  As mentioned, the library works great with the Arduino Uno.  However, I am in the process of building some driver dashboards with TfT displays and was looking to use the ESP8266 or ESP32 to drive everything since I have a reasonable amount of experience with these boards. I managed to get the code to run without constantly resetting the board by doing the following: if (CarreraCommandPacket packet = cu.read(0)) I believe the ESP8266 doesn’t like blocking and so resets itself through the watchdog function waiting for the read to happen.  This is my theory anyway.  I may need to play around with the value for cu.read(). I haven’t had a chance to test it on the track yet (my laptop died on me yesterday).  Once I get the laptop working again I will let you know what happens. DeanSent from Dean's iPadOn Jan 8, 2023, at 2:11 PM, Thomas Kemmer<EMAIL_ADDRESS><EMAIL_ADDRESS>Thanks for your interest!I tested the library with Arduino Uno/Nano and Raspberry Pi Pico, but not with ESP8266.I have a NodeMCU board lying around somewhere, so I might give it a try, but it will take a while.In the mean time, if you find a way to make this work on ESP8266, your input will surely be welcome!—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>
I just re-checked, and both the CommandSniffer and DataLogger examples seem to work fine with my ESP8266 (NodeMCU V3) boards in the Arduino IDE with the "NodeMCU 1.0 (ESP-12E Module)" board selected.
Thinking about it, I guess I did do some tests with that board, at least some #ifdefs for ESP8266 do exist in the code - sorry, it's been a while...
However, if you don't connect your board to a Control Unit, it is reasonable the watchdog will reset the board when doing a blocking read() without timeout, since there won't be any data to return, so read() will wait forever. I was also able to reproduce this by switching off the Control Unit. So I guess as soon as you're able to connect again, things will turn out fine.

Thanks again.  I managed to revive my laptop and was able to test things on the track.  read(0) does the trick.  It works fine whether connected to the track or not--no resetting of the ESP and I am able to capture the CU messages.

@darnold: I added cu.read() timeouts to the examples, so there should be no more surprises on ESP8266 platforms. The "startlight" example should also show blinking LEDs if no connection to the CU can be established.
Thanks for your efforts!


Run Background Task when app is on closed and foreground state.

---> i want to run  react-native-background-job when application is on foreground as well as closed state.
---> this should happen when device is connected to internet.
my code is :     BackgroundJob.schedule({
jobKey: regularJobKey,
period: 5 * 1000,
networkType: BackgroundJob.NETWORK_TYPE_ANY,
allowExecutionInForeground: true
});
Current Behaviour:
---> schedule Job is working when app is opened(foreground state). but not runing when app is closed.
---> In emulator  Expected Bahaviour is working fine, but not working in mobile device.
Expected Bahaviour:
---> scheduled task should work when app is closed and app is open( in foreground state).
please help me  @imran1992   @vikeri @toteto @hkairi @Looveh @Looveh @toteto @MaximilianKindshofer @cristianocca @ivan-branets
Thanks In Advance.
**### More Info About My Project Specification **
Dependency Version : "react-native-background-job": "^2.1.1",
version of RN is: 0.50.3
react-native-cli: 2.0.1
My Device : windows-7, 64-bit , 8GB RAM

@prasanthyejje Could you create an example repo where this issue exists so that we can debug it?

react-native-background-job is not working run in android API 28

If this is related to #129 I'll close this issue and keep the other one open.

react-native-background-job is not working run in android API 28

the same issue for me how to handle that

Have you guys got anything on this ???


FEATURE REQUEST - PwnedPasswordsNTLM

Would you like have a tool or script added? Please include a link
Checker for PwnedPasswords in a Hashcat Dump of AD
Tool:
https://github.com/JacksonVD/PwnedPasswordsNTLM/releases
PwnedPasswordsList (too large to include):
https://haveibeenpwned.com/Passwords
Is your feature request related to a problem? Please describe.
It is nice to have this possibility if you are in the Blue Team, but also useful for Red Team in post exploitation.
If related to a problem, describe the solution you'd like
Find compromised passwords in use.
Describe alternatives you've considered
Easy enough to install this myself - just opened this issue because this might be useful for others.

@anlx-sw Thank you for opening the issue, this is definitely a useful tool. We will get it added.

Added with 1.3 release


Markdown in Gogs incorrectly renders code when it is nested inside a list

If you have a some form of step-by-step guide and put code examples inside list, then Markdown renderer insider Gogs changes styling and styles inner code as it would be inline code, not full-line code. See examples below.
From left to right: Markdown code | rendering effect in GitHub | rendering effect in Gogs:
Case 1: Code is formatted using backticks:

Case 1: Code is formatted using space indent:

As I said, this Markdown construction is very useful for step-by-step guides, so it would be wonderful, if this could be fixed ASAP. Thank you!
Issue somehow related to #1415.

See https://try.gogs.io/manfer/MarkDownSample for fixed version on develop.

Closed as implemented. :star:


extended maximum wait time before yum update

What this PR does / why we need it:
Fixes the issue of yum update conflicting with running AzSecPack VM extension. Increases the total wait time before running a yum update command to 30 minutes in order to allow the 20 minute timeout of the VM extension to end. More info here https://learn.microsoft.com/en-us/azure/virtual-machines/extensions/features-linux?tabs=azure-cli#common-reasons-for-extension-failures
Test plan for issue:
Run the deployment.
How do you know this will function as expected in production?
Deployment works.

/azp run ci


Checksum errors on rustup update

When trying to rustup to latest nightly on macos, I get this:
$ rustup update
info: syncing channel updates for 'nightly-x86_64-apple-darwin'
info: update not yet available, sorry! try again later
error: checksum failed, expected: 'cf1b3efd0ee9d47544612f6e0c8d81958aebf05963a7d647d4e4d88b8aa28efe', calculated: 'ca8288f2e99de91b9a2baa1e3163ed5a45f771a183c2b776d6413e9430364229'
info: checking for self-updates

  nightly-x86_64-apple-darwin update failed - rustc 1.16.0-nightly (4ecc85beb 2016-12-28)

I tried the command mutiple times (as suggested on irc) but without success. How can I fix this?
Thanks

Same here:
rustup install nightly
info: syncing channel updates for 'nightly-x86_64-unknown-linux-gnu'
info: update not yet available, sorry! try again later
error: checksum failed, expected: 'cf1b3efd0ee9d47544612f6e0c8d81958aebf05963a7d647d4e4d88b8aa28efe', calculated: 'ca8288f2e99de91b9a2baa1e3163ed5a45f771a183c2b776d6413e9430364229'

@maximih @nbigaouette FWIW it looks like 2017-01-08 is the most recent nightly I am able to install.
rustup toolchain install nightly-2017-01-08

Note that a clean install of rustup.rs and then rustup install nightly results in:
error: checksum failed, expected: 'cf1b3efd0ee9d47544612f6e0c8d81958aebf05963a7d647d4e4d88b8aa28efe', calculated: 'ca8288f2e99de91b9a2baa1e3163ed5a45f771a183c2b776d6413e9430364229'

Today's nightly seems to work:
rustup toolchain install nightly-2017-01-13

But just installing nightly still fails:
$ rustup install nightly
info: syncing channel updates for 'nightly-x86_64-unknown-linux-gnu'
info: update not yet available, sorry! try again later
error: checksum failed, expected: 'cf1b3efd0ee9d47544612f6e0c8d81958aebf05963a7d647d4e4d88b8aa28efe', calculated: 'ca8288f2e99de91b9a2baa1e3163ed5a45f771a183c2b776d6413e9430364229'

Is this still an issue?

Nope. Will close it.


No Authentication to local broker

Hi,
again: thanks for the project ;-) As written in my other issue I would like to use the bridge without IP-Symcon. Most of the brokers needs authentication. As far as I understood the nodejs mqtt client, you need extra options to add username and password. Currently, the bridge only supports to add the broker url, but no extra options.
If you are interested I would create a pull request for that - fully compatible with the current url options (so existing configs will still work).

Thank you for your good contribution. I integrated your idea into my code. Please take a look at the new version.


Don't show published in the admin change form

https://favro.com/organization/b03d6d6d9b11b61167ac4246/80515c00f3d765836dd99b31?card=Dev-3869
Confuses users - so don't add it

I remember this was confusing me too at first!


✨ ENH: Support version and locale switcher

Refs: https://github.com/MegEngine/pydata-sphinx-theme/pull/1 / #276 / #23
@greglucas FYI.
Create a simple version switcher to change versions and locales.
Features

[x] User can enable version switch feature by setting theme_use_version_switch=True and set theme_version_switch_json_url = "/versions.json", then you will get an nicely dropdown menu that render everything from /versions.json
[x]  User can enable locale dropdown as well by enable theme_version_switch_enable_locale

[x] different locales may have different versions (I believe this will happen frequently due to translation progress)
[ ] If the current version doesn't exist in the target locale, it will redirect to the default version in the target locale

Excellent thanks for picking this one up! Is there a way that we could demo this in the documentation? The theme isn’t translated to any other languages, but perhaps we can try this with the version switcher to see how things look?

Excellent thanks for picking this one up! Is there a way that we could demo this in the documentation? The theme isn’t translated to any other languages, but perhaps we can try this with the version switcher to see how things look?

We have not yet provided the English version on our official website (so as you can see, the paths of en and zh are actually the same site). Related translation work may be carried out in the next few months. The locale switcher now only supports English and Chinese（中文），which might need further improvement.
Here is the way we tested the version switcher (you can use it the same way on demo site locally):

We generated several fake different version doc websites (just modified the version variable in source/conf.py and put |version| in API reference .rst file), or you can use the same pages.
Put them together in a tmp folder and write version.json file.
Start the local web server then verify.

@MegChai, thanks for picking this up! At first glance it looks good on your site. For the language selector on your site, it looks like it may get cluttered if there is more than ~2 possibilities there, did you consider adding another dropdown selector for that?
I'll try and review this and test it out on a different local site build within the next couple of days.

@MegChai, thanks for picking this up! At first glance it looks good on your site. For the language selector on your site, it looks like it may get cluttered if there is more than ~2 possibilities there, did you consider adding another dropdown selector for that?
I'll try and review this and test it out on a different local site build within the next couple of days.

You are right. The support for multi-language should be like what we have done for multi-version. Maybe it can also be generated from version.json and using some UI like this:

yep @MegChai using a dropdown for this as well sounds like a good idea, since many projects will have several languages.

@MegChai thanks for the PR!
A few suggestions:

To keep the PR well scoped (and easier to review and  get merged), maybe we can focus for now only on the version switcher, and leave the local switcher for a next PR?
I just merged https://github.com/pydata/pydata-sphinx-theme/pull/355, which makes the navbar/sidebar customizable by using a list of templates (html files in the pydata_sphinx_theme/_templates folder). I think we should now use that approach here as well, and move the version-switcher.html to the _templates, and then someone can add this to their docs by listing it eg in the list of navbar templates (similarly as you can add the search field to the navbar this way, see https://pydata-sphinx-theme.readthedocs.io/en/latest/user_guide/configuring.html#configure-the-search-bar-position)

This branch has been not maintained for a long time, @ThuWangzw will work on another branch.
He will open a new pull request as soon as possible.


Icons: use "color" property instead of repeating color on every box-shadow

As explained here box-shadow falls back to color for its color, and it's pretty well supported

We could replace:
 .icon.is-medium.close::before {
   width: 3px;
   height: 3px;
   box-shadow: 3px 3px #212529,6px 3px #212529,9px 3px #212529,12px 3px #212529, /*…*/;
 }

with:
 .icon.is-medium.close::before {
   width: 3px;
   height: 3px;
   box-shadow: 3px 3px,6px 3px,9px 3px,12px 3px, /*…*/;
   color:  #212529;
 }

What would be the gains?

1000 characters removed for .close.is-medium alone, I did not try to make it general but I guess it would be a huge weight gain
Very easy to change color in user's css, he just has to override color and tadaaa \o/

If you think it's interesting, and does not break your compatibility goals, I'd gladly propose a PR :)

Note it could obviously be applied only to "base" color, so it's best for monochromous icons (facebook, twitter, github, close) but that's already nice to have.

I didn't know repeating color 😆
Every time I add an icon,  I'm worried about increasing the CSS file size. 😢
so, good idea 👍

@naholyr @evexoio I couldn't sleep last night and started work on this as you can see the PR. Sorry I wasn't sure if someone was already planning on it.

@jjspace that's fine 👍
@naholyr there's plenty if issues for grabs if you want 🙌 🙏

You rock dude!
On Sun, 9 Dec 2018 at 23:31, Abdullah Samman<EMAIL_ADDRESS>wrote:

@jjspace https://github.com/jjspace that's fine 👍
@naholyr https://github.com/naholyr there's plenty if issues for grabs
if you want 🙌 🙏
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nostalgic-css/NES.css/issues/60#issuecomment-445578181,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AANEM7WAPdSj0gWVbhb0x_2eMGjV0_Rbks5u3Y9QgaJpZM4Y9fhT
.

--
Nicolas Chambrier, aka naholyr
Blog : http://naholyr.fr

This issue was closed by #143.


Implement .write() on Store/ArcStore

@gbj
I was trying to implement this via brainlessly copy-pasting code from Subfield. It worked well for Field, but ArcStore and Store don't seem to trigger effects.
impl<T> Writeable for ArcStore<T>
where
    T: 'static,
{
    type Value = T;

    fn try_write(&self) -> Option<impl UntrackableGuard<Target = Self::Value>> {
        self.writer()
    }

    fn try_write_untracked(
        &self,
    ) -> Option<impl DerefMut<Target = Self::Value>> {
        self.writer().map(|mut writer| {
            writer.untrack();
            writer
        })
    }
}

I haven't been able to pinpoint where the problem lies exactly, but I suspect that self.writer() being untracked isn't the intended behavior?
I need a little help with this 🙂

This was done at some point, and I forgot to mark this closed.


KAFKA-5818: KafkaStreams state transitions not correct

need to check that state is CRATED at startup
some minor test cleanup

Call for review @bbejeck @dguy @guozhangwang

This should be cherry-picked to 0.11.0 for get into <IP_ADDRESS> bug fix release to avoid a regression. \cc @dguy

@guozhangwang @dguy Updated this.

Merged to trunk. @mjsax could you please raise another PR for 0.11.0? I tried to cherry-pick but there were conflicts (I did try to resolve, but then had test failures). Thanks


Node - was compiled against a different Node.js version using NODE_MODULE_VERSION 72

I am working on a node application. Basically its a VS Code extension. Where I am planning to use the package. But I am getting some error.
Activating extension 'x' failed: The module '\\?  \d:\x\app\node_modules\robotjs\build\Release\robotjs.node' was compiled against a different Node.js version using NODE_MODULE_VERSION 72. This version of Node.js requires NODE_MODULE_VERSION 75. Please try re-compiling or re-installing the module (for instance, using npm rebuildornpm install)
The package should work smoothly.
I thought It might be because of my Node version. S0 I change my node version from v12.18.3 to v14.9.0.
But after changing that, I am getting.
Activating extension 'x' failed: The module  '\\?\d:\x\app\node_modules\robotjs\build\Release\robotjs.node'  was compiled against a different Node.js version using NODE_MODULE_VERSION 83.  This version of Node.js requires NODE_MODULE_VERSION 75.  Please try re-compiling or re-installing the module (for instance, using npm rebuildornpm
install)
I tried to rebuild the package using both node-gyp and npm rebuild. Still the same error.
After a little bit of digging, I found out that there is no node version that contained NODE_MODULE_VERSION 75. Check the NODE_MODULE_VERSION column. Then why I am getting the error. Any help?
My Environment

RobotJS version: 6.0.0
Node.js version: 12.18.3
npm version: 6.14.6
Operating System: Windows 10 Pro

The problem you're facing is the fact that your VS Code extension will be using Electron instead of node.
ABI version 75 corresponds to Electron 7.x.x, so you either have to pre-build and release your own Electron version of robotjs or give nut.js a try which already provides pre-builds.

@s1hofmann  I have tried to rebuild robotjs using npm rebuild --runtime=electron --target=1.1.3 --disturl=https://atom.io/download/atom-shell --abi=75. Still getting the same type of error. this time I am getting robotjs.node' was compiled against a different Node.js version using NODE_MODULE_VERSION 80. This version of Node.js requires NODE_MODULE_VERSION 75

@s1hofmann  Thanks, I have rebuilt the package successfully.  Although initially, I did several things wrong.  Like my extension electron package and vs code electron version was different.
Anyone who will face the same problem, my suggestion will be to check the VS code electron and node version first. Then rebuild the electron package.

@nayan2 where is VS code electron, where can i find the VS code electron, i use webstorm ?


fix(ChatbotHeaderSelectorDropdown): Aria label should include current value

Preview: https://virtual-assistant-pr-virtual-assistant-240.surge.sh


Adding Fable.Package.SDK confuses IDE

I found this issue some time ago and thought it was related to Rider https://youtrack.jetbrains.com/issue/RIDER-118632/F-syntax-highlight-suddenly-stopped-working-in-a-project
But recently I found that Visual Studio gets confused as well

And when trying to open that highlighted file, it fails with catastrophic failure

Someone on Discord mentioned that it is failing with current VS but preview (17.12) works fine with it.
Which seems to point out that the problem is coming from the IDE more than this package implementation.

The issue is preserved in VS Preview, I created the issue for VS as well: https://developercommunity.visualstudio.com/t/Adding-FablePackageSDK-confuses-Visual/10772429?

Version 1.3.0 improves the fix for this issue, by not touching the File added by the user and instead rely on MSBuild internal target to copy the files only when packaging the package.


Master branch commit fdd44c - broken launch configurations for multiple worker node configurations

I have issues
@max-rocket-internet
Quick heads-up
This change broke worker launch configurations for multiple worker group configurations:
https://github.com/terraform-aws-modules/terraform-aws-eks/blame/master/workers.tf#L31
* module.eks.aws_launch_configuration.workers[1]: Resource 'aws_iam_instance_profile.workers' not found for variable 'aws_iam_instance_profile.workers.id'
* module.eks.aws_launch_configuration.workers[0]: Resource 'aws_iam_instance_profile.workers' not found for variable 'aws_iam_instance_profile.workers.id'

Previous code had it properly select via the count index
-  iam_instance_profile        = "${aws_iam_instance_profile.workers.id}"
+  iam_instance_profile        = "${element(aws_iam_instance_profile.workers.*.id, count.index)}"

I'm submitting a...

[X] bug report
[ ] feature request
[ ] support request
[ ] kudos, thank you, warm fuzzy

What is the current behavior?
If this is a bug, how to reproduce? Please include a code sample if relevvant.
Sample multi worker group config
worker_groups = [
  {
    "name"                 = "green"
    "instance_type"        = "m4.large"
    "asg_desired_capacity" = "0"
    "asg_max_size"         = "0"
    "asg_min_size"         = "0"
  },
  {
    "name"                 = "blue"
    "instance_type"        = "m4.large"
    "asg_desired_capacity" = "2"
    "asg_max_size"         = "2"
    "asg_min_size"         = "2"
  },
]

worker_group_count = "2"

What's the expected behavior?
Are you able to fix this problem and submit a PR? Link here if you have already.
Can submit PR by end of day 9/25 if a fix doesn't make it in
Environment details

Affected module version: master
OS:
Terraform version:

Any other relevant info

Thanks! Can you confirm this fixes it? https://github.com/terraform-aws-modules/terraform-aws-eks/pull/141

👍 look good from my local testing,
------------------------------------------------------------------------
No changes. Infrastructure is up-to-date.

Thanks! My mistake.