Evosax - Augmented Random Search

Hi there 🤗 - I am opening a first PR, which adds Augmented Random Search (Mania et al., 2018) to evojax. The implementation wraps evosax's.

Reference: Mania et al. (2018)
evosax Source Code: https://github.com/RobertTLange/evosax/blob/main/evosax/strategies/ars.py

There are a couple general considerations:

evosax strategies by default minimize the objective, while all evojax tasks maximize. Hence, the FitnessShaper has to transform the "raw" fitness.
In order to easier access the individual strategies, I added a Strategies dictionary. This comes in handy when trying to benchmark multiple strategies.
evosax is now a required dependency, which in turn requires newer versions of  jax and jaxlib. I am not sure if this breaks anything. So far when running the benchmarks it did not.

I have also created a mini-repository for running the benchmarks, storing logs and configuration files. Maybe this can be of general interest? I am planning to add a mle-hyperopt parameter search pipeline. You can find the ARS logs here and this is the benchmarking summary for ARS:

Benchmarks
Parameters
Results

CartPole (easy)
900 (max_iter=1000)
Link
902.107

CartPole (hard)
600 (max_iter=1000)
Link
666.6442

Waterworld
6 (max_iter=500)
Link
6.1300

Waterworld (MA)
2 (max_iter=2000)
Link
1.4831

Brax Ant
3000 (max_iter=300)
Link
3298.9746

MNIST
90.0 (max_iter=2000)
Link
0.9610

Update: I added hyperparameter search utilities and coarsely grid searched the initiatl learning rate and standard deviation. Here are some results for the cartpole and mnist taks:

Cartpole-Easy
Cartpole-Hard
MNIST

Hey @RobertTLange , Thanks for the detailed PR!
I have merged it with some quick adds:

quick tests, and
putting evosax as the optional ([extra]) dependency of EvoJAX.

BTW, It seems that evosax may have issues under Python 3.6, which you may want to have a look at (although it does not affect the rest of EvoJAX for now.) Please refer to

The output of CI workflow https://github.com/google/evojax/runs/5268178005 , and
The output of my local smoke testing:

Python 3.6.13 |Anaconda, Inc.| (default, Feb 23 2021, 12:58:59)
[GCC Clang 10.0.0 ] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import evosax
>>> from evosax import Augmented_RS, FitnessShaper
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: cannot import name 'Augmented_RS'
>>>


datepicker not responding on Ionic?

I have had the date picker working in the past. I did a clean install on my machine and now it is completely unresponsive, as if it was not installed.
Here are some things I've done:

I ran GapDebug to look for obvious errors.
I upgraded to Cordova 4.3. Still unresponsive
Uninstalled all platforms and plugins. Reinstalled. Still unresponsive
Installed with cordova plugin add https://github.com/VitaliiBlagodir/cordova-plugin-datepicker.git

Here is my current platform:
OS: Mac OS X Yosemite
Node Version: v0.12.0
Cordova CLI: 4.1.2
Ionic CLI Version: 1.3.19
Xcode version: Xcode 6.1.1 Build version 6A2008a
ios-sim version: 3.1.1
ios-deploy version: 1.5.0

Any thoughts?

Hi, same problem using it in form element , work great outside...

You might look at my comment on #77.  I was able to get it working if I made sure to pass a date option.

It turns out this was related to me needing to upgrade to the new cordova
plugin names. Cordova switched to a dash rather than dot syntax. Once I
updated to the newer plugins the datepicker started working again.
I also needed to do a clean platform install to make this work.
On Friday, May 8, 2015, Geoffrey Dagley<EMAIL_ADDRESS>wrote:

You might look at my comment on #77
https://github.com/VitaliiBlagodir/cordova-plugin-datepicker/issues/77.
I was able to get it working if I made sure to pass a date option.
—
Reply to this email directly or view it on GitHub
https://github.com/VitaliiBlagodir/cordova-plugin-datepicker/issues/75#issuecomment-100220317
.


Most tests fail with Ruby 2.7.0 on macOS

Hi,
I noticed a few problems with ceedling which I wanted to help sort out, but at least on macOS and ruby 2.7.0, most tests are failing, see below:
Finished in 1 minute 7.1 seconds (files took 0.50836 seconds to load)
221 examples, 113 failures, 8 pending

Failed examples:

rspec ./spec/gcov/gcov_deployment_spec.rb:27 # Ceedling Gcov basic operations
rspec ./spec/gcov/gcov_deployment_spec.rb:28 # Ceedling Gcov basic operations
rspec ./spec/gcov/gcov_deployment_spec.rb:29 # Ceedling Gcov basic operations
rspec ./spec/gcov/gcov_deployment_spec.rb:30 # Ceedling Gcov basic operations
rspec ./spec/gcov/gcov_deployment_spec.rb:31 # Ceedling Gcov basic operations
rspec ./spec/gcov/gcov_deployment_spec.rb:32 # Ceedling Gcov basic operations
rspec ./spec/gcov/gcov_deployment_spec.rb:33 # Ceedling Gcov basic operations
rspec ./spec/gcov/gcov_deployment_spec.rb:46 # Ceedling Gcov command: `ceedling example [example]` temp_sensor should be testable
rspec ./spec/system/deployment_spec.rb:25 # Ceedling deployed in a project's `vendor` directory.
rspec ./spec/system/deployment_spec.rb:26 # Ceedling deployed in a project's `vendor` directory.
rspec ./spec/system/deployment_spec.rb:27 # Ceedling deployed in a project's `vendor` directory.
rspec ./spec/system/deployment_spec.rb:28 # Ceedling deployed in a project's `vendor` directory. should match 0
rspec ./spec/system/deployment_spec.rb:29 # Ceedling deployed in a project's `vendor` directory.
rspec ./spec/system/deployment_spec.rb:30 # Ceedling deployed in a project's `vendor` directory.
rspec ./spec/system/deployment_spec.rb:31 # Ceedling deployed in a project's `vendor` directory.
rspec ./spec/system/deployment_spec.rb:32 # Ceedling deployed in a project's `vendor` directory.
rspec ./spec/system/deployment_spec.rb:33 # Ceedling deployed in a project's `vendor` directory.
rspec ./spec/system/deployment_spec.rb:34 # Ceedling deployed in a project's `vendor` directory.
rspec ./spec/system/deployment_spec.rb:35 # Ceedling deployed in a project's `vendor` directory.
rspec ./spec/system/deployment_spec.rb:36 # Ceedling deployed in a project's `vendor` directory.
rspec ./spec/system/deployment_spec.rb:37 # Ceedling deployed in a project's `vendor` directory.
rspec ./spec/system/deployment_spec.rb:38 # Ceedling deployed in a project's `vendor` directory.
rspec ./spec/system/deployment_spec.rb:39 # Ceedling deployed in a project's `vendor` directory.
rspec ./spec/system/deployment_spec.rb:40 # Ceedling deployed in a project's `vendor` directory.
rspec ./spec/system/deployment_spec.rb:41 # Ceedling deployed in a project's `vendor` directory.
rspec ./spec/system/deployment_spec.rb:42 # Ceedling deployed in a project's `vendor` directory.
rspec ./spec/system/deployment_spec.rb:43 # Ceedling deployed in a project's `vendor` directory.
rspec ./spec/system/deployment_spec.rb:44 # Ceedling deployed in a project's `vendor` directory.
rspec ./spec/system/deployment_spec.rb:45 # Ceedling deployed in a project's `vendor` directory.
rspec ./spec/system/deployment_spec.rb:55 # Ceedling deployed in a project's `vendor` directory with gitignore.
rspec ./spec/system/deployment_spec.rb:56 # Ceedling deployed in a project's `vendor` directory with gitignore.
rspec ./spec/system/deployment_spec.rb:57 # Ceedling deployed in a project's `vendor` directory with gitignore.
rspec ./spec/system/deployment_spec.rb:58 # Ceedling deployed in a project's `vendor` directory with gitignore.
rspec ./spec/system/deployment_spec.rb:59 # Ceedling deployed in a project's `vendor` directory with gitignore.
rspec ./spec/system/deployment_spec.rb:60 # Ceedling deployed in a project's `vendor` directory with gitignore.
rspec ./spec/system/deployment_spec.rb:72 # Ceedling deployed in a project's `vendor` directory without docs.
rspec ./spec/system/deployment_spec.rb:73 # Ceedling deployed in a project's `vendor` directory without docs.
rspec ./spec/system/deployment_spec.rb:74 # Ceedling deployed in a project's `vendor` directory without docs.
rspec ./spec/system/deployment_spec.rb:75 # Ceedling deployed in a project's `vendor` directory without docs. should match 0
rspec ./spec/system/deployment_spec.rb:76 # Ceedling deployed in a project's `vendor` directory without docs.
rspec ./spec/system/deployment_spec.rb:77 # Ceedling deployed in a project's `vendor` directory without docs.
rspec ./spec/system/deployment_spec.rb:78 # Ceedling deployed in a project's `vendor` directory without docs.
rspec ./spec/system/deployment_spec.rb:79 # Ceedling deployed in a project's `vendor` directory without docs.
rspec ./spec/system/deployment_spec.rb:80 # Ceedling deployed in a project's `vendor` directory without docs.
rspec ./spec/system/deployment_spec.rb:81 # Ceedling deployed in a project's `vendor` directory without docs.
rspec ./spec/system/deployment_spec.rb:82 # Ceedling deployed in a project's `vendor` directory without docs.
rspec ./spec/system/deployment_spec.rb:83 # Ceedling deployed in a project's `vendor` directory without docs.
rspec ./spec/system/deployment_spec.rb:84 # Ceedling deployed in a project's `vendor` directory without docs.
rspec ./spec/system/deployment_spec.rb:85 # Ceedling deployed in a project's `vendor` directory without docs.
rspec ./spec/system/deployment_spec.rb:86 # Ceedling deployed in a project's `vendor` directory without docs.
rspec ./spec/system/deployment_spec.rb:87 # Ceedling deployed in a project's `vendor` directory without docs.
rspec ./spec/system/deployment_spec.rb:88 # Ceedling deployed in a project's `vendor` directory without docs.
rspec ./spec/system/deployment_spec.rb:89 # Ceedling deployed in a project's `vendor` directory without docs.
rspec ./spec/system/deployment_spec.rb:90 # Ceedling deployed in a project's `vendor` directory without docs.
rspec ./spec/system/deployment_spec.rb:100 # Ceedling ugrade a project's `vendor` directory
rspec ./spec/system/deployment_spec.rb:101 # Ceedling ugrade a project's `vendor` directory
rspec ./spec/system/deployment_spec.rb:102 # Ceedling ugrade a project's `vendor` directory
rspec ./spec/system/deployment_spec.rb:103 # Ceedling ugrade a project's `vendor` directory should match 0
rspec ./spec/system/deployment_spec.rb:104 # Ceedling ugrade a project's `vendor` directory
rspec ./spec/system/deployment_spec.rb:105 # Ceedling ugrade a project's `vendor` directory
rspec ./spec/system/deployment_spec.rb:106 # Ceedling ugrade a project's `vendor` directory
rspec ./spec/system/deployment_spec.rb:107 # Ceedling ugrade a project's `vendor` directory
rspec ./spec/system/deployment_spec.rb:108 # Ceedling ugrade a project's `vendor` directory
rspec ./spec/system/deployment_spec.rb:109 # Ceedling ugrade a project's `vendor` directory
rspec ./spec/system/deployment_spec.rb:110 # Ceedling ugrade a project's `vendor` directory
rspec ./spec/system/deployment_spec.rb:111 # Ceedling ugrade a project's `vendor` directory
rspec ./spec/system/deployment_spec.rb:112 # Ceedling ugrade a project's `vendor` directory
rspec ./spec/system/deployment_spec.rb:113 # Ceedling ugrade a project's `vendor` directory
rspec ./spec/system/deployment_spec.rb:114 # Ceedling ugrade a project's `vendor` directory
rspec ./spec/system/deployment_spec.rb:115 # Ceedling ugrade a project's `vendor` directory
rspec ./spec/system/deployment_spec.rb:116 # Ceedling ugrade a project's `vendor` directory
rspec ./spec/system/deployment_spec.rb:117 # Ceedling ugrade a project's `vendor` directory
rspec ./spec/system/deployment_spec.rb:118 # Ceedling ugrade a project's `vendor` directory
rspec ./spec/system/deployment_spec.rb:119 # Ceedling ugrade a project's `vendor` directory
rspec ./spec/system/deployment_spec.rb:121 # Ceedling ugrade a project's `vendor` directory should match 0
rspec ./spec/system/deployment_spec.rb:122 # Ceedling ugrade a project's `vendor` directory
rspec ./spec/system/deployment_spec.rb:123 # Ceedling ugrade a project's `vendor` directory
rspec ./spec/system/deployment_spec.rb:124 # Ceedling ugrade a project's `vendor` directory should match 0
rspec ./spec/system/deployment_spec.rb:125 # Ceedling ugrade a project's `vendor` directory
rspec ./spec/system/deployment_spec.rb:126 # Ceedling ugrade a project's `vendor` directory
rspec ./spec/system/deployment_spec.rb:127 # Ceedling ugrade a project's `vendor` directory
rspec ./spec/system/deployment_spec.rb:128 # Ceedling ugrade a project's `vendor` directory
rspec ./spec/system/deployment_spec.rb:129 # Ceedling ugrade a project's `vendor` directory
rspec ./spec/system/deployment_spec.rb:130 # Ceedling ugrade a project's `vendor` directory
rspec ./spec/system/deployment_spec.rb:131 # Ceedling ugrade a project's `vendor` directory
rspec ./spec/system/deployment_spec.rb:132 # Ceedling ugrade a project's `vendor` directory
rspec ./spec/system/deployment_spec.rb:133 # Ceedling ugrade a project's `vendor` directory
rspec ./spec/system/deployment_spec.rb:134 # Ceedling ugrade a project's `vendor` directory
rspec ./spec/system/deployment_spec.rb:135 # Ceedling ugrade a project's `vendor` directory
rspec ./spec/system/deployment_spec.rb:136 # Ceedling ugrade a project's `vendor` directory
rspec ./spec/system/deployment_spec.rb:137 # Ceedling ugrade a project's `vendor` directory
rspec ./spec/system/deployment_spec.rb:138 # Ceedling ugrade a project's `vendor` directory
rspec ./spec/system/deployment_spec.rb:139 # Ceedling ugrade a project's `vendor` directory
rspec ./spec/system/deployment_spec.rb:140 # Ceedling ugrade a project's `vendor` directory
rspec ./spec/system/deployment_spec.rb:150 # Ceedling deployed as a gem
rspec ./spec/system/deployment_spec.rb:151 # Ceedling deployed as a gem
rspec ./spec/system/deployment_spec.rb:152 # Ceedling deployed as a gem should match 0
rspec ./spec/system/deployment_spec.rb:153 # Ceedling deployed as a gem
rspec ./spec/system/deployment_spec.rb:154 # Ceedling deployed as a gem
rspec ./spec/system/deployment_spec.rb:155 # Ceedling deployed as a gem
rspec ./spec/system/deployment_spec.rb:156 # Ceedling deployed as a gem
rspec ./spec/system/deployment_spec.rb:157 # Ceedling deployed as a gem
rspec ./spec/system/deployment_spec.rb:158 # Ceedling deployed as a gem
rspec ./spec/system/deployment_spec.rb:159 # Ceedling deployed as a gem
rspec ./spec/system/deployment_spec.rb:160 # Ceedling deployed as a gem
rspec ./spec/system/deployment_spec.rb:161 # Ceedling deployed as a gem
rspec ./spec/system/deployment_spec.rb:162 # Ceedling deployed as a gem
rspec ./spec/system/deployment_spec.rb:163 # Ceedling deployed as a gem
rspec ./spec/system/deployment_spec.rb:164 # Ceedling deployed as a gem
rspec ./spec/system/deployment_spec.rb:165 # Ceedling deployed as a gem
rspec ./spec/system/deployment_spec.rb:166 # Ceedling deployed as a gem
rspec ./spec/system/deployment_spec.rb:176 # Ceedling command: `ceedling examples` should list out all the examples
rspec ./spec/system/deployment_spec.rb:191 # Ceedling command: `ceedling example [example]` temp_sensor should be testable

