Clangd is parsing object instantiation as function declaration (not MVP ambiguity)

I have the following c++ code
struct Foo {
  Foo(int x) {}
};

int main() {
  int x = 42;
  Foo f(x);
}

That I can compile and execute with clang++. However, if I open this code in Neovim, my LSP (clangd) recognizes f as a function rather than an object:

At first I thought this might have something to do with the most-vexing-parse, however I don't think the code has any ambiguity as it is clear that x is an integer object. Any suggestion on how I can fix the clangd parsing?
System information
Output of clangd --version:
Apple clangd version 14.0.3 (clang-14<IP_ADDRESS>.1)
Features: mac+xpc
Platform: x86_64-apple-darwin23.2.0; target=arm64-apple-darwin23.2.0

Editor/LSP plugin: neovim
Operating system: macOS Sonoma 14.2.1

Could you share clangd logs please?

Could you share clangd logs please?

Thanks for your reply @HighCommander4 , is this what you were expecting?
I[09:27:07.085] Apple clangd version 14.0.3 (clang-14<IP_ADDRESS>.1)
I[09:27:07.086] Features: mac+xpc
I[09:27:07.086] PID: 20933
I[09:27:07.086] Working directory: /Users/fyc/toys/c++/playground/not_MVP
I[09:27:07.086] argv[0]: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clangd
I[09:27:07.086] argv[1]: --check=not_MVP.cpp
I[09:27:07.086] argv[2]: --log=verbose
V[09:27:07.086] User config file is /Users/fyc/Library/Preferences/clangd/config.yaml
I[09:27:07.086] Entering check mode (no LSP server)
I[09:27:07.086] Testing on source file /Users/fyc/toys/c++/playground/not_MVP/not_MVP.cpp
I[09:27:07.086] Loading compilation database...
V[09:27:07.086] Invoking /usr/bin/xcrun to find clang installation
E[09:27:07.092] Failed to load compilation database from /Users/fyc/toys/c++/playground/not_MVP/compile_commands.json: Missing key: "directory".
I[09:27:07.093] Failed to find compilation database for /Users/fyc/toys/c++/playground/not_MVP/not_MVP.cpp
I[09:27:07.093] Generic fallback command is: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -resource-dir=/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/14.0.3 -- /Users/fyc/toys/c++/playground/not_MVP/not_MVP.cpp
I[09:27:07.093] Parsing command...

I[09:27:07.104] Indexing headers...
V[09:27:07.105] indexed preamble AST for /Users/fyc/toys/c++/playground/not_MVP/not_MVP.cpp version null:
  symbol slab: 0 symbols, 120 bytes
  ref slab: 0 symbols, 0 refs, 128 bytes
  relations slab: 0 relations, 24 bytes
V[09:27:07.105] Built preamble of size 500900 for file /Users/fyc/toys/c++/playground/not_MVP/not_MVP.cpp version null in 0.01 seconds
I[09:27:07.105] Building AST...
I[09:27:07.108] Indexing AST...
V[09:27:07.108] indexed file AST for /Users/fyc/toys/c++/playground/not_MVP/not_MVP.cpp version null:
  symbol slab: 3 symbols, 4912 bytes
  ref slab: 3 symbols, 6 refs, 4320 bytes
  relations slab: 0 relations, 24 bytes
V[09:27:07.108] Build dynamic index for main-file symbols with estimated memory usage of 12680 bytes
I[09:27:07.108] Testing features at each token (may be slow in large files)
V[09:27:07.108]   0:0 struct
V[09:27:07.109]     definition: 1
V[09:27:07.109]     hover: true
V[09:27:07.109]   0:7 Foo
V[09:27:07.109]     definition: 1
V[09:27:07.109]     hover: true
V[09:27:07.109]   0:11 {
V[09:27:07.109]     definition: 1
V[09:27:07.109]     hover: true
V[09:27:07.109]   1:2 Foo
V[09:27:07.109]     definition: 1
V[09:27:07.109]     hover: true
V[09:27:07.109]   1:5 (
V[09:27:07.109]     definition: 1
V[09:27:07.109]     hover: false
V[09:27:07.109]   1:6 int
V[09:27:07.109]     definition: 0
V[09:27:07.109]     hover: false
V[09:27:07.109]   1:10 x
V[09:27:07.109]     definition: 1
V[09:27:07.109]     hover: true
V[09:27:07.109]   1:11 )
V[09:27:07.109]     definition: 1
V[09:27:07.109]     hover: false
V[09:27:07.109]   1:13 {
V[09:27:07.109]     definition: 0
V[09:27:07.109]     hover: false
V[09:27:07.109]   1:14 }
V[09:27:07.109]     definition: 0
V[09:27:07.109]     hover: false
V[09:27:07.109]   2:0 }
V[09:27:07.109]     definition: 1
V[09:27:07.109]     hover: true
V[09:27:07.109]   2:1 ;
V[09:27:07.109]     definition: 1
V[09:27:07.109]     hover: true
V[09:27:07.109]   4:0 int
V[09:27:07.109]     definition: 0
V[09:27:07.109]     hover: false
V[09:27:07.109]   4:4 main
V[09:27:07.109]     definition: 1
V[09:27:07.110]     hover: true
V[09:27:07.110]   4:8 (
V[09:27:07.110]     definition: 1
V[09:27:07.110]     hover: false
V[09:27:07.110]   4:9 )
V[09:27:07.110]     definition: 0
V[09:27:07.110]     hover: false
V[09:27:07.110]   4:11 {
V[09:27:07.110]     definition: 0
V[09:27:07.110]     hover: false
V[09:27:07.110]   5:2 int
V[09:27:07.110]     definition: 0
V[09:27:07.110]     hover: false
V[09:27:07.110]   5:6 x
V[09:27:07.110]     definition: 1
V[09:27:07.110]     hover: true
V[09:27:07.110]   5:8 =
V[09:27:07.110]     definition: 1
V[09:27:07.110]     hover: true
V[09:27:07.110]   5:10 42
V[09:27:07.110]     tweak: ExtractVariable
V[09:27:07.110]     definition: 0
V[09:27:07.110]     hover: false
V[09:27:07.110]   5:12 ;
V[09:27:07.110]     definition: 0
V[09:27:07.110]     hover: false
V[09:27:07.110]   6:2 Foo
V[09:27:07.110]     definition: 1
V[09:27:07.110]     hover: true
V[09:27:07.110]   6:6 f
V[09:27:07.110]     definition: 1
V[09:27:07.110]     hover: true
V[09:27:07.110]   6:7 (
V[09:27:07.110]     tweak: ExtractVariable
V[09:27:07.110]     definition: 1
V[09:27:07.110]     hover: true
V[09:27:07.110]   6:8 x
V[09:27:07.110]     definition: 1
V[09:27:07.110]     hover: true
V[09:27:07.110]   6:9 )
V[09:27:07.110]     tweak: ExtractVariable
V[09:27:07.110]     definition: 1
V[09:27:07.110]     hover: true
V[09:27:07.110]   6:10 ;
V[09:27:07.110]     definition: 1
V[09:27:07.110]     hover: true
V[09:27:07.111]   7:0 }
V[09:27:07.111]     definition: 0
V[09:27:07.111]     hover: false
I[09:27:07.111] All checks completed, 0 errors

is this what you were expecting?

These are logs from a clangd --check run on the command line. I'm looking for logs from the clangd invocation made by your editor when you open this file and see the problem. See this comment for how to get clangd logs from neovim.
The specific thing I'm looking for in the logs is the contents of the textDocument/documentSymbol message sent by clangd, which is what I expect the editor uses to populate that "outline" view.

Below is the log entries written by clangd with --log=verbose:
I[21:48:48.148] clangd version 16.0.2 (https://github.com/llvm/llvm-project 18ddebe1a1a9bde349441631365f0472e9693520)
I[21:48:48.148] Features: mac+grpc+xpc
I[21:48:48.148] PID: 54747
I[21:48:48.148] Working directory: /Users/fyc/toys/c++/playground/not_MVP
I[21:48:48.148] argv[0]: /Users/fyc/.local/share/nvim/mason/bin/clangd
I[21:48:48.148] argv[1]: --offset-encoding=utf-16
I[21:48:48.148] argv[2]: --log=verbose
V[21:48:48.149] User config file is /Users/fyc/Library/Preferences/clangd/config.yaml
I[21:48:48.149] Starting LSP over stdin/stdout
V[21:48:48.149] <<< {
  "id": 1,
  "jsonrpc": "2.0",
  "method": "initialize",
  "params": {
    "capabilities": {
      "general": {
        "positionEncodings": [
          "utf-16"
        ]
      },
      "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": true,
          "isPreferredSupport": true,
          "resolveSupport": {
            "properties": [
              "edit"
            ]
          }
        },
        "completion": {
          "completionItem": {
            "commitCharactersSupport": false,
            "deprecatedSupport": false,
            "documentationFormat": [
              "markdown",
              "plaintext"
            ],
            "preselectSupport": false,
            "snippetSupport": false
          },
          "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": [
              "editRange",
              "insertTextFormat",
              "insertTextMode",
              "data"
            ]
          },
          "contextSupport": false,
          "dynamicRegistration": false,
          "editsNearCursor": true
        },
        "declaration": {
          "linkSupport": true
        },
        "definition": {
          "dynamicRegistration": true,
          "linkSupport": true
        },
        "diagnostic": {
          "dynamicRegistration": false
        },
        "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
            ]
          }
        },
        "formatting": {
          "dynamicRegistration": true
        },
        "hover": {
          "contentFormat": [
            "markdown",
            "plaintext"
          ],
          "dynamicRegistration": true
        },
        "implementation": {
          "linkSupport": true
        },
        "inlayHint": {
          "dynamicRegistration": true,
          "resolveSupport": {
            "properties": [
              "textEdits",
              "tooltip",
              "location",
              "command"
            ]
          }
        },
        "publishDiagnostics": {
          "dataSupport": true,
          "relatedInformation": true,
          "tagSupport": {
            "valueSet": [
              1,
              2
            ]
          }
        },
        "rangeFormatting": {
          "dynamicRegistration": true
        },
        "references": {
          "dynamicRegistration": false
        },
        "rename": {
          "dynamicRegistration": true,
          "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,
        "didChangeConfiguration": {
          "dynamicRegistration": false
        },
        "didChangeWatchedFiles": {
          "dynamicRegistration": true,
          "relativePatternSupport": true
        },
        "inlayHint": {
          "refreshSupport": true
        },
        "semanticTokens": {
          "refreshSupport": true
        },
        "symbol": {
          "dynamicRegistration": false,
          "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.10.1"
    },
    "initializationOptions": {},
    "processId": 54744,
    "rootPath": "/Users/fyc/toys/c++/playground/not_MVP",
    "rootUri": "file:///Users/fyc/toys/c++/playground/not_MVP",
    "trace": "off",
    "workDoneToken": "1",
    "workspaceFolders": [
      {
        "name": "/Users/fyc/toys/c++/playground/not_MVP",
        "uri": "file:///Users/fyc/toys/c++/playground/not_MVP"
      }
    ]
  }
}

