v8: fix build on aarch64

Motivation for this change
Before this, the build on aarch64 failed with:
/bin/sh: aarch64-linux-gnu-g++: not found
[...]
ninja: build stopped: subcommand failed.

Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS (aarch64-linux)
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@WilliButz v8_3_14 and v8_3_16_14 still seem to be broken on aarch64, causing gitlab to fail on aarch64 currently:
  /nix/store/myghnb5wj43dvkkyg1y31lm2ch6ngzb9-v8-<IP_ADDRESS>.drv
  /nix/store/2bdgdq5fyb0996fkqwzy8588z7f0jqam-ruby2.6.5-execjs-2.6.0.drv
  /nix/store/vxx6rchnw2sff2ldgbbqhp8qw5777jx7-ruby2.6.5-uglifier-2.7.2.drv
  /nix/store/czp90k3rn42anwsnkl1s2w2j96aj1437-gitlab-env-12.4.1.drv

Any idea what needs to be fixed here?
make: *** [tools/gyp/v8_base.target.mk:225: /build/v8-<IP_ADDRESS>/out/Release/obj.target/v8_base/src/extensions/statistics-extension.o] Error 1
In file included from ../src/macro-assembler.h:67:0,
                 from ../src/ic.h:31,
                 from ../src/ic-inl.h:31,
                 from ../src/x64/codegen-x64.h:32,
                 from ../src/codegen.h:75,
                 from ../src/code-stubs.h:33,
                 from ../src/debug.cc:33:
../src/x64/assembler-x64.h: In function 'bool v8::internal::is_uint32(int64_t)':
../src/x64/assembler-x64.h:49:60: error: 'V8_UINT64_C' was not declared in this scope
   static const uint64_t kMaxUInt32 = V8_UINT64_C(0xffffffff);
                                                            ^
../src/x64/assembler-x64.h: In function 'bool v8::internal::is_int32(int64_t)':
../src/x64/assembler-x64.h:54:58: error: 'V8_INT64_C' was not declared in this scope
   static const int64_t kMinInt32 = -V8_INT64_C(0x80000000);
                                                          ^
../src/x64/assembler-x64.h: In function 'bool v8::internal::uint_is_int32(uint64_t)':
../src/x64/assembler-x64.h:59:59: error: 'V8_UINT64_C' was not declared in this scope
   static const uint64_t kMaxInt32 = V8_UINT64_C(0x7fffffff);
                                                           ^
../src/x64/assembler-x64.h: In function 'bool v8::internal::is_uint32(uint64_t)':
../src/x64/assembler-x64.h:64:60: error: 'V8_UINT64_C' was not declared in this scope
   static const uint64_t kMaxUInt32 = V8_UINT64_C(0xffffffff);
                                                            ^
make: *** [tools/gyp/v8_base.target.mk:225: /build/v8-<IP_ADDRESS>/out/Release/obj.target/v8_base/src/cpu-profiler.o] Error 1
../src/x64/assembler-x64.h: In static member function 'static bool v8::internal::CpuFeatures::IsSupported(v8::internal::CpuFeature)':
../src/x64/assembler-x64.h:468:40: error: 'V8_UINT64_C' was not declared in this scope
     return (supported_ & (V8_UINT64_C(1) << f)) != 0;
                                        ^
In file included from ../src/macro-assembler.h:67:0,
                 from ../src/ic.h:31,
                 from ../src/ic-inl.h:31,
                 from ../src/x64/code-stubs-x64.h:31,
                 from ../src/code-stubs.h:307,
                 from ../src/codegen.h:31,
                 from ../src/compiler.cc:33:
../src/x64/assembler-x64.h: In function 'bool v8::internal::is_uint32(int64_t)':
../src/x64/assembler-x64.h:49:60: error: 'V8_UINT64_C' was not declared in this scope
   static const uint64_t kMaxUInt32 = V8_UINT64_C(0xffffffff);
                                                            ^
../src/x64/assembler-x64.h: In function 'bool v8::internal::is_int32(int64_t)':
../src/x64/assembler-x64.h:54:58: error: 'V8_INT64_C' was not declared in this scope
   static const int64_t kMinInt32 = -V8_INT64_C(0x80000000);
                                                          ^
../src/x64/assembler-x64.h: In function 'bool v8::internal::uint_is_int32(uint64_t)':
../src/x64/assembler-x64.h:59:59: error: 'V8_UINT64_C' was not declared in this scope
   static const uint64_t kMaxInt32 = V8_UINT64_C(0x7fffffff);
                                                           ^
../src/x64/assembler-x64.h: In function 'bool v8::internal::is_uint32(uint64_t)':
../src/x64/assembler-x64.h:64:60: error: 'V8_UINT64_C' was not declared in this scope
   static const uint64_t kMaxUInt32 = V8_UINT64_C(0xffffffff);
                                                            ^
../src/x64/assembler-x64.h: In static member function 'static bool v8::internal::CpuFeatures::IsSupported(v8::internal::CpuFeature)':
../src/x64/assembler-x64.h:468:40: error: 'V8_UINT64_C' was not declared in this scope
     return (supported_ & (V8_UINT64_C(1) << f)) != 0;
                                        ^
In file included from ../src/macro-assembler.h:67:0,
                 from ../src/ic.h:31,
                 from ../src/ic-inl.h:31,
                 from ../src/x64/codegen-x64.h:32,
                 from ../src/codegen.h:75,
                 from ../src/code-stubs.h:33,
                 from ../src/code-stubs-hydrogen.cc:30:
../src/x64/assembler-x64.h: In function 'bool v8::internal::is_uint32(int64_t)':
../src/x64/assembler-x64.h:49:60: error: 'V8_UINT64_C' was not declared in this scope
   static const uint64_t kMaxUInt32 = V8_UINT64_C(0xffffffff);
                                                            ^
../src/x64/assembler-x64.h: In function 'bool v8::internal::is_int32(int64_t)':
../src/x64/assembler-x64.h:54:58: error: 'V8_INT64_C' was not declared in this scope
   static const int64_t kMinInt32 = -V8_INT64_C(0x80000000);
                                                          ^
../src/x64/assembler-x64.h: In function 'bool v8::internal::uint_is_int32(uint64_t)':
../src/x64/assembler-x64.h:59:59: error: 'V8_UINT64_C' was not declared in this scope
   static const uint64_t kMaxInt32 = V8_UINT64_C(0x7fffffff);
                                                           ^
../src/x64/assembler-x64.h: In function 'bool v8::internal::is_uint32(uint64_t)':
../src/x64/assembler-x64.h:64:60: error: 'V8_UINT64_C' was not declared in this scope
   static const uint64_t kMaxUInt32 = V8_UINT64_C(0xffffffff);
                                                            ^
../src/x64/assembler-x64.h: In static member function 'static bool v8::internal::CpuFeatures::IsSupported(v8::internal::CpuFeature)':
../src/x64/assembler-x64.h:468:40: error: 'V8_UINT64_C' was not declared in this scope
     return (supported_ & (V8_UINT64_C(1) << f)) != 0;
                                        ^
make: *** [tools/gyp/v8_base.target.mk:225: /build/v8-<IP_ADDRESS>/out/Release/obj.target/v8_base/src/func-name-inferrer.o] Error 1
make: *** [tools/gyp/v8_base.target.mk:225: /build/v8-<IP_ADDRESS>/out/Release/obj.target/v8_base/src/accessors.o] Error 1
In file included from ../src/macro-assembler.h:67:0,
                 from ../src/deoptimizer.h:34,
                 from ../src/frames.cc:31:
../src/x64/assembler-x64.h: In function 'bool v8::internal::is_uint32(int64_t)':
../src/x64/assembler-x64.h:49:60: error: 'V8_UINT64_C' was not declared in this scope
   static const uint64_t kMaxUInt32 = V8_UINT64_C(0xffffffff);
                                                            ^
../src/x64/assembler-x64.h: In function 'bool v8::internal::is_int32(int64_t)':
../src/x64/assembler-x64.h:54:58: error: 'V8_INT64_C' was not declared in this scope
   static const int64_t kMinInt32 = -V8_INT64_C(0x80000000);
                                                          ^
../src/x64/assembler-x64.h: In function 'bool v8::internal::uint_is_int32(uint64_t)':
../src/x64/assembler-x64.h:59:59: error: 'V8_UINT64_C' was not declared in this scope
   static const uint64_t kMaxInt32 = V8_UINT64_C(0x7fffffff);
                                                           ^
../src/x64/assembler-x64.h: In function 'bool v8::internal::is_uint32(uint64_t)':
../src/x64/assembler-x64.h:64:60: error: 'V8_UINT64_C' was not declared in this scope
   static const uint64_t kMaxUInt32 = V8_UINT64_C(0xffffffff);
                                                            ^
../src/x64/assembler-x64.h: In static member function 'static bool v8::internal::CpuFeatures::IsSupported(v8::internal::CpuFeature)':
../src/x64/assembler-x64.h:468:40: error: 'V8_UINT64_C' was not declared in this scope
     return (supported_ & (V8_UINT64_C(1) << f)) != 0;
                                        ^
make: *** [tools/gyp/v8_base.target.mk:225: /build/v8-<IP_ADDRESS>/out/Release/obj.target/v8_base/src/elements.o] Error 1
make: *** [tools/gyp/v8_base.target.mk:225: /build/v8-<IP_ADDRESS>/out/Release/obj.target/v8_base/src/factory.o] Error 1
make: *** [tools/gyp/v8_base.target.mk:225: /build/v8-<IP_ADDRESS>/out/Release/obj.target/v8_base/src/data-flow.o] Error 1
make: *** [tools/gyp/v8_base.target.mk:225: /build/v8-<IP_ADDRESS>/out/Release/obj.target/v8_base/src/code-stubs.o] Error 1
make: *** [tools/gyp/v8_base.target.mk:225: /build/v8-<IP_ADDRESS>/out/Release/obj.target/v8_base/src/bootstrapper.o] Error 1
make: *** [tools/gyp/v8_base.target.mk:225: /build/v8-<IP_ADDRESS>/out/Release/obj.target/v8_base/src/disassembler.o] Error 1
make: *** [tools/gyp/v8_base.target.mk:225: /build/v8-<IP_ADDRESS>/out/Release/obj.target/v8_base/src/assembler.o] Error 1
make: *** [tools/gyp/v8_base.target.mk:225: /build/v8-<IP_ADDRESS>/out/Release/obj.target/v8_base/src/full-codegen.o] Error 1
make: *** [tools/gyp/v8_base.target.mk:225: /build/v8-<IP_ADDRESS>/out/Release/obj.target/v8_base/src/builtins.o] Error 1
make: *** [tools/gyp/v8_base.target.mk:225: /build/v8-<IP_ADDRESS>/out/Release/obj.target/v8_base/src/execution.o] Error 1
make: *** [tools/gyp/v8_base.target.mk:225: /build/v8-<IP_ADDRESS>/out/Release/obj.target/v8_base/src/codegen.o] Error 1
make: *** [tools/gyp/v8_base.target.mk:225: /build/v8-<IP_ADDRESS>/out/Release/obj.target/v8_base/src/ast.o] Error 1
make: *** [tools/gyp/v8_base.target.mk:225: /build/v8-<IP_ADDRESS>/out/Release/obj.target/v8_base/src/deoptimizer.o] Error 1
make: *** [tools/gyp/v8_base.target.mk:225: /build/v8-<IP_ADDRESS>/out/Release/obj.target/v8_base/src/debug.o] Error 1
make: *** [tools/gyp/v8_base.target.mk:225: /build/v8-<IP_ADDRESS>/out/Release/obj.target/v8_base/src/frames.o] Error 1
make: *** [tools/gyp/v8_base.target.mk:225: /build/v8-<IP_ADDRESS>/out/Release/obj.target/v8_base/src/api.o] Error 1
make: *** [tools/gyp/v8_base.target.mk:225: /build/v8-<IP_ADDRESS>/out/Release/obj.target/v8_base/src/code-stubs-hydrogen.o] Error 1
make: *** [tools/gyp/v8_base.target.mk:225: /build/v8-<IP_ADDRESS>/out/Release/obj.target/v8_base/src/compiler.o] Error 1
make: Leaving directory '/build/v8-<IP_ADDRESS>/out'
builder for '/nix/store/myghnb5wj43dvkkyg1y31lm2ch6ngzb9-v8-<IP_ADDRESS>.drv' failed with exit code 2
cannot build derivation '/nix/store/2bdgdq5fyb0996fkqwzy8588z7f0jqam-ruby2.6.5-execjs-2.6.0.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/czp90k3rn42anwsnkl1s2w2j96aj1437-gitlab-env-12.4.1.drv': 1 dependencies couldn't be built
error: build of '/nix/store/czp90k3rn42anwsnkl1s2w2j96aj1437-gitlab-env-12.4.1.drv' failed


