Debugging an extension should forcably enable it (at least for that session)

Issue Type: Bug
This is mainly user error, but I lost so much time because of it, it would be great if there was a solution.
Scenario:

Install Extension A from a vsix
Disable Extension A from the Extensions panel and close vscode
Open the code for Extension A in vscode
Debug Extension A
:bug: vscode will open an extension host window to debug the extension, but since the extension is disabled it will never load. And since there is no visible indication of this, it looks like debugging is broken

It would be great if there was a warning, or better yet, just re-enable the extension for the debugging session.
VS Code version: Code - Insiders 1.26.0-insider (26e5a55cd8452477bfb7a472ea9475761600adf0, 2018-07-20T05:18:39.569Z)
OS version: Windows_NT x64 10.0.17713

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (8 x 4008)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: disabled_softwarevideo_decode: enabledvideo_encode: enabledvpx_decode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
31.93GB (16.74GB free)

Process Argv
C:\Users\Eric\AppData\Local\Programs\Microsoft VS Code Insiders\Code - Insiders.exe C:\Users\Eric\code\codestream\vscode-codestream\codestream.code-workspace

Screen Reader
no

VM
0%

@eamodio It works well for me on latest insiders.

I installed an extension using vsix
Opened the same extension source in VS Code
Disabled the extension
Ran the extension

And I see the extension is active and can be debugged

This is still 100% reproducible for me in both stable and insiders. Also verified that it doesn't have anything to do with vsix.

Have GitLens installed and enabled
Open vscode to the vscode-gitlens repo
Switch to extensions and disabled GitLens
Reload vscode
Start debugging (F5)
The extension host window that opens will not start GitLens

@eamodio I could not try your extension as I was getting errors while building. I tried with another extension and it works.

Here are the errors I see when I run gitlens extensions

Executing task: npm run build <

<EMAIL_ADDRESS>build /Users/sandy081/work/vscode-extensions/vscode-gitlens
npm run lint && tsc -m commonjs -p ./ && npm run build-ui -- --env.quick

<EMAIL_ADDRESS>lint /Users/sandy081/work/vscode-extensions/vscode-gitlens
tslint --project tslint.json

<EMAIL_ADDRESS>build-ui /Users/sandy081/work/vscode-extensions/vscode-gitlens
webpack --context ./src/ui --config ./src/ui/webpack.config.js "--env.quick"

