# ./spec/support/rubygems_ext.rb:44:in `gem_load'

  41) bundle exec `load`ing a ruby file instead of `exec`ing the executable raises an error without a backtrace behaves like it runs like a normally executed executable
      Failure/Error: expect(err).to eq(expected_err)

        expected: "bundler: failed to load command: /bundler/tmp/1/bundled_app/ruby_executable (/bundler/tmp/1/bundled_app/ruby_executable)\nErr: Err"
             got: "ps: unrecognized option: p\nBusyBox v1.30.1 (2019-06-12 17:51:55 UTC) multi-call binary.\n\nUsage: p...thod `strip' for nil:NilClass\n  /bundler/tmp/1/bundled_app/ruby_executable:8:in `<top (required)>'"

        (compared using ==)

        Diff:

        @@ -1,3 +1,12 @@
        +ps: unrecognized option: p
        +BusyBox v1.30.1 (2019-06-12 17:51:55 UTC) multi-call binary.
        +
        +Usage: ps [-o COL1,COL2=HEADER]
        +
        +Show list of processes
        +
        +	-o COL1,COL2=HEADER	Select columns for display
         bundler: failed to load command: /bundler/tmp/1/bundled_app/ruby_executable (/bundler/tmp/1/bundled_app/ruby_executable)
        -Err: Err
        +NoMethodError: undefined method `strip' for nil:NilClass
        +  /bundler/tmp/1/bundled_app/ruby_executable:8:in `<top (required)>'

        Commands:
        $ /usr/bin/ruby -I/bundler/lib -e  \
          <<EOS
                    require "bundler"
                    begin
                      puts Bundler.bundle_path
                    rescue Bundler::GemfileNotFound
                      ENV["BUNDLE_GEMFILE"] = "Gemfile"
                      retry
                    end

        EOS
        /bundler/tmp/1/gems/system
        # $? => 0

        $ /usr/bin/ruby --disable-gems -r/bundler/spec/support/rubygems -S gem --backtrace install \
          --no-document --ignore-dependencies /bundler/tmp/1/gems/remote1/gems/rack-1.0.0.gem
        Rack's post install message
        Successfully installed rack-1.0.0
        1 gem installed
        # $? => 0

        $ /usr/bin/ruby --disable-gems -r/bundler/spec/support/rubygems -S gem --backtrace install \
          --no-document --ignore-dependencies /bundler/tmp/1/gems/remote1/gems/rack-0.9.1.gem
        Rack's post install message
        Successfully installed rack-0.9.1
        1 gem installed
        # $? => 0

        $ /usr/bin/ruby --disable-gems -I/bundler/lib:/bundler/spec -rsupport/rubygems -rsupport/hax \
          -r/bundler/spec/support/artifice/fail /bundler/exe/bundle install --retry 0
        Resolving dependencies...
        Using bundler 2.1.0.pre.2
        Using rack 1.0.0
        Bundle complete! 1 Gemfile dependency, 2 gems now installed.
        Use `bundle info [gemname]` to see where a bundled gem is installed.
        Don't run Bundler as root. Bundler can ask for sudo if it is needed, and installing your bundle as root will break this application for all non-root users on this machine.
        # $? => 0

        $ /usr/bin/ruby --disable-gems -I/bundler/lib:/bundler/spec -rsupport/rubygems -rsupport/hax \
          -r/bundler/spec/support/artifice/fail /bundler/exe/bundle exec \
          /bundler/tmp/1/bundled_app/ruby_executable arg1 arg2
        EXEC: load
        ARGS: /bundler/tmp/1/bundled_app/ruby_executable arg1 arg2
        RACK: 1.0.0
        ps: unrecognized option: p
        BusyBox v1.30.1 (2019-06-12 17:51:55 UTC) multi-call binary.

        Usage: ps [-o COL1,COL2=HEADER]

        Show list of processes

        	-o COL1,COL2=HEADER	Select columns for display
        bundler: failed to load command: /bundler/tmp/1/bundled_app/ruby_executable (/bundler/tmp/1/bundled_app/ruby_executable)
        NoMethodError: undefined method `strip' for nil:NilClass
          /bundler/tmp/1/bundled_app/ruby_executable:8:in `<top (required)>'
        # $? => 1
      Shared Example Group: "it runs" called from ./spec/commands/exec_spec.rb:688
      # ./spec/commands/exec_spec.rb:627:in `block (4 levels) in <top (required)>'
      # ./spec/spec_helper.rb:110:in `block (2 levels) in <top (required)>'
      # ./spec/spec_helper.rb:77:in `block (2 levels) in <top (required)>'
      # ./spec/support/rubygems_ext.rb:81:in `load'
      # ./spec/support/rubygems_ext.rb:81:in `gem_load_and_activate'
      # ./spec/support/rubygems_ext.rb:44:in `gem_load'

  42) bundle exec `load`ing a ruby file instead of `exec`ing the executable exits by SignalException behaves like it runs like a normally executed executable
      Failure/Error: expect(exitstatus).to eq(exit_code) if exitstatus

        expected: 143
             got: 1

        (compared using ==)

        Commands:
        $ /usr/bin/ruby -I/bundler/lib -e  \
          <<EOS
                    require "bundler"
                    begin
                      puts Bundler.bundle_path
                    rescue Bundler::GemfileNotFound
                      ENV["BUNDLE_GEMFILE"] = "Gemfile"
                      retry
                    end

        EOS
        /bundler/tmp/1/gems/system
        # $? => 0

        $ /usr/bin/ruby --disable-gems -r/bundler/spec/support/rubygems -S gem --backtrace install \
          --no-document --ignore-dependencies /bundler/tmp/1/gems/remote1/gems/rack-1.0.0.gem
        Rack's post install message
        Successfully installed rack-1.0.0
        1 gem installed
        # $? => 0

        $ /usr/bin/ruby --disable-gems -r/bundler/spec/support/rubygems -S gem --backtrace install \
          --no-document --ignore-dependencies /bundler/tmp/1/gems/remote1/gems/rack-0.9.1.gem
        Rack's post install message
        Successfully installed rack-0.9.1
        1 gem installed
        # $? => 0

        $ /usr/bin/ruby --disable-gems -I/bundler/lib:/bundler/spec -rsupport/rubygems -rsupport/hax \
          -r/bundler/spec/support/artifice/fail /bundler/exe/bundle install --retry 0
        Resolving dependencies...
        Using bundler 2.1.0.pre.2
        Using rack 1.0.0
        Bundle complete! 1 Gemfile dependency, 2 gems now installed.
        Use `bundle info [gemname]` to see where a bundled gem is installed.
        Don't run Bundler as root. Bundler can ask for sudo if it is needed, and installing your bundle as root will break this application for all non-root users on this machine.
        # $? => 0

        $ /usr/bin/ruby --disable-gems -I/bundler/lib:/bundler/spec -rsupport/rubygems -rsupport/hax \
          -r/bundler/spec/support/artifice/fail /bundler/exe/bundle exec \
          /bundler/tmp/1/bundled_app/ruby_executable arg1 arg2
        EXEC: load
        ARGS: /bundler/tmp/1/bundled_app/ruby_executable arg1 arg2
        RACK: 1.0.0
        ps: unrecognized option: p
        BusyBox v1.30.1 (2019-06-12 17:51:55 UTC) multi-call binary.

        Usage: ps [-o COL1,COL2=HEADER]

        Show list of processes

        	-o COL1,COL2=HEADER	Select columns for display
        bundler: failed to load command: /bundler/tmp/1/bundled_app/ruby_executable (/bundler/tmp/1/bundled_app/ruby_executable)
        NoMethodError: undefined method `strip' for nil:NilClass
          /bundler/tmp/1/bundled_app/ruby_executable:8:in `<top (required)>'
        # $? => 1
      Shared Example Group: "it runs" called from ./spec/commands/exec_spec.rb:660
      # ./spec/commands/exec_spec.rb:626:in `block (4 levels) in <top (required)>'
      # ./spec/spec_helper.rb:110:in `block (2 levels) in <top (required)>'
      # ./spec/spec_helper.rb:77:in `block (2 levels) in <top (required)>'
      # ./spec/support/rubygems_ext.rb:81:in `load'
      # ./spec/support/rubygems_ext.rb:81:in `gem_load_and_activate'
      # ./spec/support/rubygems_ext.rb:44:in `gem_load'

  43) bundle exec `load`ing a ruby file instead of `exec`ing the executable raises behaves like it runs like a normally executed executable
      Failure/Error: expect(err).to eq(expected_err)

        expected: "bundler: failed to load command: /bundler/tmp/1/bundled_app/ruby_executable (/bundler/tmp/1/bundled_...utable)\nRuntimeError: ERROR\n  /bundler/tmp/1/bundled_app/ruby_executable:10:in `<top (required)>'"
             got: "ps: unrecognized option: p\nBusyBox v1.30.1 (2019-06-12 17:51:55 UTC) multi-call binary.\n\nUsage: p...thod `strip' for nil:NilClass\n  /bundler/tmp/1/bundled_app/ruby_executable:8:in `<top (required)>'"

        (compared using ==)

        Diff:

        @@ -1,4 +1,12 @@
        +ps: unrecognized option: p
        +BusyBox v1.30.1 (2019-06-12 17:51:55 UTC) multi-call binary.
        +
        +Usage: ps [-o COL1,COL2=HEADER]
        +
        +Show list of processes
        +
        +	-o COL1,COL2=HEADER	Select columns for display
         bundler: failed to load command: /bundler/tmp/1/bundled_app/ruby_executable (/bundler/tmp/1/bundled_app/ruby_executable)
        -RuntimeError: ERROR
        -  /bundler/tmp/1/bundled_app/ruby_executable:10:in `<top (required)>'
        +NoMethodError: undefined method `strip' for nil:NilClass
        +  /bundler/tmp/1/bundled_app/ruby_executable:8:in `<top (required)>'

        Commands:
        $ /usr/bin/ruby -I/bundler/lib -e  \
          <<EOS
                    require "bundler"
                    begin
                      puts Bundler.bundle_path
                    rescue Bundler::GemfileNotFound
                      ENV["BUNDLE_GEMFILE"] = "Gemfile"
                      retry
                    end

        EOS
        /bundler/tmp/1/gems/system
        # $? => 0

        $ /usr/bin/ruby --disable-gems -r/bundler/spec/support/rubygems -S gem --backtrace install \
          --no-document --ignore-dependencies /bundler/tmp/1/gems/remote1/gems/rack-1.0.0.gem
        Rack's post install message
        Successfully installed rack-1.0.0
        1 gem installed
        # $? => 0

        $ /usr/bin/ruby --disable-gems -r/bundler/spec/support/rubygems -S gem --backtrace install \
          --no-document --ignore-dependencies /bundler/tmp/1/gems/remote1/gems/rack-0.9.1.gem
        Rack's post install message
        Successfully installed rack-0.9.1
        1 gem installed
        # $? => 0

        $ /usr/bin/ruby --disable-gems -I/bundler/lib:/bundler/spec -rsupport/rubygems -rsupport/hax \
          -r/bundler/spec/support/artifice/fail /bundler/exe/bundle install --retry 0
        Resolving dependencies...
        Using bundler 2.1.0.pre.2
        Using rack 1.0.0
        Bundle complete! 1 Gemfile dependency, 2 gems now installed.
        Use `bundle info [gemname]` to see where a bundled gem is installed.
        Don't run Bundler as root. Bundler can ask for sudo if it is needed, and installing your bundle as root will break this application for all non-root users on this machine.
        # $? => 0

        $ /usr/bin/ruby --disable-gems -I/bundler/lib:/bundler/spec -rsupport/rubygems -rsupport/hax \
          -r/bundler/spec/support/artifice/fail /bundler/exe/bundle exec \
          /bundler/tmp/1/bundled_app/ruby_executable arg1 arg2
        EXEC: load
        ARGS: /bundler/tmp/1/bundled_app/ruby_executable arg1 arg2
        RACK: 1.0.0
        ps: unrecognized option: p
        BusyBox v1.30.1 (2019-06-12 17:51:55 UTC) multi-call binary.

        Usage: ps [-o COL1,COL2=HEADER]

        Show list of processes

        	-o COL1,COL2=HEADER	Select columns for display
        bundler: failed to load command: /bundler/tmp/1/bundled_app/ruby_executable (/bundler/tmp/1/bundled_app/ruby_executable)
        NoMethodError: undefined method `strip' for nil:NilClass
          /bundler/tmp/1/bundled_app/ruby_executable:8:in `<top (required)>'
        # $? => 1
      Shared Example Group: "it runs" called from ./spec/commands/exec_spec.rb:679
      # ./spec/commands/exec_spec.rb:627:in `block (4 levels) in <top (required)>'
      # ./spec/spec_helper.rb:110:in `block (2 levels) in <top (required)>'
      # ./spec/spec_helper.rb:77:in `block (2 levels) in <top (required)>'
      # ./spec/support/rubygems_ext.rb:81:in `load'
      # ./spec/support/rubygems_ext.rb:81:in `gem_load_and_activate'
      # ./spec/support/rubygems_ext.rb:44:in `gem_load'

  44) bundle exec `load`ing a ruby file instead of `exec`ing regarding $0 and __FILE__ behaves like it runs like a normally executed executable
      Failure/Error: expect(exitstatus).to eq(exit_code) if exitstatus

        expected: 0
             got: 1

        (compared using ==)

        Commands:
        $ /usr/bin/ruby -I/bundler/lib -e  \
          <<EOS
                    require "bundler"
                    begin
                      puts Bundler.bundle_path
                    rescue Bundler::GemfileNotFound
                      ENV["BUNDLE_GEMFILE"] = "Gemfile"
                      retry
                    end

        EOS
        /bundler/tmp/1/gems/system
        # $? => 0

        $ /usr/bin/ruby --disable-gems -r/bundler/spec/support/rubygems -S gem --backtrace install \
          --no-document --ignore-dependencies /bundler/tmp/1/gems/remote1/gems/rack-1.0.0.gem
        Rack's post install message
        Successfully installed rack-1.0.0
        1 gem installed
        # $? => 0

        $ /usr/bin/ruby --disable-gems -r/bundler/spec/support/rubygems -S gem --backtrace install \
          --no-document --ignore-dependencies /bundler/tmp/1/gems/remote1/gems/rack-0.9.1.gem
        Rack's post install message
        Successfully installed rack-0.9.1
        1 gem installed
        # $? => 0

        $ /usr/bin/ruby --disable-gems -I/bundler/lib:/bundler/spec -rsupport/rubygems -rsupport/hax \
          -r/bundler/spec/support/artifice/fail /bundler/exe/bundle install --retry 0
        Resolving dependencies...
        Using bundler 2.1.0.pre.2
        Using rack 1.0.0
        Bundle complete! 1 Gemfile dependency, 2 gems now installed.
        Use `bundle info [gemname]` to see where a bundled gem is installed.
        Don't run Bundler as root. Bundler can ask for sudo if it is needed, and installing your bundle as root will break this application for all non-root users on this machine.
        # $? => 0

        $ /usr/bin/ruby --disable-gems -I/bundler/lib:/bundler/spec -rsupport/rubygems -rsupport/hax \
          -r/bundler/spec/support/artifice/fail /bundler/exe/bundle exec \
          /bundler/tmp/1/bundled_app/ruby_executable arg1 arg2
        EXEC: load
        ARGS: /bundler/tmp/1/bundled_app/ruby_executable arg1 arg2
        RACK: 1.0.0
        ps: unrecognized option: p
        BusyBox v1.30.1 (2019-06-12 17:51:55 UTC) multi-call binary.

        Usage: ps [-o COL1,COL2=HEADER]

        Show list of processes

        	-o COL1,COL2=HEADER	Select columns for display
        bundler: failed to load command: /bundler/tmp/1/bundled_app/ruby_executable (/bundler/tmp/1/bundled_app/ruby_executable)
        NoMethodError: undefined method `strip' for nil:NilClass
          /bundler/tmp/1/bundled_app/ruby_executable:8:in `<top (required)>'
        # $? => 1
      Shared Example Group: "it runs" called from ./spec/commands/exec_spec.rb:764
      # ./spec/commands/exec_spec.rb:626:in `block (4 levels) in <top (required)>'
      # ./spec/spec_helper.rb:110:in `block (2 levels) in <top (required)>'
      # ./spec/spec_helper.rb:77:in `block (2 levels) in <top (required)>'
      # ./spec/support/rubygems_ext.rb:81:in `load'
      # ./spec/support/rubygems_ext.rb:81:in `gem_load_and_activate'
      # ./spec/support/rubygems_ext.rb:44:in `gem_load'

  45) bundle exec `load`ing a ruby file instead of `exec`ing regarding $0 and __FILE__ when the path is relative behaves like it runs like a normally executed executable
      Failure/Error: expect(exitstatus).to eq(exit_code) if exitstatus

        expected: 0
             got: 1

        (compared using ==)

        Commands:
        $ /usr/bin/ruby -I/bundler/lib -e  \
          <<EOS
                    require "bundler"
                    begin
                      puts Bundler.bundle_path
                    rescue Bundler::GemfileNotFound
                      ENV["BUNDLE_GEMFILE"] = "Gemfile"
                      retry
                    end

        EOS
        /bundler/tmp/1/gems/system
        # $? => 0

        $ /usr/bin/ruby --disable-gems -r/bundler/spec/support/rubygems -S gem --backtrace install \
          --no-document --ignore-dependencies /bundler/tmp/1/gems/remote1/gems/rack-1.0.0.gem
        Rack's post install message
        Successfully installed rack-1.0.0
        1 gem installed
        # $? => 0

        $ /usr/bin/ruby --disable-gems -r/bundler/spec/support/rubygems -S gem --backtrace install \
          --no-document --ignore-dependencies /bundler/tmp/1/gems/remote1/gems/rack-0.9.1.gem
        Rack's post install message
        Successfully installed rack-0.9.1
        1 gem installed
        # $? => 0

        $ /usr/bin/ruby --disable-gems -I/bundler/lib:/bundler/spec -rsupport/rubygems -rsupport/hax \
          -r/bundler/spec/support/artifice/fail /bundler/exe/bundle install --retry 0
        Resolving dependencies...
        Using bundler 2.1.0.pre.2
        Using rack 1.0.0
        Bundle complete! 1 Gemfile dependency, 2 gems now installed.
        Use `bundle info [gemname]` to see where a bundled gem is installed.
        Don't run Bundler as root. Bundler can ask for sudo if it is needed, and installing your bundle as root will break this application for all non-root users on this machine.
        # $? => 0

        $ /usr/bin/ruby --disable-gems -I/bundler/lib:/bundler/spec -rsupport/rubygems -rsupport/hax \
          -r/bundler/spec/support/artifice/fail /bundler/exe/bundle exec ruby_executable arg1 arg2
        EXEC: load
        ARGS: ruby_executable arg1 arg2
        RACK: 1.0.0
        ps: unrecognized option: p
        BusyBox v1.30.1 (2019-06-12 17:51:55 UTC) multi-call binary.

        Usage: ps [-o COL1,COL2=HEADER]

        Show list of processes

        	-o COL1,COL2=HEADER	Select columns for display
        bundler: failed to load command: ruby_executable (ruby_executable)
        NoMethodError: undefined method `strip' for nil:NilClass
          ruby_executable:8:in `<top (required)>'
        # $? => 1
      Shared Example Group: "it runs" called from ./spec/commands/exec_spec.rb:769
      # ./spec/commands/exec_spec.rb:626:in `block (4 levels) in <top (required)>'
      # ./spec/spec_helper.rb:110:in `block (2 levels) in <top (required)>'
      # ./spec/spec_helper.rb:77:in `block (2 levels) in <top (required)>'
      # ./spec/support/rubygems_ext.rb:81:in `load'
      # ./spec/support/rubygems_ext.rb:81:in `gem_load_and_activate'
      # ./spec/support/rubygems_ext.rb:44:in `gem_load'

  46) bundle exec `load`ing a ruby file instead of `exec`ing behaves like it runs like a normally executed executable
      Failure/Error: expect(exitstatus).to eq(exit_code) if exitstatus

        expected: 0
             got: 1

        (compared using ==)

        Commands:
        $ /usr/bin/ruby -I/bundler/lib -e  \
          <<EOS
                    require "bundler"
                    begin
                      puts Bundler.bundle_path
                    rescue Bundler::GemfileNotFound
                      ENV["BUNDLE_GEMFILE"] = "Gemfile"
                      retry
                    end

        EOS
        /bundler/tmp/1/gems/system
        # $? => 0

        $ /usr/bin/ruby --disable-gems -r/bundler/spec/support/rubygems -S gem --backtrace install \
          --no-document --ignore-dependencies /bundler/tmp/1/gems/remote1/gems/rack-1.0.0.gem
        Rack's post install message
        Successfully installed rack-1.0.0
        1 gem installed
        # $? => 0

        $ /usr/bin/ruby --disable-gems -r/bundler/spec/support/rubygems -S gem --backtrace install \
          --no-document --ignore-dependencies /bundler/tmp/1/gems/remote1/gems/rack-0.9.1.gem
        Rack's post install message
        Successfully installed rack-0.9.1
        1 gem installed
        # $? => 0

        $ /usr/bin/ruby --disable-gems -I/bundler/lib:/bundler/spec -rsupport/rubygems -rsupport/hax \
          -r/bundler/spec/support/artifice/fail /bundler/exe/bundle install --retry 0
        Resolving dependencies...
        Using bundler 2.1.0.pre.2
        Using rack 1.0.0
        Bundle complete! 1 Gemfile dependency, 2 gems now installed.
        Use `bundle info [gemname]` to see where a bundled gem is installed.
        Don't run Bundler as root. Bundler can ask for sudo if it is needed, and installing your bundle as root will break this application for all non-root users on this machine.
        # $? => 0

        $ /usr/bin/ruby --disable-gems -I/bundler/lib:/bundler/spec -rsupport/rubygems -rsupport/hax \
          -r/bundler/spec/support/artifice/fail /bundler/exe/bundle exec \
          /bundler/tmp/1/bundled_app/ruby_executable arg1 arg2
        EXEC: load
        ARGS: /bundler/tmp/1/bundled_app/ruby_executable arg1 arg2
        RACK: 1.0.0
        ps: unrecognized option: p
        BusyBox v1.30.1 (2019-06-12 17:51:55 UTC) multi-call binary.

        Usage: ps [-o COL1,COL2=HEADER]

        Show list of processes

        	-o COL1,COL2=HEADER	Select columns for display
        bundler: failed to load command: /bundler/tmp/1/bundled_app/ruby_executable (/bundler/tmp/1/bundled_app/ruby_executable)
        NoMethodError: undefined method `strip' for nil:NilClass
          /bundler/tmp/1/bundled_app/ruby_executable:8:in `<top (required)>'
        # $? => 1
      Shared Example Group: "it runs" called from ./spec/commands/exec_spec.rb:632
      # ./spec/commands/exec_spec.rb:626:in `block (4 levels) in <top (required)>'
      # ./spec/spec_helper.rb:110:in `block (2 levels) in <top (required)>'
      # ./spec/spec_helper.rb:77:in `block (2 levels) in <top (required)>'
      # ./spec/support/rubygems_ext.rb:81:in `load'
      # ./spec/support/rubygems_ext.rb:81:in `gem_load_and_activate'
      # ./spec/support/rubygems_ext.rb:44:in `gem_load'

