clangd "--query-driver" option doesn't follow symlinks

When I run clangd with the --query-driver option set to a path containing a symlink, the argument has no effect and I still have missing system headers. In the following case, <iostream> can't be found.
#include <iostream>

int main(int argc, char* argv[])
{
    std::cout << "hi\n";
    return 0;
}

I can work around this issue by using the complete path without any symlinks.
Within the logs, the oe-workdir path item is a symlink to another location.
Logs
Please attach the clangd stderr log if you can. (Usually available from the editor)
If possible, run with --log=verbose - note that the logs will include the contents of open files!
If this is a crash, try to put llvm-symbolizer on your PATH per the troubleshooting instructions.
[START][2024-03-16 12:09:47] LSP logging initiated
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	'I[12:09:47.584] clangd version 17.0.6\nI[12:09:47.584] Features: linux\nI[12:09:47.584] PID: 102869\nI[12:09:47.584] Working directory: /home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight\nI[12:09:47.584] argv[0]: /usr/bin/clangd\nI[12:09:47.584] argv[1]: --log=verbose\nI[12:09:47.584] argv[2]: --query-driver=/home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/oe-workdir/recipe-sysroot-native/usr/bin/aarch64-poky-linux/aarch64-poky-linux-g++\nV[12:09:47.584] User config file is /home/jasonc/.config/clangd/config.yaml\nI[12:09:47.584] Starting LSP over stdin/stdout\nV[12:09:47.584] <<< {"id":1,"jsonrpc":"2.0","method":"initialize","params":{"capabilities":{"offsetEncoding":["utf-8","utf-16"],"textDocument":{"callHierarchy":{"dynamicRegistration":false},"codeAction":{"codeActionLiteralSupport":{"codeActionKind":{"valueSet":["","quickfix","refactor","refactor.extract","refactor.inline","refactor.rewrite","source","source.organizeImports"]}},"dataSupport":true,"dynamicRegistration":false,"isPreferredSupport":true,"resolveSupport":{"properties":["edit"]}},"completion":{"completionItem":{"commitCharactersSupport":true,"deprecatedSupport":true,"documentationFormat":["markdown","plaintext"],"insertReplaceSupport":true,"insertTextModeSupport":{"valueSet":[1,2]},"labelDetailsSupport":true,"preselectSupport":true,"resolveSupport":{"properties":["documentation","detail","additionalTextEdits","sortText","filterText","insertText","textEdit","insertTextFormat","insertTextMode"]},"snippetSupport":true,"tagSupport":{"valueSet":[1]}},"completionItemKind":{"valueSet":[1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25]},"completionList":{"itemDefaults":["commitCharacters","editRange","insertTextFormat","insertTextMode","data"]},"contextSupport":true,"dynamicRegistration":false,"editsNearCursor":true,"insertTextMode":1},"declaration":{"linkSupport":true},"definition":{"linkSupport":true},"documentHighlight":{"dynamicRegistration":false},"documentSymbol":{"dynamicRegistration":false,"hierarchicalDocumentSymbolSupport":true,"symbolKind":{"valueSet":[1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26]}},"hover":{"contentFormat":["markdown","plaintext"],"dynamicRegistration":false},"implementation":{"linkSupport":true},"publishDiagnostics":{"relatedInformation":true,"tagSupport":{"valueSet":[1,2]}},"references":{"dynamicRegistration":false},"rename":{"dynamicRegistration":false,"prepareSupport":true},"semanticTokens":{"augmentsSyntaxTokens":true,"dynamicRegistration":false,"formats":["relative"],"multilineTokenSupport":false,"overlappingTokenSupport":true,"requests":{"full":{"delta":true},"range":false},"serverCancelSupport":false,"tokenModifiers":["declaration","definition","readonly","static","deprecated","abstract","async","modification","documentation","defaultLibrary"],"tokenTypes":["namespace","type","class","enum","interface","struct","typeParameter","parameter","variable","property","enumMember","event","function","method","macro","keyword","modifier","comment","string","number","regexp","operator","decorator"]},"signatureHelp":{"dynamicRegistration":false,"signatureInformation":{"activeParameterSupport":true,"documentationFormat":["markdown","plaintext"],"parameterInformation":{"labelOffsetSupport":true}}},"synchronization":{"didSave":true,"dynamicRegistration":false,"willSave":true,"willSaveWaitUntil":true},"typeDefinition":{"linkSupport":true}},"window":{"showDocument":{"support":true},"showMessage":{"messageActionItem":{"additionalPropertiesSupport":false}},"workDoneProgress":true},"workspace":{"applyEdit":true,"configuration":true,"didChangeWatchedFiles":{"dynamicRegistration":false,"relativePatternSupport":true},"semanticTokens":{"refreshSupport":true},"symbol":{"dynamicRegistration":false,"hierarchicalWorkspaceSymbolSupport":true,"symbolKind":{"valueSet":[1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26]}},"workspaceEdit":{"resourceOperations":["rename","create","delete"]},"workspaceFolders":true}},"clientInfo":{"name":"Neovim","version":"0.9.5"},"initializationOptions":{},"processId":102865,"rootPath":"/home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight","rootUri":"file:///home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight","trace":"off","workspaceFolders":[{"name":"/home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight","uri":"file:///home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight"}]}}\n\nI[12:09:47.584] <-- initialize(1)\nI[12:09:47.585] --> reply:initialize(1) 0 ms\nV[12:09:47.585] >>> {"id":1,"jsonrpc":"2.0","result":{"capabilities":{"astProvider":true,"callHierarchyProvider":true,"clangdInlayHintsProvider":true,"codeActionProvider":{"codeActionKinds":["quickfix","refactor","info"]},"compilationDatabase":{"automaticReload":true},"completionProvider":{"resolveProvider":false,"triggerCharacters":[".","<",">",":","\\"","/","*"]},"declarationProvider":true,"definitionProvider":true,"documentFormattingProvider":true,"documentHighlightProvider":true,"documentLinkProvider":{"resolveProvider":false},"documentOnTypeFormattingProvider":{"firstTriggerCharacter":"\\n","moreTriggerCharacter":[]},"documentRangeFormattingProvider":true,"documentSymbolProvider":true,"executeCommandProvider":{"commands":["clangd.applyFix","clangd.applyTweak"]},"foldingRangeProvider":true,"hoverProvider":true,"implementationProvider":true,"inactiveRegionsProvider":true,"inlayHintProvider":true,"memoryUsageProvider":true,"referencesProvider":true,"renameProvider":{"prepareProvider":true},"selectionRangeProvider":true,"semanticTokensProvider":{"full":{"delta":true},"legend":{"tokenModifiers":["declaration","definition","deprecated","deduced","readonly","static","abstract","virtual","dependentName","defaultLibrary","usedAsMutableReference","usedAsMutablePointer","constructorOrDestructor","userDefined","functionScope","classScope","fileScope","globalScope"],"tokenTypes":["variable","variable","parameter","function","method","function","property","variable","class","interface","enum","enumMember","type","type","unknown","namespace","typeParameter","concept","type","macro","modifier","operator","bracket","label","comment"]},"range":false},"signatureHelpProvider":{"triggerCharacters":["(",")","{","}","<",">",","]},"standardTypeHierarchyProvider":true,"textDocumentSync":{"change":2,"openClose":true,"save":true},"typeDefinitionProvider":true,"typeHierarchyProvider":true,"workspaceSymbolProvider":true},"offsetEncoding":"utf-8","serverInfo":{"name":"clangd","version":"clangd version 17.0.6 linux x86_64-pc-linux-gnu"}}}\n\n'
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	"V[12:09:47.699] <<< {\"jsonrpc\":\"2.0\",\"method\":\"initialized\",\"params\":{}}\n\nI[12:09:47.699] <-- initialized\nV[12:09:47.699] <<< {\"jsonrpc\":\"2.0\",\"method\":\"textDocument/didOpen\",\"params\":{\"textDocument\":{\"languageId\":\"cpp\",\"text\":\"/*\\n * SPDX-License-Identifier: GPL-3.0-or-later\\n *\\n * Copyright (C) 2023 Jason Carrete\\n *\\n * This file is part of Flight Controller.\\n *\\n * Flight Controller is free software: you can redistribute it and/or modify\\n * it under the terms of the GNU General Public License as published by\\n * the Free Software Foundation, either version 3 of the License, or\\n * (at your option) any later version.\\n *\\n * This program is distributed in the hope that it will be useful,\\n * but WITHOUT ANY WARRANTY; without even the implied warranty of\\n * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the\\n * GNU General Public License for more details.\\n *\\n * You should have received a copy of the GNU General Public License\\n * along with this program.  If not, see <https://www.gnu.org/licenses/>.\\n */\\n\\n#include \\\"appinfo.h\\\"\\n#include \\\"version.h\\\"\\n\\n#include <iostream>\\n\\nnamespace ffd = freeflight_daemon;\\n\\nint main(int argc, char* argv[])\\n{\\n    std::cout << ffd::get_app_name() << ' ' << freeflight::get_version() << ' '\\n              << freeflight::get_name() << '\\\\n';\\n    return 0;\\n}\\n\",\"uri\":\"file:///home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/src/flightd/main.cpp\",\"version\":0}}}\n\nI[12:09:47.699] <-- textDocument/didOpen\nV[12:09:47.699] System include extraction: driver clang expanded to /usr/bin/clang\nV[12:09:47.699] System include extraction: not allowed driver /usr/bin/clang\n"
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	'V[12:09:47.700] <<< {"id":2,"jsonrpc":"2.0","method":"textDocument/semanticTokens/full","params":{"textDocument":{"uri":"file:///home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/src/flightd/main.cpp"}}}\n\n'
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	"I[12:09:47.700] <-- textDocument/semanticTokens/full(2)\n"
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	"V[12:09:47.700] config note at /home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/.clangd:1:0: Parsing config fragment\n"
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	"V[12:09:47.700] config note at /home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/.clangd:1:0: Parsed 1 fragments from file\nV[12:09:47.700] Config fragment: compiling /home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/.clangd:1 -> 0x0000724F50003730 (trusted=false)\n"
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	"I[12:09:47.701] --> textDocument/publishDiagnostics\n"
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	'V[12:09:47.701] >>> {"jsonrpc":"2.0","method":"textDocument/publishDiagnostics","params":{"diagnostics":[],"uri":"file:///home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/.clangd"}}\n\n'
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	"I[12:09:47.701] Loaded compilation database from /home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/compile_commands.json\n"
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	"V[12:09:47.701] Broadcasting compilation database from /home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight\n"
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	"V[12:09:47.701] System include extraction: not allowed driver /home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/recipe-sysroot-native/usr/bin/aarch64-poky-linux/aarch64-poky-linux-g++\n"
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	"I[12:09:47.701] ASTWorker building file /home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/src/flightd/main.cpp version 0 with command \n[/home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/freeflight-1.0+git]\n/home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/recipe-sysroot-native/usr/bin/aarch64-poky-linux/aarch64-poky-linux-g++ --target=aarch64-poky-linux --driver-mode=g++ --sysroot=/home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/recipe-sysroot -I/home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/src/flightd -I/home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/src/freeflight/public -mcpu=cortex-a57 -march=armv8-a+crc -mbranch-protection=standard -fstack-protector-strong -O2 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security --sysroot=/home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/recipe-sysroot -O2 -pipe -g -feliminate-unused-debug-types -fmacro-prefix-map=/home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight=/usr/src/debug/freeflight/1.0+git-r0 -fdebug-prefix-map=/home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight=/usr/src/debug/freeflight/1.0+git-r0 -fmacro-prefix-map=/home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/freeflight-1.0+git=/usr/src/debug/freeflight/1.0+git-r0 -fdebug-prefix-map=/home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/freeflight-1.0+git=/usr/src/debug/freeflight/1.0+git-r0 -fdebug-prefix-map=/home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/recipe-sysroot= -fmacro-prefix-map=/home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/recipe-sysroot= -fdebug-prefix-map=/home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/recipe-sysroot-native= -fvisibility-inlines-hidden -O2 -g -DNDEBUG -std=gnu++20 -o src/flightd/CMakeFiles/flightd.dir/main.cpp.o -c -resource-dir=/usr/lib/clang/17 -- /home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/src/flightd/main.cpp\n"
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	"I[12:09:47.702] Loaded compilation database from /home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/freeflight-1.0+git/compile_commands.json\n"
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	"I[12:09:47.702] --> window/workDoneProgress/create(0)\n"
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	'V[12:09:47.702] >>> {"id":0,"jsonrpc":"2.0","method":"window/workDoneProgress/create","params":{"token":"backgroundIndexProgress"}}\n\n'
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	"I[12:09:47.702] Enqueueing 1 commands for indexing\n"
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	"V[12:09:47.702] Driver produced command: cc1 -cc1 -triple aarch64-poky-linux -fsyntax-only -disable-free -clear-ast-before-backend -disable-llvm-verifier -discard-value-names -main-file-name main.cpp -mrelocation-model pic -pic-level 2 -pic-is-pie -mframe-pointer=non-leaf -fmath-errno -ffp-contract=on -fno-rounding-math -mconstructor-aliases -funwind-tables=2 -target-cpu cortex-a57 -target-feature +neon -target-feature +v8a -target-feature +crc -target-abi aapcs -msign-return-address=non-leaf -msign-return-address-key=a_key -mbranch-target-enforce -debug-info-kind=constructor -dwarf-version=5 -debugger-tuning=gdb -fcoverage-compilation-dir=/home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/freeflight-1.0+git -resource-dir /usr/lib/clang/17 -I /home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/src/flightd -I /home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/src/freeflight/public -D _FORTIFY_SOURCE=2 -D NDEBUG -isysroot /home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/recipe-sysroot -internal-isystem /usr/lib/clang/17/include -internal-isystem /home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/recipe-sysroot/usr/local/include -internal-externc-isystem /home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/recipe-sysroot/include -internal-externc-isystem /home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/recipe-sysroot/usr/include -fmacro-prefix-map=/home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight=/usr/src/debug/freeflight/1.0+git-r0 -fmacro-prefix-map=/home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/freeflight-1.0+git=/usr/src/debug/freeflight/1.0+git-r0 -fmacro-prefix-map=/home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/recipe-sysroot= -O2 -Wformat -Wformat-security -Werror=format-security -std=gnu++20 -fdeprecated-macro -fdebug-compilation-dir=/home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/freeflight-1.0+git -fdebug-prefix-map=/home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight=/usr/src/debug/freeflight/1.0+git-r0 -fdebug-prefix-map=/home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/freeflight-1.0+git=/usr/src/debug/freeflight/1.0+git-r0 -fdebug-prefix-map=/home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/recipe-sysroot= -fdebug-prefix-map=/home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/recipe-sysroot-native= -ferror-limit 19 -fvisibility-inlines-hidden -stack-protector 2 -fno-signed-char -fgnuc-version=4.2.1 -fno-implicit-modules -fcxx-exceptions -fexceptions -vectorize-loops -vectorize-slp -no-round-trip-args -target-feature -fmv -faddrsig -D__GCC_HAVE_DWARF2_CFI_ASM=1 -x c++ /home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/src/flightd/main.cpp\n"
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	'V[12:09:47.702] Building first preamble for /home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/src/flightd/main.cpp version 0\nV[12:09:47.702] BackgroundIndex: building version 1 after loading index from disk\nV[12:09:47.702] <<< {"id":0,"jsonrpc":"2.0","result":null}\n\nI[12:09:47.702] <-- reply(0)\nI[12:09:47.702] --> $/progress\nV[12:09:47.702] >>> {"jsonrpc":"2.0","method":"$/progress","params":{"token":"backgroundIndexProgress","value":{"kind":"begin","percentage":0,"title":"indexing"}}}\n\n'
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	'V[12:09:47.702] BackgroundIndex: serving version 1 (50980 bytes)\nI[12:09:47.702] --> $/progress\nV[12:09:47.703] >>> {"jsonrpc":"2.0","method":"$/progress","params":{"token":"backgroundIndexProgress","value":{"kind":"report","message":"0/1","percentage":0}}}\n\nI[12:09:47.703] --> $/progress\n'
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	'V[12:09:47.703] >>> {"jsonrpc":"2.0","method":"$/progress","params":{"token":"backgroundIndexProgress","value":{"kind":"report","message":"0/1","percentage":0}}}\n\nI[12:09:47.703] --> $/progress\n'
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	'V[12:09:47.703] >>> {"jsonrpc":"2.0","method":"$/progress","params":{"token":"backgroundIndexProgress","value":{"kind":"end"}}}\n\n'
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	"I[12:09:47.716] Built preamble of size 529320 for file /home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/src/flightd/main.cpp version 0 in 0.01 seconds\n"
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	'I[12:09:47.717] --> workspace/semanticTokens/refresh(1)\nV[12:09:47.717] >>> {"id":1,"jsonrpc":"2.0","method":"workspace/semanticTokens/refresh","params":null}\n\n'
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	'V[12:09:47.717] <<< {"jsonrpc":"2.0","method":"$/cancelRequest","params":{"id":2}}\n\nI[12:09:47.717] <-- $/cancelRequest\nV[12:09:47.717] indexed preamble AST for /home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/src/flightd/main.cpp version 0:\n  symbol slab: 5 symbols, 5376 bytes\n  ref slab: 0 symbols, 0 refs, 128 bytes\n  relations slab: 0 relations, 24 bytes\nV[12:09:47.717] <<< {"id":3,"jsonrpc":"2.0","method":"textDocument/semanticTokens/full","params":{"textDocument":{"uri":"file:///home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/src/flightd/main.cpp"}}}\n\nI[12:09:47.717] <-- textDocument/semanticTokens/full(3)\n'
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	'V[12:09:47.717] <<< {"id":1,"jsonrpc":"2.0","result":null}\n\nI[12:09:47.717] <-- reply(1)\nV[12:09:47.717] Build dynamic index for header symbols with estimated memory usage of 22004 bytes\n'
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	'V[12:09:47.724] Trying to fix unresolved name "cout" in scopes: [std::]\n'
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	"V[12:09:47.724] Dex query tree: false\nV[12:09:47.724] Dex query tree: false\n"
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	"E[12:09:47.725] IncludeCleaner: Failed to get an entry for resolved path : No such file or directory\n"
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	"V[12:09:47.726] indexed file AST for /home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/src/flightd/main.cpp version 0:\n  symbol slab: 2 symbols, 4680 bytes\n  ref slab: 2 symbols, 2 refs, 4272 bytes\n  relations slab: 0 relations, 24 bytes\nV[12:09:47.726] Build dynamic index for main-file symbols with estimated memory usage of 12040 bytes\n"
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	"I[12:09:47.726] --> textDocument/publishDiagnostics\n"
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	"V[12:09:47.726] >>> {\"jsonrpc\":\"2.0\",\"method\":\"textDocument/publishDiagnostics\",\"params\":{\"diagnostics\":[{\"code\":\"pp_file_not_found\",\"message\":\"'iostream' file not found\",\"range\":{\"end\":{\"character\":19,\"line\":24},\"start\":{\"character\":9,\"line\":24}},\"relatedInformation\":[],\"severity\":1,\"source\":\"clang\"},{\"code\":\"undeclared_var_use\",\"message\":\"Use of undeclared identifier 'std'\",\"range\":{\"end\":{\"character\":7,\"line\":30},\"start\":{\"character\":4,\"line\":30}},\"relatedInformation\":[],\"severity\":1,\"source\":\"clang\"},{\"code\":\"misc-unused-alias-decls\",\"codeDescription\":{\"href\":\"https://clang.llvm.org/extra/clang-tidy/checks/misc/unused-alias-decls.html\"},\"message\":\"Namespace alias decl 'ffd' is unused (fix available)\",\"range\":{\"end\":{\"character\":0,\"line\":27},\"start\":{\"character\":0,\"line\":26}},\"relatedInformation\":[],\"severity\":2,\"source\":\"clang-tidy\",\"tags\":[1]}],\"uri\":\"file:///home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/src/flightd/main.cpp\",\"version\":0}}\n\nI[12:09:47.726] --> reply:textDocument/semanticTokens/full(2) 26 ms, error: Task was cancelled.\nV[12:09:47.726] >>> {\"error\":{\"code\":-32800,\"message\":\"Request cancelled\"},\"id\":2,\"jsonrpc\":\"2.0\"}\n\nV[12:09:47.726] ASTWorker running SemanticHighlights on version 0 of /home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/src/flightd/main.cpp\nI[12:09:47.726] --> reply:textDocument/semanticTokens/full(3) 8 ms\nV[12:09:47.726] >>> {\"id\":3,\"jsonrpc\":\"2.0\",\"result\":{\"data\":[26,10,3,15,65537,0,6,17,15,131072,2,4,4,3,131075,0,9,4,2,16387,0,12,4,2,16387],\"resultId\":\"1\"}}\n\n"

