Cannot open secondary roots when using multiple vaults

Describe the bug
When using multiple vaults only the top vault in the dendron pane will open its root. Other roots open the first vaults root.
To Reproduce
Steps to reproduce the behavior:

Create 2 vaults
Click on 1st vault root (see breadcrumb path is correct)
Close tab
Click on 2nd vault root (see breadcrumb path is NOT correct, it shows the 1st vault root)

Expected behavior
Open the root file for the selected vault.
Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: Fedora 33 (Workstation Edition)
Browser: VSCodium 1.53.2, Electron 11.2.1, Chrome 87.0.4280.141, Node.js 12.18.3, V8 <IP_ADDRESS>-electron.0, OS Linux x64 <IP_ADDRESS>.fc33.x86_64
Version: Dendron v0.29.0

Dendron Log file
Please attach the output of >Dev:Dendron: Open Logs here
(This shows as Dendron:Dev: Open Logs)
{"level":30,"time":1613810124934,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"Logger:configure","msg":"exit","log_level":"info"}
{"level":30,"time":1613810125010,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"_activate","stage":"dev","isDebug":false,"logPath":"/home/pwhitesi/.config/VSCodium/logs/20210220T083515/exthost1/dendron.dendron","logLevel":"info","extensionPath":"/home/pwhitesi/.vscode-oss/extensions/dendron.dendron-0.29.0","extensionUri":{"$mid":1,"fsPath":"/home/pwhitesi/.vscode-oss/extensions/dendron.dendron-0.29.0","path":"/home/pwhitesi/.vscode-oss/extensions/dendron.dendron-0.29.0","scheme":"file"},"storagePath":"/home/pwhitesi/.config/VSCodium/User/workspaceStorage/31064ccdb91541926dfa49d750726cfd/dendron.dendron","workspaceFile":{"$mid":1,"fsPath":"/home/pwhitesi/Documents/Notebook/dendron.code-workspace","external":"file:///home/pwhitesi/Documents/Notebook/dendron.code-workspace","path":"/home/pwhitesi/Documents/Notebook/dendron.code-workspace","scheme":"file"},"workspaceFolders":[{"uri":{"$mid":1,"fsPath":"/home/pwhitesi/Documents/Notebook/TestNewVault","external":"file:///home/pwhitesi/Documents/Notebook/TestNewVault","path":"/home/pwhitesi/Documents/Notebook/TestNewVault","scheme":"file"},"name":"TestNewVault","index":0},{"uri":{"$mid":1,"fsPath":"/home/pwhitesi/Documents/Notebook/Customer","external":"file:///home/pwhitesi/Documents/Notebook/Customer","path":"/home/pwhitesi/Documents/Notebook/Customer","scheme":"file"},"name":"Customer","index":1},{"uri":{"$mid":1,"fsPath":"/home/pwhitesi/Documents/Notebook/Notes","external":"file:///home/pwhitesi/Documents/Notebook/Notes","path":"/home/pwhitesi/Documents/Notebook/Notes","scheme":"file"},"name":"Notes","index":2}]}
{"level":30,"time":1613810125015,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"DendronWorkspace","msg":"initialized"}
{"level":30,"time":1613810125018,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"_activate","config":{"version":1,"vaults":[{"fsPath":"TestNewVault"},{"fsPath":"Customer"},{"fsPath":"Notes"}],"useFMTitle":true,"site":{"copyAssets":true,"siteHierarchies":["root"],"siteRootDir":"docs","usePrettyRefs":true,"title":"Dendron","duplicateNoteBehavior":{"action":"useVault","payload":["Personal","Notes","Customer","TestVaultForMultiRoot","TestNewVault"]}}},"configMigrated":false,"msg":"read dendron config"}
{"level":30,"time":1613810125194,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"_activate","wsConfig":{"folders":[{"path":"TestNewVault"},{"path":"Customer"},{"path":"Notes"}],"settings":{"dendron.rootDir":".","files.autoSave":"onFocusChange","pasteImage.path":"${currentFileDir}/assets/images","pasteImage.prefix":"/","markdown-preview-enhanced.enableWikiLinkSyntax":true,"markdown-preview-enhanced.wikiLinkFileExtension":".md","editor.snippetSuggestions":"inline","editor.suggest.snippetsPreventQuickSuggestions":false,"editor.suggest.showSnippets":true,"editor.tabCompletion":"on"},"extensions":{"recommendations":["dendron.dendron-paste-image","equinusocio.vsc-material-theme","dendron.dendron-markdown-shortcuts","dendron.dendron-markdown-preview-enhanced","dendron.dendron-markdown-links","github.github-vscode-theme"],"unwantedRecommendations":["dendron.dendron-markdown-notes","shd101wyy.markdown-preview-enhanced","kortina.vscode-markdown-notes","mushan.vscode-paste-image"]}},"wsConfigMigrated":{},"msg":"read wsConfig"}
{"level":30,"time":1613810125333,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"_activate","installedGlobalVersion":"0.29.0","migratedGlobalVersion":"0.29.0","previousGlobalVersion":"0.0.0","previousWsVersion":"0.29.0","platform":"linux","extensions":[{"id":"dendron.dendron-paste-image","version":"1.0.4","active":false},{"id":"equinusocio.vsc-material-theme","version":"33.1.2","active":false},{"id":"dendron.dendron-markdown-shortcuts","version":"0.12.1","active":true},{"id":"dendron.dendron-markdown-preview-enhanced","version":"0.10.23","active":false},{"id":"dendron.dendron-markdown-links","version":"0.6.19","active":false},{"id":"github.github-vscode-theme","version":"1.1.5","active":false}],"vaults":[{"fsPath":"TestNewVault"},{"fsPath":"Customer"},{"fsPath":"Notes"}]}
{"level":30,"time":1613810125336,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"startServer","logLevel":"info"}
{"level":30,"time":1613810125349,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"_activate","msg":"post-start-server","port":44903}
{"level":30,"time":1613810125354,"pid":139812,"hostname":"x1carbon","name":"logger","ctx":"FileStorageV2","wsRoot":"/home/pwhitesi/Documents/Notebook","vaultsv3":[{"fsPath":"TestNewVault"},{"fsPath":"Customer"},{"fsPath":"Notes"}],"level":"info"}
{"level":30,"time":1613810125355,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"ReloadIndex.execute","msg":"enter"}
{"level":30,"time":1613810128281,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"ReloadIndex.execute","msg":"exit"}
{"level":30,"time":1613810128281,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"reloadWorkspace","msg":"post-ws.reloadWorkspace"}
{"level":30,"time":1613810128283,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"reloadWorkspace","msg":"exit"}
{"level":30,"time":1613810128283,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"postReloadWorkspace","msg":"no previous global version"}
{"level":30,"time":1613810128283,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"postReloadWorkspace","msg":"exit"}
{"level":30,"time":1613810128284,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"TreeView:getChildren","msg":"reconstructing tree"}
{"level":30,"time":1613810128333,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"setupViews","msg":"init:backlinks"}
{"level":30,"time":1613810128335,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"activateWorkspace","stage":"dev","msg":"enter"}
{"level":30,"time":1613810128340,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"h:run","msg":"pre-execute"}
{"level":30,"time":1613810128340,"pid":139812,"hostname":"x1carbon","name":"UpgradeSettingsCommand","ctx":"Upgrade:execute"}
{"level":30,"time":1613810128345,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"toggleViews","msg":"views enabled: true"}
{"level":30,"time":1613810128345,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"_activate","msg":"fin startClient"}
{"level":30,"time":1613810128345,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"showWelcomeOrWhatsNew","version":"0.29.0","previousVersion":"0.29.0"}
{"level":30,"time":1613810128345,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"showWelcomeOrWhatsNew","msg":"not first time install"}
{"level":30,"time":1613810129171,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"TreeView:getChildren","msg":"reconstructing tree"}
{"level":30,"time":1613810129243,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"WorkspaceConfig:update","vscodeDir":"/home/pwhitesi/Documents/Notebook/TestNewVault/.vscode","snippetChanges":{}}
{"level":30,"time":1613810129243,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"Upgrade:execute","newConfig":{"extensions":{},"settings":{"add":{},"errors":{}},"snippetChanges":{}}}
{"level":30,"time":1613810129243,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"Upgrade:execute","badExtensions":[]}
{"level":30,"time":1613810129244,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"h:run","msg":"post-execute"}
{"level":30,"time":1613810129244,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"postReloadWorkspace","msg":"postUpgrade: new wsVersion"}
{"level":30,"time":1613810133375,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"d:run","msg":"pre-execute"}
{"level":30,"time":1613810133376,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"GotoNoteCommand","opts":{"qs":"root","mode":"note","vault":{"fsPath":"Customer"}},"msg":"enter"}
{"level":30,"time":1613810134326,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"WindowWatcher:onDidChangeActiveTextEditor","msg":"enter","uri":{"$mid":1,"fsPath":"/home/pwhitesi/Documents/Notebook/TestNewVault/root.md","external":"file:///home/pwhitesi/Documents/Notebook/TestNewVault/root.md","path":"/home/pwhitesi/Documents/Notebook/TestNewVault/root.md","scheme":"file"}}
{"level":30,"time":1613810141373,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"GotoNoteCommand","opts":{"qs":"root","mode":"note","vault":{"fsPath":"Customer"}},"msg":"exit"}
{"level":30,"time":1613810141391,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"d:run","msg":"post-execute"}
{"level":30,"time":1613810141849,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"d:run","msg":"pre-execute"}
{"level":30,"time":1613810141849,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"GotoNoteCommand","opts":{"qs":"root","mode":"note","vault":{"fsPath":"Notes"}},"msg":"enter"}
{"level":30,"time":1613810141850,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"d:run","msg":"pre-execute"}
{"level":30,"time":1613810141850,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"GotoNoteCommand","opts":{"qs":"root","mode":"note","vault":{"fsPath":"TestNewVault"}},"msg":"enter"}
{"level":30,"time":1613810142202,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"GotoNoteCommand","opts":{"qs":"root","mode":"note","vault":{"fsPath":"Notes"}},"msg":"exit"}
{"level":30,"time":1613810142202,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"GotoNoteCommand","opts":{"qs":"root","mode":"note","vault":{"fsPath":"TestNewVault"}},"msg":"exit"}
{"level":30,"time":1613810142202,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"d:run","msg":"post-execute"}
{"level":30,"time":1613810142203,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"d:run","msg":"post-execute"}
{"level":30,"time":1613810143720,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"d:run","msg":"pre-execute"}
{"level":30,"time":1613810143720,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"GotoNoteCommand","opts":{"qs":"root","mode":"note","vault":{"fsPath":"Notes"}},"msg":"enter"}
{"level":30,"time":1613810143765,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"GotoNoteCommand","opts":{"qs":"root","mode":"note","vault":{"fsPath":"Notes"}},"msg":"exit"}
{"level":30,"time":1613810143765,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"d:run","msg":"post-execute"}
{"level":30,"time":1613810144594,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"d:run","msg":"pre-execute"}
{"level":30,"time":1613810144594,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"GotoNoteCommand","opts":{"qs":"root","mode":"note","vault":{"fsPath":"Customer"}},"msg":"enter"}
{"level":30,"time":1613810144644,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"GotoNoteCommand","opts":{"qs":"root","mode":"note","vault":{"fsPath":"Customer"}},"msg":"exit"}
{"level":30,"time":1613810144648,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"d:run","msg":"post-execute"}
{"level":30,"time":1613810145464,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"d:run","msg":"pre-execute"}
{"level":30,"time":1613810145464,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"GotoNoteCommand","opts":{"qs":"root","mode":"note","vault":{"fsPath":"TestNewVault"}},"msg":"enter"}
{"level":30,"time":1613810145519,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"GotoNoteCommand","opts":{"qs":"root","mode":"note","vault":{"fsPath":"TestNewVault"}},"msg":"exit"}
{"level":30,"time":1613810145519,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"d:run","msg":"post-execute"}
{"level":30,"time":1613810149053,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"c:run","msg":"pre-execute"}
{"level":30,"time":1613810149053,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"execute","opts":{}}
{"level":30,"time":1613810149094,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"c:run","msg":"post-execute"}
{"level":30,"time":1613810149354,"pid":139812,"hostname":"x1carbon","name":"dendron","ctx":"WindowWatcher:onDidChangeActiveTextEditor","msg":"enter","uri":{"$mid":1,"fsPath":"/home/pwhitesi/.config/VSCodium/logs/20210220T083515/exthost1/dendron.dendron/dendron.log","external":"file:///home/pwhitesi/.config/VSCodium/logs/20210220T083515/exthost1/dendron.dendron/dendron.log","path":"/home/pwhitesi/.config/VSCodium/logs/20210220T083515/exthost1/dendron.dendron/dendron.log","scheme":"file"}}

