bundle install fails with permission denied

--- ERROR REPORT TEMPLATE -------------------------------------------------------

What did you do?
I ran the command /home/rdgon/.rvm/gems/jruby-1.6.8@cert/bin/bundle install

What did you expect to happen?
I expected Bundler to install the one gem that is mentioned in Gemfile: 'signer'

What happened instead?
Instead, what happened was this error message below.

Error details
Errno::EACCES: Permission denied - /tmp/bundler-compact-index-20161114-23261-13k1hk6/.
  org/jruby/RubyFile.java:478:in `initialize'
  org/jruby/RubyIO.java:1135:in `open'
  /home/rdgon/.rvm/rubies/jruby-1.6.8/lib/ruby/1.8/fileutils.rb:699:in `remove_entry_secure'
  /home/rdgon/.rvm/rubies/jruby-1.6.8/lib/ruby/1.8/tmpdir.rb:131:in `mktmpdir'
  /home/rdgon/.rvm/gems/jruby-1.6.8@cert/gems/bundler-1.13.6/lib/bundler/vendor/compact_index_client/lib/compact_index_client/updater.rb:29:in `update'
  /home/rdgon/.rvm/gems/jruby-1.6.8@cert/gems/bundler-1.13.6/lib/bundler/vendor/compact_index_client/lib/compact_index_client.rb:65:in `update'
  /home/rdgon/.rvm/gems/jruby-1.6.8@cert/gems/bundler-1.13.6/lib/bundler/vendor/compact_index_client/lib/compact_index_client.rb:56:in `update_and_parse_checksums!'
  /home/rdgon/.rvm/gems/jruby-1.6.8@cert/gems/bundler-1.13.6/lib/bundler/fetcher/compact_index.rb:67:in `available?'
  org/jruby/RubyMethod.java:117:in `call'
  /home/rdgon/.rvm/gems/jruby-1.6.8@cert/gems/bundler-1.13.6/lib/bundler/fetcher/compact_index.rb:15:in `available?'
  org/jruby/RubyProc.java:270:in `call'
  /home/rdgon/.rvm/gems/jruby-1.6.8@cert/gems/bundler-1.13.6/lib/bundler/fetcher.rb:157:in `use_api'
  /home/rdgon/.rvm/gems/jruby-1.6.8@cert/gems/bundler-1.13.6/lib/bundler/source/rubygems.rb:332:in `api_fetchers'
  org/jruby/RubyArray.java:2403:in `select'
  /home/rdgon/.rvm/gems/jruby-1.6.8@cert/gems/bundler-1.13.6/lib/bundler/source/rubygems.rb:332:in `api_fetchers'
  /home/rdgon/.rvm/gems/jruby-1.6.8@cert/gems/bundler-1.13.6/lib/bundler/source/rubygems.rb:337:in `remote_specs'
  /home/rdgon/.rvm/gems/jruby-1.6.8@cert/gems/bundler-1.13.6/lib/bundler/index.rb:10:in `build'
  /home/rdgon/.rvm/gems/jruby-1.6.8@cert/gems/bundler-1.13.6/lib/bundler/source/rubygems.rb:336:in `remote_specs'
  /home/rdgon/.rvm/gems/jruby-1.6.8@cert/gems/bundler-1.13.6/lib/bundler/source/rubygems.rb:83:in `specs'
  /home/rdgon/.rvm/gems/jruby-1.6.8@cert/gems/bundler-1.13.6/lib/bundler/definition.rb:261:in `index'
  org/jruby/RubyArray.java:1620:in `each'
  /home/rdgon/.rvm/gems/jruby-1.6.8@cert/gems/bundler-1.13.6/lib/bundler/definition.rb:259:in `index'
  /home/rdgon/.rvm/gems/jruby-1.6.8@cert/gems/bundler-1.13.6/lib/bundler/index.rb:10:in `build'
  /home/rdgon/.rvm/gems/jruby-1.6.8@cert/gems/bundler-1.13.6/lib/bundler/definition.rb:256:in `index'
  /home/rdgon/.rvm/gems/jruby-1.6.8@cert/gems/bundler-1.13.6/lib/bundler/definition.rb:250:in `resolve'
  /home/rdgon/.rvm/gems/jruby-1.6.8@cert/gems/bundler-1.13.6/lib/bundler/definition.rb:174:in `specs'
  /home/rdgon/.rvm/gems/jruby-1.6.8@cert/gems/bundler-1.13.6/lib/bundler/definition.rb:162:in `resolve_remotely!'
  /home/rdgon/.rvm/gems/jruby-1.6.8@cert/gems/bundler-1.13.6/lib/bundler/installer.rb:225:in `resolve_if_need'
  /home/rdgon/.rvm/gems/jruby-1.6.8@cert/gems/bundler-1.13.6/lib/bundler/installer.rb:78:in `run'
  /home/rdgon/.rvm/gems/jruby-1.6.8@cert/gems/bundler-1.13.6/lib/bundler/installer.rb:24:in `install'
  /home/rdgon/.rvm/gems/jruby-1.6.8@cert/gems/bundler-1.13.6/lib/bundler/cli/install.rb:71:in `run'
  /home/rdgon/.rvm/gems/jruby-1.6.8@cert/gems/bundler-1.13.6/lib/bundler/cli.rb:189:in `install'
  org/jruby/RubyKernel.java:2105:in `send'
  /home/rdgon/.rvm/gems/jruby-1.6.8@cert/gems/bundler-1.13.6/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
  /home/rdgon/.rvm/gems/jruby-1.6.8@cert/gems/bundler-1.13.6/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
  /home/rdgon/.rvm/gems/jruby-1.6.8@cert/gems/bundler-1.13.6/lib/bundler/vendor/thor/lib/thor.rb:359:in `dispatch'
  /home/rdgon/.rvm/gems/jruby-1.6.8@cert/gems/bundler-1.13.6/lib/bundler/cli.rb:20:in `dispatch'
  /home/rdgon/.rvm/gems/jruby-1.6.8@cert/gems/bundler-1.13.6/lib/bundler/vendor/thor/lib/thor/base.rb:440:in `start'
  /home/rdgon/.rvm/gems/jruby-1.6.8@cert/gems/bundler-1.13.6/lib/bundler/cli.rb:11:in `start'
  /home/rdgon/.rvm/gems/jruby-1.6.8@cert/gems/bundler-1.13.6/exe/bundle:34:in `(root)'
  /home/rdgon/.rvm/gems/jruby-1.6.8@cert/gems/bundler-1.13.6/lib/bundler/friendly_errors.rb:100:in `with_friendly_errors'
  /home/rdgon/.rvm/gems/jruby-1.6.8@cert/gems/bundler-1.13.6/exe/bundle:26:in `(root)'
  org/jruby/RubyKernel.java:1087:in `load'
  /home/rdgon/.rvm/gems/jruby-1.6.8@cert/bin/bundle:23:in `(root)'

Environment
Bundler   1.13.6
Rubygems  1.8.24
Ruby      1.8.7 (2012-09-18 patchlevel 357) [java]
GEM_HOME  /home/rdgon/.rvm/gems/jruby-1.6.8@cert
GEM_PATH  /home/rdgon/.rvm/gems/jruby-1.6.8@cert:/home/rdgon/.rvm/gems/jruby-1.6.8@global
RVM       1.26.11 (master)
Git       2.1.4
--- TEMPLATE END ----------------------------------------------------------------

(pre-written response)
Closing as a duplicate of the other Permission denied issues. A suite of permission errors have been addressed by https://github.com/bundler/bundler/pull/5007 which will release in Bundler 1.14. Until 1.14 releases, the team doesn't have the capacity to deal with, or deploy more fixes for, the quantity of permissions errors we receive.
I'm sorry you are experiencing issues and I hope you can get them resolved!!! Feel free to continue commenting on this issue in the meantime.

Having the same problem with 1.14.2 :cry:
Errno::EACCES: Permission denied - /tmp/bundler-compact-index-20170124-14806-1hlm63w/.
  org/jruby/RubyFile.java:478:in `initialize'
  org/jruby/RubyIO.java:1135:in `open'
  /home/flexa/.rvm/rubies/jruby-1.6.8/lib/ruby/1.8/fileutils.rb:699:in `remove_entry_secure'
  /home/flexa/.rvm/rubies/jruby-1.6.8/lib/ruby/1.8/tmpdir.rb:131:in `mktmpdir'
  /home/flexa/.rvm/gems/jruby-1.6.8/gems/bundler-1.14.2/lib/bundler/compact_index_client/updater.rb:30:in `update'
  /home/flexa/.rvm/gems/jruby-1.6.8/gems/bundler-1.14.2/lib/bundler/compact_index_client.rb:81:in `update'
  /home/flexa/.rvm/gems/jruby-1.6.8/gems/bundler-1.14.2/lib/bundler/compact_index_client.rb:68:in `update_and_parse_checksums!'
  /home/flexa/.rvm/gems/jruby-1.6.8/gems/bundler-1.14.2/lib/bundler/fetcher/compact_index.rb:68:in `available?'
  org/jruby/RubyMethod.java:117:in `call'
  /home/flexa/.rvm/gems/jruby-1.6.8/gems/bundler-1.14.2/lib/bundler/fetcher/compact_index.rb:15:in `available?'
  org/jruby/RubyProc.java:270:in `call'
  /home/flexa/.rvm/gems/jruby-1.6.8/gems/bundler-1.14.2/lib/bundler/fetcher.rb:157:in `use_api'
  /home/flexa/.rvm/gems/jruby-1.6.8/gems/bundler-1.14.2/lib/bundler/source/rubygems.rb:342:in `api_fetchers'
  org/jruby/RubyArray.java:2403:in `select'
  /home/flexa/.rvm/gems/jruby-1.6.8/gems/bundler-1.14.2/lib/bundler/source/rubygems.rb:342:in `api_fetchers'
  /home/flexa/.rvm/gems/jruby-1.6.8/gems/bundler-1.14.2/lib/bundler/source/rubygems.rb:347:in `remote_specs'
  /home/flexa/.rvm/gems/jruby-1.6.8/gems/bundler-1.14.2/lib/bundler/index.rb:10:in `build'
  /home/flexa/.rvm/gems/jruby-1.6.8/gems/bundler-1.14.2/lib/bundler/source/rubygems.rb:346:in `remote_specs'
  /home/flexa/.rvm/gems/jruby-1.6.8/gems/bundler-1.14.2/lib/bundler/source/rubygems.rb:83:in `specs'
  /home/flexa/.rvm/gems/jruby-1.6.8/gems/bundler-1.14.2/lib/bundler/definition.rb:263:in `index'
  org/jruby/RubyArray.java:1620:in `each'
  /home/flexa/.rvm/gems/jruby-1.6.8/gems/bundler-1.14.2/lib/bundler/definition.rb:261:in `index'
  /home/flexa/.rvm/gems/jruby-1.6.8/gems/bundler-1.14.2/lib/bundler/index.rb:10:in `build'
  /home/flexa/.rvm/gems/jruby-1.6.8/gems/bundler-1.14.2/lib/bundler/definition.rb:258:in `index'
  /home/flexa/.rvm/gems/jruby-1.6.8/gems/bundler-1.14.2/lib/bundler/definition.rb:252:in `resolve'
  /home/flexa/.rvm/gems/jruby-1.6.8/gems/bundler-1.14.2/lib/bundler/definition.rb:176:in `specs'
  /home/flexa/.rvm/gems/jruby-1.6.8/gems/bundler-1.14.2/lib/bundler/definition.rb:164:in `resolve_remotely!'
  /home/flexa/.rvm/gems/jruby-1.6.8/gems/bundler-1.14.2/lib/bundler/installer.rb:226:in `resolve_if_need'
  /home/flexa/.rvm/gems/jruby-1.6.8/gems/bundler-1.14.2/lib/bundler/installer.rb:78:in `run'
  /home/flexa/.rvm/gems/jruby-1.6.8/gems/bundler-1.14.2/lib/bundler/installer.rb:24:in `install'
  /home/flexa/.rvm/gems/jruby-1.6.8/gems/bundler-1.14.2/lib/bundler/cli/install.rb:70:in `run'
  /home/flexa/.rvm/gems/jruby-1.6.8/gems/bundler-1.14.2/lib/bundler/cli.rb:181:in `install'
  /home/flexa/.rvm/gems/jruby-1.6.8/gems/bundler-1.14.2/lib/bundler/settings.rb:99:in `temporary'
  /home/flexa/.rvm/gems/jruby-1.6.8/gems/bundler-1.14.2/lib/bundler/cli.rb:180:in `install'
  org/jruby/RubyKernel.java:2105:in `send'
  /home/flexa/.rvm/gems/jruby-1.6.8/gems/bundler-1.14.2/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
  /home/flexa/.rvm/gems/jruby-1.6.8/gems/bundler-1.14.2/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
  /home/flexa/.rvm/gems/jruby-1.6.8/gems/bundler-1.14.2/lib/bundler/vendor/thor/lib/thor.rb:359:in `dispatch'
  /home/flexa/.rvm/gems/jruby-1.6.8/gems/bundler-1.14.2/lib/bundler/cli.rb:20:in `dispatch'
  /home/flexa/.rvm/gems/jruby-1.6.8/gems/bundler-1.14.2/lib/bundler/vendor/thor/lib/thor/base.rb:440:in `start'
  /home/flexa/.rvm/gems/jruby-1.6.8/gems/bundler-1.14.2/lib/bundler/cli.rb:11:in `start'
  /home/flexa/.rvm/gems/jruby-1.6.8/gems/bundler-1.14.2/exe/bundle:32:in `(root)'
  /home/flexa/.rvm/gems/jruby-1.6.8/gems/bundler-1.14.2/lib/bundler/friendly_errors.rb:121:in `with_friendly_errors'
  /home/flexa/.rvm/gems/jruby-1.6.8/gems/bundler-1.14.2/exe/bundle:24:in `(root)'
  org/jruby/RubyKernel.java:1087:in `load'
  /home/flexa/.rvm/gems/jruby-1.6.8/gems/bundler-1.14.2/exe/bundle:19:in `'
  org/jruby/RubyKernel.java:1112:in `eval'
  /home/flexa/.rvm/gems/jruby-1.6.8/bin/jruby_executable_hooks:15:in `(root)'

