I got this "auto updater failed error" using 0.5.8 on ubuntu 16.04

Ops! ProtonMail Desktops auto updater failed. Check https://github.com/protonmail-desktop/application for the latest updates and please create an issue.
Anyone can help? Thanks!

Thanks for your report! Which kind of binary are you using?

@kontrollanten Thanks for the relpy! I install it via 64 bit deb package.

Okay. Is it like this every time you start the application? Are there any details provided in the dialog? If you try to open up the application from terminal (protonmail-desktop) do you get any information from there?

Yes, I have it everyone when starting the app. I only have a pop-up window showing the error message.
I tried start with terminal and got this in terminal
➜  ~ protonmail-desktop
Checking for update
Error: Error: ENOENT: no such file or directory, open '/opt/Protonmail Desktop/resources/app-update.yml'
at /opt/Protonmail Desktop/resources/app.asar/node_modules/electron-updater/src/AppUpdater.ts:362:27
at Generator.next ()
From previous event:
at AppImageUpdater.loadUpdateConfig (/opt/Protonmail Desktop/resources/app.asar/node_modules/electron-updater/out/AppUpdater.js:380:11)
at Lazy.AppUpdater.configOnDisk.Lazy [as creator] (/opt/Protonmail Desktop/resources/app.asar/node_modules/electron-updater/src/AppUpdater.ts:125:43)
at Lazy.get value [as value] (/opt/Protonmail Desktop/resources/app.asar/node_modules/lazy-val/src/main.ts:18:23)
at /opt/Protonmail Desktop/resources/app.asar/node_modules/electron-updater/src/AppUpdater.ts:273:33
at Generator.next ()
From previous event:
at AppImageUpdater.doCheckForUpdates (/opt/Protonmail Desktop/resources/app.asar/node_modules/electron-updater/out/AppUpdater.js:338:11)
at /opt/Protonmail Desktop/resources/app.asar/node_modules/electron-updater/src/AppUpdater.ts:256:25
at Generator.next ()
at runCallback (timers.js:672:20)
at tryOnImmediate (timers.js:645:5)
at processImmediate [as _immediateCallback] (timers.js:617:5)
From previous event:
at AppImageUpdater._checkForUpdates (/opt/Protonmail Desktop/resources/app.asar/node_modules/electron-updater/out/AppUpdater.js:292:11)
at AppImageUpdater.checkForUpdates (/opt/Protonmail Desktop/resources/app.asar/node_modules/electron-updater/src/AppUpdater.ts:205:35)
at App.app$1.on (/opt/Protonmail Desktop/resources/app.asar/app/src/auto-updater.js:10:17)
at emitTwo (events.js:111:20)
at App.emit (events.js:194:7)

According to https://github.com/electron-userland/electron-builder/issues/1138#issuecomment-336209761 it seems that only checkForUpdatesAndNotify (instead of currently used checkForUpdates) checks whether the current target has support for auto update.
It should be pretty easy to switch to checkForUpdatesAndNotify, but I need to read further to completely understand the flow when using that method.
Thanks for reporting! Hopefully we can fix this soon.

Great, thanks!

@sudoyang Sorry for the late response. We've now done a pre release where this should've been fixed. Can you try to download and see if it works? https://github.com/protonmail-desktop/application/releases/tag/v1.0.0-beta.1

@kontrollanten Thanks for the information! But it still seems that something went wrong...
Btw, I have updated my system to Ubuntu 18.10.
Here are details:
➜  ~ protonmail-desktop
(electron) 'app.makeSingleInstance(cb)' is deprecated. Use 'app.requestSingleInstanceLock() and app.on('second-instance', cb)' instead.
APPIMAGE env is not defined, current application is not an AppImage
Checking for update
Error: Error: ENOENT: no such file or directory, open '/opt/Protonmail Desktop/resources/app-update.yml'
at readFile (/opt/Protonmail Desktop/resources/app.asar/app/webpack:/node_modules/electron-updater/out/AppUpdater.js:625:1)
at Generator.next ()
From previous event:
at t.AppImageUpdater.loadUpdateConfig (/opt/Protonmail Desktop/resources/app.asar/app/webpack:/node_modules/electron-updater/out/AppUpdater.js:620:1)
at t.Lazy.loadUpdateConfig (/opt/Protonmail Desktop/resources/app.asar/app/webpack:/node_modules/electron-updater/out/AppUpdater.js:221:1)
at t.Lazy.creator [as value] (/opt/Protonmail Desktop/resources/app.asar/app/webpack:/node_modules/lazy-val/out/main.js:17:1)
at value (/opt/Protonmail Desktop/resources/app.asar/app/webpack:/node_modules/electron-updater/out/AppUpdater.js:503:1)
at Generator.next ()
at runCallback (timers.js:696:18)
at tryOnImmediate (timers.js:667:5)
at processImmediate (timers.js:649:5)
From previous event:
at t.AppImageUpdater.getUpdateInfoAndProvider (/opt/Protonmail Desktop/resources/app.asar/app/webpack:/node_modules/electron-updater/out/AppUpdater.js:499:1)
at getUpdateInfoAndProvider (/opt/Protonmail Desktop/resources/app.asar/app/webpack:/node_modules/electron-updater/out/AppUpdater.js:532:1)
at Generator.next ()
From previous event:
at t.AppImageUpdater.doCheckForUpdates (/opt/Protonmail Desktop/resources/app.asar/app/webpack:/node_modules/electron-updater/out/AppUpdater.js:529:1)
at t.AppImageUpdater.doCheckForUpdates [as checkForUpdates] (/opt/Protonmail Desktop/resources/app.asar/app/webpack:/node_modules/electron-updater/out/AppUpdater.js:361:1)
at App.checkForUpdates (/opt/Protonmail Desktop/resources/app.asar/app/webpack:/src/main/auto-updater.js:31:1)
at process._tickCallback (internal/process/next_tick.js:68:7)
Unhandled rejection Error: ENOENT: no such file or directory, open '/opt/Protonmail Desktop/resources/app-update.yml'
at readFile (/opt/Protonmail Desktop/resources/app.asar/app/webpack:/node_modules/electron-updater/out/AppUpdater.js:625:1)
at Generator.next ()
From previous event:
at t.AppImageUpdater.loadUpdateConfig (/opt/Protonmail Desktop/resources/app.asar/app/webpack:/node_modules/electron-updater/out/AppUpdater.js:620:1)
at t.Lazy.loadUpdateConfig (/opt/Protonmail Desktop/resources/app.asar/app/webpack:/node_modules/electron-updater/out/AppUpdater.js:221:1)
at t.Lazy.creator [as value] (/opt/Protonmail Desktop/resources/app.asar/app/webpack:/node_modules/lazy-val/out/main.js:17:1)
at value (/opt/Protonmail Desktop/resources/app.asar/app/webpack:/node_modules/electron-updater/out/AppUpdater.js:503:1)
at Generator.next ()
at runCallback (timers.js:696:18)
at tryOnImmediate (timers.js:667:5)
at processImmediate (timers.js:649:5)
From previous event:
at t.AppImageUpdater.getUpdateInfoAndProvider (/opt/Protonmail Desktop/resources/app.asar/app/webpack:/node_modules/electron-updater/out/AppUpdater.js:499:1)
at getUpdateInfoAndProvider (/opt/Protonmail Desktop/resources/app.asar/app/webpack:/node_modules/electron-updater/out/AppUpdater.js:532:1)
at Generator.next ()
From previous event:
at t.AppImageUpdater.doCheckForUpdates (/opt/Protonmail Desktop/resources/app.asar/app/webpack:/node_modules/electron-updater/out/AppUpdater.js:529:1)
at t.AppImageUpdater.doCheckForUpdates [as checkForUpdates] (/opt/Protonmail Desktop/resources/app.asar/app/webpack:/node_modules/electron-updater/out/AppUpdater.js:361:1)
at App.checkForUpdates (/opt/Protonmail Desktop/resources/app.asar/app/webpack:/src/main/auto-updater.js:31:1)
at process._tickCallback (internal/process/next_tick.js:68:7)

Thanks for your quick response! I hoped it was possible to check for new versions even if auto update isn't supported, but it seems that it's not. I'll dig a bit more into this before I remove it.

I get the feeling that electron-builder recommends to only build AppImage for Linux. I'm thinking about if we should just remove the other builds, but I'm not an experienced Linux user so I don't know if that's a bad thing. @sudoyang Is there any reason that you've choose deb instead of AppImage?

@kontrollanten In general, deb package follows the system setting better, for example, the system theme. In the case of protonmail-desktop, AppImage is equally good since it is mostly a webpage. So I do not mind to use AppImage instead.

@BeatPlus do you have any opinions about this?

