text:
shell.openExternal() raising errors

Hello,
I once asked a question on how to open a url with my ionic desktop app using @capacitor-community/electron, which i got an answer to use:
import { shell } from '@capacitor-community/electron';
shell.openExternal(url);
which i believe could would work, but it raising the following errors when i run npm run build
./electron/node_modules/fsevents/fsevents.node:1:0 - Error: Module parse failed: Unexpected character '�' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
@capacitor-community/electron:1:1122-1135 - Error: Module not found: Error: Can't resolve 'fs' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\node_modules@capacitor-community\electron\dist\core'
@capacitor-community/electron:1:1168-1183 - Error: Module not found: Error: Can't resolve 'path' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\node_modules@capacitor-community\electron\dist\core'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
./electron/node_modules/builder-util-runtime/out/ProgressCallbackTransform.js:4:17-34 - Error: Module not found: Error: Can't resolve 'stream' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\builder-util-runtime\out'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "stream": require.resolve("stream-browserify") }'
- install 'stream-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "stream": false }
./electron/node_modules/builder-util-runtime/out/httpExecutor.js:4:17-34 - Error: Module not found: Error: Can't resolve 'crypto' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\builder-util-runtime\out'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "crypto": require.resolve("crypto-browserify") }'
- install 'crypto-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "crypto": false }
./electron/node_modules/builder-util-runtime/out/httpExecutor.js:6:13-26 - Error: Module not found: Error: Can't resolve 'fs' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\builder-util-runtime\out'
./electron/node_modules/builder-util-runtime/out/httpExecutor.js:7:17-34 - Error: Module not found: Error: Can't resolve 'stream' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\builder-util-runtime\out'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "stream": require.resolve("stream-browserify") }'
- install 'stream-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "stream": false }
./electron/node_modules/builder-util-runtime/out/uuid.js:4:17-34 - Error: mModule not found: Error: Can't resolve 'crypto' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\builder-util-runtime\out'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "crypto": require.resolve("crypto-browserify") }'
- install 'crypto-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "crypto": false }
./electron/node_modules/chokidar/index.js:4:11-24 - Error: Module not found: Error: Can't resolve 'fs' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\chokidar'
./electron/node_modules/chokidar/index.js:5:16-31 - Error: Module not found: Error: Can't resolve 'path' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\chokidar'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
./electron/node_modules/chokidar/lib/constants.js:3:14-29 - Error: Module not found: Error: Can't resolve 'path' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\chokidar\lib'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
./electron/node_modules/chokidar/lib/constants.js:5:11-24 - Error: Module not found: Error: Can't resolve 'os' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\chokidar\lib'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "os": require.resolve("os-browserify/browser") }'
- install 'os-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "os": false }
./electron/node_modules/chokidar/lib/fsevents-handler.js:3:11-24 - Error: Module not found: Error: Can't resolve 'fs' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\chokidar\lib'
./electron/node_modules/chokidar/lib/fsevents-handler.js:4:16-31 - Error: Module not found: Error: Can't resolve 'path' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\chokidar\lib'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
./electron/node_modules/chokidar/lib/nodefs-handler.js:3:11-24 - Error: Module not found: Error: Can't resolve 'fs' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\chokidar\lib'
./electron/node_modules/chokidar/lib/nodefs-handler.js:4:16-31 - Error: Module not found: Error: Can't resolve 'path' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\chokidar\lib'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
./electron/node_modules/electron-serve/index.js:2:11-24 - Error: Module not found: Error: Can't resolve 'fs' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-serve'
./electron/node_modules/electron-serve/index.js:3:13-28 - Error: Module not found: Error: Can't resolve 'path' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-serve'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
./electron/node_modules/electron-updater/node_modules/fs-extra/lib/copy-sync/copy-sync.js:4:13-28[39m - Error: Module not found: Error: Can't resolve 'path' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-updater\node_modules\fs-extra\lib\copy-sync'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
./electron/node_modules/electron-updater/node_modules/fs-extra/lib/copy/copy.js:4:13-28 - Error: Module not found: Error: Can't resolve 'path' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-updater\node_modules\fs-extra\lib\copy'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
./electron/node_modules/electron-updater/node_modules/fs-extra/lib/empty/index.js:5:13-28 - Error: Module not found: Error: Can't resolve 'path' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-updater\node_modules\fs-extra\lib\empty'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
./electron/node_modules/electron-updater/node_modules/fs-extra/lib/ensure/file.js:4:13-28 - Error: Module not found: Error: Can't resolve 'path' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-updater\node_modules\fs-extra\lib\ensure'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
./electron/node_modules/electron-updater/node_modules/fs-extra/lib/ensure/link.js:4:13-28 - Error: Module not found: Error: Can't resolve 'path' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-updater\node_modules\fs-extra\lib\ensure'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
./electron/node_modules/electron-updater/node_modules/fs-extra/lib/ensure/symlink-paths.js:3:13-28 - Error: Module not found: Error: Can't resolve 'path' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-updater\node_modules\fs-extra\lib\ensure'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
./electron/node_modules/electron-updater/node_modules/fs-extra/lib/ensure/symlink.js:4:13-28 - Error: Module not found: Error: Can't resolve 'path' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-updater\node_modules\fs-extra\lib\ensure'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
./electron/node_modules/electron-updater/node_modules/fs-extra/lib/mkdirs/utils.js:7:13-28 - Error: Module not found: Error: Can't resolve 'path' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-updater\node_modules\fs-extra\lib\mkdirs'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
./electron/node_modules/electron-updater/node_modules/fs-extra/lib/move-sync/move-sync.js:4:13-28 - Error: Module not found: Error: Can't resolve 'path' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-updater\node_modules\fs-extra\lib\move-sync'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
./electron/node_modules/electron-updater/node_modules/fs-extra/lib/move/move.js:4:13-28 - Error: Module not found: Error: Can't resolve 'path' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-updater\node_modules\fs-extra\lib\move'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
./electron/node_modules/electron-updater/node_modules/fs-extra/lib/output/index.js:5:13-28 - Error: Module not found: Error: Can't resolve 'path' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-updater\node_modules\fs-extra\lib\output'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
./electron/node_modules/electron-updater/node_modules/fs-extra/lib/remove/rimraf.js:4:13-28 - Error: Module not found: Error: Can't resolve 'path' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-updater\node_modules\fs-extra\lib\remove'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
./electron/node_modules/electron-updater/node_modules/fs-extra/lib/remove/rimraf.js:5:15-32 - Error: Module not found: Error: Can't resolve 'assert' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-updater\node_modules\fs-extra\lib\remove'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "assert": require.resolve("assert/") }'
- install 'assert'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "assert": false }
./electron/node_modules/electron-updater/node_modules/fs-extra/lib/util/stat.js:4:13-28 - Error: Module not found: Error: Can't resolve 'path' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-updater\node_modules\fs-extra\lib\util'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
./electron/node_modules/electron-updater/out/AppAdapter.js:4:13-28 - Error: Module not found: Error: Can't resolve 'path' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-updater\out'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
./electron/node_modules/electron-updater/out/AppAdapter.js:5:13-26 - Error: Module not found: Error: Can't resolve 'os' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-updater\out'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "os": require.resolve("os-browserify/browser") }'
- install 'os-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "os": false }
./electron/node_modules/electron-updater/out/AppImageUpdater.js:5:24-48 - Error: Module not found: Error: Can't resolve 'child_process' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-updater\out'
./electron/node_modules/electron-updater/out/AppImageUpdater.js:7:13-26 - Error: Module not found: Error: Can't resolve 'fs' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-updater\out'
./electron/node_modules/electron-updater/out/AppImageUpdater.js:8:13-28 - Error: Module not found: Error: Can't resolve 'path' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-updater\out'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
./electron/node_modules/electron-updater/out/AppUpdater.js:5:17-34 - Error: Module not found: Error: Can't resolve 'crypto' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-updater\out'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "crypto": require.resolve("crypto-browserify") }'
- install 'crypto-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "crypto": false }
./electron/node_modules/electron-updater/out/AppUpdater.js:8:19-41 - Error: Module not found: Error: Can't resolve 'fs/promises' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-updater\out'
./electron/node_modules/electron-updater/out/AppUpdater.js:11:13-28 - Error: Module not found: Error: Can't resolve 'path' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-updater\out'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
./electron/node_modules/electron-updater/out/DownloadedUpdateHelper.js:4:17-34 - Error: Module not found: Error: Can't resolve 'crypto' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-updater\out'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "crypto": require.resolve("crypto-browserify") }'
- install 'crypto-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "crypto": false }
./electron/node_modules/electron-updater/out/DownloadedUpdateHelper.js:5:13-26 - Error: Module not found: Error: Can't resolve 'fs' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-updater\out'
./electron/node_modules/electron-updater/out/DownloadedUpdateHelper.js:9:13-28 - Error: Module not found: Error: Can't resolve 'path' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-updater\out'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
./electron/node_modules/electron-updater/out/ElectronAppAdapter.js:4:13-28 - Error: Module not found: Error: Can't resolve 'path' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-updater\out'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
./electron/node_modules/electron-updater/out/MacUpdater.js:6:13-26 - Error: Module not found: Error: Can't resolve 'fs' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-updater\out'
./electron/node_modules/electron-updater/out/MacUpdater.js:7:15-30 - Error: Module not found: Error: Can't resolve 'http' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-updater\out'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "http": require.resolve("stream-http") }'
- install 'stream-http'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "http": false }
./electron/node_modules/electron-updater/out/MacUpdater.js:10:24-48 - Error: Module not found: Error: Can't resolve 'child_process' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-updater\out'
./electron/node_modules/electron-updater/out/NsisUpdater.js:5:24-48 - Error: Module not found: Error: Can't resolve 'child_process' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-updater\out'
./electron/node_modules/electron-updater/out/NsisUpdater.js:6:13-28 - Error: Module not found: Error: Can't resolve 'path' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-updater\out'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
./electron/node_modules/electron-updater/out/NsisUpdater.js:16:15-30 - Error: Module not found: Error: Can't resolve 'zlib' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-updater\out'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "zlib": require.resolve("browserify-zlib") }'
- install 'browserify-zlib'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "zlib": false }
./electron/node_modules/electron-updater/out/differentialDownloader/DataSplitter.js:5:13-26 - Error: Module not found: Error: Can't resolve 'fs' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-updater\out\differentialDownloader'
./electron/node_modules/electron-updater/out/differentialDownloader/DataSplitter.js:6:17-34 - Error: Module not found: Error: Can't resolve 'stream' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-updater\out\differentialDownloader'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "stream": require.resolve("stream-browserify") }'
- install 'stream-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "stream": false }
./electron/node_modules/electron-updater/out/differentialDownloader/DifferentialDownloader.js:6:13-26 - Error: Module not found: Error: Can't resolve 'fs' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-updater\out\differentialDownloader'
./electron/node_modules/electron-updater/out/differentialDownloader/FileWithEmbeddedBlockMapDifferentialDownloader.js:6:15-30 - Error: Module not found: Error: Can't resolve 'zlib' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-updater\out\differentialDownloader'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "zlib": require.resolve("browserify-zlib") }'
- install 'browserify-zlib'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "zlib": false }
./electron/node_modules/electron-updater/out/differentialDownloader/ProgressDifferentialDownloadCallbackTransform.js:4:17-34 - Error: Module not found: Error: Can't resolve 'stream' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-updater\out\differentialDownloader'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "stream": require.resolve("stream-browserify") }'
- install 'stream-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "stream": false }
./electron/node_modules/electron-updater/out/providers/PrivateGitHubProvider.js:6:13-28[0m - Error: Module not found: Error: Can't resolve 'path' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-updater\out\providers'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
./electron/node_modules/electron-updater/out/windowsExecutableCodeSignatureVerifier.js:5:24-48 - Error: Module not found: Error: Can't resolve 'child_process' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-updater\out'
./electron/node_modules/electron-updater/out/windowsExecutableCodeSignatureVerifier.js:6:11-24 - Error: Module not found: Error: Can't resolve 'os' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-updater\out'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "os": require.resolve("os-browserify/browser") }'
- install 'os-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "os": false }
./electron/node_modules/electron-window-state/index.js:3:13-28 - Error: Module not found: Error: Can't resolve 'path' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-window-state'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
./electron/node_modules/electron-window-state/node_modules/jsonfile/index.js:5:8-21 - Error: Module not found: Error: Can't resolve 'fs' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-window-state\node_modules\jsonfile'
./electron/node_modules/electron-window-state/node_modules/mkdirp/index.js:1:11-26 - Error: Module not found: Error: Can't resolve 'path' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-window-state\node_modules\mkdirp'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
./electron/node_modules/electron-window-state/node_modules/mkdirp/index.js:2:9-22 - Error: Module not found: Error: Can't resolve 'fs' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\electron-window-state\node_modules\mkdirp'
./electron/node_modules/glob-parent/index.js:4:23-52 - Error: Module not found: Error: Can't resolve 'path' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\glob-parent'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
./electron/node_modules/glob-parent/index.js:5:14-36 - Error: Module not found: Error: Can't resolve 'os' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\glob-parent'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "os": require.resolve("os-browserify/browser") }'
- install 'os-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "os": false }
./electron/node_modules/graceful-fs/graceful-fs.js:1:9-22 - Error: Module not found: Error: Can't resolve 'fs' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\graceful-fs'
./electron/node_modules/graceful-fs/graceful-fs.js:87:6-29 - Error: Module not found: Error: Can't resolve 'assert' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\graceful-fs'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "assert": require.resolve("assert/") }'
- install 'assert'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "assert": false }
./electron/node_modules/graceful-fs/legacy-streams.js:1:13-37 - Error: Module not found: Error: Can't resolve 'stream' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\graceful-fs'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "stream": require.resolve("stream-browserify") }'
- install 'stream-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "stream": false }
./electron/node_modules/graceful-fs/polyfills.js:1:16-36 - Error: Module not found: Error: Can't resolve 'constants' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\graceful-fs'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "constants": require.resolve("constants-browserify") }'
- install 'constants-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "constants": false }
./electron/node_modules/is-binary-path/index.js:2:13-28 - Error: Module not found: Error: Can't resolve 'path' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\is-binary-path'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
./electron/node_modules/jsonfile/index.js:5:8-21 - Error: Module not found: Error: Can't resolve 'fs' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\jsonfile'
./electron/node_modules/picomatch/lib/constants.js:3:13-28 - Error: Module not found: Error: Can't resolve 'path' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\picomatch\lib'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
./electron/node_modules/picomatch/lib/picomatch.js:3:13-28 - Error: Module not found: Error: Can't resolve 'path' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\picomatch\lib'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
m./electron/node_modules/picomatch/lib/utils.js:3:13-28 - Error: Module not found: Error: Can't resolve 'path' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\picomatch\lib'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
./electron/node_modules/readdirp/index.js:3:11-24 - Error: Module not found: Error: Can't resolve 'fs' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\readdirp'
./electron/node_modules/readdirp/index.js:4:21-38 - Error: Module not found: Error: Can't resolve 'stream' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\readdirp'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "stream": require.resolve("stream-browserify") }'
- install 'stream-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "stream": false }
./electron/node_modules/readdirp/index.js:5:16-31 - Error: Module not found: Error: Can't resolve 'path' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\node_modules\readdirp'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
./node_modules/@capacitor-community/electron/dist/core/index.js:1:1122-1135 - Error: Module not found: Error: Can't resolve 'fs' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\node_modules@capacitor-community\electron\dist\core'
./node_modules/@capacitor-community/electron/dist/core/index.js:1:1168-1183 - Error: Module not found: Error: Can't resolve 'path' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\node_modules@capacitor-community\electron\dist\core'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
./node_modules/mime-types/index.js:16:14-37 - Error: Module not found: Error: Can't resolve 'path' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\node_modules\mime-types'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
./electron/build/src/setup.js:11:15-30 - Error: Module not found: Error: Can't resolve 'path' in 'C:\Users\ODUNAYO\Desktop\Flutter\newApp\electron\build\src'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "path": false }
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! newApp@0.0.1 build: ng build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the newApp@0.0.1 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\ODUNAYO\AppData\Roaming\npm-cache_logs\2022-01-11T09_47_38_459Z-debug.log
@IT-MikeS  kindly help with this.
Thanks

