Custom "Connect to" Buttons?

Can we do custom Connect to buttons, similar to what is found in Voxel?
Its a button where it tells the client to connect to a preconfigured server... rather than using the multiplayer browser.

Yes with the connectToServer action.
http://minecraft.curseforge.com/projects/custom-main-menu/pages/custom-main-menu/actions


Please update Resources

Adding Azure Stack Wiki
Best regards Hans

Hi @hvredevoort, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

@hvredevoort : Thanks for your contribution to the Azure documentation! The author, @azdocprs, has been notified to review your proposed change.

@tysonn Hi Tyson. Can you please review this proposed change to a TOC? Thanks.

@hvredevoort Thanks for the suggestion, Hans! Unfortunately, we're in the process of removing lists of community resources like this because they don't contain technical content.


Can you share the AJI calculation code?

Can you share the AJI calculation code?

It's here.
https://github.com/PeterJackNaylor/DRFNS/blob/master/src_RealData/utils.py


If PR stats table is first item in the PR, the "already published" check fails

If there is no other content in the PR body, the check in alreadyPublished.js returns false instead of true, and two tables get published to the PR description. I believe this is because the regex is prefixed with a new line character, so if there is not a line above the table, it returns false: const regexp = new RegExp(\n(${TABLE_TITLE})\n);. Unfortunately, I don't have time for a PR now, but wanted to open the issue so it wasn't lost! Thanks Manuel

Ohh great finding! Thanks @derek-young
No problem, I'll send the fix as soon as possible.

Fixed in v2.0.3

Hi @derek-young we forgot to build the changes (yarn build) LOL.
Now they are published in v2.1.0
Just in case you still had problems with the action.


Implement Future for MockServer

This allows the server to be awaited on, resolving when all the registered mocks are verified.

Hey!
Generally speaking: can you give me some more details on what this is useful for? What scenario pushed you to submit this PR?
Talking about the PR: this will just hang forever if assumptions are not verified, that seems a serious pitfall API-wise I am not sure I would like to push onto users.

I use wiremock for an integration test suite where the requests are made to the mock server from a separate container. I'd like to be able to detect when all the conditions are met. Currently I'm using a fork with the above change to accomplish this. You're correct that it will hang, I don't actually .await on this future directly but wrap it in a timeout mechanism so the future will resolve when the mock server resolves, or when the timeout hits, whichever comes first

I'd say let's start with a public verify method.
I understand the usecase, I would probably prefer a dedicated method to cater for it (e.g. block_until_verified or something along those lines, with a timeout baked in and configurable). It requires some more thinking.


Settings sync removes extensions

started windows VM
every extension that got auto-updated get deleted afterwards

sync-log
[2022-10-25 12:19:53.278] [settingssync] [info] Using settings sync service https://vscode-sync-insiders.trafficmanager.net/
[2022-10-25 12:19:53.278] [settingssync] [info] Auto Sync is enabled.
[2022-10-25 12:19:53.278] [settingssync] [info] Auto Sync: Suspended until auth token is available.
[2022-10-25 12:19:58.798] [settingssync] [info] Auto Sync: Triggered by Interval
[2022-10-25 12:19:58.798] [settingssync] [info] Sync started.
[2022-10-25 12:20:00.455] [settingssync] [info] Deleting from backup /C:/Users/jrieken/AppData/Roaming/Code - Insiders/User/sync/globalState/20220920T152848.json
[2022-10-25 12:20:00.456] [settingssync] [info] Deleting from backup /C:/Users/jrieken/AppData/Roaming/Code - Insiders/User/sync/globalState/20220920T153456.json
[2022-10-25 12:20:00.456] [settingssync] [info] Deleting from backup /C:/Users/jrieken/AppData/Roaming/Code - Insiders/User/sync/globalState/20220923T161535.json
[2022-10-25 12:20:00.456] [settingssync] [info] Deleting from backup /C:/Users/jrieken/AppData/Roaming/Code - Insiders/User/sync/globalState/20220923T163925.json
[2022-10-25 12:20:00.456] [settingssync] [info] Deleting from backup /C:/Users/jrieken/AppData/Roaming/Code - Insiders/User/sync/globalState/20220923T172010.json
[2022-10-25 12:20:00.456] [settingssync] [info] Deleting from backup /C:/Users/jrieken/AppData/Roaming/Code - Insiders/User/sync/globalState/20220923T173511.json
[2022-10-25 12:20:01.291] [settingssync] [info] Profiles: Updated last synchronized profiles.
[2022-10-25 12:20:04.245] [settingssync] [info] Deleting from backup /C:/Users/jrieken/AppData/Roaming/Code - Insiders/User/sync/settings/20220920T152846.json
[2022-10-25 12:20:04.606] [settingssync] [info] Settings: Updated local settings
[2022-10-25 12:20:05.197] [settingssync] [info] Settings: Updated last synchronized settings
[2022-10-25 12:20:05.393] [settingssync] [info] Keybindings: No changes found during synchronizing keybindings.
[2022-10-25 12:20:05.417] [settingssync] [info] Snippets: No changes found during synchronizing snippets.
[2022-10-25 12:20:05.436] [settingssync] [info] Tasks: No changes found during synchronizing tasks.
[2022-10-25 12:20:05.604] [settingssync] [info] GlobalState: Updated global state ["workbench.activity.showProfiles","mergeEditor/showNonConflictingChanges","workbench.explorer.views.state.hidden","workbench.activity.pinnedViewlets2","memento/gettingStartedService","recently.opened","workbench.welcomePage.walkthroughMetadata","commandPalette.mru.cache","commandPalette.mru.counter","github-jrieken","memento/workbench.editor.keybindings","tabs-list-width-horizontal","menu.hiddenCommands","snippets.usageTimestamps","mergeEditor/layout"]
[2022-10-25 12:20:05.605] [settingssync] [info] GlobalState: Updated local ui state
[2022-10-25 12:20:24.888] [settingssync] [info] GlobalState: Updated remote ui state
[2022-10-25 12:20:24.898] [settingssync] [info] GlobalState: Updated last synchronized ui state
[2022-10-25 12:20:29.504] [settingssync] [info] Extensions: Installed extension. jrieken.vscode-pr-pinger 0.0.6
[2022-10-25 12:20:34.162] [settingssync] [info] Extensions: Updated remote extensions. Removed: ["ipatalas.vscode-postfix-ts","ms-ceintl.vscode-language-pack-de","ms-vscode-remote.remote-containers","ms-vscode-remote.remote-ssh","rust-lang.rust-analyzer","ms-vscode.hexeditor","ms-vscode.vscode-github-issue-notebooks","ms-vscode.vscode-typescript-next","ms-vscode.js-debug-nightly","github.vscode-pull-request-github","github.codespaces","github.copilot","github.remotehub"].
[2022-10-25 12:20:34.178] [settingssync] [info] Extensions: Updated last synchronized extensions.
[2022-10-25 12:20:34.184] [settingssync] [info] Syncing profile. suggest
[2022-10-25 12:20:34.186] [settingssync] [info] Settings (suggest): Not synced yet. Last sync resource does not exist.
[2022-10-25 12:20:34.479] [settingssync] [info] Settings (suggest): Updated local settings
[2022-10-25 12:20:34.488] [settingssync] [info] Settings (suggest): Updated last synchronized settings
[2022-10-25 12:20:34.493] [settingssync] [info] Keybindings (suggest): Not synced yet. Last sync resource does not exist.
[2022-10-25 12:20:34.665] [settingssync] [info] Keybindings (suggest): No changes found during synchronizing keybindings.
[2022-10-25 12:20:34.673] [settingssync] [info] Keybindings (suggest): Updated last synchronized keybindings
[2022-10-25 12:20:34.676] [settingssync] [info] Snippets (suggest): Not synced yet. Last sync resource does not exist.
[2022-10-25 12:20:34.804] [settingssync] [info] Snippets (suggest): No changes found during synchronizing snippets.
[2022-10-25 12:20:34.812] [settingssync] [info] Snippets (suggest): Updated last synchronized snippets
[2022-10-25 12:20:34.816] [settingssync] [info] Tasks (suggest): Not synced yet. Last sync resource does not exist.
[2022-10-25 12:20:34.903] [settingssync] [info] Tasks (suggest): No changes found during synchronizing tasks.
[2022-10-25 12:20:34.912] [settingssync] [info] Tasks (suggest): Updated last synchronized tasks
[2022-10-25 12:20:34.914] [settingssync] [info] GlobalState (suggest): Not synced yet. Last sync resource does not exist.
[2022-10-25 12:20:35.158] [settingssync] [info] GlobalState (suggest): Updated global state ["workbench.panel.alignment","workbench.activity.pinnedViewlets2","workbench.panel.pinnedPanels","workbench.explorer.views.state.hidden","workbench.auxiliarybar.pinnedPanels","workbench.view.debug.state.hidden","colorThemeData","workbench.view.extension.gitlens.state.hidden","workbench.view.extension.gitlensPanel.state.hidden","workbench.panel.repl.hidden","workbench.view.extensions.state.hidden","workbench.panel.markers.hidden","workbench.panel.output.hidden","terminal.hidden","workbench.view.search.state.hidden","workbench.scm.views.state.hidden","workbench.telemetryOptOutShown","memento/gettingStartedService","workbench.welcomePage.walkthroughMetadata","commandPalette.mru.cache","commandPalette.mru.counter"]
[2022-10-25 12:20:35.159] [settingssync] [info] GlobalState (suggest): Updated local ui state
[2022-10-25 12:20:35.168] [settingssync] [info] GlobalState (suggest): Updated last synchronized ui state
[2022-10-25 12:20:35.172] [settingssync] [info] Extensions (suggest): Not synced yet. Last sync resource does not exist.
[2022-10-25 12:20:35.904] [settingssync] [info] Extensions (suggest): Installed extension. ms-ceintl.vscode-language-pack-de 1.73.10191010
[2022-10-25 12:20:35.978] [settingssync] [info] Extensions (suggest): Not synced yet. Last sync resource does not exist.
[2022-10-25 12:20:38.651] [settingssync] [info] Extensions (suggest): Updated remote extensions. Added: ["ms-vscode-remote.remote-wsl-recommender"].
[2022-10-25 12:20:38.660] [settingssync] [info] Extensions (suggest): Updated last synchronized extensions.
[2022-10-25 12:20:38.663] [settingssync] [info] Syncing profile. testing
[2022-10-25 12:20:38.667] [settingssync] [info] Settings (testing): Not synced yet. Last sync resource does not exist.
[2022-10-25 12:20:38.763] [settingssync] [info] Settings (testing): No changes found during synchronizing settings.
[2022-10-25 12:20:38.774] [settingssync] [info] Settings (testing): Updated last synchronized settings
[2022-10-25 12:20:38.778] [settingssync] [info] Keybindings (testing): Not synced yet. Last sync resource does not exist.
[2022-10-25 12:20:38.872] [settingssync] [info] Keybindings (testing): No changes found during synchronizing keybindings.
[2022-10-25 12:20:38.880] [settingssync] [info] Keybindings (testing): Updated last synchronized keybindings
[2022-10-25 12:20:38.884] [settingssync] [info] Snippets (testing): Not synced yet. Last sync resource does not exist.
[2022-10-25 12:20:38.974] [settingssync] [info] Snippets (testing): No changes found during synchronizing snippets.
[2022-10-25 12:20:38.981] [settingssync] [info] Snippets (testing): Updated last synchronized snippets
[2022-10-25 12:20:38.986] [settingssync] [info] Tasks (testing): Not synced yet. Last sync resource does not exist.
[2022-10-25 12:20:39.086] [settingssync] [info] Tasks (testing): No changes found during synchronizing tasks.
[2022-10-25 12:20:39.096] [settingssync] [info] Tasks (testing): Updated last synchronized tasks
[2022-10-25 12:20:39.104] [settingssync] [info] GlobalState (testing): Not synced yet. Last sync resource does not exist.
[2022-10-25 12:20:39.338] [settingssync] [info] GlobalState (testing): Updated global state ["workbench.panel.alignment","workbench.activity.pinnedViewlets2","workbench.panel.pinnedPanels","workbench.explorer.views.state.hidden","workbench.auxiliarybar.pinnedPanels","workbench.view.extensions.state.hidden","workbench.panel.repl.hidden","workbench.view.debug.state.hidden","workbench.view.extension.jupyter-variables.state.hidden","workbench.view.extension.jupyter.state.hidden","workbench.panel.markers.hidden","workbench.panel.output.hidden","terminal.hidden","workbench.view.search.state.hidden","workbench.scm.views.state.hidden","workbench.telemetryOptOutShown","memento/gettingStartedService","workbench.welcomePage.walkthroughMetadata","colorThemeData","memento/notebookGettingStarted2","commandPalette.mru.cache","commandPalette.mru.counter"]
[2022-10-25 12:20:39.339] [settingssync] [info] GlobalState (testing): Updated local ui state
[2022-10-25 12:20:39.345] [settingssync] [info] GlobalState (testing): Updated last synchronized ui state
[2022-10-25 12:20:39.349] [settingssync] [info] Extensions (testing): Not synced yet. Last sync resource does not exist.
[2022-10-25 12:20:40.594] [settingssync] [info] Extensions (testing): Installed extension. ms-toolsai.jupyter-keymap 1.0.0
[2022-10-25 12:20:40.780] [settingssync] [info] Extensions (testing): Not synced yet. Last sync resource does not exist.
[2022-10-25 12:20:41.384] [settingssync] [info] Extensions (testing): Installed extension. ms-toolsai.jupyter-renderers 1.0.10
[2022-10-25 12:20:41.440] [settingssync] [info] Extensions (testing): Not synced yet. Last sync resource does not exist.
[2022-10-25 12:20:42.096] [settingssync] [info] Extensions (testing): Installed extension. ms-toolsai.vscode-jupyter-cell-tags 0.1.6
[2022-10-25 12:20:42.115] [settingssync] [info] Extensions (testing): Installed extension. ms-toolsai.vscode-jupyter-slideshow 0.1.5
[2022-10-25 12:20:42.168] [settingssync] [info] Extensions (testing): Not synced yet. Last sync resource does not exist.
[2022-10-25 12:20:45.250] [settingssync] [info] Extensions (testing): Updated remote extensions. Added: ["ms-vscode-remote.remote-wsl-recommender"].
[2022-10-25 12:20:45.255] [settingssync] [info] Extensions (testing): Updated last synchronized extensions.
[2022-10-25 12:20:45.257] [settingssync] [info] Sync done. Took 46460ms
[2022-10-25 12:20:45.258] [settingssync] [info] Auto Sync: Triggered by Activity
[2022-10-25 12:20:45.258] [settingssync] [info] Sync started.
[2022-10-25 12:20:45.343] [settingssync] [info] Profiles: No changes found during synchronizing profiles.
[2022-10-25 12:20:45.356] [settingssync] [info] Settings: No changes found during synchronizing settings.
[2022-10-25 12:20:45.362] [settingssync] [info] Keybindings: No changes found during synchronizing keybindings.
[2022-10-25 12:20:45.379] [settingssync] [info] Snippets: No changes found during synchronizing snippets.
[2022-10-25 12:20:45.390] [settingssync] [info] Tasks: No changes found during synchronizing tasks.