System information
Output of clangd --version:
clangd version 17.0.6
Features: linux
Platform: x86_64-pc-linux-gnu
Editor/LSP plugin:
Neovim/nvim-lspconfig
Operating system:
Arch Linux
Kernel version: 6.7.9

Duplicate of #1605


Can the README be made clearer that there are no plans to update this library to the next SDK version?

Hi, I recently came across this comment by chance:
https://github.com/okta/okta-sdk-python/issues/340#issuecomment-1468520171

currently, we have migrated our .NET, Java, and Golang SDK's to OASv3. As I mentioned, we do not have current plans to upgrade Python to this version.

Could this be made clearer in the README? I spent some time implementing this library but if it wont be upgraded I'll use another SDK (Or generate it myself). Having this information in the README might help prevent others from going down the same path.

It's been several months now since this issue was opened and even longer since the initial comment -- If Okta is not planning on supporting this library or Python with first party support anymore I think that's probably extremely critical to note that clearly so that the community can plan to take over support where Okta is no longer interested, especially as this project is included in a lot of OSS projects.

https://github.com/okta/okta-sdk-python/issues/375


Use type="doi" for citations

Some citations don't have a DOI, like this one, is it possible to mix citation types?
We could use DOI when it's present with a bibtex fallback. I assume this is allowed since they are different XML nodes.

Perfect! I'll create an issue over in q2galaxy to render that when possible.

Superseded by https://github.com/qiime2/q2galaxy/issues/38