This seems to be more an issue of trying to use the function in your app and not via the context bridge to the main process. So when you build your app webpack throws a fit trying to package up electron and its dependencies.

@IT-MikeS, Yeah i now understand the cause, but what can be the possible solution  to this issue ?

There are two possible fixes here...
Quick and dirty
You could add the following to /electron/src/rt/electron-rt.ts:
// This line should already exist. Add 'shell'.
import { ipcRenderer, contextBridge, shell } from 'electron';

contextBridge.exposeInMainWorld('openExternal', shell.openExternal);

You could simply use it in the browser like this:
openExternal('https://google.com');

This could be dangerous!: https://benjamin-altpeter.de/shell-openexternal-dangers/
Best
The best solution is to add a custom plugin (that checks the input). This is a bit more work, but it is the best solution in the long run. You can find the docs here: https://capacitor-community.github.io/electron/docs/creatingplugins.

I added a pull-request to the default Capacitor plugins repo that adds support for Electron to the AppLauncher plugin: https://github.com/ionic-team/capacitor-plugins/pull/793

There are two possible fixes here...
Quick and dirty
You could add the following to /electron/src/rt/electron-rt.ts:
// This line should already exist. Add 'shell'.
import { ipcRenderer, contextBridge, shell } from 'electron';

contextBridge.exposeInMainWorld('openExternal', shell.openExternal);