sharedProcess-log
[2022-10-25 12:19:53.969] [sharedprocess] [info] Starting worker process with pid 4712 (type: fileWatcher, window: 1).
[2022-10-25 12:19:54.275] [sharedprocess] [info] Deleted from disk ms-vscode.vscode-github-issue-notebooks c:\Users\jrieken\.vscode-insiders\extensions\ms-vscode.vscode-github-issue-notebooks-0.0.121
[2022-10-25 12:19:55.097] [sharedprocess] [info] WSL is not installed, so could not detect WSL profiles
[2022-10-25 12:19:57.513] [sharedprocess] [info] Getting Manifest... eamodio.gitlens
[2022-10-25 12:19:57.513] [sharedprocess] [info] Getting Manifest... github.codespaces
[2022-10-25 12:19:57.520] [sharedprocess] [info] Getting Manifest... github.copilot
[2022-10-25 12:19:57.521] [sharedprocess] [info] Getting Manifest... github.remotehub
[2022-10-25 12:19:57.523] [sharedprocess] [info] Getting Manifest... github.vscode-pull-request-github
[2022-10-25 12:19:57.525] [sharedprocess] [info] Getting Manifest... ipatalas.vscode-postfix-ts
[2022-10-25 12:19:57.527] [sharedprocess] [info] Getting Manifest... ms-ceintl.vscode-language-pack-de
[2022-10-25 12:19:57.528] [sharedprocess] [info] Getting Manifest... ms-vscode-remote.remote-containers
[2022-10-25 12:19:57.529] [sharedprocess] [info] Getting Manifest... ms-vscode-remote.remote-ssh
[2022-10-25 12:19:57.530] [sharedprocess] [info] Getting Manifest... ms-vscode.hexeditor
[2022-10-25 12:19:57.531] [sharedprocess] [info] Getting Manifest... ms-vscode.js-debug-nightly
[2022-10-25 12:19:57.531] [sharedprocess] [info] Getting Manifest... ms-vscode.remote-repositories
[2022-10-25 12:19:57.532] [sharedprocess] [info] Getting Manifest... ms-vscode.vscode-github-issue-notebooks
[2022-10-25 12:19:57.533] [sharedprocess] [info] Getting Manifest... ms-vscode.vscode-typescript-next
[2022-10-25 12:19:57.534] [sharedprocess] [info] Getting Manifest... rust-lang.rust-analyzer
[2022-10-25 12:19:57.835] [sharedprocess] [info] Installing extension: github.codespaces
[2022-10-25 12:19:58.388] [sharedprocess] [info] Installing extension: ms-ceintl.vscode-language-pack-de
[2022-10-25 12:19:58.390] [sharedprocess] [info] Installing extension: ms-vscode-remote.remote-ssh
[2022-10-25 12:19:58.392] [sharedprocess] [info] Installing extension: ms-vscode-remote.remote-containers
[2022-10-25 12:19:58.451] [sharedprocess] [info] Installing extension: github.copilot
[2022-10-25 12:19:58.452] [sharedprocess] [info] Installing extension: github.vscode-pull-request-github
[2022-10-25 12:19:58.453] [sharedprocess] [info] Installing extension: github.remotehub
[2022-10-25 12:19:58.454] [sharedprocess] [info] Installing extension: ms-vscode.vscode-github-issue-notebooks
[2022-10-25 12:19:58.455] [sharedprocess] [info] Installing extension: ms-vscode.hexeditor
[2022-10-25 12:19:58.455] [sharedprocess] [info] Installing extension: ms-vscode.remote-repositories
[2022-10-25 12:19:58.534] [sharedprocess] [info] Installing extension: ipatalas.vscode-postfix-ts
[2022-10-25 12:19:58.535] [sharedprocess] [info] Installing extension: ms-vscode.vscode-typescript-next
[2022-10-25 12:19:58.536] [sharedprocess] [info] Installing extension: rust-lang.rust-analyzer
[2022-10-25 12:19:58.541] [sharedprocess] [info] Installing extension: eamodio.gitlens
[2022-10-25 12:19:58.545] [sharedprocess] [info] Installing extension: ms-vscode.js-debug-nightly
[2022-10-25 12:20:01.260] [sharedprocess] [info] Getting Manifest... ms-vscode.remote-repositories
[2022-10-25 12:20:03.619] [sharedprocess] [info] Downloaded extension: github.codespaces c:\Users\jrieken\AppData\Roaming\Code - Insiders\CachedExtensionVSIXs\github.codespaces-1.12.1
[2022-10-25 12:20:03.644] [sharedprocess] [info] Waiting for already requested installing extension ms-vscode.remote-repositories github.remotehub
[2022-10-25 12:20:06.283] [sharedprocess] [info] Downloaded extension: ms-ceintl.vscode-language-pack-de c:\Users\jrieken\AppData\Roaming\Code - Insiders\CachedExtensionVSIXs\ms-ceintl.vscode-language-pack-de-1.72.10120946
[2022-10-25 12:20:06.286] [sharedprocess] [info] Downloaded extension: ms-vscode-remote.remote-ssh c:\Users\jrieken\AppData\Roaming\Code - Insiders\CachedExtensionVSIXs\ms-vscode-remote.remote-ssh-0.90.1
[2022-10-25 12:20:06.286] [sharedprocess] [info] Downloaded extension: github.copilot c:\Users\jrieken\AppData\Roaming\Code - Insiders\CachedExtensionVSIXs\github.copilot-1.55.7117
[2022-10-25 12:20:07.112] [sharedprocess] [info] Extracted extension to c:\Users\jrieken\.vscode-insiders\extensions\.903369ae-557d-4d4c-8b39-f608f599fcaa: github.copilot
[2022-10-25 12:20:07.193] [sharedprocess] [info] Renamed to c:\Users\jrieken\.vscode-insiders\extensions\github.copilot-1.55.7117
[2022-10-25 12:20:07.311] [sharedprocess] [info] Extracting completed. github.copilot
[2022-10-25 12:20:07.323] [sharedprocess] [info] Downloaded extension: ms-vscode.hexeditor c:\Users\jrieken\AppData\Roaming\Code - Insiders\CachedExtensionVSIXs\ms-vscode.hexeditor-1.9.9
[2022-10-25 12:20:07.337] [sharedprocess] [info] Downloaded extension: ms-vscode.remote-repositories c:\Users\jrieken\AppData\Roaming\Code - Insiders\CachedExtensionVSIXs\ms-vscode.remote-repositories-0.23.2022102501
[2022-10-25 12:20:07.352] [sharedprocess] [info] Downloaded extension: github.vscode-pull-request-github c:\Users\jrieken\AppData\Roaming\Code - Insiders\CachedExtensionVSIXs\github.vscode-pull-request-github-0.53.2022101809
[2022-10-25 12:20:07.352] [sharedprocess] [info] Downloaded extension: ipatalas.vscode-postfix-ts c:\Users\jrieken\AppData\Roaming\Code - Insiders\CachedExtensionVSIXs\ipatalas.vscode-postfix-ts-1.11.3
[2022-10-25 12:20:07.352] [sharedprocess] [info] Downloaded extension: ms-vscode-remote.remote-containers c:\Users\jrieken\AppData\Roaming\Code - Insiders\CachedExtensionVSIXs\ms-vscode-remote.remote-containers-0.261.0
[2022-10-25 12:20:07.409] [sharedprocess] [info] Extension installed successfully: github.copilot
[2022-10-25 12:20:07.432] [sharedprocess] [info] Extracted extension to c:\Users\jrieken\.vscode-insiders\extensions\.151bdd34-607f-47f7-b820-07f8ee5721f0: ms-ceintl.vscode-language-pack-de
[2022-10-25 12:20:07.459] [sharedprocess] [info] Renamed to c:\Users\jrieken\.vscode-insiders\extensions\ms-ceintl.vscode-language-pack-de-1.72.10120946
[2022-10-25 12:20:07.710] [sharedprocess] [info] Extracting completed. ms-ceintl.vscode-language-pack-de
[2022-10-25 12:20:07.949] [sharedprocess] [info] Downloaded extension: github.remotehub c:\Users\jrieken\AppData\Roaming\Code - Insiders\CachedExtensionVSIXs\github.remotehub-0.45.2022102501
[2022-10-25 12:20:07.960] [sharedprocess] [info] Downloaded extension: ms-vscode.vscode-github-issue-notebooks c:\Users\jrieken\AppData\Roaming\Code - Insiders\CachedExtensionVSIXs\ms-vscode.vscode-github-issue-notebooks-0.0.126
[2022-10-25 12:20:07.961] [sharedprocess] [info] Adding language packs from the extension ms-ceintl.vscode-language-pack-de
[2022-10-25 12:20:08.000] [sharedprocess] [info] Downloaded extension: ms-vscode.vscode-typescript-next c:\Users\jrieken\AppData\Roaming\Code - Insiders\CachedExtensionVSIXs\ms-vscode.vscode-typescript-next-4.9.20221018
[2022-10-25 12:20:08.001] [sharedprocess] [info] Downloaded extension: ms-vscode.js-debug-nightly c:\Users\jrieken\AppData\Roaming\Code - Insiders\CachedExtensionVSIXs\ms-vscode.js-debug-nightly-2022.10.1317
[2022-10-25 12:20:08.336] [sharedprocess] [info] Downloaded extension: eamodio.gitlens c:\Users\jrieken\AppData\Roaming\Code - Insiders\CachedExtensionVSIXs\eamodio.gitlens-13.0.3
[2022-10-25 12:20:08.357] [sharedprocess] [info] Extension installed successfully: ms-ceintl.vscode-language-pack-de
[2022-10-25 12:20:08.839] [sharedprocess] [info] Extracted extension to c:\Users\jrieken\.vscode-insiders\extensions\.312b860b-1bca-4055-8d02-af4957912634: ms-vscode.hexeditor
[2022-10-25 12:20:08.902] [sharedprocess] [info] Extracted extension to c:\Users\jrieken\.vscode-insiders\extensions\.ed228eee-74ac-4483-acb0-a21daf99403f: ms-vscode.remote-repositories
[2022-10-25 12:20:08.903] [sharedprocess] [info] Renamed to c:\Users\jrieken\.vscode-insiders\extensions\ms-vscode.hexeditor-1.9.9
[2022-10-25 12:20:08.928] [sharedprocess] [info] Extracting completed. ms-vscode.hexeditor
[2022-10-25 12:20:08.935] [sharedprocess] [info] Renamed to c:\Users\jrieken\.vscode-insiders\extensions\ms-vscode.remote-repositories-0.23.2022102501
[2022-10-25 12:20:08.936] [sharedprocess] [info] Extension installed successfully: ms-vscode.hexeditor
[2022-10-25 12:20:08.952] [sharedprocess] [info] Extracted extension to c:\Users\jrieken\.vscode-insiders\extensions\.b249de3c-ac1b-48bb-a211-6f347b8c4dcb: github.remotehub
[2022-10-25 12:20:08.975] [sharedprocess] [info] Renamed to c:\Users\jrieken\.vscode-insiders\extensions\github.remotehub-0.45.2022102501
[2022-10-25 12:20:09.221] [sharedprocess] [info] Extracting completed. github.remotehub
[2022-10-25 12:20:09.236] [sharedprocess] [info] Extracting completed. ms-vscode.remote-repositories
[2022-10-25 12:20:09.348] [sharedprocess] [info] Extension installed successfully: ms-vscode.remote-repositories
[2022-10-25 12:20:09.348] [sharedprocess] [info] Extension installed successfully: github.remotehub
[2022-10-25 12:20:09.374] [sharedprocess] [info] Extracted extension to c:\Users\jrieken\.vscode-insiders\extensions\.2145e776-6898-46db-b72b-1fe7985c23dc: ms-vscode.vscode-github-issue-notebooks
[2022-10-25 12:20:09.393] [sharedprocess] [info] Extracted extension to c:\Users\jrieken\.vscode-insiders\extensions\.55ac22d0-32a8-4ed9-924e-d9602db528a6: ipatalas.vscode-postfix-ts
[2022-10-25 12:20:09.560] [sharedprocess] [info] Extracted extension to c:\Users\jrieken\.vscode-insiders\extensions\.6c61e728-e448-4d90-83cb-b035a46941b7: github.vscode-pull-request-github
[2022-10-25 12:20:09.568] [sharedprocess] [info] Renamed to c:\Users\jrieken\.vscode-insiders\extensions\ipatalas.vscode-postfix-ts-1.11.3
[2022-10-25 12:20:09.568] [sharedprocess] [info] Renamed to c:\Users\jrieken\.vscode-insiders\extensions\ms-vscode.vscode-github-issue-notebooks-0.0.126
[2022-10-25 12:20:09.596] [sharedprocess] [info] Extracting completed. ipatalas.vscode-postfix-ts
[2022-10-25 12:20:09.603] [sharedprocess] [info] Extracting completed. ms-vscode.vscode-github-issue-notebooks
[2022-10-25 12:20:09.604] [sharedprocess] [info] Renamed to c:\Users\jrieken\.vscode-insiders\extensions\github.vscode-pull-request-github-0.53.2022101809
[2022-10-25 12:20:09.608] [sharedprocess] [info] Extension installed successfully: ipatalas.vscode-postfix-ts
[2022-10-25 12:20:09.631] [sharedprocess] [info] Extension installed successfully: ms-vscode.vscode-github-issue-notebooks
[2022-10-25 12:20:09.822] [sharedprocess] [info] Extracting completed. github.vscode-pull-request-github
[2022-10-25 12:20:09.951] [sharedprocess] [info] Extension installed successfully: github.vscode-pull-request-github
[2022-10-25 12:20:09.998] [sharedprocess] [info] Extracted extension to c:\Users\jrieken\.vscode-insiders\extensions\.abe1e79d-a60e-4703-b462-b951bfc5744f: ms-vscode.js-debug-nightly
[2022-10-25 12:20:10.392] [sharedprocess] [info] Renamed to c:\Users\jrieken\.vscode-insiders\extensions\ms-vscode.js-debug-nightly-2022.10.1317
[2022-10-25 12:20:10.462] [sharedprocess] [info] Extracting completed. ms-vscode.js-debug-nightly
[2022-10-25 12:20:10.476] [sharedprocess] [info] Extension installed successfully: ms-vscode.js-debug-nightly
[2022-10-25 12:20:11.161] [sharedprocess] [info] Extracted extension to c:\Users\jrieken\.vscode-insiders\extensions\.73d4f49b-8e3b-4c38-8f8e-926d73b7bea0: ms-vscode-remote.remote-ssh
[2022-10-25 12:20:11.169] [sharedprocess] [info] Extracted extension to c:\Users\jrieken\.vscode-insiders\extensions\.265eb6a1-a3e8-4531-82af-8be7db93845c: github.codespaces
[2022-10-25 12:20:11.191] [sharedprocess] [info] Renamed to c:\Users\jrieken\.vscode-insiders\extensions\github.codespaces-1.12.1
[2022-10-25 12:20:11.214] [sharedprocess] [info] Renamed to c:\Users\jrieken\.vscode-insiders\extensions\ms-vscode-remote.remote-ssh-0.90.1
[2022-10-25 12:20:11.384] [sharedprocess] [info] Extracting completed. github.codespaces
[2022-10-25 12:20:11.437] [sharedprocess] [info] Extension installed successfully: github.codespaces
[2022-10-25 12:20:11.542] [sharedprocess] [info] Extracting completed. ms-vscode-remote.remote-ssh
[2022-10-25 12:20:11.785] [sharedprocess] [info] Extension installed successfully: ms-vscode-remote.remote-ssh
[2022-10-25 12:20:12.112] [sharedprocess] [info] Downloaded extension: rust-lang.rust-analyzer c:\Users\jrieken\AppData\Roaming\Code - Insiders\CachedExtensionVSIXs\rust-lang.rust-analyzer-0.4.1259-win32-arm64
[2022-10-25 12:20:12.417] [sharedprocess] [info] Extracted extension to c:\Users\jrieken\.vscode-insiders\extensions\.c4d6191c-dced-4155-9c63-4bcb3211cf93: eamodio.gitlens
[2022-10-25 12:20:12.458] [sharedprocess] [info] Renamed to c:\Users\jrieken\.vscode-insiders\extensions\eamodio.gitlens-13.0.3
[2022-10-25 12:20:12.472] [sharedprocess] [info] Extracting completed. eamodio.gitlens
[2022-10-25 12:20:12.483] [sharedprocess] [info] Extension installed successfully: eamodio.gitlens
[2022-10-25 12:20:12.880] [sharedprocess] [info] Extracted extension to c:\Users\jrieken\.vscode-insiders\extensions\.c36af5e0-963d-4bf0-b387-e1da18abbf18: ms-vscode.vscode-typescript-next
[2022-10-25 12:20:12.896] [sharedprocess] [info] Renamed to c:\Users\jrieken\.vscode-insiders\extensions\ms-vscode.vscode-typescript-next-4.9.20221018
[2022-10-25 12:20:12.910] [sharedprocess] [info] Extracting completed. ms-vscode.vscode-typescript-next
[2022-10-25 12:20:12.917] [sharedprocess] [info] Extension installed successfully: ms-vscode.vscode-typescript-next
[2022-10-25 12:20:13.270] [sharedprocess] [info] Extracted extension to c:\Users\jrieken\.vscode-insiders\extensions\.4ea714e9-abe7-4148-a69b-53bdda2ebe15: ms-vscode-remote.remote-containers
[2022-10-25 12:20:13.290] [sharedprocess] [info] Renamed to c:\Users\jrieken\.vscode-insiders\extensions\ms-vscode-remote.remote-containers-0.261.0
[2022-10-25 12:20:13.292] [sharedprocess] [info] Extracted extension to c:\Users\jrieken\.vscode-insiders\extensions\.7e4d287a-cfc0-4211-a501-d4b1bdbb0fc9: rust-lang.rust-analyzer
[2022-10-25 12:20:13.301] [sharedprocess] [info] Extracting completed. ms-vscode-remote.remote-containers
[2022-10-25 12:20:13.305] [sharedprocess] [info] Extension installed successfully: ms-vscode-remote.remote-containers
[2022-10-25 12:20:13.307] [sharedprocess] [info] Renamed to c:\Users\jrieken\.vscode-insiders\extensions\rust-lang.rust-analyzer-0.4.1259-win32-arm64
[2022-10-25 12:20:13.316] [sharedprocess] [info] Extracting completed. rust-lang.rust-analyzer
[2022-10-25 12:20:13.325] [sharedprocess] [info] Extension installed successfully: rust-lang.rust-analyzer
[2022-10-25 12:20:25.452] [sharedprocess] [info] Getting Manifest... jrieken.vscode-pr-pinger
[2022-10-25 12:20:26.139] [sharedprocess] [info] Installing extension: jrieken.vscode-pr-pinger
[2022-10-25 12:20:26.139] [sharedprocess] [info] Installing the extension without checking dependencies and pack jrieken.vscode-pr-pinger
[2022-10-25 12:20:29.001] [sharedprocess] [info] Downloaded extension: jrieken.vscode-pr-pinger c:\Users\jrieken\AppData\Roaming\Code - Insiders\CachedExtensionVSIXs\jrieken.vscode-pr-pinger-0.0.6
[2022-10-25 12:20:29.476] [sharedprocess] [info] Extracted extension to c:\Users\jrieken\.vscode-insiders\extensions\.838a0e73-be9b-4c69-b2b2-b3acbb079616: jrieken.vscode-pr-pinger
[2022-10-25 12:20:29.485] [sharedprocess] [info] Renamed to c:\Users\jrieken\.vscode-insiders\extensions\jrieken.vscode-pr-pinger-0.0.6
[2022-10-25 12:20:29.493] [sharedprocess] [info] Extracting completed. jrieken.vscode-pr-pinger
[2022-10-25 12:20:29.504] [sharedprocess] [info] Extension installed successfully: jrieken.vscode-pr-pinger
[2022-10-25 12:20:35.712] [sharedprocess] [info] Getting Manifest... ms-ceintl.vscode-language-pack-de
[2022-10-25 12:20:35.717] [sharedprocess] [info] Installing extension: ms-ceintl.vscode-language-pack-de
[2022-10-25 12:20:35.717] [sharedprocess] [info] Installing the extension without checking dependencies and pack ms-ceintl.vscode-language-pack-de
[2022-10-25 12:20:35.813] [sharedprocess] [info] Adding language packs from the extension ms-ceintl.vscode-language-pack-de
[2022-10-25 12:20:35.904] [sharedprocess] [info] Extension installed successfully: ms-ceintl.vscode-language-pack-de
[2022-10-25 12:20:39.778] [sharedprocess] [info] Getting Manifest... ms-toolsai.jupyter-renderers
[2022-10-25 12:20:39.784] [sharedprocess] [info] Getting Manifest... ms-toolsai.jupyter-keymap
[2022-10-25 12:20:40.110] [sharedprocess] [info] Getting Manifest... ms-toolsai.vscode-jupyter-slideshow
[2022-10-25 12:20:40.112] [sharedprocess] [info] Getting Manifest... ms-toolsai.vscode-jupyter-cell-tags
[2022-10-25 12:20:40.285] [sharedprocess] [info] Installing extension: ms-toolsai.jupyter-renderers
[2022-10-25 12:20:40.285] [sharedprocess] [info] Installing the extension without checking dependencies and pack ms-toolsai.jupyter-renderers
[2022-10-25 12:20:40.299] [sharedprocess] [info] Installing extension: ms-toolsai.jupyter-keymap
[2022-10-25 12:20:40.299] [sharedprocess] [info] Installing the extension without checking dependencies and pack ms-toolsai.jupyter-keymap
[2022-10-25 12:20:40.486] [sharedprocess] [info] Downloaded extension: ms-toolsai.jupyter-renderers c:\Users\jrieken\AppData\Roaming\Code - Insiders\CachedExtensionVSIXs\ms-toolsai.jupyter-renderers-1.0.10
[2022-10-25 12:20:40.509] [sharedprocess] [info] Downloaded extension: ms-toolsai.jupyter-keymap c:\Users\jrieken\AppData\Roaming\Code - Insiders\CachedExtensionVSIXs\ms-toolsai.jupyter-keymap-1.0.0
[2022-10-25 12:20:40.528] [sharedprocess] [info] Extracted extension to c:\Users\jrieken\.vscode-insiders\extensions\.5f3c1ff5-f386-42f4-bb43-ae17f9f0cf4b: ms-toolsai.jupyter-keymap
[2022-10-25 12:20:40.568] [sharedprocess] [info] Renamed to c:\Users\jrieken\.vscode-insiders\extensions\ms-toolsai.jupyter-keymap-1.0.0
[2022-10-25 12:20:40.586] [sharedprocess] [info] Extracting completed. ms-toolsai.jupyter-keymap
[2022-10-25 12:20:40.594] [sharedprocess] [info] Extension installed successfully: ms-toolsai.jupyter-keymap
[2022-10-25 12:20:40.607] [sharedprocess] [info] Installing extension: ms-toolsai.vscode-jupyter-slideshow
[2022-10-25 12:20:40.608] [sharedprocess] [info] Installing the extension without checking dependencies and pack ms-toolsai.vscode-jupyter-slideshow
[2022-10-25 12:20:40.608] [sharedprocess] [info] Installing extension: ms-toolsai.vscode-jupyter-cell-tags
[2022-10-25 12:20:40.609] [sharedprocess] [info] Installing the extension without checking dependencies and pack ms-toolsai.vscode-jupyter-cell-tags
[2022-10-25 12:20:41.363] [sharedprocess] [info] Extracted extension to c:\Users\jrieken\.vscode-insiders\extensions\.5c4e6d5f-24a3-4b4c-9a59-ed7cf9aaa7d7: ms-toolsai.jupyter-renderers
[2022-10-25 12:20:41.370] [sharedprocess] [info] Renamed to c:\Users\jrieken\.vscode-insiders\extensions\ms-toolsai.jupyter-renderers-1.0.10
[2022-10-25 12:20:41.376] [sharedprocess] [info] Extracting completed. ms-toolsai.jupyter-renderers
[2022-10-25 12:20:41.384] [sharedprocess] [info] Extension installed successfully: ms-toolsai.jupyter-renderers
[2022-10-25 12:20:42.014] [sharedprocess] [info] Downloaded extension: ms-toolsai.vscode-jupyter-cell-tags c:\Users\jrieken\AppData\Roaming\Code - Insiders\CachedExtensionVSIXs\ms-toolsai.vscode-jupyter-cell-tags-0.1.6
[2022-10-25 12:20:42.047] [sharedprocess] [info] Downloaded extension: ms-toolsai.vscode-jupyter-slideshow c:\Users\jrieken\AppData\Roaming\Code - Insiders\CachedExtensionVSIXs\ms-toolsai.vscode-jupyter-slideshow-0.1.5
[2022-10-25 12:20:42.066] [sharedprocess] [info] Extracted extension to c:\Users\jrieken\.vscode-insiders\extensions\.9a866147-6659-46c5-81a2-28757ab39660: ms-toolsai.vscode-jupyter-cell-tags
[2022-10-25 12:20:42.083] [sharedprocess] [info] Renamed to c:\Users\jrieken\.vscode-insiders\extensions\ms-toolsai.vscode-jupyter-cell-tags-0.1.6
[2022-10-25 12:20:42.087] [sharedprocess] [info] Extracted extension to c:\Users\jrieken\.vscode-insiders\extensions\.f015f5a1-ec9f-4a44-b370-bb563198ea10: ms-toolsai.vscode-jupyter-slideshow
[2022-10-25 12:20:42.089] [sharedprocess] [info] Extracting completed. ms-toolsai.vscode-jupyter-cell-tags
[2022-10-25 12:20:42.096] [sharedprocess] [info] Extension installed successfully: ms-toolsai.vscode-jupyter-cell-tags
[2022-10-25 12:20:42.101] [sharedprocess] [info] Renamed to c:\Users\jrieken\.vscode-insiders\extensions\ms-toolsai.vscode-jupyter-slideshow-0.1.5
[2022-10-25 12:20:42.107] [sharedprocess] [info] Extracting completed. ms-toolsai.vscode-jupyter-slideshow
[2022-10-25 12:20:42.115] [sharedprocess] [info] Extension installed successfully: ms-toolsai.vscode-jupyter-slideshow