"Block" example from documentation does not evaluate

https://cortexjs.io/compute-engine/reference/control-structures/#block-and-if
    const expr = ce.box(["Block", ["Tuple", "c", 5], ["Multiply", "c", 2]])
    console.log(expr.evaluate().valueOf()) // returns: ["Block",["Pair","c",5],["Multiply",2,"c"]]

Works now, although the syntax has changed slightly:
["Block", ["Assign", "c", 5], ["Multiply", "c", 2]]
// ➔ 10


Quering takes time

Workflow version
v2024.1
Alfred version
5.1.4
macOS version
macOS Sonoma 14.3.1
Debugger output
[16:12:21.429] Shortcuts[Script Filter] Queuing argument '(null)'
[16:12:28.307] Shortcuts[Script Filter] Script with argv '(null)' finished
[16:12:28.312] Shortcuts[Script Filter] {"cache":{"seconds":300,"loosereload":true},"items":s

More details
Previous updates were much snappier, didn't even have to wait for this long.

This is now using the new caching mechanism in Alfred 5.5 Beta. You can update Alfred or download the previous version in the meantime if you prefer.

You can’t be having the same issue, because the one above was based on the cache never being saved due to not having the correct Alfred version.
What you’ll be be seeing is the cache being rebuilt more often and in the foreground, while previously it was always in the background and done less often. You should only see a slower build after restarting Alfred and then they’re instant.


Change intersect to intersection

What's in this pull request?

Fix specifying stdlib deployment targets in build script.

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    All supported platforms     | @swift-ci Please smoke test and merge
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    All supported platforms     | @swift-ci Please test and merge
    OS X platform               | @swift-ci Please test OS X platform
    OS X platform               | @swift-ci Please benchmark
    Linux platform              | @swift-ci Please test Linux platform

Lint Testing
    Language     | Comment
    ------------ | -------------
    Python       | @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

Python's builtin set uses intersection not intersect.

@swift-ci Please Python lint

@kuzi117 Thank you!  I wish build-script was in a statically-typed language that would prevent issues like this.

@gribozavr No problem, thanks for the quick turn around :+1:


Upgrading rspec to 3.7.0 causes 'Error in reactor loop'.

When upgrading rspec and rspec-rails from 3.6.0 resp. 3.6.1 to 3.7.0 resp. 3.7.1, my tests fail in a loop, with the following stacktrace:
Error in reactor loop escaped: Invalid argument (Errno::EINVAL)
/Users/xxx/.rbenv/versions/2.3.4/lib/ruby/gems/2.3.0/gems/puma-3.10.0/lib/puma/reactor.rb:29:in `select'
/Users/xxx/.rbenv/versions/2.3.4/lib/ruby/gems/2.3.0/gems/puma-3.10.0/lib/puma/reactor.rb:29:in `run_internal'
/Users/xxx/.rbenv/versions/2.3.4/lib/ruby/gems/2.3.0/gems/puma-3.10.0/lib/puma/reactor.rb:154:in `block in run_in_thread'

Downgrading Puma does not resolve the issue. Note, I also use capybara 2.13.0 and capybara-webkit 1.14.0.

@alexbuijs
Thanks for the issue. We need a little more detail to be able to reproduce this.
Could you please provide us with a rails app that we can clone that demonstrates the issue. Specifically it'd be great if

you could rails new an application and commit
make all the changes necessary to reproduce the issue and commit

then, provide us with a description of how to clone your application and reproduce the issue.
Thanks :)

This is probably related to our system test integration, try setting Capybara.server = :webbrick as a work around until we resolve the teething troubles we've been having.

you mean Capybara.server = :webrick with only one 'b' I guess ?

puma/puma#1582 seems related. TL;DR: Using Timecop can cause Puma to sleep for too long, causing an error.

I am also getting this on 3.11.4. We are using Timecop.

I'm running into the same issue with selenium_chrome_headless and replacing Timecop with ActiveSupport time helpers. Replacing puma with webrick fixed it for me, but it'd be better if that weren't necessary.

This looks very similar. I don't know how to get more helpful background info on how to reproduce the problem. Please let me know how I can help.
capybara (3.9.0)
capybara-selenium (0.0.6)
chromedriver-helper (2.1.0)
rspec (3.8.0)
rspec-core (3.8.0)
rspec-expectations (3.8.2)
rspec-instafail (1.0.0)
rspec-mocks (3.8.0)
rspec-rails (3.8.0)
rspec-support (3.8.0)
puma (3.12.0)
Error in reactor loop escaped: Invalid argument (Errno::EINVAL)
ruby-2.3.7@clear_value_plus/gems/puma-3.12.0/lib/puma/reactor.rb:126:in 'select'
ruby-2.3.7@clear_value_plus/gems/puma-3.12.0/lib/puma/reactor.rb:126:in 'run_internal'
ruby-2.3.7@clear_value_plus/gems/puma-3.12.0/lib/puma/reactor.rb:251:in 'block in run_in_thread'

I strongly doubt this issue has anything to do with RSpec, which is why I linked puma/puma#1582 earlier. I think this is likely a time travel (Timecop and/or ActiveSupport's TimeHelpers) + Puma issue.

Either way a more detailed backtrace is the start to reproducing whats going on here :)

Alternative quick-fix tip - don't travel to future, travel to past only
After some investigations, in our case these errors are happening only when dates are stubbed to future date. When stubbed to past date there is no errors (guess because delta is negative 😄 ), so..... just refactored everything to past.

Alternative quick-fix tip - don't travel to future, travel to past only
After some investigations, in our case these errors are happening only when dates are stubbed to future date. When stubbed to past date there is no errors (guess because delta is negative 😄 ), so..... just refactored everything to past.

Closing as stale for now, if there is any interest in this let us know and we will reopen.
Same if you could provide a reproduction case that involves rspec-rails. 😊

@mileslane Did you try @2rba's patch?

@benoittgt, I tested it tonight.
I am no longer seeing this error: "Invalid argument (Errno::EINVAL)" and I don't see errors with puma in the stack trace.  I am seeing some timeout errors.
For example:

Failure/Error: save_screenshot!(example, respond_to?(:page) && current_url.present? && page) if save_screenshot?(example)
      Net::ReadTimeout:
        Net::ReadTimeout
      # /Users/mileslane/.rvm/gems/ruby-2.3.7@clear_value_plus/gems/aws-sdk-core-3.30.0/lib/seahorse/client/net_http/patches.rb:31:in `block in new_transport_request'
      # /Users/mileslane/.rvm/gems/ruby-2.3.7@clear_value_plus/gems/aws-sdk-core-3.30.0/lib/seahorse/client/net_http/patches.rb:28:in `catch'
      # /Users/mileslane/.rvm/gems/ruby-2.3.7@clear_value_plus/gems/aws-sdk-core-3.30.0/lib/seahorse/client/net_http/patches.rb:28:in `new_transport_request'
      # /Users/mileslane/.rvm/gems/ruby-2.3.7@clear_value_plus/gems/webmock-3.4.2/lib/webmock/http_lib_adapters/net_http.rb:97:in `block in request'
      # /Users/mileslane/.rvm/gems/ruby-2.3.7@clear_value_plus/gems/webmock-3.4.2/lib/webmock/http_lib_adapters/net_http.rb:110:in `block in request'
      # /Users/mileslane/.rvm/gems/ruby-2.3.7@clear_value_plus/gems/webmock-3.4.2/lib/webmock/http_lib_adapters/net_http.rb:109:in `request'
      # /Users/mileslane/.rvm/gems/ruby-2.3.7@clear_value_plus/gems/selenium-webdriver-3.14.1/lib/selenium/webdriver/remote/http/default.rb:121:in `response_for'
      # /Users/mileslane/.rvm/gems/ruby-2.3.7@clear_value_plus/gems/selenium-webdriver-3.14.1/lib/selenium/webdriver/remote/http/default.rb:76:in `request'
      # /Users/mileslane/.rvm/gems/ruby-2.3.7@clear_value_plus/gems/selenium-webdriver-3.14.1/lib/selenium/webdriver/remote/http/common.rb:62:in `call'
      # /Users/mileslane/.rvm/gems/ruby-2.3.7@clear_value_plus/gems/selenium-webdriver-3.14.1/lib/selenium/webdriver/remote/bridge.rb:164:in `execute'
      # /Users/mileslane/.rvm/gems/ruby-2.3.7@clear_value_plus/gems/selenium-webdriver-3.14.1/lib/selenium/webdriver/remote/bridge.rb:97:in `create_session'
      # /Users/mileslane/.rvm/gems/ruby-2.3.7@clear_value_plus/gems/selenium-webdriver-3.14.1/lib/selenium/webdriver/remote/bridge.rb:53:in `handshake'
      # /Users/mileslane/.rvm/gems/ruby-2.3.7@clear_value_plus/gems/selenium-webdriver-3.14.1/lib/selenium/webdriver/chrome/driver.rb:48:in `initialize'
      # /Users/mileslane/.rvm/gems/ruby-2.3.7@clear_value_plus/gems/selenium-webdriver-3.14.1/lib/selenium/webdriver/common/driver.rb:44:in `new'
      # /Users/mileslane/.rvm/gems/ruby-2.3.7@clear_value_plus/gems/selenium-webdriver-3.14.1/lib/selenium/webdriver/common/driver.rb:44:in `for'
      # /Users/mileslane/.rvm/gems/ruby-2.3.7@clear_value_plus/gems/selenium-webdriver-3.14.1/lib/selenium/webdriver.rb:86:in `for'
      # /Users/mileslane/.rvm/gems/ruby-2.3.7@clear_value_plus/gems/capybara-3.12.0/lib/capybara/selenium/driver.rb:30:in `browser'
      # /Users/mileslane/.rvm/gems/ruby-2.3.7@clear_value_plus/gems/capybara-3.12.0/lib/capybara/selenium/driver.rb:73:in `current_url'
      # /Users/mileslane/.rvm/gems/ruby-2.3.7@clear_value_plus/gems/capybara-3.12.0/lib/capybara/session.rb:216:in `current_url'
      # /Users/mileslane/.rvm/gems/ruby-2.3.7@clear_value_plus/gems/capybara-3.12.0/lib/capybara/dsl.rb:51:in `block (2 levels) in <module:DSL>'
      # ./spec/spec_helper.rb:152:in `block (2 levels) in <top (required)>'

So, it looks like perhaps the patch is working?  :-)