/usr/local/Cellar/ruby/2.7.0/bin/ruby -I/usr/local/lib/ruby/gems/2.7.0/gems/rspec-core-3.8.0/lib:/usr/local/lib/ruby/gems/2.7.0/gems/rspec-support-3.8.0/lib /usr/local/lib/ruby/gems/2.7.0/gems/rspec-core-3.8.0/exe/rspec --pattern spec/\*\*/\*_spec.rb failed

I can help debug this, but any hints would be appreciated :-) There's a message showing up very frequently:
There was an error while loading `ceedling.gemspec`: uninitialized constant Ceedling::Version::CEEDLING_VENDOR. Bundler cannot continue.

And here's a run of gcov deployment tests only:
> rspec spec/gcov/gcov_deployment_spec.rb
[DEPRECATED] The `--path` flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use `bundle config set path '/var/folders/px/646w_0d17517xz52r_nvzg540000gn/T/d20200313-48849-15wtw4d/gems'`, and stop using this flag

[!] There was an error while loading `ceedling.gemspec`: uninitialized constant Ceedling::Version::CEEDLING_VENDOR. Bundler cannot continue.

 #  from /Users/felipebalbi/workspace/ceedling/ceedling.gemspec:3
 #  -------------------------------------------
 #  $LOAD_PATH << File.expand_path(File.join(File.dirname(__FILE__), 'lib'))
 >  require "ceedling/version"
 #  require 'date'
 #  -------------------------------------------
FFFFFFFF

