dotenv-rails 2.2.1 with bundler 1.16.0 crashes Rails 5.2.0.beta2

Adding dotenv-rails 2.2.1 to a brand new Rails 5.2.0.beta2 project breaks everything with this error:
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/bundler-1.16.0/lib/bundler/constants.rb:4: warning: already initialized constant Bundler::WINDOWS
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/site_ruby/2.4.0/bundler/constants.rb:4: warning: previous definition of WINDOWS was here
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/bundler-1.16.0/lib/bundler/constants.rb:5: warning: already initialized constant Bundler::FREEBSD
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/site_ruby/2.4.0/bundler/constants.rb:5: warning: previous definition of FREEBSD was here
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/bundler-1.16.0/lib/bundler/constants.rb:6: warning: already initialized constant Bundler::NULL
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/site_ruby/2.4.0/bundler/constants.rb:6: warning: previous definition of NULL was here
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/bundler-1.16.0/lib/bundler/rubygems_integration.rb:10: warning: already initialized constant Bundler::RubygemsIntegration::EXT_LOCK
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/site_ruby/2.4.0/bundler/rubygems_integration.rb:12: warning: previous definition of EXT_LOCK was here
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/bundler-1.16.0/lib/bundler/current_ruby.rb:12: warning: already initialized constant Bundler::CurrentRuby::KNOWN_MINOR_VERSIONS
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/site_ruby/2.4.0/bundler/current_ruby.rb:12: warning: previous definition of KNOWN_MINOR_VERSIONS was here
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/bundler-1.16.0/lib/bundler/current_ruby.rb:23: warning: already initialized constant Bundler::CurrentRuby::KNOWN_MAJOR_VERSIONS
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/site_ruby/2.4.0/bundler/current_ruby.rb:23: warning: previous definition of KNOWN_MAJOR_VERSIONS was here
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/bundler-1.16.0/lib/bundler/current_ruby.rb:25: warning: already initialized constant Bundler::CurrentRuby::KNOWN_PLATFORMS
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/site_ruby/2.4.0/bundler/current_ruby.rb:25: warning: previous definition of KNOWN_PLATFORMS was here
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/bundler-1.16.0/lib/bundler/vendor/fileutils/lib/fileutils.rb:1186: warning: already initialized constant Bundler::FileUtils::Entry_::S_IF_DOOR
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/site_ruby/2.4.0/bundler/vendor/fileutils/lib/fileutils.rb:1186: warning: previous definition of S_IF_DOOR was here
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/bundler-1.16.0/lib/bundler/vendor/fileutils/lib/fileutils.rb:1444: warning: already initialized constant Bundler::FileUtils::Entry_::DIRECTORY_TERM
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/site_ruby/2.4.0/bundler/vendor/fileutils/lib/fileutils.rb:1444: warning: previous definition of DIRECTORY_TERM was here
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/bundler-1.16.0/lib/bundler/vendor/fileutils/lib/fileutils.rb:1446: warning: already initialized constant Bundler::FileUtils::Entry_::SYSCASE
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/site_ruby/2.4.0/bundler/vendor/fileutils/lib/fileutils.rb:1446: warning: previous definition of SYSCASE was here
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/bundler-1.16.0/lib/bundler/vendor/fileutils/lib/fileutils.rb:1499: warning: already initialized constant Bundler::FileUtils::OPT_TABLE
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/site_ruby/2.4.0/bundler/vendor/fileutils/lib/fileutils.rb:1499: warning: previous definition of OPT_TABLE was here
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/bundler-1.16.0/lib/bundler/vendor/fileutils/lib/fileutils.rb:1553: warning: already initialized constant Bundler::FileUtils::LOW_METHODS
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/site_ruby/2.4.0/bundler/vendor/fileutils/lib/fileutils.rb:1553: warning: previous definition of LOW_METHODS was here
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/bundler-1.16.0/lib/bundler/vendor/fileutils/lib/fileutils.rb:1560: warning: already initialized constant Bundler::FileUtils::METHODS
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/site_ruby/2.4.0/bundler/vendor/fileutils/lib/fileutils.rb:1560: warning: previous definition of METHODS was here
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/site_ruby/2.4.0/bundler/runtime.rb:84:in `rescue in block (2 levels) in require': There was an error while trying to load the gem 'dotenv-rails'. (Bundler::GemRequireError)
Gem Load Error is: Trying to register Bundler::GemfileError for status code 4 but Bundler::GemfileError is already registered
Backtrace for gem load error is:
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/bundler-1.16.0/lib/bundler/errors.rb:9:in `status_code'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/bundler-1.16.0/lib/bundler/errors.rb:20:in `<class:GemfileError>'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/bundler-1.16.0/lib/bundler/errors.rb:20:in `<module:Bundler>'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/bundler-1.16.0/lib/bundler/errors.rb:3:in `<main>'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/bootsnap-1.1.8/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:17:in `require'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/bootsnap-1.1.8/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:17:in `require'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/activesupport-5.2.0.beta2/lib/active_support/dependencies.rb:283:in `block in require'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/activesupport-5.2.0.beta2/lib/active_support/dependencies.rb:249:in `load_dependency'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/activesupport-5.2.0.beta2/lib/active_support/dependencies.rb:283:in `require'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/bundler-1.16.0/lib/bundler.rb:10:in `<main>'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/bootsnap-1.1.8/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:17:in `require'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/bootsnap-1.1.8/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:17:in `require'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/activesupport-5.2.0.beta2/lib/active_support/dependencies.rb:283:in `block in require'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/activesupport-5.2.0.beta2/lib/active_support/dependencies.rb:249:in `load_dependency'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/activesupport-5.2.0.beta2/lib/active_support/dependencies.rb:283:in `require'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/bundler-1.16.0/lib/bundler/setup.rb:6:in `<main>'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/bootsnap-1.1.8/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:17:in `require'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/bootsnap-1.1.8/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:17:in `require'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/activesupport-5.2.0.beta2/lib/active_support/dependencies.rb:283:in `block in require'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/activesupport-5.2.0.beta2/lib/active_support/dependencies.rb:249:in `load_dependency'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/activesupport-5.2.0.beta2/lib/active_support/dependencies.rb:283:in `require'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/spring-2.0.2/lib/spring/commands.rb:33:in `<module:Spring>'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/spring-2.0.2/lib/spring/commands.rb:4:in `<main>'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/bootsnap-1.1.8/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:17:in `require'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/bootsnap-1.1.8/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:17:in `require'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/activesupport-5.2.0.beta2/lib/active_support/dependencies.rb:283:in `block in require'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/activesupport-5.2.0.beta2/lib/active_support/dependencies.rb:249:in `load_dependency'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/activesupport-5.2.0.beta2/lib/active_support/dependencies.rb:283:in `require'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/dotenv-rails-2.2.1/lib/dotenv/rails.rb:20:in `<main>'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/bootsnap-1.1.8/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:17:in `require'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/bootsnap-1.1.8/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:17:in `require'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/activesupport-5.2.0.beta2/lib/active_support/dependencies.rb:283:in `block in require'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/activesupport-5.2.0.beta2/lib/active_support/dependencies.rb:249:in `load_dependency'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/activesupport-5.2.0.beta2/lib/active_support/dependencies.rb:283:in `require'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/dotenv-rails-2.2.1/lib/dotenv-rails.rb:1:in `<main>'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/bootsnap-1.1.8/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:50:in `require'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/bootsnap-1.1.8/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:50:in `require'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/site_ruby/2.4.0/bundler/runtime.rb:81:in `block (2 levels) in require'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/site_ruby/2.4.0/bundler/runtime.rb:76:in `each'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/site_ruby/2.4.0/bundler/runtime.rb:76:in `block in require'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/site_ruby/2.4.0/bundler/runtime.rb:65:in `each'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/site_ruby/2.4.0/bundler/runtime.rb:65:in `require'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/site_ruby/2.4.0/bundler.rb:114:in `require'
/home/user/app/config/application.rb:7:in `<main>'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/bootsnap-1.1.8/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:17:in `require'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/bootsnap-1.1.8/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:17:in `require'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/activesupport-5.2.0.beta2/lib/active_support/dependencies.rb:283:in `block in require'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/activesupport-5.2.0.beta2/lib/active_support/dependencies.rb:249:in `load_dependency'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/activesupport-5.2.0.beta2/lib/active_support/dependencies.rb:283:in `require'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/railties-5.2.0.beta2/lib/rails/commands/server/server_command.rb:145:in `block in perform'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/railties-5.2.0.beta2/lib/rails/commands/server/server_command.rb:142:in `tap'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/railties-5.2.0.beta2/lib/rails/commands/server/server_command.rb:142:in `perform'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/thor-0.20.0/lib/thor/command.rb:27:in `run'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/thor-0.20.0/lib/thor/invocation.rb:126:in `invoke_command'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/thor-0.20.0/lib/thor.rb:387:in `dispatch'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/railties-5.2.0.beta2/lib/rails/command/base.rb:65:in `perform'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/railties-5.2.0.beta2/lib/rails/command.rb:46:in `invoke'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/railties-5.2.0.beta2/lib/rails/commands.rb:18:in `<main>'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/bootsnap-1.1.8/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:17:in `require'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/bootsnap-1.1.8/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:17:in `require'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/activesupport-5.2.0.beta2/lib/active_support/dependencies.rb:283:in `block in require'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/activesupport-5.2.0.beta2/lib/active_support/dependencies.rb:249:in `load_dependency'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/activesupport-5.2.0.beta2/lib/active_support/dependencies.rb:283:in `require'
/home/user/app/bin/rails:9:in `<top (required)>'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/spring-2.0.2/lib/spring/client/rails.rb:28:in `load'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/spring-2.0.2/lib/spring/client/rails.rb:28:in `call'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/spring-2.0.2/lib/spring/client/command.rb:7:in `call'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/spring-2.0.2/lib/spring/client.rb:30:in `run'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/spring-2.0.2/bin/spring:49:in `<top (required)>'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/spring-2.0.2/lib/spring/binstub.rb:31:in `load'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/spring-2.0.2/lib/spring/binstub.rb:31:in `<top (required)>'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/site_ruby/2.4.0/rubygems/core_ext/kernel_require.rb:70:in `require'
/home/user/.asdf/installs/ruby/2.4.2/lib/ruby/site_ruby/2.4.0/rubygems/core_ext/kernel_require.rb:70:in `require'
/home/user/app/bin/spring:15:in `<top (required)>'
bin/rails:3:in `load'
bin/rails:3:in `<main>'
Bundler Error Backtrace:
	from /home/user/.asdf/installs/ruby/2.4.2/lib/ruby/site_ruby/2.4.0/bundler/runtime.rb:80:in `block (2 levels) in require'
	from /home/user/.asdf/installs/ruby/2.4.2/lib/ruby/site_ruby/2.4.0/bundler/runtime.rb:76:in `each'
	from /home/user/.asdf/installs/ruby/2.4.2/lib/ruby/site_ruby/2.4.0/bundler/runtime.rb:76:in `block in require'
	from /home/user/.asdf/installs/ruby/2.4.2/lib/ruby/site_ruby/2.4.0/bundler/runtime.rb:65:in `each'
	from /home/user/.asdf/installs/ruby/2.4.2/lib/ruby/site_ruby/2.4.0/bundler/runtime.rb:65:in `require'
	from /home/user/.asdf/installs/ruby/2.4.2/lib/ruby/site_ruby/2.4.0/bundler.rb:114:in `require'
	from /home/user/app/config/application.rb:7:in `<main>'
	from /home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/bootsnap-1.1.8/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:17:in `require'
	from /home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/bootsnap-1.1.8/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:17:in `require'
	from /home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/activesupport-5.2.0.beta2/lib/active_support/dependencies.rb:283:in `block in require'
	from /home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/activesupport-5.2.0.beta2/lib/active_support/dependencies.rb:249:in `load_dependency'
	from /home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/activesupport-5.2.0.beta2/lib/active_support/dependencies.rb:283:in `require'
	from /home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/railties-5.2.0.beta2/lib/rails/commands/server/server_command.rb:145:in `block in perform'
	from /home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/railties-5.2.0.beta2/lib/rails/commands/server/server_command.rb:142:in `tap'
	from /home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/railties-5.2.0.beta2/lib/rails/commands/server/server_command.rb:142:in `perform'
	from /home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/thor-0.20.0/lib/thor/command.rb:27:in `run'
	from /home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/thor-0.20.0/lib/thor/invocation.rb:126:in `invoke_command'
	from /home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/thor-0.20.0/lib/thor.rb:387:in `dispatch'
	from /home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/railties-5.2.0.beta2/lib/rails/command/base.rb:65:in `perform'
	from /home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/railties-5.2.0.beta2/lib/rails/command.rb:46:in `invoke'
	from /home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/railties-5.2.0.beta2/lib/rails/commands.rb:18:in `<main>'
	from /home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/bootsnap-1.1.8/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:17:in `require'
	from /home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/bootsnap-1.1.8/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:17:in `require'
	from /home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/activesupport-5.2.0.beta2/lib/active_support/dependencies.rb:283:in `block in require'
	from /home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/activesupport-5.2.0.beta2/lib/active_support/dependencies.rb:249:in `load_dependency'
	from /home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/activesupport-5.2.0.beta2/lib/active_support/dependencies.rb:283:in `require'
	from /home/user/app/bin/rails:9:in `<top (required)>'
	from /home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/spring-2.0.2/lib/spring/client/rails.rb:28:in `load'
	from /home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/spring-2.0.2/lib/spring/client/rails.rb:28:in `call'
	from /home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/spring-2.0.2/lib/spring/client/command.rb:7:in `call'
	from /home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/spring-2.0.2/lib/spring/client.rb:30:in `run'
	from /home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/spring-2.0.2/bin/spring:49:in `<top (required)>'
	from /home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/spring-2.0.2/lib/spring/binstub.rb:31:in `load'
	from /home/user/.asdf/installs/ruby/2.4.2/lib/ruby/gems/2.4.0/gems/spring-2.0.2/lib/spring/binstub.rb:31:in `<top (required)>'
	from /home/user/.asdf/installs/ruby/2.4.2/lib/ruby/site_ruby/2.4.0/rubygems/core_ext/kernel_require.rb:70:in `require'
	from /home/user/.asdf/installs/ruby/2.4.2/lib/ruby/site_ruby/2.4.0/rubygems/core_ext/kernel_require.rb:70:in `require'
	from /home/user/app/bin/spring:15:in `<top (required)>'
	from bin/rails:3:in `load'
	from bin/rails:3:in `<main>'

Steps to reproduce

Create a new Rails 5.2.0.beta2 project
Add gem 'dotenv-rails' to group :development, :test
Run bundle install
Run rails console

env files contents
None
System configuration
dotenv-rails version: 2.2.1
dotenv version: 2.2.1
Rails version: 5.2.0.beta2
Bundler version: 1.16.0
Ruby version: 2.4.2

I see bootsnap in your trace. I had the same problem until I ditched bootsnap.

Downgrading to rubygems 2.7.4 with gem update --system 2.7.4 fixed it for me.
The problem seems be related to the fact that the rubygems 2.7.5+ comes with its own copy of bundler. If you gem install bundler using rubygems 2.7.5+, then you somehow end up with two copies of bundler. Perhaps this confuses bootsnap into loading bundler twice.

This might be another manifestation of this bug: https://github.com/Shopify/bootsnap/issues/103

I am pretty sure this is not the fault of dotenv. This is the root cause: https://github.com/Shopify/bootsnap/issues/134

Hi, I removed require 'bootsnap/setup' from boot.rb and worked for me.

I believe this is resolved.


Add property streams pattern

https://journal.artfuldev.com/why-you-should-stop-using-state-reducers-in-your-app-to-be-fully-reactive-89a4279b3ece#.f3lh17bn0

Fixed


Print number of variables in repr

Show the printed and total number of variables in the repr.

[x] Passes isort . && black . && mypy . && flake8

import numpy as np
import xarray as xr

a = np.arange(0, 10)
b = np.core.defchararray.add("long_variable_name", a.astype(str))
c = np.arange(0, 25)
d = np.core.defchararray.add("attr_", c.astype(str))
e = {k: 2 for k in d}
coords = dict(time=da.array([0, 1]))
data_vars = dict()
for v in b:
    data_vars[v] = xr.DataArray(
        name=v,
        data=np.array([0, 1]).astype(bool),
        dims=["time"],
        coords=coords,
    )
ds1 = xr.Dataset(data_vars)
ds1.attrs = e

# The repr now shows how many attributes in total there are:
print(ds1)
Out[10]:
<xarray.Dataset>
Dimensions:              (time: 2)
Coordinates:
  * time                 (time) int32 0 1
Data variables:
    long_variable_name0  (time) bool False True
    long_variable_name1  (time) bool False True
    long_variable_name2  (time) bool False True
    long_variable_name3  (time) bool False True
    long_variable_name4  (time) bool False True
    long_variable_name5  (time) bool False True
    long_variable_name6  (time) bool False True
    long_variable_name7  (time) bool False True
    long_variable_name8  (time) bool False True
    long_variable_name9  (time) bool False True
Attributes (12/25):
    attr_0:   2
    attr_1:   2
    attr_2:   2
    attr_3:   2
    attr_4:   2
    attr_5:   2
      ...
    attr_19:  2
    attr_20:  2
    attr_21:  2
    attr_22:  2
    attr_23:  2
    attr_24:  2

Ouch, forgot about the doctests... Going through them by hand is not happening. Is there any automatic way to do that?

Ouch, forgot about the doctests... Going through them by hand is not happening. Is there any automatic way to do that?

unfortunately, I can't find a tool that does that. I guess either someone will have to write that tool or you will have to go through all the files and update by hand. For the latter, I would recommend to wait until the repr format has been reviewed so you don't have to do that more than once.

unfortunately, I can't find a tool that does that. I guess either someone will have to write that tool or you will have to go through all the files and update by hand. For the latter, I would recommend to wait until the repr format has been reviewed so you don't have to do that more than once.

I worked around it by only showing it when the repr is limited. That's the most important case anyway I think.

I worked around it by only showing it when the repr is limited. That's the most important case anyway I think.

I've used pytest-regtest quite a lot, which is decent. It would be another dependency. For tests like this — where the output is easier to review than to create, these "expect" / "snapshot" / "regression" tests are ideal. If anyone wanted to swap out these tests for that, I would strongly support the effort.
An aside — I tried to make a similar tool that worked for inline results — https://github.com/max-sixty/pytest-accept. Unfortunately it's not possible to make it work with bare assert statements, without swapping out a lot of pytest's internals. For a while i worked a lot on https://github.com/mitsuhiko/insta, an excellent project, would be great to have the same thing in python.

I've used pytest-regtest quite a lot, which is decent. It would be another dependency. For tests like this — where the output is easier to review than to create, these "expect" / "snapshot" / "regression" tests are ideal. If anyone wanted to swap out these tests for that, I would strongly support the effort.
An aside — I tried to make a similar tool that worked for inline results — https://github.com/max-sixty/pytest-accept. Unfortunately it's not possible to make it work with bare assert statements, without swapping out a lot of pytest's internals. For a while i worked a lot on https://github.com/mitsuhiko/insta, an excellent project, would be great to have the same thing in python.

LGTM, any final comments before we merge?

LGTM, any final comments before we merge?

Thanks @Illviljan !

Thanks @Illviljan !


Upgrade grafana

What this PR does / why we need it:
Upgrades grafana to latest avail release 5.3.0
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[X] DCO signed
[X] Chart Version bumped
[X] Variables are documented in the README.md

/lgtm


boards: nucleo_f429zi: fixup space character issue

A space character has been introduced after 'F249ZI' string
in various files. Fix this.
Signed-off-by: Erwan Gouriou<EMAIL_ADDRESS>

Codecov Report

Merging #6299 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #6299   +/-   ##
=======================================
  Coverage   53.14%   53.14%
=======================================
  Files         412      412
  Lines       40148    40148
  Branches     7733     7733
=======================================
  Hits        21338    21338
  Misses      15675    15675
  Partials     3135     3135

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 899ed91...ad88985. Read the comment docs.


Allow user to use her private templates

We need to show current user's private templates in SS UI and use them for cloning

Done


Add firrtl string to ExecutionOptionsManager.

The driver currently writes emitted firrtl to a file and reads it back
in. This can be problematic if tests are being run in parallel on the
same module.
This patch passes the firrtl string to the driver directly, instead of
reading it back in from the written file.
Should I be removing references to the emitted firrtl file?

The fix looks good, I am independently looking at some changes to how it assigns work directories for all this stuff.  I'll merge this our augment tomorrow hopefully

I am closing this. This same fix is part of PR #393


nixos/archisteamfarm: init; ASF-ui: init; ArchiSteamFarm: <IP_ADDRESS> -> <IP_ADDRESS> & fix build on aarch-64

nixos/archisteamfarm: init
ASF-ui: init
ArchiSteamFarm: <IP_ADDRESS> -> <IP_ADDRESS>

Motivation for this change
Adds a nixos module, the asf web-ui and updates archi-steam-farm to the latest version.
Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[x] (Module addition) Added a release notes entry if adding a new NixOS module
[x] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@SuperSandro2000 @aanderse Thanks for the extensive review, you both!
I've fixed all issues that have been found so far 😄. The config files are now completely generated at build-time and then only linked in place in run-time.

The config files are now completely generated at build-time and then only linked in place at run-time.
One thing seems to have broken, now that the config files are read only. The "requires input" prompt in the web-ui no longer shows up when it should, and instead the user has to use the command tab with the input command.

Upstream is working on a fix, and I've also applies a temporary workaround. So that works now as well!

Service is now smoothly running on my pi, out of the box. I'm unsure why aarch64 has different dependencies (any other dotnet package in nix just works), but I'm glad it works now.
I've also added a new option, to configure the IPC interface.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/421

@SuperSandro2000 poke :)

Resolved merge conflict.
If nothing more is wrong, I'll go ahead and merge this within the next couple of days. I've been running this branch for a month now - on both aarch64 and x86_64, without any issues.


Live Peer Integration

Problem
What problem are we solving?
Impact
Why does this matter? Who does it impact? How much does it impact them? What is the urgency?
Proposed Solution
[OPTIONAL] Thoughts on solution design. We could do  to solve this problem.
Acceptance Criteria
From an end user perspective, the below criteria must be met to consider this done:

[ ]

spec: https://www.notion.so/connext/Spec-Livepeer-Chain-Abstraction-70c21ca14985476798be0e4378d22740


Import Mapping from collections.abc

In Python 3.7, importing ABCs directly from the collections module shows a
warning (and in Python 3.8 it will stop working) - see
https://github.com/python/cpython/commit/c66f9f8d3909f588c251957d499599a1680e2320
This fixes the following DeprecationWarning:
>>> import warnings
>>> warnings.simplefilter('default')
>>> import markupsafe
.../markupsafe/__init__.py:12: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working
  from collections import Mapping

I just noticed I forgot to update the changelog - something like this might be appropriate?
diff --git a/CHANGES.rst b/CHANGES.rst
index 463ed38..831f8bc 100644
--- a/CHANGES.rst
+++ b/CHANGES.rst
@@ -11,8 +11,11 @@ Unreleased

 - ``escape`` wraps ``__html__`` result in ``Markup``, consistent with
   documented behavior. (`#69`_)