AppImage seems to have some problem too. Or is it due to my system setting?
➜  Downloads chmod a+x protonmail-desktop-1.0.0-beta.1-x86_64.AppImage
➜  Downloads ./protonmail-desktop-1.0.0-beta.1-x86_64.AppImage
(electron) 'app.makeSingleInstance(cb)' is deprecated. Use 'app.requestSingleInstanceLock() and app.on('second-instance', cb)' instead.
Checking for update
Error: HttpError: 404 Not Found
"method: undefined url: https://github.com/protonmail-desktop/application/releases/download/v1.0.0-beta.2/latest-linux.yml\n\nPlease double check that your authentication token is correct. Due to security reasons actual status maybe not reported, but 404.\n"
Headers: {
"cache-control": [
"no-cache"
],
"content-encoding": [
"gzip"
],
"content-security-policy": [
"default-src 'none'; base-uri 'self'; connect-src 'self'; form-action 'self'; img-src 'self' data:; script-src 'self'; style-src 'unsafe-inline'"
],
"content-type": [
"text/plain; charset=utf-8"
],
"date": [
"Thu, 29 Nov 2018 00:16:31 GMT"
],
"expect-ct": [
"max-age=2592000, report-uri="https://api.github.com/_private/browser/errors\""
],
"server": [
"GitHub.com"
],
"set-cookie": [
"has_recent_activity=1; path=/; expires=Thu, 29 Nov 2018 01:16:31 -0000",
"logged_in=no; domain=.github.com; path=/; expires=Mon, 29 Nov 2038 00:16:31 -0000; secure; HttpOnly",
"_gh_sess=NGpKRHM4ZFRBcUZXRi9tMDVVaTZNTDFCbVQzNzZHaTMzc3VQMFVnb0lYYmRwVFpwY2ZKYTRDN1dacVB6VHBXQ0N6bDdjdUxOQmdlL1VlZFRnR2tqTVF3WTRsbUowVmg4cTY5WWVCc2x1R0NWdkVscThsdzFCZUJqY2ZNMVAxcTZUUHh3aHMyaCtIVmw3TDV0eE5FNmNkenAybFQ0YXZCelplYjJJVk9HTmVzK1dQTU5HL3laazAwRytsd2VqNE51aDNxeGpXbTkvT1gvQVIyTC9tdklaQT09LS0xaFpEd0hncjJqSTVUNDdMR01lWjhBPT0%3D--e77f5617e1d95142135cac709874c48580b69062; path=/; secure; HttpOnly"
],
"status": [
"404 Not Found"
],
"strict-transport-security": [
"max-age=31536000; includeSubdomains; preload"
],
"transfer-encoding": [
"chunked"
],
"vary": [
"X-PJAX"
],
"x-content-type-options": [
"nosniff"
],
"x-frame-options": [
"deny"
],
"x-github-request-id": [
"AA4E:2DB7:2BC550:41E116:5BFF2FDF"
],
"x-request-id": [
"7c359d01-84bc-4c7b-833c-3d7175ab24bc"
],
"x-xss-protection": [
"1; mode=block"
]
}
at d (/tmp/.mount_protonioN1Rx/resources/app.asar/app/webpack:/node_modules/builder-util-runtime/out/httpExecutor.js:102:1)
at t.ElectronHttpExecutor.createHttpError [as handleResponse] (/tmp/.mount_protonioN1Rx/resources/app.asar/app/webpack:/node_modules/builder-util-runtime/out/httpExecutor.js:185:1)
at ClientRequest.handleResponse (/tmp/.mount_protonioN1Rx/resources/app.asar/app/webpack:/node_modules/builder-util-runtime/out/httpExecutor.js:151:1)
at ClientRequest.emit (events.js:182:13)
at URLRequest.ClientRequest.urlRequest.on (/tmp/.mount_protonioN1Rx/resources/electron.asar/browser/api/net.js:207:12)
at URLRequest.emit (events.js:182:13)
From previous event:
at t.GitHubProvider.getLatestVersion (/tmp/.mount_protonioN1Rx/resources/app.asar/app/webpack:/node_modules/electron-updater/out/providers/GitHubProvider.js:105:1)
at getLatestVersion (/tmp/.mount_protonioN1Rx/resources/app.asar/app/webpack:/node_modules/electron-updater/out/AppUpdater.js:512:1)
at Generator.next ()
at runCallback (timers.js:696:18)
at tryOnImmediate (timers.js:667:5)
at processImmediate (timers.js:649:5)
From previous event:
at t.AppImageUpdater.getUpdateInfoAndProvider (/tmp/.mount_protonioN1Rx/resources/app.asar/app/webpack:/node_modules/electron-updater/out/AppUpdater.js:499:1)
at getUpdateInfoAndProvider (/tmp/.mount_protonioN1Rx/resources/app.asar/app/webpack:/node_modules/electron-updater/out/AppUpdater.js:532:1)
at Generator.next ()
From previous event:
at t.AppImageUpdater.doCheckForUpdates (/tmp/.mount_protonioN1Rx/resources/app.asar/app/webpack:/node_modules/electron-updater/out/AppUpdater.js:529:1)
at t.AppImageUpdater.doCheckForUpdates [as checkForUpdates] (/tmp/.mount_protonioN1Rx/resources/app.asar/app/webpack:/node_modules/electron-updater/out/AppUpdater.js:361:1)
at t.AppImageUpdater.checkForUpdates [as checkForUpdatesAndNotify] (/tmp/.mount_protonioN1Rx/resources/app.asar/app/webpack:/node_modules/electron-updater/out/AppUpdater.js:389:1)
at App.checkForUpdatesAndNotify (/tmp/.mount_protonioN1Rx/resources/app.asar/app/webpack:/src/main/auto-updater.js:8:1)
at App.emit (events.js:187:15)
(node:25451) UnhandledPromiseRejectionWarning: HttpError: 404 Not Found
"method: undefined url: https://github.com/protonmail-desktop/application/releases/download/v1.0.0-beta.2/latest-linux.yml\n\nPlease double check that your authentication token is correct. Due to security reasons actual status maybe not reported, but 404.\n"
Headers: {
"cache-control": [
"no-cache"
],
"content-encoding": [
"gzip"
],
"content-security-policy": [
"default-src 'none'; base-uri 'self'; connect-src 'self'; form-action 'self'; img-src 'self' data:; script-src 'self'; style-src 'unsafe-inline'"
],
"content-type": [
"text/plain; charset=utf-8"
],
"date": [
"Thu, 29 Nov 2018 00:16:31 GMT"
],
"expect-ct": [
"max-age=2592000, report-uri="https://api.github.com/_private/browser/errors\""
],
"server": [
"GitHub.com"
],
"set-cookie": [
"has_recent_activity=1; path=/; expires=Thu, 29 Nov 2018 01:16:31 -0000",
"logged_in=no; domain=.github.com; path=/; expires=Mon, 29 Nov 2038 00:16:31 -0000; secure; HttpOnly",
"_gh_sess=NGpKRHM4ZFRBcUZXRi9tMDVVaTZNTDFCbVQzNzZHaTMzc3VQMFVnb0lYYmRwVFpwY2ZKYTRDN1dacVB6VHBXQ0N6bDdjdUxOQmdlL1VlZFRnR2tqTVF3WTRsbUowVmg4cTY5WWVCc2x1R0NWdkVscThsdzFCZUJqY2ZNMVAxcTZUUHh3aHMyaCtIVmw3TDV0eE5FNmNkenAybFQ0YXZCelplYjJJVk9HTmVzK1dQTU5HL3laazAwRytsd2VqNE51aDNxeGpXbTkvT1gvQVIyTC9tdklaQT09LS0xaFpEd0hncjJqSTVUNDdMR01lWjhBPT0%3D--e77f5617e1d95142135cac709874c48580b69062; path=/; secure; HttpOnly"
],
"status": [
"404 Not Found"
],
"strict-transport-security": [
"max-age=31536000; includeSubdomains; preload"
],
"transfer-encoding": [
"chunked"
],
"vary": [
"X-PJAX"
],
"x-content-type-options": [
"nosniff"
],
"x-frame-options": [
"deny"
],
"x-github-request-id": [
"AA4E:2DB7:2BC550:41E116:5BFF2FDF"
],
"x-request-id": [
"7c359d01-84bc-4c7b-833c-3d7175ab24bc"
],
"x-xss-protection": [
"1; mode=block"
]
}
at d (/tmp/.mount_protonioN1Rx/resources/app.asar/app/webpack:/node_modules/builder-util-runtime/out/httpExecutor.js:102:1)
at t.ElectronHttpExecutor.createHttpError [as handleResponse] (/tmp/.mount_protonioN1Rx/resources/app.asar/app/webpack:/node_modules/builder-util-runtime/out/httpExecutor.js:185:1)
at ClientRequest.handleResponse (/tmp/.mount_protonioN1Rx/resources/app.asar/app/webpack:/node_modules/builder-util-runtime/out/httpExecutor.js:151:1)
at ClientRequest.emit (events.js:182:13)
at URLRequest.ClientRequest.urlRequest.on (/tmp/.mount_protonioN1Rx/resources/electron.asar/browser/api/net.js:207:12)
at URLRequest.emit (events.js:182:13)
From previous event:
at t.GitHubProvider.getLatestVersion (/tmp/.mount_protonioN1Rx/resources/app.asar/app/webpack:/node_modules/electron-updater/out/providers/GitHubProvider.js:105:1)
at getLatestVersion (/tmp/.mount_protonioN1Rx/resources/app.asar/app/webpack:/node_modules/electron-updater/out/AppUpdater.js:512:1)
at Generator.next ()
at runCallback (timers.js:696:18)
at tryOnImmediate (timers.js:667:5)
at processImmediate (timers.js:649:5)
From previous event:
at t.AppImageUpdater.getUpdateInfoAndProvider (/tmp/.mount_protonioN1Rx/resources/app.asar/app/webpack:/node_modules/electron-updater/out/AppUpdater.js:499:1)
at getUpdateInfoAndProvider (/tmp/.mount_protonioN1Rx/resources/app.asar/app/webpack:/node_modules/electron-updater/out/AppUpdater.js:532:1)
at Generator.next ()
From previous event:
at t.AppImageUpdater.doCheckForUpdates (/tmp/.mount_protonioN1Rx/resources/app.asar/app/webpack:/node_modules/electron-updater/out/AppUpdater.js:529:1)
at t.AppImageUpdater.doCheckForUpdates [as checkForUpdates] (/tmp/.mount_protonioN1Rx/resources/app.asar/app/webpack:/node_modules/electron-updater/out/AppUpdater.js:361:1)
at t.AppImageUpdater.checkForUpdates [as checkForUpdatesAndNotify] (/tmp/.mount_protonioN1Rx/resources/app.asar/app/webpack:/node_modules/electron-updater/out/AppUpdater.js:389:1)
at App.checkForUpdatesAndNotify (/tmp/.mount_protonioN1Rx/resources/app.asar/app/webpack:/src/main/auto-updater.js:8:1)
at App.emit (events.js:187:15)
(node:25451) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:25451) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Unhandled rejection HttpError: 404 Not Found
"method: undefined url: https://github.com/protonmail-desktop/application/releases/download/v1.0.0-beta.2/latest-linux.yml\n\nPlease double check that your authentication token is correct. Due to security reasons actual status maybe not reported, but 404.\n"
Headers: {
"cache-control": [
"no-cache"
],
"content-encoding": [
"gzip"
],
"content-security-policy": [
"default-src 'none'; base-uri 'self'; connect-src 'self'; form-action 'self'; img-src 'self' data:; script-src 'self'; style-src 'unsafe-inline'"
],
"content-type": [
"text/plain; charset=utf-8"
],
"date": [
"Thu, 29 Nov 2018 00:16:31 GMT"
],
"expect-ct": [
"max-age=2592000, report-uri="https://api.github.com/_private/browser/errors\""
],
"server": [
"GitHub.com"
],
"set-cookie": [
"has_recent_activity=1; path=/; expires=Thu, 29 Nov 2018 01:16:31 -0000",
"logged_in=no; domain=.github.com; path=/; expires=Mon, 29 Nov 2038 00:16:31 -0000; secure; HttpOnly",
"_gh_sess=NGpKRHM4ZFRBcUZXRi9tMDVVaTZNTDFCbVQzNzZHaTMzc3VQMFVnb0lYYmRwVFpwY2ZKYTRDN1dacVB6VHBXQ0N6bDdjdUxOQmdlL1VlZFRnR2tqTVF3WTRsbUowVmg4cTY5WWVCc2x1R0NWdkVscThsdzFCZUJqY2ZNMVAxcTZUUHh3aHMyaCtIVmw3TDV0eE5FNmNkenAybFQ0YXZCelplYjJJVk9HTmVzK1dQTU5HL3laazAwRytsd2VqNE51aDNxeGpXbTkvT1gvQVIyTC9tdklaQT09LS0xaFpEd0hncjJqSTVUNDdMR01lWjhBPT0%3D--e77f5617e1d95142135cac709874c48580b69062; path=/; secure; HttpOnly"
],
"status": [
"404 Not Found"
],
"strict-transport-security": [
"max-age=31536000; includeSubdomains; preload"
],
"transfer-encoding": [
"chunked"
],
"vary": [
"X-PJAX"
],
"x-content-type-options": [
"nosniff"
],
"x-frame-options": [
"deny"
],
"x-github-request-id": [
"AA4E:2DB7:2BC550:41E116:5BFF2FDF"
],
"x-request-id": [
"7c359d01-84bc-4c7b-833c-3d7175ab24bc"
],
"x-xss-protection": [
"1; mode=block"
]
}
at d (/tmp/.mount_protonioN1Rx/resources/app.asar/app/webpack:/node_modules/builder-util-runtime/out/httpExecutor.js:102:1)
at t.ElectronHttpExecutor.createHttpError [as handleResponse] (/tmp/.mount_protonioN1Rx/resources/app.asar/app/webpack:/node_modules/builder-util-runtime/out/httpExecutor.js:185:1)
at ClientRequest.handleResponse (/tmp/.mount_protonioN1Rx/resources/app.asar/app/webpack:/node_modules/builder-util-runtime/out/httpExecutor.js:151:1)
at ClientRequest.emit (events.js:182:13)
at URLRequest.ClientRequest.urlRequest.on (/tmp/.mount_protonioN1Rx/resources/electron.asar/browser/api/net.js:207:12)
at URLRequest.emit (events.js:182:13)
From previous event:
at t.GitHubProvider.getLatestVersion (/tmp/.mount_protonioN1Rx/resources/app.asar/app/webpack:/node_modules/electron-updater/out/providers/GitHubProvider.js:105:1)
at getLatestVersion (/tmp/.mount_protonioN1Rx/resources/app.asar/app/webpack:/node_modules/electron-updater/out/AppUpdater.js:512:1)
at Generator.next ()
at runCallback (timers.js:696:18)
at tryOnImmediate (timers.js:667:5)
at processImmediate (timers.js:649:5)
From previous event:
at t.AppImageUpdater.getUpdateInfoAndProvider (/tmp/.mount_protonioN1Rx/resources/app.asar/app/webpack:/node_modules/electron-updater/out/AppUpdater.js:499:1)
at getUpdateInfoAndProvider (/tmp/.mount_protonioN1Rx/resources/app.asar/app/webpack:/node_modules/electron-updater/out/AppUpdater.js:532:1)
at Generator.next ()
From previous event:
at t.AppImageUpdater.doCheckForUpdates (/tmp/.mount_protonioN1Rx/resources/app.asar/app/webpack:/node_modules/electron-updater/out/AppUpdater.js:529:1)
at t.AppImageUpdater.doCheckForUpdates [as checkForUpdates] (/tmp/.mount_protonioN1Rx/resources/app.asar/app/webpack:/node_modules/electron-updater/out/AppUpdater.js:361:1)
at t.AppImageUpdater.checkForUpdates [as checkForUpdatesAndNotify] (/tmp/.mount_protonioN1Rx/resources/app.asar/app/webpack:/node_modules/electron-updater/out/AppUpdater.js:389:1)
at App.checkForUpdatesAndNotify (/tmp/.mount_protonioN1Rx/resources/app.asar/app/webpack:/src/main/auto-updater.js:8:1)
at App.emit (events.js:187:15)