Failures:

  1) Ceedling Gcov basic operations
     Failure/Error:
             Dir.chdir @proj_name do
               FileUtils.cp test_asset_path("project_with_guts_gcov.yml"), "project.yml"
               FileUtils.cp test_asset_path("example_file.h"), 'src/'
               FileUtils.cp test_asset_path("example_file.c"), 'src/'
               FileUtils.cp test_asset_path("test_example_file_success.c"), 'test/'

               output = `bundle exec ruby -S ceedling gcov:all`
               expect($?.exitstatus).to match(0) # Since a test either pass or are ignored, we return success here
               expect(output).to match(/TESTED:\s+\d/)
               expect(output).to match(/PASSED:\s+\d/)

     Errno::ENOENT:
       No such file or directory @ dir_chdir - fake_project
     # ./spec/gcov/gcov_test_cases_spec.rb:12:in `chdir'
     # ./spec/gcov/gcov_test_cases_spec.rb:12:in `block in can_test_projects_with_gcov_with_success'
     # ./spec/spec_system_helper.rb:162:in `block (2 levels) in with_context'
     # ./spec/spec_system_helper.rb:193:in `with_constrained_env'
     # ./spec/spec_system_helper.rb:158:in `block in with_context'
     # ./spec/spec_system_helper.rb:157:in `chdir'
     # ./spec/spec_system_helper.rb:157:in `with_context'
     # ./spec/gcov/gcov_test_cases_spec.rb:11:in `can_test_projects_with_gcov_with_success'
     # ./spec/gcov/gcov_deployment_spec.rb:27:in `block (4 levels) in <top (required)>'

  2) Ceedling Gcov basic operations
     Failure/Error:
             Dir.chdir @proj_name do
               FileUtils.cp test_asset_path("project_with_guts_gcov.yml"), "project.yml"
               FileUtils.cp test_asset_path("example_file.h"), 'src/'
               FileUtils.cp test_asset_path("example_file.c"), 'src/'
               FileUtils.cp test_asset_path("test_example_file.c"), 'test/'

               output = `bundle exec ruby -S ceedling gcov:all 2>&1`
               expect($?.exitstatus).to match(1) # Since a test fails, we return error here
               expect(output).to match(/TESTED:\s+\d/)
               expect(output).to match(/PASSED:\s+\d/)

     Errno::ENOENT:
       No such file or directory @ dir_chdir - fake_project
     # ./spec/gcov/gcov_test_cases_spec.rb:30:in `chdir'
     # ./spec/gcov/gcov_test_cases_spec.rb:30:in `block in can_test_projects_with_gcov_with_fail'
     # ./spec/spec_system_helper.rb:162:in `block (2 levels) in with_context'
     # ./spec/spec_system_helper.rb:193:in `with_constrained_env'
     # ./spec/spec_system_helper.rb:158:in `block in with_context'
     # ./spec/spec_system_helper.rb:157:in `chdir'
     # ./spec/spec_system_helper.rb:157:in `with_context'
     # ./spec/gcov/gcov_test_cases_spec.rb:29:in `can_test_projects_with_gcov_with_fail'
     # ./spec/gcov/gcov_deployment_spec.rb:28:in `block (4 levels) in <top (required)>'

  3) Ceedling Gcov basic operations
     Failure/Error:
             Dir.chdir @proj_name do
               FileUtils.cp test_asset_path("project_with_guts_gcov_abortonuncovered.yml"), "project.yml"
               FileUtils.cp test_asset_path("example_file.h"), 'src/'
               FileUtils.cp test_asset_path("example_file.c"), 'src/'
               FileUtils.cp test_asset_path("uncovered_example_file.c"), 'src/'
               FileUtils.cp test_asset_path("test_example_file_success.c"), 'test/'

               output = `bundle exec ruby -S ceedling gcov:all 2>&1`
               expect($?.exitstatus).to match(255) # Since a test fails, we return error here
               expect(output).to match(/TESTED:\s+\d/)

     Errno::ENOENT:
       No such file or directory @ dir_chdir - fake_project
     # ./spec/gcov/gcov_test_cases_spec.rb:48:in `chdir'
     # ./spec/gcov/gcov_test_cases_spec.rb:48:in `block in can_test_projects_with_gcov_with_fail_because_of_uncovered_files'
     # ./spec/spec_system_helper.rb:162:in `block (2 levels) in with_context'
     # ./spec/spec_system_helper.rb:193:in `with_constrained_env'
     # ./spec/spec_system_helper.rb:158:in `block in with_context'
     # ./spec/spec_system_helper.rb:157:in `chdir'
     # ./spec/spec_system_helper.rb:157:in `with_context'
     # ./spec/gcov/gcov_test_cases_spec.rb:47:in `can_test_projects_with_gcov_with_fail_because_of_uncovered_files'
     # ./spec/gcov/gcov_deployment_spec.rb:29:in `block (4 levels) in <top (required)>'

  4) Ceedling Gcov basic operations
     Failure/Error:
             Dir.chdir @proj_name do
               FileUtils.cp test_asset_path("project_with_guts_gcov_abortonuncovered.yml"), "project.yml"
               FileUtils.cp test_asset_path("example_file.h"), "src/"
               FileUtils.cp test_asset_path("example_file.c"), "src/"
               FileUtils.cp test_asset_path("uncovered_example_file.c"), "src/foo_file.c" # "src/foo_file.c" is in the ignore uncovered list
               FileUtils.cp test_asset_path("test_example_file_success.c"), "test/"

               output = `bundle exec ruby -S ceedling gcov:all 2>&1`
               expect($?.exitstatus).to match(0)
               expect(output).to match(/TESTED:\s+\d/)

     Errno::ENOENT:
       No such file or directory @ dir_chdir - fake_project
     # ./spec/gcov/gcov_test_cases_spec.rb:67:in `chdir'
     # ./spec/gcov/gcov_test_cases_spec.rb:67:in `block in can_test_projects_with_gcov_with_success_because_of_ignore_uncovered_list'
     # ./spec/spec_system_helper.rb:162:in `block (2 levels) in with_context'
     # ./spec/spec_system_helper.rb:193:in `with_constrained_env'
     # ./spec/spec_system_helper.rb:158:in `block in with_context'
     # ./spec/spec_system_helper.rb:157:in `chdir'
     # ./spec/spec_system_helper.rb:157:in `with_context'
     # ./spec/gcov/gcov_test_cases_spec.rb:66:in `can_test_projects_with_gcov_with_success_because_of_ignore_uncovered_list'
     # ./spec/gcov/gcov_deployment_spec.rb:30:in `block (4 levels) in <top (required)>'

  5) Ceedling Gcov basic operations
     Failure/Error:
             Dir.chdir @proj_name do
               FileUtils.cp test_asset_path("project_with_guts_gcov.yml"), "project.yml"
               FileUtils.cp test_asset_path("example_file.h"), 'src/'
               FileUtils.cp test_asset_path("example_file.c"), 'src/'
               FileUtils.cp test_asset_path("test_example_file_boom.c"), 'test/'

               output = `bundle exec ruby -S ceedling gcov:all 2>&1`
               expect($?.exitstatus).to match(1) # Since a test explodes, we return error here
               expect(output).to match(/ERROR: Ceedling Failed/)
             end

     Errno::ENOENT:
       No such file or directory @ dir_chdir - fake_project
     # ./spec/gcov/gcov_test_cases_spec.rb:86:in `chdir'
     # ./spec/gcov/gcov_test_cases_spec.rb:86:in `block in can_test_projects_with_gcov_with_compile_error'
     # ./spec/spec_system_helper.rb:162:in `block (2 levels) in with_context'
     # ./spec/spec_system_helper.rb:193:in `with_constrained_env'
     # ./spec/spec_system_helper.rb:158:in `block in with_context'
     # ./spec/spec_system_helper.rb:157:in `chdir'
     # ./spec/spec_system_helper.rb:157:in `with_context'
     # ./spec/gcov/gcov_test_cases_spec.rb:85:in `can_test_projects_with_gcov_with_compile_error'
     # ./spec/gcov/gcov_deployment_spec.rb:31:in `block (4 levels) in <top (required)>'

  6) Ceedling Gcov basic operations
     Failure/Error:
       Dir.chdir @proj_name do
         FileUtils.cp test_asset_path("project_with_guts_gcov.yml"), "project.yml"
         output = `bundle exec ruby -S ceedling help`
         expect($?.exitstatus).to match(0)
         expect(output).to match(/ceedling gcov:\*/i)
         expect(output).to match(/ceedling gcov:all/i)
         expect(output).to match(/ceedling gcov:delta/i)
         expect(output).to match(/ceedling utils:gcov/i)
       end

     Errno::ENOENT:
       No such file or directory @ dir_chdir - fake_project
     # ./spec/gcov/gcov_test_cases_spec.rb:101:in `chdir'
     # ./spec/gcov/gcov_test_cases_spec.rb:101:in `block in can_fetch_project_help_for_gcov'
     # ./spec/spec_system_helper.rb:162:in `block (2 levels) in with_context'
     # ./spec/spec_system_helper.rb:193:in `with_constrained_env'
     # ./spec/spec_system_helper.rb:158:in `block in with_context'
     # ./spec/spec_system_helper.rb:157:in `chdir'
     # ./spec/spec_system_helper.rb:157:in `with_context'
     # ./spec/gcov/gcov_test_cases_spec.rb:100:in `can_fetch_project_help_for_gcov'
     # ./spec/gcov/gcov_deployment_spec.rb:32:in `block (4 levels) in <top (required)>'

  7) Ceedling Gcov basic operations
     Failure/Error:
             Dir.chdir @proj_name do
               FileUtils.cp test_asset_path("project_with_guts_gcov.yml"), "project.yml"
               FileUtils.cp test_asset_path("example_file.h"), 'src/'
               FileUtils.cp test_asset_path("example_file.c"), 'src/'
               FileUtils.cp test_asset_path("test_example_file_success.c"), 'test/'

               output = `bundle exec ruby -S ceedling gcov:all`
               output = `bundle exec ruby -S ceedling utils:gcov`
               expect(output).to match(/Creating gcov results report\(s\) in 'build\/artifacts\/gcov'\.\.\. Done/)
               expect(File.exists?('build/artifacts/gcov/GcovCoverageResults.html')).to eq true

     Errno::ENOENT:
       No such file or directory @ dir_chdir - fake_project
     # ./spec/gcov/gcov_test_cases_spec.rb:115:in `chdir'
     # ./spec/gcov/gcov_test_cases_spec.rb:115:in `block in can_create_html_report'
     # ./spec/spec_system_helper.rb:162:in `block (2 levels) in with_context'
     # ./spec/spec_system_helper.rb:193:in `with_constrained_env'
     # ./spec/spec_system_helper.rb:158:in `block in with_context'
     # ./spec/spec_system_helper.rb:157:in `chdir'
     # ./spec/spec_system_helper.rb:157:in `with_context'
     # ./spec/gcov/gcov_test_cases_spec.rb:114:in `can_create_html_report'
     # ./spec/gcov/gcov_deployment_spec.rb:33:in `block (4 levels) in <top (required)>'

  8) Ceedling Gcov command: `ceedling example [example]` temp_sensor should be testable
     Failure/Error: expect(output).to match(/created!/)

       expected "/usr/local/opt/ruby/bin/ruby: No such file or directory -- ceedling (LoadError)\n" to match /created!/
       Diff:
       @@ -1,2 +1,2 @@
       -/created!/
       +/usr/local/opt/ruby/bin/ruby: No such file or directory -- ceedling (LoadError)

     # ./spec/gcov/gcov_deployment_spec.rb:42:in `block (6 levels) in <top (required)>'
     # ./spec/spec_system_helper.rb:162:in `block (2 levels) in with_context'
     # ./spec/spec_system_helper.rb:193:in `with_constrained_env'
     # ./spec/spec_system_helper.rb:158:in `block in with_context'
     # ./spec/spec_system_helper.rb:157:in `chdir'
     # ./spec/spec_system_helper.rb:157:in `with_context'
     # ./spec/gcov/gcov_deployment_spec.rb:40:in `block (5 levels) in <top (required)>'

Finished in 4.64 seconds (files took 0.40579 seconds to load)
8 examples, 8 failures

Failed examples:

rspec ./spec/gcov/gcov_deployment_spec.rb:27 # Ceedling Gcov basic operations
rspec ./spec/gcov/gcov_deployment_spec.rb:28 # Ceedling Gcov basic operations
rspec ./spec/gcov/gcov_deployment_spec.rb:29 # Ceedling Gcov basic operations
rspec ./spec/gcov/gcov_deployment_spec.rb:30 # Ceedling Gcov basic operations
rspec ./spec/gcov/gcov_deployment_spec.rb:31 # Ceedling Gcov basic operations
rspec ./spec/gcov/gcov_deployment_spec.rb:32 # Ceedling Gcov basic operations
rspec ./spec/gcov/gcov_deployment_spec.rb:33 # Ceedling Gcov basic operations
rspec ./spec/gcov/gcov_deployment_spec.rb:46 # Ceedling Gcov command: `ceedling example [example]` temp_sensor should be testable

How are you running the tests and do you have gcov installed for  the gcov specific tests?
I'd like to take the first steps of this by adding ruby 2.7 to the matrix to confirm it's not a ruby comparability issue, but that probably won't be for a few more days.

Running tests with bundle exec rake. gcov is installed. The only tests that fail are gcov and system. I think the problem is related to trying to to install the gem in a temporary directory.
There's also an annoying error about not having CEEDLING_VENDOR constant initialised. Seems like it's looking for it in the wrong place:
[!] There was an error while loading `ceedling.gemspec`: uninitialized constant Ceedling::Version::CEEDLING_VENDOR. Bundler cannot continue.

 #  from /Users/felipebalbi/workspace/ceedling/ceedling.gemspec:3
 #  -------------------------------------------
 #  $LOAD_PATH << File.expand_path(File.join(File.dirname(__FILE__), 'lib'))
 >  require "ceedling/version"
 #  require 'date'
 #  -------------------------------------------

gcov:
> gcov --version
Apple LLVM version 11.0.0 (clang-1<IP_ADDRESS>)
  Optimized build.
  Default target: x86_64-apple-darwin19.3.0
  Host CPU: skylake

ruby:
> ruby --version
ruby 2.7.0p0 (2019-12-25 revision 647ee6f091) [x86_64-darwin19]

If I ignore the subdirectories, everything works fine:
> find spec -type f -maxdepth 1 | xargs rspec
...........*........*..........**.............****..........................................................

Pending: (Failures listed here are expected and do not affect your suite's status)

  1) FileFinderHelper#find_file_in_collection handles duplicate files
     # Temporarily skipped with xit
     # ./spec/file_finder_helper_spec.rb:26

  2) uncategorized set_verbosity needs to be defined
     # Temporarily skipped with xit
     # ./spec/uncatagorized_specs_spec.rb:6

  3) ConfiguratorBuilder is scary
     # Temporarily skipped with xit
     # ./spec/configurator_builder_spec.rb:6

  4) ConfiguratorHelper doesn't exist...
     # Temporarily skipped with xit
     # ./spec/configurator_helper_spec.rb:4

  5) Configurator#standardize_paths should standardize [:project][:build_root]
     # Temporarily skipped with xit
     # ./spec/configurator_spec.rb:5

  6) Configurator#standardize_paths should standardize [:paths]
     # Temporarily skipped with xit
     # ./spec/configurator_spec.rb:6

  7) Configurator#standardize_paths should standardize [:files]
     # Temporarily skipped with xit
     # ./spec/configurator_spec.rb:7

  8) Configurator#standardize_paths should standardize [:tools]
     # Temporarily skipped with xit
     # ./spec/configurator_spec.rb:8

Finished in 0.93279 seconds (files took 1.16 seconds to load)
108 examples, 0 failures, 8 pending

I ran rspec --bisect and it confirms what I mentioned before:
Bisect complete! Reduced necessary non-failing examples from 108 to 0 in 47.5 seconds.

The minimal reproduction command is:
  rspec ./spec/gcov/gcov_deployment_spec.rb[1:1:1:1,1:1:1:2,1:1:1:3,1:1:1:4,1:1:1:5,1:1:1:6,1:1:1:7,1:1:2:1:1] ./spec/system/deployment_spec.rb[1:1:1,1:1:2,1:1:3,1:1:4,1:1:5,1:1:6,1:1:7,1:1:8,1:1:9,1:1:10,1:1:11,1:1:12,1:1:13,1:1:14,1:1:15,1:1:16,1:1:17,1:1:18,1:1:19,1:1:20,1:1:21,1:2:1,1:2:2,1:2:3,1:2:4,1:2:5,1:2:6,1:3:1,1:3:2,1:3:3,1:3:4,1:3:5,1:3:6,1:3:7,1:3:8,1:3:9,1:3:10,1:3:11,1:3:12,1:3:13,1:3:14,1:3:15,1:3:16,1:3:17,1:3:18,1:3:19,1:4:1,1:4:2,1:4:3,1:4:4,1:4:5,1:4:6,1:4:7,1:4:8,1:4:9,1:4:10,1:4:11,1:4:12,1:4:13,1:4:14,1:4:15,1:4:16,1:4:17,1:4:18,1:4:19,1:4:20,1:4:21,1:4:22,1:4:23,1:4:24,1:4:25,1:4:26,1:4:27,1:4:28,1:4:29,1:4:30,1:4:31,1:4:32,1:4:33,1:4:34,1:4:35,1:4:36,1:4:37,1:4:38,1:4:39,1:4:40,1:5:1,1:5:2,1:5:3,1:5:4,1:5:5,1:5:6,1:5:7,1:5:8,1:5:9,1:5:10,1:5:11,1:5:12,1:5:13,1:5:14,1:5:15,1:5:16,1:5:17,1:6:1,1:7:1:1]

