Cannot get the plugin to work (Despite positive checkhealth) NixOS 24.05 (flake included to test)

:checkhealth asciidoc-preview
==============================================================================
asciidoc-preview: require("asciidoc-preview.health").check()
nvim-asciidoc-preview ~

OK macOS (Linux) supported
OK node installed
OK npm installed
OK curl installed

Asciidoctor (optional) ~

The following warnings or errors can be ignored
if Asciidoctor.js (converter = 'js') is used.
WARNING asciidoctor not installed
OK ruby installed
WARNING asciidoctor gem not installed
WARNING asciidoctor-diagram gem not installed

(I cannot find the file  ~/.local/state/nvim/nvim-asciidoc-preview-server.log)

Flake for tests:
REQUIRED:

nix

With flakes enabled
nix run github:jirafey/nvim-flake
if you have git cloned the repo -> cd to the repo and  nix run
Legacy (may seem like it stalls)
nix-shell -p '(import (builtins.fetchTarball "https://github.com/jirafey/nvim-flake/archive/master.tar.gz")).packages.${builtins.currentSystem}.default' --run nvim
If you need the link: https://github.com/jirafey/nvim-flake
Nvim version:

@EdenEast maybe you can help here since I see you're inactive here for quite some time but you seem to use NixOS

was able to do this, thanks to  @Gerg-L
nix run . -- basic-example.adoc

however :AsciiDocPreview :AsciiDocPreviewOpen does not work
:AsciiDocPreview just doesn't throw and error but just does nothing

https://github.com/user-attachments/assets/b90f3dd4-524a-4444-b298-6de55d945ea9

Okay, I'll take a look

It seems as if the preview server cannot be started, which is why the page cannot be reached in the web browser and no log file can be written.
Does the directory ~/.local/state/nvim/ exist?
The plugin may have problems finding the correct paths in your environment.

Can you please show me the following results?
Open an AsciiDoc file in nvim and execute the following commands:

lua print(vim.g.tigion_asciidocPreview_rootDir) (this shows the plugin path)
lua print(vim.fn.stdpath('log')) (this shows the log and cache path of nvim)
lua print(vim.fn.stdpath('cache'))

Open the Preview with :AsciidocPreview, wait for the webbrowser and run the following command in the terminal:

ps -ax | grep -v grep | grep nvim-asciidoc-preview (this shows, if the preview server is running)

[!WARNING]
Attention, the user name is displayed. So perhaps anonymize this information first.

It seems as if the preview server cannot be started, which is why the page cannot be reached in the web browser and no log file can be written.
Does the directory ~/.local/state/nvim/ exist? The plugin may have problems finding the correct paths in your environment.

I did not have ~/.local/state/nvim/ before but I installed kickstart-nix.nvim so it probably created that.
I will try using the flake i was using before then. I'll try to provide that later this day.

Can you please show me the following results?
Open an AsciiDoc file in nvim and execute the following commands:
* `lua print(vim.g.tigion_asciidocPreview_rootDir)` (this shows the plugin path)

Output: /nix/store/8hnhmgimylvbfxlrvxalkn0qf4y82hqr-source

* `lua print(vim.fn.stdpath('log'))` (this shows the log and cache path of nvim)

Output: /home/user/.local/state/gerg

* `lua print(vim.fn.stdpath('cache'))`

Output: /home/user/.local/state/gerg
Open the Preview with :AsciidocPreview, wait for the webbrowser and run the following command in the terminal:
E492: Not an editor command: AsciidocPreview
* ps -ax | grep -v grep | grep nvim-asciidoc-preview (this shows, if the preview server is running)

Warning
Attention, the user name is displayed. So perhaps anonymize this information first.

if this is confusing keep in mind this:

username = user
hostname = hostname

The command is :AsciiDocPreview sorry for the typo.

The command is :AsciiDocPreview sorry for the typo.

The :AsciiDocPreview, :AsciiDocPreviewNotify, :AsciiDocPreviewOpen, :AsciiDocPreviewStop output nothing, just sit there seems to lag nvim a bit and i need to click ESC a few times, or wait, ive made a bash script with your proposed ps -ax | grep -v grep | grep nvim-asciidoc-preview
so it watches it every 0.1s but no command resulted in any output rather than the expected no results, this may be due to my lack of knowledge of NixOS, grep, ps, and anything in between so your command may work on any linux but not on NixOS.
the shebang is unique for NixOS, the output was just "Not running."
#!/usr/bin/env bash
while true; do
  ps -ax | grep -v grep | grep nvim-asciidoc-preview > /dev/null && echo "Running..." || echo "Not running."
  sleep 0.1 # Check every 0.1 seconds
done

The server for the preview is not started, therefore the commands do not work and no log file is written. I am not yet sure what the problem is.
Can you try the following:

cd /nix/store/8hnhmgimylvbfxlrvxalkn0qf4y82hqr-source (I hope this is the correct path to the plugin)
server/scripts/start.sh --port 11235 (starts the preview server)
open http://localhost:11235/ in the web browser and check if an output is coming
curl -s -X POST http://localhost:11235/api/actions/stop (stops the preview server)

Does the file server/logs/nvim-asciidoc-preview-server.log in /nix/store/8hnhmgimylvbfxlrvxalkn0qf4y82hqr-source exist?
What is the content of the log file?

The server for the preview is not started, therefore the commands do not work and no log file is written. I am not yet sure what the problem is.
Can you try the following:
1. `cd /nix/store/8hnhmgimylvbfxlrvxalkn0qf4y82hqr-source` (I hope this is the correct path to the plugin)

2. `server/scripts/start.sh --port 11235` (starts the preview server)

3. open `http://localhost:11235/` in the web browser and check if an output is coming

4. `curl -s -X POST http://localhost:11235/api/actions/stop` (stops the preview server)

Does the file server/logs/nvim-asciidoc-preview-server.log in /nix/store/8hnhmgimylvbfxlrvxalkn0qf4y82hqr-source exist?
What is the content of the log file?

I'll try to get someone that is more informed in NixOS to help me with this: for your information here is the content of your commands
$ cd /nix/store/8hnhmgimylvbfxlrvxalkn0qf4y82hqr-source

[user@hostname:/nix/store/8hnhmgimylvbfxlrvxalkn0qf4y82hqr-source]$ server/scripts/start.sh --port 11235
Log directory '' does not exist. Use default: 'logs/'
mkdir: cannot create directory ‘logs’: Read-only file system
server/scripts/start.sh: line 38: logs/nvim-asciidoc-preview-server.log: No such file or directory
server/scripts/start.sh: line 21: logs/nvim-asciidoc-preview-server.log: No such file or directory
server/scripts/start.sh: line 40: logs/nvim-asciidoc-preview-server.log: No such file or directory
server/scripts/start.sh: line 21: logs/nvim-asciidoc-preview-server.log: No such file or directory
server/scripts/start.sh: line 21: logs/nvim-asciidoc-preview-server.log: No such file or directory
server/scripts/start.sh: line 21: logs/nvim-asciidoc-preview-server.log: No such file or directory
server/scripts/start.sh: line 21: logs/nvim-asciidoc-preview-server.log: No such file or directory
server/scripts/start.sh: line 21: logs/nvim-asciidoc-preview-server.log: No such file or directory
server/scripts/start.sh: line 71: logs/nvim-asciidoc-preview-server.log: No such file or directory
server/scripts/start.sh: line 21: logs/nvim-asciidoc-preview-server.log: No such file or directory
server/scripts/start.sh: line 73: logs/nvim-asciidoc-preview-server.log: No such file or directory
server/scripts/start.sh: line 74: logs/nvim-asciidoc-preview-server.log: No such file or directory

[user@hostname:/nix/store/8hnhmgimylvbfxlrvxalkn0qf4y82hqr-source]$ sudo server/scripts/start.sh --port 11235
[sudo] password for user:
Log directory '' does not exist. Use default: 'logs/'
mkdir: cannot create directory ‘logs’: Read-only file system
server/scripts/start.sh: line 38: logs/nvim-asciidoc-preview-server.log: No such file or directory
server/scripts/start.sh: line 21: logs/nvim-asciidoc-preview-server.log: No such file or directory
server/scripts/start.sh: line 40: logs/nvim-asciidoc-preview-server.log: No such file or directory
server/scripts/start.sh: line 21: logs/nvim-asciidoc-preview-server.log: No such file or directory
server/scripts/start.sh: line 21: logs/nvim-asciidoc-preview-server.log: No such file or directory
server/scripts/start.sh: line 21: logs/nvim-asciidoc-preview-server.log: No such file or directory
server/scripts/start.sh: line 21: logs/nvim-asciidoc-preview-server.log: No such file or directory
server/scripts/start.sh: line 21: logs/nvim-asciidoc-preview-server.log: No such file or directory
server/scripts/start.sh: line 71: logs/nvim-asciidoc-preview-server.log: No such file or directory
server/scripts/start.sh: line 21: logs/nvim-asciidoc-preview-server.log: No such file or directory
server/scripts/start.sh: line 73: logs/nvim-asciidoc-preview-server.log: No such file or directory
server/scripts/start.sh: line 74: logs/nvim-asciidoc-preview-server.log: No such file or directory

[user@hostname:/nix/store/8hnhmgimylvbfxlrvxalkn0qf4y82hqr-source]$ ls
LICENSE  lua  plugin  README.md  server

[user@hostname:/nix/store/8hnhmgimylvbfxlrvxalkn0qf4y82hqr-source]$ pwd
/nix/store/8hnhmgimylvbfxlrvxalkn0qf4y82hqr-source

Please be aware that the last quoted sentence refers to the log file used during the bash script, not to the server as a whole.

Okay, the steps were used to start the server manually for testing with a fallback log directory to this directory. Since it is a Read-only file system, the log file cannot be written.
Normally it would write the logfile from the plugin to lua print(vim.fn.stdpath('log')).
The path to the log file can be specified with --logdir /path/to/logdir/ to a writable directory.

server/scripts/start.sh --port 11235 --logdir /path/to/logdir/

I think in NixOS there is a special handling needed.

I found some time to experiment on my own.
--------------------------------------------------------
2024-08-07 21:23:50 [INFO]: Starting script...
--------------------------------------------------------
2024-08-07 21:23:50 [INFO]: Log file: /home/nobbz/.local/state/gerg/nvim-asciidoc-preview-server.log
2024-08-07 21:23:50 [OKAY]: 'npm' found
2024-08-07 21:23:50 [OKAY]: 'node' found
2024-08-07 21:23:50 [OKAY]: '/nix/store/8hnhmgimylvbfxlrvxalkn0qf4y82hqr-source/server/server.js' found
2024-08-07 21:23:51 [INFO]: Arguments: --logdir /home/nobbz/.local/state/gerg --cachedir /home/nobbz/.cache/gerg --port 11235
--------------------------------------------------------
2024-08-07 21:23:51 [INFO]: Starting node server...
--------------------------------------------------------
node:internal/modules/cjs/loader:1148
  throw err;
  ^

Error: Cannot find module 'express'
Require stack:
- /nix/store/8hnhmgimylvbfxlrvxalkn0qf4y82hqr-source/server/server.js
    at Module._resolveFilename (node:internal/modules/cjs/loader:1145:15)
    at Module._load (node:internal/modules/cjs/loader:986:27)
    at Module.require (node:internal/modules/cjs/loader:1233:19)
    at require (node:internal/modules/helpers:179:18)
    at Object.<anonymous> (/nix/store/8hnhmgimylvbfxlrvxalkn0qf4y82hqr-source/server/server.js:4:17)
    at Module._compile (node:internal/modules/cjs/loader:1358:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1416:10)
    at Module.load (node:internal/modules/cjs/loader:1208:32)
    at Module._load (node:internal/modules/cjs/loader:1024:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:174:12) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/nix/store/8hnhmgimylvbfxlrvxalkn0qf4y82hqr-source/server/server.js'
  ]
}

Node.js v20.14.0

This is basically what I expected, required dependencies are not available to start the server. I am sadly not sure how to tackle that. I am not using neovim for long enough myself to know all the edges of the ecosystem within nixpkgs. Also I know that this particular config uses non-standard build helpers, which are quite young.
I think a good start would be, if there was a message issued by the plugin that the server couldn't be started.
To fix the underlying problem for this particular configuration, I think only @gerg-l can help, noone else really knows their tooling well enough ;)

I think the node part of this plugin needs to be properly packaged