Fixed in latest release!


merge package template from Kronos-Tools/npm-package-template

.npmignore

chore(npm)

Changes Unknown when pulling 2bbcdb5b0989e77ddb5a7a34ca37bf9d9ae60b3b on template-sync-1 into ** on master**.

Codecov Report

Merging #168 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #168   +/-   ##
=======================================
  Coverage   86.59%   86.59%
=======================================
  Files           1        1
  Lines         194      194
=======================================
  Hits          168      168
  Misses         26       26

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 55b4438...2bbcdb5. Read the comment docs.


Adds port and protocol command line options

This PR supports port and protocol command line options to easily reuse large test suites without having to modify all the yaml files.
@csanders-git @zmallen

hi there!
Thanks for the commit. Ill be looking into this today/tomorrow. Dont worry about travis failing -- those tests are fixed in a separate P/R

@zmallen thanks! Looking forward to your review/feedback.

this is blocked by #84 which @csanders-git should be merging tonight (nudge nudge). I'll ping on here for you to rebase with master once #84 is merged then tests should pass.

hi @bclodius can you rebase with master? ill merge this in and do a pip release tonight

@zmallen due to a mistake on my side with git history; I'll resubmit this on another PR.

ACK, thx


Cannot access output parameters in non-exit hook

Checklist

[x] Double-checked my configuration.
[x] Tested using the latest version.
[x] Used the Emissary executor.

Summary
When trying to access output parameters in hooks other than exit I get templates.main.steps failed to resolve {{steps.step-1.outputs.parameters.result}}
Argo 3.3.6
Diagnostics
This is the example from https://github.com/argoproj/argo-workflows/blob/df37649251f5791c40802defd923dd735924eb3a/examples/exit-handler-with-param.yaml with exit replaced with foo
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: exit-handler-with-param-
  labels:
    workflows.argoproj.io/test: "true"
  annotations:
    workflows.argoproj.io/description: |
      onExitTemplate enables workflow to pass the arguments (parameters/Artifacts) to exit handler template.
    workflows.argoproj.io/version: '>= 3.1.0'
spec:
  entrypoint: main
  templates:
    - name: main
      steps:
        - - name: step-1
            template: output
            hooks:
              foo:
                template: exit
                arguments:
                  parameters:
                    - name: message
                      value: "{{steps.step-1.outputs.parameters.result}}"

    - name: output
      container:
        image: python:alpine3.6
        command: [sh, -c]
        args: ["echo -n hello world > /tmp/hello_world.txt"]
      outputs:
        parameters:
          - name: result
            valueFrom:
              default: "Foobar"   # Default value to use if retrieving valueFrom fails. If not provided workflow will fail instead
              path: /tmp/hello_world.txt

    - name: exit
      inputs:
        parameters:
          - name: message
      script:
        image: python:alpine3.6
        command: [ python ]
        source: |
          print("{{inputs.parameters.message}}")

level=info msg="Processing workflow" namespace=default workflow=exit-handler-with-param-jrg25
level=warning msg="Non-transient error: templates.main.steps failed to resolve {{steps.step-1.outputs.parameters.result}}"
level=info msg="Updated phase  -> Failed" namespace=default workflow=exit-handler-with-param-jrg25
level=info msg="Updated message  -> invalid spec: templates.main.steps failed to resolve {{steps.step-1.outputs.parameters.result}}" namespace=default workflow=exit-handler-with-param-jrg25
level=info msg="Marking workflow completed" namespace=default workflow=exit-handler-with-param-jrg25
level=error msg="Unable to set ExecWorkflow" error="templates.main.steps failed to resolve {{steps.step-1.outputs.parameters.result}}" namespace=default workflow=exit-handler-with-param-jrg25
level=info msg="Checking daemoned children of " namespace=default workflow=exit-handler-with-param-jrg25
level=info msg="cleaning up pod" action=deletePod key=default/exit-handler-with-param-jrg25-1340600742-agent/deletePod

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

@sarabala1979 Could you take a look?

@sarabala1979 Who's working on this?

Still experiencing this issue.

@sarabala1979 @terrytangyuan It would be really useful to have this fixed.
My use case is having the exit hook to access and work with STDOUT of each task in dag workflow within a sensor (v3.3.9). And, most probably, this issue is the blocker for me. I'm using the same approach, but in my case the value is not interpolated correctly, so
print("{{inputs.parameters.message}}") prints exactly this sting {{steps.step-1.outputs.parameters.result}}, not it's value.
Maybe there is some obvious approach that I'm missing to easily access STDOUT of each task from the exit hook?
Thank you.

Could you try the most recent release and see if the problem persists?

In my case the issue still persist with releases 3.3.9 and v3.4.0-rc2

@sarabala1979 Could this be fixed by one of your recent commits?

Comment to prevent closing

@Tolsto @yavulan can you try on v3.4.2?

Using the release 3.4.2 (which was released yesterday), the issue reproducing code produces an error - Failed: invalid spec: templates.main.steps failed to resolve {{steps.step-1.outputs.parameters.result}}. If you change hook name from foo to success - the error message is the same. But it works as expected with exit hook.
Though, we have an improvement - previously when you change {{steps.step-1.outputs.parameters.result}} to {{steps.step-1.status}} - it printed {{steps.step-1.status}}. Now it prints Succeeded. But if you use {{steps.step-1.exitCode}} - it prints string {{steps.step-1.exitCode}}, and the same problem is with {{steps.step-1.outputs.result}}.

This does not work because the docs say it should not work.
What does work (counter to the docs perhaps) is
        - - name: step-1
            template: output
        - - name: step-2
            template: output
            hooks:
              foo:
                template: exit
                expression: steps["step-1"].status == "Succeeded"
                arguments:
                  parameters:
                    - name: message
                      value: "{{steps.step-1.outputs.parameters.result}}"

Because the output of step 1 is available when step 2 runs.
What also doesn't work is the lack of expression in the foo hook, causing other issues. #10910 covers this.
In theory it should be possible to make step-1 get it's own outputs in the Succeeded or Failed status events, but the same is achievable in an exit hook already, so I'm suggesting just documenting this.


[ko] Translate tasks/debug-application-cluster/debug-cluster.md

This is a Feature Request
Translate [/content/en/docs/tasks/debug-application-cluster/debug-cluster.md] in Korean
What would you like to be added
Translate [/content/ko/docs/tasks/debug-application-cluster/debug-cluster.md] in Korean
Why is this needed
This file is not translated yet.
Comments
Page to translate : https://kubernetes.io/docs/tasks/debug-application-cluster/debug-cluster/
/language ko
/assign

/triage accepted

Resolved by

#31155
#31637

/close


Update Swift Package Manager to v4.2

Swift 5 no longer supports the Swift 3 Package.swift tools-version, which means Xcode 10.2 doesn't either. This updates Package.swift to the latest, version 4.2.

Oh, looks like this is already done in #403


added sentencepiece

hello Karpathy, This is great work.
I recently working llama-2 model thought could be cool to add sentencepiece model to here too.

we'll add it, but from scratch. and then use sp for unit tests.

I see, thanks and looking forward to contribute in the future.


refactor: move from io/ioutil to io and os package

The io/ioutil package has been deprecated in Go 1.16 (See https://golang.org/doc/go1.16#ioutil). This PR replaces the existing io/ioutil functions with their new definitions in io and os packages.

Codecov Report

Merging #1298 (b1f6c32) into master (b25a9e5) will decrease coverage by 0.10%.
The diff coverage is 40.00%.

@@            Coverage Diff             @@
##           master    #1298      +/-   ##
==========================================
- Coverage   44.54%   44.43%   -0.11%
==========================================
  Files         485      476       -9
  Lines       29534    29435      -99
==========================================
- Hits        13156    13080      -76
+ Misses      14967    14943      -24
- Partials     1411     1412       +1

Impacted Files
Coverage Δ

infra/conf/geodata/memconservative/cache.go
0.00% <0.00%> (ø)

main/confloader/external/external.go
6.97% <0.00%> (ø)

app/dns/nameserver_doh.go
68.05% <50.00%> (ø)

common/common.go
24.69% <50.00%> (ø)

common/drain/drainer.go
65.51% <100.00%> (ø)

testing/scenarios/common.go
70.68% <100.00%> (-3.45%)
:arrow_down:

testing/servers/tcp/tcp.go
81.81% <0.00%> (-5.46%)
:arrow_down:

transport/internet/udp/hub.go
73.61% <0.00%> (-4.17%)
:arrow_down:

transport/internet/system_listener.go
50.00% <0.00%> (-4.00%)
:arrow_down:

... and 16 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 b25a9e5...b1f6c32. Read the comment docs.

Thanks for your work.


[Feature]: SSH Verbosity Levels

Added the ability to specify an optional SSH verbosity level in the shipit configuration file.
{
    ...

    // 0 (none), 1 (-v), 2 (-vv), 3 (-vvv)
    // Defaults to `none`
    verboseSSHLevel: 1
}

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@a764fff). Click here to learn what that means.
The diff coverage is 14.28%.

@@            Coverage Diff            @@
##             master     #191   +/-   ##
=========================================
  Coverage          ?   80.96%
=========================================
  Files             ?       26
  Lines             ?      562
  Branches          ?       91
=========================================
  Hits              ?      455
  Misses            ?       84
  Partials          ?       23

Impacted Files
Coverage Δ

packages/shipit-cli/src/Shipit.js
57.33% <ø> (ø)

packages/ssh-pool/src/Connection.js
97.43% <ø> (ø)

packages/ssh-pool/src/commands/ssh.js
48.27% <14.28%> (ø)

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 a764fff...7e2827e. Read the comment docs.

Thanks for your PR, just a few minor changes please.

@mitchtreece good! A last thing, can you please update all readme to reflect the change?

@neoziro You got it. Updated! 🎉

I think you missed this one https://github.com/shipitjs/shipit/blob/master/packages/ssh-pool/README.md

@neoziro Oops. Should be good now!

Thanks!


Correctly persist NonRDFSource description triples

JIRA Ticket: https://jira.duraspace.org/browse/FCREPO-3015
I got the idea for this fix from https://github.com/fcrepo4/fcrepo4/pull/1491
What does this Pull Request do?
Tries to add/remove the triples for binaries on the description (was using the actual binary).
How should this be tested?
See steps in associated ticket.
Create a binary, update the triples on the /fcr:metadata endpoint.
Basically you can add triples but can't seemingly delete them. In practice I found when GET then PUT altered triples they were entirely ignored.
Additional Notes:
Example:

Does this change require documentation to be updated? no
Does this change add any new dependencies? no
Does this change require any other modifications to be made to the repository (ie. Regeneration activity, etc.)? no
Could this change impact execution of existing code? no

Interested parties
@fcrepo4/committers @dannylamb

@whikloj :  shouldn't you be targeting 5.1.0-RC branch rather than master?

@dbernstein problem also exists in master, I can open a second PR against the RC branch once its approved.

@whikloj :  ah - okay.  I'll do the reverse on https://github.com/fcrepo4/fcrepo4/pull/1531 - ie once merged I"ll create a PR on master.


P2P KYC - Ask user to provide full SSN when LexisNexis cannot