You could simply use it in the browser like this:
openExternal('https://google.com');

This could be dangerous!: https://benjamin-altpeter.de/shell-openexternal-dangers/
Best
The best solution is to add a custom plugin (that checks the input). This is a bit more work, but it is the best solution in the long run. You can find the docs here: https://capacitor-community.github.io/electron/docs/creatingplugins.

@jdgjsag67251 thanks for your response, i tried the Quick and Dirty hack, but it didn't work as i keep getting the same error, and i  really don't know how to approach that suggested Best Solution

I added a pull-request to the default Capacitor plugins repo that adds support for Electron to the AppLauncher plugin: ionic-team/capacitor-plugins#793

I hope this yield something positive

```ts
contextBridge.exposeInMainWorld('openExternal', shell.openExternal);

How to call openExternal() in my page.ts file?? what to import? as i am importing shell form electron its not working.

contextBridge.exposeInMainWorld('openExternal', shell.openExternal);

How to call openExternal() in my page.ts file?? what to import? as i am importing shell form electron its not working.

i used this code
window['openExternal']()
this works

contextBridge.exposeInMainWorld('openExternal', shell.openExternal);

How to call openExternal() in my page.ts file?? what to import? as i am importing shell form electron its not working.

i used this code window['openExternal']() this works

What I did is:
add this code in my electron-rt.ts
contextBridge.exposeInMainWorld('electron', {
  shell: {
    openExternal: shell.openExternal
  }
});

and then called it in my ts as:
window.electron.shell.openExternal('https://google.com')

way way better, I will use this option

App.jsx
const handleOpenExternal = (url) => {
   window.electron.openExternal(url);
 };

<div className="menu-item" onClick={() => handleOpenExternal('https://cyberpunkcity.com')}>
     <img src={homeIcon} alt="Home" />
      <span>Website</span>
</div>
<div className="menu-item" onClick={() => handleOpenExternal('https://xoxno.com/collection/CITYNFT-26cded')}>
      <img src={nftIcon} alt="Shop" />
      <span>Shop</span>
</div>

preload.js
const { contextBridge, ipcRenderer, shell } = require('electron');

contextBridge.exposeInMainWorld('electron', {
    download: () => ipcRenderer.invoke('download'),
    verify: () => ipcRenderer.invoke('verify'),
    openExternal: (url) => shell.openExternal(url),
});

Uncaught Error: Cannot read properties of undefined (reading 'openExternal')
I keep getting this error. How can I solve it? What am I doing wrong?

repo: capacitor-community/electron


text:
Failure in core tests with proxy without user info

Maven build fails with:
15:39:35.202 [main] DEBUG d.f.e.p.store.ArtifactStoreBuilder - Build ArtifactStore(useCache: true)
Download PRODUCTION:Linux:B64 START
15:39:35.269 [main] ERROR c.c.d.repository.EmbeddedMongoDBRule - Unexpectedly, something in your proxy configuration was blank or misreferenced for com.capitalone.dashboard.repository.EmbeddedMongoDBRule$SystemProxy
java.lang.NullPointerException: null
at com.capitalone.dashboard.repository.EmbeddedMongoDBRule$SystemProxy.createProxy(EmbeddedMongoDBRule.java:58) ~[test-classes/:na]
at de.flapdoodle.embed.process.store.Downloader.downloadInputStream(Downloader.java:111) [de.flapdoodle.embed.process-1.50.0.jar:na]
at de.flapdoodle.embed.process.store.Downloader.download(Downloader.java:69) [de.flapdoodle.embed.process-1.50.0.jar:na]
at de.flapdoodle.embed.process.store.ArtifactStore.checkDistribution(ArtifactStore.java:66) [de.flapdoodle.embed.process-1.50.0.jar:na]
at de.flapdoodle.embed.process.store.CachingArtifactStore.checkDistribution(CachingArtifactStore.java:62) [de.flapdoodle.embed.process-1.50.0.jar:na]
at de.flapdoodle.embed.process.runtime.Starter.prepare(Starter.java:55) [de.flapdoodle.embed.process-1.50.0.jar:na]
at com.capitalone.dashboard.repository.EmbeddedMongoDBRule.before(EmbeddedMongoDBRule.java:136) [test-classes/:na]
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:46) [junit-4.11.jar:na]
at org.junit.rules.RunRules.evaluate(RunRules.java:20) [junit-4.11.jar:na]
at org.junit.runners.ParentRunner.run(ParentRunner.java:309) [junit-4.11.jar:na]
at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:163) [spring-test-4.1.7.RELEASE.jar:4.1.7.RELEASE]
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) [surefire-junit4-2.17.jar:2.17]
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) [surefire-junit4-2.17.jar:2.17]
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) [surefire-junit4-2.17.jar:2.17]
at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) [surefire-booter-2.17.jar:2.17]
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) [surefire-booter-2.17.jar:2.17]
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) [surefire-booter-2.17.jar:2.17]
This is caused by an assumption in EmbeddedMongoDBRule.java that assumes the HTTP_PROXY URL has a userinfo portion:
			URL proxyUrl = new URL(proxy);

			// Case for Proxy authentication required
			try {
				StringTokenizer tokenizedUrl = new StringTokenizer(proxyUrl
						.**getUserInfo**().toString(), ":");
				if (tokenizedUrl.hasMoreTokens()) {

The userinfo portion of the proxy URL is optional, so without it we pop the NPE.

Fixed.

source: gharchive/issue

repo: capitalone/Hygieia

license_type: permissive

license_source: github-api


text:
Need clarification on Fortify Collector

@tabladrum Regarding HP Fortify Collector,Could you pls help me to

how to get exact web service url for fortifyfortify.server=http://myfortify/ssc/fm-ws/services

is fortify a REST or SOAP service?

You need to configs:
fortify.token= ?????
fortify.server=http://myfortify/ssc
Fortify latest version is Rest. But current the collector that we use is 4.30 supported only.

@tabladrum currently I am using 4.21 version, can u pls tell me the changes that needs to be done for 4.30 collector code

I think the current collector should support 4.21 too.

@tabladrum  For Jira collector we have this type of query in Feature Repository
@Query(value = "{'sTeamID' : ?0 , 'isDeleted' : 'False', $and : [{'sSprintID' : {$ne : null}} , {'sSprintBeginDate' : {$lte : ?1}} , {'sSprintEndDate' : {$gte : ?1}}]}, $orderby: { 'sStatus' :-1 }", fields = "{'sSprintID' : 1, 'sSprintName' : 1,'sSprintBeginDate' : 1, 'sSprintEndDate' : 1}")
List getCurrentSprintDetail(String sTeamID, String currentISODateTime);
I want to retrieve spring details whose start date is less than current date and end date greater than current date.
From where do I need to pass these values?
Pls help

@tabladrum : When i am parsing .fpr file from hp fortify collector, I am getting mismatch in the count
Values from collector:
Severity-->blocker value-->9
Severity-->major value-->450
Severity-->critical value-->72
Values from hp fortify ssc UI:
Severity-->blocker value-->0
Severity-->major value-->50
Severity-->critical value-->12
Please help!!

We are aware of this mapping issue. We did a custom mapping. Will correct it.

@tabladrum : could you please let us know once this mapping issue is resolved.
Thanks in advance. It will be really great if this issue is fixed asap :)

Working on it. I know the changes need to be made.

@tabladrum : I tried from my end as well to map this but couldn't make it. any update ?

@tabladrum  any update on this, can this be closed?

I need to correct some mapping. Will get to it before year end.

Any update on this?

Not yet.

fyi - I have noticed that the fortify collector eats too much memory resulting into other process getting killed. seems to me that it is introducing some memory leaks

@tabladrum - Any update about the mapping mismatch? We are also facing this issue.

Hi,
Regarding the fortify token to be put in the properties file, can anyone please clarify which token is this exactly.
Fortify has a number of tokens. I have tried with authentication token which we get after sending a post request to fortify api, but that doesn't work. Please provide more details about the fortify token.
Thanks

closing the issue due to inactivity

how cam i get below configurations ?
fortify.token= ?????
fortify.server=http://myfortify/ssc

authors: Arush1989 Booma-Baskaran amitmawkin avadhmr ghouspasha rvema satishkumar-dev tabladrum


text:
Add fields description

Provide a small description to explain each field.

A tooltip was added next to the block name.
It describes all the form fields and the expected values.

repo: capsule-corp-ternoa/ternoa-js-test-dapp


text:
FileUploader add, remove comparison logic is faulty

FileUploader dispatches add/remove if the number of files changes.
This doesn't account for the case of adding/removing the same number of files.
Instead, the comparison should track some sort of id. While we shouldn't rely on the file name as the id (#1115), we can probably use file.lastModified + file.name as a heuristic.
if (files.length > prevFiles.length) {
  dispatch("add", files);
} else {
  dispatch(
    "remove",
    prevFiles.filter((_) => !files.includes(_))
  );
}

Fixed in v0.58.4


text:
[CTA section] Update the functional specs to allow offset so 2x2 layout of 4 content items

User Story

As a [user role below]:
DDS developer

I need to:
have the CTA section updated functional specs

so that I can:
so that I can properly code the CTA section component that meets the Design functions and intent

Additional information

Overview and scope of the engineering work should be included in the linked epic (#5885 )
Development issue (#TBD )

Acceptance criteria

[ ] Documented CTA section functional specifications
[ ] Sent and/or presented the specs to Design and Engineering for their review and comments
[ ] Comment is added with link to functional specs

@photodow You moved this issue to the Done pipeline, but I don't see updates / links to the functional specs.

Sorry, @RobertaJHahn you caught me in the middle of moving things over. As of right now, I don't think we should update any functional specs for this. Here is what I shared with the designers last week.

Looking over some of this L shaped card group, offsetting card group, and 2x2 layout of four content items orphan logic issues. In particular that last item right now. Card group, and the content items we’re talking about includes multiple column layouts like 2, 3, 4 as an example. Each column increases the complexity of adding this orphan card or orphan content item logic. With the addition of the L-shape we need to bring in the offsetting in card group. With that comes different logic for not only each column, but for each placement of that offset and how many are offset. With that said I still have some major reservations by adding this type of logic to our components. If we add the offset ability the adopter can implement this type of logic themselves as needed given a specific context. But anyway that’s some of my concerns and thoughts.

After discussion, we decided it's best not to allow for so many instances of the CTA section content items. We will allow up to 6, and this issue is requesting for 7 content items situ. Let's push on having more succinct and categorized content within the section.

authors: RobertaJHahn photodow shixiedesign


text:
fix(card-in-card): add icon style for missing play icon and documentation around video variation and video title overriding

Related Ticket(s)
[Video Play Icon Missing]: In the card-in-card component the video-play icon is missing when cta-type is video #7341
Description
The play video icon was not appearing correctly in card-in-card. This PR adds the icon styling and adds documentation on implementing the video variation as well as overriding the default video title from Kaltura.
BEFORE:

AFTER:

Changelog
Changed

extend the image-icon styles
add documentation in card-in-card README

@shixiedesign @skuruvil the video duration disappearing in smaller breakpoints is coming from a recently committed PR. Will open a new PR to address that issue.

source: gharchive/pull-request


text:
feat(tutorial): complete step 1

Changelog
New

{{tsimkulet carbon-tutorial react-step-1}}

@tsimkulet looks fantastic!  I've recorded your completion of step 1.

authors: ericweinmann tsimkulet

repo: carbon-design-system/carbon-tutorial


text:
Apply common file names across components

Resolves #440
Ensure all files use the common file names/formats set out in code guidelines. As a consequence of the previous fix, this means the tests and stories in particular will no longer appear in our build outputs.
What did you change?
Renamed various test and story files.
How did you test and verify your work?
Ran a build and checked outputs. Ran storybook and checked functional.

@dcwarwick CDAI uses .spec.js

Carbon-react uses 'test', though. Albeit they use -test.js (which doesn't work for them) rather than .test.js. Both 'test' and 'spec' seem to be current practices, and most configs are set up to include either, which is also true of ours:

I'm submitting my vote for .test.js 🎉

Fair enough @dcwarwick although it might give @matthewgallo the impression this is a democracy ;-)

authors: dcwarwick lee-chase matthewgallo


text:
Cupcake website dev fix - Gernal spacing fix across the website

General spacing fix

[ ] The vertical space below the H2s across the website is inconsistent.

[ ] The vertical space below below the list.

(Original task issue #246)
What we currently have on the website - too much vertical spacing.

It should only be a line break and looks like this.

This work is no longer needed.  Closing this issue.

authors: JennySanchez RobertaJHahn

repo: carbon-design-system/ibm-dotcom-library


text:
Investigate build issues with the IBM.com Library website

Detailed description

Describe in detail the issue you're having.

Builds are currently failing in our CI for the IBM.com Library website.

Is this a feature request (new component, new icon), a bug, or a general
issue?

Is this issue related to a specific component?

What did you expect to happen? What happened instead? What would you like to
see changed?

What browser are you working in?

What version of the IBM.com Library are you using?

What offering/product do you work on? Any pressing ship or release dates we
should be aware of?

Steps to reproduce the issue

Step one
Step two
Step three
etc.

Additional information

Screenshots or code
Notes

Made some performance tweaks with image sizes (they were quite massive), some yarn updates, and also tweaks the CPU configuration for gatsby. Builds seem to be going through now.


text:
🛑 mainnet - API is down

In 8bdfe8d, mainnet - API (https://api.beta.explorer.cardano.org/api/v1/epochs) was down:

HTTP code: 0
Response time: 0 ms

Resolved: mainnet - API is back up in 7edefce after 1 minute.

repo: cardano-foundation/cf-explorer-status

license: MIT


text:
Minimize & stabilize EPD GUI dependencies

Currently, every instantiation of Anaconda environment epd_gui_env takes up at least 1.6GB.
Further investigation will be done shortly to explore alternatives to reduce software bloat.

Investigation: Use virtualenv instead.

References
lark-parser - https://github.com/lark-parser/lark
Lark is a parsing toolkit for Python, built with a focus on ergonomics, performance and modularity.
empy - https://pypi.org/project/empy/
EmPy is a system for embedding Python expressions and statements

This issue is resolved but still can be improved under https://github.com/ros-industrial/easy_perception_deployment/pull/56. Closing.


text:
Generate breakpoint classes with a mixin

The breakpoint classes in cardinal are all manually added for each breakpoint in the Less source. This makes updating classes pretty cumbersome and error prone as well as adding a lot of bloat to the source. I've written a mixin that generates these breakpoint classes so they only need to be written once.
It can be used like this:
.breakpoint-prefixes({
  .@{breakpoint-prefix}my-class{ background: red; }
});

to generate this CSS:
.my-class {
  background: red;
}
@media (min-width: 480px) {
  .xs-my-class {
    background: red;
  }
}
@media (min-width: 600px) {
  .sm-my-class {
    background: red;
  }
}
@media (min-width: 768px) {
  .md-my-class {
    background: red;
  }
}
@media (min-width: 960px) {
  .lg-my-class {
    background: red;
  }
}
@media (min-width: 1140px) {
  .xl-my-class {
    background: red;
  }
}
@media (min-width: 1380px) {
  .xxl-my-class {
    background: red;
  }
}

This pull request replaces 5,258 lines of Less with 316 while maintaining 100% functionally identical CSS output.

@lukechilds this looks great! ill take a deeper look when i have a free moment.

Awesome! If you build and do a diff on cardinal.css you can see nothing's changed (apart from the odd comment).

Nice job @lukechilds! Awesome contribution, seriously. :+1: :smiley:

authors: cbracco lukechilds

repo: cardinalcss/cardinalcss

license: mit

license_source: bigquery


text:
Optimize performance of main puzzle table view

Currently it takes ~5 seconds to load the main hunts page with ~300 puzzles. An actual hunt would have fewer puzzles, but not by more than an order of magnitude.
Most of the time is spent rendering the table (whether it's the server rendering the HTML table, or the client calculating style and layout as it receives the HTML from the server). This suggests that shipping the puzzle contents to the client as a payload (e.g. JSON) and letting the client assemble the table could be advantageous:

Let datatables create the table, so only the necessary DOM nodes are created (instead, we get over 1k from the server, which are laid out and rendered before being hidden again by datatables when it paginates the table)
The HTML payload transferred by the server is 1MB which is substantial (100s of ms). The JSON payload would be smaller. Both would benefit from content compression though (at the cost of some server load).

Example profile captured from Chrome
Audit from Chrome

Some more (future) ideas, roughly sorted in order of ease:

Limit initial fetch of puzzles and do subsequent puzzle fetches in the background
Do puzzle updates asynchronously (use AJAX or likewise)
Implement live sync. Example idea: Use GraphQL subscriptions. Switch puzzle view to use something based on React, e.g. react-redux-grid. It's only mentioned in this performance issue because implementing live sync should reduce the need to refresh the page.

repo: cardinalitypuzzles/smallboard


text:
Evaluate test result issue run.sh using ERFNet-CULane-PyTorch for TuSimple data

------------Configuration---------
anno_dir: ./segGT6/0601/
detect_dir: ./tools/prob2lines/output/vgg_SCNN_DULR_w9/clips/0601/
im_dir: ./clips/0601/
list_im_file: ./list/test_img.txt
width_lane: 30
iou_threshold: 0.3
im_width: 1640
im_height: 590
Evaluating the results...
tp: 0 fp: 0 fn: 0
no positive detection
no ground truth positive
finished process file
precision: -1
recall: -1
Fmeasure: -1
Any advice?
Thank you very much.

It seems that both labels and model predictions are not correctly read. Please check the path of predictions and labels.

repo: cardwing/Codes-for-Lane-Detection


text:
Feature Request: 建议自动生成导航

发现导航菜单需要手动生成。比较麻烦。

[ ] 可以做一个 Action，或者看看有没有已有的 Action，在 Build 前生成菜单

感谢你的议题！关于该事项，在 #34 目录导航改为自动生成 已经被提及，我们进行了测试，但自动生成的目录似乎和所需要的有所不同，参考下图

手动

自动

不过因为你提及了 Action ，我们会在近期去查找是否有可行的方案

如果你是指显示上会出现 [^1] 的话，可以考虑：

使用替换的 Action 或者 Bash 脚本进行内容替换
写一个脚本实现生成。从原理来说并不难。

不是，我指的是顺序和层级关系不对应，自动生成有两种顺序：

默认先生成md文档，然后再生成文件夹，顺序为 index ， pr ， template ， markdown文件夹
通过插件设置排序，此时按照规范下面的内容，生成的顺序则会变成 markdown 文件夹， index ， pr 和 template
但这两种排序显然都不符合要求（在上一个回复中手动截图提供的层级顺序），因而我并未采取。
(◦˙▽˙◦)当然如果你有更好的想法，也欢迎提出适合的方案。

不是，我指的是顺序和层级关系不对应，自动生成有两种顺序：

默认先生成md文档，然后再生成文件夹，顺序为 index ， pr ， template ， markdown文件夹
通过插件设置排序，此时按照规范下面的内容，生成的顺序则会变成 markdown 文件夹， index ， pr 和 template

但这两种排序显然都不符合要求（在上一个回复中手动截图提供的层级顺序），因而我并未采取。 (◦˙▽˙◦)当然如果你有更好的想法，也欢迎提出适合的方案。

一般来说，可以通过 Markdown 内的元数据指定顺序。通常会提供 priority 或者 order 之类的字段。至少可以依据这个字段进行排序。或者，通过设置 slug 前缀影响顺序，例如 01_xxx.md

不是，我指的是顺序和层级关系不对应，自动生成有两种顺序：

默认先生成md文档，然后再生成文件夹，顺序为 index ， pr ， template ， markdown文件夹
通过插件设置排序，此时按照规范下面的内容，生成的顺序则会变成 markdown 文件夹， index ， pr 和 template

但这两种排序显然都不符合要求（在上一个回复中手动截图提供的层级顺序），因而我并未采取。 (◦˙▽˙◦)当然如果你有更好的想法，也欢迎提出适合的方案。

一般来说，可以通过 Markdown 内的元数据指定顺序。通常会提供 priority 或者 order 之类的字段。至少可以依据这个字段进行排序。或者，通过设置 slug 前缀影响顺序，例如 01_xxx.md

哈哈， 01_xxx.md 这个方案我也想过，但并未测试，稍后我会进行测试。

目前目录已经可以自动生成

authors: SakurajimaMaii pluveto

repo: cargo-youth/ToolDiy


text:
Only 1 Joycon will be sent to the server

The default SlimeVR server can only take up to 2 rotational inputs from each IP. One from the packet type 1 and packet type 16. Since this seems to only use packet type 1 it sends all the rotational data to one tracker. Adding an option for every pair of joycons to have a different IP could allow for redirecting the packets from another device like a phone.

Hi. This project hasn't been released yet

I have added support for more than one Joycon in the 0.2 release. Closing issue.

authors: Searith carl-anders

repo: carl-anders/slimevr-wrangler


text:
Measurements

Hello,
I am running Carla on windows. I find from the documentation that there are a lot of measurements that are logged from Carla while running, however, I don't know where can I find these measurements. I searched for them in the whole directory, and I found nothing.

Hi @mhusseinsh
looking at other issues, you may find that the measurements are not dumped in any way by default. You have to fetch them using your client and dump them by yourself in the way you want it. Take a look at e.g. #446 for an example on dumping the location of the Ego vehicle into a .txt file.

Hey @mhusseinsh.
It is exactly like @p-schulz says. I recommend you to read the docs about measurements.

Okay thanks a lot :)

authors: marcgpuig mhusseinsh p-schulz

repo: carla-simulator/carla


text:
Scenario Runner - Openscenario, How to find road_ID of a junction in the carla map

I am trying to write a custom openscenario to use it with scenario runner 9.13.
I want to spawn the vehicle near a junction in the Carla town01.  How can I find the "road_ID" and "S" and "t" values to define in my openscenario file?
Is trial and error the only way?

You can use an online OpenDRIVE viewer. For example:  https://odrviewer.io/

This is a cool tool. Thanks a lot for sharing. But, may I know where can I find the openDrive files of carla towns for example carla town10HD!

oh Never Mind, I found it. The path is: WindowsNoEditor\CarlaUE4\Content\Carla\Maps\OpenDrive.  Thanks

authors: demirciogl prabanjanGITHUB


text:
Errors compiling tests don't break the build on CI

tarpaulin apparently exits with 0 if there are compiler errors in cargo test. Since we are only running tests on CI using tarpaulin, and not compiling them first, this means that if the crate compiles correctly, but the tests don't compile, the build will appear to have succeeded when, in fact, tests were never even run.
See build 605 for an example of this problem.

I suspect this can be fixed by pre-compiling the test executables before running the tests with tarpaulin for coverage...


text:
Client should validate request URI.

This patch adds checks for the request URI and rejects invalid URIs. In
the case of forwarding an HTTP 1.1 request with a path, an "http" pseudo
header is added to satisfy the HTTP/2.0 spec.
convert_send_message is removed from the Peer trait as it is not
needed to be generic. The client version now returns an error if the request
is invalid.
This PR depends on https://github.com/hyperium/http/pull/147.
Closes #179

I pushed a new http crate and am restarting CI.


text:
send_to doesn't work on the Windows

I find UdpSocket::send_to return Ok(None) on the Windows, but the client don't receive any response. The code:
fn transmit_handler(tx_recv: RxQueue, tx_only: UdpSocket) {
	loop {
		match tx_recv.recv() {
			Ok(q_res) => {
				match q_res.response.to_bytes() {
					Ok(bytes) => {
						let _ = tx_only.send_to(&bytes[..], &q_res.address);
					},
					Err(_) => {
						error!("Failed to decode response");
					}
				}
			},
			Err(_) => {
				info!("Shutting down Transmit Handler");
				break;
			}
		}
	}
}

@Covertness do you have a larger code sample that we could test out and run? It looks like errors may be ignored here which may be indicative of a problem?

@alexcrichton Yeah. I met this issue when I test the coap-rs. The project is A Constrained Application Protocol(CoAP) library. You can run examples or test cases to reproduce this issue.

@Covertness ah my point was that on this line the result is ignored, so it could perhaps be sending "would block" which is why it's not transmitting. This may work on Unix for now due to slightly different semantics, and if that error is handled it may work correctly on Windows.

@alexcrichton The result Ok(None) when I tested it on Windows. It doesn't seem like an error.

@Covertness Ok(None) indicates that it wasn't able to complete the request, it needs to wait until a readable event happens for the socket

@alexchrichton are we misusing the UDP socket in some way here? From a high level, we have two threads that have access to the UDPSocket (one has the original, one has a clone): One that is recv()ing, which dispatches the incoming messages to a threadpool, and a second thread that send()s, if the threadpool workers have a response (these responses are managed through a channel to the tx-thread).
Is the Ok(None) an indicator of an issue with how we use the library, or is it some kind of other issue?

@jamesmunns I haven't scrutinized the code in too much detail, but Ok(None) indicates that nothing was sent along the socket and it needs to be deferred to a later point somehow. The precise semantics of when I/O succeeds for fails are subtly different on Unix and Windows, but the contracts are the same.

@jamesmunns It seems that we can send the response only when a readable event happen. I will have a try.

@Covertness You could just give the TX thread a handle to the write side of the channel, which will just put it back in the queue to be consumed later.

It sounds like this was a local problem, so I'm going to close, but I'd be willing to help out if there are still problems!

authors: Covertness alexcrichton jamesmunns

repo: carllerche/mio


text:
Feature/inmemory h2 for tests

closes #8

Coverage increased (+17.7%) to 82.716% when pulling 41fc6dff08c19beffb1df0f690cb597df7173bb0 on feature/inmemory-h2-for-tests into 3402a1b18604956bfdd667940d724b098de465c2 on master.

authors: carlomorelli coveralls

repo: carlomorelli/project-muon


text:
🛑 OCI VPN is down

In 87b6b7c, OCI VPN (https://vpn-2.zaffonatto.it/) was down:

HTTP code: 530
Response time: 82 ms

Resolved: OCI VPN is back up in 203b0c9 after 3 hours, 27 minutes.

repo: carloszaffonatto/upptime


text:
Placeholders for SystemPrompt, CommitPrompt

Describe the need of your request
I want to make my prompts aware of my branch, project, and other Metadata the IDE does provide and place it in my custom-prompts.
For example:
{{BRANCH}}
{{PROJECT}}
{{CURRENT_DATE}}

So i am able to prompt the model to use the information.
Current_Branch: {{BRANCH}}
Create a commit message based on this diff, extract the TicketNumber <JIRA-xxxx> and set [TicketNumber] <commit message>
Proposed solution
Add a new function to process placeholders when getting the stored prompts.
new: java/ee/carlrobert/codegpt/util/PlaceholderUtil.java
modify:

ee.carlrobert.codegpt.settings.configuration.ConfigurationState#getSystemPrompt
ee.carlrobert.codegpt.settings.configuration.ConfigurationState#getCommitMessagePrompt

Additional context
No response

Please let me know if this will work for you and I will try to implement it.

Sure, this sounds like a good idea. I assume those placeholders will be configured inside a table?

authors: carlrobertoh rwese

repo: carlrobertoh/CodeGPT


text:
Code Completion for Azure

Describe the need of your request
Code Completion sounds fantastic, and I would love to test it. When do you plan to activate this awesome feature for Azure OpenAI or Custom OpenAI Providers?
Proposed solution
No response
Additional context
I like your Plugin and use it nearly every day

You should be able to use Azure for code-completions now (https://github.com/carlrobertoh/CodeGPT/pull/476)
In the Custom OpenAI Providers settings:

Thanks for the implemention. I tried the recent Azure GPT3 and GPT4 models, which only support the "chat/completations" API (not the normal "/completations" API). I cannot get it to run. The connection test fails (see screenshot).

That is correct, you would need to create a separate deployment using the gpt-3.5-turbo-instruct model to use the /completions api. Azure seems to ignore the model provided in the request body, and instead use the one associated with your deployment.

@sisve Thanks for your help and fast response! I got it working now with gpt-3.5-turbo-instruct. This wasn't documented well in the Azure OpenAI manuals.

authors: FabGoe PhilKes QuadStingray sisve


text:
[wrong challenge ]

on the mors on the zombies tab the challeng is down for 250 kills with full attachments but the challenge is actully get 50 merc kills

This is due to the WSP Stinger also having a camo called "Apocalyptic" so it's extracting the data from there. Might also be happening if there is another camos with same name for different guns.

Should be fixed in #77!

authors: V6Fuzzy carlssonemil maeriens

repo: carlssonemil/interstellar


text:
Proposal: Create "Instructor" badge in AMY

Background
All badged instructors in AMY have one of two badges: SWC and/or DC. We recently agreed that badged instructors are allowed to self-select to teach any lesson from any lesson community if they've completed instructor training and checkout. When workshop requests come in, there is typically a preference for a workshop of type SWC, DC or LC from the workshop host. We don't have great systems for tagging instructors from those areas to match them with workshop requests. Having specific badges could help select instructors based on their expressed preferences.
Proposal
I propose that we create a new badge type "Instructor" in AMY, and assign it to all existing badged instructors. Then from now-on we assign SWC, DC and LC badges based on instructor's personal preference to teach/not teach those types of workshops (provided they already have an instructor badge). For existing instructors, they will receive a new badge "Instructor", but keep their old badges. If this proposal is accepted, going forward we can give out "Instructor" badges at completion of check-out and allow self-assignment of other badges based on teaching preference.
To implement this we will need to:

Add the new badge to AMY
Update all currently badged instructors to have that badge assigned (Should be doable with a SQL Query)
Add LC instructor badge.
Put a process in place for gathering new instructor's teaching preferences

I'd very much like to hear input from  @maneesha @sheraaron  if this would create any problems to existing workflows or would even be helpful. I've mostly developed the idea based on discussions about tracking LC instructors and reaching out to them when LC workshop requests come in.
cc: @tracykteal @ErinBecker

It wouldn't create problems with workflows. For most workshops I don't actually look at which badge they have (or even what skill sets they have as  those are often out of date), just whether they are badged at all.  I trust instructors to self-select for what they can teach.
However I know that many of our badged instructors have allegiances and affinity for their badge so I think it's more of an issue from the point of view ofthe instructors. I'd want to know if our instructors are OK with not having a Carpentry-specific badge.

I agree with this proposal, with one change.
Agreed:

For existing instructors - add Instructor badge and retain old badges.

Change:

For new instructors - add Instructor badge and the badge for the
Carpentry that they did their teaching demo for. This is what we do
currently.

This change wouldn't require us to figure out a new process for asking
Instructors their teaching preferences and updating that in the system. It
is also extensible, as we can imagine also giving badges for particular
lesson sets (e.g. someone can be an Instructor, DC Instructor,
Genomics Instructor).
On Thu, Feb 22, 2018 at 1:47 AM, maneesha sane notifications@github.com
wrote:

It wouldn't create problems with workflows. For most workshops I don't
actually look at which badge they have (or even what skill sets they have
as those are often out of date), just whether they are badged at all. I
trust instructors to self-select for what they can teach.
However I know that many of our badged instructors have allegiances and
affinity for their badge so I think it's more of an issue from the point of
view ofthe instructors. I'd want to know if our instructors are OK with not
having a Carpentry-specific badge.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/swcarpentry/amy/issues/1232#issuecomment-367517640,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ASSbf4Tdzj38qxrHyM1axoe7SC2zwL8fks5tXKr5gaJpZM4SOgEP
.

--
Associate Director, The Carpentries

I agree with both Maneesha and Erin. I do not look at badges regularly. Only when awarding them. It would be nice to have documentation to know "which" badge they would like to have. Currently, if they made a SWC HW contribution but completed a DC Demo, I am not sure which badge to give them. I just choose. So this will help us in the future in allowing them to select.

Closing this as it is being discussed in #1162

authors: ErinBecker jduckles maneesha sheraaron

repo: carpentries/amy


text:
what if i want to use button tag?

what if i want to use a button tag instead of share-button what can i do?

You are able to use a class and pass the class name as the first argument into the share button. Just wondering, why don't you want to use the share-button element?
--
Henry Snopek
On Thu, Oct 29, 2015 at 9:48 AM, Irakli Safareli notifications@github.com
wrote:

what if i want to use a button tag instead of share-button what can i do?
Reply to this email directly or view it on GitHub:
https://github.com/carrot/share-button/issues/245

Also because you're not using the share-button element you'll have to modify the style sheet as it looks for that element rather than a class
--
Henry Snopek
On Thu, Oct 29, 2015 at 9:48 AM, Irakli Safareli notifications@github.com
wrote:

what if i want to use a button tag instead of share-button what can i do?
Reply to this email directly or view it on GitHub:
https://github.com/carrot/share-button/issues/245

I think better way would be to apply styles using class selector like .share-button or whatever and on javascript side don't use that tag  just select elements with class selector like .js-share-button. for example I wanted to use it on div element because i was using React and couldn't accomplish my coule without editing this library. or what if someone wants to use button element for accessibility reasons for example?

With react you should still be able to use a custom element. Otherwise regarding accessibility, I believe any custom element is recognized as a div. You can use a class as specified before, just change share-button in the stylus file to .you-custom-class.

you cant use div element and just path selector because of this line
https://github.com/carrot/share-button/blob/v1.0.2/src/share-button.js#L165
and you cant path some specific dom node because it will think that it's a configuration object
https://github.com/carrot/share-button/blob/v1.0.2/src/share-button.js#L19
think there should be way to:

pass dom node as an element to ShareButton
use any html element with some predefined class and

to accomplish these tasks I needed to change css and js :/

Oh yeah, totally forgot we did that. You're correct we don't allow just class/div's anymore because a custom tag is less complex. Excuse myself from earlier, didn't have my :coffee: yet. Otherwise @declandewet helped me out with his react knowledge and created an example which uses the latest release.

I'm using it on server and it doesn't works as expected https://gist.github.com/safareli/5e2a99b2fec9420ca608
But the point is that one should be able to

pass dom node as an element to ShareButton
use any html element with some predefined class and
use custom html in share button (in case someone wants to use some other icon or multiple icons for example and or whatever)

that you think about these points?

I'm unfortunately unable to debug the provided code without having the client side code as well. I'm not familiar enough with your code to fully debug it. If you provide more code I can dig further into the issue though.
Alright to touch on your points:

pass dom node as an element to ShareButton
use any html element with some predefined class

No longer needed because Custom Tags have been available since HTML 4 and act like standard div when styling. With more recent technology, like Web components, you can now render x-tags in javascript. With that in mind, share-button is not a web component because browser support. With that in mind, you're able to create custom elements with react or web components. Because share-button isn't a web component, all you need to do when you display share-button is to instantiate new ShareButton(opts).

use custom html in share button (in case someone wants to use some other icon or multiple icons for example and or whatever)

In share-button we create all the icons in our styles file. This full customization of the button without having to touch any html. We no longer use the Entypo font icon set because we can render all of the icons as background images.

ok whatever

authors: hhsnopek safareli

repo: carrot/share-button


text:
Remove WormMap and WormSet.

Since the latest improvements to HashMap, in practice WormMap is not useful compared to HashMap. For example, in Lucene, WormMap and HashMap were compared and HashMap was chosen.
If I had some improvements to bring, I would work on HashMap.
So, maybe we can remove WormMap and WormSet to reduce the HPPC lib?

If you decide to go ahead, then perhaps add an entry to changes.txt?

Thanks for searching usages. I agree it is not used much except in benchmarks.
I added an entry in CHANGES, in the 0.10.0 section since it is an API change I think.

Yep, looks great.

authors: bruno-roustant dweiss

repo: carrotsearch/hppc


text:
Make adding auth headers after init easier.

This is useful for me, so perhaps it is for others.
I want my auth info in once place, and my auth service will add the auth headers it knows about for
requests created by other view models, since they define those terms and not auth this allows better SRP adherence.

I'd also add this is working well for me currently.

repo: carson-katri/swift-request


text:
Allow enterprise github installations to be used

Currently, github.com is hard-coded. While Carson Bot is intended to be used on Symfony, I can see this being very useful for other people, and businesses may have an enterprise github installation. My suggestion be to remove the hard-coded values and provide a configuration option for these enterprise installations to point to the correct API endpoints.

Thanks for your suggestion! :) Our current focus is obviously to make things working for Symfony, but if you want to provide a PR for this feel free to submit one. Cheers!

Shall be closed IMHO.

authors: HexTitan nicolas-grekas webmozart

repo: carsonbot/carsonbot


text:
App CR should require one of serviceAccountName or cluster.

Describe the problem/challenge you have
Both serviceAccountName and cluster properties of the App CR are marked as optional. Anyone not understanding that one or the other is required may not even add either. When neither is added, then the App CR is still accepted and you end up with an error which you have to look in the App CR status of:
  status:
    conditions:
    - message: 'Preparing kapp: Expected service account or cluster specified'
      status: "True"
      type: ReconcileFailed

Further, when trying to delete the App in this situation it fails with it eventually exiting with the error:
kapp: Error: waiting on reconcile app/educates-training-platform (kappctrl.k14s.io/v1alpha1) namespace: default:
  Finished unsuccessfully (Reconcile failed:  (message: Preparing kapp: Expected service account or cluster specified))

resulting in you needing to manually delete the finalizer from the App resource.
The latter problem relates to issue https://github.com/vmware-tanzu/carvel-kapp-controller/issues/416.
Describe the solution you'd like
The CR definition should enforce that one or the other of serviceAccountName and cluster is required so that attempting to create an App CR with neither is rejected immediately.
My understanding is that this can be achieved in the CR schema by using:
anyOf:
- required:
  - serviceAccountName
- required:
  - cluster

Anything else you would like to add:
Having to look into the status of the App CR is non obvious so anything that avoids getting into that situation in the first place is a bonus. So failing early at the point of creating the App is better.

Vote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.

Hi team, I would like to take up this issue.

hi  @hemakshis ! Thanks for showing interest in taking this on.
This might be a helpful start:
https://github.com/vmware-tanzu/carvel-kapp-controller/blob/develop/pkg/apis/kappctrl/v1alpha1/types.go#L51-L55

We use https://github.com/kubernetes-sigs/controller-tools to generate our crds, the script we use can be found here - https://github.com/vmware-tanzu/carvel-kapp-controller/blob/develop/hack/gen-crds.sh
This uses kubebuilder underneath as a way to specify constraints (such as optional, nullable, int max etc ) on the structure of our custom resources.

Let us know how we can support you! You might also find our dev docs a good place to start on just getting this up and running.

@GrahamDumpleton   could you pls provide the file where I need to commit changes

authors: GrahamDumpleton hemakshis neil-hickey sarthaksarthak9

repo: carvel-dev/kapp-controller


text:
feat: add password Item forcibly when PasswordOn enabled

Signed-off-by: sh1luo 690898835@qq.com

Demo link: http://1.13.13.178:8000/

repo: casbin/casdoor


text:
How do I get permission and role information?

I only found the login related information in the sdk, how can I get, for example, the list of permissions, the user's role, and the user's permission after login?

Not supported for the time being. it on the basis of the development of casdoor & SwiftCasbin

This SDK is under development.Current version is 0.0.1.not recommended for use in production.future versions may have disruptive updates.If you really have requirements, you can extend the Casdoor class. Refer to API documentation（ https://door.casdoor.com/swagger/ ) . We expect you to contribute code to the community

This SDK is under development.Current version is 0.0.1.not recommended for use in production.future versions may have disruptive updates.If you really have requirements, you can extend the Casdoor class. Refer to API documentation（ https://door.casdoor.com/swagger/ ) . We expect you to contribute code to the community

Thanks, I'm not very good at reading swagger documentation yet, so I found this sdk. it seems I can't get around it.
I will try to submit pr if possible - as I do need to integrate casdoor in the project

@rakuyoMo PR is welcome, thanks for the contribution!

@kofj

authors: hsluoyz rakuyoMo xiaobeiswift

repo: casdoor/casdoor-ios-sdk


text:
face authentication without typing in the username

Hello there
Am trying to use casdoor to grant users access to a secure area  , and am trying to see if i can get the facial recognition to work without asking  users to type in the user name . basically  do a face match with all the saved user facial data and get username and authorize the user . I really like to implement this with casdoor because  its user friendly and admins love used it with other things . i also really like  the subscription  mode which means i can give access to users for a period of time .
any help in the right direction will do

Hello @hsluoyz

@addisflava github way is making PR. And if you don't know how to code about it, I don't think we can make this feature right finally.
Doing so without username is very difficult. This is why we don't do this. I thought you proposed this idea so you know how to do this. But you said you don't know how to do it. So my answer is that I can't promise that we can do this well at this stage.

authors: addisflava hsluoyz

repo: casdoor/casdoor


text:
feat: huyi sms

feat huyiwuxian sms provider

add license header and translate comments to eng

lgtm

authors: Curlson hsluoyz

repo: casdoor/go-sms-sender


text:
Show full example of getting XDG user directory

Per XDG base directory specification, getting an XDG user directory involves a bit more than reading an environment variable:

All paths set in these environment variables must be absolute. If an implementation encounters a relative path in any of these variables it should consider the path invalid and ignore it.
...
$XDG_CONFIG_HOME defines the base directory relative to which user-specific configuration files should be stored. If $XDG_CONFIG_HOME is either not set or empty, a default equal to $HOME/.config should be used.

This PR expands the example to fully show how to get an XDG user directory in a justfile.

Interesting!
This does at least slightly make the case that getting the XDG dirs correctly is painful, and should be better supported by just.
I wonder if this is something that users should actually care about. I.e., if the XDG_CONFIG_HOME isn't absolute, the user should really fix that, and the justfile shouldn't try to compensate, even if it is acting according to the spec.
Because if so you could do:
xdg_config_dir := env('XDG_CONFIG_HOME', home_directory() / '.config')

Which is much nicer.

Gotcha. And that isn't much shorter than the fully correct version which uses =~ '^/', so we might as well do that.

repo: casey/just


text:
Improve BIP

People are responding well to the ordinal theory post, and we're focusing on the sats-as-collectables use case at first, so I think the BIP should reflect this:

Remove all the speculation about future applications that use ordinals. (I still think these applications are possible, and some will come about, but I think it detracts from the initial, easy, concrete use-case.)
Add extensive comments to the specification code
Mention that dust limit isn't a problem
Mention that this is a playful art project, and that 99.99% of users don't need to know or care about ordinals.
Add degree notation.

I think this is mostly done.

repo: casey/ord


text:
Resurrect difficulty target PR

#750.

Mainly for linking blocks by number.

Done!


text:
Do not crash applying Box margins before view attach

⚠ STACKED PR ⚠
Refs #900

[x] CHANGELOG.md's "Unreleased" section has been updated, if applicable.

Looks like margins entirely not functioning on iOS. Going to file that for follow-up.

repo: cashapp/redwood


text:
Add examples of different use cases to the doc of load API

load API will stay the same, examples added to doc on when/how to use the  manifestUrls flow to fulfill different needs from downstream application.

closing this, as https://github.com/cashapp/zipline/pull/1223 has more updated docs.

repo: cashapp/zipline


text:
update for release 3.1.1

updates default version to release 3.1.1-2

:+1: LGTM


text:
Outdated cask: mdrp

Outdated cask: mdrp.
Info:

version: 6.0.0.
appcast url: https://www.macdvdripperpro.com/mdrp_sparkle5.xml.

6.0.2

Updated in #18401.

repo: caskroom/homebrew-cask