After analysing logs, I suspect that this is caused by the profiles. It seems the above machine that removed the extensions

was not having any profiles before this session
in this session, settings started importing profiles, this made VS Code to enter into profile mode
at the same time, the window has start updating extensions
there is a race condition between VS Code entering into profile mode and auto updating extensions which could have caused this data loss.

To explain in detail, when VS Code enters into profile mode, I migrate extensions installed in the default profile into extensions manifest file. It might have happen that when auto update of extensions is triggered, VS Code is still in no profile mode and therefore auto updated extensions are extracted into extensions folder but not captured in the default extensions manifest file. The migrated default extensions manifest file still contain outdated old extensions which were marked uninstalled by the system after auto update. Therefore when extensions sync was triggered (from timing perspective that happened after auto updates are finished), most of these auto updated extensions were removed as the system did not return them when asked for installed extensions in the default profile. I said only most of these auto updated extensions because, eamodio.gitlens that got auto updated at the same time was not removed. Unfortunately I do not know the reason behind this.
Since this is a combination of profiles and settings sync which is not enabled in stable, moving this to next release.


nixos/nat: optional networking.nat.externalInterface

Motivation for this change
networking.nat.externalInterface is not required in the simple cases
Moreover, networking.nat.externalInterface is not always known at the configuration time
for example, on a laptop (which might provide nat for the virtual machines or hosapd-connected devices) externalInterface flips between eth0 and wlan0 depending on whether WiFi or Ethernet cable are connected