Closing as stale for now, if there is any interest in this let us know and we will reopen.
Same if you could provide a reproduction case that involves rspec-rails. 😊

Please reopen this and apply the patch.  I am getting this problem with a project:
.rvm/gems/ruby-2.5.3/gems/puma-3.12.1/lib/puma/reactor.rb:128:in select' .rvm/gems/ruby-2.5.3/gems/puma-3.12.1/lib/puma/reactor.rb:128:in run_internal'
.rvm/gems/ruby-2.5.3/gems/puma-3.12.1/lib/puma/reactor.rb:253:in `block in run_in_thread'
Error in reactor loop escaped: Invalid argument (Errno::EINVAL)
Gemfile includes:
Using capybara 3.15.0
Using puma 3.12.1
Using rspec-core 3.8.0
Using timecop 0.9.1
package.json includes:
"ember-ajax": "4.0.2",
"ember-cli": "<3.5.0",
"ember-cli-emblem": "0.12.0",
"ember-cli-qunit": "4.4.0",
"ember-cli-rails-addon": "0.10.0",
"ember-cli-sass": "7.2.0",
"ember-qunit": "4.4.1",
"qunit": "2.9.2"

@benoittgt - Please reactivate this issue.

I cannot determine whether this is the correct fix, but it does prevent this showing up thousands of times in our test output:
Error in reactor loop escaped: Invalid argument (Errno::EINVAL)
.rvm/gems/ruby-2.5.3/gems/puma-3.12.1/lib/puma/reactor.rb:128:in select' .rvm/gems/ruby-2.5.3/gems/puma-3.12.1/lib/puma/reactor.rb:128:in run_internal'
.rvm/gems/ruby-2.5.3/gems/puma-3.12.1/lib/puma/reactor.rb:253:in `block in run_in_thread'

Hi @mileslane that patch is for Puma, I suggest asking them if they would welcome it for inclusion. There is nothing for RSpec to do at this time.


XDMF TImeSeriesWriter in "append" mode?

Is it possible to open an existing xdmf file (with time series data), and append data of a new timestep?
In my tests it is apparently not possible to add a new dataset once I left the "with" environment. Is there any other way to achieve it?
Thanks

Could you provide a sample code?
Usually, you should be able to append data (whatever you mean) and write it.
with meshio.xdmf.TimeSeriesReader(filename) as reader:
    points, cells = reader.read_points_cells()
    tsteps, point_data, cell_data = [], [], []
    for k in range(reader.num_steps):
        t, pdata, cdata = reader.read_data(k)
        tsteps.append(t)
        point_data.append(pdata)
        cell_data.append(cdata)

# Do whatever you want with point_data and/or cell_data

with meshio.xdmf.TimeSeriesWriter(filename) as writer:
    writer.write_points_cells(points, cells)
    for t, pdata, cdata in zip(tsteps, point_data, cell_data):
        writer.write_data(t, point_data=pdata, cell_data=cdata)

What I am trying to do is to compute and save pdata in an initial time step (nr 1):
with meshio.xdmf.TimeSeriesWriter(filename) as writer:
    writer.write_points_cells(points, cells)
    writer.write_data(1, point_data=pdata)

Then later (another session) I would like to compute new pdata in a time step nr 2 and "append it" (setting an imaginary mode="append") to the existing xdmf file:
with meshio.xdmf.TimeSeriesWriter(filename, mode='append') as writer:
    writer.write_points_cells(points, cells)
    writer.write_data(2, point_data=pdata)

At the moment, when I write to an existing xdmf file, it gets overwritten, keeping only data corresponding to time step 2.
I have tried several workarounds that like reading and writing data of previous time steps, keeping data in memory during simulation, saving fields to an auxiliary hdf5 file, or just keeping the last time step, but I am trying to avoid them as I am planning on generating big files in long simulations. Does it make sense?

There is no append mode, as far as I know. You have to rewrite all the time steps.
with meshio.xdmf.TimeSeriesWriter(filename) as writer:
    writer.write_points_cells(points, cells)
    writer.write_data(1, point_data=pdata)

    pdata2 = f(pdata)  # Compute data for next time step
    writer.write_data(2, point_data=pdata2)

I see. Not a big deal in comparison to my gains for switching to meshio. Thanks for your help.


click on a file in the tree view replace the content of the open/active tab

When I click a file in the tree view, it replaces the content of the current opened file. The desired behavior should open the file in a new tab, not replacing the content of the existing opened file. Although doubling click do open the file in a new tab, double clicking is harder than single clicking. Is there a way to configure this? Or is this just a bug?
Prerequisites

[ ] Can you reproduce the problem in safe mode?
[ ] Are you running the latest version of Atom?
[ ] Did you check the debugging guide?
[ ] Did you check the FAQs on Discuss?
[ ] Are you reporting to the correct repository?
[ ] Did you perform a cursory search to see if your bug or enhancement is already reported?

For more information on how to write a good bug report or enhancement request, see the CONTRIBUTING guide.
Description
[Description of the bug or feature]
Steps to Reproduce

[First Step]
[Second Step]
[and so on...]

Expected behavior: [What you expected to happen]
Actual behavior: [What actually happened]
Versions
You can get this information from executing atom --version and apm --version at the command line.

This used to open each file clicked on. Now, it just replaces the last opened but unedited file. There does not appear to be any menu actions to force opening into a new tab.

@caneridge Sorry for the confusion! Take a look here for more information: https://github.com/atom/atom/issues/11243#issuecomment-199959295


Cannot assign a scoped module to a specific entry point

version<EMAIL_ADDRESS>What is the current behavior?
I'm following the Code Splitting - Libraries guide to split the application vs vendor bundle entry points.  All is well except a private scoped module; it is not being placed in the vendor bundle as expected with the other packages.
If the current behavior is a bug, please provide the steps to reproduce.
Here is a gist of my actual config.
This is likely more succinctly illustrated by slightly modifying the code from the Code Splitting - Libraries guide:
var webpack = require('webpack');
module.exports = function(env) {
    return {
        entry: {
            main: './index.js',
            vendor: ['moment', '@acme/foo'] // MODIFICATION: add any scoped package
        },
        output: {
            filename: '[chunkhash].[name].js',
            path: './dist'
        },
        plugins: [
            new webpack.optimize.CommonsChunkPlugin({
                names: ['vendor', 'manifest'] // Specify the common bundle's name.
            })
        ]
    }
};

What is the expected behavior?
In the test case above, the @acme/foo should be placed in the assigned vendor bundle, but it is instead placed in the main entry bundle.
Please mention other relevant information such as the browser version, Node.js version, Operating System and programming language.
❯❯❯ node --version                                                                                ⏎ feature/entry-point-split ✱
v7.2.0

❯❯❯ sw_vers                                                                                feature/entry-point-split ✱
ProductName:	Mac OS X
ProductVersion:	10.12.1
BuildVersion:	16B2659

Enviroment:

webpack 2.2.0-rc.3
node 6.7.0
Mac OS X 10.11.6

I have same problem with webpack 2 and the same config:
const entry = {
  libs: [
    'es6-promise/auto',
    'whatwg-fetch',
    'vue',
    'vue-router'
  ],
  vendor: [
    'assets/libs/fastclick',
    'components/request',
    'components/ui',
    urls.bootstrap, // bootstrap
  ]
}
// ...
new webpack.optimize.CommonsChunkPlugin({
  names: ['vendor', 'libs', 'manifest']
})

When System.import('./component') or import('./component'),
the __webpack_require__  function will get the error: TypeError: Cannot read property 'call' of undefined

BUT when I using webpack-dev-server with the same config, System.import success and with out errors.
SO I must using this config for production build:
new webpack.optimize.CommonsChunkPlugin({
  names: ['vendor', 'libs', 'manifest'],
  minChunks: Infinity
})

Could you go up one level in stack trace and show us the generated code in the 2.82554519.js file? In addition to this I like to see the stats output for the compilation. Is manifest.e2d728.js and 2.82554519.js part of the same compilation?

@sokra
stats with bug
new webpack.optimize.CommonsChunkPlugin({
  names: ['vendor', 'libs', 'manifest']
})

stats without bug
new webpack.optimize.CommonsChunkPlugin({
  names: ['vendor', 'libs', 'manifest'],
  minChunks: Infinity
})

I don't know if my commonsChunkConfig is correct.
The CommonsChunkPlugin document can't meet my needs.

Hey @rosskevin.
Does this issue still happen if you change
        entry: {
            main: './index.js',
            vendor: ['moment', '@acme/foo'] // MODIFICATION: add any scoped package
        },

to
        entry: {
            main: './index.js',
            vendor: './vendor' // MODIFICATION: add any scoped package
        },

and inside vendor you do the following:
import 'moment';
import '@acme/foo';

Curious whether there is some sort of resolver snafu or this is related to plugins itself. Or something different. Or even better, could I convince you to make a small reproducible repo in which this happens?

@blade254353074 Are you using the extract-text-plugin? Could you try to disable it and check if this affects the bug?

@sokra ...You are right. After disable extract-text-plugin, the builds are correct.

@sokra Is that a bug caused by  extract-text-plugin?

@sokra Is that a bug caused by extract-text-plugin?

yes


Faster augmentation

I've made very fast augmentation server/iterator for keras version of project
It augments approx 140 images per second(original caffe C++ code augments 30).
Trick is in making whole augmentation with one single warpAffine, and vectorized generation of heamaps without 2 nested loops for coordinates.
https://github.com/anatolix/keras_Realtime_Multi-Person_Pose_Estimation
If you like it I could make pull request here

@anatolix That is amazing. Pull Request is always welcome.
I will wait for your awesome codes!

@anatolix Any plan to make pull request recently? It would be nice if data augmentation can be speed up as training is pretty slow right now.

Close due to inacitivity.


Replaced WebL10n to i18next in Media Viewer

Migrated Media Viewer to i18next

@llaske, could you please review this PR

Nice. Thanks.


An error occurred in 'crypto_sign_verify_detached' on the chrome browser

I used a web pack to make a file and run it on the browser.
Error is
index.js:28 Uncaught Error: WASM not loaded. Wait for Sha512.ready(cb)

It works well in Safari and Firefox.

can you post npm ls here so we can see which versions of the dependencies where installed?

npm ls is
npms.txt
My test code is https://github.com/MichaelKim20/boa-sdk-ts-test

I solved it using setTimeout(function() {}, 100);
Chrome browser seems to load slowly on WASM compared to other browsers.
Thank you.