Finished in 26 minutes 39 seconds (files took 1.02 seconds to load)
2739 examples, 46 failures, 4 pending

Failed examples:

rspec ./spec/commands/clean_spec.rb:545 # bundle clean when missing permissions returns a helpful error message
rspec ./spec/bundler/bundler_spec.rb:370 # Bundler#requires_sudo? bundle_path exists and is unwritable is expected to equal true
rspec ./spec/bundler/bundler_spec.rb:399 # Bundler#requires_sudo? path writability unwritable paths should return true and display warn message
rspec ./spec/bundler/bundler_spec.rb:341 # Bundler#requires_sudo? bundle_path doesn't exist and parent dir can't be written is expected to equal true
rspec ./spec/install/gemfile/path_spec.rb:351 # bundle install with explicit source paths handles directories in bin/
rspec ./spec/install/gemfile/path_spec.rb:686 # bundle install with explicit source paths gem install hooks runs post-install hooks
rspec ./spec/install/gemfile/path_spec.rb:666 # bundle install with explicit source paths gem install hooks runs pre-install hooks
rspec ./spec/commands/doctor_spec.rb:95 # bundle doctor when home contains files that are not readable/writable when home contains files that are not owned by the current process exits with an error if home contains files that are not readable/writable and are not owned by the current user
rspec ./spec/commands/doctor_spec.rb:105 # bundle doctor when home contains files that are not readable/writable when home contains files that are not owned by the current process exits with a warning if home contains files that are read/write but not owned by current user
rspec ./spec/commands/package_spec.rb:302 # bundle install with gem sources when cached and locked does not reinstall already-installed gems
rspec ./spec/runtime/setup_spec.rb:813 # Bundler.setup with bundler is located in symlinked GEM_HOME should not remove itself from the LOAD_PATH and require a different copy of 'bundler/setup'
rspec ./spec/commands/init_spec.rb:47 # bundle init when the dir is not writable by the current user notifies the user that it can not write to it
rspec ./spec/commands/binstubs_spec.rb:129 # bundle binstubs <gem> when the gem exists in the lockfile the bundle binstub runs bundler
rspec ./spec/commands/binstubs_spec.rb:182 # bundle binstubs <gem> when the gem exists in the lockfile the bundle binstub when update --bundler is called calls through to the latest bundler version
rspec ./spec/commands/binstubs_spec.rb:169 # bundle binstubs <gem> when the gem exists in the lockfile the bundle binstub when a lockfile exists with a locked bundler version runs the correct version of bundler when the version is a pre-release
rspec ./spec/commands/binstubs_spec.rb:152 # bundle binstubs <gem> when the gem exists in the lockfile the bundle binstub when a lockfile exists with a locked bundler version runs the correct version of bundler when the version is older and a different major
rspec ./spec/commands/binstubs_spec.rb:205 # bundle binstubs <gem> when the gem exists in the lockfile the bundle binstub using another binstub loads all gems
rspec ./spec/commands/install_spec.rb:548 # bundle install with gem sources when bundle path does not have write access should display a proper message to explain the problem
rspec ./spec/commands/install_spec.rb:582 # bundle install with gem sources when bundle install is executed with unencoded authentication should display a helpful message explaining how to fix it
rspec ./spec/install/gems/compact_index_spec.rb:525 # compact index api installs the binstubs
rspec ./spec/other/cli_dispatch_spec.rb:4 # bundle command names work when given fully
rspec ./spec/other/cli_dispatch_spec.rb:10 # bundle command names work when not ambiguous
rspec ./spec/runtime/executable_spec.rb:145 # Running bin/* commands use BUNDLE_GEMFILE gemfile for binstub
rspec ./spec/install/gemfile/git_spec.rb:1071 # bundle install with git sources gem install hooks runs post-install hooks
rspec ./spec/install/gemfile/git_spec.rb:1051 # bundle install with git sources gem install hooks runs pre-install hooks
rspec ./spec/install/gemfile/git_spec.rb:500 # bundle install with git sources when specifying local override explodes and gives correct solution if given path does not exist on install
rspec ./spec/install/gemfile/git_spec.rb:521 # bundle install with git sources when specifying local override explodes and gives correct solution if branch is not given on install
rspec ./spec/install/gemfile/git_spec.rb:217 # bundle install with git sources when specifying a revision works when the revision is a non-head ref
rspec ./spec/install/gemfile/git_spec.rb:247 # bundle install with git sources when specifying a revision works when the revision is a non-head ref and it was previously downloaded
rspec ./spec/install/gemfile/git_spec.rb:201 # bundle install with git sources when specifying a revision works when the revision is a symbol
rspec ./spec/install/gems/dependency_api_spec.rb:499 # gemcutter's dependency API installs the binstubs
rspec ./spec/update/git_spec.rb:77 # bundle update git sources notices when you change the repo url in the Gemfile
rspec ./spec/install/gemspecs_spec.rb:11 # bundle install when a gem has a YAML gemspec still installs correctly
rspec ./spec/install/gemspecs_spec.rb:20 # bundle install when a gem has a YAML gemspec still installs correctly when using path
rspec ./spec/commands/exec_spec.rb:58 # bundle exec respects custom process title when loading through ruby
rspec './spec/commands/exec_spec.rb[1:28:10:1:1]' # bundle exec `load`ing a ruby file instead of `exec`ing when the executable exits non-zero via at_exit behaves like it runs like a normally executed executable
rspec './spec/commands/exec_spec.rb[1:28:11:1:1]' # bundle exec `load`ing a ruby file instead of `exec`ing when disable_exec_load is set behaves like it runs like a normally executed executable
rspec './spec/commands/exec_spec.rb[1:28:2:2:1:1]' # bundle exec `load`ing a ruby file instead of `exec`ing the executable exits explicitly with exit 99 behaves like it runs like a normally executed executable
rspec './spec/commands/exec_spec.rb[1:28:2:1:1:1]' # bundle exec `load`ing a ruby file instead of `exec`ing the executable exits explicitly with exit 0 behaves like it runs like a normally executed executable
rspec './spec/commands/exec_spec.rb[1:28:7:1:1]' # bundle exec `load`ing a ruby file instead of `exec`ing when the file uses the current ruby shebang behaves like it runs like a normally executed executable
rspec './spec/commands/exec_spec.rb[1:28:6:1:1]' # bundle exec `load`ing a ruby file instead of `exec`ing the executable raises an error without a backtrace behaves like it runs like a normally executed executable
rspec './spec/commands/exec_spec.rb[1:28:3:1:1]' # bundle exec `load`ing a ruby file instead of `exec`ing the executable exits by SignalException behaves like it runs like a normally executed executable
rspec './spec/commands/exec_spec.rb[1:28:5:1:1]' # bundle exec `load`ing a ruby file instead of `exec`ing the executable raises behaves like it runs like a normally executed executable
rspec './spec/commands/exec_spec.rb[1:28:12:1:1]' # bundle exec `load`ing a ruby file instead of `exec`ing regarding $0 and __FILE__ behaves like it runs like a normally executed executable
rspec './spec/commands/exec_spec.rb[1:28:12:2:1:1]' # bundle exec `load`ing a ruby file instead of `exec`ing regarding $0 and __FILE__ when the path is relative behaves like it runs like a normally executed executable
rspec './spec/commands/exec_spec.rb[1:28:1:1]' # bundle exec `load`ing a ruby file instead of `exec`ing behaves like it runs like a normally executed executable

