Not working with nuxt 2.17

tsparticles is broken after upgrading to nuxt 2.17 (I also created fresh nuxt app and got same error).
console output for build:
>  ERROR  Failed to compile with 26 errors                                                            friendly-errors 11:20:03

 ERROR  in ./node_modules/tsparticles-engine/esm/Utils/ColorUtils.js                                friendly-errors 11:20:03

Module parse failed: Unexpected token (116:31)                                                      friendly-errors 11:20:03
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
| }
| export function stringToAlpha(input) {
>     return stringToRgba(input)?.a;
| }
| export function stringToRgb(input) {
                                                                                friendly-errors 11:20:03
 @ ./node_modules/tsparticles-engine/esm/index.js 4:0-53 7:0-15 8:0-15
 @ ./node_modules/vue2-particles/dist/vue2-particles.js
 @ ./plugins/vue2-particles.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./node_modules/eventsource-polyfill/dist/browserify-eventsource.js (webpack)-hot-middleware/client.js?reload=true&timeout=30000&ansiColors=&overlayStyles=&path=%2F__webpack_hmr%2Fclient&name=client ./.nuxt/client.js
                                                                                friendly-errors 11:20:03

 ERROR  in ./node_modules/tsparticles-engine/esm/Utils/NumberUtils.js                               friendly-errors 11:20:03

Module parse failed: Unexpected token (120:27)                                                      friendly-errors 11:20:03
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
| export function calcPositionOrRandomFromSize(data) {
|     return {
>         x: ((data.position?.x ?? getRandom() * 100) * data.size.width) / 100,
|         y: ((data.position?.y ?? getRandom() * 100) * data.size.height) / 100,
|     };
                                                                                friendly-errors 11:20:03
 @ ./node_modules/tsparticles-engine/esm/Core/Utils/Circle.js 2:0-54 9:15-26
 @ ./node_modules/tsparticles-engine/esm/exports.js
 @ ./node_modules/tsparticles-engine/esm/index.js
 @ ./node_modules/vue2-particles/dist/vue2-particles.js
 @ ./plugins/vue2-particles.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./node_modules/eventsource-polyfill/dist/browserify-eventsource.js (webpack)-hot-middleware/client.js?reload=true&timeout=30000&ansiColors=&overlayStyles=&path=%2F__webpack_hmr%2Fclient&name=client ./.nuxt/client.js
                                                                                friendly-errors 11:20:03

 ERROR  in ./node_modules/tsparticles-engine/esm/Options/Classes/Particles/Move/OutModes.js         friendly-errors 11:20:03

Module parse failed: Unexpected token (12:35)                                                       friendly-errors 11:20:03
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
|             this.default = data.default;
|         }
>         this.bottom = data.bottom ?? data.default;
|         this.left = data.left ?? data.default;
|         this.right = data.right ?? data.default;
                                                                                friendly-errors 11:20:03
 @ ./node_modules/tsparticles-engine/esm/exports.js 67:0-58 67:0-58
 @ ./node_modules/tsparticles-engine/esm/index.js
 @ ./node_modules/vue2-particles/dist/vue2-particles.js
 @ ./plugins/vue2-particles.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./node_modules/eventsource-polyfill/dist/browserify-eventsource.js (webpack)-hot-middleware/client.js?reload=true&timeout=30000&ansiColors=&overlayStyles=&path=%2F__webpack_hmr%2Fclient&name=client ./.nuxt/client.js
                                                                                friendly-errors 11:20:03

 ERROR  in ./node_modules/tsparticles-engine/esm/Options/Classes/Options.js                         friendly-errors 11:20:03

Module parse failed: Unexpected token (14:101)                                                      friendly-errors 11:20:03
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
|     constructor(engine, container) {
|         this._findDefaultTheme = (mode) => {
>             return (this.themes.find((theme) => theme.default.value && theme.default.mode === mode) ??
|                 this.themes.find((theme) => theme.default.value && theme.default.mode === "any"));
|         };
                                                                                friendly-errors 11:20:03
 @ ./node_modules/tsparticles-engine/esm/exports.js 52:0-42 52:0-42
 @ ./node_modules/tsparticles-engine/esm/index.js
 @ ./node_modules/vue2-particles/dist/vue2-particles.js
 @ ./plugins/vue2-particles.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./node_modules/eventsource-polyfill/dist/browserify-eventsource.js (webpack)-hot-middleware/client.js?reload=true&timeout=30000&ansiColors=&overlayStyles=&path=%2F__webpack_hmr%2Fclient&name=client ./.nuxt/client.js
                                                                                friendly-errors 11:20:03

 ERROR  in ./node_modules/tsparticles-engine/esm/Options/Classes/Particles/Opacity/OpacityAnimation.js

Module parse failed: Unexpected token (15:17)                                                       friendly-errors 11:20:03
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
|     }
|     load(data) {
>         if (data?.opacity_min !== undefined && data.minimumValue === undefined) {
|             data.minimumValue = data.opacity_min;
|         }
                                                                                friendly-errors 11:20:03
 @ ./node_modules/tsparticles-engine/esm/exports.js 74:0-69 74:0-69
 @ ./node_modules/tsparticles-engine/esm/index.js
 @ ./node_modules/vue2-particles/dist/vue2-particles.js
 @ ./plugins/vue2-particles.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./node_modules/eventsource-polyfill/dist/browserify-eventsource.js (webpack)-hot-middleware/client.js?reload=true&timeout=30000&ansiColors=&overlayStyles=&path=%2F__webpack_hmr%2Fclient&name=client ./.nuxt/client.js
                                                                                friendly-errors 11:20:03

 ERROR  in ./node_modules/tsparticles-engine/esm/Options/Classes/Particles/Size/SizeAnimation.js    friendly-errors 11:20:03

Module parse failed: Unexpected token (15:17)                                                       friendly-errors 11:20:03
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
|     }
|     load(data) {
>         if (data?.size_min !== undefined && data.minimumValue === undefined) {
|             data.minimumValue = data.size_min;
|         }
                                                                                friendly-errors 11:20:03
 @ ./node_modules/tsparticles-engine/esm/exports.js 77:0-63 77:0-63
 @ ./node_modules/tsparticles-engine/esm/index.js
 @ ./node_modules/vue2-particles/dist/vue2-particles.js
 @ ./plugins/vue2-particles.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./node_modules/eventsource-polyfill/dist/browserify-eventsource.js (webpack)-hot-middleware/client.js?reload=true&timeout=30000&ansiColors=&overlayStyles=&path=%2F__webpack_hmr%2Fclient&name=client ./.nuxt/client.js
                                                                                friendly-errors 11:20:03

 ERROR  in ./node_modules/tsparticles-engine/esm/Utils/CanvasUtils.js                               friendly-errors 11:20:03

Module parse failed: Unexpected token (16:35)                                                       friendly-errors 11:20:03
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
| }
| export function paintBase(context, dimension, baseColor) {
>     context.fillStyle = baseColor ?? "rgba(0,0,0,0)";
|     context.fillRect(0, 0, dimension.width, dimension.height);
| }
                                                                                friendly-errors 11:20:03
 @ ./node_modules/tsparticles-engine/esm/exports.js 83:0-36 83:0-36
 @ ./node_modules/tsparticles-engine/esm/index.js
 @ ./node_modules/vue2-particles/dist/vue2-particles.js
 @ ./plugins/vue2-particles.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./node_modules/eventsource-polyfill/dist/browserify-eventsource.js (webpack)-hot-middleware/client.js?reload=true&timeout=30000&ansiColors=&overlayStyles=&path=%2F__webpack_hmr%2Fclient&name=client ./.nuxt/client.js
                                                                                friendly-errors 11:20:03

 ERROR  in ./node_modules/tsparticles-engine/esm/Options/Classes/Particles/Shape/Shape.js           friendly-errors 11:20:03

Module parse failed: Unexpected token (16:70)                                                       friendly-errors 11:20:03
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
|                 this.options[altKey] = emptyValue;
|             }
>             this.options[mainKey] = deepExtend(this.options[mainKey] ?? emptyValue, item);
|             if (!this.options[altKey] || altOverride) {
|                 this.options[altKey] = deepExtend(this.options[altKey] ?? emptyValue, item);
                                                                                friendly-errors 11:20:03
 @ ./node_modules/tsparticles-engine/esm/exports.js 75:0-56 75:0-56
 @ ./node_modules/tsparticles-engine/esm/index.js
 @ ./node_modules/vue2-particles/dist/vue2-particles.js
 @ ./plugins/vue2-particles.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./node_modules/eventsource-polyfill/dist/browserify-eventsource.js (webpack)-hot-middleware/client.js?reload=true&timeout=30000&ansiColors=&overlayStyles=&path=%2F__webpack_hmr%2Fclient&name=client ./.nuxt/client.js
                                                                                friendly-errors 11:20:03

 ERROR  in ./node_modules/tsparticles-engine/esm/Core/Utils/Vector3d.js                             friendly-errors 11:20:03

Module parse failed: Unexpected token (17:24)                                                       friendly-errors 11:20:03
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
|             this.x = xOrCoords;
|             this.y = y;
>             this.z = z ?? 0;
|         }
|         else {
                                                                                friendly-errors 11:20:03
 @ ./node_modules/tsparticles-engine/esm/exports.js 9:0-38 9:0-38
 @ ./node_modules/tsparticles-engine/esm/index.js
 @ ./node_modules/vue2-particles/dist/vue2-particles.js
 @ ./plugins/vue2-particles.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./node_modules/eventsource-polyfill/dist/browserify-eventsource.js (webpack)-hot-middleware/client.js?reload=true&timeout=30000&ansiColors=&overlayStyles=&path=%2F__webpack_hmr%2Fclient&name=client ./.nuxt/client.js
                                                                                friendly-errors 11:20:03

 ERROR  in ./node_modules/tsparticles-engine/esm/Options/Classes/OptionsColor.js                    friendly-errors 11:20:03

Module parse failed: Unexpected token (19:17)                                                       friendly-errors 11:20:03
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
|     }
|     load(data) {
>         if (data?.value === undefined) {
|             return;
|         }
                                                                                friendly-errors 11:20:03
 @ ./node_modules/tsparticles-engine/esm/exports.js 53:0-47 53:0-47
 @ ./node_modules/tsparticles-engine/esm/index.js
 @ ./node_modules/vue2-particles/dist/vue2-particles.js
 @ ./plugins/vue2-particles.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./node_modules/eventsource-polyfill/dist/browserify-eventsource.js (webpack)-hot-middleware/client.js?reload=true&timeout=30000&ansiColors=&overlayStyles=&path=%2F__webpack_hmr%2Fclient&name=client ./.nuxt/client.js
                                                                                friendly-errors 11:20:03

 ERROR  in ./node_modules/tsparticles-engine/esm/Options/Classes/Particles/Number/ParticlesNumber.js

Module parse failed: Unexpected token (19:34)                                                       friendly-errors 11:20:03
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
|         }
|         this.density.load(data.density);
>         const limit = data.limit ?? data.max;
|         if (limit !== undefined) {
|             this.limit = limit;
                                                                                friendly-errors 11:20:03
 @ ./node_modules/tsparticles-engine/esm/exports.js 71:0-67 71:0-67
 @ ./node_modules/tsparticles-engine/esm/index.js
 @ ./node_modules/vue2-particles/dist/vue2-particles.js
 @ ./plugins/vue2-particles.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./node_modules/eventsource-polyfill/dist/browserify-eventsource.js (webpack)-hot-middleware/client.js?reload=true&timeout=30000&ansiColors=&overlayStyles=&path=%2F__webpack_hmr%2Fclient&name=client ./.nuxt/client.js
                                                                                friendly-errors 11:20:03

 ERROR  in ./node_modules/tsparticles-engine/esm/Options/Classes/Interactivity/Interactivity.js     friendly-errors 11:20:03

Module parse failed: Unexpected token (19:42)                                                       friendly-errors 11:20:03
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
|             return;
|         }
>         const detectsOn = data.detectsOn ?? data.detect_on;
|         if (detectsOn !== undefined) {
|             this.detectsOn = detectsOn;
                                                                                friendly-errors 11:20:03
 @ ./node_modules/tsparticles-engine/esm/exports.js 49:0-62 49:0-62
 @ ./node_modules/tsparticles-engine/esm/index.js
 @ ./node_modules/vue2-particles/dist/vue2-particles.js
 @ ./plugins/vue2-particles.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./node_modules/eventsource-polyfill/dist/browserify-eventsource.js (webpack)-hot-middleware/client.js?reload=true&timeout=30000&ansiColors=&overlayStyles=&path=%2F__webpack_hmr%2Fclient&name=client ./.nuxt/client.js
                                                                                friendly-errors 11:20:03

 ERROR  in ./node_modules/tsparticles-engine/esm/Options/Classes/Particles/Size/Size.js             friendly-errors 11:20:03

Module parse failed: Unexpected token (22:42)                                                       friendly-errors 11:20:03
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
|             return;
|         }
>         const animation = data.animation ?? data.anim;
|         if (animation !== undefined) {
|             this.animation.load(animation);
                                                                                friendly-errors 11:20:03
 @ ./node_modules/tsparticles-engine/esm/exports.js 76:0-54 76:0-54
 @ ./node_modules/tsparticles-engine/esm/index.js
 @ ./node_modules/vue2-particles/dist/vue2-particles.js
 @ ./plugins/vue2-particles.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./node_modules/eventsource-polyfill/dist/browserify-eventsource.js (webpack)-hot-middleware/client.js?reload=true&timeout=30000&ansiColors=&overlayStyles=&path=%2F__webpack_hmr%2Fclient&name=client ./.nuxt/client.js
                                                                                friendly-errors 11:20:03

 ERROR  in ./node_modules/tsparticles-engine/esm/Options/Classes/Particles/Opacity/Opacity.js       friendly-errors 11:20:03

Module parse failed: Unexpected token (22:42)                                                       friendly-errors 11:20:03
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
|         }
|         super.load(data);
>         const animation = data.animation ?? data.anim;
|         if (animation !== undefined) {
|             this.animation.load(animation);
                                                                                friendly-errors 11:20:03
 @ ./node_modules/tsparticles-engine/esm/exports.js 73:0-60 73:0-60
 @ ./node_modules/tsparticles-engine/esm/index.js
 @ ./node_modules/vue2-particles/dist/vue2-particles.js
 @ ./plugins/vue2-particles.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./node_modules/eventsource-polyfill/dist/browserify-eventsource.js (webpack)-hot-middleware/client.js?reload=true&timeout=30000&ansiColors=&overlayStyles=&path=%2F__webpack_hmr%2Fclient&name=client ./.nuxt/client.js
                                                                                friendly-errors 11:20:03

 ERROR  in ./node_modules/tsparticles-engine/esm/Options/Classes/Interactivity/Events/DivEvent.js   friendly-errors 11:20:03

Module parse failed: Unexpected token (31:30)                                                       friendly-errors 11:20:03
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
|             return;
|         }
>         const ids = data.ids ?? data.elementId ?? data.el;
|         if (ids !== undefined) {
|             this.ids = ids;
                                                                                friendly-errors 11:20:03
 @ ./node_modules/tsparticles-engine/esm/exports.js 42:0-64 42:0-64 44:0-64 44:0-64
 @ ./node_modules/tsparticles-engine/esm/index.js
 @ ./node_modules/vue2-particles/dist/vue2-particles.js
 @ ./plugins/vue2-particles.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./node_modules/eventsource-polyfill/dist/browserify-eventsource.js (webpack)-hot-middleware/client.js?reload=true&timeout=30000&ansiColors=&overlayStyles=&path=%2F__webpack_hmr%2Fclient&name=client ./.nuxt/client.js
                                                                                friendly-errors 11:20:03

 ERROR  in ./node_modules/tsparticles-engine/esm/Options/Classes/Particles/Number/ParticlesDensity.js

Module parse failed: Unexpected token (32:34)                                                       friendly-errors 11:20:03
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
|             this.enable = data.enable;
|         }
>         const width = data.width ?? data.area ?? data.value_area;
|         if (width !== undefined) {
|             this.width = width;
                                                                                friendly-errors 11:20:03
 @ ./node_modules/tsparticles-engine/esm/exports.js 72:0-68 72:0-68
 @ ./node_modules/tsparticles-engine/esm/index.js
 @ ./node_modules/vue2-particles/dist/vue2-particles.js
 @ ./plugins/vue2-particles.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./node_modules/eventsource-polyfill/dist/browserify-eventsource.js (webpack)-hot-middleware/client.js?reload=true&timeout=30000&ansiColors=&overlayStyles=&path=%2F__webpack_hmr%2Fclient&name=client ./.nuxt/client.js
                                                                                friendly-errors 11:20:03

 ERROR  in ./node_modules/tsparticles-engine/esm/engine.js                                          friendly-errors 11:20:03

Module parse failed: Unexpected token (32:49)                                                       friendly-errors 11:20:03
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
|         }
|         else {
>             this._configs.set(nameOrConfig.name ?? "default", nameOrConfig);
|         }
|     }
                                                                                friendly-errors 11:20:03
 @ ./node_modules/tsparticles-engine/esm/index.js 1:0-34 9:24-30
 @ ./node_modules/vue2-particles/dist/vue2-particles.js
 @ ./plugins/vue2-particles.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./node_modules/eventsource-polyfill/dist/browserify-eventsource.js (webpack)-hot-middleware/client.js?reload=true&timeout=30000&ansiColors=&overlayStyles=&path=%2F__webpack_hmr%2Fclient&name=client ./.nuxt/client.js
                                                                                friendly-errors 11:20:03

 ERROR  in ./node_modules/tsparticles-engine/esm/Options/Classes/Particles/Move/MoveAttract.js      friendly-errors 11:20:03