Environment
Bundler   1.14.2
Rubygems  1.8.24
Ruby      1.8.7 (2012-09-18 patchlevel 357) [java]
GEM_HOME  /home/flexa/.rvm/gems/jruby-1.6.8
GEM_PATH  /home/flexa/.rvm/gems/jruby-1.6.8:/home/flexa/.rvm/gems/jruby-1.6.8@global
RVM       1.28.0 (latest)
Git       2.7.4
Platform  universal-java-1.8
OpenSSL   JRuby-OpenSSL 0.9.19
rubygems-bundler (1.4.4)

I still have this issue
Java HotSpot(TM) 64-Bit Server VM warning: You have loaded library /opt/jruby-1.6.4/lib/native/i386-Linux/libjffi-1.0.so which might have disabled stack guard. The VM will try to fix the stack guard now.
It's highly recommended that you fix the library with 'execstack -c ', or link it with '-z noexecstack'.
Don't run Bundler as root. Bundler can ask for sudo if it is needed, and
installing your bundle as root will break this application for all non-root
users on this machine.
JRuby limited openssl loaded. http://jruby.org/openssl
gem install jruby-openssl for full support.
--- ERROR REPORT TEMPLATE -------------------------------------------------------
Error Report
Questions
Please fill out answers to these questions, it'll help us figure out
why things are going wrong.

What did you do?
I ran the command /opt/jruby-1.6.4/bin/bundle install

What did you expect to happen?
I expected Bundler to...

What happened instead?
Instead, what happened was...

Have you tried any solutions posted on similar issues in our issue tracker, stack overflow, or google?
I tried...

Have you read our issues document, https://github.com/bundler/bundler/blob/master/ISSUES.md?
...

Backtrace
Errno::EACCES: Permission denied - /tmp/bundler-compact-index-*******/.
  org/jruby/RubyFile.java:442:in `initialize'
  org/jruby/RubyIO.java:1107:in `open'
  /opt/jruby-1.6.4/lib/ruby/1.8/fileutils.rb:699:in `remove_entry_secure'
  /opt/jruby-1.6.4/lib/ruby/1.8/tmpdir.rb:131:in `mktmpdir'
  /opt/jruby-1.6.4/lib/ruby/gems/1.8/gems/bundler-1.14.2/lib/bundler/compact_index_client/updater.rb:30:in `update'
  /opt/jruby-1.6.4/lib/ruby/gems/1.8/gems/bundler-1.14.2/lib/bundler/compact_index_client.rb:81:in `update'
  /opt/jruby-1.6.4/lib/ruby/gems/1.8/gems/bundler-1.14.2/lib/bundler/compact_index_client.rb:68:in `update_and_parse_checksums!'
  /opt/jruby-1.6.4/lib/ruby/gems/1.8/gems/bundler-1.14.2/lib/bundler/fetcher/compact_index.rb:68:in `available?'
  org/jruby/RubyMethod.java:117:in `call'
  /opt/jruby-1.6.4/lib/ruby/gems/1.8/gems/bundler-1.14.2/lib/bundler/fetcher/compact_index.rb:15:in `available?'
  org/jruby/RubyProc.java:274:in `call'
  /opt/jruby-1.6.4/lib/ruby/gems/1.8/gems/bundler-1.14.2/lib/bundler/fetcher.rb:157:in `use_api'
  /opt/jruby-1.6.4/lib/ruby/gems/1.8/gems/bundler-1.14.2/lib/bundler/source/rubygems.rb:342:in `api_fetchers'
  org/jruby/RubyArray.java:2400:in `select'
  /opt/jruby-1.6.4/lib/ruby/gems/1.8/gems/bundler-1.14.2/lib/bundler/source/rubygems.rb:342:in `api_fetchers'
  /opt/jruby-1.6.4/lib/ruby/gems/1.8/gems/bundler-1.14.2/lib/bundler/source/rubygems.rb:347:in `remote_specs'
  /opt/jruby-1.6.4/lib/ruby/gems/1.8/gems/bundler-1.14.2/lib/bundler/index.rb:10:in `build'
  /opt/jruby-1.6.4/lib/ruby/gems/1.8/gems/bundler-1.14.2/lib/bundler/source/rubygems.rb:346:in `remote_specs'
  /opt/jruby-1.6.4/lib/ruby/gems/1.8/gems/bundler-1.14.2/lib/bundler/source/rubygems.rb:83:in `specs'

Same here:
Java HotSpot(TM) 64-Bit Server VM warning: You have loaded library /opt/jruby-1.6.7/lib/native/i386-Linux/libjffi-1.0.so which might have disabled stack guard. The VM will try to fix the stack guard now.
It's highly recommended that you fix the library with 'execstack -c ', or link it with '-z noexecstack'.
--- ERROR REPORT TEMPLATE -------------------------------------------------------
Error Report
Questions
Please fill out answers to these questions, it'll help us figure out
why things are going wrong.

What did you do?
I ran the command /home/nifi/.rvm/gems/jruby-<IP_ADDRESS>/bin/bundle

What did you expect to happen?
I expected Bundler to...

What happened instead?
Instead, what happened was...

Have you tried any solutions posted on similar issues in our issue tracker, stack overflow, or google?
I tried...

Have you read our issues document, https://github.com/bundler/bundler/blob/master/doc/contributing/ISSUES.md?
...

Backtrace
Errno::EACCES: Permission denied - /tmp/bundler-compact-index-20170315-4211-1i69fq8/.
  org/jruby/RubyFile.java:443:in `initialize'
  org/jruby/RubyIO.java:1135:in `open'
  /opt/jruby-1.6.7//lib/ruby/1.8/fileutils.rb:699:in `remove_entry_secure'
  /opt/jruby-1.6.7//lib/ruby/1.8/tmpdir.rb:131:in `mktmpdir'
  /home/nifi/.rvm/gems/jruby-<IP_ADDRESS>/gems/bundler-1.14.6/lib/bundler/compact_index_client/updater.rb:30:in `update'
  /home/nifi/.rvm/gems/jruby-<IP_ADDRESS>/gems/bundler-1.14.6/lib/bundler/compact_index_client.rb:81:in `update'
  /home/nifi/.rvm/gems/jruby-<IP_ADDRESS>/gems/bundler-1.14.6/lib/bundler/compact_index_client.rb:68:in `update_and_parse_checksums!'
  /home/nifi/.rvm/gems/jruby-<IP_ADDRESS>/gems/bundler-1.14.6/lib/bundler/fetcher/compact_index.rb:68:in `available?'
  org/jruby/RubyMethod.java:117:in `call'
  /home/nifi/.rvm/gems/jruby-<IP_ADDRESS>/gems/bundler-1.14.6/lib/bundler/fetcher/compact_index.rb:15:in `available?'
  org/jruby/RubyProc.java:270:in `call'
  /home/nifi/.rvm/gems/jruby-<IP_ADDRESS>/gems/bundler-1.14.6/lib/bundler/fetcher.rb:157:in `use_api'
  /home/nifi/.rvm/gems/jruby-<IP_ADDRESS>/gems/bundler-1.14.6/lib/bundler/source/rubygems.rb:341:in `api_fetchers'
  org/jruby/RubyArray.java:2395:in `select'
  /home/nifi/.rvm/gems/jruby-<IP_ADDRESS>/gems/bundler-1.14.6/lib/bundler/source/rubygems.rb:341:in `api_fetchers'
  /home/nifi/.rvm/gems/jruby-<IP_ADDRESS>/gems/bundler-1.14.6/lib/bundler/source/rubygems.rb:346:in `remote_specs'
  /home/nifi/.rvm/gems/jruby-<IP_ADDRESS>/gems/bundler-1.14.6/lib/bundler/index.rb:10:in `build'
  /home/nifi/.rvm/gems/jruby-<IP_ADDRESS>/gems/bundler-1.14.6/lib/bundler/source/rubygems.rb:345:in `remote_specs'
  /home/nifi/.rvm/gems/jruby-<IP_ADDRESS>/gems/bundler-1.14.6/lib/bundler/source/rubygems.rb:82:in `specs'
  /home/nifi/.rvm/gems/jruby-<IP_ADDRESS>/gems/bundler-1.14.6/lib/bundler/definition.rb:263:in `index'
  org/jruby/RubyArray.java:1615:in `each'
  /home/nifi/.rvm/gems/jruby-<IP_ADDRESS>/gems/bundler-1.14.6/lib/bundler/definition.rb:261:in `index'
  /home/nifi/.rvm/gems/jruby-<IP_ADDRESS>/gems/bundler-1.14.6/lib/bundler/index.rb:10:in `build'
  /home/nifi/.rvm/gems/jruby-<IP_ADDRESS>/gems/bundler-1.14.6/lib/bundler/definition.rb:258:in `index'
  /home/nifi/.rvm/gems/jruby-<IP_ADDRESS>/gems/bundler-1.14.6/lib/bundler/definition.rb:252:in `resolve'
  /home/nifi/.rvm/gems/jruby-<IP_ADDRESS>/gems/bundler-1.14.6/lib/bundler/definition.rb:176:in `specs'
  /home/nifi/.rvm/gems/jruby-<IP_ADDRESS>/gems/bundler-1.14.6/lib/bundler/definition.rb:164:in `resolve_remotely!'
  /home/nifi/.rvm/gems/jruby-<IP_ADDRESS>/gems/bundler-1.14.6/lib/bundler/installer.rb:226:in `resolve_if_need'
  /home/nifi/.rvm/gems/jruby-<IP_ADDRESS>/gems/bundler-1.14.6/lib/bundler/installer.rb:78:in `run'
  /home/nifi/.rvm/gems/jruby-<IP_ADDRESS>/gems/bundler-1.14.6/lib/bundler/installer.rb:24:in `install'
  /home/nifi/.rvm/gems/jruby-<IP_ADDRESS>/gems/bundler-1.14.6/lib/bundler/cli/install.rb:70:in `run'
  /home/nifi/.rvm/gems/jruby-<IP_ADDRESS>/gems/bundler-1.14.6/lib/bundler/cli.rb:181:in `install'
  /home/nifi/.rvm/gems/jruby-<IP_ADDRESS>/gems/bundler-1.14.6/lib/bundler/settings.rb:99:in `temporary'
  /home/nifi/.rvm/gems/jruby-<IP_ADDRESS>/gems/bundler-1.14.6/lib/bundler/cli.rb:180:in `install'
  org/jruby/RubyKernel.java:2076:in `send'
  /home/nifi/.rvm/gems/jruby-<IP_ADDRESS>/gems/bundler-1.14.6/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
  /home/nifi/.rvm/gems/jruby-<IP_ADDRESS>/gems/bundler-1.14.6/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
  /home/nifi/.rvm/gems/jruby-<IP_ADDRESS>/gems/bundler-1.14.6/lib/bundler/vendor/thor/lib/thor.rb:359:in `dispatch'
  /home/nifi/.rvm/gems/jruby-<IP_ADDRESS>/gems/bundler-1.14.6/lib/bundler/cli.rb:20:in `dispatch'
  /home/nifi/.rvm/gems/jruby-<IP_ADDRESS>/gems/bundler-1.14.6/lib/bundler/vendor/thor/lib/thor/base.rb:440:in `start'
  /home/nifi/.rvm/gems/jruby-<IP_ADDRESS>/gems/bundler-1.14.6/lib/bundler/cli.rb:11:in `start'
  /home/nifi/.rvm/gems/jruby-<IP_ADDRESS>/gems/bundler-1.14.6/exe/bundle:32:in `(root)'
  /home/nifi/.rvm/gems/jruby-<IP_ADDRESS>/gems/bundler-1.14.6/lib/bundler/friendly_errors.rb:121:in `with_friendly_errors'
  /home/nifi/.rvm/gems/jruby-<IP_ADDRESS>/gems/bundler-1.14.6/exe/bundle:24:in `(root)'
  org/jruby/RubyKernel.java:1058:in `load'
  /home/nifi/.rvm/gems/jruby-<IP_ADDRESS>/gems/bundler-1.14.6/exe/bundle:19:in `'
  org/jruby/RubyKernel.java:1083:in `eval'
  /home/nifi/.rvm/gems/jruby-<IP_ADDRESS>/bin/jruby_executable_hooks:15:in `(root)'