It does atm because the module is larger than 4kb. Next version it will be able to load sync

Thank you very much for solving this problem.


Update services.md

Reflect product name change. Azure Machine Learning Workbench itself is deprecated, but the name Azure Machine Learning Service is still valid.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/aws-professional/services.md
:white_check_mark:Succeeded
View

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


Improvise logging for Channel connection timeout on platform code

Why?
I've been calling Realtime#channels#get#attach without calling Realtime#connect first
This iteratively tries to attach to the channel and on timeout, RealtimeChannelStatus will be set as suspended. I wasn't sure until @paddybyers asked me whether I connected to the realtime instance in the first place!
Suggestion
Improvise VERBOSE/INFO logging on timeout and if realtime instance status is not connected to show:
attach timeout, realtime instance is not connected
retrying attach

NOTE: This enhancement must be done on platform code ably-java and ably-cocoa

This suggestion is one possible solution. There may be others (e.g. fail faster).
See internal conversation.

Hmm. I just went through conversation and there doesn't seem to be a decision on how to tackle this. Considering this is an issue rooting from the platform implementations I would say they should be handled there. WDYT @QuintinWillison ? If so I can create issues for corresponding platforms

@ikbalkaya yes, please create platform issues and link them back to this issue. This issue should remain open until those dependencies have been updated here.


can you provide simple example

Example route /admin how to prevent a normal user or authorize but not admin to access that route? Sorry I am new to nodejs and express.

auth.role('admin', (req, done) => {
    done(null, getUser(req).type === 'admin');
  });
...
auth.action('administer', ['admin', 'editorz']);
...
app.get(
    '/somePath',
    auth.can('administer'),
    (req, res, next) => {})

The project ships with a test suite which shows some examples.


[TextField] Clicking on label does not focus the input in IE11 (mouse only)

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior
Clicking on the label, when it sits "inside" the input will focus the input.
Current Behavior
This is only happening in IE11 and only on desktop with a mouse (tab focus works as expected and laptop trackpad works as expected). If you click on the label while it is over top of the input, it moves the label to above the input, but the input does not receive focus. The user must click a second time to focus the input. If the user clicks within the input but not on the label, focus is received as expected.
Steps to Reproduce (for bugs)
https://coop.com/login

Navigate to login page in IE11 on a desktop with a mouse attached
Click on the User Name or Password labels sitting on top of the inputs
Notice that the label moves to above the input but does not focus the input
Click a second time to focus the input

Context
IE11 users have to click twice for the input to receive focus if the first click is on the label. Leads to user confusion and bad UX.
Your Environment

Tech
Version

Material-UI
^1.0.0-beta.41

React
16.3.1

browser
IE11

OS
Windows 10

@mikeriley131 I can't reproduce the double click issue. Have you made any progress?

@oliviertassinari Strange. What version of Windows is that? I'm still seeing it on my end. Make sure you haven't yet focused any inputs and make sure you're clicking on the label (still have the arrow cursor and not the text cursor).

I have tried Windows 10, 8.1 and 7. I'm clue less.

Clueless as in you're not able to reproduce at all or clueless as in now you're seeing it but can't figure out why?

I'm clueless in a sense of I can't reproduce and I don't see what could explain such behavior.

Strange because I'm not the only one that can reproduce this. Like I said in the original post, more of an annoyance than an issue. I'll keep digging in and let you know if I find anything.

I'm having a similar issue where clicking the label of a required TextField, while it is inside the input, does not trigger the shrink animation, nor does it give focus to the input. Should I create another issue or is this related? Happens on Chrome/Firefox/Safari
Example

this happens to me on latest chrome can get focus on click, but if I hold click it gets focus. Any ideas?

Hmm, I can't reproduce this on Windows 10. IE11 or Chrome 76

I have this problem in safari for 4.3.0

@Ch-Valentine Did you provide an id?

@Ch-Valentine Did you provide an id to the textfield?

Thank you, it solves my problem, you need to have id because label will use id to add to <labelfor='id'>


Gangsters Organized Crime, Main Menu is blacked out

I downloaded your patch, the october 2019 for windows 10 and the game wont show the main menu at all, it goes through the all the starting videos and then nothing, tried running in the compatibility that you showed on the patch page and then some others yet nothing changes

Yeah, my fix not perfect yet.  The issue with this game is that certain controls (labels, buttons, etc.) will be pushed to the back so they are hidden.  My "fix" simply activates the main window which will reorder the controls so that you can see them.  If the latest release does not work try using an older one.  Maybe one from early 2018 or late 2017.

I just posted an update patch that should address this issue.  You can see the update here:  Gangsters Organized Crime patch

This should be fixed with the latest update:  https://github.com/elishacloud/dxwrapper/wiki/Gangsters-Organized-Crime


Moved "heading="Ability Build" to json file

whoops, I saw #1236  first even though this was opened first.  Sorry about that, but thank you for the contribution!


[Event Change] Codeunit::"Copy Document Mgt." - Function CopySalesInvLinesToDoc - OnAfterCopySalesLineFromSalesLineBuffer

We like to request the following Event:
Object: Codeunit::"Copy Document Mgt."
Function: CopySalesInvLinesToDoc
Publisher Event: OnAfterCopySalesLineFromSalesLineBuffer
Reason: add an extra Parameter
Where is the event placed:
Event Code:
[IntegrationEvent(false, false)]
local procedure OnAfterCopySalesLineFromSalesLineBuffer(var ToSalesLine: Record "Sales Line"; FromSalesInvLine: Record "Sales Invoice Line"; IncludeHeader: Boolean; RecalculateLines: Boolean; var TempDocSalesLine: Record "Sales Line" temporary; ToSalesHeader: Record "Sales Header"; FromSalesLineBuf: Record "Sales Line"; var FromSalesLine2: Record "Sales Line"; FromSalesLine: Record "Sales Line"; ExactCostRevMandatory: Boolean)
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


v2.0.0 is correct version from JitPack

Hi, thanks for your work.
Please update Readme to correct version from Jitpack.
It's 'v2.0.0' not '2.0.0'.
compile 'com.github.spiddekauga:MaterialShowcaseView:v2.0.0'
Or add new release :)

Thanks for noticing!
I've updated the tag to 2.0.0 now :)


fixes and a possible canvas addition

What I am not sure about is fill_layout (see #202). I added it because it was needed to push layouts directly, but currently I am working on removing the dependency on text altogether. (And instead push the glyph outlines).

fill_layout is perfectly fine. I was thinking of adding it myself actually.

Hmm, we shouldn't return a reference from Outline::last() then, but let's fix that in a follow up.

    pub(crate) outline: Vec<LineSegment>, // Could be Vec<(start, end)>

not much that can be done here …


"WASM module instantiate failed: allocate memory failed" when using Alloc_With_Pool on x86-32

Regardless of how large I set the heap size, when using x86-32, I get the error "WASM module instantiate failed: allocate memory failed". The exact same program (with the same build options otherwise) works on x86-64.
I'm using wasm_runtime_full_init as described in the embedding documentation. The issue arises when calling wasm_runtime_instantiate.
I don't yet have a minimal test case (that isn't tied into proprietary code) for this, but I can reproduce this with a very simple test WASM module (a single test function that takes and int32 and returns the same) compiled using emscripten in stand alone mode (WASI compliant). If it would be useful, let me know and I can make a minimal C program that exhibits the issue.
I'm using WAMR-1.2.2 built as follows:
set(WAMR_BUILD_PLATFORM "linux")

if(CMAKE_SYSTEM_PROCESSOR MATCHES "^(arm64|aarch64)")
    set(WAMR_BUILD_TARGET "AARCH64")
elseif(CMAKE_SYSTEM_PROCESSOR MATCHES "^(armv7a|cortex)")
    set(WAMR_BUILD_TARGET "ARMV7")
elseif(CMAKE_SYSTEM_PROCESSOR STREQUAL "x86_64")
    set(WAMR_BUILD_TARGET "X86_64")
    set(WAMR_BUILD_SIMD 1)
elseif(CMAKE_SYSTEM_PROCESSOR STREQUAL "x86")
    set(WAMR_BUILD_TARGET "X86_32")
else()
    message(SEND_ERROR "Unsupported build target platform ${CMAKE_SYSTEM_PROCESSOR}!")
endif()

set(WAMR_BUILD_INTERP 1)
set(WAMR_BUILD_FAST_INTERP 1)
set(WAMR_BUILD_AOT 1)
set(WAMR_BUILD_LIBC_BUILTIN 1)
set(WAMR_BUILD_LIBC_WASI 1)
set(WAMR_ROOT_DIR "${CMAKE_CURRENT_SOURCE_DIR}/wasm-micro-runtime")

include (${WAMR_ROOT_DIR}/build-scripts/runtime_lib.cmake)
add_library(vmlib ${WAMR_RUNTIME_LIB_SOURCE})
target_include_directories(vmlib PUBLIC ${WAMR_ROOT_DIR}/core/iwasm/include)
target_link_libraries (vmlib INTERFACE -lm -ldl -lpthread)

It appears after some debugging that it tries to allocate 16 MB when I have set the pool to be 10 MB. Also for wasm_runtime_instantiate I'm passing a stack size of 2048 and same for the heap size. I don't see why it would try to allocate a whole 16 MB. This is more than I can afford on my 32-bit target.

The issue goes away if I rebuild the test program with WASI-SDK instead of emscripten in standalone mode. Not sure what is going on, possibly an emscripten bug? Also why doesn't the issue happen in 64-bit builds of WAMR?

can you share the wasm module which causes the problem?

can you share the wasm module which causes the problem?

Yes, this was a simple test module for a unit test of our C++ bindings for WAMR. In the attached archive is both the source code and the compiled module: simple_wasm.tar.gz
The build command was: emcc -O3 simple_wasm.c -o simple_wasm_emcc.wasm -s STANDALONE_WASM
If I instead build it with WASI-SDK, it works just fine: /opt/wasi-sdk/bin/clang -O3 simple_wasm.c -o simple_wasm_wasisdk.wasm
The strange thing is that it believes it need 16 MB of allocation, but only in the 32-bit build of WAMR. The 64-bit build of WAMR does not fail the memory allocation, even though the same memory pool with the same settings is used.

thank you.
because the module has 16MB linear memory, 16MB allocation is normal.
depending on configurations, the linear memory is served by mmap. (ie. out of the configured memory pool.)
i guess it's what happens for your 64-bit case.

Ah okay, thanks. I guess the issue is that emscripten has weird defaults then? I'm very new to wasm, so I hope you can forgive me for not understanding all the intricate details of it.

Ah okay, thanks. I guess the issue is that emscripten has weird defaults then? I'm very new to wasm, so I hope you can forgive me for not understanding all the intricate details of it.

although i'm not familiar with emscripten, i guess it has some option to control the "initial-memory".


Failed to Setup

Describe the bug
I updated to version 6.3.0 through HACS this morning and after restarting Eufy devices are offline.
Under integrations, Eufy Security shows "Failed to set up"
The Eufy security add-on starts and appears to connect to the base station before it errors.
Additional information
Go to Settings -> System -> Repairs -> Click on 3 dots (...) -> System Information and get Version and Installation Type to below fields;

Home Assistant Installation Type (OS):