Good catch!
This should be a one line fix. Going to leave this up as a good first issue and fix this after a week if no one claims it.
By the way, if you are on our discord, feel free to ping me your handle since this earns you the bug catcher role 😇

Hey :-) No I'm not, but I will join and let you know :+1: I'm new to Dendron so building up my usage


python311Packages.pytest-testinfra: 9.0.0 -> 10.0.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.pytest-testinfra is: Pytest plugin for testing your infrastructure
meta.homepage for python311Packages.pytest-testinfra is: https://github.com/pytest-dev/pytest-testinfra
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 10.0.0 with grep in /nix/store/1gsxqhhb9h779q8xxyys3719s8d0a254-python3.11-pytest-testinfra-10.0.0
found 10.0.0 in filename of file in /nix/store/1gsxqhhb9h779q8xxyys3719s8d0a254-python3.11-pytest-testinfra-10.0.0

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
python310Packages.pytest-testinfra
python311Packages.pytest-testinfra

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/1gsxqhhb9h779q8xxyys3719s8d0a254-python3.11-pytest-testinfra-10.0.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.pytest-testinfra https://github.com/r-ryantm/nixpkgs/archive/19387d78af795708d63e63c6a4673ca1eb8cca1d.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/19387d78af795708d63e63c6a4673ca1eb8cca1d#python311Packages.pytest-testinfra

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/1gsxqhhb9h779q8xxyys3719s8d0a254-python3.11-pytest-testinfra-10.0.0
ls -la /nix/store/1gsxqhhb9h779q8xxyys3719s8d0a254-python3.11-pytest-testinfra-10.0.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package failed to build:

python310Packages.pytest-testinfra

1 package built:

python311Packages.pytest-testinfra

Maintainer pings
cc @hulr for testing.

error: builder for '/nix/store/cki427ndqca730qxnr8dj2h4sgx0v9h6-python3.10-pytest-testinfra-10.0.0.drv' failed with exit code 1;
       last 10 log lines:
       >         import salt.client
       >     except ImportError:
       > >       raise RuntimeError("You must install salt package to use the salt backend")
       > E       RuntimeError: You must install salt package to use the salt backend
       >
       > testinfra/backend/salt.py:16: RuntimeError
       > =========================== short test summary info ============================
       > FAILED test/test_backends.py::test_backend_importables - RuntimeError: You must install salt package to use the salt backend
       > ========================= 1 failed, 69 passed in 8.09s =========================
       > /nix/store/bbxdw4rgwwl3gnajri82yidr1nlsfskf-stdenv-linux/setup: line 1596: pop_var_context: head of shell_variables not a function context

Because python3 is now python311, the salt package is now only built for Python 3.11.
Created PR https://github.com/NixOS/nixpkgs/pull/269496 to fix build on Python 3.10.

https://github.com/NixOS/nixpkgs/pull/269496 merged, closing this PR.


jellyfin-web: 10.7.6 -> 10.7.7

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for jellyfin-web is: "Web Client for Jellyfin"
meta.homepage for jellyfin-web is: "https://jellyfin.org/"
meta.changelog for jellyfin-web is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 10.7.7 in filename of file in /nix/store/0527x3hxpl0dq9g9f6xhnzn2ih479b35-jellyfin-web-10.7.7

directory tree listing: https://gist.github.com/cfe0ae944525462807dc185c9bfba8f5

du listing: https://gist.github.com/9a4b729cadbcc12cda05733caa4ac3b6

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

2 total rebuild path(s)

2 package rebuild(s)

2 x86_64-linux rebuild(s)
0 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
0 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
jellyfin
jellyfin-web

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/0527x3hxpl0dq9g9f6xhnzn2ih479b35-jellyfin-web-10.7.7 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A jellyfin-web https://github.com/r-ryantm/nixpkgs/archive/567d7a24b5a25fbe553032d7af386df554e40878.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/0527x3hxpl0dq9g9f6xhnzn2ih479b35-jellyfin-web-10.7.7
ls -la /nix/store/0527x3hxpl0dq9g9f6xhnzn2ih479b35-jellyfin-web-10.7.7/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

jellyfin
jellyfin-web

Maintainer pings
cc @nyanloutre @minijackson @purcell @jojosch for testing.

duplicate of #136857


add additional KEYCLOAK_USER and PASSWORD secrets