If the plugin directory is not writable, the required packages cannot be installed. These are then missing for starting.
The installation is initiated via the Lazy.nvim Config of the plugin.
I will add a check to the plugin or the :checkhealth.

I have pushed a new version. Now an error message is displayed if the plugin directory is not writable.

I've gotten it to work
pkgs.buildNpmPackage {
            name = "nvim-asciidoc";
            src = pkgs.fetchFromGitHub {
              owner = "tigion";
              repo = "nvim-asciidoc-preview";
              rev = "06b13166ec0aaa5ae59531bc5c38017171323947";
              hash = "sha256-6v5DsgCDbpAOHFaNk1i/j5KzO0NFCkIwDpT0Dezceao=";
            };
            postPatch = "pushd server";
            npmDepsHash = "sha256-HGEuBpMkupoLMkqrNo1tw989dVzrIiZf5OJCMo4FOgU=";
            dontNpmBuild = true;
            installPhase = ''
              runHook preInstall

              popd
              cp -r . $out/

              runHook postInstall
            '';
          };
          ```

I've gotten it to work
pkgs.buildNpmPackage {
  name = "nvim-asciidoc";
  src = pkgs.fetchFromGitHub {
    owner = "tigion";
    repo = "nvim-asciidoc-preview";
    rev = "06b13166ec0aaa5ae59531bc5c38017171323947";
    hash = "sha256-6v5DsgCDbpAOHFaNk1i/j5KzO0NFCkIwDpT0Dezceao=";
  };
  postPatch = ''
    pushd server
  '';
  npmDepsHash = "sha256-HGEuBpMkupoLMkqrNo1tw989dVzrIiZf5OJCMo4FOgU=";
  dontNpmBuild = true;
  installPhase = ''
    runHook preInstall

    popd
    cp -r . $out/

    runHook postInstall
  '';
}

how can I apply this change?

Use that snippet instead of adding the plugin from npins, i can help you elsewhere, this can probably get closed

with this change:
https://github.com/jirafey/nvim-flake/blob/3a6501e0e97039826e4dbad56a71a985929b364d/flake.nix#L113
plugins =
              [
                (pkgs.buildNpmPackage {
                  name = "nvim-asciidoc";
                  src = pkgs.fetchFromGitHub {
                  owner = "tigion";
                  repo = "nvim-asciidoc-preview";
                  rev = "06b13166ec0aaa5ae59531bc5c38017171323947";
                  hash = "sha256-6v5DsgCDbpAOHFaNk1i/j5KzO0NFCkIwDpT0Dezceao=";
                  };
                  postPatch = ''
                    pushd server
                  '';
                  npmDepsHash = "sha256-HGEuBpMkupoLMkqrNo1tw989dVzrIiZf5OJCMo4FOgU=";
                  dontNpmBuild = true;
                  installPhase = ''
                    runHook preInstall
                    popd
                    cp -r . $out/
                  runHook postInstall
                  '';
                })
                ```

The preview properly opens in browser, `:AsciiDocPreview` and `:AsciiDocPreviewOpen` work.
`:AsciiDocPreviewNotify` or `:AsciiDocPreviewStop` are just overwritten by  `:AsciiDocPreviewOpen`. So at least the needed functionality is there, the fix probably needs some extra care.

The normal behavior is that the preview is started with AsciiDocPreview and the preview exits when leaving the Neovim buffer (with an open AsciiDoc file).
The commands AsciiDocPreviewOpen, AsciiDocPreviewNotify or AsciiDocPreviewStop are covered by normal use. They simply offer the option of triggering things separately.

The normal behavior is that the preview is started with AsciiDocPreview (starts the preview node server and opens the the preview url in the web browser) and the preview exits (stops the preview node server)when leaving the Neovim buffer (with an open AsciiDoc file).
The commands AsciiDocPreviewOpen (only opens the the preview url in the web browser), AsciiDocPreviewNotify (tells the preview to refresh) or AsciiDocPreviewStop (stops the preview node server) are covered by normal use. They simply offer the option of triggering things separately.

so it stops when you exit the file.
But stop does not stop the preview node server
And I'm not sure about the notify one. I'll record a video later today, maybe it will be easier for you to understand, what is going on.

You are right. The preview server is currently terminated when vim is closed (Event: VimLeavePre).

You are right. The preview server is currently terminated when vim is closed (Event: VimLeavePre). :AsciiDocPreviewStop stops the preview server manually.

the issue is that it was not being closed when :AsciiDocPreviewStop was used or any other option was just running :AsciiDocPreviewOpen (open the server node preview in new tab)

You are too fast. I edited my text. Can you please open a new issue for this problem.

 I edited my text. Can you please open a new issue for this problem.


Retire legacy indexing code

This PR retires the previous indexing code base out of this repository and provides a migration document for existing users of the deprecated code.  Going forward any users of the legacy indexing code will need to use the new query code that replaces the legacy implementation along with the migration document to update their implementations.

This looks good. I think we can merge as is, +1.


Fix: vmix preloading

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Changes in how vmix-preloading works

What is the current behavior? (You can also link to an open issue here)

The vmix-preloading of media onto inputs is done on a separate command-queue (executed on currentTime) but generated from the stored state's (tied to resolveTime).
This can cause issues because the sending of those commands aren't done in sync with the state-tracker, so multiple commands for the same thing might be generated. (I excperienced this issue in PR #270 ).

What is the new behavior (if this is a feature change)?

I moved away the handling of pre-loading command into a separate class that handles those commands only and tracks the actual state of those. So these commands are now sent asynchronously from the main command-queue, but that should be OK since we also tracks a separate state for them.

Other information:

Codecov Report
Patch coverage: 1.69% and project coverage change: -0.17% :warning:

Comparison is base (7ac1d7e) 37.91% compared to head (39d3eba) 37.74%.

Additional details and impacted files
@@              Coverage Diff              @@
##           release51     #280      +/-   ##
=============================================
- Coverage      37.91%   37.74%   -0.17%
=============================================
  Files             99       99
  Lines           9963    10008      +45
  Branches        2466     2475       +9
=============================================
+ Hits            3777     3778       +1
- Misses          5625     5663      +38
- Partials         561      567       +6

Files Changed
Coverage Δ

...line-state-resolver/src/integrations/vmix/index.ts
2.94% <1.69%> (-0.07%)
:arrow_down:

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

@alvancamp I was hoping you could give some insight into that actually, since you've been working with the vmix integration a lot


Mock database service for unit testing

Many of our unit tests which need to mock a database operation actually use couch and require a deployment of the couchdb playbook. Instead, we should have a mock library to emulate the db contract and eschew the actual datastore service.
As additional SPIs are added for couchbase, mongo, etc, having this canonical library will simplify how we test the other implementations.
FYI @chetanmeh

This task is now done with #3517.


Tab icons render as white squares

Running patchmatrix-v0.24.0 (though the issue is also present with a hand-built version from the latest git commit 79cac7) on amd64 Debian Testing (using X and Pipewire) the icons for the Audio, Midi, CV and OSC tabs all render as white squares:

everything else seems to work fine (aside from the segfault i mentioned in #23 ) and the only console output is complaints from pipewire-jack. i wasn't sure how related this was to the segfault issue in #23 so i figured it deserved its own issue.

You likely have not installed the (hand-built) application and the resources are not found.

that sounds very likely, though it's worth noting that this is true of the prebuilt binaries as well (run from their own directory where i unpacked them somewhere in /tmp). looking at output from strace it seems like the only place it actually looks for the icons is /builds/OpenMusicKontrollers/patchmatrix/patchmatrix-0.24.0/x86_64-linux-gnu-bullseye/share/patchmatrix/audio.png which seems a little impractical as installation locations go.

thanks for reporting
fixed in bd35f4ba724a3483dda0677edcf7dc9e6c7759a9


SwinUNETR on BTCV with unused CLI arguments

Describe the bug
The training script for SwinUNETR on BTCV includes CLI arguments for smoothing coefficients in the Dice loss. However, those coefficients are never used. Were they used for training the original models reported in the publication?
https://github.com/Project-MONAI/research-contributions/blob/46279a9601852a1e5f3a2581fa32be403f57885e/SwinUNETR/BTCV/main.py#L78-L79
https://github.com/Project-MONAI/research-contributions/blob/46279a9601852a1e5f3a2581fa32be403f57885e/SwinUNETR/BTCV/main.py#L144-L146
@ahatamiz

Hi @razorx89
Thanks for the comment. Those coefficients particularly were intended to be used for squared Dice loss. However, we did not use it for training the models whose benchmarks are reported in the papers. I have submitted a PR with the option of using squared Dice loss, in case you would like to give it a try.
Best,

Thanks.


Diversity estimates not plausible

Hi,
When computing Shannon and Inverse Simpson diversities for my samples from the divnet-rs output, samples that have a very low observed richness have shannon diversities of 9 and higher - how can this be? This is biologically not logical if i only have say 5 species in  that sample and such a high shannon index and inverse simspn numbers of >1000. Do you have any suggestion on how to deal with this?
Alice

Hi Alice, thanks for your report.
It's hard for me to say what's going on without seeing how you ran all the commands and your input data.
Would you be able to share your input data, the exact command line command you ran, and the R code in which you calculated the diversity measures? If so I can try to reproduce the issue.
Thanks!

I see that some members of the Willis lab have responded to this issue on the DivNet R page (https://github.com/adw96/DivNet/issues/126).
I'm closing the issue here to avoid duplicated work between the two groups.


7TV and BTTV live emote updates are not proxied

Checklist

[X] I'm reporting a problem with Chatterino
[X] I've verified that I'm running the most recent nightly build or stable release
[X] I've looked for my problem on the wiki
[X] I've searched the issues and pull requests for similar looking reports

Describe your issue
When using socks proxy that is reachable, starting the app, everything loads and works, when you make said proxy unreachable (e.g. disable VPN connection), chatterino disconnects (as it should), but 7TV and BTTV emote updates still get received.

I'm not familiar with websockets (which seems to be the case for this usage), but shouldnt they still be proxied?
(When using socks proxy and starting the app with connection to proxy disabled, obviously nothing shows up, no "connected message" nothing loads, and emote live updates dont show up (but I could not confirm whether they are transmitted or not).)
Screenshots
No response
OS and Chatterino Version
Chatterino Nightly 2.5.1 (commit c3b84cb4) built on 2024-05-11 with Qt 6.5.0, MSVC 193833135 Running on Windows 11 Version 23H2, kernel: 10.0.22631

This is a known limitation, and is documented on the wiki
https://wiki.chatterino.com/Environment Variables/#chatterino2_proxy_url

It's a pretty heavy lift atm, so it won't be fixed specifically to fix this, no. You can use HTTP proxy to work around it.


It's review time!

Why don't you tell my Managers how you think I have done over the last 6 months or so ...
When providing feedback consider all three of the following ways of having impact on the community, product, and project results:

Key individual accomplishments that contributed to community, product, and project results
Results that build on the work, ideas, or effort of others
Contributions to the success of others
What have I done well?
What have I done poorly?
Do I share enough? accomplish enough? Am I respectful?, disrespectful? Am I open enough, do you feel involved?
What's my code like?
Please provide specific examples:

Please email @jaredpar with your feedback.
Thanks
Kevin

@jaredpar
OK; I'll bite.
I'm creator of #513, a bit of a rambling pull request, but one that performs a valid and valuable result (IMnsHO!) (also #549, #577 & #594 - they were basically spin offs from #513, and maintainter of FSharp.Quotations.Evaluator)
Anyway, my gripe relates to #513 where there was lack of communication after @latkin left. I would of appreciated (and still would?!?!) some updated timeframe as to when (if!?!?!?) this work is going to be merged.
It definitely deterred me from spending time working of further improvements (although, to be fair, my 2 daughters also deter me from work as well - probably more so!)
I don't mean this to cause grief to @KevinRansom, as I can see he has been busy getting the coreclr support across the line, but just me being selfish banging on for what's most important to me!

@manofstick i think we should mail @jaredpar directly ( the mail is the profile )

closing old discussion :)


Follow up on dependency verification update in release notes

Proposes changes following up on the comments made in #18863

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

OK, I've already triggered a build for you.


SMB timeout

Hi,
i'm getting this error on HA using this plugin:
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/00-banner.sh
-----------------------------------------------------------
 Add-on: Samba Backup
 Create backups and store them on a Samba share
-----------------------------------------------------------
 Add-on version: 5.2.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 9.3  (amd64 / qemux86-64)
 Home Assistant Core: 2022.11.4
 Home Assistant Supervisor: 2022.11.2
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
cont-init: info: /etc/cont-init.d/00-banner.sh exited 0
cont-init: info: running /etc/cont-init.d/01-log-level.sh
Log level is set to DEBUG
cont-init: info: /etc/cont-init.d/01-log-level.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[22-11-25 13:07:51] INFO: ---------------------------------------------------
[22-11-25 13:07:51] INFO: Host/Share: 192.168.xx.xx/Temp_restore
[22-11-25 13:07:51] INFO: Target directory: HA_Backup
[22-11-25 13:07:51] INFO: Keep local/remote: 7/14
[22-11-25 13:07:51] INFO: Trigger time: 11:37
[22-11-25 13:07:51] INFO: Trigger days: Mon Tue Wed Thu Fri Sat Sun
[22-11-25 13:07:51] INFO: ---------------------------------------------------
[22-11-25 13:07:51] DEBUG: Backups local/remote: 0/0
[22-11-25 13:07:51] DEBUG: Total backups succeeded/failed: 0/0
[22-11-25 13:07:51] DEBUG: Last backup: never
[22-11-25 13:07:57] WARNING: do_connect: Connection to 192.168.xx.xx failed (Error NT_STATUS_IO_TIMEOUT)
[22-11-25 13:07:57] FATAL: Cannot access share. Unknown reason.
[22-11-25 13:07:57] DEBUG: Posting sensor data to API at /core/api/states/sensor.samba_backup
[22-11-25 13:07:57] DEBUG: API Status: 200
[22-11-25 13:07:57] DEBUG: API Response: {"entity_id":"sensor.samba_backup","state":"FAILED","attributes":{"friendly_name":"Samba Backup","backups_local":"0","backups_remote":"0","total_backups_succeeded":"0","total_backups_failed":"0","last_backup":"never"},"last_changed":"2022-11-25T12:05:03.254218+00:00","last_updated":"2022-11-25T12:05:03.254218+00:00","context":{"id":"01GJQATJMPDJ8YVCNDKNCCH86J","parent_id":null,"user_id":"f9392b5e809040cf89076526c9e48d01"}}

looking at the error
WARNING: do_connect: Connection to 192.168.xx.xx failed (Error NT_STATUS_IO_TIMEOUT)
and google it, it seems to be something with SMB versions:
his is most likely because the box your trying to do smbclient uses an outdated (and insecure) version of SMB such as SMBv1.
You'll need to edit the smb.conf in your machine and specify the client min protocol into CORE. You'll also need to specify the client max protocol into SMB3.

More information here: https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html

Steps: On your host machine:

sudo nano /etc/samba/smb.conf
Add the following settings under Global Settings:
client min protocol = CORE
client max protocol = SMB3
Write (Ctrl + O) and Exit (Ctrl + X) nano text editor.
Retry smbclient

see here
as my nas is on SMBv3 i dont want to downgrade it.

Actually it's the other way around. This most likely means that your NAS only supports an outdated SMB version, so this addon refuses to connect. You could take a look at the compatibility_mode option --> https://github.com/thomasmauerer/hassio-addons/blob/master/samba-backup/DOCS.md#option-compatibility_mode


[bug]: -p, --path option is not working

Describe the bug
path option is not working.
Affected component/components
Probably ALL
How to reproduce
Please try following code to reproduce this bug.
npx shadcn@latest add [some-component] -p [some-path]

Codesandbox/StackBlitz link
No response
Logs
none

System Info
npx -v => 10.8.2
npx shadcn@latest -v => 2.0.1

Before submitting

[X] I've made research efforts and searched the documentation
[X] I've searched for existing issues

I am facing the same issue by trying to add a dialog component in its own folder using pnpm:
pnpm dlx shadcn@latest add dialog --path src/dialog

This worked with the previous version, and it does not work anymore since the update.

Oh. component.json resolve this issue. (--path exists with mistake...? 🤔 )
like following.
I'll close this issue. thanks.
{
  "$schema": "https://ui.shadcn.com/schema.json",
  "style": "new-york",
  "rsc": true,
  "tsx": true,
  "tailwind": {
    "config": "tailwind.config.ts",
    "css": "src/app/globals.css",
    "baseColor": "zinc",
    "cssVariables": true,
    "prefix": ""
  },
  "aliases": {
    "components": "@/_lib/shadcn/components",
    "utils": "@/_lib/shadcn/utils",
    "ui": "@/_lib/shadcn/components/ui",
    "lib": "@/_lib/shadcn",
    "hooks": "@/_lib/shadcn/hooks"
  }
}


Increase the quantity of operation in GitHub Action stale

There are too many stale issues/pull requests, the default operation quantity in a single run is 30, which is too small.
related link: https://github.com/actions/stale#operations-per-run

do we have any available tools to do with it ?


Accelerate logging print nothing

System Info
- `Accelerate` version: 0.30.1
- Platform: Linux-5.4.0-132-generic-x86_64-with-glibc2.17
- `accelerate` bash location: /miniconda3/envs/test/bin/accelerate
- Python version: 3.8.18
- Numpy version: 1.24.3
- PyTorch version (GPU?): 1.13.1 (True)
- PyTorch XPU available: False
- PyTorch NPU available: False
- PyTorch MLU available: False
- System RAM: 330.26 GB
- GPU type: NVIDIA GeForce RTX 3090
- `Accelerate` default config:
	Not found

Information

[X] The official example scripts
[ ] My own modified scripts

Tasks

[X] One of the scripts in the examples/ folder of Accelerate or an officially supported no_trainer script in the examples folder of the transformers repo (such as run_no_trainer_glue.py)
[ ] My own task or dataset (give details below)

Reproduction
from accelerate.logging import get_logger
from accelerate import Accelerator

logger = get_logger(__name__)

accelerator = Accelerator()
logger.info("My log", main_process_only=False)
logger.debug("My log", main_process_only=True)

logger = get_logger(__name__, log_level="DEBUG")
logger.info("My log")
logger.debug("My second log")

array = ["a", "b", "c", "d"]
letter_at_rank = array[accelerator.process_index]
logger.info(letter_at_rank, in_order=True)

Expected behavior
logging My log and other

The issue is that there is no handler configured for the logger. After adding it, the outputs are shown:
import logging
from accelerate.logging import get_logger
from accelerate import Accelerator

accelerator = Accelerator()
logger = get_logger(__name__, log_level="DEBUG")
handler = logging.StreamHandler()
logger.logger.addHandler(handler)
logger.info("My log")
logger.debug("My second log")

array = ["a", "b", "c", "d"]
letter_at_rank = array[accelerator.process_index]
logger.info(letter_at_rank, in_order=True)

The reason why we don't need to add a handler when using logger.warning or higher is that Python has a last resort handler for this log levels.

The issue is that there is no handler configured for the logger. After adding it, the outputs are shown:
import logging
from accelerate.logging import get_logger
from accelerate import Accelerator

accelerator = Accelerator()
logger = get_logger(__name__, log_level="DEBUG")
handler = logging.StreamHandler()
logger.logger.addHandler(handler)
logger.info("My log")
logger.debug("My second log")

array = ["a", "b", "c", "d"]
letter_at_rank = array[accelerator.process_index]
logger.info(letter_at_rank, in_order=True)

The reason why we don't need to add a handler when using logger.warning or higher is that Python has a last resort handler for this log levels.

thank you, i got the outputs,but it's out-of-order, even i set in_order=True

What exactly did you run to get this error? What is your setup?

What exactly did you run to get this error? What is your setup?

i use the example in https://huggingface.co/docs/accelerate/v0.30.1/en/package_reference/logging, and add streamhandler,
    accelerator = Accelerator()

    logger = get_logger(__name__, log_level="DEBUG")
    handler = logging.StreamHandler()
    logger.logger.addHandler(handler)
    logger.info("My log")
    logger.debug("My second log")

    accelerator.wait_for_everyone()

    array = ["a", "b", "c", "d"]
    letter_at_rank = array[accelerator.process_index]
    logger.info(letter_at_rank, main_process_only=False, in_order=True)

the output is
My log
My second log
a
d
c
b

Indeed, I think in_order=True does not do what it is supposed to do or I misunderstand its meaning:
$ accelerate launch accelerate-2827.py
in order True
hello from rank 0
hello from rank 1
in order False
hello again from rank 0
hello again from rank 1
$ accelerate launch accelerate-2827.py
hello from rank 1
in order True
hello from rank 0
in order False
hello again from rank 0
hello again from rank 1
$ accelerate launch accelerate-2827.py
in order True
hello from rank 0
hello from rank 1
in order False
hello again from rank 1
hello again from rank 0
$ accelerate launch accelerate-2827.py
in order True
hello from rank 0
hello from rank 1
in order False
hello again from rank 0
hello again from rank 1
$ accelerate launch accelerate-2827.py
hello from rank 1
in order True
hello from rank 0
in order False
hello again from rank 1
hello again from rank 0
$ accelerate launch accelerate-2827.py
hello from rank 1
in order True
hello from rank 0
in order False
hello again from rank 1
hello again from rank 0

using
import logging
from accelerate.logging import get_logger
from accelerate import Accelerator

accelerator = Accelerator()
logger = get_logger(__name__, log_level="DEBUG")
handler = logging.StreamHandler()
logger.logger.addHandler(handler)
accelerator.print("in order True")
logger.info(f"hello from rank {accelerator.process_index}", in_order=True, main_process_only=False)
accelerator.wait_for_everyone()
accelerator.print("in order False")
logger.info(f"hello again from rank {accelerator.process_index}", in_order=False, main_process_only=False)

What exactly did you run to get this error? What is your setup?

any update?

What exactly did you run to get this error? What is your setup?

What exactly did you think about this? is this a bug?

Not stale.


Styling of loader/promise toast

Hello,
I'm trying to customize Toast colors, but also i want to use promise/loading toast.
          toastOptions={{
            classNames: {
              error: "bg-red-400",
              success: "text-green-400",
              warning: "text-yellow-400",
              info: "bg-blue-400",
              loader: "bg-blue-400",
            },
          }}

But styles for "loader" are not working, even if I apply unstyled: true then promise/loading toast ends with reset styling.

So you'd basically want a promise key?

I would like to customize loader and promise toast styles in toastOptions.

@Rjuks use loading instead of loader. (#255)

Like @angelocala94 mentioned!

tried loader & loading, none worked


How to write to file?

I asked this on stackoverflow, but then I realized you probably know best. If you can help me out, it would be awesome. See the full question here: https://stackoverflow.com/questions/78762369/set-properties-of-an-exe-using-golang

I am not sure I understood what you're aiming for.
If you modified the peFile.Anomalies, and you reparse the file, ofc the value will be gone.
Why not just keep a map that holds filepath -> pefile struct ?

@LordNoteworthy I don't understand. I want to change the file properties. Let's use peFile.Anomalies as an example property. I want to

change that property (as easy as peFile.Anomalies = []string{"new stuff"})
write that change to the actual file

That last part is the part I don't know how to do. So the goal is to change the file such that if you run pe.New() and pe.Parse() again, it should hold the value the next time you rerun your Go script (or check the file properties a different way). I know it's possible for a user to open a file's properties and change them manually.
The reason a map wouldn't be sufficient is because I need the file to contain the information even after the script has been closed, which means, of course, that all memory has been cleared.

I see, this is not possible, simply because a PE parser is not supposed to do something like this.
Anomalies are extracted from a file because some PE fields have abnormal values, you can write an anomaly back to a PE file, it does not make sense.
There is many ways you can do what you want, simply keep track in a KV embedded database, the list of anomalies as value, and the filepath as key.


Fix nullability of getMap in LottieAnimationViewPropertyManager

We're making some changes in an upcoming react-native release which fix the nullability of some getters in ReadableNativeArray. This ensures that lottie-react-native will continue to build in the next RN release

Yes, it was already possible for getMap to return null values, but the type annotation was interface was incorrect, which we've now fixed.
I'm not sure what this error is about:

The local project doesn't define a 'packageManager' field. Corepack will now add one referencing

It's a yarn lockfile issue. For some reason, when it tries to install, the hash signature of the lockfile is not matching up. Ordinarily i would make a separate PR for fixing it, but it will take a while for me to find another person to approve it, so if you can, just run yarn in your patch please and i can approve and merge this


The cursor sometimes jumps

The cursor may jump during the animation
I think I can fix it by changing the flash to after drawing.

https://github.com/SSlime-s/afk-animation/commit/228ba147333a18dd1e9d3cafb964e1524d342834
https://github.com/SSlime-s/afk-animation/commit/0920930299e64781f5a6891af4faf23dfef2585a


Updated update_test_result

Updated -- update_test_result
put instead of post result so that new execution id is not created every time updating test result.

@nassauwinter @crapitea Please review request -- Updated -- update_test_result
put instead of post result so that new execution id is not created every time updating test result.

Hi @jay-2597! Thank you for your contribution.
The official method from Zephyr Scale Server API is POST. PUT is not supported/documented. So I suggest to leave update_test_result method as is.
Anyway, could you please add a new method for that endpoint? Name it like modify_test_result with explicit statement in its docstring that the method is not supported/documented in official documentation; it works and makes it possible to modify a test result.

@nassauwinter @crapitea ,
put is documented in documentation of zephyr scale server api can you follow the link as below endpoint:
https://support.smartbear.com/zephyr-scale-server/api-docs/v1/
/testrun/{testRunKey}/testcase/{testCaseKey}/testresult

@jay-2597,
My mistake. Here is a bug in update_test_result. Look at the create_test_result and update_test_result: both use post while update_test_result expected to use put. Would you modify your PR to fix that?


New Chart Type not rendering

Expected Behavior
I am trying to create a chart to the effect of the following image:
http://imgur.com/a/rk098
It is basically a scatter chart with some custom element coloring. I attempted to create a custom chart called "casting" that would create this. The way I did it is simply by using the existing controller.line.js from your GitHub, removing everywhere that it draws the line, and customizing the getPointBackgroundColor function to use a data field called "status". I realize I could just extend the line controller but I was interested in learning how to build a custom controller.
Current Behavior
The data points do not render on the chart, as seen in the codepen example below.
Possible Solution
I'm not sure...
Steps to Reproduce (for bugs)
https://codepen.io/anon/pen/YVWyXr
Context
I am trying to create a chart to the effect of the following image:
http://imgur.com/a/rk098
Environment

Chart.js version: 2.5.0
Browser name and version: Chrome 57.0.2987.133
Link to your project: https://codepen.io/anon/pen/YVWyXr

@arasfeld the issue is the clipArea call. In development since v2.5.0 we aliased chart.chart.ctx to chart.ctx which is why that line fails.
If you replace Chart.canvasHelpers.clipArea(chart.ctx, area); with Chart.canvasHelpers.clipArea(chart.chart.ctx, area); it should work fine


MD5 Error (The Content-MD5 you specified did not match what we received.)

I need to compile and upload my assets to a s3 bucket. But I got this error:
remote: -----> Running run_collectstatic
remote: -----> Collecting static files
remote: Post-processed 'assets/css/main.css' as 'assets/css/main.css'
remote: Post-processed 'assets/css/report.css' as 'assets/css/report.css'
remote: Traceback (most recent call last):
remote: boto.exception.S3ResponseError: S3ResponseError: 400 Bad Request
remote: <?xml version="1.0" encoding="UTF-8"?>
remote: <Error>BadDigest<Message>The Content-MD5 you specified did not match what we received.</Message><ExpectedDigest>oFCX4Uq8pIY5LUadGPlVMg==</ExpectedDigest><CalculatedDigest>ffV8cbpJ3i2fW5M1ry6wVQ==</CalculatedDigest><RequestId>E34D0F23055F53F7</RequestId><HostId>gHrb9XvVyyCt098gKGM86pG8BgXoJhol1q+clLFXRsABn3sj8Zkc8/LwwjR4BCkB</HostId></Error>

My settings:
DEFAULT_FILE_STORAGE = 'website.models.MediaRootS3BotoStorage'
STATICFILES_STORAGE = 'website.models.StaticRootS3BotoStorage'

STATICFILES_DIRS = (
    os.path.join(BASE_DIR, 'components', 'bower_components'),
)

PIPELINE_CSS_COMPRESSOR = 'pipeline.compressors.cssmin.CSSMinCompressor'
PIPELINE_CSSMIN_BINARY = '/usr/bin/env cssmin'
PIPELINE_CSSMIN_ARGUMENTS = ''

PIPELINE_JS_COMPRESSOR = 'pipeline.compressors.uglifyjs.UglifyJSCompressor'
PIPELINE_UGLIFYJS_BINARY = '/usr/bin/env uglifyjs'
PIPELINE_UGLIFYJS_ARGUMENTS = ''

PIPELINE_COMPILERS = (
  'pipeline.compilers.coffee.CoffeeScriptCompiler',
  'pipeline.compilers.less.LessCompiler',
)

STATICFILES_FINDERS = (
    'pipeline.finders.FileSystemFinder',
    'pipeline.finders.AppDirectoriesFinder',
    'pipeline.finders.PipelineFinder',
)

how can i fix this?

@danielgatis are you using Python 3?  I just found a very elusive bug in https://github.com/boto/boto that presents this way in py3 only.

yep! python 3. thanks for sharing.

@danielgatis and anyone else who runs into this problem, see this issue: https://github.com/boto/boto/issues/2868


Failure to run custom logger example since eb3599e

Hey,
Today I updated the dependencies of my local osquery plugin that makes use of osquery-go and can no longer start a custom logger. As soon as I try and Run() a NewExtensionManagerServer() instance, I get a panic as follows:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x12a016a]

goroutine 35 [running]:
github.com/xxxxt/vendor/github.com/kolide/osquery-go/gen/osquery.(*ExtensionManagerClient).RegisterExtension(0xc4201bc060, 0x150c400, 0xc4200be010, 0xc4201c2080, 0xc4201a8090, 0x1471de0, 0x1, 0xc4201c2080)
	/Users/xxxx/Documents/git/gopath/src/github.com/xxxxt/vendor/github.com/kolide/osquery-go/gen/osquery/osquery.go:1853 +0x8a
github.com/xxxxt/vendor/github.com/kolide/osquery-go.(*ExtensionManagerClient).RegisterExtension(0xc4201bc080, 0xc4201c2080, 0xc4201a8090, 0x0, 0x0, 0x0)
	/Users/xxxx/Documents/git/gopath/src/github.com/xxxxt/vendor/github.com/kolide/osquery-go/client.go:73 +0x5f
github.com/xxxxt/vendor/github.com/kolide/osquery-go.(*ExtensionManagerServer).Start.func1(0xc42001e080, 0xc4201d0f78, 0x0, 0x0)
	/Users/xxxx/Documents/git/gopath/src/github.com/xxxxt/vendor/github.com/kolide/osquery-go/server.go:143 +0xfe
github.com/xxxxt/vendor/github.com/kolide/osquery-go.(*ExtensionManagerServer).Start(0xc42001e080, 0x0, 0x0)
	/Users/xxxx/Documents/git/gopath/src/github.com/xxxxt/vendor/github.com/kolide/osquery-go/server.go:172 +0x41
github.com/xxxxt/vendor/github.com/kolide/osquery-go.(*ExtensionManagerServer).Run.func1(0xc4201c0060, 0xc42001e080)
	/Users/xxxx/Documents/git/gopath/src/github.com/xxxxt/vendor/github.com/kolide/osquery-go/server.go:186 +0x2b
created by github.com/xxxxt/vendor/github.com/kolide/osquery-go.(*ExtensionManagerServer).Run
	/Users/xxxx/Documents/git/gopath/src/github.com/xxxxt/vendor/github.com/kolide/osquery-go/server.go:185 +0x66

The example here currently shows the same behaviour. Could it be that there is a change in how the logger should be registered?

Pinning the dependency to d4f3a629e76ccc0d62dccc16a9b8d52e7b2fb10b still works fine for now.

I'm guessing this was fixed in #61
@leonjza can you confirm?

Should be fixed by #61.

Confirmed working with 0d2b07f57cb4def53a17a093662f80b862efbcca again. Thanks!


BUG: "stopped": rtorrent.ViewStopped

"stopped": rtorrent.ViewStopped and hashing No longer works since update 1.3.0

I can't replicate this:
exporter-scraper-1  | # HELP rtorrent_torrents_total Torrent count by view.
exporter-scraper-1  | # TYPE rtorrent_torrents_total counter
exporter-scraper-1  | rtorrent_torrents_total{label="",view="main"} 1
exporter-scraper-1  | rtorrent_torrents_total{label="",view="stopped"} 1

But maybe you're expecting it to report 0 if no torrent can be found in the view?
https://github.com/thde/rtorrent_exporter/commit/5b8eccb5038e443ca177c1e5877f97894097858b

ya most likey, thanks dude


Doctests for bevy_gizmos run for too long

Bevy version
https://github.com/bevyengine/bevy/commit/dc8fc6cb34d6064530c698f30445cd69d1c79682 (Latest as of writing)
[Optional] Relevant system information

Rust Version: rustc 1.74.1 (a28077b28 2023-12-04)
System Info:

Operating System: Kubuntu 23.10
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10
Kernel Version: 6.5.0-14-generic (64-bit)
Graphics Platform: X11
Processors: 16 × 13th Gen Intel® Core™ i5-13400
Memory: 15.4 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3060/PCIe/SSE2
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B760M DS3H AX DDR4

What you did
Running cargo test --doc on bevy_gizmos
What went wrong
The doctests are extremely long. Lasting for over 60 seconds. It appears running assert_is_system on a system with Gizmos causes massive lag. Removing assert_is_system makes the tests run much quicker.
# use bevy_gizmos::prelude::*;
# use bevy_render::prelude::*;
# use bevy_math::prelude::*;
# use std::f32::consts::PI;
fn system(mut gizmos: Gizmos) {
    gizmos.arc_2d(Vec2::ZERO, 0., PI / 4., 1., Color::GREEN);

    // Arcs have 32 line-segments by default.
    // You may want to increase this for larger arcs.
    gizmos
        .arc_2d(Vec2::ZERO, 0., PI / 4., 5., Color::RED)
        .segments(64);
}
# bevy_ecs::system::assert_is_system(system);

Additional information
I created a project that does a similar test, it ran instantly. Which is weird.

I was able to reproduce the issue! For some reason its only laggy on doctests. Unit tests work perfectly fine.
/// ```
/// use bevy::gizmos::gizmos::Gizmos;
///
/// fn system(mut _gizmos: Gizmos) {}
///
/// bevy::ecs::system::assert_is_system(system);
/// ```
pub struct A;

I was able to use a few nightly compiler flags to show the performance of the tests, so here are the benchmarks:

Doctest, without assert_is_system: ~0.55s
Doctest, with assert_is_system: ~2.9s
Unit test, with/without assert_is_system: 0.0s

Another thing to add: It appears Gizmos in particular is much laggier than normal. Other configurations take around ~1.1s to run.

This appears to also happen in other bevy crates such as bevy_ui and error for some reason.

running those test seems fast enough on my computer:
> cargo test --doc -p bevy_gizmos
    Finished test [unoptimized + debuginfo] target(s) in 0.32s
   Doc-tests bevy_gizmos

running 23 tests
test crates/bevy_gizmos/src/gizmos.rs - gizmos::Gizmos<'s>::cuboid (line 266) ... ok
test crates/bevy_gizmos/src/arcs.rs - arcs::Gizmos<'s>::arc_2d (line 25) ... ok
test crates/bevy_gizmos/src/arrows.rs - arrows::Gizmos<'s>::arrow_2d (line 97) ... ok
test crates/bevy_gizmos/src/arrows.rs - arrows::Gizmos<'s>::arrow (line 72) ... ok
test crates/bevy_gizmos/src/gizmos.rs - gizmos::Gizmos<'s>::line_gradient (line 79) ... ok
test crates/bevy_gizmos/src/circles.rs - circles::Gizmos<'s>::circle_2d (line 64) ... ok
test crates/bevy_gizmos/src/circles.rs - circles::Gizmos<'s>::circle (line 26) ... ok
test crates/bevy_gizmos/src/arrows.rs - arrows::ArrowBuilder<'_,'_>::with_tip_length (line 24) ... ok
test crates/bevy_gizmos/src/gizmos.rs - gizmos::Gizmos<'s>::line_2d (line 301) ... ok
test crates/bevy_gizmos/src/gizmos.rs - gizmos::Gizmos<'s>::line (line 59) ... ok
test crates/bevy_gizmos/src/gizmos.rs - gizmos::Gizmos<'s>::linestrip_2d (line 345) ... ok
test crates/bevy_gizmos/src/gizmos.rs - gizmos::Gizmos<'s>::line_gradient_2d (line 320) ... ok
test crates/bevy_gizmos/src/gizmos.rs - gizmos::Gizmos<'s>::linestrip_gradient (line 167) ... ok
test crates/bevy_gizmos/src/gizmos.rs - gizmos::Gizmos<'s>::ray (line 99) ... ok
test crates/bevy_gizmos/src/gizmos.rs - gizmos::Gizmos<'s>::linestrip (line 143) ... ok
test crates/bevy_gizmos/src/gizmos.rs - gizmos::Gizmos<'s>::ray_gradient (line 118) ... ok
test crates/bevy_gizmos/src/gizmos.rs - gizmos::Gizmos<'s>::ray_2d (line 391) ... ok
test crates/bevy_gizmos/src/gizmos.rs - gizmos::Gizmos<'s>::linestrip_gradient_2d (line 364) ... ok
test crates/bevy_gizmos/src/gizmos.rs - gizmos::Gizmos<'s>::ray_gradient_2d (line 410) ... ok
test crates/bevy_gizmos/src/gizmos.rs - gizmos::Gizmos<'s>::rect (line 246) ... ok
test crates/bevy_gizmos/src/gizmos.rs - gizmos::Gizmos<'s>::rect_2d (line 435) ... ok
test crates/bevy_gizmos/src/lib.rs - (line 6) ... ok
test crates/bevy_gizmos/src/gizmos.rs - gizmos::Gizmos<'s>::sphere (line 208) ... ok

test result: ok. 23 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 2.62s

running those test seems fast enough on my computer:
> cargo test --doc -p bevy_gizmos
    Finished test [unoptimized + debuginfo] target(s) in 0.32s
   Doc-tests bevy_gizmos

running 23 tests
test crates/bevy_gizmos/src/gizmos.rs - gizmos::Gizmos<'s>::cuboid (line 266) ... ok
test crates/bevy_gizmos/src/arcs.rs - arcs::Gizmos<'s>::arc_2d (line 25) ... ok
test crates/bevy_gizmos/src/arrows.rs - arrows::Gizmos<'s>::arrow_2d (line 97) ... ok
test crates/bevy_gizmos/src/arrows.rs - arrows::Gizmos<'s>::arrow (line 72) ... ok
test crates/bevy_gizmos/src/gizmos.rs - gizmos::Gizmos<'s>::line_gradient (line 79) ... ok
test crates/bevy_gizmos/src/circles.rs - circles::Gizmos<'s>::circle_2d (line 64) ... ok
test crates/bevy_gizmos/src/circles.rs - circles::Gizmos<'s>::circle (line 26) ... ok
test crates/bevy_gizmos/src/arrows.rs - arrows::ArrowBuilder<'_,'_>::with_tip_length (line 24) ... ok
test crates/bevy_gizmos/src/gizmos.rs - gizmos::Gizmos<'s>::line_2d (line 301) ... ok
test crates/bevy_gizmos/src/gizmos.rs - gizmos::Gizmos<'s>::line (line 59) ... ok
test crates/bevy_gizmos/src/gizmos.rs - gizmos::Gizmos<'s>::linestrip_2d (line 345) ... ok
test crates/bevy_gizmos/src/gizmos.rs - gizmos::Gizmos<'s>::line_gradient_2d (line 320) ... ok
test crates/bevy_gizmos/src/gizmos.rs - gizmos::Gizmos<'s>::linestrip_gradient (line 167) ... ok
test crates/bevy_gizmos/src/gizmos.rs - gizmos::Gizmos<'s>::ray (line 99) ... ok
test crates/bevy_gizmos/src/gizmos.rs - gizmos::Gizmos<'s>::linestrip (line 143) ... ok
test crates/bevy_gizmos/src/gizmos.rs - gizmos::Gizmos<'s>::ray_gradient (line 118) ... ok
test crates/bevy_gizmos/src/gizmos.rs - gizmos::Gizmos<'s>::ray_2d (line 391) ... ok
test crates/bevy_gizmos/src/gizmos.rs - gizmos::Gizmos<'s>::linestrip_gradient_2d (line 364) ... ok
test crates/bevy_gizmos/src/gizmos.rs - gizmos::Gizmos<'s>::ray_gradient_2d (line 410) ... ok
test crates/bevy_gizmos/src/gizmos.rs - gizmos::Gizmos<'s>::rect (line 246) ... ok
test crates/bevy_gizmos/src/gizmos.rs - gizmos::Gizmos<'s>::rect_2d (line 435) ... ok
test crates/bevy_gizmos/src/lib.rs - (line 6) ... ok
test crates/bevy_gizmos/src/gizmos.rs - gizmos::Gizmos<'s>::sphere (line 208) ... ok

test result: ok. 23 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 2.62s

That is really weird. What compiler are you using and what OS?

Another weird thing: Running in --release mode causes the doctests to finish in only 1.14s

That is really weird. What compiler are you using and what OS?

On an apple m1 max, with rust 1.74.1

12th Gen Intel(R) Core(TM) i7-12700H
test result: ok. 45 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 17.96s

@doonv Can you check whether you are still experiencing this issue?

With cargo run -p ci -- doc there is an entirely different story. A whole bunch of crates pass and then...
   Doc-tests bevy_gizmos

running 45 tests
test crates\bevy_gizmos\src\arcs.rs - arcs::Gizmos<'w,'s,Config,Clear>::arc_2d (line 34) has been running for over 60 seconds
test crates\bevy_gizmos\src\arcs.rs - arcs::Gizmos<'w,'s,Config,Clear>::arc_3d (line 154) has been running for over 60 seconds
test crates\bevy_gizmos\src\arcs.rs - arcs::Gizmos<'w,'s,Config,Clear>::long_arc_2d_between (line 386) has been running for over 60 seconds
test crates\bevy_gizmos\src\arcs.rs - arcs::Gizmos<'w,'s,Config,Clear>::long_arc_3d_between (line 253) has been running for over 60 seconds
test crates\bevy_gizmos\src\arcs.rs - arcs::Gizmos<'w,'s,Config,Clear>::short_arc_2d_between (line 340) has been running for over 60 seconds
test crates\bevy_gizmos\src\arcs.rs - arcs::Gizmos<'w,'s,Config,Clear>::short_arc_3d_between (line 207) has been running for over 60 seconds
test crates\bevy_gizmos\src\arrows.rs - arrows::ArrowBuilder<'_,'_,'_,Config,Clear>::with_tip_length (line 37) has been running for over 60 seconds
test crates\bevy_gizmos\src\arrows.rs - arrows::Gizmos<'w,'s,Config,Clear>::arrow (line 114) has been running for over 60 seconds
test crates\bevy_gizmos\src\arrows.rs - arrows::Gizmos<'w,'s,Config,Clear>::arrow_2d (line 145) has been running for over 60 seconds
test crates\bevy_gizmos\src\arrows.rs - arrows::Gizmos<'w,'s,Config,Clear>::axes (line 175) has been running for over 60 seconds
test crates\bevy_gizmos\src\arrows.rs - arrows::Gizmos<'w,'s,Config,Clear>::axes_2d (line 208) has been running for over 60 seconds
test crates\bevy_gizmos\src\circles.rs - circles::Gizmos<'w,'s,Config,Clear>::circle (line 116) has been running for over 60 seconds
test crates\bevy_gizmos\src\circles.rs - circles::Gizmos<'w,'s,Config,Clear>::circle_2d (line 157) has been running for over 60 seconds
test crates\bevy_gizmos\src\circles.rs - circles::Gizmos<'w,'s,Config,Clear>::ellipse (line 36) has been running for over 60 seconds
test crates\bevy_gizmos\src\circles.rs - circles::Gizmos<'w,'s,Config,Clear>::ellipse_2d (line 77) has been running for over 60 seconds
test crates\bevy_gizmos\src\circles.rs - circles::Gizmos<'w,'s,Config,Clear>::sphere (line 199) has been running for over 60 seconds
test crates\bevy_gizmos\src\cross.rs - cross::Gizmos<'_,'_,Config>::cross (line 24) has been running for over 60 seconds
test crates\bevy_gizmos\src\cross.rs - cross::Gizmos<'_,'_,Config>::cross_2d (line 59) has been running for over 60 seconds
test crates\bevy_gizmos\src\curves.rs - curves::Gizmos<'w,'s,Config,Clear>::curve_2d (line 30) has been running for over 60 seconds
test crates\bevy_gizmos\src\curves.rs - curves::Gizmos<'w,'s,Config,Clear>::curve_3d (line 64) has been running for over 60 seconds

It uses all 32 GB of RAM and causes the system to freeze up/soft crash after about 5-10 minutes.

Closing as duplicate.

What issue is this a duplicate of?
IIRC, there was a cargo issue that causes a ballooning of memory use for certain doc tests, and the gizmos are a prime example thereof.

What issue is this a duplicate of?
IIRC, there was a cargo issue that causes a ballooning of memory use for certain doc tests, and the gizmos are a prime example thereof.

https://github.com/bevyengine/bevy/issues/12207
We decided to keep the one with more info, even though it is technically newer


Update monitoring chart time zone picker location

moved it to the right most card

Thanks! I forgot to do it yesterday

Thanks @constanzauanini  - btw, I tried updating the time zone but the x-axis range stayed the same. Can you take a look - it's possible I didn't test it right since I have no data.

Thanks! I forgot to do it yesterday

Thanks @constanzauanini - btw, I tried updating the time zone but the x-axis range stayed the same. Can you take a look - it's possible I didn't test it right since I have no data.

Working for me!

I meant the range min and max on the x-axis. It is not changing, even in your video. This is not coming from the data points, i think it's an option in the chart... we may need to just apply the time zone there. The first and last labels on the x-axis.

Thanks! I forgot to do it yesterday

Thanks @constanzauanini - btw, I tried updating the time zone but the x-axis range stayed the same. Can you take a look - it's possible I didn't test it right since I have no data.

Working for me!

I just discovered the bug.  I didn't add timezone to the end date! Will make the fix


bug(git-lfs): Can't check signature: No public key

When building our devcontainer on our Gitlab-CI build pipeline (to use it in ci-jobs) with the following command
devcontainer build . --image-name $CI_REGISTRY_IMAGE/devcontainer:$CI_COMMIT_SHA --workspace-folder .  --cache-from="type=local,src=.buildx/cache" --cache-to="type=local,dest=.buildx/cache" --cache-to="type=registry,ref=reg.goibykus.de/stp/devcontainer:cache,mode=max,image-manifest=true"
the git-lfs feature fails installation with the following log:
#18 0.145 ===========================================================================
#18 0.145 Feature       : Git Large File Support (LFS)
#18 0.145 Description   : Installs Git Large File Support (Git LFS) along with needed dependencies. Useful for base Dockerfiles that often are missing required install dependencies like git and curl.
#18 0.145 Id            : ghcr.io/devcontainers/features/git-lfs
[2024-08-01T07:30:38.548Z]
#18 0.145 Version       : 1.2.2
#18 0.145 Documentation : https://github.com/devcontainers/features/tree/main/src/git-lfs
#18 0.145 Options       :
#18 0.145     VERSION="latest"
#18 0.145     AUTOPULL="true"
#18 0.145     INSTALLDIRECTLYFROMGITHUBRELEASE="false"
#18 0.145 ===========================================================================
[2024-08-01T07:30:38.741Z] #18 0.184 Installing Git LFS...
#18 0.188 (*) No apt package for bookworm amd64. Installing manually.
[2024-08-01T07:30:38.961Z] #18 0.558 GIT_LFS_VERSION=3.5.1
#18 0.558 Looking for release artfact: git-lfs-linux-amd64-v3.5.1.tar.gz
[2024-08-01T07:30:45.146Z] #18 6.743 (*) Keyserver hkp://keyserver.ubuntu.com is not reachable.
[2024-08-01T07:30:50.164Z] #18 11.76 (*) Keyserver hkp://keyserver.pgp.com is not reachable.
[2024-08-01T07:30:51.203Z] #18 12.80 (*) Downloading GPG key...
[2024-08-01T07:30:51.364Z] #18 12.81 gpg: keybox '/tmp/tmp-gnupg/pubring.kbx' created
[2024-08-01T07:30:52.248Z] #18 13.85 gpg: key F1BA225C0223B187: new key but contains no user ID - skipped
#18 13.85 gpg: Total number processed: 1
#18 13.85 gpg:           w/o user IDs: 1
[2024-08-01T07:30:52.505Z] #18 14.10 gpg: /tmp/tmp-gnupg/trustdb.gpg: trustdb created
#18 14.10 gpg: key F54FE648088335A9: public key "Chris Darroch (CODE SIGNING KEY<EMAIL_ADDRESS>imported
[2024-08-01T07:30:52.668Z] #18 14.11 gpg: Total number processed: 1
#18 14.11 gpg:               imported: 1
[2024-08-01T07:30:52.781Z] #18 14.38 gpg: key ABA67BE5A5795889: new key but contains no user ID - skipped
[2024-08-01T07:30:52.872Z] #18 14.38 gpg: Total number processed: 1
#18 14.38 gpg:           w/o user IDs: 1
#18 14.39 gpg: Signature made Thu Mar  7 21:01:49 2024 UTC
#18 14.39 gpg:                using RSA key 4DB92D1D8CEE7E54F06713452D0C9BC12F82B3A1
#18 14.39 gpg:                issuer<EMAIL_ADDRESS>#18 14.39 gpg: Can't check signature: No public key
#18 14.39 ERROR: Feature "Git Large File Support (LFS)" (ghcr.io/devcontainers/features/git-lfs) failed to install! Look at the documentation at https://github.com/devcontainers/features/tree/main/src/git-lfs for help troubleshooting this error.

I could not reproduce the issue locally when starting the devcontainer through vscode. Setting the git-lfs feature to Version 1.2.1 fixed the issue in the pipeline. The pipeline job is run in a container based on mcr.microsoft.com/vscode/devcontainers/javascript-node:0-18 with docker, buildx and devcontainer-cli installed on top.
Here is my devcontainer.json and dockerfile:
{
  "name": "devcontainer",
  "build": {
    "dockerfile": "Dockerfile",
    "cacheFrom": [
      "type=registry,ref=reg.goibykus.de/stp/devcontainer:cache"
    ]
  },
  "containerEnv": {
    "PIPX_HOME": "/usr/local/py-utils",
    "PIPX_BIN_DIR": "/usr/local/py-utils/bin"
  },
  "features": {
    "ghcr.io/devcontainers/features/git-lfs:1.2.1": {},
    "ghcr.io/rio/features/skaffold:2": {
      "version": "v2.10.1"
    },
    "ghcr.io/devcontainers/features/docker-outside-of-docker:1": {},
    "ghcr.io/devcontainers/features/kubectl-helm-minikube:1": {
      "minikube": "none",
      "helm": "3.14.4"
    },
    "ghcr.io/rio/features/k3d:1": {
      "version": "v5.6.3"
    },
    "ghcr.io/devcontainers-contrib/features/istioctl:1": {},
    "ghcr.io/stuartleeks/dev-container-features/shell-history:0": {},
    "ghcr.io/nucleuscloud/devcontainer-features/helmfile:0": {
      "version": "v0.160.0"
    },
    "ghcr.io/dhoeric/features/k9s:1": {
      "version": "0.32.4"
    }
  },
  "mounts": [
    "source=${localEnv:HOME}${localEnv:USERPROFILE}/.kube,target=/home/node/.kube,type=bind,consistency=cached"
  ],
  "customizations": {
    "vscode": {
      "extensions": [
        "EditorConfig.EditorConfig",
        "kennylong.kubernetes-yaml-formatter",
        "anweber.vscode-httpyac",
        "yokawasa.jwt-debugger",
        "ms-kubernetes-tools.vscode-kubernetes-tools",
        "mhutchie.git-graph",
        "eamodio.gitlens",
        "gitlab.gitlab-workflow",
        "valentjn.vscode-ltex"
      ],
      "settings": {
        "git.allowForcePush": true,
        "git.rebaseWhenSync": true,
        "gitlens.plusFeatures.enabled": false,
        "httpyac.environmentSelectedOnStart": [
          "devcontainer",
          "$shared"
        ],
        "yaml.customTags": [
          "!reference sequence"
        ],
        "files.associations": {
          "environments.yaml": "helm",
          "helmfile.yaml": "helm",
          "*.helmfile.yaml": "helm",
          "*.yaml.gotmpl": "helm"
        },
        "dev.containers.dockerCredentialHelper": false
      }
    }
  }
}

FROM reg.goibykus.de/microsoft-mcr/devcontainers/typescript-node:20-bookworm

@prathameshzarkar9 / @gauravsaini04  Can either of you help debug this? thanks!
@CaffeineDaemon Can you provide us with a sample repro? also, can you try with an image other than reg.goibykus.de/microsoft-mcr/devcontainers/typescript-node:20-bookworm? (maybe [mcr.microsoft.com/devcontainers/typescript-node:22](https://github.com/devcontainers/images/tree/main/src/typescript-node)

Decoding the error message you got:

The script first attempts to reach two keyservers (hkp://keyserver.ubuntu.com and hkp://keyserver.pgp.com), but both were not reachable as shown here :

(*) Keyserver hkp://keyserver.ubuntu.com is not reachable.
(*) Keyserver hkp://keyserver.pgp.com is not reachable.
The script then attempts to get the GPG keys and seems like it partially succeeded, as shown by these messages:

gpg: key F1BA225C0223B187: new key but contains no user ID - skipped
gpg: key ABA67BE5A5795889: new key but contains no user ID - skipped

This above shows while the keys had been downloaded, they were incomplete or invalid for use

One key (F54FE648088335A9) was successfully imported later on  :

gpg: key F54FE648088335A9: public key "Chris Darroch (CODE SIGNING KEY<EMAIL_ADDRESS>imported

this indicates receive_gpg_keys() was able to import at least one valid key

Now, despite retrieving and importing some keys, GPG could not verify the signature of the Git LFS tarball, can be seen through this:

gpg: Can't check signature: No public key

What we think: I think the keyservers might be down, or your network might be blocking access to them. Can you please check your network configuration for any firewall or proxies etc. before we inspect any further.

@samruddhikhandale Sorry for the late reply, i was busy and forgot to reply to you. Here is a minimal reproduction of the issue withe the image suggested by you:
{
  "name": "test",
  "image": "mcr.microsoft.com/devcontainers/typescript-node:22",
  "features": {
    "ghcr.io/devcontainers/features/git-lfs:1.2.2": {}
  }
}

It yields the same error.
But it seems @gauravsaini04 is right, i cannot reach the keyservers from the pipeline runner at all when using the standard port (11371). It seems it is blocked for outgoing connections in our network.
I will try to convince our network guys to open it, but they can be a bit stubborn on this topic.
https://datatracker.ietf.org/doc/html/draft-shaw-openpgp-hkp-00 Section 2 suggests using port 80 instead:

It has been suggested by some that for reasons of maximum compatibility
with firewalls and filtering HTTP proxies, it is better to use the
standard HTTP port (TCP port 80)

@gauravsaini04 what do you think about adding a fallback to port 80 when the keyservers cannot be reached? This could save me and other users of the feature some trouble.

Thanks @CaffeineDaemon for getting back to us, appreciate it!
Re-reading this, looks like the git-lfs Feature might be running into similar issues as reported in https://github.com/devcontainers/features/issues/1055 (especially because of https://github.com/devcontainers/features/issues/1072#issuecomment-2351997273 and the fact that keys.openpgp.org sometimes strips user IDs from keys)
@gauravsaini04 Can we make similar changes to the git-lfs Feature as of https://github.com/devcontainers/features/pull/1056 ? Thanks!

Edit: Just appending :80 to the keyserver URL seems to work with gpg to use port 80 instead of 11371, i tested it with gpg --keyserver hkp://keyserver.ubuntu.com:80  --search-key<EMAIL_ADDRESS>
If that does't fix the issues faced by @CaffeineDaemon, then we can definitely look into ^ request.

The pipeline job is run in a container based on mcr.microsoft.com/vscode/devcontainers/javascript-node:0-18 with docker, buildx and devcontainer-cli installed on top.

@CaffeineDaemon On a side note, I'd recommend pinning the image to major version 1 instead of 0 in order to receive security patches.

Have added solution in pr #1124

@CaffeineDaemon Can you check if the the latest changes to the git-lfs Feature is working for you? thanks!

PR #1124 was merged

Feel free to reopen if the issue persists, thanks!


[Working With Salesforce Client] Update the create salesforce account URL in "Obtain Access & Refresh tokens from Salesforce REST API" Blog post

Description:
In Obtain Access & Refresh tokens from Salesforce REST API
 blog post, the URL for create salesforce account is directed to free version, where user can't enable REST API. Lets provide the Salesforce Sign-up page for Developer Edition
Related Issues:
https://github.com/wso2/ballerina-integrator/issues/682

Updated the blog.


Broken Link in Readme.md

The link for the project documentation is broken.

Changes merged into master after approval of pull request.


Move to pypi RDFlib-SQLAlchemy dependency (rebased)

A rebased version of #41 which can be merged if it passes travis.

Well, that didn't work. Will return to this after reviewing the other open PRs.

When I run this locally with nosetests, this works fine.  When I run this locally with our travis-ci config command coverage run --source=gutenberg -m nose, I get the same errors as travis.  I'm going to experiment with versions of nosetests --with-coverage. Ping @hugovk

The failure is:
ERROR: test_delete (tests.test_metadata_cache.TestSqlite)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/travis/build/c-w/Gutenberg/tests/test_metadata_cache.py", line 107, in setUp
    self.cache = SqliteMetadataCache(self.local_storage)
  File "/home/travis/build/c-w/Gutenberg/gutenberg/acquire/metadata.py", line 205, in __init__
    store = plugin.get('SQLAlchemy', Store)(identifier=_DB_IDENTIFIER)
  File "/home/travis/virtualenv/python2.7.12/lib/python2.7/site-packages/rdflib/plugin.py", line 103, in get
    "No plugin registered for (%s, %s)" % (name, kind))
PluginException: No plugin registered for (SQLAlchemy, <class 'rdflib.store.Store'>)

This https://github.com/RDFLib/rdflib-sqlalchemy/commit/8f8f17f61aeedf4ca38290d160277f687db6e4c3 commit passes (which is just five commits after the https://github.com/RDFLib/rdflib-sqlalchemy/commit/20fbf1fbbdbc53917bfd7554f38d22d08e71e225 in requirements.pip):
 pip uninstall rdflib-sqlalchemy -y && pip install git+https://github.com/RDFLib/rdflib-sqlalchemy.git@8f8f17f61aeedf4ca38290d160277f687db6e4c3 && coverage run --source=gutenberg -m nose -x
The next commit https://github.com/RDFLib/rdflib-sqlalchemy/commit/ccec3517b69c4abda40e72a22f4cb65b5b33ba11 fails:
pip uninstall rdflib-sqlalchemy -y && pip install git+https://github.com/RDFLib/rdflib-sqlalchemy.git@ccec3517b69c4abda40e72a22f4cb65b5b33ba11 && coverage run --source=gutenberg -m nose -x

That commit includes 'SQLAlchemy = rdflib_sqlalchemy.SQLAlchemy:SQLAlchemy', being commented out:
    entry_points={
        'rdf.plugins.store': [
            # 'SQLAlchemy = rdflib_sqlalchemy.SQLAlchemy:SQLAlchemy',
            # 'SQLAlchemyBase = rdflib_sqlalchemy.SQLAlchemyBase:SQLAlchemy',
        ],
    },

https://github.com/RDFLib/rdflib-sqlalchemy/commit/ccec3517b69c4abda40e72a22f4cb65b5b33ba11#diff-2eeaed663bd0d25b7e608891384b7298R113

They basically changed it from auto-registering a couple plugins to putting it on the end user, which probably makes sense for them.
I believe, we need to just do something like plugin.register("SQLAlchemy") after our imports and it should work.

Well, fixed one error, get another one. Looks like registering the plugin for SQLAlchemy causes us to not change SQLite caches per test.

@sethwoodworth @MasterOdin @hugovk: I finally found some time to look into this. The latest rdflib-sqlalchemy version from PyPI now works with this project. Could you please take a look and let me know what you think?

Coverage decreased (-0.1%) to 96.32% when pulling 31eb0530860549b7f08bfd480dfd093408f00e8c on pypi-rdflib-sqlalchemy-rebased into 4fd78daf0c0872bafe45002b3db0a009ac5084f7 on master.

Coverage decreased (-0.1%) to 96.32% when pulling 31eb0530860549b7f08bfd480dfd093408f00e8c on pypi-rdflib-sqlalchemy-rebased into 4fd78daf0c0872bafe45002b3db0a009ac5084f7 on master.

Coverage decreased (-0.1%) to 96.32% when pulling 31eb0530860549b7f08bfd480dfd093408f00e8c on pypi-rdflib-sqlalchemy-rebased into 4fd78daf0c0872bafe45002b3db0a009ac5084f7 on master.

Coverage decreased (-0.1%) to 96.32% when pulling 31eb0530860549b7f08bfd480dfd093408f00e8c on pypi-rdflib-sqlalchemy-rebased into 4fd78daf0c0872bafe45002b3db0a009ac5084f7 on master.

Coverage decreased (-0.1%) to 96.32% when pulling 31eb0530860549b7f08bfd480dfd093408f00e8c on pypi-rdflib-sqlalchemy-rebased into 4fd78daf0c0872bafe45002b3db0a009ac5084f7 on master.

Coverage increased (+0.1%) to 96.537% when pulling eeea57467c9d5797cd89d7031b3d3e45891ee923 on pypi-rdflib-sqlalchemy-rebased into 4fd78daf0c0872bafe45002b3db0a009ac5084f7 on master.

Coverage increased (+0.1%) to 96.537% when pulling eeea57467c9d5797cd89d7031b3d3e45891ee923 on pypi-rdflib-sqlalchemy-rebased into 4fd78daf0c0872bafe45002b3db0a009ac5084f7 on master.

Coverage increased (+0.1%) to 96.537% when pulling eeea57467c9d5797cd89d7031b3d3e45891ee923 on pypi-rdflib-sqlalchemy-rebased into 4fd78daf0c0872bafe45002b3db0a009ac5084f7 on master.

Coverage increased (+0.1%) to 96.537% when pulling eeea57467c9d5797cd89d7031b3d3e45891ee923 on pypi-rdflib-sqlalchemy-rebased into 4fd78daf0c0872bafe45002b3db0a009ac5084f7 on master.

Coverage increased (+0.1%) to 96.537% when pulling eeea57467c9d5797cd89d7031b3d3e45891ee923 on pypi-rdflib-sqlalchemy-rebased into 4fd78daf0c0872bafe45002b3db0a009ac5084f7 on master.

After merging this in, we should then be able to release to pypi directly via git tags instead of having to worry about going through the pypi cli.


computational complexity

Very excellent work, but we would like to further evaluate the efficacy of the model.
How do we test the FLOPs of the model?

我不确定是否有一种完美的方法来计算 FLOP。一种选择是使用一些软件来估计模型定义中的计数。四处搜索，看起来 facebookresearch 有另一个包含此功能的存储库 （fvcore），您可能想尝试一下。
另一种选择是从模型定义中手动估计计数，这说起来容易做起来难！话虽如此，SAM 模型的大部分是基于转换器的，因此，如果您估计图像编码器和掩码解码器的单个转换器块的 FLOP 计数，则只需乘以模型每个组件中的转换器块数量（图像编码器和掩码器大小配置都可以在build_sam.py脚本中找到），就可以获得总 FLOP 计数的近似值。
Very excellent work！
I would like to ask, have you tried to use fvcore to calculate FLOPs, what parts are included in your calculation, I did not succeed in the calculation, I would like to ask if you have a calculation code

from calflops import calculate_flops
from torchvision import models
import requests
from PIL import Image
from transformers import SamModel, SamProcessor
import torch
device = "cuda" if torch.cuda.is_available() else "cpu"
model = SamModel.from_pretrained("./sam-vitb")
processor = SamProcessor.from_pretrained("./sam-vitb")
img_pth = "./car.png"
raw_image = Image.open(img_pth).convert("RGB")
input_points = [[[450, 600,2000,1000],
]]
inputs = processor(raw_image, input_boxes=input_points, return_tensors="pt")
outputs = model(**inputs)
masks = processor.image_processor.post_process_masks(outputs.pred_masks.cpu(), inputs["original_sizes"].cpu(), inputs["reshaped_input_sizes"].cpu())
flops, macs, params = calculate_flops(model=model,
kwargs=inputs,
print_results=True)
print("Salesforce/blip2-opt-2.7b FLOPs:%s   MACs:%s   Params:%s \n" % (flops, macs, params))
I used calflops to test lSAM-Base and SAM-Large, the code is as shown in the image, I didn't test the FLOPs of SAM-H due to memory limitations。But I now want to test FLOPs for MobileSAM and it hasn't worked out yet


[Suggestion] API Expansion?

I find it hard to find for instance the code to add new recipes to the current machines. Maybe you could expand the API a bit more to include those as well?

it's really easy just copy the recipe from the core XML then past in user XML and edit it i use Butterfly XML if you wanna see examples here is my Sagmill & Vat XML tat i added new recipes like Thermal Expansion liquids can be brewed with the vat , get saw dust from logs in the Sagmill
https://www.dropbox.com/s/xvr54gw0n1iqsoi/SAGMillRecipes_User.xml?dl=0
https://www.dropbox.com/s/901kb01l4cqciva/VatRecipes_User.xml?dl=0
there is a tiny bug i found that Enchanter User XML will not apply any enchantment books modification i don't know if adding will work but modifying any existing recipes does not seems to not work , I'm using version 2.2.8 3.4.9 / Forge 1291 i don't know if it's fixed in new version or i'm doing it wrong

IMC.java has all you need to add recipes.

Hmm, alright, fair enough, thanks ^-^ Locked and on my way I suppose~


Update quick test clustertype to have ui meta one of each type

it does now have more options, include choices and auto delete.


Shifter: Guide json template explorer

[x] -  .sgt (serialized guide template) (json file) explorer: We can check the content before load it
[x] - can edit the values
[ ] - can import partial guides from the available  components_list

Hi @mottosso ! I am using your Qjasonmodel.py module here :D

Is working really great!! Just want to thank you one more time!
The tool still WIP, provably finish tomorrow. I will keep it simple for the first release
btw: I have found it googling for references and was a big surprise when I found your name :P  Hahaha! you always ahead!

Whop! I'm using this too; but I can't take much credit. It was literally a one-to-one translation from the C++. :)


unconventional behaviour for "keep franz in background"

If "Keep Franz in background when closing the window" is enabled the window does not get closed at all and is still visible in the taskbar.
In combination with the setting "Minimize Franz to system tray" the window closes correctly again but the minimize button now also closes the window (so both "close" and "minimize" do the same).
Problem:

No possibility to get the expected behaviour of "close" and "minimize" while still keeping the application in the system tray.

Solution:

If "Keep Franz in background when closing the window" is enabled the close button should remove the application from the taskbar while also keeping Franz in the system tray.

This is very old issue which I fixed once but back in version v5.2.1-beta.1 it was reintroduced and got into stable even if I was pointing it out.
It was mentioned in serveral issues: #468, #902, #763, #1006, probably even more. Some of them were described misleadingly, the last one is spot on.
Past pull request which was merged was #1038, gif with fixed behaviour included.
This is the commit which reintroduced this problem: #1344. No idea what was fix(Windows): Fix losing window when "Keep Franz in background" is enabled. Basicaly, it added one condition which I removed to fix this issue.


Fix issues on volume snapshots page

The annotations on a VolumeSnapshotContent is an object map, not a list.

Hi @ameade thanks for pointing out.
Since we try to follow the Trivial Edits guidelines as much as we can, I kindly ask you also look for further improvement on the same page so that one PR can cover more modifications. For eg. fixing other Grammatical errors or correcting broken links or more reference links etc.

/retitle Fix issues on volume snapshots page

👋 @ameade .
Are you actively working on these changes or can you close the pull request?
Thanks

Hi @ameade please address the reviews suggested. Are you actively working this PR?

@ameade Hi there – due to the age of this PR and the lack of follow-up on reviews, I'll be closing this PR. Once you have the bandwidth, you are more than welcome to reopen this PR and continue the work, which will include checking out the feedback from our reviewers. Thanks!
/close


Make email address pattern case insensitive

System Details

FluentValidation version: Any
Web Framework version ASP.NET Core 2.1

Issue Description
I'm using micro-elements/MicroElements.Swashbuckle.FluentValidation to bind my FluentValidation rules into a Swagger document. The OpenAPI spec says the patterns are defined to be case sensitive and it does not support flags. See: https://swagger.io/docs/specification/data-models/data-types/#pattern
The binding in the library only takes the RegEx.Expression property which indicates conformity with the Open API/Swagger spec. See: https://github.com/micro-elements/MicroElements.Swashbuckle.FluentValidation/blob/master/src/MicroElements.Swashbuckle.FluentValidation/FluentValidationRules.cs#L177
However, FluentValidation uses the RegexOptions.IgnoreCase option. This is not surfaced to our Open API doc.
I propose that the regex be changed to support upper case character classes (i.e. [a-z] -> [a-zA-Z].
Aside, what's the motivation of changing the validator for ASP.NET Core to be a simple @ check?

Hi, thanks for the suggestion, but this isn't something we'll implement.
The email address validation in FluentValidation is intentionally designed to match the behaviour of the EmailAddressAttribute that's part of System.ComponentModel.DataAnnotations.
This is done for consistency, so that the two behave in the same way. For .NET 4.x, this was done with a regular expression, so FluentValidation uses essentially the same one (with a couple of minor fixes). At this point the regex in FluentValidation is not something that's going to change because a) this would diverge from the behaviour of the  .NET 4.x EmailAddressAttribute, and b) maintaining/updating/testing a regex like this is hard, complex and extremely time consuming.
For .NET Core, the EmailAddressAttribute was changed to perform a simple @ check, so FluentValidation has done the same to match it for consistency. Validation of email addresses by regex is generally considered these days to be undesirable - please see the discussion on the corefx repo.
If you really want to use a regex for email validation then you're still welcome to do so - you can use FluentValidation's Matches validator to use whatever regex you like, but the standard email validator behaviour is not going to change at this point.
Hope that makes sense.


Add LinkedList Reversal Java

GSSoC 2021 participant.
I will like to add Reversal of LinkedList in java and will use clear and concise code with explanations

I am a GSSOC'21 participant and I wish to work on this using C++. Hope to hear back from you . I will give some testcases with proper explanation too.
Thank you .

Hello
I am a GSSOC'21 participant
I would like to contribute in this issue
I can implement this code in java with proper comment for better understanding.
I will also add 2-3 testcases for better understanding

I would Like to do this in javA

pls assign it to me

Hi, I am GSSOC'21 participant. I wish to work on this using C++. Hope to hear you .Please assign me this.


perf: mixerfilter should shed reports() if telemetry is overloaded

We should validate that mixerfilter does neither block nor incur significant CPU costs once telemetry service starts rejecting RPCs. We have a risk of overloading telemetry if improperly configured, and we don't want to disrupt the entire mesh in that case.
cc @douglas-reid

great idea but we should also have a counter of how much we dropped on the floor and report that for each subsequent call so we track the % of loss

Not stale.
On Fri, Jul 20, 2018, 9:57 PM stale[bot]<EMAIL_ADDRESS>wrote:

This issue has been automatically marked as stale because it has not had
activity in the last 30 days. It will be closed in the next 2 weeks unless
it is tagged "help wanted" or other activity occurs. Thank you for your
contributions.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/5095#issuecomment-406770827, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AJGIxvNTxQ81I4CF-4f_8lGluDHJUfwQks5uIrTBgaJpZM4Tc3hR
.


Maftools to visualize verdict results

Hi @PolinaBevad and @vladsaveliev
I want to visualize VarDict vcf or maf files. For which I am planning to use maftools but the file format from VarDict does not seem to be compatible with maftools.
Any suggestion towards this will be highly appreciated.
Thanks

Hi @biobug16,
Did you try vcf2maf tool (https://github.com/mskcc/vcf2maf)? It is used to convert VCF format to one that maftools can analyze.  I know this can be a little bit complicated because you have to install ensembl VEP locally also (https://gist.github.com/ckandoth/5390e3ae4ecf182fa92f6318cfa9fa97), but I don't know about other tools to convert VCF in MAF-compatible format that are maintained at the moment.

Hi @PolinaBevad
I tried vcf2maf and it helped.
Thanks!


Find next/previous in table/column

Desired Behaviour
Find next/previous search values across a table or within a column
Acceptance test

Replaces #81

Hi @Stephen-Gates
The acceptance test mentions 'highlight'.
What should this look like (e.g., what colour, background, border)?

@mattRedBox Excel does a green surround on the current found item

You could try a green background on all found items
IKIWISI ;-)

Not sure we can release this yet - still haven't solved performance issue - also an issue for find by column - hot can't keep up with selecting cells in iterating through column at a time either.

Thanks for reporting @mattRedBox

@mattRedBox support on https://forum.handsontable.com is really responsive - worth considering

@mattRedBox how are you going with this? I have testing scheduled for tomorrow - wondering whether I should keep this in my calendar or not.

We should have a build out tonight

Just in column for now - in table can be added now with minimal effort.

Majority of this working as expected. But I found a minor issue with highlighting. Once you have finished finding next in one column, and move to another column, some of the highlights in the previous column you were working on remain.
Steps to reproduce

Select a column
Enter value in 'Find in column' field that matches text in the column and press next a few times
Select a different column
Enter value in 'Find in column' field that matches text in the column and press next a few times

See attached for picture showing highlights in multiple columns after following these steps -

Environment details:

macOS Sierra 10.12.6
DataCurator 0.14.0

Thanks for reporting this @louisjasek. To help with managing issues can you please a separate issue for this so it can be added to another milestone? Just type #633 to refer back to this issue

done @Stephen-Gates see issue #708


Camelot V2 - ARBITRUM_ONE

Review Info

Description
Info

Subgraph Reviewed
https://subgraphs.messari.io/subgraph?endpoint=https://api.thegraph.com/subgraphs/id/QmZEHXtebo5xBw63nujW3fPSbmUZRThhbTCKDZNzHDRwRe&tab=protocol

Schema Version
1.3.2

Subgraph Version
1.0.1

Methodology Version
1.0.0

Evidence Spreadsheet
https://docs.google.com/spreadsheets/d/1a_kCkElNGEc9OBNnH8SSrrYLFZKX-N0D/edit?usp=drive_link&ouid=104027705798814439445&rtpof=true&sd=true

Metric to Review
Pool Overview - TVL

The TVL data for nine out of the top 10 pools closely matches the official website data. However, there is a significant discrepancy of 34.60% in the TVL of the wstETH-WETH pool compared to the official website.

Subgraph - wstETH-WETH TVL
Official Website - wstETH-WETH TVL
Absolute difference
Difference %

$4,181,986.55
$3,106,946
$1,075,040.55
34.60%

Refer to the sheet "Pool_Overview"

Please refer to the attached worksheet for more details.

Thanks for the QA.
The wstETH-WETH TVL discrepancy pointed out an important point; there are two different types of pools in Camelot:
https://docs.camelot.exchange/protocol/amm/amm-v2/dual-liquidity-type
Currently prices for all pools were calculated using the standard Uniswap x * y = k formula, but this is incorrect for stable pools, for which a different formula must be used.
Changed the code for this in this commit and deployed a fix for this here (from 06-25 onwards). Also redeployed the whole subgraph once more, but that will take a bit longer to complete.

@spitko This looks much better! Will take a look at the full synced subgraph once its too head, but should be gtg after that

I believe it could be due to the minimum liquidity threshold config set here.
For pools with one whitelisted token, if the TVL of the whitelisted token is under the threshold, then the other token's price is set to 0, i.e only the whitelisted token is counted towards the pools TVL.
The reason it was set that high was to reduce TVL pricing issues, but it is possible a lower value would work as well.

@spitko ya this is a common problem we have been seeing with DEXs. @dmelotik @steegecs any thoughts here? I assume the best course of action is to just set the threshold lower?

Yeah, I think bringing it down lower is a good idea. 250k is pretty high. How many pricing issues were you running into @spitko ? I am wondering if you could bring this down lower to like 100k or maybe even 50k. Do you think this would make the pricing go crazy?
I see you also have a very large amount of unlabeled blacklisted tokens and pools, could some of these being missing be part of the issue?

The pricing issue happened when the whitelisted token of a pool was drained, then the other token's price never got set to zero. Which meant that pools like this, would end up with too high TVLs.
Looking at it again, I think it might be due to the buffer logic built into the findUSDPricePerToken function, which aims to reduce large price jumps. I added an additional check here, which should hopefully resolve this issue. Deployed a new version with this fix and the blacklisted tokens and pools removed, and will keep an eye on it.

Sounds good and thanks for the updated @spitko

There was one other thing I changed, under updateInputTokenBalances, the call to getOrCreateToken updated the token price before the token balances were updated, which meant the new balances used the old price.
https://github.com/messari/subgraphs/pull/2198/commits/aacd13235eb6760b0c38f8d816fcab2a8398bdad#diff-fcbf777fe9f8cf0c8252c75217a881f014e1da2f252358e7a9de364aa91c186d
Here's the full commit, if @steegecs or someone else wants to also look at this. This might be something that should also be changed under the common uniswap-v2 code.

Oh, interesting. Very nice catch @spitko. I like those changes. This is a bit of a pain, but because you are modifying code that impacts all of the uniswap forks, would you mind incrementing the version for all of the uniswap forks subgraphs? Just a patch so 1.0.0 -> 1.0.1.

@spitko we are still waiting for confirmation on the latest deployed version to check that the TVL issues were fixed.
See latest version: https://okgraph.xyz/?q=messari%2Fcamelot-v2-arbitrum
cc @bye43

Latest version also fully synced now:

This looks good to me! Thanks @spitko


Removed sfb 2019

Removed sfb 2019 as Persistent Chat feature is not present in this version https://github.com/MicrosoftDocs/office-docs-powershell/issues/1926
@AndreaBarr

OPS Build status updates of commit 805df93:
:clock10: Preparing: average preparing time is 1 min(s) 13 sec(s)

OPS Build status updates of commit 805df93:
:clock10: Incremental building: average incremental building time is 12 min(s) 24 sec(s)

OPS Build status updates of commit 805df93:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsPersistentChatEndpoint.md
:white_check_mark:Succeeded
View (skype-ps)

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.


TextExtractor turns screen completely gray [screen recording attached]

Microsoft PowerToys version
0.72.0
Installation method
GitHub, PowerToys auto-update, WinGet
Running as admin
None
Area(s) with issue?
TextExtractor
Steps to reproduce
Simply run TextExtractor. The issue is that the entire screen goes gray.
✔ Expected Behavior
I was expecting it to look similar to Windows Snip-and-Sketch's selection tool, as it did before.
❌ Actual Behavior
What happened instead was that it just made the entire screen gray. A screen recording is attached here along with logs.
Windows Version: Windows 11 22H2 (OS Build 22621.2215)
PowerToys 0.71.0 also has the same issues.
https://github.com/microsoft/PowerToys/assets/38306929/8fc97077-96a8-4067-9f43-6e1ede205084
[2023-08-27 15:38:17.835181] [p-3568] [t-35808] [info] TextExtractor logger is initialized
[2023-08-27 15:38:18.447591] [p-3568] [t-35808] [trace] TextExtractor::enable()
[2023-08-27 15:38:18.447632] [p-3568] [t-35808] [trace] Starting TextExtractor process
[2023-08-27 15:38:18.484520] [p-3568] [t-35808] [trace] Successfully started the TextExtractor process
[2023-08-27 17:04:23.860258] [p-3568] [t-35808] [trace] TextExtractor hotkey pressed
[2023-08-27 17:04:25.820067] [p-3568] [t-35808] [trace] TextExtractor hotkey pressed
[2023-08-27 17:04:28.548029] [p-3568] [t-35808] [trace] TextExtractor hotkey pressed
[2023-08-27 17:04:32.691869] [p-3568] [t-35808] [trace] TextExtractor hotkey pressed
[2023-08-27 17:04:40.899565] [p-3568] [t-35808] [trace] TextExtractor hotkey pressed
[2023-08-27 17:04:44.562598] [p-3568] [t-35808] [trace] TextExtractor::destroy()
[2023-08-27 17:04:46.827931] [p-30240] [t-28960] [info] TextExtractor logger is initialized
[2023-08-27 17:04:46.974653] [p-30240] [t-28960] [trace] TextExtractor::enable()
[2023-08-27 17:04:46.974672] [p-30240] [t-28960] [trace] Starting TextExtractor process
[2023-08-27 17:04:46.986298] [p-30240] [t-28960] [trace] Successfully started the TextExtractor process
[2023-08-27 17:04:49.605201] [p-30240] [t-28960] [trace] TextExtractor hotkey pressed

Other Software
No response

Text Extractor can conflict with some other utilities. Can you share what other display utilities you are using? Also please provide a /bugreport

Well, it seems this fixed it! I took a look at my system tray and I had Mica for Everyone (MfE) running, which was the cause of the issue. After setting the Global Rule Backdrop to default within MfE settings, TextExtractor works as intended. It seems that applying a global acrylic effect from within MfE caused the gray overlay issue.
For reference, I have attached a bug report anyway.
PowerToysReport_2023-08-30-10-33-36.zip


[WIP] Codemod notifiers

Codemod for #341.
Still a work in progress.
Also updates to codemod ^0.3.0 which allows for resolving the AST which is required for a lot of the planned changes, since we need to know the static types of variables.

I have this set up so that for tests we have the old version and the golden directory contains the migrated version. Let me know if the tests will cover all of the changes involved in updating the notifiers and I can work on making them pass.

Analysis won't pass until the syntax is available on some version of riverpod, but I've verified the tests locally.

So I've tried the cli
I'm not quite sure why, but I wasn't able to get the import rename working. It kept complaining about errors in the analysed project (when there are none).
The StateNotifierProvider update worked just fine though, thanks for that!

This should also update the list of generic parameters
StateNotifierProvider => StateNotifierProvider<Counter, int>
StateNotifierProvider.family<Counter, Param> => StateNotifierProvider<Counter, int, Param>

One thing I came accross while migrating tests: overrides
final container = ProviderContainer(
  overrides: [
    provider.overrideWithProvider(
      StateNotifierProvider((_) => TestNotifier(10)),
    )
  ],
);

should stay untouched

This should also update the list of generic parameters

Done
About overrides: The generic parameters there stay untouched for what reason? Is it just because they can be inferred? Is there harm in adding them?

Wait why was this closed? 🤦


Additional Items

Firim's Spare Forge-tap - 187908
Eidolic Particles - 187789
Trace Enigmet - 187790
Kismetric Circlet - 187791
Lost Ovoid - 190239
Unstable Containment Trap - 187909

Awesome, thanks! I'll get it added to the next version.

Added the items in version 1.1.3. Thanks again!


Remove "ServiceToTest" parameters from pipeline

We currently use the params ServiceToTest for distinguishing the core and other pipelines, since we have to run all packages depends on core as well.
We have introduced a way to dynamically collect all packages which has dependency on target service. So the parameters are no longer needed.
The issue is to clean up the use of "ServiceToTest"
The identified usages:
https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/core/ci.yml#L38
https://github.com/Azure/azure-sdk-for-net/blob/main/eng/pipelines/templates/stages/archetype-sdk-client.yml#L24
https://github.com/Azure/azure-sdk-for-net/blob/main/eng/pipelines/templates/stages/archetype-sdk-client.yml#L68
https://github.com/Azure/azure-sdk-for-net/blob/main/eng/pipelines/templates/jobs/ci.yml#L17
https://github.com/Azure/azure-sdk-for-net/blob/main/eng/pipelines/templates/jobs/ci.yml#L199

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Azure.Core:0.25254342,Extensions:0.19484453,Azure.Identity:0.10136396'

We have introduced a way to dynamically collect all packages which has dependency on target service.

Curious - how do we identify it now? Is this based on assembly reference? I am curious if this also solves the problem where we were running track1 tests as part of the core pipeline which may not always be necessary.

/cc: @sima-zhu does this also solves the following - #29271

/cc: @sima-zhu does this also solves the following - #29271

Yes, @pallavit We have excluded track 1 packages running the azure-core pipeline.
For core pipeline, we implemented a new msbuild target. Basically, the packages we fetched now satisfy two things:

The test package has a dependency on core.
The test package is client library.

I think we can close the https://github.com/Azure/azure-sdk-for-net/issues/29271, as it is being addressed by the PR: https://github.com/Azure/azure-sdk-for-net/pull/29957

Thank you for sharing the details. I have closed the issue this your PR has now been merged.