I tested this same thing on Arch Linux and got the same results. So it's either ruby version (2.7.0p0) or bundler version (2.1.4) causing problems.

https://travis-ci.org/github/art-of-dom/Ceedling/jobs/662478708?utm_medium=notification&utm_source=github_status
This quick CI test shows that 2.7 has more warnings running the tests, but they do all pass the CI. I'm currently working on restoring the OSX CI then I think I'll try to clean up the warnings which may help your case.

Interesting. I have this failing on both macOS and Arch Linux. Ruby and Bundle versions match.
/me reads TravisCI output
There's a git submodule update --init --recursive running on TravisCI which is not documented on README.md. After running that, I get all tests passing with the same warnings as TravisCI. I guess that should be patched.


Add Mutual-NN Description

Adding section for using a mutual-NN rather than a k-NN with UMAP based on this paper: https://arxiv.org/abs/2108.05525

Thanks!

Is this documentation out of date? I'd like to do some experiments with mutual-NN and would potentially be interested in helping make this a better supported option with sensible defaults.

@dribnet I think there is definitely more that could be said about this, and relative support for it. Right now a lot of this is essentially handled with the set_op_mix_ratio parameter which is not really well documented at all (or even that well named for anyone not familiar with the internals). I'd certainly welcome any suggestions or additions you have.


[PATCH] Create DEBIAN directory for dpkg-shlibdeps

dpkg-shlibdeps searches for the DEBIAN directory in order to
resolve $ORIGIN in the rpath to a directory. We need to
create the DEBIAN directory for this to work.
Fixes 12431

Cc: @do-m-en

Thanks, patch applied with some additions:
https://cmake.org/gitweb?p=cmake.git;a=commit;h=b8263a2


terraform import kibana_user_space doesn't import space name

Assume we have an existing kibana space:
{
  "id": "foo",
  "name": "Foo Space",
  "initials": "FO"
}

and we have a tf file:
resource "kibana_user_space" "foo" {
  uid = "foo"
  name = "Foo Space"
  initials = "FO"
}

When we import it into terraform state, the name is missing.
As result, the state becomes:
{
          "index_key": "foo",
          "schema_version": 0,
          "attributes": {
            "color": "",
            "description": "",
            "disabled_features": [],
            "id": "foo",
            "initials": "FO",
            "name": null,
            "uid": "foo"
          },
          "sensitive_attributes": [],
          "private": "..."
        }

When we execute terraform plan after import:
 # kibana_user_space.space.foo will be updated in-place
  ~ resource "kibana_user_space" "foo" {
        id                = "foo"
      + name              = "Foo Space"
        # (3 unchanged attributes hidden)
    }

We expect there should be no changes.

Fix on release 8.0.1: https://github.com/disaster37/terraform-provider-kibana/releases/tag/v8.0.1


Clarify what/why/how

Update README to clarify what TagBot does, why its neat, and what users need to do after adding the TagBot.yml file. What I wrote is based on my understanding of TagBot - I never used the prior version of it and I thought that the README was fuzzy on the parts that I tried to clarify. It may be that I'm still not clear on these items but would love to modify my pull request if that's the case.

Thanks again!


docs(modeling): add docs describing geometries, paths, and polys

I find it hard to remember the differences between geom, paths, and polygons. So I made some docs that makes for a easy reference. I put it in the jsdoc so that it would appear in the API Reference. If you think this belongs elsewhere, let me know.

All Submissions:

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[x] Does your submission pass tests?

@platypii These little notes are nice. There are also notes for each geometry (see index.js)
There may be some useful notes from the User Guide as well.
https://openjscad.xyz/dokuwiki/doku.php?id=en:design_guide_path

I added the following to geometries/index.js, which makes links directly to the specific geometry documentation. This seems like a good alternative.
 * @see geom2
 * @see geom3
 * @see path2
 * @see poly2
 * @see poly3

@z3dev I like that approach. Would you like me to refactor this branch to look like that? I can move my examples from geometries/index.js to geometries/*/index.js. Should I wait for you to push the changes you made? Or would you rather just include the @see links and leave examples for the wiki?

@z3dev I like that approach. Would you like me to refactor this branch to look like that? I can move my examples from geometries/index.js to geometries/*/index.js. Should I wait for you to push the changes you made? Or would you rather just include the @see links and leave examples for the wiki?

Great! Please refactor. Thanks

Refactored. I like this way much better, good call.


feat: Smart reply

Is your feature request related to a problem? Please describe:

The ML Kit Smart Reply API is not yet supported.
Describe the solution you'd like:

Add a Smart Reply plugin.
Describe alternatives you've considered:

Additional context:

This issue can be sponsored if interested. Please contact us in advance by email and mention the issue. PRs are also welcome.


Notebook cell focus border issues

I really like that we have the focus border but it still bothers me that the left and right ones are so close to the edge of the editor. Since my sidebar is on the right, the left border pretty much aligns with the edge of the window. The right border is drawn over the scroll bar. It feels like it should not touch the scrollbar. I'm wondering whether 1) we should add some margin around the border, 2) experiment with a broader border.

I think this has been discussed before and I think it could make it look a little nicer, here's an example with a 20px margin all around. @rebornix @roblourens @jrieken thoughts?

The outline under the scrollbar doesn't bother me that much. Same as the explorer

but it feels like the content of the cell is moved over to make room for the scrollbar but the outer outline isn't, which is maybe inconsistent.

This is no longer an issue with our default:

But the border does still appear when the gutter is disabled but it's also the same as our tree view so I'm closing this since we haven't heard more feedback about this


Relu(BatchNorm) Fusion

@jbobba @diyessi Guys could you please take another look? I believe I addressed all yr comments.

@pruthviIntel if the PR looks good to you, could you please approve it?

@Krovatkin added some comments. check it out. rest looks okay for me

@Krovatkin please add support for the new op in the layout pass. Just realized that it was missing.


Update documentation stylesheet

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

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 99.088%

Totals

Change from base Build<PHONE_NUMBER>8:
0.0%

Covered Lines:
1956

Relevant Lines:
1974

💛  - Coveralls


mapping file column with / causes error

Hey people,
I get an error when the mapping file column contains "/" (which is not an acceptable character in the qiime mapping file format, but users may not validate with Keemei). Alpha correlation (and other alpha commands) fail in the manner attached.

Changing the "/" to a "_ " does solve the issue. It would be nice if it the error message was clearer about what the problem is.
Thanks,
Arron

Thanks @shiffer1! We'll get this fixed when we overhaul metadata within the next couple of releases.

Looks like a similar problem surfaces when the metadata category has spaces in the name (forum post). This time it happened with alpha-correlation but I suspect it affects alpha-group-significance (possibly others). It's likely just an escaping issue with category names so should be an easy fix.
We should look into fixing this in the affected methods for the upcoming release, and then solve generally with the metadata refactor.


add git user details so merge can succeed

fixes ci failure introduced in #161
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/do-e2e-tests


Minor: Fix versions in BUILD.md

What is the purpose of the change
(For example: This pull request improves file read performance by buffering data, fixing AVRO-XXXX.)
Verifying this change
(Please pick one of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Extended interop tests to verify consistent valid schema names between SDKs
Added test that validates that Java throws an AvroRuntimeException on invalid binary data
Manually verified the change by building the website and checking the new redirect

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@martin-g Do you know if we're still at Rust 1.65 as in BUILD.md? I noticed that we default to 1.75 in the Dockerfile.


Node dies with unhandled exception on jailed plugin syntax error

I'm using
pluginInstance = new jailed.DynamicPlugin(script, api)

and
pluginInstance.whenFailed(function() {
   // Handle plugin failing
 })

but, if script has a syntax error, the process dies with an unhandled exception:
SyntaxError: Unexpected token }
    at Object.exports.runInNewContext (vm.js:48:16)
    at executeJailed (/myDir/node_modules/jailed/lib/_pluginNode.js:194:12)
    at execute (/myDir/node_modules/jailed/lib/_pluginNode.js:143:5)
    at process.<anonymous> (/myDir/node_modules/jailed/lib/_pluginNode.js:36:9)
    at emitTwo (events.js:100:13)
    at process.emit (events.js:185:7)
    at handleMessage (internal/child_process.js:689:10)
    at Pipe.channel.onread (internal/child_process.js:440:11)

Is there a way to handle this without the process dying?

(please note that the plugin is submitted by users, and can have a syntax error)

Would it help, if you execute user's code in a try-catch block?
Have a look on how it's implemented in this demo and how it reacts to a syntax error in a user's provided code:
http://asvd.github.io/jailed/demos/web/console/