Randomized with seed 62786

rake aborted!
Command failed with status (1): [bin/rspec...]
/bundler/Rakefile:24:in `block in <top (required)>'
/bundler/Rakefile:15:in `block in invoke'
/bundler/Rakefile:14:in `invoke'
/bundler/spec/support/rubygems_ext.rb:81:in `load'
/bundler/spec/support/rubygems_ext.rb:81:in `gem_load_and_activate'
/bundler/spec/support/rubygems_ext.rb:44:in `gem_load'
Tasks: TOP => spec
(See full trace by running task with --trace)


Upgrade python to 3.11 and update action versions

What and why?
Upgrades python version to 3.11 and upgrades checkout and python-setup versions to something more current.
How to test?
Trello

/deploy manna

/deploy robinm3


Fix creating keys with Passphrase.emptyPassphrase()

Previously the code supplied null to BouncyCastle's encryptor/decryptor builder's build method and that caused
NullPointerException to be thrown.
The fix checks if the passphrase is empty and omits the BouncyCastle builder in that case.
Fixes #16.

Haha, I'm literally just writing the exact same fix :D

Haha, lol. Okay I just couldn't resist! :)


Datepicker doesn't refresh with new options on emit

I think this is a common use case, to have two datepickers linked for a startdate and endate. In my case I'd like to update the 2nd one to have a min date based on the selection of the first. So I have it set up like this:
<input id="endDate" name="endDate" [(ngModel)]="endDate" materialize="pickadate"  (ngModelChange)="endDateChange()" [materializeActions]="endActions" [materializeParams]="[endOptions]"  type="text" />
then when startDateChange() is called from first datepicker, I do something like this:
startDateChange() {
  let newOptions = {min: '2017-12-25'};
  this.endActions.emit({action: 'pickadate', params: [newOptions]});
}

after this is called, the new min-date is not updated on the endDate datepicker. Am I doing this wrong?

Sorry I think this is actually the same as #280 -- anyone else have any other tips? Trying to avoid using jQuery


Nested Type Annotations

Good day,
I'm pretty new to Pkl, and despite perusing the docs, can't find a working solution for the following:
I'm trying to generate a template for an object of the following form:
table String {
    mapping String {
            gp_table: String
            gp_field: String
            bc_table: String
            bc_field: String
    }
}

In the above scenario, any table instances, must be able to contain any number of mappings.
The solution I designed got as far as, a mapping.pkl file:
module Mapping

class Mapping{
    gp_table: String
    gp_field: String
    bc_table: String
    bc_field: String
}

And an instance as follows:
import "mappings.pkl"

salesInvoices {
    documentNo_to_invoiceNumber: Mapping = new {
        ["gp_table"] = "RM20101"
        ["gp_field"] = "DOCNUMBR"
        ["bc_table"] = "salesInvoices"
        ["bc_field"] = "externalDocumentNumber"
    }
}

The above only works when the mapping isn't contained within the larger salesInvoices object, and either way, I will only be able to have a single mapping in this manner.
Is there a clever work around that I'm missing? Or rather, what is the best way to go about this? I saw the following, but in this instance I think the object only required a single instance of the nested object.

Even if there was a solution as the original poster said here, but with an undefined number of internal objects of the declared type, that would be wonderful. Not looking for an elegant solution.

I guess you want something like the following:
mappings.pkl:
tables: Mapping<String, DbTable>

typealias DbTable = Mapping<String, DbMapping>

class DbMapping {
  gp_table: String
  gp_field: String
  bc_table: String
  bc_field: String
}

amends "mappings.pkl"

tables {
  ["salesInvoices"] {
    ["documentNo_to_invoiceNumber"] {
      gp_table = "RM20101"
      gp_field = "DOCNUMBR"
      bc_table = "salesInvoices"
      bc_field = "externalDocumentNumber"
    }
  }
}