+- Fixed deprecation warning on Python 2.7 by importing from ``collections.abc``
+  instead of ``collections`` (`#98`_)

 .. _#69: https://github.com/pallets/markupsafe/pull/69
+.. _#98: https://github.com/pallets/markupsafe/pull/98

 Version 1.0

This isn't the type of change we typically add to the changelog.


缺少main_AGAIN.py

作者您好，我对您的论文Adversarially regularized graph attention networks for inductive learning on partially labeled graphs 十分感兴趣，但是在运行代码时发现其中少了main_AGAIN.py这个文件，您可以提供一下吗？谢谢

Hi,
Thanks for your interest in our work!
The missing file "main_AGAIN.py" has been added to this repository. Please have a check!

File uploaded.

Hi,
Thanks for your interest in our work!
The missing file "main_AGAIN.py" has been added to this repository. Please have a check!


C site is down!

Hello!
It seems like the website is down at the moment, I have no idea if it's because of me because I was in the for-loop section, I wrote some code and then clicked run then it showed the 522 cloudflare connection timed out error.
Win

Alright it's back up now


[Migration] One migrated bot will not send: Migration of bot to New Azure bot service

Bot Info
•SDK Platform: .NET
Issue
I implemented our 3 (three) bots via the Azure Bot Framework Service (Preview).
This hosted the bots as an app service on azure.
The migrate button for this type of Bot became available recently.
The app services are under a corporate azure subscription and I login to azure with my company O365 account.
I use this login portal.azure.com, apps.dev.microsoft.com and dev.botframework.com.
I successfully migrated two of the three bots, with the third and most popular bot, I am facing one major blocking issue:
•The migration button
When pressing the migration button, the migration completes and I can click the "Manage your bot" button.
When I attempt to test the bot via Test in Web Chat, the bot does not send.
There is no error, and clicking "retry" results in the same behavior.
The bot is also down in the web client (the channel is Facebook messenger).
I am forced to roll back the migration.
As all three bots functioned correctly all along, it appears the Migration is failing for this one bot for some unknown reason.
As this bot is heavily used during corporate orientations, and as this preview bot will stop functioning after March 31 2018 (in three weeks) any ideas or help appreciated!

