Build failure: swift

Swift still built failed after https://github.com/NixOS/nixpkgs/pull/326588 has been merged.
Steps To Reproduce
Steps to reproduce the behavior:

build swift on x86_64-darwin with nixpkgs 693bc46d169f5af9c992095736e82c3488bf7dbb

Build log
swift> clang-15: warning: overriding '-mmacos-version-min=10.15' option with '-target x86_64-apple-macosx10.13' [-Woverriding-t-option]
swift> [1150/1357] Building CXX object tools/swift-ast-script/CMakeFiles/swift-ast-script.dir/ASTScriptParser.cpp.o
swift> clang-15: warning: overriding '-mmacos-version-min=10.15' option with '-target x86_64-apple-macosx10.13' [-Woverriding-t-option]
swift> [1151/1357] Building CXX object lib/RemoteAST/CMakeFiles/swiftRemoteAST.dir/RemoteAST.cpp.o
swift> clang-15: warning: overriding '-mmacos-version-min=10.15' option with '-target x86_64-apple-macosx10.13' [-Woverriding-t-option]
swift> [1152/1357] Linking CXX static library lib/libswiftRemoteAST.a
swift> [1153/1357] Building C object tools/libSwiftScan/CMakeFiles/libSwiftScan.dir/c-include-check.c.o
swift> clang-15: warning: overriding '-mmacos-version-min=10.15' option with '-target x86_64-apple-macosx10.13' [-Woverriding-t-option]
swift> [1154/1357] Building CXX object tools/sil-nm/CMakeFiles/sil-nm.dir/SILNM.cpp.o
swift> clang-15: warning: overriding '-mmacos-version-min=10.15' option with '-target x86_64-apple-macosx10.13' [-Woverriding-t-option]
swift> [1155/1357] Building C object tools/libStaticMirror/CMakeFiles/libStaticMirror.dir/c-include-check.c.o
swift> clang-15: warning: overriding '-mmacos-version-min=10.15' option with '-target x86_64-apple-macosx10.13' [-Woverriding-t-option]
swift> [1156/1357] Building swift module _CompilerRegexParser
swift> FAILED: bootstrapping1/SwiftCompilerSources/_CompilerRegexParser.o /tmp/nix-build-swift-5.8.drv-0/build/swift/bootstrapping1/SwiftCompilerSources/_CompilerRegexParser.o
swift> cd /tmp/nix-build-swift-5.8.drv-0/src/swift/SwiftCompilerSources && /tmp/nix-build-swift-5.8.drv-0/build/swift/bootstrapping0/bin/swiftc -c -o /tmp/nix-build-swift-5.8.drv-0/build/swift/bootstrapping1/SwiftCompilerSources/_CompilerRegexParser.o -sdk /nix/store/4gp3glbgd0n7gincx4f7fazd2xc2gjl6-SDKs/MacOSX10.15.sdk -Xcc -isystem -Xcc /nix/store/d8qw1hx36cb2gxlq2wf1kf7mycsijin2-libcxx-16.0.6-dev/include/c++/v1 -I /tmp/nix-build-swift-5.8.drv-0/build/swift/bootstrapping0/bin/../lib -I /nix/store/4gp3glbgd0n7gincx4f7fazd2xc2gjl6-SDKs/MacOSX10.15.sdk/usr/lib -target x86_64-apple-macosx10.13 -module-name _CompilerRegexParser -emit-module -emit-module-path /tmp/nix-build-swift-5.8.drv-0/build/swift/bootstrapping1/SwiftCompilerSources/_CompilerRegexParser.swiftmodule -parse-as-library /private/tmp/nix-build-swift-5.8.drv-0/src/swift-experimental-string-processing/Sources/_RegexParser/Regex/AST/AST.swift /private/tmp/nix-build-swift-5.8.drv-0/src/swift-experimental-string-processing/Sources/_RegexParser/Regex/AST/ASTAction.swift /private/tmp/nix-build-swift-5.8.drv-0/src/swift-experimental-string-processing/Sources/_RegexParser/Regex/AST/ASTProtocols.swift /private/tmp/nix-build-swift-5.8.drv-0/src/swift-experimental-string-processing/Sources/_RegexParser/Regex/AST/Atom.swift /private/tmp/nix-build-swift-5.8.drv-0/src/swift-experimental-string-processing/Sources/_RegexParser/Regex/AST/Conditional.swift /private/tmp/nix-build-swift-5.8.drv-0/src/swift-experimental-string-processing/Sources/_RegexParser/Regex/AST/CustomCharClass.swift /private/tmp/nix-build-swift-5.8.drv-0/src/swift-experimental-string-processing/Sources/_RegexParser/Regex/AST/Group.swift /private/tmp/nix-build-swift-5.8.drv-0/src/swift-experimental-string-processing/Sources/_RegexParser/Regex/AST/MatchingOptions.swift /private/tmp/nix-build-swift-5.8.drv-0/src/swift-experimental-string-processing/Sources/_RegexParser/Regex/AST/Quantification.swift /private/tmp/nix-build-swift-5.8.drv-0/src/swift-experimental-string-processing/Sources/_RegexParser/Regex/Parse/CaptureList.swift /private/tmp/nix-build-swift-5.8.drv-0/src/swift-experimental-string-processing/Sources/_RegexParser/Regex/Parse/CaptureStructure.swift /private/tmp/nix-build-swift-5.8.drv-0/src/swift-experimental-string-processing/Sources/_RegexParser/Regex/Parse/CharacterPropertyClassification.swift /private/tmp/nix-build-swift-5.8.drv-0/src/swift-experimental-string-processing/Sources/_RegexParser/Regex/Parse/CompilerInterface.swift /private/tmp/nix-build-swift-5.8.drv-0/src/swift-experimental-string-processing/Sources/_RegexParser/Regex/Parse/DelimiterLexing.swift /private/tmp/nix-build-swift-5.8.drv-0/src/swift-experimental-string-processing/Sources/_RegexParser/Regex/Parse/Diagnostics.swift /private/tmp/nix-build-swift-5.8.drv-0/src/swift-experimental-string-processing/Sources/_RegexParser/Regex/Parse/LexicalAnalysis.swift /private/tmp/nix-build-swift-5.8.drv-0/src/swift-experimental-string-processing/Sources/_RegexParser/Regex/Parse/Parse.swift /private/tmp/nix-build-swift-5.8.drv-0/src/swift-experimental-string-processing/Sources/_RegexParser/Regex/Parse/Sema.swift /private/tmp/nix-build-swift-5.8.drv-0/src/swift-experimental-string-processing/Sources/_RegexParser/Regex/Parse/Source.swift /private/tmp/nix-build-swift-5.8.drv-0/src/swift-experimental-string-processing/Sources/_RegexParser/Regex/Parse/SourceLocation.swift /private/tmp/nix-build-swift-5.8.drv-0/src/swift-experimental-string-processing/Sources/_RegexParser/Regex/Parse/SyntaxOptions.swift /private/tmp/nix-build-swift-5.8.drv-0/src/swift-experimental-string-processing/Sources/_RegexParser/Regex/Printing/DumpAST.swift /private/tmp/nix-build-swift-5.8.drv-0/src/swift-experimental-string-processing/Sources/_RegexParser/Regex/Printing/PrettyPrinter.swift /private/tmp/nix-build-swift-5.8.drv-0/src/swift-experimental-string-processing/Sources/_RegexParser/Regex/Printing/PrintAsCanonical.swift /private/tmp/nix-build-swift-5.8.drv-0/src/swift-experimental-string-processing/Sources/_RegexParser/Regex/Printing/RenderRanges.swift /private/tmp/nix-build-swift-5.8.drv-0/src/swift-experimental-string-processing/Sources/_RegexParser/Regex/TreeProtocols.swift /private/tmp/nix-build-swift-5.8.drv-0/src/swift-experimental-string-processing/Sources/_RegexParser/Utility/AllScalars.swift /private/tmp/nix-build-swift-5.8.drv-0/src/swift-experimental-string-processing/Sources/_RegexParser/Utility/Errors.swift /private/tmp/nix-build-swift-5.8.drv-0/src/swift-experimental-string-processing/Sources/_RegexParser/Utility/Misc.swift /private/tmp/nix-build-swift-5.8.drv-0/src/swift-experimental-string-processing/Sources/_RegexParser/Utility/MissingUnicode.swift /private/tmp/nix-build-swift-5.8.drv-0/src/swift-experimental-string-processing/Sources/_RegexParser/Utility/TypeConstruction.swift -wmo -Xfrontend -validate-tbd-against-ir=none -Xfrontend -enable-experimental-cxx-interop -Xcc -UIBOutlet -Xcc -UIBAction -Xcc -UIBInspectable -Xfrontend -disable-implicit-string-processing-module-import -O -cross-module-optimization -Xcc -I -Xcc /tmp/nix-build-swift-5.8.drv-0/src/llvm-project/llvm/include -Xcc -I -Xcc /tmp/nix-build-swift-5.8.drv-0/build/llvm/include -Xcc -I -Xcc /tmp/nix-build-swift-5.8.drv-0/src/llvm-project/clang/include -Xcc -I -Xcc /tmp/nix-build-swift-5.8.drv-0/build/llvm/tools/clang/include -Xcc -I -Xcc /private/tmp/nix-build-swift-5.8.drv-0/src/swift/include -Xcc -I -Xcc /tmp/nix-build-swift-5.8.drv-0/build/swift/SwiftCompilerSources/../include -I /tmp/nix-build-swift-5.8.drv-0/build/swift/bootstrapping1/SwiftCompilerSources
swift> <unknown>:0: warning: overriding '-mmacos-version-min=10.15' option with '-target x86_64-apple-macosx10.13'
swift> <unknown>:0: warning: unable to perform implicit import of "_Concurrency" module: no such module found
swift> <unknown>:0: error: IR generation failure: Cannot read legacy layout file at '/private/tmp/nix-build-swift-5.8.drv-0/build/swift/bootstrapping0/lib/swift/macosx/layouts-x86_64.yaml'
swift> [1157/1357] Building CXX object tools/sil-llvm-gen/CMakeFiles/sil-llvm-gen.dir/SILLLVMGen.cpp.o
swift> clang-15: warning: overriding '-mmacos-version-min=10.15' option with '-target x86_64-apple-macosx10.13' [-Woverriding-t-option]
swift> [1158/1357] Building CXX object lib/SwiftRemoteMirror/CMakeFiles/swiftRemoteMirror.dir/__/__/stdlib/public/SwiftRemoteMirror/SwiftRemoteMirror.cpp.o
swift> clang-15: warning: overriding '-mmacos-version-min=10.15' option with '-target x86_64-apple-macosx10.13' [-Woverriding-t-option]
swift> [1159/1357] Building CXX object tools/libStaticMirror/CMakeFiles/libStaticMirror.dir/libStaticMirror.cpp.o
swift> clang-15: warning: overriding '-mmacos-version-min=10.15' option with '-target x86_64-apple-macosx10.13' [-Woverriding-t-option]
swift> [1160/1357] Building CXX object lib/StaticMirror/CMakeFiles/swiftStaticMirror.dir/ObjectFileContext.cpp.o
swift> clang-15: warning: overriding '-mmacos-version-min=10.15' option with '-target x86_64-apple-macosx10.13' [-Woverriding-t-option]
swift> /tmp/nix-build-swift-5.8.drv-0/src/swift/lib/StaticMirror/ObjectFileContext.cpp:101:16: warning: variable 'Offset' is used uninitialized whenever 'if' condition is false [-Wsometimes-uninitialized]
swift>     } else if (O->getBytesInAddress() == 4) {
swift>                ^~~~~~~~~~~~~~~~~~~~~~~~~~~
swift> /tmp/nix-build-swift-5.8.drv-0/src/swift/lib/StaticMirror/ObjectFileContext.cpp:109:68: note: uninitialized use occurs here
swift>     DynamicRelocations.insert({bind.address(), {bind.symbolName(), Offset}});
swift>                                                                    ^~~~~~
swift> /tmp/nix-build-swift-5.8.drv-0/src/swift/lib/StaticMirror/ObjectFileContext.cpp:101:12: note: remove the 'if' if its condition is always true
swift>     } else if (O->getBytesInAddress() == 4) {
swift>            ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
swift> /tmp/nix-build-swift-5.8.drv-0/src/swift/lib/StaticMirror/ObjectFileContext.cpp:93:20: note: initialize the variable 'Offset' to silence this warning
swift>     uint64_t Offset;
swift>                    ^
swift>                     = 0
swift> 1 warning generated.
swift> [1161/1357] Building CXX object tools/swift-ast-script/CMakeFiles/swift-ast-script.dir/swift-ast-script.cpp.o
swift> clang-15: warning: overriding '-mmacos-version-min=10.15' option with '-target x86_64-apple-macosx10.13' [-Woverriding-t-option]
swift> [1162/1357] Building CXX object stdlib/public/SwiftRemoteMirror/CMakeFiles/swiftRemoteMirror-macosx-x86_64.dir/SwiftRemoteMirror.cpp.o
swift> clang-15-unwrapped: warning: overriding '-mmacos-version-min=10.15' option with '-target x86_64-apple-macosx10.13' [-Woverriding-t-option]
swift> [1163/1357] Building CXX object tools/swift-ast-script/CMakeFiles/swift-ast-script.dir/ASTScriptEvaluator.cpp.o
swift> clang-15: warning: overriding '-mmacos-version-min=10.15' option with '-target x86_64-apple-macosx10.13' [-Woverriding-t-option]
swift> [1164/1357] Building CXX object tools/swift-remoteast-test/CMakeFiles/swift-remoteast-test.dir/swift-remoteast-test.cpp.o
swift> clang-15: warning: overriding '-mmacos-version-min=10.15' option with '-target x86_64-apple-macosx10.13' [-Woverriding-t-option]
swift> [1165/1357] Building CXX object tools/swift-refactor/CMakeFiles/swift-refactor.dir/swift-refactor.cpp.o
swift> clang-15: warning: overriding '-mmacos-version-min=10.15' option with '-target x86_64-apple-macosx10.13' [-Woverriding-t-option]
swift> [1166/1357] Building CXX object tools/libSwiftScan/CMakeFiles/libSwiftScan.dir/libSwiftScan.cpp.o
swift> clang-15: warning: overriding '-mmacos-version-min=10.15' option with '-target x86_64-apple-macosx10.13' [-Woverriding-t-option]
swift> [1167/1357] Building swift module Basic
swift> FAILED: bootstrapping1/SwiftCompilerSources/Basic.o /tmp/nix-build-swift-5.8.drv-0/build/swift/bootstrapping1/SwiftCompilerSources/Basic.o
swift> cd /tmp/nix-build-swift-5.8.drv-0/src/swift/SwiftCompilerSources && /tmp/nix-build-swift-5.8.drv-0/build/swift/bootstrapping0/bin/swiftc -c -o /tmp/nix-build-swift-5.8.drv-0/build/swift/bootstrapping1/SwiftCompilerSources/Basic.o -sdk /nix/store/4gp3glbgd0n7gincx4f7fazd2xc2gjl6-SDKs/MacOSX10.15.sdk -Xcc -isystem -Xcc /nix/store/d8qw1hx36cb2gxlq2wf1kf7mycsijin2-libcxx-16.0.6-dev/include/c++/v1 -I /tmp/nix-build-swift-5.8.drv-0/build/swift/bootstrapping0/bin/../lib -I /nix/store/4gp3glbgd0n7gincx4f7fazd2xc2gjl6-SDKs/MacOSX10.15.sdk/usr/lib -target x86_64-apple-macosx10.13 -module-name Basic -emit-module -emit-module-path /tmp/nix-build-swift-5.8.drv-0/build/swift/bootstrapping1/SwiftCompilerSources/Basic.swiftmodule -parse-as-library /private/tmp/nix-build-swift-5.8.drv-0/src/swift/SwiftCompilerSources/Sources/Basic/SourceLoc.swift /private/tmp/nix-build-swift-5.8.drv-0/src/swift/SwiftCompilerSources/Sources/Basic/Utils.swift -wmo -Xfrontend -validate-tbd-against-ir=none -Xfrontend -enable-experimental-cxx-interop -Xcc -UIBOutlet -Xcc -UIBAction -Xcc -UIBInspectable -Xfrontend -disable-implicit-string-processing-module-import -O -cross-module-optimization -Xcc -I -Xcc /tmp/nix-build-swift-5.8.drv-0/src/llvm-project/llvm/include -Xcc -I -Xcc /tmp/nix-build-swift-5.8.drv-0/build/llvm/include -Xcc -I -Xcc /tmp/nix-build-swift-5.8.drv-0/src/llvm-project/clang/include -Xcc -I -Xcc /tmp/nix-build-swift-5.8.drv-0/build/llvm/tools/clang/include -Xcc -I -Xcc /private/tmp/nix-build-swift-5.8.drv-0/src/swift/include -Xcc -I -Xcc /tmp/nix-build-swift-5.8.drv-0/build/swift/SwiftCompilerSources/../include -I /tmp/nix-build-swift-5.8.drv-0/build/swift/bootstrapping1/SwiftCompilerSources
swift> <unknown>:0: warning: overriding '-mmacos-version-min=10.15' option with '-target x86_64-apple-macosx10.13'
swift> <unknown>:0: warning: unable to perform implicit import of "_Concurrency" module: no such module found
swift> <unknown>:0: warning: template instantiation for 'std::reverse_iterator' not imported: too many instantiations
swift> <unknown>:0: warning: template instantiation for 'std::__pointer' not imported: too many instantiations
swift> <unknown>:0: warning: template instantiation for 'std::remove_volatile' not imported: too many instantiations
swift> <unknown>:0: warning: template instantiation for 'std::initializer_list' not imported: too many instantiations
swift> <unknown>:0: warning: template instantiation for 'std::conditional' not imported: too many instantiations
swift> <unknown>:0: warning: template instantiation for 'std::pair' not imported: too many instantiations
swift> <unknown>:0: warning: template instantiation for 'std::__add_lvalue_reference_impl' not imported: too many instantiations
swift> <unknown>:0: error: IR generation failure: Cannot read legacy layout file at '/private/tmp/nix-build-swift-5.8.drv-0/build/swift/bootstrapping0/lib/swift/macosx/layouts-x86_64.yaml'
swift> ninja: build stopped: subcommand failed.

Additional context
Add any other context about the problem here.
Notify maintainers
@dtzWill @trepetti @dduan @Trundle @stephank
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-darwin"`
 - host os: `Darwin 23.5.0, macOS 10.16`
 - multi-user?: `yes`
 - sandbox: `no`
 - version: `nix-env (Nix) 2.18.4`
 - channels(root): `""`
 - channels(user): `""`
 - nixpkgs: `/nix/store/j4jzjbr302cw5bl0n3pch5j9bh5qwmaj-source`

Add a :+1: reaction to issues you find important.

Also failing in aarch64-linux:
error: builder for '/nix/store/rcdwli2c6v6f36yqzg66yj9bgmhjg9mc-swift-5.8.drv' failed with exit code 1;
       last 25 log lines:
       > ld: warning: Could not find or use auto-linked library 'swiftCompatibility56'
       > Undefined symbols for architecture arm64:
       >   "__swift_FORCE_LOAD_$_swiftCompatibility56", referenced from:
       >       __swift_FORCE_LOAD_$_swiftCompatibility56_$_Optimizer in libswiftCompilerModules-bootstrapping1.a(Optimizer.o)
       >       __swift_FORCE_LOAD_$_swiftCompatibility56_$_SIL in libswiftCompilerModules-bootstrapping1.a(SIL.o)
       >       __swift_FORCE_LOAD_$_swiftCompatibility56_$_Basic in libswiftCompilerModules-bootstrapping1.a(Basic.o)
       >       __swift_FORCE_LOAD_$_swiftCompatibility56_$_Parse in libswiftCompilerModules-bootstrapping1.a(Parse.o)
       >       __swift_FORCE_LOAD_$_swiftCompatibility56_$__CompilerRegexParser in libswiftCompilerModules-bootstrapping1.a(_CompilerRegexParser.o)
       >       __swift_FORCE_LOAD_$_swiftCompatibility56_$_AST in libswiftCompilerModules-bootstrapping1.a(AST.o)
       >      (maybe you meant: __swift_FORCE_LOAD_$_swiftCompatibility56_$__CompilerRegexParser, __swift_FORCE_LOAD_$_swiftCompatibility56_$_SIL , __swift_FORCE_LOAD_$_swiftCompatibility56_$_Parse , __swift_FORCE_LOAD_$_swiftCompatibility56_$_Basic , __swift_FORCE_LOAD_$_swiftCompatibility56_$_Optimizer , __swift_FORCE_LOAD_$_swiftCompatibility56_$_AST )
       >   "__swift_FORCE_LOAD_$_swiftCompatibilityConcurrency", referenced from:
       >       __swift_FORCE_LOAD_$_swiftCompatibilityConcurrency_$_Optimizer in libswiftCompilerModules-bootstrapping1.a(Optimizer.o)
       >       __swift_FORCE_LOAD_$_swiftCompatibilityConcurrency_$_SIL in libswiftCompilerModules-bootstrapping1.a(SIL.o)
       >       __swift_FORCE_LOAD_$_swiftCompatibilityConcurrency_$_Basic in libswiftCompilerModules-bootstrapping1.a(Basic.o)
       >       __swift_FORCE_LOAD_$_swiftCompatibilityConcurrency_$_Parse in libswiftCompilerModules-bootstrapping1.a(Parse.o)
       >       __swift_FORCE_LOAD_$_swiftCompatibilityConcurrency_$__CompilerRegexParser in libswiftCompilerModules-bootstrapping1.a(_CompilerRegexParser.o)
       >       __swift_FORCE_LOAD_$_swiftCompatibilityConcurrency_$_AST in libswiftCompilerModules-bootstrapping1.a(AST.o)
       >      (maybe you meant: __swift_FORCE_LOAD_$_swiftCompatibilityConcurrency_$_AST, __swift_FORCE_LOAD_$_swiftCompatibilityConcurrency_$_Basic , __swift_FORCE_LOAD_$_swiftCompatibilityConcurrency_$_Parse , __swift_FORCE_LOAD_$_swiftCompatibilityConcurrency_$__CompilerRegexParser , __swift_FORCE_LOAD_$_swiftCompatibilityConcurrency_$_Optimizer , __swift_FORCE_LOAD_$_swiftCompatibilityConcurrency_$_SIL )
       > ld: symbol(s) not found for architecture arm64
       > clang-15: error: linker command failed with exit code 1 (use -v to see invocation)
       > [1105/1354] Building CXX object stdlib/public/RemoteInspection/CMakeFiles/swiftRemoteInspection-macosx-arm64.dir/TypeLowering.cpp.o
       > clang-15-unwrapped: warning: overriding '-mmacos-version-min=10.15' option with '-target arm64-apple-macosx10.13' [-Woverriding-t-option]
       > [1106/1354] Building CXX object stdlib/public/RemoteInspection/CMakeFiles/swiftRemoteInspection-macosx-arm64.dir/TypeRef.cpp.o
       > clang-15-unwrapped: warning: overriding '-mmacos-version-min=10.15' option with '-target arm64-apple-macosx10.13' [-Woverriding-t-option]
       > ninja: build stopped: subcommand failed.
       For full logs, run 'nix log /nix/store/rcdwli2c6v6f36yqzg66yj9bgmhjg9mc-swift-5.8.drv'.

The interesting part is that I could build this locally in my laptop (macOS 14.5), but it isn't working in GitHub Actions (also macOS 14.5). Here is my logs from GitHub Actions: https://github.com/thiagokokada/nix-configs/actions/runs/9976188278/job/27567744849.

This also builds on the darwin community builder:
 - system: `"aarch64-darwin"`
 - host os: `Darwin 23.5.0, macOS 14.5`
 - multi-user?: `yes`
 - sandbox: `relaxed`
 - version: `nix-env (Nix) 2.18.5`
 - nixpkgs: `/nix/store/qapc95ms35a2syn25wawy4byy3h1zbiv-8sjaji13jiylfr93qcx0d7fqc1f4gm1s-source`

Hydra also failed by same errors
https://hydra.nixos.org/build/266353277/nixlog/2
https://hydra.nixos.org/build/266353180/nixlog/1

Hello swift maintainers @dtzWill @trepetti @dduan @Trundle @stephank
on the nixpkgs trunk branch, swift-unwrapped is currently failing to build on 3/4 platforms:

https://hydra.nixos.org/job/nixpkgs/trunk/swiftPackages.swift-unwrapped.aarch64-darwin ❌
https://hydra.nixos.org/job/nixpkgs/trunk/swiftPackages.swift-unwrapped.aarch64-linux ❌
https://hydra.nixos.org/job/nixpkgs/trunk/swiftPackages.swift-unwrapped.x86_64-darwin ❌
https://hydra.nixos.org/job/nixpkgs/trunk/swiftPackages.swift-unwrapped.x86_64-linux ✅

two of the above platforms (aarch64-darwin, x86_64-darwin) have been broken for 1.5 months :(
can you please take a look?

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/release-channels-arent-stable-for-darwin-users-swift-package-broken/50452/1

Just a note on how I workaround this, in case it's helpful for people who reach here.
I am able to build my system with the latest unstable with swift replaced by the swift from 2e92235aa591abc613504fde2546d6f78b18c0cd (the previous commit of the first failed build of swift.aarch64-darwin https://hydra.nixos.org/build/262793523). In my setup swift is only used by mpv so YMMV.
(final: prev: let
  pkgsDarwin= import darwin-nixpkgs {inherit (prev) system;};
in
  prev.lib.optionalAttrs prev.stdenv.hostPlatform.isDarwin {
    inherit (pkgsDarwin) swift;
  })

where
    darwin-nixpkgs.url = "github:nixos/nixpkgs?rev=2e92235aa591abc613504fde2546d6f78b18c0cd";

in flake.inputs.

Thanks @yelite for your flakes workaround
I don't use flakes myself, so one workaround I'm using for the moment is excluding all packages that pull in swift as a dependency.
To do this:

I generated a derivation of my next system rebuild
looked at the dependency tree, found out which packages are pulling in swift
excluded them from my darwin-configuration.nix
repeated the above steps, removing packages until swift no longer appeared

Here are the commands... I generated a derivation my next rebuild by using --dry-run:
$ darwin-rebuild switch --dry-run
building the system configuration...
trace: warning: nixfmt was renamed to nixfmt-classic. The nixfmt attribute may be used for the new RFC 166-style formatter in the future, which is currently available as nixfmt-rfc-style
these 107 derivations will be built:
/nix/store/9cvhkxbx69pd8w9kw9xwcccn98bxdwc6-swift-5.8.drv
/nix/store/52bvqras0kmavb9x7mg5x2w8bjkfwwkc-swift-wrapper-5.8.drv
/nix/store/84a9v245r6829j6spf61bbv72a70s409-fix-stdlib-path.patch.drv
...
/nix/store/i37yr1qrlg15cjrv1rj5rmvsnrwh3asa-darwin-system-24.05pre634371.29e8e22b42cc+darwin4.drv

That's my next derivation there on the last line. I turned this next derivation into a dependency tree (i output it to a file so I could browse it a bit easier):
nix-store --query --tree /nix/store/i37yr1qrlg15cjrv1rj5rmvsnrwh3asa-darwin-system-24.05pre634371.29e8e22b42cc+darwin4.drv > ~/output_dependencies_next

After squinting hard at that file for a bit, it turns out that mpv, or anything that uses mpv, will also need to pull in swift. Which is unfortunate, because mpv is pretty incredible and I'd hate to go without it. I excluded mpv, and a few other packages like yt-dlp, somafmcli and curseradio
I repeated the above steps and generated a dependency tree of my next generation, and when I saw that swift wasn't included, I was finally able to run darwin-rebuild switch to completion

FWIW Swift is getting fixed as we speak as part of the macOS SDK rework. That’s still a few weeks out from landing in unstable, though.

swift is now failing to build on Linux. It's a transitive dependency of deadbeef (an audio player). The direct dependency is swift-corelibs-libdispatch.
The build error occurs when running swig to create Python bindings:
FAILED: bindings/python/LLDBWrapPython.cpp bindings/python/lldb.py /build/build/lldb/bindings/python/LLDBWrapPython.cpp /build/build/lldb/bindings/python/lldb.py
cd /build/build/lldb/bindings/python && /nix/store/alain6ji648fj2fl073sag1324xr9ivd-python3-3.12.5-env/bin/python3.12 /build/src/llvm-project/lldb/bindings/prepare_bindings.py --srcRoot=/build/src/llvm-project/lldb --targetDir=/build/build/lldb/bindings/python --cfgBldDir=/build/build/lldb/bindings/python --prefix=/build/build/lldb --swig-executable=/nix/store/ssm2qdxyzffs94ivzs2irblnah23b7bd-swig-4.2.1/bin/swig
ERROR:root:swig failed with error code 1: stdout=b'', stderr=b"/build/src/llvm-project/lldb/bindings/interfaces.swig:5: Error: Macro '__STDC_LIMIT_MACROS' redefined,\n:EOF: Error: previous definition of '__STDC_LIMIT_MACROS'.\n"
ERROR:root:command line:
/nix/store/ssm2qdxyzffs94ivzs2irblnah23b7bd-swig-4.2.1/bin/swig -c++ -shadow -python -features autodoc -threads -I/build/src/llvm-project/lldb/include -I/build/src/llvm-project/lldb/bindings -I/build/src/llvm-project/lldb/bindings/python -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -outdir /build/build/lldb/bindings/python -o /build/build/lldb/bindings/python/LLDBWrapPython.cpp /build/src/llvm-project/lldb/bindings/python/python.swig

It’s a SWIG 4 issue; I’m working on it.
FWIW the Darwin SDK rework is not going to significantly change a lot of the problems with the Swift derivation. It’s pretty unmaintainable right now. If anyone is strongly invested in Swift, I strongly suggest trying to factor out their LLVM from the core Swift derivations. Right now it spends so much time building its own LLVM and Clang and so on. I don’t know whether the use of their specific LLVM fork is mandatory. If it isn’t, then we should just use the existing packages from Nixpkgs. If it is required, then it should at least be built with the LLVM package machinery we already have in‐tree so that we don’t have to duplicate patches and other complexity.

https://github.com/NixOS/nixpkgs/pull/341384

The PR has now been merged and I successfully built Swift on aarch64-linux and x86_64-darwin. Would be good to hear more build reports to see if the problem here is fixed. We still don’t know what’s up with the builds on Hydra, though.

Works for me, using commit 418918ebb102 from master, on an x86_64-linux system.
Thanks for fixing this! :raised_hands:

Works for me as well on aarch64-darwin!

The PR has now been merged and I successfully built Swift on aarch64-linux and x86_64-darwin. Would be good to hear more build reports to see if the problem here is fixed. We still don’t know what’s up with the builds on Hydra, though.

Thanks Emily, i hadn't been using swift stuff for a bit and can confirm it fixed the issues I was having on my builds.

The PR has now been merged and I successfully built Swift on aarch64-linux and x86_64-darwin. Would be good to hear more build reports to see if the problem here is fixed. We still don’t know what’s up with the builds on Hydra, though.

Does hydra weirdness mean this? https://hydra.nixos.org/build/272581651/nixlog/1

Yes. The hope is that Randy’s SDK rework will make it go away, but I don’t think anyone understands it. It builds locally for everyone, as far as I know.

The PR has now been merged and I successfully built Swift on aarch64-linux and x86_64-darwin. Would be good to hear more build reports to see if the problem here is fixed. We still don’t know what’s up with the builds on Hydra, though.

I have tried this on macOS 15.0 x86_64 and it builds failed 😭
 - system: `"x86_64-darwin"`
 - host os: `Darwin 24.0.0, macOS 10.16`
 - multi-user?: `yes`
 - sandbox: `relaxed`
 - version: `nix-env (Nix) 2.18.5`
 - nixpkgs: `/nix/store/cjz8w4dgc3rd2n3dqv5c208vygndjyba-source`

swift.log

Same failure when bumping devenv-nixpkgs: https://github.com/cachix/devenv/actions/runs/11140734654/job/30961906452?pr=1489#step:7:4516

Can someone try building swift on https://github.com/NixOS/nixpkgs/pull/346043

Can someone try building swift on #346043

Swift is definitely broken on #346043. I have a separate set of fixes for building Swift after that is merged. I’ll be opening that (and others) later today, but it won’t be able to merge until after that PR is merged.

https://github.com/NixOS/nixpkgs/pull/346947 is the follow up PR for Swift that fixes it to build with the new SDK.

I’ve asked in the infrastructure room. Though it seems hard to relate weird linker errors to builds hanging. It kind of looks more like Swift broke during a staging cycle, but the fact that it only happens on Hydra implies something must be really weird. We thought it might be the 256 file descriptor limit on Hydra that we’re in the process of fixing causing errors in the linker, but it doesn’t seem to be. If anyone wants to try and figure it out, I suggest starting at https://github.com/apple-oss-distributions/ld64/blob/47f477cb721755419018f7530038b272e9d0cdea/src/ld/InputFiles.cpp#L786 and looking for every throw that could be leading to that line of code.

I'm glad that swift now builds on hydra. However I'm still confused because when I update my flake with unstable nixpkgs channel, my config still needs to build swift from source and can find a cached binary (in this case swift-5.8 for aarch64-darwin). What am I still missing?

@shishkin it has only fixed for 3 days on master: https://hydra.nixos.org/jobset/nixpkgs/trunk#tabs-jobs (filter for swiftPackages.swift-unwrapped). It is yet to be propagated to unstable: https://nixpk.gs/pr-tracker.html?pr=354192

Thanks @YorikSar! The PR tracker was the missing piece. Extra nice would be for CI pipeline to tag PRs once they reach various channels.


Mega.nz file download support

I have recently got access to creator with a lot of mega.nz links, so I plan to make mega.nz plugin available starting with 0.9.4

Implemented in 977aec6d8375e76303db7d72da805087d124df17

Implemented in 977aec6d8375e76303db7d72da805087d124df17


Emojis not rendering in picker

Hello, I've been using the emoji-mart and I noticed that the picker no longer seems to show the emojis (to click), but it only occurs on the live version and not within my local. There is no difference with the code to call it and I'm using angular 7

It appears as above on live, but normally on local and it seems to render everything except the emojis themselves? Below is how I am referencing it on the HTML level
<div *ngIf="emoji">           <emoji-mart             style="zoom: 70%; width: 24em;"             title="Pick your emoji"             isNative="true"             emoji="point_up"             set="emojione"             [style]="{ position: 'absolute', bottom: '2.6em', right: '0px'}"             (emojiClick)="addEmoji($event); emoji=false;"           >           </emoji-mart>         </div>

Yes, there seems to be some error in latest release

@scttcper please have a look latest version has this issue.

what version of angular are you using

@scttcper Alright I was able to find the issue. It seems like quill.snow.css is overriding emoji-mart's css.
Specifically if emoji-mart is triggered from quill-toolbar. The following css from quill-snow override emoji-mart-emoji css.
CSS from .ql-snow.ql-toolbar button, .ql-snow .ql-toolbar button overrides emoji-mart-emoji.
Adding following specifically to emoji-mart-emoji solved the issue for me:
.emoji-mart-emoji{
            float:none;
            height: 36px;
            width: 36px;
            padding: 6px;
        }

should no longer be an issue


git_version output is not consistent between platforms

git_version is (indirectly) used by the network protocol to check if the client is on the same version of Ambient as the server. Unfortunately, this is not necessarily consistent between platforms:

Server version: "0.3.0-dev-c2ed491", Client version "0.3.0-dev-c2ed4913"

We can fix this by

checking for the common prefix
finding a version of git_version!() that will return the full hash
using some other kind of versioning identifier

Fixed by #566


BTC-e TickerFetchIntegration test failing on SSL handshake.

On develop branch at e905c9dd3e1710aa65a94ccceca757b3e27007fb the attempt to run TickerFetchIntegration test for xchange-btce is failing with the complaint about the certificate:
javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
This appears to be related to another issue https://github.com/timmolter/XChange/issues/52 .
This also happens when trying to fetch account data. Switching to compiling XChange-btce with java 6 on my machine fixes this problem.

Looks like this is only with Java 7, at least on Mac OS 10.10.2. Switching to Java 8 40 solves the problem as well. BTC-e is now using a certificate issued by GoDaddy and so the JVM in 8 must have GoDaddy's root CA certificate installed.
keytool -list -keystore /Library/Java/JavaVirtualMachines/jdk1.8.0_40.jdk/Contents/Home/jre/lib/security/cacerts | grep godaddy

gives
godaddyclass2ca, Jan 20, 2005, trustedCertEntry,
godaddyrootg2ca, Jul 18, 2014, trustedCertEntry,

so it looks like the latter CA cert is the one required for BTC-e's current certificate on their website.

Yup, that's the issue. You can read more about it here: https://github.com/timmolter/XChange/issues/52


when i am using md2-datepicker in my project,it works fine in chrome browser but it fails in safari.In safari, it display as NaN format instead of date format.

Can anyone help me out?

@Muthu2020 please use md2-datepicker -> https://github.com/Promact/md2/tree/master/src/lib/datepicker instead of this, it is also maintained by us.


Space leak debugging

12,149,072,728 bytes allocated in the heap
6,452,897,264 bytes copied during GC
449,287,768 bytes maximum residency (30 sample(s))
12,132,960 bytes maximum slop
1143 MB total memory in use (0 MB lost due to fragmentation)
                                 Tot time (elapsed)  Avg pause  Max pause

Gen  0     23373 colls, 23373 par   21.256s   6.547s     0.0003s    0.0188s
Gen  1        30 colls,    29 par    5.464s   1.448s     0.0483s    0.3468s
Parallel GC work balance: 4.31% (serial 0%, perfect 100%)
TASKS: 18 (1 bound, 17 peak workers (17 total), using -N8)
SPARKS: 0 (0 converted, 0 overflowed, 0 dud, 0 GC'd, 0 fizzled)
INIT    time    0.000s  (  0.001s elapsed)
MUT     time    6.424s  (  5.796s elapsed)
GC      time   26.720s  (  7.995s elapsed)
RP      time    0.000s  (  0.000s elapsed)
PROF    time    0.000s  (  0.000s elapsed)
EXIT    time    0.008s  (  0.063s elapsed)
Total   time   33.184s  ( 13.855s elapsed)
Alloc rate    1,891,200,611 bytes per MUT second
Productivity  19.5% of total user, 42.3% of total elapsed

21 seconds spent in Gen 0 GC!
MUT (program) time is 6.424, GC time is 26.720s!

Diffarray
19,070,028,840 bytes allocated in the heap
6,286,571,472 bytes copied during GC
1,711,289,152 bytes maximum residency (24 sample(s))
516,489,440 bytes maximum slop
3374 MB total memory in use (0 MB lost due to fragmentation)
                                 Tot time (elapsed)  Avg pause  Max pause

Gen  0     32668 colls, 32668 par   54.400s  16.413s     0.0005s    0.0362s
Gen  1        24 colls,    23 par   11.380s   3.136s     0.1307s    1.2221s
Parallel GC work balance: 3.65% (serial 0%, perfect 100%)
TASKS: 18 (1 bound, 17 peak workers (17 total), using -N8)
SPARKS: 0 (0 converted, 0 overflowed, 0 dud, 0 GC'd, 0 fizzled)
INIT    time    0.000s  (  0.001s elapsed)
MUT     time   22.260s  ( 14.376s elapsed)
GC      time   65.780s  ( 19.549s elapsed)
RP      time    0.000s  (  0.000s elapsed)
PROF    time    0.000s  (  0.000s elapsed)
EXIT    time    0.056s  (  0.178s elapsed)
Total   time   88.144s  ( 34.105s elapsed)
Alloc rate    856,694,916 bytes per MUT second
Productivity  25.4% of total user, 42.7% of total elapsed

1024 size
47,963,241,280 bytes allocated in the heap
10,077,488,944 bytes copied during GC
342,391,944 bytes maximum residency (54 sample(s))
13,409,088 bytes maximum slop
936 MB total memory in use (0 MB lost due to fragmentation)
                                 Tot time (elapsed)  Avg pause  Max pause

Gen  0     91646 colls, 91646 par   46.760s  10.829s     0.0001s    0.0288s
Gen  1        54 colls,    53 par    9.124s   2.992s     0.0554s    0.3584s
Parallel GC work balance: 0.91% (serial 0%, perfect 100%)
TASKS: 18 (1 bound, 17 peak workers (17 total), using -N8)
SPARKS: 0 (0 converted, 0 overflowed, 0 dud, 0 GC'd, 0 fizzled)
INIT    time    0.000s  (  0.001s elapsed)
MUT     time   31.672s  ( 24.047s elapsed)
GC      time   55.884s  ( 13.821s elapsed)
RP      time    0.000s  (  0.000s elapsed)
PROF    time    0.000s  (  0.000s elapsed)
EXIT    time    0.008s  (  0.042s elapsed)
Total   time   87.604s  ( 37.911s elapsed)
Alloc rate    1,514,373,619 bytes per MUT second
Productivity  36.2% of total user, 63.5% of total elapsed

16 byte cache
46,265,546,408 bytes allocated in the heap
9,648,332,584 bytes copied during GC
340,806,560 bytes maximum residency (54 sample(s))
13,250,288 bytes maximum slop
928 MB total memory in use (0 MB lost due to fragmentation)
                                 Tot time (elapsed)  Avg pause  Max pause

Gen  0     88424 colls, 88424 par   41.356s  10.013s     0.0001s    0.0271s
Gen  1        54 colls,    53 par   10.120s   3.177s     0.0588s    0.3353s
Parallel GC work balance: 0.35% (serial 0%, perfect 100%)
TASKS: 18 (1 bound, 17 peak workers (17 total), using -N8)
SPARKS: 0 (0 converted, 0 overflowed, 0 dud, 0 GC'd, 0 fizzled)
INIT    time    0.000s  (  0.001s elapsed)
MUT     time   28.896s  ( 22.150s elapsed)
GC      time   51.476s  ( 13.191s elapsed)
RP      time    0.000s  (  0.000s elapsed)
PROF    time    0.000s  (  0.000s elapsed)
EXIT    time    0.004s  (  0.050s elapsed)
Total   time   80.420s  ( 35.391s elapsed)
Alloc rate    1,601,105,565 bytes per MUT second
Productivity  36.0% of total user, 62.7% of total elapsed

32768 cache size
37,413,674,960 bytes allocated in the heap
9,884,671,208 bytes copied during GC
328,210,288 bytes maximum residency (64 sample(s))
64,172,536 bytes maximum slop
880 MB total memory in use (0 MB lost due to fragmentation)
                                 Tot time (elapsed)  Avg pause  Max pause

Gen  0     61233 colls, 61233 par   68.788s  19.680s     0.0003s    0.0305s
Gen  1        64 colls,    63 par   19.460s   4.767s     0.0745s    0.2503s
Parallel GC work balance: 4.72% (serial 0%, perfect 100%)
TASKS: 18 (1 bound, 17 peak workers (17 total), using -N8)
SPARKS: 0 (0 converted, 0 overflowed, 0 dud, 0 GC'd, 0 fizzled)
INIT    time    0.000s  (  0.001s elapsed)
MUT     time   34.488s  ( 26.150s elapsed)
GC      time   88.248s  ( 24.447s elapsed)
RP      time    0.000s  (  0.000s elapsed)
PROF    time    0.000s  (  0.000s elapsed)
EXIT    time    0.012s  (  0.040s elapsed)
Total   time  122.788s  ( 50.638s elapsed)
Alloc rate    1,084,831,679 bytes per MUT second
Productivity  28.1% of total user, 51.7% of total elapsed


Question: Does it make any sense to still speak in terms of "planes"

As a vestige of the v1 documentation, the docs still reference things like "control plane" and "data plane."
Are these classification still useful to us?

This was fixed by #40


Finalized block that hasn't been proposed

Logs:
casper-logs.log
This Finalized block that hasn't been proposed error started showing up after I raised my bid in the auction.
Logs after restarting the node:
https://pastebin.com/a0GUqhzZ
System specs:
AMD Ryzen 9 3900 12c/24t
128GB DDR4 ECC
2x 2TB NVMe SSDs RAID0

It's probably harmless. Will be addressed as part of https://github.com/CasperLabs/ceps/pull/20.

@trader-payne Can you verify if the problem still occurs? According to our best knowledge it has been fixed.

@trader-payne Can you verify if the problem still occurs? According to our best knowledge it has been fixed.

Closing - we believe the issue has been fixed, and it hasn't appeared again.

Closing - we believe the issue has been fixed, and it hasn't appeared again.


Error (unexpected behavior) in projection of SVG image overlay

I have a vector graphic. I would like to partially (only some layers) display this graphic as a basic map. I exported most of the layers of this vector graphic as PNG-file and created tiles using Maptiler.
I saved the other layers as SVG-files and show them as an image overlay.
The PNG and the SVG-files have the same size ratio and the same bounding box. The PNG is 9726px  7950px and the SVG 4863,5px x 3975.7 px.
<svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px"
 width="4863.5px" height="3975.7px" viewBox="0 0 4863.5 3975.7" style="enable-background:new 0 0 4863.5 3975.7;"
 xml:space="preserve">

Unfortunately, the SVG files do not fit exactly over the tiles I created. There are small shifts. You can see it in the picture.

If I save the SVG-File as an PNG and load the PNG in the image overlay everything is fine!
I think there is something wrong with the projection. When creating the tiles, I tested with different coordinate systems. Among other things with EPSG:4326 (Bounding Box 7.088 51.401 7.365 51.541) and with EPSG:3857 (Bounding Box 789032.55 6692534.87 819868.05 6717554.10).
This is my code:

You can see a temporarily live demo here: https://fahrplan.astrid-guenther.de/

This is not a Leaflet bug, but rather an issue with the underlying data. Nothing to do here on the maintainers' part.

Thanks for your response. May I ask you something, as I do not understand:
What do you mean exactly? Do you mean: an SVG file in an image overlay is projected exactly like a PNG file and I didn't create the files correctly?
Or do you think that it is OK that an SVG file is projected differently than a PNG file?

I mean, it's normal that the streets don't match depending on the basemap or the dataset, and it's normal that map designers sway away from geographical accuracy in favour of readability (e.g. ignoring enclaves/exclaves, over/undersimplification, assuming a different stroke width or offset for the roads). All of those issues are real, but are out of the scope of what Leaflet does.


Reorganize Dockerfile

While reviewing this for https://github.com/docker-library/official-images/pull/1288, I figured it might be easier to just make a PR.  I made a couple commits to try to illustrate the reasons for the changes.

b34eabccc627c3c24fd8872709e8b5fd30e11460 was to reorder a few items like run dependencies, gosu, gpg keys, and user creation to be before the COUCHDB_VERSION so that those layers could be cached and possibly shared between versions of CouchDB.

I moved the keys to use the long fingerprints so that docker build cache is easier to break when a key gets added or removed from the list.  It also adds an extra layer of security where the getting the key fingerprint is separate from the build process.  The loop is to make it fail if only one key fails to download since gpg only fails if all keys fail.
switched to apache.osuosl.org for download since that will be closer/faster for the build server.  Is there a proxy that would redirect to the closest mirror?
also some whitespace changes to unify to 2 spaces per indent

d5952ff4bb15238c20b8c26ca1bc9d7d84b9aa17 helps differentiate build time vs run time dependencies, while also putting the installed build packages into a variable for easier remove after compilation.  Also switch to explicit gcc/g++ rather than build-essential, since that is for "building Debian packages".

The size difference isn't much, but it does save a little space:
REPOSITORY          TAG           IMAGE ID            CREATED             VIRTUAL SIZE
couchdb             new           5b373ff7d0d1        About an hour ago   226.4 MB
couchdb             old           dd39277a0793        About an hour ago   231 MB

Awesome, thank you :)
I'm not aware of an apache.org proxy that does geolocation.


ImportError: cannot import name global_preferences_registry

django-dynamic-preferences (0.8.2)
I am trying to run this project: https://github.com/mfomicheva/tradopad
And the following file fails: https://github.com/mfomicheva/tradopad/blob/master/rater/dynamic_preferences_registry.py

/Users/andy/tradopad/bin/python /Users/andy/Developer/tradopad/manage.py runserver 8000
Unhandled exception in thread started by <function wrapper at 0x10a8cc848>
Traceback (most recent call last):
File "/Users/andy/tradopad/lib/python2.7/site-packages/django/utils/autoreload.py", line 226, in wrapper
fn(args, **kwargs)
File "/Users/andy/tradopad/lib/python2.7/site-packages/django/core/management/commands/runserver.py", line 113, in > inner_run
autoreload.raise_last_exception()
File "/Users/andy/tradopad/lib/python2.7/site-packages/django/utils/autoreload.py", line 249, in raise_last_exception
six.reraise(_exception)
File "/Users/andy/tradopad/lib/python2.7/site-packages/django/utils/autoreload.py", line 226, in wrapper
fn(*args, **kwargs)
File "/Users/andy/tradopad/lib/python2.7/site-packages/django/init.py", line 27, in setup
apps.populate(settings.INSTALLED_APPS)
File "/Users/andy/tradopad/lib/python2.7/site-packages/django/apps/registry.py", line 115, in populate
app_config.ready()
File "/Users/andy/tradopad/lib/python2.7/site-packages/dynamic_preferences/apps.py", line 19, in ready
global_preferences_registry.autodiscover(settings.INSTALLED_APPS)
File "/Users/andy/tradopad/lib/python2.7/site-packages/persisting_theory/registries.py", line 107, in autodiscover
module = import(package)
File "/Users/andy/Developer/tradopad/rater/dynamic_preferences_registry.py", line 4, in
from dynamic_preferences import global_preferences_registry
ImportError: cannot import name global_preferences_registry

The correct way to import global_preferences_registry seems to be from dynamic_preferences.registries import global_preferences_registry -- but it doesn't work either (the same error). I've been only able to do from dynamic_preferences.registries import user_preferences_registry

Thank you for reporting this. I cannot reproduce this locally. The correct way to import the global_preferences_registry is from dynamic_preferences.registries, as shown, for example, in the project documentation.
I've cloned your project on my local computer and if i replace from dynamic_preferences import global_preferences_registry by from dynamic_preferences.registries import global_preferences_registry, the project loads successuflly. Can you confirm this modification works on your side ?

Indeed, the project was simply using a wrong way to import the registry. I almost figured it out yesterday but probably messed up something else. Thank you very much for taking your time and for referring me to the documentation. The ticket can be closed.

On 06 Sep 2016, at 18:57, Eliot Berriot<EMAIL_ADDRESS>wrote:
Thank you for reporting this. I cannot reproduce this locally. The correct way to import the global_preferences_registry is from dynamic_preferences.registries, as shown, for example, in the project documentation http://django-dynamic-preferences.readthedocs.io/en/latest/quickstart.html.
I've cloned your project on my local computer and if i replace from dynamic_preferences import global_preferences_registry by from dynamic_preferences.registries import global_preferences_registry, the project loads successuflly. Can you confirm this modification works on your side ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/EliotBerriot/django-dynamic-preferences/issues/61#issuecomment-244998491, or mute the thread https://github.com/notifications/unsubscribe-auth/AIDKDjPcGbIeAWLe83C26EOmQinehushks5qnY14gaJpZM4J19OQ.

No problem, I'm glad it's fixed for you :)


Carmen161's file

Step 4: Creating a Branch
Your first branch
Navigate to the Code tab
Click Branch: main in the drop-down
In the field, enter a name for your branch, like my-slide
Click Create branch: or press the Enter key to create your branch
Step 5: Your first commit
The following steps will guide you through the process of committing a change on GitHub.
Create a new file on this branch, in a _posts folder called 0000-01-02-Carmen161.md. You can do so using this shortcut or manually as follows:
Return to the "Code" tab
In the branch drop-down, select "my-slide"
Click Create new file
In the "file name" field, type _posts/0000-01-02-Carmen161.md. Entering the / in the filename will automatically place your file in the _posts directory.
When you’re done naming the file, add the following content to your file:
layout: slide
title: "Welcome to our second slide!"
Your text
Use the left arrow to go back!
After adding the text, you can commit the change by entering a commit message in the text-entry field below the file edit view. For guidelines on commit messages, check out the Commits 101 drop-down, just above these instructions
When you’ve entered a commit message, click Commit new file
Step 6: Create a pull request
Open a pull request using this shortcut or manually as follows:
From the "Pull requests" tab, click New pull request
In the "base:" drop-down menu, make sure the "main" branch is selected
In the "compare:" drop-down menu, select "my-slide"
When you’ve selected your branch, enter a title for your pull request. For example Add Carmen161's file
The next field helps you provide a description of the changes you made. Feel free to add a description of what you’ve accomplished so far. As a reminder, you have: created a branch, created a file and made a commit, and opened a pull request
Click Create pull request

Step 8: Merge the pull request
Merge the pull request
Click Merge pull request
which is at the bottom of the conversation tab when you're in the pull request larger tab
Click Confirm merge
Once your branch has been merged, you don't need it anymore. Click Delete branch.


Docs incorrectly state the all boot settings will be displayed in the API

Advanced boot settings states the following:

Any values added to config.txt will be added to the {{ $names.cloud.lower }} API during device provisioning and displayed on the dashboard.

However, udev rules are not displayed in the dashboard.

Yeah, that doesn't sound right. @codewithcheese do make a PR to rectify this.


Adding Example-4 skeleton. Commenting position_only compilation due t…

…o duplicate class.

Codecov Report

Merging #120 (3b205e7) into master (bf32f38) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           master    #120     +/-   ##
========================================
  Coverage    0.00%   0.00%
========================================
  Files          33       3     -30
  Lines        3234     383   -2851
========================================
+ Misses       3234     383   -2851

Flag
Coverage Δ

unittests
0.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...demo_hardware/src/rrbot_system_multi_interface.cpp

...l_demo_hardware/src/rrbot_system_position_only.cpp

.../ros2_control_demo_hardware/src/diffbot_system.cpp

.../ros2_control_demo_hardware/src/diffbot_system.cpp

...l_demo_hardware/src/rrbot_system_position_only.cpp

.../ros2_control_demo_hardware/src/diffbot_system.cpp

...l_demo_hardware/src/rrbot_system_position_only.cpp

...demo_hardware/src/rrbot_system_multi_interface.cpp

...l_demo_hardware/src/rrbot_system_position_only.cpp

...demo_hardware/src/rrbot_system_multi_interface.cpp

... and 26 more

Continue to review full report at Codecov.

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


Moving constants to separate constants class, maintaining old menu selections, and improving gamepad support

This change does the following:

Moves a number of constants that could hypothetically/actually be shared across classes into its their own class.
Changes the way submit/cancel/move events happen to make it simpler and to include gamepad support
Stops deleting menus when the menu is exited so that the same options as before are selected when you leave &* re-enter the menu.

Testing:

Verified that you can leave & exit the menu multiple times
Verified that same menu options as before are selected if you leave & re-enter the spawn menu
Verified that L/R/U/D, Cancel, and Submit work with both keyboard & gamepad (including analog sticks & dpad)

LGTM!


Steps to archive the lincbrain-cli package

Once https://github.com/dandi/dandi-cli/pull/1527 is merged and a new dandi-cli version is released, let's archive the lincbrain-cli.  The following items need to be addressed in this process:

[ ] Update the README of this GitHub repository to point users to the dandi-cli
[ ] Update the Project description on the PyPI project to point users to the dandi-cli
[x] Update the LINC docs - https://github.com/lincbrain/linc-docs/pull/29

[x] Update the navigation bar to point to the dandi readthedocs site
[x] Update the Welcome page
[x] Update the Upload data page to replace lincbrain and lincbrain-cli with dandi

[ ] Update LINC Data Platform

[x] https://github.com/lincbrain/linc-archive/pull/276
[ ] https://github.com/lincbrain/linc-archive/pull/279

[ ] Update Dandi Hub - https://github.com/dandi/dandi-hub/pull/205
[ ] Archive the lincbrain-cli PyPI project
[x] ~Archive~ Delete the lincbrain readthedocs site
[ ] Archive the linc-cli GitHub repository
[ ] Make an announcement on the LINC Slack #general channel

cc @aaronkanzer

Hi @aaronkanzer, after second thought, I am going to hold off on making the announcement until these items are resolved.

Hi @aaronkanzer, after second thought, I am going to hold off on making the announcement until these items are resolved.

Sounds good -- if you are happy with https://github.com/lincbrain/linc-cli/pull/67, ill archive LINC CLI across all our tooling

Great work, @aaronkanzer.  I'll go ahead and make the announcement and archive this repository.
We can work on https://github.com/dandi/dandi-hub/pull/205 whenever you get a chance.


On docker plugin, how to use custon trusted ca certificate?

I have seen that i can set trustedCertsFile on this doc: docs/user-guide/config.md
But how can i  set then on docker plugin?

Hi @sebglon,
The plug-ins are not meant to access remote libStorage API endpoints, but rather are each a self-contained libStorage client and server. Thus no TLS is necessary. If you're wanting to set the cacerts path because you think it is used for general TLS, that's incorrect. The property to which you're referring is only specific to libStorage client->server communications.

Hi @sebglon,
Also, if you want, you can always just place a file at /etc/libstorage/tls/cacerts. It will be detected and loaded as the cacerts file since that is the default path. However, this will also enable TLS for libStorage client->server communications, and may have unintended consequences (such as enabling TLS without also providing a client/server key pair).

One more point to support what @akutz is saying. TLS would be beneficial
with plugins when they are communicating separately to a controller. Here
you would use a plugin called rexray/agent and separately a plugin called
rexray/controller. We intend (through contribution or {code} efforts) to
make other standalone plugins available and also these agent and controller
plugins.
So today you can either 1) use standalone plugins (without TLS) 2) use
REX-Ray outside of plugins with TLS 3) create your own REX plugins that
specify proper paths and parameters.
On Wed, May 17, 2017 at 11:05 AM, Schley Andrew Kutz <
<EMAIL_ADDRESS>wrote:

Hi @sebglon https://github.com/sebglon,
Also, if you want, you can always just place a file at
/etc/libstorage/tls/cacerts. It will be detected and loaded as the cacerts
file since that is the default path. However, this will also enable TLS for
libStorage client->server communications, and may have unintended
consequences (such as enabling TLS without also providing a client/server
key pair).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/codedellemc/rexray/issues/862#issuecomment-302176705,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABVMMbFXRf3TBHcn_6Pmt98ZKjOU3S-Wks5r6zbygaJpZM4NeNiN
.

Thank you @clintkitson. @sebglon, the libStorage client->server to which I referred is the same as Clint's statement:

TLS would be beneficial with plugins when they are communicating separately to a controller. Here you would use a plugin called rexray/agent and separately a plugin called rexray/controller.

In the above model the agent is the libStorage client and the controller is the libStorage server (as it were).
The reason I'm following up to what Clint added above is to clarify his statement about plug-ins sans TLS:

So today you can either 1) use standalone plugins (without TLS)

While Clint is accurate in his account above, I just wanted to make sure it was clear that the lack of TLS in REX-Ray managed plug-ins for Docker is not a security issue. The fact is that REX-Ray managed plug-ins today do not have the capability to be configured in a client->remote controller model, rather both the client and controller are both operating inside the plug-in container.

Thant i want to make is to use docker pugin cinder with custom authURL with https.
But my https url use custom ca-cert that i have added on my centos trusted ca-certificates.
But i have an PKI error.

#859

Hi @sebglon,
In your case the libStorage cacerts file will prove of little help. As I said, it's not for general TLS, only for libStorage's own client->server communiques.
In your case I recommend you edit your Cinder's Dockerfile so that it copies your custom cacerts file to the image's trusted certificate file. The REX-Ray Dockerfiles are all Alpine based, so look here for informaiton on how to update Alpine's TLS trusted cert chain with your custom certificate.

this is my error when i call an https cinder server:
msg=REX-Ray
Binary: /usr/bin/rexray"
Flavor: client+agent+controller"
SemVer: 0.9.0+11+dirty"
OsArch: Linux-x86_64"
Branch: master"
Commit: e46c4324f52779a8ce0b34647b4bcb85c4b6130a"
Formed: Wed, 17 May 2017 14:42:21 UTC"
SemVer: 0.6.0"
OsArch: Linux-x86_64"
Branch: (detached from fa055d6"
Commit: fa055d6da595602715bdfd5541b4aa6d4dcbcbd9"
Formed: Wed, 17 May 2017 14:41:50 UTC"
time=\"2017-05-18T07:22:29Z\" level=panic msg=\"runtime error: comparing uncomparable type pkix.Name\" " plugin=b7c1efb1c92cde4cd981cbd017bed5792
panic: runtime error: comparing uncomparable type pkix.Name [recovered]"
\tpanic: runtime error: comparing uncomparable type pkix.Name [recovered]" plugin=b7c1efb1c92cde4cd981cbd017bed579214ca04e3b25bfcbea9049a9292082a
\tpanic: (*logrus.Entry) (0xaba360,0xc4224d72c0)"
goroutine 1 [running]:"
github.com/codedellemc/rexray/vendor/github.com/Sirupsen/logrus.Entry.log(0xc420010c80, 0xc422502120, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0xc4224d
\t/go/src/github.com/codedellemc/rexray/vendor/github.com/Sirupsen/logrus/entry.go:113 +0x28c" plugin=b7c1efb1c92cde4cd981cbd017bed579214ca04e3b2
github.com/codedellemc/rexray/vendor/github.com/Sirupsen/logrus.(*Entry).Panic(0xc420a00030, 0xc420a00110, 0x1, 0x1)" plugin=b7c1efb1c92cde4cd981
\t/go/src/github.com/codedellemc/rexray/vendor/github.com/Sirupsen/logrus/entry.go:169 +0x14b" plugin=b7c1efb1c92cde4cd981cbd017bed579214ca04e3b2
github.com/codedellemc/rexray/vendor/github.com/Sirupsen/logrus.(*Logger).Panic(0xc420010c80, 0xc420a00110, 0x1, 0x1)" plugin=b7c1efb1c92cde4cd98
\t/go/src/github.com/codedellemc/rexray/vendor/github.com/Sirupsen/logrus/logger.go:163 +0xc7" plugin=b7c1efb1c92cde4cd981cbd017bed579214ca04e3b2
github.com/codedellemc/rexray/vendor/github.com/Sirupsen/logrus.Panic(0xc420a00110, 0x1, 0x1)" plugin=b7c1efb1c92cde4cd981cbd017bed579214ca04e3b2
\t/go/src/github.com/codedellemc/rexray/vendor/github.com/Sirupsen/logrus/exported.go:107 +0x4b" plugin=b7c1efb1c92cde4cd981cbd017bed579214ca04e3
github.com/codedellemc/rexray/cli/cli.(*CLI).Execute.func2()"
\t/go/src/github.com/codedellemc/rexray/cli/cli/cli.go:240 +0xf8"
panic(0xa26000, 0xc4224fd080)"
\t/usr/local/go/src/runtime/panic.go:489 +0x2cf"
github.com/codedellemc/rexray/cli/cli.(*CLI).execute.func1()"
\t/go/src/github.com/codedellemc/rexray/cli/cli/cli.go:260 +0xa8"
panic(0xa26000, 0xc4224fd080)"
\t/usr/local/go/src/runtime/panic.go:489 +0x2cf"
github.com/codedellemc/rexray/vendor/github.com/akutz/golf.isStructKind(0xc420a00530, 0xc420a003c8, 0xc420a003d0, 0xc4224fd000)" plugin=b7c1efb1c
\t/go/src/github.com/codedellemc/rexray/vendor/github.com/akutz/golf/golf.go:391 +0x11d" plugin=b7c1efb1c92cde4cd981cbd017bed579214ca04e3b25bfcbe
github.com/codedellemc/rexray/vendor/github.com/akutz/golf.parseValue(0xc420a00530, 0xc420a1a000, 0xab10a0, 0xc420717500, 0xab10a0)" plugin=b7c1e
\t/go/src/github.com/codedellemc/rexray/vendor/github.com/akutz/golf/golf.go:359 +0xa4" plugin=b7c1efb1c92cde4cd981cbd017bed579214ca04e3b25bfcbea
github.com/codedellemc/rexray/vendor/github.com/akutz/golf.fore(0xc422500d40, 0x14, 0xa825a0, 0xc420a1a000, 0xc422502030)" plugin=b7c1efb1c92cde4
\t/go/src/github.com/codedellemc/rexray/vendor/github.com/akutz/golf/golf.go:196 +0x71c" plugin=b7c1efb1c92cde4cd981cbd017bed579214ca04e3b25bfcbe
github.com/codedellemc/rexray/vendor/github.com/akutz/golf.fore(0xc4224fce50, 0xf, 0xa71ac0, 0xc422500c20, 0xc422502030)" plugin=b7c1efb1c92cde4c
\t/go/src/github.com/codedellemc/rexray/vendor/github.com/akutz/golf/golf.go:219 +0x3bb" plugin=b7c1efb1c92cde4cd981cbd017bed579214ca04e3b25bfcbe
github.com/codedellemc/rexray/vendor/github.com/akutz/golf.fore(0xc4224fcd20, 0xb, 0xa38680, 0xc4224dfef0, 0xc422502030)" plugin=b7c1efb1c92cde4c
\t/go/src/github.com/codedellemc/rexray/vendor/github.com/akutz/golf/golf.go:219 +0x3bb" plugin=b7c1efb1c92cde4cd981cbd017bed579214ca04e3b25bfcbe
github.com/codedellemc/rexray/vendor/github.com/akutz/golf.fore(0xacce03, 0x5, 0xa9faa0, 0xc422500c40, 0xc422502030)" plugin=b7c1efb1c92cde4cd981
\t/go/src/github.com/codedellemc/rexray/vendor/github.com/akutz/golf/golf.go:219 +0x3bb" plugin=b7c1efb1c92cde4cd981cbd017bed579214ca04e3b25bfcbe
github.com/codedellemc/rexray/vendor/github.com/akutz/golf.Fore(0xacce03, 0x5, 0xa9faa0, 0xc422500c40, 0xc422500c40)" plugin=b7c1efb1c92cde4cd981
\t/go/src/github.com/codedellemc/rexray/vendor/github.com/akutz/golf/golf.go:146 +0xbb" plugin=b7c1efb1c92cde4cd981cbd017bed579214ca04e3b25bfcbea
github.com/codedellemc/rexray/vendor/github.com/akutz/golf/logrus.(*TextFormatter).appendKeyValue(0xc42012b340, 0xc42013aa80, 0xacce03, 0x5, 0xa9
\t/go/src/github.com/codedellemc/rexray/vendor/github.com/akutz/golf/logrus/text_formatter.go:176 +0xaa" plugin=b7c1efb1c92cde4cd981cbd017bed5792
github.com/codedellemc/rexray/vendor/github.com/akutz/golf/logrus.(*TextFormatter).Format(0xc42012b340, 0xc4224d7200, 0x0, 0xc420a01160, 0x6fcffe
\t/go/src/github.com/codedellemc/rexray/vendor/github.com/akutz/golf/logrus/text_formatter.go:89 +0x481" plugin=b7c1efb1c92cde4cd981cbd017bed5792
github.com/codedellemc/rexray/vendor/github.com/Sirupsen/logrus.(*Entry).Reader(0xc4224d7200, 0xc429459202, 0xc4224d7200, 0x0)" plugin=b7c1efb1c9
\t/go/src/github.com/codedellemc/rexray/vendor/github.com/Sirupsen/logrus/entry.go:44 +0x40" plugin=b7c1efb1c92cde4cd981cbd017bed579214ca04e3b25b
github.com/codedellemc/rexray/vendor/github.com/Sirupsen/logrus.Entry.log(0xc42014f180, 0xc4224dffb0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x7000102, 0x
\t/go/src/github.com/codedellemc/rexray/vendor/github.com/Sirupsen/logrus/entry.go:94 +0x11f" plugin=b7c1efb1c92cde4cd981cbd017bed579214ca04e3b25
github.com/codedellemc/rexray/vendor/github.com/Sirupsen/logrus.(*Entry).Error(0xc4224d71c0, 0xc4224fc880, 0x1, 0x1)" plugin=b7c1efb1c92cde4cd981
\t/go/src/github.com/codedellemc/rexray/vendor/github.com/Sirupsen/logrus/entry.go:152 +0xd4" plugin=b7c1efb1c92cde4cd981cbd017bed579214ca04e3b25
github.com/codedellemc/rexray/vendor/github.com/codedellemc/libstorage/api/context.(*entry).Error(0xc4224fc870, 0xc4224fc880, 0x1, 0x1)" plugin=b
\t/go/src/github.com/codedellemc/rexray/vendor/github.com/codedellemc/libstorage/api/context/context_logger.go:228 +0x7c" plugin=b7c1efb1c92cde4c
github.com/codedellemc/rexray/util.activateLibStorage(0xdf85a0, 0xc4201fec00, 0xdf6580, 0xc420265d20, 0xc420265d20, 0x6, 0x0, 0xc4201450e8, 0x0,
\t/go/src/github.com/codedellemc/rexray/util/util_std_controller.go:129 +0xbb4" plugin=b7c1efb1c92cde4cd981cbd017bed579214ca04e3b25bfcbea9049a929
github.com/codedellemc/rexray/util.ActivateLibStorage(0xdf85a0, 0xc4201fec00, 0xdf6580, 0xc420265d20, 0xc4201ec230, 0x0, 0xc420192000, 0xc4200476
\t/go/src/github.com/codedellemc/rexray/util/util.go:429 +0x1ef"
github.com/codedellemc/rexray/daemon/module.InitializeDefaultModules(0xdf85a0, 0xc4201fec00, 0xdf64a0, 0xc42017f740, 0x0, 0x0, 0x0)" plugin=b7c1e
\t/go/src/github.com/codedellemc/rexray/daemon/module/module.go:147 +0x190" plugin=b7c1efb1c92cde4cd981cbd017bed579214ca04e3b25bfcbea9049a9292082
github.com/codedellemc/rexray/daemon.start(0xdf85a0, 0xc4201fec00, 0xdf64a0, 0xc42017f740, 0xc42015af60, 0x29, 0xc4201fec60, 0x0, 0x0, 0xc4200ba0
\t/go/src/github.com/codedellemc/rexray/daemon/daemon_std_agent.go:21 +0x67" plugin=b7c1efb1c92cde4cd981cbd017bed579214ca04e3b25bfcbea9049a929208
github.com/codedellemc/rexray/daemon.Start(0xdf85a0, 0xc4201fec00, 0xdf64a0, 0xc42017f740, 0xc42015af60, 0x29, 0xc4201fec60, 0x0, 0x0, 0x0)" plug
\t/go/src/github.com/codedellemc/rexray/daemon/daemon.go:27 +0xb1"
github.com/codedellemc/rexray/cli/cli.(*CLI).startDaemon(0xc420076900)"
\t/go/src/github.com/codedellemc/rexray/cli/cli/service.go:198 +0x452"
github.com/codedellemc/rexray/cli/cli.(*CLI).start(0xc420076900)"
\t/go/src/github.com/codedellemc/rexray/cli/cli/service.go:49 +0x247"
github.com/codedellemc/rexray/cli/cli.(*CLI).initServiceCmds.func2(0xc4201fd200, 0xc4202653e0, 0x0, 0x2)" plugin=b7c1efb1c92cde4cd981cbd017bed579
\t/go/src/github.com/codedellemc/rexray/cli/cli/cmds_04_service.go:32 +0x2a" plugin=b7c1efb1c92cde4cd981cbd017bed579214ca04e3b25bfcbea9049a929208
github.com/codedellemc/rexray/vendor/github.com/spf13/cobra.(*Command).execute(0xc4201fd200, 0xc420265200, 0x2, 0x2, 0xc4201fd200, 0xc420265200)"
\t/go/src/github.com/codedellemc/rexray/vendor/github.com/spf13/cobra/command.go:648 +0x234" plugin=b7c1efb1c92cde4cd981cbd017bed579214ca04e3b25b
github.com/codedellemc/rexray/vendor/github.com/spf13/cobra.(*Command).ExecuteC(0xc42006f200, 0xc420047d78, 0xc420047d70, 0xc42015a780)" plugin=b
\t/go/src/github.com/codedellemc/rexray/vendor/github.com/spf13/cobra/command.go:734 +0x339" plugin=b7c1efb1c92cde4cd981cbd017bed579214ca04e3b25b
github.com/codedellemc/rexray/vendor/github.com/spf13/cobra.(*Command).Execute(0xc42006f200, 0xaf91f0, 0xc4202068d0)" plugin=b7c1efb1c92cde4cd981
\t/go/src/github.com/codedellemc/rexray/vendor/github.com/spf13/cobra/command.go:693 +0x2b" plugin=b7c1efb1c92cde4cd981cbd017bed579214ca04e3b25bf
github.com/codedellemc/rexray/cli/cli.(*CLI).execute(0xc420076900)"
\t/go/src/github.com/codedellemc/rexray/cli/cli/cli.go:264 +0x4b"
github.com/codedellemc/rexray/cli/cli.(*CLI).Execute(0xc420076900)"
\t/go/src/github.com/codedellemc/rexray/cli/cli/cli.go:247 +0x71"
github.com/codedellemc/rexray/cli/cli.Execute(0xdf85a0, 0xc420052780)"
\t/go/src/github.com/codedellemc/rexray/cli/cli/cli.go:214 +0x43"
github.com/codedellemc/rexray/cli/rexray.Run()"
\t/go/src/github.com/codedellemc/rexray/cli/rexray/rexray.go:102 +0x435"
main.main()"
\t/go/src/github.com/codedellemc/rexray/cli/rexray/rexray/rexray-main.go:12 +0x20" plugin=b7c1efb1c92cde4cd981cbd017bed579214ca04e3b25bfcbea9049a
Sending SIGTERM to plugin failed with error: rpc error: code = 2 desc = containerd: container not found"
Sending SIGTERM to plugin failed with error: rpc error: code = 2 desc = containerd: container not found"

Hey guys - we have another scenario for custom certificates that would benefit us if we could provide the trusted certificate authorities during a plugin install.
We would like to install the rexrey s3fs docker plugin in a corporate environment, where all the egress traffic to the internet is made via an HTTP proxy.
Additionally to that, our corporate proxy intercepts, for inspection, all the TLS traffic and uses for that our own, company-internal CA certificates. That aspect requires us to update/change the trusted CA certificates on the clients, in order to prevent from TLS handshake errors.
Example of the rexray docker plugin we are trying to enable:
docker plugin install rexray/s3fs S3FS_ACCESSKEY=$S3_ACCESS_KEY S3FS_SECRETKEY=$S3_SECRET_KEY REXRAY_LOGLEVEL=debug
This was failing initially due to the need to define the HTTP_PROXY environment variable - but after talking with  @codenrhoden and his great help we manage to overcome that (also there is now a issue to update that: https://github.com/codedellemc/rexray/issues/933).  But then we faced the TLS handshake problem due to our internal CA certificates not being trusted by the "plugin".
We manage to build the plugin from the source and made it work by changing the trusted certificate authorities file ( /etc/ssl/certs/ca-certificates.cer) to include our own CA.
It would be great if we could provide our trusted CA file for the plugin to use during the install, without having to build the plugin from the source on our own.
That would be great and very much appreciated - Thanks ! 🙏

Besides proxies in a corporate network, another, these days also very common use-case would be self-hosted S3 compatible services such as for example Minio. When hosting a minio instance behind https using a certificate signed by an internal CA, one runs into the same problem.
Current workaround:
cp ca.pem /var/lib/docker/plugins/<plugin id>/rootfs/etc/ssl/certs
docker plugin enable rexray/s3fs

Thanks to @darkl0rd for putting me on the right track. I'm using FreeNAS's S3 service, which is done via minio and forces https. I use my pfsense router as my intranet's root CA, and that was already installed on my CentOS box. My commands were:
[me@centos ~]$ docker plugin install --disable rexray/s3fs \
S3FS_OPTIONS="allow_other,nonempty,use_path_request_style,url=https://freenas-s3-host.domain.local:9000"  \
S3FS_ACCESSKEY="accesskey" S3FS_SECRETKEY="secretkey" \
S3FS_ENDPOINT="https://freenas-s3-host.domain.local:9000" \
REXRAY_LOGLEVEL=debug
--alias s3fs \
--grant-all-permissions
[me@centos ~]$ sudo cp pfsense.pem /var/lib/docker/plugins/$(docker plugin ls --no-trunc | awk '/s3fs/ {print $1}')/rootfs/etc/ssl/certs
[me@centos ~]$ docker plugin enable s3fs:latest

It would be really nice to be able to use the docker host's trusted CA, or even just put some kind of notice about this workaround in the docs somewhere. I can't get this afternoon back ☹


Fixed #98: Reduced sleep times so test executes faster

IIUC the HTTP2 GHA CI tests are not running, making it unpossible to tell if this patch affects the tests it intends to modify.
@ganeshmurthy can you please mark this PR as a draft until HTTP2 GHA CI tests are running?  Thanks.

Marked this as draft. Thanks.


Ensure '', false, and False are accepted for include_reference_documentation

The config parameter include_reference_documentation is somehow rendered to a string when set in PyProject.toml, and the falsey check doesn't work.  This change checks the string values "", "false", and "False" to correctly enable this feature.
The second change ensures that in the case of empty string, include_reference_documentation="", there is no KeyError during cleanup.
I've retained the original truthy evaluation in case there is some code path that uses it, for example, if it gets it directly from the default config Python file.

Alternative to this PR is to correctly render the type as True or False.


Drag-and-Drop connection profile into groups is not working

Azure Data Studio Version: Insiders, 1.45-RC1
OS Version: Windows 11

Steps to Reproduce:

Create a connection
Create a server group
Drag connection to server group

Dragging fails with console error:
[error] No provider found for old URI : 'connection:providerName:MSSQL|authenticationType:Integrated|connectionName:New|server:localhost\MSSQLSERVER01|trustServerCertificate:true|groupId:C777F06B-202E-4480-B475-FA416154D458'
Error: Could not find provider for uri: connection:providerName:MSSQL|authenticationType:Integrated|connectionName:New|server:localhost\MSSQLSERVER01|trustServerCertificate:true|groupId:C777F06B-202E-4480-B475-FA416154D458
    at wa.changeConnectionUri (vscode-file://vscode-app/c:/Users/cmalhotra/AppData/Local/Programs/Azure%20Data%20Studio%20-%20RC1/resources/app/out/vs/workbench/workbench.desktop.main.js:2384:90841) [<root>]
    at wa.changeGroupIdForConnection (vscode-file://vscode-app/c:/Users/cmalhotra/AppData/Local/Programs/Azure%20Data%20Studio%20-%20RC1/resources/app/out/vs/workbench/workbench.desktop.main.js:2384:89896) [<root>]

Issue got introduced with #23758 and #23791 in both builds.

Fix verified in latest RC build.


fix(packaging): fix version number for fips build

Keep the '-fips' postfix if present

This needs to happen on our fork but I approved it here anyways.

Closing as there's no need for it to be in this repo.


First pass flow for Article lifecycle.

Acceptance Criteria

[x] I can visit /admin and be prompted for login credentials.
[x] After authenticating, I see an admin UI showing an index of Articles.
[ ] I can create a new Article, providing a title, summary, body, and published_at DateTime.
[ ] I can view an Article.
[ ] I can edit an Article.
[ ] I can delete an Article.
[ ] I can remove the published_at value to remove it from the public site.

The Public site home page can for everyone

[ ] List all the articles.
[ ] Render a specific article page, including markdown conten

Not Doing

No media uploads yet.
No pagination of the list yet.
No author concept.

So this ticket / branch blew up out of control, and I've decided to break down this work into smaller issues. I'm going to merge the branch as-is tonight.


Questions regarding roadmap for goad on Kubernetes/Openshift Cluster

Currently we can execute GOADs lambda functions on a local docker service. To be able to execute GOAD on a Kubernetes Cluster, Docker Swarm or Openshift we need to address two issues.
First GOADs commandline interface needs to be able to connect to the rabbitmq gathering the results of the individual test runners. Right now the cli tries to connect to a rabbitmq on a virtual docker network. A possible solutions would be to open an ssh tunnel to the docker swarm client that runs rabbitmq and map the port over to the local machine.
Secondly we need to provision the docker container with the goad runner code and payload. Right now a directory containing the code to be executed is mounted to the container. To remove this dependency to the local file system we could copy the code into the container and create a new container snapshot to be executed on the swarm, effectively baking the runner code into a container file system layer.

@cwaltken-edrans please revive the docker based WebUI... that should be an easy to use L&P that anybody can install in its Kubernetes cluster. On top of that, we need to reach (with ssh port forwarding) the same CLI UI behaviour as we have right now against AWS

k, this is on me


about the ferminet

How to satisfy the boundary condition about the ferminet

I'm sorry but I don't understand the problem you're having.

Please only open issues if there is something wrong with the code. If you have a well-defined question about how something works in the code, feel free to send us an email.


Feature Request: Checkout new branch should default to remote branch name

Is your feature request related to a problem? Please describe.
At my org, we typically create branches on our git server instead of locally to link them to work items. I fetch, then use b c in neogit to checkout the remote branch. Neogit prompts me to name the new local branch. To keep git happy - and to keep things consistent - I have to type out the entire branch name as it is on remote, which can get a bit lengthy. I do this all the time at work.
Describe the solution you'd like
I think neogit should handle this the same way magit does: When you b c a remote branch, it should autofill the new branch name with the remote branch name, minus "origin" (or whatever the remote is named). I presume this is what most people usually want when they do this anyway.

While not exactly the same (and not to say this isn't a good idea - it absolutely is), Coming Soon™, we'll introduce branches that only exist on remotes and NOT locally to the b l list, and if selected, will check out a new branch locally and set the upstream automatically.
https://github.com/CKolkey/neogit/blob/master/lua/neogit/popups/branch/actions.lua#L42:L65


Record can end up with nonexistent Job id

I have a situation where three of my records have a job_id that doesn't exist, and no idea how they got that way:
> db.record.find( { job_id : 7 } ).count()
3
> db.record.find( { job_id : 8 } ).count()
0
> db.record.find( { job_id : 6 } ).count()
657
> db.record.find( { job_id : 5 } ).count()
995
> db.record.find( { job_id : 4 } ).count()
993
> db.record.find( { job_id : 3 } ).count()
2976
> db.record.find( { job_id : 2 } ).count()
969
> db.record.find( { job_id : 1 } ).count()
3644
> db.record.find( { job_id : 0 } ).count()
0

Pretty sure this is caused by deleting a Job from MySQL, which does not sync with mongo


Revert "Put all generated code in the build/ directory."

Reverts chipsalliance/UHDM#485
Please fix the Surelog build issues.

Well, you first have to have this here, so that I can patch Surelog and update the submodule there in a controlled manner.
You can't update the module in Surelog yet.


Breaking change in Firebase ^9.0.2 (Solution)

In the latest version of firebase (^9.0.2), there's no default export in "firebase/app".
You can get this working by modifying the import in gatsby-plugin-firebase/src/firebase.js as follows:
import firebase from "firebase/app"; → import firebase from "firebase/compat/app";

Is there a reason why there hasn't been any PR to fix this? I feel like it isn't right to modify files found inside the node_modules folder.

Now Firebase version 10 has completely changed things...for the better. Will the gatsby-plugin-firebase be updated to implement this to take advantage of the upgrade?


pull request for e2e test at 01/26/2017 20:45:10

:white_check_mark: Validation status: passed
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.


build: avoid use of ts-node wrapper script as it breaks child process forking

ts-node spawns a custom node launcher script and has a brotli-base64
encoded configuration that will point to the user-provided entry-point.
This breaks child process forking as we wouldn't be able to specify our
custom build worker and basically ng-dev would run inside ng-dev
again.

14.0.x-specific patch in #23424.


Improve Input JSON schemas

Description
Changes proposed in this pull request:

Improve Input JSON schemas

Fix encountered issues
Improve rendering of some JSON schemas in Dashboard

Screenshots
Example screenshot:

Testing

Make sure you have the latest Capact CLI (see instruction https://capact.io/docs/next/cli/getting-started#latest---from-the-latest-main-commit)
Run:

# Create local cluster
capact environment create kind --wait 5m
# Install Capact from latest charts
export SOURCE_REPO_URL="github.com/pkosiec/hub-manifests"
export SOURCE_REPO_REF="fix-schemas"
capact install \
            --verbose \
            --helm-repo=@latest \
            --version=@latest \
            --capact-overrides="hub-public.populator.enabled=true,hub-public.populator.manifestsLocation.repository=${SOURCE_REPO_URL},hub-public.populator.manifestsLocation.branch=${SOURCE_REPO_REF}"

Navigate to the https://dashboard.capact.local/ and log in according to the instructions on https://ui-docs.capact-website.pages.dev/docs/next/dashboard-ui/overview/.
Play around with the Hub view to see improved input JSON schemas.

@mszostok Thanks!
Nope, I didn't use the generator, I edited the schema in place in IDE by using multi-selection and this plugin: https://plugins.jetbrains.com/plugin/7160-camelcase. The current Helm generator would fix the issues with boolean parameters, but I would still need to edit the titles manually, as it generates CamelCase titles. We can think about such future improvement for Helm Generator.


Make more understandable example codes

It seems rust-rs example code lacks.
(For example, example using PyStorage, integrating this lib with this transport layer)
Ideally, it could be very useful to write more example codes for constructing more understanding lib.

I believe it would be good if Github Wiki includes these kinds of examples.


Priority not working?

I've got a Chaplin app I'm working on, and I'm having issues using the priority on subscriptions.... Here's a little code:
// from my "LayoutView":
mediator.subscribe('log:toggle', this.sizeViews, { priority: 9 });

// from my "LogView":
mediator.subscribe('log:toggle', this.toggleMe, { priority: 1 });

I have a console.log() in both handlers, and no matter what, the one from my Layout view is called first... I tried it at priority 0, 2 and 9... I want the one from LeftSidebar to fire first...
What am I doing wrong?
I may end up just adding a publish to the LogView stating when it's done, and the subscribe to that in my LayoutView, but that feels like the easy way out. =)

I also believe that the priority property is useless this way. It would be better to not modify priority defined by user.


Can we update this to support AndroidX

hello and thank you for your feedback.
I have just migrated the library to androidx on a specific branch.
You can access it by updating your gradle file:
implement 'com.github.smart-fun:TabStacker:1.1.0'
This is a pre-release but it should work as expected.
Any feedback is welcome before I do an official release of the library (this is a big change for the users).
thanks!
Arnaud.


Recurrent go_backwards and output reversal

Caveat: I'm Working in Theano, don’t know if TF is different.
The output of a scan with go_backwards is in the order that the sequence is processed. So, the first time step in the output of a go_backwards scan corresponds to the output after processing the original last element of the input sequence.
If return_sequences=False, this is fine. output[-1] represents the result of processing the full sequence. But in the return_sequences=True context, this is going to hurt since outputs don’t have sequential correspondence with their inputs. Consider a bidirectional sequence labeling task. The point of bidirectionality here is to have access to the entire context at each time step. Any merge on the first element contains only the recurrent output of x0 and xn, but instead should contain x0 and xn,…,0.
Easy way to check this is:
forward = Sequential()
forward.add(Embedding(100,7))
forward.add(LSTM(12, return_sequences=True))

backward = Sequential()
backward.add(Embedding(100,7))
backward.add(LSTM(12, return_sequences=True, go_backwards=True))

then compile
forward.set_weights(backward.get_weights())

input = np.array([[1,2,3,4,5,6]])

np.all(forward.predict(input[:,::-1]) == backward.predict(input))

The result of that all is going to be true, which means the final output of backwards is in reverse order from the input to forward.
EDIT
Edit 2 @lemuriandezapada pointed out a clarity issue in my response.
FYI, I've addressed this locally just by overriding get_output with a final:
if self.go_backwards:
    return output[:, ::-1, :]
else:
    return output

and have seen some pretty significant sequence labeling gains.

#1282

@mbotumbo, any particular reason you closed this? I'm pretty convinced this is still a problem. Regardless of what eventually happens with #1282, I think Recurrent go_backwards=True return_sequences=True should flip the output anyway.

@pasky I am on the fence about this. Here's my current thinking.
First, although a little bit buried it did seem pretty well covered in #1282, so I didn't wan to add to clutter.
Second, I wasn't able to fully convince myself go_backwards is useful outside of bidirectional processing (e.g. if you want to process inputs backwards only, why not reverse the input?). However, one could argue if that is the case, maybe go_backwards shouldn't be exposed at it's current level as an argument.
Third, its not totally clear to me this behavior is definitely a problem. It was annoying for me, and I gather it was for you too, but it also makes sense, in a way, why it does what it does. Again, this might indicate a little additional documentation would be helpful or, again, if i'm right about the "second" thing, perhaps it shouldn't be exposed where it is.
Thoughts? Still think I should reopen?

Thanks for this. I dug for a solution for some days.
Although I would amend it to:
return outputs[:, ::-1,:]

Since most of the time your time sequences are 3d anyway. Though I don't know if this is actually the correct way to fix this. Will autodiferentiation find the way to propagate the error if we do it like this?
This IS an issue if you want to do anything with Bi-RNNs and return_sequences = True.
For example, in my case: I have a string of tokens, one embedding layer, that then go into two RNNs, one forward, one back with return_sequences = True. The output then gets merged.  Which is pointless. Getting this properly addressed is important.

@lemuriandezapada  Indeed that was a mistake, thanks for the catch. I'll fix it above so i don't confuse anyone.
I think Theano handles this OK, and, just by the fact that this seems to work far better (i.e. better results) than not doing it would suggest error is getting propagated correctly.
Regarding Bi-RNNs, yes. This is along the lines what I was saying above. Bi(directional)-RNNs is about the only case where I'm seeing a clear use for go_backwards=True, and it is what was being addressed in #1282.

Fun fact : #1282 do not use go_backwards argument.

@farizrahman4u Yeah, but input reversal is essentially equivalent to go_backwards=True, right?

Yes.

Thanks, it helps a lot. The go_backward flag is confusing. @fchollet  I think you should at least mention this problem in the API document.

I agree, @fchollet.  I think I didn't try to add the wrapper mainly
because I ended up being in a bit of a rush and didn't want to worry
about unit tests. ;-)  I'm now offline for 14 days but I promise to
come back to this PR at the end of August and add the Bidirectional()
wrapper, unless someone beats me to it.

So @farizrahman4u, @mostlymetalman, do I understand correctly,
according to the docs the input reversal is not equivalent to go_backwards=True, but rather go_backwards=True means that you both reverse the input and reverse the outputs (meaning that you reverse the timestamp for every output).
So is the current documentation right?
Docs say: "go_backwards: Boolean (default False). If True, process the input sequence backwards and return the reversed sequence."

@nadavb These comments were from a while ago... a lot has changed since then.
I just did some quick tests (TF Backend).
go_backwards is equivalent to reversing the input. No additional reverse operation is on the output, so the output time steps are in reverse temporal order.
I think the documentation is perhaps linguistically ambiguous. Maybe it could say "Processes the input sequence backward. The output sequence will, therefore, be in reverse temporal order. So, just to make sure we are on the same page. go_backwards works like this:
def process(regular_list, go_backwards=False, op=lambda x: x+2):
    """regular_list is a regular old python list, each element is a time step"""
    if go_backwards:
        return [op(x) for x in regular_list[::-1]]
    else:
        return [op(x) for x in regular_list]

It does not work like this (reversing the input then reversing the output so that everything is in the right order):
if go_backwards:
    return [op(x) for x in regular_list[::-1]][::-1]

But, since your problem is Bidirectional layers, have you looked at this? You can see there how the fact that output is in the wrong order is handled. When y_rev is a sequence, it is in the wrong order, to it is reversed:
y_rev = self.backward_layer.call(inputs, **kwargs)
if self.return_sequences:
    y_rev = K.reverse(y_rev, 1)

I'm not sure how you tested this to prove it to yourself, but I did:
i = Input((None,))
e = Embedding(5,2,mask_zero=True)(i)
f = LSTM(3, return_sequences=True)(e)
b = LSTM(3, return_sequences=True, go_backwards=True)(e)
fm = Model(i, f)
bm = Model(i, b)
i = np.eye(3)
print("Regular")
print(fm.predict(i))
print("Reverse")
print(bm.predict(i))

Okay, so we all agree that go_backwards simply changes the order of the input, and not the output.
Can you please change the documentation from:

"If True, process the input sequence backwards and return the reversed sequence."

to something like

"If True, process the input sequence backwards"

If someone wants to also reverse the output of an LSTM, like in bidirectional LSTM for example he should do:
reversedLSTM = Lambda(lambda inputTensor: K.reverse(inputTensor, axes=0)) (LSTM)


Configure basic ruff linter as precommit hook

Only checks for issues like https://github.com/QCoDeS/Qcodes/pull/4999 for now. That pr should be merged first and then rebased away from this pr

Folded into #5006


META6 "depends" section

Does the module support the "depends" section as in S22?
I'm testing with this META6 file and getting [(Str) (Str) (Str)] for the depends section.

I think the issue happens because forcing Str type on depends, build-depends, test-depends although they can accept Array or Hash per S22.
Removing the Str and replacing @ with $ here for them, fixes the issue. I'd submit a PR but I'm not sure if this is the right fix.

Hi,
yeah that's approximately right,  it definitely needs to support either Positional or Associative and I'm just having a think about how best to do that and make it useful.

I think the issue happens because forcing Str type on depends, build-depends, test-depends although they can accept Array or Hash per S22.
Removing the Str and replacing @ with $ here for them, fixes the issue. I'd submit a PR but I'm not sure if this is the right fix.

That's basically what I have done, with additional tests for this. Thanks for the suggestion.


Feedback for Sony page

It is called Stamina mode and it instantly breaks all background processes and all alarms if enabled.

I think that the Sony Stamina is updated in many ways, and with a balanced power saving stamina mode, I didn't notice any difference in the behavior of background process. The new stamina mode is different with the old stamina mode in some ways (ie limiting graphic and cpu performance etc). I didn't add any app to the exceptions at all till date. Whatsapp web worked fine without opening whatsapp on the phone, notifications arrive on time, basically for me at least there's nothing wrong.
Also for newer Sony there's a smart memory management feature under the Sony Assist in Settings. I have that enabled too.
Overall, everything is just fine for me. I could be wrong too :) Just trying to share my thoughts.

Isn't Stamina mode actually disabled by default these days?  I don't have a Sony device myself, but from what I've seen on other people's phone's, Stamina seems to be opt-in.  In which case I think the feature is fine.  As far as I can tell, users don't run into any Sony-specific app killing issues at all, at least if they stick to default settings.  Therefore, the negative rank seems somewhat misleading to me (the reasoning of Sony having "opened the Pandora’s box" doesn't really seem relevant to end users, in my book).

Hello, many thanks I think you are right.. Sony was the first who started to break apps in non-standard ways, but now we hardly hear about issues on support. So maybe it is right to give them just one thumb down.. But the one thumb they deserve IMHO as enabling Stamina still breaks alarms..so this is compliant with our scoring policy:
https://dontkillmyapp.com/about_score

Thanks for reconsidering!

But the one thumb they deserve IMHO as enabling Stamina still breaks alarms..so this is compliant with our scoring policy:

I see how this complies with the policy, though personally I don't quite agree with that policy :smiley:   I think it's just fine to temporarily break functionality for the purposes of battery savings if the user explicitly asks the OS to do so.  Whatever, I guess this discussion is off-topic here :smiley:

I would agree with that, if the OEM would do an excellent job on explaining users what is happening.. but honestly this is not even possible as users don't read disclaimers anyway..  when stamina was introduced we got hundreds of people complaining "why is my alarm broken?". They had absolutely no idea that stamina would be anyhow related to their alarm clock not working.
Nowadays it is not so common, but still.. there is a standard feature in AOSP called Background restrictions in App settings, so IMHO stamina mode is just another vendor-specific extension to the Android's battery management which will just confuse users and make thinks worse..

there is a standard feature in AOSP called Background restrictions in App settings, so IMHO stamina mode is just another vendor-specific extension to the Android's battery management which will just confuse users and make thinks worse.

Right, that makes sense to me.  Thanks.


Everything is prefixed by 'pdf'

From my personal observation of the code everything a lot of class names, component names, react props and object properties (in state) are prefixed with a pdf. I am wondering why?
Sometimes it seems to be unnecessary and looks strange, for example recommender section is just an instance of CORE Recommender and it should not be a PDFRecommender.
On other side are props like pdfEventBus with corresponding classes like PDFEventBus which I might no completely understand.

I tried to add prefix PDF to everything related to PDF. There is no big reason for it maybe I just wanted to keep consistency with PDF.js.
Basically the reader is divided into few sections/components prefixed with PDF. The names explain what they take care of.
The most important are:

PDFLoader - responsible for loading PDF document (not rendering)
PDFViewer - Takes the loaded document and renders pages - after it's rendered some events are fired.

Regarding the props names. Yeah, I do agree indeed and I will change it. :)
Regarding recommender - I think it's part of the reader and hence the prefix should stay. But it's questionable and I can rename it if you insist.
And the last but not least - pdfEventBus This is event bus used for firing and subscribing to events fired within PDF.js. Events like pagesRendered, pageNumberChange.
I believe it is much cleaner now. 🙂
The summary is that I am open to suggestion for project structure and maybe we could get rid of those prefixes indeed.

@viktor-yakubiv This issue is quite old. We should somehow solve it. Otherwise, it stays here forever.
I do agree pdf-recommender should be renamed to just recommender. Do you see anything else which should be renamed? I must confess that I have started to like the idea about renaming everything, i.e. get rid of pdf prefixes almost everywhere. WDYT?

I agree, you can get rid out of PDF* prefix as much as possible. It's up to you to decide what should be renamed. I suggest to renamed things that are not strongly tied to PDF.
I would rename the following (but keep original names for ~stroke out items~):

~pdf-downloader~
pdf-enhancement-sidebar
pdf-highlighter
pdf-loader (if it's a spinner only, if it does actual loading, keep the PDF)
pdf-outline-sidebar
~pdf-print~
pdf-recommender
pdf-thumbnails-sidebar
pdf-toolbar
pdf-viewer

Although, it still is up to you to decide because you know the product better. I would not call generic UI parts with pdf-something but everything else is fine.