Module parse failed: Unexpected token (33:36)                                                       friendly-errors 11:20:03
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
|             this.enable = data.enable;
|         }
>         const rotateX = data.rotate?.x ?? data.rotateX;
|         if (rotateX !== undefined) {
|             this.rotate.x = rotateX;
                                                                                friendly-errors 11:20:03
 @ ./node_modules/tsparticles-engine/esm/exports.js 62:0-61 62:0-61
 @ ./node_modules/tsparticles-engine/esm/index.js
 @ ./node_modules/vue2-particles/dist/vue2-particles.js
 @ ./plugins/vue2-particles.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./node_modules/eventsource-polyfill/dist/browserify-eventsource.js (webpack)-hot-middleware/client.js?reload=true&timeout=30000&ansiColors=&overlayStyles=&path=%2F__webpack_hmr%2Fclient&name=client ./.nuxt/client.js
                                                                                friendly-errors 11:20:03

 ERROR  in ./node_modules/tsparticles-engine/esm/Options/Classes/Interactivity/Events/Events.js     friendly-errors 11:20:03

Module parse failed: Unexpected token (35:40)                                                       friendly-errors 11:20:03
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
|             return;
|         }
>         this.onClick.load(data.onClick ?? data.onclick);
|         const onDiv = data.onDiv ?? data.ondiv;
|         if (onDiv !== undefined) {
                                                                                friendly-errors 11:20:03
 @ ./node_modules/tsparticles-engine/esm/exports.js 45:0-62 45:0-62
 @ ./node_modules/tsparticles-engine/esm/index.js
 @ ./node_modules/vue2-particles/dist/vue2-particles.js
 @ ./plugins/vue2-particles.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./node_modules/eventsource-polyfill/dist/browserify-eventsource.js (webpack)-hot-middleware/client.js?reload=true&timeout=30000&ansiColors=&overlayStyles=&path=%2F__webpack_hmr%2Fclient&name=client ./.nuxt/client.js
                                                                                friendly-errors 11:20:03

 ERROR  in ./node_modules/tsparticles-engine/esm/Options/Classes/ValueWithRandom.js                 friendly-errors 11:20:03

Module parse failed: Unexpected token (40:42)                                                       friendly-errors 11:20:03
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
|             return;
|         }
>         const animation = data.animation ?? data.anim;
|         if (animation !== undefined) {
|             this.animation.load(animation);
                                                                                friendly-errors 11:20:03
 @ ./node_modules/tsparticles-engine/esm/Options/Classes/Particles/Bounce/ParticlesBounceFactor.js 1:0-56 2:43-58
 @ ./node_modules/tsparticles-engine/esm/exports.js
 @ ./node_modules/tsparticles-engine/esm/index.js
 @ ./node_modules/vue2-particles/dist/vue2-particles.js
 @ ./plugins/vue2-particles.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./node_modules/eventsource-polyfill/dist/browserify-eventsource.js (webpack)-hot-middleware/client.js?reload=true&timeout=30000&ansiColors=&overlayStyles=&path=%2F__webpack_hmr%2Fclient&name=client ./.nuxt/client.js
                                                                                friendly-errors 11:20:03

 ERROR  in ./node_modules/tsparticles-engine/esm/Options/Classes/Particles/ParticlesOptions.js      friendly-errors 11:20:03

Module parse failed: Unexpected token (42:72)                                                       friendly-errors 11:20:03
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
|                 const item = data.groups[group];
|                 if (item !== undefined) {
>                     this.groups[group] = deepExtend(this.groups[group] ?? {}, item);
|                 }
|             }
                                                                                friendly-errors 11:20:03
 @ ./node_modules/tsparticles-engine/esm/exports.js 59:0-61 59:0-61
 @ ./node_modules/tsparticles-engine/esm/index.js
 @ ./node_modules/vue2-particles/dist/vue2-particles.js
 @ ./plugins/vue2-particles.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./node_modules/eventsource-polyfill/dist/browserify-eventsource.js (webpack)-hot-middleware/client.js?reload=true&timeout=30000&ansiColors=&overlayStyles=&path=%2F__webpack_hmr%2Fclient&name=client ./.nuxt/client.js
                                                                                friendly-errors 11:20:03

 ERROR  in ./node_modules/tsparticles-engine/esm/Utils/Utils.js                                     friendly-errors 11:20:03

