Settings sync disabled itself in github.dev

I opened https://github.dev/microsoft/vscode/pull/159276 and saw my theme get changed to the default. I suspected that something went wrong with settings sync, and it appears to have been disabled.
Logs:
[2022-08-26 15:21:22.618] [settingssync] [info] Using settings sync service https://vscode-sync-insiders.trafficmanager.net/
[2022-08-26 15:21:22.626] [settingssync] [info] Auto Sync is disabled.
[2022-08-26 15:21:24.084] [settingssync] [info] Disabling extension firefox-devtools.vscode-firefox-debug
[2022-08-26 15:21:24.108] [settingssync] [info] Disabling extension ms-edgedevtools.vscode-edge-devtools
[2022-08-26 15:21:24.320] [settingssync] [info] Disabling extension ms-vscode-remote.remote-ssh-nightly
[2022-08-26 15:21:24.339] [settingssync] [info] Disabling extension ms-vscode.github-browser
[2022-08-26 15:21:24.346] [settingssync] [info] Disabling extension vscode-samples.proposed-api-sample
[2022-08-26 15:21:24.350] [settingssync] [info] Disabling extension vscode-samples.task-provider-samples
[2022-08-26 15:21:24.354] [settingssync] [info] Disabling extension ms-vscode.powershell
[2022-08-26 15:21:24.361] [settingssync] [info] Disabling extension dart-code.dart-code
[2022-08-26 15:21:25.418] [settingssync] [error] Unsupported: Cannot install the 'ESLint' extension because it is not available in this setup.
    at b.installFromGallery (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:3201:135167)
    at async W.initialize (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:118686)
    at async https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:113892
    at async Promise.all (index 1)
    at async N.initializeExtensions (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:113122)
    at async Promise.allSettled (index 1)
    at async N.initializeOtherResources (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:112935)
    at async x.initializeOtherResource (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:119874)
[2022-08-26 15:21:25.926] [settingssync] [error] Unsupported: Cannot install the 'Remote - WSL' extension because it is not available in this setup.
    at b.installFromGallery (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:3201:135167)
    at async W.initialize (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:118686)
    at async https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:113892
    at async Promise.all (index 1)
    at async N.initializeExtensions (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:113122)
    at async Promise.allSettled (index 1)
    at async N.initializeOtherResources (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:112935)
    at async x.initializeOtherResource (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:119874)
[2022-08-26 15:21:26.400] [settingssync] [error] Unsupported: Cannot install the 'Remote - Containers' extension because it is not available in this setup.
    at b.installFromGallery (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:3201:135167)
    at async W.initialize (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:118686)
    at async https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:113892
    at async Promise.all (index 1)
    at async N.initializeExtensions (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:113122)
    at async Promise.allSettled (index 1)
    at async N.initializeOtherResources (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:112935)
    at async x.initializeOtherResource (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:119874)
[2022-08-26 15:21:26.895] [settingssync] [error] Unsupported: Cannot install the 'Remote - SSH' extension because it is not available in this setup.
    at b.installFromGallery (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:3201:135167)
    at async W.initialize (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:118686)
    at async https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:113892
    at async Promise.all (index 1)
    at async N.initializeExtensions (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:113122)
    at async Promise.allSettled (index 1)
    at async N.initializeOtherResources (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:112935)
    at async x.initializeOtherResource (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:119874)
[2022-08-26 15:21:27.392] [settingssync] [error] Unsupported: Cannot install the 'Remote - SSH: Editing Configuration Files' extension because it is not available in this setup.
    at b.installFromGallery (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:3201:135167)
    at async W.initialize (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:118686)
    at async https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:113892
    at async Promise.all (index 1)
    at async N.initializeExtensions (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:113122)
    at async Promise.allSettled (index 1)
    at async N.initializeOtherResources (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:112935)
    at async x.initializeOtherResource (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:119874)
[2022-08-26 15:21:27.914] [settingssync] [error] Unsupported: Cannot install the '[Deprecated] Debugger for Chrome' extension because it is not available in this setup.
    at b.installFromGallery (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:3201:135167)
    at async W.initialize (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:118686)
    at async https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:113892
    at async Promise.all (index 1)
    at async N.initializeExtensions (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:113122)
    at async Promise.allSettled (index 1)
    at async N.initializeOtherResources (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:112935)
    at async x.initializeOtherResource (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:119874)
[2022-08-26 15:21:28.458] [settingssync] [error] Unsupported: Cannot install the 'PowerShell' extension because it is not available in this setup.
    at b.installFromGallery (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:3201:135167)
    at async W.initialize (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:118686)
    at async https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:113892
    at async Promise.all (index 1)
    at async N.initializeExtensions (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:113122)
    at async Promise.allSettled (index 1)
    at async N.initializeOtherResources (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:112935)
    at async x.initializeOtherResource (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:119874)
[2022-08-26 15:21:29.000] [settingssync] [error] Unsupported: Cannot install the 'Dart' extension because it is not available in this setup.
    at b.installFromGallery (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:3201:135167)
    at async W.initialize (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:118686)
    at async https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:113892
    at async Promise.all (index 1)
    at async N.initializeExtensions (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:113122)
    at async Promise.allSettled (index 1)
    at async N.initializeOtherResources (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:112935)
    at async x.initializeOtherResource (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:119874)
[2022-08-26 15:21:29.499] [settingssync] [error] Unsupported: Cannot install the 'Debugger for Firefox' extension because it is not available in this setup.
    at b.installFromGallery (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:3201:135167)
    at async W.initialize (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:118686)
    at async https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:113892
    at async Promise.all (index 1)
    at async N.initializeExtensions (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:113122)
    at async Promise.allSettled (index 1)
    at async N.initializeOtherResources (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:112935)
    at async x.initializeOtherResource (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:119874)
[2022-08-26 15:21:30.162] [settingssync] [error] Unsupported: Cannot install the 'German Language Pack for Visual Studio Code' extension because it is not available in this setup.
    at b.installFromGallery (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:3201:135167)
    at async W.initialize (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:118686)
    at async https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:113892
    at async Promise.all (index 1)
    at async N.initializeExtensions (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:113122)
    at async Promise.allSettled (index 1)
    at async N.initializeOtherResources (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:112935)
    at async x.initializeOtherResource (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:119874)
[2022-08-26 15:21:30.606] [settingssync] [error] Unsupported: Cannot install the 'Microsoft Edge Tools for VS Code' extension because it is not available in this setup.
    at b.installFromGallery (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:3201:135167)
    at async W.initialize (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:118686)
    at async https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:113892
    at async Promise.all (index 1)
    at async N.initializeExtensions (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:113122)
    at async Promise.allSettled (index 1)
    at async N.initializeOtherResources (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:112935)
    at async x.initializeOtherResource (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:2725:119874)
[2022-08-26 15:21:32.392] [settingssync] [info] Installed extension. ms-vscode.vscode-js-profile-table