Home Assistant Core Version:  Home Assistant 2023.6.1

Eufy Security Add-on Version: Current version: 1.3.0

Eufy Security Integration Version: v6.3.0

Logs from Eufy Security Add-on (either from Add-ons page of Home Assistant or Docker output):
2023-06-15 00:28:13.006  INFO  Eufy Security server listening on host <IP_ADDRESS>, port 3000
2023-06-15 00:28:24.276  INFO  Push notification connection successfully established
2023-06-15 00:28:24.435  INFO  Connected to station xxx on host xxx and port 10348
2023-06-15 00:28:44.424  ERROR Station xxx- CMD_NOTIFY_PAYLOAD Error:
{
error: SyntaxError: Unexpected token  in JSON at position 35
at JSON.parse ()
at P2PClientProtocol.handleDataControl (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1450:43)
at P2PClientProtocol.handleData (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1043:18)
at P2PClientProtocol.parseDataMessage (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1031:26)
at P2PClientProtocol.handleMsg (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:868:26)
at Socket. (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:84:56)
at Socket.emit (node:events:513:28)
at UDP.onMessage [as onmessage] (node:dgram:930:8),
payload: '{"cmd":1550,"payload":{"status":1}}\x00'
}
2023-06-15 00:28:51.629  ERROR Station xx- CMD_NOTIFY_PAYLOAD Error:
{
error: SyntaxError: Unexpected token  in JSON at position 35
at JSON.parse ()
at P2PClientProtocol.handleDataControl (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1450:43)
at P2PClientProtocol.handleData (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1043:18)
at P2PClientProtocol.parseDataMessage (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1031:26)
at P2PClientProtocol.handleMsg (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:868:26)
at Socket. (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:84:56)
at Socket.emit (node:events:513:28)
at UDP.onMessage [as onmessage] (node:dgram:930:8),
payload: '{"cmd":1550,"payload":{"status":0}}\x00'
}
2023-06-15 00:29:28.163  INFO  Disconnected from station xx
2023-06-15 00:29:33.329  INFO  Connected to station xxon host <IP_ADDRESS> and port 14801
2023-06-15 00:30:36.982  INFO  Disconnected from station xx
2023-06-15 00:30:42.150  INFO  Connected to station xxon host <IP_ADDRESS> and port 10447
2023-06-15 00:31:45.867  INFO  Disconnected from station xx
2023-06-15 00:31:51.030  INFO  Connected to station xxon host xx and port 27622
2023-06-15 00:32:15.608  ERROR Station xx- CMD_NOTIFY_PAYLOAD Error:
{
error: SyntaxError: Unexpected token  in JSON at position 35
at JSON.parse ()
at P2PClientProtocol.handleDataControl (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1450:43)
at P2PClientProtocol.handleData (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1043:18)
at P2PClientProtocol.parseDataMessage (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1031:26)
at P2PClientProtocol.handleMsg (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:868:26)
at Socket. (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1732:56)
at Socket.emit (node:events:513:28)
at UDP.onMessage [as onmessage] (node:dgram:930:8),
payload: '{"cmd":1550,"payload":{"status":1}}\x00'
}
2023-06-15 00:32:54.720  INFO  Disconnected from station xx
2023-06-15 00:32:59.880  INFO  Connected to station xxon host xx and port 23678
2023-06-15 00:34:03.527  INFO  Disconnected from station xx
2023-06-15 00:34:08.691  INFO  Connected to station xx on host xx and port 28400
2023-06-15 00:35:12.407  INFO  Disconnected from station xx
2023-06-15 00:35:17.570  INFO  Connected to station xx on host xx and port 16362
2023-06-15 00:36:21.232  INFO  Disconnected from station xx
2023-06-15 00:36:26.395  INFO  Connected to station xx on host xx and port 23709

Would you share your device with me in case further debugging required? (Yes):
Additional context

Solved by reinstalling and updating to the new add-on version. https://github.com/bropat/hassio-eufy-security-ws


Move cluster-defined enums/bitmaps into a separate header.

We want to put basic cluster-defined constants (enums/bitmaps) into a
header we can use from anywhere (just like data model concepts like
NodeId and whatnot).  But we don't want that for the C++ structs in
cluster-objects, which can have ABI issues.
Move the constants into a separate header, put that header into
src/lib/core in terms of include dependencies.  Add an actual src/lib/core header people should be including.
Problem
Want to use cluster-defined constants in "platform" and whatnot code, but the dependencies are not our friends.
Change overview
Move these constants into a separate file which depends only on stdint.h and can be treated as a core header.
Testing
Tree compiles.

/rebase


Various numeral conversion errors

1001 outputs 千, expected : 千一
10000 outputs 万, expected : 一万
123456789 misses "一" before 億. The test case is also wrong.
1000000000000 outputs 兆億万, expected : 一兆
10100100100101 outputs 十兆千億十万百, expected : 十兆千一億十万百一. I suspect this one to be a mix of previous issues.

Ok, I will double check this and add more unit tests.
This is quiet an alpha buggy release :)

Hmm, a PR ils definitely possible.
Actually I have my own implementation of this but mine is pretty different from yours as it based on integer computations. I can reformat what I have, rename some variables and should have a drop-in replacement for your current converter if you are interrested.
It also supports "numbers to speech" (i.e. outputs "ichi man ichi" for 1001). This is a feature request I was about to make btw.

That would be great :+1:
Is there a link or git repo to take a look?

Not yet, I might create a gist file later today.

Published on my fork :  https://github.com/Akeru/jpnforphp/commit/68621a8722a956222cc0ab5a8eb34f80003adc21

Oh, and it should also add support for #44


Use inline hard-coded answer URL value

Other language examples just inline the answer URL. This means you can see a real NCCO in the example on Nexmo Developer too.

Done already. Thanks @leggetter :)


Add Pittsgrove School District domain

@zanbucks First stage of verification passed, official domain is schalick.pittsgrove.net as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision. Proof of domain ownership: https://schalick.pittsgrove.net/school_counseling_dept_/meet_our_staff

Thank you. Let me know if you need any additional information.
On Fri, Oct 6, 2023 at 11:33 PM Philip Torchinsky @.***>
wrote:

@zanbucks https://github.com/zanbucks First stage of verification
passed, official domain is schalick.pittsgrove.net as far as I verified.
This is just an informational note. Pull request is still in the review. I
appreciate your patience while waiting for the final decision. Proof of
domain ownership:
https://schalick.pittsgrove.net/school_counseling_dept_/meet_our_staff
—
Reply to this email directly, view it on GitHub
https://github.com/JetBrains/swot/pull/18959#issuecomment-1751584696,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A77E6ZWUHUWJSZRSINPNARLX6DEQDAVCNFSM6AAAAAA5WRUYTOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJRGU4DINRZGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Daniel Rozanski
Mathematics and Computer Science Teacher
PITTSGROVE TWP. PUBLIC SCHOOLS
A.P. Schalick High School
856-358-2054 ext. 3146
@.***
“A gold medal is a wonderful thing. But if you’re not enough without it,
you’ll never be enough with it.” - Irv Blitzer, Cool Runnings

@zanbucks Thank you for your patience while waiting for a review and processing your request. Pull request merged.


copyq: 3.8.0 -> 3.9.0

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/copyq/versions.
meta.description for copyq is: '"Clipboard Manager with Advanced Features"'.
meta.homepage for copyq is: '"https://hluk.github.io/CopyQ"
Release on GitHub
Compare changes on GitHub

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
/bin/sh passed the binary check.
1 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 3.9.0 with grep in /nix/store/rx99djbbv9qfwzskj21pcmsa392if02x-CopyQ-3.9.0
directory tree listing: https://gist.github.com/74891a0be2f0483f18ba20bd2062baf1
du listing: https://gist.github.com/4414711ca204ce14427e0a4baa560a62

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

3 total rebuild path(s)
1 package rebuild(s)
1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
copyq

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/rx99djbbv9qfwzskj21pcmsa392if02x-CopyQ-3.9.0 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A copyq https://github.com/r-ryantm/nixpkgs/archive/6f03e2d9726c65ca8f1ee8e18f396c638f90d73b.tar.gz

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

tested with nix-review, could start the server, copy some text and it appeared in the search window.


Icon should be selectable from a URL

Reported by emmanuelbernard on 25 Jun 2014 12:59 UTC
Most icons will be the logo of the OTP provider (Google, Dropbox etc etc).
The current step is to copy the image to the camera roll and then select it.
It would be nice to be able to point to a URL and have FreeOTP copy the image.
Icons is an awesome feature BTW, it makes it faster to find the right OTP in a big list.

Comment by npmccallum on 19 Aug 2014 14:58 UTC
You can do this already. Open the URL in your browser and save the image to the image library. It is now available to FreeOTP. Given that most people will be searching for an image for their token via Google anyway, I think this work-flow is sufficient.
We also plan to implement the ability to specify an image URL via the QR code. This will allow admins to provision a stock image. This is already implemented on Android and will be soon implemented on iOS.


Flickering bug in using data_collector.py to get semantic segmentation

Hi,
I try to use your ''data_collector.py'' to collect some data with semantic segmentation ground truth by adding the semantic segmentation camera in ''bird_view/utils/carla_utils.py''. Among the good semantic segmentation images (the first figure), there are always some flickering frames whose segmentation is wrong (the second figure). I checked the raw data from the semantic segmentation camera. It seems in those flickering frames the size of the raw data is much smaller than the regular size and there are 'nan' in the the raw data before converted to 'uint8'.
Correct semantic segmentation:

Wrong semantic segmentation:

I wonder if anyone ever has such problems and I would be grateful if anyone would help me with it.

Please consider posting this in the original CARLA repo.


Could not load NIB in bundle: 'NSBundle  (loaded)' with name 'RMessageView'

Hi,
I recently updated an app that uses RMessage (which I am using for long time), however, some apps crash with the following message:
Could not load NIB in bundle: 'NSBundle  (loaded)' with name 'RMessageView'
Using it in iOS 13.3 on an iPad.
Any ideas?

Will look into this today. Hopefully its something I can reproduce.

Well, I can't reproduce it as I have 2 different iPads (one iPad mini and one iPad Air), and on both of them it works fine, it's very occasional I get feedback with this error, so I don't really get it. I am using Pod's in my project, so I should have the latest version..

Can you pull develop and tell me if it fixes anything. Something I forgot to ask is what version of RMessage are you using? Based on your error message it seems your are using the pre-swift version.

@donileo, the app is in a production state, pulling a developer version and releasing it would be a bit risky for me, further more it seems to be some isolated issues only, not at all reproducible..
I am using Pods, this was the output of the latest build:
RMessage (2.3.2):
- HexColors (~> 4.0)
- PPTopMostController
(my project is in Objective C)
Hope this helps

Hello,
I've come across this issue too.
I'm able to reproduce the issue when turning off mobile data and wifi.
It occurs when I call:
[ErrorMessage showConnectionError:self.navigationController
errorMessage:errorMessage
errorCode:errorCode
refreshMethod:]
Using on iPhone XR running iOS 13.3.
Hope it helps.
Thanks

Made some changes that I believe fix these issues. Commit for the change is 91188050b443ea6d0550d7cd008a57e2830c87a8. Please pull develop and test. If all seems ok I will go ahead and put out a 2.3.4 release.

