cargo test --tests also runs unit tests -- target filters are confusing

Problem
cargo test has flags --libs, --bins, --tests, --doc, which I thought (based on their documentation) would control whether the lib crate unit tests / bin crate unit tests / integration tests / doc tests, respectively, are being run. But that does not seem to be what happens, so either the documentation is wrong or it is very confusing.
Steps

Run cargo test --tests.
Notice how it runs not just the integration tests, but also the unit tests!
However, cargo test --bins runs only the binary crate unit tests.

This seems clearly inconsistent. I would expect cargo test --tests to be the same as cargo test --test a --test b (manually listing all tests), which is how cargo test --bins seems to behave.
Possible Solution(s)
No response
Notes
Generally the cargo test documentation for all these many flags that control which tests are being run, is unclear on whether the flag adds tests to the default test set, or remove the default test set to only run a small select set of tests. (This also affects other commands like cargo check.) For instance, cargo test --benches tests more than the default test set, but cargo test --bins tests less than the default test set, but the documentation for these two flags reads exactly the same. Some flags use the word 'only', which is maybe meant to indicate "reduce default test set", but --bins does not use that word and anyway this is not at all clear.
The behavior I would have expected is along the lines of "if any of these flags is present, then only what is specified by the flags is being run, no default test set", but that does not match implemented behavior. This then makes me wonder how I would even say "run only integration tests" (cargo test --tests doesn't do that), or "check only the benchmarks" (cargo check --benches doesn't do that).
Version
cargo 1.64.0-nightly (85b500cca 2022-07-24)
release: 1.64.0-nightly
commit-hash: 85b500ccad8cd0b63995fd94a03ddd4b83f7905b
commit-date: 2022-07-24
host: x86_64-unknown-linux-gnu
libgit2: 1.4.2 (sys:0.14.2 vendored)
libcurl: 7.83.1-DEV (sys:0.4.55+curl-7.83.1 vendored ssl:OpenSSL/1.1.1q)
os: Debian testing (bookworm) [64-bit]

Totally agree it is confusing. People usually invoke cargo test --help and see it say Test all tests. Then guessing like "I know cargo tests. Tests here must refer to all test targets". And it turns out to be all targets that has default test flag set.
It's hard to encourage people to use cargo help test, read all the lengthy doc^1, and figure out how it works. I believe changing the behaviour is a breaking change, so there indeed is an inconsistency between --tests and other target options such as --bins. I would suggest improve the short help message first and see how to expand the long version, though I currently have no thought about a better help message.
Test all targets in test mode that have the `test = true` manifest flag set. By default this includes the library and binaries built as unittests, and integration tests. Be aware that this will also build any required dependencies, so the lib target may be built twice (once as a unittest, and once as a dependency for binaries, integration tests, etc.). Targets may be enabled or disabled by setting the test flag in the manifest settings for the target.

So is there even a way to ask cargo to test (or check or ...) all test targets (the things that are by default in the tests/ directory, the things that can be selected via --tests) but nothing else? I expect this to be possible somehow, and there's no other flag which does this, so it must be --tests -- was my reasoning.

cargo help test

Oh wow, I had no idea that this command even existed! Thanks for pointing it out, I will try to remember. :)
I now see it is mentioned at the end of cargo test --help. Not sure how I missed it. I guess I didn't expect there to be a short and long version of the help, so I didn't even go looking.
What's the reason why cargo test --help does not do the same thing as cargo help test?

So is there even a way to ask cargo to test (or check or ...) all test targets (the things that are by default in the tests/ directory, the things that can be selected via --test name) but nothing else?

Underneath the hod, integration tests and unit tests are handled by the same mechanism. They are all collected from functions with #[test] attribute by libtest. Here is an old write-up may help. https://github.com/rust-lang/cargo/issues/10361#issuecomment-1043872481. If you do want do run all integration tests but not unit test in library target, try to leverage glob syntax such as cargo test --test '*'.

What's the reason why cargo test --help does not do the same thing as cargo help test?

I got a impression that @epage had mentioned it somewhere but can't remember.

If you do want do run all integration tests but not unit test in library target, try to leverage glob syntax such as cargo test --test '*'.

Ah, didn't know that was possible, thanks. I should really read those long docs in their entirety.
Still I feel like a flag is missing here, since we do have such a flag for all other similar cases, AFAIK.

The description of --tests in the cargo book:

By default this includes the library and binaries built as unittests, and integration tests.

But there seems to be a problem with this statement, the results of my tests using cargo test --bins to test cargo will not show up in cargo test --tests, implying that --tests doesn't test the binary unit tests? So it would make more sense for  --tests to be modified to only accomplish integration tests and library unit tests?
Also, in cargo test -h, in order to maintain uniformity, should --bins and --bin be described similarly to --lib, modified to read:
--bin: Test only the specified binary's unit tests
--bins: Test all binaries' unit tests
The description in the corresponding cargo book is updated.

In case its relevant, #12915 made some minor wording tweaks in 1.75

cargo test --test '*'

I think the main confusion is the fact that this is not equivalent to cargo test --tests. It certainly feels like it should be equivalent. The cargo help test docs now explain this, but cargo test --help still doesn't even hint at this. I should try giving this a shot...


localstore, shed: persist stamps

#933

/run beekeeper

/run beekeeper

some simplification is due in terms of the chunk type. will solicit a review once thats done

some simplification is due in terms of the chunk type. will solicit a review once thats done


Bazel build support

Need to migrate BUILD files from upstream and make compatible with OSS release.
This partially works now, with iree/base and iree/hal/vulkan building. Will iterate on the rest.

I think we can call this generally done now:

The full project builds with Bazel on Linux
Most of the project builds with Bazel on Windows
Most of the project is built and tested with Bazel on CI (Linux)


fix this.playhead undefined

using videojs.record.js in angular I get an error with this.playhead as undefined

Thanks for the PR. What was the exact error message?

I fixed it on my angular side, it doesn't matter. I'll delete this PR.
thanks for the good job!

I re-opened it, I was wrong. the bug come out with AUDIO only recording.


macOS fails to build with CMSDK_LOCAL_PATH path error

When trying to build with macOS, I get the following error:
 gui git:(main) cmake -P bootstrap.cmake
Cloning into 'CMakeSDK'...
CMake Error at CMakeLists.txt:4 (message):
  CMSDK_LOCAL_PATH must be provided

-- Configuring incomplete, errors occurred!
CMake Error at bootstrap.cmake:45 (message):
  Failed to run cmake for CMakeSDK project

@nscooling, Sorry. I was in the middle of updating some of the supporting libraries.
It should work now on main.

Still not building for me - different error
[115/264] Building CXX object SDK/JsonAPI/library/CMakeFiles/JsonAPI_release_link.dir/src/JsonDocument.cpp.o
FAILED: SDK/JsonAPI/library/CMakeFiles/JsonAPI_release_link.dir/src/JsonDocument.cpp.o
/usr/local/opt/llvm/bin/clang++ -DCMSDK_BUILD_GIT_HASH=9a2fa55 -DHAVE_CONFIG_H=1 -D__CMSDK_SDK_OPTION_EMPTY -D___release -D__link -I/Users/niall/development/StratifyLabs/gui/SDK/dependencies/JsonAPI/library/include -I/Users/niall/development/StratifyLabs/gui/SDK/local/include/StratifyOS -I/Users/niall/development/StratifyLabs/gui/SDK/dependencies/API/libraries/FsAPI/include -I/Users/niall/development/StratifyLabs/gui/SDK/dependencies/API/libraries/FsAPI/../../include -I/Users/niall/development/StratifyLabs/gui/SDK/dependencies/API/libraries/FsAPI/../ChronoAPI/include -I/Users/niall/development/StratifyLabs/gui/SDK/dependencies/API/libraries/FsAPI/../PrinterAPI/include -I/Users/niall/development/StratifyLabs/gui/SDK/dependencies/API/libraries/ChronoAPI/include -I/Users/niall/development/StratifyLabs/gui/SDK/dependencies/API/libraries/ChronoAPI/../../include -I/Users/niall/development/StratifyLabs/gui/SDK/dependencies/API/libraries/ChronoAPI/../PrinterAPI/include -I/Users/niall/development/StratifyLabs/gui/SDK/dependencies/API/libraries/PrinterAPI/include -I/Users/niall/development/StratifyLabs/gui/SDK/dependencies/API/libraries/PrinterAPI/../../include -I/Users/niall/development/StratifyLabs/gui/SDK/dependencies/API/libraries/PrinterAPI/../VarAPI/include -I/Users/niall/development/StratifyLabs/gui/SDK/dependencies/API/libraries/VarAPI/include -I/Users/niall/development/StratifyLabs/gui/SDK/dependencies/API/libraries/VarAPI/../../include -I/Users/niall/development/StratifyLabs/gui/SDK/dependencies/API/libraries/VarAPI/../API/include -I/Users/niall/development/StratifyLabs/gui/SDK/dependencies/API/libraries/API/include -I/Users/niall/development/StratifyLabs/gui/SDK/dependencies/API/libraries/API/../../include -I/Users/niall/development/StratifyLabs/gui/SDK/dependencies/JsonAPI/jansson/jansson/src -I/Users/niall/development/StratifyLabs/gui/SDK/dependencies/JsonAPI/jansson/include -I/Users/niall/development/StratifyLabs/gui/SDK/dependencies/JsonAPI/jansson/include/jansson -isystem /Users/niall/development/StratifyLabs/gui/SDK/local/include -m64 -arch x86_64 -D__macosx -D__processor_x86_64 -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX12.3.sdk -Os -std=gnu++17 -MD -MT SDK/JsonAPI/library/CMakeFiles/JsonAPI_release_link.dir/src/JsonDocument.cpp.o -MF SDK/JsonAPI/library/CMakeFiles/JsonAPI_release_link.dir/src/JsonDocument.cpp.o.d -o SDK/JsonAPI/library/CMakeFiles/JsonAPI_release_link.dir/src/JsonDocument.cpp.o -c /Users/niall/development/StratifyLabs/gui/SDK/dependencies/JsonAPI/library/src/JsonDocument.cpp
In file included from /Users/niall/development/StratifyLabs/gui/SDK/dependencies/JsonAPI/library/src/JsonDocument.cpp:4:
In file included from /Users/niall/development/StratifyLabs/gui/SDK/dependencies/JsonAPI/library/src/xml2json.hpp:15:
In file included from /Users/niall/development/StratifyLabs/gui/SDK/dependencies/JsonAPI/library/src/rapidxml/rapidxml_utils.hpp:13:
In file included from /usr/local/opt/llvm/bin/../include/c++/v1/fstream:193:
In file included from /usr/local/opt/llvm/bin/../include/c++/v1/filesystem:243:
In file included from /usr/local/opt/llvm/bin/../include/c++/v1/__filesystem/directory_entry.h:20:
/usr/local/opt/llvm/bin/../include/c++/v1/__filesystem/operations.h:77:98: error: expected ')'
inline _LIBCPP_INLINE_VISIBILITY void create_directory_symlink(const path& __target, const path& __link) { __create_directory_symlink(__target, __link); }
                                                                                ^