This PR renames the default USER and PASSWORD for the keycloak service to match the env vars set in the dockerfile (https://github.com/uselagoon/lagoon/blob/testing/keycloak/services/keycloak/Dockerfile#L61-L62 for https://github.com/keycloak/keycloak-containers/blob/16.1.1/server/tools/docker-entrypoint.sh#L40)
I've kept our KEYCLOAK_ADMIN_PASSWORD secret in there too, just in case.
I've also added the ability to define an admin username (other than admin) - but it will require a Lagoon PR to activate

I think this change couples the chart too tightly to the upstream Keycloak entrypoint scripts.
In Lagoon we have the concept of separate KEYCLOAK_ADMIN_USER and KEYCLOAK_LAGOON_ADMIN_USERNAME and it is used widely by services other than Keycloak (e.g. api). Changing this would be confusing. In addition this duplicates the same data into multiple keys in the secret.
Instead I think we could solve this in Lagoon by changing the entrypoint to be something like this?
KEYCLOAK_USER=$KEYCLOAK_ADMIN_USER KEYCLOAK_PASSWORD=$KEYCLOAK_ADMIN_PASSWORD /opt/jboss/tools/docker-entrypoint.sh "$@"

hmm - yeah, keycloak is pretty fluid with their variable names unfortunately. I'll give it a go hacking in the entrypoint and preserving the existing variables lagoon-side (but adding in the ability to define an admin username)


python38Packages.nototools: 0.2.13 -> 0.2.16

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python38Packages.nototools is: "Noto fonts support tools and scripts plus web site generation"
meta.homepage for python38Packages.nototools is: "https://github.com/googlefonts/nototools"
meta.changelog for python38Packages.nototools is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

Warning: no invocation of /nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16/bin/add_vs_cmap.py had a zero exit code or showed the expected version

Warning: no invocation of /nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16/bin/autofix_for_release.py had a zero exit code or showed the expected version

/nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16/bin/create_image.py passed the binary check.

/nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16/bin/decompose_ttc.py passed the binary check.

/nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16/bin/drop_hints.py passed the binary check.

/nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16/bin/dump_otl.py passed the binary check.

Warning: no invocation of /nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16/bin/fix_khmer_and_lao_coverage.py had a zero exit code or showed the expected version

/nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16/bin/fix_noto_cjk_thin.py passed the binary check.

/nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16/bin/generate_sample_text.py passed the binary check.

/nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16/bin/generate_website_2_data.py passed the binary check.

/nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16/bin/merge_fonts.py passed the binary check.

/nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16/bin/merge_noto.py passed the binary check.

Warning: no invocation of /nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16/bin/noto_lint.py had a zero exit code or showed the expected version

/nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16/bin/scale.py passed the binary check.

/nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16/bin/subset.py passed the binary check.

/nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16/bin/subset_symbols.py passed the binary check.

/nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16/bin/test_vertical_extents.py passed the binary check.

/nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16/bin/notocoverage passed the binary check.

/nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16/bin/notodiff passed the binary check.

Warning: no invocation of /nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16/bin/.add_vs_cmap.py-wrapped had a zero exit code or showed the expected version

Warning: no invocation of /nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16/bin/.autofix_for_release.py-wrapped had a zero exit code or showed the expected version

/nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16/bin/.create_image.py-wrapped passed the binary check.

/nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16/bin/.decompose_ttc.py-wrapped passed the binary check.

/nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16/bin/.drop_hints.py-wrapped passed the binary check.

/nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16/bin/.dump_otl.py-wrapped passed the binary check.

Warning: no invocation of /nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16/bin/.fix_khmer_and_lao_coverage.py-wrapped had a zero exit code or showed the expected version

/nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16/bin/.fix_noto_cjk_thin.py-wrapped passed the binary check.

/nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16/bin/.generate_sample_text.py-wrapped passed the binary check.

/nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16/bin/.generate_website_2_data.py-wrapped passed the binary check.

/nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16/bin/.merge_fonts.py-wrapped passed the binary check.

/nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16/bin/.merge_noto.py-wrapped passed the binary check.

Warning: no invocation of /nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16/bin/.noto_lint.py-wrapped had a zero exit code or showed the expected version

/nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16/bin/.scale.py-wrapped passed the binary check.

/nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16/bin/.subset.py-wrapped passed the binary check.

/nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16/bin/.subset_symbols.py-wrapped passed the binary check.

/nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16/bin/.test_vertical_extents.py-wrapped passed the binary check.

/nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16/bin/.notocoverage-wrapped passed the binary check.

/nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16/bin/.notodiff-wrapped passed the binary check.

14 of 38 passed binary check by having a zero exit code.

28 of 38 passed binary check by having the new version present in output.

found 0.2.16 with grep in /nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16

found 0.2.16 in filename of file in /nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16

directory tree listing: https://gist.github.com/8002a4f1844a4885348a3d1900d48d62

du listing: https://gist.github.com/bffc32aa2c8316e5a88ff7294f7c9e6f

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

13 total rebuild path(s)

4 package rebuild(s)

4 x86_64-linux rebuild(s)
3 i686-linux rebuild(s)
3 x86_64-darwin rebuild(s)
3 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
noto-fonts-emoji
python38Packages.nototools
python39Packages.nototools
twitter-color-emoji

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python38Packages.nototools https://github.com/r-ryantm/nixpkgs/archive/a6f6daa8b4b5f5047c976f51a2e5005303ab6160.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16
ls -la /nix/store/9mscja2vnkba0whvl86blhiwmfbsvk2b-python3.8-nototools-0.2.16/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package failed to build:

noto-fonts-emoji

3 packages built:

python38Packages.nototools
python39Packages.nototools
twitter-color-emoji

Maintainer pings

Result of nixpkgs-review pr 137650 at a6f6daa8 run on aarch64-linux 1

1 package skipped due to time constraints:

noto-fonts-emoji

2 packages built successfully:

python38Packages.nototools
python39Packages.nototools

1 suggestion:

warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/data/fonts/noto-fonts/tools.nix:73:3:
   |
73 |   meta = {
   |   ^


VFS-781 - webdav4,http4/5 client issues

This PR will fix following issues,

WEBDAV4 GenericURLFileName hardcoded scheme("http") won't work for https connection
Http4/Http5 proxy authentication details are not set correctly default user auth set to proxy auth which is wrong
SSL connection setting keystore type setting should be supported in config builders
If http host and proxy host are same with different ports that leads to conflict due to auth scope any
allow user to set proxy host scheme http vs https

Several issues require several PRs.

@michael-o Thanks! do you want me to create separate PR for each fix?

Issues + PR.

@michael-o Thanks! closing this! will raise separate Issue/PR for each issue


Change field properties created with createSiteColumn verb

As mentioned in the documentation, one could create Note field using createSiteColumn verb. How does one change it's type from Plain Text to Rich Text or Enhanced Rich Text? Is it possible with the createSiteColumn verb at all?
Similarly for DateTime field. How to change its type from DateOnly to DateAndTime?

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 68267476-ee8d-7b95-446b-711ddb683da2
Version Independent ID: aa099b9d-48db-5513-11c7-32c49a27e5be
Content: Site template JSON schema
Content Source: docs/declarative-customization/site-design-json-schema.md
Service: sharepoint-online
GitHub Login: @VesaJuvonen
Microsoft Alias: vesaj

Hi @vishalshitole, I'm not sure if this information would be useful, but for more complex scenarios, you can utilize createSiteColumnXml option.
the DateTime example, and take note of the setting Format='DateTime':
       {
          "verb": "addSPFieldXml",
          "schemaXml": "<Field DisplayName=\"DateTime\" FriendlyDisplayFormat=\"Relative\" Format=\"DateTime\" IsModern=\"TRUE\" Name=\"DateTime\" Title=\"DateTime\" Type=\"DateTime\" ID=\"{5fad18d8-0333-4776-a11b-bc0e670e32f2}\" StaticName=\"DateTime\"><Default>[today]</Default></Field>"
        }

the Note example, and take note of the settings RichText='True' and RichTextMode="FullHtml" :
       {
          "verb": "addSPFieldXml",
          "schemaXml": "<Field AppendOnly=\"FALSE\" DisplayName=\"MultiLine\" Format=\"Dropdown\" IsModern=\"TRUE\" IsolateStyles=\"TRUE\" Name=\"MultiLine\" RichText=\"TRUE\" RichTextMode=\"FullHtml\" Title=\"MultiLine\" Type=\"Note\" ID=\"{c52341cb-be85-4779-80cd-742319acebe4}\" StaticName=\"MultiLine\" />"
        }

Hi @mkm17 Thanks for your response.
I was able to utilize the createSiteColumnXml verb for my use case. However, I wanted to know if those kind of updates are possible with createSiteColumn verb, and whether I am missing anything in the documentation.

Hi @vishalshitole, Maybe someone can confirm, but as I can see, the documentation states to use createSiteColumnXml for more complex cases:

There are no other properties listed for createSiteColumn besides: fieldType, internalName:, displayName, isRequired, id,
group, enforceUnique,


[Feat] text align style

Fixed a bug where size could get stuck at 0 due to not accepting decimal values while interpreting font families.
Added text alignment styles

https://github.com/ZhgChgLi/ZMarkupParser/pull/27#issuecomment-1672658065

I apologize for being busy lately. I will review it before the end of August. Thank you for your contribution.


'kpt pkg sync' doesn't have a docs page

https://googlecontainertools.github.io/kpt/reference/

We are not planning to add one. We will be deprecating the command soon.


[Bugfix] Adds outlines performance improvement

This addresses concurrency performance issues when using Outlines leading to high CPU usage and a reduction in batching throughput. Timings showed ~1600% performance increase but I would very much appreciate validation of this method!
Overall approach:

Moved the mask to be created once for each request rather than per iteration to reduce memory allocations.
Use a simple caching object to reduce overall computational and data transformation costs.
Convert to a numpy array as this showed a 200% decrease in cost for Python List to Tensor conversion.
Offload int32 to int64 conversion to the GPU to maximize throughput.
Use non_blocking during tensor move operations to reduce CPU contention.

Line #      Hits         Time  Per Hit   % Time  Line Contents
==============================================================
    46                                               @line_profiler.profile
    47                                               def __call__(self, input_ids: List[int],
    48                                                            scores: torch.Tensor) -> torch.Tensor:
    49                                                   """Use the FSM to bias the logits before sampling the next token."""
    50     38607     210730.1      5.5      5.6          seq_id = hash(tuple(input_ids))
    51
    52     38607      17504.0      0.5      0.5          if len(input_ids) == 0:
    53        48        430.8      9.0      0.0              self.init_state()
    54                                                   else:
    55     38559       9725.8      0.3      0.3              last_token = input_ids[-1]
    56     38559     148043.9      3.8      3.9              last_seq_id = hash(tuple(input_ids[:-1]))
    57     77118     102817.6      1.3      2.7              self.fsm_state[seq_id] = self.fsm.next_state(
    58     38559      25271.5      0.7      0.7                  self.fsm_state[last_seq_id], last_token)
    59
    60     38607      11364.8      0.3      0.3          state = self.fsm_state[seq_id]
    61
    62                                                   # Retrieve allowed tokens from cache using the current state
    63     38607      11408.9      0.3      0.3          if state not in self.allowed_tokens_cache:
    64                                                       # Cache miss, calculate allowed tokens and cache them
    65       576     175710.0    305.1      4.7              allowed_tokens = self.fsm.allowed_token_ids(state)
    66       576     793771.6   1378.1     21.1              np_allowed_tokens = np.array(allowed_tokens, dtype=np.int32)
    67       576       2933.5      5.1      0.1              allowed_tokens_tensor = torch.from_numpy(np_allowed_tokens)
    68
    69       576        812.7      1.4      0.0              if (allowed_tokens_tensor.device != scores.device):
    70<PHONE_NUMBER>.6   2491.2     38.1                  allowed_tokens_tensor = allowed_tokens_tensor.to(scores.device, dtype=torch.int64, non_blocking=True)
    71                                                       else:
    72                                                           allowed_tokens_tensor = allowed_tokens_tensor.to(torch.int64)
    73
    74       576        600.9      1.0      0.0              self.allowed_tokens_cache[state] = allowed_tokens_tensor
    75
    76                                                   else:
    77     38031      11473.7      0.3      0.3              allowed_tokens_tensor = self.allowed_tokens_cache[self.fsm_state[seq_id]]
    78
    79     38607      10663.8      0.3      0.3          if self.mask is None:
    80        48        928.5     19.3      0.0              self.mask = torch.full_like(scores, -math.inf)
    81                                                   else:
    82     38559     291444.4      7.6      7.7              self.mask.fill_(-math.inf)
    83
    84     38607     285348.3      7.4      7.6          self.mask.index_fill_(0, allowed_tokens_tensor, 0)
    85     38607     209957.4      5.4      5.6          scores.add_(self.mask)
    86
    87     38607       7854.3      0.2      0.2          return scores

Fixes #3567

 PR Checklist (Click to Expand)
Thank you for your contribution to vLLM! Before submitting the pull request, please ensure the PR meets the following criteria. This helps vLLM maintain the code quality and improve the efficiency of the review process.
PR Title and Classification
Only specific types of PRs will be reviewed. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:

[Bugfix] for bug fixes.
[CI/Build] for build or continuous integration improvements.
[Doc] for documentation fixes and improvements.
[Model] for adding a new model or improving an existing model. Model name should appear in the title.
[Frontend] For changes on the vLLM frontend (e.g., OpenAI API server, LLM class, etc.)
[Kernel] for changes affecting CUDA kernels or other compute kernels.
[Core] for changes in the core vLLM logic (e.g., LLMEngine, AsyncLLMEngine, Scheduler, etc.)
[Hardware][Vendor] for hardware-specific changes. Vendor name should appear in the prefix (e.g., [Hardware][AMD]).
[Misc] for PRs that do not fit the above categories. Please use this sparingly.

Note: If the PR spans more than one category, please include all relevant prefixes.
Code Quality
The PR need to meet the following code quality standards:

We adhere to Google Python style guide and Google C++ style guide.
Pass all linter checks. Please use format.sh to format your code.
The code need to be well-documented to ensure future contributors can easily understand the code.
Include sufficient tests to ensure the project to stay correct and robust. This includes both unit tests and integration tests.
Please add documentation to docs/source/ if the PR modifies the user-facing behaviors of vLLM. It helps vLLM user understand and utilize the new features or changes.

Notes for Large Changes
Please keep the changes as concise as possible. For major architectural changes (>500 LOC excluding kernel/data/config/test), we would expect a GitHub issue (RFC) discussing the technical design and justification. Otherwise, we will tag it with rfc-required and might not go through the PR.
What to Expect for the Reviews
The goal of the vLLM team is to be a transparent reviewing machine. We would like to make the review process transparent and efficient and make sure no contributor feel confused or frustrated. However, the vLLM team is small, so we need to prioritize some PRs over others. Here is what you can expect from the review process:

 After the PR is submitted, the PR will be assigned to a reviewer. Every reviewer will pick up the PRs based on their expertise and availability.
 After the PR is assigned, the reviewer will provide status update every 2-3 days. If the PR is not reviewed within 7 days, please feel free to ping the reviewer or the vLLM team.
 After the review, the reviewer will put an  action-required label on the PR if there are changes required. The contributor should address the comments and ping the reviewer to re-review the PR.
 Please respond to all comments within a reasonable time frame. If a comment isn't clear or you disagree with a suggestion, feel free to ask for clarification or discuss the suggestion.

Thank You
 Finally, thank you for taking the time to read these guidelines and for your interest in contributing to vLLM. Your contributions make vLLM a great tool for everyone!

@lynkz-matt-psaltis I would suggest using PyTorch profiler (using with_stack=True option) for profiling, CPU-only profiling will not take into account GPU operations and may lead to misleading results as CPU operations block waiting on GPU.

@lynkz-matt-psaltis I would suggest using PyTorch profiler (using with_stack=True option) for profiling, CPU-only profiling will not take into account GPU operations and may lead to misleading results as CPU operations block waiting on GPU.

Epic thanks! I've never done any torch work before so that feedback is golden.

You can use the benchmark_latency.py script we have, just need to modify it to run the LLM/request with outlines enabled and add with_stack=True to the pytorch profiler context (suggest using a very small number of iterations and output tokens when profiling to reduce profile size). You can then run the script with --profile --profile-result-dir DIRECTORY arguments and view the generated json file in ui.perfetto.dev

You can use the benchmark_latency.py script we have, just need to modify it to run the LLM/request with outlines enabled and add with_stack=True to the pytorch profiler context (suggest using a very small number of iterations and output tokens when profiling to reduce profile size). You can then run the script with --profile --profile-result-dir DIRECTORY arguments and view the generated json file in ui.perfetto.dev
Also https://pytorch.org/docs/stable/notes/cuda.html#asynchronous-execution is a great read :)

Amazing! Thanks @Yard1. Can I just say you've all been such a welcoming community love it and huge shout out to everyone contributing!!!

Using state directly for the cache key wasn't sufficient - Some tests were failing for some FSMs. I swapped to a tuple on the returned array which is stable but reduces performance to around 400% increase instead of 1600% due to the hashing computational costs. I noticed that Outlines has moved to a Guide structure and the transition has been implemented here: https://github.com/vllm-project/vllm/pull/4109. I'm thinking I'd be better off putting something on top of this PR so its all aligned for an outlines update? Thoughts?

Since the update has been done (thx! @br3no) is there update to this PR and I would assume it still applies?

@lynkz-matt-psaltis I guess https://github.com/vllm-project/vllm/pull/5053 is the replacement?

@lynkz-matt-psaltis I guess #5053 is the replacement?

Kind of - I've been exploring going further with this branch against latest outlines by optimising further. Some of these required outlines changes so I'm worried about the sequencing & coordination aspects of those changes going in. Given the direction of this conversation and the potential for further api signature changes, that may not be as big an issue now.
I can look at either:

Strip this back to just vllm only optimisations
Finish the current approach which would require outlines changes as well.

Any advice?


remove test_hdf5.h5 after test

Description
Remove test_hdf5.h5 after performing the test.
Fixes #303
Checklist:

[x] I have performed a self-review of my own code
[x] My code is PEP8 compliant (flake8 anesthetic tests)
[x] My code contains compliant docstrings (pydocstyle --convention=numpy anesthetic)
[x] New and existing unit tests pass locally with my changes (python -m pytest)
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have appropriately incremented the semantic version number in both README.rst and anesthetic/_version.py

I've made the file names different for each root option, to avoid issues with the tests being run in parallel and accessing the file simultaneously

Thanks @lukashergt, deffo need to get more on top of the pytest features!


fix travis

Gemlock.* regenerated by running ruby test/run_all.rb locally..

Thank you @ignatiusreza :) I have now added this commit to master.


Increase indexheader_lazy_load_duration_seconds buckets

[ ] I added CHANGELOG entry for this change.
[x] Change is not relevant to the end user.

Changes
In Cortex we've noticed that the 99th percentile computed onindexheader_lazy_load_duration_seconds is always capped to 5s even if the average can be way higher. Reason is that the largest histogram bucket is 5s but lazy loading can take way longer than that (mostly depending on index size and the disk speed).
In this PR I proposes to add more buckets to the metric, to have a better estimation of 99th percentile on high durations.

Change is not relevant to the end user.

Is it? Do you track such changes in CHANGELOG?
Verification
N/A

Thanks @pracucci. I think 300s is little bit too large but overall LGTM.

We've actually seen several minutes too, on a store-gateway under heavy load with indexes each of few tens GB each.

If there are no concerns, can we get this merged, please?

thanks @pracucci :taco:

Thanks to you @squat ! 🌮


Installation instructions

I am new to Caddy and would like to use this add on. Caddy's own docs don't seem to specify how to install add-ons.
Is there a generic way to do this? If not, how can install this add-on?

The caddy download page has the ability to build a caddy binary that has the git plugin built in for any platform: https://caddyserver.com/download. Otherwise you could build it yourself using github.com/caddyserver/caddyext, but the download is really easiest.

I believe @captncraig's answer is sufficient.


cmake default install prefix is wrong

Issue description
According to cmake documentation, the default installation prefix on UNIX should be /usr/local, but cmake from nixpkgs uses /var/empty/local/.

We should use sane defaults.

I'm not sure we should encourage installing in other ways than through nix.  It seems e.g. likely that the projects will pick up dependencies on some /nix/store paths and those can be later garbage-collected.

I don't think we're "encouraging" anything by fixing that path. I use this for testing the installation procedure of a project while working in qtcreator. I don't plan to use this for "permanent" installs.
I don't think we should make tools more difficult to use as a way to "help" users. If we want maximum "help" we might as well inject startup code in all dev tools that abort execution unless there is an indication in the environment that it is being run under nix-build or nix-shell...

I'd expect users to choose something under $HOME instead of a global path, but that's just my personal opinion...

Right, that's what I did too (so I didn't have to use 'sudo').
But that isn't a reason for deviating from upstream default value and "breaking" their documentation.