Version info:
Version: 1.71.0-insider
Commit: 35b971c92d210face8c446a1c6f1e470ad2bcb54
Date: 2022-08-26T09:17:26.667Z
Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Console output in case it's useful:
```
 INFO Settings Sync: Updated current session github-session-sync-service
log.ts:301  INFO Skipping initializing tasks because local tasks exist.
log.ts:301  INFO Initialized User Tasks
log.ts:301  INFO Created snippet snips.code-snippets
log.ts:301  INFO Initialized User Snippets
log.ts:301  INFO Initialized Keyboard Shortcuts
log.ts:301  INFO Migrating global extension storage from github.codespaces to GitHub.codespaces...
log.ts:301  INFO Migrated global extension storage from github.codespaces to GitHub.codespaces
log.ts:301  INFO Migrating workspace extension storage from github.codespaces to GitHub.codespaces...
log.ts:301  INFO Migrated workspace extension storage from github.codespaces to GitHub.codespaces
log.ts:301  INFO Migrating global extension storage from github.vscode-pull-request-github to GitHub.vscode-pull-request-github...
log.ts:301  INFO Migrated global extension storage from github.vscode-pull-request-github to GitHub.vscode-pull-request-github
log.ts:301  INFO Migrating workspace extension storage from github.vscode-pull-request-github to GitHub.vscode-pull-request-github...
log.ts:301  INFO Migrated workspace extension storage from github.vscode-pull-request-github to GitHub.vscode-pull-request-github
log.ts:301  INFO Migrating global extension storage from github.remotehub to GitHub.remotehub...
log.ts:301  INFO Migrated global extension storage from github.remotehub to GitHub.remotehub
log.ts:301  INFO Migrating workspace extension storage from github.remotehub to GitHub.remotehub...
log.ts:301  INFO Migrated workspace extension storage from github.remotehub to GitHub.remotehub
xhr.js:166
   Refused to set unsafe header "User-Agent"

setRequestHeader @ xhr.js:166
xhr.js:166
   Refused to set unsafe header "User-Agent"

setRequestHeader @ xhr.js:166
xhr.js:166
   Refused to set unsafe header "User-Agent"

setRequestHeader @ xhr.js:166
main.js:1
   Loading vscode-nls-web-data failed. Are you running this outside of VS Code? If so, you may need to intercept the import call with your bundled NLS data.

189 @ main.js:1
abstractTaskService.ts:2294
   Custom workspace tasks are not supported.

_computeWorkspaceFolderTasks @ abstractTaskService.ts:2294
log.ts:301  INFO Getting Manifest... ms-vscode.vscode-js-profile-table
log.ts:301  INFO Installing extension: ms-vscode.vscode-js-profile-table
log.ts:301  INFO Installing the extension without checking dependencies and pack ms-vscode.vscode-js-profile-table
log.ts:301  INFO Extension installed successfully: ms-vscode.vscode-js-profile-table
log.ts:313   ERR [ms-vscode.remote-repositories]: notebook/cell/executePrimary is a proposed menu identifier. It requires 'package.json#enabledApiProposals: ["notebookEditor"]' and is only available when running out of dev or with the following command line switch: --enable-proposed-api ms-vscode.remote-repositories
18abstractTaskService.ts:2294
   Custom workspace tasks are not supported.

_computeWorkspaceFolderTasks @ abstractTaskService.ts:2294
log.ts:313   ERR Error while registering log channel file:///20220826T152121/ptyhost.log Timed out while waiting for file to be created
extHostLanguages.ts:89
   Uncaught (in promise) Error: LanguageStatusItem with id 'info' ALREADY exists
at E.createLanguageStatusItem (extHostLanguages.ts:89:10)
at Object.createLanguageStatusItem (extHost.api.impl.ts:579:29)
at _showStatusAndInfo (anycode.extension.browser.js:26093:40)
at eval (anycode.extension.browser.js:26215:5)

async.ts:357
   Uncaught (in promise) Canceled: Canceled
at c.cancel (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:84:13728)
at r.cancel (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:84:14087)
at o.unwatch (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:1998:8012)
at https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:1998:9803
at S.invoke (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:80:145)
at o.deliver (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:80:2266)
at l.fire (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:80:1844)
at _n.dispose (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:733:16875)
at S.destroyModel (https://main.vscode-cdn.net/insider/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/workbench.web.main.js:747:1250)

</details>

It has just happened again in a Codespace.

This was my own error as I was using github.dev on another machine where I hadn't enabled settings sync before. Sorry for the noise!


Scale to zero, expect 502, get 504

A number of us have seen this happening.  I've tested with three different configurations.  Those configurations and their results:

kube-aws v0.4.0 w/ k8s v1.1.2: 504
micro-kube v0.3.0 w/ k8s v1.1.7: 504
Heard reports of GKE w/ k8s v1.1.8 yielding 502 (as the tests expect), so... micro-kube (unmerged branch) w/ k8s 1.1.8: 502

So it would seem that requests to k8s services with no endpoints in service yield different response code in k8s < v1.1.8 and k8s v1.1.8.
I believe the correct resolution to this is to make the router smarter, so the response from the router is more predictable, regardless of which minor release of k8s it is running on top of.  Router did this aat one time, but the code in question was judged both buggy and unnecessary (based on what we knew at the time).  It was cut instead of fixed.  Hindsight being 20/20, that was a mistake.
I'll open a separate issue to track this in router, but I'm also filing it here so we keep good line of site between the e2e tests and whatever issues are blocking them from completing deterministically wherever they may run.

When router is enhanced to handle this better, I anticipate I'll have it returning 503 (service unavailable) under these circumstances.  The e2e tests should probably be updated accordingly.  I will handle that.

Closing this as the problem is now well understood and worked around for beta.  deis/router#153 will fix this in rc1 and #127 tracks the complementary change that needs to be made to e2e tests.


[RN0.66][Android] Direct local .aar file dependencies are not supported when building an AAR.

Description
I have 3 rn modules that uses aar files. They reference it in their own build.gradle file like this:
compile files('libs/mylib.aar')

Until now, it was working fine.
I recently upgraded my app project from react native 0.63 to react native 0.66 and now when I assembleRelease it, I get:

Direct local .aar file dependencies are not supported when building an AAR. The resulting AAR would be broken because the classes and Android resources from any local .aar file dependencies would not be packaged in the resulting AAR. Previous versions of the Android Gradle Plugin produce broken AARs in this case too (despite not throwing this error).

I workaround the problem by importing those aar files in my app's build.gradle file but that sucks, my app should not be aware of those aar files at all...
Is there any way to use aar files in rn modules now with gradle 4.2+ ?
Version
0.66.3
Output of npx react-native info
$ npx react-native info
info Fetching system and libraries information...
System:
OS: macOS 12.1
CPU: (10) arm64 Apple M1 Max
Memory: 11.16 GB / 64.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 16.13.2 - ~/.nvm/versions/node/v16.13.2/bin/node
Yarn: 1.22.10 - /usr/local/bin/yarn
npm: 8.1.2 - ~/.nvm/versions/node/v16.13.2/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.11.2 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.0.1, iOS 15.0, macOS 12.0, tvOS 15.0, watchOS 8.0
Android SDK:
API Levels: 18, 23, 24, 25, 26, 27, 28, 29, 30, 31
Build Tools: 23.0.1, 23.0.3, 25.0.0, 25.0.2, 25.0.3, 26.0.0, 26.0.1, 26.0.2, 26.0.3, 27.0.3, 28.0.2, 28.0.3, 29.0.0, 29.0.2, 29.0.3, 30.0.2, 30.0.3, 31.0.0
System Images: android-19 | Google APIs Intel x86 Atom, android-21 | Google APIs Intel x86 Atom, android-23 | Intel x86 Atom_64, android-23 | Google APIs Intel x86 Atom, android-23 | Google APIs Intel x86 Atom_64, android-25 | Google APIs Intel x86 Atom, android-27 | Google APIs Intel x86 Atom, android-28 | Intel x86 Atom, android-28 | Intel x86 Atom_64, android-28 | Google APIs Intel x86 Atom, android-29 | Intel x86 Atom, android-29 | Intel x86 Atom_64, android-29 | Google APIs Intel x86 Atom
Android NDK: 20.1.5948944
IDEs:
Android Studio: 4.2 AI-202.76<IP_ADDRESS>51085
Xcode: 13.1/13A1030d - /usr/bin/xcodebuild
Languages:
Java: 11.0.8 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.2 => 17.0.2
react-native: 0.66.3 => 0.66.3
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce
1 - Create or reuse a react native module that references a .aar file,
2- Try to gradlew assembleRelease the react native app project. You will run into this error.
Snack, code example, screenshot, or link to a repository
No response

There are a variety of way to do this:
https://stackoverflow.com/questions/60878599/error-building-android-library-direct-local-aar-file-dependencies-are-not-supp
As a last resort, you can put the .aar inside a Maven Repository (maven local at ~/.m2 or an internal instance of Nexus) and just let Gradle fetch it from there.
Closing also as this is not essentially RN related but is more a problem of how Gradle and the Android Gradle Plugin works 👍 Feel free to reopen if the previous solution don't work for you, our you encounter a RN specific problem.

Hey @zabojad, hoping you can help me out here. I'm running into this same error with a third party package. They have an AAR file in their libs/ directory, and in their build.gradle:
dependencies {
    implementation fileTree(dir: 'libs', include: ['*.jar','*.aar'])
}

You said "I workaround the problem by importing those aar files in my app's build.gradle". Could you help me out with how to do that? Or have you found a better way that I could patch this dependency?

facing the same issue
@zabojad @marcshilling did you guys fix it ?

Hi @marcshilling and @a-eid ,
So here is what you can do:

in your main RN application, put you aar files in android/app/libs,

then edit your android/app/build.graddle file and add this line:
// ...
dependencies {
// ...
implementation fileTree(dir: "libs", include: ["*.aar"]) // ADD THIS LINE
// ...

in your react native module(s), everywhere your had this:
implementation fileTree(include: ['*.jar'], dir: 'libs')

or this
compile files('libs/mylib.aar')

replace it by this:
compileOnly files('libs/mylib.aar')

re-add your rn modules, recompile the rn project and it will work. But the sad thing here is that your react native project has now direct refs to your rn modules aar files which sucks big time.
If you guys find a better way to do that without publishing the aar files to a distant repo like Maven as suggested by @cortinico , I'd be very interested in your inputs on how you manage to do that.

@zabojad unfortunately I won't be able to do that as I'm using expo.
thank you.

@a-eid here's how I got past this:

Patch the problematic 3rd party dependency's build.gradle file. Under their dependencies { } section, they had a line like this:implementation fileTree(dir: 'libs', include: ['*.jar','*.aar']) //Load all aars and jars from libs folder

My patch changes that line to:implementation(name: 'the-name-of-the-aar', ext: 'aar')

In my project's build.gradle, under allprojects { repositories { }, added:flatDir { dirs "$rootDir/../node_modules/the-third-party-dependency/android/libs" }

Where the AAR file lives

@zabojad do you duplicate your .aar file, or where does it live ?

@marcshilling I'm not sure why your solution is not working for me
would this line

implementation(name: 'the-name-of-the-aar', ext: 'aar')

include the .aar extension as well as the libs/ such that it would be

implementation(name: 'libs/the-name-of-the-aar.aar', ext: 'aar')

@a-eid here's how I got past this:

Patch the problematic 3rd party dependency's build.gradle file. Under their dependencies { } section, they had a line like this:
implementation fileTree(dir: 'libs', include: ['*.jar','*.aar']) //Load all aars and jars from libs folder

My patch changes that line to:
implementation(name: 'the-name-of-the-aar', ext: 'aar')

In my project's build.gradle, under allprojects { repositories { }, added:
flatDir { dirs "$rootDir/../node_modules/the-third-party-dependency/android/libs" }

Where the AAR file lives

Tried your method but now getting..

A failure occurred while executing com.android.build.gradle.tasks.VerifyLibraryResourcesTask$Action
Android resource linking failed

Found a solution working for me. Instead of ./gradlew assembleRelease try ./gradlew app:assembleRelease. Now APK build is working fine even with ./gradlew assembleRelease.


Avoid merging intersecting paths

Merging paths that overlap can cause problems with transparency determinations related to fill rules and can negatively impact paths which make use of relative coordinates.
Avoiding merging those paths addresses the issues in #59 also, but in a more robust way—so we can consider merging even odd fill rule paths, so long as they don't intersect.
This intersection test is fairly corse. An axis-aligned bounding box is computed for each path and a simple rectangle intersection test is performed. Since paths aren't typically rectangular, sometimes nearby but non-overlapping paths will be considered intersecting. There are more involved algorithms that can improve on this mentioned in #88, but:
a) the bounding box check is fairly good and the benefits of merging even odd paths outweigh the losses w.r.t. occasionally not merging two paths that don't overlap
b) the downside is a slightly larger than optimal graphic, but not an incorrect graphic, so improvements regarding intersection precision should only really shrink the graphic—not change its semantics.
Fixes #88, #101

I used https://codepen.io/branneman/pen/nBjeLo to sketch the bounding boxes to visually verify.
absolute elliptical arc

absolute polyquadratic

absolute smooth polyquadratic

rotated elliptical arc (toggling sweep flag)
The elliptical arc's box is computed for the whole ellipse, which you can see in the recording by me flipping the sweep flag. Not totally ideal, but good enough for now. The downside is similar to the bounding box approach in general—at worst we avoid merging paths that really could be merged but the image is not warped. Interpolating the ellipse with endpoint parameterization is kinda tricky.
https://github.com/user-attachments/assets/cb25adff-475a-49f4-ba7b-20a0b3675dc5
heart

Minnesota (regression 60)

smooth quadratic

relative polyquadratic

relative smooth polyquadratic

standalone smooth curve


Issue with predicting relations end-to-end

When I try predicting relations end-to-end in the predict_scirex_model.sh script (after resolving the issues in #12 and #13), I am getting another error:
FileNotFoundError: [Errno 2] No such file or directory: 'outputs/pwc_outputs/experiment_scirex_full/everything//metrics.json'
I'm not sure when this everything directory could have been constructed in the code, since such a directory name is not hardcoded in the training code, nor did the instructions ask to set it as an environmental variable.
Might this be a typo?

I have updated the prediction script. Can you let me know if it works now ?

Yeah that seems to work now - error went away


Adding the Webserver

Summary
Provide code for a Webserver (ktor) that builds an API that access the badge image creation libraries and facilities. See it running as https://zebadge.app .
It's hosted as a cloud function on Google, using Google's/Squarespace custom domain and cloudflares DNS for SSL. To update, ssh into cloud function, update git, rerun server.
Currently @mariobodemann is paying for hosting.
When opened, the website displays a form with name and contact, including size and color. Once this form is changed, the badge will get drawn using a js 2d canvas. Alternatively a background image can get selected. Upon changes a new request is send to the API, returning a PNG that is also drawn next to the badge.
Once happy with the badge the use can connect ZeBadge and press the "sent" button to create the serial data thought the API that needs to be sent to the badge.
Once sending is done, the digital badge will be updated, showing the new data.
How It Was Tested
It was tested two ways:

Local Host: a server is spun up locally by calling ./gradlew server:run --args="8000". Upon connecting chrome, or edge to the localhost:8000 address, the certificate error gets ignored. The website can now be fully used and some names were changed and the result was uploaded to ZeBadge.
Same test was executed on https://ZeBadge.app

Screenshot/Gif

base badge test

background image test

Success

Overall makes sense, but I'd still recommend to look at this:
https://www.cloudflare.com/application-services/products/ssl/
If you point DNS to there, you can get HTTP>HTTPS redirections for free, plus image caching for free… and the app can always run in non-SSL mode (plus you get a free cert rotation by Cloudflare). 🤷♂

Hey,
thanks for the review, I'll talk about the specific things in a minute, on individual comments.
BUT: I am using cloudflare to generate the SSL certificate (That then gets transformed from PEM to PKCS to then JKS to be delivered by the webserver). Or do you mean anything different, that I might (:scream:) not understand yet?

I will merge it for now, it is getting to big for me to handle. If there are more changes, let us do them individually...

What I meant was, you can do some port forwarding and never worry about SSL in the service itself :)
E.g.
[ Client ] -> DNS fetch -> request https://host:ip/endpoint
but here
Using Cloudflare you can point DNS to them, then enable SSL and caching on Cloudflare, then they forward all requests to you secretly. Example:
[ Client ] -> DNS fetch -> boom cloudflare hello -> secret redirect to https://host:ip/endpoint
This way the service always run in HTTP mode and you pretend certificates don't exist. The same is achievable with cert rotator attached to k8s ingress, and I've done it in docker in the past too 🗡  (but docker requires the whole server to run docker only, so that you can proxy requests through a single container to all other containers)
Not sure if that was clear 😄 yours works too, probably™. Just saying it could be simpler


fix all the broken types in the r2 workers-api-reference page

Summary
All the types in the r2 workers-api-reference page are pretty broken and this PR is addressing them.
I am pretty sure they got broken by the starlight migration.
Thanks @aslemammad for raising this 🙂

Thank you so much for being fast 🤝


Properly handle allocation failure

The change in #89 did not properly handle allocation failures. On
failure, alloc() returns a null pointer, and this is not checked.
This change moves buffer allocation to the new Alloc API, and correctly
handles allocation failure and potential unsafety with zero-sized alloc
requests.
I also removed the dependency on uefi-services from uefi-alloc. The
dependency isn't needed, and now users can use uefi-exts with their
own allocators.

Looks like a great change, thank you


Add Monitoring Thread to Watch for Worker Shutdown

Added a thread to the VixDiskLibServer to read one end of a pipe that
the SmartProxyWorker has opened.  When the read returns the worker process
has exited so the VixDiskLibServer shuts down.
This fixes the BZ https://bugzilla.redhat.com/show_bug.cgi?id=1258985
This fix was implemented in lieu of previous PR #4277 which passed SIGTERM
from the worker process to the server process.  The new implementation
will handle any signal that has caused the worker to exit including
SIGKILL. The previous PR will be closed.
Instead of using an environment variable to let VixDiskLibServer know which
FD contains the pipe we are using a known FD.  In addition we have changed
the previous logic for the other pipe being used by these two
processes which is used to hand the DRb URI back to the worker so that it
also uses a known FD.
Finally we have fixed the retry logic in the worker to read the URI before
attempting to establish the DRb connection.
The "known FD" and retry logic code come from PR #4318 by @matthewd which
will be closed in lieu of this new one.
@roliveri @jrafanie @hsong-rh please review.

Is it feasible to a spec that proves the child goes away when we SIGKILL the parent?


Adjust TextUnsupervisedTests.testCreateWikiText2WithBpe

Test currently broken: https://source.cloud.google.com/results/invocations/e9a0dadd-a808-457d-a2f5-850fa9690960/targets/s4tf%2Fmodels%2Fubuntu%2Fmanual/log.

Any idea what happened here, has the dataset changed?

Looks like it's actually flaky, I re-ran it and it passed without this change. It'd be interesting to know why.

Ah sreated an issue and explained there: https://github.com/tensorflow/swift-models/issues/568

Thanks! The checkpoint loading theory sounds plausible to me.


Sync code for supporing SIG BLE mesh and sensor monitor example

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.luwang seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Getting a failed to parse stream

Running in docker on linux. I get the following when trying to launch a stream
There is an active event. Going to start the stream.
Getting stream for event:  ca34ba2a-8324-479c-9df5-e67e500639bb
Failed to parse the stream
Any thoughts? I put the container in privileged mode just in case and am still seeing it. Any thoughts?

Yeah, I noticed in the login png that docker compose passed the quotes into username. I changed that and reset my password to something simpler. I was still getting the error but I think it could have been a patience thing as well as in one case it started playing. Ill try to do some more testing. I was seeing a different result running docker run as opposed to docker compose so Ill see what I can find. Thanks for the help and this tool!

That's interesting... I only saw that before I got the login stuff refactored and it wasn't pushing the right buttons. I'm glad it's working for you now though. Not really a way to get around that.

hi @m0ngr31 Failed to parse the stream i am getting this problem even followed the detail you suggested.
is it still working.
@ssimpson89 how did you managed to reslove this problem and is it still working.

I changed the way getting the stream works, so we can open this up again if I get more feedback.
Just for clarification for those coming in later, you should normally only get a "Failed to parse stream" message when:

You are region blocked from something
Event hasn't started
Event has already ended

I'm hoping everything else works


Add support for just passing in a string?

Is it possible to just have a method like once which instead of taking the element instead just takes the html or word string and processes it?

I do like the idea, but one thing you can do now to emulate that behavior is set your target div to display: none in the css. This way, the div doesn't show on the page and you can still do your thing.

Definitely - I hear what you're saying. Would be nice to remove that dependency all together.

Now available in version 3.0.1. Thanks for the inputs.

@RadLikeWhoa  thx for update, and can u publish the package on the npmjs，i can't find the version 3.0.1


Create an audit event entry for each resource retrieved via search

Is your feature request related to a problem? Please describe.
IBM FHIR Server has audit logging in support of HIPAA and similar legislation.
Each read/vread/history for a given resource is logged.
However, in FHIR, a search will also return the full contents of a resource (by default).
Currently, our audit logging follows the advice at https://www.hl7.org/fhir/auditevent.html#<IP_ADDRESS> and we log search with an action code of E (execute) and we capture the query and when it was performed.
However, with this information alone, it is very difficult to determine exactly which resources were returned.
Describe the solution you'd like
I'd like to capture the resource type, resource id, and resource version for each resource that is returned to the client, for every search.
Describe alternatives you've considered
Continue to log only the query and not the results of that query.
Acceptance Criteria
1.
GIVEN [a precondition]
AND [another precondition]
WHEN [test step]
AND [test step]
THEN [verification step]
AND [verification step]
Additional context
See related discussion at https://chat.fhir.org/#narrow/stream/179247-Security-and.20Privacy/topic/AuditEvent.20for.20Patient

Paul raised a concern about the overall size, but I think that even in the worst case we should be able to keep the audit message under our 1MB limit:
OK, then I feel like it should be ok.  Assuming we used some kind of string entry like <resourceType>/<id>/_history/<version>, here's my rough back-of-envelope calculations.
Average case:
entry wrapper (need to see how this looks in CADF to be sure):  1 byte * 12 chars = 12 bytes
resourceType/:  1 byte * 20 chars = 20 bytes
id/:  1 byte * 50 chars for value = 50 bytes
_history/:  1 byte * 9 chars = 9 bytes
version:  1 byte * 2 chars = 2 bytes
= 93 bytes per entry

100 entries * 93 = 186,000 bytes (.0093 MB)

Worst case:
entry wrapper (need to see how this looks in CADF to be sure):  1 byte * 12 chars = 12 bytes
resourceType/:  1 byte * 40 chars = 40 bytes
id/:  4 byte * 64 chars for value = 256 bytes
_history/:  1 byte * 9 chars = 9 bytes
version:  1 byte * 64 chars = 64 bytes
= 381 bytes per entry

2000 entries * 381 = 762,000 bytes (.762 MB)

Somewhat related... should be done at same time... https://github.com/IBM/FHIR/issues/1816

team discussion:  should we use the internal database id instead of the fhir fullUrl?
This makes a lot of sense for the CADF format, but not sure it could be used for the AuditEvent format (which uses Reference data type).
Another issue is that we don't even pass this internal id back to the rest layer today.

The "worst case" given above assumes our max page size is 1000 entries and our max include size is also 1000.
Per https://github.com/IBM/FHIR/issues/2090 these will become configurable.  Therefor, at minimum, we need to advise users to increase the max kafka message size limit if they expand the max page size or max include size above 1000.


Prevent extra similarity computation for single-level graphs

Description
#findBestEntryPoint is used to determine the entry point for the last level of HNSW search
It finds the single best-scoring node from all upper levels - but performs an unnecessary computation (along with recording one visited node) when the graph just has 1 level (so the entry node is just the overall graph's entry node)
Also added a test to demonstrate this (fails without the changes in PR) -- where we visit graph.size() + 1 nodes when the topK is high (should be a maximum of graph.size())

@kaivalnp you can add it :)

Replicated this commit (which added the 9.9.0 entry) for 9.10.0
Please let me know if I missed something..


Disk pools should have minimum/recommended sizes in manual

User needs guidance on what the disk pool needs are so they can properly select (or add) disk pool/type available in their cloud config.

Case in point:  We defined the cell to be 10GB, and the cell failed to come up with the following error in the rep.stderror log:
{"timestamp":"1534734615.211648226","source":"rep","message":"rep.failed-to-initialize-executor","log_level":2,"data":{"error":"auto disk limit must result in a positive n│··························································
umber"}}

This was due to the max_cache_size_in_bytes being over 9.5GB, so the 10GB disk was, after all deductions, massively insufficient.  See https://github.com/cloudfoundry/executor/blob/9f8d9d8a99a7dd93e841d755750f2f0104772b87/initializer/configuration/configuration.go#L63

Alternatively, or even better in conjunction with the above documentation, the check should see if the disk size is adequate enough


add support for scan test (--scan-test)

This feature will report all the tests that can be run based on the available software found in the system and all the YAML configs found in buildtest.
The user will get a report for all the packages and # of tests for each package. This will include system package test by checking all YAML configs in system package and installed system package found in the system by using rpm -q

This feature is done, see https://github.com/HPC-buildtest/buildtest-framework/commit/11f6b6d8b56c394b1c8e74204a743403afb29b2d


Typo in "conflict"

Should this be "conflict"?
https://github.com/bcbio/bcbio-nextgen/blob/9fb4ab7b65ec41313a88d7f788b1d09dcf531349/bcbio/variation/strelka2.py#L179

Thanks much for catching this, you're exactly right. I pushed a fix for this typo. Much appreciated.


Adding contributing.md file

Hey can you assign me this issue.

@Arpcoder mention in which open source program are you participated?
And your name too.

@Arpcoder mention in which open source program are you participated? And your name too.

Name- Arpna
I have opened this under SSOC

@Arpcoder go ahead.

#SSOC
@Avdhesh-Varshney can you please assign this issue to me under SSOC'24


SIGSEGV in vim at ex_getln.c:630

Hello,
We are currently working on fuzz testing feature, and we found a SIGSEGV on vim.
The stack traces are as follow:
Program received signal SIGSEGV, Segmentation fault.
__strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:65
65	../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory.
#0  __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:65
#1  0x00007ffff6e6957c in ?? () from /usr/lib/x86_64-linux-gnu/libasan.so.4
#2  0x000055555582061e in may_adjust_incsearch_highlighting (firstc=47, count=1, is_state=0x7fffffffd750, c=20) at ex_getln.c:630
#3  0x0000555555827f99 in getcmdline_int (firstc=47, count=1, indent=0, clear_ccline=1) at ex_getln.c:2261
#4  0x0000555555824adb in getcmdline (firstc=47, count=1, indent=0, do_concat=1) at ex_getln.c:1556
#5  0x00005555559903a5 in nv_search (cap=0x7fffffffda40) at normal.c:4337
#6  0x000055555597c684 in normal_cmd (oap=0x7fffffffdb80, toplevel=1) at normal.c:1099
#7  0x0000555555da04b2 in main_loop (cmdwin=0, noexmode=0) at main.c:1501
#8  0x0000555555d9f249 in vim_main2 () at main.c:878
#9  0x0000555555d9e90d in main (argc=10, argv=0x7fffffffddc8) at main.c:425

Here is the full stack trace : full_stacktrace_poc_1.zip
Step to reproduce
We configured vim using CFLAGS="-g -O0 -fsanitize=address" CXXFLAGS="-g -O0 -fsanitize=address" LDFLAGS="-g -O0 -fsanitize=address" ./configure --prefix=$(pwd)/ and build it using make -j10, and run it with:
./vim -u NONE --cmd + -Z --clean -s <attached file> -C

Attachment: input_vim_poc_1.zip
Environment

OS: Ubuntu 18.04.5 LTS
GCC version: gcc 7.5.0
vim version: latest commit (50c56893) of master branch in github (link)

Thank you.

A fuzzer tends to use lots of text that doesn't matter.
Please reduce the input to the absolute minimum.  Then we could use it as a regression test.

@brammool  asked:

Please reduce the input to the absolute minimum.

I minimized it to this:
$ ./vim --clean -c 'call feedkeys("//\x14")'
Vim: Caught deadly signal SEGV
Vim: Finished.
Segmentation fault (core dumped)

With gdb:
(gdb) bt
#0  __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:65
#1  0x00000000004b687c in may_adjust_incsearch_highlighting (firstc=47, count=1,
    is_state=0x7fffffffd9a8, c=20) at ex_getln.c:630
#2  0x00000000004b0a48 in getcmdline_int (firstc=47, count=1, indent=0, clear_ccline=1)
    at ex_getln.c:2261
#3  0x00000000004af199 in getcmdline (firstc=47, count=1, indent=0, do_concat=1) at ex_getln.c:1556
#4  0x000000000054a25c in nv_search (cap=0x7fffffffdbd8) at normal.c:4337
#5  0x0000000000544710 in normal_cmd (oap=0x7fffffffdc60, toplevel=1) at normal.c:1099
#6  0x000000000070f5ab in main_loop (cmdwin=0, noexmode=0) at main.c:1501
#7  0x000000000070dd5a in vim_main2 () at main.c:878
#8  0x000000000070b5d8 in main (argc=4, argv=0x7fffffffde48) at main.c:425

(gdb) up
#1  0x00000000004b687c in may_adjust_incsearch_highlighting (firstc=47, count=1,
    is_state=0x7fffffffd9a8, c=20) at ex_getln.c:630
630		patlen = (int)STRLEN(pat);

(gdb) list
625
626	    if (search_delim == ccline.cmdbuff[skiplen])
627	    {
628		pat = last_search_pattern();
629		skiplen = 0;
630		patlen = (int)STRLEN(pat);
631	    }
632	    else
633		pat = ccline.cmdbuff + skiplen;
634

(gdb) p pat
$1 = (char_u *) 0x0

So pat is NULL at line ex_getln.c:630.

This minimization may be better:
$ ./vim --clean -c 'call feedkeys("//\<C-g>")'
Vim: Caught deadly signal SEGV
Vim: Finished.
Segmentation fault (core dumped)

All these commands crash in a similar way:
vim --clean -c 'call feedkeys("//\<C-g>")'
vim --clean -c 'call feedkeys("//\<C-t>")'
vim --clean -c 'call feedkeys("??\<C-g>")'
vim --clean -c 'call feedkeys("??\<C-t>")'


No data returned from GCP KMS decryption function

When using the decryptSymmetric function there is no returning data.
const {KeyManagementServiceClient} = require('@google-cloud/kms');

// Instantiates a client
const client = new KeyManagementServiceClient();
const keyName = client.cryptoKeyPath(projectId, locationId, keyRingId, keyId);

async function decryptSymmetric(ciphertext) {
  console.log(ciphertext.toString('base64'));
  const [result] = await client.decrypt({
    name: keyName,
    ciphertext: ciphertext,
  });

  const plaintext = result.plaintext.toString('utf-8');

  console.log(`Plaintext: ${plaintext}`);
  return plaintext;
}

I am expecting a return plaintext that is in base64  and getting:
Serving function...
Function: helloWorld
URL: http://localhost:3030/
CiQA4vWCb+DocwFpiThkYYyO48JyFKIJ5McAd/XT0t/9Rq4k258SIQA+ePV/vGbIerd0M5OFRgo+tFKtl1JJiwCHtvWlVdd1rw==

Plaintext:
Decrypt results:

Docs I am following: https://cloud.google.com/kms/docs/encrypt-decrypt

Eliminen la linea:
const ciphertext = Buffer.from(get_ciphertext);
En su lugar coloque
let ciphertext = '<valor en base64>';
sustituir <valor en base64> por la cadena base64 que genera client.encrypt
IMPORTANTE: sin decodificar el base64
	const locationId = 'us-east1';
	const keyRingId = 'tcsecure';
	const keyId = 'tcsecureone';
	//const ciphertext = Buffer.from(get_ciphertext);
	let ciphertext = '<valor en base64>';

	// Imports the Cloud KMS library
	//const {KeyManagementServiceClient} = require('@google-cloud/kms');

	// Instantiates a client
	const client = new KeyManagementServiceClient();

	// Build the key name
	const keyName = client.cryptoKeyPath(projectId, locationId, keyRingId, keyId);

	async function decryptSymmetric() {
	  const [result] = await client.decrypt({
	    name: keyName,
	    ciphertext: ciphertext,
	  });

	  //const plaintext = result.plaintext.toString('utf8');

	  const plaintext = result.plaintext;

	  console.log(\`Plaintext: ${plaintext}\`);
	  return plaintext;
	}

	return decryptSymmetric();```