<command line>:5:16: note: expanded from here
#define __link 1

What toolchain are you using?
I always just build with the default Xcode compiler. The API framework defines __link and it looks like that is colliding with your toolchain.

This is what's referenced
$ gcc -v
Apple clang version 13.1.6 (clang-13<IP_ADDRESS>.5)
Target: x86_64-apple-darwin21.6.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin

It looks like it is using a tool chain in /usr/local/opt/llvm. That isn't the Mac OS default. I have been building on 12.5

Ah, sorry, of course, I'd forgotten I was doing some work that required standard clang rather than Apple's version. Duh, my bad.


Metamask on safari

Is there an existing issue for this?

[X] I have searched the existing issues

Package Version
0.4.3
Current Behavior
Upon trying to connect to metamask on safari on my phone, i get the Connector not found error.
Expected Behavior
I would like for this to trigger a deep link into metamask.
Steps To Reproduce

Use use-wagmi on safari on a mobile device
Try to connect to metamask

Link to Minimal Reproducible Example (StackBlitz, CodeSandbox, GitHub repo etc.)
No response
Anything else?
No response

@lostarchitect
Because there is no wallet plugin in Safari
You can use metamask app to access dapp or use wallet connect to connect

wagmi may add the function of automatically launching the mobile wallet in a later version

Understood! But I know for instance using WC it deeplinks into metamask, but WC2 has proven to be quite janky in that respect... I believe also the newest MM SDK release deeplinks into the metamask app for a non-mm mobile browser.
But overall sounds like this would be upstream, in wagmi itself?


Type "Unbound" is not callablestarpls error

This is one of a few bugs I've found when trying the LSP.
When a rule instance is declared in a BUILD file, this error always appears.

Thanks for reporting! I haven't really started work on resolution of load statements yet, but a quick solution might be assign all names that appear as the Any type. That way at least it doesn't get super busy with Unbound errors everywhere. Will make sure to get this in soon!

In general though, the LSP doesn't really  support Bazel files just yet because most of the builtin functions/modules will be considered Unbound. One thing I'm planning on landing in the near future is loading builtins from a proto file generated by the ApiExporter, at which point native functions/types should get resolved.

The errors here should be gone now! Basically while resolving load statements is still WIP, any name in a load statement will be assigned the Any type.


Remove deprecated fields from Config

Need to remove deprecated fields in the config.py.
Some are: MAX_THREADS and SQLALCHEMY_POOL_SIZE.  These were fields that were important pre 1.0, but now with Celery, this is no longer needed and should be removed to reduce confusion.
closes #1029
closes #984
Related to #1030

@mikegrima latest celery version is 4.1.0 so you mean like this version doesn't require the above mentioned configurations ?


Add option to save the plot

Add this to the end of basic command to specify where to save the plot to
... --save path/to/save/to/filename

Thats great, please go ahead!!

I will work on this. I guess no one is working on it.
@djmgit


Add support for PhysX 5 to O3DE

Add support for PhysX 5 to O3DE
Summary
We (Game Engine and Developer Services (GE&DS), part of AWS) would like to upgrade the O3DE physics backend (currently in the form of the PhysX Gem) from PhysX 4.1 to PhysX 5.1.
What is the relevance of this feature?
PhysX 4.1 is now end of life (EOL) and will receive no further updates or improvements from NVIDIA. On 2022/11/08 NVIDIA announced that they were open sourcing PhysX 5, the successor to PhysX 4. PhysX 5 had been closed source for some time and it wasn't clear if NVIDIA had plans to make it available to the open source community. The news of PhysX 5 going open source was greeted with much excitement from the community and we would like to adopt it soon so customers of O3DE can benefit from the feature set and performance improvements. It also future proofs O3DE by relying on a current technology that will continue to improve.
Note: PhysX 5 does come with a host of new GPU/CUDA specific features that are out of scope of the RFC. We interested in the core library updates for O3DE.
Feature design description
Upgrade the current PhysX Gem from PhysX 4.1 to PhysX 5.1. This should be a largely invisible update without many users being impacted.
Technical design description
We first need to add support for the platforms widely supported by O3DE that are missing from PhysX 5 today (most notably Android, iOS and macOS). We are in discussions with NVIDIA about adding support for these platforms upstream but can also in the short-term create patches to add this platform support.
See open PRs so far that are already in progress (thanks to @moraaar)

https://github.com/NVIDIA-Omniverse/PhysX/pull/51
https://github.com/NVIDIA-Omniverse/PhysX/pull/49
https://github.com/NVIDIA-Omniverse/PhysX/pull/40

There have been some small API changes (most notably to the scene query API) but nothing that breaks compatibility in many places across the engine. A deprecation/upgrade notice will be issued for the next release and an upgrade guide will be created to help users upgrade/migrate if they do experience any breaking changes.
What are the advantages of the feature?

Improved performance
More features
Continued support/development on the library from NVIDIA

What are the disadvantages of the feature?

No native platform support for Android, iOS, macOS (yet)

(This is being added now but will need to be maintained by O3DE in the short-term)

Breaking API changes that may impact some customers

How will this be implemented or integrated into the O3DE environment?

PhysX 5.1 will be added as a new third party library to the O3DE ecosystem
The PhysX Gem will be updated (in-place) to use PhysX 5.1 as its backend as opposed to PhysX 4.1

Are there any alternatives to this feature?

Yes

Stay with PhysX 4.1. This is an option but does not set up O3DE for success long-term
Look to adopt another physics backend to replace or augment PhysX

This is a much larger effort with significantly more complexity so should be considered a longer-term goal outside the scope of this RFC.

It may be possible to add PhysX 5 as a new separate Gem in addition to PhysX 4

This comes with its own set of challenges and could result in customer confusion and configuration problems. It also will be an additional support burden instead of a like for like swap.

How will users learn this feature?

Users' experience of O3DE will remain largely unchanged. Docs referring to old APIs will be updated as well as an upgrade guide for the next O3DE release to help users migrate if they're relying on any PhysX 4.1 functionality that has changed or been removed.

Are there any open questions?

Who else might help with this effort
Will NVIDIA add Android/iOS/macOS support
What else will we be missing out on if we don't upgrade
This effort will not add support for all new PhysX 5 features (though customers could access them in some contexts if they wish). We are looking to replicated existing functionality we have today in PhysX 4.1

I support this RFC. It covers well the upgrade to PhysX 5.1. Thanks @hultonha

+1
Looks like a great improvement!

+1
Nice work on the RFC!

Very cool! Really looking forward to this 😎

Excellent! I would love to be able to compare "before" and "after" on some dedicated benchmark scene - we could quantify how impactful the change is and encourage users to switch to the new release when it comes with 5.1.

+1, agree with @adamdbrw, it'd be great to know the before/after perf difference.

+1

Thanks @hultonha for preparing this RFC! This is looking great and I added it to the agenda for the upcoming governance meeting. One open question that remains for me is how we would proceed in case Nvidia does not accept the patches for Android/iOS/macOS support. If they don't, would the NVIDIA license allow us to maintain a separate distribution incorporating these changes?

Thanks @hultonha for preparing this RFC! This is looking great and I added it to the agenda for the upcoming governance meeting. One open question that remains for me is how we would proceed in case Nvidia does not accept the patches for Android/iOS/macOS support. If they don't, would the NVIDIA license allow us to maintain a separate distribution incorporating these changes?

No problem! So in the case that NVIDIA don't accept the PRs it's actually okay, it just makes our life a little more difficult. Basically every time NVIDIA update PhysX 5, we have to update (rebase) our patches again on top of their changes, and then rebuild our own third-party package. It just makes things a bit more fiddly but is doable. Please correct me if I'm wrong @moraaar who knows more about this than me! 😅

@hultonha is correct, the PRs we submitted to nVidia repo will always be available for our 3rdParty build scripts to use, unless nVidia deletes their whole github repo or something drastic like that (extremely unlikely).

every time NVIDIA update PhysX 5, we have to update (rebase) our patches again on top of their changes

Just for the record, we would only do this when WE (sig-simulation) decide we want to update PhysX Gem to use the latest updates of PhysX 5, which we may decide it's not worth our effort. So we do have certain control there as well, it'd depend if we'd like to bring certain new features or critical bug fixes.

would the NVIDIA license allow us to maintain a separate distribution incorporating these changes?

I'm not a lawyer, but I think PhysX5's BSD3 open source license is ok with that, otherwise we couldn't do it now :)

Perfect, I didn't realize that PhysX 5 now uses a plain BSD3 license without the typical NVIDIA restrictions. Based on the collected feedback, I (as SIG Simulation chair) would like to move this RFC forward to the final comment stage and give the community 5 more days to raise further comments or concerns. I will also crosspost this to Discord for visibility.

Fantastic to hear! 🥳 Thank you very much @lgleim 🙂

As no further concerns have been raised, this RFC is now approved. The initial realization is being tracked in https://github.com/o3de/o3de/pull/13802 based on a community-maintained PhysX 5 fork with mac/ios/android platform support that has been created at https://github.com/o3de/PhysX
More details on this discussion: https://github.com/NVIDIA-Omniverse/PhysX/discussions/58#discussioncomment-4470126


🔧(backend) switch from setup.cfg to pyproject.toml

Purpose
Since PEP 621 has been adopted by the python community so pyproject.toml configuration file is now the go-to config. The frontend developer spirit buried deep within myself wants to keep this project on the bleeding edge then my curiosity pushed myself to switch from setup.cfg to pyproject.toml.
https://packaging.python.org/en/latest/specifications/declaring-project-metadata https://setuptools.pypa.io/en/latest/userguide/pyproject_config.html
Questions for reviewers