Hash: fcf496d8aea37a461fdc
Version: webpack 4.5.0
Time: 4624ms
Built at: 8/22/2018 6:53:26 PM
Asset      Size    Chunks             Chunk Names
settings.js  71.2 KiB  settings  [emitted]  settings
welcome.js  70.6 KiB   welcome  [emitted]  welcome
../../settings.html  80.9 KiB            [emitted]
../../welcome.html  27.8 KiB            [emitted]
Entrypoint settings = settings.js
Entrypoint welcome = welcome.js
[./node_modules/css-loader/index.js??ref--5-2!./node_modules/sass-loader/lib/loader.js??ref--5-3!./scss/main.scss] ./node_modules/css-loader??ref--5-2!./node_modules/sass-loader/lib/loader.js??ref--5-3!./scss/main.scss 4 KiB [built] [failed] [1 error]
[./scss/main.scss] 6.9 KiB [built] [failed] [1 error]
[0] multi ./settings/index.ts ./scss/main.scss 40 bytes {settings} [built]
[1] multi ./welcome/index.ts ./scss/main.scss 40 bytes {welcome} [built]
[./settings/app.ts] 646 bytes {settings} [built]
[./settings/index.ts] 70 bytes {settings} [built]
[./shared/app-base.ts] 10.3 KiB {welcome} {settings} [built]
[./shared/colors.ts] 3.33 KiB {welcome} {settings} [built]
[./shared/dom.ts] 439 bytes {welcome} {settings} [built]
[./welcome/app.ts] 453 bytes {welcome} [built]
[./welcome/index.ts] 68 bytes {welcome} [built]
+ 2 hidden modules
ERROR in ./scss/main.scss (./node_modules/css-loader??ref--5-2!./node_modules/sass-loader/lib/loader.js??ref--5-3!./scss/main.scss)
Module build failed: Error: Node Sass does not yet support your current environment: OS X 64-bit with Unsupported runtime (64)
For more information on which environments are supported please see:
https://github.com/sass/node-sass/releases/tag/v4.8.3
at module.exports (/Users/sandy081/work/vscode-extensions/vscode-gitlens/src/ui/node_modules/node-sass/lib/binding.js:13:13)
at Object. (/Users/sandy081/work/vscode-extensions/vscode-gitlens/src/ui/node_modules/node-sass/lib/index.js:14:35)
at Module._compile (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/v8-compile-cache/v8-compile-cache.js:178:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
at Module.load (internal/modules/cjs/loader.js:599:32)
at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
at Function.Module._load (internal/modules/cjs/loader.js:530:3)
at Module.require (internal/modules/cjs/loader.js:637:17)
at require (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/v8-compile-cache/v8-compile-cache.js:159:20)
at Object. (/Users/sandy081/work/vscode-extensions/vscode-gitlens/src/ui/node_modules/sass-loader/lib/loader.js:3:14)
at Module._compile (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/v8-compile-cache/v8-compile-cache.js:178:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
at Module.load (internal/modules/cjs/loader.js:599:32)
at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
at Function.Module._load (internal/modules/cjs/loader.js:530:3)
at Module.require (internal/modules/cjs/loader.js:637:17)
at require (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/v8-compile-cache/v8-compile-cache.js:159:20)
at loadLoader (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/loader-runner/lib/loadLoader.js:13:17)
at iteratePitchingLoaders (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/loader-runner/lib/LoaderRunner.js:169:2)
at iteratePitchingLoaders (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/loader-runner/lib/LoaderRunner.js:165:10)
at /Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/loader-runner/lib/LoaderRunner.js:173:18
at loadLoader (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/loader-runner/lib/loadLoader.js:36:3)
at iteratePitchingLoaders (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/loader-runner/lib/LoaderRunner.js:169:2)
at runLoaders (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/loader-runner/lib/LoaderRunner.js:362:2)
at NormalModule.doBuild (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/webpack/lib/NormalModule.js:225:3)
at NormalModule.build (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/webpack/lib/NormalModule.js:343:15)
at Compilation.buildModule (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/webpack/lib/Compilation.js:361:10)
at factory.create (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/webpack/lib/Compilation.js:587:15)
at factory (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/webpack/lib/NormalModuleFactory.js:366:6)
at hooks.afterResolve.callAsync (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/webpack/lib/NormalModuleFactory.js:143:13)
at AsyncSeriesWaterfallHook.eval [as callAsync] (eval at create (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/tapable/lib/HookCodeFactory.js:24:12), :6:1)
at resolver (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/webpack/lib/NormalModuleFactory.js:126:29)
at process.nextTick (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/webpack/lib/NormalModuleFactory.js:304:9)
at process._tickCallback (internal/process/next_tick.js:61:11)
@ ./scss/main.scss 2:14-136
ERROR in ./scss/main.scss
Module build failed: ModuleBuildError: Module build failed: Error: Node Sass does not yet support your current environment: OS X 64-bit with Unsupported runtime (64)
For more information on which environments are supported please see:
https://github.com/sass/node-sass/releases/tag/v4.8.3
at module.exports (/Users/sandy081/work/vscode-extensions/vscode-gitlens/src/ui/node_modules/node-sass/lib/binding.js:13:13)
at Object. (/Users/sandy081/work/vscode-extensions/vscode-gitlens/src/ui/node_modules/node-sass/lib/index.js:14:35)
at Module._compile (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/v8-compile-cache/v8-compile-cache.js:178:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
at Module.load (internal/modules/cjs/loader.js:599:32)
at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
at Function.Module._load (internal/modules/cjs/loader.js:530:3)
at Module.require (internal/modules/cjs/loader.js:637:17)
at require (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/v8-compile-cache/v8-compile-cache.js:159:20)
at Object. (/Users/sandy081/work/vscode-extensions/vscode-gitlens/src/ui/node_modules/sass-loader/lib/loader.js:3:14)
at Module._compile (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/v8-compile-cache/v8-compile-cache.js:178:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
at Module.load (internal/modules/cjs/loader.js:599:32)
at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
at Function.Module._load (internal/modules/cjs/loader.js:530:3)
at Module.require (internal/modules/cjs/loader.js:637:17)
at require (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/v8-compile-cache/v8-compile-cache.js:159:20)
at loadLoader (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/loader-runner/lib/loadLoader.js:13:17)
at iteratePitchingLoaders (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/loader-runner/lib/LoaderRunner.js:169:2)
at iteratePitchingLoaders (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/loader-runner/lib/LoaderRunner.js:165:10)
at /Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/loader-runner/lib/LoaderRunner.js:173:18
at loadLoader (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/loader-runner/lib/loadLoader.js:36:3)
at iteratePitchingLoaders (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/loader-runner/lib/LoaderRunner.js:169:2)
at runLoaders (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/loader-runner/lib/LoaderRunner.js:362:2)
at NormalModule.doBuild (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/webpack/lib/NormalModule.js:225:3)
at NormalModule.build (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/webpack/lib/NormalModule.js:343:15)
at Compilation.buildModule (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/webpack/lib/Compilation.js:361:10)
at moduleFactory.create (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/webpack/lib/Compilation.js:717:12)
at factory (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/webpack/lib/NormalModuleFactory.js:366:6)
at hooks.afterResolve.callAsync (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/webpack/lib/NormalModuleFactory.js:143:13)
at AsyncSeriesWaterfallHook.eval [as callAsync] (eval at create (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/tapable/lib/HookCodeFactory.js:24:12), :6:1)
at AsyncSeriesWaterfallHook.lazyCompileHook [as _callAsync] (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/tapable/lib/Hook.js:35:21)
at resolver (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/webpack/lib/NormalModuleFactory.js:126:29)
at process.nextTick (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/webpack/lib/NormalModuleFactory.js:304:9)
at process._tickCallback (internal/process/next_tick.js:61:11)
at runLoaders (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/webpack/lib/NormalModule.js:242:20)
at /Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/loader-runner/lib/LoaderRunner.js:364:11
at /Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/loader-runner/lib/LoaderRunner.js:170:18
at loadLoader (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/loader-runner/lib/loadLoader.js:27:11)
at iteratePitchingLoaders (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/loader-runner/lib/LoaderRunner.js:169:2)
at iteratePitchingLoaders (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/loader-runner/lib/LoaderRunner.js:165:10)
at /Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/loader-runner/lib/LoaderRunner.js:173:18
at loadLoader (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/loader-runner/lib/loadLoader.js:36:3)
at iteratePitchingLoaders (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/loader-runner/lib/LoaderRunner.js:169:2)
at runLoaders (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/loader-runner/lib/LoaderRunner.js:362:2)
at NormalModule.doBuild (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/webpack/lib/NormalModule.js:225:3)
at NormalModule.build (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/webpack/lib/NormalModule.js:343:15)
at Compilation.buildModule (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/webpack/lib/Compilation.js:361:10)
at moduleFactory.create (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/webpack/lib/Compilation.js:717:12)
at factory (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/webpack/lib/NormalModuleFactory.js:366:6)
at hooks.afterResolve.callAsync (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/webpack/lib/NormalModuleFactory.js:143:13)
at AsyncSeriesWaterfallHook.eval [as callAsync] (eval at create (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/tapable/lib/HookCodeFactory.js:24:12), :6:1)
at AsyncSeriesWaterfallHook.lazyCompileHook [as _callAsync] (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/tapable/lib/Hook.js:35:21)
at resolver (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/webpack/lib/NormalModuleFactory.js:126:29)
at process.nextTick (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/webpack/lib/NormalModuleFactory.js:304:9)
at process._tickCallback (internal/process/next_tick.js:61:11)
@ ./scss/main.scss
Child extract-text-webpack-plugin node_modules/extract-text-webpack-plugin/dist node_modules/css-loader/index.js??ref--5-2!node_modules/sass-loader/lib/loader.js??ref--5-3!scss/main.scss:
Entrypoint undefined = extract-text-webpack-plugin-output-filename
[./node_modules/css-loader/index.js??ref--5-2!./node_modules/sass-loader/lib/loader.js??ref--5-3!./scss/main.scss] ./node_modules/css-loader??ref--5-2!./node_modules/sass-loader/lib/loader.js??ref--5-3!./scss/main.scss 4.17 KiB {0} [built] [failed] [1error]
ERROR in ./scss/main.scss (./node_modules/css-loader??ref--5-2!./node_modules/sass-loader/lib/loader.js??ref--5-3!./scss/main.scss)
Module build failed: Error: Node Sass does not yet support your current environment: OS X 64-bit with Unsupported runtime (64)
For more information on which environments are supported please see:
https://github.com/sass/node-sass/releases/tag/v4.8.3
    at module.exports (/Users/sandy081/work/vscode-extensions/vscode-gitlens/src/ui/node_modules/node-sass/lib/binding.js:13:13)
    at Object.<anonymous> (/Users/sandy081/work/vscode-extensions/vscode-gitlens/src/ui/node_modules/node-sass/lib/index.js:14:35)
    at Module._compile (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/v8-compile-cache/v8-compile-cache.js:178:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
    at Module.load (internal/modules/cjs/loader.js:599:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
    at Function.Module._load (internal/modules/cjs/loader.js:530:3)
    at Module.require (internal/modules/cjs/loader.js:637:17)
    at require (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/v8-compile-cache/v8-compile-cache.js:159:20)
    at Object.<anonymous> (/Users/sandy081/work/vscode-extensions/vscode-gitlens/src/ui/node_modules/sass-loader/lib/loader.js:3:14)
    at Module._compile (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/v8-compile-cache/v8-compile-cache.js:178:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
    at Module.load (internal/modules/cjs/loader.js:599:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
    at Function.Module._load (internal/modules/cjs/loader.js:530:3)
    at Module.require (internal/modules/cjs/loader.js:637:17)
    at require (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/v8-compile-cache/v8-compile-cache.js:159:20)
    at loadLoader (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/loader-runner/lib/loadLoader.js:13:17)
    at iteratePitchingLoaders (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/loader-runner/lib/LoaderRunner.js:169:2)
    at iteratePitchingLoaders (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/loader-runner/lib/LoaderRunner.js:165:10)
    at /Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/loader-runner/lib/LoaderRunner.js:173:18
    at loadLoader (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/loader-runner/lib/loadLoader.js:36:3)
    at iteratePitchingLoaders (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/loader-runner/lib/LoaderRunner.js:169:2)
    at runLoaders (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/loader-runner/lib/LoaderRunner.js:362:2)
    at NormalModule.doBuild (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/webpack/lib/NormalModule.js:225:3)
    at NormalModule.build (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/webpack/lib/NormalModule.js:343:15)
    at Compilation.buildModule (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/webpack/lib/Compilation.js:361:10)
    at moduleFactory.create (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/webpack/lib/Compilation.js:717:12)
    at factory (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/webpack/lib/NormalModuleFactory.js:366:6)
    at hooks.afterResolve.callAsync (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/webpack/lib/NormalModuleFactory.js:143:13)
    at AsyncSeriesWaterfallHook.eval [as callAsync] (eval at create (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/tapable/lib/HookCodeFactory.js:24:12), <anonymous>:6:1)
    at AsyncSeriesWaterfallHook.lazyCompileHook [as _callAsync] (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/tapable/lib/Hook.js:35:21)
    at resolver (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/webpack/lib/NormalModuleFactory.js:126:29)
    at process.nextTick (/Users/sandy081/work/vscode-extensions/vscode-gitlens/node_modules/webpack/lib/NormalModuleFactory.js:304:9)
    at process._tickCallback (internal/process/next_tick.js:61:11)

Child html-webpack-plugin for "../../settings.html":
1 asset
Entrypoint undefined = ../../settings.html
[../../node_modules/webpack/buildin/global.js] (webpack)/buildin/global.js 509 bytes {0} [built]
[../../node_modules/webpack/buildin/module.js] (webpack)/buildin/module.js 519 bytes {0} [built]
[./node_modules/html-webpack-plugin/lib/loader.js!./settings/index.html] 82 KiB {0} [built]
+ 1 hidden module
Child html-webpack-plugin for "../../welcome.html":
1 asset
Entrypoint undefined = ../../welcome.html
[../../node_modules/webpack/buildin/global.js] (webpack)/buildin/global.js 509 bytes {0} [built]
[../../node_modules/webpack/buildin/module.js] (webpack)/buildin/module.js 519 bytes {0} [built]
[./node_modules/html-webpack-plugin/lib/loader.js!./welcome/index.html] 28.3 KiB {0} [built]
+ 1 hidden module
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR<EMAIL_ADDRESS>build-ui: webpack --context ./src/ui --config ./src/ui/webpack.config.js "--env.quick"
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build-ui script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!      /Users/sandy081/.npm/_logs/2018-08-22T16_53_26_681Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR<EMAIL_ADDRESS>build: npm run lint && tsc -m commonjs -p ./ && npm run build-ui -- --env.quick
npm ERR! Exit status 2
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/sandy081/.npm/_logs/2018-08-22T16_53_26_717Z-debug.log
The terminal process terminated with exit code: 2
Terminal will be reused by tasks, press any key to close it.

@sandy081 from those errors it looks like node-sass isn't compatible with your OS version 😢
Although I've just tried again from the latest insiders and it seems to be working now.


Beyond virtual memory limits On Yarn(GPU)

when i run train_mnist.py on yarn using gpu, it will need much virtual memory (e.g. 160GB). Through process-tree for container i see that run python script need  so much memory. So i think python script may want more GPU resources and yarn try to stop this dangerous behavior.
To solve this problem , I must set yarn.nodemanager.vmem-check-enabled to false which i think it may be not a good way. Any Advices?

This issue is closed due to lack of activity in the last 90 days. Feel free to reopen if this is still an active issue. Thanks!


Feature request: check which licenses are incompatible

Could you expand please? Do you mean if a package has two different licenses? Or check each license against another? This looks like it might become a combination impossibility.

I meant comparing the current project's license against all of its dependencies to see if there are any incompatibilities. Most open-source licenses should be compatible with each other so I don't know how useful this will be but I think ianal should have a feature like this.

A similar but not the same would be in the options now as --type filter:
legally --type mit

And for the original request, I am not a lawyer as displayed in the Readme and I don't have the resources/capacity to check for compatibility for the licenses, so I close this


Fix and Re-enable flaky test test/es6/proto_disable.js

Test output includes the following line but is otherwise correct:
WARNING: DynamicProfileStorage: Dynamic Profile Data corrupted: 'e:\a\_work\2\s\test\unittestframework\unittestframework.js'
Disabled in https://github.com/Microsoft/ChakraCore/pull/2668

Fixed in #2763
Re-enabled in #2776

Apparently not fixed. Disabling the test again in #3087 and reactivating this issue.

I suspect that this is also the cause for the issue in proto_initializer, so I've disabled that test as well.


beta 2.0.15 - @theme/hooks/ was refactored.

When upgrading to beta 2.0.15 the following issue is arising:
Module not found: Error: Can't resolve '@theme/hooks/useThemeContext' in '..../node_modules/redocusaurus/node_modules/docusaurus-theme-redoc/dist-jsx/theme/Redoc'
[ERROR] Client bundle compiled with errors therefore further build is impossible.

Please see the breaking change here:
https://github.com/facebook/docusaurus/blob/main/CHANGELOG.md#boom-breaking-change
as well as here:

refactor: move @theme/hooks to @docusaurus/theme-common](https://github.com/facebook/docusaurus/pull/6289#)
https://github.com/facebook/docusaurus/pull/6289

import { useColorMode } from '@docusaurus/theme-common';
import { Redoc as RedocComponent, RedocStandalone, AppStore } from 'redoc';
import { RedocProps as Props, GlobalData } from '../../types/common';
import './styles.css';

/*!
 * Redocusaurus
 * https://rohit-gohri.github.io/redocusaurus/
 * (c) 2021 Rohit Gohri
 * Released under the MIT License
 */
function Redoc(props: Props): JSX.Element {
  const { isDarkTheme } = useColorMode();

It was published as 0.6.0, the pipeline failed but the it was released.
You can see published version<EMAIL_ADDRESS>

Upgrading to v0.6.0 should fix it, please reopen the issue if it doesn't.

Thanks solved.


Please modify question 79 of 70 - Flight Performance and Planning

This question is can easily be misinterpreted, due to the lack of punctuation's:
79 How much taxi fuel must be consumed before take-off to reduce the aircraft mass to the maximum take-off mass? Maximum ramp mass (MRM): 1150 kg Actual ramp mass: 1148 kg Maximum take-off mass (MTOM): 1145 kg
[Suggested modification: add comma's]
79 How much taxi fuel must be consumed before take-off to reduce the aircraft mass to the maximum take-off mass?
Maximum ramp mass (MRM): 1150 kg, Actual ramp mass: 1148 kg, Maximum take-off mass (MTOM): 1145 kg
-or-
[Suggested modification: align vertically, this is how it's written in de PDF]
79 How much taxi fuel must be consumed before take-off to reduce the aircraft mass to the maximum take-off mass?
Maximum ramp mass (MRM): 1150 kg
Actual ramp mass: 1148 kg
Maximum take-off mass (MTOM): 1145 kg
Source: ECQB-PPL-60-OPR-PPLA-EN.pdf
https://aircademy.com/downloads/ECQB-PPL-PDF/ECQB-PPL-20.2-INT-EN.zip
Thank you and keep up the good work!

Hi @ArthMaster, would you mind submitting a pull request for these changes?
You can read how to here: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request


[Containerapp] az containerapp create/up: --registry-server use managed identity for image pull by default

This checklist is used to make sure that common guidelines for a pull request are followed.
Related command

General Guidelines

[ ] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
[ ] Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
[ ] My extension version conforms to the Extension version schema

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

Containerapp

About src/containerapp/azext_containerapp/_utils.py, I will revert it from this PR after PR Fix create containerapp/containerappjob with msi issue merge:

The CI failed with following error, which is not relate to our containerapp extension.
=========================== short test summary info ============================
FAILED src/standbypool/azext_standbypool/tests/latest/test_standbypool.py::StandbypoolScenario::test_standby_container_group_pool_scenarios
FAILED src/standbypool/azext_standbypool/tests/latest/test_standbypool.py::StandbypoolScenario::test_standby_virtual_machine_pool_scenarios

It looks like some unrelated changes (about aks-preview) were merged into your branch?

It looks like some unrelated changes (about aks-preview) were merged into your branch?

Fixed.


adding forceresolution for netty dep in ktor server

Codecov Report

Merging #228 (201949f) into main (85598e1) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #228   +/-   ##
=======================================
  Coverage   84.34%   84.34%
=======================================
  Files          38       38
  Lines        1124     1124
  Branches      114      114
=======================================
  Hits          948      948
  Misses        124      124
  Partials       52       52

Components
Coverage Δ

protocol
85.85% <ø> (ø)

httpclient
78.34% <ø> (ø)


Build Init plugin: use configuration avoidance for task registration

Signed-off-by: Erhard Pointl<EMAIL_ADDRESS>
Fixes #8170
Context
A first part to generate builds that use configuration avoidance API.
Contributor Checklist

[x] Review Contribution Guidelines
[x] Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[x] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team
[x] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective
[x] Provide unit tests (under <subproject>/src/test) to verify logic
[ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes
[x] Ensure that tests pass locally: ./gradlew <changed-subproject>:check

Gradle Core Team Checklist

[x] Verify design and implementation
[x] Verify test coverage and CI build status
[ ] Verify documentation
[x] Recognize contributor in release notes

Thank you @epeee!

This PR only changes the generated Groovy scripts, Kotlin scripts should be changed too!

@eskatos indeed, I will provide another pr which will cover the Kotlin part soon.


Refuges - Find Your Refuge Tool

Copy over the find your refuge tool.
https://docs.google.com/a/doi.gov/document/d/1DvcCjlKT-jrzigRFn_fwNzyINS9f_46UdbP4Sc3HUpc/edit?usp=sharing

@jenmstrick I tried to embed the search tool into the page, but since it's coldfusion and redirects the user to a a results page it didn't work.  I'm just linking to the find your hunt page instead.
Closed via fba4d23665ed7e70069792b5ff9a47d789d34e5d


Enable your tenant verifiable credentials small improvements

small updates to doc
enable-your-tenant-verifiable-credentials.md
https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/active-directory/verifiable-credentials/enable-your-tenant-verifiable-credentials.md

@damienbod : Thanks for your contribution! The author(s) have been notified to review your proposed change.

thanks!

@barclayn please review and close

#sign-off


rollup packaging speed optimization

https://github.com/Jonghakseo/chrome-extension-boilerplate-react-vite/pull/379

#379


avoid disconnection error of idle connections

Codecov Report

Merging #668 into master will decrease coverage by 7.64%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #668      +/-   ##
==========================================
- Coverage   84.98%   77.33%   -7.65%
==========================================
  Files          27       27
  Lines        3296     3296
  Branches      519      482      -37
==========================================
- Hits         2801     2549     -252
- Misses        348      593     +245
- Partials      147      154       +7

Impacted Files
Coverage Δ

pykafka/rdkafka/producer.py
27.77% <ø> (-66.67%)
:arrow_down:

pykafka/rdkafka/simple_consumer.py
19.8% <0%> (-73.27%)
:arrow_down:

pykafka/connection.py
67.74% <0%> (-16.13%)
:arrow_down:

pykafka/utils/compat.py
70.27% <0%> (-14.87%)
:arrow_down:

pykafka/broker.py
81.57% <0%> (-10.53%)
:arrow_down:

pykafka/simpleconsumer.py
76.48% <0%> (-8.92%)
:arrow_down:

pykafka/handlers.py
86.92% <0%> (-7.7%)
:arrow_down:

pykafka/balancedconsumer.py
84.56% <0%> (-6.8%)
:arrow_down:

pykafka/rdkafka/helpers.py
13.33% <0%> (-6.67%)
:arrow_down:

... and 9 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 95c2e6e...3e62f12. Read the comment docs.

Thanks @maparent, this is a great find! This fixes #599.


bind-key -n equivalent

Is it possible to omit the prefix key of tmux-easy-motion? Similarly to omitting Tmux its prefix using the bind-key -n command.
My use case: when I am in copy-mode, I have unassigned keys left that I want to bind to tmux-easy-motion command directly. For example: when I press "k" I want to run the "@easy-motion-binding-w" directly (without having to press the prefix "Space").
My attempts to achieving this were:

Setting the tmux-easy-motion prefix to ""set -g @easy-motion-copy-mode-prefix ""

which did not work.
Binding "k" to a sequence of keys:bind-key -T copy-mode-vi k send-keys " " w

which did send a "Space" and a "w" but it triggered the default "w" and not the "@easy-motion-binding-w".

Thanks for the good plugin!

I solved this as follows:
server_pid="$(tmuxpid)"
bind -T copy-mode-vi k run-shell -b "$HOME/.tmux/plugins/tmux-easy-motion/scripts/easy_motion.sh '${server_pid}' '#{session_id}' '#{window_id}' '#{pane_id}' w"

this binds the key k directly to the easy-motion-w key. Above, tmuxpid is an executable:
#!/usr/bin/env bash
[[ "${TMUX}" =~ .*,(.*),.* ]] && echo "${BASH_REMATCH[1]}"


braced sections: forbid to have space before/after comma symbol ?

as title, if so should have a tip, hah
'*.{styl,css,js,jedi,php,html'  is always ok, but '*.{styl, css, js, jedi, php, html'  does not work well.

Spaces are a valid char to have in a filename, so no, that would mean a different thing.
If you're suggesting that we auto-trim the braced sections, that would be a breaking change and a departure from Bash behavior, so that's not going to happen.


Box view: rework pagination

The current pagination comes with some issues, one of them being it is impossible to move a Pokémon from one page to another.
Ideally we would implement an autoscroll that would allow the above to be performed.

We will also need to change the API for box pagination; simply having a page number isn't scalable since the server has to filter private Pokémon from the listing. For example, if a box has 3000 Pokémon, and someone other than the owner tries to view page 75/100, the server has to iterate through all of the first 74 pages in order to check which Pokémon are private; otherwise it risks disclosing the existence of a private Pokémon based on how it returns a given page.
It would be better to paginate with something like an after parameter, e.g.
GET /box/theBoxId?after=somePokemonId

...which would return all Pokémon in the box immediately following the given Pokémon.

Fixed with #417.


Feature/installer staging

Major overhaul, and this resolves #35 fixes #32 fixes #17. Deployed 3-master/3-worker clusters using this latest branch (5) consecutive, successful times.  Tested with/without ocp_storage_nfs_enable. Note that I've add a few other ocp_ vars that are not yet baked, but will set the stage for getting OCS and OpenShift Virtualization (CNV/kubevirt) deployed, too.  @c0dyhi11 would appreciate any feedback/trials before this merges.
Also a few extra notes:

To bypass some of the DNS caching/propagation issues encountered, I've added entries to /etc/hosts via ignition configs for api. and api-int. entries.
I ran into several issues when using facilities DFW2 and IAD2: failed memory module interrupting standard boot, system clock skew throwing-off validation of the installer-created CA certs (validity period was too far in the future due to slow system clock), and general provisioning timeout errors. After switching to SJC1, things went much, much smoother.

Going to close this PR since I have more changes to merge.


I freeze now since i updated.

I updated for the admin commands, and now i freeze afte rlike 5 minutes of game time.

If you downloaded the pull request, explains why.

it doesn't affect server performance and even more, currently there is no commands for authenticated players. It just provides way to check user permissions for new player commands


Update Highstock JS to  v6.0.3

This doesn't work

i'm using it

i'm using it

do you have problem in displaying the candle stick? the candle stick screen is blank


PlanarSLAM Implementation

#59
This one is particularly hard to implement generically for me that:

The factor now involves two types!
It is not trivial to combine two fixed-size vectors into one that is of a higher dimension

For 2, Rust has generic value parameters, but it appears to have not been implemented, as stated here: https://github.com/apple/swift/blob/master/docs/GenericsManifesto.md#generic-value-parameters
Anyway here is the Pose2 only version, so we can discuss :)

Looks like the GitHub Actions on macOS is down...


Type: Map: Add host fn to get a slice of a map given a start and end key

To support converting an iterator into a Map, we need to be able to get a slice of a map in a similar way that we can get a slice of a Vec. The host fn should accept two keys, a low and a high, and return a map that has the elements between those two keys.
For Vecs range selection is start inclusive and end exclusive, but I assume for a Map it will need to be start inclusive and end inclusive.

cc @jayz22

This was done.

Which PR was this done with? I don't see new map host functions. I also don't see any "slice" related functionality in the SDK.
Or is this issue about supporting iterators in maps in SDK?

This wasn't, sorry, I think I thought this was for Vec, but I see it was Map.

This got put into the July deliverables, but the SDK won't actually need this for July because I don't plan to circle back to use this fn until August. So @jayz22 if you don't need this in the July deliverable as a priority, it can be shifted.

I don't think we have a clear use case for slicing maps. I'm going to close. This functionality is purely additive, and can be added at any time that anyone identifies are use case.
Note that the original use case to support iteration, is no longer relevant.


rewrite download function

due to internal network name of minio the download and sharing using  presigned URL is not working
need to think of alternative ways

I believe we resolve the minio network issue so no need to worry about that

@ywkim312 could you write down a few sentences on what did we do with minio?

thanks for the explanation. Closing this


Implement VCS Controller

The VCS Controller is responsible to define the common interface to be provided by the Version Control Systems (in the default implementation Git).
Responsabilities:

Setup of local VC repository
Commit changes locally
Push changes to central server

Interface created


Build fails with: invalid source release: 17

What is the proper way to resolve this error:
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':file_saver:compileDebugJavaWithJavac'.
> error: invalid source release: 17

I've just been going into
~/.pub-cache/hosted/pub.dev/file_saver-0.2.9/android/build.gradle
and changing:
    compileOptions {
        targetCompatibility JavaVersion.VERSION_17
        sourceCompatibility JavaVersion.VERSION_17
    }

to
    compileOptions {
        targetCompatibility JavaVersion.VERSION_1_8
        sourceCompatibility JavaVersion.VERSION_1_8
    }

but obviously thats not a real fix.
(Also curious why do my projects have this issue and no one else seems to?)

same question，I think the requirement of VERSION_17 is very unreasonable

I get this error even when building on machine with Java 17 (openjdk 17.0.9) installed.
Changing the file ~/.pub-cache/hosted/pub.dev/file_saver-0.2.9/android/build.gradle according to the first message fixes the issue.

Hi there, was there any other resolution to this?
For me the change above (targetCompatibility JavaVersion.VERSION_1_8
) worked, but since is inside the pub cache, I'm assuming any pub operation might overwrite it, correct?

Hi there, was there any other resolution to this? For me the change above (targetCompatibility JavaVersion.VERSION_1_8 ) worked, but since is inside the pub cache, I'm assuming any pub operation might overwrite it, correct?
I also had to update my compileSdkVersion from flutter.compileSdkVersion to 34 to eliminate an warning/error on build (which still opens the app) and kotlin to latest (not really sure if connected but all happened at the same time)

I used the flutter run command to get rid of the error brought by version 17

I got it fixed by updating Android Studio.
Before doing anything, launch Android Studio and Click Help > About and take a note of the Runtime version. For me, it was a JDK 11 version.
After updating to 2023.3.1 the same About page showed JDK 17 and the Android builds ran fine.

Why are the PRs not merged?
Is there an alternative package?

Same error when running flutter build appbundle
`* What went wrong:
Execution failed for task ':file_saver:compileReleaseJavaWithJavac'.

error: invalid source release: 17
`

Tried all the solutions above.

The same error for indirect dependency for this package https://pub.dev/packages/to_csv

POTENTIAL FIX:

The problem lies within the Android inner files, not the package itself.

Solution steps:

Visit the official website and download the latest version of Android Studio. link
Once installed, execute the command flutter build appbundle.
After following these steps, the issue should be resolved, and everything should function properly.

Started working with this

It works. @SzymonDziak

Do we have a fix yet guys? Thank you!

Is there any fix yet for CI/CD?

You can use my fork
pubspec.yaml
  file_saver:
    git:
      url: https://github.com/adrianvintu/file_saver.git
      ref: VERSION_1_8

The correct way is remove these two lines;
android {
namespace "com.incrediblezayed.file_saver"
compileSdk 34
sourceSets {
    main.java.srcDirs += 'src/main/kotlin'
}
defaultConfig {
    minSdkVersion 19
}
// compileOptions {
//     targetCompatibility JavaVersion.VERSION_18
//     sourceCompatibility JavaVersion.VERSION_18
// }

}

The correct way is remove these two lines;
android { namespace "com.incrediblezayed.file_saver" compileSdk 34
sourceSets {
    main.java.srcDirs += 'src/main/kotlin'
}
defaultConfig {
    minSdkVersion 19
}
// compileOptions {
//     targetCompatibility JavaVersion.VERSION_18
//     sourceCompatibility JavaVersion.VERSION_18
// }

}

The correct way is remove these two lines;
android { namespace "com.incrediblezayed.file_saver" compileSdk 34
sourceSets {
    main.java.srcDirs += 'src/main/kotlin'
}
defaultConfig {
    minSdkVersion 19
}
// compileOptions {
//     targetCompatibility JavaVersion.VERSION_18
//     sourceCompatibility JavaVersion.VERSION_18
// }

}

It's work for me

same here

For me it helped to fork the repository and adjust content in following files (just place there same versions for java, kotlin and etc.):
gradle-wrapper.properties
build.gradle
gradle.properties

I'm so sorry guys, if it is very urgent for everyone you guys can go ahead & use the package form the PR created by a contributor in issue #87 this will fix the issue, & further discussion of this issue will take place in issue #87 so follow up in that.

It doesn't work with JavaVersion.VERSION_1_8 now...
Can we just stick with the Flutter recommended. It's annoying.

You may use this until we have an update from the developer
  file_saver:
    git:
      url: https://github.com/adrianvintu/file_saver.git
      ref: 0aae1be4df8d1c30f267e080d9bf6be9bd9a4147

Is there any fix yet for CI/CD?

this might fix CI/CD https://stackoverflow.com/a/78086249/8623062

POTENTIAL FIX:

The problem lies within the Android inner files, not the package itself.

Solution steps:

Visit the official website and download the latest version of Android Studio. link
Once installed, execute the command flutter build appbundle.
After following these steps, the issue should be resolved, and everything should function properly.

The potential fix does not work for CI/Github aAtions

yes, man I am facing same issue means i am using github CI/CD to autogenerate APk in github actions but some @plus_plugins like connectiivty_plus, share_plus are not working and you wll always get "invalid source release: 17" or similar ones .

You can also use something like below, to force the VERSION_17 build
buildscript {
    ext.kotlin_version = '1.9.20'
    repositories {
        google()
        mavenCentral()
    }

    dependencies {
        classpath 'com.android.tools.build:gradle:8.1.2'
        classpath 'com.google.gms:google-services:4.3.15'
        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
    }
}

allprojects {
    repositories {
        google()
        mavenCentral()
    }

    // When upgrading to AGP8, some projects do not have a namespace set, so we add one
    // https://stackoverflow.com/questions/76108428/how-do-i-fix-namespace-not-specified-error-in-android-studio
    subprojects {
        afterEvaluate { project ->
            if (project.hasProperty('android')) {
                project.android {
                    if (namespace == null) {
                        namespace project.group
                    }
                }
            }
        }

        subprojects {
            afterEvaluate {
                if (project.plugins.hasPlugin("com.android.application")
                        || project.plugins.hasPlugin("com.android.library")) {
                    // https://github.com/matanshukry/flutter_google_places_sdk/issues/71
                    if (project.name == "flutter_google_places_sdk_android") {
                        project.android.compileOptions {
                            sourceCompatibility = JavaVersion.VERSION_17
                            targetCompatibility = JavaVersion.VERSION_17
                        }
                    }
                }
            }
            project.buildDir = "${rootProject.buildDir}/${project.name}"
            project.evaluationDependsOn(':app')
        }

    }
}

rootProject.buildDir = '../build'
subprojects {
    // https://github.com/matanshukry/flutter_google_places_sdk/issues/71
    afterEvaluate {
        if (project.plugins.hasPlugin("com.android.application")
                || project.plugins.hasPlugin("com.android.library")) {
            if (project.name == "flutter_google_places_sdk_android") {
                project.android.compileOptions {
                    sourceCompatibility = JavaVersion.VERSION_17
                    targetCompatibility = JavaVersion.VERSION_17
                }
            }
        }
    }
}

subprojects {
    project.buildDir = "${rootProject.buildDir}/${project.name}"
    project.evaluationDependsOn(':app')
}

tasks.register("clean", Delete) {
    delete rootProject.buildDir
}

any update

Is there any fix yet for CI/CD?

this might fix CI/CD https://stackoverflow.com/a/78086249/8623062
for gh actions
      - name: Setup Java
        uses: actions/setup-java@v4
        with:
          distribution: 'zulu'
          java-version: '17'
          cache: 'gradle'
          check-latest: true

Works to me

I comment
those options
compileOptions {
targetCompatibility JavaVersion.VERSION_17
sourceCompatibility JavaVersion.VERSION_17
 but i face a other error when i run .\gradlew clean build

 `

WARNING:The specified Android SDK Build Tools version (28.0.3) is ignored, as it is below the minimum supported version (30.0.3) for Android Gradle Plugin 7.3.0.
Android SDK Build Tools 30.0.3 will be used.
To suppress this warning, remove "buildToolsVersion '28.0.3'" from your build.gradle file, as each version of the Android Gradle Plugin now has a default version of the build tools.

Task :connectivity_plus:processDebugManifest
package="dev.fluttercommunity.plus.connectivity" found in source AndroidManifest.xml: C:\Users\HP\AppData\Local\Pub\Cache\hosted\pub.dev\connectivity_plus-6.0.3\android\src\main\AndroidManifest.xml.
Setting the namespace via a source AndroidManifest.xml's package attribute is deprecated.
Please instead set the namespace (or testNamespace) in the module's build.gradle file, as described here: https://developer.android.com/studio/build/configure-app-module#set-namespace
This migration can be done automatically using the AGP Upgrade Assistant, please refer to https://developer.android.com/studio/build/agp-upgrade-assistant for more information.

Task :device_info_plus:processDebugManifest
package="dev.fluttercommunity.plus.device_info" found in source AndroidManifest.xml: C:\Users\HP\AppData\Local\Pub\Cache\hosted\pub.dev\device_info_plus-9.1.2\android\src\main\AndroidManifest.xml.
Setting the namespace via a source AndroidManifest.xml's package attribute is deprecated.
Please instead set the namespace (or testNamespace) in the module's build.gradle file, as described here: https://developer.android.com/studio/build/configure-app-module#set-namespace
This migration can be done automatically using the AGP Upgrade Assistant, please refer to https://developer.android.com/studio/build/agp-upgrade-assistant for more information.

Task :flutter_secure_storage:processDebugManifest
package="com.it_nomads.fluttersecurestorage" found in source AndroidManifest.xml: C:\Users\HP\AppData\Local\Pub\Cache\hosted\pub.dev\flutter_secure_storage-4.2.1\android\src\main\AndroidManifest.xml.
Setting the namespace via a source AndroidManifest.xml's package attribute is deprecated.
Please instead set the namespace (or testNamespace) in the module's build.gradle file, as described here: https://developer.android.com/studio/build/configure-app-module#set-namespace
This migration can be done automatically using the AGP Upgrade Assistant, please refer to https://developer.android.com/studio/build/agp-upgrade-assistant for more information.

Task :image_gallery_saver:processDebugManifest
package="com.example.imagegallerysaver" found in source AndroidManifest.xml: C:\Users\HP\AppData\Local\Pub\Cache\hosted\pub.dev\image_gallery_saver-2.0.3\android\src\main\AndroidManifest.xml.
Setting the namespace via a source AndroidManifest.xml's package attribute is deprecated.
Please instead set the namespace (or testNamespace) in the module's build.gradle file, as described here: https://developer.android.com/studio/build/configure-app-module#set-namespace
This migration can be done automatically using the AGP Upgrade Assistant, please refer to https://developer.android.com/studio/build/agp-upgrade-assistant for more information.

Task :permission_handler_android:processDebugManifest
package="com.baseflow.permissionhandler" found in source AndroidManifest.xml: C:\Users\HP\AppData\Local\Pub\Cache\hosted\pub.dev\permission_handler_android-12.0.5\android\src\main\AndroidManifest.xml.
Setting the namespace via a source AndroidManifest.xml's package attribute is deprecated.
Please instead set the namespace (or testNamespace) in the module's build.gradle file, as described here: https://developer.android.com/studio/build/configure-app-module#set-namespace
This migration can be done automatically using the AGP Upgrade Assistant, please refer to https://developer.android.com/studio/build/agp-upgrade-assistant for more information.

Task :url_launcher_android:processDebugManifest
package="io.flutter.plugins.urllauncher" found in source AndroidManifest.xml: C:\Users\HP\AppData\Local\Pub\Cache\hosted\pub.dev\url_launcher_android-6.3.1\android\src\main\AndroidManifest.xml.
Setting the namespace via a source AndroidManifest.xml's package attribute is deprecated.
Please instead set the namespace (or testNamespace) in the module's build.gradle file, as described here: https://developer.android.com/studio/build/configure-app-module#set-namespace
This migration can be done automatically using the AGP Upgrade Assistant, please refer to https://developer.android.com/studio/build/agp-upgrade-assistant for more information.

Task :video_player_android:processDebugManifest
package="io.flutter.plugins.videoplayer" found in source AndroidManifest.xml: C:\Users\HP\AppData\Local\Pub\Cache\hosted\pub.dev\video_player_android-2.4.13\android\src\main\AndroidManifest.xml.
Setting the namespace via a source AndroidManifest.xml's package attribute is deprecated.
Please instead set the namespace (or testNamespace) in the module's build.gradle file, as described here: https://developer.android.com/studio/build/configure-app-module#set-namespace
This migration can be done automatically using the AGP Upgrade Assistant, please refer to https://developer.android.com/studio/build/agp-upgrade-assistant for more information.

Task :flutter_secure_storage:compileDebugJavaWithJavac
Note: C:\Users\HP\AppData\Local\Pub\Cache\hosted\pub.dev\flutter_secure_storage-4.2.1\android\src\main\java\com\it_nomads\fluttersecurestorage\FlutterSecureStoragePlugin.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.

Task :device_info_plus:compileDebugKotlin
w: C:\Users\HP\AppData\Local\Pub\Cache\hosted\pub.dev\device_info_plus-9.1.2\android\src\main\kotlin\dev\fluttercommunity\plus\device_info\MethodCallHandlerImpl.kt: (67, 50): 'getter for defaultDisplay: Display!' is deprecated. Deprecated in Java
w: C:\Users\HP\AppData\Local\Pub\Cache\hosted\pub.dev\device_info_plus-9.1.2\android\src\main\kotlin\dev\fluttercommunity\plus\device_info\MethodCallHandlerImpl.kt: (70, 25): 'getRealMetrics(DisplayMetrics!): Unit' is deprecated. Deprecated in Java
w: C:\Users\HP\AppData\Local\Pub\Cache\hosted\pub.dev\device_info_plus-9.1.2\android\src\main\kotlin\dev\fluttercommunity\plus\device_info\MethodCallHandlerImpl.kt: (72, 25): 'getMetrics(DisplayMetrics!): Unit' is deprecated. Deprecated in Java
w: C:\Users\HP\AppData\Local\Pub\Cache\hosted\pub.dev\device_info_plus-9.1.2\android\src\main\kotlin\dev\fluttercommunity\plus\device_info\MethodCallHandlerImpl.kt: (89, 47): 'SERIAL: String!' is deprecated. Deprecated in Java

Task :image_gallery_saver:compileDebugKotlin
w: C:\Users\HP\AppData\Local\Pub\Cache\hosted\pub.dev\image_gallery_saver-2.0.3\android\src\main\kotlin\com\example\imagegallerysaver\ImageGallerySaverPlugin.kt: (21, 48): 'Registrar' is deprecated. Deprecated in Java
w: C:\Users\HP\AppData\Local\Pub\Cache\hosted\pub.dev\image_gallery_saver-2.0.3\android\src\main\kotlin\com\example\imagegallerysaver\ImageGallerySaverPlugin.kt: (104, 29): 'getExternalStoragePublicDirectory(String!): File!' is deprecated. Deprecated in Java
w: C:\Users\HP\AppData\Local\Pub\Cache\hosted\pub.dev\image_gallery_saver-2.0.3\android\src\main\kotlin\com\example\imagegallerysaver\ImageGallerySaverPlugin.kt: (142, 49): 'ACTION_MEDIA_SCANNER_SCAN_FILE: String' is deprecated. Deprecated in Java
w: C:\Users\HP\AppData\Local\Pub\Cache\hosted\pub.dev\image_gallery_saver-2.0.3\android\src\main\kotlin\com\example\imagegallerysaver\ImageGallerySaverPlugin.kt: (213, 33): Variable 'count' initializer is redundant

Task :app:compileDebugJavaWithJavac FAILED
C:\Users\HP\Desktop\Projects\Work\p1_chatapp\flutter\creacom\android\app\src\main\java\io\flutter\app\FlutterMultiDexApplication.java:13: error: package androidx.multidex does not exist
import androidx.multidex.MultiDex;
^
C:\Users\HP\Desktop\Projects\Work\p1_chatapp\flutter\creacom\android\app\src\main\java\io\flutter\app\FlutterMultiDexApplication.java:23: error: cannot find symbol
MultiDex.install(this);
^
symbol:   variable MultiDex
location: class FlutterMultiDexApplication
2 errors

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:compileDebugJavaWithJavac'.

Compilation failed; see the compiler error output for details.

Try:

Run with --info option to get more log output.
Run with --scan to get full insights.

Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
For more on this, please refer to https://docs.gradle.org/8.7/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.
BUILD FAILED in 2m 3s
160 actionable tasks: 146 executed, 14 up-to-date
`

For the people this issue still persists, please create a new issue & do add +1 with your flutter doctor -v output, I will try to reproduce & fix, apologies for the inactivity

compileOptions {
targetCompatibility JavaVersion.VERSION_1_8
sourceCompatibility JavaVersion.VERSION_1_8
}

This works.

flutter config --jdk-dir "C:\Program Files\Java\jdk-17"
Setting "jdk-dir" value to "C:\Program Files\Java\jdk-17"

This worked for me.

I am on flutter 3.19.6 and on java version 17 i am still getting error

Please set the path of your jdk 17 in gradle.properties file as follow
org.gradle.java.home=C:\Program Files\Java\jdk-17
May be different for your system. May check please
On Fri, Aug 9, 2024 at 1:54 PM Debjeet Debnath @.***>
wrote:

I am on flutter 3.19.6 and on java version 17 i am still getting error
image.png (view on web)
https://github.com/user-attachments/assets/1265f06e-6de3-4771-9cf8-5d383c2339af
—
Reply to this email directly, view it on GitHub
https://github.com/incrediblezayed/file_saver/issues/86#issuecomment-2277423868,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AK2VEETTOVIXYQQQHLOXXW3ZQR4CRAVCNFSM6AAAAAA6MN6TMGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZXGQZDGOBWHA
.
You are receiving this because you commented.Message ID:
@.***>

I solved problem with downgrading java in app/build.gradle
android {
    namespace = "com.example.mindwrite"
    compileSdk = 34
    ndkVersion = flutter.ndkVersion

    // added this
    compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
    }
   // and this
    kotlinOptions {
        jvmTarget = '1.8'
    }
    lintOptions {
        disable 'InvalidPackage'
    }

    defaultConfig {
        applicationId = "com.example.mindwrite"
        minSdk 21
        targetSdk 34
        versionCode = flutterVersionCode.toInteger()
        versionName = flutterVersionName
    }

    buildTypes {
        release {
            // TODO: Add your own signing config for the release build.
            // Signing with the debug keys for now, so `flutter run --release` works.
            signingConfig = signingConfigs.debug
        }

    }
}


Podfile use_frameworks! causes Undefined is not an Object in iOS

I added use_frameworks! as another library I need has its iOS portion written completely in Swift and is meant to be used as an embedded framework. However, I found that by doing so, I cause the following error.

I'm not sure if it's relevant but just in case, Store.js line 8 is import FilesystemStorage from 'redux-persist-filesystem-storage'; which itself uses react-native-fetch-blob.
I've thus far isolated the issue to use_frameworks!, whereupon pod installing with it has the error, and pod installing without it runs perfectly fine.

While it is an issue, apparently multiple React Native libraries have this problem.
My solution has been to use Cocoapods for static libraries as more RN libraries support Cocoapods, and Carthage for libraries that wrap Swift frameworks.


xcrun is not installed

Getting an error running this step on the Linux stack:
[2023-07-20T09:07:56.423Z] ['error'] There was an error running the uploader: xcrun is not installed, cannot process files

Probably introduced by this PR https://github.com/codecov/codecov-bitrise/pull/27?

@egor-n can you paste the entire log from Codecov here?

gpg: directory '/root/.gnupg' created
gpg: keybox '/root/.gnupg/trustedkeys.gpg' created
gpg: /root/.gnupg/trustdb.gpg: trustdb created
gpg: key ******: public key "Codecov Uploader (Codecov Uploader Verification Key<EMAIL_ADDRESS>imported
gpg: Total number processed: 1
gpg:               imported: 1
gpg: keybox '/root/.gnupg/trustedkeys.kbx' created
gpg: key ******: public key "Codecov Uploader (Codecov Uploader Verification Key<EMAIL_ADDRESS>imported
gpg: Total number processed: 1
gpg:               imported: 1
gpgv: can't allocate lock for '/root/.gnupg/trustedkeys.kbx'
gpgv: Signature made Tue 20 Jun 2023 03:39:52 PM UTC
gpgv:                using RSA key ******
gpgv: Good signature from "Codecov Uploader (Codecov Uploader Verification Key<EMAIL_ADDRESS>codecov: OK
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0

100   642    0   642    0     0   5440      0 --:--:-- --:--:-- --:--:--  5487
"version":"v0.6.1"
-Z -C a9329221814508644b40e32a96278d5f300a1d4e --xs
[2023-07-24T08:45:14.909Z] ['info']
     _____          _
    / ____|        | |
   | |     ___   __| | ___  ___ _____   __
   | |    / _ \ / _` |/ _ \/ __/ _ \ \ / /
   | |___| (_) | (_| |  __/ (_| (_) \ V /
    \_____\___/ \__,_|\___|\___\___/ \_/
  Codecov report uploader 0.6.1
[2023-07-24T08:45:14.915Z] ['info'] => Project root located at: /bitrise/src
[2023-07-24T08:45:14.918Z] ['info'] ->  Token found by environment variables
[2023-07-24T08:45:14.931Z] ['error'] There was an error running the uploader: xcrun is not installed, cannot process files

Got it, and how are you calling the Step @egor-n

- codecov:
    inputs:
    - OS: linux
    - CODECOV_TOKEN: "$CODECOV_TOKEN"


Enhance nntrainer inference filter

Regarding the implementation (#1007)

Make it work without giving in/out dimension (as it is stated inside the model description)
Giving in/out dimension is possible
Don't copy input but let nnstreamer allocate memory
Dynamic output dimension calculation from given input (this is needed because we accept number of batches)

Regarding the reliability (waiting for nnstreamer/nnstremaer/#3128)

Unittest for the inference wrapper
Templated sub-plugin test
Integrated test nnstreamer with singleshot api
Integrated test with gstreamer

:octocat: cibot: Thank you for posting issue #1005. The person in charge will reply soon.

Giving in/out dimension is possible but batch is ignored (@kparichay, any opinions?)

Lets the follow the semantics used by nnstreamer for tflite extension.
From nntrainer point of view, the batch specified in the data dimensions will be handled by the model::inference method.

Also, you can consider updating the tensor-filter plugin to use the c++ API headers, whereever possible.

#1010 handles the issue.
Yes, I made it to handle as pretty much other extension does.
I didn't use ccapi for compatibility reason, but it can be almost directly translated :)


Acme::Client::Error::AccountDoesNotExist

I had been using Webfaction's tool for generating Let's Encrypt certificates, but it appears to be disabled for issuing new ones and there's no sign of whether it will be reactivated. So, I installed this tool and seem to have everything configured, but get this error when I run it.
/home/bwareham/.letsencrypt_webfaction/gems/gems/acme-client-2.0.6/lib/acme/client/faraday_middleware.rb:54:in `raise_on_error!': No account exists with the provided key (Acme::Client::Error::AccountDoesNotExist)
	from /home/bwareham/.letsencrypt_webfaction/gems/gems/acme-client-2.0.6/lib/acme/client/faraday_middleware.rb:38:in `on_complete'
	from /home/bwareham/.letsencrypt_webfaction/gems/gems/acme-client-2.0.6/lib/acme/client/faraday_middleware.rb:23:in `block in call'
	from /home/bwareham/.letsencrypt_webfaction/gems/gems/faraday-1.0.1/lib/faraday/response.rb:65:in `on_complete'
	from /home/bwareham/.letsencrypt_webfaction/gems/gems/acme-client-2.0.6/lib/acme/client/faraday_middleware.rb:23:in `call'
	from /home/bwareham/.letsencrypt_webfaction/gems/gems/faraday-1.0.1/lib/faraday/rack_builder.rb:153:in `build_response'
	from /home/bwareham/.letsencrypt_webfaction/gems/gems/faraday-1.0.1/lib/faraday/connection.rb:492:in `run_request'
	from /home/bwareham/.letsencrypt_webfaction/gems/gems/faraday-1.0.1/lib/faraday/connection.rb:279:in `post'
	from /home/bwareham/.letsencrypt_webfaction/gems/gems/acme-client-2.0.6/lib/acme/client.rb:260:in `post'
	from /home/bwareham/.letsencrypt_webfaction/gems/gems/acme-client-2.0.6/lib/acme/client.rb:89:in `account'
	from /home/bwareham/.letsencrypt_webfaction/gems/gems/acme-client-2.0.6/lib/acme/client.rb:99:in `kid'
	from /home/bwareham/.letsencrypt_webfaction/gems/gems/letsencrypt_webfaction-4.0.1/lib/letsencrypt_webfaction/application/run.rb:166:in `register_key'
	from /home/bwareham/.letsencrypt_webfaction/gems/gems/letsencrypt_webfaction-4.0.1/lib/letsencrypt_webfaction/application/run.rb:35:in `run!'
	from /home/bwareham/.letsencrypt_webfaction/gems/gems/letsencrypt_webfaction-4.0.1/exe/letsencrypt_webfaction:8:in `<top (required)>'
	from /home/bwareham/.letsencrypt_webfaction/gems/bin/letsencrypt_webfaction:23:in `load'
	from /home/bwareham/.letsencrypt_webfaction/gems/bin/letsencrypt_webfaction:23:in `<main>'

I tried changing the email address in the .toml file after finding that worked for others who had similar problems with acme clients, but it didn't resolve my problem. HOWEVER, Webfaction's Let Encrypt button mysteriously showed up today as an option for my newly created site, so I was able to generate a certificate. If you have no interest in digging into this issue please feel free to close it.


Rename NumericLiteralTypeAnnotation to NumberLiteralTypeAnnotation

Q
A

Bug fix?
no

Breaking change?
yes

New feature?
no

Deprecations?
no

Spec compliancy?
flow

Tests added/pass?
yes

Fixed tickets
#329

License
MIT

Flow uses NumberLiteralTypeAnnotation rather than NumericLiteralTypeAnnotation, this brings babylon inline.

Current coverage is 97.46% (diff: 100%)

Merging #332 into 7.0 will not change coverage

@@                7.0       #332   diff @@
==========================================
  Files            19         19
  Lines          3237       3237
  Methods         338        338
  Messages          0          0
  Branches        847        847
==========================================
  Hits           3155       3155
  Misses           35         35
  Partials         47         47

Powered by Codecov. Last update c424156...60079c9


Test count regression checking

Tim Leslie   [Today at 16:15]
Thanks @mitchell. Thought bubble: it’d be good if we had some kind of test count regression type thing to catch this kind of oversight. :man-shrugging:
2 replies
Mitchell Hamilton   [2 minutes ago]
i think that’s possible with jest. iirc you can make it write a JSON file with the number of tests, ones that are skipped and other things
Tim Leslie   [< 1 minute ago]
Yeah, presumably there’s a way to get circle CI to investigate that and somehow make noise if the numbers change, maybe just a bot like the changeset bot, rather than a hard and fast PR blocker.

@mitchellhamilton or @timleslie can we add a bit more detail to this one please :)


Repository controller doesn't update ressource on password change

What happened?
The isUpToDate method does not check if the password provided via secret changed.
The workaround is currently to trigger an update-call by changing another field in the repo claim.
How can we reproduce it?
Deploy secret with e.g. token, deploy repo referencing the secret (see example).
Write a new token in the secret or reference another secret with a new token.
-> no update call/request + new token is not being used

/fresh
I would like to contribute to this issue.


Deprecation of torch._six.int_classes and suggested replacement

Description: The import statement from torch._six import int_classes is currently deprecated. After investigating, it was found that the suggested replacement for this is int_classes = (bool, int).
Steps to reproduce:

Attempt to import int_classes using from torch._six import int_classes
Observe the error.
Suggested Solution: Use int_classes = (bool, int) instead of importing int_classes from torch._six.

Expected Outcome: The code that previously used from torch._six import int_classes should be updated to use int_classes = (bool, int) to avoid the deprecation error.
Additional Information: This change was introduced in the newer release of PyTorch and can be found in the documentation.

It seems the issue is caused by the usage of a higher version of torch. Thanks for pointing it out.


RequestLifetimeTracking forwardRequests:  Duplicate keys were found in Dictionary

Hi,
First of all, thanks again for both RxSwift and RxFeedback, I really appreciate your work!
I'm not sure if this is the right channel for presenting this issue, but I'm experiencing (quite randomly but frequently) a crash for which I'm running out of ideas:
Thread 1: Fatal error: Duplicate keys of type 'ClassesStateMachine' were found in a Dictionary.
This is part of the stack trace:
#0	0x00000001f9231194 in swift_runtime_on_report ()
#1	0x00000001f928781c in swift_stdlib_reportFatalError ()
#2	0x00000001f8fd0ff4 in specialized String.withUnsafeBufferPointerToUTF8(:) ()
#3	0x00000001f91b4de0 in specialized assertionFailure( : _ : flags:) ()
#4	0x00000001f90ca048 in KEY_TYPE_OF_DICTIONARY_VIOLATES_HASHABLE_REQUIREMENTS(:) ()
#5	0x00000001f9035084 in NativeDictionary.setValue(:forKey:isUnique:) ()
#6	0x00000001f9015268 in Dictionary.Variant.setValue(:forKey:) ()
#7	0x00000001f91d7b20 in specialized Dictionary.subscript.setter ()
#8	0x00000001f8fe32d8 in Dictionary.subscript.setter ()
#9	0x0000000104a7b760 in closure #1 in RequestLifetimeTracking.forwardRequests(:) at myProject/Pods/RxFeedback/Sources/RxFeedback/Feedbacks.swift:160
#10	0x0000000104a77cfc in AsyncSynchronized.async(:) at myProject/Pods/RxFeedback/Sources/RxFeedback/AsyncSynchronized.swift:32
#11	0x0000000104a7ad38 in RequestLifetimeTracking.forwardRequests(:) at myProject/Pods/RxFeedback/Sources/RxFeedback/Feedbacks.swift:148
#12	0x0000000104a7dd90 in closure #1 in closure #1 in closure #1 in react<A, B, C, D>(requests:effects:) at myProject/Pods/RxFeedback/Sources/RxFeedback/Feedbacks.swift:236
The line that crashes is 160:
state.lifetimeByIdentifier[requestID] = (...)
Could it be possible that this method:
internal func async(_ mutate: @escaping Mutate) {
        guard var executeMutation = self.enqueue(mutate) else {
            return
        }
        repeat {
            executeMutation(&state) // -> is a lock needed here?
            guard let nextExecute = self.dequeue() else {
                return
            }
            executeMutation = nextExecute
        } while true
    }

mutates concurrently the state, therefore the dictionary, creating duplicate entries?
I'm wondering if that code needs to be synchronized too like queue and enqueue in the same class.
Any thoughts?
Not sure if this information helps, but: ClassesStateMachine is a Request object that I'm returning as part of some of the feedbacks that I have registered in a Driver.system. I'm using a Set to keep alive some of the requests and services started in previous loops.
I'd really appreciate any ideas you might have about this,
Thanks again!
Leandro

@leandromperez,
It would be nice if you can isolate your code and post it here.

Could it be possible that this method: ... mutates concurrently the state, therefore the dictionary, creating duplicate entries?

No, this method executes blocks in a serial fashion.

Hi @eliekarouz,
Thanks for your answer.
This is a really condensed version of the code, there are many different parts to it, but this is mostly what's related to the feedback loop:

struct ClassesStateMachine{
   //This is the State
         ...
}

extension ClassesStateMachine {
    typealias FeedbackLoop = (Driver<ClassesStateMachine>) -> Signal<ClassesStateMachine.Event>

    struct Feedback {

	//This is the system driver, a reduced version of it
        static func statemachineFeedbackDriver(_ interactor: ClassesInteractorImp) -> Driver<ClassesStateMachine> {

		return Driver.system(initialState: ClassesStateMachine.initialState,
				     reduce: ClassesStateMachine.reduce,
				     feedback:
						Feedback.uiFeedback(interactor),
						Feedback.processInteractions(interactor))
        }

        //This is the feedback that will analyze the state and respond with a service execution. E.g. when the user interacts with the screen, like tapping a button to execute some logic in the backend.
	//It returns a Set of Statemachine to avoid cancelling pending services of previous loops (i.e. interactios generated in previous Statemachines)
        private static func processInteractions(_ interactor: ClassesInteractorImp) -> ClassesStateMachine.FeedbackLoop {

            let interactionToProcess : (ClassesStateMachine) -> Set<ClassesStateMachine> = { statemachine in
                if statemachine.interactionToProcess != nil {
                    return Set([statemachine])
                }
                return Set()
            }

            let processInteraction : (ClassesStateMachine) -> Signal<ClassesStateMachine.Event> = { (statemachine) in
                return interactor.executeInteraction(of:statemachine)
            }

            return react(requests: interactionToProcess, effects: processInteraction)
        }

	//This binds te UI with the state
        private static func uiFeedback(_ interactor : ClassesInteractorImp) -> ClassesStateMachine.FeedbackLoop {

            return bind {[unowned interactor] stateMachine in

                let subscriptions = [
                    stateMachine.drive(interactor.presenter.statemachineInput),
                ]

                let events : [Signal<ClassesStateMachine.Event>] = [ interactor.viewController.userEvents]

                return Bindings(subscriptions: subscriptions, events: events)
            }
        }
    }
}

extension ClassesInteractorImp {

    //An interaction is an action that the user can perform on the screen, containing the necessary data to execute a service
    func executeInteraction( of statemachine:ClassesStateMachine) -> Signal<ClassesStateMachine.Event> {

        guard let interaction = statemachine.interactionToProcess else {fatalError("The statemachine must have an interaction")}

        let service = self.service(for:interaction, of: statemachine)

        return service.asSignal(onErrorRecover: { .just( ClassesStateMachine.Event.didFail(interaction, error:$0)) })
    }

    //This will perform a service, i.e. talk to the backend, and create an event when the response is obtained.
    func service(for interaction: ClassesStateMachine.Interaction, of statemachine: ClassesStateMachine) -> Observable<ClassesStateMachine.Event>{

        switch interaction {

        case .doSomething :
            return doSomething(with: statemachine) // talks to the backend to doSomething and returns an Event in response

            ...
        }
}

I was thinking that maybe more than one effect was mutating that dictionary concurrently, because I cannot think of another way of inserting a second object with an existing key into that dictionary.
We're not calling this function directly: public func react<State, Request: Equatable, RequestID, Event>(     requests: @escaping (State) -> [RequestID: Request],     effects: @escaping (_ initial: Request, _ state: Observable<Request>)
We're calling this one: public func react<State, Request, Event>(     requests: @escaping (State) -> Set<Request>,     effects: @escaping (Request) -> Signal<Event> )
I hope this information is useful somehow,
Thanks again,
Leandro

@leandromperez How are you declaring hashable/equatable for the ClassesStateMachine. Could it be that you have by mistake reference types that are being mutated AND used to compute the hash or ==

struct ClassesStateMachine {
    var id : Int
}

extension ClassesStateMachine: Equatable {}
func == (lhs: ClassesStateMachine, rhs: ClassesStateMachine) -> Bool {
    return lhs.id == rhs.id
}

Sometimes the reducer returns a StateMachine that doesn't mutate the id, to avoid repeating some effects in the next loop. I don't see how that could cause that crash, but do you think it might be a problem?

@leandromperez ,
Please check this line:
https://github.com/apple/swift/blob/f978cb0ba32acad5cc434331fa6a6b0c39ea9358/stdlib/public/core/NativeDictionary.swift#L449
Try to look in your code for classes (reference types) not enums or structs (value types)... Most probably you are mutating the variables inside these classes which is causing this crash.
FYI this code crashes with a similar error because the class XString is being mutated...
class XString: Hashable, Equatable {
    static func == (lhs: XString, rhs: XString) -> Bool {
        return lhs.string == rhs.string
    }

    var string: String

    init(_ string: String) {
        self.string = string
    }

    func hash(into hasher: inout Hasher) {
        hasher.combine(string)
    }
}

struct FakeValueType: Hashable, Equatable {
    let xstring: XString
}

func test() {
    let str1 = FakeValueType(xstring: XString("SomeString"))
    var dict = [str1: 0]
    for i in 0...100 {
        str1.xstring.string = "Mutation\(i) for SomeString"
        dict[str1] = i
    }
}

@eliekarouz That makes sense.
If I understood correctly, the problem comes when the struct (that's used as the dictionary key) is associated with a reference type instance, and when such instance is used to calculate the hash value.
I couldn't find a reference type instance inside the graph of associations that are used inside the hash function. But anyways, there might be one hidden somewhere I've missed.
So, I've changed the hashing code so it depends only on the identifier that's used inside the equals function. Hopefully, that will fix the issue.
I can close this ticket and re-open it if necessary,
Thanks for your help!


Conditions for conditional types of function parameters don't propagate into function bodies

Bug Report
Even when TypeScript proves that conditional type conditions hold, these proofs aren't fully propagated into the function body.
🔎 Search Terms
conditional type propagation witness entails function parameter
🕗 Version & Regression Information

This is the behavior in every version I tried since v3.3.3, and I reviewed the FAQ for entries about conditional type condition propagation

⏯ Playground Link
Playground Link
💻 Code

interface IData<T> {
    data: T
};
function getData<T extends IData<U>, U>(x: T): U {
    return x.data;
}

class A implements IData<boolean> {
    constructor(public data: boolean) {};
};
class B {
    constructor() {};
}

type MyMap = {
    "a": A,
    "b": B,
}
const myMap: MyMap = {
    "a": new A(true),
    "b": new B,
};

function myConsumer<K extends keyof MyMap, T extends IData<U>, U>(key: MyMap[K] extends T ? K : never): U {
    const _: K = key; // valid iff `MyMap[K] extends T`
    const value: T = myMap[key];
    return getData(value);
}

🙁 Actual behavior
TypeScript fails to type check this code, with the following error:
Type 'MyMap[MyMap[K] extends T ? K : never]' is not assignable to type 'T'.
  'T' could be instantiated with an arbitrary type which could be unrelated to 'MyMap[MyMap[K] extends T ? K : never]'.

🙂 Expected behavior
TypeScript successfully type checks this code. It can already prove that MyMap[K] extends T in order to bind key with type K.

Resolving of conditional types is deferred when they involve unbound type argumente. This is a design limitation.

There's not really a great way to describe the sorts of behavior where functions want to talk about "keys K of type T where T[K] is assignable to U". You can perform the filtering operation and you can perform the lookup operation but TS doesn't carry over the higher-order information that K' from keyof K in T where T[K] extends U means the T[K'] should behave as an arbitrary subtype of U.
See #48992

assuming this is a simpler example of the same issue
type Foo<T extends string> = T extends string ? T : never

const makeFoo = <T extends string>(value: T): Foo<T> => value // error

Got a similar error
function foo<T extends true | false>(arg: T): T extends true ? string : number {
  return arg === true ? 'yes' : 0 // Type 'number' cannot be assigned to type 'T extends true? String: number'. ts(2322)
}

How to implement the function of Conditional Types? No example is found in the document.

@mengdu i believe that's a different issue. it's caused by the fact that narrowing a value with a generic type doesn't necessarily mean it's safe to narrow the generic itself. this can be demonstrated by adding a second argument to your function:
type Foo<T extends string> = T extends string ? T : never

const makeFoo = <T extends string>(value: T): Foo<T> => value // error

function foo<T extends true | false>(arg: T, arg2: T): T extends true ? string : number {
    if (arg === true) {
        // these two lines have errors, because narrowing arg can't narrow T because it would be unsafe to do so
        const foo: true = arg2 //arg2 can be false
        return 'yes'
    } else {
        return 0
    }
}

foo(true, false)

see https://github.com/microsoft/TypeScript/issues/21732#issuecomment-1424824153 for another example

@RyanCavanaugh The initial test case still fails type check on 5.5.0-dev.20240324. Why was this closed as completed?


cloud-function-aws triggered by SQSEvent

Hi,
I was following the sample of cloud-function-aws.
build & run successfully. Performance was unbelievable good. (even with JPA & Postgres)
I want to run my cloud-function with a SQS trigger, using SQSEvent.
Without spring-native:  i've been using "SpringBootRequestHandler"
(which is now deprecated in favor of individual implementations of invokers)
and SQSEvent worked fine.
When running using spring native and SQSEvent - im getting:
"BeanFactoryAwareFunctionRegistry : Failed to convert output"
The handler in AWS Lambda console was set to the name of function.
Is there a way to run spring-cloud-function-aws with spring-native and SQSEvent?
Thanks

I guess you need to add native configuration for SQSEvent, if you are using 0.9.0-SNAPSHOT, this can be done with @NativeHints annotation, see an example here.
Check the detailed log error for more details about what should be configured.

Got it. Thank you. I've been using the latest tag 0.8.5
Also was not aware of @NativeHint


Black-reformat step in tox

Freshmaker is currently using a black-check step in tox. That means that black will check if it would reformat some file, and exits an error in case it would.
However, it would also be nice to have black actually reformat files during development, using the same parameters as will the check step.
This commit introduces the black-reformat in tox, which can be called manually during development to make the actual reformatting. It also introduces quick instructions on how to call it the readme file.
JIRA: CWFHEALTH-2357

LGTM. Thanks Mario!


You have exceeded a secondary rate limit

Got another Warning/Notification while trying to delete "not-that-small" (a not that huge either) amount of images.
Couldn't delete xxxxxxx/yyyy:77988391.
Status code: 403
Response: {'documentation_url': 'https://docs.github.com/en/free-pro-team@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits', 'message': 'You have exceeded a secondary rate limit. Please wait a few minutes before you try again.'}

Sorry for the lack of a response here @den-is. This issue will be fixed in the upcoming v3 release where we handle all secondary rate limits 👍 I'll update this issue when it's released.

The latest release redoes rate limiting completely. It should fix this issue, and a few more. That said, you can risk running into this, even in the new version, if you run multiple processes at the same time. For single runs however, we now handle secondary rate limits gracefully.
If you have time, the migration guide for v3 is included in the release post 👍 I would greatly appreciate feedback if you have any.
If you run into any issues, please share them in the issue opened for tracking the v3 release ☺


[epic][docs] Consider adding max character limits for all components

Description
There is little guidance for how many characters are acceptable to use in each web component; it would be helpful to provide UX guidance for each component on what the max acceptable character count should be.
For example, since we don't provide suggested character limits, it's not uncommon to see some websites that have upwards of 10 lines of body content in a card, whereas other websites have 4 lines of content per card. By providing content guidance, teams could learn that maybe there is a better component to use to get across the same point, or be more concise in their content writing.
Also, by providing an upward limit on character counts, users may have an easier easier time finding what they're looking for as they scan content for what they're interested in.
Suggested solution
Provide suggested max character limits in the documentation for the following web components:

[x] Accordion
[x] Alert
[ ] Announcement
[x] Blockquote
[x] Button
[x] Call to action
[x] Card
[x] Dialog
[ ] Disclosure
[ ] Jump links
[ ] Link(s)
[x] Popover
[ ] Progress steps
[ ] Promo
[x] Statistic
[x] Sticky banner
[x] Sticky card
[x] Tabs
[x] Tooltip

Example API
No response
Additional context
Our team occasionally uses the web components, and after recently working with a content writer, we were asked about max character limits for the components we're using. We checked with other teams and with the content team found that there doesn't seem to be a consensus on what the max limits should be for the marketing components. For example, in the documentation for cards, the closest suggestion is "A card features header, body, and footer sections. Those sections should include a limited amount of content to ensure that the card doesn’t become too tall." Leaving the user to determine what is "limited" or "too tall" could result in cards that are actually not limited and too tall.

for reference, the card docs guidelines state:

A card features header, body, and footer sections. Those sections should include a limited amount of content to ensure that the card doesn’t become too tall.
...
Don’t use too much content in one card, distribute extra content to other cards or somewhere else on the page.

Hey @bennypowers! Thanks for your response. :) I referenced that guideline in the "Additional context" section of my issue, however my content writers want a firm max limit as constraints are helpful to work with and force clarity in writing.
I gave them what I consider to be reasonable max limits, however I'm not sure if my suggestions are more or less restrictive than what the original intention was for each component.

Just bumping this to make note that this has been placed in the Continued redesign of documentation site milestone. Next steps, according to Mark:

Decide upon timing/prioritization.
Discovery around which (if any) components require max character counts, and what those counts should be.

Thanks for the update!

Added tile to the list and checked it off because character counts will be there once docs are published.

@nikkimk, these character counts include spaces. Let me know if you need additional copy or info.
Announcement (pulled from the Personalization patterns page)

Headline or body text should be 60 characters or fewer.
Call to action text should be 20 characters or fewer.

Card
I think this will need a character count because it was given as an example in this issue.

Title: 20
Headline: 50
Body text: 165

Disclosure

Title: 45 characters (This uses the same max character count as accordion's title.)

Jump links

Label: 18 characters
Section links: 30 characters

Link
I don't think an inline link would need a max character count.
Progress steps
Step indicator labels: 20 characters (maximum of two words)
Promo

I'm working on the design of inline promo for the Caterpie milestone, and I'll add a character count as part of the docs.

Sticky card

Title: 20
Headline: 50
Body text: 120

@marionnegp I have a few questions:

For card are this character counts for both the element and the pattern? Do we have character counts for the card footer?
For sticky card, do we have character counts for the footer?

Since CTA can be added to the footer for both cards and sticky cards, let's use the default CTA's character count.
Card's footer: 55 characters
Sticky card's footer: 55 characters


Improve precision of which transaction caused balance to go negative

The existing logic accumulates all buys first before decrementing from sells. As a result, it can only detect negative balances that persist until the end of the calculation period. It also means that the blamed transaction can be incorrect. Consider the following transaction sequence:
BUY 0.5 BTC
SELL 0.9 BTC
BUY 0.5 BTC
SELL 0.2 BTC

Under the current logic, an exception would be raised when processing the SELL 0.2 BTC transaction. This code, would raise an exception on the SELL 0.9 BTC transaction instead. A subtler case looks like this:
BUY 0.5 BTC
SELL 0.9 BTC
BUY 0.5 BTC
SELL 0.1 BTC

The current code would not raise any exception, despite going significantly negative for a period. The new code would correctly flag the invariant being violated.

If you like you can also run checks locally on your machine with make static_analysis check.

@eprbell Thanks, static analysis should be passing.
Completely forgot to mention this when opening the PR - a lot of test data fails this check now, which leads to a bunch of failing tests.
Easiest way would be to turn the check off for these tests, but there's a chance other issues are being hidden by the test data being off. For example, tab B2 of input/test_data.ods now has this failure in tests/test_tax_engine.py::TestTaxEngine::test_good_input:
E                   rp2.rp2_error.RP2ValueError: B2 balance of account "Coinbase" (holder "Bob") went negative (-0.20000000000) on the following transaction: OutTransaction:
E                     id=15
E                     timestamp=2020-02-11 19:58:00.000000 +0000
E                     asset=B2
E                     exchange=Coinbase
E                     holder=Bob
E                     transaction_type=TransactionType.SELL
E                     spot_price=12200.0000
E                     crypto_out_no_fee=1.00000000
E                     crypto_fee=0.00000000
E                     unique_id=
E                     is_taxable=True
E                     fiat_taxable_amount=12200.0000

Relevant cells showing the error to be correct are highlighted in yellow:

I still need to look at the code of this PR (I'll do that in the weekend or sooner), but this is a good check, so thanks for identifying and fixing this problem!
In fact I had already found that some tests end up with a negative balance (even without this fix) and added the -n switch to disable the check for negative balances: see https://github.com/eprbell/rp2/commit/195ed40a057550231c586f669505431bdf2438df.
I imagine this PR probably causes even more tests balances to go negative, however I'm reluctant to change the tests: the reason is that I did a lot of manual verification of these tests and they estabilish a strong baseline against regression (the balance may go negative here and there, but the tax engine logic is still tested fully and thoroughly by these tests).
So my suggestion is to:

disable negative balance checks (only for the tests that run into the issue), similar to what happens here: https://github.com/eprbell/rp2/blob/main/tests/test_ods_output_diff.py#L37
write new tests running with this check enabled and testing negative balances specifically (I think you already added some of these tests).

This should give us the best of both worlds. Do you have any concerns with this approach?

Makes sense as an approach - my main concern is having a giant PR that's infeasible to work with. Hopefully it's feasible to land smaller bits using your -n switch to keep things tractable. I'm going to be out of town this weekend, so might be a bit before I take a stab at things (and might submit some other unrelated PRs first).
Just for an order-of-magnitude, I'm seeing 47 tests passing, 1 failed, and 66 errors. The latter bucket seems to all be ODS output diff style tests.


Remove unused includes from old versions of the docs

Are these files no longer included by their respective CockroachDB versions, or are they referenced by those files but they are no longer used because we are no longer building those versions?  I'd worry about removing them unless we are also removing the referencing files.

@stbof The former. They aren't referenced in any document in their respective versions (or in any version for that matter, seeing as both Jekyll and htmltest built successfully).


Change the feature navigation color when multiple features are selected

When multiple features are selected on the map, the navigation color is blue, and to maintain consistency lets give make the look and feel as the pagination color as shown in the second pic

Pagination color:

@skrishn
The feature navigation UI is updated in this relase as per https://github.com/Esri/solutions-components/issues/417

@skrishn
Please check and let us know if any changes required for this in R03


Support Listing spells by System

It would be extremely useful to be able to list spells by system, like
?spells vanilla

Which would return only valid spell names for that system.

It's sort of supported already if you do ?spell system=vanilla but it's a pretty awful UX as it'll spit out each spell as it's own card, fine for when you've only got one or two spells but really awful when you've got lots.
I could make some changes to the logic so that if it returns more than 2 or 3 spells then it'll just spit out a list of names in a single message rather than doing a card for each.

This is mostly done now but is still a bit ugly. It'll return a code block with the list of spells and their system (in case someone searches by something other than system).
I've got pagination on the backlog for the API so once I add that I'll be able to return a more controlled amount back so the UX won't be just splatting a big list of text back to the client like it is now.