@sudoyang The problem with AppImage was due to a failed release from our side. If you try again it should work now.

Release 1.0.0-beta.3 should've solved the error message with the deb package.

It works both ways!


Inject router to the React 0.14 component

Hi, after update to the react 0.14 I can't use the router.
RegisterComponent.contextTypes = {
    router: React.PropTypes.func.isRequired
};

the this.context.router is null..
Know somebody how to inject correctly the router ?
Thanks Mila

duplicate of #1911 #1798 2064


Small irc parsing performance improvements

I still feel like coupled messages might error something, so I'll run this locally for a while before merging


fnm: 1.35.1 -> 1.36.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/Schniz/fnm/releases.
meta.description for fnm is: Fast and simple Node.js version manager
meta.homepage for fnm is: https://github.com/Schniz/fnm
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.36.0 with grep in /nix/store/h191pyqgq1nxky0z4zqqi09zyqgj2mh5-fnm-1.36.0
found 1.36.0 in filename of file in /nix/store/h191pyqgq1nxky0z4zqqi09zyqgj2mh5-fnm-1.36.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

fnm

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/h191pyqgq1nxky0z4zqqi09zyqgj2mh5-fnm-1.36.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A fnm https://github.com/r-ryantm/nixpkgs/archive/26e1bf519fdc6b1b914abb22dd2f3701396b3723.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/26e1bf519fdc6b1b914abb22dd2f3701396b3723#fnm

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/h191pyqgq1nxky0z4zqqi09zyqgj2mh5-fnm-1.36.0
ls -la /nix/store/h191pyqgq1nxky0z4zqqi09zyqgj2mh5-fnm-1.36.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

fnm

Maintainer pings
cc @kidonng for testing.

Result of nixpkgs-review pr 315376 run on aarch64-darwin 1

1 package built:

fnm


⚠ Bofrost.be has degraded performance

In 7d633a4, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1085 ms

Resolved: Bofrost.be performance has improved in b35b231.


config api-audiences along with SA issuer

I noticed that the API audiences were only being configured in the bootstrap phase to match the SA issuer, but during normal runtime, they would be rolled back to the default value.
Make the audiences always match the SA issuer.
/assign @marun

/hold
afaik bootstrap does need to set the audience to the custom issuer (if provided). Post-bootstrap similarly needs to synchronize the audience to the issuer (vs setting a static value), and investigation is suggested to ensure that is occurring.

/retest
/lgtm
@stlaz Maybe update the PR title and description? It doesn't seem to match the code.

based on my read, the default here was reasonable:
      --api-audiences strings                             Identifiers of the API. The service account token authenticator will validate that tokens used against the API are bound to at least one of these audiences. If the --service-account-issuer flag is configured and this flag is not, this field defaults to a single element list containing the issuer URL.

but this looks more explicit

/approve

/hold cancel

/retest

@stlaz The fact that the operator job has never passed against this PR suggests it's not a flake.
/hold

/hold cancel
/retest
aws-operator is super flakey


Transformer based NER model

Discussion 🗣
Hello all!
Continuing a discussion with @EasonC13 and @niallroche, I am opening this thread to keep track of the different approaches to fine-tune a transformer model (BERT or some variation of it like ALBERT) and its usage with Snorkel.

Context

@EasonC13 already did some work to generate a dataset with multiple NER labels using Keras here: https://github.com/accordproject/labs-cicero-classify/blob/dev/Practice/keras/keras_decompose_NER_model.ipynb
To replicate the above, we can:

Use pytorch by following the example of huggingface
Use Spacy version 3, which comes with a friendly api to work with transformer models and do easy preprocessing of the data

Detailed Description

If we go with spacy, Snorkel has compatibility with it out of the box. However, it is limited to version 2 and depending of our needs, we can do the pull request to facilitate the implementation spacy v3 in Snorkel. Although, we can go without having to do it.
Still, we can create a labelling function with our fine-tuned transformer model and use it as a custom labelling function while using Snorkel's implementation of spacy for the preprocessing needed.
Another thing to consider is the way to do inference, having in mind the high run-time cost in production of a transformer model, with the fine-tuned transformer model being used as a labelling function:

Do batch inference of the labels
Use a lightweight transformer model variation of BERT like ALBERT. huggingface has an example of how to implement it too

Let me fill up the previous context.
at 6/24, I think I am encounter a challenge.
It is easy to edit BERT NER model to have custom label. So the model can predict with one label, like “Eason” is a person.
However, I still looking on how to let NER model have “multi custom label”, I want the model to know, like, “Eason” is not only a person but also a party and a string. Because the NER example I see so far, BERT turn the label into a 128 dim label ids, not like classic classification model is the one-hot encoding.
Even-though the model at the pytorch print said it is a n dim output, the actual input data seems not like this.
So I turn to Keras because I am familiar with it.
6/25
I successfully change the model output as I wish to categorial mode via Keras.
https://github.com/accordproject/labs-cicero-classify/blob/dev/Practice/keras/keras_decompose_NER_model.ipynb
I first reference this tutorial.
https://apoorvnandan.github.io/2020/08/02/bert-ner/
Then I change the classical NER model's loss to CategoricalCrossentropy and transform train_y into the one-hot encoding format.
Now the model is training! I can't wait to validate it and create a multi_label dataset to verify this method will work or not.
I think I can do it since I first learn Deep learning via Keras. Now I need to know how to do the same thing via PyTorch. I will start reading the document on it.
If you have any clue about how to do the same setting on PyTorch, please let me know. I hope I can build one in PyTorch because Keras is CUDA version-specific and eats all my memory. So it is not a good tool for long-term production use.
And feel free to comment about this approach (and the code).
6/26
I'm keep learning and looking on how to implement one on PyTorch.

Hello @EasonC13
Using the same entity for multiple labels is something that I think may not be possible to do within the same model in BERT or at least I am not fully aware of clean ways to do it. However, you can try some hack approaches like:

Have one label being "person+party+string" and distinguish it from label "person" when training the model
Train multiple NER models for different sets of labels. So, one model would tag Eason as person, the other one would tag it as party and the third one would tag it as string

If you go for the second approach, you can try using:

Lightweight versions of BERT like ALBERT
Do adapter tuning

If yo do Adapter tuning, it means that you would have to:

Train a model for each set of labels that identify "Eason":

One model for a group of labels where "Eason" is a PERSON
One model for a group of labels where "Eason" is a STRING

Each individual model keeps BERT's pretrained weights frozen, which means "Adapter-based tuning requires training two orders of magnitude fewer parameters to fine-tuning, while attaining similar performance".
Each individual model or adapter can be combined using adapter fusion:

"The AdapterFusion component  takes  as  input  the  representations  of  multiple adapters trained on different tasks and learns a parameterized mixer of the encoded information.", which means sharing information across multiple tasks.

-- Check the documentation about how to do adapter tuning and use adapter fusion: https://docs.adapterhub.ml/

Hi @walter-hernandez , I think I can use N adapter for N labels, each adapter specialist for one datatype. So when user correct, it is easy to re-train them without interrupt others.
Now I'm trying to implement it.
While it seems adapter only can train with same output label. So it is a little challenge to set up an effective training pipeline, or I should train N times for N adapter. Now I have come up with a plan to done effective training. That is, train all wanted adapter together with one label (ex: 1), no matter it is the correct label or not, but only do gradient descent on those with correct label, then train the opposite label (ex: 0) and do gradient descent on others.
While I first will build a prototype which have N adapter for N labels, on basic NER dataset, to prove adapter will work for this job.
What do you think about it?

@EasonC13 how did this go?


Please provide help and user guide how to change default model

Hi @Simatwa ,
Thank you so much for developing a great tool.
can you please add some more help on how to change the default model from CLI ?
I am mainly interested in the gpt4free usage.

Thanks for raising this concern. It will be updated asap. Meanwhile, utilize the flag -p or --provider followed by the provider name.
For instance :
pytgpt interactive -p Aura

Note : The providers are auto-detected whether they're gf4-based or tgpt-based and then handled accordingly.

List working g4f-based working providers:
pytgpt gpt4free list providers --working

For the case of tgpt-based ones, they'll be shown in the <generate/interactive> help info along with the --provider details.
pytgpt <generate/interactive> --help

It is very much possible to specify the model name, thanks to the --model flag which employs try-error mechanism to check it's validity at response generation . However, different providers support different models so  it is advisable to check the validity status of the model in relation to that particular provider.
Perhaps you might find the following command useful.
pytgpt gpt4free list models

For the case of AutoGPT, I'm yet to dig deep into it.


Crash in Release mode