I[21:48:48.149] <-- initialize(1)
V[21:48:48.149] Invoking /usr/bin/xcrun to find clang installation

V[21:48:48.154] Invoking /usr/bin/xcrun to find clang installation
I[21:48:48.159] --> reply:initialize(1) 10 ms
V[21:48:48.159] >>> {
  "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": "",
        "moreTriggerCharacter": []
      },
      "documentRangeFormattingProvider": true,
      "documentSymbolProvider": true,
      "executeCommandProvider": {
        "commands": [
          "clangd.applyFix",
          "clangd.applyTweak"
        ]
      },
      "foldingRangeProvider": true,
      "hoverProvider": true,
      "implementationProvider": 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",
            "comment"
          ]
        },
        "range": false
      },
      "signatureHelpProvider": {
        "triggerCharacters": [
          "(",
          ")",
          "{",
          "}",
          "<",
          ">",
          ","
        ]
      },
      "standardTypeHierarchyProvider": true,
      "textDocumentSync": {
        "change": 2,
        "openClose": true,
        "save": true
      },
      "typeDefinitionProvider": true,
      "typeHierarchyProvider": true,
      "workspaceSymbolProvider": true
    },
    "offsetEncoding": "utf-16",
    "serverInfo": {
      "name": "clangd",
      "version": "clangd version 16.0.2 (https://github.com/llvm/llvm-project 18ddebe1a1a9bde349441631365f0472e9693520) mac+grpc+xpc x86_64-apple-darwin23.2.0"
    }
  }
}

V[21:48:48.306] <<< {"jsonrpc":"2.0","method":"initialized","params":{}}

I[21:48:48.306] <-- initialized
V[21:48:48.306] <<< {"jsonrpc":"2.0","method":"textDocument/didOpen","params":{"textDocument":{"languageId":"cpp","text":"struct Foo {\
  Foo(int x) {}\
};\
\
int main() {\
  int x = 42;\
  Foo f(x);\
}\
","uri":"file:///Users/fyc/toys/c++/playground/not_MVP/not_MVP.cpp","version":0}}}

I[21:48:48.306] <-- textDocument/didOpen
E[21:48:48.306] Failed to load compilation database from /Users/fyc/toys/c++/playground/not_MVP/compile_commands.json: Missing key: "directory".

I[21:48:48.306] Failed to find compilation database for /Users/fyc/toys/c++/playground/not_MVP/not_MVP.cpp
I[21:48:48.306] ASTWorker building file /Users/fyc/toys/c++/playground/not_MVP/not_MVP.cpp version 0 with command clangd fallback
[/Users/fyc/toys/c++/playground/not_MVP]
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -resource-dir=/Users/fyc/.local/share/nvim/mason/packages/clangd/clangd_16.0.2/lib/clang/16 -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk -- /Users/fyc/toys/c++/playground/not_MVP/not_MVP.cpp

V[21:48:48.307] Driver produced command: cc1 -cc1 -triple x86_64-apple-macosx14.0.0 -Wundef-prefix=TARGET_OS_ -Werror=undef-prefix -Wdeprecated-objc-isa-usage -Werror=deprecated-objc-isa-usage -fsyntax-only -disable-free -clear-ast-before-backend -disable-llvm-verifier -discard-value-names -main-file-name not_MVP.cpp -mrelocation-model pic -pic-level 2 -mframe-pointer=all -ffp-contract=on -fno-rounding-math -funwind-tables=2 -target-sdk-version=14.2 -fcompatibility-qualified-id-block-type-checking -fvisibility-inlines-hidden-static-local-var -target-cpu penryn -tune-cpu generic -mllvm -treat-scalable-fixed-error-as-warning -debugger-tuning=lldb -target-linker-version 820.1 -fcoverage-compilation-dir=/Users/fyc/toys/c++/playground/not_MVP -resource-dir /Users/fyc/.local/share/nvim/mason/packages/clangd/clangd_16.0.2/lib/clang/16 -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk -cxx-isystem /opt/homebrew/Cellar/libomp/14.0.0/include -internal-isystem /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1 -internal-isystem /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/local/include -internal-isystem /Users/fyc/.local/share/nvim/mason/packages/clangd/clangd_16.0.2/lib/clang/16/include -internal-externc-isystem /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include -fdeprecated-macro -fdebug-compilation-dir=/Users/fyc/toys/c++/playground/not_MVP -ferror-limit 19 -stack-protector 1 -fblocks -fencode-extended-block-signature -fregister-global-dtors-with-atexit -fgnuc-version=4.2.1 -fcxx-exceptions -fexceptions -fmax-type-align=16 -no-round-trip-args -D__GCC_HAVE_DWARF2_CFI_ASM=1 -x c++ /Users/fyc/toys/c++/playground/not_MVP/not_MVP.cpp
V[21:48:48.307] Building first preamble for /Users/fyc/toys/c++/playground/not_MVP/not_MVP.cpp version 0
V[21:48:48.311] indexed preamble AST for /Users/fyc/toys/c++/playground/not_MVP/not_MVP.cpp version 0:
  symbol slab: 0 symbols, 120 bytes
  ref slab: 0 symbols, 0 refs, 128 bytes
  relations slab: 0 relations, 24 bytes
I[21:48:48.311] Indexing c++17 standard library in the context of /Users/fyc/toys/c++/playground/not_MVP/not_MVP.cpp
I[21:48:48.311] Built preamble of size 218244 for file /Users/fyc/toys/c++/playground/not_MVP/not_MVP.cpp version 0 in 0.00 seconds
I[21:48:48.311] --> workspace/semanticTokens/refresh(0)
V[21:48:48.311] >>> {"id":0,"jsonrpc":"2.0","method":"workspace/semanticTokens/refresh","params":null}

V[21:48:48.314] indexed file AST for /Users/fyc/toys/c++/playground/not_MVP/not_MVP.cpp version 0:
  symbol slab: 3 symbols, 4912 bytes
  ref slab: 3 symbols, 6 refs, 4320 bytes
  relations slab: 0 relations, 24 bytes
V[21:48:48.314] Build dynamic index for main-file symbols with estimated memory usage of 12680 bytes
I[21:48:48.314] --> textDocument/publishDiagnostics
V[21:48:48.314] >>> {"jsonrpc":"2.0","method":"textDocument/publishDiagnostics","params":{"diagnostics":[],"uri":"file:///Users/fyc/toys/c%2B%2B/playground/not_MVP/not_MVP.cpp","version":0}}

V[21:48:48.333] <<< {"id":2,"jsonrpc":"2.0","method":"textDocument/documentSymbol","params":{"textDocument":{"uri":"file:///Users/fyc/toys/c++/playground/not_MVP/not_MVP.cpp"}}}

I[21:48:48.333] <-- textDocument/documentSymbol(2)
V[21:48:48.333] ASTWorker running DocumentSymbols on version 0 of /Users/fyc/toys/c++/playground/not_MVP/not_MVP.cpp
I[21:48:48.333] --> reply:textDocument/documentSymbol(2) 0 ms
V[21:48:48.333] >>> {"id":2,"jsonrpc":"2.0","result":[{"children":[{"detail":"(int)","kind":9,"name":"Foo","range":{"end":{"character":15,"line":1},"start":{"character":2,"line":1}},"selectionRange":{"end":{"character":5,"line":1},"start":{"character":2,"line":1}}}],"detail":"struct","kind":23,"name":"Foo","range":{"end":{"character":1,"line":2},"start":{"character":0,"line":0}},"selectionRange":{"end":{"character":10,"line":0},"start":{"character":7,"line":0}}},{"detail":"int ()","kind":12,"name":"main","range":{"end":{"character":1,"line":7},"start":{"character":0,"line":4}},"selectionRange":{"end":{"character":8,"line":4},"start":{"character":4,"line":4}}}]}

V[21:48:48.356] <<< {"id":3,"jsonrpc":"2.0","method":"textDocument/semanticTokens/full","params":{"textDocument":{"uri":"file:///Users/fyc/toys/c++/playground/not_MVP/not_MVP.cpp"}}}

I[21:48:48.356] <-- textDocument/semanticTokens/full(3)
V[21:48:48.356] ASTWorker running SemanticHighlights on version 0 of /Users/fyc/toys/c++/playground/not_MVP/not_MVP.cpp
I[21:48:48.356] --> reply:textDocument/semanticTokens/full(3) 0 ms
V[21:48:48.356] >>> {"id":3,"jsonrpc":"2.0","result":{"data":[0,7,3,8,131075,1,2,3,8,36867,0,8,1,2,16387,3,4,4,3,131075,1,6,1,1,16387,1,2,3,8,131072,0,4,1,1,16387,0,2,1,1,16384],"resultId":"1"}}

V[21:48:48.357] <<< {"jsonrpc":"2.0","method":"$/cancelRequest","params":{"id":3}}

I[21:48:48.357] <-- $/cancelRequest
V[21:48:48.357] <<< {"id":4,"jsonrpc":"2.0","method":"textDocument/semanticTokens/full","params":{"textDocument":{"uri":"file:///Users/fyc/toys/c++/playground/not_MVP/not_MVP.cpp"}}}

I[21:48:48.357] <-- textDocument/semanticTokens/full(4)
V[21:48:48.357] ASTWorker running SemanticHighlights on version 0 of /Users/fyc/toys/c++/playground/not_MVP/not_MVP.cpp

I[21:48:48.357] --> reply:textDocument/semanticTokens/full(4) 0 ms
V[21:48:48.357] >>> {"id":4,"jsonrpc":"2.0","result":{"data":[0,7,3,8,131075,1,2,3,8,36867,0,8,1,2,16387,3,4,4,3,131075,1,6,1,1,16387,1,2,3,8,131072,0,4,1,1,16387,0,2,1,1,16384],"resultId":"2"}}

V[21:48:48.357] <<< {"id":0,"jsonrpc":"2.0","result":null}

I[21:48:48.357] <-- reply(0)

I[21:48:48.975] Indexed c++17 standard library: 10052 symbols, 2735 filtered

V[21:48:49.001] Build dynamic index for header symbols with estimated memory usage of 6274680 bytes