For Typescript users, I got these two snippets to work.
For encryption:
const [response] = await client.encrypt({
      name: keyName,
      plaintext: Buffer.from(plaintext).toString('base64'), // e.g. decryptedStr from below snippet
});
const encryptedStr = Buffer.from(response.ciphertext || '').toString('base64');

For decryption:
const [response] = await client.decrypt({
  name: keyName,
  ciphertext: base64Ciphertext, // e.g. encryptedStr from above snippet
});
const decryptedStr = Buffer.from(response.plaintext || '').toString('utf8');

@rhyeen am I following correctly that the samples are missing the .toString('base64') which made things work for you?

@bcoe somewhat.  The samples work (as in this encryption sample and this decryption sample; but only in Javascript.  In Typescript, it's a compiler error because ciphertext.toString('base64') and result.plaintext.toString('utf8') are 1) not checking if ciphertext/result.plaintext are undefined, string, or Uint8Array and 2) for string, or Uint8Array, .toString() does not have any parameters.
Now, I don't know how it's working in Javascript given (1) and (2), but in Typescript, you essentially need to replace ciphertext.toString('base64') and result.plaintext.toString('utf8') with Buffer.from(ciphertext || '').toString('base64'); and Buffer.from(result.plaintext || '').toString('utf8'); respectively.
It should also be noted that both .decrypt and .encrypt expect plaintext and ciphertext respectively to be base 64 encoded and will hang indefinitely if not provided as such.

@mblackbourne have you been able to get your application working? If so what changes did you need to make?

@bcoe Never got my node version to work. Ended up just building it in python.

@rhyeen, thanks for digging into this!
In attempting to reproduce the issue, I think the main issue is that the function expects ciphertext to be either a Buffer or a base-64 encoded string. There is also the issue compiling Typescript, since Typescript does not know what to expect back. However, we can coerce the type as follows in Typescript and Javascript (without the optional chaining):
const plaintext = decryptResponse.plaintext?.toString();
Our generator is limited as it must return the types that it accepts, however, this particular function will always just return a Buffer.
I will update documentation on this sample accordingly to create less confusion!


How do you evaluate the model you train? So far I see translate instruction not expected output

Hi TransLLM owner, Do you have like benchmark data where expected output is provided?
Cheers!

Hi, we did not manually construct reference answers for our benchmarks in Thai (MT-Bench and Alpaca-Eval). For MT-Bench and Alpaca-Eval in English, the authors regard the GPT-4 outputs as references. Since our Thai questions are parallel to English questions, we may simply translate these GPT-4's English answers into Thai as references.


About rendering and evaluation

Hello, Could you please provide instructions for rendering and evaluation?

Hi,
Thank you for your advice! Please refer to the latest readme file and render.py.

Thank you for your assistance!


Up/Don arrow keys navigate history [Feature Request]

I am used to pressing up and down arrow key to navigate through the bash history.  Would be nice if Wave could mimic the same.  Or at least have an option to enable this, if you have other plans for the up/down arrow keys for something else.

Hi, thanks for submitting.  Up/Down arrows should be working to navigate history, when you're focused in the command input box, and also when the ctrl-r history is open.  Is that not working for you, or is there another flow where you want the up/down arrows to work?
Also, to get more context, can you let me know what architecture you're using (linux or mac) and what type of keyboard (US or is it set for a different default language)?  Thanks

Linux, with US keyboard.  Ubuntu 20.  The left and right arrow keys work to move within the command.  Just the up/down arrow keys don't do anything.

This is really strange.  Up/Down works in MacOS, and works in my Linux VM.  I'm getting a physical Linux laptop for testing, hopefully next week, and I'll be able to test on that to see if I can replicate.

Can't replicate on my side. Up/down keys do allow navigating through the bash history.


xSQLServerHelper: Create helper function Test-ClusterPermissions

Pull Request (PR) description

Added new helper function "Test-ClusterPermissions".
Changes to xSQLServerAlwaysOnAvailabilityGroup

Use the new helper function "Test-ClusterPermissions".
Refactored the unit tests to allow them to be more user friendly.

Changes to xSQLServerAlwaysOnAvailabilityGroupReplica

Use the new helper function "Test-ClusterPermissions".

Changes to SMO.cs

Added default properties to the Server class

AvailabilityGroups
Databases
EndpointCollection

Added a new overload to the Login class
Added default properties to the AvailabilityReplicas class

AvailabilityDatabases
AvailabilityReplicas

This Pull Request (PR) fixes the following issues:
Fixes #446
Task list:

[X] Change details added to Unreleased section of CHANGELOG.md?
[ ] Added/updated documentation, comment-based help and descriptions in .schema.mof files where appropriate?
[ ] Examples appropriately updated?
[X] New/changed code adheres to Style Guidelines?
[X] Unit and (optional) Integration tests created/updated where possible?

This change is

Codecov Report

Merging #830 into dev will decrease coverage by <1%.
The diff coverage is 100%.

@@         Coverage Diff         @@
##            dev   #830   +/-   ##
===================================
- Coverage    96%    96%   -1%
===================================
  Files        31     31
  Lines      3310   3293   -17
===================================
- Hits       3193   3176   -17
  Misses      117    117

Man, your did some complex refactor of the tests here! :smile:  Awesome work on the test cases! Very clean code!

Reviewed 6 of 8 files at r1, 3 of 3 files at r2.
Review status: all files reviewed at latest revision, 13 unresolved discussions.

CHANGELOG.md, line 26 at r2 (raw file):

      environment variable in the (LCM) PowerShell session did not contain the new
      module path.
  - Added new helper function "Test-ClusterPermissions". ([issue #446](https://github.com/PowerShell/xSQLServer/issues/446))

Move the full stop ('.') to the end of the text (after the parenthesis).

xSQLServerHelper.psm1, line 1199 at r2 (raw file):

        The server object on which to perform the test.
#>
function Test-ClusterPermissions

This function (with the verb 'Test') should have and output type of System.Boolean and return $true if the cluster permission exist, or $false if they don't.

xSQLServerHelper.psm1, line 1236 at r2 (raw file):

'recommended '

This must be localized as well. I think it is better to have two different localized strings instead.

xSQLServerHelper.psm1, line 1236 at r2 (raw file):

Write-Verbose

For all Write-Verbose please add -Verbose parameter. It is a bug (or feature, unknown at this point) that LCM does not pass the VerbosePreference correctly to (helper) modules. There is an issue about that somewhere (in the DscResources) also. The workaround is to add -Verbose on all Write-Verbose

xSQLServerHelper.psm1, line 1252 at r2 (raw file):

'recommended ',$loginName,"Trying with '$ntAuthoritySystemName'.

This must be localized as well.

xSQLServerHelper.psm1, line 1267 at r2 (raw file):

    {
        throw ($script:localizedData.ClusterPermissionsMissing -f $sqlServer,$sqlInstanceName )
    }

Add an else here to write a verbose message saying that the correct permission was found for account X?

Tests/Unit/MSFT_xSQLServerAlwaysOnAvailabilityGroup.Tests.ps1, line 27 at r2 (raw file):

    InModuleScope $script:DSCResourceName {

        #region mock server object variables

Please remove the extra indent inside the regions. Throughout.

Tests/Unit/MSFT_xSQLServerAlwaysOnAvailabilityGroup.Tests.ps1, line 382 at r2 (raw file):

=

Missing space after equal sign. Throughout.
If you use VS Code you can apply formatting and fix all these (I think).

Tests/Unit/MSFT_xSQLServerAlwaysOnAvailabilityGroup.Tests.ps1, line 466 at r2 (raw file):

        Describe 'xSQLServerAlwaysOnAvailabilityGroup\Set-TargetResource' {
            BeforeAll {
                Mock -CommandName Connect-SQL -MockWith $mockConnectSqlServer1 -Verifiable -ParameterFilter { $SQLServer -eq $mockServer1Name }

Please change so braces are not on the same row. For both Mock and Assert-MockCalled. Throughout.

Tests/Unit/xSQLServerHelper.Tests.ps1, line 1536 at r2 (raw file):

Mock -CommandName Test-LoginEffectivePermissions -MockWith { $mockClusterServicePermissionsPresent } -Verifiable -ParameterFilter { $LoginName -eq $clusterServiceName }

Please write this more readable
Mock -CommandName Test-LoginEffectivePermissions -MockWith {
    $mockClusterServicePermissionsPresent
} -ParameterFilter {
    $LoginName -eq $clusterServiceName
} -Verifiable

Throughout.

Tests/Unit/xSQLServerHelper.Tests.ps1, line 1542 at r2 (raw file):

            $systemAccountName= 'NT AUTHORITY\System'
        }
        BeforeEach {

New row before this one.

Tests/Unit/xSQLServerHelper.Tests.ps1, line 1548 at r2 (raw file):

New-Object -TypeName Microsoft.SqlServer.Management.Smo.Login($mockServerObject,$clusterServiceName)

This seems to work, but this should use named parameters. I think this is the more correct way?
New-Object -TypeName Microsoft.SqlServer.Management.Smo.Login -ArgumentList $mockServerObject, $clusterServiceName

Throughout.

Tests/Unit/xSQLServerHelper.Tests.ps1, line 1564 at r2 (raw file):

Assert-MockCalled -CommandName Test-LoginEffectivePermissions -Scope It -Times 0 -Exactly -ParameterFilter { $LoginName -eq $clusterServiceName }

make this more readable. Throughout.
Assert-MockCalled -CommandName Test-LoginEffectivePermissions -ParameterFilter {
    $LoginName -eq $clusterServiceName
} -Exactly -Times 0 -Scope It

Comments from Reviewable

Thanks! It was really bothering me that I couldn't "easily" update the tests with the minor change that occurred. Now it should be a little easier! :)

Review status: 4 of 9 files reviewed at latest revision, 14 unresolved discussions.

CHANGELOG.md, line 26 at r2 (raw file):
Previously, johlju (Johan Ljunggren) wrote…
Move the full stop ('.') to the end of the text (after the parenthesis).

Done.

xSQLServerHelper.psm1, line 1199 at r2 (raw file):
Previously, johlju (Johan Ljunggren) wrote…
This function (with the verb 'Test') should have and output type of System.Boolean and return $true if the cluster permission exist, or $false if they don't.

Done.

xSQLServerHelper.psm1, line 1236 at r2 (raw file):
Previously, johlju (Johan Ljunggren) wrote…

Write-Verbose

For all Write-Verbose please add -Verbose parameter. It is a bug (or feature, unknown at this point) that LCM does not pass the VerbosePreference correctly to (helper) modules. There is an issue about that somewhere (in the DscResources) also. The workaround is to add -Verbose on all Write-Verbose

Done.

xSQLServerHelper.psm1, line 1236 at r2 (raw file):
Previously, johlju (Johan Ljunggren) wrote…

'recommended '

This must be localized as well. I think it is better to have two different localized strings instead.

Done.

xSQLServerHelper.psm1, line 1252 at r2 (raw file):
Previously, johlju (Johan Ljunggren) wrote…

'recommended ',$loginName,"Trying with '$ntAuthoritySystemName'.

This must be localized as well.

Done.

xSQLServerHelper.psm1, line 1267 at r2 (raw file):
Previously, johlju (Johan Ljunggren) wrote…
Add an else here to write a verbose message saying that the correct permission was found for account X?

Done.

Tests/Unit/MSFT_xSQLServerAlwaysOnAvailabilityGroup.Tests.ps1, line 27 at r2 (raw file):
Previously, johlju (Johan Ljunggren) wrote…
Please remove the extra indent inside the regions. Throughout.

Done.

Tests/Unit/MSFT_xSQLServerAlwaysOnAvailabilityGroup.Tests.ps1, line 382 at r2 (raw file):
Previously, johlju (Johan Ljunggren) wrote…

=

Missing space after equal sign. Throughout.
If you use VS Code you can apply formatting and fix all these (I think).

Done.

Tests/Unit/MSFT_xSQLServerAlwaysOnAvailabilityGroup.Tests.ps1, line 466 at r2 (raw file):
Previously, johlju (Johan Ljunggren) wrote…
Please change so braces are not on the same row. For both Mock and Assert-MockCalled. Throughout.

Done.

Tests/Unit/xSQLServerHelper.Tests.ps1, line 1536 at r2 (raw file):
Previously, johlju (Johan Ljunggren) wrote…

Mock -CommandName Test-LoginEffectivePermissions -MockWith { $mockClusterServicePermissionsPresent } -Verifiable -ParameterFilter { $LoginName -eq $clusterServiceName }

Please write this more readable
Mock -CommandName Test-LoginEffectivePermissions -MockWith {
    $mockClusterServicePermissionsPresent
} -ParameterFilter {
    $LoginName -eq $clusterServiceName
} -Verifiable

Throughout.

Done.

Tests/Unit/xSQLServerHelper.Tests.ps1, line 1542 at r2 (raw file):
Previously, johlju (Johan Ljunggren) wrote…
New row before this one.

Done.

Tests/Unit/xSQLServerHelper.Tests.ps1, line 1548 at r2 (raw file):
Previously, johlju (Johan Ljunggren) wrote…

New-Object -TypeName Microsoft.SqlServer.Management.Smo.Login($mockServerObject,$clusterServiceName)

This seems to work, but this should use named parameters. I think this is the more correct way?
New-Object -TypeName Microsoft.SqlServer.Management.Smo.Login -ArgumentList $mockServerObject, $clusterServiceName

Throughout.

Done.

Tests/Unit/xSQLServerHelper.Tests.ps1, line 1564 at r2 (raw file):
Previously, johlju (Johan Ljunggren) wrote…

Assert-MockCalled -CommandName Test-LoginEffectivePermissions -Scope It -Times 0 -Exactly -ParameterFilter { $LoginName -eq $clusterServiceName }

make this more readable. Throughout.
Assert-MockCalled -CommandName Test-LoginEffectivePermissions -ParameterFilter {
    $LoginName -eq $clusterServiceName
} -Exactly -Times 0 -Scope It

Done.

Comments from Reviewable

Awesome work!

Reviewed 5 of 5 files at r3.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Add StripQuote option (telegram)

Quoted messages are a good option, but sometimes they flood the chat when there are too many line breaks.

With this PR:

Works better with QuoteLengthLimit:

@jx11r I think this can be something that could better be fixed with tengo, instead of yet another option.

@jx11r I think this can be something that could better be fixed with tengo, instead of yet another option.

You're right, thanks.


chore: release 0.10.0

:robot: I have created a release *beep* *boop*
0.10.0 (2021-12-07)
Features

add website and folder upload and download (#260) (3ef1ad9)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/ethersphere/bee-dashboard/releases/tag/v0.10.0 :sunflower:


Measure size of current ledger with respect to claimable balances

We need an estimate of the current ledger state:

Size (in GB)
Number of ledger entries
Breakdown of ledger entries by type

We want to know the current memory requirements for captive core, and how much headroom we have if ledger size continues to increase.

Would be great to have metrics on this in /metrics.

OK, number of ledger entries is now tracked by metric in #4015. Moving this back to Current Sprint to continue working on size of DB.

I was confused: this is not related to Postbgres DB size but RAM size. This can be hard to do. If we want to get memory usage of Stellar-Core we'd need to execute system command and I don't think a breakdown per ledger entry is possible without Stellar-Core help (like exposing metrics).

Let's start with DB disk size per ledger so we can reliably extrapolate growth of storage needs.

I'm confused by this @bartekn.
It seems to me that
i) we know the current total RAM usage of captive core
ii) we know almost all of that RAM is holding current state
iii) we are ingesting this data so we must know what the breakdown of ledger entries is on the Horizon side
So why can't we answer this question? If RAM is 10GB and 3/4 of the ledger entries are claimable balances, then claimable balances are responsible for 7.5GB. What am I missing?

i) we know the current total RAM usage of captive core

We can't access this data from Go code directly (maybe using exec on a system command is a solution but I'm not sure - this is system dependent).

ii) we know almost all of that RAM is holding current state

Probably but there's also Overlay and some other components. I can agree that it's probably 90%+ but I don't know if it's 90% or 99%.

iii) we are ingesting this data so we must know what the breakdown of ledger entries is on the Horizon side
If (for example) RAM is 10GB and 3/4 of the ledger entries are claimable balances, then claimable balances are responsible for 7.5GB. What am I missing?