yes, this might be confusing, if somebody uses cmake to build a package for a non-nixos system on nixos for instance.

Or just using cmake from nixpkgs on non-NixOS.

This issue is a bit confusing. I was trying to install my own project on macOS with the cmake installation from nix and it took me some time to find this thread. Does nix use a special build of cmake which has the changed default path?
The makefile generated by cmake offers the possibility to set the destination directory like this:
 make DESTDIR=myDestDir install

Using this doesn't really work since the /var/empty is appended after the cmake install prefix, i.e it results in myDestDir/var/empty/local/lib. Copying the files manually to /local/lib/ works as a workaround.

I'm guessing the /var/empty thing comes from a combination of this and this.

Still important to me.

should not be solved.

I think usually you want to avoid mixing cmake files from legacy package managers with nix on non-nixos systems. Which is why I think this replacement was put into place. For the same reason programs are not reading /etc/ld.so.conf because they might pick up stuff that they were not meant to read.

Related. It might help to alert the user since this behavior was unexpected while trying to debug an issue elsewhere http://sundials.2283335.n4.nabble.com/Memory-error-while-running-cvode-petsc-examples-tt4655872.html

Just hit this. I think it has to do with what is discussed in #118781

I noticed that my source of breakage here was that my cmake file was checking if the CMAKE_INSTALL_PREFIX was set to the default before overriding it. However, since nix sets its own CMAKE_INSTALL_PREFIX, this branch never got triggered. I ended up just removing the if, but I wonder if there's a better way to deal with this.
if(CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT)
  set(CMAKE_INSTALL_PREFIX "${BUILD_BUNDLE_DIR}" CACHE PATH "..." FORCE)
endif()

Thanks @smasher164!
Just hit this issue while creating a new Flutter project and this if condition is present in the default linux build configuration.
Removing it fixed my issue :+1:


Feature/cache experiment

endpoint for cache performance
remove egit in favour of kohsuke/github-api, use conditional requests where possible https://developer.github.com/v3/#conditional-requests
webservice will now wait when out of rate limit and disallow additional requests
webservice will re-use okhttp request cache between launches
some build log cleanup