Thanks. Here is the textDocument/documentSymbol response that clangd is sending, formatted:
{
  "id": 2,
  "jsonrpc": "2.0",
  "result": [
    {
      "children": [
        {
          "detail": "(int)",
          "kind": 9,
          "name": "Foo",
          "range": {
            "end": {
              "character": 15,
              "line": 1
            },
            "start": {
              "character": 2,
              "line": 1
            }
          },
          "selectionRange": {
            "end": {
              "character": 5,
              "line": 1
            },
            "start": {
              "character": 2,
              "line": 1
            }
          }
        }
      ],
      "detail": "struct",
      "kind": 23,
      "name": "Foo",
      "range": {
        "end": {
          "character": 1,
          "line": 2
        },
        "start": {
          "character": 0,
          "line": 0
        }
      },
      "selectionRange": {
        "end": {
          "character": 10,
          "line": 0
        },
        "start": {
          "character": 7,
          "line": 0
        }
      }
    },
    {
      "detail": "int ()",
      "kind": 12,
      "name": "main",
      "range": {
        "end": {
          "character": 1,
          "line": 7
        },
        "start": {
          "character": 0,
          "line": 4
        }
      },
      "selectionRange": {
        "end": {
          "character": 8,
          "line": 4
        },
        "start": {
          "character": 4,
          "line": 4
        }
      }
    }
  ]
}

There are only three entries: one for the struct Foo, one for its constructor, and one for the function main.
I have no idea where neovim is getting the fourth entry in its outline view from, but it looks like it's not clangd. I would suggest filing a neovim issue for further investigation.

Makes sense, thanks for your prompt response! Will do.


False positive with ConstructorLeaksThis

Consider this class:
public final class Test {
    public Test() {
        this(0);
    }

    public Test(int i) {
        /* Field assignment irrelevant. */
    }
}

Running with -Xep:ConstructorLeaksThis:ERROR yields:
Test.java:3: error: [ConstructorLeaksThis] Constructors should not pass the 'this' reference out in method invocations, since the object may not be fully constructed.
        this(0);
        ^
    (see http://errorprone.info/bugpattern/ConstructorLeaksThis)
1 error

Have the same, SuppressWarnings also doesn't work, still prints the message in both ERROR and WARN cases.
public final class ConfigurationEntry
{
@Nonnull
private final Integer id;
@Nonnull
private final Instant lastChanged;
@Nonnull
private final Type type;
@Nullable
private final String value;
@SuppressWarnings("ConstructorLeaksThis")
public ConfigurationEntry(@Nonnull final Integer id, @Nonnull final Type type, @Nullable final String value)
{
this(id, type, value, Instant.now());
}
ConfigurationEntry(
@Nonnull final Integer id, @Nonnull final Type type,
@Nullable final String value, @Nonnull final Instant lastChanged
)
{
this.id = requireNonNull(id, "ID is required");
this.lastChanged = requireNonNull(lastChanged, "Last changed is required");
this.type = requireNonNull(type, "Type is required");
this.value = value;
}
}

Update: Warning suppression works if it is put to the enclosing class, not the the affected constructor.

@krisztiankocsis I filed #735 for that, as it's a separate issue.

(I just checked: the issue described in this ticket is still valid in version 2.1.1.)

Just hit this as well .. perhaps someone could merge https://github.com/google/error-prone/pull/789 some time, so that so this goes into the next release? Without this, ConstructorLeaksThis isn't really usable on our code base.

I think this issue was fixed in c2b37f4f5bc86d6736812ff4cc7f099615f561aa.

@sebright right you are!


[gyb] Get doctest to pass

What's in this pull request?
Mainly because of from __future__ import print_function, doctest was broken.
$ python -m doctest utils/gyb.py

In addition, currently, we always invoke utils/gyb with --test option.
https://github.com/apple/swift/blob/fc9c1f6a/cmake/modules/SwiftHandleGybSources.cmake#L41
This doesn't really work.
It used to test __main__ module of utils/gyb, but not gyb module of utils/gyb.py.

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    All supported platforms     | @swift-ci Please smoke test and merge
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    All supported platforms     | @swift-ci Please test and merge
    OS X platform               | @swift-ci Please test OS X platform
    OS X platform               | @swift-ci Please benchmark
    Linux platform              | @swift-ci Please test Linux platform

Lint Testing
    Language     | Comment
    ------------ | -------------
    Python       | @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

@swift-ci Please Python lint

@swift-ci Please test

@swift-ci Please Python lint

@swift-ci Please test

LGTM, thank you!


Error in cogs

This issue tracker is ONLY used for reporting bugs with topggpy. Feel free to share your suggestions in the #api channel in our Discord server!
For help with general Python issues, use StackOverflow, our #development channel, or the Python Discord server.

Expected Behavior

Should work fine
Current Behavior
Error

`  File "C:\Users\pc\python\lib\site-packages\discord\ext\commands\bot.py", line 644, in _load_from_module_spec
setup(self)
File "c:\Users\pc\projeler\bot\cogs\redditcommands.py", line 63, in setup
bot.add_cog(Redditcommands(bot))
File "c:\Users\pc\projeler\bot\cogs\redditcommands.py", line 12, in init
self.dbl = topgg.DBLClient(bot=self.bot, token=dbltoken)
File "C:\Users\pc\python\lib\site-packages\topgg\client.py", line 112, in init
self.http = HTTPClient(token, loop=self.loop, session=kwargs.get("session"))
File "C:\Users\pc\python\lib\site-packages\topgg\http.py", line 83, in init
self.rate_limiter = AsyncRateLimiter(
File "C:\Users\pc\python\lib\site-packages\topgg\ratelimiter.py", line 53, in init
self.__lock = asyncio.Lock()
File "C:\Users\pc\python\lib\asyncio\locks.py", line 81, in init
self._loop = events.get_event_loop()
File "C:\Users\pc\python\lib\asyncio\events.py", line 642, in get_event_loop
raise RuntimeError('There is no current event loop in thread %r.'
RuntimeError: There is no current event loop in thread 'MainThread'.
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "c:\Users\pc\projeler\bot\bot.py", line 61, in
bot.load_extension(f"cogs.{name}")
File "C:\Users\pc\python\lib\site-packages\discord\ext\commands\bot.py", line 704, in load_extension
self._load_from_module_spec(spec, name)
File "C:\Users\pc\python\lib\site-packages\discord\ext\commands\bot.py", line 649, in _load_from_module_spec
raise errors.ExtensionFailed(key, e) from e
discord.ext.commands.errors.ExtensionFailed: Extension 'cogs.redditcommands' raised an error: RuntimeError: There is no current event loop in thread 'MainThread'.`
Development Environment

3.9 ,1.0.1
Steps to Reproduce

1.Using top gg client in cog

Context

Votelocking command

Odd, I don't think this should happen. Did you by any chance call asyncio.run or something that closes the event loop?

Is there any update on this?


Install on Raspberry Pi

Hi everyone,
I'm trying to install @ngrok/ngrok (version 1.0.0) on a raspberry pi (Linux ARM release: 4.19.97-v7l+).
And I'm getting this error when I try to require the package in node:
Welcome to Node.js v16.17.0.
Type ".help" for more information.
> require('@ngrok/ngrok')
Uncaught:
Error<EMAIL_ADDRESS>cannot open shared object file: No such file or directory
    at Object.Module._extensions..node (node:internal/modules/cjs/loader:1210:18)
    at Module.load (node:internal/modules/cjs/loader:1004:32)
    at Function.Module._load (node:internal/modules/cjs/loader:839:12)
    at Module.require (node:internal/modules/cjs/loader:1028:19)
    at require (node:internal/modules/cjs/helpers:102:18) {
  code: 'ERR_DLOPEN_FAILED'
}

I've tried checking dependencies, verifying permissions, and reinstalling ngrok.
Any guidance on how to troubleshoot and resolve this issue?

Thank you!
I have a Raspberry Pi 4 Model B Rev 1.1 with 2GB ram and Linux ARM release: 4.19.97-v7l+.
I managed to build the binary locally, and it works. Thanks for the suggestion!
I guess there's a compatibility issue with the ngrok.linux-arm-gnueabihf.node file in the repo for my rpi version?

Hi here, I was not able to load a raspios 2020-05-28 with 4.19.118-v7+ on the 4, errors on boot due to the software being too old. This 2021-12-02 with 5.10.63-v7+ runs ngrok-javascript without issue.
I'm happy that compiling it locally is working since that's probably the way forward here, but out of curiosity, what distribution are you running with the older 4.19.97-v7l+ kernel?

I'm running Raspbian GNU/Linux 10 (buster).
This solution works fine for me. Thanks again!

Glad that solution is working for you! I'll close the issue, let us know if you run into anything else. Thanks!


.map is not a function

Uncaught TypeError: node.nodes.map is not a function
NPM web pack build is not converting to es5.

For others that get this error, the data structure being provided to the preview is probably not in the documented format. In my case, the value was an object, not an array (ie a single node).


Morpheus backward compatibility

Previous explainability updates to return of get_anomaly_score break current and previous version of Morpheus. This PR reverts back to original signature and adds new method that returns anomaly scores along with loss values. This will allow us to merge back into nv-updates branch which Morpheus currently uses.

This looks good to me. Should be backward compatible with current Morpheus, while still integrating Ex2.0.


Add documentation for cards

This PR adds documentation for cards. It is deployed on SherlockML.
page.py is becoming a bit unwieldy, so I might, as a separate PR, try to split it out into a page for each component.

This looks awesome!


Visitors are called to often

This should fix: https://github.com/fabric8io/kubernetes-client/issues/521

This should be fine now!


[QUESTION] 这个框架支持自定义java程序任务吗

*For better global communication, please give priority to using English description, thx! *
就是使用编写一个连接数据库的程序，Java来处理数据，都是这种任务，然后对这些任务进行依赖管理。
Describe the question
A clear and concise description of what the question is.
Which version of DolphinScheduler:
-[1.1.0-preview]
Additional context
Add any other context about the problem here.
**Requirement or improvement

Please describe about your requirements or improvement suggestions.

Please describe your problem in English.
You can package your java program into jar and run java task by shell.
你可以把你的java文件打成jar包然后创建并运行shell类型的任务。

Please describe your problem in English.
You can package your java program into jar and run java task by shell.

can this method solve your problem ? , or you can describe what function do you need
By the way, English is needed

No, I want to have something like an XXL-JOB executor, and I implement the logic of this class

No, I want to have something like an XXL-JOB executor, and I implement the logic of this class

could you give more information ?
I'm not familiar with xxl-job, please give some more  information about how to use , you can give some screenshot or someting

No, I want to have something like an XXL-JOB executor, and I implement the logic of this class

could you give more information ?
I'm not familiar with xxl-job, please give some more information about how to use , you can give some screenshot or someting

like this , through the RPC invoke the job executor in the other system.

No, I want to have something like an XXL-JOB executor, and I implement the logic of this class

could you give more information ?
I'm not familiar with xxl-job, please give some more information about how to use , you can give some screenshot or someting

like this , through the RPC invoke the job executor in the other system.

very good , could you give this document url?  it seems like task plugin, maybe I can study how to implement it better, thx

Thanks,I hope you can finish it, this is the url .
xxljob-BEAN

现在这个需求已经实现了吗？有同样的诉求


Script doesn't work due to headers error.

Login cookie never gets set due to the error : PHP Warning:  Cannot modify header information - headers already sent by (output started at /home/blah/edit.php:21)

Thanks for submitting this issue. Can you see if the commits I've made to master solve the problem?

New code gives error : PHP Parse error:  syntax error, unexpected '}', expecting end of file in /home/blah/TextEditor/TextEditor.php on line 89
Fixed by delete } at line 89.