The problem here is the ledger entries are not equal in size. A data entry can be much smaller that claimable balance with a bunch of claimants. If the estimated values are OK then we can probably calculate it this way but we still don't have access to RAM usage of CC from Horizon code (see: i)).

Closing because better memory analysis requires exposing more metrics in Stellar-Core. However, given we probably need to move CC to disk such metric is probably no longer needed.


Bump dependencies

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


GCP TF Provider Old as dirt

Howdie! The current google cloud tf provider is set to 3.5 and presents a challenge for users who are using ARM based Macs. Terraform cli took a minute to adopt go 1.16, which supports mac ARM, and that delay cascaded to the GCP provider. Updating the GCP provider to 4.31 will allow for ARM based mac support.

Happy to take this one. I've got it all running in my own test bed.

@FrankYang0529 as the original author of the GCP work, any concerns here?

Yeah, I think it's good to upgrade gcp terraform provider. Version 3.5 was released almost 2 years ago. It's good to update to the latest version. Version 4.31 works fine on my laptop.

Feel free to assign this to me. I have a PR ready to go.


Make compatible with ES6 imports

Please use exports.default instead of setting module.exports to avoid this error when importing with ES6 Modules syntax:
export 'default' (imported as 'smoothscroll') was not found in 'smoothscroll-polyfill'