Details
Ask for full 9 digit SSN when LexisNexis cannot find the first five after the user gives his last 4.
Fixed Issues
Part of https://github.com/Expensify/Expensify/issues/193504
Tests
Tested with the secure PR (but should be merged before the secure one) and these app fixes: https://github.com/Expensify/App/pull/7782 and https://github.com/Expensify/App/pull/7812
Try to transfer your wallet balance.
Fill up the Additional Details Step with random 4 digit SSN.
Submit the form.
Make sure you get an error, asking you to enter your full SSN.
Enter your full SSN and submit. You should then get another error (not SSN related).
QA Steps
None, as it needs the secure PR.
Tested On

[x] Web
[ ] Mobile Web
[ ] Desktop
[ ] iOS
[ ] Android

Screenshots
Web

Bump @ctkochan22 and @marcaaron

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by @nkuoch in version: 1.1.41-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
failure ❌

🚀 Deployed to staging by @nkuoch in version: 1.1.41-0 🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
failure ❌

🚀 Deployed to production by @francoisl in version: 1.1.41-6 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Cmdlets over cron and task scheduler

This came out of today's Community Call.  Summary of the discussion is that:

cron and task scheduler are fundamentally different in syntax and semantics that an abstraction would be highly complex and probably still incomplete
makes more sense to focus on the top scenarios and build a new set of cmdlets to enable scheduling cross-platform

So this issue is to brainstorm on requirements and scenarios before we move towards authoring a RFC.

One possible guiding principle is that since cron is likely a subset of schedule tasks, that we start with full cron - but remove any agreed esoterics.

@DarwinJS it would be great if we had some specific examples of some of the capabilities required from existing use of cron and existing use of task scheduler

On macOS will use launchd or cron. The later has been deprecated since 10.11 if recall. It is still there but in a disabled state and no files exist for it by default.