I was experimenting with mosaic on twitter-small graph and found that both "generate_graph.py" and "run_mosaic.py" crash in release mode. Below is the error message from "./generate_graph.py --dataset twitter-small --binary --in-memory":
[SG-LOG] Partitioning time: 4.042466
[SG-LOG] Shutdown PartitionManager 0
[SG-ERR:threadMain:121] Fail to pin a thread: Invalid argument
XXX [threadMain:122] error exit with 1
stack trace for /mnt/D/di/mosaic/build/Release-x86_64/tools/grc/grc-in-memory pid=7292
Could not attach to process.  If your uid matches the uid of the target
process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try
again as the root user.  For more details, see /etc/sysctl.d/10-ptrace.conf
ptrace: Operation not permitted.
/mnt/D/di/mosaic/src/tools/scripts/7292: No such file or directory.
No thread selected
No stack.
grc-in-memory: /mnt/D/di/mosaic/src/lib/util/util.cc:25: void scalable_graphs::util::__die(int, const char*, int): Assertion `0' failed.
Command terminated by signal 6
Attaching it to gdb revealed it was crashing in
#5  0x00005555555915c9 in scalable_graphs::util::Runnable::threadMain (arg=0x5555557b5250) at /mnt/D/di/mosaic/src/lib/util/runnable.cc:122
122	        die(1);
(gdb) list
117	    cpu_set_t* cpuset = &runnable->cpuset_;
118	    if (CPU_COUNT(cpuset)) {
119	      int rc = sched_setaffinity(0, sizeof(*cpuset), cpuset);
120	      if (rc) {
121	        sg_err("Fail to pin a thread: %s\n", strerror(errno));
122	        die(1);
123	      }
124	    }
125	    runnable->run();
126	  }
Below is the error message from "./run_mosaic.py --dataset twitter-small --algorithm pagerank --max-iteration 20 --gdb":
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[SG-LOG] Running with 1334392 vertices, 94 tiles, 32-bit-index: true
[SG-LOG] selective scheduling false
[SG-LOG] Started edge processor 0.
[SG-LOG] selective scheduling false
[SG-LOG] Started edge processor 1.
[SG-LOG] Started all edge processors.
[SG-LOG] Intialization done
Program received signal SIGSEGV, Segmentation fault.
scalable_graphs::core::getGlobalToOrigIDFileName[abi:cxx11](config_t const&) () at /mnt/D/di/mosaic/src/lib/core/util.cc:93
93	    return getGlobalToOrigIDFileName(config.path_to_globals);
Interestingly they both finished without crashing in debug mode.

Regarding the crash when executing generate_graph.py, the error message points to sched_setaffinity() returning an EINVAL return code. The internet suggests this might happen if some of the CPUs of your system have been disabled (see https://stackoverflow.com/questions/53881781/why-does-sched-setaffinity-work-on-one-system-fails-on-another). Enabling all CPUs is likely to fix that? The crash in run_mosaic.py is likely a result of the previous graph generation not completing correctly.


Refactor molfilefactory to actually be a factory

Description
Provide a brief description of the PR's purpose here.
Fixes #681
Make the molfilefactory actually be a factory like the other factories and removes semi-redundant from_file method.
Developers certificate of origin

[X] I certify that this contribution is covered by the MIT license as defined in our LICENSE and adheres to the Developer Certificate of Origin.

Codecov Report

Merging #737 (31486bc) into main (bfa7656) will increase coverage by 27.15%.
The diff coverage is n/a.

Additional details and impacted files

@JenkeScheen @ijpulidos @chrisiacovella @apayne97 @kaminow can I grab a review from one of you please?


${workspaceRoot} in launch.json cannot contain a space

Hi,
I noticed today that if I try and debug an, application that is in a path that contains a space, it will fail. The reason is that as soon as it contains a space, everything to the right of the space is trimmed from the path, leaving it to execute on the wrong path
For example I've put a simple repo application in c:\test app and when I attempt to debug it, this what will be in the debug output
No executable found matching command "dotnet-c:\test"
The program 'c:\test app\bin\Debug\netcoreapp1.0\test.dll' has exited with code 1 (0x00000001).

remove the space and it works just fine.
This is what I have in my launch.json for a simple console app
{
    "name": ".NET Core Launch (console)",
    "type": "coreclr",
    "request": "launch",
    "preLaunchTask": "build",
    "program": "${workspaceRoot}/bin/Debug/netcoreapp1.0/test.dll",
    "args": [],
    "cwd": "${workspaceRoot}",
    "stopAtEntry": false
},

I'm running Visual Studio Code - Insiders build with omnisharp-vscode v1.0.1-rc2
$ dotnet --info
.NET Command Line Tools (1.0.0-rc2-002376)

Product Information:
 Version:     1.0.0-rc2-002376
 Commit Sha:  9d71cce383

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.10586
 OS Platform: Windows
 RID:         win10-x64

I fixed this in post rc2 release builds.

Any deadline on the next release?

Unfortunately it is outside of our control - there are a whole bunch of different projects (CoreCLR, CoreFX, .NET CLI, ASP.NET, VS Tooling, us, and the list goes on and on) that all need to go out together for rc2. Because there are so many projects, and because there are so many changes between rc1 and rc2 so none of the projects are at all independent, it means that the C# extension team doesn't get to decide when we ship, and it also means that the C# extension needs to avoid churn to make sure we aren't risking the overall release.
The good news is that ~1-2 weeks after rc2 ships, we plan to ship again to fix all the issues we weren't able to fix in the rc2 release. The fix for this will ship then.

I think I might just be confusing things here, I was thinking that this was a fix in omnisharp-vscode that puts our releases every now and then. But is this fix in the VSCode debugger package that is downloaded extra the first time you open a .cs file?

Correct.


Unbalanced calls to begin/end appearance transitions.

Currently I have an application where the button that is triggered from a react view controller which pushes a modal view for Healthkit permissions.
I get the following "warning" nothing bad happens but might want to have a way to properly tell containing view that something is above to pushed on top of you modally with out getting this:
Unbalanced calls to begin/end appearance transitions for <UIViewController: 0x154d6e7a0>.

Thanks.

@myusuf3 - this seems like an iOS related question, not so much React Native - perhaps give StackOverflow a try :smile:

@brentvatne I totally disagree. This isn't something I am doing incorrectly. Correct me if i am wrong, but react isn't able to handle modals appearing on top of it unexpectedly granted the push is coming from some native code.

@myusuf3 - sorry I don't quite understand the issue because there is not a code example. If you can provide one that would help a lot and then I would be happy to reopen :smile:


Add missing 'we've moved' callout

Overview
Changes

Fixes: # .

Verification

This optional section is a place where you can detail the specific type of verification
you want from reviewers. For example, if you want reviewers to checkout the PR locally
and validate the functionality of specific scenarios, provide instructions
on the specific scenarios and what you want verified.
If there are specific areas of concern or question feel free to highlight them here so
that reviewers can watch out for those issues.
As a reviewer, it is possible to check out this change locally by using the following
commands (substituting {PR_ID} with the ID of this pull request):
git fetch origin pull/{PR_ID}/head:name_of_local_branch
git checkout name_of_local_branch

@hferrone Are you looking to get these headers into the github.io pages or just the GitHub repo?

@keveleigh Into the github.io pages :)


[DOC-3081] Apply standards to SMP getting started

Apply standards to SMP getting started
What Type of PR is This?

[ ] Issue
[ ] Feature
[x] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[x] Tested Locally
[ ] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


Add "Refresh" button for updating PR data without reloading page

This patch adds a "Refresh" button to the header which reloads the PR data without refreshing the page or navigating away from the current view:

While a refresh is in progress, the button is disabled:

Thanks to @tdas for suggesting this feature.

I added an auto-refresh timer which refreshes the data every 5 minutes.

Going to merge this now.  It might be fun to add animated transitions or something later to make it more obvious when things are updating.


Add multiple functions to merge/concatenate effects and/or its outputs

Enhance the ways (array/closure) to merge/concatenate effects and/or its outputs and add instance functions for chaining.
with array/closure, we can merge different effects/outputs by the conditions:
let effect: Effect<Int, Never> = Effect.merge {
  if condition {
    return [Effect(value: 1)]
  } else {
    return [Effect(value: 1), Effect(value: 2)]
  }
}

merge the effects with its outputs:
enum ExampleAction {
    case action1
    case action2
    case action3
  }

// Instead of:
let mergedEffect: Effect<ExampleAction, Never> = Effect.merge(
  Effect(value: .action1),
  Effect(value: .action2),
  Effect(value: .action3),
)

// We can:
let mergedEffectWithActions: Effect<ExampleAction, Never> = Effect.mergeOutputs(.action1, .action2, .action3)

and we can chain the effects/outputs in different ways:
let mergedEffect: Effect<ExampleAction, Never> = Effect.mergeOutputs(.action1, .action2).concatenateOutputs(.action3)

Hi @marslin1220! We appreciate the time you took to PR these changes and share.
We may not be doing enough to communicate this to contributors, but we've been working to minimize surface area in the core library, and also to minimize the Combine publisher-forward interfaces of the Effect type, so while these helpers could definitely be handy, they unfortunately add to both of these surface areas. With our recent concurrency release, we think folks should mostly only use Effect.task, Effect.run, Effect.fireAndForget, and Effect.none.
The Combine integration isn't going away right away, though, so I think it's fine to share these helpers as a companion package/library if you choose to open source them as one, or if you'd like to share them in the GitHub discussion forums, I'm sure some folks may be interested in using them.
Thanks again! And sorry that the helpers aren't right for the core library at this time!

Hi @stephencelis , thank you for your response and I agree with you to separate the core library and the helpers.
I will create another repo to share those helpers and share the repo link in this PR. 🤝


Feature Request: Autocrafting Blocking

It would be most useful to have a feature which would allow only one item in a crafting recipe to be crafted at a time. This would greatly simplify automation of in-world crafting and complex crafting recipes involving multiple machines.
When this feature was first added to RS, there was much rejoicing among my friends an me. The removal of this feature is preventing me from upgrading Refined Storage in my modpacks, because it will break too much existing automation.
Please?

This feature has been removed for a reason.


some error occurred after loading pretrained model MeshGraphormer/models/hrnet/hrnetv2_w64_imagenet_pretrained.pth

=> loading pretrained model MeshGraphormer/models/hrnet/hrnetv2_w64_imagenet_pretrained.pth
WARNING: All log messages before absl::InitializeLog() is called are written to STDERR
I0000 00:00:1715066596.992713  616354 task_runner.cc:85] GPU suport is not available: INTERNAL: ; RET_CHECK failure (mediapipe/gpu/gl_context_egl.cc:84) egl_initializedUnable to initialize EGL

Have you solved it? I'm facing the same issue and looking forward to your reply

Hi, do you have a more complete error log?


can't add admin user into database

Laravel: v7.28.1
Voyager: v1.4
PHP: 7.4.0
Database: MySQL 8.0

after install voyager without dummy , I run php artisan voyager:admin<EMAIL_ADDRESS>--create throw a error:
Enter the admin name:

Aborted.
Screenshots

This is a bug in PHP 7.4.0 on Windows so you either update to 7.4.1 or downgrade to 7.3.
There is nothing we can change in Voyager to make it work.
For more info
https://github.com/laravel/framework/issues/31859
https://bugs.php.net/bug.php?id=78883


WEB: "flutter run -d chrome" crashes when using package with protobuf in dependencies

I am playing with flutter web (master channel version 1.10.7-pre.70) in vs code.
When my application app_io is using package app_main, which has protobuf reference in app_main/pubspec.yaml:
dependencies:
  protobuf:

than flutter run -d chrome crashes.
It is curious, that:

protobuf is not used in app_main package code, just referenced in app_main/pubspec.yaml
when I reference (or even use protobuf code) in app_io application, all is OK.

You can evoke an error in https://github.com/PavelPZ/protobuf_problem

uncomment protobuf: line in https://github.com/PavelPZ/protobuf_problem/blob/master/app_main/pubspec.yaml
run flutter run -d chrome again.
following error raise:

flutter run -d chrome
Launching lib\main.dart on Chrome in debug mode...
Unhandled exception:
NoSuchMethodError: The getter 'name' was called on null.
Receiver: null
Tried calling: name
#0      Object.noSuchMethod (dart:core-patch/object_patch.dart:51:5)
#1      _packageBuildConfig.<anonymous closure> (package:build_runner_core/src/package_graph/target_graph.dart:85:61)
#2      MappedListIterable.elementAt (dart:_internal/iterable.dart:415:29)
#3      ListIterable.toList (dart:_internal/iterable.dart:219:19)
#4      new BuildConfig.useDefault (package:build_config/src/build_config.dart:90:34)
#5      BuildConfig.fromBuildConfigDir (package:build_config/src/build_config.dart:52:26)
<asynchronous suspension>
#6      _packageBuildConfig (package:build_runner_core/src/package_graph/target_graph.dart:90:30)
<asynchronous suspension>
#7      TargetGraph.forPackageGraph (package:build_runner_core/src/package_graph/target_graph.dart:37:17)
<asynchronous suspension>
#8      BuildOptions.create (package:build_runner_core/src/generate/options.dart:107:39)
<asynchronous suspension>
#9      BuildRunnerDaemonBuilder.create (package:build_runner/src/daemon/daemon_builder.dart:182:43)
<asynchronous suspension>
#10     DaemonCommand.run (package:build_runner/src/entrypoint/daemon.dart:83:48)
<asynchronous suspension>
#11     CommandRunner.runCommand (package:args/command_runner.dart:197:27)
<asynchronous suspension>
#12     CommandRunner.run.<anonymous closure> (package:args/command_runner.dart:112:25)
#13     new Future.sync (dart:async/future.dart:224:31)
#14     CommandRunner.run (package:args/command_runner.dart:112:14)
#15     run (package:build_runner/src/entrypoint/run.dart:24:31)
<asynchronous suspension>
#16     main (package:flutter_tools/src/build_runner/build_script.dart:200:28)
<asynchronous suspension>
#17     _startIsolate.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:301:32)
#18     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:172:12)
Building application for the web...                                24.7s
Failed to build application for the web.

Thanks for reporting. It's an interesting observation. But you are not blocked, right?

I'm not able to reproduce your example on the latest master. Please include flutter doctor -v. Also ensure that you've run flutter packages get after adding the new dependency, or try running flutter clean

Of course, I ran all things you suggest.
Basically, my github example is result of 3 days of investigation of why is my large project build crash.
Now, if I add protobuf reference to app_io/pubspec.yaml too, it helps. When I remove it (and delete protobuf record from pubspec.lock and from .packages files) error raises again.
I suspect that the error is related to protobuf version. In one of my attempts I solved version collision between protobuf-0.14.4 x protobuf-0.14.3 x protobuf-0.13.?.
Attached is flutter doctor result :
PS C:\protobuf_problem\app_io> flutter doctor -v
[√] Flutter (Channel master, v1.10.7-pre.70, on Microsoft Windows [Version 10.0.17134.1006], locale en-US)
    • Flutter version 1.10.7-pre.70 at c:\flutter
    • Framework revision 25f2399ba3 (25 hours ago), 2019-09-28 00:22:37 -0700
    • Engine revision 5b952f286f
    • Dart version 2.6.0 (build 2.6.0-dev.3.0 6ff8d2199d)

[!] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at C:\Users\pzika\AppData\Local\Android\sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    X No Java Development Kit (JDK) found; You must have the environment variable JAVA_HOME set and the java binary in your      PATH. You can download the JDK from https://www.oracle.com/technetwork/java/javase/downloads/.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

[√] Visual Studio - develop for Windows (Visual Studio Community 2019 16.4.0 Preview 1.0)
    • Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2019\Preview
    • Visual Studio Community 2019 version 16.4.29319.158
    • The current Visual Studio installation is a pre-release version. It may not be supported by Flutter yet.

[!] Android Studio (version 3.5)
    • Android Studio at C:\Program Files\Android\Android Studio
    X Flutter plugin not installed; this adds Flutter specific functionality.
    X Dart plugin not installed; this adds Dart specific functionality.
    X Unable to determine bundled Java version.
    • Try updating or re-installing Android Studio.

[√] VS Code (version 1.38.1)
    • VS Code at C:\Users\pzika\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.4.1

[√] Connected device (3 available)
    • Windows • Windows • windows-x64    • Microsoft Windows [Version 10.0.17134.1006]
    • Chrome  • chrome  • web-javascript • Google Chrome 77.0.3865.90
    • Server  • web     • web-javascript • Flutter Tools

! Doctor found issues in 2 categories.

If it really depends on the version, best to raise an issue at the protobuf repository too and reference this issue.

This was reported again here: https://github.com/flutter/flutter/issues/42218. We need to look into it. Adding to near-term goals.

Problem raised again in another context. In this case I cannot find workaround.
I suspect that problem is related with importing packages, which has more that single version in c:\Users<username>\AppData\Roaming\Pub\Cache\hosted\pub.dartlang.org\
I have to stop development web version of my app.

Neither @PavelPZ's nor @decker deckerst sample apps reproduce the issue for me on a Linux computer and on a Mac computer as of dd43da71febaafc58852000a61a6bc1ac4fb57ef. I did see the CLI get stuck on "Attempting to connect to browser instance" but that seems unrelated.
What else am I missing?

I have tried to add -v to flutter test --platform chrome and found this notice:
Unable to read module information for package:convert, make sure you have a dependency on it in your pubspec

It is curious that:

test for package_a (with missing package:convert) runs well and does not show any error
test build for package_b (which uses package_a) crashes (and does not show any error)
adding -v shows info about missing dependency

I apologize for reporting it in this issue.
Console:
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Try the new cross-platform PowerShell https://aka.ms/pscore6

PS C:\wikibulary\dart\utils\utils_auth> flutter test --platform chrome -v
[  +52 ms] executing: [c:\flutter\] git -c log.showSignature=false log -n 1 --pretty=format:%H
[ +158 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[   +4 ms] 9423a01204ba9abf2e4b26fda3d5ef06d6897ef9
[   +1 ms] executing: [c:\flutter\] git describe --match v*.*.* --first-parent --long --tags
[ +185 ms] Exit code 0 from: git describe --match v*.*.* --first-parent --long --tags
[   +1 ms] v1.10.14-95-g9423a0120
[  +24 ms] executing: [c:\flutter\] git rev-parse --abbrev-ref --symbolic @{u}
[ +103 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[   +1 ms] origin/master
[        ] executing: [c:\flutter\] git ls-remote --get-url origin
[  +96 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[ +206 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[  +25 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[+16175 ms] Starting daemon...
[ +384 ms] Initializing inputs
[ +619 ms] Building new asset graph...
[+2767 ms] Building new asset graph completed, took 2.8s

[   +1 ms] Checking for unexpected pre-existing outputs....
[   +1 ms] Checking for unexpected pre-existing outputs. completed, took 2ms

[  +20 ms] Initializing inputs
[   +8 ms] Building new asset graph...
[   +1 ms] Building new asset graph completed, took 2.8s
[   +1 ms] Checking for unexpected pre-existing outputs....
[   +1 ms] Checking for unexpected pre-existing outputs. completed, took 2ms
[+1869 ms] About to build [web, test]...
[  +24 ms] Running build...
[ +311 ms] building for target test/auth_test.dart.browser_test.dart
[+1037 ms] 1.4s elapsed, 87/105 actions completed.
[+1095 ms] 2.5s elapsed, 219/223 actions completed.
[+1004 ms] 3.5s elapsed, 390/405 actions completed.
[+1001 ms] 4.5s elapsed, 557/565 actions completed.
[+1098 ms] 5.6s elapsed, 713/733 actions completed.
[+1099 ms] 6.7s elapsed, 861/877 actions completed.
[+1095 ms] 7.8s elapsed, 1010/1014 actions completed.
[+1017 ms] 8.8s elapsed, 1148/1165 actions completed.
[+1083 ms] 9.9s elapsed, 1282/1287 actions completed.
[+1098 ms] 11.0s elapsed, 1441/1445 actions completed.
[+1001 ms] 12.0s elapsed, 1529/1531 actions completed.
[  +63 ms] Unable to read module information for package:convert, make sure you have a dependency on it in your pubspec.
[  +72 ms] Unable to read module information for package:convert, make sure you have a dependency on it in your pubspec.
[ +454 ms] Unable to read module information for package:convert, make sure you have a dependency on it in your pubspec.
[ +396 ms] Unable to find modules for some sources, this is usually the result of either a
                    bad import, a missing dependency in a package (or possibly a dev_dependency
                    needs to move to a real dependency), or a build failure (if importing a
                    generated file).

                    Please check the following imports:

[ +296 ms] AssetNotFoundException: utils|lib/guid_small.ddc.dill
[  +44 ms] #0      ScratchSpace.ensureAssets.<anonymous closure> (package:scratch_space/src/scratch_space.dart:94:20)
           <asynchronous suspension>
           #1      MappedIterator.moveNext (dart:_internal/iterable.dart:393:18)
           #2      new List.from (dart:core-patch/array_patch.dart:33:29)
           #3      Iterable.toList (dart:core/iterable.dart:398:5)
           #4      ScratchSpace.ensureAssets (package:scratch_space/src/scratch_space.dart:116:8)
           #5      _createDevCompilerModule.<anonymous closure> (package:build_web_compilers/src/dev_compiler_builder.dart:121:42)
           #6      _NoOpBuilderActionTracker.trackStage (package:build_runner_core/src/generate/performance_tracker.dart:300:15)
           #7      BuildStepImpl.trackStage (package:build/src/builder/build_step_impl.dart:146:21)
           #8      _createDevCompilerModule (package:build_web_compilers/src/dev_compiler_builder.dart:120:19)
           #9      _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:71:64)
           #10     _rootRunUnary (dart:async/zone.dart:1132:38)
           #11     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
           #12     _FutureListener.handleValue (dart:async/future_impl.dart:137:18)
           #13     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:678:45)
           #14     Future._propagateToListeners (dart:async/future_impl.dart:707:32)
           #15     Future._completeWithValue (dart:async/future_impl.dart:522:5)
           #16     _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:30:15)
           #17     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:288:13)
           #18     Resource._fetch.<anonymous closure> (package:build/src/resource/resource.dart)
           #19     _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:71:64)
           #20     _rootRunUnary (dart:async/zone.dart:1132:38)
           #21     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
           #22     _FutureListener.handleValue (dart:async/future_impl.dart:137:18)
           #23     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:678:45)
           #24     Future._propagateToListeners (dart:async/future_impl.dart:707:32)
           #25     Future._addListener.<anonymous closure> (dart:async/future_impl.dart:387:9)
           #26     _rootRun (dart:async/zone.dart:1124:13)
           #27     _CustomZone.run (dart:async/zone.dart:1021:19)
           #28     _CustomZone.runGuarded (dart:async/zone.dart:923:7)
           #29     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:963:23)
           #30     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
           #31     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
           #32     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:116:13)
           #33     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:173:5)

[+1745 ms] 14.2s elapsed, 1580/1652 actions completed.
[ +630 ms] 15.3s elapsed, 1580/1652 actions completed.
[ +972 ms] 16.5s elapsed, 1580/1652 actions completed.
[ +873 ms] 17.5s elapsed, 1585/1657 actions completed.
[ +322 ms] BuildStepCompletedException: Attempt to use a BuildStep after is has completed
[   +2 ms] #0      BuildStepImpl.readAsBytes (package:build/src/builder/build_step_impl.dart:93:22)
           #1      ScratchSpace.ensureAssets.<anonymous closure>.<anonymous closure>.<anonymous closure>
           (package:scratch_space/src/scratch_space.dart:111:56)
           <asynchronous suspension>
           #2      Pool.withResource (package:pool/pool.dart:127:28)
           <asynchronous suspension>
           #3      ScratchSpace.ensureAssets.<anonymous closure>.<anonymous closure> (package:scratch_space/src/scratch_space.dart:105:35)           #4      _LinkedHashMapMixin.putIfAbsent (dart:collection-patch/compact_hash.dart:291:23)
           #5      ScratchSpace.ensureAssets.<anonymous closure> (package:scratch_space/src/scratch_space.dart:103:30)
           <asynchronous suspension>
           #6      MappedIterator.moveNext (dart:_internal/iterable.dart:393:18)
           #7      new List.from (dart:core-patch/array_patch.dart:33:29)
           #8      Iterable.toList (dart:core/iterable.dart:398:5)
           #9      ScratchSpace.ensureAssets (package:scratch_space/src/scratch_space.dart:116:8)
           #10     _createDevCompilerModule.<anonymous closure> (package:build_web_compilers/src/dev_compiler_builder.dart:121:42)
           #11     _NoOpBuilderActionTracker.trackStage (package:build_runner_core/src/generate/performance_tracker.dart:300:15)
           #12     BuildStepImpl.trackStage (package:build/src/builder/build_step_impl.dart:146:21)
           #13     _createDevCompilerModule (package:build_web_compilers/src/dev_compiler_builder.dart:120:19)
           #14     _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:71:64)
           #15     _rootRunUnary (dart:async/zone.dart:1132:38)
           #16     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
           #17     _FutureListener.handleValue (dart:async/future_impl.dart:137:18)
           #18     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:678:45)
           #19     Future._propagateToListeners (dart:async/future_impl.dart:707:32)
           #20     Future._completeWithValue (dart:async/future_impl.dart:522:5)
           #21     _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:30:15)
           #22     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:288:13)
           #23     Resource._fetch.<anonymous closure> (package:build/src/resource/resource.dart)
           #24     _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:71:64)
           #25     _rootRunUnary (dart:async/zone.dart:1132:38)
           #26     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
           #27     _FutureListener.handleValue (dart:async/future_impl.dart:137:18)
           #28     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:678:45)
           #29     Future._propagateToListeners (dart:async/future_impl.dart:707:32)
           #30     Future._addListener.<anonymous closure> (dart:async/future_impl.dart:387:9)
           #31     _rootRun (dart:async/zone.dart:1124:13)
           #32     _CustomZone.run (dart:async/zone.dart:1021:19)
           #33     _CustomZone.runGuarded (dart:async/zone.dart:923:7)
           #34     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:963:23)
           #35     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
           #36     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
           #37     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:116:13)
           #38     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:173:5)

[+1651 ms] BuildStepCompletedException: Attempt to use a BuildStep after is has completed
[ +378 ms] #0      BuildStepImpl.readAsBytes (package:build/src/builder/build_step_impl.dart:93:22)
                    #1      ScratchSpace.ensureAssets.<anonymous closure>.<anonymous closure>.<anonymous closure>
                    (package:scratch_space/src/scratch_space.dart:111:56)
                    <asynchronous suspension>
                    #2      Pool.withResource (package:pool/pool.dart:127:28)
                    <asynchronous suspension>
                    #3      ScratchSpace.ensureAssets.<anonymous closure>.<anonymous closure>
                    (package:scratch_space/src/scratch_space.dart:105:35)
                    #4      _LinkedHashMapMixin.putIfAbsent (dart:collection-patch/compact_hash.dart:291:23)
                    #5      ScratchSpace.ensureAssets.<anonymous closure> (package:scratch_space/src/scratch_space.dart:103:30)
                    <asynchronous suspension>
                    #6      MappedIterator.moveNext (dart:_internal/iterable.dart:393:18)
                    #7      new List.from (dart:core-patch/array_patch.dart:33:29)
                    #8      Iterable.toList (dart:core/iterable.dart:398:5)
                    #9      ScratchSpace.ensureAssets (package:scratch_space/src/scratch_space.dart:116:8)
                    #10     _createDevCompilerModule.<anonymous closure>
                    (package:build_web_compilers/src/dev_compiler_builder.dart:121:42)
                    #11     _NoOpBuilderActionTracker.trackStage (package:build_runner_core/src/generate/performance_tracker.dart:300:15)
                    #12     BuildStepImpl.trackStage (package:build/src/builder/build_step_impl.dart:146:21)
                    #13     _createDevCompilerModule (package:build_web_compilers/src/dev_compiler_builder.dart:120:19)
                    #14     _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:71:64)
                    #15     _rootRunUnary (dart:async/zone.dart:1132:38)
                    #16     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
                    #17     _FutureListener.handleValue (dart:async/future_impl.dart:137:18)
                    #18     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:678:45)
                    #19     Future._propagateToListeners (dart:async/future_impl.dart:707:32)
                    #20     Future._completeWithValue (dart:async/future_impl.dart:522:5)
                    #21     _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:30:15)
                    #22     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:288:13)
                    #23     Resource._fetch.<anonymous closure> (package:build/src/resource/resource.dart)
                    #24     _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:71:64)
                    #25     _rootRunUnary (dart:async/zone.dart:1132:38)
                    #26     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
                    #27     _FutureListener.handleValue (dart:async/future_impl.dart:137:18)
                    #28     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:678:45)
                    #29     Future._propagateToListeners (dart:async/future_impl.dart:707:32)
                    #30     Future._addListener.<anonymous closure> (dart:async/future_impl.dart:387:9)
                    #31     _rootRun (dart:async/zone.dart:1124:13)
                    #32     _CustomZone.run (dart:async/zone.dart:1021:19)
                    #33     _CustomZone.runGuarded (dart:async/zone.dart:923:7)
                    #34     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:963:23)
                    #35     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
                    #36     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
                    #37     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:116:13)
                    #38     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:173:5)

^CTerminate batch job (Y/N)?

Wondering if this may be Windows-specific. @yjbanov if you need help reproing on Windows, swing by one of the usual suspects :-)

For sure I'm adding this link: https://github.com/flutter/flutter/issues/44583


ability to fetch existing DeployedFlow

There are a total of 5 cases, documented below:
No @project decorator

- Name is “parameterflow”
- Branch name DOESN’T EXIST
- Project name DOESN’T EXIST

With @project(name='parameterflow_project')

- Name is “parameterflowproject.user.madhurtandon23gmail.com.parameterflow”
- Branch name is<EMAIL_ADDRESS>- Project name is “parameterflow_project”

With @project(name='parameterflow_project') AND —production as True

- Name is “parameterflowproject.prod.parameterflow”
- Branch name is “prod”
- Project name is “parameterflow_project”

With @project(name='parameterflow_project') AND —branch=“hello”

- Name is “parameterflowproject.test.hello.parameterflow”
- Branch name is “test.hello”
- Project name is “parameterflow_project”

With @project(name='parameterflow_project') AND —branch=“hello” AND —production as True

- Name is “parameterflowproject.prod.hello.parameterflow”
- Branch name is “prod.hello”
- Project name is “parameterflow_project”

The following scenarios are tested:
df = DeployedFlow.from_deployment("parameterflow")
df = DeployedFlow.from_deployment("parameterflowproject.user.madhurtandon23gmail.com.parameterflow")
df = DeployedFlow.from_deployment("parameterflowproject.prod.parameterflow")
df = DeployedFlow.from_deployment("parameterflowproject.test.hello.parameterflow")
df = DeployedFlow.from_deployment("parameterflowproject.prod.hello.parameterflow")

and then doing triggered_run = df.trigger(myparam=20) after each of the above..

Usage:
with Deployer(flow_file="../../try.py", file_read_timeout=1).argo_workflows() as ar:
    ar_obj = ar.create()

    # save this somewhere / remember it...
    identifier = ar_obj.name
    metadata = ar_obj.metadata

    df = DeployedFlow.from_deployment(identifier=identifier, metadata=metadata)
    triggered_run = ar_obj.trigger(myparam=10)

Usage if @project is present in flow file
with Deployer(flow_file="../../try.py", file_read_timeout=1, branch="hello", production=True).argo_workflows() as ar:
    ar_obj = ar.create()

    # save this somewhere / remember it...
    identifier = ar_obj.name
    metadata = ar_obj.metadata

    df = DeployedFlow.from_deployment(identifier=identifier, metadata=metadata)
    triggered_run = ar_obj.trigger(myparam=10)

Usage if @conda_base or @conda is present in the original flow file:
with Deployer(
    flow_file="../../try.py",
    file_read_timeout=1,
    environment="conda"
).argo_workflows() as ar:
    ar_obj = ar.create()

    # save this somewhere / remember it...
    identifier = ar_obj.name
    metadata = ar_obj.metadata

    df = DeployedFlow.from_deployment(identifier=identifier, metadata=metadata)
    triggered_run = df.trigger(beta={"madhur": "cool"})

similarly for @pypi or @pypi_base, just use environment="pypi"
Note that the fake flow file generated doesn't use these decorators at all..
because the purpose for the fake flow file is for inferring user injected parameters..


ulimit -n is too low inside toolbox and can't be changed.

Building GStreamer with Cerbero requires over 1024 FDs, creating a container by hand with podman I can do "--ulimit nofile=10240", but I can't find a similar option when using toolbox.

Interesting.
We could bump the default limit for all toolboxes and/or introduce a toolbox create command line flag to override it.
However, I don't think it will really work. A non-root user can't override ulimit -n when running directly on the host. While rootless podman create --name foo --ulimit nofile=10240 ... does work, rootless podman start foo will error out. So you can't really use the container.

Were you by any chance referring to the soft and hard limits?
On my host, the hard limit is 4096 and the soft limit is 1024. Hence a non-root user can bump the soft limit till 4096:
[rishi@kolache ~]$ ulimit -H -n
4096
[rishi@kolache ~]$ ulimit -S -n
1024
[rishi@kolache ~]$ ulimit -S -n 4096
[rishi@kolache ~]$ ulimit -H -n
4096
[rishi@kolache ~]$ ulimit -S -n
4096

However, inside the rootless toolbox container, both soft and hard limits are 1024:
⬢[rishi@toolbox ~]$ ulimit -H -n
1024
⬢[rishi@toolbox ~]$ ulimit -S -n
1024

As @giuseppe pointed out, this does work: podman create --ulimit nofile=1024:4096.
Are 4096 file descriptors enough to build GStreamer with Cerbero? :)

Yes, I'm referring to the hard limit inside the container being set to the soft limit of the host. I guess ideally for toolbox, the hard would be set to the hard limit of the host for most thing.

On my recently installed F30 machine, I have a hard limit of 524288 fds, which makes a lot of sense

Erm, for GStreamer, we set it to 10240 .. but I thinkm ito's just adding a 0.. Can't we just inherit the limit from the host ? --ulimit nofile=$(ulimit -n):$(ulimit -H -n)

On my recently installed F30 machine, I have a hard limit of 524288 fds

Ah, so the hard limit is indeed higher on Fedora 30. So far I was playing on Fedora 29, where the hard limit used to be 4096.

Can't we just inherit the limit from the host ? --ulimit nofile=$(ulimit -n):$(ulimit -H -n)

Yeah, I think for toolbox containers we should just use the host limits. @giuseppe said that he's investigating if this can be made even easier with --ulimit host. If so we'd just use that. The more we can delegate to Podman, the better. :)

I've opened a PR so you can use --ulimit host and not have to worry to copy them from the system:
https://github.com/containers/libpod/pull/3491

Just experienced a problem with this when I tried to install packages using npm.

The low limit also causes issues with Wine/Esync.

Fixed via https://github.com/debarshiray/toolbox/pull/229
You'd need Podman 1.5.0 to have the ulimits passed through from the host to the containers.


Validate defcustom :type specifications in CI

As per discussion in https://github.com/raxod502/straight.el/pull/628#issuecomment-726825989, we could catch some bugs by checking the defcustom forms in straight.el to see that their default values are compatible with their :type specifications. An example of doing this is at https://github.com/progfolio/doct/blob/dabb30ebea866ef225b81561c8265d740b1e81c3/tests/doct-test.el#L148-L165.

Came across this package which looks relevant:
https://endlessparentheses.com/validate-el-schema-validation-for-emacs-lisp.html

Nice, yeah, that looks like exactly what we would need!

I took a look over our defcustoms, and for most of them we can get away with simple assertions.
Added tests for them in #798

See also https://github.com/raxod502/straight.el/pull/825.


packaging: switch to native WiX toolchain and Windows runner

Cross-platform msitools do not support the Environment directive, which should be the proper way to address the issue, so this PR adapts the Makefile to assume a Windows environment when building, addressing #1374.
make dist now runs on all platforms, but on Windows, assuming candle.exe, light.exe and GNU tar are installed it builds all tarballs, zip and msi packages. On other platforms it will only build the tarballs and print a warning:
Makefile:340: WARNING: MSI generation only supported on Windows platforms. Skipping.

~Currently in draft because it requires make dist to run under Windows, so needs further fiddling to make it at least  usable elsewhere.~
Alternative approach would be to break make dist to 2 steps and run only the Windows step on a Windows runner.
Signed-off-by: Edoardo Vacchi<EMAIL_ADDRESS>

great notes. I think this is the path forward, but I can also see a reluctance to depend on a windows phase. That said, basically every maintainer needs to be able to run windows occasionally at this point, so I feel personally not too critical about it!

yeah let's go with this rather than #1383

@codefromthecrypt speaking of func-e I noticed that while trying func-e and wazero on my Windows machine, and uninstalling I think it tried to uninstall wazero instead of func-e (or the other way round, don't remember right now). I suspect the reason is that they share the same GUID here:
<!-- UpgradeCode needs to be constant until an incompatible change occurs
     See https://docs.microsoft.com/en-us/windows/win32/msi/upgrade-table -->
<?ifndef var.UpgradeCode?>
<?define UpgradeCode = "FC6C326B-1DB7-4D48-8F05-E13E79DF4D0E" ?>
<?endif?>

https://github.com/tetratelabs/func-e/blob/master/packaging/msi/func-e.wxs#L36-L40
shall we change that on wazero maybe? I can do it in this PR.

shall we change that on wazero maybe? I can do it in this PR.

OMG please do

I removed the warning because it was being printed unconditionally always for any make target.


Memoize sorting state

I am rendering table using handlebars, every time when my data updated, table will be re-rendered again. Would be cool to have an option to retrieve "sorting state" and apply this state again on new table.

Thanks @sammy007. Is this something you could do on your end by saving a clone of the table node before you re-render with handlebars?


！！
Most people only care about how to generate strings through templates
I have finally found you, the one who goes upstream

Glad you found it useful!


Release Process Updates

It came up in the Goreleaser PR #2437 that the team isn't using the CI for the release process.  If the team would like to begin using the CI for the release process, for goreleaser to auto build the binaries and generate the release, then we should align on the process and make the corresponding updates to the CI.
          [no change needed][follow up refactor] I only ever cut celestia-app releases with via the **Draft a new release** button on [celestia-app/releases](https://github.com/celestiaorg/celestia-app/releases) so that I can manually inspect the auto-generated release notes. AFAIK cutting a release via that page doesn't qualify as a [`workflow_dispatch`](https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#workflow_dispatch) event. If that's also how @evan-forbes cuts releases, then we may not need this step and can potentially drop this section above:

  workflow_dispatch:
    # Inputs the workflow accepts.
    inputs:
      version:
        # Friendly description to be shown in the UI instead of 'name'
        description: "Semver type of new version (major / minor / patch)"
        # Input has to be provided for the workflow to run
        required: true
        type: choice
        options:
          - patch
          - minor
          - major

Originally posted by @rootulp in https://github.com/celestiaorg/celestia-app/pull/2437#discussion_r1317399036

Closing as won't do. We don't use the workflow dispatch to create releases and so it was removed from CI.


Please give  the download link

Sir  please  give  download link which contains only GPUView.zip files, so that users can download separately and add  to  C:\windows\system32.
Include  both  32bit and 64bit versions
Thanks to authors

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

ID: 5371abe0-588e-75e0-caab-96fe3b8f275a
Version Independent ID: 06f1f66e-6d3b-dcaa-548f-dffae63faf18
Content: Using GPUView - Windows drivers
Content Source: windows-driver-docs-pr/display/using-gpuview.md
Product: windows-hardware
GitHub Login: @mimisasouvanh
Microsoft Alias: misaso

I'm not sure if things have changed, but that link does not help - it simply refers back to the same MS Docs page for the download.  Trying to install the entire Win7 SDK just for a single executable tool seems excessive (not to mention that the install keeps failing...)
Providing a link to the actual tool, rather than directing us in a circular reference, would be much more helpful!


Force mountPaths to be below directory

To further restrict what a podspec can do we could enforce that only mount points under /opt/systemk (or whatever) are acceptable. This prevents systemk from chowning directories it shouldn't.

Wasn't this addressed already by #43?

Wasn't this addressed already by #43?

Yep
/close
(I'll hook up a bit that makes this work)
On Wed, 20 Jan 2021, 21:27 Pires<EMAIL_ADDRESS>wrote:

Wasn't this addressed already by #43
https://github.com/virtual-kubelet/systemk/pull/43?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/virtual-kubelet/systemk/issues/31#issuecomment-763911608,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACWIW4L6AHNSFJQ3FFPLBTS244ENANCNFSM4VHCUGUA
.

Yep
/close
(I'll hook up a bit that makes this work)
On Wed, 20 Jan 2021, 21:27 Pires<EMAIL_ADDRESS>wrote:

Wasn't this addressed already by #43
https://github.com/virtual-kubelet/systemk/pull/43?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/virtual-kubelet/systemk/issues/31#issuecomment-763911608,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACWIW4L6AHNSFJQ3FFPLBTS244ENANCNFSM4VHCUGUA
.


Espose Zdog.TAU

Having the constant exposed for easier rotation handling would be useful

I don't see really why you would want that. To me, this is out-of-scope, I'm going to close this one. Feel free to tell me your use case anyhow

From here: https://zzz.dog/api#utilities-tau

A full rotation in radians. Math.PI * 2. TAU is more user-friendly than PI as TAU maps directly to a full rotation.
const TAU = Zdog.TAU; // easier to read constant

rotate: { y: TAU/4 } // /4 = quarter turn
rotate: { y: TAU/2 } // /2 = half turn
rotate: { y: TAU*3 } // *3 = 3 full turns```