PS: This is a better fit for "Discussions" than "Issues".

The type alias only improves readability and reusability.
Otherwise it's the same as tables: Mapping<String, Mapping<String, DbMapping>>.
A Pkl Mapping is often called "map" in other programming languages.

There is also a Map type in Pkl with an richer API 🤓

Entirely with @translatenix's suggestions (both code and Discussion; but now that it's here, that's alright... do please close this Issue when you're fully satisfied, @yesteryearer).
Since you're talking about database tables and fields, I bet there are restrictions on the names of those things. It depends entirely on which database you're using what those restrictions are, but just for the example, I'm assuming names may not contain whitespace. This is to demonstrate type constraints and to further illustrate @translatenix's point about typealiases:
tables: Mapping<String, DbTable>

typealias DbTable = Mapping<String, DbMapping>

/// The database can't take arbitrary strings as names, so names must be restricted.
typealias DbName = String(!contains(" "))

class DbMapping {
  gp_table: DbName
  gp_field: DbName
  bc_table: DbName
  bc_field: DbName
}

So to clarify, the reason I originally posted this here was because of the following error:
–– Pkl Error ––
A non-local object property cannot have a type annotation.

At which point I didn't know a workaround exists.
Thanks for the help.


Delete policy vs delete locator?

The first bullet point under considerations:

You cannot delete an AssetDeliveryPolicy associated with an asset while an OnDemand (streaming) locator exists for that asset. The recommendation is to remove the policy from the asset before deleting the policy.

Remove the policy before deleting the policy? I think this is supposed to be 'remove the locator from the asset before deleting the policy'

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 56bb6999-8bf4-2568-3fc2-5323b04a65f8
Version Independent ID: 47318fca-85e1-6820-8530-db86cdd83b66
Content
Content Source
Service: media-services

@brouwer  Thanks for the feedback, I assigned the issue to the content team.

@mingfeiy @SyntaxC4 @Juliako - We are not able to assign directly to @mingfeiy in the GitHub UI, so assigning to content team for Media Services to ensure follow up on this issue.

Hi @brouwer ,
The recommendation is to delete all of the streaming locators associated with the asset and then delete the AssetDeliveryPolicy.
You can create new streaming locators if desired, perhaps with a new AssetDeliveryPolicy.
I will update the document with this information.
Thank you,
Julia

#fixes MicrosoftDocs/azure-docs#5224

#please-close

@brouwer
We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


api.stackstorm.com is unsync with openapi.yaml (CD)

In the openapi spec there are several instances of a block called x-parameters. These are "vendor extensions" according the OpenAPI spec https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#patterned-objects .
The API documentation generator is leaving these out, so there's no way to know they exist without looking directly at the spec.
Example:

API docs for POST /auth/v1/tokens https://api.stackstorm.com/auth/v1/tokens/#/token_controller.post
Spec for POST /auth/v1/tokens https://github.com/StackStorm/st2/blob/master/st2common/st2common/openapi.yaml#L3991-L4020
You can see that the parameters remote_addr and remote_user are missing from the docus, even though they're in the spec.

Confirming there is unsync between https://api.stackstorm.com/ and openapi.yaml.
After looking further, last update for https://api.stackstorm.com is Nov 3, 2017, according to https://github.com/StackStorm/st2/pull/4046#issuecomment-374579734.

We'll need to add re-generation task for api.stackstorm.com in CircleCI if openapi.yaml content was changed (on master build, similar to deploy job).

@enykeev and I had a chat and we decided on the following:

We'll ship updated documentation on every release. Having API documentation from master is a stretch goal. We can use api-staging.stackstorm.com for this if needed.

In terms of how we are going to automate this:

We are going to add a task in st2cd release automation to invoke a circle build on https://github.com/StackStorm/st2apidocs

There are some minor improvements we decided to do. I'll link PRs here when I make those changes.

Also, I created api-unstable.stackstorm.com to show master API documentation. When DNS propagates, this should work.

@lakshmi-kannan For api-unstable can you please include the Terraform change in: https://github.com/StackStorm/ops-infra/blob/master/terraform/api.stackstorm.com.tf ?
Considering there is already infra-as-code for api.stackstorm.com, there would be no good excuse to skip the api-unstable ;)

@armab Didn't realize we had a tf for this :). Would have made my life easier instead of figuring out AWS UI manually. Let me add it.

https://github.com/StackStorm/st2apidocs is responsible for the https://api.stackstorm.com/ generation.
Looks like the build in https://github.com/StackStorm/st2apidocs is still broken that results in CD failure to generate and upload the documentation. See https://github.com/StackStorm/st2apidocs/issues/9 for more info.

Thanks to @Sheshagiri work https://github.com/StackStorm/st2apidocs/issues/9 https://github.com/StackStorm/st2apidocs/pull/11 https://github.com/StackStorm/st2apidocgen/pull/9, API docs generation and deployments are now working.

stable API doc, based on current v3.2.0 branch: https://api.stackstorm.com/
latest evelopment API doc, based on master branch: https://api-unstable.stackstorm.com/


Cant go get id3-go on windows

When i try to do a go get github.com/mikkyang/id3-go on windows it fails. I just install gcc with MinGW and it is a fresh install so i doubt it come from this part.
go get -x github.com/mikkyang/id3-go
WORK=C:\Users\admin\AppData\Local\Temp\go-build230481106
mkdir -p $WORK\github.com\djimenez\iconv-go\_obj\
mkdir -p $WORK\github.com\djimenez\
cd D:\Pro\go\src\github.com\djimenez\iconv-go
CGO_LDFLAGS="-g" "-O2" "-liconv" "C:\\Go\\pkg\\tool\\windows_amd64\\cgo.exe" -objdir "C:\\Users\\admin\\AppData
\\Local\\Temp\\go-build230481106\\github.com\\djimenez\\iconv-go\\_obj\\" -importpath github.com/djimenez/iconv
-go -- -I "C:\\Users\\admin\\AppData\\Local\\Temp\\go-build230481106\\github.com\\djimenez\\iconv-go\\_obj\\" c
onverter.go
go build github.com/djimenez/iconv-go: C:\Go\pkg\tool\windows_amd64\cgo.exe: exit status 2

Thanks for the feedback. Unfortunately, I don't own any Windows products, so I wouldn't be able to personally reproduce this error and debug it. Have you had this error with any other Go packages? Sorry that I can't help you with this.

@Jbbouille the build fails on github.com/djimenez/iconv-go maybe ask there or find a suitable replacement for that dependency here and build conditionally.

Has anyone found a solution to this yet? I am completely stuck on the same issue.

Unfortunately, it's fairly unlikely to be fixed, as it would require ripping out everything to do with iconv and using a different, cross-platform approach.


43 shape mutator

Fixes #43
Includes the adjustment of reducing the margin space within the mutator menu for ALL mutator UI while also removing blocks from the mutator UI 'flyout' once they are dragged into the menu 'workspace' ONLY for attributes within the shape blocks.
For consideration: This was never discussed en masse, however, @codestar12 and I thought that changing the icon for the mutator symbol would also be more effective in communicating to users what type of action the menu would have after reviewing some confusion in user tests. We went with a 'plus' icon to show that attributes can be "added" to blocks that have mutators on them and @hgclose agreed it was more effective than the original gear icon which some might find confusing as well as having lots of fine detail for a small icon.

❤ it. Looks great:

Can't wait to see #78 added to this.


Update contribution guidelines regarding local angular-meteor development

https://github.com/Urigo/angular-meteor/blob/master/.github/CONTRIBUTING.md#run-local-angular-meteor-in-your-project
This section needs to be updated since we no longer get angular-meteor from atmosphere.

Awesome work @kamilkisiela ! Thanks


fixed for julia 0.7

at least functions covered by test

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@f55b305). Click here to learn what that means.
The diff coverage is 100%.

@@            Coverage Diff            @@
##             master       #1   +/-   ##
=========================================
  Coverage          ?   87.16%
=========================================
  Files             ?        1
  Lines             ?      148
  Branches          ?        0
=========================================
  Hits              ?      129
  Misses            ?       19
  Partials          ?        0

Impacted Files
Coverage Δ

src/TransformUtils.jl
87.16% <100%> (ø)

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 f55b305...3c4d863. Read the comment docs.

@dehann the quick way of fixing warnings and errors for julia 0.7/1.0, at least functions covered by test


[oslog][stdlib-private] Remove OSLogByteBufferBuilder type from the new OSLog library implementation.

This PR modifies the implementation of the new OSLog library so that the type: OSLogByteBufferBuilder is no longer needed. This would make backward deployment of code using the new log APIs easier, besides other minor benefits.

@swift-ci Please test and merger


stringifyQuery cannot be overridden

Here is a demo repo. As you see custom stringifyQuery method is never being called.

useQueries is applied internally by the router. The router component <Router> passes the query configuration from its props.
In other words, don't use useQueries with <Router>, but pass your custom parseQueryString and stringifyQuery as props: <Router parseQueryString={..} stringifyQuery={...} />


ni:// URI should not escape commas in query-portion

Per RFC-3986 (which RFC-6920 delegates to for query-part construction), URI schemes should treat a comma (",") as a reserved character separator in the query-portion of the URI, and should not escape them.
Currently, however, NamedInformationUri.java URL-encodes commas in the query-portion of an ni://-schemed URI when there are multiple instances of a given "key" (e.g., for conditions with multiple subtypes keys).
For example, the following String is what I would expect NamedInformationUri to construct, per RFC-3986 (notice the plain-text commas):
ni:///sha-256?fpt=ed25519-sha-256,prefix-sha-256,preimage-sha-256
However, the following is what is produced currently:
ni:///sha-256?fpt=ed25519-sha-256%2Cprefix-sha-256%2Cpreimage-sha-256
While not invalid (RFC-3986 seems to allow commas in the query to be encoded depending on context), the above style moves the meaning of the comma separator into the fpt definition, instead of allowing it to be handled via RFC-3986. Here's a SO answer that examines the usage of commas in URI query portions, especially in light of RFC-3986 (which obsoletes RFC-2396 as referenced by the SO question-submitter).
One final rationale to not escape commas is the result of various Java implementations of URL/URI, which do not escape commas in the query-portion when creating URI strings.
For example, here's what Java does with an http URI:
URI.create("https://example.com?foo=ba%20r,baz").getQuery();
// Emits: "foo=ba r,baz"

URI.create("https://example.com?foo=ba%20r,baz").getRawQuery();
// Emits: "foo=ba%20r,baz"

Likewise, Square's OkHttp library has a very nice HttpUrl class (see here for whey they created a new URL class), which emits the following:
HttpUrl.parse("https://example.com?foo=ba%20r,baz").toString();
// Emits: "https://example.com/?foo=ba%20r,baz"

HttpUrl.parse("https://example.com?foo=ba r,baz").toString();
// Emits: "https://example.com/?foo=ba%20r,baz"

Notice things like a "space" are percent-encoded in the query, but commas are not.

@adrianhopebailie I think this test vector in the Javascript project confirms that this issue is a bug (see the URL query-params for the Threshold condition).
I've opened issue 12 in the Crypto-Condition RFC project to get the spec to clarify this behavior, but for now we should probably maintain compatibility with the JS implementation. If you agree, feel free to approve this PR and I'll merge it in.

As discussed on the phone I actually think the JS impl and test vectors are wrong but this is one of those cases where the impl drive the spec so I agree, let's get in sync with the JS and test vectors.