@SteveL-MSFT - here are some examples of how I do use scheduling.  I can't say that they are the uber example - but they are ones that would benefit from CMDLet parity.
Also the main focus in the below is a) server b) automation - as such it exhibits using the scheduler for things like "getting into SYSTEM account context (windows)" and "scheduling something for shutdown or startup" and "scheduling something to run only once"
This article directly talks about the overcomplexity of the current CMDLets and why schtasks.exe is better.  It shows the comparison of the code complexity:
https://cloudywindows.io/post/continue-your-automation-to-run-once-after-restarting-a-headless-windows-system
Notice it takes advantage of a super easy way to get admin without a password (assuming you run the schedule command with admin) = "/ru SYSTEM" and the ability to run on startup "/sc ONSTART"
This code does "self-unscheduling".
This brings up a positive distinction about Windows well developed scheduler over linux - it has these sort of meta-functions that a) aren't strictly the typical domain of a pure scheduler, b) that are some of it's most useful shortcuts.  Stuff like ONSTART and SYSTEM account without admin.  If this concept could be extended to linux - it would make the PowerShell version of scheduling legions better than the native.  I know it is a big ask - but I've always loved the way PowerShell surfaces super-needed, super-simple high level functionality like this.
These two scripts are meant to have identical functionality on Windows and Linux.  They use a repeating task to: *) run in parallel to remaining automation, *) persist across reboots that are so common during initial automation:
In Windows I used schtasks.exe to avoid the complexity and limited availability of scheduling cmdlets:
https://github.com/DarwinJS/DevOpsAutomationCode/blob/master/InitializeDisksWithFIO.ps1#L274
https://github.com/DarwinJS/DevOpsAutomationCode/blob/master/InitializeDisksWithFIO.sh#L343
This code does "self-unscheduling".
Here's an example of running a cleanup.  The CMDLets were used because I only needed one.  Surprising running elevated didn't take more cmdlets.
Running with root / system w/ no password would be a feature to be on a simple cmdlet because it is used so frequently in server automation
Here is a use case of using scheduler to do something on the next start (rather than fussing with each systems particular "startup automation" techniques:
https://github.com/DarwinJS/ChocoPackages/blob/master/PowerShell/v5.1/tools/ChocolateyInstall.ps1#L168
Running only once and running on events like startup or shutdown would be very handy as those are frequent too - however I understand they aren't implicitly a feature in both schedulers.
Self-unscheduling upon completion - is another thing I use time and again for system automation.
I have resorted to the scheduler on Windows for so many more scenarios that simply "setup a repeating scheduled job" - that I guess it would seem a crime to roll back new functionality to only be that.  I think that newly presented functionality might want to acknowledge that on a bare bones Windows or Linux system, the scheduler has other identifable defacto "meta uses" patterns.
Multi-platform functionality that would be useful to my work (ignoring how "hard" they might be):

way to gain SYSTEM / root account context (without knowing implementation details)
easy way to setup code to run on system wide events like startup, shutdown (without knowing implementation details)
way to self-remove a task upon successful completion (without knowing implementation details)
simple way to re-run, re-run, re-run until the job is done.  Maybe scheduler function takes a flag file name to know when it is done.  Almost always combined with self-remove.

I am already using PowerShell jobs on both platforms to run in parallel - but jobs are not reboot nor session resilient.
Also - sometimes implementations like the above (scheduler "meta-functions") get labeled esoteric.  My counter to that is "If we can guess that these things would receive wide adoption upon recognition by potential users - then they are only esoteric in a short term sense - the sense also described by 'innovating something that customers can't articulate before they see it - but wholehearted recognize when they do'"   In other words "we've never heard anyone do that or ask for that before" is not an exclusive vote for "esoteric and unneeded" it could just as easily be "unarticulated and unrecognized, yet very needed"
To me, the entire story of PowerShell is actually one that carries the same sense - I'm interested in the continuance of that spirit rather than devolving to "minimum common functionality" just because doing multiplatform is hard.

Added to the Cmdlets Working Group for review.

The Cmdlet Working Group has discussed this issue. The PSScheduledJob module is not supported in PowerShell 7 because .NET Core no longer supports System.Runtime.Serialization.NetDataContractSerializer. This is the primary reason this is marked as won't fix. The group also believes that while the Windows task scheduler and Unix cron,  do the same thing conceptually are architecturally different enough that building a cmdlet set to abstract the process over both is not practical. It would be better to have different sets of cmdlets.
In Windows, PowerShell 7 supports the ScheduledTasks module. Users could create PowerShell scheduled tasks with these cmdlets today. The Working Group is recommending that any solution to creating PowerShell scheduled jobs be left to the community and published to the PowerShell Gallery.


CASSANDRA-18508 - Sensitive JMX SSL configuration options can be easily exposed

This PR addresses CASSANDRA-18508

@JeetKunDoug Will close this PR without merge since the other parallel PR is reviewed already by Stefan and CI build is green out of it. Sorry for keeping two PRs open. Didn't realize that I accidentally opened this PR prior to opening PRs on myfork to get your initial reviews. Ref: https://github.com/apache/cassandra/pull/3638


ValueError: Error initialising UART

I have some error in IoT2000 model IoT2040 UART communication using python MRAA library,
please anyone help me to resolve this error....
root@iot2000:~# sudo python recv.py
Traceback (most recent call last):
  File "recv.py", line 5, in <module>
    u = mraa.Uart(0)
  File "/usr/lib/python2.7/site-packages/mraa.py", line 1521, in __init__
    this = _mraa.new_Uart(*args)
ValueError: Error initialising UART
root@iot2000:~#

@vjvicky007 please post the contents of the syslog (/var/log/syslog or journalctl -x output, depending on what Siemens has there these days), there should be some additional information in there. Right now it looks like some UART-related error, which for Quark should not theoretically happen as it's been around for quite a while.

Closing for no reply - feel free to respond if you still need assistance.


Add python_requires and 3.7 classifier

Is Python 3.5 supported? It's no longer tested on Travis CI.

You are correct, good catch.


README postgresql_server_listen example/usage

The current example in the usage of the variable postgresql_server_listen:

use '*' for all

If you try this exact value, PostgreSQL fails to start.
Sep 15 23:24:11 pg-int-testing.openmicroscopy.org postmaster[18973]: LOG:  syntax error in file "/var/lib/pgsql/9.6/data/postgresql.conf" line 644, near token "*"
Sep 15 23:24:11 pg-int-testing.openmicroscopy.org postmaster[18973]: FATAL:  configuration file "/var/lib/pgsql/9.6/data/postgresql.conf" contains errors

It needs to be quoted to work, which is in fact the syntax used below in the Example Playbook section, cf https://github.com/openmicroscopy/ansible-role-postgresql/blame/master/README.md#L62
It's correct that you want to end up with '*' in the postgresql.conf file, but since that's not the Ansible syntax to achieve it, perhaps it shouldn't be written that way in the variable usage?

Makes sense to me. Since it's just in the README, I'd propose we merge without tagging. Guess there is the question of whether or not there should be a related test.
cc: @manics

@openmicroscopy/devops This is documentation style issue. Up to now I've used the literal value in README text (so e.g. * would mean a literal asterisk, '*' means a literal single-quoted asterisk), with the quoting requirements of the format (json, long-yaml, single-line-yaml) left to the user. If everyone agrees we could switch to the policy that in-line values in READMEs should always be in a form that can be copy-and-pasted into a long-form-yaml file.

Not sure then. For me the verb "use" implies that's what should be "used", rather than that's what we'd like to end up with in the resulting config file. Could just be me confused by that then.
If it's in line with all the rest of our Ansible variable documentation then I'll just need to learn that, and I  wouldn't expect us to change every role just for me.

If we have unquoted everywhere else, I'd say let's go for:

unquoted in text
"quoted" (since necessary) in the examples

If after trying to adjust to it, @kennethgillen, you still think we need quoted everywhere, let's do that in one go everywhere.

rather than that's what we'd like to end up with in the resulting config file.

It's what we'd like to end up with after parsing the yaml (or json) file, the purpose of the variable is irrelevant.

Re-opened and reverted in order to at least fix the missing space.


Add thud to LAYERSERIES_COMPAT

Hi,
This is required to build with latest poky master.
Thanks

@shiftee The maintainer doesn't use Github PRs. Could you instead submit this to the mailing list as described in the readme? Thank you.
Submitting patches
------------------

You can submit your patches (or post questions reagarding
this layer to the swupdate Mailing List:

<EMAIL_ADDRESS>
When creating patches, please use something like:

    git format-patch -s --subject-prefix='meta-swupdate][PATCH' <revision range>

Please use 'git send-email' to send the generated patches to the ML
to bypass changes from your mailer.


Silent failure on forgetting that strings in JS are immutable

Describe the bug
A clear and concise description of what the bug is.
JS interpreter crashes on attempting to modify string. It would be more helpful to show error message in the console.
To Reproduce
Steps to reproduce the behavior:

Go to for example https://learn.freecodecamp.org/javascript-algorithms-and-data-structures/basic-algorithm-scripting/reverse-a-string
In code area replace code with

let test = "ABFC";
console.log("before");
test[0]="A";
console.log("after");

Expected behavior
A clear and concise description of what you expected to happen.
I would expect something like "attempted to modify immutable string object" in the output of console, rather than a silent failure
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Lubuntu 16.04
Browser Firefox 63.0.3 (64-bit)

Additional context
Add any other context about the problem here.

Hi @matkoniecz,
Thank you for opening this issue. The ECMAScript specification doesnt throw error if you try to mutate primitive values, therefore none of the browsers (implementer of the the spec) throws an error if you try to mutate the String or any other primitive type.
If you try the following code in the browser:
let test = "ABFC";
test[0] = "E";

You'll see that the last assignment returns "E", giving the impression that string has been mutated whereas in reality it hasnt been mutated.
We're simply sticking to the language spec, which IMO is completely fine, because if we didnt campers will get confused with different behavior.
Hope this resolves your issue. Closing this.
Feel free to reopen if you think this issue hasnt been resolved.
Happy coding.

Feel free to reopen

Note that on GitHub people are unable to reopen issues closed by maintainers :)

The ECMAScript specification doesnt throw error

Is it explicitly requiring a silent failure?
I still think that it would be better to give error message noting that this type of error would cause program to silently crash, but I understand why it was fine this way.

Maybe the proper solution would be to add strict mode to the initial code?
It is a good practise, especially for people learning as it seems to give much better error reporting without loss of any reasonable functionality.

@matkoniecz I suppose its possible to add use strict to the challenges, we do have strict mode in some challenges. Maybe others can chime on this.
Reopening the issue.

If no-one protests I will start making PRs adding strict mode.

I'd suggest not doing that until a proper discussion happens. This probably was suggested before too and if they didnt add that, then there might a reason.
Lets wait for the core members.
cc @Bouncey @raisedadead

Sorry, I though I had replied already.
'use strict is not required to throw an error here. We run all the code through babel and babel does this for us. The results of which can be seen in the output window under the editor

If we need to make this clearer some how, I would gladly listen to suggestions.

Using that code in my browser console
FireFox:
"use strict";
let test = "ABFC";
console.log("before");
test[0]="A";
console.log("after");
// TypeError: 0 is read-only[Learn More]

Chrome:
"use strict";
let test = "ABFC";
console.log("before");
test[0]="A";
console.log("after");

// before
// Uncaught TypeError: Cannot assign to read only property '0' of string 'ABFC' at <anonymous>:4:8

The TypeErrors are what you are seeing in the output panel below the editor. All we do is copy the error message and display it in the output window.
Is there anywhere else we can display this or increase the visibility in some way that makes sense from a UI/UX standpoint?

And adding "use strict"; is not changing anything from what I see in my testing

This is because it is already there, in the background, as we run all code through babel in the browser to enable the use of the latest language features.

The TypeErrors are what you are seeing in the output panel below the editor.

Only on clicking "Run the tests" button, rerunning code after edit is not displaying them.

Is there anywhere else we can display this or increase the visibility in some way that makes sense from a UI/UX standpoint?

Show this type of error also after user edited text in code text area.

Looks like some recent modifications to the console output now display an error in these cases...

So it's probably safe to close this.


Make chop indicator on-screen position configurable

As of TreeChop 0.14.0, the indicator's position can be changed in treechop-client.toml

Added in 0.14.0


Unusual RAM usage

Hi, I ran into the same issue as #1931 but even with latest version ,the problem still happens in my Netlify CI.
The project is my personal website, code here: https://github.com/prazdevs/praz.dev
And the CI that fails is here: https://app.netlify.com/sites/prazdev/deploys/6387dc5a3bf8ac70cbda6fb0
By building locally on my machine, i get unusual RAM usage of the Node runtime, up to 2.7GB, which is beyond netlify CI limit, probably what causes it to fail.
This is using the nuxt plugin.

Duplicated of https://github.com/unocss/unocss/issues/1931. It's fixed in #1935 but these are not released yet.
For the time being you better stick with v0.46.5.

mb, thought it was already released 😅  thanks for the fast answer


Need to update you Adapter as per new changes of FB sdk as it's throwing error.

Please update this adapter to latest version of Facebook Audience Network library. As your adapter is not supporting to present apps. Thanks for your library it is awesome !

is it working for you in span grid view after updating facebook library..?

I have tried numbers of time to update facebook library but it didn't work.
very initial stage its throwing error.

I am also facing this error.

I have the same problem. help!


fix: use widget from pymmcore-widgets main branch

@ianhi linked to https://github.com/pymmcore-plus/napari-micromanager/pull/264#issuecomment-1653752822
This PR updates napari-micromanager using the pymmcore-widgets in main branch.

This raises the question of the dependency structure of the testing between these two repos. Would it maybe make more sense to do the following?

In regular CI use the main branch of pymmcore-widgets/pymmcore-plus
In testing prior to a release use the currently released versions

It seems that that would allow smooth development, but still make sure released versions are compatible.
@tlambert03 @fdrgsp

the structure I prefer is for upstream libraries to test against the main branch of their dependents with -W ignore

useq tests main branch of pymmcore-plus
pymmcore-plus tests main branch of widgets
widgets tests main branch of napari-micromanager

While the downstream libraries test against the current release (NOT against the main branch).
Once the tests are in place, it's the upstream libraries responsibility to emit warnings rather than breakages, and let the downstream libraries test fail with a warning (rather than an actual error).  This mimics the case that would happen with a downstream third party library we're not testing.
I know you've just jumped into an odd state, but we're actively working on this and you just caught us at a funny time.

Hooray, seeing some green lights here


[oidc] fix reporting to backend when using OIDC [THREESCALE-1080]

Fixes THREESCALE-1080
Simplified backport of https://github.com/3scale/apicast/pull/774 for 3.2 release.

@mikz what do you mean by 'simplified' backport?

@davidor it does not port the whole post_action refactoring and passing context. It just properly updates 'self.credentials'. I consider this a bit dirty, but simpler approach. But appropriate in this situation of making minimal changes in patch releases.
Will update the PR description.


cannot setup CARET on Ubuntu 20.04

I have set up all the dependencies for caret but got the following error when building.
It seems the ros galactic rmw has deleted the "event_callback_type.h".
hydrapc@hydrapc:~/projects/ros2_caret_ws$ colcon build --symlink-install --cmake-args -DCMAKE_BUILD_TYPE=Release
[0.442s] WARNING:colcon.colcon_core.package_selection:Some selected packages are already built in one or more underlay workspaces:
	'rclcpp_components' is in: /opt/ros/galactic
	'rcl' is in: /opt/ros/galactic
	'rcl_action' is in: /opt/ros/galactic
	'rclcpp_lifecycle' is in: /opt/ros/galactic
	'rcl_yaml_param_parser' is in: /opt/ros/galactic
	'rcl_lifecycle' is in: /opt/ros/galactic
	'rclcpp_action' is in: /opt/ros/galactic
	'rclcpp' is in: /opt/ros/galactic
If a package in a merged underlay workspace is overridden and it installs headers, then all packages in the overlay must sort their include directories by workspace order. Failure to do so may result in build failures or undefined behavior at run time.
If the overridden package is used by another package in any underlay, then the overriding package in the overlay must be API and ABI compatible or undefined behavior at run time may occur.

If you understand the risks and want to override a package anyways, add the following to the command line:
	--allow-overriding rcl rcl_action rcl_lifecycle rcl_yaml_param_parser rclcpp rclcpp_action rclcpp_components rclcpp_lifecycle

This may be promoted to an error in a future release of colcon-override-check.
 Use build and pip and other standards-based tools.
  warnings.warn(
/home/hydrapc/.local/lib/python3.8/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
  warnings.warn(
/home/hydrapc/.local/lib/python3.8/site-packages/pkg_resources/__init__.py:123: PkgResourcesDeprecationWarning: 0.1.36ubuntu1 is an invalid version and will not be supported in a future release
  warnings.warn(
/home/hydrapc/.local/lib/python3.8/site-packages/pkg_resources/__init__.py:123: PkgResourcesDeprecationWarning: 0.23ubuntu1 is an invalid version and will not be supported in a future release
  warnings.warn(
---
Finished <<< tracetools_trace [1.34s]
--- stderr: tracetools_read
/home/hydrapc/.local/lib/python3.8/site-packages/setuptools/command/easy_install.py:144: EasyInstallDeprecationWarning: easy_install command is deprecated. Use build and pip and other standards-based tools.
  warnings.warn(
/home/hydrapc/.local/lib/python3.8/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
  warnings.warn(
/home/hydrapc/.local/lib/python3.8/site-packages/pkg_resources/__init__.py:123: PkgResourcesDeprecationWarning: 0.1.36ubuntu1 is an invalid version and will not be supported in a future release
  warnings.warn(
/home/hydrapc/.local/lib/python3.8/site-packages/pkg_resources/__init__.py:123: PkgResourcesDeprecationWarning: 0.23ubuntu1 is an invalid version and will not be supported in a future release
  warnings.warn(
---
Finished <<< tracetools_read [1.34s]
Starting >>> tracetools_launch
Starting >>> ros2trace
--- stderr: caret_analyze
/home/hydrapc/.local/lib/python3.8/site-packages/setuptools/command/easy_install.py:144: EasyInstallDeprecationWarning: easy_install command is deprecated. Use build and pip and other standards-based tools.
  warnings.warn(
/home/hydrapc/.local/lib/python3.8/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
  warnings.warn(
/home/hydrapc/.local/lib/python3.8/site-packages/pkg_resources/__init__.py:123: PkgResourcesDeprecationWarning: 0.1.36ubuntu1 is an invalid version and will not be supported in a future release
  warnings.warn(
/home/hydrapc/.local/lib/python3.8/site-packages/pkg_resources/__init__.py:123: PkgResourcesDeprecationWarning: 0.23ubuntu1 is an invalid version and will not be supported in a future release
  warnings.warn(
---
Finished <<< caret_analyze [1.37s]
Starting >>> ros2caret
--- stderr: tracetools_launch
/home/hydrapc/.local/lib/python3.8/site-packages/setuptools/command/easy_install.py:144: EasyInstallDeprecationWarning: easy_install command is deprecated. Use build and pip and other standards-based tools.
  warnings.warn(
/home/hydrapc/.local/lib/python3.8/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
  warnings.warn(
/home/hydrapc/.local/lib/python3.8/site-packages/pkg_resources/__init__.py:123: PkgResourcesDeprecationWarning: 0.1.36ubuntu1 is an invalid version and will not be supported in a future release
  warnings.warn(
/home/hydrapc/.local/lib/python3.8/site-packages/pkg_resources/__init__.py:123: PkgResourcesDeprecationWarning: 0.23ubuntu1 is an invalid version and will not be supported in a future release
  warnings.warn(
---
Finished <<< tracetools_launch [1.33s]
Starting >>> tracetools_test
--- stderr: ros2caret
/home/hydrapc/.local/lib/python3.8/site-packages/setuptools/command/easy_install.py:144: EasyInstallDeprecationWarning: easy_install command is deprecated. Use build and pip and other standards-based tools.
  warnings.warn(
/home/hydrapc/.local/lib/python3.8/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
  warnings.warn(
/home/hydrapc/.local/lib/python3.8/site-packages/pkg_resources/__init__.py:123: PkgResourcesDeprecationWarning: 0.1.36ubuntu1 is an invalid version and will not be supported in a future release
  warnings.warn(
/home/hydrapc/.local/lib/python3.8/site-packages/pkg_resources/__init__.py:123: PkgResourcesDeprecationWarning: 0.23ubuntu1 is an invalid version and will not be supported in a future release
  warnings.warn(
---
Finished <<< ros2caret [1.33s]
--- stderr: ros2trace
/home/hydrapc/.local/lib/python3.8/site-packages/setuptools/command/easy_install.py:144: EasyInstallDeprecationWarning: easy_install command is deprecated. Use build and pip and other standards-based tools.
  warnings.warn(
/home/hydrapc/.local/lib/python3.8/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
  warnings.warn(
/home/hydrapc/.local/lib/python3.8/site-packages/pkg_resources/__init__.py:123: PkgResourcesDeprecationWarning: 0.1.36ubuntu1 is an invalid version and will not be supported in a future release
  warnings.warn(
/home/hydrapc/.local/lib/python3.8/site-packages/pkg_resources/__init__.py:123: PkgResourcesDeprecationWarning: 0.23ubuntu1 is an invalid version and will not be supported in a future release
  warnings.warn(
---
Finished <<< ros2trace [1.37s]
--- stderr: tracetools_test
/home/hydrapc/.local/lib/python3.8/site-packages/setuptools/command/easy_install.py:144: EasyInstallDeprecationWarning: easy_install command is deprecated. Use build and pip and other standards-based tools.
  warnings.warn(
/home/hydrapc/.local/lib/python3.8/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
  warnings.warn(
/home/hydrapc/.local/lib/python3.8/site-packages/pkg_resources/__init__.py:123: PkgResourcesDeprecationWarning: 0.1.36ubuntu1 is an invalid version and will not be supported in a future release
  warnings.warn(
/home/hydrapc/.local/lib/python3.8/site-packages/pkg_resources/__init__.py:123: PkgResourcesDeprecationWarning: 0.23ubuntu1 is an invalid version and will not be supported in a future release
  warnings.warn(
---
Finished <<< tracetools_test [0.92s]
--- stderr: rcl
In file included from /home/hydrapc/projects/ros2_caret_ws/src/ros2/rcl/rcl/include/rcl/client.h:27,
                 from /home/hydrapc/projects/ros2_caret_ws/src/ros2/rcl/rcl/src/rcl/client.c:20:
/home/hydrapc/projects/ros2_caret_ws/src/ros2/rcl/rcl/include/rcl/event_callback.h:18:10: fatal error: rmw/event_callback_type.h: No such file or directory
   18 | #include "rmw/event_callback_type.h"
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [CMakeFiles/rcl.dir/build.make:76: CMakeFiles/rcl.dir/src/rcl/client.c.o] Error 1
make[2]: *** Waiting for unfinished jobs....
In file included from /home/hydrapc/projects/ros2_caret_ws/src/ros2/rcl/rcl/include/rcl/client.h:27,
                 from /home/hydrapc/projects/ros2_caret_ws/src/ros2/rcl/rcl/include/rcl/event.h:27,
                 from /home/hydrapc/projects/ros2_caret_ws/src/ros2/rcl/rcl/src/rcl/event.c:20:
/home/hydrapc/projects/ros2_caret_ws/src/ros2/rcl/rcl/include/rcl/event_callback.h:18:10: fatal error: rmw/event_callback_type.h: No such file or directory
   18 | #include "rmw/event_callback_type.h"
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [CMakeFiles/rcl.dir/build.make:128: CMakeFiles/rcl.dir/src/rcl/event.c.o] Error 1
In file included from /home/hydrapc/projects/ros2_caret_ws/src/ros2/rcl/rcl/include/rcl/client.h:27,
                 from /home/hydrapc/projects/ros2_caret_ws/src/ros2/rcl/rcl/include/rcl/graph.h:35,
                 from /home/hydrapc/projects/ros2_caret_ws/src/ros2/rcl/rcl/src/rcl/graph.c:20:
/home/hydrapc/projects/ros2_caret_ws/src/ros2/rcl/rcl/include/rcl/event_callback.h:18:10: fatal error: rmw/event_callback_type.h: No such file or directory
   18 | #include "rmw/event_callback_type.h"
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [CMakeFiles/rcl.dir/build.make:154: CMakeFiles/rcl.dir/src/rcl/graph.c.o] Error 1
In file included from /home/hydrapc/projects/ros2_caret_ws/src/ros2/rcl/rcl/include/rcl/subscription.h:27,
                 from /home/hydrapc/projects/ros2_caret_ws/src/ros2/rcl/rcl/include/rcl/rcl.h:79,
                 from /home/hydrapc/projects/ros2_caret_ws/src/ros2/rcl/rcl/src/rcl/guard_condition.c:23:
/home/hydrapc/projects/ros2_caret_ws/src/ros2/rcl/rcl/include/rcl/event_callback.h:18:10: fatal error: rmw/event_callback_type.h: No such file or directory
   18 | #include "rmw/event_callback_type.h"
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [CMakeFiles/rcl.dir/build.make:167: CMakeFiles/rcl.dir/src/rcl/guard_condition.c.o] Error 1
In file included from /home/hydrapc/projects/ros2_caret_ws/src/ros2/rcl/rcl/include/rcl/subscription.h:27,
                 from /home/hydrapc/projects/ros2_caret_ws/src/ros2/rcl/rcl/include/rcl/rcl.h:79,
                 from /home/hydrapc/projects/ros2_caret_ws/src/ros2/rcl/rcl/src/rcl/node.c:33:
/home/hydrapc/projects/ros2_caret_ws/src/ros2/rcl/rcl/include/rcl/event_callback.h:18:10: fatal error: rmw/event_callback_type.h: No such file or directory
   18 | #include "rmw/event_callback_type.h"
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [CMakeFiles/rcl.dir/build.make:297: CMakeFiles/rcl.dir/src/rcl/node.c.o] Error 1
In file included from /home/hydrapc/projects/ros2_caret_ws/src/ros2/rcl/rcl/include/rcl/client.h:27,
                 from /home/hydrapc/projects/ros2_caret_ws/src/ros2/rcl/rcl/include/rcl/graph.h:35,
                 from /home/hydrapc/projects/ros2_caret_ws/src/ros2/rcl/rcl/src/rcl/network_flow_endpoints.c:21:
/home/hydrapc/projects/ros2_caret_ws/src/ros2/rcl/rcl/include/rcl/event_callback.h:18:10: fatal error: rmw/event_callback_type.h: No such file or directory
   18 | #include "rmw/event_callback_type.h"
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [CMakeFiles/rcl.dir/build.make:284: CMakeFiles/rcl.dir/src/rcl/network_flow_endpoints.c.o] Error 1
/home/hydrapc/projects/ros2_caret_ws/src/ros2/rcl/rcl/src/rcl/publisher.c: In function ‘rcl_publisher_wait_for_all_acked’:
/home/hydrapc/projects/ros2_caret_ws/src/ros2/rcl/rcl/src/rcl/publisher.c:328:19: warning: implicit declaration of function ‘rmw_publisher_wait_for_all_acked’; did you mean ‘rcl_publisher_wait_for_all_acked’? [-Wimplicit-function-declaration]
  328 |   rmw_ret_t ret = rmw_publisher_wait_for_all_acked(publisher->impl->rmw_handle, rmw_timeout);
      |                   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      |                   rcl_publisher_wait_for_all_acked
make[1]: *** [CMakeFiles/Makefile2:431: CMakeFiles/rcl.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
make: *** [Makefile:141: all] Error 2
---
Failed   <<< rcl [5.42s, exited with code 2]

Summary: 13 packages finished [6.57s]
  1 package failed: rcl
  8 packages had stderr output: caret_analyze rcl ros2caret ros2trace tracetools_launch tracetools_read tracetools_test tracetools_trace
  9 packages not processed

@Torreskai0722
Thank you for reporting.
Could you tell me which branch of CARET your are trying?

@Torreskai0722 Thank you for reporting. Could you tell me which branch of CARET your are trying? Are you working on galactic ?
We'll be glad if you share the procedure to find the same issue. Best,

Yes, I checkout to galactic branch since I'm using Ubuntu 20.04 with ROS galactic.
I followed the setup here. I manually installed lttng 2.12.5 with this deb package since the 2.12 version cannot be installed.

@Torreskai0722
I doubt that you have checked out to galactic branch before execution of vcs import src < caret.repos.
event_callback.h which appeared in your error message has been added since ROS 2 Humble release (link). event_callback.h does not exist in ROS 2 Galactic (link).
Could you try the following commands in order?
git clone https://github.com/tier4/caret.git -b galactic ros2_caret_ws
mkdir src
vcs import src < caret.repos
./setup_caret.sh # this is necessary for executing colcon build
colcon build --symlink-install --cmake-args -DCMAKE_BUILD_TYPE=Release

@Torreskai0722 I doubt that you have checked out to galactic branch before execution of vcs import src < caret.repos. event_callback.h which appeared in your error message has been added since ROS 2 Humble release (link). event_callback.h does not exist in ROS 2 Galactic (link).
Could you try the following commands in order?
git clone https://github.com/tier4/caret.git -b galactic ros2_caret_ws
mkdir src
vcs import src < caret.repos
./setup_caret.sh # this is necessary for executing colcon build
colcon build --symlink-install --cmake-args -DCMAKE_BUILD_TYPE=Release

It works! Thanks for your reply.

@Torreskai0722 I doubt that you have checked out to galactic branch before execution of vcs import src < caret.repos. event_callback.h which appeared in your error message has been added since ROS 2 Humble release (link). event_callback.h does not exist in ROS 2 Galactic (link).
Could you try the following commands in order?
git clone https://github.com/tier4/caret.git -b galactic ros2_caret_ws
mkdir src
vcs import src < caret.repos
./setup_caret.sh # this is necessary for executing colcon build
colcon build --symlink-install --cmake-args -DCMAKE_BUILD_TYPE=Release

It works! Thanks for your reply.

I finished the setup and tried the measurement tutorial.
I can get the results under evaluate/e2e_sample, but got the following error when run check_ctf. I have found both check_ctf.py and record_cpp_impl.py files and changed their permissions. But it doesn't solve the issue. Any idea of how to address it?
Thanks!
(base) hydrapc@hydrapc:~/projects/ros2_ws/evaluate$ ros2 caret check_ctf -d ~/projects/ros2_ws/evaluate/e2e_sample/
Failed to load entry point 'check_ctf': No module named 'record_cpp_impl'
Traceback (most recent call last):
  File "/opt/ros/galactic/bin/ros2", line 11, in <module>
    load_entry_point('ros2cli==0.13.4', 'console_scripts', 'ros2')()
  File "/opt/ros/galactic/lib/python3.8/site-packages/ros2cli/cli.py", line 39, in main
    add_subparsers_on_demand(
  File "/opt/ros/galactic/lib/python3.8/site-packages/ros2cli/command/__init__.py", line 250, in add_subparsers_on_demand
    extension.add_arguments(
  File "/home/hydrapc/projects/ros2_caret_ws/build/ros2caret/ros2caret/command/caret.py", line 22, in add_arguments
    add_subparsers_on_demand(
  File "/opt/ros/galactic/lib/python3.8/site-packages/ros2cli/command/__init__.py", line 237, in add_subparsers_on_demand
    extension = command_extensions[name]
KeyError: 'check_ctf'

@Torreskai0722
I suspect that path of command did not included in PATH variable.
Could you try as below?
source /path/to/ros2_caret_ws/install/setup.bash
ros2 caret check_ctf -d ~/projects/ros2_ws/evaluate/e2e_sample/

I have sourced it. Still doesn't work.
(base) hydrapc@hydrapc:~$ source ~/projects/ros2_caret_ws/install/setup.bash
(base) hydrapc@hydrapc:~$ ros2 caret check_ctf -d ~/projects/ros2_ws/evaluate/e2e_sample/
Failed to load entry point 'check_ctf': No module named 'record_cpp_impl'
Traceback (most recent call last):
  File "/opt/ros/galactic/bin/ros2", line 11, in <module>
    load_entry_point('ros2cli==0.13.4', 'console_scripts', 'ros2')()
  File "/opt/ros/galactic/lib/python3.8/site-packages/ros2cli/cli.py", line 39, in main
    add_subparsers_on_demand(
  File "/opt/ros/galactic/lib/python3.8/site-packages/ros2cli/command/__init__.py", line 250, in add_subparsers_on_demand
    extension.add_arguments(
  File "/home/hydrapc/projects/ros2_caret_ws/build/ros2caret/ros2caret/command/caret.py", line 22, in add_arguments
    add_subparsers_on_demand(
  File "/opt/ros/galactic/lib/python3.8/site-packages/ros2cli/command/__init__.py", line 237, in add_subparsers_on_demand
    extension = command_extensions[name]
KeyError: 'check_ctf'

Depends on permittions, similar issue can reproduce.
chmod 000 -R ./ros2_caret_ws/install/caret_analyze_cpp_impl/lib

$ ros2 caret check_ctf -d e2e_sample
Failed to load entry point 'check_ctf': No module named 'record_cpp_impl'
Traceback (most recent call last):
  File "/opt/ros/galactic/bin/ros2", line 11, in <module>
    load_entry_point('ros2cli==0.13.4', 'console_scripts', 'ros2')()
  File "/opt/ros/galactic/lib/python3.8/site-packages/ros2cli/cli.py", line 39, in main
    add_subparsers_on_demand(
  File "/opt/ros/galactic/lib/python3.8/site-packages/ros2cli/command/__init__.py", line 250, in add_subparsers_on_demand
    extension.add_arguments(
  File "/home/hasegawa/ros2_caret_ws/build/ros2caret/ros2caret/command/caret.py", line 22, in add_arguments
    add_subparsers_on_demand(
  File "/opt/ros/galactic/lib/python3.8/site-packages/ros2cli/command/__init__.py", line 237, in add_subparsers_on_demand
    extension = command_extensions[name]
KeyError: 'check_ctf'

It seems that libraries in caret_analyze_cpp_impl may don't have enough permissions.

If caret_analyze_cpp_impl is built correctly, following binaries should exist.
$ find install/caret_analyze_cpp_impl/ | grep "\.so"
install/caret_analyze_cpp_impl/lib/python3.8/site-packages/record_cpp_impl.cpython-38-x86_64-linux-gnu.so
install/caret_analyze_cpp_impl/lib/libcaret_analyze_cpp_impl.so

Were there any warning or errors in colcon build?
$ colcon build --symlink-install --packages-select caret_analyze_cpp_impl
Starting >>> caret_analyze_cpp_impl
Finished <<< caret_analyze_cpp_impl [14.1s]

Summary: 1 package finished [14.4s]

I'm concerned with PYTHONPATH after source /path/to/caret/install/setup.bash
Could you share the result of the following commands execution.
source /path/to/caret/install/setup.bash
echo $PYTHONPATH

I can find them, and there is no warning when building the caret_analyze_cpp_impl.
(base) hydrapc@hydrapc:~/projects/ros2_caret_ws$ find install/caret_analyze_cpp_impl/ | grep "\.so"
install/caret_analyze_cpp_impl/lib/libcaret_analyze_cpp_impl.so
install/caret_analyze_cpp_impl/lib/python3.8/site-packages/record_cpp_impl.cpython-37m-x86_64-linux-gnu.so

(base) hydrapc@hydrapc:~/projects/ros2_caret_ws$  colcon build --symlink-install --cmake-args -DCMAKE_BUILD_TYPE=Release --packages-select caret_analyze_cpp_impl
Starting >>> caret_analyze_cpp_impl
Finished <<< caret_analyze_cpp_impl [0.41s]

Summary: 1 package finished [0.68s]

I can find them, and there is no warning when building the caret_analyze_cpp_impl.
(base) hydrapc@hydrapc:~/projects/ros2_caret_ws$ find install/caret_analyze_cpp_impl/ | grep "\.so"
install/caret_analyze_cpp_impl/lib/libcaret_analyze_cpp_impl.so
install/caret_analyze_cpp_impl/lib/python3.8/site-packages/record_cpp_impl.cpython-37m-x86_64-linux-gnu.so

(base) hydrapc@hydrapc:~/projects/ros2_caret_ws$  colcon build --symlink-install --cmake-args -DCMAKE_BUILD_TYPE=Release --packages-select caret_analyze_cpp_impl
Starting >>> caret_analyze_cpp_impl
Finished <<< caret_analyze_cpp_impl [0.41s]

Summary: 1 package finished [0.68s]

I'm concerned with PYTHONPATH after source /path/to/caret/install/setup.bash
Could you share the result of the following commands execution.
source /path/to/caret/install/setup.bash
echo $PYTHONPATH

Here is the result:
(base) hydrapc@hydrapc:~/projects/ros2_caret_ws$ echo $PYTHONPATH
/home/hydrapc/projects/ros2_caret_ws/build/tracetools_launch:/home/hydrapc/projects/ros2_caret_ws/install/tracetools_launch/lib/python3.8/site-packages:/home/hydrapc/projects/ros2_caret_ws/build/ros2trace:/home/hydrapc/projects/ros2_caret_ws/install/ros2trace/lib/python3.8/site-packages:/home/hydrapc/projects/ros2_caret_ws/build/tracetools_trace:/home/hydrapc/projects/ros2_caret_ws/install/tracetools_trace/lib/python3.8/site-packages:/home/hydrapc/projects/ros2_caret_ws/build/tracetools_read:/home/hydrapc/projects/ros2_caret_ws/install/tracetools_read/lib/python3.8/site-packages:/home/hydrapc/projects/ros2_caret_ws/build/ros2caret:/home/hydrapc/projects/ros2_caret_ws/install/ros2caret/lib/python3.8/site-packages:/home/hydrapc/projects/ros2_caret_ws/install/caret_analyze_cpp_impl/lib/python3.8/site-packages:/home/hydrapc/projects/ros2_caret_ws/build/caret_analyze:/home/hydrapc/projects/ros2_caret_ws/install/caret_analyze/lib/python3.8/site-packages:/home/hydrapc/projects/CARLA/CARLA_Leaderboard_20/PythonAPI/carla/:/home/hydrapc/projects/CARLA/scenario_runner:/home/hydrapc/projects/CARLA/leaderboard:/home/hydrapc/projects/CARLA/CARLA_Leaderboard_20/PythonAPI/carla/dist/carla-0.9.13-py3.7-linux-x86_64.egg:/opt/ros/galactic/lib/python3.8/site-packages

I'm concerned with PYTHONPATH after source /path/to/caret/install/setup.bash
Could you share the result of the following commands execution.
source /path/to/caret/install/setup.bash
echo $PYTHONPATH

Here is the result:
(base) hydrapc@hydrapc:~/projects/ros2_caret_ws$ echo $PYTHONPATH
/home/hydrapc/projects/ros2_caret_ws/build/tracetools_launch:/home/hydrapc/projects/ros2_caret_ws/install/tracetools_launch/lib/python3.8/site-packages:/home/hydrapc/projects/ros2_caret_ws/build/ros2trace:/home/hydrapc/projects/ros2_caret_ws/install/ros2trace/lib/python3.8/site-packages:/home/hydrapc/projects/ros2_caret_ws/build/tracetools_trace:/home/hydrapc/projects/ros2_caret_ws/install/tracetools_trace/lib/python3.8/site-packages:/home/hydrapc/projects/ros2_caret_ws/build/tracetools_read:/home/hydrapc/projects/ros2_caret_ws/install/tracetools_read/lib/python3.8/site-packages:/home/hydrapc/projects/ros2_caret_ws/build/ros2caret:/home/hydrapc/projects/ros2_caret_ws/install/ros2caret/lib/python3.8/site-packages:/home/hydrapc/projects/ros2_caret_ws/install/caret_analyze_cpp_impl/lib/python3.8/site-packages:/home/hydrapc/projects/ros2_caret_ws/build/caret_analyze:/home/hydrapc/projects/ros2_caret_ws/install/caret_analyze/lib/python3.8/site-packages:/home/hydrapc/projects/CARLA/CARLA_Leaderboard_20/PythonAPI/carla/:/home/hydrapc/projects/CARLA/scenario_runner:/home/hydrapc/projects/CARLA/leaderboard:/home/hydrapc/projects/CARLA/CARLA_Leaderboard_20/PythonAPI/carla/dist/carla-0.9.13-py3.7-linux-x86_64.egg:/opt/ros/galactic/lib/python3.8/site-packages

@Torreskai0722
Sorry for not responding. Could you upload compressed log directory generated in /path/to/caret/log?
Best,

@Torreskai0722
Have you try building CARET just after deleting directories; build and install?
I suspect that cached data in build and install caused your issue.
If no, please try the following commands
cd /path/to/ros2_caret_ws
rm -rf build install log

colcon build --symlink-install --cmake-args -DCMAKE_BUILD_TYPE=Release

@Torreskai0722 Have you tried building CARET just after deleting directories; build and install? I suspect that cached data in build and install caused your issue.
If no, please try the following commands
cd /path/to/ros2_caret_ws
rm -rf build install log

colcon build --symlink-install --cmake-args -DCMAKE_BUILD_TYPE=Release

I tried to delete them and rebuint. The error is still there.

@Torreskai0722
Do you use Anaconda-based Python?
I suppose that (base) on your terminal might imply that you are using Anaconda.
We have verified that CARET works on standard Python, but we haven't verified with Anaconda.

I deactivated the conda environment. Then I delete build, install and log folders and rebuild the caret. It works now! Thanks!
hydrapc@hydrapc:~/projects/ros2_caret_ws$ ros2 caret check_ctf -d ../ros2_ws/evaluate/e2e_sample/
Succeed to find record_cpp_impl. the C++ version will be used.
converting: 14143it [00:00, 35055.19it/s]
14019 events found.
loading: 100%|████████████████████████| 14019/14019 [00:00<00:00, 146950.64it/s]
14019 events found.
loading: 100%|███████████████████████| 14019/14019 [00:00<00:00, 1518632.91it/s]
filtered to 222 events.
/home/hydrapc/projects/ros2_caret_ws/build/caret_analyze/caret_analyze/infra/lttng/lttng_info.py:436: FutureWarning: In a future version of pandas, a length 1 tuple will be returned when iterating over a groupby with a grouper equal to a list of length 1. Don't supply a list with a single grouper to avoid this warning.
  for _, group_df in concat_df.groupby(['callback_group_addr']):
/home/hydrapc/projects/ros2_caret_ws/build/caret_analyze/caret_analyze/infra/lttng/lttng_info.py:436: FutureWarning: In a future version of pandas, a length 1 tuple will be returned when iterating over a groupby with a grouper equal to a list of length 1. Don't supply a list with a single grouper to avoid this warning.
  for _, group_df in concat_df.groupby(['callback_group_addr']):
/home/hydrapc/projects/ros2_caret_ws/build/caret_analyze/caret_analyze/infra/lttng/lttng_info.py:436: FutureWarning: In a future version of pandas, a length 1 tuple will be returned when iterating over a groupby with a grouper equal to a list of length 1. Don't supply a list with a single grouper to avoid this warning.
  for _, group_df in concat_df.groupby(['callback_group_addr']):
/home/hydrapc/projects/ros2_caret_ws/build/caret_analyze/caret_analyze/infra/lttng/lttng_info.py:436: FutureWarning: In a future version of pandas, a length 1 tuple will be returned when iterating over a groupby with a grouper equal to a list of length 1. Don't supply a list with a single grouper to avoid this warning.
  for _, group_df in concat_df.groupby(['callback_group_addr']):
/home/hydrapc/projects/ros2_caret_ws/build/caret_analyze/caret_analyze/infra/lttng/lttng_info.py:436: FutureWarning: In a future version of pandas, a length 1 tuple will be returned when iterating over a groupby with a grouper equal to a list of length 1. Don't supply a list with a single grouper to avoid this warning.
  for _, group_df in concat_df.groupby(['callback_group_addr']):
/home/hydrapc/projects/ros2_caret_ws/build/caret_analyze/caret_analyze/infra/lttng/lttng_info.py:436: FutureWarning: In a future version of pandas, a length 1 tuple will be returned when iterating over a groupby with a grouper equal to a list of length 1. Don't supply a list with a single grouper to avoid this warning.
  for _, group_df in concat_df.groupby(['callback_group_addr']):


Upload geojson file

Possible to upload polygons with .geojson or .json format.
Polygon is drawn in map automatically.
Automatic zoom to uploaded polygon.
Run area report on uploaded polygons.
Error snackbar if geometry in uploaded geojson is wrong.

Test den: https://forvaltningsportal.test.artsdatabanken.no/pr/forvaltningsportal_381

Test den: https://forvaltningsportal.test.artsdatabanken.no/pr/forvaltningsportal_381


Fix blurry bitmaps

Fixes issue #594  (hopefully)
this also comes with:

Optimized shaders
Added Bitmap.pixelSnapping support (not fully)
BitmapData should default to nearest filtering.

Let's wait until we have confirmation that this fixes it before merging :sweat_smile:

You rang?

I just did some testing, and it seems good, if we find ways to improve, we can refine from here :smile:


1.19.2 Broken on latest ae2 version 12.9.8

you cant store nor take out items from me systems

I don`t find problems. Send more information

like what? ive tried with just ae2 and the latest version of the mod for 1.19.2 and it still didnt work, singleplayer or server, idk anything else, i use modrinth to get mods

Send config ae2ao.toml

https://pastebin.com/CKTwEUWq - unedited config
https://pastebin.com/C8ibKihz - edited config
tried both

It is version forge 8.1? Config has more parameters

fabric 1.19.2

It`s repository for forge. Now I'll see what's broken


Introduce broadcast API for event sharing

What would you like to be added:
Yorkie presently relies on the Publish-Subscribe model for sharing document and presence events (refer to: pub-sub.md).
However, this lacks the capability to extend its scope to encompass additional event types, notably notifications for end users  concerning new document updates or comments.
To address this limitation, the introduction of a "broadcast" feature is recommended.
This feature would enable users to define and share a wider range of general events beyond the existing document and presence events.
It's also related to #442, which extracts Room from Document and moves Presence from Client to Room.
Why is this needed:
Provide a more comprehensive event-sharing mechanism that satisfies various use cases.

Is this feature replaces current watch API (pub/sub model)?
I want to know further details and implementation for this proposal :)

Is this feature replacing the current watch API (pub/sub model)? I want to know further details and implementation for this proposal :)

Thanks for your interest.
It won't replace the watch API, but extend the current pub/sub model to accept general events.
You can find more details in the broadcast docs of Supabase, Liveblocks or Socket.IO.
ref.
https://supabase.com/docs/guides/realtime/broadcast

SDKs:

[x] Go SDK: https://github.com/yorkie-team/yorkie/pull/631
[ ] JS SDK:
[ ] iOS SDK:
[ ] Android SDK:

I'll work on the js sdk

It would be beneficial to allow broadcasts to emit events via REST API. For certain events (such as Refresh Notification), it is more natural for the server to emit the events rather than the client.
Reference: https://liveblocks.io/docs/api-reference/rest-api-endpoints#post-broadcast-event

Could I give it a try for JS-SDK?

Could I give it a try for JS-SDK?

@gwbaik9717 Sure. If you have any questions, feel free to ask.


HTML custom tag has wrong color when name partially overlaps with standard tag

VSCode Version: 1.12.1
OS Version: Win 10 Version 1703 64b

Steps to Reproduce:

create an HTML (Angular template) file
type a custom component tag, whose name starts with a known standard HTML tag, e.g. some <form-field> tag.

Exptected
<form-field> should all be formatted in one color, the same applied to HTML standard tags.
Actual
<form half has same color as standard tag, while the rest, -field>, is colored as an attribute:

This issue was moved to textmate/html.tmbundle#63


feat: add rev_map() to @immut/list

Mirrors OCaml's List.rev_map, which is a more efficient (tail-recursive) version of List.map at the cost of getting a reversed list.

Pull Request Test Coverage Report for Build 3589
Details

3 of 3 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 82.33%

Totals

Change from base Build 3580:
0.01%

Covered Lines:
4198

Relevant Lines:
5099

💛  - Coveralls


Node.js Quickstart cannot work

Expected Behavior
Actual Behavior
Steps to Reproduce the Problem

Specifications

Node version (node -v)
OS (Mac/Linux/Windows)

help please

??????

give us an error


Fix broken script include on full-page examples

The getFingerprint function returns a path that includes the leading slash already, so this currently evaluates to //javascripts/govuk-frontend-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.js which means the browser treats the URL as a protocol-less but absolute URL and tries to load https://javascripts/govuk-frontend-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.js.

You can preview this change here:
Built with commit a6e11281f3498d7225f658fc1c5a434e9d7b61a9
https://deploy-preview-520--govuk-design-system-preview.netlify.com


detect current PAM status

Hi,
Currently, when the plugin is in the environment, Snakemake will fail whenever the password is not given on the command line. However, the default auth scheme is PAM, if I am not mistaken. Hence, when an iinit command has been successfully performed, the password should not be required any more.
Defining the password in an env variable or on the command line [edit:] or in a plain text file [/edit] is not a good idea because this exposes it (classroom, office and every admin).
Or am I missing something, here?
Cheers
Christian

Hi Christian,
I think specifying the PAM password might on the one hand be necessary for some use cases in order to deal with the limited TTL of cached passwords. On the other hand, I agree it makes sense to also allow for using cached passwords in situations where that is not an issue.
I've created a PR to make the plugin fall back on the cached password if no password is provided via the command-line arguments, settings file or iRODS environment file: https://github.com/snakemake/snakemake-storage-plugin-irods/pull/11
Best,
Sietse


Update lvl-drag-drop.js

Returning the DOM elements themselves causes a $parse:isecdom error in newer versions of AngularJS. Simply enough, let the dropped(...) callback handle fetching the elements.
See: https://github.com/logicbomb/lvlDragDrop/issues/14

Sorry I missed this, it's been addressed in commit 9b3ccfa


[Upstream] Update core libraries

swc core v1.3.87
sharp v0.32.6
webpack v5.88.2
the other libs

@Licoy would you take a look into this PR?


.md syntax fix for coming-from-other-languages.md

Titles were lacking spaces, breaking linking from the ToC and making it hard to read.

Thanks


Hydration fails on fresh app with "Expected server HTML to contain a matching  in "

What version of Remix are you using?
@remix-run/express ^1.6.8
Steps to Reproduce

Create a minimal Express-based app using npx create-remix@latest and the following settings:

? Where would you like to create your app? ./minimal
? What type of app do you want to create? Just the basics
? Where do you want to deploy? Choose Remix App Server if you're unsure; it's easy to change deployment targets.
Express Server
? TypeScript or JavaScript? TypeScript
? Do you want me to run `npm install`? Yes

Run the app and visit in a browser
Open console to view errors

Expected Behavior
No errors in browser console
Actual Behavior

If I comment out <Scripts /> in root.tsx, the errors disappear.

This is one of your browser extensions injecting code : https://remix.run/docs/en/v1/pages/gotchas#browser-extensions-injecting-code

@machour Thanks for your help. I had looked at the page you linked; not sure how I missed that section! :sweat_smile:
The extension causing the error was Apollo Client DevTools, which is something I have used for React development in the past. Is it something that should play nicely with Remix also? If so, should I submit an issue here or with the Apollo team (or both)?


how  can I use this code do image segmentation

maybe u should check https://github.com/svip-lab/AS-MLP-Object-Detection

@useunreal Please refer to https://github.com/svip-lab/AS-MLP-Semantic-Segmentation


Compatibility of workflow steps

Describe the bug
Currently people can select 'lfq_quantification' without ever having imported or searched any file. It would be important to make the selection of workflow steps somehow linked to whether an hdf file with required information is already there.
Importantly, in these cases, the settings files need to somehow be saved differently to ensure that users can still follow how the final results were created in case multiple different settings were used and then stacked on top of each other.

Moved to suggestions.


Additional folder for useful tools

People are sharing links to useful tools, we could collect them in one place and split based on operating system / just list them and tag on what OS are they working / just list them.

Good idea, I would split them based on the operating system.

This may be useful for you @jvaes when you will split links. Closing for now, but please keep it in your mind! :)


It keeps recreating migration for models that have state field

Description:
Because django-river uses a random related_name in the state field, Django thinks that the state field got updated every time we run makemigrations. It should not be recreating it.

@javrasya of course, sorry for delay, I was posting the content of the migration but I guess you were able to recreate it.

@superandrew can you try v1.0.2 which has just been published. It must  re-create the migration once and for all now.

I installed 1.0.2 from pip and I can confirm that the migration isn't generated anymore in my project.

Thank you for the contribution @superandrew . Please keep up reporting when you face some bugs. 🙏


[Feature] Zoom support

It seems that there is no easy way to implement this feature in few days, therefore I need some weeks to survey and try to implement it on Obsidian platform. Please be patience for waiting status update.

Hello @scruel,
I have implement the zoom feature on the version 1.0.8 of the this plugin.
You could update to latest version and try to use it to see if something wrong.


Is it a typo?

The README.md title reporting "# Oddly satisfying usell build script" while I suppose you want to write useless

It's a typo, going to correct it.


AdminLTE v2.4.0

A new version of AdminLTE is out.  The changes are rather minimal:
https://adminlte.io/docs/2.4/upgrade-guide
I'm mostly pointing this out as a warning, since I use the assets from the adminlte npm package, and had to downgrade it to get them back in sync.

Hi! Thanks. I am already busy with upgrading and will publish the new version soon.

v1.22.0 of this package is just released and includes AdminLTE v2.4.0!