If you won't add it it's no big deal just thought it would generally bring more of the surface of Zdog to the wrapper library.

If you use it extensively in templates, it is easy to expose that yourself :
Vue.prototype.TAU = Math.PI * 2
I'd rather left that in userland.


Remove the "all_history" permission

Remove the all_history permission (Modifier) because according to the documentation only the GET method (Viewer) is used.

user group permissions

$ curl -X GET "${DOJOT_HOST}/auth/pap/group/viewer/permissions" -H "Authorization: Bearer ${JWT}" -H 'Content-Type:application/json'
{
    "permissions": [
        {
            "id": 9,
            "path": "/history/(.*)",
            "name": "ro_history",
            "method": "GET",
            "permission": "permit",
            "type": "system",
            "created_date": "2019-04-15T18:14:58.094124",
            "created_by": 0
        },
        {
            "id": 8,
            "path": "/history/(.*)",
            "name": "all_history",
            "method": "(.*)",
            "permission": "permit",
            "type": "system",
            "created_date": "2019-04-15T18:14:58.093796",
            "created_by": 0
        }
    ]
}

Affected Version: 58.2-20190321

Test OK.

Tested on Version: 62.3-20190603


Use Media Foundation on Windows for restricted codecs

Currently your only option to play H.264 and AAC on Windows is to use FFmpeg, but this is not ideal. Most Windows versions come with Media Foundation nowadays, so we should be able to use that where available.