Environment
Bundler   1.14.6
Rubygems  1.8.15
Ruby      1.8.7 (2012-02-22 patchlevel 357) [java]
GEM_HOME  /home/nifi/.rvm/gems/jruby-<IP_ADDRESS>
GEM_PATH  /home/nifi/.rvm/gems/jruby-<IP_ADDRESS>:/home/nifi/.rvm/gems/jruby-<IP_ADDRESS>@global
RVM       1.29.1 (latest)
Git       not installed
Platform  universal-java-1.8
OpenSSL   JRuby-OpenSSL 0.9.20
rubygems-bundler (1.4.4)

--- TEMPLATE END ----------------------------------------------------------------

Unfortunately, an unexpected error occurred, and Bundler cannot continue.

First, try this link to see if there are any existing issue reports for this error:
https://github.com/bundler/bundler/search?q=Permission+denied+-+%2Ftmp%2Fbundler-compact-index-20170315-4211-1i69fq8%2F.&type=Issues

If there aren't any reports for this error yet, please create copy and paste the report template above into a new issue. Don't forget to anonymize any private data! The new issue form is located at:
https://github.com/bundler/bundler/issues/new

HI lynncyrin,
Do you have an answer for this issue still coming even after updating the bundle to 1.14.x or 1.15.x versions ?

@gav-y can you please open a new issue with the details of the problem you're experiencing.


Baking DropEvents into Performance

We need to "bake" the Program-DropEvents into the Performance's Events array.
This is to allow manual fretting to overwrite the predetermined fret of a BassDropEvent, whilst keeping it future-proof for possible Performance-editors.
This means, all DropEvents occuring atomatically during a Performance recording, are baked into the Program's Event list with the appropriate BakeType. This is not the case for other Event types, as only DropEvents can be stored in a Program.
export enum EventBakeType {
	AUTO, // Baked Dropevents
	MODIFIED_AUTO, // Baked Dropevents, overridden manually (e.g. frets of a BassDropEvent)
	MANUAL, // Manually done stuff
}

I'm not seeing why this is necessary.   If anything the fret parameter of the BassDropEvent should be removed so the note played is deduced by the position of the capo.  If that's the case, unless marble drops can be blocked by the user (no need for this when there is a muting lever) I see no need for this "Baking" of drop events.

@Tiedye the reason for the fret parameter is to simulate manual pressing of the frets, as it would be quite tedious to do on a computer

@mozi-h The data representation doesn't have to optimize for minimal events as you wont be writting it manually.  I think the fret parameter should be removed as the same effect can be achieved with a capo and a bass drop event.  As it is it will just complicate player/simulator implementations.

I can’t quite follow, @Tiedye
The reason for marking the baked DropEvents as Auto, Modified (BassDropEvent only for now) or Manual, is so (very) future Performance-editors have a way of knowing which is which since they’ll share the same event array.


Avoid empty message_content div for /me messages.

This also makes the template a bit more readable.
(As an aside, copy/paste is broken for /me messages,
but that precedes this commit.)

Merged, thanks @showell!  One thing I'm curious about after reading this is whether we should have the message_content CSS class on the status message elements -- it seems like we should in order for things like code block styling to be applied correctly...


tab to next completion argument doesn't work in coder

If you complete a multiple keyword argument, the tab key should move to the next uncompleted argument. Currently, the tab key is indenting the current line instead of advancing the cursor to the next uncompleted item.


fixed pointer cast that discards const qualifier

[]const Vector2 converted to [*c]Vector2 which discards the const qualifier. Which throws an error.
I removed the const from []const Vector2 which fixed the issue. If you want to keep the const you can either use @constCast
or change [*c]Vector2 to [*c]const Vector2 and also change cdef counter part to also  [*c]const Vector2 which may work. I haven't tested the last one.
There might be more functions also effected, but the ones I changed were the ones I located.

I'd rather leave the [] const Vector2, but I don't have a testing project to try out if [*c]const Vector2 works. I'll leave this open until I find some time.

I changed it to [*c]const and I tested it. No errors works just fine.

Sorry, I didn't check what C does and since it doesn't make any const promises either, your first approach was correct

Ok no problem


Apply JSON files for storing curation/annotation information

Description of the issue:

This issue is derived from another ongoing issue (#27), which aims to drive the repo toward binary-free mode eventually
JSON is an open-standard and language-independent file format. It is human-readable text and commonly used for data interchange
JSON files appear to be ideal for archiving information in GEM-type repo and helping the migration to binary-free mode, given that Matlab recently started to support JSON by providing built-in functions (jsondecode, jsonencode) for import/export.

Expected feature/value/output:

It is attempted here to utilize JSON files for storing the model annotation information and curation results that are often cell array type variables in humanGEM and previously saved as .mat files
Develop necessary tailored functions to support the smooth application of JSON files

I hereby confirm that I have:

[X] Checked that a similar issue does not exist already

Examples for loading/exporting cell array structure from/to a JSON file:

Load JSON file abc.json to a variable:

variableName = jsondecode(fileread('abc.JSON'));

Export a variable to a abc.json file to :

jsonStr = jsonencode(variableName);
fid = fopen('abc.json', 'w');
fwrite(fid, prettyJson(jsonStr));
fclose(fid);


Views in fragment are selectable while Stepper Feedback progress is shown

Good day. Thanks for the stepper feedback feature, looks awesome. However, it doesn't make views inside of a fragment unclickable or unselectable while feedback progess is shown. For instance I can edit my text fields while progress is shown, which is undesirable behaviour. It would be nice if the library would do that automaticaly, instead of doing that manually for each fragment or view. Thank you.
P.S.: I think it should be written in wiki that in order to have disabled effect on bottom navigation bar, button colors should be assigned using selectors like in sample app:
   app:ms_backButtonColor="@color/ms_disabling_button_text_color_selector"     app:ms_nextButtonColor="@color/ms_disabling_button_text_color_selector"     app:ms_completeButtonColor="@color/ms_disabling_button_text_color_selector"
Because it took me quite a while to figure out why my navigation bar buttons aren't changing their color.

Hi,
I agree about the readme description, I'll update it so there's no confusion there :)
However, as far as the view selection is concerned i think this shouldn't be done by the library. You mentioned EditText, however this can be any other view (including custom views)  and there's no way for the library to know how to disable it, e.g. it could be simply calling setEnabled(false), but it doesn't have to. It could also mean stopping some ongoing animations, etc. Therefore, I believe this should be the Step's responsibility to do that.

I think simply infalting an empty view which would overlay and dim the content and at the same time intercept all clicks, so that they don't reach underlying content. It would also fix another issue of mine, where content behind stepper layout is not being dimmed.

I tried putting a view to dim the content, however I found that the effect was worse than changing alpha since it could look completely different depending on what's inside the step (especially with different step backgrounds).
However if you have any ideas how to make this better I'll gladly accept PRs regarding this!

How about for time adding an option to choose the dim type? Alpha by default but optional overlay. Also would be nice to be able to change alpha amount and overlay color.
Here's how my implementation looks like, to make it clear.
Expected behavior

Real behaviour

Even worse with keyboard :)

I'd suggest splitting content feedback type into content_dim, content_fade stepper feedback types then? Also, new attributes ms_stepperFeedback_contentDimBackground and ms_stepperFeedback_contentFadeAlpha could be added for further customisation?

Exactly. This offers good flexibility for developers.

I think that click intercepting could be also done for content_fade  or we could create e.g. disabled_content_interactions feedback type.

disabled_content_interactions feedback type sounds excellent. I'm looking forward to see these features in future releases!

This was merged to develop and will be available with the next release.
Thanks for contributing!


Cloud Vms add missing list actions

We should have all actions shown in list. So the list of actions
should be the same as list in VM detail.
Fixes BZ:
https://bugzilla.redhat.com/show_bug.cgi?id=1278400

This feels like two separate PRs to me.  One for fixing the workers' settings names, and one for adding the missing list actions.
Are they related somehow?

@blomquisg ah, good catch, that setting commit got here by accident, it was merged while ago in another PR

Much better :smile:

@ladas, ugh, one more request ... screenshot?

Screenshot-ManageIQ: Instances - Google Chrome


[Marker.io] (Mobile) have to scroll down a bit now in order to see the success message

Steps to reproduce:
Open contact page in mini devices(ios)
2) enter field values
3) in message, enter 4 or 5 different lines text
4) submit
Actual result:have to scroll down a bit to see the message when page is scrolled up a bit automatically after submission
Expected result: if possible, this should be improved
See video in comments

Reported by: Vinod<EMAIL_ADDRESS>- Contact via Marker.io
Source URL: https://kensway.webflow.io/contact
Issue details: Open in Marker.io
Device typemobileBrowserSafari 17.5Screen Size375 x 812OSiOS 17.5.1Viewport Size375 x 628Pixel Ratio@3x

🤖 Marker.io bot - 💬 Vinod commented:

video:
https://drive.google.com/file/d/10ROZMdUcVYnNfrZvBTFt7RTcHjAYP4ZH/view?usp=sharing

Reply here

on desktop, have to scroll up a bit now in order to see the success message:

(windows 10 64 bit chrome, 1366*768 resolution)


[Upload Error]: [upload part: send upload part 81 RPC: rpcDoRequest: retryUntilAck: engine forcibly closed: context canceled]

What version of gotd are you using?
github.com/gotd/td v0.71.0

Can this issue be reproduced with the latest version?
Yes
What did you do?
func (d *Telegram) upload(path string) (int, *tg.Document, error) {
	f, err := uploader.NewUploader(d.TGClient).WithPartSize(524288).WithProgress(d).WithThreads(12).FromPath(d.Context, path)
	if err != nil {
		return 0, nil, err
	}
	msg, err := unpack.Message(message.NewSender(d.TGClient).Media(d.Context, message.UploadedDocument(f)))
	if err != nil {
		return 0, nil, err
	}
	doc, ok := msg.Media.(*tg.MessageMediaDocument).Document.AsNotEmpty()
	if !ok {
		return 0, nil, fmt.Errorf("invalid document")
	}
	return msg.ID, doc, nil
}

What did you expect to see?
No error
What did you see instead?
upload part: send upload part 81 RPC: rpcDoRequest: retryUntilAck: engine forcibly closed: context canceled
upload part: send upload part 154 RPC: rpcDoRequest: engine forcibly closed: context canceled
What Go version and environment are you using?
go version go1.19.2 linux/amd64