Cool - can you approve the PR (#51) if it looks ok to you?

Closing this since #51 is now merged.


Tokenizer splits all-capital words

Example:
doc = nlp.tokenizer("PAST MEDICAL HISTORY: ")
list(doc)
>>> [P, A, S, T, M, E, D, I, C, A, L, H, I, S, T, O, R, Y, :]

Besides fixing this, I'll set up some tests for this and related expected behavior.

This issue now has several tests for it and the UPPERCASE ISSUE is now resolved.


KYLIN-4132 Kylin needn't use "org.apache.directory.api.util.Strings"

Kylin needn't use "org.apache.directory.api.util.Strings"  to import extra dependency

CI passed. LGTM.

Pull Request Test Coverage Report for Build 5675

0 of 5 (0.0%)  changed or added relevant lines in 2 files are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage remained the same at 27.527%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

server-base/src/main/java/org/apache/kylin/rest/service/ProjectService.java
0
1
0.0%

server-base/src/main/java/org/apache/kylin/rest/service/JobService.java
0
4
0.0%

Files with Coverage Reduction
New Missed Lines
%

server-base/src/main/java/org/apache/kylin/rest/util/QueryRequestLimits.java
1
47.62%

stream-core/src/main/java/org/apache/kylin/stream/core/storage/CheckPointStore.java
2
73.74%

Totals

Change from base Build 5670:
0.0%

Covered Lines:
24298

Relevant Lines:
88270

💛  - Coveralls

LGTM


Renaming too general className with project-specific one (#305)

Issue 😱:
Closes https://github.com/emilkowalski/sonner/issues/305
What has been done ✅:

Replaced the generic .loader class with the project specific .sonner-loader to prevent conflicts with other projects

Screenshots/Videos 🎥:
N/A

@emilkowalski ToastClassnames still has loader as an option. From what I can see it is never used or even a valid option. I left it in since it might be legacy code which could break existing projects. Please advice if I should use this Pull Request to clean it up as well.

@jschoder let's leave loader as is, thank you!


Merge UTscapy files

from https://github.com/secdev/scapy/pull/671 (I am rebasing it).
@guedou @p-l- Please merge

Are they the modified files from the Scapy PR?

yes


feat: auto mode

Description
Restore auto mode for v4 for both Nuxt module and standalone plugin
Linked Issues
#325
Additional context
Was removed in v4.0.0

really waiting for auto to be back


Software you might want to look at.  OpporunitySpace and ZoningCases

From an email of Carlos Moreno<EMAIL_ADDRESS>of Tulsa OK
we're working on a couple different fronts here in Tulsa, OK.

we've started working with OpportunitySpace (http://www.opportunityspace.org/) to help us use their software to visualize public land for sale that's ripe for development, especially in neglected neighborhoods.

we've created an "Open Data Steering Committee" with the City of Tulsa's IT department, where we identify public records that can be made more open, and more easy to use.  https://www.cityoftulsa.org/our-city/open-tulsa/open-tulsa-dataset-list.aspx

last year we created: http://zoningcases.com/ (right now the site is just a demo; it doesn't take live data yet (we're working on that part!)) to use data to inform citizens in their neighborhoods what building, planning, and zoning changes, etc. were going on their neighborhood, on a push notification basis.  this is very similar to the citygram: https://www.citygram.org/ project.

in 2010 the Kauffman Foundation did a comprehensive report on Tulsa's "Entrepreneurial Ecosystem" (http://tulsagew.com/ - scroll to the bottom of the page to download the report) and identified the impact of small, grassroots, community based groups and efforts to encourage small-scale entrepreneurship.  It was generally felt at the time that you could grow organic economic development --  and indeed there has been a lot of positive growth in the past 5 years.  One missing link is that of the cit's leadership (the mayor, city council, the chamber of commerce, etc.) to support these efforts on a policy basis.  I am encouraged that by positive outcomes of our most recent efforts, that this will eventually happen.
@bmejia7 @MichaelRobak

Though you might be interested in
A form-based code is a land development regulation that fosters predictable built results and a high-quality public realm by using physical form (rather than separation of uses) as the organizing principle for the code. A form-based code is a regulation, not a mere guideline, adopted into city, town, or county law. A form-based code offers a powerful alternative to conventional zoning regulation.
http://formbasedcodes.org/definition

Moved to wiki


Assemble artifacts explicitly before publish

Hi!
I made those changes because I have issue with current CI process. Without assemble stage there is no artifacts built and release stage says it unable to find artifacts.

fixed in 1aceefb85b21cecf7dcc0ac68e46168cdc14a01c

for the record, assemble is never called directly due to a weird bug that causes the project compilation to run twice during CI (which can potentially lead to file hash mismatches between the github and the maven release, which some people are annoyed about)


Count resolution error when providing a bucket_id

Describe the Bug
When providing a value for bucket_id, module can not plan or apply.
Expected Behavior
Ability to create my own bucket and provide it as an input
Steps to Reproduce
##---------------------------------------------------
## AWS S3 Bucket for storing logs
##---------------------------------------------------
# S3 bucket for storing logs
module "log_storage" {
  source = "cloudposse/s3-log-storage/aws"
  name      = "account-guardian-logs-${data.aws_caller_identity.current.account_id}"
  namespace = "ga"

  s3_object_ownership           = "BucketOwnerPreferred"
  bucket_key_enabled            = true
  versioning_enabled            = true
  lifecycle_rule_enabled        = false
  lifecycle_configuration_rules = [local.lifecycle_configuration_rule]
}

##---------------------------------------------------
## AWS Systems Manager Patch Manager
##---------------------------------------------------

module "ssm-patch-manager-critical-al2" {
  source  = "cloudposse/ssm-patch-manager/aws"
  version = "0.6.0"
  region = data.aws_region.current.name

  approved_patches_compliance_level = "CRITICAL"

  namespace = "ga-account-guardian"
  operating_system = "AMAZON_LINUX_2"
  reboot_option = "NoReboot"
  scan_patch_groups = ["al2-automatic"]
  install_patch_groups = ["al2-automatic"]
  bucket_id = module.log_storage.bucket_id

  patch_baseline_approval_rules = [
    {
      approve_after_days  = 0
      compliance_level    = "HIGH"
      enable_non_security = false
      patch_baseline_filters = [
        {
          name   = "PRODUCT"
          values = ["AmazonLinux2", "AmazonLinux2.0"]
        },
        {
          name   = "CLASSIFICATION"
          values = ["Security"]
        },
        {
          name   = "SEVERITY"
          values = ["Critical", "Important"]
        }
      ]
    }
  ]

  // Schedule for the maintenance window
  // Install, and then scan to see if there are any missing patches/reboots needed
  install_maintenance_window_schedule = "cron(0 6 * * ? *)" // Run every day at 6:00 AM
  scan_maintenance_window_schedule = "cron(0 7 * * ? *)" // Run every day at 7:00 AM
}

Screenshots
No response
Environment
terraform --version
Terraform v1.4.2
on darwin_amd64

provider registry.terraform.io/hashicorp/aws v5.37.0
provider registry.terraform.io/hashicorp/time v0.10.0

cat .terraform/modules/modules.json | jq
{
  "Modules": [
    {
      "Key": "",
      "Source": "",
      "Dir": "."
    },
    {
      "Key": "log_storage",
      "Source": "registry.terraform.io/cloudposse/s3-log-storage/aws",
      "Version": "1.4.2",
      "Dir": ".terraform/modules/log_storage"
    },
    {
      "Key": "log_storage.aws_s3_bucket",
      "Source": "registry.terraform.io/cloudposse/s3-bucket/aws",
      "Version": "3.1.2",
      "Dir": ".terraform/modules/log_storage.aws_s3_bucket"
    },
    {
      "Key": "log_storage.aws_s3_bucket.s3_user",
      "Source": "registry.terraform.io/cloudposse/iam-s3-user/aws",
      "Version": "1.1.0",
      "Dir": ".terraform/modules/log_storage.aws_s3_bucket.s3_user"
    },
    {
      "Key": "log_storage.aws_s3_bucket.s3_user.s3_user",
      "Source": "registry.terraform.io/cloudposse/iam-system-user/aws",
      "Version": "1.0.0",
      "Dir": ".terraform/modules/log_storage.aws_s3_bucket.s3_user.s3_user"
    },
    {
      "Key": "log_storage.aws_s3_bucket.s3_user.s3_user.store_write",
      "Source": "registry.terraform.io/cloudposse/ssm-parameter-store/aws",
      "Version": "0.10.0",
      "Dir": ".terraform/modules/log_storage.aws_s3_bucket.s3_user.s3_user.store_write"
    },
    {
      "Key": "log_storage.aws_s3_bucket.s3_user.s3_user.store_write.this",
      "Source": "registry.terraform.io/cloudposse/label/null",
      "Version": "0.25.0",
      "Dir": ".terraform/modules/log_storage.aws_s3_bucket.s3_user.s3_user.store_write.this"
    },
    {
      "Key": "log_storage.aws_s3_bucket.s3_user.s3_user.this",
      "Source": "registry.terraform.io/cloudposse/label/null",
      "Version": "0.25.0",
      "Dir": ".terraform/modules/log_storage.aws_s3_bucket.s3_user.s3_user.this"
    },
    {
      "Key": "log_storage.aws_s3_bucket.s3_user.this",
      "Source": "registry.terraform.io/cloudposse/label/null",
      "Version": "0.25.0",
      "Dir": ".terraform/modules/log_storage.aws_s3_bucket.s3_user.this"
    },
    {
      "Key": "log_storage.aws_s3_bucket.this",
      "Source": "registry.terraform.io/cloudposse/label/null",
      "Version": "0.25.0",
      "Dir": ".terraform/modules/log_storage.aws_s3_bucket.this"
    },
    {
      "Key": "log_storage.bucket_name",
      "Source": "registry.terraform.io/cloudposse/label/null",
      "Version": "0.25.0",
      "Dir": ".terraform/modules/log_storage.bucket_name"
    },
    {
      "Key": "log_storage.this",
      "Source": "registry.terraform.io/cloudposse/label/null",
      "Version": "0.25.0",
      "Dir": ".terraform/modules/log_storage.this"
    },
    {
      "Key": "ssm-patch-manager-critical-al2",
      "Source": "registry.terraform.io/cloudposse/ssm-patch-manager/aws",
      "Version": "0.6.0",
      "Dir": ".terraform/modules/ssm-patch-manager-critical-al2"
    },
    {
      "Key": "ssm-patch-manager-critical-al2.install_window_label",
      "Source": "registry.terraform.io/cloudposse/label/null",
      "Version": "0.25.0",
      "Dir": ".terraform/modules/ssm-patch-manager-critical-al2.install_window_label"
    },
    {
      "Key": "ssm-patch-manager-critical-al2.scan_window_label",
      "Source": "registry.terraform.io/cloudposse/label/null",
      "Version": "0.25.0",
      "Dir": ".terraform/modules/ssm-patch-manager-critical-al2.scan_window_label"
    },
    {
      "Key": "ssm-patch-manager-critical-al2.ssm_patch_log_s3_bucket",
      "Source": "registry.terraform.io/cloudposse/s3-bucket/aws",
      "Version": "4.0.0",
      "Dir": ".terraform/modules/ssm-patch-manager-critical-al2.ssm_patch_log_s3_bucket"
    },
    {
      "Key": "ssm-patch-manager-critical-al2.ssm_patch_log_s3_bucket.s3_user",
      "Source": "registry.terraform.io/cloudposse/iam-s3-user/aws",
      "Version": "1.2.0",
      "Dir": ".terraform/modules/ssm-patch-manager-critical-al2.ssm_patch_log_s3_bucket.s3_user"
    },
    {
      "Key": "ssm-patch-manager-critical-al2.ssm_patch_log_s3_bucket.s3_user.s3_user",
      "Source": "registry.terraform.io/cloudposse/iam-system-user/aws",
      "Version": "1.0.0",
      "Dir": ".terraform/modules/ssm-patch-manager-critical-al2.ssm_patch_log_s3_bucket.s3_user.s3_user"
    },
    {
      "Key": "ssm-patch-manager-critical-al2.ssm_patch_log_s3_bucket.s3_user.s3_user.store_write",
      "Source": "registry.terraform.io/cloudposse/ssm-parameter-store/aws",
      "Version": "0.10.0",
      "Dir": ".terraform/modules/ssm-patch-manager-critical-al2.ssm_patch_log_s3_bucket.s3_user.s3_user.store_write"
    },
    {
      "Key": "ssm-patch-manager-critical-al2.ssm_patch_log_s3_bucket.s3_user.s3_user.store_write.this",
      "Source": "registry.terraform.io/cloudposse/label/null",
      "Version": "0.25.0",
      "Dir": ".terraform/modules/ssm-patch-manager-critical-al2.ssm_patch_log_s3_bucket.s3_user.s3_user.store_write.this"
    },
    {
      "Key": "ssm-patch-manager-critical-al2.ssm_patch_log_s3_bucket.s3_user.s3_user.this",
      "Source": "registry.terraform.io/cloudposse/label/null",
      "Version": "0.25.0",
      "Dir": ".terraform/modules/ssm-patch-manager-critical-al2.ssm_patch_log_s3_bucket.s3_user.s3_user.this"
    },
    {
      "Key": "ssm-patch-manager-critical-al2.ssm_patch_log_s3_bucket.s3_user.this",
      "Source": "registry.terraform.io/cloudposse/label/null",
      "Version": "0.25.0",
      "Dir": ".terraform/modules/ssm-patch-manager-critical-al2.ssm_patch_log_s3_bucket.s3_user.this"
    },
    {
      "Key": "ssm-patch-manager-critical-al2.ssm_patch_log_s3_bucket.this",
      "Source": "registry.terraform.io/cloudposse/label/null",
      "Version": "0.25.0",
      "Dir": ".terraform/modules/ssm-patch-manager-critical-al2.ssm_patch_log_s3_bucket.this"
    },
    {
      "Key": "ssm-patch-manager-critical-al2.ssm_patch_log_s3_bucket_label",
      "Source": "registry.terraform.io/cloudposse/label/null",
      "Version": "0.25.0",
      "Dir": ".terraform/modules/ssm-patch-manager-critical-al2.ssm_patch_log_s3_bucket_label"
    },
    {
      "Key": "ssm-patch-manager-critical-al2.this",
      "Source": "registry.terraform.io/cloudposse/label/null",
      "Version": "0.25.0",
      "Dir": ".terraform/modules/ssm-patch-manager-critical-al2.this"
    },
    {
      "Key": "ssm-patch-manager-critical-ubuntu20",
      "Source": "registry.terraform.io/cloudposse/ssm-patch-manager/aws",
      "Version": "0.6.0",
      "Dir": ".terraform/modules/ssm-patch-manager-critical-ubuntu20"
    },
    {
      "Key": "ssm-patch-manager-critical-ubuntu20.install_window_label",
      "Source": "registry.terraform.io/cloudposse/label/null",
      "Version": "0.25.0",
      "Dir": ".terraform/modules/ssm-patch-manager-critical-ubuntu20.install_window_label"
    },
    {
      "Key": "ssm-patch-manager-critical-ubuntu20.scan_window_label",
      "Source": "registry.terraform.io/cloudposse/label/null",
      "Version": "0.25.0",
      "Dir": ".terraform/modules/ssm-patch-manager-critical-ubuntu20.scan_window_label"
    },
    {
      "Key": "ssm-patch-manager-critical-ubuntu20.ssm_patch_log_s3_bucket",
      "Source": "registry.terraform.io/cloudposse/s3-bucket/aws",
      "Version": "4.0.0",
      "Dir": ".terraform/modules/ssm-patch-manager-critical-ubuntu20.ssm_patch_log_s3_bucket"
    },
    {
      "Key": "ssm-patch-manager-critical-ubuntu20.ssm_patch_log_s3_bucket.s3_user",
      "Source": "registry.terraform.io/cloudposse/iam-s3-user/aws",
      "Version": "1.2.0",
      "Dir": ".terraform/modules/ssm-patch-manager-critical-ubuntu20.ssm_patch_log_s3_bucket.s3_user"
    },
    {
      "Key": "ssm-patch-manager-critical-ubuntu20.ssm_patch_log_s3_bucket.s3_user.s3_user",
      "Source": "registry.terraform.io/cloudposse/iam-system-user/aws",
      "Version": "1.0.0",
      "Dir": ".terraform/modules/ssm-patch-manager-critical-ubuntu20.ssm_patch_log_s3_bucket.s3_user.s3_user"
    },
    {
      "Key": "ssm-patch-manager-critical-ubuntu20.ssm_patch_log_s3_bucket.s3_user.s3_user.store_write",
      "Source": "registry.terraform.io/cloudposse/ssm-parameter-store/aws",
      "Version": "0.10.0",
      "Dir": ".terraform/modules/ssm-patch-manager-critical-ubuntu20.ssm_patch_log_s3_bucket.s3_user.s3_user.store_write"
    },
    {
      "Key": "ssm-patch-manager-critical-ubuntu20.ssm_patch_log_s3_bucket.s3_user.s3_user.store_write.this",
      "Source": "registry.terraform.io/cloudposse/label/null",
      "Version": "0.25.0",
      "Dir": ".terraform/modules/ssm-patch-manager-critical-ubuntu20.ssm_patch_log_s3_bucket.s3_user.s3_user.store_write.this"
    },
    {
      "Key": "ssm-patch-manager-critical-ubuntu20.ssm_patch_log_s3_bucket.s3_user.s3_user.this",
      "Source": "registry.terraform.io/cloudposse/label/null",
      "Version": "0.25.0",
      "Dir": ".terraform/modules/ssm-patch-manager-critical-ubuntu20.ssm_patch_log_s3_bucket.s3_user.s3_user.this"
    },
    {
      "Key": "ssm-patch-manager-critical-ubuntu20.ssm_patch_log_s3_bucket.s3_user.this",
      "Source": "registry.terraform.io/cloudposse/label/null",
      "Version": "0.25.0",
      "Dir": ".terraform/modules/ssm-patch-manager-critical-ubuntu20.ssm_patch_log_s3_bucket.s3_user.this"
    },
    {
      "Key": "ssm-patch-manager-critical-ubuntu20.ssm_patch_log_s3_bucket.this",
      "Source": "registry.terraform.io/cloudposse/label/null",
      "Version": "0.25.0",
      "Dir": ".terraform/modules/ssm-patch-manager-critical-ubuntu20.ssm_patch_log_s3_bucket.this"
    },
    {
      "Key": "ssm-patch-manager-critical-ubuntu20.ssm_patch_log_s3_bucket_label",
      "Source": "registry.terraform.io/cloudposse/label/null",
      "Version": "0.25.0",
      "Dir": ".terraform/modules/ssm-patch-manager-critical-ubuntu20.ssm_patch_log_s3_bucket_label"
    },
    {
      "Key": "ssm-patch-manager-critical-ubuntu20.this",
      "Source": "registry.terraform.io/cloudposse/label/null",
      "Version": "0.25.0",
      "Dir": ".terraform/modules/ssm-patch-manager-critical-ubuntu20.this"
    }
  ]
}

Additional Context
Plan: 31 to add, 0 to change, 0 to destroy.
╷
│ Error: Invalid count argument
│
│   on .terraform/modules/ssm-patch-manager-critical-al2/ssm_log_bucket.tf line 19, in data "aws_iam_policy_document" "bucket_policy":
│   19:   count = local.create_log_bucket ? 1 : 0
│
│ The "count" value depends on resource attributes that cannot be determined until apply, so Terraform cannot predict how many
│ instances will be created. To work around this, use the -target argument to first apply only the resources that the count
│ depends on.
╵
╷
│ Error: Invalid count argument
│
│   on .terraform/modules/ssm-patch-manager-critical-al2/ssm_log_bucket.tf line 42, in module "ssm_patch_log_s3_bucket":
│   42:   count   = local.create_log_bucket ? 1 : 0
│
│ The "count" value depends on resource attributes that cannot be determined until apply, so Terraform cannot predict how many
│ instances will be created. To work around this, use the -target argument to first apply only the resources that the count
│ depends on.
╵
╷
│ Error: Invalid count argument
│
│   on .terraform/modules/ssm-patch-manager-critical-ubuntu20/ssm_log_bucket.tf line 19, in data "aws_iam_policy_document" "bucket_policy":
│   19:   count = local.create_log_bucket ? 1 : 0
│
│ The "count" value depends on resource attributes that cannot be determined until apply, so Terraform cannot predict how many
│ instances will be created. To work around this, use the -target argument to first apply only the resources that the count
│ depends on.
╵
╷
│ Error: Invalid count argument
│
│   on .terraform/modules/ssm-patch-manager-critical-ubuntu20/ssm_log_bucket.tf line 42, in module "ssm_patch_log_s3_bucket":
│   42:   count   = local.create_log_bucket ? 1 : 0
│
│ The "count" value depends on resource attributes that cannot be determined until apply, so Terraform cannot predict how many
│ instances will be created. To work around this, use the -target argument to first apply only the resources that the count
│ depends on.

@AdamTylerLynch 👋 This felt odd to me since the actual count conditional was not dependent on anything that has to do with list or map types, which is where this type of problem comes up the most. I dug in and quickly setup your test with the following configurations:
##---------------------------------------------------
## AWS S3 Bucket for storing logs
##---------------------------------------------------
# S3 bucket for storing logs
module "log_storage" {
  source  = "cloudposse/s3-log-storage/aws"
  version = "1.4.2"

  name      = "account-guardian-logs"
  namespace = "ga"

  s3_object_ownership           = "BucketOwnerPreferred"
  bucket_key_enabled            = true
  versioning_enabled            = true
  lifecycle_rule_enabled        = false
  lifecycle_configuration_rules = []
}

##---------------------------------------------------
## AWS Systems Manager Patch Manager
##---------------------------------------------------

module "ssm-patch-manager-critical-al2" {
  source  = "cloudposse/ssm-patch-manager/aws"
  version = "0.6.0"

  region = "us-east-1"
  approved_patches_compliance_level = "CRITICAL"

  namespace = "ga-account-guardian"
  operating_system = "AMAZON_LINUX_2"
  reboot_option = "NoReboot"
  scan_patch_groups = ["al2-automatic"]
  install_patch_groups = ["al2-automatic"]
  bucket_id = module.log_storage.bucket_id

  patch_baseline_approval_rules = [
    {
      approve_after_days  = 0
      compliance_level    = "HIGH"
      enable_non_security = false
      patch_baseline_filters = [
        {
          name   = "PRODUCT"
          values = ["AmazonLinux2", "AmazonLinux2.0"]
        },
        {
          name   = "CLASSIFICATION"
          values = ["Security"]
        },
        {
          name   = "SEVERITY"
          values = ["Critical", "Important"]
        }
      ]
    }
  ]

  // Schedule for the maintenance window
  // Install, and then scan to see if there are any missing patches/reboots needed
  install_maintenance_window_schedule = "cron(0 6 * * ? *)" // Run every day at 6:00 AM
  scan_maintenance_window_schedule = "cron(0 7 * * ? *)" // Run every day at 7:00 AM
}

provider "aws" {
  region = "us-east-1"
}

terraform {
  required_version = ">= 1.0.0"

  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = ">= 4.1"
    }
  }
}