Is there any plan to support this in the short/mid term?


Stay on Ubuntu 22 for test on CI for now

there are issues with Ubuntu 24 which is the new default version
reported https://issues.redhat.com/browse/FUSETOOLS2-2519 to upgrade to latest Ubuntu later

see with this PR that the main branch is currently not working with Ubuntu 24 https://github.com/camel-tooling/camel-dap-client-vscode/pull/794


The following MissingPluginException was thrown while activating platform stream on channel shell_sftp:

Hi Owner,
I met the following issue when try to rub your ssh2 example, would pls double check and advise me how to handle this issue?
Many thanks.
Mang Zhang /China
<EMAIL_ADDRESS>════════ Exception caught by services library ══════════════════════════════════
The following MissingPluginException was thrown while activating platform stream on channel shell_sftp:
MissingPluginException(No implementation found for method listen on channel shell_sftp)
When the exception was thrown, this was the stack
C:/b/s/w/ir/cache/builder/src/out/host_debug/dart-sdk/lib/internal/js_dev_runtime/private/ddc_runtime/errors.dart 251:49  throw
packages/flutter/src/services/platform_channel.dart 154:7                                                                  _invokeMethod
C:/b/s/w/ir/cache/builder/src/out/host_debug/dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 45:50
C:/b/s/w/ir/cache/builder/src/out/host_debug/dart-sdk/lib/async/zone.dart 1687:54                                          runUnary
C:/b/s/w/ir/cache/builder/src/out/host_debug/dart-sdk/lib/async/future_impl.dart 160:18                                    handleValue
C:/b/s/w/ir/cache/builder/src/out/host_debug/dart-sdk/lib/async/future_impl.dart 767:44                                    handleValueCallback
C:/b/s/w/ir/cache/builder/src/out/host_debug/dart-sdk/lib/async/future_impl.dart 796:13                                    _propagateToListeners
C:/b/s/w/ir/cache/builder/src/out/host_debug/dart-sdk/lib/async/future_impl.dart 602:5                                     [_completeWithValue]
C:/b/s/w/ir/cache/builder/src/out/host_debug/dart-sdk/lib/async/future_impl.dart 640:7                                     callback
C:/b/s/w/ir/cache/builder/src/out/host_debug/dart-sdk/lib/async/schedule_microtask.dart 40:11                              _microtaskLoop
C:/b/s/w/ir/cache/builder/src/out/host_debug/dart-sdk/lib/async/schedule_microtask.dart 49:5                               _startMicrotaskLoop
C:/b/s/w/ir/cache/builder/src/out/host_debug/dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 166:15