Let's see if the nat tests (which don't test this new feature yet) still work.
@GrahamcOfBorg test nat.firewall nat.standalone

Failure on x86_64-linux (full log)
Attempted: tests.nat.firewall, tests.nat.standalone
Partial log (click to expand)
the VM quit before connecting
cleaning up
killing client (pid 594)
killing router (pid 606)
killing server (pid 618)
vde_switch: EOF on stdin, cleaning up and exiting
vde_switch: EOF on stdin, cleaning up and exiting
vde_switch: Could not remove ctl dir '/build/vde1.ctl': Directory not empty
builder for '/nix/store/g32f450r53v1jzzv7qhp94l4xncdl6n6-vm-test-run-natStandalone.drv' failed with exit code 255
error: build of '/nix/store/g32f450r53v1jzzv7qhp94l4xncdl6n6-vm-test-run-natStandalone.drv', '/nix/store/p5xsypnlvg00gqzhywkxzn7famqzj0si-vm-test-run-natWithFirewall.drv' failed

Success on aarch64-linux (full log)
Attempted: tests.nat.firewall, tests.nat.standalone
Partial log (click to expand)
cleaning up
killing client (pid 628)
killing server (pid 654)
killing router (pid 641)
vde_switch: EOF on stdin, cleaning up and exiting
vde_switch: EOF on stdin, cleaning up and exiting
vde_switch: vde_switch: Could not remove ctl dir '/build/vde2.ctl': Directory not emptyCould not remove ctl dir '/build/vde1.ctl': Directory not empty

/nix/store/kagmbn6sa3x46i8agshz35mbym3q5bzr-vm-test-run-natWithFirewall
/nix/store/cgrhb6h20hykflbhkv9a93mhmdk7ai07-vm-test-run-natStandalone

x86_64-linux: Sporadic failure related to the builder machine, I've seen these on hydra too. Can be ignored. Tests succeed on my local machine.

It just allows networking.nat.externalInterface to be null or not defined
It should not affect existing configurations as they all have networking.nat.externalInterface set.


Requsting modification of SubpTool

Hi,
As I used the SubpTool.exe for long time know, every issues I encounter with wrong editing format is highlighted by the SubpTool except for one.
That is when these two Line  <Line Text and <Timing Start  has swap positions.
While Editing There's a chance that the order of these two lines will be changed by mistake. Then when encoding the xml to subp it show that there's an error but it's not  highlighting which Line number is causing the fault.
That is what it showed
Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object.
   at SubpTool.Subp.SubpEntry.Write(Stream outputStream, Encoding encoding)
   at SubpTool.Subp.SubpFile.Write(Stream outputStream, Encoding encoding)
   at SubpTool.Program.PackSubp(String path, Encoding encoding)
   at SubpTool.Program.Main(String[] args)

You'd have to provide the file that caused that error.

https://mega.nz/#!uZtFCJhA!TmDTL5YtB8gO0o8ZhZN36wru0akbuLU1ajKPVt3BnR0

Invalid Subp XML-files will now crash in v0.2.5. and the error message will contail the line and position of the issue.

Thanks


Metrics - Adds ProgramCacheStats::water_level

Problem
It is hard to tell whether or not the program cache is over-flowing from a lack of evictions. An explicit metric for the water level of loaded entries (their count is limited by the capacity of the cache) would make it easier to monitor.
Summary of Changes
Adds ProgramCacheStats::water_level

I decided against loaded_entries_count because it is ambiguous: Does it mean loaded and kept right now, or loaded during transaction loading in total ...


Mark as unsupported?

Now that https://docs.silverstripe.org/ has been rewritten to use Gatsby instead of this module, it's unlikely that anyone from Silverstripe will be supporting it. It begs the question — will anyone else?
The maintainer is listed as @wilr but I don't know if that's historical or still a commitment he's wanting to retain. @chillu @Martimiz @camfindlay @robbieaverill @UndefinedOffset @halkyon @SpiritLevel and @sachajudd are the top-10 committers.
If someone wants to put up their hand for support, then awesome, but otherwise should we add a "deprecated" note to the header, abandoned warning to the composer metadata, and/or move to https://github.com/silverstripe-archive ?
Maybe we leave this ticket open until end of January and if there has been no takers migrate as suggested. I'd probably do all of:

[ ] Mark on composer/packagist as abandoned
[ ] Move repo to https://github.com/silverstripe-archive
[ ] Add a deprecated note to readme
[ ] Close open RFCs and enhancements

Do we still need to support it for the CWP docs? I assume userhelp will transfer time a Gatsby site at some point too

@sminnee we use it internally on a whole lotta things  so happy to transfer it to me to continue to maintain if you don't want it on the org.

Do we still need to support it for the CWP docs?

...good point. So realistically we're probably looking to keep running it for another year.
@wilr perhaps we re-open that discussion then?
Moving it off the github org isn't critical; I just wanted to have some clarity as to whether anyone was gonna still maintain this module, to which the answer is "yep, Will still needs it" ;)
Do you imagine you'd get around to an SS4 upgrade, though? :p

Gonna close this issue, then since it's not relevant for the next wee while 😊

@sminnee SS4 upgrade is sitting in a PR waiting for a rebase and merge https://github.com/silverstripe/silverstripe-docsviewer/pull/150/files


Add option for FSG files

It works but if an issue occurs we do not have any details and we have to run pocket_sphinx in command line.

Thank you!
Can't remember the reason why I left this unfinished..


Only consult applocal userconfig if metrics are enabled

If metrics are not enabled, we do not need to read and write the user config file.

/azp run

/azp run

I am happy that my comments were addressed here and think this is ready to land as soon as builds and tests pass.

/azp run

Many recursive locking bugs later, success!


docs(update-marble-diagrams): update all rate limiting operators

Description:
Update marble diagrams for all rate limiting operators.
Update marble diagrams for all rate limiting operators.
All images are in the same format as the original images. All file names are identical with the original one.
Included operators are:

audit
auditTime
debounce
debounceTime
sample
sampleTime
throttle
throttleTime

Related issue (if exists):
#4382

Updated according to the original information. For details see https://github.com/ReactiveX/rxjs/pull/4955#issuecomment-520078095

IIRC we put these marble diagrams on hold for the docs, therefore, I close all the related prs. If I got this wrong, feel free to reopen


sumneko.lua-lsp server crash - matcher.lua

I cannot get the extension to work at the moment because I get this error repeatedly until eventually the extension decides to not restart the server.
c:\Users\Feez.vscode\extensions\sumneko.lua-0.9.4\server\bin\lua-language-server: ...extensions/sumneko.lua-0.9.4/server/src/glob\matcher.lua:99: attempt to concatenate a nil value (field 'integer index')
stack traceback:
...extensions/sumneko.lua-0.9.4/server/src/glob\matcher.lua:99: in function <...extensions/sumneko.lua-0.9.4/server/src/glob\matcher.lua:95>
(...tail calls...)
...extensions/sumneko.lua-0.9.4/server/src/glob\matcher.lua:52: in function <...extensions/sumneko.lua-0.9.4/server/src/glob\matcher.lua:50>
(...tail calls...)
...extensions/sumneko.lua-0.9.4/server/src/glob\matcher.lua:41: in function <...extensions/sumneko.lua-0.9.4/server/src/glob\matcher.lua:40>
(...tail calls...)
...extensions/sumneko.lua-0.9.4/server/src/glob\matcher.lua:61: in method 'anyPath'
...extensions/sumneko.lua-0.9.4/server/src/glob\matcher.lua:123: in method 'pattern'
...extensions/sumneko.lua-0.9.4/server/src/glob\matcher.lua:144: in function 'glob.matcher'
...tensions/sumneko.lua-0.9.4/server/src/glob\gitignore.lua:66: in method 'addPattern'
...tensions/sumneko.lua-0.9.4/server/src/glob\gitignore.lua:204: in function 'glob.gitignore'
...de/extensions/sumneko.lua-0.9.4/server/src/workspace.lua:118: in method 'scanFiles'
...de/extensions/sumneko.lua-0.9.4/server/src/workspace.lua:158: in method 'init'
...ions/sumneko.lua-0.9.4/server/src/method\initialized.lua:7: in upvalue 'initAfterConfig'
...ions/sumneko.lua-0.9.4/server/src/method\initialized.lua:65: in field 'callback'
.../.vscode/extensions/sumneko.lua-0.9.4/server/src/rpc.lua:79: in function 'rpc.recieve'
...code/extensions/sumneko.lua-0.9.4/server/src/service.lua:698: in method '_loadProto'
...code/extensions/sumneko.lua-0.9.4/server/src/service.lua:681: in method '_doCompileTask'
...code/extensions/sumneko.lua-0.9.4/server/src/service.lua:923: in method 'onTick'
...code/extensions/sumneko.lua-0.9.4/server/src/service.lua:945: in method 'listen'
...eez.vscode\extensions\sumneko.lua-0.9.4\server\main.lua:32: in main chunk
[C]: in ?
[Info  - 12:22:20 PM] Connection to server got closed. Server will restart

Please check your .gitignore or files.exclude or Lua.workspace.ignoreDir，as far as I know, the glop grammar only support [A-Z0-9], is there an input error?

Here is the content of my .gitignore file:
*
!DreamPred[DEV].lua
!DreamTS.lua

Oh, I did a test and found !DreamPred[DEV].lua works. It seems that the .gitignore does not use the standard glob grammar. I will try to support this.

Seems fixed, thanks!

I'm having trouble getting the gitignore to work for my nested directories. It is matching a ton of files in my workspace when I'm only trying to enable the few in nested directories. Is it possible to only include a few files? The regex grammar above doesn't seem to work for it if the file is nested.