Here are my notes from testing in different scenarios:

Using tofu 1.6.1 -- The above root module planned, applied, and destroyed without issue.
Using terraform 1.7.3 -- The above root module planned, applied, and destroyed without issue.
Using terraform 1.4.2 -- Plan went 💥
Using terraform 1.5.7 -- Plan went 💥
Using terraform 1.6.6 -- The above root module planned, applied, and destroyed without issue.

Net result is that I probably spent 40 minutes on this cause it got me curious, but I did figure it out 😁 In basically doing a git bisect across many different versions, I was able to pin it down to a change in 1.6, which led me to finding this fix / enhancement in the changelog: https://github.com/hashicorp/terraform/pull/33234
Anyway, I'm not sure why someone else hasn't run into this before... but upgrading TF to 1.6.0+ will do the trick for you. I know that is not a great option though... so another option is we add a simple bool var, log_bucket_enabled, that will allow us to easily skirt around this issue. Happy to either help out here and do an upgrade of this module to support that use-case and clean it up in general as it looks like it needs it (e.g. var.region is required + not used 👎).
One thing I found interesting from looking at issues... Mart was saying this was intended back in early 1.0 days: https://github.com/hashicorp/terraform/issues/28962. I'm surprised by that!

@Gowiem thank you friend! Yes, upgrading the Terraform version to 1.7.4 fixed this issue.