Same issue here, did you succeed in solving this?

Hello,
This package does not support Windows. You may want to check out these other options:
https://pub.dev/packages/dartssh2
https://pub.dev/packages/libssh_binding


OCP details popover & tooltip for derived and infrastructure cost

The popover, when clicking the info icon, describes what derived and infrastructure costs are. The tooltip shows the actual derived and infrastructure costs.
Fixes https://github.com/project-koku/koku-ui/issues/670
Cost tooltip:

Info icon popover:

Codecov Report

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

@@           Coverage Diff           @@
##           master     #729   +/-   ##
=======================================
  Coverage   76.97%   76.97%
=======================================
  Files         224      224
  Lines        3587     3587
  Branches      614      614
=======================================
  Hits         2761     2761
  Misses        741      741
  Partials       85       85

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 ac4286c...0e16527. Read the comment docs.


Notify when receiving ethereum coins.

I want to send payment to eth base account once i receive ethers in my account. But the ether is not reflected in my account.How we can set the wallet notification for ethereum?
Like in btc we can set the walletnotify in the bitcoin.conf file.

How does this is related to Peatio? Please, google for walletnotify eth.

Thanks,But in peatio ,how get notified when any of the ETH address receive deposits.

@antechdemo
Maybe we can use crontab for this, if anyone can figure it out it will be great.
It's related to peatio, if there is no balance change after deposit in Peatio accounts then eth is not working properly.