go env Output

GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/user/.cache/go-build"
GOENV="/home/user/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/user/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/user/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.19.2"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/user/gotelegram/go.mod"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build1435934855=/tmp/go-build -gno-record-gcc-switches"

Looks like client was closed during upload.

Client can close itself on some critical failure.
Can you please pass logger to client and enable debug logs?

Let's fix it, I just need some debug logs just before this error happens to investigate.

Sorry, pretty busy right now, I'll try to find some time to investigate it soon.
General workaround for this error is use client.Run() directly without bg helper.

After inspecting logs, I've found out that telegram client observed connection timeout:
2023-03-16T06:29:57.022Z	DEBUG	conn	manager/conn.go:125	Connection dead	{"v": "v0.79.0", "conn_id": 0, "dc_id": 5, "error": "group: task pingLoop: disconnect (pong missed): write: write: write intermediate: write tcp <IP_ADDRESS>:46430-><IP_ADDRESS>:443: i/o timeout", "errorVerbose": "group:\n    github.com/gotd/td/internal/mtproto.(*Conn).Run\n        /root/go/pkg/mod/github.com/gotd/td@v0.79.0/internal/mtproto/conn.go:214\n  - task pingLoop:\n    github.com/gotd/td/internal/tdsync.(*LogGroup).Go.func1\n        /root/go/pkg/mod/github.com/gotd/td@v0.79.0/internal/tdsync/log_group.go:48\n  - disconnect (pong missed):\n    github.com/gotd/td/internal/mtproto.(*Conn).pingLoop\n        /root/go/pkg/mod/github.com/gotd/td@v0.79.0/internal/mtproto/ping.go:115\n  - write:\n    github.com/gotd/td/internal/mtproto.(*Conn).pingDelayDisconnect\n        /root/go/pkg/mod/github.com/gotd/td@v0.79.0/internal/mtproto/ping.go:71\n  - write:\n    github.com/gotd/td/transport.(*connection).Send\n        /root/go/pkg/mod/github.com/gotd/td@v0.79.0/transport/connection.go:48\n  - write intermediate:\n    github.com/gotd/td/internal/proto/codec.Intermediate.Write\n        /root/go/pkg/mod/github.com/gotd/td@v0.79.0/internal/proto/codec/intermediate.go:64\n  - write tcp <IP_ADDRESS>:46430-><IP_ADDRESS>:443: i/o timeout"}
github.com/gotd/td/telegram/internal/manager.(*Conn).Run.func1
	/root/go/pkg/mod/github.com/gotd/td@v0.79.0/telegram/internal/manager/conn.go:125
github.com/gotd/td/telegram/internal/manager.(*Conn).Run
	/root/go/pkg/mod/github.com/gotd/td@v0.79.0/telegram/internal/manager/conn.go:128
github.com/gotd/td/internal/tdsync.(*CancellableGroup).Go.func1
	/root/go/pkg/mod/github.com/gotd/td@v0.79.0/internal/tdsync/cancel_group.go:48
golang.org/x/sync/errgroup.(*Group).Go.func1
	/root/go/pkg/mod/golang.org/x/sync@v0.1.0/errgroup/errgroup.go:75
2023-03-16T06:29:57.022Z	INFO	telegram/connect.go:75	Restarting connection	{"v": "v0.79.0", "error": "group: task pingLoop: disconnect (pong missed): write: write: write intermediate: write tcp <IP_ADDRESS>:46430-><IP_ADDRESS>:443: i/o timeout", "errorVerbose": "group:\n    github.com/gotd/td/internal/mtproto.(*Conn).Run\n        /root/go/pkg/mod/github.com/gotd/td@v0.79.0/internal/mtproto/conn.go:214\n  - task pingLoop:\n    github.com/gotd/td/internal/tdsync.(*LogGroup).Go.func1\n        /root/go/pkg/mod/github.com/gotd/td@v0.79.0/internal/tdsync/log_group.go:48\n  - disconnect (pong missed):\n    github.com/gotd/td/internal/mtproto.(*Conn).pingLoop\n        /root/go/pkg/mod/github.com/gotd/td@v0.79.0/internal/mtproto/ping.go:115\n  - write:\n    github.com/gotd/td/internal/mtproto.(*Conn).pingDelayDisconnect\n        /root/go/pkg/mod/github.com/gotd/td@v0.79.0/internal/mtproto/ping.go:71\n  - write:\n    github.com/gotd/td/transport.(*connection).Send\n        /root/go/pkg/mod/github.com/gotd/td@v0.79.0/transport/connection.go:48\n  - write intermediate:\n    github.com/gotd/td/internal/proto/codec.Intermediate.Write\n        /root/go/pkg/mod/github.com/gotd/td@v0.79.0/internal/proto/codec/intermediate.go:64\n  - write tcp <IP_ADDRESS>:46430-><IP_ADDRESS>:443: i/o timeout", "backoff": "569.375796ms"}

This led to rpc engine restart and re-connection, which drops all ongoing requests.
All invokations will fail after this.
While re-connection is in progress, no requests can be successfully done.
Also I've found out that reconnect was successfull and invocations should work after that.
So, there is no bug in client that we can fix.
To mitigate this issue, implement retries for uploads on your side.
Probably we can add opt-in retry for uploading individual chunks in uploader, but this will be not a bugfix, but a feature.

What's the main reason why the observed connection got a timeout?

It got timeout while sending data via TCP connection, i.e. some network problems, that lead to ping loop to fail.
Looks like re-creating client is better workaround. This can't be implemented in contrib/bg package now.
Anyway, client should work after reconnect. I'll try to reproduce this issue, but logs shows that connection was restarted.

I've simulated connection loss and looks like client can't recover for some reason.
So more general issue is #1030

@ernado So using  client.Run  will mitigate this issue?
Also  retry for uploading individual chunks is the best approach  I am trying  to implement this  and found a change will be needed  here https://github.com/gotd/td/blob/999a9a3ad5fd8f0437b197b3f9d758fd9240c733/telegram/uploader/big.go#L34  what is the best way to recreate client here.


Add text-label option to circle* viz classes

For all circle* viz types, add a parameter option to use a data property as a text-label.
An example of labels on top of circles based on a data property:
https://www.mapbox.com/mapbox-gl-js/example/cluster/

An initial version of this merged in 0.0.2.


Fix: :bug: Echarts resize error

closed #148

https://github.com/apache/echarts/issues/15253#issuecomment-870635766


disambiguate "duplicate" methods

sometimes we get "duplicated" method names:
...
0.07 java.net.URLClassLoader$1.run
0.07 java.net.URLClassLoader$1.run
...
this could happen for a number of reasons, it would be useful to have the option to collapse/aggregate these into one line item in the reporting or to disambiguate them with some additional information to indicate what one or other relates to or how it came to be different from the other.
else this could be a bug where we are double counting a method in some way.

Problem here might be that the method is recompiled to a different 'jmethodId'. The profile is currently collecting stats for each method by methodId, not by name. Alternatively it might be that there are several classloaders in play, leading to the same method name correctly being identified with several method ids and again correctly being profiled separately.
I see 2 optional solutions:

Collect stats by name: This is probably what most people want, but can be quite misleading in the face of several classloader possibly loading very different implementations for the same method.
Report jmethodId: This will clearly signal that these are 2 different methods, but is quite opaque and I can't see how anyone would be helped by this reporting. It would be helpful as debug information and perhaps as a way to dissambiguate confusing profiles where the edge case from point 1 is encountered.
Since the bug is quite old, a reproduction case would be useful.

If you can get the parameter types of the jmethodid then we could disambiguate overloads based upon their signature. This would solve some of the ambiguity problems.

@RichardWarburton good point, this is actually not hard to do:
error = jvmti->GetMethodName(frame.method_id, methodName.GetRef(), NULL, NULL);
We seem to have opted out of getting the signature here, could add that in


Added useLocation hooks

Added useLocation hooks where necessary

Codecov Report

Merging #266 (b771458) into main (6b1ad41) will decrease coverage by 0.01%.
The diff coverage is 0.00%.

Additional details and impacted files

@@           Coverage Diff            @@
##            main    #266      +/-   ##
========================================
- Coverage   5.32%   5.31%   -0.02%
========================================
  Files         43      43
  Lines       1764    1768       +4
  Branches     328     328
========================================
  Hits          94      94
- Misses      1670    1674       +4

Impacted Files
Coverage Δ

src/routes/components/export/ExportSubmit.tsx
0.00% <0.00%> (ø)

...components/state/empty-filter/EmptyFilterState.tsx
0.00% <0.00%> (ø)

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 6b1ad41...b771458. Read the comment docs.


[vk] add debug labels for descriptor sets

Fixes #issue
PR checklist:

[x] make succeeds (on *nix)
[ ] make reftests succeeds
[ ] tested examples with the following backends:
[ ] rustfmt run on changed code

bors retry

Bors retry
(Will add you to the team shortly)

On Sep 15, 2019, at 11:47, Aleksi Juvani<EMAIL_ADDRESS>wrote:
bors retry
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.


OSX 10.10 compatibility

Hi, I fixed whatever issues came up on OS X 10.10. There were just a few minor problems.
The app now successfully runs on my machine, which is running the latest Yosemite preview.
The commit messages go into more details.

Hey @x1024, thanks for your contribution. After some discussing with the core team, we'll have to close this one as it collides with our current development.
Alcatraz should be working normally on 10.10, and we'll add plugin list caching soon.


Code Mirror + Compiler

Hi guys, I  wuold like to create a training code site, I can put into my site codeMirror, how can I control the code write in Code Mirror, any suggest?

