Folding with multiple trailing content

Describe the bug
When a function takes multiple trailing content block arguments, folding is only applied to the first one.

Note: I've pointed out some inaccuracies in this report template with ‼ below, HIH
Package/Software version:
VSCode version(Help -> About):
‼ In my case this is Code -> About Visual Studio Code
Version: 1.92.0 (Universal)
Commit: b1c0a14de1414fcdaa400695b4db1c0799bc3124
Date: 2024-07-31T23:26:45.634Z
Electron: 30.1.2
ElectronBuildId: 9870757
Chromium: 124.0.6367.243
Node.js: 20.14.0
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 23.4.0

tinymist extension version: v0.11.0. Get it by tinymist --version in terminal.
‼ tinymist isn't in my path after installing the extension, I had to run it like this ~/.vscode/extensions/myriad-dreamin.tinymist-0.11.18-darwin-arm64/out/tinymist --version
tinymist
Build Timestamp:     2024-08-04T19:30:39.635429000Z
Build Git Describe:  v0.11.18
Commit SHA:          fb0a300bc2ef8cfb74a62100441fa4a3f648f4b2
Commit Date:         None
Commit Branch:       None
Cargo Target Triple: aarch64-apple-darwin
Typst Version:       0.11.1

Logs:
tinymist server log(Output Panel -> tinymist):
‼ Output Panel -> Tinymist Typst Language Server
[2024-08-05T17:31:09Z INFO  tinymist] starting LSP server: LspArgs {
        mirror: MirrorArgs {
            mirror: "",
            replay: "",
        },
        font: CompileFontArgs {
            font_paths: [],
            ignore_system_fonts: false,
        },
    }
[2024-08-05T17:31:09Z INFO  sync_lsp] handling initialize - (0) at Instant { tv_sec: 1538136, tv_nsec: 863740916 }
[2024-08-05T17:31:09Z INFO  tinymist::init] preferred theme: Some("light") {"compileStatus": String("enable"), "exportPdf": String("never"), "formatterMode": String("disable"), "formatterPrintWidth": Number(120), "onEnterEvent": Bool(true), "outputPath": String(""), "preferredTheme": String("light"), "preview": Object {"cursorIndicator": Bool(false), "fontPaths": Array [], "invertColors": Null, "partialRendering": Bool(true), "pinPreviewFile": Bool(false), "refresh": String("onType"), "scrollSync": String("onSelectionChangeByMouse"), "showInActivityBar": Bool(false), "sysInputs": Object {}, "systemFonts": Bool(true)}, "previewFeature": String("enable"), "semanticTokens": String("enable"), "systemFonts": Bool(true), "trace": Object {"server": String("off")}, "typstExtraArgs": Array []}
[2024-08-05T17:31:09Z INFO  tinymist::server] LanguageState: initialized with config Config { compile: CompileConfig { roots: ["/Users/carlos/Documents/Util", "/Users/carlos/Desktop"], output_path: PathPattern(""), export_pdf: Never, root_path: None, font_opts: CompileFontArgs { font_paths: [], ignore_system_fonts: false }, system_fonts: Some(true), font_paths: [], fonts: OnceCell(Uninit), notify_status: true, periscope_args: None, typst_extra_args: Some(CompileExtraOpts { root_dir: None, entry: None, inputs: {}, font: CompileFontArgs { font_paths: [], ignore_system_fonts: false }, creation_timestamp: None }), preferred_theme: Some("light"), has_default_entry_path: false, lsp_inputs: {"x-preview": "{\"version\":1,\"theme\":\"light\"}"} }, semantic_tokens: Enable, formatter: Disable, formatter_print_width: 120 }
[2024-08-05T17:31:09Z INFO  tinymist::server] LanguageState: initialized with const_config ConstConfig { position_encoding: Utf16, cfg_change_registration: true, tokens_dynamic_registration: true, tokens_overlapping_token_support: false, tokens_multiline_token_support: false, doc_line_folding_only: true, doc_fmt_dynamic_registration: true }
[2024-08-05T17:31:09Z INFO  tinymist::actor] TypstActor: creating server for primary, entry: Workspace { root: "/Users/carlos/Documents/Util", main: None }, inputs: {"x-preview": "{\"version\":1,\"theme\":\"light\"}"}
[2024-08-05T17:31:09Z INFO  tinymist::init] creating SharedFontResolver with CompileFontArgs { font_paths: [], ignore_system_fonts: false }
[2024-08-05T17:31:09Z INFO  sync_lsp] handled  initialize - (0) in 11.41ms
[2024-08-05T17:31:09Z INFO  sync_lsp] notifying initialized - at Instant { tv_sec: 1538137, tv_nsec: 4559250 }
[2024-08-05T17:31:09Z INFO  tinymist::server] server initialized
[2024-08-05T17:31:09Z INFO  sync_lsp] notifing initialized succeeded in 1.44ms
[2024-08-05T17:31:09Z INFO  sync_lsp] handling workspace/executeCommand - (1) at Instant { tv_sec: 1538137, tv_nsec: 7089083 }
[2024-08-05T17:31:09Z INFO  sync_lsp] handled  workspace/executeCommand - (1) in 26.05ms
[2024-08-05T17:31:09Z INFO  sync_lsp] handling workspace/executeCommand - (2) at Instant { tv_sec: 1538137, tv_nsec: 33204541 }
[2024-08-05T17:31:09Z INFO  tinymist::actor::typ_client] the entry file of TypstActor(primary) is changing to Workspace { root: "/Users/carlos/Desktop", main: Some(/test.typ) }
[2024-08-05T17:31:09Z INFO  tinymist::tool::preview] PreviewTask(riz83r): arguments: PreviewCliArgs {
        preview: PreviewArgs {
            data_plane_host: "<IP_ADDRESS>:0",
            control_plane_host: "",
            enable_partial_rendering: true,
            invert_colors: "never",
            task_id: "riz83r",
            refresh_style: OnType,
        },
        compile: CompileOnceArgs {
            input: Some(
                "/Users/carlos/Desktop/test.typ",
            ),
            root: None,
            inputs: [],
            font: CompileFontArgs {
                font_paths: [],
                ignore_system_fonts: false,
            },
            creation_timestamp: None,
        },
        preview_mode: Document,
        static_file_host: "<IP_ADDRESS>:0",
        not_as_primary: false,
        dont_open_in_browser: false,
    }