Coverage increased (+0.3%) to 66.399% when pulling 897e3f1113ef86f21d4e909c7d952b38af445b42 on feature/cache_experiment into 6bf8ff28dd24c06636a2549615e466a17d8bd3e3 on develop.


KAFKA-7308: Fix rat and checkstyle config for Java 11 support

Relative paths in Gradle break when the Gradle daemon is used
unless user.dir can be changed while the process is running.
Java 11 disallows this, so we use project paths instead.
Verified that rat and checkstyle work with Java 11 after these
changes.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Thanks @lindong28. Test failures are unrelated, so merging to trunk.


fix None type handling on union codegen

What
Worked on my machine and got missed because of that (python versioning things)?
Checklist

[x] I have read and agree to Contributor Guide and the Code of Conduct
[x] I've included a screenshot or gif (if applicable)
[x] I have tested the web demo (if applicable):

Using examples from latest main build: rerun.io/viewer
Using full set of examples from nightly build: rerun.io/viewer

[x] The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG
[x] If applicable, add a new check to the release checklist!

PR Build Summary
Recent benchmark results
Wasm size tracking

To run all checks from main, comment on the PR with @rerun-bot full-check.

this internal slack thread counts as a review I think ;-)
https://rerunio.slack.com/archives/C045J1Z7DU7/p1715181520173509


Services do not start after a reboot of the container

I was puzzled why when my container rebooted (either because I was shutting down the container or because of machine reboot) the netatalk service inside the container would not start.
I believe that this is caused by a stale lock file in /var/lock/netatalk
I have altered the start_services.sh to remove that file before starting the service and it seems that the issue is fixed for me.
What are your thoughts on this?

I saw mine seize up as well. I didn't have time to investigate. But if this fixes it, that would be awesome. PR?

Please, submit a PR so we can check it and improve the container.
And thanks for your research work :)

Solved at PR https://github.com/odarriba/docker-timemachine/pull/6 :)


Add base and core bindless validation instrumentation classes

Getting id shift in my tests on the linux-based platforms. Windows is passing. Any ideas?

Figured out the id shift problem. I had two different routines that were doing TakeNextId() and was calling them as arguments to a function call where, I presume, the order of execution is not guaranteed across platforms.

Building of the validation files is failing although I haven't made any (direct) changes in the area. Any thoughts on what is going on here or how to proceed?

Looks like it failed on windows due to PDB issues. Usually re-building fixes the problem.

Related to what @dj2 was asking for, now that we have the official PR, is there a spec or something in gitlab that describes how all of this is suppose to work with all of the other parts?  What tasks will be validation layer be responsible for, and how will a user know which descriptor set and bindings the output will be located in?  Are these error codes defined in a specification for the feature?  What about the layouts for the messages?
I would like to know that the external interface is agreed upon and what it is  so I have a way of verifying that it is implemented correctly.
Also, should some of the things exist in spirv-headers, or something like that.  If they are in spirv-tools,  any project that uses this feature will have to depend on spirv-tools.

is there a spec or something in gitlab that describes how all of this is suppose to work with all of the other parts?

InstBindlessCheckPass is designed to partially address gitlab issue 1327 (Add Bounds Checking to Layers Using GPU-Assisted Validation) and InstrumentPass is designed to partially address 1293 (Develop tooling for shader instrumentation?). These are the only public documents for this work. The most recent design in 1327 should give you some context to understand the larger layer mechanism and how the instrumentation fits into it.
There is a lower-level design document that the layer developer is keeping here internal to LunarG, but as internal document, it is not clear how useful it would be for you to verify against it.
You should note that I have documented in inst_bindless_check_pass.h that the external design of InstBindlessCheckPass is wholly intended to address the needs of the bindless validation layer and that its external design may change as the needs of that layer change. This is meant to give a heads up to anyone else who builds anything against this design.
That said, the design of both InstBindlessCheckPass and the layer are pretty much set, at least for the core functionality. We have a version of the layer that was recently demo'd at the last F2F and is running solidly on at least one real game. So I am not expecting too much more change, which is why I am now attempting to check this in.
Can we just assume that the functionality that I document in inst_bindless_check_pass.h, instrument.hpp and optimizer.hpp is useful to the community, and verify that the code matches the documentation?

how will a user know which descriptor set and bindings the output will be located in?

As is documented in optimizer.hpp, the descriptor set is passed in by the layer through CreateInstBindlessCheckPass(). As is documented in instrument.hpp, the binding for the stream output buffer is 0. Let me know if you think this should be documented some other way.

Are these error codes defined in a specification for the feature? What about the layouts for the messages?

The documentation I have written is for the developer of the validation layer. The developer of the validation layer will decide what and how to document to the user of the layer since that is really a separate design.

I would like to know that the external interface is agreed upon and what it is so I have a way of verifying that it is implemented correctly.

The external interface for the output buffer for InstBindlessCheckPass is essentially what is documented in instrument.hpp. The layer includes instrument.hpp and uses those static consts, so by definition there is agreement on the external interface.

Also, should some of the things exist in spirv-headers, or something like that. If they are in spirv-tools, any project that uses this feature will have to depend on spirv-tools.

If the layer wishes to publish offsets somewhere to allow other tools to instrument to the layer, that would be their prerogative, but for now the layer is giving the control of the format of the output buffer to InstBindlessCheckPass.

This is documented elsewhere, but I thought I would point out that this current commit only covers core bindless functionality. The core functionality assumes that descriptor arrays are of compile-time constant size and all descriptors are initialized.
Future commits will cover the vk_ext_descriptor_indexing extension, which allows for runtime-sized descriptor arrays and uninitialized descriptors (if unused). My current thinking is that I will extend InstBindlessCheckPass to handle runtime-sized descriptor arrays, but will create a separate pass to check for uninitialized descriptors. Both passes will use the same output buffer stream to record errors.

We talked internally about the header file, and it is fine.  I don't really like GetLabel returning a reference to a unique pointer, but I won't hold this up any longer.  We can change that later if we need a need.

We talked internally about the header file, and it is fine.

My view was that these constants are tightly coupled to the code that does the instrumentation.  The new instrumentation code is being added to SPIRV-Tools so it's natural to put this header here.  It's good that the new constants are in their own header file, so it's clear that it's a different part of the API surface.
In future, we might expose the optimizer's classes and APIs for representing, manipulating, and analyzing a SPIR-V module (a real representation for update purposes).  In that case this instrumentation code could take a life of its own in its own repository (and independent maintenance, evolution, and leadership).  In that case the code doing the instrumentation and its interface header would move to that other repository.  That future is still open to us, and that's great.


[Theme]: Love and Deep Space

Tips

[X] I have read and understood the tips above

Theme Name
Love and Deep Space
Preview and ZIP file
尺寸73*173，主图透明底gif，预览图为白底png
LoveAndDeppSpace.zip

我是不是应该把preview放在外面

Thanks for sharing, the theme is now available.
Theme name:
love-and-deepspace
Preview:


Use Store from github

Use latest orbit-db-store

Depends on: https://github.com/orbitdb/orbit-db-store/pull/37


[MAD][DATA1018][visualizing-real-world-data] Miriam Montaño

Good job Miriam!! The rating is quite similar to a categorical variable so it doesn't make sense at all to plot a scatter for these kind of variables. It's more useful to plot barplots between categorical variables. It's sometimes useful when you have such concentration of data, as is the price in this case, you can split your analysis off app between low price, medium and high price (in case you have enough records to plot).
Keep on working!!


[10.x] Remove deprecated dispatchNow functionality

This will remove the deprecated functions and methods around dispatchNow. The internals will remain to not make the upgrade path too hard but in general we want to push people more to use dispatchSync which is the only supported way to dispatching immediately.

I just realized, unlike dispatchNow we can not mention the onQueue in dispatchSync. this is mandatory in my case to pass dynamic queue name. so dispatchNow is an essential function for me. Please update dispatchSync to accept queue name.


Does nerfmm work well with 360 captured scene?

Were any experiments conducted with 360 captured scene? Curious to know if there is any difference between training forward facing vs 360 scene.

Hi @nischal-sanil,
Nope. nerfmm only support forward-facing scenes currently. There are mainly three issues when applying it to 360-degree scenes:

We use NDC so that we do not need to estimate nerf/far boundaries.
Camera poses in 360-degree scenes are much more difficult to estimate.
As stated in NeRF++, things become more complicated in 360-degree scenes even when camera poses are available, for example, the nerf/far boundaries, sampling strategies on a ray, background handling and etc. Check out this issue. With camera poses from COLMAP, 360-degree scenes are still challenging to the official NeRF sometimes.

Best,
Zirui

Hi @ziruiw-dev and @nischal-sanil,
I was playing around with 360 captured scene with --use_ndc False.
I slightly modified tasks/nerfmm/train.py to use volume_sampling() instead of volume_sampling_ndc().
The data I'm using looks like this:

I used the camera parameters estimated by COLMAP and start refining from 1000th epoch.
However, the evaluation visualization is catastrophic:

Could you please provide any suggestion on how to solve this problem?
Thank you.

Hi @DeanChan,
There are a few things you should check:

Check if you can train the scene with a standard NeRF, which might also have difficulties in these 360-degree scenes.
Check if you set near and far to reasonable values so that the 3D point samples can be observed by all cameras.
Check if you set --start_refine_epoch=1000 (in target/refine_nerfmm) or some value larger than 0. This can train the NeRF with COLMAP camera parameters and start refining camera parameters after this epoch value.

After all, this paper/repository is not designed to handle 360-degree scenes and it is not trivial to extend it to 360-degree scenes.
Best,
Zirui

Hi @ziruiw-dev. Thank you for your suggestions!
I replaced near, far = 0, 1 with near, far = meta['bounds'].min(), meta['bounds'].max(). The rendering result looks quite well now.
I also find that the rendering result is highly sensitive to the near and far settings. Do you have any general rule to choose the appropriate bounds?
Thanks😃