I'm no longer sure that this is a problem with the way exports is used. May be something with Babel/Webpack instead. Mystified....

I am setting modules: false, but I've found the solution:
I didn't realize that it was normal practice to exclude node_modules from Babel compilation. Now that I've set the include (or, alternatively, exclude) property in my Babel config, things are working as expected.


Avoid saving/getting "main" subdirectories of dependencies (at least in vendor/ mode)

Some packages have subdirectories that contain "main" packages; common cases are either providing examples of usage (see https://github.com/Sirupsen/logrus for instance), or command-line applications that use the library itself (see https://github.com/rasky/multigz). Notice that it's possible for these main packages to import third-party libraries, which might not be otherwise a dependency of the library itself. For instance, https://github.com/rasky/multigz/blob/master/cmd/multigz/multigz.go imports pflag and atime, both of which are not a dependency of multigz the library, but just of this specific main package.
When working in a pure Go 1.5 vendoring scenario, godep does not vendor these additions libraries (pflag/atime in the example) and I believe it is right in doing so, as they are not required for using the library themselves. Unfortunately, this breaks go test ./..., which exits with an error:
vendor/github.com/rasky/multigz/cmd/multigz/multigz.go:16:2: cannot find package "github.com/djherbis/atime" in any of:
	/home/ubuntu/.go_project/src/myproj/vendor/github.com/djherbis/atime (vendor tree)
	/usr/local/go/src/github.com/djherbis/atime (from $GOROOT)
	/home/ubuntu/.go_project/src/github.com/djherbis/atime (from $GOPATH)

I'm not even sure why go test cares about dependencies that main package; there are not even test files in that directory in the first place.
Anyway: do you think it would make sense for godep to avoid vendoring those main packages  altogether? They don't serve any purpose in the vendor directory after all, as they cannot be imported. Skipping them would be similar (conceptually) to avoid copying _test files, which godep does already.

It's because you specified ./... with go test. Which means you are running all of your tests and all tests inside the vendor/ directory. Go test needs to build the code first so you run into this error. In go 1.5+ you can't import main packages (you could previously), so I think it makes sense for us to not vendor them. I won't be able to look into this more until later in the week / early next week, but will do so.


Blacklist not working

Blacklist not working if blacklisted site accessed from address bar.

You could implement a custom RequestHandler and check the blacklisted URL in "OnBeforeBrowse".
https://github.com/cefsharp/CefSharp/blob/master/CefSharp.Example/Handlers/RequestHandler.cs

Thanks NovaStrip. I will work on that


docs(auth): clarify "Bearer token" terminology

Follow-up to #11300, where my wording could have been clearer
Motivation

Per https://github.com/argoproj/argo-workflows/discussions/11680 and some others, this is still a point of confusion with users
Modifications

be specific when referring to $ARGO_TOKEN, which includes "Bearer ", and the SA Secret, which is the part after "Bearer "
also fix the one doc that has Bearer $ARGO_TOKEN whereas the rest of the codebase has $ARGO_TOKEN with "Bearer " part of it

Verification

make docs passes
Related Notes

Note: the internal terminology is actually a bit off here. In the IETF standards spec, the "token" is referred to as the part after "Bearer "

The spec does not quite specify this in its terminology section, however, which means this is not as clear as it could be in the industry
See also another common industry reference's use of the terminology: https://swagger.io/docs/specification/authentication/bearer-authentication/
Internally though (which is more than just docs, it includes source code and tests as well), $ARGO_TOKEN always includes "Bearer "

so this change makes everything internally consistent. changing all internals would be very complex at this time

Bearer  was removed in #12014, which was reviewed and merged before this PR, despite being made ~1.5 months after it... 😕
That PR did not have any description, but this one does describe in detail that Bearer  is currently included in the $ARGO_TOKEN variable in the codebase, but probably shouldn't be according to industry terminology.
I merged master as a result, but this description and remaining changes are still relevant


feat(Topology/ContinuousMap/*): add some simp lemmas

This PR adds some easy lemmas about ContinuousMap and its relatives, intended to be used by simp.

Otherwise LGTM. Thanks!

Almost forgot:
bors d+

bors r+


New version: Genie v0.13.4

Registering package: Genie
Repository: https://github.com/GenieFramework/Genie.jl
Created by: @essenciary
Version: v0.13.4
Commit: 19f59fb568a17ba942838cbfc54f136551a80873
Reviewed by: @essenciary
Reference: https://github.com/GenieFramework/Genie.jl/commit/19f59fb568a17ba942838cbfc54f136551a80873#commitcomment-34744915

0.13.0? Or even 0.12.0?

@fredrikekre I made a request for 0.12 and 0.13 but they got lost in a sea of requests -- per my discussions with Stefan (https://github.com/JuliaRegistries/General/pull/2573).
I guess let's try to have the registered version the same as the one on the #master and then keep them in sync. All the other versions were pushed to #master in the past days and weeks.


How to visualize my own model?

Hi @alwayslj,  you can refer to basecam.py. If your model is not in torchvision.models, you may need to modify the find_layer function to suit your own model.

@haofanwang for a models like Faster RCNN and MaskRCNN which layer_name should be passed ??

Hi, @abhigoku10, you are free to select a feature layer, for example, the last conv layer. You can directly print the model and get the name of a specific layer.

@haofanwang does this principle work even for object detection architectures ?? there should be some modifications for this right

@abhigoku10 As far as I know, detection model usually has a classification branch. So you can use the middle feature as the activation map, and the classification score as weight. You can treat it as a self-defined model, the only thing you need to modify is to hook the activation output (this file).

@haofanwang thanks for the response I was able to hardcode the layer which i required and was able to get the activation map from it but to pass the classification score as weight how to do it since mine is detection/segmentation model I directly get the probability scores should I pass these values as weight

@abhigoku10  Yes, you can try to use the probability score as weight, but I'm not sure whether it works well.


Build wheels for all platforms in azure pipelines

Summary
Azure pipelines offers hosts on Linux, macOS, and Windows so just like
for our CI test jobs we can leverage it for building all our binaries
for pypi upload. Right now we use a combination of azure, travis, and
appveyor (as a fallback for azure) to build the binary wheels and upload
them to pypi. This commit simplifies all of that and configures things
so that we only need to run jobs on a single CI system.
Details and comments

This should not be merged until we get 0.9 out the door. Right before a release is not the time to experiment with our build automation.

Removing the on hold because 0.10.0 development has started, that being said we need to figure out the secret env variables in azure. The windows wheel build for 0.9.0 failed because twine say for 60min waiting for a password instead of seeing the env variable.


Fix /bulk-alerts/plan swagger response schema

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

Project coverage is 92.99%. Comparing base (ebd50b1) to head (8fe22e5).

Additional details and impacted files
@@            Coverage Diff            @@
##               main     #238   +/-   ##
=========================================
  Coverage     92.99%   92.99%
  Complexity      486      486
=========================================
  Files            81       81
  Lines          1656     1656
  Branches        103      103
=========================================
  Hits           1540     1540
  Misses           72       72
  Partials         44       44

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Decode main_data in decode_wal_record()

So, if I understand correctly, this doesn't have any user-visible effect yet, but adds infrastructure that will be needed later. Looks good as far as it goes.
I presume the next step then is to add parsing of commit/abort records drop relations, and SMGR_CREATE and SMGR_TRUNCATE records, so that the relation sizes can be tracked accurately in the page cache. Is that what you have in mind, too?

So, if I understand correctly, this doesn't have any user-visible effect yet, but adds infrastructure that will be needed later. Looks good as far as it goes.
I presume the next step then is to add parsing of commit/abort records drop relations, and SMGR_CREATE and SMGR_TRUNCATE records, so that the relation sizes can be tracked accurately in the page cache. Is that what you have in mind, too?

Right. I pushed some more.
It works on top of request_nonrel postgres branch and requests all catalog pages and pg_clog pages from pageserver.
To fix a race caused by walreceiver connection I added a flag - see 4188b73 .
For now, only pg_clog commit replay Is implemented and it seems to be enough to pass the existing test.
The next steps are abort handling, and other record types (subtrans? multixact? smgr?) that we will need. Now, that record parsing and replay infrastructure are ready, it should be easier to implement.


Error object v2

What this PR does:
Initial error object v2
This is still not in use, it is dead code. Once we get it in we will move from the "playing" package into parent "exceptions" package once we start using it.
This  PR is to get it into the main, next setps are:

start using it
start making it return the errors on the API

Which issue(s) this PR fixes:
Fixes #
Checklist

[*] Changes manually tested
[ ] Automated Tests added/updated
[ * Documentation added/updated
[ ] CLA Signed: DataStax CLA

follow up tickets, and there will soon be a PR that makes this usable that will move it from the "playing" package
https://github.com/stargate/data-api/issues/1374
https://github.com/stargate/data-api/issues/1375
merging


Upgrade postgres and postgis

Ignore branch name, we are upgrading to postgres 11 and postgis 3.0.

Coverage remained the same at 71.253% when pulling 755f5b111986626ad92636e705fdddc5d49b3466 on postgres12 into d7ca0cbb37d4269de8530286a70b19811335fc82 on development.


Bluetooth: mesh: Fix boolean return type

Boolean functions should return bool and not int.
Signed-off-by: Johan Hedberg<EMAIL_ADDRESS>

Not really sure why the zephyrbot hasn't changed its assignment behavior. Locally the get_maintainers.py script only returns the mesh entry for this patch.

Seems it cause more changes since the function is used as callback with different prototype

@alxelax yeah, I noticed the same. Looking into it. The bt_mesh_subnet_find() should be fixed since it does treat the callback return as a boolean, yet it's currently defined to return 'int'.

@trond-snekvik do you remember the justification of why commit eca01411528 uses int instead of bool for the callback return value?

What's worse, even though bt_mesh_subnet_find() treats the return as boolean, I found at least secure_beacon_send() in beacon.c that's actually returning 0 or a negative error value, which is obviously not right. So there's a much bigger issue here that needs fixing. It'd really be good to hear your thoughts on this @trond-snekvik

What's worse, even though bt_mesh_subnet_find() treats the return as boolean, I found at least secure_beacon_send() in beacon.c that's actually returning 0 or a negative error value, which is obviously not right. So there's a much bigger issue here that needs fixing.

This is the intended and documented behavior, and I believe secure_beacon_send was actually the first user. The name of the function is misleading though, and I agree it's probably better to change it to a boolean to avoid any further confusion.
For clarification, secure_beacon_send returns a non-zero value when we fail to send a beacon, so we can stop iterating, since this is caused by missing resources, and there's no point in continuing. if (-ENOMEM) is a passing condition, and the find function will exit as intended.
This is not a public API, so we can easily change it. Would you like to do this here @jhedberg, or would you prefer it if I made a separate PR to change all occurrences?

This is not a public API, so we can easily change it. Would you like to do this here @jhedberg, or would you prefer it if I made a separate PR to change all occurrences?

@trond-snekvik I think it might be better if you go and do the change, since you're more familiar with this code, thanks! I'll close this PR meanwhile.


Using nextra-theme-docs with NextJS 14 - TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string or an instance of Buffer or URL.

TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string or an instance of Buffer or URL. Received undefined
    at readdir (node:fs:1467:10)
    at go$readdir (D:\Projects\Office Projects\SSL Projects\nextjs_setup\node_modules\graceful-fs\graceful-fs.js:206:16)
    at readdir (D:\Projects\Office Projects\SSL Projects\nextjs_setup\node_modules\graceful-fs\graceful-fs.js:211:12)
    at node:internal/util:442:7
    at new Promise (<anonymous>)
    at readdir (node:internal/util:428:12)
    at D:\Projects\Office Projects\SSL Projects\nextjs_setup\node_modules\nextra\dist\index.js:205:25
    at Generator.next (<anonymous>) {
  code: 'ERR_INVALID_ARG_TYPE'

I also experienced this error. In the end, I switched to using pages directory and deleted my app directory and it worked. So it looks like an app directory issue.

app router is indeed not supported by nextra, it's planned for future version 4, see https://github.com/shuding/nextra/issues/2600

app router is indeed not supported by nextra v2 nor next version 3, it's planned for future version 4, see #2600

indeed, please move all discussions according support app router into https://github.com/shuding/nextra/issues/2023


Macports install

This is not an issue, it's just an information regarding installation. If you use macports instead of brew, the only thing you need to do before installing the module is:
sudo port install osxfuse +devel

You can do a pull-request adding this info to the readme :-)


Markwon jetpack compose

Markwon version: 4.6.2

Is this library haven't available for jetpack compose?

Hello @fendysaputro ,
nope.
To give more context - this library is not available for compose, but you can try using native android view, or a different library. See #348 for some info


[main] Upgrade to latest dependencies

Cron -knative-prow-robot
/cc knative/func-approvers
/assign knative/func-approvers
Produced by: knative-sandbox/knobots/actions/update-deps

@lance plz override the codecov.

/override codecov/project

/override codecov/project


7.16.2 release changelog

7.16.2

7.16.2 as default version.

PR
Author
Title

#1507
@jmlrt
[elasticsearch] remove usage of ELASTIC_USERNAME (#1506)

#1499
@elasticmachine
Bump version to 7.16.2-SNAPSHOT

jenkins test this please

jenkins test this please

@jmlrt @mgreau could you take a look, please? Something went wrong in Jenkins tests 👀

tests are failing because of #1443. Merging


kernel: Fix double-list-removal corruption case in timeout handling

This fixes #8669, and is distressingly subtle for a one-line patch:
The list iteration code in _handle_expired_timeouts() would remove the
timeout from our (temporary -- the dlist header is on the stack of our
calling function) list of expired timeouts before invoking the
handler.  But sys_dlist_remove() only fixes up the containing list
pointers, leaving garbage in the node.  If the action of that handler
is to re-add the timeout (which is very common!) then that will then
try to remove it AGAIN from the same list.
Even then, the common case is that the expired list contains only one
item, so the result is a perfectly valid empty list that affects
nothing.  But if you have more than one, you get a corrupt cycle in
the iteration list and things get weird.
As it happens, there's no value in trying to remove this timeout from
the temporary list at all.  Just iterate over it naturally.
Really, this design is fragile: we shouldn't be reusing the list nodes
in struct _timeout for this purpose and should figure out some other
mechanism.  But this fix should be good for now.

Codecov Report

Merging #9620 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #9620      +/-   ##
==========================================
- Coverage   52.15%   52.14%   -0.01%
==========================================
  Files         212      212
  Lines       25916    25913       -3
  Branches     5582     5582
==========================================
- Hits        13517    13513       -4
  Misses      10149    10149
- Partials     2250     2251       +1

Impacted Files
Coverage Δ

kernel/sys_clock.c
95.08% <ø> (-0.16%)
:arrow_down:

kernel/include/timeout_q.h
94.44% <0%> (-1.45%)
:arrow_down:

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 0be1875...2376a77. Read the comment docs.

Hey @andyross, is this covered with tests or do we need to add one?

Added #9627 to track the need for refactoring here.

new bug

@andyross @nashif when working on new shell #9362 we encountered an issue (hardfault) after rebase on master. I couldn't figure out the issue so i ended up rebasing back and finally found that https://github.com/zephyrproject-rtos/zephyr/pull/9620/commits/2376a770790c97fe89b6e87b8e0c8a53585d7b26 introduces this fault.
Example is fairly simple. It has two periodic instances of k_timer. When only one is running app is stable, enabling second periodic timer results in hardfault. Can you recommend something?

Could this actually be also the source of some faults we've been seing recently?

in my case it was usually hardfault pointing to sys_dlist_peek_prev_no_check or mpu fault (attempt to execute from ram address)

I've also observed this problem when I used: k_sleep(1); in my application. When I have replaced k_sleep(1); with k_busy_wait(1000); problem is gone.
My error msg is following:

@jarz-nordic does reverting this commit also fix it for you if you use k_sleep(1)?

@carlescufi @nordic-krch @andyross : Once I've reveted this commit the problem is gone.

@andyross as the original author of this patch, could you take a look at the reports here?


Mark all children as dirty if display changes

If we set display:none all children are set with layout sizes/values of 0. We need do mark all those children as dirty to force a relayout if we toggle the display on a higher parent node. This fixes #443

👍 Thanks! Sorry about that

This PR failed to import. Could you rebase & squash. That usually fixes things. Thanks!

here you are!

I took a slightly different approach to this when looking at the code again. You will see once this lands in a couple hours. I just made sure to set the cachedLayout property while handling the display:none case during layout.

Great I idea! I haven't thought of that 👍

@emilsjolander Much better! Great 👍


dependency-build should be run before lint

BUG REPORT :
Environment (plugin version, maven version, OS, ...): 5.3
When project has dependency in Chart.yaml below configuration doesn't work:
<plugin>
    <groupId>com.kiwigrid</groupId>
    <artifactId>helm-maven-plugin</artifactId>
    <version>5.3</version>
    <executions>
        <execution>
            <id>helm</id>
            <goals>
                <goal>init</goal>
                <goal>dependency-build</goal>
                <goal>lint</goal>
                <goal>package</goal>
                <goal>upload</goal>
            </goals>
        </execution>
    </executions>
    <configuration>
    </configuration>
</plugin>

because goal dependency-build is run after lint, so dependency is not resolved.
dependency-build is bind to prepare-package phase and lint is bind to test phase.
dependency-build should be bind to some earlier phase, maybe compile
This configuration is workaround:
<plugin>
    <groupId>com.kiwigrid</groupId>
    <artifactId>helm-maven-plugin</artifactId>
    <version>5.3</version>
    <executions>
        <execution>
            <id>helm-init</id>
            <phase>initialize</phase>
            <goals>
                <goal>init</goal>
            </goals>
        </execution>
        <execution>
            <id>helm-update</id>
            <phase>compile</phase>
            <goals>
                <goal>dependency-build</goal>
            </goals>
        </execution>
        <execution>
            <id>helm</id>
            <goals>
                <goal>lint</goal>
                <goal>package</goal>
                <goal>upload</goal>
            </goals>
        </execution>
    </executions>
    <configuration>
    </configuration>
</plugin>

Packaging with the Helm Lifecycle
I suspect that Packaging with the Helm Lifecycle also will not work for chart with dependency.
We have in plugin life cycle configuration:
<lifecycle>
    <id>default</id>
    <phases>
        <initialize>com.kiwigrid:helm-maven-plugin:init</initialize>
        <test>com.kiwigrid:helm-maven-plugin:lint</test>
        <package>com.kiwigrid:helm-maven-plugin:package</package>
        <deploy>com.kiwigrid:helm-maven-plugin:upload</deploy>
    </phases>
</lifecycle>

so goal dependency-build is not bind to any phase
What you expected to happen:
build pass

see #101

@thomschke - Your change resolve second case from my issue. Thanks.
Still we need change binding of dependency-build goal.

current binding:
<phases>
    <initialize>io.kokuwa.maven:helm-maven-plugin:init</initialize>
    <test>io.kokuwa.maven:helm-maven-plugin:lint</test>
    <prepare-package>io.kokuwa.maven:helm-maven-plugin:dependency-build</prepare-package>
    <package>io.kokuwa.maven:helm-maven-plugin:package</package>
    <deploy>io.kokuwa.maven:helm-maven-plugin:upload</deploy>
</phases>

what do you think to change to:
<phases>
    <initialize>io.kokuwa.maven:helm-maven-plugin:init</initialize>
    <generate-resources>io.kokuwa.maven:helm-maven-plugin:dependency-build</generate-resources>
    <test>io.kokuwa.maven:helm-maven-plugin:lint</test>
    <package>io.kokuwa.maven:helm-maven-plugin:package</package>
    <deploy>io.kokuwa.maven:helm-maven-plugin:upload</deploy>
</phases>

dependency-build will be executed in phase generate-resources before lint

Hi,
this would destroy a lot of our builds (generate-resources is too soon - we stage helm charts, incl. patches in target/ to values.yaml, etc. - in these phases).
I also believe such change would require major version bump.
BR,
Vojtech

Od: Slawomir Jaranowski @.***>
Odesláno: čtvrtek 24. března 2022 10:37:33
Komu: kokuwaio/helm-maven-plugin
Kopie: Subscribed
Předmět: Re: [kokuwaio/helm-maven-plugin] dependency-build should be run before lint (#81)
current binding:

io.kokuwa.maven:helm-maven-plugin:init
io.kokuwa.maven:helm-maven-plugin:lint
io.kokuwa.maven:helm-maven-plugin:dependency-build
io.kokuwa.maven:helm-maven-plugin:package
io.kokuwa.maven:helm-maven-plugin:upload

what do you think to change to:

io.kokuwa.maven:helm-maven-plugin:init
io.kokuwa.maven:helm-maven-plugin:dependency-build
io.kokuwa.maven:helm-maven-plugin:lint
io.kokuwa.maven:helm-maven-plugin:package
io.kokuwa.maven:helm-maven-plugin:upload

dependency-build will be executed in phase generate-resources before lint
—
Reply to this email directly, view it on GitHubhttps://github.com/kokuwaio/helm-maven-plugin/issues/81#issuecomment-1077425118, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFS5IR65DBYLPGP3FVPRKZDVBQZV3ANCNFSM4LERLKSQ.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

For me any phase will be ok if  dependency-build will be executed before lint.
So phase for lint can also be changed from test to something else.
Any other proposition?

This one issue is blocking for me for using helm-packaging.
As I see implementation is easy, the most difficult is to find proper binding for goals.
Order of goals should be:

init
dependency-build
lint
package
upload

Maybe process-classes will be ok for dependency-build it is after generate-resources
https://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html

Why process-classes and not process-resources? Any advantages or disadvantages? Both are after generate-resources.

process-resources is ok, is after generate-resources and before test

@slawekjaranowski can you provide a pr with an invoker test using goals helm:init, helm:dependency-build and helm:lint?

@sschnabe invoker tests added


Apply prettier to docs

(This PR is related to #2381)
Hi, I applied Prettier to the code blocks of documentation. Besides, it caught many syntax errors (missing commas, parentheses, fullwidth characters..)  and I have fixed them manually.
Also the Store type declaration in Glossary.md cannot be parsed by prettier. Sorry I'm not familiar with flow, should I add commas to it? Like below:
type Store = {
  dispatch: Dispatch,
  getState: () => State,
  subscribe: (listener: () => void) => () => void,
  replaceReducer: (reducer: Reducer) => void
}

Ho boy, that's a lot of changes...
Any chance you can share your tooling to do this? That actually sounds like a really cool project to run prettier on code blocks in a markdown doc. I'd encourage you to publish it!
As for the Glossary, I wouldn't worry about that. It's only a loose typing, not comprehensive. It's mainly there for explanatory reasons, so having perfect formatting isn't a requirement.
Since this is a lot of changes, some of which revert intentional style deviations, what if we break this up into more manageable chunks? I still publish the docs manually, so it wouldn't be published until everything is buttoned up and good to go. Maybe by folder?

Actually it's just a very rough and ugly script I wrote for this. But sure, I can spend some time to cleanup the code and publish it.
Did you mean I should break this PR to smaller ones so you can merge them progressively? Should I just open several PRs or is there any better way to do that? thanks.

Yeah, just several PRs will work. Should only be a handful of them. We've got thousands, so what are a few more? 😄

Closing in favor of the other PRs.


Configurable timeouts on creating workers node group.

I have issues
I'm submitting a...

[ ] bug report
[x] feature request
[ ] support request - read the FAQ first!
[ ] kudos, thank you, warm fuzzy

What is the current behavior?
Creating a new node group can take longer than an hour, which causes the node_groups.aws_eks_node_group.workers resource to timeout.
What's the expected behavior?
Timeout behaviour for node_groups.aws_eks_node_group.workers should be configurable!
Environment details

Affected module version: v12.2.0
OS: Linux
Terraform version: 0.12.x

This is a constant pain point with automating EKS clusters

should be fixed shortly

Fixed in #1552
Released in v17.9.0.


Update package.json - repository url

npm was parsing the value as
git://github.com/%3Anpm/npm-remote-ls.git
which is wrong

Redo of #15 after I pushed to the wrong branch :fearful:


Moved function descriptions to .cpp from .h

Moved the function descriptions in the .h file to the .cpp file and added a documentation header at the top of clean.cpp.  Also adjusted the styling of documentation on diffNaive.cpp

I like the changes, but maybe keep the function descriptions in both places?  That way a user can quickly look through the list of available functions in the header and figure out how to use them and what arguments are needed.

Also, this should be merged into develop, not master

Okay I'll make those changes. I was just following the styling guide which said put the comments right  where it's actually implemented, but I can add them back. Also sorry about making the push to master. I wasn't sure where to push to and I realized after that it should probably have been to develop.

Thats ok!  I've also clarified the style guide for that.