Please update the script manually, and then test whether the configuration is valid:
IgnoredDirectory/*
!IgnoredDirectory/ReservedFile.lua

It should be fixed. If has any other issues, please create a new issue.


Freshdesk ticket creation triggers pagerduty

When a Freshdesk ticket is created trigger pagerduty to page person "on call" in pagerduty schedule.

Freshdesk observer can trigger a webhook call to pagerduty


Add support of LINKMAP fields

Related issue: https://github.com/orientechnologies/orientdb/issues/4848


Proper way to stop audio track

Hi, thanks for the great work.
I am a noob to the whole angular/npm ecosystem so go easy on me.  I have a single audio player that will be playing only one track at a time.  When a user selects a different url, I then change the url of the audio component and it works.
The problem is, I can see in my chrome dev tools that the old track is still being downloaded in the background even though it is no longer needed!.  This is hogging my BW and I would like to fix it.  I think I am using this wrong but please guide me.
This is my code when the track is changed:
 console.log("Track Changed!");`
document.execCommand("Stop", false);

this.audioComponent.pause();

this.audioProvider.stop();

this.audioComponent = null;

//while (this.audioProvider.tracks.length > 0)
//  this.audioProvider.tracks.pop();
this.audioComponent = new AudioTrackComponent(this.audioProvider);

this.audioComponent.track = this.currentTrack;

this.audioComponent.ngOnInit();

//set handler to inform parent track finished playing
this.audioComponent.onFinish.subscribe((event) => this.loadingStatus.emit(2));

`

There are two ways to interact with an audio track. Either by using the AudioTrack component or by means of the provider. In both cases, if you call stop() it should unload the current audio. Is that not happening?

It continues to download the old track for some time.
In the image, track 1 is being played but on switching to 11, it continues to download 1 for about 20-30 seconds.  Same for track 11 to 27.  But notice 27 to 28, if the track is switched before it loads (green region represents waiting time), then it doesn't cancel the old request!  It downloads and plays both tracks.  I hear both tracks being played but I can only control the last one!

Thanks for your time 👍

Hi @azmathmoosa
Thanks for the detailed report. I assume you are testing on the browser with the default HTML Audio. I am afraid that is the way HTML Audio works. I am not sure there is a way to cancel download completely, or is there one?


Compatibility layer

To support automatic interfacing with other plugins that make use of the local filesystem and processes, we could potentially create a function that temporarily replaces all APIs that would do local filesystem and process execution with mirrors that perform distant operations.
I'm not sure how feasibility this is to do and it wouldn't work for vimscript where we cannot replace calls to system() or job control. We can only replace vim.fn.system and vim.fn.jobstart.
List of functions to overwrite
Used by nvim-lspconfig

uv.os_homedir -> session.system_info
uv.os_uname -> session.system_info
uv.fs_stat -> session.metadata
uv.fs_realpath -> session.metadata({ canonicalize = true })
vim.fn.jobstart -> session.spawn
vim.fn.jobwait -> proc.wait

Tracker for support in other ways: https://github.com/neovim/nvim-lspconfig/issues/1317
Used by toggleterm.nvim

vim.fn.termopen -> session.spawn with pty = true

Closing in favor of #97.


Multi site test

Multisite proposal with Wade's scripts.

bits.netbeans.org : generation of javadoc from sources
netbeans.apache.org: some initial basic content with Wade's scripts.

Merging into multisite-test to allow Neil's PRs.


Breaking change in 3.1.8: using config.import with gives "[//] give is not a valid HTTP URL"

Describe the bug
After upgrading from 3.1.7 to 3.1.8 using config.import with optional and using default "://" gives a "[//] is not a valid HTTP URL error".
Stacktrace:
Caused by: java.lang.IllegalArgumentException: [//] is not a valid HTTP URL
	at org.springframework.web.util.UriComponentsBuilder.fromHttpUrl(UriComponentsBuilder.java:316)

Sample
Using this config in application.yml:
spring:
    config.import:
      - optional:vault://
      - optional:configserver:${SPRING_CLOUD_CONFIG_URI://}

As reference this should still be valid use:
Conditionally enable/disable Vault Configuration
In some cases, it can be required to launch an application without Vault. You can express whether a Vault config location should be optional or mandatory (default) through the location string:
optional:vault:// (default location)
See: https://docs.spring.io/spring-cloud-vault/docs/current/reference/html/config-data.html
Using these dependencies:
<spring-boot.version>2.7.13</spring-boot.version>
<spring-cloud.version>2021.0.8</spring-cloud.version>

@ryanjbaxter this codechange is breaking the default use of for example "optional:vault://:" in config.import.
The urisHashCode calls UriComponentsBuilder.fromHttpUrl which results in above error.
https://github.com/spring-cloud/spring-cloud-config/commit/9f3ad4f04b0438cd10aaba7fdeb7904a18962370

@ryanjbaxter will this be also added to spring-cloud-dependencies 2021.0.9?

Correct the fix went into the 3.1.x, 4.0.x, and main branches

@ryanjbaxter the issue still occurs when using the newest spring-cloud-config-client 4.0.4.
WARN 60490 --- [           main] o.s.c.c.c.ConfigServerConfigDataLoader   : Could not locate PropertySource ([ConfigServerConfigDataResource@7c3ebc6b uris = array<String>['//'], optional = true, profiles = 'default']): Invalid URL: //

@MarkvanOsch the problem is actually this line optional:configserver:${SPRING_CLOUD_CONFIG_URI://}.  // is not valid for the config server (like it is vault).  I think what you want is optional:configserver:${SPRING_CLOUD_CONFIG_URI:}

@ryanjbaxter I tried with several setups, but above fails with:
java.lang.IllegalStateException: Unable to load config data from 'optional:configserver:

Caused by: java.lang.IllegalStateException: File extension is not known to any PropertySourceLoader. If the location is meant to reference a directory, it must end in '/' or File.separator

It seems like the behaviour of import checking is changed. This is my setup that I use:

This works fine in local dev with:
Spring cloud 2022.0.2
Spring cloud config client 4.0.2

But gives a WARN with:
Spring cloud 2022.0.3
Spring cloud config client 4.0.3

Is this a different issue maybe?

If you remove ‘//‘ from the spring.config.import statement does the warning go away with 2202.0.4?

No, then I get this ERROR:
java.lang.IllegalStateException: Unable to load config data from 'optional:configserver:'

Caused by: java.lang.IllegalStateException: File extension is not known to any PropertySourceLoader. If the location is meant to reference a directory, it must end in '/' or File.separator

And you have spring cloud config on the class path and it’s enabled?  Can you provide a sample that reproduces the problem?

The last image seems right.
Hard for me to say why you see the warning now with the default profile, I need an example to look at.  // was never a valid was to tell the conflig client to use the default url like it is for vault

Thanks, I will provide a sample to reproduce.

Sample project to reproduce, with readme.
spring_cloud_config_reproduce_2304.zip

Thanks!
This is kind of interesting but the behavior is now expected.
Spring Boot's config data loading happens in 2 phases:

Load configuration without any profiles active in order to collect any activated profiles
Load configuration with all the activated profiles

Prior to 2022.0.3 the config client skipped 1 and only did 2.  Now since we also do 1 your import statement is being run by the config client to try and load configuration without the dev profile active and you see the warning.  Then after the dev profile gets active the config client config data loader doesn't run in phase 2.
I think the reason why you are seeing Unable to load config data from 'optional:configserver:' when you remove the // is because when the // is present it is matching one of the Spring Boot config data loaders and that is handling the import statement.
These are actually 2 completely unrelated behaviors :)

Thanks Ryan, it's clear to me now. 👍
In our setup I will go forward to moving the config.import to the specific cloud profile. So not use it in the default.

I am trying to load vault using spring.config.import; vault:// in the spring config server's application.properties file and still get
Unable to load data from vault://

Caused by: java.lang.IllegalStateException: File extension is not known to any PropertySourceLoader. If the location is meant to reference a directory, it must end in '/' or File.separator

Can anyone help me get why this is still happening on local dev environment? I am using spring cloud 2023.0.0 and boot 3.2.+ ? Thanks

@ENate Hi, this is the setup we now use which solves the earlier issues. It supports local development (without vault/configserver) and cloud deployments (with vault/configserver) using profiles. Maybe you can use it to double check your setup?

Hi @MarkvanOsch thanks. I tried to import both vault and config server properties for other services but still getting an error with the property source not found. The issue is I locked my config server using spring security (and implemented login calls from a database). Next, I will also want services to use the login details which I provided in vault to load their properties from config server. I do not know whether it is best to fetch login details directly from the config server database. But I still feel it is sufficient to provide the login for other services via vault for them to be picked up. But the issue with property source not being loaded could be the problem. The config--server runs fine. The main issue is the inability for other services to pick up the secrets from vault and login to the config server. Thanks again


How to prepare input data?

Hi,
What's the format of input data? I have 10X UMI data and loom files from Velocyto. The web of Phylovelo did not describe the input data in detial.  For example, "sd = pv.scData(count=xx, phylo_tree=xx)".

Hi, thank you for your interest in PhyloVelo. PhyloVelo requires lineage tracing data to estimate the velocity. The input format for PhyloVelo is that you need to provide a UMI count matrix X (pandas.DataFrame) and a phylogenetic tree T (biopython.Phylo.BaseTree) as arguments to the pv.scData function, such as sd=pv.scData(count=X, phylo_tree=T). Only 10X scRNA-seq is not suitable for PhyloVelo analysis. I hope this helps. Please let me know if you have any other questions or feedback.

Hi, thank you for your interest in PhyloVelo. PhyloVelo requires lineage tracing data to estimate the velocity. The input format for PhyloVelo is that you need to provide a UMI count matrix X (pandas.DataFrame) and a phylogenetic tree T (biopython.Phylo.BaseTree) as arguments to the pv.scData function, such as sd=pv.scData(count=X, phylo_tree=T). Only 10X scRNA-seq is not suitable for PhyloVelo analysis. I hope this helps. Please let me know if you have any other questions or feedback.

I'm very intersted in this new tool and working on it. Because i am new to the analysis of scRNA-seq data, i don't know how to generate a phylogenetic tree or get a newick data, could you suggest any suitable tools for creating a phylogenetic tree? Perhaps URD or Monocle might be suitable? Thank you in advance for your guidance.

Hi @iceautumn,
Thank you for your interest in our PhyloVelo work. To reconstruct a phylogenetic tree, you need to have DNA-seq data as the input. There are different algorithms that can be used for this task, such as maximum parsimony, neighbor joining or maximum likelihood. In our PhyloVelo work, we used the following tools to implement these algorithms:
R package phangorn for maximum parsimony
R package ape for neighbor joining
IQ-TREE for maximum likelihood
Please note that these methods require DNA sequences as the input, and scRNA-seq data alone cannot be used for this purpose.
I hope this helps you understand our PhyloVelo work better.
Best regards,
Kun


improves hotp.go coverage

Codecov Report

Merging #1 into master will increase coverage by 5.75%.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           master     #1      +/-   ##
========================================
+ Coverage   94.24%   100%   +5.75%
========================================
  Files           3      3
  Lines         139    139
========================================
+ Hits          131    139       +8
+ Misses          6      0       -6
+ Partials        2      0       -2

Impacted Files
Coverage Δ

hotp.go
100% <0%> (+11.42%)
:arrow_up:

Continue to review full report at Codecov.

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


Possibility to persist virtual setter/getter to MongoDB when using bulk insert?

I have my domain logic defined in virtuals, such as:
https://gist.github.com/nottinhill/78565d04bc01278de3a5#file-gistfile1-js
I have quite a few complex virtual getters. In order to minimise refactoring and maximise re-usability for different data sets I would like to persist the data returned by my virtuals getters to my MongoDB.
From my understanding I can achieve this with virtual setters. This is a overview of my current code:
1.) Parse Data (big data)
2.) Use Bulk Insert without Mongoose Schema due to this bug: http://stackoverflow.com/questions/24466366/mongoose-rangeerror-maximum-call-stack-size-exceeded
3.) Query Data with virtual getters
Due to the bulk insert bug I guess using virtual setters when using MongoDB Native Driver is not possible?
Would it be possible to add an additional step 4.) in order to load the populated model via the virtual getters into node.js and then bulk insert the populated data back into MongoDB to persist the population?

No, the whole point of virtuals is that they are not persisted to mongodb ever, as the first line of the docs says. If you really want to make it so all of your virtuals are stored in the database rather than computed when accessed, something like this would be the ideal way. Just make sure you remove all of your virtuals from your schema definition afterwards, otherwise they would conflict with the real path names.
var stream = MyModel.find({}).stream();
var docsLoaded = 0;
var docsSaved = 0;
var done = false;
stream.on('data', function(doc) {
  var updated = doc.toObject({ virtuals: true });
  ++docsLoaded;
  MyModel.update({ _id: doc._id }, updated, { overwrite: true }, function(err) {
    if (done && ++docsSaved >= docsLoaded) {
      process.exit(0);
    }
  });
});

stream.on('end', function() {
  done = true;
});


About porting to the diffusers pipeline

Thank you very much for implementing this awesome paint-with-words technique based on Stable Diffusion.
I am in the process of porting this project to the diffusers pipeline as a custom pipeline so that it can be used more easily by a wider variety of people.
If the porting is completed, I will clearly indicate that my implementation is based on yours, would you allow me to do so?

Sure, go ahead!


Recorded app version and where to find the Label, Key values

First and foremost,
thank you for the great work on this brige, the installation was flowless and I got my up emitting event in less than 10 minutes.
I have 2 questions (probably quite trivial):
1- the app version that is tracked on Anlytics is by default 1.0. How can I change it? IS that a value picked up from XCode field ? if yes, where is the Android setting?
2- I dispatch events in this way:
trackScreenView('Product Screen', {label: 'id', value: this.props.id})

So ideally, every time the user gets to the Product Screen view, I know the id of the product.
Unfortunately I cannot find that dimension on analytics.
Any idea?
Thank you again
Nicola

Hi @nicolabortignon

The app versions, are as far as I know, picked up from the Info.plist for iOS. And in the build.gradle for Android. Basically the same version fields you mutate for releases in store.

The trackScreenView does not have labels. You want to use the trackEvent.


Modal - Ability to modify z-index

The modal uses a ng-style to set the z-index, which will overwrite any class styles defined.
ng-style="{\'z-index\': 1040 + (index && 1 || 0) + index*10}"
This is associated with the backdrop and the window.
I would suggest either making the 1040/1050 configurable or adding another property, such as:
ng-style="{\'z-index\': 1040 + (index && 1 || 0) + index*10 + configurableIndex}"
I'm working under the assumption the above index property is used to handle multiple modals, and changing it to use classes is not feasible. Is that accurate?

Personally, I'd rather have the config option, so that I don't have to override the templates.

I agree: different types of modals, wishing I could have configurable option.

Throwing my vote in for configurable z-index.  Running into an issue right now.

+1

+1

+1

+1

+1

As @pkozlowski-opensource already said months ago, we won't be adding another option to the already extensive config possibilities of the modal. You can easily use a custom template with the correct z-index by using templateUrl. That, in combination with the options to overwrite the default template or to add a windowClass you should have enough tools to achieve what you want.
Please don't add +1's to this issue as it is already closed.


Organize CMake functionality

Type

[ ] Bug fix
[ ] Feature addition
[ ] Feature update
[ ] Breaking change
[X] Non-functional change
[ ] Documentation
[X] Infrastructure

Goals
Reduce complexity of top-level CMake file.
Technical Details

Move vcpkg related functionality into its own script file and introduce function to configure it.
Move windows related functionality into existing windows/CMakeLists.txt file.
Ensure vcpkg driver target is set even when vcpkg is not being used to resolve dependencies.

Test Results
Built with dev and vcpkg-dev presets, with clear caches, and verified everything worked, including the simulator driver build.
Reviewer Focus
None
Future Work

Security hardening needs to move to its own script file.

Options need to be categorized and applied appropriately: all configs, debug, release.\

Checklist

[ ] Build target all compiles cleanly.
[ ] clang-format and clang-tidy deltas produced no new output.
[ ] Newly added functions include doxygen-style comment block.

This PR is doing too much. Abandoning it in favor of several smaller PRs with more targeted goals.


Feature Request: LDAP authentication to Azure Windows server

Just curious, it may be well out of scope, but we are using this to secure access to a Windows server in Azure, but as it works now only the certificate is used to authenticate to the VPN. Would it be possible to extend this to query LDAP on a Windows server in Azure to look up the username and also require a password along with the certificate?

Check this post out here. Basically, add a package with apt (this guide uses yum, but the same package is on apt) then configure the server to authenticate against AD. You need to add one line (auth-user-pass) to the template that generates the .ovpn file.
https://www.allcloud.io/how-to/configure-openvpn-authentication-using-active-directory/
It could be a feature, but given that almost every implementation of AD has some quirks to it, I think it's one of those areas I'd leave to the user to customize.
Hope this helps.

Thanks, who would have thought it would have been so easy? LoL Because, as you say, every time I've played with LDAP and/or AD it is a bit quirky.  I played around with an approach using an external script basaed on this post:
https://forums.openvpn.net/viewtopic.php?t=13053
It works, but using the plugin may prove more performant and secure.
Thanks so much for the feedback, hopefully this will prove useful for someone down the road.


Character portraits

Concept art done, now needs to made digital with talk frames, and placed in spritemap


use pi4j-plugin-linuxfs for I2C (needs update to pi4j 2.1.1)

backported enhancements from Theremin-Project

Is it a good thing to use linuxfs in template?

@DieterHolz i think so, as this has the proper I2C driver


fix(data-type): 16進数の解説を修正

fix #680

Deploy preview for js-primer ready!
Built with commit 1788ce2c87a01fcaa1a9e23343c88672f45d2c8c
https://deploy-preview-681--js-primer.netlify.com

Deploy preview for js-primer ready!
Built with commit e20ed776ad9535654b6a3a83a59677263b7218e7
https://deploy-preview-681--js-primer.netlify.com

Deploy preview for js-primer ready!
Built with commit 006f8f051d1a108005238d2b837049de6476d16a
https://deploy-preview-681--js-primer.netlify.com

Deploy preview for js-primer ready!
Built with commit 94222f691eb285c003eb41431db660c5e61b0ee2
https://deploy-preview-681--js-primer.netlify.com

Deploy preview for js-primer ready!
Built with commit 8a31e463bf6b8f9ea03a50c51db67afe4dffc084
https://deploy-preview-681--js-primer.netlify.com


Improve AML syntax

AML is a markup language to easily define database schema. It's made to be quick, easy and flexible to write to capture user intent rather than capture all the details needed for each database.
It already quite great but needs some improvement to handle additional features and use cases.
It would be nice also to add some developer utils to easy it's adoption.
Syntax improvements:

[ ] handle nested columns (same as columns but with more indentation levels)
[ ] handle composite relations
[ ] define types/enum as standalone (cf https://github.com/azimuttapp/azimutt/issues/255)
[ ] define a global schema for the whole AML file

Developer tools:

[ ] Make a JS library to validate/parse/generate AML
[ ] Make a syntax highlighter for a JS editor

#179 and #166 may be related to this issue.

Thanks for your comment, why do you think they can be related?
They are more linked to UI display than AML as I'm Azimutt is focused on physical layer or db design, not on logical one.

My suggestion was based on the notion that representing relationships among tables in Azimutt may involve syntax changes in AML. While I acknowledge the primary focus on the physical layer, there might be a connection in terms of how AML syntax could be extended or modified to facilitate the representation of relationships in the UI.

Thanks for your clarification.
For this I'm considering more inferences from the UI than changing the schema model.
For example:

a relation from a column with a unique could be shown as a 1-1 relation
a table with a primary key containing two relations could be shown as a n-n relation

If you see how AML could be improved for this, would be happy to discuss suggestions ;)


Fix broken Windows target

Our windows target is failing (https://github.com/r-three/git-theta/actions/runs/4668786682/jobs/8266325660) with
checkout
Error: Process completed with exit code 128.

Here are some ideas on how to fix it: https://github.com/actions/checkout/issues/417

Some more examples of when this failure occurs:

https://github.com/r-three/git-theta/actions/runs/4668786682/jobs/8266325660#step:5:41
https://github.com/r-three/git-theta/actions/runs/4672210342/jobs/8274136287#step:5:122
https://github.com/r-three/git-theta/actions/runs/4765796504/jobs/8471989669#step:5:123

The issue seems to be transient as manually re-running the failed jobs seems to fix them after a while

Here is another example of the failure, there is more log info on this one but the issue seems to be the same
https://github.com/r-three/git-theta/actions/runs/5026793162/jobs/9015490470?pr=216#step:5:2350


tests(*): match_error_log block and match_error_log_grep modifier

Many of our tests are too lenient on checking the ordering and number of occurrences of expected log messages. grep_error_log_out makes it possible to avoid the problems of error_log_out, but it is tricky to get it right.
For example, this entry is still too lenient, because the .* entries between lines can consume additional lines and miss unordered repeats.
Getting more robust entries using grep_error_log_out is possible, at the cost of readability — but even this example is still not enough (spot the use of .*?)... This comes closer ...but are we sure it's right?
This PR introduces a new block handler, match_error_log, where you give it an array of plain substrings (not regexes), and the test passes if and only if all occurrences of the given substrings in the error log match the given list in the exact order, including repeats.
This makes it easy to write more solid tests:

unexpected repeats are caught
entries out of order are caught
regex mistakes due to special characters are avoided

The subset of relevant lines to be checked can be filtered by a regex using match_error_log_grep. If not given, the entire error.log is checked. Filtering makes it easier to test for things like ["[info]", "my message", "[info]", "another message"] (ensuring there are no other [info] entries in between), but then the usual concerns about crafting careful regexes in match_error_log_grep to avoid undesired lines applies.
This PR includes the implementation commit, intended to be cherry-picked, and an example commit showcasing the use with and without the filtering.

@thibaultcha I wrote this on top of feat/ffi-properties-code-review but that shouldn't matter — it was just so I could showcase the block using tests from that PR. The relevant commits are the last two.

A note on --- grep_error_log with [^#*]* and co: These can easily be avoided if the extracting regex does not match .* at the end. Most likely, many of these regexes could be changed to capture lines in some other way, perhaps until the Nginx-injected comma , or something else.
Will --- match_error_log also catch extraneous matching lines before or after the test substrings and not just in-between? For example, I consider --- grep_error_log the most thorough testing method when used with a good extraction regex and a delimited matching regex with \A ... \Z limits. See for example recent connection drop tests in which this pattern caught false-positive test cases with other similar lines that were initially left-out by grep_error_log_out. I have seen many unexpected lines show before and after the matching --- grep_error_log_out regex recently, and wanted to bring this up eventually. So, unless --- match_error_log with --- match_error_log_grep can also do this, --- grep_error_log might still have an important edge for critical or existing test cases.

These can easily be avoided if the extracting regex does not match .* at the end.

A bunch of the regexes in tests have .* in the middle though ([info] .* something something) and grep_error_log will happily match that across two different log lines. We'd need to change every .* to something like [^\n]*, etc. Gets annoying and error-prone fast.

Will --- match_error_log also catch extraneous matching lines before or after the test substrings and not just in-between?

Yes. It checks before, after and in-between. If you put 4 items in the substring list, the whole match (or the whole file if not using match_error_log_grep) must contain only 4 occurrences of those substrings, in the given order.

After playing with it a little, I am not convinced by --- match_error_log and still think grep_error_log is superior in most cases.

A bunch of the regexes in tests have .* in the middle though ([info] .* something something) and grep_error_log will happily match that across two different log lines. We'd need to change every .* to something like [^\n]*, etc. Gets annoying and error-prone fast.

Right; my point is that we don't really care about checking for [info] (but if we do we can still craft the proper regexes for it), and should write grep_error_log_out regexes without checking for the log level, and without catch-all checks.
I updated --- match_error_log to accept a plain string (or \n-separated array) and so far I find that the failure case is more difficult to debug than --- grep_error_log_out which will print the full string and a diff with the subject, while match_error_log wants me to count n lines and find the difference by myself (excess occurrence of 18th substring "wasmx.empty_dyn_property: string """ was found in error.log:301). Secondly, I remove a line in the middle of match_error_log:
diff --git a/t/04-openresty/ffi/304-proxy_wasm_set_property_getter.t b/t/04-openresty/ffi/304-proxy_wasm
_set_property_getter.t
index 65f04b0a..ae99dd11 100644
--- a/t/04-openresty/ffi/304-proxy_wasm_set_property_getter.t
+++ b/t/04-openresty/ffi/304-proxy_wasm_set_property_getter.t
@@ -517,8 +517,8 @@ ok
     }
 --- response_body
 ok
---- grep_error_log eval: qr/(getting\s)?wasmx\.\S+property.*?(?=while)/
---- grep_error_log_out
+--- match_error_log_grep eval: qr/(getting\s)?wasmx\.\S+property.*?(?=while)/
+--- match_error_log
 getting wasmx.const_property counter: 1
 wasmx.const_property: string "1"
 getting wasmx.dyn_property counter: 2
@@ -530,7 +530,6 @@ getting wasmx.nil_const_property counter: 4
 wasmx.nil_const_property: nil "nil"
 getting wasmx.nil_dyn_property counter: 5
 wasmx.nil_dyn_property: nil "nil"
-wasmx.nil_const_property: nil "nil"
 getting wasmx.nil_dyn_property counter: 6
 wasmx.nil_dyn_property: nil "nil"
 getting wasmx.empty_const_property counter: 7

And the test still passes, as a false-positive that grep_error_log would have caught.
I am not convinced. So far I think I will update the property getter/setter tests to grep_error_log instead of match.

@thibaultcha That's thoughtful feedback, thank you!

my point is that we don't really care about checking for [info]

Ah, I wasn't aware — I thought it was a requirement.

Firstly, I find that the failure case is more difficult to debug than --- grep_error_log_out which will print the full string and a diff with the subject

(Pedantic correction: when using regexes, it produces not a diff but the full string and the regex — I've always found these long error dumps hard to read, but...) ...that's a great point. My error output was lazy there (typical mistake of making them correct-but-not-very-readable); in fact I think that with substring matching we can make the error messages better than grep_error_log_out and produce actual visual diffs.
More generally, your examples brought the point home to me about what my main gripe with grep_error_log really is: it does one big multi-line regex in grep_error_log_out (bad), even though it does per-line filtering in grep_error_log (good). That is the single thing that makes it difficult to write correct regexes with it.
Your example about removing the line also suggests that, when a grep-filter is applied to match_error_log, a more interesting behavior (perhaps even the expected one) is that all filter-matched lines should contain at least one matched substring. That would require grep filters to not be too wide, but since we're using extended-regexps with |-alternatives, it's easy to combine multiple simple specific ones.
Requiring one match per filtered line would not only cover the scenario you mentioned but make the "hardened" test matching the default behavior if the test author does nothing special and just writes a basic grep regex and a plain substring.

perhaps at a slightly higher effort cost, sure, just like all good things in life.

Not everyone is a mountain climber, though, so our notions of effort are calibrated at different levels. :)
Joke aside, I'll still disagree about the effort cost given that, looking at the current state of the main branch, I don't think none of us have been able to write a single bullet-proof regex using grep_error_log in the existing test cases; both my and your examples at hardening them all have some fault or another that I could identify. Of course it's not impossible to do it, but you know me: I'm always one for improving the tooling to make the more obvious path the correct one rather than painstakingly improving everyone's "crafting" by trial and error — even if that requires me to *gasp*, write some Perl. :)
I still think we will find grep_error_log to be useful in specific scenarios, but I think it's also worth building the cable-car that takes us effortlessly to the top of the mountain. :)
Fine by me if we continue moving the property setters/getters forward with grep_error_log, but I'll still give this PR another spin to address the points above.

I don't think that is is worth spending time on --- match_error_log; the getter/setter PR will have simple and reliable perfect grep matching and that is the pattern we should follow going forward. That said, there are many, many things with getter/setter that I don't think are fully finished either, so also working on that...

I've pushed an updated version of the block in this PR. I think it addresses all issues you raised and provides (IMO) better diagnostics than grep_error_log.

That said, there are many, many things with getter/setter that I don't think are fully finished either, so also working on that...

Let me know if there's any way I can help. You asked me to stop pushing on that branch so I did not make any further changes, but you did get my comment with the diff with the set_r fix, right? Did that stop the crashes on your end?

Oh yes, the set_r fix is good no worries there!
Since I am not sure I will be done today I'll list the main things that were holding this for me:

At first I went through test cases to use --- grep_error_log, and doing so, found double-logging errors in the return nil, err tests: an error in Lua and another in the filter hostcall. I now moved the return nil, err message into a wasm trap when in hostcalls: we want a stacktrace and we want to avoid double-errors in the logs when possible, so this design results in much more concise/actionable error logs.
In tests, I added many more scenarios I found necessary (this is when the set_r fix came in handy), and asserted the yielding behavior too.
While updating tests, I have also found that getter tests were going through the wasm filter loop (t/get_property), while the setter tests were mostly going through the FFI API (proxy_wasm.set_property()). For now I am also working on fixing this disparity in the testing symmetry (existing tests assumed both execute the same underlying code), and ensuring errors from the wasm filters throw a trap (and backtrace), while errors from the FFI API are returned as a string in the nil, error signature.

I will push a merge PR with the updates before merging anything.

Still looking at it; I think it does fix my above concerns on the subject matching. It feels a little easier to use than --- grep for tests with a small number of lines in the subject, but very noisy and way harder to read than the no_long_string diff output for tests with a lot of lines. But if you think you can make good use of it, I think it's fine to have and also a good template to have to further extend Test::Nginx if needed again.

Although one more thing: unless I am mistaken, now that --- match_error_log_grep is mandatory the main difference it has with --- grep_error_log is the way it treats the subject patterns (as plain substrings). Otherwise it works the same way: 1) extracts a pattern (the --- grep), test the pattern (the --- grep_out). May I suggest we rename --- match_error_log to something that better reflects its main difference from --- grep_error_log? Maybe --- fgrep_error_log, --- fgrep_error_log_out (fgrep like grep -F)? Or something more verbose, I don't mind, like --- plain_grep_error_log or --- grep_error_log_plane. Bust mostly keeping the same terminology: --- block, --- block_out?

I think that if we don't need to match multiple substrings within the same line (e.g. [info] and relevant text), then the benefit of match_error_log becomes truly marginal. I was basically operating under a different set of assumptions.
Adopting plaintext mode of grep_error_log_out whenever possible addresses my main concern about having big multiline regexes everywhere. I agree that the diff output in plaintext grep_error_log_out is nicer, too. The only other thing still going for match_error_log then, besides the support for multiple matches per line, would be that the filtering regex is easier to write (because you can match the whole line and then it does substring search), but that doesn't make it worth it, IMO.
If we needed multiple substrings matched in order per line, this would've been a big boost for test readability/reliability. But given our actual requirements, I'm happy to close down this one and follow the patterns from your latest tests!


Write a GO program to print reverse of a string

Description
Write a GO program to print reverse of a string
Reverse of a string is the string with the characters in reverse order. For example, the reverse of "hello" is "olleh".
Input  : abcd
Output : dcba

How to contribute

Save the solution in print_reverse_of_a_string.go file
Add print_reverse_of_a_string.go file in print-reverse-of-a-string folder

!assign


Fixed #32332 -- Fixed loss of parent with non-numeric pk when saving child after parent.

https://code.djangoproject.com/ticket/32332

@hramezani Thanks :+1:


Uncaught TypeError: AngularComponent(...).Class is not a function (Angular 5+ removed ES5 DSL)

<EMAIL_ADDRESS>angular@7

Angular2 Driver does not work with Angular5+
https://github.com/angular/angular/commit/cac130eff9b9cb608f2308ae40c42c9cd1850c4d#diff-635fe23be5795132e3385c8f4899dc3a
need to use static properties annotations and parameters
https://stackoverflow.com/a/47731407

Is it possible to fix that without changing source code of zoid?


different route found for customer profile edit page for velocity theme

Bug report
Title
different route found for customer profile edit page for velocity theme
Issue Description
different route found for customer profile edit page for default theme to velocity theme..
Preconditions
1. framework Version- master

Steps to reproduce
1. step1- on default theme, go to the edit customer profile page
2. step2- update velocity theme from backend, reload the previous edit profile route again.

Expected result
All routes should be the same for both themes
Actual result

Fixed


feature request

an option tto put sbc futbin id and tool automatically buy all players with their futbin price

Duplicate of https://github.com/chithakumar13/fut-trade-enhancer/issues/26


feat: Share env variables for pre-built builder binaries

closes https://github.com/slsa-framework/slsa-github-generator/issues/501

This is great!
Including some docs would be helpful! Especially when all of this isn't compiled code( shell script and YAML)

I've added comment next to each variable. Does it help?

This is great!
Including some docs would be helpful! Especially when all of this isn't compiled code( shell script and YAML)

I've added comment next to each variable. Does it help?

Thank you! It helps!

friendly ping for review


Support TUNSETIFF on MIPS, PPC and SPARC

This commit adds support for the TUNSETIFF constant on MIPS, PPC and
SPARC. The TUNSETIFF constant defined in the Linux kernel headers uses
architecture-specific macros. For this commit, the architecture-specific
definitions of the constant in the Golang source code were consulted.

The commit message and the code comment now include more information.

Thank you!


Changes to allow Omni Core to be used in a 'regtest' blockchain

Changes to allow Omni Core to be used in a 'regtest' blockchain along with other nodes running newer versions (e.g. 0.16.2) of Bitcoin Core.

Hello @claudiosdc,
we are about the port Omni Core to the current Bitcoin Core 0.18 code base. Is this patch then still needed?

Hi @dexX7,
Oh, that’s good news!
No, in that case that patch would not be required.
Thanks,
Cláudio de Castro
Híades Tecnologia

Em 26 de jul de 2019, à(s) 10:35, dexX7<EMAIL_ADDRESS>escreveu:
Hello @claudiosdc https://github.com/claudiosdc,
we are about the port Omni Core to the current Bitcoin Core 0.18 code base. Is this patch then still needed?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/OmniLayer/omnicore/pull/973?email_source=notifications&email_token=AAKAMHMWYLN55HIC75BRHC3QBL4TFA5CNFSM4H7F2BM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD24TN6I#issuecomment-515454713, or mute the thread https://github.com/notifications/unsubscribe-auth/AAKAMHMPFVRLKB7VYZ3VWCDQBL4TFANCNFSM4H7F2BMQ.


Development 22/07

@thenukagunawardana Please check the CI/CD pipeline issues.

@thenukagunawardana Please check it with @RazeenRamzy and fix the issues

fixed @pankajan05

Good Job @RazeenRamzy

Please solve these issues.


Define a way to register a new chain to use

A chain should be registered on Desmos in order to use if messages are sending from other chains.

This may not be valid if IBC is implemented.

Closed in favor of #114


Bug: API always creates 4 images

num_images seems to be ignored by the SDK. No mather the value it always generates four images.

Anyone from the Leonardo team who could acknowledge this?

Hey @ejkkan, can you provide an example of how you're using the SDK that is causing this to occur?

@anuraagnalluri
I've created this example for most of the issues I've reported. See here
So please config it to make the setup relevant for each issue.
Notice that I'm using v1.28 specifically because of functionality being broken as mentioned in

Hi @ejkkan , I believe that this should have been resolved with the patch that resolved the other issues you submitted.

It is fixed indeed! Thanks!

Hey @alexadrake, I'm still seeing this exact behaviour in 2.2.0. Of note, at https://docs.leonardo.ai/reference/creategeneration this issue does not exist.
const generationResponse = await sdk.generation.createGeneration({         modelId: '...',         presetStyle: "ILLUSTRATION",         num_images: 1,         height: 1024,         width: 1024,         alchemy: true,         photoReal: false,         public: false,         nsfw: false,         elements: [{ akUUID: '...', weight: 1 }],       },);


feat(s2n-quic-platform): add blocking tasks

Resolved issues:
resolves #ISSUE-NUMBER1, resolves #ISSUE-NUMBER2, etc.
Description of changes:

Call-outs:

Testing:

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

closing this for now


Bottom Nav Share, "Create a public link" displays "GT Guide" onscreen after creating the link.

Occurs in LCW v2.0.11-build 66 on iOS and Android.
(I can't find "GT Guide" text in the JSON of the all the credentials I've tried, nor did a search in the repo turn up anything except for inside mock credentials.) Attached is a credential where one can see the issue.
To reproduce:

Add a credential to LCW
From the bottom nav, select the share icon
Select "Create a public link"
Select (any) credential, and "Create Link" from the "Are you sure?" modal
Note GT Guide at the top of the interstitial screen when the Public Link is getting created and on the resulting Public Link (Beta) screen.

Bottom Nav, Share Screen

Interstitial as Public Link getting created—Note GT Guide

Resulting Public Link screen—Note GT Guide

Checking on credential name display

"GT Guide" displays no matter what the credential name is. Please change so that the credential name of the chosen credential is displayed.

Confirm that the chosen credential name displays (instead of GT GUIDE)  in both ioS and android


[SASS-3114] Added service-manager related scripts.

Description
Added two scripts for a more convenient control of service manager.
SASS-3193
Checklist PR Reviewer
Before Reviewing

[ ]  Have you pulled the branch down?
[ ]  Have you assigned yourself to the PR?
[ ]  Have you moved the task to “in review” on JIRA?
[ ]  Have you checked to ensure all dependencies are up to date?
[ ] Have you checked to ensure its been rebased against the current version of main?

Whilst Reviewing

[ ]  Have you run the journey tests?
[ ]  Have you looked at the JIRA story to make sure all Acceptance Criteria has been met?

After Reviewing

[ ] Have you checked for merge conflicts or any changes in the current main that may affect the current pull request? i.e. does it need another rebase?
the current pull request?
[ ]  Have you checked to make sure there are no builds in the pipeline before you merge?
[ ]  Have you moved the task to “in pipeline” on Jira?

Checklist PR Raiser
Before creating PR

[ ]  Have you run the journey tests?
[ ]  Have you addressed warnings where appropriate?
[ ]  Have you rebased against the current version of main?

For this run (using release version of all services) I didn't interact with the computer at all.
[info] ScalaTest
[info] Run completed in 27 minutes, 23 seconds.
[info] Total number of tests run: 0
[info] Suites: completed 0, aborted 0
[info] Tests: succeeded 0, failed 0, canceled 0, ignored 0, pending 0
[info] No tests were executed.
[info] Passed: Total 82, Failed 0, Errors 0, Passed 82
[success] Total time: 1648 s (27:28), completed 4 Aug 2022, 17:23:41

My Mac mini (M1) has 16GB.

Note that I used the sm scripts added here.


How to configure multiple python gunicorn workers? Not working

I'm using a premium P3 v2 large web app with 4 cores(single node).  With a forced delay on the flask request I can confirm that the requests are being serialized and not processed in parallel.
This happens even after doing the following:
-created a  startup.txt with:
gunicorn --workers=4 application:app
-commit/pushed new startup.txt to web app git
-added startup.txt as startup file in web app settings as describes
-restarted the app
the requests are still being serialized with only one request executing at a time, even with 4 cores available :(
what's missing?
thx!

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

ID: 4348313e-7280-dc7e-4943-14c4675bbe5a
Version Independent ID: 970e6640-8042-5f88-5ecf-84d58d09b8fd
Content: Configure built-in Python image in Azure App Service
Content Source: articles/app-service/containers/how-to-configure-python.md
Service: app-service-web
GitHub Login: @cephalin
Microsoft Alias: astay;cephalin

ok, found the problem, was not forcing proper bind and was using <IP_ADDRESS>
this fixed it, and now I see requests happening in parallel! :)
(would be interesting to see this scenario explored in docs, with some best practices/advices)
gunicorn -b <IP_ADDRESS>:8000 -w 1 -k gthread --thread=2 application:app
or
gunicorn -w 4 -b <IP_ADDRESS>:8000 application:app
thx

@rquintino  You are lifesaver, its 4 years, and gunicorn workers on azure still don't work,.... when I used your script, my application is blazingly fast.... thanks !


Added unique=True in category name to resolve Issue #2472

fixing issue #2472.

@lostwarrior404 ping (Let us know if you need help)

Sorry for the late reply I'll try to resolve this by tonight.

When I try to apply migrations using command
./manage.py makemigrations openslides.motions --setting=openslides.global_settings
I get an error ImproperlyConfigured("The SECRET_KEY setting must not be empty.").
Am i doing something wrong? Can someone explain how to proceed towards solving this?

In a development version you can just run python manage.py createsettings to get a development settings with random secret key and the like. See the new directory personal_data. The you can run python manage.py makemigrations to get a new migrations file.

@normanjaeckel Can you review the requested changes again?

@lostwarrior404 Ping. When can you  finish this pull request? Please let us know if you need help.

@lostwarrior404 Do you need any help here to complete this? Otherwise we have to close this (unfinished and outdated) pull request.

Implementation is not complete. We close this pull request. Feel free to reopen with a new proposal (rebased on top of current master) or even open a new pull request. Thanks in advance.


LC0010 does not work in code-workspaces

The LC0010 documentation states the Lintercop.json needs to be part of the 'project' root.
When opening the project roots folder, the LC0010 is calculated correctly.
However, when opening a code-workspace file (all our apps have a workspace with an alpackages shortcut, App folder and Test folder), the LC0010 does no longer respect the settings from the individual app / project folders.

Just tried to reproduce, and it works for me. I can even have individual LinterCop.json files for each workspace folder

I did reload and I did not work.
Then I opened the project root folder instead.
Reopened the workspace again and it did work.
WIll keep an eye on it and re-open if needed / if I can better simulate an off-scenario.
Thx!

Hey Stefan.
Please find below a setup of our workspaces.

The code-workspace contains various folders:
"folders": [
        {
            "path": "../.alpackages"
        },
        {
            "path": "../Dynavision Core/App",
            "name": "ESCA - Core"
        },
        {
            "path": "App",
            "name": "ESCN - Purchasing and Procurement Center"
        },
        {
            "path": "Test",
            "name": "ESCN - Purchasing and Procurement Center (Test)"
        }
    ],

... of which only one (the /App folder) contains a LinterCop.json file
{
"cyclomaticComplexetyThreshold": 25,
"maintainablityIndexThreshold": 20,
"enableRule0011ForTableFields": false
}
Still files under the /App folder result in LC0010 warnings, where they should not, since the cyclomaticComplexetyThreshold has been increased to 25 for these files.

If I'm not mistaken @StefanMaron has resolved this in v0.29.6..
@fvet and/or @ernestasjuska Could you confirm this?

@Arthurvdv I'm currently not using LC0010 pro-actively, however I just tested the reported scenario again in my workspace and can confirm that all works, so I'll be closing the issue ;)


Release v0.4.0

Coverage increased (+1.5%) to 98.247% when pulling 3d433339db90a4317a189738c496beccf886eba5 on master into b1ed735fe576458cac8c79b2f7aa81773254d2d6 on stable.

Coverage increased (+1.5%) to 98.247% when pulling 3d433339db90a4317a189738c496beccf886eba5 on master into b1ed735fe576458cac8c79b2f7aa81773254d2d6 on stable.


⚠ Processors has degraded performance

In 9fa4207, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 85 ms

Resolved: Processors performance has improved in e9ca91c.


Message: Call to undefined method GuzzleHttp\Utils::chooseHandler()

Guzzle version(s) affected: 7.3.0
PHP version: 7.4.14
cURL version: 7.58.0 (hint: php -i | grep cURL)
Description
GuzzleHttp\Utils::chooseHandler() when calling google ads api
How to reproduce
https://github.com/googleads/google-ads-php/issues/612#issuecomment-859560324

Chances are you are not using Guzzle 7.3.0, but a globally installed version of Guzzle different to the version you thought.

How I can identify globally installed version and different versions?
I may say that I have 2 repo which might require different guzzle versions but those 2 repo are installed with composer in 2 different folders with 2 autoload file.
So is this a issue?

Hi @GrahamCampbell ,
Is there any hint how I can differentiate which is global and which is local guzzle version?
Thanks,

Use xdebug to look at the stacktrace.
You also see what version you have installed in composer.lock. (Or run composer show).
Please refer to a support forum for support. This issue tracker is for bugs.


Did I install it incorrectly?

It's laggy, and don't work, so I re-installed it. Still laggy. Is this not what it's supposed to look like?

Yes, you rename it to vphysics.dll


⚠ Bofrost.at has degraded performance

In 4ba540c, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1966 ms

Resolved: Bofrost.at performance has improved in e5930f4 after 6 minutes.