Setting near and far in nerfmm is as same as the original NeRF. Basically, the near and far values determine the size of a camera frustum. When you have multiple cameras looking at something in common, you should set the near and far so that those camera frustums intersect with each other. The overlapped 3D space is the space where you sample 3D points and input to the NeRF network. One good way to check if your near and far are reasonable is to visualise those camera frustums in 3D.

Thank you for the suggestions. @ziruiw-dev

Hi @DeanChan, I was trying to run nerfmm on a 360-degree as well. you mentioned that you got a better result after changing near and far values. Could you please share the improved results so that I can compare it to my results?

Hi @basit-7, the improved results look like this:


[ROS2] Add wall in front of user for all movements but the final MoveToMouth / initial MoveFromMouth

Currently, sometimes the MoveFromMouth action will have a cartesian motion back from the mouth, and will then move closer to the user's face during the kinematic motion. That movement closer to the user's face feels scary and unnecessary.
To address this, we should have a wall in front of the user that prevents the robot from moving closer to the user. For safety, we should have this wall for all motions, and only disable it for the cartesian motions to/from the mouth in MoveToMouth / MoveFromMouth. However, if we put this wall too close to the staging pose, it is possible that the end configuration of the cartesian motion in MoveFromMouth leaves the robot in collision with this. Therefore, we might also need to be able to move this wall based on the robot arm pose so it is always right beyond the forktip, and essentially prevents the robot from moving closer to the user than it already is.

Reopening because I saw a MoveToMouth movement to the staging configuration that moved unnecessarily close to the head. So even MoveToMouth should add this wall for the movement to the staging configuration.


Logic for reading OSCAL component file

Create logic for reading a file from arguments and unmarshalling into oscalComponentDefinition objects.

Having filesystem logic be able to read a single file is required. Being able to read a directory of files would be nice to have.
Create/import a type struct for oscalComponentDefinition
Integrate with the field added by the additions made to the istio oscal-component.yaml

Completed in: https://github.com/defenseunicorns/compliance-auditor/pull/17


embedding lure url in iframes

i tried embedding the url into iframe and it redirected and created a pop up which was blocked by my browser...is there anyone who can help me out with this.

Check out https://github.com/waelmas/frameless-bitb

**Hi 👽 ! If you are interested in ⚙Advanced Phishing⚙ and the ✨Evilginx3✨ tool then I offer you Google Gmail and Custom Phishlets with a ✅Free Tutorial✅ which arrives if the 📈Telegram reaches 50 Subscribers📈
⏳ GOOGLE GMAIL PHISHLET 2024 WITH PROOF ⏳
->
⛔https://www.youtube.com/watch?v=nA47UknIE6A⛔
🔓 Ask your questions and a free tutorial from 50 subs on telegram !!!
->
📩https://t.me/Noremorse1011📩**


Support log output to file

Close #36

[x] Support log output to specified file
[ ] Disable log when show command without --out option

Coverage increased (+0.05%) to 95.331% when pulling e57de5fd9a17967a2ce8f896c64875ecde1f1345 on enhance-logger into 0430fdb5c8d6e6fc1d06b65b9f5eca0fbc289103 on master.

Coverage increased (+0.06%) to 95.348% when pulling 5e4465513ecdb67fe03b4eb3af52fc694a585bc1 on enhance-logger into 0430fdb5c8d6e6fc1d06b65b9f5eca0fbc289103 on master.


Address unit size & description

Blocked on https://github.com/rust-embedded/svd/pull/104 & https://github.com/rust-embedded/svd/pull/101

Just noting that rust-embedded/svd#101 has been superseded by rust-embedded/svd#115, which has also yet to merge.


update developer guide to include tailored k8s cluster installation

Problem
The current developer guide documentation references the main knative install docs for instructions on how to create a  k8s cluster for this project. However, the referenced knative docs does not include the creation of k8s clusters and assumes that user's already have one created.
Persona:
Which persona is this feature for?
Contributor

/assign

@pierDipi any update on this?

I'm on it

@Alfusainey can you follow steps described here: https://github.com/knative-sandbox/eventing-kafka-broker/pull/29

@Alfusainey can you follow steps described here: #29?

ok, am on it now


Ft users settings

changes made to pass the ci/cd

also add proper description on your pull request


EFU-912 Create components: SwitchButton - Tile/List

(The frame rate of the GIF is not on point. It looks much smoother in the storyboard.)
Note:
There are certainly still ways to improve the switch. But this is at least a start.

Codecov Report

Merging #46 (b118f48) into main (c3131b8) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main       #46   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           15        25   +10
  Lines          101       148   +47
  Branches        19        29   +10
=========================================
+ Hits           101       148   +47

Impacted Files
Coverage Δ

packages/switches/src/Switch/LabelledSwitch.tsx
100.00% <100.00%> (ø)

packages/switches/src/Switch/SimpleSwitch.tsx
100.00% <100.00%> (ø)

packages/switches/src/Switch/Switch.tsx
100.00% <100.00%> (ø)

packages/switches/src/Switch/index.ts
100.00% <100.00%> (ø)

...ges/switches/src/ViewsSwitch/ChakraViewsSwitch.tsx
100.00% <100.00%> (ø)

packages/switches/src/ViewsSwitch/ViewsSwitch.tsx
100.00% <100.00%> (ø)

packages/switches/src/ViewsSwitch/index.ts
100.00% <100.00%> (ø)

packages/switches/src/ViewsSwitch/styles/index.ts
100.00% <100.00%> (ø)

packages/switches/src/index.ts
100.00% <100.00%> (ø)

... and 9 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 c3131b8...b118f48. Read the comment docs.


Not able to run this respository after cloning the same following is the error

Last login: Thu Aug 26 19:30:45 on ttys001
fsd2@Nikhils-MacBook-Pro ~ % /Users/fsd/Downloads/react-native-scoped-storage-master/example/node_modules/react-native/scripts/launchPackager.command ; exit;
                    #######
               ################
            #########     #########
        #########             ##########
    #########        ######        #########
   ##########################################
  #####      #####################       #####
  #####          ##############          #####
  #####    ###       ######       ###    #####
  #####    #######            #######    #####
  #####    ###########    ###########    #####
  #####    ##########################    #####
  #####    ##########################    #####
  #####      ######################     ######
   ######        #############        #######
     #########        ####       #########
          #########          #########
              ######### #########
                   #########

                Welcome to Metro!
          Fast - Scalable - Integrated

To reload the app press "r"
To open developer menu press "d"
BUNDLE  ./index.js
error: Error: While trying to resolve module react-native-scoped-storage from file /Users/fsd/Downloads/react-native-scoped-storage-master/example/App.tsx, the package /Users/fsd/Downloads/react-native-scoped-storage-master/example/node_modules/react-native-scoped-storage/package.json was successfully found. However, this package itself specifies a main module field that could not be resolved (/Users/fsd/Downloads/react-native-scoped-storage-master/example/node_modules/react-native-scoped-storage/index.js. Indeed, none of these files exist:

/Users/fsd/Downloads/react-native-scoped-storage-master/example/node_modules/react-native-scoped-storage/index.js(.native|.android.js|.native.js|.js|.android.json|.native.json|.json|.android.ts|.native.ts|.ts|.android.tsx|.native.tsx|.tsx)
/Users/fsd/Downloads/react-native-scoped-storage-master/example/node_modules/react-native-scoped-storage/index.js/index(.native|.android.js|.native.js|.js|.android.json|.native.json|.json|.android.ts|.native.ts|.ts|.android.tsx|.native.tsx|.tsx)
at DependencyGraph.resolveDependency (/Users/fsd/Downloads/react-native-scoped-storage-master/example/node_modules/metro/src/node-haste/DependencyGraph.js:436:17)
at Object.resolve (/Users/fsd/Downloads/react-native-scoped-storage-master/example/node_modules/metro/src/lib/transformHelpers.js:317:42)
at resolve (/Users/fsd/Downloads/react-native-scoped-storage-master/example/node_modules/metro/src/DeltaBundler/traverseDependencies.js:629:33)
at /Users/fsd/Downloads/react-native-scoped-storage-master/example/node_modules/metro/src/DeltaBundler/traverseDependencies.js:645:26
at Array.reduce ()
at resolveDependencies (/Users/fsd/Downloads/react-native-scoped-storage-master/example/node_modules/metro/src/DeltaBundler/traverseDependencies.js:644:33)
at /Users/fsd/Downloads/react-native-scoped-storage-master/example/node_modules/metro/src/DeltaBundler/traverseDependencies.js:329:33
at Generator.next ()
at asyncGeneratorStep (/Users/fsd/Downloads/react-native-scoped-storage-master/example/node_modules/metro/src/DeltaBundler/traverseDependencies.js:137:24)
at _next (/Users/fsd/Downloads/react-native-scoped-storage-master/example/node_modules/metro/src/DeltaBundler/traverseDependencies.js:159:9)
info Reloading app...
BUNDLE  ./index.tsx

error: Error: While trying to resolve module react-native-scoped-storage from file /Users/fsd/Downloads/react-native-scoped-storage-master/example/App.tsx, the package /Users/fsd/Downloads/react-native-scoped-storage-master/example/node_modules/react-native-scoped-storage/package.json was successfully found. However, this package itself specifies a main module field that could not be resolved (/Users/fsd/Downloads/react-native-scoped-storage-master/example/node_modules/react-native-scoped-storage/index.js. Indeed, none of these files exist:

/Users/fsd/Downloads/react-native-scoped-storage-master/example/node_modules/react-native-scoped-storage/index.js(.native|.android.js|.native.js|.js|.android.json|.native.json|.json|.android.ts|.native.ts|.ts|.android.tsx|.native.tsx|.tsx)
/Users/fsd/Downloads/react-native-scoped-storage-master/example/node_modules/react-native-scoped-storage/index.js/index(.native|.android.js|.native.js|.js|.android.json|.native.json|.json|.android.ts|.native.ts|.ts|.android.tsx|.native.tsx|.tsx)
at DependencyGraph.resolveDependency (/Users/fsd/Downloads/react-native-scoped-storage-master/example/node_modules/metro/src/node-haste/DependencyGraph.js:436:17)
at Object.resolve (/Users/fsd/Downloads/react-native-scoped-storage-master/example/node_modules/metro/src/lib/transformHelpers.js:317:42)
at resolve (/Users/fsd/Downloads/react-native-scoped-storage-master/example/node_modules/metro/src/DeltaBundler/traverseDependencies.js:629:33)
at /Users/fsd/Downloads/react-native-scoped-storage-master/example/node_modules/metro/src/DeltaBundler/traverseDependencies.js:645:26
at Array.reduce ()
at resolveDependencies (/Users/fsd/Downloads/react-native-scoped-storage-master/example/node_modules/metro/src/DeltaBundler/traverseDependencies.js:644:33)
at /Users/fsd/Downloads/react-native-scoped-storage-master/example/node_modules/metro/src/DeltaBundler/traverseDependencies.js:329:33
at Generator.next ()
at asyncGeneratorStep (/Users/fsd/Downloads/react-native-scoped-storage-master/example/node_modules/metro/src/DeltaBundler/traverseDependencies.js:137:24)
at _next (/Users/fsd/Downloads/react-native-scoped-storage-master/example/node_modules/metro/src/DeltaBundler/traverseDependencies.js:159:9)

It points to a index.tsx file which does exist. not sure why you are getting this error. can you try again?


Pick team photos

The About page (XD link) contains photos and bios for the lab team. Everyone should either 👍 their current photo choice, or provide a replacement for Joanna to clip and stylize. (@cguess and @ericaryan in particular have low-res photos).
I'm assigning this task to everyone involved to individually give their approval or provide replacement!

Mine looks great. Thanks!

Happy with mine!

Is this better quality?

@joannafonte I leave it up to you to decide if you think we need to clip everyone's backgrounds out or not. May reach a point of diminishing returns on that one, lol.

Heeeeeeeeere's Asa!

I found this fantastic photo of @markstencel and nominate it for inclusion.

With all of these collected, I'm closing this and kicking the rest of the work over to #429.


Default configuration files

It would be nice that the first time you run the program it generates the default .env files as well as the sample config.json in the location where the binary/exe is.
The program should be default try to open http://localhost:8080/?configPath=./config.json

I agree with the first point, but not at the runtime. Maybe a command like monitoror init to prevent creating useless files for those who do not want them since you can put your env variables in your profile, or in the command line and use a config from a URL.
I'm OK with the 2nd idea, but not that way. I think it can be done via another idea from another issue/post (IDK where ^^') which consists in setting default config path/URL from .env, which makes the query param useless, and the usage more transparent and easy.
Thank you for your feedback :)