Should we keep setup.py file ?

(According to setuptools documentation, it seems safer to keep this file to prevent some issue with development mode)

Proposal

[x] Switch from setup.cfg to pyproject.toml
[x] Install flake8-pyproject to be able to configure flake8 through pyproject.toml (It's temporary of course, ruff is coming!)

I think we should update renovate.json to set the right matchManagers, but I can't find it in docs for now.

Maybe we could just replace setup-cfg with pep621 ?

I think we should update renovate.json to set the right matchManagers, but I can't find it in docs for now.

Maybe we could just replace setup-cfg with pep621 ? https://docs.renovatebot.com/modules/manager/#supported-managers

According to https://github.com/openfun/warren, setup-cfg looks able to manage update through pyproject.toml


Structured data

Are there plans to move structured data into json-ld schema in the headers?
That is now the recommended format for presenting structured data by google.
To add some context I am setting up the blog to be valid AMP so it needs the structured data in the headers.
Right now it's in the template which is easy to alter, but once it goes to the headers it needs a template tag probably. I might try to write something, but didn't want to duplicate efforts.

Hello,
json-ld is planned.
But contributions are welcome.
Regards


this._super() fails in 'classic' computeds

With ember-decorators-polyfill installed, calling  this._super() in a computed property in a classic class no longer returns the value from the definition on the parent.
const Parent = EmberObject.extend({
  foo: computed(function() {
    return 'ok';
  }),
});

const Child = Parent.extend({
  foo: computed(function() {
    // `value` is `'ok'` in both 3.9 and the 3.10 beta,
    // but `undefined` in 3.9 with the polyfill installed
    let value = this._super();
    return value.toUpperCase();
  }),
});

Child.create().foo;

Running into the same issue. This breaks the ember-cp-validations add-on (see addon/validations/factory.js#L115)

This should be fixed in v1.0.5!


No data or "meters" showing up in HA

After setting up the Home Assistant add-on and configuring it as shows in the docs, I am not getting a sensor in HA. In Mosquitto I listened for "rtlamr/status" and got "online", but I'm not getting anything when I listen for "rtlamr/gas_meter/state".
Here is my config:
general:
  sleep_for: 300
  verbosity: debug
  tickle_rtl_tcp: true
  device_id: 0bda:2838
mqtt:
  ha_autodiscovery: true
  ha_autodiscovery_topic: homeassistant
  tls_enabled: false
  tls_ca: /etc/ssl/certs/ca-certificates.crt
  tls_cert: /etc/ssl/my_self_signed_cert.crt
  tls_keyfile: /etc/ssl/my_self_signed_cert_key.key
  tls_insecure: true
  host: <HA Blue internal IP Address)
  port: 1883
  user: mqtt-user
  password: <redacted>
custom_parameters:
  rtltcp: '-s 2048000'
  rtlamr: '-unique=true'
meters:
  - id: 265087065 #not sure if this should have the 2 at the beginning or not, but I tried both ways.
    protocol: scm
    name: gas_meter
    format: '####.###'
    unit_of_measurement: ft³
    icon: mdi:gas_canister
    device_class: gas
    state_class: total_increasing

Here is my log for the add-on:
[2022-05-12 11:54:48] RTLAMR2MQTT Starting...

[2022-05-12 11:54:48] RTL SDR Device 0bda:2838 found on USB port 001:005 - Index: 0

[2022-05-12 11:54:48] Configured MQTT sender:

[2022-05-12 11:54:48]  > hostname => <HA Blue Internal IP Address

[2022-05-12 11:54:48]  > port => 1883

[2022-05-12 11:54:48]  > username => mqtt-user

[2022-05-12 11:54:48]  > client_id => rtlamr2mqtt

[2022-05-12 11:54:48]  > tls => None

[2022-05-12 11:54:48] Reseting USB device: /dev/bus/usb/001/005

[2022-05-12 11:54:49] Reset sucessful.

[2022-05-12 11:54:49] Sending message to MQTT:

[2022-05-12 11:54:49]  > topic => rtlamr/status

[2022-05-12 11:54:49]  > payload => online

[2022-05-12 11:54:49]  > retain => True

[2022-05-12 11:54:49] Trying to start RTL_TCP: /usr/bin/rtl_tcp -d 0 -s 2048000

[2022-05-12 11:54:49] RTL_TCP started with PID 10

[2022-05-12 11:54:54] RTL_TCP is ready to receive connections!

[2022-05-12 11:54:54] server: <IP_ADDRESS>:1234, host: <IP_ADDRESS>, port: 1234

[2022-05-12 11:54:54] Attempting to tune rtl_tcp to a different freq to shake things up

[2022-05-12 11:54:54] Successfully tickled rtl_tcp

[2022-05-12 11:54:54] Trying to start RTLAMR: /usr/bin/rtlamr -msgtype=scm -format=json -filterid=265087065 -unique=true

[2022-05-12 11:54:54] RTLAMR started with PID 17

[2022-05-12 11:54:54] 11:54:54.519576 decode.go:45: CenterFreq: 912600155

[2022-05-12 11:54:54] 11:54:54.519848 decode.go:46: SampleRate: 2359296

[2022-05-12 11:54:54] 11:54:54.519858 decode.go:47: DataRate: 32768

[2022-05-12 11:54:54] 11:54:54.519864 decode.go:48: ChipLength: 72

[2022-05-12 11:54:54] 11:54:54.519869 decode.go:49: PreambleSymbols: 21

[2022-05-12 11:54:54] 11:54:54.519874 decode.go:50: PreambleLength: 3024

[2022-05-12 11:54:54] 11:54:54.519879 decode.go:51: PacketSymbols: 96

[2022-05-12 11:54:54] 11:54:54.519884 decode.go:52: PacketLength: 13824

[2022-05-12 11:54:54] 11:54:54.519893 decode.go:59: Protocols: scm

[2022-05-12 11:54:54] 11:54:54.519899 decode.go:60: Preambles:<PHONE_NUMBER>01001100000

[2022-05-12 11:54:54] 11:54:54.519904 main.go:124: GainCount: 29

Maybe your meter is not SCM but SCM+ ?
There is no problem showing with your output.
Some meters send data only when the utility truck are nearby.
Try playing around with the "LISTEN_ONLY" mode to check if your meter shows up in the output.
Regards.

Thanks Allan. I would appreciate a little help on how to use LISTEN ONLY mode with the Add-On (I'm new a lot of this stuff). Thanks for your hard work!

hey makeitworktech, any chance are you using pge gas meter?


Provide Yarn 2+ lockfiles support

closes #204

:tada: This PR is included in version 8.1.0 :tada:
The release is available on:

v8.1.0
npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


TLP sometimes loses pendrives

Using kinoite-laptop-userns-hardened
This is a known and old TLP bug.
I am not sure if TLP is the best tool for all hardware either.
On my laptop sometimes pendrives dont show up. sudo tlp false fixes this by manually switching to AC mode.
Some time ago I went and made my own tlp.conf but I lost it.
I could try to find the fitting setting and add a minimal conf file to /etc so users can still change it if the want to.
linrunner.de/tlp/settings/
Ostechnix article
It should be
USB_AUTOSUSPEND=0

There is an option to blocklist devices from autosuspend too, which may be useful for usb ports.

This is upstream in multiple ways.

lol but if TLP is included it should at least be easy to avoid this common issue. Documentation?

tlp's installation and corresponding config is owned by ublue bling.

Documentation?

It is not in secureblue nor ublue's scope to document upstream issues.

Okay thanks I will ask ublue then. For me as soon as you package software you can be held accountable for it. I suppose upstream will not fix this in a looong time and this config is an easy, even though not "real" fix

For me as soon as you package software you can be held accountable for it.

neither ublue nor secureblue is packaging tlp.

I would call "preinstalling on an immutable distro" packaging tbh.
Reported upstream

I would call "preinstalling on an immutable distro" packaging tbh.

You would be incorrect. There is no concept of packaging in the industry that would refer to it in such a way. And even if there was, package maintainers are not responsible for bugs in the software they're packaging.  Evaluate where the issue belongs carefully and only then open a report.
This is yet another example of your prioritization of your own interests over community goals and norms. You have consistently declined to follow basic concepts of ownership and scope, even after a 3 day ban. You have repeatedly opened obviously out of scope issues here and who knows where else. In doing so you have demonstrated a disregard for other people's time and effort. My time is better spent on other things instead of constantly reminding you of these basics and the code of conduct.
If you value access to this community at all, cut it out.


add route for akka-http static files

Codecov Report

Merging #61 (9170fd4) into master (d31281d) will decrease coverage by 0.40%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master      #61      +/-   ##
==========================================
- Coverage   52.35%   51.95%   -0.41%
==========================================
  Files          67       67
  Lines         890      897       +7
  Branches       31       24       -7
==========================================
  Hits          466      466
- Misses        424      431       +7

Impacted Files
Coverage Δ

...n/scala/org/bitlap/zim/server/api/ZimUserApi.scala
0.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


Port count and size should affect node size

Best described using an image:

The node size should be at least the size of the largest port group. Also links are at a wrong position when the port group is larger than the node (at least that one should be fixed).

Fixed by PR #162.


v2: Links with aria-current="false" get the same treatment as if the link is for an active page

Describe the issue
When creating a link with aria-current a link can have a style that matches hover and focus states for being active.
Current Behavior
Currently, if aria-current="false" is set, the link will get style treatment as if it is active.
Expected Behavior
When using aria-current="false" as a value, a link should not get style treatment as if it is active. Note that false is marked as a valid value for aria-current.
Reproduction URL
This can easily be seen in any codesandbox running Pico v2
Environment
All environments. This is not unique to a specific browser.

Thanks ❤


How to install "rasterize_tris"?

I want to run on the windows. But I cannot install rasterize_tris. Where can I download this?

Hi,
Did you run setup.py as described in the README?


Remove deprecated elevate methods

Removes elevate_file, elevate_string, and elevate_package which were flagged for removal.
Removes tests associated with deprecated methods.
Minor documentation changes.

There was also an elevate_package.  I don't see that in the README.  Maybe it never was there :-)

I think we removed it from the README when we initially thought about deprecating these methods.. 😅

Should we put it back in??


Test

What issue do you find in Pulsar docs?
Test
What is your suggestion?
Test
Do you have any references?
Test
Would you like to fix this issue?
Test
Note

[X] I have researched my question.

Test

Test


Cant download language package

Wont allow me to download language packets or update windows.

May better use mine: https://github.com/farag2/Windows-10-Setup-Script


Better explanation of botFileSecret

Creating issue as per @JasonSowers for sample readme issue
Sample information
Any sample that uses a .bot file
Describe the bug
In several of the samples, the index.js file looks for botFilePath, botFileSecret, and transcriptsPath in the .env file.
For example, some repro steps:

Clone samples repo
Navigate to a bot. If I chose a Node bot, readmes instruct me to run npm i, and npm start

Get this error without further setup:
Error reading bot file. Please ensure you have valid botFilePath and botFileSecret set for your environment.

 - The botFileSecret is available under appsettings for your Azure Bot Service bot.

 - If you are running this bot locally, consider adding a .env file with botFilePath and botFileSecret.

Should reference proper instructions in all readmes that use .bot files one how to create a .bot file in the first place (i.e. using msbot CLI or manually and referencing an example .bot file)

Link or better explanation of botFileSecret

@nyxsys actually pointed out that the bulk of the samples' index.js are actually written to search for the botFileSecret variable in .env, but the value can actually be set to empty string ""
Expected behavior
Clear instructions on how to get a bot started (i.e. include instructions/link in readme on how to add a bot file that would give user more context as to what the error above on botFilePath and botFileSecret means)
[bug]

@Zerryth and @nyxsys  take a look at 828 and rewview to see if you think this is addressed in the new readme


Using youtube-dl in Windows cmd whilst storing a variable seems to strip non ASCII characters

Checklist

[x] I'm asking a question
[x] I've looked through the README and FAQ for similar questions
[x] I've searched the bugtracker for similar questions including closed ones

Question

Running youtube-dl directly in CMD works as expected:
youtube-dl -e "https://www.youtube.com/watch?v=E_JXrNAxGzM"
It correctly gives the title of the Youtube video: 27/12/2016 晚間新聞 楊家駿直播睇手機
However if I try to store the title as a variable and echo the result, the non ASCII characters are stripped:
FOR /F "delims=" %i IN ('youtube-dl -e "https://www.youtube.com/watch?v=E_JXrNAxGzM"') DO (ECHO %i)
This only gives this result: 27/12/2016
Result of the same code as above but with -v
C:\Users\me>FOR /F "delims=" %i IN ('youtube-dl -e "https://www.youtube.com/watch?v=E_JXrNAxGzM" -v') DO (ECHO %i)
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-e', 'https://www.youtube.com/watch?v=E_JXrNAxGzM', '-v']
[debug] Encodings: locale cp1252, fs mbcs, out cp1252, pref cp1252
[debug] youtube-dl version 2020.06.06
[debug] Python version 3.4.4 (CPython) - Windows-10-10.0.18362
[debug] exe versions: ffmpeg git-2020-05-25-6268034, ffprobe git-2020-05-25-6268034
[debug] Proxy map: {}

C:\Users\me>(ECHO [debug] Default format spec: bestvideo+bestaudio/best )
[debug] Default format spec: bestvideo+bestaudio/best

C:\Users\me>(ECHO 27/12/2016   )
27/12/2016

(Same example here in image form)
Is it something to do with youtube-dl or Windows cmd storing variables?

Nothing to do with youtube-dl.


Closing One Instances Closes all

First of all, Thanks for all the effort. I really like Oni so far! I've just encountered one little Problem:
When i close one instance of Oni with ":q!", all other instances also close. This does not happen, when i terminate an instance with the window managers "x" button. Below is a gif showing the problem:

I'm running ONI 0.2.3-1235 on KDE Neon (Ubuntu 16.04, 64bit)

Cheers @mrWinston , thanks for the kind words!
I've run into this issue every so often too, but forgot to log an issue for it - so thanks for opening it up and including the gif. Definitely a bug

Resolved by #461


Workspace Settings python.pythonPath Error

Hello I am having issues connecting to my Azure Synapse Spark Pools with VS Code on macOS using this extension and following the instructions here: https://docs.microsoft.com/en-us/azure/synapse-analytics/spark/vscode-tool-synapse
Do you have updated instructions that can resolve this issue?
This is the error I get despite running the scripts in a dedicated folder/workspace:
[Error] Error: Unable to write to Workspace Settings because python.pythonPath is not a registered configuration.

I get this error as well, but only when trying to run interactive.

Can we fix this? It drives me and my customers crazy. You cannot use this extension for active Spark development.

We got it working by installing the specific versions of Python and Jupyter extensions as follows:
JUPYTER EXTENSION VERSION: v2022.1.1001614873
PYTHON EXTENSION VERSION: v2021.12.1559732655


AbstractFidoChallengeHandler and telemetry names

Summary
This PR adds the classes of AbstractFidoChallengeHandler, ITelemetryHelper, IFidoTelemetryHelper, and FidoTelemetryHelper and span and attribute names for future telemetry calls.
The eventual PasskeyFidoChallengeHandler, which will take care of getting the FIDO assertion and sending it to the server, will extend AbstractFidoChallengeHandler.
ITelemetryHelper is an interface which helps consolidate the setStatus methods of the CBA and FIDO telemetry helpers. IFidoTelemetryHelper has methods to set the Challenge and ChallengeHandler names on the future Fido span. Noting these object names will help determine the type of FIDO request (authentication vs registration) and the type of passkey used (regular passkey on device, or security key). The main implementation of IFidoTelemetryHelper is FidoTelemetryHelper, and a future implementation  will be done for unit testing purposes.
None of these classes are currently being used in logic, but reviewing them now helps cut down the future PR which will contain the PasskeyFidoChallengeHandler implementation.
Related PRs

https://github.com/AzureAD/ad-accounts-for-android/pull/2547

Added SkipConsumers check label due to some errors occurring in the Linux Broker assemble consumers task which are unrelated to this PR. All the other assemble consumer tasks passed.


CfguType(ConnectionString) RegEx is too broad

Actual behavior
Couldn't find any string that doesn't match the RegEx.
for example:
://example.com
should not match

To Reproduce

Expected behavior

Screenshots

Additional context

We decided to drop this type for now, thanks

We decided to drop this type for now, thanks


image/png: panic whilst decoding png

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
go1.9.1
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
GOARCH=amd64
GOOS=linux
What did you do?
Run the program at: https://play.golang.org/p/yibwQ0ST5z
What did you expect to see?
An error message returned by png.Decode to be printed
What did you see instead?
panic: runtime error: makeslice: len out of range
goroutine 1 [running]:
image.NewNRGBA(...)
        /usr/local/go/src/image/image.go:365
image/png.(*decoder).readImagePass(0xc42008a400, 0x7fb114058030, 0xc4200980f0, 0x0, 0xc420098000, 0x0, 0xc400000000, 0xc4200aa000, 0xc42008a478)
        /usr/local/go/src/image/png/reader.go:460 +0x2dd2
image/png.(*decoder).decode(0xc42008a400, 0x0, 0x0, 0x0, 0x0)
        /usr/local/go/src/image/png/reader.go:365 +0x5bd
image/png.(*decoder).parseIDAT(0xc42008a400, 0x15, 0x4d6b69, 0x4)
        /usr/local/go/src/image/png/reader.go:839 +0x36
image/png.(*decoder).parseChunk(0xc42008a400, 0x0, 0x0)
        /usr/local/go/src/image/png/reader.go:899 +0x409
image/png.Decode(0x549160, 0xc420084180, 0xc42009e050, 0x4e, 0x4e, 0x0)
        /usr/local/go/src/image/png/reader.go:958 +0x156
main.main()
        /home/tyho/workspace/badihdr/main.go:15 +0xbd
exit status 2

This is caused by an integer overflow when multiplying the width of the image by the height, and subsequently trying to allocated a slice with a negative element count. image.New*() functions should probably guard against integer overflow before calling make().
I would like to try to write the fix.
NOTE: this only panics on 64 bit architectures, hence does not panic on the playground.

CC @nigeltao


Server maintance

To upgrade some critical system software we'll need to reboot the API server at 21:00 (GMT+8) tomorrow (21:00, 1 Sept 2017, GMT+8). There will be approximately 1 ~ 3 minutes of down time.

Done.


[#1024] checkstyle.xml: enforce line wrap indentation of 8 spaces

Fixes #1024
checkstyle.xml: enforce line wrap indentation of 8 spaces

The OSS Java Coding standard states that indentation for wrapped
lines should be 8 spaces. This however, is not enforced in the
AddressBook4's checkstyle.

Let's follow the OSS Java Coding standard and enforce line
wrap indentation of 8 spaces, for consistencies' sake.

Note that the checkstyle in AddressBook1,2,3 also does not enforce the 8 space line wrap indentation rule.

Please squash the commits and force push it again.

Done so.

@fzdy1914 how about for AddressBook1,2,3? Should I make PRs to modify those as well?

any updates on this?

@pyokagan Can I have your input?

Looks like this PR got left behind.
@fzdy1914 I'll merge this if you are OK with this. Confirm OK?

LGTM. @damithc


Firefox version?

Not being familiar with porting Chrome extensions to Firefox, is it possible to easily port this extension to Firefox?
Excellent extension on Chrome.

On review now.

Published: https://addons.mozilla.org/firefox/addon/add-to-microsoft-to-do/
If you notice any problems with the extension, please let me know.


wasm-bindgen doesn't work on latest nightly

Describe the Bug
For my current project I am compiling my Rust crate to wasm32 and it was working up until I try to update to the latest nightly version. I am using parking_lot for their Mutex and RwLock but with the latest nightly of Rust and the latest wasm-bindgen I am getting a strange error:
i32_atomic_wait in module wasm32 in parking_lot_core-0.7.2/src/thread_parker/wasm_atomic.rs:47:38.
When I lock the toolchain to nightly-2020-05-15 it works just fine.
Is there something I am missing or doesn't this work with the latest nightly yet?

AFAIK the latest nightly should work ok, I recently compiled the parallel raytrace application just fine. Do you have some source code to peek at, or perhaps want to gist the full build log?

So for some reason I am now getting this if I bump wasm-bindgen-futures from 0.4.13 to 0.4.19:
error[E0425]: cannot find function `memory_atomic_notify` in module `core::arch::wasm32`
  --> /Users/delm/.cargo/registry/src/github.com-1ecc6299db9ec823/wasm-bindgen-futures-0.4.19/src/task/multithread.rs:39:33
   |
39 |             core::arch::wasm32::memory_atomic_notify(
   |                                 ^^^^^^^^^^^^^^^^^^^^ not found in `core::arch::wasm32`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0425`.
error: could not compile `wasm-bindgen-futures`.

I saw that you're using the same version for the raytracing exmaple. Any idea why it would not work for me?
Here's my dependencies:
[dependencies]
js-sys = "0.3.46"
wasm-bindgen = { version = "0.2.69", features = ["serde-serialize"] }
once_cell = "1.5.2"
serde = { version = "1.0.117", features = ["derive", "rc"] }
serde-wasm-bindgen = "0.1.3"
serde_json = "1.0.60"
serde_repr = "0.1.6"
cfg-if = "1.0.0"
futures = "0.3.5"
wasm-bindgen-futures = "0.4.19"
parking_lot = { version = "0.10.2", features = ["nightly", "serde"] }
console_error_panic_hook = { version = "0.1.6", optional = true }

And my cargo config
[build]
rustflags=["-C", "target-feature=+atomics,+bulk-memory"]

And last but not least, I am running wasm-pack:
wasm-pack build --out-dir dist --release --target web -- -Z build-std=std,panic_abort

Hm what rustc version are you're using? I think you'll want to be sure you're using the latest nightly

For what it's worth, I am getting the same on the raytracing

Oh dang, you're right. I was not on the latest rustc nightly.

Yep, that works. Now I have another issue but that's not wasm-bindgen related.


Change GCST for a study

Would it be possible to change 'GCST90188384' to 'GCT90002413'?
GCT90002413 exists and is referenced in the user's paper, but I had to resubmit all their sumstats in a new submission: '635a4733c6aae2000190d5a5'.
The original submission '5f4513ae2d70930001d640f5' could be deleted, if necessary.

The user has confirmed all 16 files should be made available. Similar to ticket #886, I suggest:

Delete submission '5f4513ae2d70930001d640f5' and 'GCT90002413' (including sumstats folder on FTP).
Change GCST90188384 to GCT90002413

@sajo-ebi okay, I think that's because the template is invalid 'https://www.ebi.ac.uk/gwas/deposition/submission/5f4513ae2d70930001d640f5'. Please could you change 'GCST90188384' to 'GCT90002413' anyway?

@earlEBI done

@sajo-ebi brill, thank you.

ticket can be closed.


trulens-connectors-snowflake 1.1.0 :snowflake:

trulens-connectors-snowflake 1.1.0 :snowflake:
Destination channel: Snowflake
Links

PKG-5844
dev_url:        https://github.com/truera/trulens/tree/trulens-1.1.0
conda_forge:    None
pypi:           n/a
pypi inspector: n/a

Explanation of changes:

new version number

CI seems unstable?
2024-10-18T10:57:08.782365+00:00  | INFO     |   Solving environment: ...working... done
2024-10-18T10:57:09.438843+00:00  | INFO     |
2024-10-18T10:57:09.440154+00:00  | INFO     |   ('Connection broken: IncompleteRead(948541 bytes read, 5155745 more expected)', IncompleteRead(948541 bytes read, 5155745 more expected))


Ignore unparseable files from telemetry reporting

Is your feature request related to a problem? Please describe.
Any package.json file being edited that breaks the json format still triggers dependency analysis. Analysis fails because of the malformed document but is reported in Woopra, which adds no value because it's not actionable, eg:
component_analysis_failed, error:
column=44&line=8&message=Unexpected symbol <c> at 8:44 6 | "scripts": { 7 | "test": "echo \"Error: no test specified\" && exit 1", 8 | "deploy": "serverless deploy -s, ^ 9 | "create:domain": "serverless create_domain -s", 10 | "start:offline": "serverless offline --skipCacheInvalidation start -s"&name=SyntaxError&rawMessage=Unexpected symbol <c> at 8:44&source=

Moreover these eat our Woopra action quota.
Describe the solution you'd like
Unless there's value in reporting such events (please enlighten me), please ignore syntax errors from reporting, so we can focus on real errors.

@fbricon , yes. this should be ignored.


conda install fails on travis-ci with Python 3.6

@bsipocz - The Python 3.6 builds on travis-ci are failing with a conda install fail:
https://travis-ci.org/astropy/regions/jobs/202159396
UnsatisfiableError: The following specifications were found to be in conflict:
  - astropy
  - numpy 1.12*
  - python 3.6*

This is just a CI issue, so I'll still cut the 0.2 release now.
(just mentioning it so that you don't commit to master, but go through a pull request to fix this CI issue)

Yes, this is annoying and I'm figuring out a workaround today as others reported this, too. Too bad that conda updates their package list so slow this time, numpy 1.12 was released a month ago.

Well, probably there are zero issues with 3.6 that aren't covered by testing with 3.5.
So my suggestion would be that you just deactivate the Python 3.6 entries from the build matrix and in a month or two, when the issue has resolved itself, re-activate them.

The issue is not with 3.6, but with numpy 1.2, as there is no build for this combination yet. There will be one on conda-forge, soon, but that won't help us in most of the packages.
I'll add a workaround into ci-helpers later today, so install astropy from pip in this case, but that's an ugly hack so I'll wait a bit longer in case someone has a better idea...

We're now getting a similar (the same?) error in Gammapy with Python 3.5 also:
https://travis-ci.org/gammapy/gammapy/jobs/202965853
Is there any way to fix or work around this conda install issue?
The Gammapy coding sprint in Paris  🇫🇷 starts tomorrow.
cc @adonath

@cdeil - The regions one should already work (astropy 1.3 + np1.12).
The gammapy one you get is due to the missing photutils version. I'll look that issue tonight, and will try to build the missing conda packages (have an idea for working around the current conda issue). I'll ping you once it's done. If nothing else works then I would suggest to temporarily use pip for photutils.

@cdeil - Unfortunately I don't think I can do much about this until the 1.12 builds became available on the defaults channel (e.g. https://travis-ci.org/bsipocz/gammapy/jobs/203288932, that has that only change on top of the branch you linked above). As a workaround I would though suggest to add conda-forge to CONDA_CHANNELS, so conda install photutils will see the astropy builds from there (somehow having astropy installed from pip is not good enough to it).

closing this issue as regions is all green now.


⚠ Bofrost.lu has degraded performance

In f416989, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1155 ms

Resolved: Bofrost.lu performance has improved in 1ab5e3d after 8 minutes.


[Suggestion] tetra compat

It would be nice to be able to configure tetra weapons for custom damage percentage based on modules.

Oops, duplicate of #17


Trying to reinstall bun when it is installed

Describe the bug
When initializing a reflex project with reflex init, it does not check properly if bun is already installed. In fact, it check if bun is installed but, even if it is installed, reflex tries to reinstall it again.
Analyzing the code I saw that it is an issue with the versions check. I would like to fix the error.
To Reproduce
Steps to reproduce the behavior:

Running reflex init --loglevel debug when node is already installed.

Expected behavior
It should skip the installation of bun if it is already installed and the version is higher than the required one.
Screenshots
There is a partial copy of the output in debug mode.
Debug: [Reflex 0.4.2 with Python 3.11.2 (PATH: /home/paos/test_reflex/.venv/bin/python3)]
Debug: [Node 18.19.0 (Expected: 18.17.0) (PATH:/usr/bin/node)]
Debug: [FNM 1.35.1 (Expected: 1.35.1) (PATH: /home/paos/.local/share/reflex/fnm/fnm)]
Debug: [Bun 1.0.29 (Expected: 1.0.13) (PATH: /home/paos/.local/share/reflex/bun/bin/bun)]
Debug: [OS Linux Debian GNU/Linux 12 (bookworm)]
...
Debug: Running command: ['/home/paos/.local/share/reflex/bun/bin/bun', '-v']
Debug: Downloading https://bun.sh/install

Specifics (please complete the following information):

Python Version: 3.11.2
Reflex Version: 0.4.2
OS: Debian 12 (on WSL)

Thanks would be happy to accept a pr that fixes this


Added the ability to inject config properties into EntityManager creation.

This pull request is my solution to https://github.com/google/guice/issues/933

Travis CI failed due to an issue unrelated to my pull request:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:2.7:jar (default) on project guice: Execution default of goal org.apache.maven.plugins:maven-javadoc-plugin:2.7:jar failed: Plugin org.apache.maven.plugins:maven-javadoc-plugin:2.7 or one of its dependencies could not be resolved: Could not transfer artifact commons-collections:commons-collections:jar:3.2 from/to central (https://repo.maven.apache.org/maven2): GET request of: commons-collections/commons-collections/3.2/commons-collections-3.2.jar from central failed: Connection reset -> [Help 1]


n_trees is annoy_n_trees in bbknn 1.5.x

Latest BBKNN versions (>=1.5.x) uses annoy_n_trees in place of n_trees, just applying that fix here.

I've already opened a more comprehensive PR for this five days ago, but haven't heard back on it.

Ahh, apologies @ktpolanski , closing now.

All good, thanks for doing this :)

Hi,
I also met this problem. I am using Scanpy 1.7.2, and could you please suggest which version of BBKNN I should use if I don't want to update Scanpy to 1.8.0.
Thanks,
Min

The scanpy one is just a wrapper for bbknn.bbknn(). Use that one.

Two options:

bbknn < 1.5.0
use bbknn.bbknn() instead of the scanpy wrapper

Thank you for your rapid reply, bbknn 1.4 works for me (scanpy 1.7.2). The second option is good.
Thanks!


support requirements

Hi, I am interested in adding atomicswap capability to a Bitcoin-based altcoin. Is there a checklist of required capabilities?
Update. I found https://blog.decred.org/2017/09/20/On-Chain-Atomic-Swaps/

In order to perform an on-chain atomic swap between 2 cryptocurrencies, there are several prerequisites. Both chains must support:

branched transaction scripts
the same hash algorithm in both chains’ transaction scripts
signature checks in transaction scripts
CheckLockTimeVerify or CheckSequenceVerify (“CLTV” and “CSV” for short) in transaction scripts

Since Decred and Litecoin are forks of Bitcoin, the first 3 conditions are trivially satisfied. Further, both Decred and Litecoin have been tracking updates from Bitcoin, so they both support CLTV. The CLTV/CSV support is used to effect a refund, in the cases where either party does not complete part of the process. With some further work on part of other Bitcoin-based cryptocurrency projects, this on-chain atomic swap can occur between any pair of cryptocurrencies that satisfy the above constraints.

Some of these items, I can add in, but is it truly necessary for the same hash algorithm in both chains? Why is this needed?

Yes, both chains must support the same hash opcode. We use SHA256.

Closing due to age and the question has been answered.


Leverage and Influence for recommendation

https://las.inf.ethz.ch/files/mcwilliams14fast-long.pdf

Based on the statistical concepts of leverage of linear regression,
we should be able to recommend points that are most useful to get a label.

What would be the GP version?
How it this related to D-optimal design?
Leverage additionally takes the residual error into account, and therefore
needs access to the labels to compute. However a semi-supervised approach might be feasible.


Mat-Button and Mat-Chips do not respect $fontConfig SCSS variables

Bug, feature request, or proposal:
In the SCSS variable $fontConfig, the button property specifies the font-size, and line-height values for the mat-button elements.  Additionally, the body-2 property specifies the stylings which are used for the mat-chip elements.
What is the expected behavior?
When modifying the font-size and line-height for buttons/chips, the padding should be relative to these variables.
What is the current behavior?
The padding is fixed, and is not relative to the font-size.  It is configurable, but not through the theme or it's variables.
What are the steps to reproduce?
The stackblitz app, https://angular-e7zgff.stackblitz.io, shows the material.angular.io button documentation, with the button font-size set to 9px with a line-height of 10px.

What is the use-case or motivation for changing an existing behavior?
I'm working on a Material theme generator (http://materialtheme.arcsine.org), and the button font-size is a configurable property.  I am currently working around this by overriding the padding/line-height behavior to achieve the desired state.
// Handle buttons appropriately, with respect to line-height
.mat-raised-button, .mat-stroked-button, .mat-flat-button {
  padding: 0 1.15em;
  margin: 0 .65em;
  min-width: 3em;
  line-height: 36.4px // Computed from selected line-height for the font.
}

.mat-standard-chip {
  padding: .5em .85em;
  min-height: 2.5em;
}

Which versions of Angular, Material, OS, TypeScript, browsers are affected?
All
Is there anything else we should know?

@devversion Was hoping for some direction if possible.  Thought it seems like it might be a more wholistic conversation about variables in general.

Just came across this. I created an up-to-date StackBlitz that sets the $button typography configuration. https://stackblitz.com/edit/comp-14359?file=src/styles.scss.
I'm not sure which padding is referred to here? It looks like the button only has horizontal padding, while the actual button height is based on the line-height. The bug here seems that line-height from the typography configuration is not respected in the button (where 36px line-height is hard-coded).

Closing because no clarification was provided.


Use type annotations to allow type-checking of unknowns

Category
Cedar validation features
Describe the feature you'd like to request
Currently, unknowns have a type_annotation field but it is unused during validation. In my fork of Cedar  which I used to implement a translation from Cedar policies to SQL (so that users could e.g. query all resources that a principal has access to), I added this feature by changing the unknown type annotation to SchemaType.
There is a reasonably straightforward way to turn SchemaTypes into validator Types. The only tricky bit is what to convert EmptySet into, and here I chose Set(Never). This allows us to type check expressions with unknowns in them.
Describe alternatives you've considered
An alternative to using SchemaTypes would be to continue using the existing "runtime" types, and simply making unknowns annotated with Set and Record give type errors (or Record could even go to a record with open_attributes set to true).
Finally, we could simply refuse to type check unknowns entirely.
Additional context
To see my implementation, see https://github.com/cedar-policy/cedar/compare/main...prakol16:cedar:partial_eval_to_sql and ctrl+f the file cedar-policy-validator/src/typecheck.rs (note that there are 2 major changes: I also added support for variadic extension functions that take in an unknown number of parameters, to support rawsql).
Is this something that you'd be interested in working on?

[ ] 👋 I may be able to implement this feature request
[ ] ⚠ This feature might incur a breaking change

Thanks for the suggestion @prakol16! We've decided that this issue requires further discussion to decide on the exact syntax, whether to allow type annotations anywhere else, and so on, so I'm marking this issue as "requires RFC". We'll leave the issue open until we (or an external contributor) get around to making a proper RFC, following the instructions here https://github.com/cedar-policy/rfcs.


Completely wrong output

when i compare the results given and the other speed test, the difference is so huge.

I have the same problem....

I had this same problem, so I understand that this is solved using a server near your region.

I have the same problem.
sometimes it shows up to 3000 Mbps


fix radius ValueError in case of non int values

Coverage decreased (-0.1%) to 89.072% when pulling 90b3731a32c84c7fe9ff5a80925ee592bbaa5373 on feature/radius-value-error-fix into 6c0749bdb310138b873398714e8a3338e9698d46 on develop.


[Question]: Display issues with Task Executor

Describe your problem
When accessing the system interface, the task executor has no content displayed, and the backend always reports the following error. There is a problem when retrieving data from the Redis database

Looks like the TASK EXECUTOR isn't startup. Do you have more error log information?

The following issue is that taskexecutors are None and cannot iterate RedisDB.smembers TASKEXE encountered an exception: WRONGTYPE operation was performed on keys holding incorrect type values. Below is my Redis image

The type of key TASKEXE is indeed not a set. What is the reason for this


Django 1.10 / 1.11

Minimal code changes and doc updates for django 1.10 (and 1.11) compatibility.
These change allow for: installation, example survey loading, completion, and results download.
No guarantee that there are not still other compatibility issues to address.
One detail I noticed: rendering of headers in links is not correct (":/take/1" on the example main page, and "h1" headers), not sure how to correct that.

@gcaprio any feedback?

Merged. Thanks @pathway


Add continuous-integration

[x] add continuous-integration
[x] add .gitattributes to reduce pkg size shipped to users

⚠ This requires activating GitHub actions for this repo.

Wow, thanks! I've always wanted to set this up. Let me check the status of GitHub actions here.

I think this should "just work" ™ as soon as we pull this PR. I'll just try and see..

Well, it doesn't work at all. Actions are enabled for the repo. I'm totally in the dark about why it doesn't see the new workflow file and refuses to do anything.

maybe because this is a fork?

It does run now apparently. I forgot it would only run when you touch a file in the paths

Yeah.

Here's the workflow badge, in case you want it:
![CI](https://github.com/braver/SublimeSass/workflows/CI/badge.svg)

I didn't add it with this PR.


[BUG] Unable to create or import environments with names like DEV or QA.

An error is thrown on create, rename or import the environment with name dev or qa.

@Sergi0Martin Isn't it because you already have environments with those names ? Haven't been able to reproduce your error without have duplicate names. We could correct "An error occured while created" btw.

@Sergi0Martin Isn't it because you already have environments with those names ? Haven't been able to reproduce your error without have duplicate names. We could correct "An error occured while created" btw.

No, I have not environments with those names. What I did first was try to import from postman environment and the error was thrown, after that either create nor rename wasn't possible.
I downloaded the app yesterday so it should be the last version.

Could you provide a screen record or the exact process you used to reproduce this issue ?
I tried importing a postman environment named DEV, renaming it to DEV2, renaming it back to DEV

@bpoulaindev
Here is the video and the environmente file generated by postman, I removed some values for security reasons:

DEV.postman_environment.json

I see what's happening, first time importing the env works fine but it doesn't appear in collection.

The second import crashes because we're importing with the same name as the previous one, however the file still exists in the directory it's just unreadable, i'll see what i can do.

I think it should not persist that file if the import failed. And some kind of error message in the devtool console would be also great.
Thanks @bpoulaindev.

I will like to add on to this issue. I tried to create environment name Localhost or localhost, it faild with the error message An error occurred while created the environment, but there is no error message in the console.
I can't create it even though I don't have any environments.

@jiaming10 are you sure the environment isn't corrupted ? i can use the "localhost" name withut any issue, although it's with a very basic env file

@jiaming10 are you sure the environment isn't corrupted ? i can use the "localhost" name withut any issue, although it's with a very basic env file

Sorry for the misunderstanding. I do have the envs in my folder, but it is not shown in Bruno client. So this leads to the confusion where:

Bruno unable to detect the localhost env in the folder.
Bruno unable to create localhost, because the env existed in the folder.

@bpoulaindev you are right that the environment is corrupted. The imported Postman environment has variables with spaces in the name.
vars {
  User PasswordRecoveryToken:
  User PasswordRecoveryTokenMobilePin:
  User ChangeEmailTokenMobilePin:
}

Closing the issue as it seems to be resolved. Please open a new issue if it isn't!


Use of a controller to call welcome module API

Needed to avoid relative path in file include

Thanks for that PR @toutantic !
It should fix bugs like this one : http://forge.prestashop.com/browse/BOOM-3036
@maximebiloe @aleeks  could you merge and create a new build of the module ?
Thanks guys

@vincentbz this PR doesn't fix anything. Why did you say that ?!!


fix: removed stage-packages from gcloud part

Visualisation ROCK failed to build in GH runner due to incorrect rockcraft.yaml file.
stage-packages are not needed in gcloud part.
Logs are in https://github.com/canonical/pipelines-rocks/actions/runs/5639877801/job/15275708711
Summary of changes:

Removed stage-packages from gcloud part.

Do you have the GitHub Action log to see the error ?

Do you have the GitHub Action log to see the error ?

Updated description.

@SamirPS I will be closing this. I think there is another issue.

The problem came because you forgot a s at the field it's stage-packages .  @i-chvets


Add a "... more news" link

To bottom of news overlay on landing page

Added

Done and tested on production


Add eslint-plugin-import-order to plugins

As per request, this adds eslint-plugin-import-order to the list of plugins.
Let me know if and where I need to add tests, as I could not find related ones.

Let me know if and where I need to add tests, as I could not find related ones.

Nah. Already have one to ensure plugins are loaded.

Been running it over some of my projects and seems to work good :)

Cool!

Saw a few raised issues, and will keep working on it ;)


support DESTDIR and prefix installation

The Makefile does not support a configurable installation destination. It should be fixed to support both DESTDIR and prefix as documented here:
https://www.gnu.org/prep/standards/html_node/DESTDIR.html

The Makefile is mostly just a convenience wrapper around Meson, and by extension Ninja. That is to say, depending on your use-case, it may be best to fallback to the underlying commands.
That said, DESTDIR seems to be working for me. Like I can do this:
~/ttfrm$ DESTDIR=/tmp/ttfrm make install
cd build && ninja install
[0/1] Installing files.
Installing /home/tim/ttfrm/ttfrm/tfrm.hpp to /tmp/ttfrm/usr/local/include/ttfrm
Installing /home/tim/ttfrm/ttfrm/tfrm_tree.hpp to /tmp/ttfrm/usr/local/include/ttfrm
Installing /home/tim/ttfrm/build/meson-private/ttfrm.pc to /tmp/ttfrm/usr/local/lib/x86_64-linux-gnu/pkgconfig

On the other hand, prefix is not working through the Makefile, and I think using it will require using Meson directly, such as:
~/ttfrm$ meson --prefix=/prefix build
...
~/ttfrm$ cd build
~/ttfrm/build$ DESTDIR=/tmp/ttfrm ninja install
...
Installing /home/tim/ttfrm/ttfrm/tfrm.hpp to /tmp/ttfrm/prefix/include/ttfrm
Installing /home/tim/ttfrm/ttfrm/tfrm_tree.hpp to /tmp/ttfrm/prefix/include/ttfrm
Installing /home/tim/ttfrm/build/meson-private/ttfrm.pc to /tmp/ttfrm/prefix/lib/x86_64-linux-gnu/pkgconfig


[Task]: Delete only the editable version, not the published ones and don’t allow instantiate of modules for that module

SubTasks

Delete only the editable version, not the published ones, and don’t allow instantiation of modules for that module
Consumable APIs should only return the latest excluding ones that are deleted
Related thread on Slack

We will revisit the entire delete flow later. Till then it will be put in the ICE BOX.


OSError: CUDA_HOME environment variable is not set. Please set it to your CUDA install root.

Operating Environment:
Windows 11, Python 3.10.14 under Conda.
I am very sure that all environment variables related to CUDA are set correctly, but I still get an error after running pip install e .:
Installing build dependencies ... done
Getting requirements to build wheel ... error
error: subprocess-exited-with-error
× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> [24 lines of output]
C:\Users\jiahe\AppData\Local\Temp\pip-build-env-zvisi0tm\overlay\Lib\site-packages\torch_subclasses\functional_tensor.py:258: UserWarning: Failed to initialize NumPy: No module named 'numpy' (Triggered internally at C:\actions-runner_work\pytorch\pytorch\builder\windows\pytorch\torch\csrc\utils\tensor_numpy.cpp:84.)
cpu = _conversion_method_template(device=torch.device("cpu"))
Traceback (most recent call last):
File "C:\Users\jiahe.conda\envs\sam2\lib\site-packages\pip_vendor\pyproject_hooks_in_process_in_process.py", line 353, in
main()
File "C:\Users\jiahe.conda\envs\sam2\lib\site-packages\pip_vendor\pyproject_hooks_in_process_in_process.py", line 335, in main
json_out['return_val'] = hook(**hook_input['kwargs'])
File "C:\Users\jiahe.conda\envs\sam2\lib\site-packages\pip_vendor\pyproject_hooks_in_process_in_process.py", line 118, in get_requires_for_build_wheel
return hook(config_settings)
File "C:\Users\jiahe\AppData\Local\Temp\pip-build-env-zvisi0tm\overlay\Lib\site-packages\setuptools\build_meta.py", line 327, in get_requires_for_build_wheel
return self._get_build_requires(config_settings, requirements=[])
File "C:\Users\jiahe\AppData\Local\Temp\pip-build-env-zvisi0tm\overlay\Lib\site-packages\setuptools\build_meta.py", line 297, in _get_build_requires
self.run_setup()
File "C:\Users\jiahe\AppData\Local\Temp\pip-build-env-zvisi0tm\overlay\Lib\site-packages\setuptools\build_meta.py", line 313, in run_setup
exec(code, locals())
File "", line 70, in
File "", line 51, in get_extensions
File "C:\Users\jiahe\AppData\Local\Temp\pip-build-env-zvisi0tm\overlay\Lib\site-packages\torch\utils\cpp_extension.py", line 1076, in CUDAExtension
library_dirs += library_paths(cuda=True)
File "C:\Users\jiahe\AppData\Local\Temp\pip-build-env-zvisi0tm\overlay\Lib\site-packages\torch\utils\cpp_extension.py", line 1214, in library_paths
paths.append(_join_cuda_home(lib_dir))
File "C:\Users\jiahe\AppData\Local\Temp\pip-build-env-zvisi0tm\overlay\Lib\site-packages\torch\utils\cpp_extension.py", line 2416, in _join_cuda_home
raise OSError('CUDA_HOME environment variable is not set. '
OSError: CUDA_HOME environment variable is not set. Please set it to your CUDA install root.
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error
× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.

same issue, I am using virtualenv. I got passed it once, but decided to clone again fresh and this time I can't get past this step for some reason.

https://github.com/facebookresearch/segment-anything-2/issues/19

#19

Thank you, but I have already seen this issue and tried pip install --no-build-isolation -e .
I still get the error OSError: CUDA_HOME environment variable is not set. Please set it to your CUDA install root.

to build sam2, first you also need to install these (at least for me it was):
--extra-index-url https://download.pytorch.org/whl/cu121 # here set your cuda version if it's not 12.1
torch>=2.3.1
torchvision>=0.18.1
transformers
numpy<2
tqdm>=4.66.1
hydra-core>=1.3.2
iopath>=0.1.10
pillow>=9.4.0
wheel
ninja

let me know if this helps.

to build sam2, first you also need to install these (at least for me it was):
--extra-index-url https://download.pytorch.org/whl/cu121 # here set your cuda version if it's not 12.1
torch>=2.3.1
torchvision>=0.18.1
transformers
numpy<2
tqdm>=4.66.1
hydra-core>=1.3.2
iopath>=0.1.10
pillow>=9.4.0
wheel
ninja

let me know if this helps.

No need to install these explicitly since they are already set as install deps in setup.py.
Segment Anything 2.0 require to compile a .cu file with nvcc at build time. Hence, a cuda installation is required. You can use a "cuda devel" pytorch docker image if you want to avoid installing cuda on your machine.

I'm experiencing the same problems. I have tried installing different versions of CUDA (12.1, 12.4, 12.5), all with the respective pytorch. Checked that cuda is available (import torch > torch.cuda.is_available() > returns True).
When I run pip install e ., I get an error similar to yours, where CUDA_HOME is not set. And when I run pip install --no-build-isolation -e . as suggested in other threads, I get "An error happened while installing SAM 2 in editable mode."
Ran out of things to try.

 You need the CUDA compiler.

I'm experiencing the same problems. I have tried installing different versions of CUDA (12.1, 12.4, 12.5), all with the respective pytorch. Checked that cuda is available (import torch > torch.cuda.is_available() > returns True).
When I run pip install e ., I get an error similar to yours, where CUDA_HOME is not set. And when I run pip install --no-build-isolation -e . as suggested in other threads, I get "An error happened while installing SAM 2 in editable mode."
Ran out of things to try.

 You need the CUDA compiler.

I'm experiencing the same problems. I have tried installing different versions of CUDA (12.1, 12.4, 12.5), all with the respective pytorch. Checked that cuda is available (import torch > torch.cuda.is_available() > returns True).
When I run pip install e ., I get an error similar to yours, where CUDA_HOME is not set. And when I run pip install --no-build-isolation -e . as suggested in other threads, I get "An error happened while installing SAM 2 in editable mode."
Ran out of things to try.

 You need the CUDA compiler.

nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2023 NVIDIA Corporation
Built on Wed_Feb__8_05:53:42_Coordinated_Universal_Time_2023
Cuda compilation tools, release 12.1, V12.1.66
Build cuda_12.1.r12.1/compiler.32415258_0

I'm experiencing the same problems. I have tried installing different versions of CUDA (12.1, 12.4, 12.5), all with the respective pytorch. Checked that cuda is available (import torch > torch.cuda.is_available() > returns True).
When I run pip install e ., I get an error similar to yours, where CUDA_HOME is not set. And when I run pip install --no-build-isolation -e . as suggested in other threads, I get "An error happened while installing SAM 2 in editable mode."
Ran out of things to try.

 You need the CUDA compiler.

Yes, I also reinstalled the environment and followed the commands provided on the PyTorch official website exactly:
pip3 install torch torchvision torchaudio --index-url https://download.pytorch.org/whl/cu124

Then, I downloaded CUDA Toolkit 12.4 according to the CUDA version specified by PyTorch and updated the CUDA environment variables.
Running nvcc --version outputs the following:
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2024 NVIDIA Corporation
Built on Tue_Feb_27_16:28:36_Pacific_Standard_Time_2024
Cuda compilation tools, release 12.4, V12.4.99
Build cuda_12.4.r12.4/compiler.33961263_0

After that, I confirmed that torch.cuda.is_available() indeed returns true.
However, when I run pip install -e ., it still throws the error:
OSError: CUDA_HOME environment variable is not set. Please set it to your CUDA install root.

I'm experiencing the same problems. I have tried installing different versions of CUDA (12.1, 12.4, 12.5), all with the respective pytorch. Checked that cuda is available (import torch > torch.cuda.is_available() > returns True).
When I run pip install e ., I get an error similar to yours, where CUDA_HOME is not set. And when I run pip install --no-build-isolation -e . as suggested in other threads, I get "An error happened while installing SAM 2 in editable mode."
Ran out of things to try.

 You need the CUDA compiler.

Yes, I also reinstalled the environment and followed the commands provided on the PyTorch official website exactly:
pip3 install torch torchvision torchaudio --index-url https://download.pytorch.org/whl/cu124

Then, I downloaded CUDA Toolkit 12.4 according to the CUDA version specified by PyTorch and updated the CUDA environment variables.
Running nvcc --version outputs the following:
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2024 NVIDIA Corporation
Built on Tue_Feb_27_16:28:36_Pacific_Standard_Time_2024
Cuda compilation tools, release 12.4, V12.4.99
Build cuda_12.4.r12.4/compiler.33961263_0

After that, I confirmed that torch.cuda.is_available() indeed returns true.
However, when I run pip install -e ., it still throws the error:
OSError: CUDA_HOME environment variable is not set. Please set it to your CUDA install root.

Afterward, I successfully ran the command by following the solution provided in #19: pip install --no-build-isolation -e .
(win11,conda python 3.10,cuda 12.4,pytorch:pip3 install torch torchvision torchaudio --index-url https://download.pytorch.org/whl/cu124)

Thank you all for your help, the issue has been resolved. Here is the method I used (on Windows 11):
First, download cuda12.4;
Then:
Add a new entry to the system environment variables, with the name CUDA_HOME and the value C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v12.4;
Final:
cd \segment-anything-2
conda create -n sam2 python=3.10

pip3 install torch torchvision torchaudio --index-url https://download.pytorch.org/whl/cu124

pip install --no-build-isolation -e .
pip install --no-build-isolation -e ".[demo]"

Thank you all for your help, the issue has been resolved. Here is the method I used (on Windows 11):
First, download cuda12.4;
Then:
Add a new entry to the system environment variables, with the name CUDA_HOME and the value C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v12.4;
Final:
cd \segment-anything-2
conda create -n sam2 python=3.10

pip3 install torch torchvision torchaudio --index-url https://download.pytorch.org/whl/cu124

pip install --no-build-isolation -e .
pip install --no-build-isolation -e ".[demo]"

can't segment anything-2  work on server without GPU?

Thank you all for your help, the issue has been resolved. Here is the method I used (on Windows 11):
First, download cuda12.4;
Then:
Add a new entry to the system environment variables, with the name CUDA_HOME and the value C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v12.4;
Final:
cd \segment-anything-2
conda create -n sam2 python=3.10

pip3 install torch torchvision torchaudio --index-url https://download.pytorch.org/whl/cu124

pip install --no-build-isolation -e .
pip install --no-build-isolation -e ".[demo]"

is CUDA 12.4 necessary? Can 12.1 work?

Thank you all for your help, the issue has been resolved. Here is the method I used (on Windows 11):
First, download cuda12.4;
Then:
Add a new entry to the system environment variables, with the name CUDA_HOME and the value C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v12.4;
Final:
cd \segment-anything-2
conda create -n sam2 python=3.10

pip3 install torch torchvision torchaudio --index-url https://download.pytorch.org/whl/cu124

pip install --no-build-isolation -e .
pip install --no-build-isolation -e ".[demo]"

is CUDA 12.4 necessary? Can 12.1 work?

yup, works fine on 12.1.

Ran into another error: C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v12.1\include\crt/host_config.h(153): fatal error C1189: #error:  -- unsupported Microsoft Visual Studio version! Only the versions between 2017 and 2022 (inclusive) are supported! The nvcc flag '-allow-unsupported-compiler' can be used to override this version check; however, using an unsupported host compiler may cause compilation failure or incorrect run time execution. Use at your own risk.
(I'm using VS 2022 Preview, which apparently causes this error)
I edited the setup.py to include -allow-unsupported-compiler on NVCC and it seems to have finally built. Hopefully I can get it running this time!

-allow-unsupported-compiler

It works for me. Thx

棒极了，终于环境问题解决了！！！！


Remove geopandas as a run dependency

This PR resolves #330
as it looks like geopandas dependency increased the conda resolving time considerably, this PR removes geopandas from run dependency.

this PR is ready for review. thanks!

@jclay .. sounds good. I will do it. thanks!

Thanks @xmnlab looks good!
We will want to keep an eye on the libtiff=4.0.10 pin as well. As soon as that build issue affecting libtiff is fixed, we will likely see some benefit from relaxing that as well.

sounds good. I opened an issue for that: https://github.com/omnisci/pymapd/issues/334


SysCallEnterTraceData + ProcessId and ThreadId not set

Hey all,
i'm not sure whether this is a real issue or not. Whenever i check the data within SysCallEnterTraceData, the given ProcessId as well as the ThreadId is -1. I saw several places in code where comments suggested, that there is/was an issue with the corresponding ProcessId and ThreadId.
Is there no ProcessId and ThreadId available in this case, or is there a bug? Unfortunately i haven't found anything in documentations concerning this topic.
Thx in advance

The SysCall events don't have any thread or process information which is why you see -1.   However IF there are stacks associated with the events the thread and process information is there and PerfView can extract it  (in my experiment it does get the thread ID.
It turns out that PerfVIew did this fixup for the threadID but not he process ID.   I have a fix in flight to fix it for the process ID as well.
However you can work-around this problem by not using the EventViewer and instead us the 'Any Stacks' view for the SystCalls. these will have the process ID in them.

I have checked in the changes to make SysCalls work better.   I am closing the issue for now.


GNU License is too restrictive

From memory the GNU License prevents use in applications without open source release of all code in that application. Unfortunately this will prevent your code being used by many people. Please consider changing to a more permissive license.

Licences are not my domain. Can you tell me which will be bets for this. I don't want to prevent people use it. What about MIT?

@camohub Yes MIT is good, thanks.

Done.


fix(KFLUXBUGS-1116): support signing all manifest digests

add-fbc-contribution now produces a result of the digests for each arch found in the manifest list
sign-index-image now consumes this list and creates an InternalRequest for each digest.
fbc-release updated to specify new parameter for sign-index-image

Requires https://github.com/hacbs-release/app-interface-deployments/pull/74

Fixed problem with https://github.com/hacbs-release/app-interface-deployments/pull/75
/test release-pipelines-e2e-suite


Debug Recommendations

Nice plugin! Working as expected.
Any recommendations for a debug/breakpoint setup if I am looking to extend this?

Hi @guzman-raphael,
what exactly do you want to debug?
The module implements only pam_sm_authenticate(), which calls oauth2_authenticate(). The last one does most of the job.
For local debugging probably the easiest would be adding the main() function and calling oauth2_authenticate() from it.


Update CI to no longer deny linter warnings

This can be a bit of a difficulty for folks opening PRs and then the linter complains about completely unrelated code and denies their PR.
Instead, we continue to warn about these issues, but we do not block CI.

@dnaka91 @simbleau you guys ok with this?

That's fine with me. Quite annoying when people suddenly get a CI failure and that's actually just lints due to a new Rust release (as we might not always follow up with linter fixes directly after a new Rust release).
As an alternative, we could pin the Rust version for the clippy check 🤔.


About Panoptic Occupancy Processing

Heatmap and occ_semantic are not obtained from the same branch, the number of instance centers obtained by instance regression maybe different from the number of instances actually existing in occ_semantic, which may cause these problems:

There is not a distance threshold limit when looking for the nearest instance center point. If a very far center point is found, under-segmentation will occur, and the instance ID of multiple instances will be the same
If the heatmap head dosen't perform well, there will be many categories in the field of the same location which can't be filtered by maxpooling, then over-segmentation will occur, and multiple instance IDs will appear for the same instance

I don't know whether these issues will affect the final panoptic occupancy results...

Thanks for your suggestions.
Heatmap and occ_semantic obtained from the same branch may alleviate the above 2 issues and promote the performance.


Adding commit-msg which prepend branch name for SWS-XXX branches

This git hook prepend a branch name for each commit for SWS-XXX branches. It is really useful when you name your branches as your JIRAs. Forget to add the JIRA name to each commit manually.
I find this useful for me, but I don't know if it something we want to add to the repo.

indeed not everyone names local branches with SWS (I personally never did that in any project), but this is up to the majority who writes most of the code here to decide (which I'm not ;))

I think this is optional, as the other hook is. I think this is a nice to
have stuff.
Perhaps it would be better to have a gist and share it with team :)
On Tue, Mar 13, 2018 at 1:09 PM, abonas<EMAIL_ADDRESS>wrote:

indeed not everyone names local branches with SWS (I personally never did
that in any project), but this is up to the majority who writes most of the
code here to decide (which I'm not ;))
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kiali/swscore/pull/105#issuecomment-372643704, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAldtn4AWpcUulMbnE2Tfm0DXtcefB8xks5td7bmgaJpZM4SokLM
.

--
Xavier Canal i Masjuan

-1 I don't like this. my branch names are sometimes not even useful to anyone but me.


Adding source and submitted_by fields to privacy request

Closes PROD-1809 and PROD-1788
❗Contains migration to add new columns to the consentrequest and privacyrequest tables
Description Of Changes
Updating privacy requests to include an optional source field. The options are currently restricted to the following:

Privacy Center - The most common source, for requests sent from the Privacy Center
Request Manager - For request submitted via the Request manager page in the Admin UI (plus only)
Consent Webhook - For requests created as part of the consent webhook flow for bidirectional consent (plus only)

This is a plus feature so I tried to draw the line in a reasonable way that wouldn't add to much scope. For example, I decided against creating overrides for the /consent and /privacy-request endpoints in plus that accept the source value in the request.
Code Changes

[ ] Updated requests from the Privacy Center to have a source of Privacy Center
[ ] Updated request from the Request manager page to have a source of Request Manager and to store the submitting user ID under the new privacy request column, submitted_by
[ ] Updated the Admin UI to show the source column in the privacy request table and privacy request detail page if plus is enabled

Steps to Confirm

[ ] Start fidesplus
[ ] Submit a review from the Privacy Center and from the Request manager in the Admin UI
[ ] Verify the two requests show the source in the Privacy request table and the privacy request details

Pre-Merge Checklist

[ ] All CI Pipelines Succeeded
[ ] Issue Requirements are Met
[ ] Update CHANGELOG.md
If there are any database migrations:

[ ] Ensure that your downrev is up to date with the latest revision on main
[ ] Ensure that your downgrade() migration is correct and works

[ ] If a downgrade migration is not possible for this change, please call this out in the PR description!

Starting review...


User Level Attributes

Adding a setting to have user level attributes.
This would be a setting when configuring the attribute to switch it to user level.
When at user level each attributes section will have a subsection utilizing the user login name to store values instead of storing them in the base.  Both the reading and writing of the attributes will interface with this and grab the values from an individual user.

two function used to set Attributes:
track.setAttribute(name, value)
track.setFeatureAttribute(frameRef.value, name, value)
These need to be modified to set using the userId if they are user attributes.


fixing footer for cocktail.html

was able to fix footer for all html by adding the following to CSS:
body {
display: flex;
min-height: 100vh;
flex-direction: column;
}
main {
flex: 1 0 auto;
}


Left View of Binary Tree | C++

i will add the implementation for left/right view of a binary tree.

Make a folder here named Left/Right of Binary Tree