The docs are here, and the proper place to ask questions (after you've read the docs) is here.


Fix file associations on Windows + opening project bug

Pull Request Description

Fixes #10983 The ext field was not set according to the documentation in rust
Also discovered a regression in opening project by passing argument/clicking the file: we store the file location as file:// URL, but without caution, it made a havoc with windows paths.

Important Notes
Need to confirm that everything works on macOS (installation with file associations + opening project when process is running and when not)
Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[x] The documentation has been updated, if necessary.
[ ] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
[x] All code follows the
Scala,
Java,
TypeScript,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
[ ] Unit tests have been written where possible.

Working on MacOS:

Opening .enso-project files while running/not running the app
Opening .enso files while running/not running the app

Although I might note a small detail: it is impossible to open multiple projects simultaneously when clicking files in Finder – the latest project always takes precedence and the previous one will be closed. It is the issue on develop as well, though, so not to block this PR.

@vitvakatu i think being able to only open a single project is intentional, but tbh I'm not 100% sure it is intended behavior for the local backend. @jdunkerley can you confirm or deny?

Yes currently we only support opening one project at a time. We will improve that later.


swedish ssn symbol depends on birthday date of person

If a person is older than 100 years, their SSN should have a "+" as the separator.
I found that when I was using datafaker and it sometimes creates SSNs that look like "000229+XXXX," which is an invalid SSN because February 29 did not exist in the year 1900.
more info: https://swedish.identityinfo.net/personalidentitynumber

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 77.77778% with 6 lines in your changes missing coverage. Please review.

Project coverage is 92.28%. Comparing base (ab1c267) to head (c5ced30).

Files with missing lines
Patch %
Lines

...n/java/net/datafaker/idnumbers/SwedenIdNumber.java
77.77%
1 Missing and 5 partials :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff              @@
##               main    #1458      +/-   ##
============================================
- Coverage     92.37%   92.28%   -0.09%
- Complexity     3228     3231       +3
============================================
  Files           324      324
  Lines          6332     6349      +17
  Branches        606      610       +4
============================================
+ Hits           5849     5859      +10
- Misses          340      343       +3
- Partials        143      147       +4

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@TrueJacobG Thank you, merged!


RSS feeds

The readme mentions native RSS support. I see feed definitions in views.py, but the feed views are not referenced  in the URLs, so they're effectively off-line.
Default templates should probably also link to feed views or include autodiscovery meta tags for them.

Ah, I see what's happening here. You have defined a feed URL for LatestCategoryFeed, but not for LatestEntriesFeed (which is the most important one), since that one hangs off a wagtail view and is not part of your own URL definitions. Hmm.  Thinking about this...

Feel free to suggest changes - I usually end up having to customize each usage of this app anyway. But sane defaults are good.

Part of the challenge is that wagtail lets you stick a BlogIndex anywhere in the hierarchy, so we really have a multi-blog system here. That works for the most part, but makes it tough to define URL structures for feeds when the first part of the URL is unknown. We can't even guarantee that 'blog' is in the URL at all - these are all valid blog index URLs:
/blog
/teachers/joe/blog
/parents/mary

I'm thinking maybe any URL that ends with feed or blogfeed triggers a view that inspects the page type at the parent of that? So /parents/mary/blogfeed would inspect the page type of /parents/mary. If that's a BlogIndex, it would return a feed for that blog; else 404. Gets complicated quickly.

OK, here's the solution I came up with, in case you want it to incorporate it / provide better defaults. This version works for multiple blogs on the site at any path, dynamically creates the main title, link and description, uses BLOG_PAGINATION_PER_PAGE from settings if it exists for number of items, and truncates the number of words in item descriptions.
So that the URL is not tied to paths under /blog, add to the global urls.py (matching URLs ending with "rss")
from blog.views import LatestEntriesFeed
...
urlpatterns = patterns(
    '',
    # Generate RSS feeds for blogs
    url(r'(?P<blog_slug>[\w-]+)/rss.*/', LatestEntriesFeed(), name="latest_entries_feed"),

and in blog.views:

class LatestEntriesFeed(Feed):
    '''
    If a URL ends with "rss" try to find a matching BlogIndexPage
    and return its items.
    '''

    def get_object(self, request, blog_slug):
        return get_object_or_404(BlogIndexPage, slug=blog_slug)

    def title(self, blog):
        return blog.title

    def link(self, blog):
        return blog.full_url

    def description(self, blog):
        return blog.search_description

    def items(self, blog):
        num = getattr(settings, 'BLOG_PAGINATION_PER_PAGE', 10)
        return blog.get_descendants()[:num]

    def item_title(self, item):
        return item.title

    def item_description(self, item):
        return truncatewords(item.specific.body, 50)

    def item_link(self, item):
        return item.full_url

Ok, will review when I have some time.

Sorry it's taken so long for me to respond. Would you be up for submitting a pull request and unit test?
I'd like the idea of supporting more options with where things go on the tree, different urls, multiple blogs ect. I'm not sure I have time for it myself.

Ditto - sorry for response delay. I've moved on to another project and am not deep in wagtail land ATM, but will resume in a month or two. Feel free to manually paste in the code above, or I'll do a PR in a few months. Cheers!


feat: massive refactor and fix for xo 40 +

I forked and published this package as a new extension - since it seems this is no longer being maintained or accepting PRs. This PR is a giant deviation so I don't necessarily expect it to get approved, although I would love to get the issue hunt reward for #91 💯  - but no big deal either way!
Please try this via the link below, and feel free to file issues in my fork. My extension should work now for all versions of XO.
If for some reason this PR does get some attention - I would be happy to become the maintainer of this repo and archive my fork - and find some way to merge the extensions to promote oneness in the community or whatever!
My published extension can be found below:
https://marketplace.visualstudio.com/items?itemName=spence-s.linter-xo

also the reason I removed TS from the project was

I don't really use TS so I found it distracting.
I solved this by using dynamic imports for importing the xo which are not yet supported. https://github.com/microsoft/TypeScript/issues/45125

Please try this via the link below, and feel free to file issues in my fork.

Your fork has issues disabled.

Please try this via the link below, and feel free to file issues in my fork.

Your fork has issues disabled.

Fixed now, thanks!

@Spence-S would you be open to be added to this repo and take the maintenance/development/release on you? I don't have the time to do any active work on this anymore.

@SamVerschueren yes - that would be ideal. Not sure how extension ownership/permissions work but I'd be happy to maintain as much as needed and keep the community unified on a single solution.

Awesome! I'll make sure to do the necessary steps!

@Spence-S can you please request the bounty so I can credit you?

@yakov116 Thank you so much for this! I submitted this PR against the issue some time ago. I don't see a way I can do anything else. My submitted PR links directly to this page. 🤷🏻♂

@can you close the issue? Maybe that will allow me to award you?

@yakov116 done

@Spence-S Do you have Twitter so we can chat through DM regarding publish rights for this extension? Or should I just drop you an email?

@SamVerschueren sent you a dm on Twitter


Capture packets sent per second data for CTS Traffic

Get packets sent per second counter during Stage 2, verify at least 600,000 packets per second sent by CTS Traffic

Closing since NTTTCP has replaced CTSTraffic.


[CHANGE ME] Re-generated Functions to pick up changes in the API or client library generator.

This PR was generated using Autosynth. :rainbow:
Synth log will be available here:
https://source.cloud.google.com/results/invocations/236b3d5e-1e5b-42fe-8ea8-3a47fdeb391f/targets

[ ] To automatically regenerate this PR, check this box. (May take up to 24 hours.)

superceded by https://github.com/googleapis/google-cloud-php/pull/5010/files


Decoupling styles from HTML

Hello,
Just to give a background on this request, I am one of the developers on the UI Bootstrap project, and am on the ng-bootstrap team for implementing Bootstrap 4 with Angular 2 usage through writing idiomatic Angular 2 components around Bootstrap.
One problem we have had in UI Bootstrap with Bootstrap 3 is that the DOM structure is very tightly coupled by the CSS in a way that is hard to negotiate with. One example of this is with the accordion groups/tabs. There is no allowance for intermediary empty elements, so this creates a problem if our generated HTML ends up like

  <uib-accordion-group>

      ...

  </uib-accordion-group>
  <uib-accordion-group>

      ...

  </uib-accordion-group>
  ...

This situation results in third party libraries having to hack around this undesired coupling in a way that goes against consumption in libraries such as Angular. I realize in Bootstrap 4 that implementations are a little different, but a good solution here is important to us. Any guidance/thoughts on the Bootstrap's team's position here is much appreciated.
Reference to issue where this causes problem in Angular 1.x: https://github.com/angular/angular.js/issues/13805

Bootstrap v4 is moving towards using explicit classes wherever feasible, and avoiding tag name selectors and child selectors, which should help with this generally, although perhaps not in the specific case of accordions.
CC: @mdo
@wesleycho Out of curiosity, what's the technical reason that UI Bootstrap can't generate <uib-accordion-group class="panel"> instead?

@cvrebert problem is that we must explicitly set the display: block styling for it in that case, which may not necessarily be desired for a user (say if they want display: flex instead).

@wesleycho Could you set uib-accordion-group { display: block; } and then the user could use a class to override the display if need be (and their class would win over your tag-name selectors because of CSS specificity)?

@cvrebert for those situations, that would work - for something like the carousel or tabs, in v3 they have some direct child selectors, which creates a tighter coupling. Perhaps this would be enough to override that problem though, would need to investigate this more deeply.

As @cvrebert mentioned, we're trying to decouple structured markup from styles through the use of singular classes in our selectors. That's about all we can offer right now I'm afraid.


Error Analysis and Interpretability Scalability Design Decisions

Issue: Error analysis heatmap and treemap views can be calculated on very large datasets. Interpretabiliy, however, downsamples to 5K and only generates that many local explanations and render them in the UI. This mismatch of scalability capabilities needs to be navigated and addressed in the UI to not limit the error analysis functionalities and features. We discussed the following solution: We will calculate Error analysis tree map and heat map on ALL DATA, but only generate explanations for 5K subsampled dataset. Now, users going thorugh the dashboard can see the following options:
-- User selects a cohort on the decision tree or selects one of more grids on the heatmap and clicks on “explanation”. Downsampling for explanation can lead to that cohort not having any explanations attached (In an unfortunate situation none of the 5K subsampled dataset covers the cohort datapoints). Solution we chose:
-------> [CHOSEN OPTION] Allow them to click on the explanation tab. But, disable only global and local explanation tabs and let them explore data explorer and ONLY see aggregate insights on all data. Aggregate insights calculations will be kicked off from UI and happen on ALL Data not subsampled data.
-- User selects a cohort on the decision tree or selects one of more grids on the heatmap and clicks on “explanation”. Downsampling for explanation can lead to that cohort not having any explanations attached (In an unfortunate situation none of the 5K subsampled dataset covers the cohort datapoints). Solution we chose:
-------> [CHOSEN OPTION] Allow them to click on the explanation tab. But, disable only global and local explanation tabs and let them explore data explorer and ONLY see aggregate insights on all data. Aggregate insights calculations will be kicked off from UI and happen on ALL Data not subsampled data.
-- User selects a cohort on the decision tree or selects one of more grids on the heatmap and clicks on “explanation”. Downsampling for explanation can lead to that cohort having some explanations attached (explanations generated for the downsampled dataset has some overlap with that cohort datapoints). Solution we chose:
-------> [CHOSEN OPTION] 1. Data explorer will show aggregate insights of all cohort data points of that cohort.
-------> [CHOSEN OPTION] 2. Global explanation will have a warning on top stating that this is overall explanations of the subsampled dataset. (if the explanations are for less than X datapoints, maybe we go with the previous approach of assuming no explanations are there…)
-------> [CHOSEN OPTION] 3. [For end of Jan] local explanation tab only shows the cohorts data points that have explanations.
[In future, not for end of Jan] we would like to expand our UI capabilities to enable on-demand generation of local explanations for a cohort datapoints that user has selected and thus, in the instance view, we can show all individuals of that cohort. Adding pagination capabilities to our instance table to expand it at scale [Using AP as our role model].

for warning message, add: "for scale reasons of the UI, explanations are randomly subsampled down to <5k datapoints"

closing as PR https://github.com/microsoft/responsible-ai-toolbox/pull/1098 has been merged and this was the last remaining part of this issue


Rebuilding stuck waiting on previous build

Rebuilds against persistent orgs should set previous rebuilds and original build to non-running status and release org lock.

It is possible to rebuild a build at any point unless it has completed as successful. This means that you can just stack up a ton of rebuilds even while they are all queued or waiting. The rebuild should not be possible until the build has completed in some way (fail/error/success).


IndexError: list index out of range

HYE THERE
I am using peddy to calculate PCA with command
-m peddy -p 4 --plot --prefix 69_out PCA_data/69_without_N_imputated.vcf.gz PCA_data/69_without_N_imputed.plk.ped
after some initial start it is giving the following error.
IndexError: list index out of range
After reading a previous discussion I also modified the last row of the ped file, but still error is prevailing.
built installed from anaconda and git hub both are giving the same error.
Kindly help me sorting it out

Hi, can you report the full error message and share your ped file? You can send it to me privately if you prefer.

Dear sure I will send you by morning. Sure
On Feb 12, 2018 11:43 PM, "Brent Pedersen"<EMAIL_ADDRESS>wrote:
Hi, can you report the full error message and share your ped file? You
can send it to me privately if you prefer.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/brentp/peddy/issues/39#issuecomment-364961847, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AiuftH125wzk0fQc7UAWxu43KcTSUDzIks5tUFwHgaJpZM4SCV2s
.
--
http://ricecongress2018.irri.org/
The International Rice Research Institute http://irri.org is a member of
the CGIAR http://cgiar.org System Organization, a global research
partnership for a food secure future.

Peddy requires that there is depth information associated with the variants. This is critical for filtering to high-quality genotype calls. You can add this artificially by setting e.g. AD=20,20.
Peddy could support cases where no genotypes have depths, but I have no plans to add that at this time as it will complicate the user-interface.

Thanks dear for Help. Just another sily question do I need to put this
information in my ped file or adding it in my command line?
On Feb 14, 2018 5:33 AM, "Brent Pedersen"<EMAIL_ADDRESS>wrote:

Peddy requires that there is depth information associated with the
variants. This is critical for filtering to high-quality genotype calls.
You can add this artificially by setting e.g. AD=20,20.
Peddy could support cases where no genotypes have depths, but I have no
plans to add that at this time as it will complicate the user-interface.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/brentp/peddy/issues/39#issuecomment-365411598, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AiuftB5z0IbZtS5VsnD5zxhpnYoqYi2qks5tUf-sgaJpZM4SCV2s
.

--
http://ricecongress2018.irri.org/
The International Rice Research Institute http://irri.org is a member of
the CGIAR http://cgiar.org System Organization, a global research
partnership for a food secure future.

It would have to go in your VCF. Peddy only uses the first 6 columns of the ped/fam file to determine the expected relationships.


It is posible to contro by step/dir???

Hi sir iam interesting with your project.
It is posible to drive motor by step/dir???
And it posible to make big driver for ac servo 220v, amd with 2000ppr encorder sir??
I will wait for your reply.
Thank uou so much.

Hello @artayasa,
Thank you for your comments! This library is for brushless DC motors, and the main purpose is for starters, including myself, to learn the basics of motor control, instead of a library which works under broad scenario.
Stepper motor, driven by step/dir signals, uses a different control strategy. And high voltage is usually an issue of hardware in addition to software. I would suggest you to use some big libraries, like Odrive.
Thank you!
Yours sincerely,
Haotian

Hi, the period for the PWM is 2400, but in the foc calculation for duty, 1600 is used. Is this a mistake? thx!


Upgrade gradle version

We should update our gradle version to the latest version.

fix bootstrap classpath issue
fix bintrayUpload

Upgraded to gradle 7.1


reddit data cleaning & initial analysis

create script

reddit data cleaning and initial data analysis

No conflict with the base branch. Okay to merge.


RpcQueryRequest expects and sends blockId but RPC node expects block_id

Describe the bug
This code conforms to the TypeScript typings, and the library has no problem sending it off:
await near.connection.provider.query({
  request_type: 'view_account',
  account_id: 'nectar.near',
  blockId: 40258947,
});

But the RPC node expects block_id instead of blockId and breaks.
Possibly related
To Reproduce
Steps to reproduce the behavior:
const near = await connect({
  networkId: 'mainnet',
  keyStore: new keyStores.BrowserLocalStorageKeyStore(),
  nodeUrl: 'https://archival-rpc.mainnet.near.org', // using archival RPC so that I can request a specific block ID
  walletUrl: 'https://wallet.mainnet.near.org',
  helperUrl: 'https://helper.mainnet.near.org',
});

await near.connection.provider.query({
  request_type: 'view_account',
  account_id: 'nectar.near',
  blockId: 40258947,
});

Generated request:
{
    "method": "query",
    "params": {
        "request_type": "view_account",
        "account_id": "nectar.near",
        "blockId": 40258947
    },
    "id": 125,
    "jsonrpc": "2.0"
}

Response:
{
    "jsonrpc": "2.0",
    "error": {
        "code": -32602,
        "message": "Invalid params",
        "data": "Failed parsing args: no variant of enum BlockReference found in flattened data"
    },
    "id": 125
}

Expected behavior
Either the library expects block_id or it remaps blockId to block_id such that generated request is:
{
    "method": "query",
    "params": {
        "request_type": "view_account",
        "account_id": "nectar.near",
        "block_id": 40258947
    },
    "id": 125,
    "jsonrpc": "2.0"
}

Response:
{
    "jsonrpc": "2.0",
    "result": {
        "amount": "19916070150000000000000",
        "locked": "0",
        "code_hash": "11111111111111111111111111111111",
        "storage_usage": 346,
        "storage_paid_at": 0,
        "block_height": 40258947,
        "block_hash": "HxdYhKTs44Huyg7gZkMoUxVW6xHP2j1BfQeBroHtGeTx"
    },
    "id": 125
}

Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Windows 10 20H2 Build 19042.1081
near-api-js version 0.41.0

Additional context
I am connecting to an archival RPC node.

I'm using the last version of near-api-js, but the code is still:
export declare type BlockReference = {
    blockId: BlockId;
} // etc.

So it hasn't been fixed, has it?
I have to use force by disabling the TS typing:
near.connection.provider.query({
    request_type: 'view_account',
    account_id: accountId,
    block_id: blockHeight,
} as any)


pb_decode clears callbacks in pb_callback_t fields within oneof's

Hi,
Problem:
When decoding a message which has callback dependent fields within a oneof, pb_decode_static_field will re-initialize the selected oneof and remove any attached callbacks, causing those fields to be skipped in the decoding.
Solution:
I think this issue can be solved strictly by removal of the following code: pb_decode.h lines [468, 474]:
if (PB_LTYPE(type) == PB_LTYPE_SUBMESSAGE)
{
  /* We memset to zero so that any callbacks are set to NULL.
  * Then set any default values. */
  memset(iter->pData, 0, iter->pos->data_size);
  pb_message_set_to_defaults((const pb_field_t*)iter->pos->ptr, iter->pData);
}```

Nope, see #175. Because all the subfields occupy the same memory, the callbacks have to be cleared to avoid crashing.
In 0.4.x, there are better ways to handle this.

It seemed to me that since you know the which tag of the union, you know which member of the union will actually be used in the decoding of the submessage, you could just set the callback of the active union element and leave the others alone. There's probably a use case I'm missing...
Thank you, I will look into the no_unions and submsg_callback options.  Appreciate your work!

The issue is that within an union, all the members occupy the same
memory. So if you store a callback in different submessages inside
oneof, they could overwrite each other.
In simple cases it would be possible for exactly one oneof member
to contain callbacks, but even that would break if the protobuf
message would contain a different oneof member before the
callback-containing one. That's not very common, but it is valid
protobuf.

And just to complete the solution; in the new callback for the union/oneof, one can assign typical callbacks that are normally null'd
bool DecodeSegmentField(pb_istream_t *stream, const pb_field_t *field, void **arg)
{
	auto& Segment = *reinterpret_cast<Segment_t*>(arg[0]);

	if ( field->tag == myproto_Segment_external_tag )
	{
		auto& Message = *reinterpret_cast<myproto_Segment_external*>( field->message );
		Message.textures.external.url.funcs.decode = DecodeToStdString;
		Message.textures.external.url.arg = &Segment.mExternalUrl;
		Message.textures.external.content_type.funcs.decode = DecodeToStdString;
		Message.textures.external.content_type.arg = &Segment.mExternalContentType;
		return true;
	}
	else
	{
		return false;
	}
}


Default forward axis Z+ or -Z?

master branch
Manjaro Linux
I was playing around trying to make an IK system when I ran completely stumped against why I couldn't point bones in the proper direction.
To my knowledge, and correct me at any point, the steps required to point something are as follows:
var target_t = $target.global_transform
var bone = $arm.global_transform
var old_v = -bone.basis[2]
var new_v = target_t.origin - bone.origin
var rot_axis = old_v.cross(new_v)
var new_t = bone.looking_at(target_t.origin, rot_axis)

$arm.global_transform = new_t

This above code makes sense when I use a spatial node with a mesh facing the Godot forward, -Z.
var sk = get_parent() #Assume Skeleton parent
if target == null:
	return
var target_t = target.global_transform #target is a MeshInstance node
var bone = sk.get_bone_pose(1)
var old_v = -bone.basis[2]
var new_v = target_t.origin - bone.origin
var rot_axis = old_v.cross(new_v)
var new_t = bone.looking_at(target_t.origin, rot_axis)

sk.set_bone_pose(1, bone.interpolate_with(new_t, delta))

Now when I move this code to a Skeleton and try to apply the same logic to a bone, it always seems really messed up. The bone never points at the target, it either points in the opposite direction, or 90 degrees to it.
This is strange to me because I thought I created my arm in blender in the standard -Y forward, which I thought the axis switch is covered in the conversion. However I notice that the models coming in from blender in both DAE and GLTF are facing Z+ which is my guess as to why the transforms are also backward.
This is also confusing to me, because in the Skeleton tutorial it says that the bone vector is basis[2] of the bone transform. This must be so, but how is this supposed to be used when the looking_at function points using -Z?
I'm sure this is confusing for some others as well, as I've not found much on IK in godot yet, I'm just hoping someone who understands the system better than I can explain this odd behaviour, or heck maybe its not even odd and I'm just wrong.
Can provide a project if needed.
Thanks

@jedStevens raises some good points. Pressing numpad 1 brings up "front view" which implies the forward direction is +Z but look_at rotates assuming -Z. Am I missing something or should I open a new issue about this?


chore(deps): update quay.io/mytestworkload/test-renovate-updates-task-coverage:0.1 docker digest to 415fcd8

This PR contains the following updates:

Package
Type
Update
Change

quay.io/mytestworkload/test-renovate-updates-task-coverage
tekton-bundle
digest
c0e8d54 -> 415fcd8

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: component-a-pipelinerun-pr.yaml
Command failed: migration-tool.py -f quay.io/mytestworkload/test-renovate-updates-task-coverage:0.1@sha256:c0e8d54d653aea2b710e667f5559b3ad67a77832b58d663c1950ae0687ba60f9 -t quay.io/mytestworkload/test-renovate-updates-task-coverage:0.1@sha256:415fcd8e3eac18bd4bba678e4acb2437ecc9ee30f88d74cece1dfbced557ba6e -m manual -p component-a-pipelinerun-pr.yaml
INFO:build.log:2024-09-10 09:17:48,340:Doing migration for task update:
INFO:build.log:2024-09-10 09:17:48,340:from: quay.io/mytestworkload/test-renovate-updates-task-coverage:0.1@sha256:c0e8d54d653aea2b710e667f5559b3ad67a77832b58d663c1950ae0687ba60f9
INFO:build.log:2024-09-10 09:17:48,340:to: quay.io/mytestworkload/test-renovate-updates-task-coverage:0.1@sha256:415fcd8e3eac18bd4bba678e4acb2437ecc9ee30f88d74cece1dfbced557ba6e
DEBUG:build.log:2024-09-10 09:17:48,340:inspect image: quay.io/mytestworkload/test-renovate-updates-task-coverage:0.1@sha256:415fcd8e3eac18bd4bba678e4acb2437ecc9ee30f88d74cece1dfbced557ba6e
INFO:migrate_per_task:2024-09-10 09:17:49,705:[{'name': '0.1-95c412fc032c26323bfd1d5ef4332a6cc8fe72f1', 'reversion': False, 'start_ts':<PHONE_NUMBER>, 'manifest_digest': 'sha256:415fcd8e3eac18bd4bba678e4acb2437ecc9ee30f88d74cece1dfbced557ba6e', 'is_manifest_list': False, 'size': 339, 'last_modified': 'Tue, 10 Sep 2024 01:08:14 -0000'}, {'name': '0.1-5f0a2b8e2ccb06a2a28f46a7c82178d78247be45', 'reversion': False, 'start_ts':<PHONE_NUMBER>, 'manifest_digest': 'sha256:c0e8d54d653aea2b710e667f5559b3ad67a77832b58d663c1950ae0687ba60f9', 'is_manifest_list': False, 'size': 338, 'last_modified': 'Mon, 09 Sep 2024 06:14:34 -0000'}]
INFO:migrate_per_task:2024-09-10 09:17:53,816:discovered migration file ./tasks/migrations/task-coverage-0.1.1.sh
INFO:migrate_per_task:2024-09-10 09:17:57,123:discovered migration file ./tasks/migrations/task-coverage-0.1.2.sh
INFO:migrate_per_task:2024-09-10 09:17:57,178:apply migrations ./tasks/migrations/task-coverage-0.1.1.sh to /tmp/tmp3hld5yci-pipeline
INFO:migrate_per_task:2024-09-10 09:17:57,201:apply migrations ./tasks/migrations/task-coverage-0.1.2.sh to /tmp/tmp3hld5yci-pipeline
Error: parsing expression: Lexer error: could not match text starting at 1:1 failing at 1:3.
	unmatched text: "f."
Traceback (most recent call last):
  File "/home/cqi/.local/bin/migration-tool.py", line 236, in <module>
    main()
  File "/home/cqi/.local/bin/migration-tool.py", line 224, in main
    migrate_per_task.migrate(args.from_task_bundle, args.to_task_bundle, args.pipeline_run_file)
  File "/home/cqi/code/konflux/test-renovate-updates/migrate_per_task.py", line 129, in migrate
    subprocess.run(["bash", migration_file, pipeline_file], check=True)
  File "/usr/lib64/python3.12/subprocess.py", line 571, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['bash', './tasks/migrations/task-coverage-0.1.2.sh', '/tmp/tmp3hld5yci-pipeline']' returned non-zero exit status 1.


Djanicek/core 1553/collect test results

This adds a script to our test pipelines that pushes data from each test out to pachyderm.pachops. We are not really processing this data in the PR. The next ticket  will be processing the data in an egress pipeline so we can visualize results in Grafana.
This ticket roughly has 2 parts:

Output test data to a file if we aren't already. We have slightly different was of doing this depending on if we are using gotestsum or go test, but the end result should be a jsonl file in the /tmp/test-results folder for each test job. (I'd like to reign some of these different test commands in when I look at splitting the tests more efficiently.)
Run the go collector script at etc/testing/circle/workloads/go-test-results/collector/main.go after the tests finish in a separate job.

Example data from this branch is here: https://pachyderm.pachops.com/lineage/ci-metrics/repos/go-test-results-raw/branch/default
Interestingly, test-go verbose output is a little over 1gb of data. I think this is OK short term, but long term I think we probably don't want to store 1GB per branch indefinitely. We could just clean the raw data out of pachyderm when the branch is no longer in use. Since the next step will be putting the important data into the DB for visualization, we shouldn't really need the raw data for an extended period of time. Follow up ticket for that if/when we think it is necessary: https://pachyderm.atlassian.net/browse/CORE-1645

few comments.
but i think we should consider maybe not failing the jobs if it cant upload. how reliable we think the pachops cluster will be. would hate to see alot of CI failures/block in case pachop cluster is not taking in the data. but if its reliable enough then its okay with me

I was already considering this, but never quite made up my mind. Since it came up, I'll do it before merge.


Is it possible to use multiline strings in state trigger decorators?

As an example:
_state_sensor = 'sensor.office_state'
@state_trigger(f"""
{_state_sensor} in ['recently occupied', 'unoccupied', 'dormant', 'unavailable'] and
(sensor.octoprint_actual_tool0_temp == 'unavailable' or float(sensor.octoprint_actual_tool0_temp) <= 110) and
(sensor.octoprint_actual_bed_temp == 'unavailable' or float(sensor.octoprint_actual_bed_temp) <= 110)
""", state_hold_false=0)
def should_turn_off():
    _light_off()

This does not seem to work at all, which is pretty disappointing. Am I doing something wrong?

Remove the starting space, as from my tests it is the main cause.
Also, if you want your complex triggers to be more readable, try playing with formatting instead:
@state_trigger(
    f"{LAUNDRY_VENTS} == 'off'"
    f" and {entity_exists(LAUNDRY_TEMPERATURE)}"
    f" and ( "
    f"  float_({LAUNDRY_TEMPERATURE}) <= {TEMPERATURE_LOW} "
    f"  or float_({LAUNDRY_TEMPERATURE}) > 30"
    f" )",
    watch=[LAUNDRY_TEMPERATURE],
    state_hold=HOLD_2H,
    kwargs={
        'disable_notification': True,
        'target': TELEGRAM_CHAT_ALERT_HA,
    },
)

Don't mind the constants in this example, just the formatting.
For you it's
_state_sensor = 'sensor.office_state'
@state_trigger(
    f"{_state_sensor} in ['recently occupied', 'unoccupied', 'dormant', 'unavailable']"
    f" and (sensor.octoprint_actual_tool0_temp == 'unavailable' or float(sensor.octoprint_actual_tool0_temp) <= 110)"
    f" and (sensor.octoprint_actual_bed_temp == 'unavailable' or float(sensor.octoprint_actual_bed_temp) <= 110)",
    state_hold_false=0
)
def should_turn_off():
    _light_off()

or
_state_sensor = 'sensor.office_state'
@state_trigger(
    f"{_state_sensor} in ['recently occupied', 'unoccupied', 'dormant', 'unavailable']"
    f" and ("
    f"   sensor.octoprint_actual_tool0_temp == 'unavailable'"
    f"   or float(sensor.octoprint_actual_tool0_temp) <= 110"
    f" )"
    f" and ("
    f"  sensor.octoprint_actual_bed_temp == 'unavailable'"
    f"  or float(sensor.octoprint_actual_bed_temp) <= 110"
    f" )",
    state_hold_false=0
)
def should_turn_off():
    _light_off()


Downgrade vscode-langaugeclient

Looks like it broke completion :(
bors r+
🤖

bors r+

Yikes is there an upstream issue about this?


[CLN] Refactor code to extract out unpacking embeddings set from existing validation logic

Refactor before https://github.com/chroma-core/chroma/issues/2286.
Description of changes
Summarize the changes made by this PR.

Improvements & Bug fixes

Unpacking and validating embeddings set is being done within a single function. This PR helps improve code readability and enforce SRP.

Test plan
How are these changes tested?

[ ] Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Documentation Changes
Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs repository?

#2686 : 2  dependent PRs (#2699 , #2709 ) 👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @spikechroma and the rest of your teammates on  Graphite

#2686 : 2  dependent PRs (#2699 , #2709 ) 👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @spikechroma and the rest of your teammates on  Graphite


Update monitor.py

Instead of using the on_any_event, expanded individual events to get around the constant opened event triggering.

Looks good! Thanks for your contributions :)


Pull react instance method impls out of ReactContext

Summary:
Context
Prior, ReactContext used to implement bridge logic.
For bridgeless mode, we created BridgelessReactContext < ReactContext
Problem
This could lead to failures: we could call bridge methods in bridgeless mode.
Changes
Primary change:

Make all the react instance methods inside ReactContext abstract.

Secondary changes: Implement react instance methods in concrete subclasses:

New: BridgeReactContext: By delegating to CatalystInstance
New: ThemedReactContext: By delegating to inner ReactContext
Unchanged: BridgelessReactContext: By delegating to ReactHost

Auxiliary changes
This fixes ThemedReactContext in bridgeless mode.
Problem: Prior, ThemedReactContext's react instance methods did not work in bridgeless mode: ThemedReactContext wasn't initialized in bridgeless mode, so all those methods had undefined behaviour.
Solution: ThemedReactContext now implements all react instance methods, by just forwarding to the initialized ReactContext it decorates (which has an instance).
Changelog: [Android][Removed] Delete ReactContext.initializeWithInstance(). ReactContext now no longer contains legacy react instance methods. Please use BridgeReactInstance instead.

Reviewed By: fkgozali
Differential Revision: D55505416

f99dc486cdd742988320a8235c180ccecdcdd0d6


Whitespace is taken over by Atom

Open a file with carefully crafted indentation. Perform no change whatsoever, and save. Bam! The indentation is destroyed, because Atom thought it knew better how whitespace should be used. And I do not talk about the polluted diff. Related issue: #8424.
Atom 1.0.7, MacOS 10.10.5 (14F27).
Again, I don't know any text editor that forces this very intrusive behavior. Intrusive as in "all your data are belong to us". You could at least provide a preference.

Closing, as a dupe of #8424.


Have compilation context info available earlier in the build process

Eventually, I hope this will allow us to ignore platform-specific dependencies when irrelevant for the current build earlier in the process. This should save on extraneous errors. As is, this seems like it already decreases coupling in the code base.

r? @alexcrichton
(rust_highfive has picked a reviewer for you, use r? to override)

@bors r+

:pushpin: Commit 84eb12f has been approved by matklad

:hourglass: Testing commit 84eb12f7d2e0aa30c40bb524d46690b2275aaab4 with merge 43308b5990ef0662dc0305eb80459de9ce93289b...

:broken_heart: Test failed - status-travis

So that last one went a little bit crazy. It does seem like this is much clearer about the actual workings, though, in that cargo_rustc did actually not represent any command, but had a whole bunch of code related to driving the compiler, which seems to make more sense in core.

This looks great to me, but let's also ask @alexcrichton about this refacrtoring!

It also seems like RLS might need updating after this PR as well: they use cargo as a library, and so are pretty sensitive to internal organization.

@bors: r+

:pushpin: Commit a340ba0 has been approved by alexcrichton

:hourglass: Testing commit a340ba0b3362a3229d03bc5863b0930ef90b4fb9 with merge 827bf050dcff4315a997649023b245c22d78133c...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing 827bf050dcff4315a997649023b245c22d78133c to master...


Different colours for different PMs

Is your feature request related to a problem? Please describe.
Sometimes I get a little confused then talking to multiple people via private messages.
Describe the solution you'd like
PMs from different people have different color. The color for each person can be random for easier implementation, but kept the same whilst on the same session.
Describe alternatives you've considered
An alternative way of making the PMs less confusing is making sent and received PMs have different colors. It might not be as easy to identify as having a different color for each friend, but it's still more friendly to your eyes than seeing a big block of text all in the same color.

I have tried to implement your feature but having some problems with getting the color into the private message screen.  So far I am trying to change the color of the sender message in the public and private chatbox.
The following changes were made in my version of git branch:
In the ChatColorConfig.Java file I included this:

The following feature was included in my version of the game:
Made another option for a different color for the 2nd user in the private messaging. The button works with changing the color but can't implement it with the private message.

The color change can happen inside the chat folder, its location is given below:

The colors are being called in the ChatMessageManager.java.


⚠ GitLab Server has degraded performance

In c0ab3ea, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 6890 ms

Resolved: GitLab Server performance has improved in 8140c4d.


Error 403 when using OpenStreetMap

I'm using my own mapbox account to download the maps. Google Map works fine, however, I would need OpenStreetMap. But regardless of the zoom level, I encountered this error "403 Error downloading tile".

I cannot get the User Interface to show the map. Why is this so?


LED Hardware needs config change before it works

Hello,
i have Hyperion.ng up and running with arduino since a month or two.
the only issue still bothering me is that if i start all the devices (raspberry, led power supply etc), the leds stay black.
hyperion.ng is running, in the webconfig i see that there is a picture in the grabber and the arduino does the initial rgb flash 2 or 3 times, but then nothing happens.
I have to change and then reset a parameter in "LED Hardware"-Section to get it working. (set the connection delay f.e.)
any ideas?

Try setting the connection delay setting (start with 5000ms) as it might be that during inital startup with the Arduino it needs a bit more time.
Had the same problem with Hyperion non-ng and that solved it here, using this adalight sketch:
https://raw.githubusercontent.com/hyperion-project/hyperion.ng/master/assets/firmware/arduino/adalight/adalight.ino
If you still have the problem just let us know and will check it further.

it's wierd.
i have the delay at 9000 ms.. Sometimes it works like a charm, sometimes i have to change one of the parameters.
I dont know wich sketch i used in arduino, but i will try the one mentioned by you just to make sure.

can be closed.
works like a charm with the sketch mentioned above.
((i also extended the startup effect to a duration of 7500 ms to get it shown))


Update GetEnvVal docstring

As recently the implementation changed
to expose additional device informaiton,
we should align comment to describe new
behaviour.

#473

Thanks for heling with this!


is website ok ?

Hi,
I get a weird error when logging on my aptabase account,
Also website is strangely displayed at : https://aptabase.com/
Sorry for opening up an issue but seemed the easiest

As this repo is related to flutter, I'd recommend you @flutter-painter open that issue on respectively repo: https://github.com/aptabase/aptabase-com
also, the website looks ok for me tho (Safari, Mac, only landing page)

Thank you for the heads up, Indeed all good in chrome


Python: Add a feature to specify service id for a semantic function

name: Semantic functions should have a service ID
about: Allows a semantic function config to include an LLM service id. Parallels an existing feature in .NET SK introduced in https://github.com/microsoft/semantic-kernel/pull/2739. The original issue was brought up in https://github.com/microsoft/semantic-kernel/issues/2228.

Closing as no longer needed.


Update skip logic in CPU info table

Pull Request Test Coverage Report for Build<PHONE_NUMBER>5
Details

0 of 2 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 63.411%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qpbenchmark/utils.py
0
2
0.0%

Totals

Change from base Build<PHONE_NUMBER>4:
0.0%

Covered Lines:
461

Relevant Lines:
727

💛  - Coveralls


[BUG] failed to parse constraint version >= <IP_ADDRESS> < 2.8.0-0: improper constraint: >= <IP_ADDRESS> < 2.8.0-0

Rancher Server Setup

Rancher version: 2.7.0
Installation option (Docker install/Helm Chart):

Helm on k3s

Proxy/Cert Details:

Information about the Cluster

Kubernetes version:  v1.24.8-k3s1
Cluster Type (Local/Downstream):

local

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom)

admin

Describe the bug
Got this error message just after deploy rancher helmchart:
[ERROR] failed to parse constraint version >= <IP_ADDRESS> < 2.8.0-0: improper constraint: >= <IP_ADDRESS> < 2.8.0-0

According to https://github.com/Masterminds/semver/blob/master/constraints.go
validConstraintRegex must match the given constraint version string, which is >= <IP_ADDRESS> < 2.8.0-0 here.
And validConstraintRegex would look like below:
^(\s*(=||!=|>|<|>=|=>|<=|=<|~|~>|\^)\s*(v?([0-9|x|X|\*]+)(\.[0-9|x|X|\*]+)?(\.[0-9|x|X|\*]+)?(-([0-9A-Za-z\-]+(\.[0-9A-Za-z\-]+)*))?(\+([0-9A-Za-z\-]+(\.[0-9A-Za-z\-]+)*))?)\s*)((?:\s+|,\s*)(=||!=|>|<|>=|=>|<=|=<|~|~>|\^)\s*(v?([0-9|x|X|\*]+)(\.[0-9|x|X|\*]+)?(\.[0-9|x|X|\*]+)?(-([0-9A-Za-z\-]+(\.[0-9A-Za-z\-]+)*))?(\+([0-9A-Za-z\-]+(\.[0-9A-Za-z\-]+)*))?)\s*)*$

Which allow version string with 3 digits, but for <IP_ADDRESS> which is 4 digits.
It may be a typo.

To Reproduce

Result
Expected Result
No error log

Screenshots

Additional context

This should be caused by this line:
https://github.com/rancher/charts/blob/d0f4ab5acb9173cead5c0b116ccc5b0fb9dc445c/index.yaml#L2494-L2509
  - annotations:
      catalog.cattle.io/auto-install: neuvector-crd=match
      catalog.cattle.io/certified: rancher
      catalog.cattle.io/display-name: NeuVector
      catalog.cattle.io/kube-version: '>=1.18.0-0 < 1.25.0-0'
      catalog.cattle.io/namespace: cattle-neuvector-system
      catalog.cattle.io/os: linux
      catalog.cattle.io/permit-os: linux
      catalog.cattle.io/provides-gvr: neuvector.com/v1
      catalog.cattle.io/rancher-version: '>= <IP_ADDRESS> < 2.8.0-0'
      catalog.cattle.io/release-name: neuvector
      catalog.cattle.io/type: cluster-tool
      catalog.cattle.io/ui-component: neuvector
      catalog.cattle.io/upstream-version: 2.2.3
    apiVersion: v1
    appVersion: 5.0.3

Hey, I'm seeing the same error message, and longhorn app is not showing up in the charts list while logging and monitoring apps (and others) are there (rancher 2.7.0 deployed on rke1 1.24.6 cluster). Is this related ?

For Longhorn, I don't think it's related. I can see the Longhorn app in the same setup.

Thanks for your help.
After digging in the docker image, I think my issue is related to helm charts missing in /var/lib/rancher-data/local-catalogs/v2/rancher-charts/ (I'm installing rancher with useBundledSystemChart: true
The most recent chart I can find is longhorn-100.2.3+up1.3.2.tgz, which is specific to rancher 2.6.x

I will open an issue as it's not related to this one

Same issue here, resulting in an empty page after ther chart -> install button.

Hello ^^
We are facing the same issue: level=error msg="failed to parse constraint version >= <IP_ADDRESS> < 2.8.0-0: improper constraint: >= <IP_ADDRESS> < 2.8.0-0"
We can't install or update apps from the Rancher catalog anymore.
Thanks for your help

@samjustus - Can you do a little digging and try and figure out what we might need to do here? Also, let's check the status based on dates for Q2-2023.

I got a small update, running rancher-2.7.1: recently added a new cluster k3s-v1.24.10+k3s1, which seems to be not affected, i could install charts from the apps-catalog. Previously added cluster (same k3s-version) though still show an empty page.

Created PR to fix this issue in NeuVector chart
https://github.com/rancher/charts/pull/2431

Hello ^^ We are facing the same issue: level=error msg="failed to parse constraint version >= <IP_ADDRESS> < 2.8.0-0: improper constraint: >= <IP_ADDRESS> < 2.8.0-0" We can't install or update apps from the Rancher catalog anymore.
Thanks for your help

Same here, can't install or update any apps. k3s cluster v1.24.10+k3s1

@bmdepesa @ronhorton some info to test this issue:
Looking at the issue comments above, it seems there are 2 errors reported

Unable to deploy Rancher version: 2.7.0 using helm option
Installation option (Docker install/Helm Chart):
Helm on k3s
Proxy/Cert Details:
Information about the Cluster
Kubernetes version: v1.24.8-k3s1

Other observations reported talk about apps from catalog cannot be deployed and face the "failed to parse constraint" error on rancher 2.7/2.7.1

Pass Verified in rancher v2.7-head commit ID 1712bf9

installed rancher on k3s cluster
created downstream k3s cluster
imported cluster > custom namespace
cluster imported successfully
installed rancher-monitoring-102.0.0-up40.1.2

successfully installed; no errors observed


Automated cherry pick of #10348

Cherry pick of #10348 on release-7.0.
/cc  @AshishDhama
NONE

Will try to auto merge this PR once all tests and checks are passing. This might take up to an hour.

Trying to auto merge this PR.

Pull Request successfully merged
SHA: 662cc3f469be2ab257ee3317758081a2d7f18d07


Add Connection Overrides to Twilio Client

User Story - Business Need
Add the following to Twilio callback URLs: #ct=10000&rc=5&rp=all.

[ ] Ticket is understood, and QA has been contacted (if the ticket has a QA label).

User Story(ies)
As VA Notify
I want Twilio to attempt retries and have a longer connection timeout
So that fewer callbacks fall through the cracks
Additional Info and Resources

Twilio documentation on Connection Overrides

ct is the connection timeout - set to 10 seconds (default is 5 seconds)
rc is the retry count - set to 5 retries (default is 1)
rp is the retry policy - set to all (default is ct - connection timeout essentially)

Engineering Checklist

[ ] #ct=10000&rc=5&rp=all is appended to the callback url for all outgoing Twilio requests
[ ] Wherever it is set there is a link to the documentation as a comment, since it is a sequence of characters
[ ] This value is specified as a class variable or instance member and appended to the url
Note: So it is not buried and forgotten

Acceptance Criteria

Override added to the callback url for Twilio requests.

Hey team! Please add your planning poker estimate with Zenhub @babyjunior56 @cris-oddball @EvanParish @k-macmillan @kalbfled @ldraney @nikolai-efimov

PR approved and merged, deployed to Perf.
Sent a test message from the Twilio testing service in Perf and the message was received.
That's about as far as we can go with testing. In the past 30 days, no timeouts on deliverystatus were received in dev or perf (just staging and prod) according to Twilio's error logs. Will close this ticket out and see what happens when it gets to Staging on the next release.
{
    "billing_code": null,
    "body": "Testing template, no personalisations.",
    "completed_at": "2023-11-28T21:13:30.288617Z",
    "cost_in_millicents": 0.0,
    "created_at": "2023-11-28T21:13:09.541502Z",
    "created_by_name": null,
    "email_address": null,
    "id": "6c42781b-34b1-4286-85a3-d731801fb912",
    "line_1": null,
    "line_2": null,
    "line_3": null,
    "line_4": null,
    "line_5": null,
    "line_6": null,
    "phone_number": "+1<redacted>",
    "postage": null,
    "postcode": null,
    "provider_reference": "SM98cef61fb0efa94b90166c81171f913b",
    "recipient_identifiers": [],
    "reference": null,
    "scheduled_for": null,
    "segments_count": 0,
    "sent_at": "2023-11-28T21:13:10.597641Z",
    "sent_by": "twilio",
    "sms_sender_id": "f6979d20-6b2a-4e58-907c-1f007874c86f",
    "status": "delivered",
    "status_reason": null,
    "subject": null,
    "template": {
        "id": "e0db3e86-ba17-40d0-9fc7-4ff9eb33ef72",
        "uri": "https://sandbox-api.va.gov/v2/template/e0db3e86-ba17-40d0-9fc7-4ff9eb33ef72/version/2",
        "version": 2
    },
    "type": "sms"
}


How should I save the loss value during training? model.fit has no return value

How should I save the loss value during training?
model.fit has no return value

I think you need to use Tensorflow.Keras.Engine.Sequential instead of model,
and then use predict, calculate loss from the result of predict,
calculate new gradients with Tensorflow.Gradients.GradientTape,
and finally use your keras.optamizers.[chosen optimizer].apply_gradients().
However, I am less than sure about this. I hope Haiping can answer this - possibly correcting my answer.

model.fit returns History for next release v0.100.2.

When would the new version(v0.100.2) be available on Nuget ?

My guess, it will take at least a few days, probably a few weeks:
There are many small bugs to fix at present (927, 928... 973...)


Just getting malformed characters on render();

All I get when using this library is:
�PNG  IHDR����<�PLTE���U��~5IDATX�혱��0D)�H�<�F�G�(�e ��������rE�蹑�;Q�I���X��Y90��d����G0�t��� &n�O��际��H&�t+��  ��,p�o��-&������vDri��S<�et)j�Yl��D�R�x��x�U�2����e�X�p[��Q�}-C�ʫ ��ᕀXZV�0E����Ą���v(��3113>����ǜ�LD��ie3ʪ��ڵ��ql)���ՋE&���a���5�ʝ�dv������HC�9ʙ?� Kt5\��l0����W~%��F���෴�>�L��OO�i��E��IEND�B�
What am I doing wrong? Am i missing a library? I'm not seeing any error messages...

@endroid setting "Content-Type" header to "image/png" like so: header('Content-Type: image/png'); didn't work for me. Any new updated fix?

Hi @Mark-Brightcloud when I generate a PNG and set the content header to image/png (like you say you do) I get a valid image. Can you provide a test case that fails and add it to the test suite or provide the code sample that generates the QR code so I can see if I can reproduce it? If I can reproduce the issue on this side, I can probably find a solution.


Chunk loading crash on startup with OTG / Biome Bundle, Sponge, and Farseek / Streams

Crosspost from spongeforge #2660

Hey, thanks for reporting. Need to confirm that this has been fixed with the latest versions of Streams/Farseek.

Fixed on Farseek's end :).


MMCA-4661-Remove JS supression code

We still have below warning while running the tests. Pease address as this ticket is to remove the mentioned warning
[error] WARN: Collapsing variable t [customshistoricstatementfrontend-app.js:204,52786

We still have below warning while running the tests. Pease address as this ticket is to remove the mentioned warning
[error] WARN: Collapsing variable t [customshistoricstatementfrontend-app.js:204,52786

Above comment can be ignored and it is being under discussion for the best and right course of action.

We still have below warning while running the tests. Pease address as this ticket is to remove the mentioned warning
[error] WARN: Collapsing variable t [customshistoricstatementfrontend-app.js:204,52786

Above comment can be ignored and it is being under discussion for the best and right course of action.

Resolving


44194: Biologics login modal is double encoding HTML error messages

Rationale
Passing server-generated HTML error messages is not a great idea, as seen in #44194
Changes

Eliminate FormattedError usages and class
Introduce LabKeyErrorWithLink class to convey additional advice text and link
Pass adviceText and adviceHref in the JSON error object
login.js: encode the message and add a link if adviceText and adviceHref are present

We still need to teach the app login pages about adviceText and adviceHref (biologics, sample manager, CDS?).
I opted to provide optional advice text and href, and force the client to create a proper <a> tag. This means the whole advice text becomes a link, whereas we previously linkified just a portion of that text. A more flexible solution would be to generate HTML server side and pass it to the client as adviceHtml. This is not strongly typed like HtmlString but the name makes it fairly obvious. We have exactly three error messages that use this mechanism, so the less flexible approach seems good enough.


Nutrition tab: calories always zero

In nutrition tab, calories are always shown as zero on my device. All products affected. "Preferred energy unit" is set to kcal in the settings. Language English, same issue in German.
OFF Android App 3.0.8
LG G7 ThinQ, Android 8.0.0. Stock ROM.

Hey, can you provide the barcode you're scanning ?


Offline.js not working on safari

I am using Jquery file upload plugin to upload files to s3 in my rails application.
While during a file upload if internet connection is lost and then restored , the uploading part is resumed on google chrome automatically but it fails on safari.
I am using offline.js to detect internet connection status , but it fails to resume failed Ajax requests made while connection was down.
Please help me with this

@TarunG96 Did you manage to solve this problem?