[2024-08-05T17:31:09Z INFO  sync_lsp] notifying textDocument/didOpen - at Instant { tv_sec: 1538137, tv_nsec: 35535666 }
[2024-08-05T17:31:09Z INFO  tinymist::server] did open Url { scheme: "file", cannot_be_a_base: false, username: "", password: None, host: None, port: None, path: "/Users/carlos/Desktop/test.typ", query: None, fragment: None }
[2024-08-05T17:31:09Z INFO  typst_preview] Previewer: typst actor spawned
[2024-08-05T17:31:09Z INFO  typst_preview] Data plane server listening on: <IP_ADDRESS>:59011
[2024-08-05T17:31:09Z DEBUG typst_preview::actor::typst] TypstActor: waiting for message
[2024-08-05T17:31:09Z INFO  tinymist::server] create source: "/Users/carlos/Desktop/test.typ"
[2024-08-05T17:31:09Z INFO  sync_lsp] notifing textDocument/didOpen succeeded in 885.96µs
[2024-08-05T17:31:09Z INFO  sync_lsp] handling workspace/executeCommand - (3) at Instant { tv_sec: 1538137, tv_nsec: 36961916 }
[2024-08-05T17:31:09Z INFO  tinymist::cmd] first manual focusing is coming
[2024-08-05T17:31:09Z INFO  sync_lsp] handled  workspace/executeCommand - (3) in 8.96µs
[2024-08-05T17:31:09Z INFO  tinymist::tool::preview] PreviewTask(riz83r): static file server listening on: <IP_ADDRESS>:59012
[2024-08-05T17:31:09Z INFO  sync_lsp] handled  workspace/executeCommand - (2) in 300.09ms
[2024-08-05T17:31:09Z INFO  sync_lsp] handling workspace/executeCommand - (4) at Instant { tv_sec: 1538137, tv_nsec: 333291041 }
[2024-08-05T17:31:09Z INFO  sync_lsp] handled  workspace/executeCommand - (4) in 747.21µs
[2024-08-05T17:31:09Z INFO  sync_lsp] handling textDocument/codeAction - (5) at Instant { tv_sec: 1538137, tv_nsec: 334058916 }
[2024-08-05T17:31:09Z INFO  sync_lsp] handling textDocument/documentColor - (6) at Instant { tv_sec: 1538137, tv_nsec: 334101958 }
[2024-08-05T17:31:09Z INFO  sync_lsp] notifying $/cancelRequest - at Instant { tv_sec: 1538137, tv_nsec: 334112083 }
[2024-08-05T17:31:09Z WARN  sync_lsp] unhandled notification: $/cancelRequest
[2024-08-05T17:31:09Z INFO  sync_lsp] handling textDocument/codeAction - (7) at Instant { tv_sec: 1538137, tv_nsec: 334134041 }
[2024-08-05T17:31:09Z INFO  sync_lsp] handling textDocument/foldingRange - (8) at Instant { tv_sec: 1538137, tv_nsec: 334144208 }
[2024-08-05T17:31:09Z INFO  tinymist_query::syntax::lexical_hierarchy] lexical hierarchy analysis took 46.292µs
[2024-08-05T17:31:09Z INFO  sync_lsp] handled  textDocument/foldingRange - (8) in 372.71µs
[2024-08-05T17:31:10Z INFO  sync_lsp] notifying $/setTrace - at Instant { tv_sec: 1538137, tv_nsec: 410459791 }
[2024-08-05T17:31:10Z WARN  sync_lsp] unhandled notification: $/setTrace
[2024-08-05T17:31:10Z INFO  sync_lsp] notifying workspace/didChangeConfiguration - at Instant { tv_sec: 1538137, tv_nsec: 410757625 }
[2024-08-05T17:31:10Z INFO  sync_lsp] notifing workspace/didChangeConfiguration succeeded in 44.63µs
[2024-08-05T17:31:10Z INFO  tinymist::init] preferred theme: Some("light") {"compileStatus": String("enable"), "exportPdf": String("never"), "fontPaths": Null, "formatterMode": String("disable"), "formatterPrintWidth": Number(120), "hoverPeriscope": Null, "outputPath": String(""), "preferredTheme": String("light"), "rootPath": Null, "semanticTokens": String("enable"), "systemFonts": Bool(true), "typstExtraArgs": Array []}
[2024-08-05T17:31:10Z INFO  tinymist::server] new settings applied
[2024-08-05T17:31:10Z INFO  sync_lsp] notifying $/setTrace - at Instant { tv_sec: 1538137, tv_nsec: 439526458 }
[2024-08-05T17:31:10Z WARN  sync_lsp] unhandled notification: $/setTrace
[2024-08-05T17:31:10Z INFO  sync_lsp] notifying workspace/didChangeConfiguration - at Instant { tv_sec: 1538137, tv_nsec: 439546833 }
[2024-08-05T17:31:10Z INFO  sync_lsp] notifing workspace/didChangeConfiguration succeeded in 20.83µs
[2024-08-05T17:31:10Z INFO  sync_lsp] notifying $/cancelRequest - at Instant { tv_sec: 1538137, tv_nsec: 441229750 }
[2024-08-05T17:31:10Z WARN  sync_lsp] unhandled notification: $/cancelRequest
[2024-08-05T17:31:10Z INFO  sync_lsp] handling textDocument/codeAction - (9) at Instant { tv_sec: 1538137, tv_nsec: 441245250 }
[2024-08-05T17:31:10Z INFO  sync_lsp] notifying $/cancelRequest - at Instant { tv_sec: 1538137, tv_nsec: 444101583 }
[2024-08-05T17:31:10Z WARN  sync_lsp] unhandled notification: $/cancelRequest
[2024-08-05T17:31:10Z INFO  sync_lsp] handling textDocument/codeAction - (10) at Instant { tv_sec: 1538137, tv_nsec: 444118541 }
[2024-08-05T17:31:10Z INFO  tinymist::init] preferred theme: Some("light") {"compileStatus": String("enable"), "exportPdf": String("never"), "fontPaths": Null, "formatterMode": String("disable"), "formatterPrintWidth": Number(120), "hoverPeriscope": Null, "outputPath": String(""), "preferredTheme": String("light"), "rootPath": Null, "semanticTokens": String("enable"), "systemFonts": Bool(true), "typstExtraArgs": Array []}
[2024-08-05T17:31:10Z INFO  tinymist::server] new settings applied
[2024-08-05T17:31:10Z INFO  sync_lsp] notifying $/setTrace - at Instant { tv_sec: 1538137, tv_nsec: 490294875 }
[2024-08-05T17:31:10Z WARN  sync_lsp] unhandled notification: $/setTrace
[2024-08-05T17:31:10Z INFO  sync_lsp] notifying workspace/didChangeConfiguration - at Instant { tv_sec: 1538137, tv_nsec: 490322125 }
[2024-08-05T17:31:10Z INFO  sync_lsp] notifing workspace/didChangeConfiguration succeeded in 20.67µs
[2024-08-05T17:31:10Z INFO  sync_lsp] notifying $/setTrace - at Instant { tv_sec: 1538137, tv_nsec: 510514125 }
[2024-08-05T17:31:10Z WARN  sync_lsp] unhandled notification: $/setTrace
[2024-08-05T17:31:10Z INFO  sync_lsp] notifying workspace/didChangeConfiguration - at Instant { tv_sec: 1538137, tv_nsec: 510560166 }
[2024-08-05T17:31:10Z INFO  sync_lsp] notifing workspace/didChangeConfiguration succeeded in 59.75µs
[2024-08-05T17:31:10Z INFO  tinymist::init] preferred theme: Some("light") {"compileStatus": String("enable"), "exportPdf": String("never"), "fontPaths": Null, "formatterMode": String("disable"), "formatterPrintWidth": Number(120), "hoverPeriscope": Null, "outputPath": String(""), "preferredTheme": String("light"), "rootPath": Null, "semanticTokens": String("enable"), "systemFonts": Bool(true), "typstExtraArgs": Array []}
[2024-08-05T17:31:10Z INFO  tinymist::server] new settings applied
[2024-08-05T17:31:10Z INFO  tinymist::init] preferred theme: Some("light") {"compileStatus": String("enable"), "exportPdf": String("never"), "fontPaths": Null, "formatterMode": String("disable"), "formatterPrintWidth": Number(120), "hoverPeriscope": Null, "outputPath": String(""), "preferredTheme": String("light"), "rootPath": Null, "semanticTokens": String("enable"), "systemFonts": Bool(true), "typstExtraArgs": Array []}
[2024-08-05T17:31:10Z INFO  tinymist::server] new settings applied
[2024-08-05T17:31:10Z INFO  sync_lsp] handling textDocument/codeLens - (11) at Instant { tv_sec: 1538137, tv_nsec: 589783666 }
[2024-08-05T17:31:10Z INFO  typst_preview] Peer address: <IP_ADDRESS>:59015
[2024-08-05T17:31:10Z INFO  typst_preview] New WebSocket connection: <IP_ADDRESS>:59015
[2024-08-05T17:31:10Z DEBUG typst_preview::actor::render] OutlineRenderActor: waiting for message
[2024-08-05T17:31:10Z DEBUG typst_preview::actor::render] RenderActor: waiting for message
[2024-08-05T17:31:10Z DEBUG typst_preview::actor::render] RenderActor: has_full_render: true
[2024-08-05T17:31:10Z INFO  typst_preview::actor::render] RenderActor: document is not ready
[2024-08-05T17:31:10Z DEBUG typst_preview::actor::render] RenderActor: waiting for message
[2024-08-05T17:31:10Z DEBUG typst_preview::actor::render] OutlineRenderActor: received message: RenderFullLatest
[2024-08-05T17:31:10Z INFO  typst_preview::actor::render] OutlineRenderActor: document is not ready
[2024-08-05T17:31:10Z DEBUG typst_preview::actor::render] OutlineRenderActor: waiting for message
[2024-08-05T17:31:10Z INFO  sync_lsp] handling textDocument/semanticTokens/full - (12) at Instant { tv_sec: 1538137, tv_nsec: 695148125 }
[2024-08-05T17:31:10Z INFO  sync_lsp] handled  textDocument/semanticTokens/full - (12) in 742.25µs
[2024-08-05T17:31:10Z INFO  sync_lsp] notifying $/cancelRequest - at Instant { tv_sec: 1538137, tv_nsec: 787330166 }
[2024-08-05T17:31:10Z WARN  sync_lsp] unhandled notification: $/cancelRequest
[2024-08-05T17:31:10Z INFO  sync_lsp] handling textDocument/codeAction - (13) at Instant { tv_sec: 1538137, tv_nsec: 787355708 }
[2024-08-05T17:31:10Z INFO  sync_lsp] handled  textDocument/codeAction - (9) in 364.81ms
[2024-08-05T17:31:10Z INFO  tinymist::actor::editor] received status request(primary) Compiling
[2024-08-05T17:31:10Z INFO  sync_lsp] handled  textDocument/codeAction - (7) in 479.37ms
[2024-08-05T17:31:10Z INFO  sync_lsp] handled  textDocument/documentColor - (6) in 479.50ms
[2024-08-05T17:31:10Z INFO  sync_lsp] handled  textDocument/codeAction - (5) in 490.72ms
[2024-08-05T17:31:10Z INFO  sync_lsp] handled  textDocument/codeAction - (13) in 37.59ms
[2024-08-05T17:31:10Z INFO  sync_lsp] handled  textDocument/codeLens - (11) in 238.67ms
[2024-08-05T17:31:10Z INFO  sync_lsp] handled  textDocument/codeAction - (10) in 386.21ms
[2024-08-05T17:31:10Z INFO  sync_lsp] notifying $/cancelRequest - at Instant { tv_sec: 1538137, tv_nsec: 841647500 }
[2024-08-05T17:31:10Z WARN  sync_lsp] unhandled notification: $/cancelRequest
[2024-08-05T17:31:10Z INFO  typst_ts_compiler::diag::console] Some(/test.typ): compilation succeeded in 208.592ms
[2024-08-05T17:31:10Z INFO  tinymist::actor::editor] received diagnostics from primary:5: diag(Some(0))
[2024-08-05T17:31:10Z INFO  tinymist::actor::editor] received status request(primary) CompileSuccess
[2024-08-05T17:31:10Z DEBUG typst_preview::actor::render] RenderActor: has_full_render: false
[2024-08-05T17:31:10Z DEBUG typst_preview::actor::render] OutlineRenderActor: received message: RenderIncremental
[2024-08-05T17:31:10Z DEBUG typst_preview::actor::render] OutlineRenderActor: sending outline
[2024-08-05T17:31:10Z DEBUG typst_preview::actor::render] OutlineRenderActor: waiting for message
[2024-08-05T17:31:10Z INFO  tinymist::task::cache] CacheEvictTask: evict cache in 2.379875ms
[2024-08-05T17:31:10Z DEBUG typst_preview::actor::render] RenderActor: waiting for message
[2024-08-05T17:31:10Z INFO  tinymist::actor::editor] received status request(primary) Compiling
[2024-08-05T17:31:10Z INFO  typst_ts_compiler::diag::console] Some(/test.typ): compilation succeeded in 13.887ms
[2024-08-05T17:31:10Z INFO  tinymist::actor::editor] received diagnostics from primary:6: diag(Some(0))
[2024-08-05T17:31:10Z INFO  tinymist::actor::editor] received status request(primary) CompileSuccess
[2024-08-05T17:31:10Z DEBUG typst_preview::actor::render] OutlineRenderActor: received message: RenderIncremental
[2024-08-05T17:31:10Z DEBUG typst_preview::actor::render] OutlineRenderActor: sending outline
[2024-08-05T17:31:10Z DEBUG typst_preview::actor::render] OutlineRenderActor: waiting for message
[2024-08-05T17:31:10Z DEBUG typst_preview::actor::render] RenderActor: has_full_render: false
[2024-08-05T17:31:10Z INFO  tinymist::task::cache] CacheEvictTask: evict cache in 44.666µs
[2024-08-05T17:31:10Z DEBUG typst_preview::actor::render] RenderActor: waiting for message
[2024-08-05T17:31:10Z INFO  sync_lsp] notifying $/setTrace - at Instant { tv_sec: 1538138, tv_nsec: 213666750 }
[2024-08-05T17:31:10Z WARN  sync_lsp] unhandled notification: $/setTrace
[2024-08-05T17:31:10Z INFO  sync_lsp] notifying workspace/didChangeConfiguration - at Instant { tv_sec: 1538138, tv_nsec: 213710833 }
[2024-08-05T17:31:10Z INFO  sync_lsp] notifing workspace/didChangeConfiguration succeeded in 155.88µs
[2024-08-05T17:31:10Z INFO  tinymist::init] preferred theme: Some("light") {"compileStatus": String("enable"), "exportPdf": String("never"), "fontPaths": Null, "formatterMode": String("disable"), "formatterPrintWidth": Number(120), "hoverPeriscope": Null, "outputPath": String(""), "preferredTheme": String("light"), "rootPath": Null, "semanticTokens": String("enable"), "systemFonts": Bool(true), "typstExtraArgs": Array []}
[2024-08-05T17:31:10Z INFO  tinymist::server] new settings applied
[2024-08-05T17:31:11Z INFO  sync_lsp] handling textDocument/codeLens - (14) at Instant { tv_sec: 1538138, tv_nsec: 394878791 }
[2024-08-05T17:31:11Z INFO  sync_lsp] handled  textDocument/codeLens - (14) in 665.75µs
[2024-08-05T17:31:11Z INFO  sync_lsp] handling textDocument/codeAction - (15) at Instant { tv_sec: 1538138, tv_nsec: 439824666 }
[2024-08-05T17:31:11Z INFO  sync_lsp] handled  textDocument/codeAction - (15) in 835.75µs
[2024-08-05T17:31:11Z INFO  sync_lsp] handling textDocument/foldingRange - (16) at Instant { tv_sec: 1538138, tv_nsec: 492457125 }
[2024-08-05T17:31:11Z INFO  tinymist_query::syntax::lexical_hierarchy] lexical hierarchy analysis took 204.958µs
[2024-08-05T17:31:11Z INFO  sync_lsp] handled  textDocument/foldingRange - (16) in 358.42µs
[2024-08-05T17:31:11Z INFO  sync_lsp] handling textDocument/codeAction - (17) at Instant { tv_sec: 1538138, tv_nsec: 596415416 }
[2024-08-05T17:31:11Z INFO  sync_lsp] handled  textDocument/codeAction - (17) in 690.46µs
[2024-08-05T17:31:11Z INFO  sync_lsp] handling textDocument/foldingRange - (18) at Instant { tv_sec: 1538138, tv_nsec: 793799458 }
[2024-08-05T17:31:11Z INFO  tinymist_query::syntax::lexical_hierarchy] lexical hierarchy analysis took 58.417µs
[2024-08-05T17:31:11Z INFO  sync_lsp] handled  textDocument/foldingRange - (18) in 441.00µs
[2024-08-05T17:31:11Z INFO  sync_lsp] handling textDocument/codeAction - (19) at Instant { tv_sec: 1538138, tv_nsec: 825346166 }
[2024-08-05T17:31:11Z INFO  sync_lsp] handled  textDocument/codeAction - (19) in 371.33µs
[2024-08-05T17:31:11Z INFO  sync_lsp] handling textDocument/semanticTokens/full/delta - (20) at Instant { tv_sec: 1538138, tv_nsec: 893932666 }
[2024-08-05T17:31:11Z INFO  sync_lsp] handled  textDocument/semanticTokens/full/delta - (20) in 188.38µs
[2024-08-05T17:31:11Z INFO  sync_lsp] handling textDocument/codeLens - (21) at Instant { tv_sec: 1538139, tv_nsec: 77232250 }
[2024-08-05T17:31:11Z INFO  sync_lsp] handled  textDocument/codeLens - (21) in 247.00µs
[2024-08-05T17:31:12Z INFO  sync_lsp] handling textDocument/codeAction - (22) at Instant { tv_sec: 1538139, tv_nsec: 894175875 }
[2024-08-05T17:31:12Z INFO  sync_lsp] handled  textDocument/codeAction - (22) in 184.04µs
[2024-08-05T17:31:12Z INFO  sync_lsp] handling textDocument/documentSymbol - (23) at Instant { tv_sec: 1538139, tv_nsec: 896211250 }
[2024-08-05T17:31:12Z INFO  tinymist_query::syntax::lexical_hierarchy] lexical hierarchy analysis took 46.334µs
[2024-08-05T17:31:12Z INFO  sync_lsp] handled  textDocument/documentSymbol - (23) in 80.54µs
[2024-08-05T17:31:12Z INFO  sync_lsp] notifying $/setTrace - at Instant { tv_sec: 1538139, tv_nsec: 951202750 }
[2024-08-05T17:31:12Z WARN  sync_lsp] unhandled notification: $/setTrace
[2024-08-05T17:31:12Z INFO  sync_lsp] notifying workspace/didChangeConfiguration - at Instant { tv_sec: 1538139, tv_nsec: 951220333 }
[2024-08-05T17:31:12Z INFO  sync_lsp] notifing workspace/didChangeConfiguration succeeded in 337.50µs
[2024-08-05T17:31:12Z INFO  tinymist::init] preferred theme: Some("light") {"compileStatus": String("enable"), "exportPdf": String("never"), "fontPaths": Null, "formatterMode": String("disable"), "formatterPrintWidth": Number(120), "hoverPeriscope": Null, "outputPath": String(""), "preferredTheme": String("light"), "rootPath": Null, "semanticTokens": String("enable"), "systemFonts": Bool(true), "typstExtraArgs": Array []}
[2024-08-05T17:31:12Z INFO  tinymist::server] new settings applied
[2024-08-05T17:31:14Z INFO  sync_lsp] handling workspace/executeCommand - (24) at Instant { tv_sec: 1538141, tv_nsec: 714661208 }
[2024-08-05T17:31:14Z INFO  sync_lsp] handled  workspace/executeCommand - (24) in 64.08µs