Forgot the memory usage cost for serialiseData

A massive PR for the memory cost of serialiseData, which I forgot to do in #4480.  We have to account for the size of the serialized object as a function of the size of the input, so I've gone for a factor of 2 to account for any overhead.  A factor of 1 would probably be safe anyway though.

(I failed to update the cost-model-generation code here, but that's fixed in #4570.)


Configure on_unexpected_dn on ldap query

Codecov Report

Merging #306 into master will not change coverage by %.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master      #306   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           12        12
  Lines         1802      1812   +10
=========================================
+ Hits          1802      1812   +10

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 d7938d9...1281ee8. Read the comment docs.


Update to USING doc about libclang dep

That libclang is needed on the build host to use n2o4 is not obvious, but it wasn't mentioned in our documentation, creating a trivially easy stumbling block for new users. This pull request fixes that.
This closes issue #31.

Hmm, you have a point. I'll change the wording there.


Add Nodejs 10 Agent

yeah same as  4.1 ... not sure backporting a new feature like this to 3.11 is such a good idea
it hasn't even soaked in 4.3/master yet
is there some background here?
/hold

@gabemontero Nodejs 8 goes EOL end of this year, that's the only reason we are introducing this.

ok that is what I expected @waveywaves
but the established pattern is to introduce the new nodejs/maven in our newer releases and eventually remove the EOL ones
we explicitly did NOT backport newer nodejs/maven images to older openshift releases
for example, if you look at https://github.com/openshift/jenkins/tree/openshift-3.6, it doesn't even have nodejs8.... it has the old/original 4.4 version of nodejs
There are several concerns around such backports, which we would consider features.  QE coverage for example.
I would advise maintaining this pattern.  But perhaps a conversation between us, @akram , @siamaksade , is warranted.

/close


Create an issue template for the website issues

I see some issues without important informations when I added the new websites. I see two solutions to how to the reporters/senders know we need that

parameter url https://github.com/11ty/11ty.io/issues/new?title=I+built+a+site+with+Eleventy!&body=name:+Your+website+name,+source+url:+paste+the+url+of+your+repository+here+if+you+would+like+to+share+it+with+the+community,+description:+what+your+website+is+about,+twitter:+your+twitter+account+name+if+you+have+one
issue template to the websites https://help.github.com/en/articles/manually-creating-a-single-issue-template-for-your-repository

I prefer the second, what do you think?

Second one.
I was just opening an issue because everybody else did :-D
Could we state where those would show up?
What about adding a <meta generator> tag so that we could discover sites via crawler?
(Likely as plugin)

Sure, no problem, the website only have one link, and it is easy for that.

The Meta generator is a good idea, but I think it is an other issue to original eleventy repository

Alright! Let me prep a package for eleventy then :-)

eleventy-plugin-meta-generator

Correct me if I’m wrong but this was implemented!


Figure out why Encode[Exception] is often not picked up

Somehow the default instances from the Decode companion object is used. I guess it's something about priority. Hopefully there is a way to make it more pleasant for users. Right now they have to define an instance of Encode[Exception] right before the call to .toService.

Lots of changed around exceptions so I'm closing until reported again.


Fail with better error message if no terraform files exist in default location

similar to #114 if user tries to connect a digger action and there is no digger.yml file AND no terraform files exist in the root directory then no errors are shown to the user instead the following error is shown:
terraform plan failed. dir: .
2023/04/07 04:39:35 Error executing plan: terraform plan failed. exit status 1
Error: Process completed with exit code 1.

We would like to improve this by showing a clearer error message

I can take this one

Thank you! @fleroux514


405 —  Method not allowed — SO-184

This PR will make sure to throw a special exception in case the current path has been matched, but it wasn't possible to find an appropriate method.
We'll catch these exceptions and return the appropriate status codes in a follow up PR.
Highlights:

Dry some functions that were unexpectedly complicated and/or accumulating state over time (matchServer, randomPath)
Do not creare Error objects in place where they're not thrown, otherwise the stack trace is wrong and you have no idea where the exception happened. (This made me lose some time)
Refactored the route method to not accumulate the state over time with global booleans, but rather create a matches object and find the correct thing to do using a series of filters
Added tests for the new scenario.

SO-184