Fix TrainsLogger doctest failing (switch to bypass mode in GitHub CI)

Fix TrainsLogger CI doctests failing
See PR #1352 and allegroai/trains#119
TrainsLogger run in offline (bypass-mode) automatically on GitHub CI doctest.

this fix is just for the two CI, but what about other users running test offline?

This is still supported with:
TrainsLogger.set_bypass_mode(True)

This PR drops coverage though. Can we fix that?

Guys, the "Build-Docs" started failing, yesterday it passed on the exact same code base.
Did something change in the CI ?

It looks like sphinx got a new release but one of our extensions is not ready for that.
A temporary fix is to change sphinx>=2.0 to sphinx<3.0 in docs/requirements.txt
@Borda what do you think?

@awaelchli yes i think as a general rule we should pin versions to prevent upgrading major releases without explicit review
sphinx>=2.0,<3.0

@Borda how do you run the codecov bot again?

@Borda how do you run the codecov bot again?

you need to re-run Drone CI because only this one is sending the report

@Borda How do I do that (re-run Drone CI) ?

Guys, I still can't detect any change in Codecov, is it just me? (The decrease in coverage was due to the CI bypass mode, I think I manage to tell Codecov to ignore it, but I'm uncertain...)

@williamFalcon I can't get the Codecov bot to update the new coverage but on the drone log it seems to stay 92% (i.e. no change)
See testing section log here


Missing TS definitions in 2.X packages

Please tell us about your environment:

_winston version?

[X ] winston@2
[ ] winston@3

node -v outputs: v8.10.0
Operating System? macOS
Language? TypeScript 3.0

What is the problem?

The @types/winston package no longer has the TS definitions, claiming that winston package itself includes them. However the latest winston 2.X release, 2.4.3, doesn't include them https://github.com/winstonjs/winston/tree/2.4.3
Although they seem to be in the 2.X branch https://github.com/winstonjs/winston/tree/2.x
Consecuence: my TS builds are failing as definitions can't be found neither in winston nor in @types/winston. I have to install an old version of @types/winston to have definitions (2.3.9).
What do you expect to happen instead?

To get the TS definitions into the latest winston 2.X package.
Other information

Need them in the 3.x package as well, although it looks like it's already in GitHub and just needs to be published to npm.

Can confirm I have a similar issue, where I used to be able to pass winston.debug( ) an object and it work fine however now it doesn't compile saying
*object type* is not assignable to parameter of type 'string'.

Seems to have been fixed in version 2.4.4.

Yes.  New 3.x release should be published very soon. Thanks!


Remove single threaded scheduler from dask_es test fixture after Dask issue is resolved

In PR #1079 a change was made to use the dask single threaded scheduler for tests involving the dask_es pytest fixture because of failures in the unit tests that were occurring when using the default threaded scheduler with pandas 1.1.0 installed.
There is a related Dask issue #6454 as a result of these failures.
When the Dask issue is resolved, we should switch back to using the default threaded scheduler for the tests by removing the following line from the dask_es fixture in conftest.py:
dask.config.set(scheduler='single-threaded')

So far, I have not been able to reproduce the error documented in the Dask repo using pandas version 1.1.2, so it might now be safe to switch back to using the default scheduler, as long as we are using pandas >= 1.1.2.


Add Style/StyleRef types to represent "fill or stroke"

In the spirit of Brush and BrushRef these are a pair of owned and reference types to abstractly represent either a fill or a stroke.
The motivation is for linebender/vello#284 where trying to parameterize on draw style within a builder that is consumed by fill or stroke methods is ergonomically painful. The intention is to replace those methods with a single draw method taking impl Into<StyleRef> as the first parameter. This will likely extend to other SceneBuilder methods in the future.
I could add these types directly to vello but it probably makes more sense for them to live here.

Thanks for the quick review!


review duplicates strategies

/unassign @seanmalloy

@safanaj thanks for improving the code. Do you still plan on crafting the PR? This is a good improvement of the strategy.

I wrote a possible option which tries to balance them out. Comments welcome.
https://github.com/mattwilliamson/descheduler/commit/1fc84f5c2a6961a6f9186f78d15a0b275e87a598

@safanaj ping again, would you like to continue this PR, possibly with some of the changes in https://github.com/kubernetes-sigs/descheduler/pull/269#issuecomment-634262885?
If not, @mattwilliamson feel free to open your changes as a new PR whenever you feel appropriate.

As mentioned in https://github.com/kubernetes-sigs/descheduler/issues/263#issuecomment-644227249, this PR hasn't had any updates yet we do have some other contributors interested in picking up the work. For that reason I won't hold anyone else back from continuing the work started here, and will close this if a replacement PR is opened (though I encourage any new PRs to build off of the work started here so that all contributors receive appropriate credit)

/reopen

@farah is there some reason we need to reopen this PR? I think someone needs to pick up where this PR left off, but a new PR needs to get created.

@seanmalloy yes that was unintentional. i'll have a new PR based partly off this work very soon....


improve development guide

What's this PR do?
This PR improve development guide
Any background context you want to provide?
This PR solves the  issue improve development guide #341

@akashnimare  solve the link problem, you can review

Thanks, @rrhythmsharma.

How did we arrive on the **2GB of available RAM data?
**Followings are optional yet recommended prerequisites -** - What is the use of the following installations?

The english looks very informal at some parts and there is a severe issue of incorrect capitalisation in sentences and headings.
@rishig  should probably go through the text once.

@abhigyank , before running development environment we need to install many prerequisites, so i thought to add 2 GB line and i took help from  here for windows installation instruction, please tell me the mistakes here

@akashnimare @rrhythmsharma additionally speaking, why is there a heading "Improve development guide" in the new guide ? Also see the heading "build and run", atleast the Case should be changed. The changes could be better formatted i guess.

It would better if @abhigyan review. I will change it then

@akashnimare  can we revert the commit PR? There are a lot of issues with it. It really looks bad as our development guide.
@rrhythmsharma I went through the dropbox paper and started to review but there are so many things wrong with it in terms of language and grammar, I think it'd be better to start with a new draft.

I will send another PR, no issues

can we revert the commit PR? There are a lot of issues with it. It really looks bad as our development guide.

I knew this while merging the PR, it was getting difficult to collaborate on paper so I thought let's merge the v1 and then we can take things from there. @vsvipul, @rrhythmsharma feel free to send a PR.


e2e Record Splitter test scenarios

@sawantpritam Please review

Add Override service account details steps in all scenarios

Add Override service account details steps in all scenarios

Added the Override service account details steps in all scenarios where required.

Add Override service account details steps in all scenarios

Added the Override service account details steps in all scenarios where required.

Add  below method in TestSetupHook for override to work in macro scenario.
@Before(order = 1)
  public static void overrideServiceAccountFilePathIfProvided()

https://github.com/data-integrations/google-cloud/blob/c3d0fc99448f56a2761d40dee8a2efe84b9ae24a/src/e2e-test/java/io/cdap/plugin/common/stepsdesign/TestSetupHooks.java#L70

Added the method in TestSetupHook


Eager Instruction Creation

At present, the instructions are constructed when-needed. This is helpful for avoiding things which are a little awkward to construct, but has a run-time hit associated to checking whether each instruction is / is-not assigned each time it is encountered.
This PR will attempt to modify this. It necessarily taxes the robustness of our system further, because it requires that any instruction we encounter can be constructed. The basic tests pass locally for the interpreted function as-is, so I'm opening this PR to see whether the integration tests also pass. Presumably they won't.

Completely redundant -- closing.


[firebase-auth/google_sign_in] Visual bug when signing in

Steps to Reproduce

Sign in with google on an account that has already signed in once before in a flutter app

Target Platform: Android
Devices: Emulator and Physical Devices
Flutter Version: Flutter (Channel stable, v1.9.1+hotfix.6, on Microsoft Windows [Version 10.0.19025.1052], locale en-US)
firebase_auth: ^0.15.0+1
google_sign_in: ^4.0.14
You can see an example of this visual bug from a live stream I did a bit ago: https://youtu.be/OlcYP6UXlm8?t=3132
When you click sign in with google, the screen fades slightly and then a bar drops down from the top before the screen fades back in.  According to one of my Subscribers, this problem persists on the current stable version of flutter and it also exists while running in a physical application with a release version of the app.  I have verified this bug myself after the subscriber mentioned it to me.  There is nothing in my application that I can see that would cause this behavior.  I also recall seeing it in previous applications.

Hi @tensor-programming (big fan here)
I see you recently update the source code available in the video you linked,
I take it as a viable minimal code sample to reproduce the problem;
could you please provide your flutter run --verbose ?
If you believe that the issue is caused by firebase-auth,
please open the issue in the dedicated github.
thank you

Thank you (flattered that a core contributor is a fan!).
I did not realize that you guys had split off some of the flutterfire plugins to their own repository.  I am not sure if the problem is in firebase_auth though that seems likely.  After thanksgiving today, Ill take the code and bring it down to a much more minimal example. I think all I need to do to replicate the problem is just sign in with firebase_auth using a provider like Google or Facebook instead of email/password.  What part of the flutter run --verbose log do you require?  Should I just give you the portion of the log as I am clicking on the button or the entire log from boot up till close?

Should I just give you the portion of the log as I am clicking on the button or the entire log from boot up till close?

yes please,
thanks again
and have a nice thanksgiving

Not really sure if that means the entire log or what.
Here is the log that I generated (at least as much as I could grab given my terminal's line limit).
At the bottom, I included a set of lines that happen when you click on the sign in to google button in the application.
// Information from clicking the login button:
[+4126 ms] W/ActivityThread( 8147): handleWindowVisibility: no activity for token android.os.BinderProxy@d7bc475
[ +121 ms] D/EGL_emulation( 8147): eglMakeCurrent: 0xe6d7c4a0: ver 3 0 (tinfo 0xd32aefd0)
[ +331 ms] D/EGL_emulation( 8147): eglMakeCurrent: 0xe6d7c4a0: ver 3 0 (tinfo 0xd32aefd0)
[  +45 ms] W/BiChannelGoogleApi( 8147): [FirebaseAuth: ] getGoogleApiForMethod() returned Gms: com.google.firebase.auth.api.internal.zzak@1f49dd
[ +390 ms] D/FirebaseAuth( 8147): Notifying id token listeners about user ( ueAquSTWLrViVSdbLtFxtyYZNO82 ).
// print function call
[   +5 ms] I/flutter ( 8147): signed in with google ueAquSTWLrViVSdbLtFxtyYZNO82

The log that this was taken from is a simplified version of the original app without the router logic and the facebook signin process. (You can just click the button to sign in with a gmail account but it doesn't go anywhere).  The source is here  I still see the visual glitch which indicates that its likely google_sign_in related. The screen fade does look similar to what happens when the screen fades and you sign in for the first time.

I'm closing this issue in favor of the slightly more recent #48371 (seems to contain a smaller repro case). Thanks for reporting!