tinymist client log(Help -> Toggle Developer Tools -> Console):
log.ts:419  INFO Started local extension host with pid 40279.
TMScopeRegistry.ts:46 Overwriting grammar scope name to file mapping for scope text.tex.
Old grammar file: file:///Applications/Visual%20Studio%20Code.app/Contents/Resources/app/extensions/latex/syntaxes/TeX.tmLanguage.json.
New grammar file: file:///Users/carlos/.vscode/extensions/james-yu.latex-workshop-10.1.0/syntax/TeX.tmLanguage.json
register @ TMScopeRegistry.ts:46
TMScopeRegistry.ts:46 Overwriting grammar scope name to file mapping for scope text.tex.latex.
Old grammar file: file:///Applications/Visual%20Studio%20Code.app/Contents/Resources/app/extensions/latex/syntaxes/LaTeX.tmLanguage.json.
New grammar file: file:///Users/carlos/.vscode/extensions/james-yu.latex-workshop-10.1.0/syntax/LaTeX.tmLanguage.json
register @ TMScopeRegistry.ts:46
TMScopeRegistry.ts:46 Overwriting grammar scope name to file mapping for scope text.bibtex.
Old grammar file: file:///Applications/Visual%20Studio%20Code.app/Contents/Resources/app/extensions/latex/syntaxes/Bibtex.tmLanguage.json.
New grammar file: file:///Users/carlos/.vscode/extensions/james-yu.latex-workshop-10.1.0/syntax/Bibtex.tmLanguage.json
register @ TMScopeRegistry.ts:46
TMScopeRegistry.ts:46 Overwriting grammar scope name to file mapping for scope text.tex.markdown_latex_combined.
Old grammar file: file:///Applications/Visual%20Studio%20Code.app/Contents/Resources/app/extensions/latex/syntaxes/markdown-latex-combined.tmLanguage.json.
New grammar file: file:///Users/carlos/.vscode/extensions/james-yu.latex-workshop-10.1.0/syntax/markdown-latex-combined.tmLanguage.json
register @ TMScopeRegistry.ts:46
TMScopeRegistry.ts:46 Overwriting grammar scope name to file mapping for scope source.cpp.embedded.latex.
Old grammar file: file:///Applications/Visual%20Studio%20Code.app/Contents/Resources/app/extensions/latex/syntaxes/cpp-grammar-bailout.tmLanguage.json.
New grammar file: file:///Users/carlos/.vscode/extensions/james-yu.latex-workshop-10.1.0/syntax/cpp-grammar-bailout.tmLanguage.json
register @ TMScopeRegistry.ts:46
TMScopeRegistry.ts:46 Overwriting grammar scope name to file mapping for scope source.typst.
Old grammar file: file:///Users/carlos/.vscode/extensions/myriad-dreamin.tinymist-0.11.18-darwin-arm64/out/typst.tmLanguage.json.
New grammar file: file:///Users/carlos/.vscode/extensions/quarto.quarto-1.113.0/languages/typst/typst.tmLanguage.json
register @ TMScopeRegistry.ts:46
2console.ts:137 [Extension Host] determineVscodeTheme 1
console.ts:137 [Extension Host] vscodeVariables test: Object
console.ts:137 [Extension Host] validate /Users/carlos/.vscode/extensions/myriad-dreamin.tinymist-0.11.18-darwin-arm64/out/tinymist args Array(1)
console.ts:137 [Extension Host] deserializeWebviewPanel Object
console.ts:137 [Extension Host] Preview Command /Users/carlos/Desktop/test.typ
console.ts:137 [Extension Host] Launched preview, data plane port:59011, static server port:59012
webviewElement.ts:486 An iframe which has both allow-scripts and allow-same-origin for its sandbox attribute can escape its sandboxing.
mountTo @ webviewElement.ts:486
7console.ts:137 [Extension Host] determineVscodeTheme 1
VM7:12 state eyJtb2RlIjoiZG9jIiwiYXNQcmltYXJ5IjpmYWxzZSwidXJpIjoiZmlsZTovLy9Vc2Vycy9jYXJsb3MvRGVza3RvcC90ZXN0LnR5cCJ9
VM7:16 vscode_state Object
console.ts:137 [Extension Host] determineVscodeTheme 1
VM8:5842 plugin initialized, build info: Object
VM8:5728 WebSocket connection opened WebSocket
VM8:5763 batch 2 messages
VM8:5784 recv partial-rendering 22
VM8:5821 Experimental feature: partial rendering enabled
VM8:5784 recv invert-colors 19
VM8:5827 Experimental feature: invert colors strategy taken: never
log.ts:429  WARN Semantic token with invalid length detected at lineNumber 2, column 1
VM8:5763 batch 1 messages
VM8:5784 recv diff-v1 50252
VM8:1387 render_in_window with partial rendering enabled window 1.0143265689711973 0 26.37249079325113<PHONE_NUMBER>771226<PHONE_NUMBER>420605 , patch scale 51023
VM8:368 parse 3.90 ms, rerender 7.40 ms, total 11.30 ms
VM8:1830 updateCanvas start
VM8:1862 updateCanvas one miss undefined cZWuV8urjj4Ybp0b5hAMqJY
VM8:1862 updateCanvas one miss undefined cH6BV5uDKc9UoYQoE2d20oU
VM8:1862 updateCanvas one miss undefined c/2HdrKpustsNVnjQVwW2uE
VM8:5763 batch 1 messages
VM8:5784 recv diff-v1 292
VM8:1387 render_in_window with partial rendering enabled window 1.0144578313253012 0 26.375903614457833<PHONE_NUMBER>686747<PHONE_NUMBER>73494 , patch scale 4260
VM8:1666 cancel canvas rendering
VM8:368 parse 0.10 ms, rerender 2.10 ms, total 2.20 ms
VM8:1870 updateCanvas done 44.80000019073486
VM8:1830 updateCanvas start
2console.ts:137 [Extension Host] determineVscodeTheme 1
VM8:1870 updateCanvas done 115
2console.ts:137 [Extension Host] determineVscodeTheme 1
log.ts:419  INFO [perf] Render performance baseline is 15ms
console.ts:137 [Extension Host] skip extension-output file extension-output-myriad-dreamin.tinymist-#1-Tinymist Typst Language Server
VM8:1387 render_in_window with partial rendering enabled window 1.5253623188405796 0 39.65942028985507<PHONE_NUMBER>811594 1108.9384057971013 , patch scale 26963
VM8:368 parse 0.00 ms, rerender 6.80 ms, total 6.80 ms
VM8:1830 updateCanvas start
VM8:1870 updateCanvas done<PHONE_NUMBER>0463257

Thanks for this and #537!


Added handling of ":" in XML attribute names

We use magic chunks localy, and we also use XML configuration namespaces within attribute values.
This fix allows for transforming configurations such as:
<configuration>
  <add key="domain:keyItem" value="someValue"/>
</configuration>

using transformation:
{
"configuration/add[@key='domain:keyItem']" : "someNewValue"
}

will get:
<configuration>
  <add key="domain:keyItem" value="someNewValue"/>
</configuration>

I see it is already solved

Thank you for your efforts. You're right, it's already solved. But I have some problems with deployment.
Check #42 for further news.


Error parsing xml