The problem is that I need to call functions on the user code / plugin . Evaluating the user block won't work.
Also, if you specify, for example function(a) { return 'a' } in the Web Console, it returns Unexpected token (

But can you maybe call those functions in try-catch block? What would happen then?

Also, if you specify, for example function(a) { return 'a' } in the Web Console, it returns Unexpected token (

Same happens if you run that code in Chrome Dev-tools. To make it work, you can add an assignment:
b = function(a) { return 'a' }

(what I'm doing now is something like):
var log
  , except
  , action
  , next
  , parameters = {}
  , staticData = {}
  , initException = null
  , indexedDB = null
  , location = null
  , navigator = null
  , onerror = null
  , onmessage = null
  , performance = null
  , self = null
  , webkitIndexedDB = null
  , postMessage = null
  , close = null
  , openDatabase = null
  , openDatabaseSync = null
  , webkitRequestFileSystem = null
  , webkitRequestFileSystemSync = null
  , webkitResolveLocalFileSystemSyncURL = null
  , webkitResolveLocalFileSystemURL = null
  , addEventListener = null
  , dispatchEvent = null
  , removeEventListener = null
  , dump = null
  , onoffline = null
  , ononline = null
  , importScripts = null
  , console = null

try {
    application.whenConnected(function() {

      application.remote.start()

      log = application.remote.log
      action = application.remote.action
      except = application.remote.except
      next = application.remote.next

      if (initException) except({type: 'init', e: stringifyException(initException)})

      application.setInterface ({
        callUserFunction: function(data) {
          try {
            onUserFunction(data)
            next()
          }
          catch(e) {
            except({type: 'runtime', e: stringifyException(e)})
          }
        }
      })

      application = undefined

      ${script}

    })

}
catch(e) {
  initException = e
  if (except) except({type: 'init', e: stringifyException(e)})
}

var stringifyException = function(err, filter, space) {
  var plainObject = {}
  Object.getOwnPropertyNames(err).forEach(function(key) {
    plainObject[key] = err[key]
  })
  return JSON.stringify(plainObject, filter, space)
}

where ${script} contains the user code, which is like:
function onUserFunction (data) {
  // do something with the data
  log('did something with the data')
}

@asvd - btw, if I execute the users's code in a try catch block:
 try {
        ${script}
      }
    catch (e) {
      initException = e
      if (except) except({type: 'init', e: stringifyException(e)}
    }

It still dies with an unhandled exception

so user code is substituted into the plugin code body before creating the plugin instance?

Yep, it is.

I just can't pass it as a string and then eval it, because I need to call a callback in the user code and it needs to call callbacks in mine.

Not good, user can close the brace and break the structure of the code.
Do the following:

add the plugin method setUserFunction() which will save user code as a string;
evaluate it in a try-catch block upon callUserFunction() invocation;
call whatever callbacks you need afterwards (next()?).

Is there any callbacks you cannot call in this way?

mmmh I guess so. Users want to be called repeatedly with new data and call interface functions inside their routine (ie: log), how could they do that inside an eval?

Should work if user's code simply calls log(), since eval() executes code in a current context and has everything available.
But if user-provided code is only intended to process some data, I would suggest simply to let user return the result, and then perform any respective actions on the application site. Why do you need user's code to do something additional?

See another demo concerning processing the data with user-provided code:
https://asvd.github.io/jailed/demos/web/process/

Because the user has to send commands to the main application based on the data. Ideally, the user would only have to write something like:
var state = {}

var initialize = function(initData) {
  // This is called once
  state.whatever = initData.whatever
}

var onData = function(data) {
  // This is called repeatedly every time there's a new piece of data
  state.whatever = state + data.whatever
  log('did something with the data')
  action('DO_SOMETHING', calculatedValue)
}

You can also return a string describing which respective action to perform on the application site. Or an array of them in case there might be several actions to be performed. Or a serialized object with properties containing the detailed description concerning what exactly user code wants to happen.

Your example:
var onData = function(data, oldState) {
    return {
        newState: oldState + data.whatever,
        action : {
            name: 'DO_SOMETHING',
            params: [calculatedValue]
        },
        log : 'did something with the data'
    };
}

I'll try something similar, thank you. Btw, the last demo doesn't work -- Mixed Content: The page at 'https://asvd.github.io/jailed/lib/_frame.html' was loaded over HTTPS, but requested an insecure Worker script 'blob:null/4abedc87-2d97-45be-9fc6-1c9bc351aa60'. This request has been blocked; the content must be served over HTTPS.

yep, will investigate on this. Should work if you load it by http instead of https

@asvd Can I close this or you need it open for the https issue?

We can close it. The https issue is solved on HEAD already.


Example/sample?

I have been unable to successfully build a deb using dpkg-buildpackage | db-virtualenv | make-deb.
It could be a bad setup.py or misconfigured python3 venv ( an issue with debian jessie) or something else...
Since this has never worked for me I would like to start troubleshooting with a known good build.
Is there a known working Python3 project that you use for testing?  Can you publish it?
Thanks
Bill

I'm also having issues with configuring simple py3 application.


[Bug]: Puppeteer is detected by cloudflare

Minimal, reproducible example
import { launch } from 'puppeteer-core'

;(async () => {
  console.log('launching...')
  const browser = await launch({
    executablePath: 'C:/Program Files/Google/Chrome/Application/chrome.exe',
    headless: false,
    defaultViewport: null
  })
  console.log('connected')
  const page = await browser.newPage()
  await page.goto('https://nowsecure.nl')
  console.log('waiting for 1 min...')
  await new Promise((r) => setTimeout(r, 60_000))
  console.log('closing...')
  await browser.close()
})()

Error string
N/A
Bug behavior

[ ] Flaky
[ ] PDF

Background
I have used the simplest possible example in puppeteer with a real browser (no headless) and no automation scripts.
I have replicated this without puppeteer and clicking on the cloudflare verification button I pass through to the website, which means I suspect that somehow they are able to detect Puppeteer?
I have also replicated this on android, forwarding the port to chrome dev tools via ADB and connected to the debugging port and experience the same result.
See the video below (the clicks on the page are executed manually):
https://github.com/puppeteer/puppeteer/assets/25906558/c5d0be24-3251-4e91-8fa3-e8bb535fed2d
Expectation
After clicking the verification in Cloudflare (manually), I would expect to pass cloudflare verification and continue to the website
Reality
Cloudflare re-directs back to the verification no matter how many times I click the verification
Puppeteer configuration file (if used)
No response
Puppeteer version
21.3.5
Node version
18.14.2
Package manager
npm
Package manager version
9.5.0
Operating system
Windows

import puppeteer from 'puppeteer-extra'
import StealthPlugin from 'puppeteer-extra-plugin-stealth'
puppeteer.use(StealthPlugin())

;(async () => {
  console.log('launching...')
  const browser = await puppeteer.launch({
    executablePath: 'C:/Program Files/Google/Chrome/Application/chrome.exe',
    headless: false,
    defaultViewport: null
  })
  console.log('connected')
  const page = await browser.newPage()
  await page.goto('https://nowsecure.nl')
  console.log('waiting for 1 min...')
  await new Promise((r) => setTimeout(r, 60_000))
  console.log('closing...')
  await browser.close()
})()

I did try using stealth (as well as connecting to chrome running on an android device) with the same result wich leads me to believe that they can detect the puppeteer connection somehow. I just don't understand how if I am not querying anything.

I'm currently facing the same issues.

Minimal, reproducible example
import { launch } from 'puppeteer-core'

;(async () => {
  console.log('launching...')
  const browser = await launch({
    executablePath: 'C:/Program Files/Google/Chrome/Application/chrome.exe',
    headless: false,
    defaultViewport: null
  })
  console.log('connected')
  const page = await browser.newPage()
  await page.goto('https://nowsecure.nl')
  console.log('waiting for 1 min...')
  await new Promise((r) => setTimeout(r, 60_000))
  console.log('closing...')
  await browser.close()
})()

Error string
N/A
Bug behavior

[ ]  Flaky
[ ]  PDF

Background
I have used the simplest possible example in puppeteer with a real browser (no headless) and no automation scripts.
I have replicated this without puppeteer and clicking on the cloudflare verification button I pass through to the website, which means I suspect that somehow they are able to detect Puppeteer?
I have also replicated this on android, forwarding the port to chrome dev tools via ADB and connected to the debugging port and experience the same result.
See the video below (the clicks on the page are executed manually):
Just.a.moment.-.Google.Chrome.2023-09-27.16-04-47.mp4
Expectation
After clicking the verification in Cloudflare (manually), I would expect to pass cloudflare verification and continue to the website
Reality
Cloudflare re-directs back to the verification no matter how many times I click the verification
Puppeteer configuration file (if used)
No response
Puppeteer version
21.3.5
Node version
18.14.2
Package manager
npm
Package manager version
9.5.0
Operating system
Windows

The solution of Cloudflare is very simple: they just request only this "honest"parameter over the browser API... So:)))

@lavr2004 , how do you suggest that can be solved?

hello, any progress?

I've since moved to using chrome-devtools-frontend package directly, then I have complete control over what commands are sent and received.
It does have a steep learning curve however

@joeledwardson Please, Can you share some kind of sample code how do you solve Cloudflare issue?

same issue :(((


render_loss oscillate

@sklcg ,hello, I want to use the pytorch  implementing your method.But the render_loss always oscillating.As follows:
my code:

the visualization:

And I set the lr in feature extractor as 1e-5, the lr in dense layer and convs2x3 as 1e-3.Could you help me?

我个人理解是：
1.作者源码里面的render_loss大多情况下是以envmap来计算的，它相当于用球谐函数重构公式来重构光照分布。如果一直用envmap来算loss，整体趋势应该是稳定的下降。
2.源码里还是会用上特定三维模型的shmap的，那应该是用球谐函数特征来渲染虚拟物体的光照效果，所以整体loss会有一定震荡。
ps:选择shmap的代码（pytorch）

我在pytorch里面的实现，用原文的学习率5e-4。
另外我render_loss是这样的：
torch.mean(torch.sum((render_pred -render_gt) ** 2, (1, 2)) / torch.nonzero(torch.sum(shmap, -1)).size(0))

@linzi-h ,thank you very much! When I train the model, the rendered image is randomly selected and the render loss may oscillate.But after I modified it, I still can't realize the rendering effect in the paper. Could you give me some your render result?

@Haoyanlong ，我修改过网络结构，这是网络预测的渲染效果图

图片路径：'0019/430_x.jpg'；'0074/409_x.jpg',

@Haoyanlong , Thanks for @linzi-h ‘s reply. As @linzi-h  mentioned，the 3rd shmap is the shmap mainly used for rendering image during traning. It can make loss value converge better. Futhermore,  larger batchsize, SGD optimizer, deeper network model, smaller learning rate or other training tricks can also weaken the oscillation of loss function in some degree. You can apply these tricks reasonably based on your experience and observation.


Add support for ARO

For ARO managed cluster:

OCP scc files should be applied
cloud prepare should be skipped

Fixes: https://github.com/stolostron/submariner-addon/issues/529
Signed-off-by: Yossi Boaron<EMAIL_ADDRESS>

/cc @skitt @aswinsuryan @sridhargaddam @tpantelis

Checked it from ACM - it looks OK.

/approve


render_built_form doesn't work with django 1.11

Using the render_built_form template tag doesn't work using Django 1.11.11.
Whats happening:
The render method in the BuiltFormNode gets passed a RequestContext object. Therefore when it is passed to t.render(context) it throws a TypeError as the use of RequestContext has been deprecated for that function.
Temp Solution
I rewrote it as an inclusion tag that takes context.

NVM, I see this has been fixed in the repo but PyPi has an old version. Please update version, see #216


KAFKA-4283: records deleted from CachingKeyValueStore still appear in range and all queries

Records that are deleted/removed from the CachingKeyValueStore shouldn't appear in range and all queries.
Modified the iterator such that it skips over the deleted records.

@guozhangwang @enothereska @mjsax - found this one today. I'd say it needs to be on 0.10.1, too. otherwise people will get strange results if they query and records have been deleted.

LGTM, great tests!

@dguy Checkstyle seems failing due to
:streams:checkstyleTest[ant:checkstyle] /home/jenkins/jenkins-slave/workspace/kafka-trunk-git-pr-jdk7/streams/src/test/java/org/apache/kafka/streams/state/internals/MergedSortedCacheKeyValueStoreIteratorTest.java:120:44: '++' is preceded with whitespace.  FAILED

@guozhangwang fixed the checkstyle failure and addressed the other comments

Merged to trunk and 0.10.1 branch.


Discuss further revisions to CI/CD privacy notice

Description
From conversation with @haydentherapper, as a follow-on to #2796 / #2797, this is a longer-term placeholder to follow up on whether to further revise / expand the privacy statement notice as relates to CI/CD usage.
May also want to consider whether to clarify usage of flags (e.g. --yes) in connection with non-interactive usage.

I think my preference here is to make opt-in explicit with a unique --accept-terms flag. It seems somewhat wrong that non-interactive clients don't actually accept the terms (similarly for --yes).
That said, it's a little user-hostile so I'd be happier if we introduce a local Cosign state first so you could accept the terms permanently.

Chatted with Zack about this, summary of a few ideas from the chat:

Each prompt should be "pre-answerable" using a unique CLI flag (--accept-terms, --allow-private-container-upload)
We should have a Cosign config file which lets you define the values for each flag. Hopefully should be easy to add, mapping a flag to an env var to a config value
We should rename --yes to something like --accept-defaults. It should be very clearly documented what this does (skips all prompts, push for private containers, may in the future permit other behavior unexpectedly)
The default value for the ToS prompt should be no, forcing explicit consent (note that it currently is)

Shouldn't have to worry about deprecations for any of these changes. We'll alias --yes and remove it later, but no need to prioritize that.

We should rename --yes to something like --accept-defaults. It should be very clearly documented what this does (skips all prompts, push for private containers, may in the future permit other behavior unexpectedly)

Hi, I'm a bit confused by the specification of --accept-defaults. The default values of the ToS prompt is no, and so --accept-defaults will reject the ToS. Is that correct?

We chatted about that too, probably need a different name. The goal is some flag that bypasses all prompts

Thanks for mentioning that, @favonia. Yeah, I think the goal here is:

Provide a flag you can pass to make sure Cosign never hangs by doing something instead of prompting.
Make it really obvious what the behavior  of that flag is (--yes isn't great for that).
Make that flag not accept the terms of service, as you haven't really accepted the terms if you didn't look at them.
Transitioning to the end-goal state smoothly.

We probably need to bikeshed a little (e.g., we should replace rather than rename --yes) but I think the core ideas are right.

I think that's a great idea, but there's a catch: the OAuth URL doesn't capture all of the flows that might result in something being uploaded to a transparency log (there's Rekor and also ambient-credential-based OAuth flows). I'd also be worried that it'd be easy to miss.


Question

How does one check whether a video is currently playing

You need to keep track of the state as it happens. You can do it manually or by using YouTubePlayerTracker.


[bugfix] Comment out Graylog handler from CSCS config

The current dummy server and port produce errors when trying to log the
performance. For this reason, the corresponding configuration lines are
commented out specially using the #@ prefix and will be patched
on-the-fly for production runs.
This must be merged asap, cos it's blocking other PRs.
Fixes #349.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #352   +/-   ##
=======================================
  Coverage   91.09%   91.09%
=======================================
  Files          68       68
  Lines        8244     8244
=======================================
  Hits         7510     7510
  Misses        734      734

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 2ba6d2f...ea1fa19. Read the comment docs.


Using Parceler inside a library project

Since parcelsIndex configuration option is removed from the Parcel annotation, what is the correct way of using Parceler inside a library module?

Make sure the Parceler api and Parceler annotation processor are defined in your library and annotate the given bean.  Parceler will look up the generated class for you even if it's used across different modules.

 Run with --info or --debug option to get more log output.
[14:31:13][Step 1/1] Step Build (Gradle) failed

You must be configuring your Message class as @Parcel in both your modules, possibly using hte @ParcelClass.

No, This happens If I put @Parcel annotation on Message class, Message class is defined in the library module and I haven't used @ParcelClass annotation in app module.

Do you have a working example that you can share to demonstrate the issue?

I'm afraid I can't share the current project with you, but I'll try to create a demo project for this asap.
Also, please not that my app uses Multidex. Today I removed annotation processor from the library module and annotated all Pojos using @ParcelClasses in app module. One strange thing I noticed is, I was getting above error if I set minSdkVersion to 15, but error disappeared for minSdkVersion 21.

Any progress @jimmy0251?


Tooltip on hover or click?

Describe the solution you'd like
I'd like to provide more information about individual nodes in my graph. I was wondering if there's a tooltip on hover or click to display the additional node data? Like a label for each node to display.
Describe your use case
graph with node data.
Describe alternatives you've considered
Maybe regular d3.js has access to this feature and it would be nice to pull it in.
Additional context
Add any other context or screenshots about the feature request here.

Hello @owlstack, thanks for reporting. This is a duplicate of https://github.com/danielcaldas/react-d3-graph/issues/46. You can use custom nodes where you can define yourself a tooltip.


Fix building of Alonzo transaction in Babbage era.

This is achieved by auto-converting from Babbage field protocolParamUTxOCostPerByte to Alonzo field protocolParamUTxOCostPerWord, which is a multiplication by 8.
Fixes https://github.com/input-output-hk/cardano-node/issues/4164

bors r+


cracklib: Add ptest

Purpose of pull request
This PR adds ptest of cracklib.
This ptest executes make test to test the strength of some passwords and check the results.
Note
0003-Fix-a-missing-header-inclusion.patch is a follow-up patch of libcrack2-error-safer-check-variant.patch (Debian patch).
If ptest is enabled, libcrack2-error-safer-check-variant.patch causes the following build failure.
0003-Fix-a-missing-header-inclusion.patch is necessary to fix this issue.
| In file included from ../../cracklib-2.9.6/util/teststr.c:9:
| ../../cracklib-2.9.6/lib/crack.h:32:41: error: unknown type name 'size_t'
|                                          size_t errmsg_len);
|                                          ^~~~~~
| ../../cracklib-2.9.6/lib/crack.h:32:41: note: 'size_t' is defined in header '<stddef.h>'; did you forget to '#include <stddef.h>'?
| ../../cracklib-2.9.6/lib/crack.h:1:1:
| +#include <stddef.h>
|  #ifndef CRACKLIB_H
| ../../cracklib-2.9.6/lib/crack.h:32:41:
|                                          size_t errmsg_len);
|                                          ^~~~~~

Also, cracklib doesn't have any expected data for make test, so expected-data is newly added to compare it with the actual result.
Test
How to test

Enable ptest and install cracklib package

$ . setup-emlinux
$ cat << EOS >> conf/local.conf
MACHINE = "qemuarm64"
DISTRO_FEATURES_append = " ptest"
EXTRA_IMAGE_FEATURES += "ptest-pkgs"
IMAGE_INSTALL_append = " cracklib"
EOS

Build core-image-minimal image

$ bitbake core-image-minimal

Run qemu and execute ptest of cracklib

$ runqemu nographic
...(snip)...
# ptest-runner -l
...(snip)...
# ptest-runner cracklib

Also, I confirmed that SDK build succeeds with bitbake core-image-minimal-sdk -c populate_sdk.
Test result
root@qemuarm64:~# ptest-runner -l
Available ptests:
acl     /usr/lib/acl/ptest/run-ptest
busybox /usr/lib/busybox/ptest/run-ptest
cracklib        /usr/lib/cracklib/ptest/run-ptest
util-linux      /usr/lib/util-linux/ptest/run-ptest
zlib    /usr/lib/zlib/ptest/run-ptest
root@qemuarm64:~# ptest-runner cracklib
START: ptest-runner
2023-12-22T00:07
BEGIN: /usr/lib/cracklib/ptest

=======================================================
If you get an error when running make test about a
missing pw_dict.pwd file, that indicates that the word
list dictionary file has not been built. You need to
at least run make install and make dict to install
the dictionay. See the README file for more details.
=======================================================

util/cracklib-check < test-data
(data fread failed): Success
(data fread failed): Invalid argument
(data fread failed): Success
(data fread failed): Success
(data fread failed): Success
(data fread failed): Success
(data fread failed): Success
PASS: antzer: it is based on a dictionary word
PASS: G@ndalf: OK
PASS: neulinger: it is based on a dictionary word
PASS: lantzer: OK
PASS: Pa$$w0rd: it is based on a dictionary word
PASS: PaS$W0rd: it is based on a dictionary word
PASS: Pas$w0rd: it is based on a dictionary word
PASS: Pas$W0rd: it is based on a dictionary word
PASS: Pa$sw0rd: it is based on a dictionary word
PASS: Pa$sW0rd: it is based on a dictionary word
=== Test Summary ===
TOTAL: 10
PASSED: 10
FAILED: 0
DURATION: 2
END: /usr/lib/cracklib/ptest
2023-12-22T00:08
STOP: ptest-runner

ptest-cracklib.log
Test summary

TOTAL: 10

PASS: 10
FAIL: 0

I executed this ptest 3 times and obtained the same results

meta-debian-extendedの最新版にrebaseした上で、SDKビルドが通ることを確認しました。
meta-debian, meta-debian-extended, meta-emlinux, pokyを使い、DISTRO=emlinux で bitbake core-image-minimal-sdk -c populate_sdk を実行しました。


up start improvements

Just an issue for #239, the gist of it is to provide local build/clean hooks so that up start starts the proxy and runs node app.js, or go run main.go etc for you.
The alternative is to replace up start with a less magical up proxy PORT, so instead of running:
$ up start

You'd run something like the following, where 5000 is the port app.js is listening on.
$ node app.js
$ up proxy 5000

and visit the proxy's port instead of your app's. This might be a bit more confusing, but you also need to be aware of less magic which could be potentially confusing as well if you start deviating from the conventions (of ./app.js, and ./main.go etc), because then you'd need something like:
{
  "proxy": {
    "local_command": "go run cmd/api/main.go"
  }
}

Opinions?

Signal propagation, stdio inheritance, etc make the up start code much more error prone.  But if they can be solved with confidence, perhaps up start seems simpler.
Given that up start might need to interact with other systems, probably allowing a --port option would be good.  Then when it launches the subprocesses, process.env.PORT can define what port to run on.
up start --port 8080

With up proxy, it would have to look something like this:
up proxy --bind 8080 5000

which might be confusing enough to not use it in my opinion.
Either way I think proxy.local_command will be necessary, since often times in development you won't be launching your code the same way as in prod, you will be using some kind of dev server (hot reloading, etc).

If we don't have up start, you'd just go run main.go or whatever as you would normally, so that definitely cuts out a lot of weird edge-cases we might hit.
up start is definitely a bit simpler UX-wise which I like, but I'm not 100% sold on it since it's so much easier to just say "run your app however you normally do" haha

doing local_command for now, but later it might make more sense to refactor that out, and do local overrides for anything (move it to stages.local).

Was think it would be really useful if the locally developed lambda could assume the function role.
Right now my iterations are using gin locally, and when I deploy, obviously I have to deal with the inevitable & confusing misalignment with IAM permissions between my own AWS_PROFILE and the role that the lambda runs under.

@kaihendry ahhh good idea, I'll see if I can add that!


Integration Test - Release - 2022/01/12 05:30:32

Auto create for integration test. IssueCommandFlow

#pri1

Just type '#pri3'

#pri2

#pri3

#assign PRMergerTest1

#assign NonAllowedUser

The following users don't have valid GitHub IDs, or are not collaborators on this repo: nonalloweduser

#reassign NonAllowedUser

#reassign PRMergerTest2

#please-close

The following users don't have valid GitHub IDs, or are not collaborators on this repo: nonalloweduser

GitHub user PRMergerTest2 has been removed from the MicrosoftDocs organization, so they were automatically removed as an assignee.

#unassign PRMergerTest1

#unassign NonAllowedUser


[BUG] index-park_buffer message during stuck plot

Describe the bug
When plotting a k34, encountered the message in the View Log, index-park_buffer 9991 park_buffer_size 9377. Source of the output text is this code match from a search engine in chiapos immediately prior to throwing an InvalidStateException, which I assume is output somewhere else.
To Reproduce
Steps to reproduce the behavior:

Create a new k34 associated with a non-self-pool NFT in the GUI
Select the three vertical dots under the Action column in the Plots tab
Choose "View Log"
Error occurred at 85% displayed completion while compressing tables 3 and 4, during the second pass.

Expected behavior
Plot completes normally or notifies user that it has failed, rather than hanging. No idea if the exception is fatal or not, what causes it, how to correct or prevent it, et cetera.
Screenshots

Desktop

OS: Windows 10 Pro
OS Version/Flavor: 10.0.19043
CPU: Intel i3-9100F

Additional context
Never had an issue plotting k34s before. This is my first time creating a new plot since Chia 1.1.3 or so. I was plotting to a dynamic spanned drive comprised of two HDDs, used both as the temporary and final destination for the plots.
I assume encountering what appears to be a fatal exception is a bug. If it is not, then consider this an Enhancement request to make the displayed info in the log clearer that the plot has failed, with instructions on how to proceed.

Still needs to be reviewed to see if there's an underlying issue.
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: github-actions[bot] @.>
Sent: Friday, September 24, 2021 7:06:00 AM
To: Chia-Network/chiapos @.>
Cc: Dimelo Waterson @.>; Manual @.>
Subject: Re: [Chia-Network/chiapos] [BUG] index-park_buffer message during stuck plot (#307)
'This issue has been flagged as stale as there has been no activity on it in 14 days. If this issue is still affecting you and in need of review, please update it to keep it open.'
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/Chia-Network/chiapos/issues/307#issuecomment-926540140, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AM4UEJB5GOU43PTBK6RYXDLUDRLRRANCNFSM5DX5BHUQ.

Issue still exists in Chia 1.2.9 for plots as small as k-33

@mariano54 who would I reach out to to reopen this?

Still needs review
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows

From: github-actions[bot] @.>
Sent: Sunday, December 12, 2021 6:05:40 AM
To: Chia-Network/chiapos @.>
Cc: Dimelo Waterson @.>; Manual @.>
Subject: Re: [Chia-Network/chiapos] [BUG] index-park_buffer message during stuck plot (#307)
'This issue has been flagged as stale as there has been no activity on it in 14 days. If this issue is still affecting you and in need of review, please update it to keep it open.'
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/Chia-Network/chiapos/issues/307#issuecomment-991877177, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AM4UEJECETNN2NSEC5RSFTTUQR6YJANCNFSM5DX5BHUQ.


Parameter references

Considering the idea of parameter references, i.e. specific reference spans for arguments to a method. It would be useful to see all the places where an optional parameter is set. That said, the space requirement for this would probably be quite large as this would introduce a large number of additional references that need to be indexed. One possibility would be to only do this for optional parameters, but that would be inconsistent and potentially make for a non-intuitive user experience. The other option is to store the parameter reference span inside the reference span for the method. This would reduce storage space considerably because the number of indexed documents would remain unchanged and line span text inside references could be reused in many cases. Further, the parameter index could be indexed to allow only finding reference results which actually have the parameter specified.

We could just highlight all optional arguments in the FAR for the method itself. So you click on the method to find all references, and when you read through the references you see which call sites specify the optional argument because we highlight it.

Not quite that simple. That assumes all parameters are on the same line (as we only store the line text with the reference spans). There also is the issue of how to know which parameter to highlight (I don't want to build in special knowledge about how C# binds arguments to parameters).


The examples list on the home page leads to a blank screen

Describe the bug
Clicking on an example in the examples list according to these instructions results in a blank page.
Version
test
Browser

[x] Chrome
[ ] Safari
[ ] Firefox
[ ] Edge

OS

[ ] macOS
[x] Windows
[ ] Ubuntu

To Reproduce
Steps to reproduce the behavior:

Install Composer according to these instructions
After starting Composer in a browser, click the Echo Bot button at the top of the Examples list on the homepage.
See blank page

Expected behavior
The Composer UI should remain loaded in the browser window and the popup to setup the example should be displayed.

Closing this as it should already be addressed in the latest version of master.


building for iOS Simulator, but linking in dylib built for macOS, file '/usr/local/Cellar/gmp/6.2.0/lib/libgmp.dylib' for architecture x86_64

I am very glad that I got this great library for homomorphic encryption in my app. But I would like to inform that i am getting compilation issue while running the project on simulator. below are the details. Any suggestion would be appreciated.
Xcode version: 11.3.1
iOS version: 13.0
Swift version: 5.0 as well as 4.2
d /Users/anusuya_p/Library/Developer/Xcode/DerivedData/VisionSample-gisduavvviadxadozdzqqmpaaxku/Build/Products/Debug-iphonesimulator/VisionSample.app/VisionSample normal (in target 'VisionSample' from project 'VisionSample')
cd /Users/anusuya_p/Downloads/VisionSample

/Users/anusuya_p/Downloads/Xcode_12.1.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -target x86_64-apple-ios13.0-simulator -isysroot /Users/anusuya_p/Downloads/Xcode_12.1.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator14.1.sdk -L/Users/anusuya_p/Library/Developer/Xcode/DerivedData/VisionSample-gisduavvviadxadozdzqqmpaaxku/Build/Products/Debug-iphonesimulator -F/Users/anusuya_p/Library/Developer/Xcode/DerivedData/VisionSample-gisduavvviadxadozdzqqmpaaxku/Build/Products/Debug-iphonesimulator -filelist /Users/anusuya_p/Library/Developer/Xcode/DerivedData/VisionSample-gisduavvviadxadozdzqqmpaaxku/Build/Intermediates.noindex/VisionSample.build/Debug-iphonesimulator/VisionSample.build/Objects-normal/x86_64/VisionSample.LinkFileList -Xlinker -rpath -Xlinker @executable_path/Frameworks -dead_strip -Xlinker -object_path_lto -Xlinker /Users/anusuya_p/Library/Developer/Xcode/DerivedData/VisionSample-gisduavvviadxadozdzqqmpaaxku/Build/Intermediates.noindex/VisionSample.build/Debug-iphonesimulator/VisionSample.build/Objects-normal/x86_64/VisionSample_lto.o -Xlinker -export_dynamic -Xlinker -no_deduplicate -Xlinker -objc_abi_version -Xlinker 2 -fobjc-link-runtime -L/Users/anusuya_p/Downloads/Xcode_12.1.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/iphonesimulator -L/usr/lib/swift -Xlinker -add_ast_path -Xlinker /Users/anusuya_p/Library/Developer/Xcode/DerivedData/VisionSample-gisduavvviadxadozdzqqmpaaxku/Build/Intermediates.noindex/VisionSample.build/Debug-iphonesimulator/VisionSample.build/Objects-normal/x86_64/VisionSample.swiftmodule -L/usr/local/Cellar/gmp/6.2.0/lib -lgmp -Xlinker -sectcreate -Xlinker __TEXT -Xlinker __entitlements -Xlinker /Users/anusuya_p/Library/Developer/Xcode/DerivedData/VisionSample-gisduavvviadxadozdzqqmpaaxku/Build/Intermediates.noindex/VisionSample.build/Debug-iphonesimulator/VisionSample.build/VisionSample.app-Simulated.xcent /Users/anusuya_p/Library/Developer/Xcode/DerivedData/VisionSample-gisduavvviadxadozdzqqmpaaxku/Build/Products/Debug-iphonesimulator/PackageFrameworks/SipHash.framework/SipHash -Xlinker -dependency_info -Xlinker /Users/anusuya_p/Library/Developer/Xcode/DerivedData/VisionSample-gisduavvviadxadozdzqqmpaaxku/Build/Intermediates.noindex/VisionSample.build/Debug-iphonesimulator/VisionSample.build/Objects-normal/x86_64/VisionSample_dependency_info.dat -o /Users/anusuya_p/Library/Developer/Xcode/DerivedData/VisionSample-gisduavvviadxadozdzqqmpaaxku/Build/Products/Debug-iphonesimulator/VisionSample.app/VisionSample -Xlinker -add_ast_path -Xlinker /Users/anusuya_p/Library/Developer/Xcode/DerivedData/VisionSample-gisduavvviadxadozdzqqmpaaxku/Build/Intermediates.noindex/SwiftPaillier.build/Debug-iphonesimulator/SwiftPaillier.build/Objects-normal/x86_64/SwiftPaillier.swiftmodule -Xlinker -add_ast_path -Xlinker /Users/anusuya_p/Library/Developer/Xcode/DerivedData/VisionSample-gisduavvviadxadozdzqqmpaaxku/Build/Intermediates.noindex/BigInt.build/Debug-iphonesimulator/BigInt.build/Objects-normal/x86_64/BigInt.swiftmodule -Xlinker -add_ast_path -Xlinker /Users/anusuya_p/Library/Developer/Xcode/DerivedData/VisionSample-gisduavvviadxadozdzqqmpaaxku/Build/Intermediates.noindex/Bignum.build/Debug-iphonesimulator/Bignum.build/Objects-normal/x86_64/Bignum.swiftmodule

ld: building for iOS Simulator, but linking in dylib built for macOS, file '/usr/local/Cellar/gmp/6.2.0/lib/libgmp.dylib' for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

I'm happy to hear, that the library is useful for you. Actually, I don't have much time to look into this issue right now, but it seems, that the GMP library can't be linked. You should be able to remove GMP from this library and use Bignum only, which is pure Swift, so there shouldn't be any linking problem.

Thanks for the reply. you mean OpenSSL-based Swift big number library? Do you have any quick reference to refer and make the things work? I am looking for the details how to remove GMP from this library and use the BigInt ? could you please help me on this. Thank you!

To remove GMP, you have to remove the dependency BignumGMP from Package.swift (line 14 and in line 19). Then you have to remove it from Paillier.swift: I'm not 100% sure, but I think it should be possible to replace line 8 with typealias Bignum = BigUInt.
Let me know, if this works.

Thanks @code28 for the details. I made necessary changes and made it up and running on iOS application by removing the bigNum package. I will make it available to the public sometimes later as I am running with ton of task on my plate. When you have some time you can quick go through the git and share your comments once I have pushed the code.
Thanks again.


Update shader blocks to include "width" block

At present shader blocks documentation mentions 5 shader blocks namely global,position,color,normal,filter. (refer: here)
It seems width is also used as a shader block in the style sheets (including eraser map style sheet).

Thanks – fixed with https://github.com/tangrams/tangram-docs/commit/83349b504979ea6495aa32e8da626443b46f1c71 – can I get a check for accuracy?

Adjusted block order: https://github.com/tangrams/tangram-docs/commit/5a9fe69131f5054e7f8bcf60ca8095fa3deb957a


DDPG input discrepancy

This line gives error if the input is passed as a list rather than a np.ndarray. However the docstring suggests input can be a list.
https://github.com/AgileRL/AgileRL/blob/b0eb228ba6a0ec26c5a11ea5e7168ac8d3cbfb65/agilerl/algorithms/ddpg.py#L280

Fixed, thanks for pointing this out.


Gallery view has usability issues

Doesn't really make sense to allow gallery dimensions to be chosen from more than one table.

Dimension selection window is confusing. There is no indication of which field you are selecting for.

Good point. We should have a more descriptive header/description on the dimension selector modal, perhaps?
On Thu, May 7, 2015 at 3:39 PM -0700, "Nicole Coleman"<EMAIL_ADDRESS>wrote:
Dimension selection window is confusing. There is no indication of which field you are selecting for.
—
Reply to this email directly or view it on GitHub.

I've added a 'description' attribution to the 'modal' directive. If it is provided, it will replace the header text. I'll make use of that in the gallery view now.

I've updated this on the master branch. If we want even more flexibility (maybe a title and a secondary description, then it's fairly easy to add this functionality to the modal).

Also addressed some brittleness when selecting dimensions that could result in errors on the console. Will close this issue.


feat: make messages overridable individually

I wanted the ability to override a single message without having to specify all of them in the config file so I just added a deep merge in loadConfig.
I was torn between lodash or other libs to do the deep merge itself but lodash is a handy collection of utilities so that's what I went with.

@jcw- Any chance I could grab a review from you? 😄

Very happy to help. It was also something I found myself wanting. 😃


Cannot install in Ubuntu 22

Describe the bug
Cannot install in Ubuntu 22, mktemp succeeds but directory is non-writable
To Reproduce
Steps (or project) to reproduce the behavior:

Follow installation instructions for Linux at https://docs.gauge.org/getting_started/installing-gauge.html?os=linux&language=python&ide=vscode

$ sudo curl -SsL https://downloads.gauge.org/stable | sh

Logs
Downloading binary from URL: https://github.com/getgauge/gauge/releases/download/v1.4.3/gauge-1.4.3-linux.x86_64.zip to /tmp/tmp.8LUXhdFX4o
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
Warning: Failed to open the file ./gauge.zip: Permission denied
  0 8982k    0  8259    0     0  12107      0  0:12:39 --:--:--  0:12:39 12107
curl: (23) Failure writing output to destination
command failed: curl -L -o ./gauge.zip https://github.com/getgauge/gauge/releases/download/v1.4.3/gauge-1.4.3-linux.x86_64.zip

Expected behavior
Gauge installer downloads to /tmp/ directory created by mktemp

OS Ubuntu 22.04.2 LTS

Additional context
Suspect Ubuntu protections for /tmp (introduced in Ubuntu 20) block the script from using that directory (even by sudo) to store temp files.

I am on popOS (an ubuntu based distro) and here is what I see:
$ sudo curl -SsL https://downloads.gauge.org/stable | sh
[sudo] password for steam:
Downloading binary from URL: https://github.com/getgauge/gauge/releases/download/v1.4.3/gauge-1.4.3-linux.x86_64.zip
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 8982k  100 8982k    0     0  2524k      0  0:00:03  0:00:03 --:--:-- 4194k
You do not have write permision for /usr/local/bin. Trying with sudo.
Downloaded the binary to '/usr/local/bin'.
Make sure the above path is available in 'PATH' environment variable.
$ gauge -v
Gauge version: 1.4.3
Commit Hash: f98dd40

Plugins
-------
dotnet (0.5.0)
html-report (4.2.0)
java (0.9.1)
js (2.4.0)
json-report (0.3.7)
python (0.3.17)
screenshot (0.1.0)
spectacle (0.1.4)
ts (0.1.0)
steam@pop-os:~$ lsb
lsblk        lsb_release
steam@pop-os:~$ lsb
lsblk        lsb_release
$ lsb_release -a
LSB Version:	core-11.1.0ubuntu4-noarch:printing-11.1.0ubuntu4-noarch:security-11.1.0ubuntu4-noarch
Distributor ID:	Pop
Description:	Pop!_OS 22.04 LTS
Release:	22.04
Codename:	jammy

I tried with raw Ubuntu 22.0.4 and can't replicate a problem here. Will close this. We can re-open if you can provide more specific replication instructions.


Configure PR still adds renovate.json when you have it in package.json

I have and kinda prefer the config of it to be in the package.json. When it detects package.json to look for renovate field and only if there's no such field to add renovate.json.
(btw, side question [not worth whole new issue] how to ignore pinning only specific package, like semantic release, which should be with caret always - i know i can just close the future pr that will come, but isn't in next run try to pin it again? or when new release of it it will send pr with pinned version?)

So you added config to package.json then installed Renovate App for the repo? And it raises unnecessary PR still?

To target specific packages, add config like this:
"packageRules": [{
  "packageNames: ["semantic-release"],
  "pinVersions": false
}]

Note this used to be called "packages", now renamed to "packageRules". Both work, but don't use both at the same time.

Yea, look over here https://github.com/tunnckoCore/koa-better-serve/pull/6.
Actually, not sure what is the exact case. Maybe is interesting, because PR is sent 5 minutes after the commit that has the config, the old one package.json didn't have renovate field.
BUT, there's but. Because Renovate is activated only on @tunnckoCore, before some time (dont know how much, but in around last hour +/- some mins) i moved it there from @charlike profile (so it's activated on that moment). So maybe that's the reason.
So yea, maybe my fault. I will probably do more moves today, so we'll see if there is really a problem.

To target specific packages, add config like this:

Cool! Thanks :blossom:

You can always just close the PR I merged and it will then use package json config if found. But I'll keep this open to investigate if we can prevent this in the first place.

Renovate runs on hourly schedule still so any "5 minutes after" is purely coincidental.

Renovate runs on hourly schedule still so any "5 minutes after" is purely coincidental.

Yea, yea, probably that's what happened. Because in the moment when it was activated (in the moment of move) there was the old package.json :)

BTW Renovate only looks for either Configure Renovate PR or renovate.json so this behaviour is expected. But it's probably OK to also look for a renovate config in root package.json too.

 Am i crazy, or today is just very bad day for me :sob: :scream:

But why are you expecting any PRs for that repo? With the default settings (in Configure Renovate PR) there was just one PR expected - pinning semantic-release. But then in your package.json you've unpinned that package so therefore.. nothing to do?

Oh god, yea, sorry!  :D Awful day.
I'll close it, and will see if it happens to some other repos :)


git: add error

I am having issues with the git add not working in sublime. this is the error that populates:
/usr/local/bin/git apply --cached - failed with following output:
fatal: unrecognized input
I was able to git add and commit just fine last night but now this morning there is this error. I have not seen any documentation on this issue for fixes.

Do you have the exact steps you did? There is many ways to add in gitsavvy.

I am adding via git: add in the command + shift + p
then when it says use super enter it gives me the error message, but it worked just fine yesterday

Having funky issue in my git repo, working now after change....thanks anyways

Good, feel free to reopen.


Remove duplicate definition for mapbox settings.

@akatsoulas r?

r+
Just check why the tests are failing


Aneeque works/fishnet

@MHHukiewitz Please assure the query function

@AneequeZubair9 wrong target repository :sweat_smile:


how to use https in h2 client?

any example to use https h2 client?

https://www.cloudwego.io/docs/hertz/tutorials/basic-feature/protocol/http2/


Can't use nested fieldGroups for advanced layout

I am using angular-material to layout a form and have been experimenting with different layout possibilities. I can get things to work with a single level of fieldGroup, but I can't make it work when nesting one fieldGroup inside of another. One example where this would be useful is putting a column layout inside of a row layout to produce something like:

The template that produces the image above is:

Trying to port this over to formly-fields would look like:
vm.myFields = [
    {
      elementAttributes: {
        layout: 'row',
        style: 'height:200px'
      },
      fieldGroup: [
        {
          template: '

',
          elementAttributes: {
            flex: '75',
            style: 'background-color:blue'
          }
        },
        {
          elementAttributes: {
            flex: '25',
            layout: 'column',
            style: 'height:200px'
          },
          fieldGroup: [
            {
              template: '

',
              elementAttributes: {
                flex: '60',
                style: 'background-color:red'
              }
            },
            {
              template: '

',
              elementAttributes: {
                flex: '40',
                style: 'background-color:green'
              }
            }
          ]
        }
      ]
    }
];

Unfortunately this doesn't work because the flex: '25' attribute on the column
 gets applied to the inner ng-form element created by the fieldGroup instead of the outer formly-field element that contains the second fieldGroup. This breaks the flexbox design as the second element in the flex row has no flex attribute and gets assigned a 0 width. As far as I can tell there is no way to assign attributes to this second formly-field in the row in this example (it is created by formly behind the scenes).

This is definitely something that I want to make work. Give me some time to look into it later.

I created a jsbin for it to demonstrate the issue: http://jsbin.com/goduno/edit

Boy, you've really got me stumped... I don't know how to accomplish that design based on how angular-formly works. Could you describe the UI you're trying to actually build? Maybe I can help you figure out a work-around.

Honestly, I was just trying to grok how to fully use angular-material's flex layout with formly and was trying some things out. I ended up just setting things up without nesting flex layouts and it all looks nice and works great.
One thing I thought of to make this nesting work is if there was a property on the field configuration object like containerAttributes that only applied when a fieldGroup property was also provided. Then the containerAttributes are applied to the outer formly-field element that wraps the inner ng-form created by the fieldGroup. Then, moving the flex: 25 into containerAttributes instead of elementAttributes in the second fieldGroup would fix the issue.

That shouldn't be too difficult to add I think... If you think that it would work and you need that functionality, then I may take the time to add it.

I think I have figured out a nice way to do this, but there might be a drawback that I am not seeing, please point it out for me if you see one.
Instead of forcing the layout into the javascript, do the flex layout in the html and use multiple formly-form elements that share the same model. For example the html :
  <form>

      <formly-form flex="75" style="background-color:blue" model="vm.myModel" fields="vm.blueFields"></formly-form>

        <formly-form flex="60" style="background-color:red" model="vm.myModel" fields="vm.redFields"></formly-form>
        <formly-form flex="40" style="background-color:green" model="vm.myModel" fields="vm.greenFields"></formly-form>

  </form>

and the javascript:
ngModule.controller('testController', function() {
  var vm = this;
  vm.myModel = {};

  vm.blueFields = [
    {
      type: 'input',
      key: 'blueInput',
      templateOptions: {
        label: 'Blue Input'
      }
    }
  ];

  vm.redFields = [
    {
      type: 'radio',
      key: 'redRadio',
      templateOptions: {
        label: 'Red Radio',
        options: [
          {
            label: 'Option 1',
            value: 1
          },
          {
            label: 'Option 2',
            value: 2
          }
        ]
      }
    }
  ];

  vm.greenFields = [
    {
      type: 'radio',
      key: 'greenRadio',
      templateOptions: {
        label: 'Green Radio',
        options: [
          {
            label: 'Option 1',
            value: 1
          },
          {
            label: 'Option 2',
            value: 2
          }
        ]
      }
    }
  ];
});

Yields:

What drawbacks are there to having my fields split among separate formly-form elements?

I don't think any drawbacks of having multiple formly-forms would be noticeable. If you wanted to make sure that formState was shared between all of the fields (in the different forms) then you'd have to make sure it was initialized prior to the forms rendering. Another thing you'd need to be aware of is that the fields property for each of the forms would be different. Not normally a real issue though. I think you've found a good solution. Do you mind creating an example for the website?

Sure, I can do that. Also, would there be a point in making the formly-forms use the same form attribute? I am not entirely clear what impact that would have.

Ah, good catch. I didn't notice that. Basically, the last formly-form would overwrite the other ones. So you don't want to do that. Instead, wrap all of them in a single ng-form or form and specify a name on that and don't worry about specifying a form attribute on any of the formly-forms (unless you're interested in that specific form controller for some reason).

I'm going to go ahead and close this issue. An example for the website would be welcome. Thanks @DrDanRyan!

This isn't a good solution if I'm working with multiple possible advanced layouts. I need no HTML layout configuration. (sorry for bad english)

I'm not sure I understand the problem you're having. Could you follow the instructions here so we can help you better? http://help.angular-formly.com


Documentation page for Overrides + Defaults

Should include the diagram showing the whole stack of how things interact, where the data comes from, the relevant APIs, etc.

Link to this page from the visualizer override UI section.

Link to this page from the visualizer override UI section.

The new section help tooltip are prime candidates for these links


[NOTICE] Pin to old debian version if seeing issues with debian 12 (bookworm)

Debian 12 bookworm was released on June 10th, 2023.  As of June 15th, 2023, many of the images we publish in devcontainers/images have also been updated to use bookworm as a base.  We have tagged these bookworm based images with a new major version and continue to tag alternative versions with older debian OSs (eg bullseye).
As with any major OS release, it takes time for upstream dependencies that these Features rely on to update. Notably, several Features in this repo rely on the debian apt repositories maintained by Microsoft, which has only just started to get populated.
If you're seeing a new install failure related to debian bookworm, please pin your dev container's base image to the previous version of debian.  An example is shown below:.
For example, for typescript-node, using an image tag that references  -bullseye (the previous version of Debian) works:
{
  "image": "mcr.microsoft.com/devcontainers/typescript-node:1-16-bullseye", // bullseye is version 11 of Debian
  "features": {
     "ghcr.io/devcontainers/features/docker-in-docker:2": {}
  }
}

All the tags for a given image can be found from the README on the devcontainers/images repo (eg: https://mcr.microsoft.com/v2/devcontainers/typescript-node/tags/list)
Alternatively, pinning to the previous major version is another possible strategy (mcr.microsoft.com/devcontainers/typescript-node:0-16)
Please bear with us as we work to update everything in our control and harden where we are forced to wait!  The best practice here is to always pin images in your dev containers to a specific distro/version to avoid any impact in the future.
Related:
https://github.com/devcontainers/images/issues/607
https://github.com/devcontainers/features/issues/573
https://github.com/devcontainers/images/pull/630
https://github.com/devcontainers/images/pull/608

Thanks! This fixed my broken CI.

mcr.microsoft.com/devcontainers/typescript-node:0-16


How to implement CollisionSoundController?

Hi dear TomorrowTodayLabs, I want to implement CollisionSoundController, but it's not working.
What should I do, to make it working?
In my case I'm adding CollisionSoundController and NVR Collision Sound Object. But nothing happening.
Thank you!

Start by looking at the example scene, are the sounds working for you in there?  Then inspect how those items are constructed and copy them.

@SmartCarrion , sure, I'm already trying to to that, but I missing something, something not obvious


Feat xWELL Router

Router contract to simplify user experience when going from well on moonbeam to xwell on base.

Feat xWELL Router

Generated at commit: febd86ff613c74c24bf8c684cdeee85a724ac366

🚨 Report Summary
Severity Level	Results
Contracts Critical
High
Medium
Low
Note
Total	1
0
0
15
40
56
Dependencies Critical
High
Medium
Low
Note
Total	0
0
0
0
0
0
For more details view the full report in OpenZeppelin Code Inspector

Side note: @ElliotFriedman I'd love to hear your opinion on the crit included above - I think it's safe to ignore but wanted to check.