Just released a new version (2.3.3) via Pod; easier to test the fix now.

I just did a pod update and it went to version 2.3.3. and when I ran I got the following crash:
*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Could not read RMessage config file from main bundle with name RMessageDefaultDesign.json' *** First throw call stack: ( 	0   CoreFoundation                      0x00007fff23e3cf0e __exceptionPreprocess + 350 	1   libobjc.A.dylib                     0x00007fff50ba89b2 objc_exception_throw + 48 	2   CoreFoundation                      0x00007fff23e3cc88 +[NSException raise:format:arguments:] + 88 	3   Foundation                          0x00007fff258b8bd2 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 191 	4   RMessage                            0x000000010a48503e +[RMessageView setupGlobalDesignDictionary] + 494 	5   RMessage                            0x000000010a4853ab +[RMessageView addDesignsFromFileWithName:inBundle:] + 107 	6   RMessage                            0x000000010a4841b5 +[RMessage addDesignsFromFileWithName:inBundle:] + 101 	7   Salonbiz Book                       0x0000000104caa057 -[HomeViewController viewDidLoad] + 263
as seen I am calling the following method for it to read my custom RMessageDesigns.json:
[RMessage addDesignsFromFileWithName:@"RMessageDesigns" inBundle:NSBundle.mainBundle];
Thought you should know. I reverted to 2.3.2 and working again.

If it was easier for me to test 2.3.2 this would be easier to fix. Unfortunately latest Xcode doesn't support build for iOS 7 which is the target 2.3.x series supports. Downgrading Xcode to something like Xcode 9 which does support 2.3.x requires me to run on something lower than catalina which I don't have a spare machine to do that with.

Can you please clean your build directory and your derived data and see if this happens?. I am not seeing that error message when building with latest Xcode on my end.

Okay, cleaning did not work. But I did debug the code, and one issue is here: in 2.3.3 a static RMessageBundle property was added, but the init code fails to locate it properly. It fails on this line:
  NSURL *resourceBundleURL = [appBundle URLForResource:@"RMessage" withExtension:@"bundle"];
which then cause the lookup for the default json file to fail and then crash when trying to read.
in 2.3.2 it used a simple [NSBundle [self class]] which appears to work fine. I can debug further if you like, but for now i will be using 2.3.2.

Side question: what would be the possibility of lowering the iOS version requirement of RMessage 3.0 down to iOS 9.3? Are there iOS 11 specific features it is using?

Lowering the requirement after its been declared for the 3.0 series isn't going to happen. That would be breaking the contract as far as what has already been declared for that release. The real issue is fixing this problem which is tedious on my end because I can't reproduce. On my end it works correctly on the latest Xcode 11 and iOS 13.1 runtime. I tried downgrading to Xcode 9 so that I can run on the lowest supported iOS Simulator runtime of 7.0 and debug the issue but I can't because Xcode 9 isn't supported by Mac OS Catalina and I don't have a separate machine to run that on. I'll to see if I can somehow run on an iOS 9 runtime and see if I can catch the issue you are seeing.

FYI, I am running with Xcode 11.5 on an iPad 13.5 simulator. So not an issue with iOS 9..

Ok, can you try the RMessage demo target and see if you get the crash there? Maybe its specific to integrating RMessage into an app.

Ok, so just tested on a brand new Xcode 11.1 project with iPhone SE2 simulator, brought in RMessage 2.3.3 using Cocoapods. Using a RMessageDesigns.json file in my main app bundle via [RMessage addDesignsFromFileWithName:@"RMessageDesigns" inBundle:NSBundle.mainBundle];. Works perfectly on my end.

Just to be sure, you included:
use_frameworks!
in your Podfile?
I narrowed it down to this line:
NSBundle *appBundle = [NSBundle mainBundle];
which returns my main .app and so the next URLForResource will fail, since the resource is not a child. If I instead change that line to:
NSBundle *appBundle = [NSBundle bundleForClass:[self class]];
then everything works as expected. Thanks!

Ahh. That’s exactly the problem. Please see https://github.com/CocoaPods/CocoaPods/issues/3226. Given that, I should have a fix soon.

Great. Look forward to it. :-)

@tylerwilson Ok can you point your RMessage pod to 2.x.x_develop now and retest?

Okay, I updated my Podfile to:
pod 'RMessage', :git => 'https://github.com/donileo/RMessage.git', :branch => '2.x.x_develop'
updated, ran and all good! Thank you!

@tylerwilson Thanks for the bug report. Will put out a 2.3.4 release sometime soon today or tommorrow hopefully.

2.3.4 Release is now on Cocoapods.

Verified that all is working for me now with 2.3.4. Thank you!

Closing this issue out as I believe it is fixed.

Hi, I still see the errors  with 2.3.4.. Many app crashes with the following debug info:
Could not load NIB in bundle: 'NSBundle  (not yet loaded)' with name 'RMessageView'
-or-
Could not load NIB in bundle: 'NSBundle  (loaded)' with name 'fwX-4r-u7q-view-Y9P-0D-SwC' and directory 'Main.storyboardc'

Hi, I still see the errors  with 2.3.4.. Many app crashes with the following debug info:
Could not load NIB in bundle: 'NSBundle  (not yet loaded)' with name 'RMessageView'
-or-
Could not load NIB in bundle: 'NSBundle  (loaded)' with name 'fwX-4r-u7q-view-Y9P-0D-SwC' and directory 'Main.storyboardc'

Hi, I still see the errors  with 2.3.4.. Many app crashes with the following debug info:

Could not load NIB in bundle: 'NSBundle  (not yet loaded)' with name 'RMessageView'

-or-

Could not load NIB in bundle: 'NSBundle  (loaded)' with name 'fwX-4r-u7q-view-Y9P-0D-SwC' and directory 'Main.storyboardc'

What iOS version are you testing with?

Hi, I still see the errors  with 2.3.4.. Many app crashes with the following debug info:

Could not load NIB in bundle: 'NSBundle  (not yet loaded)' with name 'RMessageView'

-or-

Could not load NIB in bundle: 'NSBundle  (loaded)' with name 'fwX-4r-u7q-view-Y9P-0D-SwC' and directory 'Main.storyboardc'

What iOS version are you testing with?

I am receiving crash reports from various users. All of them are iOS 14.x with the masters report for iOS 14.3
I don’t know if it helps, but my project is in Objective C

I am receiving crash reports from various users. All of them are iOS 14.x with the masters report for iOS 14.3
I don’t know if it helps, but my project is in Objective C

Can you reproduce the crashes yourself if you run on a fresh project with iOS14?

Can you reproduce the crashes yourself if you run on a fresh project with iOS14?

No, that is the issue. It works fine on all my tests and devices. It’s just that some users report the app crashes. Totally random. I am not able to reproduce it.

No, that is the issue. It works fine on all my tests and devices. It’s just that some users report the app crashes. Totally random. I am not able to reproduce it.


Add in-place reformat

Clang-format allows to do in-place reformatting with -i option. Would be useful to have the same in the script as well.
Example - using in git pre-commit hook to auto-format all the files. Probably it should still exit with non-zero exit code if at least one file was reformatted though.

I would recommend git clang-format for this kind of things.

I believe this issue can be closed, as the -i flag has been added in:

https://github.com/Sarcasm/run-clang-format/pull/30

Indeed, closing, thank you.


Integrate OpenDAL

ref: https://github.com/spring-rs/spring-rs/issues/13

[ ] Try using the build script dynamic set OpenDAL feature
[ ] doc

Please also provide the documentation.

Please also provide the documentation.

sure

@holmofy I don't know how to test OpenDAL layers, only test blocking, so maybe someone can help this one day = .=

I created a contrib-plugins directory, and the community contributed plugins can be placed in this directory. There is a README.md file in Chinese and English. Please put the introduction of opendal-plugin in the list.

clippy lint failed.    what is this ❓
error: failed to run custom build command for `etcd-client v0.14.0`

Caused by:
  process didn't exit successfully: `/home/runner/work/spring-rs/spring-rs/target/debug/build/etcd-client-688806136fda4a82/build-script-build` (exit status: 101)
  --- stdout
  cargo:rerun-if-changed=proto
  cargo:rerun-if-changed=proto/auth.proto
  cargo:rerun-if-changed=proto/kv.proto
  cargo:rerun-if-changed=proto/rpc.proto
  cargo:rerun-if-changed=proto/v3election.proto
  cargo:rerun-if-changed=proto/v3lock.proto
  cargo:rerun-if-changed=proto

  --- stderr
  thread 'main' panicked at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/etcd-client-0.14.0/build.rs:17:10:
  Failed to compile proto files: Custom { kind: NotFound, error: "Could not find `protoc`. If `protoc` is installed, try setting the `PROTOC` environment variable to the path of the `protoc` binary. To install it on Debian, run `apt-get install protobuf-compiler`. It is also available at https://github.com/protocolbuffers/protobuf/releases  For more information: https://docs.rs/prost-build/#sourcing-protoc" }
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...

clippy lint failed. what is this ❓
error: failed to run custom build command for `etcd-client v0.14.0`

Caused by:
  process didn't exit successfully: `/home/runner/work/spring-rs/spring-rs/target/debug/build/etcd-client-688806136fda4a82/build-script-build` (exit status: 101)
  --- stdout
  cargo:rerun-if-changed=proto
  cargo:rerun-if-changed=proto/auth.proto
  cargo:rerun-if-changed=proto/kv.proto
  cargo:rerun-if-changed=proto/rpc.proto
  cargo:rerun-if-changed=proto/v3election.proto
  cargo:rerun-if-changed=proto/v3lock.proto
  cargo:rerun-if-changed=proto

  --- stderr
  thread 'main' panicked at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/etcd-client-0.14.0/build.rs:17:10:
  Failed to compile proto files: Custom { kind: NotFound, error: "Could not find `protoc`. If `protoc` is installed, try setting the `PROTOC` environment variable to the path of the `protoc` binary. To install it on Debian, run `apt-get install protobuf-compiler`. It is also available at https://github.com/protocolbuffers/protobuf/releases  For more information: https://docs.rs/prost-build/#sourcing-protoc" }
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...

seems lint --all-features enable feature services-etcd ?


Causes deferred long-running timer task(s) error.

When using HackTimer.js, In my browser's console a warning is logged :
Deferred long-running timer task(s) to improve scrolling smoothness. See crbug.com/574343.
And The whole website lags.
Any fix for this?
Using latest File.

Could you please give some more information

browser version
used libraries (jQuery, ...)
demo page to reproduce issue

Google Chrome	51.0.2704.84 (Official Build) m (32-bit)
Using jQuery with some other plugins.
Demo Page: I can personal message you.

I just added console.log(time);
here :
if(data.hasOwnProperty('time')) { time = data.time; console.log(time); }
And when monitoring on chrome, the time that is being logged is nice at some parts but at some parts it's 1000,2000,3000 and even 4000ms which I think is causing the long-running timer task(s) error because as I read on the forums if time is >50ms it will cause the issue.

Did you find issue on device with touchscreen or desktop pc?
Could you please send me e-mail<EMAIL_ADDRESS>with demo page?

I found this issue on a mobile device with a touch screen, Yes! Desktop Mode woks flawlessly!