Please provide your app ID

LTLAssistant4
MS AppID:
acf84990-3cec-4d10-8ee6-ab93282449fd
Thanks

In this doc https://docs.microsoft.com/en-us/bot-framework/bot-service-troubleshoot-general-problems search for migration and see if any of the troubleshooting steps help you.

Thanks
I used many of the approaches documented here when I initially developed and implemented the bot in question.
Doing so now has a number of drawbacks:

In order to troubleshoot the migrated bot I must re-migrate the Production bot first.
Drawback: This takes the bot offline and it is heavily used as we are currently onboarding staff across the globe.
*The code for the production bot functions as required and has no issues.
Drawback: I would be troubleshooting something that is an outcome of a failed migration, and / or the migration is altering the existing code, which is not supposed to occur (these issues are Microsoft's issues).
I am understanding that I cannot get a resolution to the failed migration?
Please clarify as if that is the case I need to inform the organization that the bot will become unavailable at the end of the month.

OK I took a different approach.
I updated the code for all bots, and, only this bot leveraged Azure Table Storage for logging.
The code also created a table if it was not present.
I removed that code from the original bot debugged deployed and tested same.
I then migrated the bot and tested the migrated bot.
SUCCESS
Thanks for your guidance

Glad you found a solution, good luck

L.U.C.K.
Laboring Under Correct Knowledge :)


Rally Collector configuration values are not stored in Mongo Database

I have tried all the solution provided by @Sbrenthughes but still unable to get the rallyserver value inserted in database.
Is there anything which I should be doing.
Step taken so far -

Deleted the beans file and recreated the jar
Deleted the document from database and re run the collector
Deleted the database as well and re executed all the steps

here is my config file -
Database Name
dbname=dashboarddb
Database HostName - default is localhost
dbhost=<IP_ADDRESS>
Database Port - default is 27017
dbport=27017
Database Username - default is blank
dbusername=
Database Password - default is blank
dbpassword=
Collector schedule (required)
rally.cron=0 0/5 * * * *
Rally server(s) (required) - Can provide multiple
rally.servers[0]=https://rally1.rallydev.com
Rally username/password for the provided server- with read-access to all resources.
rally.usernames[0]=
rally.passwords[0]=
#logging.level.com.capitalone.dashboard.collector=DEBUG
Actually, I see where the collector didn't insert the server URL. Can you try deleting that row and rerunning the collector?
Originally posted by @Sbrenthughes in https://github.com/Hygieia/Hygieia/issues/2725#issuecomment-462887484

Are you running this collector on your local machine?

yes I am running on local machine.

Any pointer? Anything I should be looking at. I have dropped the old database and executed using -Dserver.port option, no luck. Now started to look into the code, but its little hard and time consuming to understand.

Can you show the logs ?

Sure, I just commented out if block in RallyCollectorTask.java
/*if(rallySettings.getServers()==null) {
				rallySettings.setUsernames(new ArrayList<>());
				rallySettings.setPasswords(new ArrayList<>());
				rallySettings.setServers(new ArrayList<>());
			} else {
				rallySettings.getUsernames().clear();
				rallySettings.getServers().clear();
				rallySettings.getPasswords().clear();
			}*/

and recompiled. Now I am able to see the data in mongo database as well as job is fetching the records.
2019-04-11 16:10:03,852 INFO  com.capitalone.dashboard.Application - Started Application in 14.242 seconds (JVM running for 16.027)
2019-04-11 16:10:04,780 INFO  c.c.d.collector.CollectorTask - Fetched projects   68            1s
2019-04-11 16:10:04,967 INFO  c.c.d.collector.CollectorTask - New projects           68        0s
2019-04-11 16:10:05,023 INFO  c.c.d.collector.CollectorTask - Updated                 0        0s
2019-04-11 16:10:05,023 INFO  c.c.d.collector.CollectorTask - Finished                         1s


forum app | Doubled tables with the same purpose

In the forums app, if we take a look at the models.py module, one can see there two models:  Forum and Comment.
In the Forum model defined 'comments' ManyToMany field. And in the Comment a 'forum' ForeignKey field.
According to Django Docs, a ForeignKey to a model (in our case: Forum) auto-generates the reverse-access-manager (with the name: _set ).
Docs: https://docs.djangoproject.com/en/3.2/topics/db/queries/#following-relationships-backward
(It exists also in the m2m field)
Its actually a table that Django generates for us. In our case: 'comment_set'.
We can see that exist two tables with the same purpose ('comment_set' and 'comment'), so we basically create a situation with redundant table.
Image here: https://github.com/LiorA1/Django/blob/main/dj4e-samples/forums/DJ4ESpecialization.png
Fix Suggestion here: https://github.com/LiorA1/Django/blob/main/dj4e-samples/forums/models.py
Thanks
P.S: The same issue exists in the favs App.
P.S 2: For Non C.S Grads, it maybe be beneficial to see it explicitly.

This is a great comment.   I agree with your "P.S." statements.   Let me figure out where to use this approach - I think that since it is the "Django way" - it would be good to slowly switch to this pattern.


Why my bot isn't trading?

