Build From Source error

In https://github.com/ciscospark/react-ciscospark/blob/master/README.md page, when I tried to install the build from source, after I ran the command “npm run build”, I met the following error. It seems it might be more related to the package itself. Please help give some advice on it, thanks in advance!

KAYALI-M-Q4T0:react-ciscospark joyin$ npm run build

<EMAIL_ADDRESS>build /Applications/react-ciscospark
npm run build:packages && npm run build:bundle

<EMAIL_ADDRESS>build:packages /Applications/react-ciscospark
cross-env NODE_ENV=${NODE_ENV:-production} babel-node --presets=stage-1,es2015 scripts/build-packages.js

Cleaning react-component-activity-item dist folder...
Building react-component-activity-item...
Hash: 5d1986700df8e10adfaa
Version: webpack 2.6.1
Time: 16383ms
Asset     Size  Chunks                    Chunk Names
fonts/Atlantic-Neo-Icons.woff   104 kB          [emitted]
bundle.js   439 kB       0  [emitted]  [big]  main
main.css  43.3 kB       0  [emitted]         main
bundle.js.map  3.16 MB       0  [emitted]         main
main.css.map  15.3 kB       0  [emitted]         main
+ 529 hidden modules
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_ID environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_SECRET environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
react-component-activity-item... Done
Cleaning react-component-activity-item-base dist folder...
Building react-component-activity-item-base...
Hash: 84f4cac9de83bab0c93d
Version: webpack 2.6.1
Time: 4656ms
Asset     Size  Chunks             Chunk Names
fonts/Atlantic-Neo-Icons.woff   104 kB          [emitted]
bundle.js    89 kB       0  [emitted]  main
main.css  38.9 kB       0  [emitted]  main
bundle.js.map   476 kB       0  [emitted]  main
main.css.map  14.9 kB       0  [emitted]  main
+ 41 hidden modules
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_ID environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_SECRET environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
react-component-activity-item-base... Done
Cleaning react-component-activity-list dist folder...
Building react-component-activity-list...
Hash: a637551a944b2e1d79ab
Version: webpack 2.6.1
Time: 15001ms
Asset     Size  Chunks                    Chunk Names
fonts/Atlantic-Neo-Icons.woff   104 kB          [emitted]
bundle.js   443 kB       0  [emitted]  [big]  main
main.css  44.5 kB       0  [emitted]         main
bundle.js.map  3.19 MB       0  [emitted]         main
main.css.map  15.6 kB       0  [emitted]         main
+ 535 hidden modules
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_ID environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_SECRET environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
react-component-activity-list... Done
Cleaning react-component-activity-menu dist folder...
Building react-component-activity-menu...
Hash: 14db0b1ba4df1d7479ab
Version: webpack 2.6.1
Time: 4211ms
Asset     Size  Chunks             Chunk Names
fonts/Atlantic-Neo-Icons.woff   104 kB          [emitted]
bundle.js  91.2 kB       0  [emitted]  main
main.css  35.8 kB       0  [emitted]  main
bundle.js.map   506 kB       0  [emitted]  main
main.css.map  12.4 kB       0  [emitted]  main
+ 77 hidden modules
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_ID environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_SECRET environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
react-component-activity-menu... Done
Cleaning react-component-activity-post dist folder...
Building react-component-activity-post...
Hash: bf6bc544e44952ec60c1
Version: webpack 2.6.1
Time: 6090ms
Asset     Size  Chunks             Chunk Names
fonts/Atlantic-Neo-Icons.woff   104 kB          [emitted]
bundle.js   142 kB       0  [emitted]  main
main.css  39.7 kB       0  [emitted]  main
bundle.js.map  1.06 MB       0  [emitted]  main
main.css.map  14.2 kB       0  [emitted]  main
+ 295 hidden modules
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_ID environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_SECRET environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
react-component-activity-post... Done
Cleaning react-component-activity-post-action dist folder...
Building react-component-activity-post-action...
Hash: 537b9d38593ee0bf672a
Version: webpack 2.6.1
Time: 3725ms
Asset     Size  Chunks             Chunk Names
fonts/Atlantic-Neo-Icons.woff   104 kB          [emitted]
bundle.js  83.6 kB       0  [emitted]  main
main.css  34.9 kB       0  [emitted]  main
bundle.js.map   452 kB       0  [emitted]  main
main.css.map  11.5 kB       0  [emitted]  main
+ 37 hidden modules
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_ID environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_SECRET environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
react-component-activity-post-action... Done
Cleaning react-component-activity-share-file dist folder...
Building react-component-activity-share-file...
Hash: 0cf662b40eb0f2082785
Version: webpack 2.6.1
Time: 8898ms
Asset     Size  Chunks                    Chunk Names
fonts/Atlantic-Neo-Icons.woff   104 kB          [emitted]
bundle.js   271 kB       0  [emitted]  [big]  main
main.css  35.7 kB       0  [emitted]         main
bundle.js.map  1.86 MB       0  [emitted]         main
main.css.map  12.6 kB       0  [emitted]         main
+ 338 hidden modules
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_ID environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_SECRET environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
react-component-activity-share-file... Done
Cleaning react-component-activity-share-files dist folder...
Building react-component-activity-share-files...
Hash: f8fb9fb5658e43a40da2
Version: webpack 2.6.1
Time: 13327ms
Asset     Size  Chunks                    Chunk Names
fonts/Atlantic-Neo-Icons.woff   104 kB          [emitted]
bundle.js   391 kB       0  [emitted]  [big]  main
main.css  42.9 kB       0  [emitted]         main
bundle.js.map   2.8 MB       0  [emitted]         main
main.css.map  14.9 kB       0  [emitted]         main
+ 501 hidden modules
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_ID environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_SECRET environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
react-component-activity-share-files... Done
Cleaning react-component-activity-share-thumbnail dist folder...
Building react-component-activity-share-thumbnail...
Hash: e726bd027d32d0fb5b52
Version: webpack 2.6.1
Time: 8911ms
Asset     Size  Chunks                    Chunk Names
fonts/Atlantic-Neo-Icons.woff   104 kB          [emitted]
bundle.js   273 kB       0  [emitted]  [big]  main
main.css  36.9 kB       0  [emitted]         main
bundle.js.map  1.87 MB       0  [emitted]         main
main.css.map  13.5 kB       0  [emitted]         main
+ 343 hidden modules
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_ID environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_SECRET environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
react-component-activity-share-thumbnail... Done
Cleaning react-component-activity-system-message dist folder...
Building react-component-activity-system-message...
Hash: 3aa7c290d565d7c9464c
Version: webpack 2.6.1
Time: 4387ms
Asset       Size  Chunks             Chunk Names
bundle.js    73.4 kB       0  [emitted]  main
main.css  201 bytes       0  [emitted]  main
bundle.js.map     682 kB       0  [emitted]  main
main.css.map  368 bytes       0  [emitted]  main
+ 97 hidden modules
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_ID environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_SECRET environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
react-component-activity-system-message... Done
Cleaning react-component-activity-text dist folder...
Building react-component-activity-text...
Hash: 042a04aab5cc98269984
Version: webpack 2.6.1
Time: 4835ms
Asset       Size  Chunks             Chunk Names
bundle.js    74.1 kB       0  [emitted]  main
main.css  947 bytes       0  [emitted]  main
bundle.js.map     854 kB       0  [emitted]  main
main.css.map    1.32 kB       0  [emitted]  main
+ 284 hidden modules
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_ID environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_SECRET environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
react-component-activity-text... Done
Cleaning react-component-add-file-button dist folder...
Building react-component-add-file-button...
Hash: 18bb811a42e1bc97a5d4
Version: webpack 2.6.1
Time: 3557ms
Asset     Size  Chunks             Chunk Names
fonts/Atlantic-Neo-Icons.woff   104 kB          [emitted]
bundle.js  82.8 kB       0  [emitted]  main
main.css  35.1 kB       0  [emitted]  main
bundle.js.map   447 kB       0  [emitted]  main
main.css.map  12.2 kB       0  [emitted]  main
+ 35 hidden modules
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_ID environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_SECRET environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
react-component-add-file-button... Done
Cleaning react-component-avatar dist folder...
Building react-component-avatar...
Hash: b6250af5350d4069a8d3
Version: webpack 2.6.1
Time: 3639ms
Asset     Size  Chunks             Chunk Names
fonts/Atlantic-Neo-Icons.woff   104 kB          [emitted]
bundle.js  83.4 kB       0  [emitted]  main
main.css  35.9 kB       0  [emitted]  main
bundle.js.map   450 kB       0  [emitted]  main
main.css.map  12.8 kB       0  [emitted]  main
+ 35 hidden modules
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_ID environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_SECRET environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
react-component-avatar... Done
Cleaning react-component-button dist folder...
Building react-component-button...
Hash: 1eff207204f8ce1bc697
Version: webpack 2.6.1
Time: 3580ms
Asset     Size  Chunks             Chunk Names
fonts/Atlantic-Neo-Icons.woff   104 kB          [emitted]
bundle.js    83 kB       0  [emitted]  main
main.css  34.8 kB       0  [emitted]  main
bundle.js.map   448 kB       0  [emitted]  main
main.css.map  11.6 kB       0  [emitted]  main
+ 35 hidden modules
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_ID environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_SECRET environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
react-component-button... Done
Cleaning react-component-button-controls dist folder...
Building react-component-button-controls...
Hash: 5384aaeab2c8fdbcbbbf
Version: webpack 2.6.1
Time: 4151ms
Asset     Size  Chunks             Chunk Names
fonts/Atlantic-Neo-Icons.woff   104 kB          [emitted]
bundle.js    90 kB       0  [emitted]  main
main.css  35.2 kB       0  [emitted]  main
bundle.js.map   500 kB       0  [emitted]  main
main.css.map  11.9 kB       0  [emitted]  main
+ 75 hidden modules
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_ID environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_SECRET environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
react-component-button-controls... Done
Cleaning react-component-chip-base dist folder...
Building react-component-chip-base...
Hash: ec2414cc0e03f308d592
Version: webpack 2.6.1
Time: 3700ms
Asset     Size  Chunks             Chunk Names
fonts/Atlantic-Neo-Icons.woff   104 kB          [emitted]
bundle.js  83.7 kB       0  [emitted]  main
main.css  35.4 kB       0  [emitted]  main
bundle.js.map   453 kB       0  [emitted]  main
main.css.map  12.1 kB       0  [emitted]  main
+ 37 hidden modules
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_ID environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_SECRET environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
react-component-chip-base... Done
Cleaning react-component-chip-file dist folder...
Building react-component-chip-file...
Hash: 1764e9dc7ce801ee1d96
Version: webpack 2.6.1
Time: 3964ms
Asset     Size  Chunks             Chunk Names
fonts/Atlantic-Neo-Icons.woff   104 kB          [emitted]
bundle.js  85.2 kB       0  [emitted]  main
main.css  36.5 kB       0  [emitted]  main
bundle.js.map   460 kB       0  [emitted]  main
main.css.map  13.1 kB       0  [emitted]  main
+ 39 hidden modules
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_ID environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_SECRET environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
react-component-chip-file... Done
Cleaning react-component-confirmation-modal dist folder...
Building react-component-confirmation-modal...
Hash: 08161c08208cc5df0357
Version: webpack 2.6.1
Time: 2804ms
Asset     Size  Chunks             Chunk Names
bundle.js  26.1 kB       0  [emitted]  main
main.css  4.61 kB       0  [emitted]  main
bundle.js.map   292 kB       0  [emitted]  main
main.css.map  6.26 kB       0  [emitted]  main
+ 33 hidden modules
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_ID environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_SECRET environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
react-component-confirmation-modal... Done
Cleaning react-component-cover dist folder...
Building react-component-cover...
Hash: c03b38baa2686bbeb47e
Version: webpack 2.6.1
Time: 2666ms
Asset       Size  Chunks             Chunk Names
bundle.js    21.7 kB       0  [emitted]  main
main.css  389 bytes       0  [emitted]  main
bundle.js.map     279 kB       0  [emitted]  main
main.css.map  619 bytes       0  [emitted]  main
+ 33 hidden modules
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_ID environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_SECRET environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
react-component-cover... Done
Cleaning react-component-day-separator dist folder...
Building react-component-day-separator...
Hash: 09b129893109bfa6db76
Version: webpack 2.6.1
Time: 5232ms
Asset     Size  Chunks             Chunk Names
bundle.js   118 kB       0  [emitted]  main
main.css  1.22 kB       0  [emitted]  main
bundle.js.map   977 kB       0  [emitted]  main
main.css.map  1.64 kB       0  [emitted]  main
+ 61 hidden modules
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_ID environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_SECRET environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
react-component-day-separator... Done
Cleaning react-component-error-display dist folder...
Building react-component-error-display...
Hash: b0f732fde00eaa7e23f8
Version: webpack 2.6.1
Time: 2878ms
Asset       Size  Chunks             Chunk Names
bundle.js    26.7 kB       0  [emitted]  main
main.css  967 bytes       0  [emitted]  main
bundle.js.map     315 kB       0  [emitted]  main
main.css.map    1.23 kB       0  [emitted]  main
+ 54 hidden modules
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_ID environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_SECRET environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
react-component-error-display... Done
Cleaning react-component-file-staging-area dist folder...
Building react-component-file-staging-area...
Hash: 62df18ccb7d3a76caad9
Version: webpack 2.6.1
Time: 9147ms
Asset     Size  Chunks                    Chunk Names
fonts/Atlantic-Neo-Icons.woff   104 kB          [emitted]
bundle.js   272 kB       0  [emitted]  [big]  main
main.css  37.3 kB       0  [emitted]         main
bundle.js.map  1.87 MB       0  [emitted]         main
main.css.map  13.3 kB       0  [emitted]         main
+ 342 hidden modules
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_ID environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_SECRET environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
react-component-file-staging-area... Done
Cleaning react-component-icon dist folder...
Building react-component-icon...
Hash: 3ecb927c56588eef9358
Version: webpack 2.6.1
Time: 3458ms
Asset     Size  Chunks             Chunk Names
fonts/Atlantic-Neo-Icons.woff   104 kB          [emitted]
bundle.js  81.8 kB       0  [emitted]  main
main.css  34.6 kB       0  [emitted]  main
bundle.js.map   442 kB       0  [emitted]  main
main.css.map  39.9 kB       0  [emitted]  main
+ 33 hidden modules
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_ID environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_SECRET environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
react-component-icon... Done
Cleaning react-component-incoming-call dist folder...
Building react-component-incoming-call...
Hash: 88fd5df579c43e290907
Version: webpack 2.6.1
Time: 4318ms
Asset     Size  Chunks             Chunk Names
fonts/Atlantic-Neo-Icons.woff   104 kB          [emitted]
bundle.js  93.8 kB       0  [emitted]  main
main.css  37.5 kB       0  [emitted]  main
bundle.js.map   517 kB       0  [emitted]  main
main.css.map  13.2 kB       0  [emitted]  main
+ 79 hidden modules
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_ID environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_SECRET environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
react-component-incoming-call... Done
Cleaning react-component-list-separator dist folder...
Building react-component-list-separator...
Hash: 94f647a74849f2559d60
Version: webpack 2.6.1
Time: 2700ms
Asset     Size  Chunks             Chunk Names
bundle.js    22 kB       0  [emitted]  main
main.css  1.22 kB       0  [emitted]  main
bundle.js.map   280 kB       0  [emitted]  main
main.css.map  1.64 kB       0  [emitted]  main
+ 33 hidden modules
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_ID environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_SECRET environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
react-component-list-separator... Done
Cleaning react-component-loading-screen dist folder...
Building react-component-loading-screen...
Hash: e6fefce052d1560b4dcf
Version: webpack 2.6.1
Time: 3261ms
Asset       Size  Chunks             Chunk Names
bundle.js    27.3 kB       0  [emitted]  main
main.css  670 bytes       0  [emitted]  main
bundle.js.map     316 kB       0  [emitted]  main
main.css.map  938 bytes       0  [emitted]  main
+ 56 hidden modules
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_ID environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
WARNING in EnvironmentPlugin - MESSAGE_DEMO_CLIENT_SECRET environment variable is undefined.
You can pass an object with default values to suppress this warning.
See https://webpack.js.org/plugins/environment-plugin for example.
ERROR in ./styles.css
Module build failed: ModuleBuildError: Module build failed: Error: spawn /Applications/react-ciscospark/node_modules/pngquant-bin/vendor/pngquant ENOENT
at exports._errnoException (util.js:1050:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
at onErrorNT (internal/child_process.js:367:16)
at _combinedTickCallback (internal/process/next_tick.js:80:11)
at process._tickCallback (internal/process/next_tick.js:104:9)
at runLoaders (/Applications/react-ciscospark/node_modules/webpack/lib/NormalModule.js:192:19)
at /Applications/react-ciscospark/node_modules/loader-runner/lib/LoaderRunner.js:364:11
at /Applications/react-ciscospark/node_modules/loader-runner/lib/LoaderRunner.js:230:18
at context.callback (/Applications/react-ciscospark/node_modules/loader-runner/lib/LoaderRunner.js:111:13)
at imagemin.buffer.then.catch.err (/Applications/react-ciscospark/node_modules/image-webpack-loader/index.js:80:9)
@ ./index.js 20:14-37
ERROR in ./styles.css
Module build failed: ModuleBuildError: Module build failed: Error: spawn /Applications/react-ciscospark/node_modules/pngquant-bin/vendor/pngquant ENOENT
at exports._errnoException (util.js:1050:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
at onErrorNT (internal/child_process.js:367:16)
at _combinedTickCallback (internal/process/next_tick.js:80:11)
at process._tickCallback (internal/process/next_tick.js:104:9)
at runLoaders (/Applications/react-ciscospark/node_modules/webpack/lib/NormalModule.js:192:19)
at /Applications/react-ciscospark/node_modules/loader-runner/lib/LoaderRunner.js:364:11
at /Applications/react-ciscospark/node_modules/loader-runner/lib/LoaderRunner.js:230:18
at context.callback (/Applications/react-ciscospark/node_modules/loader-runner/lib/LoaderRunner.js:111:13)
at imagemin.buffer.then.catch.err (/Applications/react-ciscospark/node_modules/image-webpack-loader/index.js:80:9)
ERROR in<EMAIL_ADDRESS>doesn't export content
/Applications/react-ciscospark/scripts/build-packages.js:21
throw err;
^
Error: Error building react-component-loading-screen package, Error: Command failed: cd /Applications/react-ciscospark/packages/node_modules/@ciscospark/react-component-loading-screen && webpack --config /Applications/react-ciscospark/scripts/webpack/webpack.prod.babel.js
at buildPackage (/Applications/react-ciscospark/scripts/build-package.js:25:13)
at /Applications/react-ciscospark/scripts/build-packages.js:9:12
at Array.map (native)
at Object. (/Applications/react-ciscospark/scripts/build-packages.js:6:22)
at Module._compile (module.js:571:32)
at loader (/Applications/react-ciscospark/node_modules/babel-register/lib/node.js:144:5)
at Object.require.extensions.(anonymous function) [as .js] (/Applications/react-ciscospark/node_modules/babel-register/lib/node.js:154:7)
at Module.load (module.js:488:32)
at tryModuleLoad (module.js:447:12)
at Function.Module._load (module.js:439:3)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build:packages: cross-env NODE_ENV=${NODE_ENV:-production} babel-node --presets=stage-1,es2015 scripts/build-packages.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build:packages script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!      /Users/joyin/.npm/_logs/2017-05-30T08_49_54_590Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build: npm run build:packages && npm run build:bundle
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!      /Users/joyin/.npm/_logs/2017-05-30T08_49_54_635Z-debug.log
KAYALI-M-Q4T0:react-ciscospark joyin$

@joeyyin123 There's a fix for this incoming #261

Thanks bzang. It is working for me now.


Piping content to goaccess --no-global-config causes no time format error

Under goaccess 1.2:
goaccess --no-global-config -f /tmp/somelog works
cat /tmp/somelog | goaccess --no-global-config crashes with the following:
GoAccess - version 1.2 - May 18 2017 01:56:07
Config file: No config file used

Fatal error has occurred
Error occured at: src/goaccess.c - set_curses - 1394
No time format was found on your conf file.

When data is piped, you need to set it in a config file or simply on the command line such as:
cat /tmp/somelog | goaccess --no-global-config --log-format=COMBINED

or create a new config file, specify the log/date/time formats and use:
cat /tmp/somelog | goaccess -p /path/to/copied/goaccess.new.conf

Any updates on this?

Closing this. Feel free to reopen it as needed.

Only repository contributors can re-open issues, but there is no need to re-open this.
I was basing my usage off the example from the readme:
# tail -f access.log | goaccess -

I guess the only bug here is in the readme? Is that intended to be used with an existing goaccess session in the background?

That's a good point. No, it's not intended to be use with an existing session. I can add a note to the examples section on README.md that piping data into goaccess won't prompt the log config dialog and therefore it's required to specify it on a config file or through the command line. Thanks for pointing that out.

A note has been added. Thanks again!

One more question: shouldn't the behavior of
cat file.log | goaccess --no-global-config
match the behavior of
goaccess --no-global-config -f file.log ?
The latter prompts the user to pick a format, but the former throws an error.

I agree, however, when data is piped into goaccess, it reads it from stdin. The issue is that at that point handling keyboard sequences and stdin at the same time becomes a bit of a mess.
Actually v1.2 it's duplicating file descriptors so it doesn't get in the way of curses' normal reading stdin, so probably adding this functionality shouldn't be too much of a pain. It would be nice to revise this and see what can be done to handle both.

For the record, here's the code I mentioned above.

Interesting, I never thought of that!
I use the combined log format so I don't know the answer to this question: are there any self-documenting log formats and does goaccess support automatically detecting the log format from those files? If the answer is no, would it make things easier to not touch the pipe descriptor until you've asked the user for log format if no format has been specified at the command-line?

That's correct, it doesn't automatically detect the log format (It's on the to-do list).
I'm not sure if I follow, and please correct me if I'm wrong, but you are saying that we should display the log-format dialog when data is piped, read the entered format and then read data from the pipe?


(GH-115) Migrate to sdk project format and nuget update

Migrated to the sdk project format, updated the nuget packages to latest

@gep13, could you please review this one?

@gep I have updated with the latest changes from the develop

Great, now we should be able to multi target

@arturcic said...
Great, now we should be able to multi target

What are your thoughts around this?  Would you mind raising an issue for discussion?

Well I had in mind 2 issues with this PR, to use the latest Octokit library so that we can use AccessToken instead of User and Password, and also to be able to use it as Global Tool

@arturcic said...
latest Octokit library so that we can use AccessToken instead of User and Password

It is already possible to use an AccessToken today.  It just gets passed along as the password.  But having actual support for a standalone variable will be useful.

@arturcic said...
be able to use it as Global Tool

Yes, I had the same thought.  Is this something you would like to work on?

@arturcic said...
be able to use it as Global Tool

Yes, I had the same thought. Is this something you would like to work on?

Yes, I'll create an issue

@arturcic said...
latest Octokit library so that we can use AccessToken instead of User and Password

It is already possible to use an AccessToken today. It just gets passed along as the password. But having actual support for a standalone variable will be useful.

I had a look here https://github.com/GitTools/GitReleaseManager/blob/develop/Source/GitReleaseManager.Cli/Options/BaseGitHubSubOptions.cs#L27 and it seems the Credentials instance is created from user/password.
Just to clarify, can I use the access token as password?
Anyway I would prefer to have the -token option instead of user/password

added #117


Guild countdown broken

Guild event in past, not showing countdown to next guild raid

fixed in https://github.com/Phloot/omen-bot/pull/61


Add job details to database when creating new testplan.

Description:
Currently when creating a new test-plan, the Jenkins job is created and the relevant URL is given as the response. But we has to add jenkins job details to the database as well.

Closing since the Build-API is deprecated as we are moving with GitOPS


SEA-RAFT L Checkpoints & Zero-Shot Validation

Hi, great work again! Are the SEA-RAFT large checkpoints just the medium checkpoints with more refinement iterations? Additionally, I do not fully understand the zero-shot validation approach. In the paper, you are stating that you are downsampling the 1080p images of Kitti by a factor of two and upsample the optical flow again. However, the Kitti images have a resolution different than 1080p (typically 376  x 1241 pixels, but the size varies). Do you crop before downsampling, or do you use the original resolution (probably padded to accommodate the required backbone stride of 8)? Thanks again for the help :)

SEA-RAFT(L) and SEA-RAFT(M) share the same weights. For Spring zero-shot evaluation, we use downsample-upsample strategy as mentioned in the papers. For KITTI and Sintel zero-shot eval, we use full-resolution images as the input without cropping.

Thanks for the clarification; cheers, Christoph!


feat: cooldown cache & database

This adds a basic cache for storing cooldowns and support for multiple database drivers so cooldown data can persist between server restarts.

Thanks for this! Is there anything more you want to go over with this or would you consider it ready for merge?

Thanks for this! Is there anything more you want to go over with this or would you consider it ready for merge?

I'd prefer it if you continued this PR by making commits on the same branch until this is stable.
The db and cache should work perfectly fine, I've not implemented any usage for them, however.
Note that this is also completely untested so it needs a bit of work.

Fixed the DB issue. I removed hsql as a suggested DB driver as it was buggy for me and made h2 the default.
Also made the reload command run the correct code. See the "todo" in the relevant commit for some more stuff needed for reload functionality to properly work. https://github.com/Alathra/AlathranCommands/pull/2/commits/63be11581538e795f556e573042715fc3a84cd93

The latest two commits were supposed to be on the main branch, my bad heh


Update from GSX to GDI

https://github.com/datakaveri/ogc-resource-server/pull/204 - server changes
https://github.com/datakaveri/gsx-developer-docs/pull/22 - Docs changes


s3fs.S3FileSystem.ls() returns FileNotFoundError starting from 2023.9.0

Starting from 2023.9.0+ calling ls() on a path to a file that does not exist returns a FileNotFoundError where as previously it returned an empty list.
Looking at the changelog, I think this is a result of updates to fsspec, so let me know if this issue is more appropriately filed in that repository.
Example:
import s3fs

fs = s3fs.S3FileSystem()

# In 2023.6.0 returned []
# in 2023.9.0+ raises FileNotFoundError
response = fs.ls("s3://path/to/file/that/does/not/exist")

+1

Isn't FileNotFound the correct thing to return? This is how posix shells work, for instance.

Yes, I think FileNotFound is the correct thing to return.
This is more a comment on a breaking change in the expected response with a minor version change.

This is a breaking change that should be documented...


Add Mousetrap.prototype.destroy

Then we can make instance unbind event from document

Why isn't this merged already? =)
When you can create new instances, you should be able to remove them!

+1
I was investigating a memory leak in a react app which lead me here. react-hotkeys uses this lib and naively calls reset() assuming things will be cleared up but they aren't.
This means that every time your react component is mounted or rerendered it will leak 3 event handlers.

Well it looks like this has been forgotten, but i dont like idea of generating memory leaks, that means Mousetrap is not usable for scoped events without memory leaks so far, pity.
It is only usable globaly for document

@ccampbell any chance we could get this merged? mousetrap looks great for our use case but the inability to properly unbind the event listener it creates is a show-stopper for us: our use case is an application that can be unmounted and re-mounted, resulting in event listeners piling up.

Hi. Thanks for following up on this. I am happy to merge this.
My only question for @bolasblack (if he even remembers after all these years) is why the destroy method was omitted from the global Mousetrap instance (the one on document)? I don’t see any reason to prevent someone from using the global Mousetrap instance and then calling Mousetrap.destroy() to remove the event listeners on document.

Yeah, I ran into that too when trying to actually call destroy() from application code. Seems like that one change should not be in this diff.

Hi guys.
Well i was trying to find out whether is that missing destroy big problem or not. As i said before, its problem when you want to have global shortcuts and also local lets say for form. But as i found out, all event listeners are garbage collected by browser if there are no references on any instance that uses them. So maybe:
this._mousetrap.reset();
this._mousetrap = null;

is enough. But i did not try to profile it, so I am not sure.


[FEAT] User can go directly to their language with URL path, ie say /nederlands or /espanol, etc.

⚠ IMPORTANT: Please fill out this template to give us as much information as possible to consider/implement the feature.
Prerequisites

[x] check this box if you have completed the following:

Reviewed the contributing guidelines and support files
Reviewed the README file for the repository you are working in
Searched for relevant instructions on our Discord server
Searched the issues of the repository you are working in to make sure one was not already filed

Summary

Based on user feedback from doctor in Belgium
Problem: “Which url brings me to the version where Dutch is integrated (as I use the beta link from the website I still do not see Dutch as a language).”
Action: Create React Router path (and if necessary backend endpoint to the translated version of site) in the user's native language. That way the user doesn't have to know English to navigate to the choose a language section.
For example:
Dutch:
coronatrackerbeta.com/nederlands
Spanish:
coronatrackerbeta.com/español and coronatrackerbeta.com/espanol (in case they can't get ñ)
Corner case to consider:
For non-Latin languages like Chinese or Arabic, should we have the endpoint in their native language and English version? How do speakers access English sites in their own languages?
@AdhamAH @salvolpe @njordhov
How does Facebook or large multilingual site do this?
Motivation
Why are we doing this?
We want non-English speakers to be able to use our application easier, by letting them visit the app in their native language directly from the URL
**What use cases does it support? **
Easier user onboarding at the beginning of the app
What is the expected outcome?
users can access our site without having the possible roadblock of not knowing English.
Possible Alternatives

Assume that most speakers with a cellphone know enough basic English to click on the button to choose their language. Or they will experiment and click on the button and see their language.
Additional Context

DocMusher is a doctor in Belgium who fits one of the user cohorts that we want to interview and gain good insights from. As an external set of eyes with domain experience dealing with COVID-19 patients, we are able to learn what is useful on the field.

Not sure if backend endpoint is necessary. Added the info just in case.

This is likely related to #643
Based on schema.org we should look at an overall standard for language names, such as: https://en.m.wikipedia.org/wiki/IETF_language_tag

@tesla809 In order to get access to the user native language version of the app user still have to type url with latin characters.
I thinking we can declare routs for each language and if user hit the rout we can trigger the same logic as if user click on the select language button.

I agree with @pavel-ilin - I'd say we should update this issue accordingly, where if the user hits a certain route this calls the language selector and then opens the app

Note that the user's preferred language can be determined from the web browser settings:
https://developer.mozilla.org/en-US/docs/Web/API/NavigatorLanguage/language
That way, they can be directed directly to a page in their preferred language, instead of explicitly selecting it. Although its still a good idea to provide a way for the user to override the default language and choose another.

Note that the user's preferred language can be determined from the web browser settings:
https://developer.mozilla.org/en-US/docs/Web/API/NavigatorLanguage/language
That way, they can be directed directly to a page in their preferred language, instead of explicitly selecting it. Although its still a good idea to provide a way for the user to override the default language and choose another.

Just FYI, manual language routs, like this like if was described in this issue, did not setup.


Bug: async updates cause unwanted history

There's a class of bugs involving async actions that leaves the history stack in an unwanted state. The problem occurs when a future update needs to replace a past update such as when uploading an image. Typically, an image node is inserted with a loading state because we don't know the src until it's uploaded. Eventually, we'll set the src as the result of an async action. If the async update is not merged then it's possible to "undo" back to the image's initial loading state which the user would never want.
Updates that use discrete: true and the history-merge tag will properly squash the update, but only if there have been no other updates in between. There's no way to merge a new update into a previous update of arbitrary position in the history stack.
The current way to solve this is to track data in a separate map keyed by node key. It's cumbersome and feels like something that the library should provide a built-in solution for.
Lexical version: 0.9.0 (and earlier)
Steps To Reproduce

Insert an image node with a loading indicator. Asynchronously upload the desired image to your backend of choice.
Make random edits unrelated to the image
When the async upload finishes, update the placeholder image node with the new src attribute.
Trigger "undo" to reset the editor to state (2) where the image is still loading

Link to code example: https://codesandbox.io/s/lexical-plain-text-example-forked-usgq8e?file=/src/Editor.js
The current behavior
The user can "undo" back to an unwanted loading state.
The expected behavior
Previous history should be overwritten so that the user cannot return to unwanted loading states.

We allow uses to create their own history states with createEmptyHistoryState. You can then access it via context using something like the below which is on the playground:
  const {historyState} = useSharedHistoryContext();

This will give you access to the undo and redo stacks, which you can probably manually manipulate to edit existing editor states.

we allow uses to create their own history states with createEmptyHistoryState for these sort of edge cases

In my opinion, updating the editor as a result of an async action is not an edge case. It's anecdotal, but I've seen several people with similar issues in the Lexical Discord.

@montlebalm did you get any further with handling this? I have similar questions around the handling of preview+loading progress states within nodes without causing a bunch of unwanted and problematic history states

Unfortunately no. I was hoping to get a response to my last comment regarding the expected way to handle these async updates.
Our current workaround is to keep this kind of data out of lexical as much as possible. For example, it feels natural to store an image's src on its node, but we have to keep it as React state since it's modified once the upload completes. It's inconvenient and makes serialization more difficult.

I see that we didn't get a full resolution here, so I'm reopening so we can keep track of it

Our current workaround is to keep this kind of data out of lexical as much as possible. For example, it feels natural to store >an image's src on its node, but we have to keep it as React state since it's modified once the upload completes. It's >inconvenient and makes serialization more difficult.

I don't think this is bad. One strategy we make use of internally that bypasses this problem completely is storing some sort of ID on the node, then using that to fetch or generate a URL at runtime and encapsulating the logic for doing that in the React component. @fantactuka is working on documenting this pattern.
I realize that it suggests a change in architecture, and I'd love to get you a solution that doesn't force that, but I did want to call this one out. It's not without it's own complexities, though.

Maybe a different history tag with slightly different semantics (like history-ignore or history-discard) could solve this

Throwing in my use case:

I have special element nodes that get numbered
these nodes only exist at the root
I use registerMutationListener to find when the nodes are added and deleted
I update the numbers

With no way to "merge" undo states all of my updates to the numbers create their own entry in the undo stack

Oh history merge worked well for me. Should be documented

Not really sure how this can be built-in, given async action can have any delay you'd have to go through whole history undo/redo stacks, find that node and patch it. So it has to be some sort of patch callback that will alter all historical snapshots exposed through API? Instead I'd suggest to go with what @thegreatercurve suggested above and use createEmptyHistoryState:

Create own history stack so that you have pointer to it
When async action has finished you run editor.update with historic tag (a.k.a. history-ignore)
Run through history stack (since now you have pointer) and alter node value there

I'd also consider caching async request results for few reasons: you might copy-paste node while it's still running async action and you'd likely want to reuse existing running request instead of starting a new one.

I think rewriting history could be a fine solution provided there are examples. Even better if lexical exports a helper utility.
Here's what I was able to come up with based on the natural language description of the process:
//
// Utility
//

const updateNode = <TNode extends LexicalNode>(
  stack: HistoryStateEntry,
  nodeKey: NodeKey,
  updater: (node: TNode) => void
): boolean => {
  //  Find the node in history. If we can't find it then we're past the point
  //  at which it was created.
  const node = stack.editorState.read(() => $getNodeByKey<TNode>(nodeKey));
  if (!node) return false;

  stack.editor.update(
    () => {
      updater(node);
      $addUpdateTag('history-ignore');
    },
    { discrete: true }
  );

  return true;
};

const updateHistoricalNode = <TNode extends LexicalNode>(
  history: HistoryState,
  nodeKey: NodeKey,
  updater: (node: TNode) => void
) => {
  // Update current state
  if (history.current) {
    updateNode(history.current, nodeKey, updater);
  }

  // Update undo history
  for (const stack of history.undoStack) {
    const updated = updateNode(stack, nodeKey, updater);
    if (!updated) break;
  }

  // Update redo history
  for (const stack of history.redoStack) {
    const updated = updateNode(stack, nodeKey, updater);
    if (!updated) break;
  }
};

//
// Usage
//

uploadImage(url).then((serverId) => {
  updateHistoricalNode(history, nodeKey, (node) => {
    node.setServerId(serverId);
  });
});

Does that look right? It could potentially cause a lot of updates based on the size of the undo/redo stack. Any suggestions on how to make it more efficient?

When async action has finished you run editor.update with historic tag (a.k.a. history-ignore)

Should "history-ignore" be "history-merge"? I don't see the ignore tag in the codebase.

I've arrived here because I have a similar, but not same use case.
In the editor a user can type /, which shows a menu, from which they can select an action. Actions are async, so upon choosing the action I insert a temporary "loading indicator" node in place of /. When a server responds, I insert the response as a text node, replacing the "loading indicator" node. I would not want ctrl + z to get user back to a state where the "loading indicator" node is visible, it should either be a final state, or the state before they typed /.

@fantactuka @thegreatercurve does my example look like what you'd expect? Any suggestions for improvement?

@fantactuka @thegreatercurve just following-up to see if my proposed approach matches your expectations

@fantactuka @thegreatercurve checking in again to see if y'all have any guidance on how to do the proposed history rewrite


Increment script L1->L2 now working in Cross Chain tutorial.

The script is fixed with added comments.
Some other minor fixes.
Running on latest Node.

tested and added a few minor changes @kailash-manasarovar @krofax


Overflowing Logos In the Website

Some company logos on the https://thanos.io/ website are overflowing from their respective containers
For example Cloud & Heat, Infinite Devices
Screenshot of the same:

Environment:

OS (e.g. from /etc/os-release): Ubuntu 20.04
Kernel (e.g. uname -a): Linux Kernel 5.8

Yes, help wanted 🤗

I would love to work on it @bwplotka. Could you please assign it to me?😊


sqlalchemy.exc.OperationalError raised in the scheduler

When completed and new jobs are collected/updated in the database simultaneously the sqlite3.OperationalError database is locked is raised due to concurrent transaction timeout. This exception is immediately followed by sqlite3.ProgrammingError: SQLite objects created in a thread can only be used in that same thread.. I suppose that the latter error is raised by a parent thread trying to clean-up. Transaction is never closed and database gets locked indefinitely.
This issue seems to be specific to sqlite3 being unable to handle more than one transaction at the time.
Suggested actions:

make multiple short transactions within a single session instead of a large one
this error is inevitable and scheduler must be able to handle it gracefully.

Probably fixed, but the result will come out during more intensive stress testing.

The problem still occurrs. Try not store the list of output files in the database. Fetch it from the file system using the configuration files instead.

Fixed by 79de9f58c2a5aeed54cd0f20b9d41c6c81fbeedc


web version timestamp truncated

Dart JS supports only 32-bit bit manipulation. Therefore, UUID v7 does not work correctly.

I'll need more info, as my manipulations stick to 32bit and below. What's the actual error or problem?

uuid: ^4.3.2
void main() {
  print(const Uuid().v7());
  print(const Uuid().v7());
}

I wanted to use UUID v7, generate them on multiple machines, and sort them chronologically,
javascript version generated an invalid ke, so I couldn't sort chronologically.
<javascript>
f3b80000-2d78-7e3e-9214-d7b3935cab87
f3b80000-2d79-7fee-9238-9c2a18c4d2f1

<macOs>
flutter: 018cf3b7-9411-7ebf-bdc2-bf9e957ac16f
flutter: 018cf3b7-942d-7673-88ef-5abe52ba7c14

Ok, I can confirm it's truncation. I fixed it for v7 but found a related bug in v6. But it's trickier to fix, but I should have a new version with fixes soon

fixed in 4.3.3


Set DropEntry for CompatHelper

When looking through recent PRs, old compat entries are always dropped when updating compat entries. This PR sets  entry_type=DropEntry(), so that CompatHelper will drop existing compat entries.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 81.165%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1198

Relevant Lines:
1476

💛  - Coveralls

Hm I don't think that we usually want to do this - the recent PRs just happened to be updates of packages with many breaking changes that also affected Turing. If possible, I think we should keep compatibilities with previous versions and hence not dropping them would be the better default. For instance, there is no good reason for dropping support for SpecialFunctions 1 when upgrading to SpecialFunctions 2. In fact, it would be very disruptive for the package ecosystem if packages would remove compatibility with SpecialFunctions 1.

Ok :+1:


How to disable display of help text when sourcing "$(brew --prefix nvm)/nvm.sh"?

I have the following lines in my .bash_profile
export NVM_DIR="$HOME/.nvm"
. "$(brew --prefix nvm)/nvm.sh"

nvm seems to be working fine, but I get the Node Version Manager help text displayed on my console on every login. It also happens whenever I execute . "$(brew --prefix nvm)/nvm.sh" from any command line. Clearly, after sourcing the file, the nvm function is getting called with no arguments. What is causing that?
I'm running bash on Mac OS X El Capitan.

I solved my problem by commenting out this line of code at the bottom of the nvm.sh script:
#nvm_process_parameters "$@"

I hope that doesn't break anything.

@jeffmikels nvm is completely unsupported on homebrew, which the brew formula warns you about when installing it.
So first, definitely do not make any edits to nvm.sh, as that will break some functionality. However, I highly brew uninstalling it, and installing it properly with the curl command in the readme.

I removed the homebrew version of nvm.
I Installed it using the curl command.
I removed the lines from .bash_profile keeping the line from .bashrc
export NVM_DIR="/Volumes/Jeff/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"  # This loads nvm

I STILL get the nvm --help text on every Terminal window.
I think this is undesirable and therefore a bug.

@jeffmikels thanks for following up! would you be able to share the contents of .bashrc/.bash_profile that runs before the nvm lines?

Also, just to confirm - if you set your NVM_DIR to be $HOME/.nvm (the default) do you still see the same behavior?

To eliminate all bashrc and bash_profile problems, I can reproduce the problem using only sh.
sh -c "sh .nvm/nvm.sh"

This ignores all bash login scripts and still displays the nvm --help output.

Wow, that's super odd - the env -i should use the default NVM_DIR. However, is this .nvm directory still on /Volumes/Jeff instead of inside $HOME? It'd be ideal to test env -i on $HOME/.nvm/nvm.sh specifically

/Volumes/Jeff = $HOME
Jeff Mikels
Pastor, Lafayette Community Church
helping people find full life in Christ
http://jeff.mikels.cc
http://lafayettecc.org
765-404-0807
Jesus: "I have come that they may have life, and have it to the full."
-- John 10:10 --
On Fri, Jun 10, 2016 at 4:35 PM, Jordan Harband<EMAIL_ADDRESS>wrote:

Wow, that's super odd - the env -i should use the default NVM_DIR.
However, is this .nvm directory still on /Volumes/Jeff instead of inside
$HOME? It'd be ideal to test env -i on $HOME/.nvm/nvm.sh specifically
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/creationix/nvm/issues/1113#issuecomment-225288738,
or mute the thread
https://github.com/notifications/unsubscribe/ADV_ZGZDeEs49qIuSXhYpMWNkSOL54D5ks5qKcqTgaJpZM4IyYvX
.

aha, i wonder if having $HOME be a volume, instead of a dir on the OS volume, could be causing issues. Can you clarify if you have a .nvmrc file anywhere (in whichever directory you run these commands in, or, in any directory upwards to /), and if so, what's in it?

I can't see how it would matter, and this error only started recently.
However, I installed nvm under another user account on my Mac where $HOME
points to a directory under /Users and the nvm.sh script executes properly
without displaying the help text.
Therefore, I think it must have something to do with my user environment OR
with the fact that the HOME directory is in a non-standard location.
Further testing must be done.

Thanks for working through it so far :-) My suspicion is having it on a separate volume. If you could share your bash profile file in a gist (with sensitive parts blotted out) that might help as well.

I moved the .bash_profile and the .bashrc out of my home directory
entirely, opened a new terminal and the error persisted. Something in the
script must be incompatible with my HOME setup.
When I log in without the .bash_profile or .bashrc, this is what my
environment looks like:
TERM_PROGRAM=Apple_Terminal
SHELL=/bin/bash
TERM=xterm-color
TMPDIR=/var/folders/gj/8bp694f15qb2zhl4q3l5ns700000gn/T/
Apple_PubSub_Socket_Render=/private/tmp/com.apple.launchd.B0l1jhHDO4/Render
TERM_PROGRAM_VERSION=361.1
TERM_SESSION_ID=1348E86F-150B-4D06-906C-7933E4BD5517
USER=jeff
SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.nBlUQKJ1Zo/Listeners
__CF_USER_TEXT_ENCODING=0x1F5:0x0:0x0
PATH=/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/opt/ImageMagick/bin
PWD=/Volumes/Jeff
LANG=en_US.UTF-8
XPC_FLAGS=0x0
XPC_SERVICE_NAME=0
SHLVL=1
HOME=/Volumes/Jeff
LOGNAME=jeff
DISPLAY=/private/tmp/com.apple.launchd.5wvMIsQ6gY/org.macosforge.xquartz:0
SECURITYSESSIONID=186aa

Is /Volumes/Jeff case-sensitive, or case-insensitive?

Mac default... Case Insensitive

I have confirmed the following strange behavior:
cd /Volumes; . $HOME/.nvm/nvm.sh
cd /; . $HOME/.nvm/nvm.sh

No help text shown in either case.
cd /Volumes/Jeff; . $HOME/.nvm/nvm.sh

Help text IS shown.
The help text displays depending on the current working directory, and only seems to show when my current working directory is /Volumes/Jeff

Do you see the same behavior when you run nvm_auto use? What does nvm alias default report?

I DO get the same behavior with nvm_auto use.
nvm alias default reported nothing so I assigned it using nvm alias default 4.4.3 and now everything is FIXED!
The help text no longer shows up unless I want it to.
Why would that make a difference?
Before, I had these aliases set:
$ nvm alias

node -> stable (-> v4.4.3) (default)
stable -> 4.4 (-> v4.4.3) (default)
iojs -> N/A (default)

Now, I have these:
$ nvm alias

default -> 4.4.3 (-> v4.4.3)
node -> stable (-> v4.4.3) (default)
stable -> 4.4 (-> v4.4.3) (default)
iojs -> N/A (default)

OK - in that case, it's related to the automatic behavior of .nvmrc where nvm tries to crawl up the tree to / to locate config files - nvm_rc_version in that dir probably returns 0, but afterwards what does echo $NVM_RC_VERSION say?

Currently, echo $NVM_RC_VERSION yields nothing. Also, my .nvmrc file exists in $HOME but is empty.

ok that's the issue :-) the file is assumed to have contents if it's present.
I assume as well that if you nvm unalias default && rm "$HOME/.nvmrc" that everything works fine?

Yes, yes it does. If .nvmrc exists and is empty, I get the undesirable behavior. If .nvmrc does not exist, things work as they should. However, the script seems to only care if .nvmrc is in the current working directory because as noted before, when I was in a different directory, the help text would not show up.
Finally, I was under the assumption that nvm would handle configuration files the way other tools do, that is, settings in config files should override the existing defaults and configuration settings specified on the command line would get saved into the config file for future use. I touched the .nvmrc assuming that file needed to exist to make my settings persistent.
Is there documentation about the .nvmrc that I missed somewhere?

Found it... now I understand. .nvmrc is not a user level configuration file. It is a project level configuration file.

That's correct - although it's totally fine to use it at the user level, and I do so. It just can't be an empty file :-)
I'm going to reopen this to track fixing the issue though, an empty .nvmrc file should probably just be ignored.

Thanks for working through this with me.

Thank you!!


ModularPods will not install

This will download the file, but then tell me it can't install, as the file is not downloaded or is corrupt.

There was a new release, is this fixed now?


Remove "-inkscape-font-specification"

Even when exporting plain SVG's through Inkscape, there are cases where it inserts an "-inkscape-font-specification" inside an object style.
This style isn't considered, also because the standard font-family attribute is generated as well.
Thus, there are two cases for optimization:
Case 1 - Inkspace font style together with other styles
In this case, only the "-inkscape-font-specification" must be removed.
<!-- This -->
<text style="-inkscape-font-specification:'Source Sans Pro Bold';text-align:center">...</text>

<!-- Should become this -->
<text style="text-align:center">...</text>

Case 2 - Inkspace style alone
In this case, all the style attribute must be removed.
<!-- This -->
<text style="-inkscape-font-specification:'Source Sans Pro Bold'">...</text>

<!-- Should become this -->
<text>...</text>

SVGO doesn't remove vendor prefixes (and all unknown attributes). It can be improved in convertStyleToAttrs plugin.

Ok, thanks!

Does that mean, we have to manually update the script locally?

I believe that we should create a new plugin, which is optional, to work in such cases. This way it becomes an option. Unfortunately, I am not with free time enough to work on this right now.

I'm having the same problem. Did anyone come up with a solution?

I'm having the same problem. Did anyone come up with a solution?


Pull commit from all forks

Pull commit from this forks:

https://github.com/ganeshapp/redpush
https://github.com/ravikannankr/redpush

https://github.com/ganeshapp/redpush and https://github.com/ravikannankr/redpush are synchronized.

Done.


ARROW-16590: [C++] Consolidate files dealing with row-major storage

The primary goal of this refactor of old code was to improve the readability and clarity of the code base. I did not make any functional changes to the code and if any functional changes are suggested which modify existing code I will happily discuss them here but defer the changes themselves to follow-up PRs. I would very much appreciate any feedback on naming, making sure we have sufficient test coverage, and overall layout of the code.

KeyRowArray -> RowTableImpl KeyEncoder -> RowTableEncoder: The old name made sense because this data is currently represented physically as an array of rows. However, the data is conceptually tabular. We are storing rows & columns. In particular, I found it confusing that KeyColumnArray was a 1D data structure while KeyRowArray was a 2D table structure.
KeyEncoder::Context -> LightContext: There's nothing particular to the key encoder here and I worry keeping it there may lead to fracturing into many different "context" objects.
Overall structure: I created a new folder arrow/compute/row and put all row-based utilities in here. Most of the files are now marked as _internal and the content in these files is not used outside of arrow/compute/row. The grouper had previously been alongside the kernel code and it didn't really belong there as it relies very heavily on the internal structure of the row encoding.
Row structure: I documented the file arrow/compute/row/row_internal.h

CI failures appear unrelated.


1.1.0 migration: "Module adapter for class X could not be loaded. Please ensure that code generation was run for this module"

I'm testing the upgrade from 1.0.1 to 1.1.0 (Maven, Java 7), and added the new dagger-compiler dependency as described, but all my TestNG tests - which call ObjectGraph.create( new MyModule() ) as a final static - now fail:
[snip]
Caused by: java.lang.IllegalStateException: Module adapter for class blah.MyModule could not be loaded. Please ensure that code generation was run for this module.
at dagger.internal.FailoverLoader.getModuleAdapter(FailoverLoader.java:41)
at dagger.internal.Modules.getAllModuleAdapters(Modules.java:43)
at dagger.ObjectGraph$DaggerObjectGraph.makeGraph(ObjectGraph.java:167)
at dagger.ObjectGraph$DaggerObjectGraph.access$000(ObjectGraph.java:134)
at dagger.ObjectGraph.create(ObjectGraph.java:126)
at blah.MyTest.(MyTest.java:53)
... 26 more
I can paste the Module, if you like.
Are there any more steps I need to take?

I got this problem too.... how can i fix?


PWA: unblur spinner on pageshow

happened when hitting the back button and it was bugging me so hard I fixed it tonight :muscle:
These were the interesting reads:

pointing me to the event that worked on pageload: https://christopheraue.net/design/fading-pages-on-load-and-unload
more info on the page lifecycle and the chrome exclusive APIs if this fix does not work everywhere: https://developer.chrome.com/blog/page-lifecycle-api/

This is related to my comments on #357, but not the initial part about it not working on iOS. Maybe @jeriox can have another look?

Coverage: 88.287%. Remained the same when pulling eb70a94c4433fe0194526f7f3c58cb017778c4d9 on pwa-clear-spinner-on-back into 3b0a0b3b02e8cb81a93313e9236420615d77864f on main.

Coverage: 88.287%. Remained the same when pulling eb70a94c4433fe0194526f7f3c58cb017778c4d9 on pwa-clear-spinner-on-back into 3b0a0b3b02e8cb81a93313e9236420615d77864f on main.

omg great! will have a look on iOS once i have my iPad at hand

Seems like it's a known "bug" in webkit (see https://bugs.webkit.org/show_bug.cgi?id=199854 )
I could not find a solution for iOS


[FEATURE] Configurable Spawn Rate and Location for Scrolls

The ability to tweak where and how Hex scrolls spawn in chest loot would be useful for pack development. Packdevs could gate Hex later in a pack, make scrolls scarcer to incentivize exploration, or tweak where scrolls spawn (for example, a custom loot table for a special Hex ruins structure).

You can do this with a datapack I'm pretty sure


Design Meeting Notes, 10/12/2022

ESM Migration

Transition is mostly done - running, tested, working.
Currently awaiting some dependencies.
Wanted to use API Extractor here.

Can't shadow top-level globals (e.g. Node, Symbol)
Doesn't support module augmentations.
We made an ad-hoc .d.ts bundler - works for us because of the nature of our API.

New APILibCheck test that validates that the bundler is doing its job.

Similar to the API sample tests.

Single entry-point, easy enough to support.
A few things to fix there.
--stripInternal?

We are more aggressive about preserving JSDoc comments than others - so we switched all the /* @internal */ comments to /** @internal */.

What's checker.ts look like?

Top of the file is awful.
Auto-import works, doesn't insert in the right place.

Probably a case-sensitivity bug.

What are the _namespace/ts.ts files?

They are "barrel" files that ensure correct initialization.

How should new code be authored?

New code should reference the _namespace/ts.ts file.
Auto-imports just do the right thing anyhow.

Have avoided many tooling issues around git blame thanks to a new file called .git-blame-ignore-revs.
"Scary" that we're not using our own emit.

CI will always verify that the compiler runs properly with bundling enabled.
Can enable that locally with hereby --bundle false

hereby?

hereby!
The module migration will break lots of our bisect tooling anyway. Good opportunity to change stuff.
gulp has audit problems, 20% of our install time, not really leveraging all of the features.
@jakebailey made a small tool called hereby which is a quick and fast for our purposes.
Trade-offs?

No watch mode, but nobody on the team was building with watch mode.

Not off the table long-term.

Why is it called hereby?

It was just a funny thing to call it. Can come up with another name.

So...when do we want to type-check?

Need to figure out the core team's inner dev loop.

Enum Fixes and Improvements
#50528

First, we consider some mixed enums to be possibly numeric enums (#40862)
enum Stringy {
    hello = "hi"
}

enum OhNo {
    zero = 0,
    str = Stringy.hello,
}

// Today, no error.
const x: number = OhNo.str;

Another issue: when referencing a property off of a value whose symbol appears declared by an enum, then within some enum declaration, we will inline its initializer.

In #40793, someone asked to concatenate enums to create new enums.

The idea to fix is to more cleanly split the world between numeric and literal enums.

literal enum initializers are

string literals (no placeholders)
concatenation of string literals with +
numeric literals (possibly prefixed by + or -)
an identifier naming a member of the (current?) enum

enums are literal enums if

all their members have literal enum initializers

it is an error for any initializer to be a string literal or a string literal concatenation, outside of literal enums.

Need to make sure bundlers/compilers work well here (e.g. esbuild, babel).

What about the proposal for template strings in #40793?

Would be odd if we allowed string literal types.

Doesn't feel like this is a deal-breaker.

What about the breaks to fix the problems with the motivating code?

We feel like they're not widespread, easy to get around.

Feel like we should separate out the fixes from the new features.

but nobody on the team was building with watch mode.

do you mean gulp watch-min?

I use watch-min mainly for continuous type checking and the output is always fresh. The latter is important when developing with tsserver. If the tsserver is always fresh, I can run Restart TS server in my debugging VSCode session and reload the language server. If there is no watch mode, I'll need to do two things to reload it.

Most build tasks will no longer be type checking (now only needed for d.ts emit, which is only done for local, lkg, and runtests); but I am adding a watch task in VS Code which will do that if needed for the whole workspace. But, that won't get you the outputs anymore.
I'll see how bad it is to reimplement a watch mode in the new build. I avoided it since it was already half broken in the old build and nobody I talked to actually used it.

Seems like I can add something similar back, though it won't be 100% (no watch mode for the d.ts files), but that's fixable in time. I'll add the tasks back to the branch.

Though I guess that eats up a terminal.

I know it's editor-specific, but when building VS Code, they have a build task that shows two concurrent watch steps side-by-side. We could do the same with type-checking and building.

it sounds like you can always just run tsc -b tsconfig.json --watch, right?

Yes, that gets you compiler errors for the workspace, but not the outputs as those aren't produced by tsc. I have explicitly supported this on the new branch:

Where it'll run tsc over the whole project and you'll get compiler errors.

I know it's editor-specific, but when building VS Code, they have a build task that shows two concurrent watch steps side-by-side. We could do the same with type-checking and building.

Now that I've restored watch mode for the actual output files (besides non-bundler/tsc files), we can add another for the actual outputs if wanted.

just curious, what bundler are you using? rollup? esbuild (but it does not support es5 emit)?

esbuild, see #49332, or my stack on https://github.com/jakebailey/TypeScript/pull/1. Or, see the PR next week, probably!


feat: Spark Streaming using Spark Operator

What does this PR do?
🛑 Please open an issue first to discuss any significant work and flesh out details/direction - we would hate for your time to be wasted.
Consult the CONTRIBUTING guide for submitting pull-requests.
This will provision a stack for Spark streaming from Amazon MSK, doesn't need to be from MSK, could be replaced with Kafka in strimzi for example. The most value of the solution is showing examples of applications working in this stack using the operator and spark streaming.
Motivation
Customer requested PoC
More

[X] Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
[X] Mandatory for new blueprints. Yes, I have added a example to support my blueprint PR
[X] Mandatory for new blueprints. Yes, I have updated the website/docs or website/blog section for this feature
[X] Yes, I ran pre-commit run -a with this PR. Link for installing pre-commit locally

For Moderators

[ ] E2E Test successfully complete before merge?

Additional Notes

Nice work on this PR @lusoal ! PR looks good to me. I presume that you have tested the blueprint end to end. Please ask some of our internal teams to run through the instructions. I would also add a warning to the website doc for any security requirements that needs to be tighten if they implement this in prod.

Yes I tested indeed! Will ask to someone else to execute the steps. Thanks @vara-bonthu


Add CommitmentInput - python

https://github.com/iotaledger/tips-draft/blob/tip45/tips/TIP-0045/tip-0045.md#commitment-input

Closed by https://github.com/iotaledger/iota-sdk/pull/1228


T-A7670G GPS not working.

Hi all,
I have two T-A7670Gs.
The HW version is V1.2 (2022-7-18).

I want to use real time GPS tracking.
But the GPS doesn't work.

additional information as below.
AT+SIMCOMATI
Manufacturer: INCORPORATED
Model: A7670G-LLSE
Revision: A011B15A7670M7
A7670M7_B15V01_230111

7670G  nosupport gps

7670G no support gps

You should fix your AliExpress listing then:

Check your order and send it to customer service for confirmation


Update examples.rst

Added a missing linespace.
Last one, I promise.

Coverage remained the same at 44.1% when pulling 7ee7804daaea12c4551ac1d4e71998831f2dea0d on davidyell:issue-280 into c765e225e126494327b853104dbde9e94238e79c on josegonzalez:master.

Now you need to fix the tests :P

Yep. Getting coverage up is on my list
On Wed, 4 Feb 2015 17:18 Jose Diaz-Gonzalez<EMAIL_ADDRESS>wrote:

Now you need to fix the tests :P
--
Reply to this email directly or view it on GitHub
https://github.com/josegonzalez/cakephp-upload/pull/284#issuecomment-72896605
.


Optimizations

Major features

Minor features

Improvements

Cached more stuff to improve loading times. Implements #710
Cleaned up how planets are destroyed. Should make load screens faster. Implements #573

Bug fixes

Whoever reviews this can you like, test it on mods. Incursion would be a good one, fly out of the system and check proxies.


Consistent formatting (Python Black)

Given that we have different authors with different styles, our formatting/conventions are not consistent. We should look into using something like yapf or black to make our code consistent and maybe pydocstyle for our documentation.

As part of this, also:

make sure names are properly formatted (snake_case for variables, etc)
add linter (for code and docstrings) to CI

After everything else has stabilized, run this on everything.

Chiming in here from the pyOpenSci review.
We do require this--indirectly--by asking that linting checks pass.
As you comment above, I would address other issues first and then add linting.
There are many ways to skin this cat, see https://learn.scientific-python.org/development/guides/style/
I use a nox session so anyone can run linting checks locally without learning the pre-commit CLI but you could also just let contributors remain mostly blissfully ignorant of linting, and run pre-commit in CI on PRs, etc.
How you do it is up to you but there should be some linting checks.

[in progress] Interim Summary of Considerations so Far:
We are currently looking at  Ruff and optional  pre-commit hook to introduce formatting conventions. Below is a brief consideration of ruff and pre-commit, as well as a list of their respective configurations and a brief explanation of each.
Ruff Linting:
Ruff has been chosen for its speed and efficiency in identifying common Python code issues.
Configurations:
TODO
Nox
TODO
Optional Pre-Commit
Hook: A pre-commit hook can be added to run Ruff linting on code before it is committed. This ensures that developers catch and fix linting issues early in the development process.
TODO: can be manually turned off
Configurations:  (see .pre-commit.yaml:
Legend: ✅: included, ❓: recommended, but not inlcuded)

check-added-large-files  ✅

Purpose: Checks for large files added to the repository, typically to prevent accidental inclusion of large binaries or datasets.

check-case-conflict ✅

Purpose: Detects potential filename conflicts due to case-insensitive filesystems (e.g., Windows) where File.txt and file.txt would be considered the same

check-merge-conflict ✅

Purpose: Checks for leftover merge conflict markers (<<<<<<<, =======, >>>>>>>) in files.

check-symlinks ❓

Purpose: Verifies that symbolic links are valid and do not point to non-existent targets.

check-yaml✅

Purpose: Validates YAML files for syntax errors.

debug-statements ✅

Purpose: Detects debug statements (e.g., print, console.log) left in code.

end-of-file-fixer✅
- Purpose: Ensures files have a newline at the end.
mixed-line-ending❓

Purpose: Checks for files with mixed line endings (e.g., both LF and CRLF).

Pros: Prevents compatibility issues across platforms, ensures consistent line endings.
Cons: Can require adjustments for projects that intentionally use mixed line endings for specific reasons.
name-tests-test ✅

Purpose: Renames test files to follow a standard naming convention, often starting with test_.

requirements-txt-fixer❓

Purpose: Standardizes the format of requirements.txt files, ensuring they follow conventions and are easy to manage.
Requires adjustments for projects with complex dependency requirements.

trailing-whitespace✅

Purpose: Removes trailing whitespace characters from files.

CI Pipeline:
Finally, the CI configuration has been updated to include a step for running Ruff  formatting and linting check on all new commits and pull requests. Two separate actions were chosen to signal the developer which combination of the two might be causing an error.

Now, that the ruff linter and formatter have been introduced (see PR #266), possible next steps to consider are as follows:
Note that if additional linting rules are to be introduced (e.g., B), each rule should be introduced in a separate PR. Therefore, we may want to consider closing this big issue and using my notes below and putting them in separate smaller issues.
Next steps:
0. restructure contributing file (see issue #296)
1.Ruff Linting
Include the following linting rules (in pyproject.toml ) and resolve linting errors:

B (flake8-bugbear):
Checks for common programming errors, style issues, or patterns that are error-prone
ARG (flake8-unused-arguments):
Flags unused function arguments.
C4 (flake8-comprehensions):
Checks for issues in list comprehensions and generator expressions.
EM (flake8-errmsg):
Lints error message formatting.
ICN (flake8-import-conventions):
Ensures imports are formatted according to best practices.
PTH (flake8-use-pathlib):
Encourages the use of pathlib instead of os.path.
RET (flake8-return):
Checks for issues related to return statements.
SIM (flake8-simplify):
Suggests simplifications for code.
T20 (flake8-print):
Flags print statements.
UP (pyupgrade):
Upgrades syntax to modern Python standards.
YTT (flake8-2020):
Enforces Python 3.8+ compatibility.

2. Nox:
We might want to consider to include nox sessions for:

format: Runs code formatting too
docs: Builds and verifies the project's documentation to ensure it's up to date and properly rendered.
type check: uses mypy or a similar tool to perform static type checking,  to catch type-related errors early.

3. Pre-commit
We might want to add the following to .pre-commit-config.yaml :

mixed-line-ending

Purpose: Checks for files with mixed line endings (e.g., both LF and CRLF).

Pros: Prevents compatibility issues across platforms, ensures consistent line endings.
Cons: Can require adjustments for projects that intentionally use mixed line endings for specific reasons.

requirements-txt-fixer

Purpose: Standardizes the format of requirements.txt files, ensuring they follow conventions and are easy to manage.
Requires adjustments for projects with complex dependency requirements.


[SUPPORT] how to migrate  exist bloom index table to bucket table

Are there any documentation that provide migrate  exist   table of bloom index to bucket index ?
Hudi version :0.11.1
Spark version :3.2.2
Hive version :3.1.3
Hadoop version :3.3.2

ok,I appreciate your answers.


walingest/walredo: simplify Visibility Map flag clearing code

While working on https://github.com/neondatabase/neon/pull/6002 I found there was some repetition in the code paths for Visibility Map flag clearing.
This PR reduces the repetition, uses less mutable state, and less confusing control flow.
At least to me, it makes it clearer what's going on.
I understand the Visibility Map is quite a critical structure, so, reviewers, please apply extra scrutiny here.

Different from this PR:

I kept the if-else logic to decide whether to write one or two ClearVisibilityMapFlags records, instead of converting it to a match statement
I didn't rename the ClearVisibilityMapFlags fields. You made that change because you changed the logic so that you could no longer tell from the ClearVisibilityMapFlags record anymore whether the change corresponds to the old or the new block of an UPDATE record. I think that would be fine, we don't really need to know that, but I'm not eager to change it unless there's a reason.

Fine with leaving these out as well.
Can you please open a PR for your branch? I'll close this one.

Ok, here's a PR with that: https://github.com/neondatabase/neon/pull/6274


E2: Add remaining Lua escape sequences

See https://www.lua.org/pil/2.4.html
Fixes #1905
Untested.

Didn't find any issues in my test

I don't like the string of if then elseif statements. Why not something like (untested):
local special_escape_seqs = {'a', 'b', 'f', 'n', 'r', 't', 'v'}

if self.character == "\\" then
    for _, char in pairs(special_escape_seqs) do
        if self.character == char then
            self.tokendata = self.tokendata .. "\" .. char
            self:SkipCharacter()
            break
        end
        self:NextCharacter()
    end
else
    self:NextCharacter()
end

I've noticed the same pattern in Tokenizer:NextSymbol(). Is this because of a conscious design choice that I've missed, or is a minor refactor due?

That loop would be even slower. A lookup table would be best, but it doesn't really matter.

A lookup table makes sense. It's a minor refactor that only takes a few minutes to implement, and I like to live by the "if it takes less than 5 minutes do it now" rule #1916


1.6 release status

Not much on the radar yet that is important; targeting early June for what currently exists.

[x] UniformBytesPartitioner
[x] UnsafeReadFrom for kmsg (for advanced use cases, no option in the client for now)

[x] kmsg 1.1

[x] unnecessary optimizations in the sticky balancer
[x] kadm API audit, potential stabilization
[x] #110
[x] Add debug logs to retries on unknown coordinator
[x] kversion.V3_2_0
[x] #166
[x] bugfix LogAppendTime fetch timestamp (a23a076629f395a572e026322ca7feec39708e0d)

Released: https://github.com/twmb/franz-go/releases/tag/v1.6.0


ClusterIP service not honouring sessionAffinity: ClientIP in v1.16.1 and v1.15.3 (no KPR)

Is there an existing issue for this?

[x] I have searched the existing issues

Version
equal or higher than v1.16.0 and lower than v1.17.0
What happened?
In cilium v1.15.x a non-headless ClusterIP service is not honouring sessionAffinity: ClientIP.
curl -s my-clusterip-service:80

Served on port 80 by my-nginx-deployment-fc744ddc5-mvm86
Served on port 80 by my-nginx-deployment-fc744ddc5-mvm86
Served on port 80 by my-nginx-deployment-fc744ddc5-llzf5
Served on port 80 by my-nginx-deployment-fc744ddc5-llzf5
Served on port 80 by my-nginx-deployment-fc744ddc5-vcmtd
Served on port 80 by my-nginx-deployment-fc744ddc5-llzf5
Served on port 80 by my-nginx-deployment-fc744ddc5-llzf5
Served on port 80 by my-nginx-deployment-fc744ddc5-xzsgz
Served on port 80 by my-nginx-deployment-fc744ddc5-vcmtd
Served on port 80 by my-nginx-deployment-fc744ddc5-llzf5
...

And exec inside the container (confirming it's not a headless service):
minikube kubectl -- exec -it my-web-client-5fdbf7ddf8-2486j -- bash
root@my-web-client-5fdbf7ddf8-2486j:/# apt-get update && apt-get install dnsutils
...
root@my-web-client-5fdbf7ddf8-2486j:/# nslookup my-clusterip-service
;; Got recursion not available from <IP_ADDRESS>
Server:		<IP_ADDRESS>
Address:	<IP_ADDRESS>#53

Name:	my-clusterip-service.default.svc.cluster.local
Address: <IP_ADDRESS>
;; Got recursion not available from <IP_ADDRESS>

root@my-web-client-5fdbf7ddf8-2486j:/# curl -s <IP_ADDRESS>
Served on port 80 by my-nginx-deployment-fc744ddc5-llzf5
root@my-web-client-5fdbf7ddf8-2486j:/# curl -s <IP_ADDRESS>
Served on port 80 by my-nginx-deployment-fc744ddc5-llzf5
root@my-web-client-5fdbf7ddf8-2486j:/# curl -s <IP_ADDRESS>
Served on port 80 by my-nginx-deployment-fc744ddc5-vcmtd
root@my-web-client-5fdbf7ddf8-2486j:/# curl -s <IP_ADDRESS>
Served on port 80 by my-nginx-deployment-fc744ddc5-vcmtd
root@my-web-client-5fdbf7ddf8-2486j:/# curl -s <IP_ADDRESS>
Served on port 80 by my-nginx-deployment-fc744ddc5-vcmtd
root@my-web-client-5fdbf7ddf8-2486j:/# curl -s <IP_ADDRESS>
Served on port 80 by my-nginx-deployment-fc744ddc5-vcmtd
root@my-web-client-5fdbf7ddf8-2486j:/# curl -s <IP_ADDRESS>
Served on port 80 by my-nginx-deployment-fc744ddc5-vcmtd
root@my-web-client-5fdbf7ddf8-2486j:/# curl -s <IP_ADDRESS>
Served on port 80 by my-nginx-deployment-fc744ddc5-xzsgz

root@my-web-client-5fdbf7ddf8-2486j:/# curl -s my-clusterip-service
Served on port 80 by my-nginx-deployment-fc744ddc5-xzsgz
root@my-web-client-5fdbf7ddf8-2486j:/# curl -s my-clusterip-service
Served on port 80 by my-nginx-deployment-fc744ddc5-xzsgz
root@my-web-client-5fdbf7ddf8-2486j:/# curl -s my-clusterip-service
Served on port 80 by my-nginx-deployment-fc744ddc5-mvm86
root@my-web-client-5fdbf7ddf8-2486j:/# curl -s my-clusterip-service
Served on port 80 by my-nginx-deployment-fc744ddc5-xzsgz
root@my-web-client-5fdbf7ddf8-2486j:/# curl -s my-clusterip-service
Served on port 80 by my-nginx-deployment-fc744ddc5-llzf5
root@my-web-client-5fdbf7ddf8-2486j:/# curl -s my-clusterip-service
Served on port 80 by my-nginx-deployment-fc744ddc5-llzf5

See the tar.gz with a simple set of manifests to repro. Same repro works correctly with other CNIs.
How can we reproduce the issue?
Just apply the manifests in this tar.gz, and check output of my-web-client:
bug_affinity_manifests.tar.gz
Cilium Version
v1.16.1. v1.15.3 is also affected.
Kernel Version
6.1.0-22-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.94-1 (2024-06-21) x86_64 GNU/Linux
Kubernetes Version
1.31.0 (minikube 1.34.0).
Tried also with 1.30.0 (minikube 1.33.1), cilium 1.15.3.
Regression
No response
Sysdump
cilium-sysdump-20241006-180423.zip
Relevant log output
No response
Anything else?
No response
Cilium Users Document

[ ] Are you a user of Cilium? Please add yourself to the Users doc

Code of Conduct

[x] I agree to follow this project's Code of Conduct

I forgot to mention that it makes no different whether internalTrafficPolicy: Local is commented or not. With kube-proxy-replacement=false fails no matter (an execution withoout internalTrafficPolicy: Local):
kubectl describe service my-clusterip-service
Name:                     my-clusterip-service
Namespace:                default
Labels:                   <none>
Annotations:              <none>
Selector:                 app=my-nginx-app
Type:                     ClusterIP
IP Family Policy:         SingleStack
IP Families:              IPv4
IP:                       <IP_ADDRESS>
IPs:                      <IP_ADDRESS>
Port:                     web  80/TCP
TargetPort:               80/TCP
Endpoints:                <IP_ADDRESS>:80,<IP_ADDRESS>:80,<IP_ADDRESS>:80 + 1 more...
Port:                     web-alt  8080/TCP
TargetPort:               8080/TCP
Endpoints:                <IP_ADDRESS>:8080,<IP_ADDRESS>:8080,<IP_ADDRESS>:8080 + 1 more...
Session Affinity:         ClientIP
Internal Traffic Policy:  Cluster
Events:
  Type     Reason                        Age    From                       Message
  ----     ------                        ----   ----                       -------
  Warning  FailedToUpdateEndpointSlices  2m13s  endpoint-slice-controller  Error updating Endpoint Slices for Service default/my-clusterip-service: failed to create EndpointSlice for Service default/my-clusterip-service: Unauthorized

kubectl logs my-web-client-5fdbf7ddf8-tqxn8 | tail -n 10
Served on port 80 by my-nginx-deployment-fc744ddc5-s756d
Served on port 80 by my-nginx-deployment-fc744ddc5-prk2h
Served on port 80 by my-nginx-deployment-fc744ddc5-26l2d
Served on port 80 by my-nginx-deployment-fc744ddc5-s756d
Served on port 80 by my-nginx-deployment-fc744ddc5-prk2h
Served on port 80 by my-nginx-deployment-fc744ddc5-prk2h
Served on port 80 by my-nginx-deployment-fc744ddc5-s756d
Served on port 80 by my-nginx-deployment-fc744ddc5-26l2d
Served on port 80 by my-nginx-deployment-fc744ddc5-ttnsk
Served on port 80 by my-nginx-deployment-fc744ddc5-ttnsk

With kube-proxy-replacement=true, after redeploying, works as expected:
#cilium config set kube-proxy-replacement true
✨ Patching ConfigMap cilium-config with kube-proxy-replacement=true...
♻  Restarted Cilium pods

Served on port 80 by my-nginx-deployment-fc744ddc5-466ld
Served on port 80 by my-nginx-deployment-fc744ddc5-466ld
Served on port 80 by my-nginx-deployment-fc744ddc5-466ld
Served on port 80 by my-nginx-deployment-fc744ddc5-466ld
Served on port 80 by my-nginx-deployment-fc744ddc5-466ld
Served on port 80 by my-nginx-deployment-fc744ddc5-466ld
Served on port 80 by my-nginx-deployment-fc744ddc5-466ld
Served on port 80 by my-nginx-deployment-fc744ddc5-466ld
Served on port 80 by my-nginx-deployment-fc744ddc5-466ld
Served on port 80 by my-nginx-deployment-fc744ddc5-466ld
Served on port 80 by my-nginx-deployment-fc744ddc5-466ld
Served on port 80 by my-nginx-deployment-fc744ddc5-466ld

Does it help if you enable --enable-session-affinity?

Does it help if you enable --enable-session-affinity?

Let me check later today.  The run is with vanilla minikube start --cni=cilium. With KPR, there wasn't the need to set this to true to make it work.
Btw, session stickiness sessionAffinity: ClientIP:
https://kubernetes.io/docs/concepts/services-networking/service/#session-stickiness
is a stable feature. Cilium didn't complain (I think), and forwarded traffic to the service ignoring sessionAffinity: ClientIP, which doesn't seem right to me.
Should --enable-session-affinity flag be removed / ignored so that session stickiness works all the time when specified?

With kube-proxy-replacement=false indeed --enable-session-affinity=true is required for sessionAffinity: ClientIP to work.
Should we change this behaviour to:

Should --enable-session-affinity flag be removed / ignored so that session stickiness works all the time when specified?

I think there's two avenues we can pursue in parallel

improve the docs (consider where in the docs you looked when this didn't work ...), and improve reporting from the LB control plane (if a service asks for Service Affinity but Cilium doesn't support the feature, that's worth flagging?)
flip the default value for --enable-session-affinity to true. IIRC we didn't do this for BPF complexity reasons, but the situation has hopefully improved. Imho it's worth running it through CI and doing the change in v1.17.

improve the docs (consider where in the docs you looked when this didn't work ...), and improve reporting from the LB control plane (if a service asks for Service Affinity but Cilium doesn't support the feature, that's worth flagging?)

Agreed. Will issue one/two PRs for that, and might be worth backporting.

flip the default value for --enable-session-affinity to true. IIRC we didn't do this for BPF complexity reasons, but the situation has hopefully improved. Imho it's worth running it through CI and doing the change in v1.17.

Any chance we can just remove this flag entirely in 1.17, which would mean ignoring/warn the user that --enable-session-affinity is no longer required and will be ignored?
From what I can see here, the only requirement is a 5.7 Kernel. Is there any chance to bump the kernel version here to 5.7?

Any chance we can just remove this flag entirely in 1.17, which would mean ignoring/warn the user that --enable-session-affinity is no longer required and will be ignored?

Let's follow the usual deprecation strategy? I don't see why we should risk breaking users without giving them a way to restore old behavior.

From what I can see here, the only requirement is a 5.7 Kernel. Is there any chance to bump the kernel version here to 5.7?

FWIW I believe the 5.7 kernel requirement actually only applies to configs with SocketLB (see here). Otherwise it's just a matter of increased BPF complexity.
I don't think this sort of corner case should be driving the decision on a kernel version upgrade, we can just follow the regular schedule.

Let's follow the usual deprecation strategy? I don't see why we should risk breaking users without giving them a way to restore old behavior.

I am confused.
The only case in which the behaviour of the system would change is if users were to define their services with sessionAffinity: ClientIP but without --enable-session-affinity=true with kube-proxy-replacement=false.
This effectively means:

They have the wrong configuration; you have to explicitly added sessionAffinity: ClientIP in your SVC manifest, but it's actually not being honoured today. And this is a deliberate act, not defining it doesn't provide session stickiness.
Under this bogus scenario, the only change that removing the flag and warning the user could effectively produce is that traffic is distributed differently than before due to Cilium now honouring - as it should - sessionAffinity: ClientIP.

So to summarize:

they had the wrong configuration and...
they didn't realise it and...
the result of actually obeying the configuration that they themselves have set creates some imbalance in the traffic that they can't tolerate (which is possible, but unlikely).

I don't see why we should care about a user that does 1 and 2, especially given that the solution is to "properly fix" their manifests and remove sessionAffinity: ClientIP if 3) is a problem for them.
So I would still remove it, without any mercy, as long as there are no complexity reasons, as discussed below.

FWIW I believe the 5.7 kernel requirement actually only applies to configs with SocketLB (see here). Otherwise it's just a matter of increased BPF complexity.
I don't think this sort of corner case should be driving the decision on a kernel version upgrade, we can just follow the https://github.com/cilium/cilium/issues/34423.

That's fair.
Do we think or know if today Kernel 5.4 with --enable-session-affinity=true has any complexity issues in one or more knob combinations?

I don't see why we should care about a user that does 1 and 2, especially given that the solution is to "properly fix" their manifests and remove sessionAffinity: ClientIP if 3) is a problem for them.
So I would still remove it, without any mercy, as long as there are no complexity reasons, as discussed below.

Fully agreed - I think any user who unintentionally was not getting sessionAffinity support so far, will be very happy once we enable it by default. But BPF complexity limits are a real thing, the relevant LB code is in the critical path, and we don't have full CI coverage for all configs. Giving users a chicken switch for recovery really is non-negotiable.

Do we think or know if today Kernel 5.4 with --enable-session-affinity=true has any complexity issues in one or more knob combinations?

We don't know, the code changes too fast to make strong statements. In the past it even tipped over the balance on newer kernels. Let's enable it by default and wire it up in the CI complexity tests to learn :).


Cosmos ref doc landing page issues

Moving the content of the below 2 issues from another repo to here

https://github.com/MicrosoftDocs/azure-docs-sdk-node/issues/753
https://github.com/MicrosoftDocs/azure-docs-sdk-node/issues/1004

@zfoster, @southpolesteve, Both these issues are for the page Azure Cosmos DB Modules for JavaScript. The source md file to fix is https://github.com/MicrosoftDocs/azure-docs-sdk-node/blob/master/docs-ref-services/latest/cosmos-db.md

@ramya-rao-a I think the page to update for the second issue is here: https://docs.microsoft.com/en-us/javascript/api/overview/azure/cosmos-readme?view=azure-node-latest#read-an-item rather than the one linked. The example is perfectly valid but there is also a viable overload, the docs should include both uses.
PR for the first issue: https://github.com/MicrosoftDocs/azure-docs-sdk-node/pull/1105

https://github.com/MicrosoftDocs/azure-docs-sdk-node/pull/1181 fixes the remaining issue