[1.4] MODCLUSTER-745 CI: Optionally test with JDK 17 as well

https://issues.redhat.com/browse/MODCLUSTER-745

Replaced by https://github.com/modcluster/mod_cluster/pull/567 - which is only about testing; not compiling per se.


If entering superuser password fails, offer to retry

Q: Is the ability to do this a configuration option for sudo, and if so can we mirror that behaviour?

This would be great. As it is, I mistyped my password on the last step, and I'm not sure the best way to proceed if I don't want to do the download/unxipping all over again.


Simplify Dockerfilei386 by using i386/python base image

Use i386/python:3.6-slim instead of i386/ubuntu:18.04, save the time and network bandwidth to install python, also align to Dockerfile(python:3.6-slim), make the environment more consistent, also save the disk space and image size:
REPOSITORY                    TAG                 IMAGE ID            CREATED             SIZE
new                           latest              7d03381094c9        6 minutes ago       145MB
old                           latest              1a5e52fb3e2e        11 minutes ago      485MB

We use the docker image to build some binaries via AppVeyor. If you could please check the errors for the failing check, that would be helpful.
Your point on reducing file size is awesome.

I didn't notice that AppVeyor will be affected, will take a look and see how to deal with it.

Looks like the binutils package is missing, I'll see not using slim image or install it manually, which one is better here.
https://pyinstaller.readthedocs.io/en/stable/requirements.html#gnu-linux

@rafaelpivato should be fixed now!


Compatibility issues with built in Vim

So I really like this plugin and want to keep using it but when running it alongside the built in VIM keybindings it cause an annoying issue:
If I call vimium: show markers then they show up but whatever I press does not get captured by vimium because the VIM keybindings capture it first and do not allow passthrough. The only way I can get vimium to capture the key strokes is to press a first to get into insert mode and then call vimium: show markers.
Is there any way this extra step can be removed? Its most problematic when I'm in a area where there is no insert mode possibility like a side panel.
Maybe making the vimium event listener higher priority than vim?

I tried to figure out a way I could use a shortcut key to run a macro that first send a keypress of the letter a and then does the vimium: show markers command but I could not find a way to send that letter a keypress

A silly method that just crossed my mind would be to prepend A in front of all the generated vimium markers using css


Add support for Azure Blob Storage

Extend to support Azure Blob Storage as a remote.  I did this by looking for instances of the word aws and making sensible extensions.
I've also added some more examples to explain how to use each of the remotes.

Thanks. I dont habe an Azure account so I could not test it.
But I hope it will work 😏


better description when no exports found

** a feature **

What is the current behavior?
when output.pathinfo is set to true and no exports are found in a module, the module is labeled with:
/* unknown exports provided */

What is the expected behavior?
I find this message a bit misleading since it suggests that there are some exports but they are unknown for some reason. But as far as I know this message appears when webpack found no exports because there are none or it couldn't find any.
If this is a feature request, what is motivation or use case for changing the behavior?
I think that message like: /* no exports found */ would be more appropriate.
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
<EMAIL_ADDRESS>

There could be CJS or AMD exports, but we can't detect them as CJS and AMD are dynamic and exports are only known at runtime.

@sokra If the file has no exports (as it often is with the main file) the message it the same /* unknown exports provided */. When I first saw it I interpreted it as if there were some malicious exports I didn't know about, but it fact the module just didn't export anything. Current description is a bit misleading and I propose to replace it with /* no static exports found */ to ease the pain for future webpack users that are not familiar with this practice.

/* no static exports found */

that's great. Do you want to send a PR? -> lib/FunctionModuleTemplate.js

Sure, I think webpack is awesome and it's a pleasure to make it even better.


Should the 7.3 RC Kotlin DSL also target Java 17?

Kotlin Build Script DSL on the Grade 7.3 branch still targets java 1.8 (when the branch is about support Java 17)
See here: https://github.com/gradle/gradle/blob/v7.3.0-RC5/subprojects/kotlin-dsl/src/main/kotlin/org/gradle/kotlin/dsl/KotlinBuildScript.kt#L46
Release notes here: https://docs.gradle.org/7.3-rc-5/release-notes.html
Expected Behavior
Either the plugin could target Java 17 or it should allow the target to be overridden.
Current Behavior
Targetting 1.8 with the code:
@ScriptTemplateAdditionalCompilerArguments(
    [
...
        "-jvm-target", "1.8",
...

Context
Moving to a world where all our code targets Java 17.
Steps to Reproduce
See above link.
Your Environment
All Env's
n/a

The target we have set for running Gradle is a lower bound for what Java versions we support, so 1.8 is where we want to be. You can still use Java 17 for your own code.

Gradle now supports running on and building with Java 17.

@jbartok if my plugin uses the Gradle kts plugin, I have to target java 8 because of this line of code
I'd like to target java 11, not even 17 :D
Or do you know a way around this?

IIUC now,  you are trying to implement a precompiled script plugin in Kotlin. That needs to be aligned with the runtime that Gradle uses, which is Java 8. There's no way around that. You can write a "classic" Gradle plugin in Kotlin which doesn't have a limitation (i.e. use the kotlin-gradle-plugin).

Reading in teh area https://blog.jetbrains.com/kotlin/2021/11/gradle-jvm-toolchain-support-in-the-kotlin-plugin/

Related: https://github.com/gradle/gradle/issues/18227


/decks/updated gives a 500 if you don't supply a querystring

Actually I think it may have bitrotted away entirely. Can't get any non-500 response from it.


Is it possible to get this working with null ls ?

Kinda curious, cause this would be really usefull if it could work with null ls .
Though if im honest i was really sure how one would set it up properly.

Hello -- yep, it's totally possible to have this work with null-ls.nvim. In your call to require"null-ls".setup(...), you'll want to supply an on_attach function -- check out the null-ls.nvim docs for on_attach here.
It will probably look something like this:
local null_ls = require"null-ls"
null_ls.setup({
  sources = {
    -- NOTE: sources must support range formatting!
    null_ls.builtins.formatting.prettier,
    null_ls.builtins.formatting.autopep8,
    -- ...
  },
  on_attach = function(client, bufnr)
    -- your usual configuration — options, keymaps, etc
    -- ...

    local lsp_format_modifications = require"lsp-format-modifications"
    lsp_format_modifications.attach(client, bufnr, { format_on_save = false })
  end
})

The caveat here is that the sources must support range formatting. At the time of writing, from a cursory glance over the null-ls's built-in sources, it looks like the following support range formatting:

autopep8
clang_format
prettier_d_slim
prettier
stylua
yapf

Hope this helps!

Ah epic, thanks, also great plugin :)


Greenhills support: fix the naked_function inline asm expansion compile error

fix the naked_function inline asm expansion compile error with Greenhills compiler
fix the incorrect stub-function entry address of svc call

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.guoshichao seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Empty DataFrames are always created without columns information

https://github.com/javascriptdata/danfojs/blob/df757838b812766c813489942401b424d034d62e/src/danfojs-base/core/generic.ts#L75
In this line, I see that when a DataFrame is created with empty data, the columns information is not passed to the DataFrame object.
I think this approach is not correct, because empty dataframes can also have useful information such as columns names or columns types. I will start to create a Pull Request with some tests in order to implement this, and maybe we can discuss if this could be added, but I think that DanfoJS already has a very good and solid design/structure to implement this without too much struggling.
Also not having empty dataframes creates unexpected errors (at least the ones who are used to Pandas) when filtering data.
For example, with DanfoJS we get this:
var data = {
    worker: ["david", "david", "john", "alice", "john", "david"],
    day: ["monday", "tuesday", "wednesday", "thursday", "friday", "friday"],
    hours: [5, 6, 2, 8, 4, 3],
};

var df = new dfd.DataFrame(data);

df.loc({rows: df["day"].eq("friday")}).groupby(["worker"]).count().print();
// ╔════════════╤═══════════════════╤═══════════════════╤═══════════════════╗
// ║            │ worker            │ day_count         │ hours_count       ║
// ╟────────────┼───────────────────┼───────────────────┼───────────────────╢
// ║ 0          │ john              │ 1                 │ 1                 ║
// ╟────────────┼───────────────────┼───────────────────┼───────────────────╢
// ║ 1          │ david             │ 1                 │ 1                 ║
// ╚════════════╧═══════════════════╧═══════════════════╧═══════════════════╝

df.loc({rows: df["day"].eq("saturday")}).groupby(["worker"]).count().print();
// Uncaught TypeError: r[0] is undefined
//     getRowAndColValues utils.ts:172
//     loadObjectIntoNdframe generic.ts:143
//     e generic.ts:83
//     t frame.ts:122
//     toDataFrame groupby.ts:412
//     operations groupby.ts:418
//     count groupby.ts:431

While in Pandas we get this:
import pandas as pd

data = {
    "worker": ["david", "david", "john", "alice", "john", "david"],
    "day": ["monday", "tuesday", "wednesday", "thursday", "friday", "friday"],
    "hours": [5, 6, 2, 8, 4, 3],
}

df = pd.DataFrame(data)

print(df.loc[df["day"] == "friday"].groupby(["worker"]).count())
#         day  hours
# worker
# david     1      1
# john      1      1

print(df.loc[df["day"] == "saturday"].groupby(["worker"]).count())
# Empty DataFrame
# Columns: [day, hours]
# Index: []

https://github.com/javascriptdata/danfojs/blob/df757838b812766c813489942401b424d034d62e/src/danfojs-base/core/generic.ts#L75
In this line, I see that when a DataFrame is created with empty data, the columns information is not passed to the DataFrame object.
I think this approach is not correct, because empty dataframes can also have useful information such as columns names or columns types. I will start to create a Pull Request with some tests in order to implement this, and maybe we can discuss if this could be added, but I think that DanfoJS already has a very good and solid design/structure to implement this without too much struggling.
Also not having empty dataframes creates unexpected errors (at least the ones who are used to Pandas) when filtering data.
For example, with DanfoJS we get this:
var data = {
    worker: ["david", "david", "john", "alice", "john", "david"],
    day: ["monday", "tuesday", "wednesday", "thursday", "friday", "friday"],
    hours: [5, 6, 2, 8, 4, 3],
};

var df = new dfd.DataFrame(data);

df.loc({rows: df["day"].eq("friday")}).groupby(["worker"]).count().print();
// ╔════════════╤═══════════════════╤═══════════════════╤═══════════════════╗
// ║            │ worker            │ day_count         │ hours_count       ║
// ╟────────────┼───────────────────┼───────────────────┼───────────────────╢
// ║ 0          │ john              │ 1                 │ 1                 ║
// ╟────────────┼───────────────────┼───────────────────┼───────────────────╢
// ║ 1          │ david             │ 1                 │ 1                 ║
// ╚════════════╧═══════════════════╧═══════════════════╧═══════════════════╝

df.loc({rows: df["day"].eq("saturday")}).groupby(["worker"]).count().print();
// Uncaught TypeError: r[0] is undefined
//     getRowAndColValues utils.ts:172
//     loadObjectIntoNdframe generic.ts:143
//     e generic.ts:83
//     t frame.ts:122
//     toDataFrame groupby.ts:412
//     operations groupby.ts:418
//     count groupby.ts:431

While in Pandas we get this:
import pandas as pd

data = {
    "worker": ["david", "david", "john", "alice", "john", "david"],
    "day": ["monday", "tuesday", "wednesday", "thursday", "friday", "friday"],
    "hours": [5, 6, 2, 8, 4, 3],
}

df = pd.DataFrame(data)

print(df.loc[df["day"] == "friday"].groupby(["worker"]).count())
#         day  hours
# worker
# david     1      1
# john      1      1

print(df.loc[df["day"] == "saturday"].groupby(["worker"]).count())
# Empty DataFrame
# Columns: [day, hours]
# Index: []

Hey @igonro You're correct, and I would gladly review a PR from you on this.

Hi @risenW, can you briefly explain why this line is needed? I think I may have to modify it in order to fix some tests, but I don't see the motivation behind it (and I'm sure that there is a good reason)
https://github.com/javascriptdata/danfojs/blob/c9cc17d2b8fafb3f12b35cc14f82ca2e240b4e28/src/danfojs-base/core/generic.ts#L316
Thanks!