Module parse failed: Unexpected token (51:45)                                                       friendly-errors 11:20:03
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
| export async function loadFont(font, weight) {
|     try {
>         await document.fonts.load(`${weight ?? "400"} 36px '${font ?? "Verdana"}'`);
|     }
|     catch {
                                                                                friendly-errors 11:20:03
 @ ./node_modules/tsparticles-engine/esm/index.js 5:0-38 11:5-10
 @ ./node_modules/vue2-particles/dist/vue2-particles.js
 @ ./plugins/vue2-particles.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./node_modules/eventsource-polyfill/dist/browserify-eventsource.js (webpack)-hot-middleware/client.js?reload=true&timeout=30000&ansiColors=&overlayStyles=&path=%2F__webpack_hmr%2Fclient&name=client ./.nuxt/client.js
                                                                                friendly-errors 11:20:03

 ERROR  in ./node_modules/tsparticles-engine/esm/Utils/RgbColorManager.js                           friendly-errors 11:20:03

Module parse failed: Unexpected token (8:67)                                                        friendly-errors 11:20:03
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
|     }
|     handleColor(color) {
>         const colorValue = color.value, rgbColor = colorValue.rgb ?? color.value;
|         if (rgbColor.r !== undefined) {
|             return rgbColor;
                                                                                friendly-errors 11:20:03
 @ ./node_modules/tsparticles-engine/esm/index.js 3:0-58 6:28-43
 @ ./node_modules/vue2-particles/dist/vue2-particles.js
 @ ./plugins/vue2-particles.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./node_modules/eventsource-polyfill/dist/browserify-eventsource.js (webpack)-hot-middleware/client.js?reload=true&timeout=30000&ansiColors=&overlayStyles=&path=%2F__webpack_hmr%2Fclient&name=client ./.nuxt/client.js
                                                                                friendly-errors 11:20:03

 ERROR  in ./node_modules/tsparticles-engine/esm/Options/Classes/Particles/Move/Move.js             friendly-errors 11:20:03

Module parse failed: Unexpected token (90:40)                                                       friendly-errors 11:20:03
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
|         }
|         this.gravity.load(data.gravity);
>         const outModes = data.outModes ?? data.outMode ?? data.out_mode;
|         if (outModes !== undefined) {
|             if (typeof outModes === "object") {
                                                                                friendly-errors 11:20:03
 @ ./node_modules/tsparticles-engine/esm/exports.js 63:0-54 63:0-54
 @ ./node_modules/tsparticles-engine/esm/index.js
 @ ./node_modules/vue2-particles/dist/vue2-particles.js
 @ ./plugins/vue2-particles.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./node_modules/eventsource-polyfill/dist/browserify-eventsource.js (webpack)-hot-middleware/client.js?reload=true&timeout=30000&ansiColors=&overlayStyles=&path=%2F__webpack_hmr%2Fclient&name=client ./.nuxt/client.js
                                                                                friendly-errors 11:20:03

 ERROR  in ./node_modules/tsparticles-engine/esm/Options/Classes/ManualParticle.js                  friendly-errors 11:20:03

Module parse failed: Unexpected token (9:36)                                                        friendly-errors 11:20:03
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
|         if (data.position) {
|             this.position = {
>                 x: data.position.x ?? 50,
|                 y: data.position.y ?? 50,
|                 mode: data.position.mode ?? "percent",
                                                                                friendly-errors 11:20:03
 @ ./node_modules/tsparticles-engine/esm/exports.js 51:0-49 51:0-49
 @ ./node_modules/tsparticles-engine/esm/index.js
 @ ./node_modules/vue2-particles/dist/vue2-particles.js
 @ ./plugins/vue2-particles.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./node_modules/eventsource-polyfill/dist/browserify-eventsource.js (webpack)-hot-middleware/client.js?reload=true&timeout=30000&ansiColors=&overlayStyles=&path=%2F__webpack_hmr%2Fclient&name=client ./.nuxt/client.js
                                                                                friendly-errors 11:20:03

 ERROR  in ./node_modules/tsparticles-engine/esm/Utils/HslColorManager.js                           friendly-errors 11:20:03

Module parse failed: Unexpected token (9:67)                                                        friendly-errors 11:20:03
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
|     }
|     handleColor(color) {
>         const colorValue = color.value, hslColor = colorValue.hsl ?? color.value;
|         if (hslColor.h !== undefined && hslColor.s !== undefined && hslColor.l !== undefined) {
|             return hslToRgb(hslColor);
                                                                                friendly-errors 11:20:03
 @ ./node_modules/tsparticles-engine/esm/index.js 2:0-58 6:69-84
 @ ./node_modules/vue2-particles/dist/vue2-particles.js
 @ ./plugins/vue2-particles.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./node_modules/eventsource-polyfill/dist/browserify-eventsource.js (webpack)-hot-middleware/client.js?reload=true&timeout=30000&ansiColors=&overlayStyles=&path=%2F__webpack_hmr%2Fclient&name=client ./.nuxt/client.js

Related issue: https://github.com/nuxt/nuxt/issues/9221#issuecomment-830012118
You need to add tsparticles-engine and other tsparticles imported libraries like this:
https://github.com/tsparticles/vue2/blob/2bcda535a0450886159e681b4f2dd4dc4318c1b1/apps/nuxt2/nuxt.config.js#L47-L49

Thanks for your response, after adding build transpile it now say "File was processed with these loaders" but still get few errors (i also tried to add tsparticles-plugin-emitters, tsparticles-move-base to transpile but still no luck)
ERROR in ./node_modules/tsparticles-plugin-emitters/cjs/EmitterInstance.js 109:22
Module parse failed: Unexpected token (109:22)
File was processed with these loaders:
 * ./node_modules/babel-loader/lib/index.js
You may need an additional loader to handle the result of these loaders.
|     this._startParticlesAdded = false;
|     let particlesOptions = (0, tsparticles_engine_1.deepExtend)({}, this.options.particles);
>     particlesOptions ??= {};
|     particlesOptions.move ??= {};
|     particlesOptions.move.direction ??= this.options.direction;
 @ ./node_modules/tsparticles-plugin-emitters/cjs/Emitters.js 9:26-54
 @ ./node_modules/tsparticles-plugin-emitters/cjs/index.js
 @ ./node_modules/tsparticles/cjs/index.js
 @ ./node_modules/babel-loader/lib??ref--2-0!./node_modules/@nuxt/components/dist/loader.js??ref--0-0!./node_modules/vue-loader/lib??vue-loader-options!./pages/index.vue?vue&type=script&lang=js&
 @ ./pages/index.vue?vue&type=script&lang=js&
 @ ./pages/index.vue
 @ ./.nuxt/router.js
 @ ./.nuxt/index.js
 @ ./.nuxt/server.js
 @ multi<EMAIL_ADDRESS>./.nuxt/server.js

ERROR in ./node_modules/tsparticles-engine/cjs/Core/Utils/FrameManager.js 25:31
Module parse failed: Unexpected token (25:31)
File was processed with these loaders:
 * ./node_modules/babel-loader/lib/index.js
You may need an additional loader to handle the result of these loaders.
|         return;
|       }
>       container.lastFrameTime ??= timestamp;
|       const delta = initDelta(timestamp - container.lastFrameTime, container.fpsLimit, container.smooth);
|       container.addLifeTime(delta.value);
 @ ./node_modules/tsparticles-engine/cjs/Core/Container.js 23:23-54
 @ ./node_modules/tsparticles-engine/cjs/Core/Loader.js
 @ ./node_modules/tsparticles-engine/cjs/engine.js
 @ ./node_modules/tsparticles-engine/cjs/index.js
 @ ./node_modules/tsparticles-plugin-emitters/cjs/index.js
 @ ./node_modules/tsparticles/cjs/index.js
 @ ./node_modules/babel-loader/lib??ref--2-0!./node_modules/@nuxt/components/dist/loader.js??ref--0-0!./node_modules/vue-loader/lib??vue-loader-options!./pages/index.vue?vue&type=script&lang=js&
 @ ./pages/index.vue?vue&type=script&lang=js&
 @ ./pages/index.vue
 @ ./.nuxt/router.js
 @ ./.nuxt/index.js
 @ ./.nuxt/server.js
 @ multi<EMAIL_ADDRESS>./.nuxt/server.js

ERROR in ./node_modules/tsparticles-move-base/cjs/BaseMover.js 64:46
Module parse failed: Unexpected token (64:46)
File was processed with these loaders:
 * ./node_modules/babel-loader/lib/index.js
You may need an additional loader to handle the result of these loaders.
|       pxRatio = container.retina.pixelRatio,
|       slowFactor = (0, Utils_1.getProximitySpeedFactor)(particle),
>       baseSpeed = (particle.retina.moveSpeed ??= (0, tsparticles_engine_1.getRangeValue)(moveOptions.speed) * pxRatio) * container.retina.reduceFactor,
|       moveDrift = particle.retina.moveDrift ??= (0, tsparticles_engine_1.getRangeValue)(particle.options.move.drift) * pxRatio,
|       maxSize = (0, tsparticles_engine_1.getRangeMax)(particleOptions.size.value) * pxRatio,
 @ ./node_modules/tsparticles-move-base/cjs/index.js 7:20-42
 @ ./node_modules/tsparticles-slim/cjs/index.js
 @ ./node_modules/tsparticles/cjs/index.js
 @ ./node_modules/babel-loader/lib??ref--2-0!./node_modules/@nuxt/components/dist/loader.js??ref--0-0!./node_modules/vue-loader/lib??vue-loader-options!./pages/index.vue?vue&type=script&lang=js&
 @ ./pages/index.vue?vue&type=script&lang=js&
 @ ./pages/index.vue
 @ ./.nuxt/router.js
 @ ./.nuxt/index.js
 @ ./.nuxt/server.js
 @ multi<EMAIL_ADDRESS>./.nuxt/server.js

Try adding these packages too:
https://github.com/tsparticles/vue2/blob/e2bbc05e3a79494a64f61ef3668036e6f3c3153b/apps/nuxt2/package.json#L29-L31

That didn't help, i just checked sample app and noticed that you added
  // Disable server-side rendering: https://go.nuxtjs.dev/ssr-mode
  ssr: false,

  // Target: https://go.nuxtjs.dev/config-target
  target: "static",

However, I am using ssr and target is server (these are also the default values in nuxt) and then I get these errors that I have posted above.

Have you created the Nuxt plugin file?
You need to add it to your Nuxt config like this:
https://github.com/tsparticles/vue2/blob/e2bbc05e3a79494a64f61ef3668036e6f3c3153b/apps/nuxt2/nuxt.config.js#L27-L32
and it MUST be "client", it can't work server side.
You can see the sample plugin here:
https://github.com/tsparticles/vue2/blob/e2bbc05e3a79494a64f61ef3668036e6f3c3153b/apps/nuxt2/plugins/vue2-particles.ts#L1-L4
In my app I didn't use SSR since I don't need it for a test application, but since the plugin must be installed as a client one it shouldn't matter.

Yes i did that, just change
ssr to true and target to server and try to build your test app, it throw errors.

Yeah it works this way:
async particlesInit(engine) {
  if (process.client) {
    const { loadFull } = await import("tsparticles")
    await loadFull(engine)
  }
},


Tag-Swipe -> MapView -> TagSwipe Crashes on Save

Sometimes if I'm in the tag view, go back to the map view, then go back to the tag view, then save to ODK Collect, the app crashes.
Looking at the log, there is a null pointer exception for OSM Element keys and values. Perhaps the selected OSMElement somehow gets lost in the mix.

In investigating further, it appears that the actual crash happens when we return to ODK Collect. Perhaps some sort of inconsistency is introduced to the intent's extras?
The MapActivity is finished, and ODK Collect is returned to.
https://github.com/AmericanRedCross/OpenMapKitAndroid/blob/6585d499064745a94bccccc544d9be4a98be34d4/app/src/main/java/org/redcross/openmapkit/MapActivity.java#L667

After a bit of debugging, I'm not seeing any errors in logcat *:E.
The crash occurs in ODK Collect, though I think OpenMapKit is sending Activity.RESULT_CANCELED to ODK Collect in onActivityResult.
https://github.com/opendatakit/collect/blob/60aae502fd6cc8877576ff69f6742c489d85b82f/collect_app/src/main/java/org/odk/collect/android/activities/FormEntryActivity.java#L574
This is strange, because we explicitly set Activity.RESULT_OK ever time, including if the user goes back and forth between TagSwipe.
https://github.com/AmericanRedCross/OpenMapKitAndroid/blob/c107c89f48065c1fab93790257f8f997be2cee35/app/src/main/java/org/redcross/openmapkit/MapActivity.java#L691
My only guess is that there is some error (though it's not getting logged in logcat?) that is popping both TagSwipe and MapActivity off the stack outside of this line of code?


Navs and tabs should look the same with

Elements like navs and tabs are mostly used with  in the docs. Anyhow modern JavaScript apps (e.g. using React or Angular) often do not use  elements to trigger internal ui events.
IMO It should be possible to use this elements CSS with buttons, too and they should look the same:

    <button class="nav-link active">Active

    <button class="nav-link">Link

    <button class="nav-link">Link

Currently using components like .nav with buttons will totally break the layout.
This may affect the CSS only and must not apply to Bootstrap's Javascript.
Target version: 4.x / 5.x

can you suggest me to work on it?

Hi there,
FYI this in already in progress with #32630. At least this PR gets rid of border and background for buttons, which makes them look the same than links.
@MickL If that doesn't match your request, feel free to elaborate a bit more and provide a reduced test case.


update MMEvol code

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


Issue Triage instructions

Not sure if this covers all the labels as a they are currently used but it seems like a good starting point.

@ndelangen should we merge this?


Update Hacktoberfest Banner in the readme file

Description
Updated the Hacktoberfest banner, so that it can be visible properly.
Screenshot

Hey @ZoranPandovski, please have a look on my PR. Please comment if any change is required.

very good, I have been talking with @ZoranPandovski  since a week to assign me this issue and you came abruptly and sent the PR.
What is this?


Title:  Organization event management system

Is your proposal related to a problem? Please describe.
This is an web development project which helps an organization to manage the committee, committee members, events, and to manage the meeting rooms and provide the food facility to the attendees of the event. And the committee members can view the events allotted to them and attend the events.
Add any other context or screenshots about the proposal request here.

@Kushal997-das  please assign this issue under Gssoc2022


UnixPB: Fix Insecure Downloads In RHEL/SLES playbooks.

Fixes #3341 & #3147
Ref: Security Audit Issue TOB-5 issues identified with insecure downloads in SLES & RHEL

Checklist

[X] commit message has one of the standard prefixes
[ ] faq.md updated if appropriate
[ ] playbook changes run through VPC or QPC (if you have access)

/thaw

Did you find something that required zlib-devel to be installed? With Use bundled zlib on all versions, not just 21 temurin-build#3459 the JDK should no longer require it for build purposes

I've tried both build and test without zlib ( building fails due to missing X11, ALSA & Fontconfig dependencies, ), of which the Fontconfig does have a dependency on zlib ( which isn't installed by default on SLES 12 at least ).. Im inclined to leave it for the moment, and do some further investigation.


Provide missing formatting code for JSON-RPC API page

Provide missing Markdown for an admonition in the Web3Signer JSON-RPC API page.
Fixes #197

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

I would like to be the owner of this issue.


-p / --pretty should imply --json

What happens
Running deps-report -p find-dependencies *.js yields the regular output
What's expected
The output should be JSON. The help text says -p, --pretty Pretty-print JSON output (implies --json).

With Pretty-print JSON output (implies --json) I mean that you need to use -jp together. You can't use only -p because it will have no effect to the output!


fix: sort-objects ignore-pattern add Property type

Description
fixes #125
Additional context

What is the purpose of this pull request?

[x] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[x] Ideally, include relevant tests that fail without this PR but pass with it.
[x] Read contribution guidelines.

Thanks!


cannot login: Error: failed to authenticate: bad status code "400 Bad Request": malformed request: EOF

Description
cannot login
Steps to reproduce the issue:
$ hub-tool login
Username:
Password:
Error: failed to authenticate: bad status code "400 Bad Request": malformed request: EOF
Describe the results you received:
"400 Bad Request": malformed request: EOF
Describe the results you expected:
login is performed
Additional information you deem important (e.g. issue happens only occasionally):
Output of hub-tool --version:
Version:    v0.4.1
Git commit: 505194662f8bb7e5b3cd500e3f98961097c4c3d7

Output of docker version:
Docker version 20.10.8, build 3967b7d

Output of docker info:
Client:
 Context:    default
 Debug Mode: false
 Plugins:
  app: Docker App (Docker Inc., v0.9.1-beta3)
  buildx: Build with BuildKit (Docker Inc., v0.6.1-docker)
  scan: Docker Scan (Docker Inc., v0.8.0)

Server:
 Containers: 1
  Running: 1
  Paused: 0
  Stopped: 0
 Images: 12
 Server Version: 20.10.8
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: e25210fe30a0a703442421b0f60afac609f950a3
 runc version: v1.0.1-0-g4144b63
 init version: de40ad0
 Security Options:
  apparmor
  seccomp
   Profile: default
 Kernel Version: 5.4.0-84-generic
 Operating System: Ubuntu 20.04.2 LTS
 OSType: linux
 Architecture: x86_64
 CPUs: 8
 Total Memory: 15.89GiB
 Name: builder
 ID: D6E2:QC44:44F6:V33P:5BPN:HMZH:CWLY:TKJM:7TXW:TJTI:F7NB:J2BP
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Username: bdinnovations
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  <IP_ADDRESS>/8
 Live Restore Enabled: false

WARNING: No swap limit support

Additional environment details (AWS, VirtualBox, physical, etc.):
also reproduced on macbook with recent version of hub-tool

The issue has been fixed and released https://github.com/docker/hub-tool/releases/tag/v0.4.4


python-libp2p dev meeting

cc: @BrendanBenshoof @JulienPalard @bmcorser @SilverWingedSeraph @mvanveen
Our kick-off meeting went pretty well (#20) and I think we now have a pretty good idea about how to start this project.  I think the plan is to build a python port of libp2p first and then build the IPFS protocol on top of that.  I was thinking we should probably schedule another meeting to discuss libp2p in more detail and perhaps delegate some tasks.  Thoughts?

I tried to start loading the big picture of libp2p in my head, but current spec, typically
abstract-transport opens so many questions for me.
Typically, a few one I still have in mind:

transport.createListener(options, function (stream) {})

what is "options" ?
what is this callback for ?

"This method waits and listens for incoming transports by other peers." OK but

listener.listen(options, [callback]) "This method opens the listener to start listening for incoming transports" Wasn't this already done by the createListener ?

Does someone here have answers to those kind of questions or should we open tickets for each of them ?
It also look like it stick a lot to the underlying nodejs network paradign, and if we're using coroutines, I don't think that the "callback everywhere" design pattern is the pythonic way to do it. Yet there's probably almost no difference. But this opens the (already opened ?) subject await vs yield from.

@JulienPalard the spec was most recently re-written by @diasdavid after making it in node, so yeah it will have a node tint to it. But just check out the go implementation for an example with coroutines.

transport.createListener(options, function (stream) {})

what is "options" ?
what is this callback for ?

This doesnt have to be this way at all, that's just the idiomatic node version. here it is in go:
l := utp.Transport.Listen("/ip4/<IP_ADDRESS>/udp/1234/utp")
// though maybe more options, dont recall. but def no callback.

"This method waits and listens for incoming transports by other peers." OK but

listener.listen(options, [callback]) "This method opens the listener to start listening for incoming transports" Wasn't this already done by the createListener ?

yeah. another idiomatic choice.
@diasdavid, in Go it's not idiomatic to do that btw, the above call (transport.Listen(...)) should leave the listener in a state of already listening. from there,
conn := l.Accept()

is this ok with you @diasdavid? or there a critical reason why one MUST do:
// your way in go
l, err := transport.NewListener()
err := l.Listen(addr)

// the go way
l, err := transport.Listen(addr) // implicitly creates listener

cc @whyrusleeping

To clarify, an abstract-<something> module is a way to create a spec for a component that has the goal to be swappable, it is not, however, to force any kind of interface bias on other language ecosystems.
One example, which has two different interfaces already, is https://github.com/diasdavid/abstract-stream-muxer . Don't feel that you have to use the Node.js way of doing Asynchronous I/O in Python, just make sure you can create an interface in Python that follows the same expectations.
Also, one goal is to have the battery of tests all in one place, currently only the Node.js ones live in that repo, the Go ones live inside https://github.com/jbenet/go-peerstream, until we have a better way to manage packages in Go ready.

@diasdavid btw, the "abstract-" thing is common in node, but most other languages use "interface" to mean this instead. may be worth using that for cross-lang friendliness.

@jbenet good point, should we get a better name that is abstract/interface agnostic? What about making available on that repo, the file which contains the interface/abstract for the language, such thing would not exist for JS, but for go, we can have the interface.go, and go would import it?

we could-- but might make it more annoying to work with. i kinda like how multiaddr and multihash work in go/js.

@JulienPalard I think we should interpret the libp2p specs in terms of data flow between subsystems, and as @diasdavid said we should do whats most fitting for python async i/o (e.g. asyncio coroutines -- for which we can reference the go implementations like @jbenet suggested).
@diasdavid It would be awesome to have you in python libp2p meetings!  I'm very excited to get this up and running.

@amstocker  Yep async/await are almost only syntactic sugar over @asyncio.coroutine and yield from.
They're nicer on some points (more strict, more readable, distinguisable from the real yield from usage, etc...).
But I'm OK to not stick to 3.5 only for the moment, not sure how much person have access to a 3.5 interpreter for the moment.
@jbenet @diasdavid In one hand it's nice to hear we won't have to stick to the specs about interfaces, (mostly for the non-python way to present things). In the other hand, it's probably harder to read a spec when it mixes between itself and current implementation in another language.
For the moment I still have hard times to load the spec in my brain, find an independent, testable module I can write, and write it. (spent a lot of time last time to read the abstract-* wondering what to do in python with it, and what the undocumented parameter meant :-p).

@JulienPalard take a look at go interfaces too. and yes the specs need cleaning, but it's hard work. help would be appreciated, but note it's bikeshedding central.

@JulienPalard @jbenet I think I get the gist of the libp2p ideas/architecture, and am planning to do some kind of a roadmap for python-libp2p by next week.  As the libp2p spec is refined we will of course have to change things, but as it stands we definitely have a lot to work on in the first place.  @JulienPalard Here are some of the references I've found that each have bits and pieces of the spec:
https://github.com/ipfs/js-ipfs
https://github.com/diasdavid/js-libp2p
https://github.com/diasdavid/js-libp2p-swarm
https://github.com/ipfs/specs/blob/master/protocol/network/4-architecture.md#41-peer-routing
https://github.com/ipfs/specs/blob/master/protocol/network/6-interfaces.md#62-peer-routing
https://github.com/ipfs/go-ipfs/tree/057f0e281f9c516e8157c28e7542bae9fd4b0821/p2p

I was just chatting on the IRC and was wondering if the meeting is still open to join? I've been tinkering with IPFS in Python (mostly as a proof of concept before implementing it in Objective-C), and I'd love to be involved.

May be useful if some Python folks join the general libp2p hangouts too.
Those are high throughput so prob worth keeping both for now
Btw-- are you keeping minutes like the others? It's useful to be able to
read back on discussion. Feel free to PR any coordination stuff you need in
github.com/ipfs/pm and join the general irc syncs as you please
On Wed, Nov 18, 2015 at 00:00 Richard Moore<EMAIL_ADDRESS>wrote:

I was just chatting on the IRC and was wondering if the meeting is still
open to join? I've been tinkering with IPFS in Python (mostly as a proof of
concept before implementing it in Objective-C), and I'd love to be involved.
—
Reply to this email directly or view it on GitHub
https://github.com/ipfs/py-ipfs/issues/21#issuecomment-157638546.

@jbenet I'm planning on joining a few of the core dev hangouts as soon as I have time, and I'm sure others would be willing to as well.  In regards to minutes, we've only had one meeting so far (https://github.com/ipfs/py-ipfs/issues/20), this python-libp2p one hasn't happened yet.

I've been cleaning up, organizing things and going through the process of what I would have to do if I wanted to start building a new libp2p implementation in another language. The end result was a cleaner description and a uniform pattern across available implementations, check:

https://github.com/diasdavid/go-libp2p/blob/docs/roadmap/README.md
https://github.com/diasdavid/js-libp2p
https://github.com/diasdavid/rust-libp2p (pretty much just the landing repo, for now)

Some of the first things that need to be built are the Generic modules, used by every other part:

PeerInfo
PeerId
multihash
multihashing
multiaddr
multistream

Hope this helps :)

@diasdavid this is awesome!  Should give us a lot to work on for the time being.

glad you liked it :) also, to test multistream against go and node, one way is to follow PDD, for more info and guide check - https://github.com/ipfs/specs/tree/master/pdd

@diasdavid, really nice. I have a PR with a copy of your roadmap that I intended for us to use as documentation when implementing. I'll add your links today and rebase.

Any update on progress? Let me know if I can provide any help! :)

@diasdavid I've been busy finishing school so I haven't been around much, but in the next few weeks I'm definitely interested in getting back up to speed and start work on python-libp2p.

@amstocker sounds great, good luck with school!

@amstocker would be great to help for this implementation. Let me know what I have to read to catch up.

@Mec-iS I think right now we still need to get the generic modules done (#23), then we can start to focus on the core implementation for py-libp2p (see: https://github.com/diasdavid/js-libp2p).  Also it would be good to get as familiar as possible with the libp2p spec (see: https://github.com/ipfs/specs/tree/master/libp2p).  The specs for libp2p are a little scattered but you should be able to get the gist from the js-libp2p repo and the spec repo.


Cannot run win container - (hcsshim) parameter is incorrect

Hi all,
when trying to run one of the windows base images in docker, I got following error:
docker: Error response from daemon: hcsshim::CreateComputeSystem e7b0e497ac2b9xxxx: The parameter is incorrect.
I followed the instruction as described on the Microsoft pages (see link below) and tried with nanoserver (build 2004, 1903) and with servercore (2004, ltsc2009). Unfortunately I got always the same error output. I am using Microsoft Windows, Version 10.0.19041.450.
The strange thing is that on other computers with same setup (win os, images, docker version) it's running without any error.
Does anybody know where this error is coming from and what to do to get rid of it?
Thx in advance!
Link to doc:
https://docs.microsoft.com/de-de/virtualization/windowscontainers/quick-start/run-your-first-container

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


change how uploaded file type is validated. Issue #136

Re #136 fixes problem with how uploaded file types are recognised

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Seems like you can slightly tweak the regexps like this:

/\.xlsx?$/i
/.json$/i
/.([ctd]sv|txt)$/i

Thank you but we moved to a new version of rawgraphs!
v1 is no longer supported


Submit to PyPI

[x] Resolve #13
[x] Update docs to include pip install wagtail-autocomplete
[x] Submit to PyPI

This can now be closed, no?

Yes! Thank you!


Custom CloudFormation resources should gracefully handle stack creation rollbacks

CloudFormations behavior when rolling back a stack creation is kinda weird. Event if the custom resource was never created, it will send a Delete request with an autogenerated PhysicalResourceId. Right now, the InstancePort and ECSService custom resources fail when this happens.

To add more information, this happens when a resource creation fails, at which point we send an empty string as the PhysicalResourceId.
Turns out, CloudFormation doesn't like it when PhysicalResourceId is not provided, so it generates one automatically for it, then sets the Status Reason to Invalid PhysicalResourceId instead of showing the Reason that we provided from the error:

Now, when the stack starts rolling back, CloudFormation sends a Delete request with it's automatically generated physical resource id, and the current handles don't know what to do with that, so they fail, return an empty physical resource id and CloudFormation complains again, eventually resulting in a ROLLBACK_FAILED.
A simple repro for this is to change this line to:
+ return "", nil, errors.New("foo")

Then deploy to a new app that will cause a new stack to get created:
$ emp create foo
$ emp deploy remind101/acme-inc:master -a foo

I'll have a PR to fix these issues in a sec.


Landing layout at medium screens

There's an issue with centering landing (search and title section) on medium to small screens (looks like it's sub 1300px to 1024px)

👋🏻


Build from git on arm64 stop at 217/222 when cargo install arx works

Hi,
I fall in same problem (must be a relative utf-8 path) when trying archiving a chroot (so with broken symlink)
I test x86_64 binaries proposed and it solve the problem.
I will try to generate arx on an arm64 (Ubuntu2204) system (final target is for Asustor NAS ... but it's my problem)
... using cargo install arx ... all run as well binaries are available and run BUT WITH the ERROR (ready to be adapted as NAS (my part))
... due to error, I have tried to compile from git (where problem is solved) I clone the repo.
And I use :  cargo build --release (I am not a rust dev.)
ALL seems to go ahead without error up to freezing ...
Building [=======================> ] 217/222: mount_fuse_arx(bin), auto_mount(bin), zip2arx(bin), tar2arx(...
...

Hi,
1 I confirm the 2 problems causing the error (title)
... rustc is SMP for compile but use lot of memory
... rutsc is mono-processor when --release is used and multiple packages (arx, tar2arx, zip2arx, auto_mount are requested in one step
2 after generating one by one (my system have 4 CPU Realtek RTD1619B (Quad-Core 1.7 GHz) and 2GB of memory only).
... all is generated (long) and run as well (folder is a chroot with broken pipes)
3 transfer to be used on NAS (so restricted embedded Linux)
Linux AS3302Tv2aphil 5.10.107 #1 SMP PREEMPT Wed Jun 12 03:44:39 CST 2024 aarch64 GNU/Linux
some result : based on compare arx default value and tar but using pigz (gzip multiprocessor)
root@AS3302Tv2aphil:/share/Public # time arx create -o NewARM642204.archive NewARM642204/
real    1m 45.07s
user    2m 40.71s
sys     0m 20.68s
root@AS3302Tv2aphil:/share/Public# time tar -c --use-compress-program=pigz -f NewARM642204.tgz NewARM642204
real    2m 11.00s
user    6m 24.85s
sys     0m 20.29s
result size ... folder size is : 3.2G    NewARM642204 folder
305270 -rw-------    1 root     root<PHONE_NUMBER> Jul 29 17:54 NewARM642204.archive
305271 -rw-r--r--    1 root     root<PHONE_NUMBER> Jul 29 17:57 NewARM642204.tgz
... so size is not significant (near)
... arx is winner in term of duration ... on a "small" system  arm64
UNFORTUNATLY ... extract or mount have problem : (I redo test before opening an issue)
arx extract NewARM642204.archive
[ERROR arx] Error : IO Error Invalid argument (os error 22)
SAME with MOUNT
arx mount  ./NewARM642204.archive ./mnt/
[ERROR arx] Error : IO Error Invalid argument (os error 22)
mount_fuse_arx generate an error
"name" = "arx" "operating_system" = "Linux [unknown bitness]" "crate_version" = "0.2.1" "explanation" = """ Panic occurred in file '/root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/jubako-0.2.2/src/reader/container_pack.rs' at line 50 """ "cause" = "index out of bounds: the len is 0 but the index is 65535" "method" = "Panic" "backtrace" = """
ATTENTION extract and mount had worked with previous arx generated using cargo install arx.
... so ... please wait up I have more time to run test and do a comparison with x86_64 version ...
Philippe.

It's due (I think after more tests) to the memory usage & swap when generate an optimized binary (--release)
... when swap is added ... no freeze but optimization use ONLY one CPU (so on a limited in mips arm64 (4 CPU)), using only one CPU add a long delay . do you think is editable ?

Seems that it's not the case for cargo install arx ... I don't know why ...
This is probably dues to the lto option in arx repository (https://github.com/jubako/arx/blob/main/Cargo.toml#L24-L26)
I should have not commit this. When using cargo install arx the configuration of the project is ignored. Can you comment the lines and test please ?

ATTENTION extract and mount had worked with previous arx generated using cargo install arx.

The main branch (of jubako, on which main branch of arx is based) break the format with 0.2 versions.
I've took this liberty as I knew no one (but me) using arx and we are pretty soon in the project. But seems I am outrun by you in the release process. I plan to release 0.3.0 very soon. I will accelerate the process, even if we need a 0.3.1 just after. Hopefully it will be the last time.
So you have generated an archive with 0.2 (cargo install arx) you cannot read it with main branch. Sorry about that.

Hi,
No press no hurry ... I just want to participate and help if I can.
Thanks for the response (I will test, not sure today, because I am in travel) but in few time.
I am an integrator on NAS (multiples architectures) and I am really interested by this project ... but I have no target ... just test and see if it's corresponding to my requirements (and NAS usage interest to manage large archives) ....
So if I can help ... even I am not a developer, but I have some expertise ... and have some platforms (like arm64, etc.) to run some tests.
Philippe.

Hi,
Some information (please consider it's just information )
After suppressing lto in Cargo.toml ...
I generate arx without problem
... test 1
create an archive (small size) OK
list OK
extract OK
mount OK
... test 2
create an archive large folder lot of files (3,8 GB) OK archive = 1,1GB
list  FAIL cmd : arx list archive
... ... [ERROR arx] Error : Opening "archive": IO Error Invalid argument (os error 22)
extract FAIL cmd : arx extract archive
... ... [ERROR arx] Error : IO Error Invalid argument (os error 22)
mount FAIL cmd : arx mount archive ./mnt
... ... ERROR arx] Error : IO Error Invalid argument (os error 22)
I have also run a tests with an Ubuntu 2204 32 bits (armhf) it fail certainly due to some 64 bits instruction or format, I have a trace ... but 32 bits old arm is not a real target ... it's just for information  (cargo is proposed ... so)
best regards.
Philippe.
NB I am back for some weeks in Paris (where is my lab) so if I can run some tests don't hesitate to ask me.

I have also run a tests with an Ubuntu 2204 32 bits (armhf) it fail certainly due to some 64 bits instruction or format, I have a trace ... but 32 bits old arm is not a real target ... it's just for information (cargo is proposed ... so)

Format should be readable, independently of the running architecture.
32 bits and armhf arch should be supported but they are not tested (even manually) so no guaranty at all (for now)

... test 2
create an archive large folder lot of files (3,8 GB) OK archive = 1,1GB
list FAIL cmd : arx list archive
... ... [ERROR arx] Error : Opening "archive": IO Error Invalid argument (os error 22)

Can you read the archive on a x86_64 architecture ?
If yes it is probably a bug in the reading code. Else it is in the creating code.
Is it possible than you share the archive with me (only) ?
You may also pass the option -2 (or --two-files) when you create the archive. You will create an archive in two files (one with extension .jbkc). The jbkc file contains the content of the files and the other contains the metadata. You can share only the later one, I would have access to the list(name/size) of the files but not their content.

Hi,
F.Y.I.
... I have compiled arx without lto on x86_64 (clean install)
I have transferred my archive created on arm64
.... SAME error (OS error 22) when trying to list contents.
At this time, I am busy ... so I will have to stop form some hours.
TODO :  I will regenerate an archive on x86_64 and try to list, extract, mount it
please wait I will be back, I also post the output of generating arx on armhf ... just F.Y.I.
and a tar gziped (pigz smp gzip) of the folder I used for test. ... no secret, no data ... just an Ubuntu 2204 chroot ... so public
Best regards.
Philippe.

Hi,
arx_install_fail.log
Here the log file when cargo fail to generate arx on armhf / 32 bits
Philippe.


feat(plot): add cross-check plotting and improve existing plot aesthetics (#33)

Added a new plot_cross_check function to enable side-by-side comparison of input datasets.

Improved plot_inventory_vertical_profiles with better aesthetics:

Added gridlines and enhanced plot formatting.
Included support for stepfilled histograms with custom colors.

Retained existing functionality, ensuring backward compatibility.
Optimized plot_results by improving subplot aesthetics with dashed gridlines and a lighter background.
Verified compatibility and ensured plots are visually polished.

Addresses #33: Enhancements to plotting routines for improved visualization and data comparison.

The main branch is reserved for major software releases. Please wait for the contribution guidelines to be published soon where we will define our workflows and standards. Thank you for understanding. Best regards, Stefan


There is no means of private contact for security issues

So - I have a fairly ugly security issue I found with this - but I do not want to post it here for the script kiddies to exploit.
I suggest, strongly, that you provide an email address - a throwaway dedicated one if need be - for security issue reporting. You have 30,000+ downloads, you owe it to them to provide a means for this sort of thing to be discussed and hopefully fixed before it is exposed, if it has not been already.

well - nevermind. My issue is already a filed bug. Back in 2014. so much for that.

https://github.com/sveale/remote-edit/blob/d3c0bb647451bb15fb5bc4de8cbe69a89fdcf8e7/package.json#l17


request: looser syntax for powers

Instead of pow(2,3), could vim-crunch accept also the more common, and intuitive, expressions 2^3 or 2**3 to compute the cube of 2?

I'd like that too. I think this would need a real parser, and right now crunch is just a bunch of search and replace hacks.  I'd like to do this one day but right now it's not a priority of mine.

That's great news


Command bar fixes

The command bar currently works, but is not very clear.
For example, an option simply labeled "Enable" appears there, which actually refers to the "Fast mode toggle". this should be fixed so that by looking at the command bar, it becomes clear what the option is meant to do
for addresses, it should be clear which wallet they come from (and perhaps what their index is within that wallet), and if they have an alias or not

Could I take a shot at this?