Reopening this issue as I want us on @cloudposse/contributors to get this fixed as others with run into this.
I figured the issue out last night, but I didn't write it up all that well. To sum things up, the root cause is that we're using local.create_log_bucket (here) to determine the creation of multiple resources within the module. That local depends on checking if the given var.bucket_id is null and if a consumer passes a literal value for that bucket_id, then all is good. But if the consumer creates the bucket alongside their consumption of this module in their root module and passes a reference to that resource's ID (e.g. module.log_storage.bucket_id) then we end up hitting this issue in Terraform: https://github.com/hashicorp/terraform/issues/28962. This will affect any Terraform version prior to 1.6, which is a lot of folks and is why I think this needs to be addressed.
We can get this fixed by adding a log_bucket_creation_enabled variable that we depend on instead of the bucket_id == null check. That will let pre-1.6 terraform not complain about this and properly fix the bug.
We should also do some general cleanup of this module, other PRs, and issues. I will take a stab at this next time I have a clean hour or so.


Default port from 8000 to 9000

I think the default port used in this commend - poetry run uvicorn wandbot.api.app:app --host="<IP_ADDRESS>" --port=8000 > api.log 2>&1) might conflict with Jupyter Notebook's port.
Suggest to change it to 9000 maybe.
Trivial issue though. :)

@ayulockin , doesn't Jupyter default to 8888 or 8889 ? I mean there is no harm in changing the default port, but i'm curious that's all.

closing this for now


Text and image in .navbar-brand issue

When setting text and an image in the .navbar-brand component, the text gets pushed below the image - breaking the navbar - since the image is set to display: block in the Sass code. Cases where this would happen is when you want to display the brand name next to its minimal logo.
Recreate: Add an image and text to the navbar-brand component of a navbar.
Expected behavior: That the text be next to the image.
Current behavior: The text gets pushed below the image
Example pen code

Hi @chesedo!
You appear to have posted a live example (http://codepen.io/chesedo/pen/xEYXGV.html), which is always a good first step. However, according to Bootlint, your example has some Bootstrap usage errors, which might potentially be causing your issue:

line 18, column 5: W007: Found one or more <button>s missing a type attribute.

You'll need to fix these errors and post a revised example before we can proceed further.
Thanks!
(Please note that this is a fully automated comment.)

Improvements made in #19890.


项目引入新的依赖后，提示s.hasChanged is not a functiond

Describe the bug
项目引入新的依赖后，提示s.hasChanged is not a functiond
at Object.transform (/opt/node_modules/unplugin-auto-import/dist/chunk-D3CKI5NO.cjs:195:12)
Reproduction
re
System Info
1

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

We temporarily close this due to the lack of enough information.
Please provide a minimal reproduction to reopen the issue.
Thanks.

Why reproduction is required


Update datasets to remove unneeded commas on reactions

Commas need to be appended by the server and/or the client where needed, not in the database.

resolved in #134


py 3.4.2 support

Hey I had to restart the raspberry pi the script is running on and now for some reason it is stuck at Starting... Do you know what is causing this?

Also the bot is going in loops and is messaging the same user over and over again.

I'm working on the second, the first is because I don't have any real loggin in place


[CWS] serialize caps to an empty array if process has no caps

Before:
"{cap_effective":null,"cap_permitted":null}
After:
{"cap_effective":[],"cap_permitted":[]}

What does this PR do?

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

This is not supposed to happen if the serialization is done correctly with<EMAIL_ADDRESS>NilSliceAsEmpty


How to open the graph file in GUI model dumped from decomp_dbg

I have built the native decompiler in debug model according to the issue. And I dumped the controlflow graph by command "graph controlflow xx.cfg", but I do not know how to open this file in GUI model. Please help me, thanks.

I found the comments, in graph.hh, that "NOTE: Serializes graphs in format used by Renoir". Unfortunately, the Renoir does not release currently. So it means that the graph file generated by these graph commands  provided by decomp_dbg is useless...What a pity.


Plan to Update?

Do you plan to update this mod to be like the original version. I don't like that it requires JEI. I also really liked the feature of unlimited items. I miss the old NEI :(. If you plan to update it I will be so happy.

If it dose go back expect no mod support mod authors will not want to support both.
There is no problem with it being a JEI addon its works fine and has the benefit of JEI's API (So much nicer)

So, here is the path that NEI is taking. It IS being moved to a JEI addon that simply skins JEI to look and fee like NEI, the issues with NEI going back to a standalone mod is, NEI doesnt actually provide the recipe handlers that show you all the custom stuff from mods, that is the mod doing it using NEI's api, that being said the same thing is happening with JEI mods are supporting it instead of NEI, You will be back to this tracker in 5 min complaining that there is no recipes, it just doesnt work that way sadly.

Ok I Understand, at least it has some features like the potion GUI and the encant GUI.


Invalid typescript generation for empty schema

What are the steps to reproduce this issue?
Generate spec:
import { defineConfig } from 'orval'

export default defineConfig({
  main: {
    output: {
      mode: 'tags-split',
      target: './testspec/main.ts',
      schemas: './testspec/model',
      client: 'react-query',
      tsconfig: './tsconfig.json',
    },
    input: {
      target: 'testspec.yaml',
    },
    hooks: {
      afterAllFilesWrite: 'prettier --write',
    },
  },
})

openapi: 3.0.3
info:
  description: test
  title: test
  version: test
paths:
  /ping:
    get:
      summary: test
      responses:
        '200':
          description: ok
components:
  schemas:
    DbNotificationID: {}

What happens?
Outputs invalid typescript:
export interface DbNotificationID unknown

What were you expecting to happen?
Same output as in 6.23.0:
export interface DbNotificationID = unknown

What versions are you using?
Package Version: 6.24.0

Thank you made this report and suggest.
Looks good interface DbNotificationID {}. you fix It is also possible to create a PR.

I'll l submit a fix for this issue, so I assigned it to me.

Hi, @danicc097 @dyatko
Since we released "v6.25.0" this issue has been fixed 👍


(BKR-321) lxc hypervisor driver

Slightly modified version of Ashish:s PR with yard docs and rspec tests

Can one of the admins verify this patch?

ok to test

We do not currently have an lxc maintainer - are you willing to take that on should this PR land?  You'd need to be available to do reviews and provide lxc advice.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1620/
Test FAILed.

@anodelman I'm willing to provide whatever support I can give as maintainer for the lxc code but I'm pretty fresh wh

Did indeed forget to rebase, this one is rebased on to current master

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1638/
Test FAILed.

@qvicksilver, unfortunately, our Jenkins is internal at this point, so you won't be able to see the results.
It looks like you have some commits polluting your change history.  We don't usually merge PRs that have merge commits in them.  Also, you have some other changes that don't appear to be needed for the lxc hypervisor in them, but I'm assuming those are related to the merge commits.
Once you clean this up, I look forward to getting it into Beaker!
Thanks,
KI

Made a clean branch and created a PR from it in https://github.com/puppetlabs/beaker/pull/985


change Harcoded strings and margins in fragment_media_details.xml

Fixes #217
UI remains the same

@kulloveth can you resolve the conflicts ?

@kulloveth can you resolve the conflicts ?

fixed

Thanks @kulloveth


[Datastore question] How to build AllocateIdRequest?

Greetings,
As I understand, a Java AllocateIdsRequest instance can be built using Keys or PathElements, but according to the API it expects the key to contain incomplete paths. I saw no public way to build a Key without an id or name, and I no public way to get the path of an IncompleteKey. Can you please provide and example of building an AllocateIdsRequest from a string representing the kind? Also, wouldn't it make sense to be able to build AllocateIdsRequest from IncompleteKeys?
Thanks.

I will try to investigate this question within a few days.

@GabiAxel - Are you possibly looking for something like this?
Datastore ds = DatastoreOptions.newBuilder().build().getService();
//Create an incomplete key for kind, MyKind...
IncompleteKey incompleteKey = ds.newKeyFactory().setKind("MyKind").newKey();
System.out.println(incompleteKey);
//Allocate the ID
Key completeKey = ds.allocateId(incompleteKey);
System.out.println(completeKey);

This would print the below to the console:
IncompleteKey{projectId=my-project-id, namespace=, path=[PathElement{kind=MyKind, id=null, name=null}]}
Key{projectId=my-project-id, namespace=, path=[PathElement{kind=MyKind, id=5640376756994048, name=null}]}

Yes, that's it. Thanks.

Looks like the question was answered - closing out the issue.


regression of self semantic highlighting in async-trait

I landed a fix for this in #10899 - however, due to lack of proc macro testing infrastructure didn't write a test :(
It looks like this recently regressed, and a bisect has shown the following PR as the culprit: #11171
cc @Veykril

Ah I made a mistake when rewriting things earlier, should be fixed by https://github.com/rust-analyzer/rust-analyzer/pull/11175


Is there a way to get all values for a key pattern in one operation on Redis cluster? E.g.  get all values having key starting with "data*"

We primarily use GitHub as an issue tracker; for usage and support questions, please check out these resources below. Thanks! 😁.
Support questions will be closed immediately.

Reference documentation: https://lettuce.io/docs/
Wiki: https://github.com/lettuce-io/lettuce-core/wiki
Javadoc: https://lettuce.io/core/release/api/
Gitter Chat (General discussion): https://gitter.im/lettuce-io/Lobby
Google Group/Mailing List (General discussion, announcements and releases): https://groups.google.com/d/forum/lettuce-redis-client-users or<EMAIL_ADDRESS>Stack Overflow (Questions): https://stackoverflow.com/questions/tagged/lettuce
Twitter: If it's just a quick question you can ping our Twitter: https://twitter.com/LettuceDriver
Also have a look at the readme for more information on how to get support:
https://github.com/lettuce-io/lettuce-core/blob/master/README.md

I find this post useful when was  looking for this https://github.com/lettuce-io/lettuce-core/issues/497


[GLUTEN-1632][CH]Daily Update Clickhouse Version (20230606)

Auto commit by gluten daily build, please check the build status and merge it if it's green.

Run Gluten Clickhouse CI

Compatible with current gluten

Compatible with current gluten


Add support vitejs (ESM)

