sonarr: avoid fetch-deps in updateScript

Description of changes
There seems to be something wrong with the performance of passthru.fetch-deps (perhaps after the recent refactors in #327651?). For sonarr package, we can avoid future regressions (and using nix build/nix develop from update script) by running nuget-to-nix directly since we already have an ad-hoc update script.
Before:
$ updateScript=$(nix build --no-link --print-out-paths --file . sonarr.updateScript)
$ time "$updateScript"
(output omitted, runs unrelated yarn hooks as well)
real    12m16.377s
user    1m59.283s
sys     0m57.620s

After:
$ updateScript=$(nix build --no-link --print-out-paths --file . sonarr.updateScript)
$ time "$updateScript"
(output omitted)
real    3m31.448s
user    1m33.406s
sys     0m36.634s

Related:

https://github.com/NixOS/nixpkgs/pull/338719#pullrequestreview-2276794947

Things done

Built on platform(s)

[ ] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

If that's not the case, I'd like to investigate the performance problem.

@corngood, the performance regressions seems to be caused by --disable-parallel flag (we don’t inherit enableParallelBuilding argument in buildDotnetModule, but previous fetch-deps implementation was using it).

$ git diff --no-ext-diff
diff --git a/pkgs/build-support/dotnet/build-dotnet-module/default.nix b/pkgs/build-support/dotnet/build-dotnet-module/default.nix
index 418c90c64899..e36e339dfa7f 100644
--- a/pkgs/build-support/dotnet/build-dotnet-module/default.nix
+++ b/pkgs/build-support/dotnet/build-dotnet-module/default.nix
@@ -147,6 +147,8 @@ let
       dotnetUseAppHost = useAppHost;
       inherit useDotnetFromEnv;

+      inherit enableParallelBuilding;
+
       nativeBuildInputs = args.nativeBuildInputs or [ ] ++ [
         dotnetConfigureHook
         dotnetBuildHook
diff --git a/pkgs/by-name/so/sonarr/update.py b/pkgs/by-name/so/sonarr/update.py
index 195a2d5d05ac..9996e9cd3b22 100644
--- a/pkgs/by-name/so/sonarr/update.py
+++ b/pkgs/by-name/so/sonarr/update.py
@@ -152,7 +152,7 @@ with tempfile.TemporaryDirectory() as work_dir:
             fetch_deps,
             deps_file,
         ],
-        stdout=subprocess.DEVNULL,
+        # stdout=subprocess.DEVNULL,
         check=True,
     )

$ nix build --file . sonarr.updateScript
$ time ./result
structuredAttrs is enabled
Running phase: createNugetDirs
The template "NuGet Config" was created successfully.

Processing post-creation actions...