This is my chart:
http://by-code.com:3013/?sim_id=&selector=gdax.BTC-EUR&period=1m&limit=2000

Your link shows a 1m chart, do you have zenbot configured to trade every 1 minute? Make sure you are launching zenbot with the run function: ./zenbot launch map reduce run server --config <your config.js> optionally with map --backfill if you need trade history.

Yes, I run zenbot with command:
./zenbot launch map reduce run server --config config_btc_eur.js

Your config looks the same as mine, so it should work. I should try the following.
Run zenbot with this command: ./zenbot launch map --backfill reduce run server --config config_btc_eur.js
This will backfill all necessary data.
Also, do you have have all your assets in EUR? If that is so, maybe the bot didn't try to buy BTC yet because of the fall in price. Otherwise check the longs and search for the word 'attempting', zenbot logs each try to trade and report the failure reason, if there is one.
Be patient, it can take a couple of days for zenbot to start making transactions. Good luck!

Yeah, this works! :)
What happens if during the works of the bot I will add some money/btc to gdax?

It will notice there's new money and just keeps running (trading your new money as well)

@itsMichael I think it wasn't trading because the command you used to launch zenbot was missing the zenbot run launch command. How has it been working for you, any profits so far?  I'm curious as I've never traded BTC-EUR, what is your current ROI?

In 3 days:
Initial money: 79.08 EUR
Actually money: 79.22 EUR
ROI: 1.002
I have to restart bot, because i noticed that it doesn't work for few hours :/

currently: 78.98 EUR :/

currently: 78.80 EUR.

just relax, the bot doesn't have a crystal ball so it'll make mistakes, just like normal traders do

I'm aware :)

@JFD3D I have now 77.33 EUR. I started with 79.01 EUR. Every time this bot makes mistakes.
Should I change something config for this currency?

@JFD3D I have now 76.88 EUR. I started with 79.01 EUR (12 days ago). Every time this bot makes mistakes.
Should I change something config for this currency? (maybe default_logic.js)

You need to backtest and change default logic to fine tune it.
On Sun, Oct 2, 2016, 18:01 itsMichael<EMAIL_ADDRESS>wrote:

@JFD3D https://github.com/JFD3D I have now 76.88 EUR. I started with
79.01 EUR (12 days ago). Every time this bot makes mistakes.
Should I change something config for this currency? (maybe
default_logic.js)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/carlos8f/zenbot/issues/75#issuecomment-250978600, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHMwQw7IsW5-e4NtdDM2pVognrfgEtSmks5qv9VFgaJpZM4KC4w_
.


BanglExercise v0.02

Add sit ups
Add more feedback to the user about the exercises
Clean up code

Nice - thanks!


Add documentation for dIntegrate function.

Fix https://github.com/stack-of-tasks/pinocchio/issues/759
Add some mathematical insight to the documentation of integrate, difference and dIntegrate.

Generally speaking, this doc is a good thing. I think there is a need for a page which summarizes the notations. There are a few tricky points which ought to be highlighted:

q0 \oplus (q1 \ominus q0) can be different from q1 (in cases which are however easy to understand).
q0 \oplus (v0 + v1) is generally different from (q0 \oplus v0) \oplus v1.
You should never check equality using q0 == q1 (neither (q0-q1).norm() < thr). This can work if you now what you are doing. If you don't know, better use (q0 \ominus q1).norm() < thr.
You should prefer \oplus and \ominus  operations over + and - ones on configuration vectors.
Moreover, when computing derivatives, you should always think of these operators as functions with their own non-trivial derivatives. It will help you avoid hard-to-find wrong derivative (and they are a lot easier to write using the Lie Algebra)

I am sure the list is not exhaustive.

@matthieuvigne can you address the comments of @gabrielebndn. I will then open a new issue concerning the comments of @jmirabel
Thanks in advance.

@jmirabel I definitely agree with you on this. It's easy to confuse the joint configuration for a vector space (in particular because in practice, it is implemented as a vector) when you work with only 1DoF joints, and then everything stats to fall apart when you look at more complex kinematics. Viewing everything in terms of Lie group is a lot more powerful, and really well handled by pinocchio, but it takes some practice and it's easy to take the wrong habits.


waf: 2.0.23 -> 2.0.24

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/waf/versions.
meta.description for waf is: "Meta build system"
meta.homepage for waf is: "https://waf.io"
meta.changelog for waf is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.0.24 with grep in /nix/store/ik51chy0ysz300wmjjr5n3zfwa5wz8j5-waf-2.0.24
found 2.0.24 in filename of file in /nix/store/ik51chy0ysz300wmjjr5n3zfwa5wz8j5-waf-2.0.24

Rebuild report (if merged into master) (click to expand)

4196 total rebuild path(s)

4196 package rebuild(s)

First fifty rebuilds by attrpath
CHOWTapeModel
ChowCentaur
ChowKick
ChowPhaser
CuboCore.corepdf
CuboCore.coretoppings
DisnixWebService
EmptyEpsilon
HentaiAtHome
LibreArp
LibreArp-lv2
MIDIVisualizer
MMA
PageEdit
R
SDL2
SDL2_gfx
SDL2_image
SDL2_mixer
SDL2_net
SDL2_sound
SDL2_ttf
SDL2_ttf_2_0_15
SDL_audiolib
SDL_compat
SDL_gpu
SDL_mixer
Sylk
_1oom
_20kly
_7kaa
_90secondportraits
a2jmidid
abbaye-des-morts
abuse
acoustidFingerprinter
adapta-gtk-theme
adl
adoptopenjdk-icedtea-web
aegisub
aeolus
aerc
aether-lv2
afew
agi
ahoviewer
airwindows-lv2
aj-snapshot
alan
alass

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ik51chy0ysz300wmjjr5n3zfwa5wz8j5-waf-2.0.24 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A waf https://github.com/r-ryantm/nixpkgs/archive/b51e4f631e694b0ada2c227fa1d833e4194b33e5.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/ik51chy0ysz300wmjjr5n3zfwa5wz8j5-waf-2.0.24
ls -la /nix/store/ik51chy0ysz300wmjjr5n3zfwa5wz8j5-waf-2.0.24/bin

Pre-merge build results
NixPkgs review skipped

Maintainer pings
cc @vrthra for testing.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/1116


???ArrayFIFOQueue#dequeue??? should throw NoSuchElementException