Maybe @steveoni can help too answering this question(?)
Thank you very much!

Hi @risenW, can you briefly explain why this line is needed? I think I may have to modify it in order to fix some tests, but I don't see the motivation behind it (and I'm sure that there is a good reason)
https://github.com/javascriptdata/danfojs/blob/c9cc17d2b8fafb3f12b35cc14f82ca2e240b4e28/src/danfojs-base/core/generic.ts#L316
Thanks!

That’s the default column name when non is provided for Series. Theoretical, Series is not suppose to have a column name though.
Does removing that break any test? If no, then modify and we can test together after your PR


Roboto Mono?

https://www.google.com/fonts/specimen/Roboto+Mono
I have no pressing need right now.  I or someone will try to get someone to add PowerLine glyphs someday....

Cool! I think a version of Roboto with those glyphs added would live in https://github.com/powerline/fonts though

https://github.com/powerline/fonts/issues/116

Thanks for digging up that Issue!

I suggest this can be closed


Updates the Quarkus version to the latest LTS version (3.8.6)

Updates the Quarkus version to the latest LTS version (3.8.6)
Also moved the release to next one 0.2.3

@baldimir could you review and merge when CI finishes?

@gmunozfe I can't. I am not the maintainer of this repo. @fjtirado could you please take a look?

@ricardozanini is a maintainer now.
@all-contributors add @ricardozanini for code and maintenance


Update Cargo.toml

Update to the new defmt-rtt version, re-enable lto and opt-level after they got dixed upstream and some drive-by changes.
Fixes #5, #63.

Oh wait bors isn't running here


mocha don't wait for "done()" callback

Hello i need test async code but mocha don't wait for done
using angulars $q promise
using karma
 it('should set subscribers and groups "getData()"', done => {
      ctrl.users= [];
      ctrl.groups = [];
      ctrl.getData()
        .then(res => {
          done()
        });

      expect(ctrl.users).to.not.be.empty;
      expect(ctrl.groups).to.be.not.empty;
    });

error: Ensure the done() callback is being called in this test

Problem was in angularjs $q promisses
related stack:
http://stackoverflow.com/questions/35180958/promises-with-q-and-angular-in-karma-mocha-chai
sorry for issue


Keyboard not showing up in android 12 devices

Keyboard is not showing up for android 12 devices, overlay comes indicating keyboard is on but nothing is shown. It is working properly for older android versions.
Below is an image of simple text field with keyboard on have tried changing all properties of text field also. Its an existing application so tried testing the existing textfields even in those its showing the same behaviour.
android gradle settings
minSdkVersion 24
targetSdkVersion 30
compileSdkVersion 31

flutter doctor code -
flutter doctor -v
[✓] Flutter (Channel stable, 2.2.3, on macOS 11.4 20F71 darwin-x64, locale en-IN)
    • Flutter version 2.2.3 at /Users/uable/Downloads/flutter
    • Framework revision f4abaa0735 (4 months ago), 2021-07-01 12:46:11 -0700
    • Engine revision 241c87ad80
    • Dart version 2.13.4

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/uable/Library/Android/sdk
    • Platform android-31, build-tools 31.0.0
    • ANDROID_HOME = /Users/uable/Library/Android/sdk
    • ANDROID_SDK_ROOT = /Users/uable/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[!] Xcode - develop for iOS and macOS
    ✗ Xcode installation is incomplete; a full installation is necessary for iOS development.
      Download at: https://developer.apple.com/xcode/download/
      Or install Xcode via the App Store.
      Once installed, run:
        sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer
        sudo xcodebuild -runFirstLaunch
    • CocoaPods version 1.10.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] Connected device (2 available)
    • sdk gphone64 x86 64 (mobile) • emulator-5554 • android-x64    • Android 12 (API 31) (emulator)
    • Chrome (web)                 • chrome        • web-javascript • Google Chrome 95.0.4638.54

! Doctor found issues in 1 category.

@maheshmnj it's working now setting the value of hardwareAccerlated to true in manifest fixed the issue.

@maheshmnj it's working now setting the value of hardwareAccerlated to true in manifest fixed the issue.

Provided your last message I feel it's safe to close the issue.
Thanks


[Maintenance] Need Templates for Issues and PRs

Need to replicate the Templates for Issues and PRs used in other projects to this one.

Completed


jest --json does not output JSON

Although running
jest --json --outputFile=foo.json

Produces a valid JSON file, running
jest --json

Does not produce valid JSON on standard out. Standard out contains some non-printable characters before the JSON content, meaning that you cannot usefully pipe jest output into another program.
You cannot, for example, run:
jest --json | python -m json.tool

I would expect
jest --json --outputFile=foo.json
jest --json > bar.json

To produce two identical files, but it does not.
The non-JSON content looks like the characters to get the console to draw the test progress while they're running. In the case where you're piping or redirecting output, standard out isn't even a tty.

This is fixed in the latest alpha, try<EMAIL_ADDRESS>cc @mjesun

Hi,
it looks like the problem still exists in 26.6.3


'Llama' object has no attribute 'ctx'

Please i need help. I have this issue when i try to run vicuna-13b model.
root@DESKTOP-EEQG16M:/mnt/f/AI_and_data/LLAMA_models# python3 test_LLama_cpp.py
Traceback (most recent call last):
File "test_LLama_cpp.py", line 2, in
llm = Llama(
File "/usr/local/lib/python3.8/dist-packages/llama_cpp/llama.py", line 155, in init
raise ValueError(f"Model path does not exist: {model_path}")
ValueError: Model path does not exist: F:\AI_and_data\LLAMA_models\llama.cpp\models\ggml-vicuna-13b-4bit.bin
Exception ignored in: <function Llama.del at 0x7f1db5ea4b80>
Traceback (most recent call last):
File "/usr/local/lib/python3.8/dist-packages/llama_cpp/llama.py", line 1076, in del
if self.ctx is not None:
AttributeError: 'Llama' object has no attribute 'ctx'

Model path does not exist: F:\AI_and_data\LLAMA_models\llama.cpp\models\ggml-vicuna-13b-4bit.bin
That looks like a Windows path but you seem to be on Linux?

i use WSL

In wsl you need to use the path where windows file system is mounted. For example "/mnt/c/Users/..." to access the model in windows file system

I use relative path

And?

I have thé sale issue

Can you review #225, please?

Closing. Reopen if the issue is not resolved.

I have this issue can you help me solve it:
raise ValueError(f"Model path does not exist: {model_path}")

Can someone please share the fix for this?
File "/Users/userame/PycharmProjects/PythonAdventure/.venv/lib/python3.11/site-packages/llama_cpp/llama.py", line 320, in init
raise ValueError(f"Model path does not exist: {model_path}")
ValueError: Model path does not exist: /Users/userame/.ollama/models/llama3:latest


Can't open Ledger with the latest Bitcoin app selected

Bitcoin app version: 1.5.1
OS: Ubuntu 20
hid detects Ledger, but open of the device fails.
This breaks communication with Ledger for HWI and Specter.
>>> from btchip import btchipComm
>>> btchipComm.getDongle()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/ss/dev/desktop/myspecter/.venv/lib/python3.8/site-packages/btchip/btchipComm.py", line 230, in getDongle
    dev.open_path(hidDevicePath)
  File "hid.pyx", line 72, in hid.device.open_path
OSError: open failed

https://github.com/bitcoin-core/HWI/pull/403 should fix it

No, we already integrated that.
Enumeration works, I get correct path, but hid device can not be opened:
>>> import hid
>>> hid.enumerate()
[{'path': b'0001:0019:00', 'vendor_id': 11415, 'product_id': 4117, 'serial_number': '', 'release_number': 513, 'manufacturer_string': '', 'product_string': '', 'usage_page': 0, 'usage': 0, 'interface_number': 0}, {'path': b'0001:0019:01', 'vendor_id': 11415, 'product_id': 4117, 'serial_number': '', 'release_number': 513, 'manufacturer_string': '', 'product_string': '', 'usage_page': 0, 'usage': 0, 'interface_number': 1}, {'path': b'0001:0003:00', 'vendor_id': 1118, 'product_id': 1970, 'serial_number': '', 'release_number': 1862, 'manufacturer_string': '', 'product_string': '', 'usage_page': 0, 'usage': 0, 'interface_number': 0}, {'path': b'0001:0003:01', 'vendor_id': 1118, 'product_id': 1970, 'serial_number': '', 'release_number': 1862, 'manufacturer_string': '', 'product_string': '', 'usage_page': 0, 'usage': 0, 'interface_number': 1}, {'path': b'0001:0003:02', 'vendor_id': 1118, 'product_id': 1970, 'serial_number': '', 'release_number': 1862, 'manufacturer_string': '', 'product_string': '', 'usage_page': 0, 'usage': 0, 'interface_number': 2}]
>>> dev = hid.device()
>>> dev.open_path(b'0001:0019:00')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "hid.pyx", line 72, in hid.device.open_path
OSError: open failed

This works just fine on my own Ubuntu 20.04 with python3/btchip 0.31.1/bitcoin 1.5.1/Firmware 1.6.1
`>>> from btchip import btchipComm

btchipComm.getDongle()`

Try to use the other interface: dev.open_path(b'0001:0019:01') instead of dev.open_path(b'0001:0019:00')

Thanks, updating udev rules did it.

I have both BTC and ETH apps in my ledger device.
The following code does not run on my ubuntu when i have BTC app open, but it runs when i have ETH app open:
import TransportWebHID from "@ledgerhq/hw-transport-webhid";

const transport = await TransportWebHID.create();

The same code will run in Windows environment.


Deploy lv2_util.h also for external lv2 plugins

Without this change the lv2_util header file is not part of the lv2 package nor of the lv2-dev package.
Therefore external Lv2 plugins could not use it.

Patch also send to mailing list
http://lists.lv2plug.in/pipermail/devel-lv2plug.in/2018-April/thread.html

PR is fine (though so is the mailing list) if you prefer.  Sorry, just a bit slow getting around to things lately.

@drobilla
As you mentioned I have used a for loop to reduce the duplicates

PR is fine (though so is the mailing list) if you prefer.

I prefer GitHub but I was not aware if anyone will see this.
Anything else to change?

Seems fine, thanks.