Package source with Name: _nix added successfully.
Running phase: unpackPhase
unpacking source archive /nix/store/y3qvfp3n67d2sm0xl9zfzdl3q2q759hf-source
source root is source
Running phase: patchPhase
applying patch /nix/store/gaf5kjl5nb2gqvcmwk12qv5ap8lra3rf-nuget-config.patch
patching file NuGet.Config (renamed from src/NuGet.Config)
Running phase: configureNuget
Running phase: updateAutotoolsGnuConfigScriptsPhase
Running phase: configurePhase
Executing dotnetConfigureHook
Package source with Name: _nix added successfully.
  Determining projects to restore...
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.RuntimePatches/Sonarr.RuntimePatches.csproj (in 12.74 sec).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common/Sonarr.Common.csproj (in 22.78 sec).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Core/Sonarr.Core.csproj (in 1.62 min).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.SignalR/Sonarr.SignalR.csproj (in 1.62 min).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.Http/Sonarr.Http.csproj (in 1.66 min).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.Api.V3/Sonarr.Api.V3.csproj (in 1.66 min).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Console/Sonarr.Console.csproj (in 1.66 min).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Host/Sonarr.Host.csproj (in 1.66 min).
  Determining projects to restore...
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.RuntimePatches/Sonarr.RuntimePatches.csproj (in 377 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common/Sonarr.Common.csproj (in 377 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.SignalR/Sonarr.SignalR.csproj (in 387 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Core/Sonarr.Core.csproj (in 387 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.Http/Sonarr.Http.csproj (in 425 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Host/Sonarr.Host.csproj (in 426 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.Api.V3/Sonarr.Api.V3.csproj (in 426 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Console/Sonarr.Console.csproj (in 427 ms).
  Determining projects to restore...
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.RuntimePatches/Sonarr.RuntimePatches.csproj (in 375 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common/Sonarr.Common.csproj (in 375 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.SignalR/Sonarr.SignalR.csproj (in 407 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Core/Sonarr.Core.csproj (in 408 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.Http/Sonarr.Http.csproj (in 461 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.Api.V3/Sonarr.Api.V3.csproj (in 461 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Host/Sonarr.Host.csproj (in 466 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Console/Sonarr.Console.csproj (in 469 ms).
  Determining projects to restore...
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common/Sonarr.Common.csproj (in 404 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.RuntimePatches/Sonarr.RuntimePatches.csproj (in 405 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.SignalR/Sonarr.SignalR.csproj (in 425 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Core/Sonarr.Core.csproj (in 425 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.Http/Sonarr.Http.csproj (in 492 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.Api.V3/Sonarr.Api.V3.csproj (in 495 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Host/Sonarr.Host.csproj (in 497 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Console/Sonarr.Console.csproj (in 500 ms).
  Determining projects to restore...
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common/Sonarr.Common.csproj (in 216 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Mono/Sonarr.Mono.csproj (in 3.78 sec).
  Determining projects to restore...
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common/Sonarr.Common.csproj (in 248 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Mono/Sonarr.Mono.csproj (in 248 ms).
  Determining projects to restore...
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Mono/Sonarr.Mono.csproj (in 267 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common/Sonarr.Common.csproj (in 267 ms).
  Determining projects to restore...
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common/Sonarr.Common.csproj (in 267 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Mono/Sonarr.Mono.csproj (in 267 ms).
  Determining projects to restore...
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common/Sonarr.Common.csproj (in 360 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Core/Sonarr.Core.csproj (in 380 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.SignalR/Sonarr.SignalR.csproj (in 380 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.Http/Sonarr.Http.csproj (in 431 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.Api.V3/Sonarr.Api.V3.csproj (in 431 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Test.Common/Sonarr.Test.Common.csproj (in 2.94 sec).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Api.Test/Sonarr.Api.Test.csproj (in 6.25 sec).
  Determining projects to restore...
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common/Sonarr.Common.csproj (in 347 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.SignalR/Sonarr.SignalR.csproj (in 358 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Core/Sonarr.Core.csproj (in 358 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Test.Common/Sonarr.Test.Common.csproj (in 359 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.Http/Sonarr.Http.csproj (in 396 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Api.Test/Sonarr.Api.Test.csproj (in 396 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.Api.V3/Sonarr.Api.V3.csproj (in 397 ms).
  Determining projects to restore...
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common/Sonarr.Common.csproj (in 380 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Core/Sonarr.Core.csproj (in 395 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.SignalR/Sonarr.SignalR.csproj (in 395 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Test.Common/Sonarr.Test.Common.csproj (in 399 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.Http/Sonarr.Http.csproj (in 448 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.Api.V3/Sonarr.Api.V3.csproj (in 450 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Api.Test/Sonarr.Api.Test.csproj (in 453 ms).
  Determining projects to restore...
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common/Sonarr.Common.csproj (in 381 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Core/Sonarr.Core.csproj (in 406 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Test.Common/Sonarr.Test.Common.csproj (in 407 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.SignalR/Sonarr.SignalR.csproj (in 406 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.Http/Sonarr.Http.csproj (in 463 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.Api.V3/Sonarr.Api.V3.csproj (in 464 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Api.Test/Sonarr.Api.Test.csproj (in 463 ms).
  Determining projects to restore...
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Test.Dummy/Sonarr.Test.Dummy.csproj (in 272 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common/Sonarr.Common.csproj (in 411 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Core/Sonarr.Core.csproj (in 503 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.SignalR/Sonarr.SignalR.csproj (in 510 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Test.Common/Sonarr.Test.Common.csproj (in 513 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.Http/Sonarr.Http.csproj (in 638 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Host/Sonarr.Host.csproj (in 647 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.Api.V3/Sonarr.Api.V3.csproj (in 653 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common.Test/Sonarr.Common.Test.csproj (in 657 ms).
  Determining projects to restore...
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Test.Dummy/Sonarr.Test.Dummy.csproj (in 294 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common/Sonarr.Common.csproj (in 329 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Core/Sonarr.Core.csproj (in 362 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Test.Common/Sonarr.Test.Common.csproj (in 363 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.SignalR/Sonarr.SignalR.csproj (in 362 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.Http/Sonarr.Http.csproj (in 396 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.Api.V3/Sonarr.Api.V3.csproj (in 400 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common.Test/Sonarr.Common.Test.csproj (in 399 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Host/Sonarr.Host.csproj (in 400 ms).
  Determining projects to restore...
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Test.Dummy/Sonarr.Test.Dummy.csproj (in 279 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common/Sonarr.Common.csproj (in 346 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.SignalR/Sonarr.SignalR.csproj (in 395 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Core/Sonarr.Core.csproj (in 395 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Test.Common/Sonarr.Test.Common.csproj (in 400 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.Http/Sonarr.Http.csproj (in 449 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.Api.V3/Sonarr.Api.V3.csproj (in 453 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Host/Sonarr.Host.csproj (in 453 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common.Test/Sonarr.Common.Test.csproj (in 457 ms).
  Determining projects to restore...
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Test.Dummy/Sonarr.Test.Dummy.csproj (in 294 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common/Sonarr.Common.csproj (in 353 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.SignalR/Sonarr.SignalR.csproj (in 409 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Test.Common/Sonarr.Test.Common.csproj (in 410 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Core/Sonarr.Core.csproj (in 409 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.Http/Sonarr.Http.csproj (in 463 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Host/Sonarr.Host.csproj (in 465 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.Api.V3/Sonarr.Api.V3.csproj (in 466 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common.Test/Sonarr.Common.Test.csproj (in 466 ms).
  Determining projects to restore...
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common/Sonarr.Common.csproj (in 295 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Core/Sonarr.Core.csproj (in 313 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Test.Common/Sonarr.Test.Common.csproj (in 315 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Core.Test/Sonarr.Core.Test.csproj (in 359 ms).
  Determining projects to restore...
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common/Sonarr.Common.csproj (in 299 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Core/Sonarr.Core.csproj (in 309 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Test.Common/Sonarr.Test.Common.csproj (in 312 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Core.Test/Sonarr.Core.Test.csproj (in 331 ms).
  Determining projects to restore...
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common/Sonarr.Common.csproj (in 316 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Core/Sonarr.Core.csproj (in 338 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Test.Common/Sonarr.Test.Common.csproj (in 339 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Core.Test/Sonarr.Core.Test.csproj (in 375 ms).
  Determining projects to restore...
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common/Sonarr.Common.csproj (in 314 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Core/Sonarr.Core.csproj (in 336 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Test.Common/Sonarr.Test.Common.csproj (in 339 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Core.Test/Sonarr.Core.Test.csproj (in 374 ms).
  Determining projects to restore...
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common/Sonarr.Common.csproj (in 378 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Core/Sonarr.Core.csproj (in 406 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.SignalR/Sonarr.SignalR.csproj (in 406 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Test.Common/Sonarr.Test.Common.csproj (in 406 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.Http/Sonarr.Http.csproj (in 470 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Host.Test/Sonarr.Host.Test.csproj (in 471 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.Api.V3/Sonarr.Api.V3.csproj (in 477 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Host/Sonarr.Host.csproj (in 480 ms).
  Determining projects to restore...
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.SignalR/Sonarr.SignalR.csproj (in 418 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common/Sonarr.Common.csproj (in 412 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Core/Sonarr.Core.csproj (in 416 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Test.Common/Sonarr.Test.Common.csproj (in 422 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Host.Test/Sonarr.Host.Test.csproj (in 459 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.Http/Sonarr.Http.csproj (in 461 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.Api.V3/Sonarr.Api.V3.csproj (in 461 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Host/Sonarr.Host.csproj (in 460 ms).
  Determining projects to restore...
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common/Sonarr.Common.csproj (in 394 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Test.Common/Sonarr.Test.Common.csproj (in 424 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Core/Sonarr.Core.csproj (in 421 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.SignalR/Sonarr.SignalR.csproj (in 421 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.Http/Sonarr.Http.csproj (in 492 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Host.Test/Sonarr.Host.Test.csproj (in 491 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.Api.V3/Sonarr.Api.V3.csproj (in 494 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Host/Sonarr.Host.csproj (in 495 ms).
  Determining projects to restore...
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common/Sonarr.Common.csproj (in 431 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.SignalR/Sonarr.SignalR.csproj (in 451 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Core/Sonarr.Core.csproj (in 451 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Test.Common/Sonarr.Test.Common.csproj (in 453 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.Http/Sonarr.Http.csproj (in 501 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Host/Sonarr.Host.csproj (in 503 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.Api.V3/Sonarr.Api.V3.csproj (in 502 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Host.Test/Sonarr.Host.Test.csproj (in 502 ms).
  Determining projects to restore...
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common/Sonarr.Common.csproj (in 303 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Core/Sonarr.Core.csproj (in 330 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Test.Common/Sonarr.Test.Common.csproj (in 331 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Libraries.Test/Sonarr.Libraries.Test.csproj (in 378 ms).
  Determining projects to restore...
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common/Sonarr.Common.csproj (in 312 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Core/Sonarr.Core.csproj (in 324 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Test.Common/Sonarr.Test.Common.csproj (in 325 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Libraries.Test/Sonarr.Libraries.Test.csproj (in 346 ms).
  Determining projects to restore...
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common/Sonarr.Common.csproj (in 317 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Core/Sonarr.Core.csproj (in 337 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Test.Common/Sonarr.Test.Common.csproj (in 337 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Libraries.Test/Sonarr.Libraries.Test.csproj (in 374 ms).
  Determining projects to restore...
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common/Sonarr.Common.csproj (in 333 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Core/Sonarr.Core.csproj (in 348 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Test.Common/Sonarr.Test.Common.csproj (in 351 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Libraries.Test/Sonarr.Libraries.Test.csproj (in 389 ms).
  Determining projects to restore...
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Test.Dummy/Sonarr.Test.Dummy.csproj (in 304 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common/Sonarr.Common.csproj (in 483 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Mono/Sonarr.Mono.csproj (in 489 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.SignalR/Sonarr.SignalR.csproj (in 576 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Core/Sonarr.Core.csproj (in 583 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Test.Common/Sonarr.Test.Common.csproj (in 591 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.Api.V3/Sonarr.Api.V3.csproj (in 744 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.Http/Sonarr.Http.csproj (in 769 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Mono.Test/Sonarr.Mono.Test.csproj (in 769 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Host/Sonarr.Host.csproj (in 770 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common.Test/Sonarr.Common.Test.csproj (in 770 ms).
  Determining projects to restore...
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Test.Dummy/Sonarr.Test.Dummy.csproj (in 326 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common/Sonarr.Common.csproj (in 363 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Mono/Sonarr.Mono.csproj (in 363 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.SignalR/Sonarr.SignalR.csproj (in 392 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Test.Common/Sonarr.Test.Common.csproj (in 392 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Core/Sonarr.Core.csproj (in 392 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.Http/Sonarr.Http.csproj (in 439 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Host/Sonarr.Host.csproj (in 439 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common.Test/Sonarr.Common.Test.csproj (in 439 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Mono.Test/Sonarr.Mono.Test.csproj (in 439 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.Api.V3/Sonarr.Api.V3.csproj (in 439 ms).
  Determining projects to restore...
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Test.Dummy/Sonarr.Test.Dummy.csproj (in 312 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common/Sonarr.Common.csproj (in 389 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Mono/Sonarr.Mono.csproj (in 390 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.SignalR/Sonarr.SignalR.csproj (in 435 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Core/Sonarr.Core.csproj (in 436 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Test.Common/Sonarr.Test.Common.csproj (in 441 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.Http/Sonarr.Http.csproj (in 506 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Host/Sonarr.Host.csproj (in 509 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Mono.Test/Sonarr.Mono.Test.csproj (in 509 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.Api.V3/Sonarr.Api.V3.csproj (in 509 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common.Test/Sonarr.Common.Test.csproj (in 510 ms).
  Determining projects to restore...
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Test.Dummy/Sonarr.Test.Dummy.csproj (in 314 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Mono/Sonarr.Mono.csproj (in 390 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common/Sonarr.Common.csproj (in 399 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Test.Common/Sonarr.Test.Common.csproj (in 437 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.SignalR/Sonarr.SignalR.csproj (in 438 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Core/Sonarr.Core.csproj (in 445 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.Http/Sonarr.Http.csproj (in 513 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common.Test/Sonarr.Common.Test.csproj (in 508 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/Sonarr.Api.V3/Sonarr.Api.V3.csproj (in 514 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Host/Sonarr.Host.csproj (in 515 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Mono.Test/Sonarr.Mono.Test.csproj (in 508 ms).
  Determining projects to restore...
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common/Sonarr.Common.csproj (in 305 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Core/Sonarr.Core.csproj (in 319 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Test.Common/Sonarr.Test.Common.csproj (in 322 ms).
  Determining projects to restore...
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common/Sonarr.Common.csproj (in 275 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Test.Common/Sonarr.Test.Common.csproj (in 286 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Core/Sonarr.Core.csproj (in 287 ms).
  Determining projects to restore...
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common/Sonarr.Common.csproj (in 299 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Core/Sonarr.Core.csproj (in 313 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Test.Common/Sonarr.Test.Common.csproj (in 315 ms).
  Determining projects to restore...
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Common/Sonarr.Common.csproj (in 325 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Test.Common/Sonarr.Test.Common.csproj (in 353 ms).
  Restored /tmp/tmp.Zis7TQuzD1/source/src/NzbDrone.Core/Sonarr.Core.csproj (in 354 ms).
yarn config v1.22.22
success Set "yarn-offline-mirror" to "/nix/store/c3r7901ccdnmcw23j735jn5igfgijxcb-offline".
Done in 0.04s.
yarn install v1.22.22
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "react-dnd-multi-backend ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "react-dnd-multi-backend ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "react-document-title ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^0.14.0 || ^15.0.0 || ^16.0.0".
warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^15.0.0 || ^16.0.0".
warning "react-popper ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^15.0.0 || ^16.0.0".
warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^16.0.0-alpha".
warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^16.0.0-alpha".
[4/4] Building fresh packages...
warning Ignored scripts due to flag.
Done in 12.60s.
patching script interpreter paths in node_modules
<EMAIL_ADDRESS>interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
<EMAIL_ADDRESS>interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
<EMAIL_ADDRESS>interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
<EMAIL_ADDRESS>interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
<EMAIL_ADDRESS>interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
<EMAIL_ADDRESS>interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/acorn/bin/acorn: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/autoprefixer/node_modules/browserslist/cli.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/autoprefixer/node_modules/update-browserslist-db/cli.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/autoprefixer/bin/autoprefixer: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/browserslist/cli.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/clipboard/.husky/pre-commit: interpreter directive changed from "#!/bin/sh" to "/nix/store/w7r5zwsyfrd99sbnfr7zrg7xhv8gq7nf-bash-5.2p32/bin/sh"
node_modules/core-js-compat/node_modules/browserslist/cli.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/core-js-compat/node_modules/update-browserslist-db/cli.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/crc-32/bin/crc32.njs: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/css-loader/node_modules/semver/bin/semver.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/css-modules-typescript-loader/node_modules/json5/lib/cli.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/cssesc/bin/cssesc: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/del/node_modules/rimraf/bin.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/envinfo/dist/cli.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/errno/build.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/errno/cli.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/eslint/bin/eslint.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/eslint-config-prettier/bin/cli.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/eslint-plugin-react/node_modules/resolve/bin/resolve: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/flat-cache/node_modules/rimraf/bin.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/flat/cli.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/fork-ts-checker-webpack-plugin/node_modules/semver/bin/semver.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/global-prefix/node_modules/which/bin/which: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/he/bin/he: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/html-minifier-terser/cli.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/image-size/bin/image-size.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/import-local/fixtures/cli.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/jiti/bin/jiti.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/jsesc/bin/jsesc: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/js-yaml/bin/js-yaml.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/loose-envify/cli.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/mime/cli.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/json5/lib/cli.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/less/node_modules/mime/src/build.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/less/node_modules/mime/cli.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/less/node_modules/semver/bin/semver: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/less/bin/lessc: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/nanoid/bin/nanoid.cjs: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/needle/bin/needle: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/mkdirp/bin/cmd.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/normalize-package-data/node_modules/semver/bin/semver.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/postcss-loader/node_modules/semver/bin/semver.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/prettier/bin-prettier.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/read-pkg/node_modules/semver/bin/semver: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/regjsparser/node_modules/jsesc/bin/jsesc: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/regjsparser/bin/parser: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/resolve/bin/resolve: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/rgb/bin/rgb: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/rimraf/dist/cjs/src/bin.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/semver/bin/semver.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/sass/sass.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/stylelint/bin/stylelint.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/stylus/bin/stylus: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/terser/bin/terser: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/terser/bin/uglifyjs: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/ts-loader/node_modules/semver/bin/semver.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/tsconfig-paths/node_modules/json5/lib/cli.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/typescript/bin/tsc: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/typescript/bin/tsserver: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/update-browserslist-db/cli.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/webpack/bin/webpack.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/webpack-cli/bin/cli.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
node_modules/which/bin/node-which: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/rbv8jmnhifp2znxc4issvl7zgmy7f24j-nodejs-20.16.0/bin/node"
Finished dotnetConfigureHook
configurePhase completed in 2 minutes 43 seconds
Succesfully wrote lockfile to /tmp/tmpl4u98bmj/deps.nix

real    4m48.263s
user    2m21.308s
sys     1m0.759s

I don't think I like this idea. It makes the package much more of an outlier in terms of how it interacts with the dotnet infrastructure, and will be difficult to maintain.

Ideally, I’d like to use some prefetch-dotnet-deps script on the prefetched source (similar to prefetch-yarn-deps) instead of fetch-deps building all dependencies and starting an entire development shell with stdenv, phases, hooks and whatnot. E.g. the current fetch-deps implementation runs completely unrelated yarn postConfigure hook that we use for Sonarr frontend (see log above) and it’s hard to compose fetch-deps with different language ecosystems and tools in general. Running dotnet restore & nuget-to-nix decouples update process from Nix derivations, but some tool to encapsulate this would definitely be useful (parametrized by projects & runtime IDs).

I think what you're seeing with the timings is just the fact that by default, fetch-deps restores for all supported RIDs, and with your custom fetcher, it's only using one.

This shouldn’t be the case, updateScript is using the same list of projects, runtime IDs, and dotnet flags (but from nix eval instead of nix develop/nix-shell).
nix repl:

nix repl
Nix 2.22.1
Type :? for help.
nix-repl> :l .
Added 22560 variables.

nix-repl> sonarr.meta.platforms
[
  "aarch64-darwin"
  "aarch64-linux"
  "x86_64-darwin"
  "x86_64-linux"
]

nix-repl> sonarr.dotnetProjectFiles ++ sonarr.dotnetTestProjectFiles
[
  "src/NzbDrone.Console/Sonarr.Console.csproj"
  "src/NzbDrone.Mono/Sonarr.Mono.csproj"
  "src/NzbDrone.Api.Test/Sonarr.Api.Test.csproj"
  "src/NzbDrone.Common.Test/Sonarr.Common.Test.csproj"
  "src/NzbDrone.Core.Test/Sonarr.Core.Test.csproj"
  "src/NzbDrone.Host.Test/Sonarr.Host.Test.csproj"
  "src/NzbDrone.Libraries.Test/Sonarr.Libraries.Test.csproj"
  "src/NzbDrone.Mono.Test/Sonarr.Mono.Test.csproj"
  "src/NzbDrone.Test.Common/Sonarr.Test.Common.csproj"
]

update.py:

https://github.com/NixOS/nixpkgs/blob/33684688f1f911dda15574ed0138f6ddde52821a/pkgs/by-name/so/sonarr/update.py#L58-L60
https://github.com/NixOS/nixpkgs/blob/33684688f1f911dda15574ed0138f6ddde52821a/pkgs/by-name/so/sonarr/update.py#L141-L155

dotnet-configure-hook:

https://github.com/NixOS/nixpkgs/blob/d52e3211304fe654f251864d6dd2cabbef321568/pkgs/build-support/dotnet/build-dotnet-module/hooks/dotnet-configure-hook.sh#L70-L71
https://github.com/NixOS/nixpkgs/blob/d52e3211304fe654f251864d6dd2cabbef321568/pkgs/build-support/dotnet/build-dotnet-module/hooks/dotnet-configure-hook.sh#L29-L30

fetch-deps building all dependencies and starting an entire development shell with stdenv, phases, hooks and whatnot

Without doing this, it seems like it would be difficult to identify nuget package dependencies that are provided by those dependencies (buildInputs) and wired up with the dotnet hooks.


fix save avatar

fixed save avatar image not loaded  try to open it externally to fix format problem
if response content length is 0, an error is reported.

即使重试也不一定能获取到头像，
https://github.com/Urinx/WeixinBot/issues/85


Added an url_prefix setting

Not sure if this is worth merging (perhaps I simply missed anything in the docs/configuration), but I ran into a situation where the URL's returned by LFM weren't correct. Belows are the steps to reproduce and a PR fixing this issue.
Steps to reproduce

Setting base_directory to storage/app/public
Leave images_folder_name and files_folder_name to defaults
Create the default symlink in Laravel using php artisan storage:link
Upload an image using the editor
Insert an image in CKEditor or any editor of choice

The problem
The full URL to the image being returned ends up being http://yoursite.com/photos/1/12345.jpg for example. While the generated symlink expects the URL to be http://yoursite.com/storage/photos/1/123456.jpg.
The suggested fix (in the PR)

Adding a url_prefix setting to the configuration file
Setting the value of url_prefix to (in this case) "storage"
Get the getFileUrl()method in LfmHelpers.php to prefix the URL using the url_prefix configuration value
End up having the correct link

For some strange reason, this setting "url_prefix" already exists.. while not being documented (as far as I can see) it's within LfmHelpers.php:L113


NaN detected in cls_loss for decoder 0, skipping

Hi, I am training SparseDrive with my own dataset.  During stage 1,  the objection detection and map detection can converge。 But in the middle of training, Nan is detected,  is there any idea to avoid this problem?  I am using 8 A100 for stage 1 training.
NaN detected in cls_loss for decoder 0, skipping.
NaN detected in cls_loss for decoder 1, skipping.
NaN detected in cls_loss for decoder 2, skipping.
NaN detected in cls_loss for decoder 3, skipping.
NaN detected in cls_loss for decoder 4, skipping.
NaN detected in cls_loss for decoder 5, skipping.
Traceback (most recent call last):
File "tools/train.py", line 321, in
main()
File "tools/train.py", line 296, in main
custom_train_model(

I met the same problem using 4 H20 for stage 1 training.

Thanks for feedback.   I already fix the problem. My custom dataset has NaN in box' velocity.


Add Button Functionality to Pagination Next/Prev/First/Last Buttons

Ignore, unless main features implemented.


Add special logic for pdbs without /names stream

Fix for #270.
I've tested this stuff manually for generated pdb without /names stream, ran all the tests to check regression.

@tom-englert, @sharwell, @hubuk would appreciate some feedback from you, guys:)

I didn't try it out, but LGTM. I left two comments about small things to consider before merging.

@sharwell Thanks for the review. Unfortunately, no tests for this fix. The only way I can think about them is to add "broken" pdb, but that definitely not the best approach!


Test and migrate Docker registry example to 1.9.

I'll take a stab at this.

Thanks for taking this example on, Augustine!
I've noticed there hasn't been a pull request submitted yet, do you need any help, or just need some more time? If you ran into a problem, updating this issue to explain would be a huge help so we can try to assist you.
If something came up and you aren't able to complete updating this example, no problem! Just let us know that so we can assign it to another community member. We'll look forward to working with you next time :)

Hi @pleia2 . I did take it for a spin but got stuck in the first few lines. Since I was testing this on both AWS and Azure, there is an action  at the start on creating a self signed certificate in the bootstrap node. But no such node is created on the Azure or AWS deploy. Before I had a chance to apply any thought, got caught up in greenkeeper whack-a-mole with my other OSS projects that I maintain.

Thanks for this update, do you think you'll be able to take a look at this a bit closer anytime soon, or should we ask someone else to take over? Either way, thanks for giving it a try! :smiley:

Digging into this one, it is indeed a very complex example, a WIP PR is up at #185

PR here https://github.com/dcos/examples/pull/186
@pleia2 @ryadav88


How can i add d3.js charts in the gadget?

How to add d3.js charts with given gadget in this framework instead of ngx-chart.
Please, share any link or explain the steps.

Don't have a link but may have an example. You could also look at the source for NGX Charts which is based on D3.

Follow the instructions in this project's readme for adding a new gadget and then review the following article. This article is pretty straightforward: https://medium.com/@jeanphilippelemieux/creating-a-responsive-graph-with-angular-and-d3-b45bb8065588
D3 is already part of this project so there will be no need to install it. Try it out and if you get it working contribute it back to this project.


Testing of Develop branch of XC3 before merging into main branch.

User stories
#1 As a DevOps engineer, I have to test develop branch of XC3 by deploying it to dev and prod environment.
Acceptance Criteria
What must be achieved to consider this story complete?

[x] Deploy XC3 into dev and prod Environment.
[x] Check grafana dashbaord to see everything is working correctly.
[x] Run Drata test and make sure all test are passed.
[ ] Create PR and merge it to Main branch of XC3.

Grafana Dashboard.

Everything is okay. Here is results for Drata tests.


chore(deps): use uWebSockets.js as peer dependency

This is a good idea and I had the same thing in mind. But we need to add uWebSockets.js package to testbed/basic/package.json otherwise tests won't run properly.
Also you need to run pnpm install after package.json changes otherwise the lockfile will become stale.

@cyco130 commit done

Thank you for your contribution!


fix: corrected cookies functionality, hyperlinks and shown appropriate content in footer (#1070)

closes #1070
👷🏻 Changes made
Corrected cookie names all around code and fixed backend code that fixes this issue.

📸 Screenshots
Before Logging in 👇

After logging in 👇

@tamalCodes Is this good?

@tamalCodes You mentioned the backend  clears the isLoggedIn cookie but it doesn't which also raises issues with sign in and signup button visibility after logging out, but as you mentioned you are working on it, I am not going to modify anything in backend.
Let me modify the code to create new PR

It's been great contributing this project, I apologise for the delay.


Why will the filter bar be visible

The Question
Why is the filter bar visible?

Can anybody label this as 'Issue-Question' and remove the label 'Issue-Feature'?

What filter bar are you referring to?

This bar

Oh, sorry, wrong repository.


[BP-1.12][FLINK-23954][tests] Fix e2e test test_queryable_state_restart_tm.sh

Backport of #17027 to release-1.12.

The test failure seems to be unrelated. Merging this PR now.


Update technical-reference-details-about-encryption.md

Updated the statement for TLS 1.3, which is supported by some but not all the services.

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks

@KCCross Please merge this PR. Thanks

Happy to merge this PR as we've been working on 1.3 support for some time. Please identify which services support 1.3 as the roll out continues. Thank you!


Parser hang on invalid input

The following hangs rather than succeeding or failing:
parseOnly Net.IPv6.Text.parser "1111:2222:3333:4444:5555:6666::7777:8888"

Forcing just to Left or Right also fails:
either (const "L") (const "R") $ parseOnly Net.IPv6.Text.parser "1111:2222:3333:4444:5555:6666::7777:8888"

Actually, the parse itself is fine, producing Right, but forcing the parse result hangs.

Sorry, I just realized that I wasn't previously receiving notifications for this repo. I'll add a test case for this and figure out what's wrong.


Add the ability to programmatically filter the available target SQL version in sql-database-project extension

When creating a SQL Project in ADS the available Target Platforms are SQL 2005  to SQL 2019, Azure SQL Database and Azure SQL Data Warehouse.
Other extensions leveraging the sql-database-project might not support all the versions listed above as a target and would need to have the ability to filter only specific version at SQL project creation. This would bring clarity  on supported targets for the customers using the custom extensions and avoid surfacing errors related to that.
@nahk-ivanov

Before this we need to have a target version selection in the project creation dialog and and ability to call it programmatically. Original suggestion was to use existing projects.new command but with the command we cannot pass any arguments neither can we collect the result (name of the newly created project). It seems like the API to create the project comes from generic data-workspace extension, so I assume we will need to have API over there to be able to popup the dialog with preselected project type (SQL proj and not some other project), but then how is it going to know the version filter (which is SQL-specific)? I think we should expose this API from 'SQL Database Project' extension, so that it (the API) can be customized for just SQL projects.


I crashed while calling try file.parsesharedstrings () with an error:

I crashed while calling try file.parsesharedstrings () with an error:
keyNotFound(CodingKeys(stringValue: "uniqueCount", intValue: nil), Swift.DecodingError.Context(codingPath: [CodingKeys(stringValue: "uniqueCount", intValue: nil)], debugDescription: "No attribute or element found for key CodingKeys(stringValue: \"uniqueCount\", intValue: nil) (\"uniqueCount\").", underlyingError: nil))"

test.xlsx
this is test file.

Hi @linkfei, thank you very much for reporting this. This issue is now fixed in master in #78. By the way, would you mind if I add your file to our test suite?

@MaxDesiatov  Thanks ! No problem !

When will it be updated?

Thanks !


Documentation might be outdated for -v

The manual says -v takes a number:
https://github.com/containers/krunvm/blob/v0.2.3/docs/krunvm.1.txt#L39-L40
*-v* _NUM_::
  Sets the verbosity level, from the lowest (0) to the highest (5).

but trying -v 5 results in:
error: Found argument '5' which wasn't expected, or isn't valid in this context

From the looks of it, it isn't even implemented. https://github.com/containers/krunvm/blob/main/src/main.rs#L153


[harfbuzz] Fix CMake config

What does your PR fix?
Fixes #23694. Alternative to #23709.
This is my minimal version of the fix. The config provides variables likes a find module. Some of these variables should be set as (global) cache variables, some should always be set because they are scoped. Only the target can be skipped if it already exists.
(Note: Trying to complement this port with a test port indicates that the config still needs significant work to be complete, so I decided to only offer a minimal fix now. Even FindICU.cmake doesn't provide release+debug config or transitive usage requirements. And the provided config is "unofficial" - there is a semi-deprecated official config which provides additonal targets.)

Which triplets are supported/not supported? Have you updated the CI baseline?
unchanged

Does your PR follow the maintainer guide?
yes

If you have added/updated a port: Have you run ./vcpkg x-add-version --all and committed the result?
yes

Thanks! This was really annoying -- so happy to see it fixed :)


[Suggestion] Collect tech companies guides on their green guidlines

This proposal was brainstormed during the TAG project meeting at KubeCon EU in Amsterdam

Description
The idea is pretty simple: We call for contribution and ask all "big tech" companies for their green IT guidelines or paragraphs within their Sustainability Guidelines.
From the response, we will draft a template that others can use.
Impact
Scope
The effort behind it will be large as we have to track the outreach and responses. Putting everything together and so on.
Additional info and comments
We need to discuss if this is still within our scope.
No further deep thoughts are made on this, should be handled with care.

P.S.: I'm just the facilitator of this suggestion.

I think this would fit into the Comms WG
WDYT @caradelia ?

I will close this since we are starting a project with this purpose #361


Sync conflicts are ignored and overwritten without warning

I edited a task on my phone, then straight away edited the task in Nextcloud before the phone synced. Once the phone synced with nextcloud the edits made on phone were gone without warning. This seems prone to problems with missing data and unexpected results.

I agree this is annoying. However, sync conflicts must be handled by the sync app. OpenTasks doesn't know anything about the task status on the server.
Early next year I'm going to work on a new sync algorithm for your own apps which reduces the chances of a sync conflict because it syncs on a much finer granularity. This way we can avoid data loss in many situations when we're currently overriding data.

I think this issue happened to me today. I believe what happened is that Davx5 was set to manual sync when I set the synch to daily/when local task is update, the up to date tasks in my phone were rewritten by the outdated tasks found on the Nextcloud server.
I guess there is no way to restore the local content?


recv() cpu abuse

Hello. I'm new with Rust. 20 recv()  uses 40% cpu on my linux box. Is this a known issue?
extern crate bus;
use bus::Bus;
use std::sync::{Arc, Mutex};
use std::thread;
use std::io;

fn main() {
    let bus: std::sync::Arc<std::sync::Mutex<bus::Bus<usize>>>
        = Arc::new(Mutex::new(Bus::new(10)));

    for _ in 0..20 {
        let mut rxb = bus.clone().lock().unwrap().add_rx();
        thread::spawn(move || loop {
            let msg = rxb.recv().unwrap();
        });
    }

    io::stdin().read_line(&mut String::new()).unwrap();
}

total
11909 root      20   0 1029148   1980   1700 S  39.2   0.1   1:01.07 bus_possible_bu

per thread
11926 root      20   0 1029148   1980   1700 R   2.7   0.1   0:00.19 bus_possible_bu
11927 root      20   0 1029148   1980   1700 R   2.7   0.1   0:00.19 bus_possible_bu
11931 root      20   0 1029148   1980   1700 R   2.7   0.1   0:00.19 bus_possible_bu

cpu
model name      : Intel(R) Core(TM) i3 CPU         540  @ 3.07GHz

Ah, yes, those idle cycles stem from https://github.com/jonhoo/bus/blob/ec317a217d7745895cd7b9f95be7f62e20f1ff51/src/lib.rs#L405. There is at least one case where the readers race with the writer and may not successfully wake it up, so the writer has to park with a timeout. I would love to get rid of this, but haven't had a chance to dig into it, and no longer use this library actively myself. If you want to take a look, I'd be happy to help out!

@jonhoo Would be great to note this problem in the README.  With this problem the crate isn't exactly "Efficient". Perhaps suggest an alternative if this crate is no longer maintained.
I like its API, so thanks for putting it up!

@xixixao Would you be up for writing up a quick PR that adds this note to the README? Seems completely reasonable to me :+1:

If anyone has ideas on how to patch/fix this, I'd be interested in helping explore solutions. I moved from ZeroMQ pub-sub to bus to eliminate serialization, and I really like the ergonomics of bus, but am running in a resource constrained "edge" environment where burning cpu cycles actually has operational implications.


brew fails (hangs/stalls/timeouts) when IPv6 GIF network exists at router ("authentication issues")

brew config output
HOMEBREW_VERSION: 3.6.5
ORIGIN: https://github.com/Homebrew/brew
HEAD: fb52a12144e80118c112ea744ab65ab6ca997d67
Last commit: 3 days ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: 8cd7ef45bb5cc49ac27c13b65db2882751b63df2
Core tap last commit: 28 minutes ago
Core tap branch: master
HOMEBREW_PREFIX: /usr/local
HOMEBREW_CASK_OPTS: []
HOMEBREW_DISPLAY: /private/tmp/com.apple.launchd.iYko4kB15c/org.xquartz:0
HOMEBREW_MAKE_JOBS: 12
HOMEBREW_NO_ANALYTICS: set
HOMEBREW_NO_INSTALL_CLEANUP: set
Homebrew Ruby: 2.6.8 => /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby
CPU: dodeca-core 64-bit kabylake
Clang: 14.0.0 build 1400
Git: 2.38.0 => /usr/local/bin/git
Curl: 7.79.1 => /usr/bin/curl
macOS: 12.6-x86_64
CLT: <IP_ADDRESS>.1.1661618636
Xcode: 14.0.1

brew doctor output
Your system is ready to brew.

Verification

[X] I ran brew update and am still able to reproduce my issue.
[X] I have resolved all warnings from brew doctor and that did not fix my problem.

What were you trying to do (and why)?
All fail (hangs/stalls/timeout):
brew install
brew upgrade
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/uninstall.sh)"
Works:
brew update worked.
What happened (include all command output)?
Hangs/stalls/timeouts.  Messages regarding authentication failures (when trying manually with browsers).
What did you expect to happen?
It would work ... with IPv6 over a GIF interface.  It use to work fine.
I apologize if this is not specifically a brew issue, but brew could solve the problem if it could disable IPv6 support (or if I knew how it can).
Step-by-step reproduction instructions (by running brew commands)
If IPv6 is enabled going out over GIF on router, brew fails.

If IPv6 is disabled (entirely), brew works.

I tried the procedure to create an alternate curl using Microsoft vcpkg (?).  No success.

I manually uninstalled brew (brew uninstall script fails as well!).  Ripped all components and directories out.  Disabling IPv6 was only way to brew.

It would be helpful if brew had a configuration setting (or if I knew what it was if there is) to disable IPv6 support.  Difficult to create firewall rules (and Little Snitch appears not to be IP version sensitive).

We don't ship any networking code at all. We invoke curl and git mainly.
I can't really give any advice without seeing exactly what stage it gets stuck at. You've not provided any command output.
If the issue is curl, then you can do echo ipv4 >> ~/.curlrc and then export HOMEBREW_CURLRC=1.


document updated build process

The document docs/BUILD.md was out of date, had some incorrect information, and was missing some. Updated it to describe the build process. This is valuable on its own, but will be followed up with some actual extensions/additions/improvements.

I changed nothing but stuff in docs/ here; why is CI failing?


Tetsubo hands is 2, not 1

In pathfinder nexus the Tetsubo indicates the use of 2 hands instead of 1 as it appears in foundry, for this reason and given the 3 bulk and the fact that the weapon usually measures between 4 and 6 feet, in addition to the fact that its historical zone has always been 2 hands takes me to see the error in the entry

Pathfinder Nexus is not considered a primary source. Please confirm with the printed book prior to making a report in future. Book and page numbers are appreciated in data entry error reports :)
we’ll try to track down a primary source and update if incorrect.


Knopflerfish fails to start if arbitraty working directory contains files with special names

Usually SystemBundle.initSystemBundle() initializes list of packages exported by SystemBundle reading lists contained in internal resource files packages.txt and exports contained in framework.jar using internal method addSysPackagesFromFile . The same method is used to add packages from file given in property org.knopflerfish.framework.system.packages.file . Therefore this method tries to find the file on the disk before it takes the resource from the jar.
final File f = new File(new File(sysPkgFile).getAbsolutePath());

    if (!f.exists() || !f.isFile()) {
      url = SystemBundle.class.getResource(sysPkgFile);
      if (null == url) {
        url = SystemBundle.class.getResource("/" + sysPkgFile);
      }

Unfortunately it causes a failure if the working directory occasionally contains files with matching names. Our users have experienced such failures.
Therefore I ask you to change the above logic so that framework can be started in any directory and it does not depend on its content.
As a work around I am going to temporarily change values of system property user.dir when the framework is initialized and change it back when the first plug-in is being  activated.

Removed resource override from current working directory. Now we require explicit override. Fix available in framework 8.0.3. Download from https://bintray.com/knopflerfish/master/download_file?file_path=distrib_6.0.0.snapshot-1701041603-master%2Fknopflerfish_osgi_sdk_6.0.0.snapshot-1701041603-master.jar


PID loop not going back after reaching 100% cooling output

We have set the Setpoint to 22’C and the initial Return Temperature was at 23’C which the Cooling Valve began to open and started at 14%, this gradually opened until this had reached 100%. By this time the Return Temperature had reduced to 22.4’C with the Valve remaining at 100%.
At this point we then raised the Setpoint to 24’C and you can see by the screenshot we had no change in the Cooling output and the Valve remained at 100% even though the Setpoint was higher than the Return Temperature.
We have set the Deadband for the PID Loop at 0.5’C so the way this should operate is once the Return Temperature is 0.5’C +/- from Setpoint then the PID Loop should begin to close so in the instance of the screenshot attached I would expect the Cooling Output to start going back to 0% and the Heating Output to be enabled once the Cooling Valve has reached 0% but in this case nothing is happening. The Cooling Output is just remaining fully open.
We have also checked the Node Red and the PID Loop is showing a blue button with a stop sign that is flashing on and off and the setpoint has not been changed within the PID Loop from 22’C to 24’C. This may be the reason why the cooling valve is not closing off but it was still at 100% after we made the change and left this for 20mins and by this time the return temperature was now at 22.3’C which is still within deadband of a Setpoint of 22’C.

'[{"id":"16b469ed.ac4976","type":"inject","z":"22b5c7f.df03238","name":"Override TEST - TRUE","topic":"","payload":"true","payloadType":"bool","repeat":"","crontab":"","once":false,"x":143.5,"y":502,"wires":[["90197846.a8b7c8"]]},{"id":"fa6689fa.5af1f","type":"inject","z":"22b5c7f.df03238","name":"InitialSetPoint","topic":"FCU/setpoint4","payload":"22","payloadType":"num","repeat":"","crontab":"","once":true,"x":125.5,"y":465,"wires":[["feefee7a.928178","223b5806.f7691","7698021f.b2768c"]]},{"id":"79f77052.eb804","type":"inject","z":"22b5c7f.df03238","name":"Override TEST - FALSE","topic":"","payload":"false","payloadType":"bool","repeat":"","crontab":"","once":false,"x":155,"y":534,"wires":[["90197846.a8b7c8"]]},{"id":"90197846.a8b7c8","type":"Or","z":"22b5c7f.df03238","topic":"topic","inputCount":"4","x":591.5,"y":375,"wires":[["1876ccc1.4369b3"]]},{"id":"1876ccc1.4369b3","type":"And","z":"22b5c7f.df03238","inputCount":"1","x":715,"y":383,"wires":[["90c82d79.640738","cec74f68.3f0e2","c3294c2a.3ca7f8","6a5cd772.abaf2","c78007b1.38913"]]},{"id":"c3294c2a.3ca7f8","type":"change","z":"22b5c7f.df03238","name":"enable","rules":[{"t":"set","p":"topic","pt":"msg","to":"enable","tot":"str"}],"action":"","property":"","from":"","to":"","reg":false,"x":879.5,"y":370,"wires":[["c0baee8b.f384f8"]]},{"id":"c0baee8b.f384f8","type":"link out","z":"22b5c7f.df03238","name":"EnableDisable","links":["3eb76b10.80a8bc","83ffb985.d7d138","e4fa579b.2d6ef8"],"x":979.5,"y":369,"wires":[]},{"id":"3eb76b10.80a8bc","type":"link in","z":"22b5c7f.df03238","name":"Enableout","links":["c0baee8b.f384f8"],"x":290.5,"y":586,"wires":[["6769fb2c.5d85fc","feefee7a.928178"]]},{"id":"feefee7a.928178","type":"PIDLoop","z":"22b5c7f.df03238","Kp":"10","Ki":"300","Kd":1,"recalcTime":5,"setPointTopic":"FCU/setpoint4","fireTopic":"enable","fixedTopic":"fixed","fixedValue":0,"deadBand":"0.5","x":405.5,"y":560,"wires":[["85ae2d5.bb7875","96e7a62c.56fd7"],["d9145772.8c6758","a2396485.d55f18"]]}]'


iam authenticator with latest aws-sdk-go since proxies does not work

Hi,
This is Badal from AWS Premium Support. One of the customers is having issues with using aws-iam-authenticator.
"""
aws-iam-authenticator currently uses a version of aws-sdk-go that doesn't work with proxies when using custom CA bundles via the AWS_CA_BUNDLE environment variable. This prevents us using IAM authentication with kubectl because our corporate man-in-the-middle proxies require us to set a custom CA bundle.
We believe that using a more recent version of aws-sdk-go will fix this (assuming it includes https://github.com/aws/aws-sdk-go/pull/2343 ), but until then, the official release is broken.
"""
Can you confirm if this is the issue? Is there any way to work-around this issue?
Awaiting your response.

Any update on this?

FYI we're having the same issue as above (I'll be raising this with our Enterprise TAM as well), but it looks like a workaround is to create a wrapper script:
#!/bin/bash

unset AWS_CA_BUNDLE
exec /usr/local/bin/aws-iam-authenticator "$@"

... and then replace the binary in ~/.kube/config with this wrapper script.
NB: Our interception CA is in the system certificate store, YMMV, etc.


Thiet

Product and Version [VS/VSCode]:
OS Version [macOS/Windows]:
Live Share Extension Version:
Target Platform or Language [e.g. Node.js]:
Steps to Reproduce / Scenario:

thiet

Closing this issue due to a lack of actionable details. Please re-open it if you're still encountering an issue. Thanks!


SID detection in Linux

def sid_linux
    cmd = "cat /etc/fstab| awk '$2~ \"sapmnt\" {print $2}' " # Search the fstab table for /sapmnt/ABC pattern
    cmd += "| awk -F / '{print $3}'" # Print only the possible SID on the system.
    shell_out(cmd).stdout.split("\n")
  end

Assumes that the /sapmnt is a separate partition

fixed it by a little hack
  def sid_linux
    cmd = "ls -d /sapmnt/*" # Search the fstab table for /sapmnt/ABC pattern
    cmd += "| awk -F / '{print $3}'" # Print only the possible SID on the system.
    shell_out(cmd).stdout.split("\n")
  end

Hi @kmf
Thanks for your interest!  Would you mind submitting a PR with this change?
Regards,
Dan-Joe

@SAPDanJoe PR is in


build: add workspace extension recommendations and volar config deps

:tada: This PR is included in version 2.0.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add german regions

Please add the two german datacenters.
https://azure.microsoft.com/en-us/blog/microsoft-azure-germany-now-available-via-first-of-its-kind-cloud-for-europe/

Hi @Tevion, thanks for the suggestion.
Unfortunately I'm not able to add the German data centres from my subscription, I assume you need an account in Germany :¬(

From comments under the blog:
"Microsoft Azure Deutschland has a separate Portal not connected to the global environment. Hence Germany regions will not show in Portal(http://portal.azure.com)
You will require a need a German Cloud specific login to provision services in the German regions. To buy and provision services in Germany, Customers must have a billing address in EU/EFTA. If you meet the billing address in EU/EFTA requirement and want to access Germany please contact us on<EMAIL_ADDRESS>to onboard you to Microsoft Cloud Germany. "

@keklabs Thanks, does anyone have an account???


No support for custom test command

Looks like run_tests.sh is hard coded to run swift test... it would be nice if there were support for custom test commands, e.g. for a .swift-test-platform file analogous to what exists for .swift-build-platform. My use case was running tests for a package that needs to add to the library link search path.

Hi @philipce - Can you give me an example of the custom swift test command that you would be running?

Sure! For example I've installed the openBLAS library in a place that's not on my search path, so need to pass a flag to the linker. I can build with swift build -L/usr/local/opt/openblas/lib -lopenblas, but running swift test has linker issues since it can't find openBLAS. Testing with swift test -L/usr/local/opt/openblas/lib -lopenblassolves the problem.

This change is now in develop branch. We will be merging with master soon. Closing issue.


Tutorial: how to write your own mojom to access platform's APIs/services

From @sethladd on November 5, 2015 23:23
Assuming there are some platform services that don't exist as pre-bundled mojoms/Dart wrappers, we could help new users understand how to build their own mojom to access platform capabilities.
Copied from original issue: flutter/website#50

Looks like we don't need this one anymore, as we've moved away from Mojo and towards our own string/JSON-based message passing API.


Error with useBasicAuth with the latest version

Installing the latest version of arangojs I have this error:
/home/nodeapp/node_modules/arangojs/lib/util/btoa.js:8
  return Buffer.from(str).toString('base64');
                ^

TypeError: this is not a typed array.
    at Function.from (native)
    at exports.default (/home/nodeapp/node_modules/arangojs/lib/util/btoa.js:8:17)
    at new Connection (/home/nodeapp/node_modules/arangojs/lib/connection.js:78:76)
    at new Database (/home/nodeapp/node_modules/arangojs/lib/database.js:49:24)
    at module.exports (/home/nodeapp/node_modules/arangojs/lib/index.js:18:10)
    at Object.<anonymous> (/home/nodeapp/models/schemas.js:30:31)
    at Module._compile (module.js:409:26)
    at Object.Module._extensions..js (module.js:416:10)
    at Module.load (module.js:343:32)

with the following code:
const db = require('arangojs')();

db.useBasicAuth(db_user, db_pwd);
db.useDatabase('testdatabase');

Before of update arangojs, it worked... why this problem?

Sorry: I resolved.
It was because I had an old version of node (4.4.7), I tried with the last version (6.11) and it worked!


Change Language and Theme: No Changes you have made may not be saved

When changing settings in Change Language and Theme i don't get the below question when i leave without saving:

@iliajie this is coming from the theme I believe?

Yeah .. It's very minor issue .. I will take a look at it anyway but some time later ..

I like minor issues, because no one else will find them and report them 😋

I like minor issues, because no one else will find them and report them 😋

Thank you for reporting this! It will be fixed in the next Authentic Theme 21.07 release.


Merge prTesting_201909191240 branch to master branch

Docs Build status updates of commit 058b7c6:
:clock10: Pending: waiting for processors (10 builds ahead of you)
:warning: Docs Build is busy, currently there are 10 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 058b7c6:
:warning: Validation status: warnings

File
Status
Preview URL
Details

split/updateTestRef.md
:warning:Warning

Details

split/updateTestRef.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.
[Warning] Missing attribute: title. Add a title string to show in search engine results.

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.


categorization of FIA_UAU.6

FIA_UAU.6 is currently categorized as an optional requirement that applies when the TSF provides its own administrative authentication mechanism (as opposed to e.g. launching an application on a server OS that does not separately authenticate the admin, who is presumed trusted through successful authentication to the underlying OS platform).
If this continues to be the only case where this SFR applies, it should be re-categorized as an "implementation-dependent requirement" - this sub-category of optional requirements did not exist when the original draft of the Module was being done.
Note this would potentially be affected by the previous comment, depending on:

if we also decide that user re-authentication is necessary (the current SFR just talks about administrator re-authentication)
if we do decide that user re-authentication is necessary, whether that gets handled in the existing FIA_UAU.6 SFR or if we have a separate iteration for it

This has been moved to mandatory with the removal of the App PP use case, assume closed.


Issue while installing with python venv instead of conda

While running this comamnd (part of the steps included in readme file):
llama distribution install --spec local-ollama --name ollama
I get the following error:
Using ollama as the Conda environment for this distribution
Error: conda command not found. Is Conda installed and in your PATH?
Failed to install distribution local-ollama
Traceback (most recent call last):
File "/home/ec2-user/genai/myenv/bin/llama", line 8, in
sys.exit(main())
File "/home/ec2-user/genai/myenv/lib/python3.10/site-packages/llama_toolchain/cli/llama.py", line 54, in main
parser.run(args)
File "/home/ec2-user/genai/myenv/lib/python3.10/site-packages/llama_toolchain/cli/llama.py", line 48, in run
args.func(args)
File "/home/ec2-user/genai/myenv/lib/python3.10/site-packages/llama_toolchain/cli/distribution/install.py", line 105, in _run_distribution_install_cmd
assert return_code == 0, cprint(
AssertionError: None
So it seems even though the readme file says it's ok to follow the steps in either conda or pytohn venv, but actually it expects it to be conda

Yeah you are right, currently installing and running distributions requires conda.
The readme suggestion is that you can use venv to run the apps ( as the distributions are running as a separate process ).
I ll update the README to reflect that.


Recording always in fast motion

Required information

Camera board id: ssc338Q +NVR
OpenIPC version: fpv
Commit:
Branch:
Tag:
installation method: (by manual https://github.com/OpenIPC/openipc-2.1/wiki/install_hisi or another)
modified majestic.yaml: yes
killall majestic
ulimit -c unlimited
echo /tmp/%e.%p.%s.%t.core > /proc/sys/kernel/core_pattern
majestic
Core dump file from /tmp/ , e.g. /tmp/majestic.806.11.1619707881.core

Issue description
A brief description of the problem. Should include what you were
attempting to do, what you did, what happened and what you expected to
see happen.
Hello guys, yesterday I was testing the settings available on majestic.full on the ssc338Q and managed to get a good image, even in low light, so good to the point that I decided to quickly install the camera on the drone, but first I tested the recording with the NVR , the result was strange and surprising, the recording was always in fast motion, but with the 7205v200 everything was fine, so it wasn't the NVR. After several attempts to restore the recording speed, which included sysupgrade, it returned to normal recording speed, but with a darker image, which I don't like, then I changed the parameters in majestic.yaml and it returned to fast motion recording,
Through the process of elimination I concluded that the problem is in the "ISP:, "exposure: xx" section, 10 by default but when I increase it, the recording speed also increases, and with a value of 30 fast motion is already noticeable.
Has anyone ever encountered this problem?
Expectations
Steps to reproduce

Step one
Step two
Step three

Information to attach

[ ] Any relevant log output (logread -f)
[ ] majestic.yaml configuration (cat /etc/majestic.yaml)system:
webAdmin: enabled
buffer: 1024
image:
mirror: false
flip: false
rotate: none
contrast: 70
hue: 50
saturation: 50
luminance: 50
osd:
enabled: false
template: "%a %e %B %Y %H:%M:%S %Z"
nightMode:
enabled: false
records:
enabled: false
path: /mnt/mmcblk0p1/%F/%H.mp4
maxUsage: 95
video0:

enabled: true
bitrate: 12288
codec: h265
rcMode: cbr
gopSize: 1.5
size: 1280x720
fps: 60
video1:
enabled: false
jpeg:
enabled: false
mjpeg:
size: 640x360
fps: 5
bitrate: 1024
audio:
enabled: false
volume: auto
srate: 8000
rtsp:
enabled: true
port: 554
hls:
enabled: false
youtube:
enabled: false
motionDetect:
enabled: false
visualize: false
debug: false
ipeye:
enabled: false
watchdog:
enabled: true
timeout: 10
isp:
exposure: 60
drc: 350
IPQPDelta: -8
outgoing:
enabled: true
server: udp://<IP_ADDRESS>:5600

Done


Release Arrow 31.0.0 (next release after 30.0.0)

Follow on from https://github.com/apache/arrow-rs/issues/3336

Planned Release Candidate: 2023-01-13
Planned Release and Publish to crates.io: 2023-01-016

Items (from dev/release/README.md):

[ ] PR to update version and CHANGELOG:
[ ] Release candidate created:
[ ] Release candidate approved:
[ ] Release to crates.io:
[ ] Make ticket for next release

See full list here:
https://github.com/apache/arrow-rs/compare/30.0.0...master
cc @iajoiner @tustvold @viirya

I will do it tomorrow

On it now

I plan to cut the release later today, once I've fixed a minor bug in the CSV reader

This was successfully released to crates.io: https://crates.io/crates/arrow/31.0.0

label_issue.py automatically added labels {'parquet'} from #3518

label_issue.py automatically added labels {'arrow'} from #3518

label_issue.py automatically added labels {'arrow-flight'} from #3518

label_issue.py automatically added labels {'parquet-derive'} from #3518


[Dependency] error: org.freedesktop.Sdk/x86_64/22.08 not installed

Running flatpak-builder --force-clean --repo=repo build-dir com.blackmagic.Resolve.yaml throws this on latest Arch :
error: org.freedesktop.Sdk/x86_64/22.08 not installed
Failed to init: Unable to find sdk org.freedesktop.Sdk version 22.08

Installing org.freedesktop.Sdk with flatpak install org.freedesktop.Sdk beforehand makes sure the SDK is installed and up to date.

I have run into the same problem, the solution here helped to fix the issue:

Remove already installed platform

flatpak remove --user org.freedesktop.Platform

Add flathub system-wide

sudo flatpak remote-add --if-not-exists --system flathub \
  https://flathub.org/repo/flathub.flatpakrepo

Run system-wide org.freedesktop.Platform  installation, while installing make sure to install the correct 22.08 version

sudo flatpak install --verbose org.freedesktop.Platform

Then cd to the repo folder, and try to re-run:
flatpak-builder --force-clean --repo=repo build-dir com.blackmagic.Resolve.yaml


scene 1 -> scene 2 -> scene 1 (refresh with new params) how?

Hi, what I'm trying to do is:
navigate from scene 1 to scene 2 (push) -> then  do some stuff on scene 2 -> then navigate back to scene 1 (pop scene 2 and refresh params of scene1)
// 1
<Scene key="restaurantPage" hideNavBar component={RestaurantPage} />
// 2
<Scene key="verifyNumber" hideNavBar component={VerifyNumber} />

Inside RestaurantPage Actions.verifyNumber() is pushed
Then I do some stuff and I want to go back to the previous scene with new params
This doesn't seem to work, I go back to the scene 1 but there is no new params.
Actions.restaurantPage({
  type: ActionConst.POP_AND_REPLACE,
  showModalRedeem: true,
  id: rId,
});

I've also tried this (very ugly) but doesn't work either:
Actions.pop();
setTimeout(() => {
  Actions.refresh({
      showModalRedeem: true,
      id: rId,
  });
})

Is there a way to do this?
Thanks 😄

Actions.pop();Actions.refresh({...}) should work. Please check Example from latest master, I've just added pop & refresh for Login 2 page.

@aksonov sorry I forgot to mention that I'm still using v3 and your suggestion doesn't seem to work.
Is it supposed to work with v3 as well?
If so, any suggestion on where I could start debugging?
Many thanks 😄

With a bit more testing I found that this works:
        Actions.pop();
        setTimeout(() => {
          Actions.refresh({
            showModalRedeem: true,
            id: rId,
          });
        }, 0);

Any reason why it doesn't work without the setTimeout ?
It's a bit ugly but if it works I'm happy tbh
Thank you

Hi...
I had tried this for page1->page2->page1
Actions.pop();
setTimeout(() => {
Actions.refresh({
param : value
});
}, 0);
First time it is working fine and componentWillReceiveProps() called in page1. but second time I had again tried this.But it does not go in componentWillReceiveProps() in page1.
Anyone can help?
Thanks


Grid: Ability to add Row Detail View for a row

Is it possible to display row details in the grid?
A way to expand the row and display its details below that.
Something like: Mud Blazor

@aditya119 Right now, row detail view is not supported. We can do an enhancement in the future.
For now, I can recommend three options:

Row click event -> show modal/offcanvas
Row double-click event -> show modal/offcanvas
Add an action icon/button column to each row -> show modal/offcanvas

Ok. Thanks.

My current solution:
#> Row 1
#> Row 2
#> Row 3
#> Row 4
I press the Row 3 "detail button" and I show
#> Row3
---  Detail Row 1
---  Detail Row 2
---  Detail Row 2
And a "back button" to return to initial state.
So the main table is filtered for the active item only, and a new hidden/temporary table appears below.


Optimizers of inner problem and fixed point maps in approximate implicit hypergradient computations do not necessarily match

In some of the examples (e.g. in iMAML) I notice that the inner optimization corresponds to a different fixed point map compared to the one used in the approximate implicit hypergradient function call (e.g. both use GradientDescent steps, but have different learning rates). Is it required that the same fixed point map is used at both places, or is there no such necessity? I see in the paper that the approximate implicit hypergradient does not use information of the trajectory to the approximate solution of the inner problem (it only depends on the approximate solution itself), however I'm confused with the semantics of the fp_map in the implementation of the implicit hypergradient functions.

The inner fixed point map and fp_map used to compute the hypergradient are different since they have two different purposes: one is used to solve the inner problem and the other to solve the linear system arising in the hypergradient computation. I agree that this can be  confusing in the code.

How does this generalize across optimizers with momentum for the inner problem?

You can use completely different optimisers for the inner problem and linear system as long as they solve the right problem. In the case of gradient descent with momentum you can have different learning learning rates and momentum parameters for the inner problem and linear system, same as with gradient descent. You can try and see what works best for your application.


Increased transmissibility and global spread of SARS-CoV-2 variants of concern as at June 2021

https://www.eurosurveillance.org/content/10.2807/1560-7917.ES.2<IP_ADDRESS>0509
The appendix.

See also "Estimated transmissibility and impact of SARS-CoV-2 lineage B.1.1.7 in England" (Science)


Simplify config manager background goroutine logic.

This change is

Jenkins job mixer/presubmit passed

Jenkins job mixer/istio-pr passed

Jenkins job mixer/presubmit passed

Jenkins job mixer/istio-pr passed

Jenkins job mixer/presubmit passed

Jenkins job mixer/istio-pr passed


Display monitoring plot observation photos

mostly a copy of what we do in nursery withdrawals details plus some customization for monitoring plots
added photos in staging, switch to dev org and go here /observations/56/3/106/270028

To test: https://tree-location-web-git-karthik-photos-terraformation.vercel.app/observations/56/3/106/270028

Looks good!

Thanks @charlie-tf . Wanted to run this by you.. the only differences between here and nursery withdrawals photos are height/width of thumbnails and object/cover image css. Nursery withdrawals photos uses varied widths for thumbnails and shows the entire image. Would it be worth extracting this out and reusing for nursery withdrawals as well (will change some of the current behavior). Potentially reuse for accessions as well.

Looks good!

Thanks @charlie-tf . Wanted to run this by you.. the only differences between here and nursery withdrawals photos are height/width of thumbnails and object/cover image css. Nursery withdrawals photos uses varied widths for thumbnails and shows the entire image. Would it be worth extracting this out and reusing for nursery withdrawals as well (will change some of the current behavior). Potentially reuse for accessions as well.

That seems like a worthwhile thing to extract into its own component. A followup / improvement ticket is fine

I can extract it out as part of this PR. Is that a 'yes' to replacing the nursery withdrawals photos? I can do the replacements as a follow up PR.

Followup for replacements sounds fine to me

Followup for replacements sounds fine to me

Cool, created this. Refactored this PR.


Added colors.text from theme

Uses the colors.text from the theme for the menu item text color.

+1 for this one. Without it, items on the list are not showing (undefined color)

Any chance we could get this merged? This fixes the issue @adamgajzlerowicz posted on android devices.

Thanks for the PR, i have fixed the issue.


Most basic home view

only chronological
no options

[ ] Click text items
[ ] Normal font
[ ] Show media


BulkResponseAggregator Undefined index

What did you do?
Attempted to bulk insert indexes.
What did you expect to happen?
Indexes to be inserted.
What actually happened?
An error occurred.
In BulkResponseAggregator.php line 47:
Undefined index: type

What versions of PHP, Lumen and this module are you using?
PHP: 7.2.23
Lumen: 5.8.13
Elasticsearch: 7.5.0
Please include code that reproduces the issue. The best reproductions are self-contained scripts with minimal dependencies.
I was able to fix the error by replacing line 47 with the following two lines.
$item = $item["index"];
$item = $item['_type'];

I've tried to force an error to see the response object, but I've been unable to in my short testing time.
With the error object, I can open a PR to fix any potential errors with that.

I'm afraid this library isn't compatible with Elasticsearch 7.x at the moment. We're still using 5.x in most of ours projects so we haven't bothered making it work with newer versions.

Can you post a stacktrace and the full error of what's happening? I recently changed this code so maybe I broke it somehow.

I'll try and reproduce the error, but IIRC that was the only error since it was part of the bulk migration.

Crap, looks like I broke this in 3.8.0. I'll push a fix ASAP. Thanks for reporting!

Fixed in https://packagist.org/packages/nordsoftware/lumen-elasticsearch#3.8.1

Thank you @Jalle19


Add discovery destroy logic

Description

Replaced null_resource for discovery project and collection creation with restapi_object to allow for destroy
File upload is still null_resource, as it relies on form data that is unsupported by the rest api resource.
Refactored file upload to ensure duplicates are not re-uploaded

Release required?

[ ] No release
[ ] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

/run pipeline

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

GitHub release
v1.7.0

Your semantic-release bot :package::rocket:


Cannot input with custom keyboard(Rebit A-Keyboard) in Android.

In Andriod, I cannot type correctly in a TextField with Rebit A-Keyboard (custom keyboard).
It accepts only one character but ignores all other typing.

Like the image, an underline appears with character that seems like it is waiting for correction or recommendation selection. If I touch empty space in the text field so I unfocus the underline, then I can type one more character(total 2 character so far..)
If I turn off the recommendation function in the keyboard's preference, I could input whole word. But still can't input Korean.
Steps to Reproduce

Install Rebit A-Keyboard from Google Play.
https://play.google.com/store/apps/details?id=com.phillit.akeyboard&hl=en

Create an empty project and build an TextField somewhere.

Run and type anything with the keyboard.

Target Platform:
Android
Target OS version/browser:
Android 7.0
Android 8.0
Android 9
Devices:
Nexus 5X
POCO F1
BrailleSense Polaris
Redmi Note 5 Pro
MI MAX
Logs

Launching lib/main.dart on Nexus 5X in debug mode...
Built build/app/outputs/apk/debug/app-debug.apk.
I/zygote64(10929): Do partial code cache collection, code=29KB, data=27KB
I/zygote64(10929): After code cache collection, code=29KB, data=27KB
I/zygote64(10929): Increasing code cache capacity to 128KB

flutter analyze
No issues found! (ran in 1.5s)

flutter version -v
[✓] Flutter (Channel stable, v1.9.1+hotfix.6, on Mac OS X 10.14.6 18G95, locale
    ko-KR)
    • Flutter version 1.9.1+hotfix.6 at /Users/jeff/dev/flutter
    • Framework revision 68587a0916 (6 weeks ago), 2019-09-13 19:46:58 -0700
    • Engine revision b863200c37
    • Dart version 2.5.0

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/jeff/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling
      support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_152-release-1343-b01)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.0)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.0, Build version 11A420a
    • CocoaPods version 1.7.4

[✓] Android Studio (version 3.4)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 35.2.1
    • Dart plugin version 183.6270
    • Java version OpenJDK Runtime Environment (build
      1.8.0_152-release-1343-b01)

[✓] VS Code (version 1.39.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.5.1

[✓] Connected device (1 available)
    • Nexus 5X • 00b86752e2989221 • android-arm64 • Android 8.0.0 (API 26)

• No issues found!

Turns out it was an issue of keyboard app, resolved at keyboard app version 0.9.146.


Specification attributes for filtering and comparison

I need to use some specification attributes to describe my products. Also i will use these attributes for  filtering products on category page or comparison.

Can i done this task with this module?
Do you agree we should separate Product Attributes and Specification Attributes? (NopCommerce uses this approach)

In nopCommerce, the product attributes are quantifiable or descriptive aspects of a product (such as, color). For example, if you were to create an attribute for color, with the values of blue, green, yellow, and so on, you may want to apply this attribute to shirts, which you sell in various colors (you can adjust a price or weight for any of existing attribute values). You can then map these attributes to a product variant later on.
Unlike product attributes, specification attributes are used for information purposes only (visible on product details page) and can be used for filtering products on the category details page. They are mapped to products and not to product variants. (Product attributes are mapped to product variants, as described in the section above.)
Any help would be much appreciated.
/cc @bleroy

That looks like a job for taxonomies.


Subdirectory test case may be incorrect

If I have a global gitignore that ignores node_modules/ and I wanted to include one subdirectory, I could do the following in git:
# Do not ignore node_modules
!node_modules
# Ignore all node_modules suddirectories
node_modules/*
# Do not ignore the chalk directory
!node_modules/chalk

I can check this behavior with:
$ git check-ignore --verbose node_modules/jest/README.md

.gitignore:4:node_modules/*     node_modules/jest/README.md

$ git check-ignore --verbose node_modules/jest/build/index.js

.gitignore:4:node_modules/*     node_modules/jest/build/index.js

$ git check-ignore --verbose node_modules/chalk/readme.md

<no output, indicating the file is not ignored>

$ git check-ignore --verbose node_modules/chalk/source/index.js

<no output, indicating the file is not ignored>

This assertion seems to be at odds with the above behavior: https://github.com/nielsbasjes/codeowners/blob/6028b0f230dbf73d3b19407145ddd38bcbe1a7ef/gitignore-reader/src/test/java/nl/basjes/gitignore/TestGitIgnore.java#L322

I was very much wrong on this libraries behavior vs git check-ignore.
The file should not be ignored (like the test case) but the directory it's in would be ignored, so I need to check both.

Thanks for diving into this.
If you find any problem I'm happy to pick it up and fix it.
If you happen to find a list of test cases (possibly steps in a git tutorial) I'm happy to include those as additional testcases in my library to ensure it behaves the same as git behaves.


Duping issue with RFTools Storage Tablet and Storage Scanner and Refined Storage interface

Minecraft: 1.12.2
Forge: <IP_ADDRESS>54
Rftools: 1.12-7.33
Refined Storage: 1.5.32
The storage tablet is linked to a storage scanner which is scanning an interface from Refined Storage. As long as at least one item of the crafting recipe that is specified in the tablet is in the Refined Storage system, I am able to craft as many as I want of the resulting crafting recipe.
Steps to reproduce:

Setup an Refined Storage System with an interface.
Put one item in it.
Setup a storage scanner.
Link the storage scanner to the storage tablet.
Try to craft a recipe using the item.

This will, at first, use the required items. However, when the number of required items drops below the necessary, it will no longer consume items inside of the refined storage system but will still give the resulting item from the crafting recipe. If there are any items outside of it and recheable to the storage tablet (like in the player inventory or a a chest caught by the storage scanner), they will still be used.

https://github.com/raoulvdberge/refinedstorage/issues/1744

This issue relies on a feature of RS that is going away so I'm going to close the issue.


add isort to dev deps, ignore existing .py files, use black profile

This is similar to https://github.com/Chia-Network/chia-blockchain/pull/9614/files, and actually I copied the file list from there.  The idea is that we can get the checks/formatting applied to any new files right away.  Existing files can be taken on however is deemed appropriate and removed from the skip list once they are tidy.

Thanks, picked the commits!


Having an issue to use the framework to train on a new domain

Hi @knmnyn,
Not sure what I was doing wrong.
I'm currently using a new domain of text data, it is unable to start the training due to the checkpoint model is attached with 2548 labels.  When changing these number, the pre-train model file is not accepted. Just wondering if it could be modified to be used with a different number of labels?
Thanks.

Hi @bimhud : I don't believe it can be used with a different number of labels.  You may need to retrain the model if you need to use new labels.  @AKBakshay may be able to elaborate.

Hi @knmnyn @AKBakshay , I did re-train the model by replaced the downloaded checkpoint model with the original one such as https://s3.amazonaws.com/models.huggingface.co/bert/bert-base-uncased-pytorch_model.bin, voca and config files
From my understanding, this will help fine-tune the two last layers using the same framework. It is working without any issue. However, the performance is not as good as your checkpoint and the prediction result doesn't make sense.
Just wondering how many epoch that was trained in order to produce your 'checkpoint' models and what are the original pre-train model that you were using.
Any suggestion would be really appreciated.

@knmnyn Thank you for the input!
@bimhud In the repo, the available model weights correspond to the model with 2548 labels as output. Based on the requirement, the output size can be changed. But doing that, the provided weights can't be loaded.
You can manually make changes to load the weights of the provided model, remove its last 2 layers and add new layers, based on the requirement.