It's not related to this change, but something to keep in mind, is that these tests are complicated to read due to not really following describe-it syntax. They confiuse context and assertion in the title.
For example this:
 test('given a concrete matching server and unmatched templated path should not match', () => {

Should be:
describe('when server is valid', () => {
    describe('and templated path is nonsense', () => {
        it('throws a NO_METHOD_ERROR, () => {

Stuff like that. Then you can group constants for shared setup, and have more assertions in more clearly labeled its.
Learned all this in rspec land, I love the website http://betterspecs.org/ but not 100% of it is relevant to Jest ofc.

Interestingly I don't see 405in this PR, is there something else to be done? Can we test the status code? Or is there a nickname for the status code in Node?

@philsturgeon You're correct, the PR title is a little bit misleading. This PR throws an exception when the condition to return a 405 happen. The real status code is on a followup PR; the reason for this is that this already includes some refactors that are beneficial for the codebase; the whole thing together would just be too long to review.

Looks like we already had that error being returned.

No, this is incorrect. If you check the errors.ts constants you can see a new value has been added and the condition detected by reword the conditions order.

Interestingly I don't see 405in this PR, is there something else to be done? Can we test the status code? Or is there a nickname for the status code in Node?

That's what I said in the #prism channel ;) This PR doesn't return 405 it cleans some old code up which already threw an error in case method was not matched. If I understood correctly @XVincentX will return the 405 status code as part of resolving SO-141. Correct @XVincentX?
The thing I was confused about is why SO-185 was marked as won't fix and linked to SO-141 (which I think are two different things). As long as the end result is correct I don't care about ticket numbers though ;)

Yeah I take a lot of blame on this, I made some confusion with the Jira stuff.


Provide a way to remove a CodeLens in the resolveCodeLens

VSCode Version: Version 1.5.0-insider (1.5.0-insider) 538cd9ded5a471fbb20920f01eff9c8df4b83ee9
OS Version: OS X El Capitan Version 10.11.6 (15G31)

Sometimes you want the work to ultimately show a CodeLens to be deferred as much as possible, so it would be create if there was a way to signal that CodeLens being resolve isn't actually desired anymore.
For example, it might be desirable to not show a "references" CodeLens if there are no references (rather than having to say 'no references' or something like that). Basically for any CodeLens where the work involved in actually resolving it is too expensive in the providing phase.

Not convinced - whenever you remove or add a lens it moves the lines up or down. That's the reason  why we first gather all lens locations and then fill in the visible ones. In early versions of this feature we used to have what you describe and it was not fun to use.


test functionality through chat by another contact

how to create anther contact and test implemented functionality?
or
I would thankful if you share a scenario in order to test development functionality

regist contact
setting contact's username
search contact by username

regist contact   ------------> do it by add manually in user table in mysql or add in android client?
setting contact's username  ------------> do it in android client?
search contact by username ------------> do it in android client?


Pin local opam packages without confirmation for static dependencies

The opam pin -n . command was introduced to fix an issue with irmin packages. I'm not entirely sure how it will interact with the computation of static dependencies, but it would help if the pins were also available at this stage. (also added the -y to avoid confirmation)

Thanks @art-w!


VigEM not installed error

it says its not installed but ive got the latest version fo the vigembus driver, it doesnt see it. xoutput and the driver are both on disk c, can somebody please help?

Download vigem from here.
https://github.com/ViGEm/ViGEmBus/releases


Module 2 exercises [Edwina Asiedu Anderson]

Please "drag & drop" exercise 1 file below.

Please UPDATE THE TITLE of this "Issue" in the title bar above with your name.

If you haven't done so, please go back to Module 2 and make sure to
WS2_M2E2_Submission.docx
take
the post-training survey.

Well done, Edwina. You clearly grasped the material outlined in Module 2 and successfully applied it to these exercises. Thank you for your participation! Please be sure to fill out the post-Module survey before you begin the next Module.


I Have Updated the Font, Based on the desired outcome image now it's exactly matching with the solution and this Fixes #259 opened issue

…ixes #259 opened issue

Because

This Code changes will fix the font mismatch of opened issues Present in : Foundations 03 - Grouping Selectors: Wrong font style used for desired outcome image #259
This PR

Changes have done in README.md file and Solution.css file

In Solution.css file, font-family having 'Ascender Serif' and 'sans-serif' now.
In README.md file mentioned to use 'Ascender Serif' font for desired output.

Issue

Closes #259
Additional Information

Pull Request Requirements

[x] I have thoroughly read and understand The Odin Project Contributing Guide
[x] The title of this PR follows the location of change: brief description of change format, e.g. 01-flex-center: Update self check
[x] The Because section summarizes the reason for this PR
[x] The This PR section has a bullet point list describing the changes in this PR
[x] If this PR addresses an open issue, it is linked in the Issue section
[x] If applicable, I have ensured that the TOP solution files match the Desired Outcome image

this is not how we want to fix this issue.
I think it would be better to simply update the 'expected outcome' image, instead of replacing 'helvetica' with a different
font.
please update this PR.

Added Two commits with the requested changes. i think it's good to go now.


Update TracingDriver.java

This allows url prefixes other than "jdbc:tracing:" (in sub-classes).

Pull Request Test Coverage Report for Build 80

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.1%) to 25.041%

Totals

Change from base Build 76:
0.1%

Covered Lines:
151

Relevant Lines:
603

💛  - Coveralls


[BUG]: 4.0.1 not compatible with @sentry/react-native 4.1.2

Describe the bug
Trying to upgrade to Sentry RN 4+ following the merging of PR #109. Typing now seems to be broken for the transport property of Sentry.init() and it fails to work.
To Reproduce
import sentryTestkit from "sentry-testkit";
import * as Sentry from "@sentry/react-native";

const { testkit, sentryTransport } = sentryTestkit();

Sentry.init({
  dsn<EMAIL_ADDRESS>  enableNative: false,
  tracesSampleRate: 1,
  transport: sentryTransport // This line shows a type error
});

Type error:

TS2322: Type 'new (options: any) => Transport' is not assignable to type '(transportOptions: BrowserTransportOptions) => Transport'.   Type 'new (options: any) => Transport' provides no match for the signature '(transportOptions: BrowserTransportOptions): Transport'.  options.d.ts(212, 5): The expected type comes from property 'transport' which is declared here on type 'ReactNativeOptions'

Upon running:
Test suite failed to run

    TypeError: Cannot read properties of undefined (reading 'bind')

      19 | const { testkit, sentryTransport } = sentryTestkit()
      20 |
    > 21 | Sentry.init({
         |        ^
      22 |     dsn<EMAIL_ADDRESS>      23 |     enableNative: false,
      24 |     tracesSampleRate: 1,

      at Object.getNativeFetchImplementation (../../../node_modules/src/transports/utils.ts:77:1)
      at makeFetchTransport (../../../node_modules/src/transports/fetch.ts:12:1)
      at Object.transport (../../../node_modules/@sentry/react-native/src/js/client.ts:32:14)
      at new BaseClient (../../../node_modules/@sentry/src/baseclient.ts:108:1)
      at ReactNativeClient._createSuperInternal (../../../node_modules/@sentry/react-native/dist/js/client.js:34:311)
      at new ReactNativeClient (../../../node_modules/@sentry/react-native/src/js/client.ts:36:6)
      at initAndBind (../../../node_modules/@sentry/src/sdk.ts:34:1)
      at Object.init (../../../node_modules/@sentry/react-native/src/js/sdk.tsx:115:3)

Expected behavior
No typing error on the transport line, bootstrapping of Sentry.init() works.
Sentry Versions (please complete the following information):

Sentry: 4.1.2
Sentry-Testkit 4.0.1

I think this might be a Sentry issue, investigating further...

Okay, this does look to be sentry-testkit specific rather than a @sentry/react-native issue.
A test with<EMAIL_ADDRESS>doing a plain init in like this:
  Sentry.init({
    dsn<EMAIL_ADDRESS>    enableNative: false,
    tracesSampleRate: 1,
  });

will fail with TypeError: Cannot read properties of undefined (reading 'bind').
Adding<EMAIL_ADDRESS>custom transport allows this to work:
  const {sentryTransport} = sentryTestkit();

  Sentry.init({
    dsn<EMAIL_ADDRESS>    enableNative: false,
    tracesSampleRate: 1,
    transport: sentryTransport,
  });

Moving to<EMAIL_ADDRESS>without the transport results in the same error as<EMAIL_ADDRESS>so their behaviour doesn't seem to have changed.
However, adding<EMAIL_ADDRESS>transport doesn't fix the error this time.
Any ideas @mlmmn? I've uploaded a minimal repro here: https://github.com/liamjones/SentryTestkit4ReactNativeBug (just yarn then yarn test)

@liamjones i'm confused, there's a TS typing error or broken functionality?

@zivl sorry for the confusion; I originally thought it was just a typing issue and reported that but as I went further with the upgrade I discovered that the functionality is actually broken with @sentry/react-native

thanks @liamjones - I'll take a look at your repo and we'll see how to deal with it.
i'll update here once i have more insights...
@liamjones, @mlmmn - you are more than welcome to do the same and share here yours of course

@liamjones I think I understand the issue:
when @sentry/react-native is initialized it checks for the native transport layer (i.e. device network connection) and since in test environment it does not exist - it falls back to @sentry/browser's makeFetchTransport function directly (see here).
In addition, after setting the transport layer for the sentry (native) client, it overrides external options.transport definition, so the options sent to super(options) (The BaseClient as defined in @sentry/core) are actually not as given in the Sentry.init(...)
The real issue is that @sentry/react-native is not checking for external transport function coming from options: ReactNativeOptions which I think is a bug as they need to support or according to their docs.
I will open a bug/PR for Sentry guys and let's see what their opinion on this

a PR has been created: https://github.com/getsentry/sentry-react-native/pull/2398

Thank zivl. Separately, I've confirmed the types are incorrect for V7 and have opened PR #116 to resolve that.

a fix has been released in<EMAIL_ADDRESS>


Portfolio data

Hi, it's possible to view portfolio data such as available amount, assets value etc..., simply the data in the bottom bar in the portfolio section of etoro dashboard.
Thanks

Hi, sorry for late answer, i haben‘t found such api yet, will inform a soon as i find it


Use Font Awesome from Storyboard

Is there any way to use this from storyboard directly?

@funkenstrahlen There is no way at the moment. You have to do it in code.


Export module or set global variable, but not both

This prevents the library from being both exported and set as a global variable in a webpack build.

Merged in #21 and released as 1.0.3


Fix DataProtection Backup Vaults

It seams that Microsoft.DataProtection API has an issue with some storage configurations.
when storageSettings.datastoreType is set to SnapshotStore the deployment will fail.

Issue in Bicep Docu:
https://github.com/Azure/bicep-types-az/issues/1194


Clarify unique refresh token behavior

I found the existing docs to be a little vague and had to read the source and experiment with the unique and revocable flags to figure out exactly how this works. I think this will be a little more clear.

Thanks!


[Refactor codebase]

Use const for constant constructors
fix the naming convention of files and folders
remove unused files
Making code short where possible

@Roshaen You can assign me to it under JWOC

Sure
Go for it @sarkartanmay393


Capture Volume widget should be able to load a blank scene

It seems that after first loading the widget there is no "blinking" out of the GUI for subsequent reloads. It might be a good way to keep things smoother and avoid complications.
perhaps a simple solution is to have the widget take a controller rather than a camera_array/point_estimates, then perform the checks internally to figure out what to do....
And I think if I do this then I don't really need be doing anything terribly fancy when running checks to enable / disable tabs

I haven't been duplicating this blinking problem lately. not really a priority


Introduce Google Forms connector with examples and tests

Implement the Google Forms connector for Ballerina.

Client Implementation

Add GoogleFormsClient class with methods to create, retrieve, and update Google Forms.
Define types for Form, Question, Response, UpdateForm, UpdateQuestion, and Error.

Documentation

Update Module.md and Package.md with an overview, setup guide, quickstart, and examples.
Add examples in examples/README.md for creating, retrieving, and updating Google Forms.

Examples

Add example1.bal to demonstrate creating a Google Form.
Add example2.bal to demonstrate retrieving responses from a Google Form.
Add example3.bal to demonstrate updating a Google Form.

Tests

Add client_test.bal to implement a test suite covering core functionalities of the Google Forms connector.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Cleanup usage of unwrap() in re_data_store

What
Part of #6330
Removes or explicitly allows unwrap() where it makes sense.
Checklist

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

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

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

PR Build Summary
Recent benchmark results
Wasm size tracking

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

@emilk As I don't have write access - how do you guys handle usually external contributions? Do I need to check the other boxes or do anything else, or will you take over from here?

Our CI for external contributors is slightly broken: https://github.com/rerun-io/rerun/issues/1994
The checkboxes you have control over though

Haha, okay.
I just meant what are the guideline for the checkboxes? The first two are obvious but when is it necessary to e.g. test the web demos or when to add something to the checklist, what's a good PR title, etc? And I can't change the labels anyway.
So should I always just leave the remaining checkboxes unchecked or just check them all?
And thanks!


Fix the path of seed_nodes configuration

@neuyilan Thanks. It's done.

Hi, please fix the conflict

Hi, @qiaojialin . Thanks for your comment. It's done.


request logging: add "early" log messages and timing information

This does two things to flask app request logging:

If the zipkin is_sampled property is set on the request, will cause a log message to be emitted when flask receives a request (before_request). This could be useful in cases where the app for some reason doesn't manage to log its request completing.
Adds timing information to the existing after_request log events. This should allow us to deduce how much time is spent queueing for a python thread/process.

:steam_locomotive: :train: :train:

Just wait till we get python 3.7 and I add thread_time too https://docs.python.org/3/library/time.html#time.thread_time


Add auto completion for attribute tags

This PR implements https://github.com/microsoft/vscode-html-languageservice/issues/115
It makes use of the existing CompletionConfiguration.attributeDefaultValue to decide whether "" or '' should be used.
I think the completion function could be made simpler if invalid html can be ignored (e.g. <a foo== )

Thanks @jzyrobert !


Make marray constexpr compatible

Adding the constexpr specifier to methods of the device_array class template to make the following compile:
constexpr sycl::marray<float, 3> v{0.0f, 0.0f, 0.0f};

Currently, this fails to compile:
constexpr_test.cpp: error: constexpr variable 'v' must be initialized by a constant expression
        constexpr sycl::marray<float, 3> v{0.0f, 0.0f, 0.0f};
                                         ^~~~~~~~~~~~~~~~~~~
/bin/../include/AdaptiveCpp/CL/../hipSYCL/sycl/libkernel/marray.hpp:56:7: note: non-constexpr function 'operator[]' cannot be used in a constant expression
      _data[offset] = x;
      ^
/bin/../include/AdaptiveCpp/CL/../hipSYCL/sycl/libkernel/marray.hpp:65:5: note: in call to '&v->init_offset(0, 0.F)'
    init_offset(current_offset, arg);
    ^
/bin/../include/AdaptiveCpp/CL/../hipSYCL/sycl/libkernel/marray.hpp:100:6: note: in call to '&v->initialize_from_arg(current_offset, 0.F)'
    (initialize_from_arg(current_offset, args), ...);
     ^
constexpr_test.cpp: note: in call to 'marray(0.F, 0.F, 0.F)'
        constexpr sycl::marray<float, 3> v{0.0f, 0.0f, 0.0f};
                                         ^
/bin/../include/AdaptiveCpp/CL/../hipSYCL/sycl/libkernel/detail/device_array.hpp:46:6: note: declared here
  T& operator[] (size_t i) noexcept

Thanks for the PR.
I tried to compile your example (constexpr sycl::marray<float, 3> v{0.0f, 0.0f, 0.0f};) with AdaptiveCpp built from your branch but I still get a compile error since the marray constructors are not marked constexpr.
I opened #1102 a while ago which basically is this PR + a few additional changes in marray.hpp. I actually thought it was already merged but there seems to be one small issue in #1102 that needs to be fixed, I'll have a look at that right away and then we can merge #1102 and probably close this PR. Sorry for the unnecessary work...

You're absolutely right, I just looked at the error message that said something about non constexpr constructors and thought that it referred to the marray constructors. I actually complains about the device_array constructors. The class device_array<T,N> is specialised for N=1,2,3,4. And the (implictly defined) default constructor for these specialised classes are not automatically constexpr. That's why I zero-initialised all the entries for these cases (see e.g. here).

Oh, I see. My Apple clang compiler on macOS did not complain about this. Sorry, so far I haven't tested my solution on any other platform.

As a new user of AdaptiveCpp, I wasn't familiar with the test suite. But let me take a look and add a test case to my pull request. Thanks.
I expect the test will fail on most platforms due to the issue you mentioned. I will then make the necessary code changes to fix it.

As I said earlier, the missing changes are already included in #1102 (which is just not merged yet). So there's no need for you to do the extra work

I see. Thanks for the clarification. Then I am closing this PR.


[WIP] Add support uploading files from url

 UploadClient: add the support of url uploads in fileFrom

 UploadClient: fix progress of fileFrom


Bugfix/Set correct merge policy

JIRA URL
https://spothero.atlassian.net/browse/IOS-2029
Description
Fixes crashing caused by merge conflicts by defining the merge policy to use the stored data instead of in-memory data.
Mimics Vokoder merge policy: https://github.com/vokal/Vokoder/blob/71b4dbec7a6a53d7403ecb1af71efab6364bc388/Pod/Classes/VOKCoreDataManager.m#L218

What do you mean by "all cases"? To mimic the Vokoder implementation, we would set it whenever the defaultContext var was accessed and returned.

But I'm thinking maybe you mean to leave it and allow the user to define it where needed?

Right. UtilityBelt is meant to be a CoreData abstraction, not a 1:1 Vokoder replacement or the CoreData layer specific to SpotHero. We could implement this in Attendant Hero, for example.
If we do that, should this be a variable that is passed in, or is it recommended that we set it here in all cases?
If we want to set it in all cases, can you comment in the code as to why?
Happy to support either way, just lacking context!

Alright, I'm following. In that case, I am feeling that I will close this and define the policy from the SpotHero app.

Sounds good!


Writing CHROM directly rather than truncating the "chr" prefix

As a user, I want the chromosome (CHROM) string to be stored exactly as it is stored in the original VCF so that I know for sure whether a particular chromsome was labeled in the VCF as eg chr19 or 19 or otherwise.

I think I originally did this for space-saving reasons. Maybe if this becomes a problem in the future, the main records table could store a truncated version and include a reference out to some kind of pattern (e.g. chr* to indicate a leading "chr" prefix) but that seems like unnecessary for now


License requirements

Can you please provide details about licensing of Microsoft Search?

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

ID: 0af30bbd-1bc5-5026-87d9-8aa40de2489e
Version Independent ID: ffb6b68d-57ff-270e-1b63-d7175a5b61d3
Content: FAQs
Content Source: MicrosoftSearch/faqs.md
Service: mssearch
GitHub Login: @jeffkizn
Microsoft Alias: jeffkizn

Microsoft Search is part of Office 365. There are no specific licensing requirements on top of Office 365 SKUs.

There is definitelly need for E3/E5 to use connectors. Do you need office 365 suite (Business/F/E/A) or can you use Microsoft Search with SPO plan 1 standalone?

There are features where specific license requirements may be needed, like Connectors. These cases are called out in the specific documentation section for those features. SPO plan 1 does allow for the use of Microsoft Search.

Thanks @jeffkizn. Do you think it would make sense to add my question and your answers to this FAQ?

As a general rule, we try to stay away from that when there isn't anything specific about the feature and is just part of Office 365 SKUs. But it's something we'll look at with the appropriate teams and determine if it makes sense. Thanks for your comments; I appreciate it.


Gdal extension has a dependency on DotSpatial.Data.Forms

This issue was imported from CodePlex
BjartN wrote 2011-01-26 at 15:53
Isn't the gdal extension dependency on DotSpatial.Data.Forms a violation of the architectural principles ?
http://dotspatial.codeplex.com/SourceControl/changeset/view/6298da964438#DotSpatial.Data.Rasters.GdalExtension%20-%20GDAL%201.7%2fDotSpatial.Data.Rasters.GdalExtension64%2fDotSpatial.Data.Rasters.Gdal1-7Extension64.csproj
Shade1974 wrote 2011-01-26 at 19:30
Great question. Is this true only for the Gdal1-7Extension64.csproj? It may be an oversight. This new implementation was contributed I think by Tidyup and others, so it may just be in there because it starts out in there by default and they didn't bother
to remove the reference. I don't think there is anything in the library itself that requires System.Windows.Forms. This is probably a very easy fix by simply removing the reference.
Ted
mudnug wrote 2011-01-26 at 20:13
It looks like the issue appears in the 32 and 64 versions.
GdalRasterProvider depends on RasterExt.Open() in DotSpatial.Data.Forms
Shade1974 wrote 2011-01-26 at 21:28
Oh. Um...hmm. What that does is show a dialog box allowing a user to navigate to a raster file. The same thing happens in the DataManager control though, and that definitely should have System.Windows.Forms available to it. So I'm not exactly sure why
the raster provider itself would need to do that. It is probably a useless appendix at this point, and stems from an earlier time when things were organized differently. If your feeling up to it Mathew, what might be appropriate is to modify the code so that
the RasterProvider would no longer ever launch a dialog like that. If necessary we can shift any content up to the DataManager or even the AppManager if necessary. Either an event or something else might be necessary, but honestly, I'm having trouble thinking
of the use case where the RasterProvider would ever open that dialog itself.
Ted

Not actual


Installing CST in SAS EG

Hello,
I'm trying to install the open source CST to use in SAS EG. I've installed Apache ANT and downloaded the v1.7.5 release package. In the config.properties file (C:\Program Files\SASHome\SASStudioSingleUser\3.8\war\config), I've added the following.
#---SAS Clinical Standards toolkit
SET CSTHOME C:Users\Y.D.Dang_pc\Documents\SAS CST\cstFrameworkLibrary
CSTGLOBALLIB C:Users\Y.D.Dang_pc\Documents\SAS CST\cstGlobalLibrary
CSTSAMPLELIB C:Users\Y.D.Dang_pc\Documents\SAS CST\cstSampleLibrary
insert sasautos '!CSTHOME/macros'
JREOPTIONS (-Dsas.app.class.dirs=!CSTHOME/jar)
SET CLASSPATH !CSTHOME/jar
I'm currently however unable to run any of the programs. E.g. if I run cstvalidate I'm getting the following message:
WARNING: Apparent symbolic reference _CST_RC not resolved.
ERROR: A character operand was found in the %EVAL function or %IF condition where a numeric operand is required. The condition was:
&_cst_rc
ERROR: The macro CSTVALIDATE will stop executing.

Is the config file the correct one as I'm using SAS EG.
If correct should I add a '-' before each line. E.g. -SET CSTHOME.... ( It is originally added in the txt file in sctFrameworklibrary)
I'm not able to stop server. Is it automatically stopped if I close SAS EG? A local server on my machine is used.
Any other points that I've missed that might cause these errors?

Thanks,
Yen

I'm not sure about EG configurations but I did notice that your paths are missing a slash: C:Users... should be C:\Users...

Thanks,
But it's still not working. I've added the slash and an include to run the cstFramework programs and initialized the global macro variables,
But I'm still getting a fatal error in cstvalidate and several libraries can not be found.
Added in SAS program:
%include "C:\Users\Y.D.Dang_pc\Documents\SAS CST\cstFrameworkLibrary\macros*.sas";
/*
initialize the global macro variables needed by the framework
/
Options macrogen symbolgen mlogic mprint mfile;
%cst_setstandardproperties(
_cstStandard=CST-FRAMEWORK
,_cstSubType=initialize
);
/
initialize the global macro variables needed by CDISC SDTM
*/
..............
Part of SAS log:
27         /%include "C:\cstFrameworkLibrary\macros*.sas";/
28         /%include "C:\Users\Y.D.Dang_pc\Documents\SAS CST\cstFrameworkLibrary\macros\cstvalidate.sas";/
29         %include "C:\Users\Y.D.Dang_pc\Documents\SAS CST\cstFrameworkLibrary\macros*.sas";
MLOGIC(CSTVALIDATE):  Beginning execution.
MLOGIC(CSTVALIDATE):  Parameter _CSTCALLINGPGM has value Unspecified
MLOGIC(CSTVALIDATE):  Parameter _CSTREPORTOVERRIDE has value N
SYMBOLGEN:  Macro variable _CST_RC resolves to 1
MLOGIC(CSTVALIDATE):  %IF condition &_cst_rc is TRUE
MLOGIC(CSTVALIDATE):  %PUT ****************************************************************

MLOGIC(CSTVALIDATE):  %PUT ERROR: Fatal error encountered, validation process cannot start.
ERROR: Fatal error encountered, validation process cannot start.
..............
MPRINT(CSTUTIL_CREATETEMPMESSAGES):   set _cst5154.standards (where=( (upcase(standard)="CST-FRAMEWORK") AND
(upcase(isStandardDefault)="Y") ));
ERROR: Library _CST5154 does not exist.
...........
MPRINT(CSTUTIL_CREATETEMPMESSAGES):   * Include the generated code;
SYMBOLGEN:  Macro variable _CSTNEXTCODE resolves to _cst0371
ERROR: Catalog WORK._CST0371 does not exist.
ERROR: Cannot open %INCLUDE file _CST0371.

let's start by seeing what's actually defined in your SAS session for CST.  Start your SAS session and run this code.
``
%put %sysget(CSTHOME);
%put %sysget(CLASSPATH);
proc options
option=cstgloballib
option=cstsamplelib
option=sasautos
option=jreoptions;
run;

You need to add the CST config statements to the SAS configuration file.  SASHOME/SASFoundation/9.4/nls/en/sasv9.cfg.

I've addit to the sasV9 file, but I get the same result.
If I add csthome and classpath in windows as system environment variables I do get a path for csthome and classpath, but the cstgloballib and cstsamplelib are still empty.
Added in sasv9.cfg:
/* This is the ANSI character set (for SAS Monospace font and ANSI Sasfont) */
-FORMCHAR '82838485868788898A8B8C2B3D7C2D2F5C3C3E2A'x
-CSTGLOBALLIB C:\Users\Y.D.Dang_pc\Documents\SAS CST\cstGlobalLibrary
-CSTSAMPLELIB C:\Users\Y.D.Dang_pc\Documents\SAS CST\cstSampleLibrary
-insert sasautos '!CSTHOME/macros'
-JREOPTIONS (-Dsas.app.class.dirs=!CSTHOME/jar)
/---------------------------------------------------------------
| WARNING:  INSTALL Application edits below this line.  User     |
|           options should be added above this box comment.      |
|           INSTALL Application maintains and modifies the       |
|           following options; -SASAUTOS, -SASHELP, -SASMSG,     |
|           -PATH, and -MAPS.  It also maintains and modifies    |
|           the following CONFIG variables with the -SET option; |
|           INSTALL, USAGE, LIBRARY, SAMPSIO, SAMPSRC, SASCBT,   |
|           and SASEXT01-SASEXT50.  It preserves all lines above |
|           the line containing 'DO NOT EDIT BELOW THIS LINE'.   |
---------------------------------------------------------------/
/* DO NOT EDIT BELOW THIS LINE - INSTALL Application edits below this line /
/ * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * */
SAS log:
25         GOPTIONS ACCESSIBLE;
26         %put %sysget(CSTHOME);
C:\Users\Y.D.Dang_pc\Documents\SAS CST\cstFrameworkLibrary
27         %put %sysget(CLASSPATH);
C:\Users\Y.D.Dang_pc\Documents\SAS CST\jar
28
29         proc options
30         option=cstgloballib
31         option=cstsamplelib
32         option=sasautos
33         option=jreoptions;
34         run;
SAS (r) Proprietary Software Release 9.4  TS1M6

CSTGLOBALLIB=     Specifies the location of the SAS Clinical Standards Toolkit global library.
CSTSAMPLELIB=     Specifies the location of the SAS Clinical Standards Toolkit sample library.
SASAUTOS=SASAUTOS Specifies the location of one or more autocall libraries.
JREOPTIONS=(             -DPFS_TEMPLATE=C:\Program Files\SASHome\SASFoundation\9.4\tkjava\sasmisc\qrpfstpt.xml
-Djava.class.path=C:\PROGRA~1\SASHome\SASVER~1\eclipse\plugins\SASLAU~1.JAR          -Djava.security.auth.login.config=C:\Program
Files\SASHome\SASFoundation\9.4\tkjava\sasmisc\sas.login.config          -Djava.security.policy=C:\Program
Files\SASHome\SASFoundation\9.4\tkjava\sasmisc\sas.policy          -Djava.system.class.loader=com.sas.app.AppClassLoader
-Dlog4j.configuration=file:/C:/Program%20Files/SASHome/SASFoundation/9.4/tkjava/sasmisc/sas.log4j.properties
-Dsas.app.class.path=C:\PROGRA~1\SASHome\SASVER~1\eclipse\plugins\tkjava.jar          -Dsas.ext.config=C:\Program
Files\SASHome\SASFoundation\9.4\tkjava\sasmisc\sas.java.ext.config
-Dsas.jre.libjvm=C:\PROGRA~1\SASHome\SASPRI~1\9.4\jre\bin\server\jvm.dll
-Dtkj.app.launch.config=C:\PROGRA~1\SASHome\SASVER~1\picklist          -Xms128m          -Xmx128m           )
Specifies the Java Runtime Environment options for SAS.

Maybe of additional note I use the sasv9.cfg in the u8 file.
In the C:\Program Files\SASHome\SASFoundation\9.4\sasv9.csf file I've specified: -config "C:\Program Files\SASHome\SASFoundation\9.4\nls\u8\sasv9.cfg" instead of 'en'
But if I add the config statements to the u8 sasv9.cfg file then I get an error 'A connection to the server could not be established'.


[rule suggestion] ban-syntax

I often use ESLint's no-restricted-syntax rule which allows users to pass in node types which should never be used in the app's code. Does TSLint already possess this capability?
The ESLint config is pretty intuitive:
"rules": {
        "ban-syntax": [true, ["GetAccessor", "DeleteExpression"]]
}

Possible duplicate of #2497.
Currently there is no such rule. It shouldn't be too hard to implement (depending on the complexity of selectors the rule supports initially).
The configuration is probably the difficult part. There is a strong opinion against AST node names in the config, see https://github.com/palantir/tslint/pull/3238#issuecomment-342610651

I can understand the concern about config confusion, and, as you said, a custom rule implementation is not too difficult. Won't bother me if you want to close this out.

as you said, a custom rule implementation is not too difficult.

I didn't mean to say this should be a custom rule. I don't have a strong opinion whether it belongs to TSLint core or a custom rules package. That depends on the decision of @adidahiya if he would accept such a rule.

I'm generally 👎  on rules that expose internals of the AST in their configuration like this; I don't think they're user-friendly enough.

Lets close this out, since we're avoiding using AST in configuration.


turksatkablo.com.tr

https://www.turksatkablo.com.tr/userUpload/EPG/b.json?_=1636034936820
https://www.turksatkablo.com.tr/yayin-akisi-program-detay.aspx?d=4&m=11&y=2021&kID=283&eID=196444373822
This can be found on webgrabplus site pack

Already on the list, but disabled due to unstable site performance.
https://github.com/iptv-org/epg/tree/master/sites/turksatkablo.com.tr


Feature/data directory

Adding a data directory option

Hi,
first of all, I have to apologize that I did not respond earlier. Somehow I did not notice all the pull requests that were open. I am sorry about that.
Second, thanks for contributing. Merging your other pull requests regarding the log dir made this one un-mergeable. Would you mind fixing it? I promise this time I will be merging it much quicker :)
Thanks.
-Tobias

No worries, it's happened to me on some projects too. I just updated my fork so it should be able to merge now. Thanks for sharing the work for these RPMs.

Thanks. Great that it was useful for someone else :)


Instantiate standardized accounts from account seed

Currently, when using methods for creating standard accounts (e.g., via create_basic_wallet or create_basic_fungible_faucet), we require users to supply init_seed.  This init_seed is then used to compute account_seed with which to instantiate the account. The search for account_seed is resource-intensive, and thus, it could take a while before the right account seed is found.
This means that we can use the methods mentioned above to create new accounts from scratch, but we can't use them to create accounts with an already-known account seed. The latter would be useful for things like genesis blocks, mock data, and probably other things.
So, it addition to functions like create_basic_wallet, we can add another function which would look something like this:
pub fn create_basic_wallet_from_account_seed(
    account_seed: Word,
    auth_scheme: AuthScheme,
    account_type: AccountType,
) -> Result<Account, AccountError>

These functions can then be used to instantiate standard accounts from human-readable descriptions like this:
{
    "type": "basic_wallet",
    "seed": "0x1245",
    "auth": {
        "type": "RpoFalcon512",
        "pub_key": "0x12456"
    },
    "mutable_code": true,
    "storage_mode": "local"
}

Closing this as we've decided to take a different approach with genesis block generation.


[PECO-237] Direct results support (WIP)

Easier to review commit by commit. First few commits contain some preparation work
Direct results is a Databricks feature that allows to reduce count of requests made by client in order to fetch data. With this feature, server will execute query, and if possible immediately return operation status, metadata, and part or all the data. If it was possible to return all the data - it will also automatically close operation, otherwise it's clients' responsibility to fetch the rest and close the operation. In other words, depending on what server was able to do, different parts of response may or may not be populated. Client should use what's available and use the "usual" mechanism to get the rest.
This PR adds generic direct results support and enables it for DBSQLSession.executeStatement. Some other methods of DBSQLSession (like getCatalogs/getSchemas/getTables also could use this feature, but in order to keep this PR smaller I'll enable it in a follow-up PR.

[x] Add direct results support to DBSQLSession.executeStatement
[ ] Update/add tests

I'm still working on tests for this feature, but considering that I did a lot of manual testing, as well as e2e still pass, - I doubt I'll need to add more changes to the code. So you're welcome to review the code 🙂

Codecov Report

Merging #51 (ee2ec28) into main (37c8035) will decrease coverage by 0.94%.
The diff coverage is 95.48%.

@@            Coverage Diff             @@
##             main      #51      +/-   ##
==========================================
- Coverage   94.56%   93.61%   -0.95%
==========================================
  Files          48       50       +2
  Lines         754      642     -112
  Branches       68       77       +9
==========================================
- Hits          713      601     -112
- Misses         18       21       +3
+ Partials       23       20       -3

Impacted Files
Coverage Δ

lib/DBSQLSession.ts
96.07% <88.88%> (-3.93%)
:arrow_down:

lib/DBSQLOperation/FetchResultsHelper.ts
93.75% <93.75%> (ø)

lib/DBSQLOperation/OperationStatusHelper.ts
94.73% <94.73%> (ø)

lib/DBSQLOperation/index.ts
94.87% <96.29%> (+1.93%)
:arrow_up:

lib/DBSQLOperation/CompleteOperationHelper.ts
100.00% <100.00%> (ø)

lib/DBSQLOperation/SchemaHelper.ts
100.00% <100.00%> (ø)

lib/contracts/IOperation.ts
100.00% <100.00%> (ø)

lib/hive/Types/index.ts
100.00% <100.00%> (ø)

lib/connection/transports/HttpTransport.ts
66.66% <0.00%> (-20.84%)
:arrow_down:

lib/connection/auth/NoSaslAuthentication.ts
40.00% <0.00%> (-17.15%)
:arrow_down:

... and 36 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Codecov Report

Merging #51 (b061d14) into main (37c8035) will decrease coverage by 0.27%.
The diff coverage is 97.54%.

@@            Coverage Diff             @@
##             main      #51      +/-   ##
==========================================
- Coverage   94.56%   94.29%   -0.28%
==========================================
  Files          48       50       +2
  Lines         754      648     -106
  Branches       68       79      +11
==========================================
- Hits          713      611     -102
- Misses         18       19       +1
+ Partials       23       18       -5

Impacted Files
Coverage Δ

lib/DBSQLOperation/FetchResultsHelper.ts
93.75% <93.75%> (ø)

lib/DBSQLOperation/OperationStatusHelper.ts
95.55% <95.55%> (ø)

lib/DBSQLOperation/CompleteOperationHelper.ts
100.00% <100.00%> (ø)

lib/DBSQLOperation/SchemaHelper.ts
100.00% <100.00%> (ø)

lib/DBSQLOperation/index.ts
100.00% <100.00%> (+7.05%)
:arrow_up:

lib/DBSQLSession.ts
100.00% <100.00%> (ø)

lib/contracts/IOperation.ts
100.00% <100.00%> (ø)

lib/hive/Types/index.ts
100.00% <100.00%> (ø)

lib/connection/transports/HttpTransport.ts
66.66% <0.00%> (-20.84%)
:arrow_down:

lib/connection/auth/NoSaslAuthentication.ts
40.00% <0.00%> (-17.15%)
:arrow_down:

... and 36 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Codecov Report
Base: 94.57% // Head: 94.30% // Decreases project coverage by -0.26% :warning:

Coverage data is based on head (6a3a9be) compared to base (8bbf410).
Patch coverage: 97.54% of modified lines in pull request are covered.

:exclamation: Current head 6a3a9be differs from pull request most recent head 780a12e. Consider uploading reports for the commit 780a12e to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #51      +/-   ##
==========================================
- Coverage   94.57%   94.30%   -0.27%
==========================================
  Files          48       50       +2
  Lines         756      650     -106
  Branches       69       80      +11
==========================================
- Hits          715      613     -102
- Misses         18       19       +1
+ Partials       23       18       -5

Impacted Files
Coverage Δ

lib/DBSQLOperation/FetchResultsHelper.ts
93.75% <93.75%> (ø)

lib/DBSQLOperation/OperationStatusHelper.ts
95.55% <95.55%> (ø)

lib/DBSQLOperation/CompleteOperationHelper.ts
100.00% <100.00%> (ø)

lib/DBSQLOperation/SchemaHelper.ts
100.00% <100.00%> (ø)

lib/DBSQLOperation/index.ts
100.00% <100.00%> (+7.05%)
:arrow_up:

lib/DBSQLSession.ts
100.00% <100.00%> (ø)

lib/contracts/IOperation.ts
100.00% <100.00%> (ø)

lib/hive/Types/index.ts
100.00% <100.00%> (ø)

lib/connection/transports/HttpTransport.ts
66.66% <0.00%> (-20.84%)
:arrow_down:

lib/connection/auth/NoSaslAuthentication.ts
40.00% <0.00%> (-17.15%)
:arrow_down:

... and 36 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Custom TypeScript types for better RDF/JS compatibility

My goal was to make the the types generated by wasm more compatible with RDF/JS Dataset types. For example, term implementations are expected to have a string literal termType and not a string. The TypeScript compiler complains about this.
Rather than writing ugly wrappers in my TypeScript, I tried to fix the generated .d.ts here. In model.rs and store.rs I marked the term classes, the Store class, and two functions to skip_typescript in wasm_bindgen, then provided a typescript_custom_section with more specific types, per the approach suggested in this comment.
For reference, the RDF/JS reference types are in data-model.d.ts and dataset.d.ts.
I did my best with the Store class by analyzing the code. I'm relatively inexperienced with Rust. Corrections would obviously be welcome. I didn't try to make the Rust Store methods return this, since Store isn't a complete DatasetCore anyway without a quad iterator implementation.
The resulting .d.ts:
/* tslint:disable */
/* eslint-disable */
/**
* @param {string} value
* @returns {NamedNode}
*/
export function namedNode(value: string): NamedNode;
/**
* @param {string | undefined} [value]
* @returns {BlankNode}
*/
export function blankNode(value?: string): BlankNode;
/**
* @returns {DefaultGraph}
*/
export function defaultGraph(): DefaultGraph;
/**
* @param {string} value
* @returns {Variable}
*/
export function variable(value: string): Variable;
/**
* @param {any} subject
* @param {any} predicate
* @param {any} object
* @returns {Quad}
*/
export function triple(subject: any, predicate: any, object: any): Quad;
/**
* @param {any} original
* @returns {any}
*/
export function fromTerm(original: any): any;
/**
* @param {any} original
* @returns {any}
*/
export function fromQuad(original: any): any;
/**
*/
export function main(): void;

export function literal(value: string | undefined, languageOrDataType?: string | NamedNode): Literal;
export function quad(subject: Quad_Subject, predicate: Quad_Predicate, object: Quad_Object, graph: Quad_Graph): Quad;

export class BlankNode {
    readonly termType: "BlankNode";
    readonly value: string;

    equals(other: Term | null | undefined): boolean;
    toString(): string;
}

export class DefaultGraph {
    readonly termType: "DefaultGraph";
    readonly value: "";

    equals(other: Term | null | undefined): boolean;
    toString(): string;
}

export class Literal {
    readonly datatype: NamedNode;
    readonly language: string;
    readonly termType: "Literal";
    readonly value: string;

    equals(other: Term | null | undefined): boolean;
    toString(): string;
}

export class NamedNode {
    readonly termType: "NamedNode";
    readonly value: string;

    equals(other: Term | null | undefined): boolean;
    toString(): string;
}

export interface BaseQuad {
    readonly graph: Term;
    readonly object: Term;
    readonly predicate: Term;
    readonly subject: Term;
    readonly termType: "Quad";
    readonly value: "";

    equals(other: Term | null | undefined): boolean;
    toString(): string;
}

export class Quad implements BaseQuad {
    readonly graph: Quad_Graph;
    readonly object: Quad_Object;
    readonly predicate: Quad_Predicate;
    readonly subject: Quad_Subject;
    readonly termType: "Quad";
    readonly value: "";

    equals(other: Term | null | undefined): boolean;
    toString(): string;
}

export type Quad_Graph = DefaultGraph | NamedNode | BlankNode | Variable;
export type Quad_Object = NamedNode | Literal | BlankNode | Quad | Variable;
export type Quad_Predicate = NamedNode | Variable;
export type Quad_Subject = NamedNode | BlankNode | Quad | Variable;

export type Term = NamedNode | BlankNode | Literal | Variable | DefaultGraph | BaseQuad;

export class Variable {
    readonly termType: "Variable";
    readonly value: string;

    equals(other: Term | null | undefined): boolean;
    toString(): string;
}

export class Store {
    readonly size: number;

    constructor(quads?: Quad[]);

    add(quad: Quad): void;

    delete(quad: Quad): void;

    dump(
        options: {
            format: string;
            from_graph_name?: BlankNode | DefaultGraph | NamedNode;
        },
        from_graph_name?: BlankNode | DefaultGraph | NamedNode
    ): string;

    has(quad: Quad): boolean;

    load(
        data: string,
        options: {
            base_iri?: NamedNode | string;
            format: string;
            no_transaction?: boolean;
            to_graph_name?: BlankNode | DefaultGraph | NamedNode;
        },
        base_iri?: NamedNode | string,
        to_graph_name?: BlankNode | DefaultGraph | NamedNode
    ): void;

    match(subject?: Term | null, predicate?: Term | null, object?: Term | null, graph?: Term | null): Quad[];

    query(
        query: string,
        options?: {
            base_iri?: NamedNode | string;
            results_format?: string;
            use_default_graph_as_union?: boolean;
        }
    ): boolean | Map<string, Term>[] | Quad[];

    update(
        update: string,
        options?: {
            base_iri?: NamedNode | string;
        }
    ): void;
}

@Tpt I wondered why wasm-pack is not in the package.json devDependencies? I added it in my local checkout so the build script would work but didn't commit my changes.

@Tpt I went ahead and changed the tests to TypeScript, which revealed a couple of type issues in the custom TypeScript declarations. I was concerned about that with the initial PR. I'm glad you nudged me in that direction.
I changed the tests to use vitest instead of Mocha. It handles TypeScript a little more gracefully. I enabled defineGlobals in the vitest config so the rdfjs-datamodel Mocha tests (which assume global describe and it) still run.

Sadly CI seems to be broken because of a limitation of getrandom with ES modules).

I found the right incantation to work around this:
import { webcrypto } from "node:crypto";
vi.stubGlobal("crypto", webcrypto);

where vi is imported from vitest.


DFE-816 Changes to BDC  terra branding

Made changes to BDC Terra logos, favicon and primary accent color

@kilonzi did you optimize the SVGs ( yarn optimize-image-svg)?

@kilonzi did you optimize the SVGs ( yarn optimize-image-svg)?

@kilonzi some reference info in case it helps

As an aside, it may be good to move the this Confluence content to the Contributor Guide wiki with its own section.

@cahrens Thank you for the review. I have optimized them.


bump node.js to v.20 for all C3 workflows

The C3 e2es (both experimental and not) tests for Nuxt using yarn under ubuntu seem to be consistently failing on every PR that runs them.
By looking at the logs it looks like Nuxt is incompatible with the version of node that we're using in our workflows:

So in this PR I am simply bumping the node version used by all the C3 workflows as that should be pretty safe to do I think.
I did not change the default node version for all workflows as I assume that we have a specific reason as to why we want to use 18.20.2 there (if not I am happy to change that value instead)

Tests

[ ] TODO (before merge)
[ ] Tests included
[x] Tests not necessary because: this is just a CI change

E2E Tests CI Job required? (Use "e2e" label or ask maintainer to run separately)

[ ] I don't know
[x] Required
[ ] Not required because:

Public documentation

[ ] TODO (before merge)
[ ] Cloudflare docs PR(s):
[x] Documentation not necessary because: this is just a CI change

Wrangler v3 currently supports Node v16+ as stated in the docs. But we are changing it to 18+ in v4 following the Nodejs support window (https://nodejs.org/en/about/previous-releases). So the wrangler workflow should probably stay in node16 for now.
But if we are just changing the c3 tests for frameworks to use node 18, i think it is fine?

Wrangler v3 currently supports Node v16+ as stated in the docs. But we are changing it to 18+ in v4 following the Nodejs support window (https://nodejs.org/en/about/previous-releases). So the wrangler workflow should probably stay in node16 for now.

The value I was referring to is the default one for the install-dependecies action:
https://github.com/cloudflare/workers-sdk/blob/ab7204a6eb8f5bab00172a6a2623251ba2d757ba/.github/actions/install-dependencies/action.yml#L6
So, I think that it should be the one most commonly used across all the various GitHub workflows.
There are a few gh workflows that use the action: GitHub search, I am not too involved/familiar with the monorepo so I cannot really say what default would make most sense without digging deeper into things a bit.
Interestingly the wrangler e2es are already purposely run under node 18 actually (instead of 16):
https://github.com/cloudflare/workers-sdk/blob/ab7204a6eb8f5bab00172a6a2623251ba2d757ba/.github/workflows/e2e.yml#L23

But if we are just changing the c3 tests for frameworks to use node 18, i think it is fine?

yeah I do think so, alternatively we skip the nuxt+yarn+ubuntu tests for the time being, but I would personally prefer to just bump the node version as I think we can reasonably expect people to use a relatively newer version of node when scaffolding a new application.
Actually 20 is not an LTS, so I wonder if it would be better to just straight jump to 22 🤔

One thing to note is that c3 has support for node 18 and up:
https://github.com/cloudflare/workers-sdk/blob/ab7204a6eb8f5bab00172a6a2623251ba2d757ba/packages/create-cloudflare/package.json#L91
Anyways I am fine with whatever the team prefers 🙂

One thing to note is that c3 has support for node 18 and up:

In that case I think c3 workflow should use node 18 in general, but node 20+ just for framework tests. We have no control over the node version requirements of the frameworks but the rest of the template should remain supported with node 18.

In that case I think c3 workflow should use node 18 in general, but node 20+ just for framework tests. We have no control over the node version requirements of the frameworks but the rest of the template should remain supported with node 18.

This makes sense to me 👍 , unfortunately C3 e2es run all together, we don't currently have a way to run separately the ones that use frameworks from the ones that don't 🥲
Of course we could implement that, but it would, in my opinion, require quite some refactoring and make the e2es process generally more complicated, so I don't think that it would be worth it 😕
Personally I would go with just using node 20+ (or 22+ as I mentioned) and:

as I mentioned assume that people do use modern node versions for new apps scaffolding
assume that if things work fine with node 20+/22+ then most likely they run well with node 18+ (since we don't use any newer fancy node feature as far as I know)
on the next major version of C3 we bump the node requirement accordingly realigning everything

Closing in favour of #7649 (turns out a non-controversial patch bump was enough 🤦)


obs-backgroundremoval: reinit at 0.5.16

Description of changes
Closes https://github.com/NixOS/nixpkgs/issues/219332
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2051

@ofborg build obs-studio-plugins.obs-backgroundremoval


sql: allow YMD, DMY for DateStyle as a session variable

PR: https://github.com/cockroachdb/cockroach/pull/68093
From release notes:

When the date value is out of range, a hint now suggests that the user try a different DateStyle. [#68093][#68093] {% comment %}doc{% endcomment %}

Hint, doesn't need explicit docs