Help, i have error:
Uncaught SyntaxError: The requested module '/node_modules/leaflet/dist/leaflet-src.js?v=8128ddc4' does not provide an export named 'default'

Sorry, I have no experience with vitejs.
I have played with snowpack, but what I find is that different frontend tooling have their own problems.

@Rysakov1986 did you ever end up getting this to work? I'd like to use this for a project, but I'm getting the same error and @ngyewch answer doesn't really help or give me much hope. It looks as if it's an active project though.

Using this trick https://github.com/ngyewch/svelte-leaflet/issues/3#issuecomment-987199487, I was able to run it OK on a svelte-kit project (which is powered by Vite).
Since this summer, there was a lot of improvement on Vite's side to handle the different module flavors (CJS, ESM, UMD, etc.). I'm personally very impatient that the ecosystem will be mainly ESM-only (this topic is such a pain to handle !)

The error sounds like you're doing:
import LeafletMap from 'svelte-leafletjs'

That should use the library's default export, but package.json points vite to the dist directory, and those files don't seem to have a default export. Maybe rollup needs to create an ESM-import-friendly build?
Anyway, try importing the named exports, e.g.
import { LeafletMap, TileLayer } from 'svelte-leafletjs'

The library still does not work even when following that guide.
I get the following error:
svelte-leaflet doesn't appear to be written in CJS, but also doesn't appear to be a valid ES module (i.e. it doesn't have "type": "module" or an .mjs extension for the entry point). Please contact the package author to fix.

Nevermind, it seems that I had a second import that was not using the ?client directive. This method still works as far as I am aware.

@ngyewch, as the Svelte ecosystem moved mainly to using Vite as build tool, could you revisit this issue?

@notramo Yeah, I have moved to Vite for other projects. I just have to find some time to migrate this project. Hopefully in the near future.

A basic vite svelte project with svelte-leafletjs  works fine, it only emits this warning:

10:00:47 AM [vite-plugin-svelte] WARNING: The following packages have a svelte field in their package.json but no exports condition for svelte.
<EMAIL_ADDRESS>Please see https://github.com/sveltejs/vite-plugin-svelte/blob/main/docs/faq.md#missing-exports-condition for details.

Quoting the link:

missing exports condition
If you see a warning logged for this when using a Svelte library, please tell the library maintainers.
Using the svelte field in package.json to point at .svelte source files is deprecated and you must use a svelte export condition.
vite-plugin-svelte 3 still resolves it as a fallback, but in a future major release this is going to be removed and without exports condition resolving the library is going to fail.
Example:
// package.json
  "files": ["dist"],
  "svelte": "dist/index.js",
+ "exports": {
+   ".": {
+     "svelte": "./dist/index.js"
+   }
  }


IGNITE-13701 Fixed content, order and amount of columns in INDEXES, TABLES and SCHEMAS views.

This PR is associated with a resolved ticket. Closing the PR, please reopen it if you still need it.


TotallyUsefulSoftware,Inc.QuickSFV version 3.0.0

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[x] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

I'll honestly probably just make a new pr, at least until I can have some time to wrap my head around git and how to do things a bit more


Run the netty-buffer tests in parallel

Motivation:
We have a lot of test cases to go through, due to the number of combinations and buffer states explored by the parameterised tests.
Modification:
Tell the JUnit 5 runner platform to run the buffer tests in parallel, per class.
Within each class, the tests will run sequentially.
This preserves the existing setup/tear-down behaviour.
The BufferCleanerTest is an exception, due to how it accesses Statics.MEM_USAGE_NATIVE, so it runs in isolation, when no other tests are running.
Result:
Faster build.
~This PR may randomly fail, until #12356 is merged and we can rebase on top of it.~
Rebased.

Huh, looks like it only saved around 2 minutes. Was a bigger effect locally.


Unbalanced braces will cause error

Hi，
Thank you very much for such a useful project.
I use ticklecharts to draw line charts for analyzing logs, some data is directly read from external files, so there may be unbalanced braces.
I'd like to report an issue: Unbalanced braces will cause error.
Description
In the README.md, there is a simplest example:
package require ticklecharts

set chart [ticklecharts::chart new]

$chart Xaxis -data [list {Mon Tue Wed Thu Fri Sat Sun}]
$chart Yaxis
$chart Add "lineSeries" -data [list {150 230 224 218 135 147 260}]

$chart Render

However,  assuming that the data is generated by other commands and contains unbalanced braces:
package require ticklecharts

set chart [ticklecharts::chart new]

# $chart Xaxis -data [list {Mon Tue Wed Thu Fri Sat Sun}]
set data [ list ]
set t [ list ]
lappend t "Mon\{1"
lappend t Tue Wed Thu Fri Sat Sun
lappend data $t
$chart Xaxis -data $data

$chart Yaxis
$chart Add "lineSeries" -data [list {150 230 224 218 135 147 260}]

$chart Render

get error out:

How to fix
As the error message,
https://github.com/nico-robert/ticklecharts/blob/023012fd495d588c06bd97a055eaf6cfdd562d43/chart.tcl#L351
error occurs when execute join, my suggestion is, join first and then string map
return [string map [list %json% $json] [join $newhtml "\n"]]

@pantao1227 many thanks for your fix, I will include it in my next version.


BasicAuthentication Support

Is basic authentication supported in the most recent version of the clickhouse JDBC drivers? (clickhouse-jdbc-0.3.2-patch11 is my version).
I found an older PR saying that everyone got switched over https://github.com/ClickHouse/clickhouse-jdbc/issues/522, but looks like it may not be true in the most revent version.
I tried using the custom_http_headers property to set my own auth header, but the client complains about double auth because https://github.com/ClickHouse/clickhouse-jdbc/blob/f285b73d45597e29cf36dff4daf4cb4f9f53453a/clickhouse-http-client/src/main/java/com/clickhouse/client/http/ClickHouseHttpConnection.java#L166 this method is still always attempting to add the X-Clickhouse user and password methods. I can't find anywhere in the codebase that ever attempts to set an accessToken based method.
Am I missing a way to properly configure the client to use a BasicAuth header?

Thank you @tpoll for the report. I'll fix it later today so that you can verify using nightly build.

Thanks for the fast response @zhicwu. What time does the nightly build kickoff? Happy to test it out on our setup once it's available.

It's schedule to build at 3:55pm UTC and the packages will be generated in a few minutes. You can download latest snapshot from https://s01.oss.sonatype.org/content/repositories/snapshots/com/clickhouse/clickhouse-jdbc/0.3.3-SNAPSHOT/.

@zhicwu  thanks, this seems to have allowed us to use the auth header!


Link Cable Support in GB Studio

Is your feature request related to a problem? Please describe.
My feature request is not related to a problem. It is a request for a new feature.
Describe the solution you'd like
I would like GB Studio to have support for making multiplayer games via the game link cable.
Describe alternatives you've considered

Making single-player games

Additional context
The Game Link Cable for the Game Boy can handle real-time movement of 2 players. For an example of this, see Ballon Kid. (https://en.wikipedia.org/wiki/Balloon_Kid)

Hi,
Don't know if it helps, yet a YouTuber makes a value exchange successfully : https://www.youtube.com/watch?v=OggAC5PoZHo&t=87s
Seems working when I test it (doesn't work evry time anyway, but some times it does well).
Next step should be a way to have a synchronisation routine for syncing x,y coordinates of player 1 and 2. Could be useful for a tag game.
Regards,
Tchaly

This has already been added, could you close this issue @tguy7890 ?


moov atom not found

The details show as follow.
allen@allen-vm:~$ autosub -S en-GB -D zh-CN SimplySolar.mp4
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x932caa0] moov atom not found
SimplySolar.mp4: Invalid data found when processing input
Traceback (most recent call last):
File "/usr/local/bin/autosub", line 260, in
sys.exit(main())
File "/usr/local/bin/autosub", line 194, in main
audio_filename, audio_rate = extract_audio(args.source_path)
File "/usr/local/bin/autosub", line 104, in extract_audio
subprocess.check_output(command)
File "/usr/lib/python2.7/subprocess.py", line 544, in check_output
raise CalledProcessError(retcode, cmd, output=output)
subprocess.CalledProcessError: Command '['ffmpeg', '-y', '-i', 'SimplySolar.mp4', '-ac', '1', '-ar', '16000', '-loglevel', 'error', '/tmp/tmpdlIVEL.wav']' returned non-zero exit status 1

You need to add the path of ffmpeg.exe (path of bin directory)  in drive to PATH variable environtment in windows.


Fixed default value assignment for skipInit parameter

Description

Questions
Answers

Why?
Right now, if you pass anything that is not undefined for the skipInit-Parameter, it'll always be true

BC breaks?
yes

Tests exists & pass?
no

Related tickets?

How to test?
Try to load a SubApplication into the Shopware backend with the Shopware.app.Application.addSubApplication function and set the skipInit parameter to false. The SubApplication will load, but nothing happens afterwards. See example below

Example: Type this into the developer tools of your browser
Shopware.app.Application.addSubApplication({
    name: 'Shopware.apps.Analytics',
    action: 'index'
}, false);

This is especially annoying if you want to use the callback parameter:
Shopware.app.Application.addSubApplication({
    name: 'Shopware.apps.Analytics',
    action: 'index'
}, false, function () {
    console.log('callback');
});

What you'd have to do at the moment to actually set skipInit to false:
Shopware.app.Application.addSubApplication({
    name: 'Shopware.apps.Analytics',
    action: 'index'
}, undefined);

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-19741.
Please use this issue to track the state of your pull request.

thanks for your PR @oktupol :+1:


Releasing a new patch version for azure-cli-ml version 1.33.1

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[x] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

ml


AreaSelect error

Fix areaSelecr function

:tada: This issue has been resolved in version 1.29.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 1.29.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Use bzip2 compressed feature set json as pipeline option

What this PR does / why we need it:
Dataflow runner has a limit of 256kb for pipeline option. As we are storing feature sets as json string in pipeline option, the size will grow proportionally to the number of feature set versions. Compressing the feature set json will help us to support more feature sets.
Which issue(s) this PR fixes:
None
Does this PR introduce a user-facing change?:
Users will be able to have more feature set before dataflow job submission fails. However, this depends on the compression ratio, which in turn depends on how much repetition exists in ithe feature set json.

There are a lot of formatting changes in this. Which IDE + settings are you using?
I have imported the IntelliJ settings as described here:
https://github.com/gojek/feast/blob/master/docs/contributing.md#code-conventions
but I don't think it matches what you've submitted.

There are a lot of formatting changes in this. Which IDE + settings are you using?
I have imported the IntelliJ settings as described here:
https://github.com/gojek/feast/blob/master/docs/contributing.md#code-conventions
but I don't think it matches what you've submitted.

It's the maven spotless plugin.

/lgtm
/approve


frame index of video frame

Since frame.pts is often only by coincidence equal to frame index in video stream (and will ultimately fail with non constant frame rates), I was hoping for frame.index to represent the frame index in the steam.
However, it appears that frame index == encoded frame count on frame creation. This mean that after a seek the index become -at least the way I understand it- false.
Any ideas on how to fix that?

In my own code, after much painful and tedious research :) I have the following:
'''
        PTS (Presentation Time Stamp), which indicates when this frame should
        be shown, is expressed according to stream.time_base.

        We can compare the PTS to frame numbers if we scale by:
            (stream.average_rate / stream.time_base)
'''
pts_scale = video_stream.average_rate * video_stream.time_base

frame_pts = int(frame_index / pts_scale)

I'm not certain how portable this is, as we only use MP4 video streams.

I'm going to close this issue, as the following time-related attributes are properly documented nowadays:

dts
pts
time_base