[BUG] Footer Icons

Description of the bug
As of now in footer , first section and second section has its elements in up down order, but icons are side by side. We can improve design and make it more standard by making it top down icons
Please add screenshots (if applicable)

Add any other context about the problem here
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Assign it to me

Are you working it under GSSoC ?


ENH Updated manual curation for latest RGI

I thought we had decided to change the representation of the data to not include unmapped lines in either the automated annotation outputs or the manual curation. This would also make merging the two a trivial operation (just concatting the tables)
I'm fine if this is not a good idea, but it feels that this should be an explicit design decision


Cube Texture sample gives an error

I tried to display the following sample with Chrome Canary 111.
https://06wj.github.io/WebGPU-Playground/#/Samples/CubeTexture
However, there seems to be an error in the console.
Tint WGSL reader failure: :20:11 error: 'final' is a reserved keyword
      var final = vec3<f32>(pos.x, pos.y, pos.z);
          ^^^^^

Fixed it.

Thanks!


Cannot load amdgpu after updating flake

Describe the bug
I recently updated my flake.lock using nix flake update. After that commit, the amdgpu kernel module can't be loaded anymore:

After reverting that commit, it works again. Here is my config, and here the config specific to that machine.
It's a TUXEDO Pulse 15 Gen 2 laptop.
Output of cat /proc/cpuinfo (if that's important): https://paste.debian.net/1305813
Steps To Reproduce
Steps to reproduce the behavior:

Update flake using cd /path/to/repo && sudo nix flake update
Rebuild system using sudo nixos-rebuild --flake .#
Reboot

Expected behavior
amdgpu module should be loaded fine
Screenshots
See above
Notify maintainers
@corngood
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
db > nix-shell -p nix-info --run "nix-info -m"
this path will be fetched (0.00 MiB download, 0.00 MiB unpacked):
  /nix/store/2bk3cqpj26fi3fwgshgg3k0fxwz0h55g-nix-info
copying path '/nix/store/2bk3cqpj26fi3fwgshgg3k0fxwz0h55g-nix-info' from 'https://cache.nixos.org'...
 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.8, NixOS, 24.05 (Uakari), 24.05.20231227.cfc3698`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.1`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

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

Okay sorry, I guess this is most likely fixed by https://github.com/NixOS/nixpkgs/pull/284487. However, when I run nix flake update, I'm on c002c6a, which is 3 days old. Can anyone tell me why?

Could you share dmesg output, or whatever other error you got about the kernel module?

Could you share dmesg output, or whatever other error you got about the kernel module?

I did, it's embedded as an image in my first post.

I do not think the commit resolving this has made it to nixos-unstable yet -- you can track progress here though.

@devusb Thanks. To be honest, I'm a little bit confused. Not sure why it needs to be present in nixos-unstable if I have nixpkgs-unstable as an input and it's present there. That is, if nix flake update would get me to the latest commit, which it doesn't for some reason.

@minikN Sorry!  ad-blocker was too aggressive :)
Yeah, that's definitely the same issue.

Not sure why it needs to be present in nixos-unstable if I have nixpkgs-unstable as an input and it's present there.

I'm not sure what you mean by this.  Your system seems to be using nixos-unstable.  I don't see a reference to nixpkgs-unstable in there.

@minikN Sorry! ad-blocker was too aggressive :)
Yeah, that's definitely the same issue.

Not sure why it needs to be present in nixos-unstable if I have nixpkgs-unstable as an input and it's present there.

I'm not sure what you mean by this. Your system seems to be using nixos-unstable. I don't see a reference to nixpkgs-unstable in there.

Sorry, just realized that I'm indeed using nixos-unstable. I just read up on it on the wiki:

For Nix users, nixpkgs-unstable is the bleeding-edge, where packages pass only basic build tests and are upgraded continuously.
For NixOS users, nixos-unstable is the bleeding-edge, where packages pass build tests and integration tests on a VM, and are tested from the perspective of being an operative system (this means things like the X server, KDE, various servers, and lower level details like installing bootloaders and runnning the nixos installation steps are also tested).

This means because I'm running NixOS and not just nix, I need to wait until that PR get's to nixos-unstable, is that correct?

This means because I'm running NixOS and not just nix, I need to wait until that PR get's to nixos-unstable, is that correct?

Yes, unless you choose to use a different channel, like nixos-unstable-small.

Alright, thanks @alyssais @devusb @corngood !


extra permission node "minecraft.command."

There seems to be an additional permission node registered for a command, unclear when or why as it showing up seems to be sporadic. The node is in the format "minecraft.command."
It seems to always appear when registering a command without a PermissionNode specified, and sometimes show up if I specify my own PermissionNode when registering the command. I am using LuckPerms' /lp tree command to list permission nodes, I have had one instance so far where "minecraft.command." node does not show up at first, but will appear in the tree later.
In all cases, the command will still complete despite the extra permission node being attached to the command, but I cannot use the command if I do not have this permission set for myself.
Using version 1.6 with Paper 1.13.2 build 444

Sorry it took so long for a response, this is by far the hardest bug I've tried to sort out and I still have not gotten close to a solution yet.
To answer to first query: Why the minecraft.command. node is added. Simply put, the CommandAPI is a wrapper for Brigadier. Brigadier is primarily used by Minecraft to register Vanilla Minecraft Commands. When Bukkit (Craftbukkit/Spigot/PaperSpigot) registers a "vanilla" minecraft command, it automatically registers the permission node minecraft.command.<commandName> to that command.
Now, permissions are this tightly knit super unnecessarily complex topic where things get very hazy and it is really difficult to understand. I'm trying to create a "valid" workaround for the problem - There are some "cheap" workarounds which fix the problem (i.e. you can't run the command if you don't have the permission), but aren't "correct" in the sense that they have the perfect desired effect (i.e. tab complete doesn't occur if you don't have the permission etc. - which is handled internally by the server)
I'm still trying my very best to work on this issue, but I don't believe I'll be able to push out the desired bug fix in time for the next planned release of 1.7.

Alright! I finally made progress and found a way to fix the issue in this commit.
In this commit, lots of the permission system was rewritten and should have full support for permissions. I'll deal with sub-permissions in the relevant issue #26 instead of here.
Keep an eye out for the documentation when 1.7 is released which should cover the new syntax changes for permissions.


Add user control session

Coverage increased (+0.2%) to 18.966% when pulling 005d1dce7b28359b814b9ee0e74e7a75af9cbd37 on user_session into fd5d56caa0d86318751ef4c19b5cae642326f988 on master.

Coverage increased (+0.2%) to 18.966% when pulling 43a534db7a89438b5435e0f99371a6cba5a58ebc on user_session into fd5d56caa0d86318751ef4c19b5cae642326f988 on master.


Import Katana and NOWIN harnesses from FubuMVC

Nope, not gonna do this one now that it's not going to be OWIN based.


Add new capability for selecting a specific kernel index

Hi all,
this patch is meant to let the user choose a specific kernel identified by its index in the Master Solution Library.
Comments and suggestions are more than welcome.
Alessandro

First, we should be consistent in calling this a 'solution' index, not a 'kernel' index, since a solution can involve multiple kernels being invoked (for GSU).
Second, if this environment variable is set, then Tensile will only support one particular transpose, and one particular data type.  It may also have other restrictions in terms of problem/stride size since some solutions may have such limitations.  @zaliu I'm not sure if there's a need to communicate this better?
Finally, this would be best implemented in MasterSolutionLibrary: https://github.com/ROCmSoftwarePlatform/Tensile/blob/develop/Tensile/Source/lib/include/Tensile/MasterSolutionLibrary.hpp#L87 as the the solutions member is a map from SolutionIndex to Solution.  We just need to check the predicates and then either return the solution or nullptr if the predicates fail.