dequeue??? should throw NoSuchElementException if there is no element in the queue like dequeueLast???. ??? is the primitive type name.
Alternatively have 2 methods like in Java where on rentuns a special value and another throws an exception. (https://docs.oracle.com/javase/7/docs/api/java/util/Queue.html)

That's not English. Please rephrase.

Done

Can you provide a unit test for the last version? I cannot reproduce.

The documentation does not mention that it throws a exception or not. E.g.: http://fastutil.di.unimi.it/docs/it/unimi/dsi/fastutil/objects/ObjectArrayFIFOQueue.html#dequeue--

I see. The problem is that when you inherit documentation you don't inherit the exceptions. I never realized that. Fixed.

I do not see any change in the Docs?

It'll take quite some time 😂


Unencrypted credentials in helm values

Hi.
I am currently trying to configure email reporting. Unfortunately I could only find a way to specify the mailserver credentials in the values.yaml file. The file is going to be pushed to my gitops repository. Since the credentials are unencrypted in the values.yaml file, they are exposed to everyone who is able to access my git repository.
I would rather like to create a secret containing the mailserver credentials beforehand and just reference it in the values.yaml file.
Could you implement a way to reference a secret in the values.yaml file?
Thanks

Hey, you can also create your own configuration service and configure it in the values.yaml:
https://github.com/kyverno/policy-reporter/blob/main/charts/policy-reporter/values.yaml#L220
does this help or how would your workflow looks like?

Oh sorry, I see this is only used for the deployment, not the email reports. So you would like to use a similar approach for the email reports, am I right?

Oh sorry, I see this is only used for the deployment, not the email reports. So you would like to use a similar approach for the email reports, am I right?

Yes, I would like to create the secret with the smtp configuration by myself, which preferebly only contains the smtp username and password. The other smtp configuration should be specified in the helm chart.
Check the values.yaml of the grafana helm chart as an example.

okay, thanks. I will have a look on it.

I created a PR to manage the SMTP configuration complete or partially as secret.
You can configure each key that is also available in the helm chart over the secret: host, port, encryption, from, username, password
The secret configuration has a higher priority as the configuration in the release values, when both are provided. Would this working for you?

I created a PR to manage the SMTP configuration complete or partially as secret.
You can configure each key that is also available in the helm chart over the secret: host, port, encryption, from, username, password
The secret configuration has a higher priority as the configuration in the release values, when both are provided. Would this work for you?

Looks good to me. I couldn't test it yet though, since the new image hasn't been released yet.

If you want to test it you could use
image:
  tag: dev
  registry: docker.io
  repository: fjogeleit/policy-reporter

with the PR changes. I tested it with this build.
I will release the new version tomorrow.

Using the dev image I was able to verify that my use case works.
Thanks, can't wait for the release. :)

Thanks for the fast verification. So I decided to release it already today. It is released as Helm Chart Version  2.11.3.
I hope the email reports feature offers everything you expect. I am happy about all kind of feedback.
I close the issue, just let me know if you encounter any other problems.

Thank you for the very fast implementation. I just updated policy reporter to the new version on my kubernetes cluster.


adjusted spacing and width of image

This is a fix for #81 and other spacing issues. Long term this page should be made more responsive with a layout not determining width by image size.

Coverage remained the same at 100.0% when pulling 5d0e1f0b222e4998972c7e57b658d63ea408cf71 on issue-81 into fe69fc070640409a8986474e0a873000d5d0a085 on dev.


Support generic types from XML namespaces

In .NET 8, XML namespaces can now support generic types.
https://github.com/dotnet/maui/pull/16486

Associated WorkItem - 164913

No action required.


fix(aeternity): show correct transaction details for token transfers

part of #2675,
missed in https://github.com/superhero-com/superhero-wallet/commit/39d94200d0c0688406f843b5d9ec9b8fd69a074d,

Fixed for FT, LGTM


rosidl_typesupport: 1.5.0-1 in 'rolling/distribution.yaml' [bloom]

Increasing version of package(s) in repository rosidl_typesupport to 1.5.0-1:

upstream repository: https://github.com/ros2/rosidl_typesupport.git
release repository: https://github.com/ros2-gbp/rosidl_typesupport-release.git
distro file: rolling/distribution.yaml
bloom version: 0.10.7
previous version for package: 1.4.2-3

rosidl_typesupport_c
* Install headers to include/${PROJECT_NAME} (#121 <https://github.com/ros2/rosidl_typesupport/issues/121>)
* Contributors: Shane Loretz

rosidl_typesupport_cpp
* Install headers to include/${PROJECT_NAME} (#121 <https://github.com/ros2/rosidl_typesupport/issues/121>)
* Contributors: Shane Loretz

Please hold for coordinated merge.


errors when using import alias, zap package since version 0.3.0

We are using gci as part of golangci-lint. Ever since version 0.3.0, we have been getting errors where previous versions have worked.
This error seems like it's expecting everything to import from github.com, however we use zap which comes from go.uber.org.
Expected 'i', Found 'o'
"go.uber.org/zap"
We also get this, which seems to be related to using aliases
Expected '"', Found 'l'
log "github.com/sirupsen/logrus"
This version also seems to not like blank lines between our third party libraries and internal imports.
Expected '\t', Found '\n'

Could you try latest version?

Could you try latest version?

I'm using the latest version of golangci-lint, which includes gci 0.3.2.  https://github.com/golangci/golangci-lint/pull/2640
I'm not sure when they will update to 0.3.3, but it doesn't look like that version has fixes for these issues.

@brandon-lango Could you please specify the exact command that you ran gci with and upload the affected files so that I can try to reproduce the issue. Only the import section is relevant you can remove everything else.

Here are a few examples. It seems to fail everywhere there is an import alias or we use the zap package. I'm running gci as a part to golangci-lint, not as a standalone command. We are using all the default settings for gci.
Expected 'i', Found 'o' at pkg/mt/infra/providers/onedrive/download.go[line 9,col 4] (gci)
"go.uber.org/zap"
import (
	"encoding/json"
	"fmt"
	"io/ioutil"
	"sync"

	"go.uber.org/zap"
)

Expected '\t', Found '\n' at pkg/mt/infra/providers/externalstorage/goroutines.go[line 5,col 1] (gci)
import (
	"github.com/hashicorp/go-multierror"

	mtCommand "github.com/langomobiledev/lango/pkg/mt/app/command"
	"github.com/langomobiledev/lango/pkg/mt/domain/filestorage"
)

Expected '"', Found 'l' at pkg/auth/infra/providers/cognito/register.go[line 11,col 2] (gci)
log "github.com/sirupsen/logrus"
import (
	"context"
	"errors"
	"fmt"

	"github.com/aws/aws-sdk-go-v2/aws"
	cognito "github.com/aws/aws-sdk-go-v2/service/cognitoidentityprovider"
	"github.com/aws/aws-sdk-go-v2/service/cognitoidentityprovider/types"
	log "github.com/sirupsen/logrus"

	"github.com/langomobiledev/lango/pkg/auth/domain/users"
)

Please add prefix to test.

I've got this issue as well with golangci-lint v1.46.2
infrastructure/database/database.go:7:2: Expected '"', Found 'g' at infrastructure/database/database.go[line 7,col 2] (gci)
        gormTrace "gopkg.in/DataDog/dd-trace-go.v1/contrib/gorm.io/gorm.v1"
        ^


Add job to check CVP test results and create auto-fix PR

A new job review-cvp is added to check CVP test results for an assembly and send a summary text to release Slack channel.
It also has the ability to automatically create a PR to fix some common CVP content_set_check failures.
Requires https://github.com/openshift/elliott/pull/368 to have elliott print CVP test results in json format.
This PR also changes Python version to 3.8.
Example job run:
https://saml.buildvm.hosts.prod.psi.bos.redhat.com:8888/job/hack/job/yuxzhu/job/aos-cd-builds/job/build%252Freview-cvp/18/console

/lgtm


Can't use west to flash test images into up_squared board.

Describe the bug
when using west flash to download image into up_squared, it met an error "KeyError: 'misc-flasher',
it is that for up_squared, in the runner_config args list,  the misc-flasher is NONE, so when invoking "runner_config['args'][runner_name]", it will report an error.
To Reproduce
Steps to reproduce the behavior:

west build -b up_squared -p auto samples/hello_world/
west flash
See error

Screenshots or console output
[ztest@zserver12 zephyr]$ west flash ~/up_squared.sh
-- west flash: rebuilding
ninja: no work to do.
-- west flash: using runner misc-flasher
Traceback (most recent call last):
File "/home/ztest/.local/bin/west", line 11, in
sys.exit(main())
File "/home/ztest/.local/lib/python3.6/site-packages/west/main.py", line 583, in main
args.handler(args, unknown)
File "/home/ztest/.local/lib/python3.6/site-packages/west/main.py", line 334, in ext_command_handler
command.run(args, unknown, topdir, manifest=manifest)
File "/home/ztest/.local/lib/python3.6/site-packages/west/commands/init.py", line 118, in run
self.do_run(args, unknown)
File "/home/ztest/work/zephyrproject/zephyr/scripts/west_commands/flash.py", line 30, in do_run
do_run_common(self, my_args, runner_args)
File "/home/ztest/work/zephyrproject/zephyr/scripts/west_commands/run_common.py", line 170, in do_run_common
runner_config['args'][runner_name] +
KeyError: 'misc-flasher'
Environment (please complete the following information):

OS: fedora28
Toolchain: zephyr-sdk-0.11.1
Commit ID: 82e006660

@mbolivar Could you take a look of this? it's related to commit" eb95bed55".

Thanks for the report. I believe https://github.com/zephyrproject-rtos/zephyr/pull/23027 is a fix.


[knnclassifier] compiler error with Dot

Something broke example knnclassifier. I wasn't sure what the problem is (at first), as I was just getting started with this library.
# github.com/sjwhitworth/golearn/metrics/pairwise
../../metrics/pairwise/euclidean.go:17: vectorX.Dot undefined (type *mat64.Dense has no field or method Dot)
../../metrics/pairwise/poly_kernel.go:21: vectorX.Dot undefined (type *mat64.Dense has no field or method Dot)

Problem seems to be in a breaking change in the gonum/matrix library.
See https://github.com/gonum/matrix/commit/ef442ed5f2e6da03a1dbf42d164180071ab2c121
Working on a PR to fix.

I have encountered the same error messages, and @EtienneBruines pull request does fix the issue.

Excellent! Weill be merged shortly.
On 25 September 2015 at 14:26, Anzel Lai<EMAIL_ADDRESS>wrote:

I have encountered the same error messages, and @EtienneBruines
https://github.com/EtienneBruines pull request does fix the issue.
—
Reply to this email directly or view it on GitHub
https://github.com/sjwhitworth/golearn/issues/119#issuecomment-143221562
.


Tensorflow distributed training question: Do we have to manually copy ckpt files from worker 0  to ps servers?

Operating System:
Linux XNLPEXP2 4.4.0-24-generic #43-Ubuntu SMP Wed Jun 8 19:27:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Azure VM 8 cores, 56GB memory
If installed from binary pip package, provide:
pip 8.1.2 from /home/xubixiong/.local/lib/python2.7/site-packages (python 2.7)
0.10.0rc0
When I am trying to restore training from latest checkpoint, I found that I have to copy checkpoint files to ps servers, from worker 0.
Is it the right and recommended way? Or I did something wrong? ?

In general, the tf.train.Saver code assumes that the worker and parameter server jobs share the same filesystem. For example, you could use a shared NFS mount, or you could use the support for Google Cloud Storage; support for more filesystems - such as HDFS,, #2218 - is in development.
In the special case that you are using the same parameter server hosts when restoring, you can try passing sharded=True to the saver constructor, and each parameter server will write its shard of the parameters to its local filesystem. It should then be able to restore from that path as well.

Great, I did miss this point. After trying, I used rsync to work around. Now I will adjust to the recommended way.
Thank you very much.
Get Outlook for iOShttps://aka.ms/o0ukef
On Mon, Aug 15, 2016 at 11:35 PM +0800, "Derek Murray" <notifications<EMAIL_ADDRESS>wrote:
In general, the tf.train.Saver code assumes that the worker and parameter server jobs share the same filesystem. For example, you could use a shared NFS mount, or you could use the support for Google Cloud Storage; support for more filesystems - such as HDFS,, #2218https://github.com/tensorflow/tensorflow/issues/2218 - is in development.
In the special case that you are using the same parameter server hosts when restoring, you can try passing sharded=True to the saver constructor, and each parameter server will write its shard of the parameters to its local filesystem. It should then be able to restore from that path as well.

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/tensorflow/tensorflow/issues/3812#issuecomment-239834251, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AUBCfscXcI1Fn8_2EcvvxosO81o4zYiyks5qgIccgaJpZM4JkIye.

I just find the method _AddRestoreOps in Saver.
And I try to change this node device, from Variable's device to chief device. And it can restore the whole cluster well.
  new_device = '/job:worker/task:0'
  with ops.device(graph_util.set_cpu0(new_device) if v.device else None):
# with ops.device(graph_util.set_cpu0(v.device) if v.device else None)

Is this a propositional solution for this issue? Or maybe it may call other errors.

@coderXiangLi I'm not sure exactly what change you're suggesting, but it doesn't look like that is a general fix. We might consider adding an API to place the save and/or restore ops on a different device, but we can't hardcode it to be on /job:worker/task:0 as that cause far more copies than necessary (from the worker task to the PS tasks, for example).


get_shared_volumes() doesn't return the necessary number of available volumes

intermittent test failure not related to zfs devices
Timed out waiting for         self.wait_until_true(lambda: len(self.get_shared_volumes(required_hosts)) >= expected_volumes)
get_shared_volumes doesn't return the necessary number of available volumes
this could be to do with deficiencies in the device scanning.
http://jenkins.lotus.hpdd.lab.intel.com/job/integration-tests-shared-storage-configuration/376/arch=x86_64,distro=el7//consoleFull
FAIL: test_create_filesystem_with_failover_mgs (tests.integration.shared_storage_configuration.test_managed_filesystem_with_failover.TestManagedFilesystemWithFailover)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/share/chroma-manager/tests/integration/shared_storage_configuration/test_managed_filesystem_with_failover.py", line 44, in test_create_filesystem_with_failover_mgs
    filesystem_id, volumes_expected_hosts_in_normal_state = self._test_create_filesystem_with_failover()
  File "/usr/share/chroma-manager/tests/integration/shared_storage_configuration/test_managed_filesystem_with_failover.py", line 14, in _test_create_filesystem_with_failover
    filesystem_id = self.create_filesystem_standard(self.TEST_SERVERS)
  File "/usr/share/chroma-manager/tests/integration/core/chroma_integration_testcase.py", line 348, in create_filesystem_standard
    ha_volumes = self.wait_for_shared_volumes(4, 4)
  File "/usr/share/chroma-manager/tests/integration/core/chroma_integration_testcase.py", line 487, in wait_for_shared_volumes
    self.wait_until_true(lambda: len(self.get_shared_volumes(required_hosts)) >= expected_volumes)
  File "/usr/share/chroma-manager/tests/integration/core/utility_testcase.py", line 140, in wait_until_true
    'Timed out waiting for %s\nError Message %s' % (inspect.getsource(lambda_expression), error_message))
AssertionError: Timed out waiting for         self.wait_until_true(lambda: len(self.get_shared_volumes(required_hosts)) >= expected_volumes)
Error Message ```

other occurrence: http://jenkins.lotus.hpdd.lab.intel.com/job/integration-tests-shared-storage-configuration/380/arch=x86_64,distro=el7//consoleFull


Const-correctness: H::const_iterator should not be convertible to H::iterator

#include "plf_hive.h"
#include <type_traits>

using H = plf::hive<int>;
static_assert(!std::is_convertible_v<H::const_iterator, H::iterator>); // fails
static_assert(!std::is_convertible_v<H::const_reverse_iterator, H::reverse_iterator>); // fails

FWIW IMHO this isn't a very high-priority bug. I mean, sure, it's not rock-solid STL-level quality, but the exact metaprogramming to get all the right conversions in the right places is pretty fiddly. (See https://quuxplusone.github.io/blog/2018/12/01/const-iterator-antipatterns/ )
This hole in plf::hive's const-correctness allows the user-programmer to do silly things like:
#include "plf_hive.h"

int main() {
    const plf::hive<int> h = {1, 2, 3, 4};
    plf::hive<int>::iterator it = h.begin();  // you shouldn't allow this
    *it += 42;  // this line modifies the contents of the const hive
}

I agree-
using a templated iterator was an initial suggestion to me, which I
followed, but it has it's downsides.
The only alternative (as far as I know) is a restructuring based on
inheritance - which involves a lot more code.
If you have a suggestion for overloading the conversions to prevent
const->non_const without switching to an inheritance model, please fill
me in.
On 23/04/2022 4:28 am, Quuxplusone wrote:

|#include "plf_hive.h" #include <type_traits> using H = plf::hive;
static_assert(!std::is_convertible_v<H::const_iterator, H::iterator>);
// fails static_assert(!std::is_convertible_v<H::const_reverse_iterator,
H::reverse_iterator>); // fails |
FWIW IMHO this isn't a very high-priority bug. I mean, sure, it's not
rock-solid STL-level quality, but the exact metaprogramming to get all
the right conversions in the right places is pretty fiddly. (See
https://quuxplusone.github.io/blog/2018/12/01/const-iterator-antipatterns/
https://quuxplusone.github.io/blog/2018/12/01/const-iterator-antipatterns/
)
This hole in |plf::hive|'s const-correctness allows the user-programmer
to do silly things like:
|#include "plf_hive.h" int main() { const plf::hive h = {1, 2, 3,
4}; plf::hive::iterator it = h.begin(); // you shouldn't allow this
*it += 42; // this line modifies the contents of the const hive } |
—
Reply to this email directly, view it on GitHub
https://github.com/mattreecebentley/plf_hive/issues/7, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABE4FIT2AHTX6VAHJX2N3HTVGLHUNANCNFSM5UCZR5YQ.
 If you don't mind spoilers in the form of code, see https://github.com/Quuxplusone/SG14/blob/fd6dfac/include/sg14/plf_hive.h#L272-L307 , which implements the specific pattern described in this paragraph:
https://quuxplusone.github.io/blog/2018/12/01/const-iterator-antipatterns/#personally-i-would-be-inclined-t
Switching to public inheritance would be much worse, because of
https://quuxplusone.github.io/blog/2021/07/14/an-iterator-is-not-a-const-iterator/

Good to know-
fixed in beta.
There's a slightly faster way to do the unconst approach, which I use
elsewhere in the code too.
On 27/04/2022 12:57 am, Quuxplusone wrote:

https://quuxplusone.github.io/blog/2018/12/01/const-iterator-antipatterns/
https://quuxplusone.github.io/blog/2018/12/01/const-iterator-antipatterns/
describes one (actually, two or three ;)) ways to do it, with their
upsides and downsides. If you don't mind spoilers in the form of code,
see
https://github.com/Quuxplusone/SG14/blob/fd6dfac/include/sg14/plf_hive.h#L272-L307
https://github.com/Quuxplusone/SG14/blob/fd6dfac/include/sg14/plf_hive.h#L272-L307
, which implements the specific pattern described in this paragraph:
https://quuxplusone.github.io/blog/2018/12/01/const-iterator-antipatterns/#personally-i-would-be-inclined-t
https://quuxplusone.github.io/blog/2018/12/01/const-iterator-antipatterns/#personally-i-would-be-inclined-t
Switching to public inheritance would be much worse, because of
https://quuxplusone.github.io/blog/2021/07/14/an-iterator-is-not-a-const-iterator/
https://quuxplusone.github.io/blog/2021/07/14/an-iterator-is-not-a-const-iterator/
—
Reply to this email directly, view it on GitHub
https://github.com/mattreecebentley/plf_hive/issues/7#issuecomment-1109763965,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABE4FIR5SPVD5HELIVCEWPTVG7R3PANCNFSM5UCZR5YQ.
You are receiving this because you commented.Message ID:
@.***>


SmartEdge DEK dosen't support muti-node ceph deployment

Hi, we can deploy SmartEdge DEK 22.03.02 with single node ceph, but muti-node ceph is not avaiable, seems like SmartEdge DEK dosen't support muti-node ceph deployment at all

Dose SmartEdge team have any plan to support muti-node ceph deployment, when will this bug be fixed ? What's the work around for this issue?


Change junit class name to be implementation.file name instead of file.function to allow for multiple-run reporting

Fixed as of a while ago


supports mobile terminal multiselect?

hi！     The box supports mobile terminal multiselect?

Hi @piyegui,
By saying "mobile terminal", I assume that you mean a regular mobile phone or tablet? The component works on my mobile device, but certainly isn't optimized for mobile devices - this component was built for a version of the ext-js library which didn't support mobile as a first-class citizen.


requests.exceptions.ProxyError when using text prompt

thank for your great jobs! it is ok when i use point prompt,but i meet this error when i try text prompt.
requests.exceptions.ProxyError: HTTPSConnectionPool(host='huggingface.co', port=443): Max retries exceeded w
ith url: /bert-base-uncased/resolve/main/tokenizer_config.json (Caused by ProxyError('Cannot connect to prox
y.', NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7fcbd46a6140>: Failed to establish
a new connection: [Errno 113] No route to host'))

This is caused by the connection error to huggingface. Grounding-DINO requires the access to huggingface for downloading its checkpoint and configs. Thus please check your network proxy to make sure you can visit huggingface from your device. And sometimes simple retrying can fix it.
If the problem insists, try to search for similar issues in the project of Grounding-DINO and huggingface
Hope this can help you.

The currently released version of SA3D does not support multi-object segmentation. And treating multiple objects as one object is unreasonable and makes SAM confused. Thus we simply select the box with the highest confidence predicted by Grounding-DINO. 🤣

oh thanks! I tried point prompts and it can provide multiple mask ,so i misunderstand it .


Update nagware lambda to cache results to redis

Summary
In support of https://github.com/cds-snc/platform-forms-client/pull/4221 we need a way to cache template / form ids that have overdue responses.
Currently we don't have any connectivity to our Redis instance from  the Lambda code i.e. the nagware lambda.
Proposal

Add Redis connectivity:

Nagware lambda needs to be connected to the VPC and given a security group
This new security group needs to be granted access to Redis

Update the Cron schedule that calls the Nagware to run daily (needs further discussion).

Update the Nagware lambda to cache the return value of

async function findOldestFormResponseByFormID() {
  const formResponses = await retrieveNewOrDownloadedFormResponsesOver28DaysOld();

  // cache to Redis here
  const KEY = "overdue:responses:template-ids";
  const EXPIRE =  "some-value";
  await redis.setex(KEY, EXPIRE, JSON.stringify(formResponses);

Once we have a cache we can update https://github.com/cds-snc/platform-forms-client/pull/4221/files#diff-91681091461b6a582441e8c061992bfd193ad370776cc802a0b1f5ba7331926bR4  to pull from the cache.
Noting the front-end has been updated to be generic i.e. just list overdue vs listing the amount of submissions that are overdue.  With this we can the Nagware function will get us enough info to flag that a template has overdue responses.

Nagware function has been moved into the VPC and should now be able to communicate with Redis (no function code changes have been made to test this).

Nagware function has now been updated with the caching code and deployed to Staging.  I'll check for errors after its scheduled run this weekend but in theory this should now be ready for app testing using the cache.

Three months of data for how long the Nagware takes to run (< 60s)

Code is now merged to read the data app side
https://github.com/cds-snc/platform-forms-client/pull/4250

Will monitor Nagware invocations in Prod now that this change has been deployed.

Confirmed that Nagware ran this morning in prod without sending emails.


listenTCP and consequently listenHTTPPlain fail with default HTTPServerSettings

listenTCP and consequently listenHTTPPlain fail with default HTTPServerSettings where
bindAddresses = ["::", "<IP_ADDRESS>"];

So this example from vibe.d start page doesn't work:
auto settings = new HTTPServerSettings;
settings.port = 8080;
listenHTTP(settings, &handleRequest);

Specifying either "::", "<IP_ADDRESS>" or a real IP as bind address resolves the issue.
The exception is
std.exception.ErrnoException@../../.dub/packages/vibe-d-master/source/vibe/core/drivers/libevent2.d(323): Error binding listening socket (Address already in use)
./vibetest(@safe bool vibe.core.drivers.utils.socketEnforce!(bool).socketEnforce(bool, lazy immutable(char)[], immutable(char)[], ulong)+0x48) [0x6a74e4] ./vibetest(vibe.core.drivers.libevent2_tcp.Libevent2TCPListener vibe.core.drivers.libevent2.Libevent2Driver.listenTCP(ushort, void delegate(vibe.core.net.TCPConnection), immutable(char)[], vibe.core.net.TCPListenOptions)+0x1dd) [0x692fa9] ./vibetest(vibe.core.net.TCPListener vibe.core.net.listenTCP(ushort, void delegate(vibe.core.net.TCPConnection), immutable(char)[], vibe.core.net.TCPListenOptions)+0x80) [0x6b7350]
This happens on Fedora 21 x64. Works on Windows 8.1 x64 though.

Not sure when this got fixed, but currently you'll still get an error for the second address, but the HTTP server will still run if listening on any of the interfaces  succeeds. In this case, "::" will succeed and the failure of "<IP_ADDRESS>" will be ignored.
If I were to choose the defaults today, I'd use ["::1", "<IP_ADDRESS>"] instead, but changing them now would break existing projects. The reason why things are like this is that the initial default was ["<IP_ADDRESS>"], which was still fine, but then IPv6 support only got added later, and this was the only way to not break backwards compatibility.


[Doc] Add installation instructions for Go 1.21.3

Proposed changes
My devbox uses Go 1.20.11 by default, so I got some compilation errors when I ran make build. In addition, go.mod requires 1.21.3, but the doc does not mention it.
Checklist
Before creating a PR, run through this checklist and mark each as complete.

[x] I have read the CONTRIBUTING doc
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked that all unit tests pass after adding my changes
[x] I have updated necessary documentation
[x] I have rebased my branch onto main
[x] I will ensure my PR is targeting the main branch and pulling from my branch from my own fork

@kevin85421 I think we should say that the project requires the version to be at least 1.21. And maybe you could add a note about the go toolchain.
Setting GOTOOLCHAIN=auto will make go find the appropriate toolchain, so even if you're on 1.21.2 and the go.mod says 1.21.4 you'll still be able to build

I think we should say that the project requires the version to be at least 1.21. And maybe we could add a note about the go toolchain.

This makes sense to me. Based on information from https://go.dev/doc/toolchain, starting with Go 1.21, support for GOTOOLCHAIN is provided. Therefore, it will compare the version of the bundled toolchain with the versions specified by the go or toolchain lines in go.mod or go.work. If GOTOOLCHAIN=auto is set, it will select the newer version.

Setting GOTOOLCHAIN=auto will make go find the appropriate toolchain, so even if you're on 1.21.2 and the go.mod says 1.21.4 you'll still be able to build

Do we need to set GOTOOLCHAIN=auto explicitly? The toolchain doc says that the default GOTOOLCHAIN setting is auto.
I experimented as shown in the following screenshot:

GOTOOLCHAIN starts from Go 1.21. Hence, when I use Go 1.20.11 under the nginx-gateway-fabric directory, it does not switch to the newer toolchain (Go 1.21.3 for this case) specified by go.mod under the directory.
When I use Go 1.21.2 in a directory without a go.mod file, which is shown as workspace in the screenshot, Go 1.21.2 is used. However, when I operate under the nginx-gateway-fabric directory, it automatically switches to Go 1.21.3.

Several questions

Should I say "latest version of Go" or "at least 1.21"?
Do I need to set GOTOOLCHAIN=auto explicitly?

Thanks!

@kevin85421 I'd say "at least Go v1.21". GOTOOLCHAIN=auto is the default, so we may not need to mention it.

Thanks! I've already updated the document.

I don't think we need the example instructions on how to install Go. Their docs should explain that. You're also using Go to install Go, so that's a little confusing. I would just keep to the simple link and and version.

This makes sense. I have updated the PR. Thanks!


Feature Request:  Calculate Creatinine Clearance

Feature Idea
This function would calculate Creatinine Clearance (CRCL).  This is used renal function assessment. It could be used to create a parameter for ADLB or a baseline value.  The baseline values are typically used in PK programming for NCA or POPPK.  It might be similar to the functions in derive_advs_params.R such as  derive_param_bmi() and compute_bmi()
This is the formula I have typically seen used:
For CREATBL in umol/L:
For SEX = 'F': then CRCL = ((140 - AAGE) * WTBL * 1.04) / CREATBL
For SEX = 'M': then CRCL = ((140 - AAGE) * WTBL * 1.23) / CREATBL
There could be the option to use different formulas if desired.
  Thank you for putting together.  Let's discuss at tomorrow's PK Working group meeting.

@airdjan @bms63 I added an initial compute_crcl() which we can discuss in the PK meeting.  We could potentially add the CKD-EPI equation to the same function or a separate function.


refactor: optimize condition orders from least frequent to most frequent - [merged]

Merges condition-order -> staging
https://workshop.codes/wiki/articles/help-my-server-is-crashing-a-guide-on-how-to-improve-server-stability-for-your-codes#condition-ordering

mentioned in commit 9042f18984c6646981c224f0303b236a6566d095

In GitLab by @ghost1 on Oct 6, 2023, 22:07
:tada: This MR is included in version 0.11.2 :tada:
The release is available on GitLab release.
Your semantic-release bot :package: :rocket:


"Tracker Networks Top Offenders" section semantically comes before the site details 📄

"Tracker Networks Top Offenders" semantically comes before the details of the site. I suspect this part is not as important so it might be better to move the markup below .site-info.

This one has been bugging me so much.

I believe this was resolved by #489


Nothing in OUTPUT frame

I surprisingly found that if I debug my c++ program with clang,  there will be nothing in the output frame and there is a popup from the system asking me whether the program can visit the documentary.  The last time I use vscode to code c++ is the time before the system updated to big sur. And I try to build the launch and task .json as the following in the official documentary. It's still not right.

/extCpp

/extCpp


Bug: Truncation in Table Cells

Describe the bug
The last character in a table cell is truncated and replaced with … even though it would have fit.
Source Code
https://go.dev/play/p/Z_uMf1mdLFr
Actual behavior
╭───┬───┬─────┬────╮
│On…│Tw…│Thre…│Fou…│
├───┼───┼─────┼────┤
│on…│tw…│thre…│fou…│
╰───┴───┴─────┴────╯

Expected behavior
╭───┬───┬─────┬────╮
│One│Two│Three│Four│
├───┼───┼─────┼────┤
│one│two│three│four│
╰───┴───┴─────┴────╯

I'm also seeing this. The regression happened between 0.9.1 and 0.10.0. My guess is that this PR broke it: https://github.com/charmbracelet/lipgloss/pull/256

@mikelorant You're the original author of the PR - could you please take a look at this? The Go Playground example above is very small and makes it super easy to rep.

@nivanov-ati I will take a look a this over the next few days, shouldn't be too difficult to sort out.

@aymanbagabas Need some assistance here, this has highlighted a bug in your ANSI package.
package main

import (
    "fmt"

    "github.com/charmbracelet/x/ansi"
)

func main() {
    str := "one"

    out := ansi.Truncate(str, len(str), ".")
    fmt.Println(out)
}

Expected: one
Result: on.
Your explanation of the truncate function deviates from how it works:

// Truncate truncates a string to a given length, adding a tail to the
// end if the string is longer than the given length.

While we could hack in a fix for this, it would be the wrong approach when we know the problem is likely impacting many other parts of Lipgloss.

this probably doesn't add much value but I added these two test cases to test_truncate.go in the X repo and they fail as expected. Staring at the code for a few minutes I don't see an obvious quick fix:
	{"short", "one", ".", 3, "one"},
	{"shortemoji", "on👋", ".", 3, "on👋"},

Not sure what Charm's process is here but should an issue on the X repo be made?

Thank you @mikelorant for jumping in here and thank, you @jbcpollak, for the test cases. Please do open up a PR on /x.
Ayman's on holiday right now. We may be able to sort this out beforehand, but worst case we can pick it back up when he's back.

I spent more time trying to fix this but its definitely not something I feel super comfortable with. I left some thoughts on the above PR.

Fwiw, this issue existed in muesli/reflow and got carried over in the implementation in x/ansi

Does Lipgloss need to be revved to take this new version of x as an end user?

@jbcpollak This is now patched in v0.11.1


docs: fix typo on "Threats and Mitigations" page

This:

If you believe you have identified a dependency confusion packages...

Should read:

If you believe you have identified a dependency confusion package...

Many thanks @MylesBorins for following up on this and other recent PRs! :rocket:


error in declaration files in the published NPM package

Bug description
When installed from npm (tried with 3.0.1 and 3.0.2) and imported into a typescript project, the library causes the build to fail because the 'getConsent' function appears to be missing in the declaration files :
> tsc -b .

../../node_modules/@inrupt/solid-client-access-grants/dist/index.d.ts:15:169 - error TS2305: Module '"./common/getters"' has no exported member 'getConsent'.

15 export { AccessGrantWrapper, getAccessModes, getExpirationDate, getId, getIssuanceDate, getIssuer, getRequestor, getResourceOwner, getResources, getTypes, getPurposes, getConsent, getCredentialSubject, getInbox, getInherit, } from "./common/getters";
                                                                                ~~~~~~~~~~

Additional information
Looking at the dist files in the NPM package, that function is indeed required by index.d.ts, but missing from ./common/getters.d.ts . It is in the source TS file, though.
Maybe it's ommitted by the bundler because of the @internal flag on the function ?
https://github.com/inrupt/solid-client-access-grants-js/blob/59482e438ca81b34445760a88bab9bbce7f94003/src/common/getters.ts#L128

Hi @pduchesne , thanks for reaching out! I'll look into this right ahead.

You are absolutely correct, our TSConfig has the stripInternal config option set to true, so there is no type declaration for things marked as @internal. I'll see whether it shouldn't be internal or should not be part of the exports, and release a fix soon.

The issue should be fixed with the latest v3.0.3 release of the library. If you confirm that this resolves the issue on your end, then this issue can be closed.

Yes it works.
Thank you.


Merge master branch to prTesting1_202005132044 branch

Docs Build status updates of commit b1bee43:
:clock10: Pending: waiting for processors (17 builds ahead of you)
:warning: Docs Build is busy, currently there are 17 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit b1bee43:
:warning: Validation status: warnings

File
Status
Preview URL
Details

split/updateTestRef1.md
:warning:Warning

Details

split/updateTestRef1.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.
[Warning] Missing attribute: title. Add a title string to show in search engine results.
Line 0: [Warning] Markdown content is not allowed before H1.
Line 1: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 04/01/2020.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


GA Release Checklist

We plan to release ByConity GA version by the end of May, we made a checklist here and expect to finish them before 15/May/2023.
The checklist includes 4 parts, stability, performance improvement, benchmark, document and new features.
Stability

[ ] Enhance ci to have 8 test suits
[ ] Fix all beta p0/p1 bugs reported github issue
[ ] Perform Regression testing

Performance improvement

[x] Primary Index cache
[ ] Optimize static cost of optimizer with stats
[ ] Pick some recent aggregation optimization from community

Benchmark

[ ] Compare ByConity with clickhouse/doris/presto in benchmark cluster (ssb/tpcds/clickbench)
[x] Compare ByConity performance with in-house version
[ ] Compare ByConity cold/hot run performance

Doc

[ ] Refine readme to make the instruction more clear
[ ] Migrate ByConity repo to byconity.doc repo

New features

[x] Provide binary install package
[x] Data cache preload
[ ] HDFS kerberos support
[ ] S3 object storage (preview)
[ ] Support ORC for HIVE external table (preview)
[ ] Multi-server integration (preview)

@hustnn  Could you add the PR links below the task which is closed to keep the track of the code？

The progress is tracked in https://github.com/ByConity/ByConity/milestone/1


feat: add proxy server for proving

partially attends #908

Currently the PR includes gRPC proxy, timeouts, rate limiting and round robin load balancing.
It still lacks of support for queues as mentioned in #908 .

Currently the PR includes gRPC proxy, timeouts, rate limiting and round robin load balancing.

Nice! One question: given that the amount of extra code is pretty small and also that it is logically related to the tx-prover crate - do we actually need to have a separate crate for this?
An alternative could be to move the code into tx-prover crate and just to have 2 separate binaries generated from there.

Currently the PR includes gRPC proxy, timeouts, rate limiting and round robin load balancing.

Nice! One question: given that the amount of extra code is pretty small and also that it is logically related to the tx-prover crate - do we actually need to have a separate crate for this?
An alternative could be to move the code into tx-prover crate and just to have 2 separate binaries generated from there.

Yes, it makes sense, even with the queues it shouldn't be that much code. I will merge the binaries. Thanks!

Yes, it makes sense, even with the queues it shouldn't be that much code. I will merge the binaries. Thanks!

The binaries could be named something like miden-tx-prover for the coordinator and miden-tx-prover-worker for the worker services (the one that is currently named miden-tx-prover).

The binaries could be named something like miden-tx-prover for the coordinator and miden-tx-prover-worker for the worker services (the one that is currently named miden-tx-prover).

We could even consider merging them into a single binary and then use different commands to start different services - e.g., something like:
# start the coordinator
miden-tx-prover start

# start a worker
miden-tx-prover start worker

But not sure if that's worth it.

We can address the above comments in a follow-up PR (no need to create a dedicated PR for them).


Exchanged Device Id between PIC18F47Q10 and PIC18F27Q10, and a modification of .ino

Hi, I've successfully used your programmer on linux (with a common Arduino UNO) to flash a PIC18F47Q10!
Please note that the Device Id of PIC18F27Q10 and PIC18F47Q10 are exchanged, so I've corrected at first them in your "pp3_devices.dat" files.
I've also noticed that  the MCLR/VPP pin (A3) is normally at HIGH level. This can be an issue when connecting your programmer to self-powerd boards. I've checked on both the MPLAB Pickit 4 and MPLAB SNAP programmers and they leave the MCLR/VPP pin at GND or 3-stated.
So I've modified your .ino and added a small switch on A2 so I can put your programmer into a "stand-by" state with all the ICSP pin at GND (or 3-stated) . This allows to connect safely the ICSP cable with an un-powered target board while the Arduino Uno is powered. Then I can power the target board and change the position of the switch to let  the programmer operate as intended.
After the programming I do in sequence: set the switch to "stand-by" again, reset the Arduino UNO, un-power the target board, disconnect the ICSP cable, and finally un-power the Arduino UNO.
Here the changed part at the beginning of you "int main" function:
.....
int main (void)
{
pinMode(13, OUTPUT);
pinMode(A2, INPUT_PULLUP);
while (digitalRead(A2))
{
digitalWrite(13, HIGH);
_delay_ms(200);
digitalWrite(13, LOW);
_delay_ms(200);
}
.....
The blinking Led of the Arduino UNO is used to give the feedback that the programmer is in the "stand-by" state, and the connection or disconnection to/from the target board is safe.
Thanks for this beautiful programmer!
I'll use it to give a simple and cheap way to program the PIC18F47Q10 MCU used inside my 68k-MBC board.
Here a couple of images of my Arduino Uno and the "ICSP adapter boad":
https://i.postimg.cc/L4PDWjcP/20210417-155447.jpg
https://i.postimg.cc/zvTkR1C7/20210417_155718.jpg
Regards.

Thank you for your contribution, I merged it.


[release-1.6] zipkin: Fix wrongly rendered timestamp value (#10400)

Manual cherry-pick https://github.com/envoyproxy/envoy/commit/01fe4b620f643bea06bdf5cea3443f9b0767fc40
ref issue: https://github.com/istio/istio/issues/22968
This patch fixes the wrongly rendered timestamp value of serialized
zipkin span by introducing replacers. This path is chosen since the way
protobuf struct holds numeric data is by using double as its data type and
when it is serialized (through MessageToJsonString; internally by
snprintf-ing the value to a string) sometimes lead to a value with
scientific notation involved (e.g.<PHONE_NUMBER>476870 will be printed as
1.58432429547687e+15). A better solution probably by going down to fix
protobuf MessageToJsonString.
Signed-off-by: Dhi Aurrahman<EMAIL_ADDRESS>For an explanation of how to fill out the fields, please see the relevant section
in PULL_REQUESTS.md
Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
[Optional Fixes #Issue]
[Optional Deprecated:]

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

test-asan_envoy
a6a2a05262d29bd7a914ea23a5d9499a8949f69b
link
/test test-asan_envoy

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test test-asan_envoy


SKW-32: [Web][Skyeex][Richard] Stating what we did

I think by mistake I created a branch from your "Stating what we did" and have also those changes. We can update this with production after yours enters, fetch it and push the updated version


Heapster pod crashes continously - panic: runtime error: slice bounds out of range

I'm using Kubespray to install and configure a Kubernetes cluster. Kubernetes version running is 1.7.5
The heapster version of image used is gcr.io/google_containers/heapster-amd64:v1.4.2.
Heapster  grafana version of image used is  gcr.io/google_containers/heapster-grafana-:v4.4.3
Heapster influxdb version of image used is gcr.io/google_containers/heapster-influxdb-:v1.3.3
After a couple of minutes the pod fails with this below error. It has restarted hundreds of times.
panic: runtime error: slice bounds out of range

goroutine 172 [running]:
k8s.io/heapster/metrics/sources/kubelet.(*kubeletMetricsSource).decodeMetrics(0xc4202a32c0, 0xc420238a00, 0xc420e09b60, 0xc420238c62, 0xc4202a2540)
        /go/src/k8s.io/heapster/metrics/sources/kubelet/kubelet.go:162 +0x1279
k8s.io/heapster/metrics/sources/kubelet.(*kubeletMetricsSource).ScrapeMetrics(0xc4202a32c0, 0xed17cab34, 0xc400000000, 0x255d380, 0xed17cab70, 0xc400000000, 0x255d380, 0x195b8e9)
        /go/src/k8s.io/heapster/metrics/sources/kubelet/kubelet.go:241 +0x3e3
k8s.io/heapster/metrics/sources.scrape(0x23d2dc0, 0xc4202a32c0, 0xed17cab34, 0xc400000000, 0x255d380, 0xed17cab70, 0x0, 0x255d380, 0x0)
        /go/src/k8s.io/heapster/metrics/sources/manager.go:169 +0x2a0
k8s.io/heapster/metrics/sources.(*sourceManager).ScrapeMetrics.func1(0xc420415540, 0x23d2dc0, 0xc4202a32c0, 0xc4202a3500, 0xed17cab34, 0x0, 0x255d380, 0xed17cab70, 0x0, 0x255d380, ...)
        /go/src/k8s.io/heapster/metrics/sources/manager.go:99 +0x155
created by k8s.io/heapster/metrics/sources.(*sourceManager).ScrapeMetrics
        /go/src/k8s.io/heapster/metrics/sources/manager.go:115 +0x387

I've been trying to debug this for a couple of days, I tried to change versions of heapster-amd64 and other image combinations of grafana and influxdb. But none of them worked. I also tried to disable dns once as I saw in another issue in github, but it didnt work as well. Pls suggest what might be wrong.

looks like a bug in the legacy kubelet source, which really just needs to be removed.  Please try using --source=kubernetes.summary_api=... and see if you hit the bug.  A quick glance seems to indicate that it's due to a hack put in place to extract container names

hi @DirectXMan12 Thx a lot, it worked, I'll close the issue in another few minutes to make sure it doesn't restart


Update finding-ways-to-contribute-to-open-source-on-github.md

What's being changed (if available, include any code snippets, screenshots, or gifs):
Removed dots from inside double quotes throughout the code/documentation. This change ensures consistent formatting in line with style guidelines.
Before:
"text."
After:
"text".

@MostafaGalal1 Thank you so much for opening a PR! ✨
We actually keep periods inside the ending quotation marks per our style guide (reference note right under the "Style Guide title" where the periods are inside the quotation marks 💛)

For markup specific to source content on docs.github.com, see "Using Markdown and Liquid in GitHub Docs." For any questions about the GitHub brand, see our "GitHub Brand Guide."

Thank you very much for your willingness to contribute to our docs! 🙇
If you're looking for another issue to pick up, take a look at our help wanted section to find open issues you can work on ✨