Hi,
I am trying to use your xmltojson converter and cannot seem to get it to work.
I am trying to use this npm module as part of a nativescript application that does not have a DOM. I have noticed that the stringToXML function only caters for DOM and Microsoft ActiveXObject and returns a null value.
I am testing this code directly in node.
var xmlc= require('xmltojson');
var testString = 'It Works!';   // get some xml (string or document/node)
var myOptions = {
mergeCDATA: false,
xmlns: false
};
var result = xmlc.parseString(testString,myOptions);
console.log('xmlToJSON=' + result);
/*
and get the following errors:
var result = xmlc.parseString(testString,myOptions);
^
TypeError: Object # has no method 'parseString'
at Object. (I:\Software\nodejs\test\test.js:21:20)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Function.Module.runMain (module.js:497:10)
at startup (node.js:119:16)
at node.js:906:3
any ideas?
many thanks
Peter

xmlToJSON is meant to be used in a browser and relies on the availability of a compatible W3C DOM API.  Unfortunately, nodejs does not provide such an implementation.  Others have reported success using xmlDOM https://github.com/jindw/xmldom .

Thanks William
I found another package xml2js which worked with very little fuss.
Thanks for your contribution to the community.
regards
Peter


How to open the source code in Visual Studio?

I'm new to C++. There are no vcproj files. How to open the source code in Visual Studio for normal edit, compile, debug experience?
What IDE do you use on Windows to develop this library?

See https://github.com/tdlib/td#building.
Also, new enough Visual Studio supports CMake out of the box. See https://learn.microsoft.com/en-us/cpp/build/cmake-projects-in-visual-studio for more details.

As stated in the linked docs I need to open a folder with CMakeLists.txt. The folder \td\telegram\ doesn't contain it. If I try to open root folder VS shows this error:

Error at D:\tgproj\td-master\CMakeLists.txt:9 (project):
No CMAKE_CXX_COMPILER could be found.
Tell CMake where to find the compiler by setting either the environment
variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full path
to the compiler, or to the compiler name if it is in the PATH

No, it answers your question. See, what is CMake: https://en.wikipedia.org/wiki/CMake.

CMake isn't a build tool. To build a project with MSVC compiler it generates a Visual Studio solution with multiple projects in the build directory. You can open the solution build/TDLib.sln in Visual Studio.
Alternatively, you can open the TDLib root directory in Visual Studio. It will be able to find CMakeLists.txt and build the project using it by creating a solution inside "out" subdirectory. Given, OpenSSL and zlib are required to build TDLib, you will also need to change "CMake Settings for TDLib" by right-clicking the CMakeLists.txt file, choosing corresponding menu item, and adding <full path to vcpkg>/vcpkg/scripts/buildsystems/vcpkg.cmake as CMake toolchain file. Also, don't forget to delete and regenerate CMake cache after changing the toolchain file if you tried to build the project before specifying the toolchain file.


Upgrades to streamlit app

This PR upgrades our streamlit app #459 which is launched when dlt pipeline PIPELINE_NAME show command is called.
It also includes better prompt to detect and install streamlit and additional packages if it is missing.

Closing this in favor of https://github.com/dlt-hub/dlt/pull/1060 because I decided to split automatic dependency installation utilities in the separate PR.


Performance

Hi,
I'm currently developing a simple game. You can check it out here : http://insurancelovers.com/goa/africa/
Everything is working fine but the main issue is the performance. The game doesn't run smooth and is laggy. The performance in firefox is some what better as compared to chrome.
Any tips on improving the game performance?
Thanks

Which bits aren't smooth for you?

In particular the rollover functionality. The each individual map of the country should light up as soon as the cursor roll over it but it takes a few seconds before it lights up.

And then on clicking I'm highlighting the maps using different colors which I have employed using the ColorFilter

Hi @createbyte - as a friendly note, this Issues tracker is for logging reproducible bugs with the library. For more nebulous problems (like non-specific performance help), I'd strongly encourage you to use Stack Overflow. You'll get better / faster answers, and it keeps this tracker focused.
That said, it sounds like you are applying a filter on rollover. Depending on the area it is applied to, filters can be very expensive, so you might be seeing a delay in updates due to that. I'd recommend something other than a filter as your hoverstate if you think you can make it work. The fact that FireFox is faster is also a clue that this is the problem (Chrome usually performs better in canvas tasks, but filters are almost pure computation).

I'd also suggest using createjs.Ticker.timingMode = createjs.Ticker.RAF instead of createjs.Ticker.setInterval

Oh, and don't tick the stage unless it needs to be updated.


Feat: implement round_series_to_precision() method and tests for it

This PR introduces the round_series_to_precision() method, which is necessary for implementing issue #35.
Key points:

Python does not natively support method overloading, so instead of overloading the existing round_to_precision() method, I created a new method, round_series_to_precision(), for the vectorized version. This avoids adding type checks and splitting the logic within a single method.
The tests are currently written under the TestLedger() class. These tests are expected to be refactored in milestone #2.

@lasuk Please review the changes and provide feedback or approval for merging

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Flag
Coverage Δ

unittests
58.03% <100.00%> (+0.15%)
:arrow_up:

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

Files
Coverage Δ

pyledger/ledger_engine.py
58.71% <100.00%> (+0.33%)
:arrow_up:

I have changed my opinion on the best way to combine the two related methods dealing with singleton and vector arguments.
Currently, we have one method taking singleton and another method taking pd.Series as arguments:
round_to_precision(self, amount: float, currency: str) -> float
round_series_to_precision(self, amount: pd.Series, currency: pd.Series) -> pd.Series

I propose instead to implement a single method where each argument can be either a singleton or a vector. The return value is a float if both arguments are singletons and a vector of float otherwise.
round_to_precision(self, amount: float | "vector of float", currency: str | "vector of str") -> float | vector of float

Motivation: The proposed solution is more flexible, it allows to provide one singleton and one vector as argument.

Also, the method shall be open to any vector input in python, including arrays, rather than narrowly focusing on a pd.Series. This must be a quite common problem in Pyhton and we shall stick with the usual pattern used in python. We should also stick to the usual return type for such cases (array instead of pd.Series?).


Allow size calculations to be skipped

[X] I confirm this contribution is my own and I agree to license it with Apache 2.0.
[] I confirm the moderators may change the PR before merging it in.
Summary of changes
To minimise ROM space, add an option for constant, skipping the
size calculation.

Fixed up unit test - I'd taken out the "do size calculation" call from the build thinking it was only needed for the memset(0), but it also serves as a pre-sanity check for parameters.
(Which in turn means if the size calculation skip is enabled, there will be less parameter sanity checking.)

This is showing include problems on the test job Tero set up - I'm not sure what the correct fix for the failing environment is.
(And we're getting run-time problems on the device it was intended for, but that could be straightforward lack of memory).

Changed include in header from mbed-coap/sn_config.h to just sn_config.h, matching include style in other header, to try to resolve buid issues.
Added tr_error in overflow return.


az login fails: OSError: [WinError -2146892987]

Describe the bug
When running Azure CLI on Microsoft.AzureStackHCI/clusters, az login fails:
> az login --use-device-code
az : WARNING: To sign in, use a web browser to open the page https://microsoft.com/devicelogin and enter the code xxx to authenticate.
    + CategoryInfo          : NotSpecified: (WARNING: To sig...o authenticate.:String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError

ERROR: The command failed with an unexpected error. Here is the traceback:
ERROR: [WinError -2146892987] : ''
Traceback (most recent call last):
  File 'D:\\a\\1\\s\\build_scripts\\windows\\artifacts\\cli\\Lib\\site-packages\\knack/cli.py', line 231, in invoke
  File 'D:\\a\\1\\s\\build_scripts\\windows\\artifacts\\cli\\Lib\\site-packages\\azure/cli/core/commands/__init__.py', line 658, in execute
  File 'D:\\a\\1\\s\\build_scripts\\windows\\artifacts\\cli\\Lib\\site-packages\\azure/cli/core/commands/__init__.py', line 721, in _run_jobs_serially
  File 'D:\\a\\1\\s\\build_scripts\\windows\\artifacts\\cli\\Lib\\site-packages\\azure/cli/core/commands/__init__.py', line 692, in _run_job
  File 'D:\\a\\1\\s\\build_scripts\\windows\\artifacts\\cli\\Lib\\site-packages\\azure/cli/core/commands/__init__.py', line 328, in __call__
  File 'D:\\a\\1\\s\\build_scripts\\windows\\artifacts\\cli\\Lib\\site-packages\\azure/cli/core/commands/command_operation.py', line 121, in handler
  File 'D:\\a\\1\\s\\build_scripts\\windows\\artifacts\\cli\\Lib\\site-packages\\azure/cli/command_modules/profile/custom.py', line 149, in login
  File 'D:\\a\\1\\s\\build_scripts\\windows\\artifacts\\cli\\Lib\\site-packages\\azure/cli/core/_profile.py', line 153, in login
  File 'D:\\a\\1\\s\\build_scripts\\windows\\artifacts\\cli\\Lib\\site-packages\\azure/cli/core/auth/identity.py', line 158, in login_with_device_code
  File 'D:\\a\\1\\s\\build_scripts\\windows\\artifacts\\cli\\Lib\\site-packages\\msal/application.py', line 1608, in acquire_token_by_device_flow
  File 'D:\\a\\1\\s\\build_scripts\\windows\\artifacts\\cli\\Lib\\site-packages\\msal/oauth2cli/oauth2.py', line 384, in obtain_token_by_device_flow
  File 'D:\\a\\1\\s\\build_scripts\\windows\\artifacts\\cli\\Lib\\site-packages\\msal/oauth2cli/oauth2.py', line 346, in _obtain_token_by_device_flow
  File 'D:\\a\\1\\s\\build_scripts\\windows\\artifacts\\cli\\Lib\\site-packages\\msal/oauth2cli/oidc.py', line 115, in _obtain_token
  File 'D:\\a\\1\\s\\build_scripts\\windows\\artifacts\\cli\\Lib\\site-packages\\msal/oauth2cli/oauth2.py', line 789, in _obtain_token
  File 'D:\\a\\1\\s\\build_scripts\\windows\\artifacts\\cli\\Lib\\site-packages\\msal/application.py', line 581, in lambda
  File 'D:\\a\\1\\s\\build_scripts\\windows\\artifacts\\cli\\Lib\\site-packages\\msal/token_cache.py', line 307, in add
  File 'D:\\a\\1\\s\\build_scripts\\windows\\artifacts\\cli\\Lib\\site-packages\\msal/token_cache.py', line 113, in add
  File 'D:\\a\\1\\s\\build_scripts\\windows\\artifacts\\cli\\Lib\\site-packages\\msal/token_cache.py', line 184, in __add
  File 'D:\\a\\1\\s\\build_scripts\\windows\\artifacts\\cli\\Lib\\site-packages\\msal_extensions/token_cache.py', line 49, in modify
  File 'D:\\a\\1\\s\\build_scripts\\windows\\artifacts\\cli\\Lib\\site-packages\\msal_extensions/persistence.py', line 163, in save
  File 'D:\\a\\1\\s\\build_scripts\\windows\\artifacts\\cli\\Lib\\site-packages\\msal_extensions/windows.py', line 82, in protect
OSError: [WinError -2146892987] : ''
To open an issue, please run: 'az feedback'

Email: AKS on HCI | az login failing with unexpected error, probably known issue

The workaround is to turn off token encryption: https://github.com/Azure/azure-cli/issues/20231#issuecomment-1007176901

To be honest, the DPAPI failure is not actionable for MSAL. I believe @bgavrilms also observed similar issues on MSAL .Net too. Is there a contact for DPAPI to report these issues to?

Yes, indeed, after many struggles with token encryption on both Windows and Mac (for Linux we always knew there is a problem), we decided to allow apps to store tokens in plaintext as a fallback. We recommend that the app makes it very clear to the user that tokens are stored in plaintext.

By the way, that error code means:
The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation
(on corpnet, you can go to http://errors to understand windows errors).
This is pretty standard error in some cases of virtualization, see here. Although there are workarounds, these seem to be "too complex" for most orgs (complex admin policies etc.)

By the way, that error code means:
The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation
(on corpnet, you can go to http://errors to understand windows errors).
This is pretty standard error in some cases of virtualization, see here. Although there are workarounds, these seem to be "too complex" for most orgs (complex admin policies etc.)

Thanks for the details, Bogdan! I am inspired to work out this PR in MSAL EX to hopefully help Azure CLI and/or its users to troubleshoot.

Workaround
First, you may try to clear the credential cache and re-login:
az account clear
az login

If this still doesn't help, you may temporarily turn off token cache encryption. (⚠ This is an internal experimental config option. We may change it or drop it anytime.)
az config set core.encrypt_token_cache=false
az login

Just dropping in - we have an AzureCLI@2 task on ADO intermittently failing with the following output:
##[error]Error Code: [1]
##[error]Error: Azure login failed
##[error]Script failed with error: ERROR: Encryption failed: [WinError -2146892987] The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation. See also https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/enable-computer-and-user-accounts-to-be-trusted-for-delegation. Consider disable encryption.
Please report to us via Github: https://github.com/Azure/azure-cli/issues/21010

We're on our own semi-customized pool (based on windows-latest from upstream).
Ping me for more details on Teams if you need them :)

Just dropping in - we have an AzureCLI@2 task on ADO intermittently failing with the following output:
##[error]Error Code: [1]
##[error]Error: Azure login failed
##[error]Script failed with error: ERROR: Encryption failed: [WinError -2146892987] The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation. See also https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/enable-computer-and-user-accounts-to-be-trusted-for-delegation. Consider disable encryption.
Please report to us via Github: https://github.com/Azure/azure-cli/issues/21010

We're on our own semi-customized pool (based on windows-latest from upstream). Note that rerunning a failed job has always succeeded for us (without changing anything). Ping me for more details on Teams if you need them :)

(I'm thinking out loud...) @jiasli , do you know whether the "AzureCLI@2 task on ADO" is expected to support DPAPI/encryption? If not, can we somehow disable it in that task?

It's resolved by refering https://learn.microsoft.com/en-us/cli/azure/install-azure-cli-windows?tabs=azure-cli using remove data section, remove .bin file

After and before install az cli

I try to run an "az login" through an ansible playbook. Therefore I installed on my windows server the azure-cli 2.29.2. The connection from ansible to windows is done through SSH.
The ansible task looks as follows:

name: Login to azure
win_shell: >
az login --service-principal --username myuser --password mypassword --tenant mytenant

With azure-cli version 2.29.2 this worked.
I now installed azure-cli version 2.42.0 on my windows server and the ansible task now fails with this error:
FAILED! => {"changed": true, "cmd": "az login --service-principal --username myuser --password mypassword --tenant mytenant", "delta": "0:00:07.533507", "end": "2022-11-15 09:13:59.947535", "msg": "non-zero return code", "rc": 1, "start": "2022-11-15 09:13:52.414027", "stderr": "ERROR: Decryption failed: [WinError -2146892987] The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation. See also https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/enable-computer-and-user-accounts-to-be-trusted-for-delegation. App developer may consider this guidance: https://github.com/AzureAD/microsoft-authentication-extensions-for-python/wiki/PersistenceDecryptionError\r\nPlease report to us via Github: https://github.com/Azure/azure-cli/issues/21010", "stderr_lines": ["ERROR: Decryption failed: [WinError -2146892987] The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation. See also https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/enable-computer-and-user-accounts-to-be-trusted-for-delegation. App developer may consider this guidance: https://github.com/AzureAD/microsoft-authentication-extensions-for-python/wiki/PersistenceDecryptionError", "Please report to us via Github: https://github.com/Azure/azure-cli/issues/21010"], "stdout": "", "stdout_lines": []}
Is there a way to solve this without adding everywhere a privilege escalation (ansible becom) where I call a win_shell command or powershell script (ps1)??

I try to run an "az login" through an ansible playbook. Therefore I installed on my windows server the azure-cli 2.29.2. The connection from ansible to windows is done through SSH. The ansible task looks as follows:
... ERROR: Decryption failed: [WinError -2146892987] The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation. See also https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/enable-computer-and-user-accounts-to-be-trusted-for-delegation....
Is there a way to solve this without adding everywhere a privilege escalation (ansible becom) where I call a win_shell command or powershell script (ps1)??

Does this earlier workaround not work for you?

@rayluo The workaround with encrypt_token_cache=false would work...
az config set core.encrypt_token_cache=false
But this configuration is not even mentioned on https://learn.microsoft.com/en-us/cli/azure/azure-cli-configuration. An @jiasli  wrote: ⚠ This is an internal experimental config option. We may change it or drop it anytime.)
This breaking change came with the version 2.30.0 from azure-cli: https://learn.microsoft.com/en-us/cli/azure/release-notes-azure-cli#november-02-2021. There are some alternatives mentioned in https://learn.microsoft.com/en-us/cli/azure/msal-based-azure-cli but I need to login first to get an access-token and the login fails. I'm not using an interactive session, it's all done through ansible playbooks.
And I have no idea how evil the deactivation of the cached token is.

I'm not using an interactive session, it's all done through ansible playbooks.

@jiasli, those automation environment might not satisfy that implicit requirement. What if we change Azure CLI to automatically set encrypt_token_cache=false (and perhaps even persist it) upon encountering an encryption/decryption failure?

It's resolved by refering https://learn.microsoft.com/en-us/cli/azure/install-azure-cli-windows?tabs=azure-cli look into remove data section, remove .bin file, after and before delete az cli and install latest one 2.42.0

Thanks @himanshukgit for sharing this.
For me it was sufficient to delete C:\Users\<username>\.azure\msal_token_cache.bin as described in section "Remove data" of the document Install Azure CLI on Windows you have shared.


fix typo

LGTM

Coverage remained the same at 87.264% when pulling 8fc1a7f64c456b54169f9a9fe3f4f67edc402a93 on typo into 47cecb1d4da0777562866dcd26e12b651584965f on master.


Fix https://github.com/select2/select2/issues/4276

This pull request includes a

[x] Bug fix
[ ] New feature
[ ] Translation

The following changes were made

Change mousedown to click event. Fix for https://github.com/select2/select2/issues/4276

There are some other issues related to mousedown vs click events:

#4763 (addressed in #4536)
#4642 (addressed in #4644)
https://github.com/select2/select2/issues/4482#issuecomment-264916443
https://github.com/select2/select2/issues/4276#issuecomment-212663921

Actually #4276 makes a good point:

Simply changing the opening event from mousedown to click fixes it, at the cost of losing functionality parity with a base <select> element.
A small (humanly imperceptible) delay between an opening mousedown and a selecting mouseup may be another way around it (ie, within the range of a normal 'click'), but again is not all that ideal.
Perhaps just an option on which event to listen for...?

Could you review these please?  It sounds like mousedown was originally used instead of click because of the behavior of mobile browsers, but this behavior has since been removed from most mobile browsers.
I just want to make sure we don't introduce any new regressions.  It sounds like maybe a configuration setting for this might still be worthwhile, even if we change the default to be click?

@alexweissman
Checked this fix for a long time in Chrome/Safari on Mac OS X.
Checked in Android Firefox/Chrome, iOS Safari/Chrome, Windows Chrome/Firefox/IE just now.
Looks like all of this issues have same trouble because dropdown overlap selection container:
https://github.com/select2/select2/issues/4763
https://github.com/select2/select2/issues/4642
https://github.com/select2/select2/issues/4276
I can't check this issue:
https://github.com/select2/select2/issues/4482
But if mousedown really not fired in iOS WebView (found many questions about it on StackOverflow e.g.) PR must be help.
I don't think that need to configure that because we can bind $('#mySelect2').select2('open'); on any actions.

Ok so as far as #4644 goes, do you think we should leave it as click in the multi-select case?
I'm actually not quite sure how this PR addresses #4200 - that issue seems to be related to mouseup, not mousedown.  Could you explain further?

I'm actually not quite sure how this PR addresses #4200 - that issue seems to be related to mouseup, not mousedown. Could you explain further?
My bad. I mentioned wrong issue.

Ok so as far as #4644 goes, do you think we should leave it as click in the multi-select case?
What must occur when we click in Alaska in provided example? https://jsfiddle.net/vwsg4tn5/
We can delete item by cross. And we can show dropdown by clicking on Alaska. I don't think this behavior is wrong.

So, #4642 and #4295 describe some potential issues with using click for multi-select.

@UksusoFF it seems like this is not a good fix in the long term.  See my comment at https://github.com/select2/select2/issues/4276#issuecomment-334624014.

Okay let's continue in issue.


Idea: Auth in Route

I'd like to move my auth logic out of my jsx components and into Routes. Something that would let me control my available routes when logged in. At the moment I use a mixin, in my LoggedIn handler but I'd like to remove it from there and into the Route by grouping routes within a Route that has a authRequired attrib.
<Route handler={App}>
    <Route handler={LoggedIn} authRequired={MyAuthHandler} noAuth={LogIn}>
      <Route name="acts" handler={Acts}/>
      <Route name="home" path="/" handler={Home}/>
    </Route>
    <Route name="login" handler={LogIn}/>
    <NotFoundRoute handler={NotFound}/>
  </Route>

If you define your routes the programmatic way, you can set onEnter handlers that can take on this functionality, though it means giving up the JSX definition of your routes.
Check out this PR for more details https://github.com/rackt/react-router/pull/845

1.0 you can have any props you want on routes, and use getRoutes to decide what to do (like check app state like authentication) and return different routes.
personally, I'd have a parent route w/o a path that redirects if you're not logged in.
// requireAuth redirects if they aren't auth'd
<Route component={Auth} onEnter={requireAuth)>
  <Route .../>
  <Route ../>
</Route>


Some grammer/spelling corrections. And one code sample fix

Notices a few items while I was reading the book.

Thanks! 😁


Mumbai House Price Detection

Hi, I would like to add a a machine learning model for predicting the prices of houses in various localities of Mumbai which is a city with major housing crisis. I will use a dataset contains information on factors such as house area, number of bedrooms, locality, and more. Model will use several regression techniques for predictions.
This model aims to provide valuable insights for potential buyers and sellers in the real estate market.
Please assign this issue to me under GSSOC'24

can i work on it?

I would like to work on this issue , Please assign this task to me

can i work on it?

@invigorzz313

There are many issues similar to this already. Please raise new issues if you have any new ideas.


raw.drop_channels

raw.drop_channels crashes when the channels are not included in the data being processed. Would be convenient to have a warning message instead.

We should add a on_missing='raise' | 'warn' | 'ignore' as we do elsewhere. Should be an easy one for someone if they're motivated!


Cache Results  - especially clang-sa

I am running code-checker in a CI without the web-frontend, only generating HTML-output. The codechecker-run is the longest running job. Caching results could greatly improve the performance.
I searched the net for caching clang-sa. However as ccache does not support this, and I haven't found other solutions.
I'm just a user of codechecker and no clang-sa/tidy/.. - expert. Yet if I understand things right: As long as no CTU-Analysis is active, hashing the pre-processor-output, clangsa-flags and -version should probably do the job, right?

I think, the best performance could be gained by some ccache-like cache for Clang analysis results. Unfortunately I'm not aware of any. From CodeChecker point of view the analysis performance can be controlled only by running non-CTU as you mentioned, or turning off unnecessary and/or style checkers.
Yes, you're right, it sounds technically feasible to implement some caching of analysis results (i.e. plist files) based on the pre-processor output and some further data. The only difficulty should be generating a build command which does the pre-processing. According to my experiences, it's not always as simple as adding a -E flag, but having a study on this issue and some prototype implementation would be great.


Weird format when nesting custom containers.

I'm trying to create some utility classes for use in my markdown.
Give this:
:::section-columns

:::section-column

column 1

:::

:::section-column

column 2

:::

:::

I get this:

column 1

column 2

I expected (wrongly?) this:

column 1

column 2

Hmm, sorry, I see another issue here with the same issue: #202
I think it comes down to the number of :'s used. Let me try that real quick.

Yup, this works:
::::section-columns

:::section-column

column 1

:::

:::section-column

column 2

:::

::::

Any ideas why that is required? Pandoc seems to handle it (correctly?).


griffin dispersion?

So I am look at some older griffin data and am a bit confused by the calibration.  It appears that we have calibration parameters which are greater than 1 after we divide by a kvalue of 512.  This means we take a less dispersed peal from the charge spectrum and artificial increase its with?  Surely I am missing something, other wise we are doing low resolution spectroscopy with griffin...

Are you arbitrarily choosing 512? I think the kValues tend to be closer to 600.
On Aug 30, 2016, at 6:00 PM, pcbend <notifications<EMAIL_ADDRESS>wrote:
[screenshot-13]https://cloud.githubusercontent.com/assets/433187/18108645/09f12062-6ec2-11e6-8e53-22eeb77027dc.png
So I am look at some older griffin data and am a bit confused by the calibration. It appears that we have calibration parameters which are greater than 1 after we divide by a kvalue of 512. This means we take a less dispersed peal from the charge spectrum and artificial increase its with? Surely I am missing something, other wise we are doing low resolution spectroscopy with griffin...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/GRIFFINCollaboration/GRSISort/issues/750, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AFLTwAQWy7bO2AMozyCsvyd8LT1J7xZtks5qlKfvgaJpZM4JxBj3.

No, it is in the fragment like that.
On Aug 30, 2016 3:05 PM, "Ryan Dunlop"<EMAIL_ADDRESS>wrote:

Are you arbitrarily choosing 512? I think the kValues tend to be closer to
600.
On Aug 30, 2016, at 6:00 PM, pcbend<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:
[screenshot-13]<https://cloud.githubusercontent.com/assets/
433187/18108645/09f12062-6ec2-11e6-8e53-22eeb77027dc.png>
So I am look at some older griffin data and am a bit confused by the
calibration. It appears that we have calibration parameters which are
greater than 1 after we divide by a kvalue of 512. This means we take a
less dispersed peal from the charge spectrum and artificial increase its
with? Surely I am missing something, other wise we are doing low resolution
spectroscopy with griffin...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<https://github.com/
GRIFFINCollaboration/GRSISort/issues/750>, or mute the thread<
https://github.com/notifications/unsubscribe-auth/
AFLTwAQWy7bO2AMozyCsvyd8LT1J7xZtks5qlKfvgaJpZM4JxBj3>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/GRIFFINCollaboration/GRSISort/issues/750#issuecomment-243596621,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAacI5Ix1DwrNTEcr_hmbI1OQofy024nks5qlKk_gaJpZM4JxBj3
.

But either way, a value that large will cause the same issue with dispersion
On Aug 30, 2016 3:05 PM, "Ryan Dunlop"<EMAIL_ADDRESS>wrote:

Are you arbitrarily choosing 512? I think the kValues tend to be closer to
600.
On Aug 30, 2016, at 6:00 PM, pcbend<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:
[screenshot-13]<https://cloud.githubusercontent.com/assets/
433187/18108645/09f12062-6ec2-11e6-8e53-22eeb77027dc.png>
So I am look at some older griffin data and am a bit confused by the
calibration. It appears that we have calibration parameters which are
greater than 1 after we divide by a kvalue of 512. This means we take a
less dispersed peal from the charge spectrum and artificial increase its
with? Surely I am missing something, other wise we are doing low resolution
spectroscopy with griffin...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<https://github.com/
GRIFFINCollaboration/GRSISort/issues/750>, or mute the thread<
https://github.com/notifications/unsubscribe-auth/
AFLTwAQWy7bO2AMozyCsvyd8LT1J7xZtks5qlKfvgaJpZM4JxBj3>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/GRIFFINCollaboration/GRSISort/issues/750#issuecomment-243596621,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAacI5Ix1DwrNTEcr_hmbI1OQofy024nks5qlKk_gaJpZM4JxBj3
.

I did see this in the 128-130Cd runs. Luckily I only looked at half-lives, so it didn't bother me much. But yes, you are correct...This is something we should keep an eye on in the future. Not sure what to do about it now.

We could simply divide by 125; which would give a charge to energy ratio of
5:1 instead. However with pileup this becomes tricky.
I think this should be brought to someone's attention.  I really am not
sure how the data has been collected and uses so long like this.
On Aug 30, 2016 3:10 PM, "Ryan Dunlop"<EMAIL_ADDRESS>wrote:
I did see this in the 128-130Cd runs. Luckily I only looked at half-lives,
so it didn't bother me much. But yes, you are correct...This is something
we should keep an eye on in the future. Not sure what to do about it now.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/GRIFFINCollaboration/GRSISort/issues/750#issuecomment-243597715,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAacI-nzkAKp8oAB6XVQOVKwN4vRrCNOks5qlKpZgaJpZM4JxBj3
.

I think this was an issue for the one experiment. I don’t think that it is ongoing. I will tell Adam. I think in many of the old experiments the pileup stuff was wonky anyway so you can use 125 and do a complete pileup rejection.

When was this data collected? What is the bank id?

To be clear, the most recent groups of experiments do not have this problem. So whether it has been noticed or not, it's not an issue that is consistently present.

@AdamGarnsworthy  The data I noticed in in was Iris' 128-130Cd decay which was a GRIF2 bank.

Ok, thanks. I dont understand this issue right now. We will have to investigate a little. We are on grif3 format currently and will move to 4 for the Oct data collection. We will stay on 4 for a long while after that, maybe it will be the final change...

By calibration parameters, you're specifically saying that the slope to
convert charge to energy is greater than one?
I don't fully understand the problem.
On Tue, Aug 30, 2016 at 6:32 PM, Ryan Dunlop<EMAIL_ADDRESS>wrote:

@AdamGarnsworthy https://github.com/AdamGarnsworthy The data I noticed
in in was Iris' 128-130Cd decay which was a GRIF2 bank.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/GRIFFINCollaboration/GRSISort/issues/750#issuecomment-243632902,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKHQyRhSIqyNbYfB_d-jf5epLzYm6s1Cks5qlNmigaJpZM4JxBj3
.

This issue is present in any data where the gain coefficient used in calibration is greater then one.  If griffin out put has plenty of precision - we are simply dividing it out.  When ever we take the raw charge and divide be such a large number we loss precision and naively one should never bin a histogram smaller then one's gain coefficient.   This means all griffin data calibrated so far with a gain of 1.2-ish should at minimum have this as its minimum bin width.
Talking with Greg H. and Adam G.  yesterday I think there is a relatively simple fix for this.  We should change the griffin parser so when it extracts a kvalue from the data stream we simple store the kvalue / 5.  This would put the griffin data back into the 5:1 channels:keV ratio need for high resolution spectroscopy, with the side effect of all peak fitting for gamma-rays should be easier and more accurate.
@SmithJK , this is the same problem we discussed sometime ago in the detector lab before I left triumf.  Yes, in the calibration files I have seen for griffin data so far, the gain coefficients are greater then 1.  I have not participated in all experiments, so I can not say this is a problem for everyone, but if we are calibrating using the GetCharge() function and the kvalue is 500-600 this problem will be present.  And to be clear, the problem is, the dispersion of the peak is on the order of the resolution of the detector.  In order to do a good fit, one ideally needs more then two channels to fit.  While it is true we can fill channels in a peak to greater precision with floating point numbers from the calibration - these numbers are not the same as data collected by the digitizer.

@pcbend am I correct in saying that the only problem here is when you apply the random number? If one was to apply the random number (between 0 and 1) to the raw charge, if you keep the number as a floating point, then as long as your gain coefficient isn't greater than your kValue you should be fine. Right? Our charges are 500x more disperse than what we are binning in the end, so it's kind of semantics no? I do agree we should try to make this as fine as possible, but I think we are ok.

This is precisely my confusion, because what @r3dunlop mentioned is where my logic took me as well.

ok, I have had some time and have followed the trail.
From whenever (a month ago?) we moved from add the randomized bin from the
TChannel calibrate function to the DataParser; this becomes less of a
problem.  It can work like this, however the issues I still see is in the
applied and as far as I know, unwritten rules and data interpretation that
storing the charge like this requires.

If we stick to this large k values; we must have gain coefficients for
griffin many decimal points (i.e. the number of significant figures become
very important).  I am hesitant to say how many right off the bat, it has
been an extremely long week and my brain is a bit fried,

When ever we make a griffin charge spectrum to calibrate, we have to
compensate the extremely low charge value with binning.  Its true root can
handle this, but from where I see it is not at all obvious that if I have a
charge spectrum which has values less than 8000 units in it that it must
have a binning of 32000. With out this inplace, any fitting routine will
cause the significant figures in the above point to be wrong, which could
easily cause peak shifts on the order of a kev or 2.

As I see it, there are still two paths forward here.  Do nothing to the
code and somehow inforce the above rules for people we haven't meet yet
(i.e. future users).  Or change the kvalue stored to something like the
kvalue/5 as suggested earlier. In my mind the later is far easier and makes
the griffin charge spectrum behave/look like every other high resolution
hpge array around.
On Fri, Sep 2, 2016 at 11:55 AM, SmithJK<EMAIL_ADDRESS>wrote:

This is precisely my confusion, because what @r3dunlop
https://github.com/r3dunlop mentioned is where my logic took me as well.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GRIFFINCollaboration/GRSISort/issues/750#issuecomment-244459481,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAacI53l2UvtSJCCGHO7lQ-B89ClaCGJks5qmHEogaJpZM4JxBj3
.

I'm a bit behind on the most recent set of changes, so let me know if I've missed something. In the update, the GetRandom was moved to the data parser, so instead of performing that randomization on the fly with the calibration, it's done before writing to the ROOT file. This means we're no longer writing the charge that is in the MIDAS file, we're writing the integer charge plus a random number between zero and one. In both cases, however, the randomization is applied to the raw total integrated charge value in the MIDAS file.
----aside----
The integrated charge is a sum of N samples. The sampling is really where this discretization is taking place - not the integrated charge. If we had all the sample information, wouldn't we add a random value between 0 and 1 to each sample? And wouldn't this be equivalent to a random (not necessarily integer) number between 0 and N added to the integrated charge?
----end aside----
If we were to use KValues of KValue/10, then that would remove a single sensitive digit from the charge to energy calibration slope, so I'm not sure that dividing by 5 necessarily solves this problem. I agree that the slopes need a lot of significant figure as they are. If the charge to energy slope is 1.25 keV/ADC unit (roughly what they are now), then a change to 1.2501 keV/ADC unit changes an energy of 10 MeV by roughly 1 keV.
@pcbend, I've definitely found what you suggest: my calibration changes slightly if I bin the spectrum differently. However, I don't have any predilection to set the bin width at 1, if I know that what I'm binning is most definitely not an integer and I see that my statistics can support it (Keeping the bin width far greater than 1/KValue still).
I haven't dealt with a lot of other HPGe raw charge spectra, so I can't comment on (or be swayed by) the argument to make GRIFFIN spectra like every other HPGe array. Right now I don't think it's worth changing, since that would be taking another step away from the ideal of the FragmentTree being simply the MIDAS file unpacked and I don't see huge value in the change. I don't think doing so would significantly impact the pile-up or summing though. As long as every KValue is divided by the same value, that's just a linear scaling.

Writing a int charge and writing the same value as a float + number < 1
are identical.  They take up the same room on disk and float can always be
cast to give back the exact int value.  This of course is not true for very
large int values, but luckly this is not the case here.
In all reality, having a KValue of 600 is a fault of the daq and should
have never been put like that in the data stream. For the purpose of the
value, it is ridiculously large and naively turns the array used for
stopped spectroscopy into a low resolution spectrometer, as discussed in
previous posts.  My suggestion is for the code to fix this - as we know how
to divide the kvalue down with a rather simple fix.  The suggestion of 5
was not arbitrary; it is to get the array into the ballpark of 0.25
keV/channel by default.  This will give 8-10 bins at a MeV which is more
then enough to gain an accurate, repeatable fit while not overly spreading
the data to thin.  Sure we could make it 10, but then one would also have
to take calibrations source runs twice as long as dividing by 5 and 10
times as long as being down now to get the same level of stats/bin.  A
tenth of a keV per bin feels like over kill for a detector that has a
natural resolution of 2 keV @ 1MeV, but it would easier to understand then
what is currently being done with the data.
At the end of the above paragraph, perhaps you can see how intertwined
this decisions become.  The idea that the charge is really a float is
fictional. It allows one to believe a level of accuracy which is not
there.  Whether or not a calibration is good, whether or not a efficiency
histogram has enough counts, whether or not a peak is real and where one
says it is, is far too dependent on the person collecting the data and
however they have the data displayed.  This is why it should really be
changed in the data stream itself. I am not sure at what level this
decision was made, but I can see no benefit to it.
As you say, your calibrations change with binning.  This simply should
not happen - it is not an detector or daq effect, solely a software one.
Energy calibration is the first step to any analysis, if this is not
stable, how does one propagate this error across the rest of the analysis?
Also, dividing the as far as dividing the kvalue in the unpacker goes, I
do not see this as a deviation away from midas->fragment clone.  I see it
as yet another necessary correction to the raw midas data need to display
the intended output of the daq correctly.  Nothing in this conversation so
far has been about the effects of pileup and summing - the fact that we
have to use the kvalue at all is due to pileup, but of course changing the
stored kvalue can not effect the behavior of the daq led triggering.   And
yes, it is absolutely a linear scaling to make sure everyone sees the raw
data in the same light.
On Sun, Sep 4, 2016 at 10:46 PM, SmithJK<EMAIL_ADDRESS>wrote:

I'm a bit behind on the most recent set of changes, so let me know if I've
missed something. In the update, the GetRandom was moved to the data
parser, so instead of performing that randomization on the fly with the
calibration, it's done before writing to the ROOT file. This means we're no
longer writing the charge that is in the MIDAS file, we're writing the
integer charge plus a random number between zero and one. In both cases,
however, the randomization is applied to the raw total integrated charge
value in the MIDAS file.
----aside----
The integrated charge is a sum of N samples. The sampling is really where
this discretization is taking place - not the integrated charge. If we had
all the sample information, wouldn't we add a random value between 0 and 1
to each sample? And wouldn't this be equivalent to a random (not
necessarily integer) number between 0 and N added to the integrated charge?
----end aside----
If we were to use KValues of KValue/10, then that would remove a single
sensitive digit from the charge to energy calibration slope, so I'm not
sure that dividing by 5 necessarily solves this problem. I agree that the
slopes need a lot of significant figure as they are. If the charge to
energy slope is 1.25 keV/ADC unit (roughly what they are now), then a
change to 1.2501 keV/ADC unit changes an energy of 10 MeV by roughly 1 keV.
@pcbend https://github.com/pcbend, I've definitely found what you
suggest: my calibration changes slightly if I bin the spectrum differently.
However, I don't have any predilection to set the bin width at 1, if I know
that what I'm binning is most definitely not an integer and I see that my
statistics can support it (Keeping the bin width far greater than 1/KValue
still).
I haven't dealt with a lot of other HPGe raw charge spectra, so I can't
comment on (or be swayed by) the argument to make GRIFFIN spectra like
every other HPGe array. Right now I don't think it's worth changing, since
that would be taking another step away from the ideal of the FragmentTree
being simply the MIDAS file unpacked and I don't see huge value in the
change. I don't think doing so would significantly impact the pile-up or
summing though. As long as every KValue is divided by the same value,
that's just a linear scaling.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GRIFFINCollaboration/GRSISort/issues/750#issuecomment-244663216,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAacIytDpXcmvMzucU0gItqooXjbXBKRks5qm6zQgaJpZM4JxBj3
.

Hi,
Bruno here. There was an extreme case of this issue in the last GRIFFIN run in August. When ZDS was connected to the new 4G card it used some ridiculously big KValue (like 2048 or something like that). When plotting GetEnergy the whole ZDS energy spectrum was compressed to 3 channels, while plotting the raw charge showed the correct energy distribution.
I know the data are still there and can be correctly calibrated, but doing a fit between channels 12 and 14 with the first non-zero in the 4th or 5th decimal is not the most intuitive thing to do and can easily led to errors.

I think this would be good info to put up on the wiki so I am making a request for it. Once it is there we can kill this issue I think.

I'm not sure I understand the problem here. Our data has two values, an integrated charge (integer even though stored as float), and the integration length/k-value (also an integer). This means the resolution limit of our "charge" (integrated charge divided by integration length) is 1/k-value (apart from issue #896). Using a gain of 1.1 this would lead to an energy resolution limit of 1.1/k-value which is still much less than 1.
So how is this a low-resolution spectroscopy?
Of course people have to use the right binning, but that will always be the case, whether we divide by the k-value or divide by a fifth of the k-value. The only advantage I could see is that a binning of 1 (which people might use as a standard) would be fine enough. Is that what you're trying to say?
Because the whole argument of "one should never bin a histogram smaller then one's gain coefficient" only is holds true if you look at the real gain coefficient, i.e. the coefficient applied to the raw charge value. That is in our case something like 1.1/500 (in newer runs the integration length is 700). Just because we first divide by the k-value and then apply our "gain coefficient" doesn't mean that this coefficient limits our binning.

I think that the issue is more that people take the charge/512 spectrum binned at 1 charge unit per bin, fit this spectrum for a centroid, and then try to gain match to a large gain. This means you don't line the detectors up very well just based on the fact that you don't get as good of a fit on coarse binning. The data shouldn't really care because the total charge is the most disperse number we have, so as long as our gain isn't > kValue we are doing things correctly. I think this really just boils down to getting a good centroid based on binning. Has anyone tried making similar spectra to the ones above using only 1 crystal? I find it hard to believe that you would see that effect there.


CodeWindow Scrolling doesn't work properly

If you scroll inside the Code-Window the Cursor scrolls outside the Code-Window.
Or if you have marked a line, it will move upwards or downwards
If you try to select a line afterwards, the cursor is not shown on the correct spot.
Also, the mouse wheel only works for scrolling up

No longer relevant as editing capabilities have been removed.


Hook up baseURI field for ODataFeed/Entry

Coverage increased (+0.0002%) to 99.947% when pulling 0f92ffde9ae4a34579bd58f7eea3b80bf1faace6 on CyberiaResurrection:UpdateSerialiser into 9920069ea180f1c6077778b467b0366ac4c42b04 on Algo-Web:master.

Coverage increased (+0.0002%) to 99.947% when pulling 69721708cddb750aa4e34986abb9a26f6cc1c8f0 on CyberiaResurrection:UpdateSerialiser into 9920069ea180f1c6077778b467b0366ac4c42b04 on Algo-Web:master.


sorbet: Update RBI files.

Autogenerated by the sorbet workflow.

This probably shouldn't be accepting a block but whatever.
I feel the DSL method handling may need refactoring at some point anyway.


Circle instead of RoundRect in SwiftUI Example.

I've added a new button:

Button("Rounded Rect, keep 1:1 ratio") {
                reset()
                cropShapeType = .roundedRect(radiusToShortSide: 10, maskOnly: false)
                presetFixedRatioType = .alwaysUsingOnePresetFixedRatio(ratio: 1)
                showingCropper = true
            }.font(.title)

But instead of a RoundRect, a Circle cropping is produced:

Without keeping the 1:1 ratio, an Oval will be presented.

Button("Rounded Rect") {
                reset()
                cropShapeType = .roundedRect(radiusToShortSide: 10, maskOnly: false)
                showingCropper = true
            }.font(.title)


Fix handling of non-model-fragment hashes

Regular hash objects didn't work before
model-definition.js:50 Uncaught TypeError: Cannot read property 'match' of undefined

Example hash:
FactoryGuy.define 'modelName',
  default:
    foo: { bar: true }

Thanks for the PR .. good catch .. and can add a test for this .. ??

can do, will update once I get some time

I run into this issue and was wondering when this fix will be available (merged in)?

I will work on this one today .. might be able to wrap it up .. stay tuned

Question .. what version of factory guy you on ..I just wrote a test for this and it works fine to use hash at attribute for non model fragment.
You will have to update factory guy ( and rerun that test )
or send me your model, and your factory and your test that is failing so i can try and recreate it

Never mind .. I found the bug .. you have to pass in the hash in the build options .. ok .. I am all set

I have this fixed .. will release tomorrow

Fixed in new patch version:
https://github.com/danielspaniel/ember-data-factory-guy/releases/tag/v2.8.1


Adds Alerts Markdown support

With Alerts being supported on GitHub recently, this PR adds the updated markdown support to indicate the importance of the text.
Example:

[!IMPORTANT]
We 💙 our community but this repository does not accept community contributions at this time.
There are no active maintainers to review PRs.
Please read this [community blog post][freeing-maintainers] for details.

Reference: https://github.com/orgs/community/discussions/16925

I've added it in the forum.
Here is the link for the same: http://forum.exercism.org/t/adds-alerts-markdown-support/9343

/format

This is blocked by #2321

Could you rebase this on main?

Could you rebase this on main?

Like, I merge this branch to the main branch in my fork?

I meant using git rebase to effectively unwind all the changes, get the latest changes from main and then re-apply this branch on top. This way, any changes we have since made to main will show up here (including the formatting fixes), without a merge commit.
Anyway, I've gone ahead and applied the changes and fixed the formatting of config.json (not broken in this PR, but made it all fail).


Note that coin-selection/random not supported for Byron random wallets. + migration test update

Issue Number

Overview

b3f3278ce3d5259b0db32a5d75b0b7fd7540ab5e
Note that coin-selection/random not supported for Byron random wallets.

30b15a9f0c4bb5a01c93878f55fc33f41b7bd5e6
Update migration tests to include v2020-10-13

Comments

bors merge


Avoid profiling offline or not present CPUs

In the current implementation, if I try to run example/c/profile in a virtual machine, libbpf_num_possible_cpus will get the wrong number of CPUs, causing the program to exit and throw an error: Fail to set up performance monitor on a CPU/Core because the wrong CPU id is passed to syscall and throwing No such device
The Rust version (example/rust/profile) of the implementation ignores this error and continues to execute bpf_program__attach_perf_event, which throws invalid perf event FD -1, but profile can still be used because bpf_program__attach_perf_event handles the case of passing the wrong CPU id.
This fix has only been applied to the C(example/c/profile).

Also, please write a commit message, not just subject. It doesn't have to be extensive, but should explain the purpose of the commit. Thanks!

An one more thing, presumably "tzssangglass" isn't your real name. Signed-off-by:  requires full real name to be used, so please update that as well. thanks!

An one more thing, presumably "tzssangglass" isn't your real name. Signed-off-by:  requires full real name to be used, so please update that as well. thanks!

I have already modified the Signed-off-by, now it is my real name. I don't know why the DCO check failed.

Ok, just few tiny things.

Please squash two commits into one final one.
Please make sure to wrap long lines in commit message to be under 80 characters
I guess I'm fine with calling into parse_cpu_mask_file directly to make code shorter and because we know that we link statically to libbpf. But please add comment next to extern that this function is coming from libbpf, but is not a public API and we can do this only as a demonstration and because we statically link against libbpf built from submodule. Ok?

Otherwise looks great, thanks!

Please squash two commits into one final one.
Please make sure to wrap long lines in commit message to be under 80 characters
I guess I'm fine with calling into parse_cpu_mask_file directly to make code shorter and because we know that we link statically to libbpf. But please add comment next to extern that this function is coming from libbpf, but is not a public API and we can do this only as a demonstration and because we statically link against libbpf built from submodule. Ok?

done, thank you for reviewing and providing suggestions.

I did tweak your code a bit to fix formatting, cleanup, and use of user-space extern declaration in C header that's included from BPF side (we should do that). Please check the final version to see the fixes I did. Thanks!


Improve Design in Empty Balance Button

As discussed in our weekly demo the current button for emptying the project/even balance shows 0.00 after the project balance is emptied. We probably needs some design iteration/review for this.
So currently for projects/events what we have is,

@opencollective/design

@SudharakaP For this we can use same format as used in "Start a new conversation" button.

For this one I am thinking why not hide the section of emptying the event balance completely if the balance is 0 (i.e; it's already emptied) as there's nothing to empty anymore?
cc: @opencollective/design @Betree

For this one I am thinking why not hide the section of emptying the event balance completely if the balance is 0 (i.e; it's already emptied) as there's nothing to empty anymore?

I'm not a fan of hiding, people end up contacting us asking "Why can't I see X? The docs say it should be there". My preference goes for disabling + having a clear message.

As discussed in our weekly demo the current button for emptying the project/even balance shows 0.00 after the project balance is emptied. We probably needs some design iteration/review for this.

Can we clearly describe why we think this is a problem? I'm open to other perspectives but in my opinion this view is pretty clear.

Can we clearly describe why we think this is a problem? I'm open to other perspectives but in my opinion this view is pretty clear.

I also think the current button itself is clear enough. Since it's been a while I don't quite remember why we thought this was a problem in the first place. Thus I am closing this issue, but if others feel this design needs to change please feel free to re-open. My thinking is at least for now no-one has raised this issue and thus maybe we are overthinking? 🤔
@opencollective/design


Allow Network.onConnect and Network.onDisconnect to use takeUntil

Ionic version:  (check one with "x")
[ ] 1.x
[ ] 2.x
[x] 3.x
I'm submitting a ...  (check one with "x")
[ ] bug report
[x] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
Can't use takeUntil. I get Property takeUntil does not exist on type Observable<any>, which doesn't really make sense given that it does.
Expected behavior:

Steps to reproduce:

Related code:
insert any relevant code here

Other information:

Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
Your system information:

Cordova CLI: 6.5.0
Ionic Framework Version: 3.0.1
Ionic CLI Version: 2.2.1
Ionic App Lib Version: 2.2.0
Ionic App Scripts Version: 1.3.0
ios-deploy version: 1.9.1
ios-sim version: 5.0.13
OS: OS X El Capitan
Node Version: v6.9.1
Xcode version: Xcode 8.2.1 Build version 8C1002

This issue was moved to driftyco/ionic-native#1571


Criterion trigger/test inconsistency

AbstractCriterion has a method, test(ServerPlayerEntity player, Predicate<T> tester).
This is protected, and is used by subclasses in methods which look like this (in BeeNestDestroyedCriterion):
public void test(ServerPlayerEntity player, Block block, ItemStack stack, int beeCount) {
    this.test(player, (conditions) -> { return conditions.test(block, stack, beeCount); });
}

or (in BrewedPotionCriterion):
public void trigger(ServerPlayerEntity player, Potion potion) {
   this.test(player, (conditions) -> { return conditions.matches(potion); });
}

all subclasses of AbstractCriterion have a method like this - some call it trigger, and some call it test. The name should be consistent, as all these methods do basically the same thing.

What do you suggest then? Just test I guess?
trigger sounds more intuitive in case people use advancements as event callbacks. But it does both trigger and perform testing.

Hmm, given advancements can have quite a bit side effects, I support trigger.


Example for file log

Since slog-stream is obsoleted, what is the best way to log to file now, I can't find example in slog and slog-term.

slog-term's PlainSyncDecorator takes now anything implementing io::Write: https://docs.rs/slog-term/2.0.0-4.0/slog_term/struct.PlainSyncDecorator.html#method.new . Just give it  an open File, like i https://github.com/slog-rs/term/blob/master/examples/full.rs#L11 .
Similiarily slog-json takes a W : io::Write https://docs.rs/slog-json/2.0.0-alpha2/slog_json/struct.Json.html#method.new . Similar convention is envisioned for any other crates.

Maybe slog-term isn't the most appropriate name anymore if it is intended to be used with non-terminal outputs.

Well, the output format is meant for terminals, and accidently looks OK in a file, so slog-term is temporarily covering that base. Ideally, I think someone should come up with a slog crate that is truly targeting logging to a file uses case:

pick format that is best for it
doesn't pull in irrelevant dependencies (eg. detecting color)

Potentially taking care of other features like:

file naming
file rotation

That would be a good slog-file crate. :)
I have spent most of my time figuring out the core details to make slog fast, versatile and robust, providing some basics. The idea is that one person can't write all possible logging features, so it's better to let community cooperate when writing their own.
Anyone interested? If not I might get to it at some point too.

I'm not sure if I'm in the minority, but I do like an option to keep the ansi colour codes in my log file, and I just less -R those logs to view them in colour (and for sublime there's an ansi view plugin)

@azriel91 This one is a tricky feature. slog_term::TermDecorator uses term crate underneath that does not support it.
What could we do:
One way is: you can just write your own slog_term::Decorator implementation, that would wrap io : io::Write and output escape codes.
Another way would be to add a code to slog-term:
struct VT100Term<W>(io : W)

impl term::Terminal for VT100Term {

}

term::Terminal comes from:  https://docs.rs/term/0.4.5/term/trait.Terminal.html
and then slog_term::TermDecoratorBuilder could get a new method that would accept and make it use, custom term::Terminal type.
I would be happy to merge the later into slog-term if you can submit a PR. Otherwise, it will have to wait until I find some time to do it.`


Upgradeable accounts

Accounts can have a version field (which is part of seed when creating associated accounts). Then, we can change the data of an account and there can be a method that will migrate data from the old to the new account, destroying the old one.
Suggested by @NorbertBodziony

We could potentially put the version number in the account header, next to the discriminant. So the layout is 8-byte-discriminant || version || borsh(account)

We will also need to force that no one will be able to create an old version of the account. Maybe allow for only one use of init/associated ?

@NorbertBodziony I believe no one will be able to create an old version of the account by virtue of the program's code being updated, since only the program can modify account data.


MC: Track creation and use of untypical Revit Phases

Track on Mission Control the team's use and creation of untypical Revit Phases.

By untypical you mean anything that is not Phase Created, Phase Demolished ?

@ksobon Untypical in terms of 'Project Phases' utilized, Existing and New Construction.

Sorry but I still dont know whats an “untypical” project phase. Explain this to me like I am 4 years old.

@ksobon In the most common of phased projects, you will have views to illustrate Existing, Demolition, and New Construction conditions. On more complex projects, you might have several stages of new construction as you build out larger facilities. The phasing dialog box by default shows only Existing and New Construction, so new users may mistakenly create a new phase for Demolition, or other conditions that do not apply to phasing (recently experienced by a team affecting all disciplines). Demolished elements are represented with phase filters, not as a dedicated project phase.

So, when do you need to create more than the phases shown by default? As one example, think of a staged construction project that will happen in two new phases. In this scenario, you are designing with a start time for the building shell followed by another phase for interiors, allowing the owner to split funding for the project into two budgets. In the first phase, the building core and shell are built. In the second phase, interior construction occurs.


Stop copying if ASGs are used in network rules

Hi, Martin!
I have encountered an interesting bug in COPY mode. When running with standard parameters, the following error appears, referring to NSG and ASG (specified as destinations in NSG). This happens at the deployment step, after which the script stops.
In source RG several network rules specify Application security group as Destination.
{"code": "InvalidTemplateDeployment", "message": "The template deployment 'rgcopy.vm_template_rg.TARGET' is not valid according to the validation procedure. The tracking id is ''. See inner errors for details."}

Inner Errors:
{"code": "SecurityRuleParametersMissing", "target": "/subscriptions//resourceGroups/vm_template_rg/providers/Microsoft.Network/networkSecurityGroups/saturn-nsg", "message": "Required security rule parameters are missing for security rule with Id: /subscriptions//resourceGroups/vm_template_rg/providers/Microsoft.Network/networkSecurityGroups/saturn-nsg/securityRules/SSH. Security rule must specify DestinationAddressPrefixes, DestinationAddressPrefix, or DestinationApplicationSecurityGroups."}

Hi,
the resource type "Microsoft.Network/applicationSecurityGroups" is currently not supported in RGCOPY. The supported resources are listed here: https://github.com/Azure/RGCOPY/blob/main/rgcopy-docu.md#supported-azure-resources
Please send me the RGCOPY zip file (containing all logs and templates). I will check whether I can add support for this scenario in the next version of RGCOPY.
In the meanwhile, you could use the following RGCOPY parameter to skip copying all security rules.
skipSecurityRules = '*'
Thanks
Martin


Invalid token address: argument of type 'NoneType' is not iterable

Hi! It's up and running, it's fine. But when I enter the Jetton address () I get the error "Only NFT collection and Jetton master addresses are allowed:
Invalid token address:
argument of type 'NoneType' is not iterable".
I've tried to put a lot of things here, the answer is always the same
I've tried it with quotes and square brackets and quotes and square brackets and so on and so forth.
What am I missing?

@sanya8923 Hi! Please write to me in telegram t.me/nessshon

The error appears when searching for the address of the jetton from the mainnet network.
In the .env IS_TESTNET=True needs to be changed to IS_TESTNET=False


Remove nodev from mounts

We need the ability to create overlayfs in empty dir volumes
and support similar use cases.
Signed-off-by: Mrunal Patel<EMAIL_ADDRESS>
- What I did
- How I did it
- How to verify it
- Description for the changelog

/test all

/lgtm

/test e2e_rhel

/test e2e_rhel


Dangling locks if lambda execution times out

In the event an action acquires a lock and then times out the lock can be left dangling causing the session to be entirely unusable. While waiting on locks things should check the expiration of the lock and purge the dangling record if it is expired (make sure lock expiration is set to lambda execution timeout as well).

set lock expiration to 3 seconds (default lambda execution time which hasn't been altered for any lambdas) and added code to purge stale locks while waiting on locks


How to: Multiple Publisher to Single Subscriber

Is your feature request related to a problem? Please describe.
How to map multiple publisher with same topic name into single subscriber (Many to One) or (Many to Many) in the same machine?
For example, I create two publisher, Pub1 and  Pub2, one subscriber Sub1, all of them use topic /test/topic,
then I get warning when using ecal_mon_gui: 2 publishers,
Is that Ok if I put multiple publisher in single machine?  Will that cause some unexpected behaviour?
Which is the best way to achieve Many to One mode or Many to Many pub/sub mode.
Describe the solution you'd like
Describe alternatives you've considered
Additional context

Hi @BriFuture ,
It is totally ok to have multiple publishers.
This warning in eCAL monitor was added only because we had scenarios, where we unintentionally had two publishers for the same topic and users wanted to be made aware of it.
But from eCAL point of view, it's totally ok to have Many to One / Many to Many scenarios.


Setting credentials fails when multiple data sources are used

Preflight Checklist

[X] I have installed the latest version of Power Query SDK.
[X] I have checked existing resources, including the common issues and the release notes.
[X] I have searched for similar issues.

Power Query SDK
0.1.7
Regression From
No response
Platform
Windows
Architecture
x64
OS Version
No response
VSCode version
No response
PQSdkTool Path
No response
Bug Description
When "Set credential" or pqTest set-credential is run for a file that uses multiple data sources, credential setting dies with an error along the lins of: Error: Expected 1 data source in expression, but 2 were found..
Steps to Reproduce
Connector:
section MyTester;

[DataSource.Kind="MyTester"]
shared MyTester.Do = () => "hi";

[DataSource.Kind="MyTester2"]
shared MyTester2.Do = (code) => "hi";

MyTester = [Authentication = [Implicit = []]];

MyTester2 = [Authentication = [Implicit = []]];

Test query:
{ MyTester.Do(), MyTester2.Do("abc") }

Actual Experience
PQTest.exe set-credential `
>> --extension "c:\Users\ben\Desktop\TestConnector\BenTest\bin\AnyCPU\Debug\BenTest.mez"`
>> --queryFile "c:\Users\ben\Desktop\TestConnector\BenTest\BenTest.query.pq"`
>> --prettyPrint -ak Anonymous
Error: Expected 1 data source in expression, but 2 were found.

Expected Experience
Should be allowed to set credentials.
In order for this to work, need a way to specify from the command line which data source I'm setting credentials for, then would need to run set-credentials twice, once per source.
Additional Context
No response

Related: https://github.com/microsoft/vscode-powerquery-sdk/issues/154#issuecomment-1277600947

This issue is preventing me from getting my unit tests to work on VSCode without having to split them into individual *.query.pq files. The new extension is already a great improvement over Visual Studio, having this would be the icing on the cake! 🎂
Is there an ETA on this? :)


BroadLink logspam when internet dies

Home Assistant release (hass --version):
0.56.2
Python release (python3 --version):
Python 3.5.3
Component/platform:
/switch/broadlink.py
Description of problem:
HA fails to reconnect to my BroadLink MP1 device, if my internet/router went down.
Both the BroadLink MP1 and HA reconnects to my router and gets the same IP from DHCP.
I'm able to use the BroadLink MP1 via the Android app, but not from HA.
My log is getting spammed with this:
https://pastebin.com/snYQhe9j
What fixes it is turning the BroadLink MP1 off and on again.

Just taking a guess, but this sounds like an issue with the broadlink mp1. Does restarting HA fix it, or do you have to restart the broadlink mp1?
Also, the android app likely still works since it traverses whatever internet based API broadlink is using for the app vs. the way HA is connecting over LAN.

I have to restart the MP1.
Can I lower the logging somehow, because the log grows by a couple of megabytes daily, if I don't restart the MP1.