@zaliu I'm not sure if there's a need to communicate this better?
Your comments are clear enough.  I'm sure @afanfa will communicate directly with us if clarifications are needed.  Thanks!

Sorry, by communicate I mean by means of a comment in the code or a printed warning when this environment variable is active.

Thanks for the quick review. I will implement this functionality in MasterSolutionLibrary as suggested by @sdquiring with a better naming.

Something didn't work with my rebase.


PR for issues #3, #9, #8, #4, #10, #5

PR for issues #3, #9, #8, #4, #10, #5

@lorban, @anthonydahanne : I'll let you check / merge it ?

If you add AverageHistory and still keep the non-history classes, why not adding a Average class too?

Since everything seems to extend from AbstractMeasurableStatistic after your change, why not getting rid of it as well as the MeasurableStatistic interface and merging that all in AbstractStatistic / Statistic?

@lorban , @anthonydahanne : PR updated after review / comments. I added StatisticHistory interface to handle more easily on user side the history-based statistics (having list of samples)


knolleary/pubsubclient.h library delay issue when server down..

Hii,
I am new user to mqtt. Kindly support for my few basic question.
I have implemented mqtt with knolleary/pubsubclient.h and it works absolutely fine without any issue. But I am facing an issue when my server is down..
When my server is down or if my LAN connection is broken with my router it takes around 5 secs to get detected and connect and because of that I am unable to function my other functionalities.
I tried reading libraries and tried to detect exact delay but was unsuccessful..
Please find my reconnect loop below.
void reconnect() {
// Loop until we're reconnected
if (!client.connected())
{
Serial.println("Attempting MQTT connection...");
// Attempt to connect
client.connect("ESP8266Client");
if (client.connect("ESP8266Client"))
{
Serial.println("connected");
// Once connected, publish an announcement...
client.publish(outTopic, "MCU Active");
// ... and resubscribe
client.subscribe(inTopic);
}
else
{
Serial.println("failed");
}
}
}
Immidiate support will be greatful.
Thanks all.

I'm having similar issue. I'm using the non-blocking way of connecting and also defined MQTT_SOCKET_TIMEOUT to 2 secs (just for testing) but it looks like that definition isn't taken into account as I still have to wait roughly 5secs until I get a response from connect() method with a response code -2...

Hi,
same thing happened on my esp8266.
I could connect to test.mosquitto.org = <IP_ADDRESS>,
but not to my local mosquitto on a RPi or mosquitto docker on a qnap.
I always got the -2 error code.
In another issue i saw this solution:
Just add the   WiFi.mode(WIFI_STA); before wifi.begin
  WiFi.mode(WIFI_STA);
  WiFi.begin(ssid, password);

This is working for me now.


CORS for requests originating from Chrome extension

Hi,
I'm trying to enable CORS for requests originating from a Chrome Extension, but I can't get it to work. The docs clearly state that enableCors: true only works for requests originating from a browser, but a Chrome extension doesn't seem to follow that rule.
Request header is as follows (check origin).
Accept:*/*
Content-Type:application/x-www-form-urlencoded
CSP:active
Origin:chrome-extension://kaagfgncegpdenjlhoekjfigancflibd

any ideas? Thanks in advance

Hi Satya!
I agree that it would be nice to test CORS from browser REST clients, but I'm not sure that's possible, based on the accepted answer to this Stack Overflow question. If that doesn't answer your question, your best bet would probably be to continue the discussion on Stack Overflow, as this is a bit outside the scope of Restivus.
Thanks for the question!

Are you sure that's outside Restivus scope? What I've read so far is (http://meteorpedia.com/read/REST_API):

There are security implications for making REST requests to other domains, and you may run into problems with the default security policies. Full info from MDN at HTTP access control (CORS).
Particularly, a HTTP.call('POST', url, { data: object }); (POST with data) will (correctly) set the Content-Type to application/json, but default security policies won't allow this. You'll get something like:
Failed to load resource: No 'Access-Control-Allow-Origin' header is present on the requested resource.  Origin 'http://www.blah.com/' is therefore not allowed access.
That's because requests of this nature send a preflight request using the OPTIONS method, and your API needs to handle these kinds of requests. It's expected that the higher level methods mentioned above will handle this for you. More info in this meteor-talk post.

I feel this is exactly my problem.

FYI: I've upgraded to 0.8.0 and now CORS works fine.

Awesome! Glad to hear it solved the issue.


⚠ SceneTime has degraded performance

In 532cf87, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 3088 ms

Resolved: SceneTime performance has improved in bda4f1c after 7 minutes.


Release

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

v1.50.0
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.50.0-develop.3 :tada:
The release is available on:

v1.50.0-develop.3
GitHub release

Your semantic-release bot :package::rocket:


onShow called when modal really shown

Great lib, a pleasure to use it !

I used the onShow, which seems the prefect option for that.
However, it is called at the end of the _modalShow, and at that moment, the new DOM piece is not yet drawn by the browser.
Therefore you can't access your new DOM elements. (you might not notice if your post-processing is slow like for example ajaxing some data)
It therefore makes more sense to call the onShow when the dialog has really finished displaying.
That means in the callback of the fadeIn.

thanks :)


Added Dynatrace Adaptor

Closes https://github.com/appwrite/appwrite/issues/4210

@PineappleIOnic If can add the hacktoberfest-accepted label to this PR  to ensure it counts towards my Hacktoberfest contributions count, I would greatly appreciate it!

Thank you so much for the PR 🤩. We're adding the hacktoberfest-accepted label to ensure this PR counts towards your Hacktoberfest contributions count. With that said, please stay active on this PR to address any comments once you receive a review. Happy Hacktoberfest! 🎃

@stnguyen90 I would greatly appreciate if you can review this PR. Please let me know if additional changes are needed.

@michizhou looks like there are merge conflicts. Would you please resolve them?

@stnguyen90 I have resolved the merge conflicts. Please let me know if additional changes are needed.


[refactoring] Use glMatrix rather than THREEJS.* for math operation whenever possible

http://glmatrix.net/

May or may not be a good idea. Got to see if it has some threeJS implications


[BUG] Can't apply grid ufunc with padding if axis position doesn't change

I realised that I overlooked quite an important case: currently if you try to apply a grid ufunc which pads along an axis but still returns a variable which has that same axis:position pair as the input, xr.apply_ufunc will throw an error. For example whilst this works:
@as_grid_ufunc("(X:center)->(X:left)", boundary_width={"X": (1, 0)})
def diff_center_to_left(a):
    return a[..., 1:] - a[..., :-1]

this does not:
@as_grid_ufunc("(X:center)->(X:center)", boundary_width={"X": (2, 0)})
def diff_center_to_center_second_order(a):
    return 0.5 * (a[..., 2:] - a[..., :-2])

The latter throws an error like
ValueError: size of dimension 'depth_c' on inputs was unexpectedly changed by applied function from 11 to 9.
Only dimensions specified in ``exclude_dims`` with xarray.apply_ufunc are allowed to change size.

The reason is that the dimensions of the output variable are set by the grid positions in the signature - in the first case we pad a dimension to be longer, then act on it with xr.apply_ufunc and want the output to be shorter along a different dimension, whereas in the second case we pad a dimension to be longer, then act on it with xr.apply_ufunc and want the output to be shorter along that same dimension.
There are potentially two ways to fix this:

Do something clever with renaming dimensions to have temporary names whilst inside xr.apply_ufunc, so xarray doesn't realise there is a conflict in sizes,
Move the padding inside the ufunc as described in #436.

This bug is currently what's stopping me from computing vorticity of LLC data @rabernat FYI, because the simplest grid ufunc for that looks like this (see #436)
def diff(a, axis):
    def _diff(a):
        return a[..., 1:] - a[..., :-1]

    return np.apply_along_axis(_diff, axis, a)

@as_grid_ufunc("(lon:left,lat:center),(lon:center,lat:left)->(lon:left,lat:left)",
               boundary_width={"lon": (1, 0), "lat": (1, 0)})
def vort(u, v):
    """This needs to return an array 1 element smaller along both axis -1 & -2."""
    u_trimmed = u[..., 1:]
    v_trimmed = v[..., 1:, :]

    return (
        diff(v_trimmed, axis=-1)
        - diff(u_trimmed, axis=-2)
    )

which has lon:left and lat:left on both inputs and outputs.

We could probably also make this work by adding the dimension to exclude_dims (see this example, but I still think we should move the padding inside the applied function.

Closed by #451 by adding exclude_dims.


Add support for pdf2htmlex --split-page option

This PR adds support for directing pdf2htmlex to write its output to multiple pages.
On the Ruby side you can now provide a split_pages parameter:
Kristin.convert("someFile.pdf", "someFile.html", { split_pages: true })

This is passed to pdf2htmlex as this command line option:
--split-pages 1

...as discussed in the pdf2htmlex docs

closing...i will create another that will supersede this.


[1015] Add trainee start date workflow

Context
https://trello.com/c/vF1XOj65/1015-l-add-commencement-date
Changes proposed in this pull request

Add commencement_date field to the Trainee
Replace "Trainee ID" with "Trainee start date and ID" on the review draft page
New training details page to capture both trainee ID and start date, including validation and progress tracking
Add edit page for Trainee start date
Non-draft will have separate confirmation for each field.
Send commencement_date to DTTP
Remove trainee ID field from new record page

Guidance to review
Visit a draft and non-draft record play around with changing the trainee ID and start date

 [L] Add commencement date

@defong Pushed fix

Validation message?

2000+ years ago?

I think we need some better validation on dates. Filling in the day and month only is accepted as valid - it appears to convert the empty year in to year 0, which is then considered valid.

The summary card for trainee start date and id should exist on the 'review this record' page on draft records. At the moment it's showing the old summary card.

@edwardhorsford Pushed more updates. Hopefully, that should be all the issues sorted.


Fix schema stats prometheus summary memory leak

Motivation
#14723 introduces schemaId label metrics.
Prometheus summary maintains a map to record label and value, summary will not auto-release the label. Which will leads to memory leak.
We missed to unRecord label when schemaId were deleted.