build for windows fails with LNK2001: unresolved external symbol, and more errors

Steps to reproduce

create a simple project using Visual Code/Flutter extension, such as the "first flutter app" namer_app codelab ... and ...
make sure to save it on a different device than the device Visual Studio/Windows SDK is installed on
Click on "Run" above the main() declaration in the VScode project code file.
Watch a stream of errors and the build fail on errors

Expected results
I had already got the namer_app running on the chrome device, which worked fine with my project source code on "P:" So, I was expecting to see my namer_app running as a windows app.
I recreated the project source files under %USERPROFILE% (on the C: drive) and the namer_app built for Windows without errors and displayed as expected, with hot reload working as expected.
I think the "Download the Flutter SDK" Warning text block on https://docs.flutter.dev/get-started/install/windows/desktop should also warn users to save their project files to %USERPROFILE% or C:\dev
Actual results
Several lines of error messages, and then "Build process failed." and "Exited (1)."  The screenshot below shows the error output, which includes references to my project files on P:  The Visual Studio installation is on C: in it's default installation configuration.
Code sample
Code sample
// just cut and paste from the "first flutter app" namer_app codelab (it's Step 3)
// find it here: https://codelabs.developers.google.com/codelabs/flutter-codelab-first#2

Screenshots or Video

Screenshots / Video demonstration

Logs
Logs
I'm using VScode for everything, not using terminal to enter commands. When I filed this bug with the Dart Code people, they asked me to use terminal to say: "flutter run", and if I have the same error, to refile this issue with flutter/flutter
```console
[Paste your logs here]
```

Flutter Doctor output
Doctor output
C:\Users\peter\flutter\bin\flutter.bat doctor -v

[√] Flutter (Channel stable, 3.19.1, on Microsoft Windows [Version 10.0.22631.3155], locale en-CA)
    • Flutter version 3.19.1 on channel stable at C:\Users\peter\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision abb292a07e (7 days ago), 2024-02-20 14:35:05 -0800
    • Engine revision 04817c99c9
    • Dart version 3.3.0
    • DevTools version 2.31.1

[√] Windows Version (Installed version of Windows is version 10 or higher)

[!] Android toolchain - develop for Android devices (Android SDK version 33.0.2)
    • Android SDK at C:\Users\peter\Documents\Processing\android\sdk
    • Platform android-33-2, build-tools 33.0.2
    X No Java Development Kit (JDK) found; You must have the environment variable JAVA_HOME set and the java binary in your PATH. You can download the JDK from https://www.oracle.com/technetwork/java/javase/downloads/.

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

[√] Visual Studio - develop Windows apps (Visual Studio Community 2022 17.9.2)
    • Visual Studio at C:\Program Files\Microsoft Visual Studio\2022\Community
    • Visual Studio Community 2022 version 17.9.34622.214
    • Windows 10 SDK version 10.0.22621.0

[!] Android Studio (not installed)
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/docs/get-started/install/windows#android-setup for detailed instructions).

[√] VS Code (version 1.86.2)
    • VS Code at C:\Users\peter\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.82.0

[√] Connected device (3 available)
    • Windows (desktop) • windows • windows-x64    • Microsoft Windows [Version 10.0.22631.3155]
    • Chrome (web)      • chrome  • web-javascript • Google Chrome 122.0.6261.69
    • Edge (web)        • edge    • web-javascript • Microsoft Edge 121.0.2277.112

[√] Network resources
    • All expected network resources are available.

! Doctor found issues in 2 categories.

Hi @peter-b-web
For us to further investigate this issue, please provide the error in text format instead of a screenshot for better readability and investigation.
You should switch to Terminal tab, execute flutter run -v (with verbose) and then share the entire stack trace here that will help us can look at this deeper. If the logs are too large to be uploaded to GitHub, you may upload them as a txt file or use online tools like https://pastebin.com/ to share it .Thanks!

The entire stack trace is here ... starting with the Terminal prompt ...
PS P:\Desktop\flutter_test\namer_app> flutter run -v
[ +208 ms] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[   +3 ms] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[        ] Artifact Instance of 'LegacyCanvasKitRemover' is not required, skipping update.
[   +7 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[ +112 ms] executing: C:\Users\peter\Documents\Processing\android\sdk\platform-tools\adb.exe devices -l
[  +44 ms] List of devices attached
[   +7 ms] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[   +6 ms] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[  +66 ms] Connected devices:
[  +34 ms] Windows (desktop) • windows • windows-x64    • Microsoft Windows [Version 10.0.22631.3155]
[   +1 ms] Chrome (web)      • chrome  • web-javascript • Google Chrome 122.0.6261.69
[        ] Edge (web)        • edge    • web-javascript • Microsoft Edge 121.0.2277.112
[        ] [1]: Windows (windows)
[        ] [2]: Chrome (chrome)
[        ] [3]: Edge (edge)
[        ] Please choose one (or "q" to quit)
[        ] :
[+11996 ms] 1
[  +30 ms] Skipping pub get: version match.
[ +451 ms] Generating P:\Desktop\flutter_test\namer_app\android\app\src\main\java\io\flutter\plugins\GeneratedPluginRegistrant.java
[ +181 ms] No packages with native assets. Skipping native assets compilation.
[   +2 ms] Initializing file store
[  +30 ms] Skipping target: gen_localizations
[   +3 ms] gen_dart_plugin_registrant: Starting due to {InvalidatedReasonKind.inputChanged: The following inputs have updated
contents: P:\Desktop\flutter_test\namer_app.dart_tool\package_config_subset}
[  +83 ms] gen_dart_plugin_registrant: Complete
[   +1 ms] Skipping target: composite
[   +1 ms] complete
[   +3 ms] Launching lib\main.dart on Windows in debug mode...
[   +2 ms] C:\Users\peter\flutter\bin\cache\dart-sdk\bin\dartaotruntime.exe --disable-dart-dev
C:\Users\peter\flutter\bin\cache\dart-sdk\bin\snapshots\frontend_server_aot.dart.snapshot --sdk-root
C:\Users\peter\flutter\bin\cache\artifacts\engine\common\flutter_patched_sdk/ --incremental --target=flutter
--experimental-emit-debug-metadata -DFLUTTER_WEB_AUTO_DETECT=true
-DFLUTTER_WEB_CANVASKIT_URL=https://www.gstatic.com/flutter-canvaskit/04817c99c9fd4956f27505204f7e344335810aed/ --output-dill
C:\Users\peter\AppData\Local\Temp\flutter_tools.c8aaccfc\flutter_tool.11366616\app.dill --packages
P:\Desktop\flutter_test\namer_app.dart_tool\package_config.json -Ddart.vm.profile=false -Ddart.vm.product=false --enable-asserts
--track-widget-creation --filesystem-scheme org-dartlang-root --initialize-from-dill
build\f4da31578bf74e160393d588ebd02ee2.cache.dill.track.dill --verbosity=error --enable-experiment=alternative-invalidation-strategy
[  +74 ms] executing: C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe -format json -products * -utf8 -latest
-version 16 -requires Microsoft.VisualStudio.Workload.NativeDesktop Microsoft.VisualStudio.Component.VC.Tools.x86.x64
Microsoft.VisualStudio.Component.VC.CMake.Project
[  +77 ms] Exit code 0 from: C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe -format json -products * -utf8
-latest -version 16 -requires Microsoft.VisualStudio.Workload.NativeDesktop Microsoft.VisualStudio.Component.VC.Tools.x86.x64
Microsoft.VisualStudio.Component.VC.CMake.Project
[   +1 ms] [
{
"instanceId": "5ef9c351",
"installDate": "2024-02-27T20:33:11Z",
"installationName": "VisualStudio/17.9.2+34622.214",
"installationPath": "C:\Program Files\Microsoft Visual Studio\2022\Community",
"installationVersion": "17.9.34622.214",
"productId": "Microsoft.VisualStudio.Product.Community",
"productPath": "C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\devenv.exe",
"state":<PHONE_NUMBER>,
"isComplete": true,
"isLaunchable": true,
"isPrerelease": false,
"isRebootRequired": false,
"displayName": "Visual Studio Community 2022",
"description": "Powerful IDE, free for students, open-source contributors, and individuals",
"channelId": "VisualStudio.17.Release",
"channelUri": "https://aka.ms/vs/17/release/channel",
"enginePath": "C:\Program Files (x86)\Microsoft Visual
Studio\Installer\resources\app\ServiceHub\Services\Microsoft.VisualStudio.Setup.Service",
"installedChannelId": "VisualStudio.17.Release",
"installedChannelUri": "https://aka.ms/vs/17/release/channel",
"releaseNotes": "https://docs.microsoft.com/en-us/visualstudio/releases/2022/release-notes-v17.9#17.9.2",
"resolvedInstallationPath": "C:\Program Files\Microsoft Visual Studio\2022\Community",
"thirdPartyNotices": "https://go.microsoft.com/fwlink/?LinkId=661288",
"updateDate": "2024-02-27T20:33:11.6333063Z",
"catalog": {
"buildBranch": "d17.9",
"buildVersion": "17.9.34622.214",
"id": "VisualStudio/17.9.2+34622.214",
"localBuild": "build-lab",
"manifestName": "VisualStudio",
"manifestType": "installer",
"productDisplayVersion": "17.9.2",
"productLine": "Dev17",
"productLineVersion": "2022",
"productMilestone": "RTW",
"productMilestoneIsPreRelease": "False",
"productName": "Visual Studio",
"productPatchVersion": "2",
"productPreReleaseMilestoneSuffix": "1.0",
"productSemanticVersion": "17.9.2+34622.214",
"requiredEngineVersion": "3.9.2164.57262"
},
"properties": {
"campaignId": "3600:3284660329c9437b91b5504c0fcfd4b7",
"channelManifestId": "VisualStudio.17.Release/17.9.2+34622.214",
"nickname": "",
"setupEngineFilePath": "C:\Program Files (x86)\Microsoft Visual Studio\Installer\setup.exe"
}
}
]
[   +7 ms] Building Windows application...
[ +119 ms] <- compile package:namer_app/main.dart
[   +3 ms] executing: C:\Program Files\Microsoft Visual
Studio\2022\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin\cmake.exe -S P:\Desktop\flutter_test\namer_app\windows -B
P:\Desktop\flutter_test\namer_app\build\windows\x64 -G Visual Studio 17 2022 -A x64 -DFLUTTER_TARGET_PLATFORM=windows-x64
[ +162 ms] -- Selecting Windows SDK version 10.0.22621.0 to target Windows 10.0.22631.
[ +189 ms] -- Configuring done (0.2s)
[ +662 ms] -- Generating done (0.6s)
[  +49 ms] -- Build files have been written to: P:/Desktop/flutter_test/namer_app/build/windows/x64
[   +7 ms] executing: C:\Program Files\Microsoft Visual
Studio\2022\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin\cmake.exe --build
P:\Desktop\flutter_test\namer_app\build\windows\x64 --config Debug --target INSTALL --verbose
[ +102 ms] Change Dir: 'P:/Desktop/flutter_test/namer_app/build/windows/x64'
[   +1 ms] Run Build Command(s): "C:/Program Files/Microsoft Visual Studio/2022/Community/MSBuild/Current/Bin/amd64/MSBuild.exe"
INSTALL.vcxproj /p:Configuration=Debug /p:Platform=x64 /p:VisualStudioVersion=17.0 /v:n
[ +152 ms] MSBuild version 17.9.5+33de0b227 for .NET Framework
[  +86 ms] Build started 2024-02-29 7:26:00 AM.
[ +195 ms] Project "P:\Desktop\flutter_test\namer_app\build\windows\x64\INSTALL.vcxproj" on node 1 (default targets).
[        ] Project "P:\Desktop\flutter_test\namer_app\build\windows\x64\INSTALL.vcxproj" (1) is building
"P:\Desktop\flutter_test\namer_app\build\windows\x64\ZERO_CHECK.vcxproj" (2) on node 1 (default targets).
[        ] PrepareForBuild:
[        ]   Structured output is enabled. The formatting of compiler diagnostics will reflect the error hierarchy. See
https://aka.ms/cpp/structured-output for more details.
[   +1 ms] InitializeBuildStatus:
[        ]   Creating "x64\Debug\ZERO_CHECK\ZERO_CHECK.tlog\unsuccessfulbuild" because "AlwaysCreate" was specified.
[        ]   Touching "x64\Debug\ZERO_CHECK\ZERO_CHECK.tlog\unsuccessfulbuild".
[  +18 ms] CustomBuild:
[        ]   All outputs are up-to-date.
[  +27 ms] FinalizeBuildStatus:
[        ]   Deleting file "x64\Debug\ZERO_CHECK\ZERO_CHECK.tlog\unsuccessfulbuild".
[        ]   Touching "x64\Debug\ZERO_CHECK\ZERO_CHECK.tlog\ZERO_CHECK.lastbuildstate".
[        ] Done Building Project "P:\Desktop\flutter_test\namer_app\build\windows\x64\ZERO_CHECK.vcxproj" (default targets).
[  +54 ms] Project "P:\Desktop\flutter_test\namer_app\build\windows\x64\INSTALL.vcxproj" (1) is building
"P:\Desktop\flutter_test\namer_app\build\windows\x64\ALL_BUILD.vcxproj" (3) on node 1 (default targets).
[   +1 ms] Project "P:\Desktop\flutter_test\namer_app\build\windows\x64\ALL_BUILD.vcxproj" (3) is building
"P:\Desktop\flutter_test\namer_app\build\windows\x64\flutter\flutter_wrapper_app.vcxproj" (4) on node 1 (default targets).
[        ] Project "P:\Desktop\flutter_test\namer_app\build\windows\x64\flutter\flutter_wrapper_app.vcxproj" (4) is building
"P:\Desktop\flutter_test\namer_app\build\windows\x64\flutter\flutter_assemble.vcxproj" (5) on node 1 (default targets).
[        ] PrepareForBuild:
[        ]   Structured output is enabled. The formatting of compiler diagnostics will reflect the error hierarchy. See
https://aka.ms/cpp/structured-output for more details.
[   +1 ms] InitializeBuildStatus:
[        ]   Creating "x64\Debug\flutter_assemble\flutter_assemble.tlog\unsuccessfulbuild" because "AlwaysCreate" was specified.
[   +1 ms]   Touching "x64\Debug\flutter_assemble\flutter_assemble.tlog\unsuccessfulbuild".
[   +1 ms] CustomBuild:
[        ]   "The build of
'P:\Desktop\flutter_test\namer_app\build\windows\x64\CMakeFiles\a5b6e94afe30b7bcf6335f482d76d34e\flutter_assemble.rule' depends on
'P:\DESKTOP\FLUTTER_TEST\NAMER_APP\WINDOWS\FLUTTER\EPHEMERAL\FLUTTER_WINDOWS.DLL' which is produced by the build of
'P:\Desktop\flutter_test\namer_app\build\windows\x64\CMakeFiles\b8e36a16cbd8b8d886f26744c6300135\flutter_windows.dll.rule'. The items
cannot be built in parallel."
[  +86 ms]   Generating P:/Desktop/flutter_test/namer_app/windows/flutter/ephemeral/flutter_windows.dll,
P:/Desktop/flutter_test/namer_app/windows/flutter/ephemeral/flutter_export.h,
P:/Desktop/flutter_test/namer_app/windows/flutter/ephemeral/flutter_windows.h,
P:/Desktop/flutter_test/namer_app/windows/flutter/ephemeral/flutter_messenger.h,
P:/Desktop/flutter_test/namer_app/windows/flutter/ephemeral/flutter_plugin_registrar.h,
P:/Desktop/flutter_test/namer_app/windows/flutter/ephemeral/flutter_texture_registrar.h,
P:/Desktop/flutter_test/namer_app/windows/flutter/ephemeral/cpp_client_wrapper/core_implementations.cc,
P:/Desktop/flutter_test/namer_app/windows/flutter/ephemeral/cpp_client_wrapper/standard_codec.cc,
P:/Desktop/flutter_test/namer_app/windows/flutter/ephemeral/cpp_client_wrapper/plugin_registrar.cc,
P:/Desktop/flutter_test/namer_app/windows/flutter/ephemeral/cpp_client_wrapper/flutter_engine.cc,
P:/Desktop/flutter_test/namer_app/windows/flutter/ephemeral/cpp_client_wrapper/flutter_view_controller.cc, phony
[ +506 ms]   [  +50 ms] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[   +1 ms]   [   +2 ms] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[   +1 ms]   [        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[   +1 ms]   [        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'LegacyCanvasKitRemover' is not required, skipping update.
[        ]   [   +1 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[   +1 ms]   [        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[   +1 ms]   [        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[  +59 ms]   [  +74 ms] Artifact Instance of 'MaterialFonts' is not required, skipping update.
[   +1 ms]   [        ] Artifact Instance of 'GradleWrapper' is not required, skipping update.
[   +1 ms]   [        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[   +1 ms]   [        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'LegacyCanvasKitRemover' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'FlutterSdk' is not required, skipping update.
[   +1 ms]   [   +1 ms] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[   +1 ms]   [        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'FontSubsetArtifacts' is not required, skipping update.
[        ]   [        ] Artifact Instance of 'PubDependencies' is not required, skipping update.
[  +21 ms]   [  +31 ms] Initializing file store
[  +24 ms]   [  +24 ms] Done initializing file store
[ +154 ms]   [ +153 ms] Skipping target: native_assets
[        ]   [   +1 ms] Skipping target: gen_localizations
[        ]   [   +1 ms] Skipping target: gen_dart_plugin_registrant
[+3195 ms]   [+3195 ms] Skipping target: unpack_windows
[+3266 ms]   [+3266 ms] Skipping target: kernel_snapshot
[ +509 ms]   [ +509 ms] Skipping target: debug_bundle_windows_assets
[   +1 ms]   [        ] Persisting file store
[   +8 ms]   [   +9 ms] Done persisting file store
[  +14 ms]   [  +14 ms] build succeeded.
[   +4 ms]   [   +4 ms] "flutter assemble" took 7,300ms.
[  +92 ms]   [  +92 ms] ensureAnalyticsSent: 88ms
[        ]   [        ] Running 0 shutdown hooks
[        ]   [        ] Shutdown hooks complete
[        ]   [        ] exiting with code 0
[  +98 ms] FinalizeBuildStatus:
[   +1 ms]   Deleting file "x64\Debug\flutter_assemble\flutter_assemble.tlog\unsuccessfulbuild".
[        ]   Touching "x64\Debug\flutter_assemble\flutter_assemble.tlog\flutter_assemble.lastbuildstate".
[        ] Done Building Project "P:\Desktop\flutter_test\namer_app\build\windows\x64\flutter\flutter_assemble.vcxproj" (default
targets).
[   +2 ms] PrepareForBuild:
[        ]   Structured output is enabled. The formatting of compiler diagnostics will reflect the error hierarchy. See
https://aka.ms/cpp/structured-output for more details.
[   +1 ms] InitializeBuildStatus:
[        ]   Creating "flutter_wrapper_app.dir\Debug\flutter.A007F3EF.tlog\unsuccessfulbuild" because "AlwaysCreate" was specified.
[        ]   Touching "flutter_wrapper_app.dir\Debug\flutter_.A007F3EF.tlog\unsuccessfulbuild".
[        ] CustomBuild:
[        ]   All outputs are up-to-date.
[  +46 ms] ClCompile:
[   +1 ms]   All outputs are up-to-date.
[  +29 ms] Lib:
[        ]   All outputs are up-to-date.
[   +2 ms]   flutter_wrapper_app.vcxproj -> P:\Desktop\flutter_test\namer_app\build\windows\x64\flutter\Debug\flutter_wrapper_app.lib
[  +19 ms] FinalizeBuildStatus:
[        ]   Deleting file "flutter_wrapper_app.dir\Debug\flutter_.A007F3EF.tlog\unsuccessfulbuild".
[        ]   Touching "flutter_wrapper_app.dir\Debug\flutter_.A007F3EF.tlog\flutter_wrapper_app.lastbuildstate".
[        ] Done Building Project "P:\Desktop\flutter_test\namer_app\build\windows\x64\flutter\flutter_wrapper_app.vcxproj" (default
targets).
[  +20 ms] Project "P:\Desktop\flutter_test\namer_app\build\windows\x64\ALL_BUILD.vcxproj" (3) is building
"P:\Desktop\flutter_test\namer_app\build\windows\x64\flutter\flutter_wrapper_plugin.vcxproj" (6) on node 1 (default targets).
[   +1 ms] PrepareForBuild:
[   +1 ms]   Structured output is enabled. The formatting of compiler diagnostics will reflect the error hierarchy. See
https://aka.ms/cpp/structured-output for more details.
[   +1 ms] InitializeBuildStatus:
[        ]   Creating "flutter_wrapper_plugin.dir\Debug\flutter_.F73D4AD8.tlog\unsuccessfulbuild" because "AlwaysCreate" was
specified.
[   +1 ms]   Touching "flutter_wrapper_plugin.dir\Debug\flutter_.F73D4AD8.tlog\unsuccessfulbuild".
[   +2 ms] CustomBuild:
[   +1 ms]   All outputs are up-to-date.
[   +9 ms] ClCompile:
[   +1 ms]   All outputs are up-to-date.
[   +7 ms] Lib:
[   +1 ms]   All outputs are up-to-date.
[        ]   flutter_wrapper_plugin.vcxproj ->
P:\Desktop\flutter_test\namer_app\build\windows\x64\flutter\Debug\flutter_wrapper_plugin.lib
[   +5 ms] FinalizeBuildStatus:
[        ]   Deleting file "flutter_wrapper_plugin.dir\Debug\flutter_.F73D4AD8.tlog\unsuccessfulbuild".
[        ]   Touching "flutter_wrapper_plugin.dir\Debug\flutter_.F73D4AD8.tlog\flutter_wrapper_plugin.lastbuildstate".
[        ] Done Building Project "P:\Desktop\flutter_test\namer_app\build\windows\x64\flutter\flutter_wrapper_plugin.vcxproj" (default
targets).
[  +24 ms] Project "P:\Desktop\flutter_test\namer_app\build\windows\x64\ALL_BUILD.vcxproj" (3) is building
"P:\Desktop\flutter_test\namer_app\build\windows\x64\runner\namer_app.vcxproj" (7) on node 1 (default targets).
[   +1 ms] PrepareForBuild:
[        ]   Structured output is enabled. The formatting of compiler diagnostics will reflect the error hierarchy. See
https://aka.ms/cpp/structured-output for more details.
[   +1 ms] InitializeBuildStatus:
[        ]   Touching "namer_app.dir\Debug\namer_app.tlog\unsuccessfulbuild".
[        ] CustomBuild:
[        ]   All outputs are up-to-date.
[  +38 ms] ClCompile:
[        ]   C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.39.33519\bin\HostX64\x64\CL.exe /c
/IP:\Desktop\flutter_test\namer_app\windows /IP:\Desktop\flutter_test\namer_app\windows\flutter\ephemeral
/IP:\Desktop\flutter_test\namer_app\windows\flutter\ephemeral\cpp_client_wrapper\include /nologo /W4 /WX /diagnostics:column /O2 /D
_UNICODE /D UNICODE /D _HAS_EXCEPTIONS=0 /D _DEBUG /D "FLUTTER_VERSION="0.0.1+1"" /D FLUTTER_VERSION_MAJOR=0 /D
FLUTTER_VERSION_MINOR=0 /D FLUTTER_VERSION_PATCH=1 /D FLUTTER_VERSION_BUILD=1 /D NOMINMAX /D UNICODE /D _UNICODE /D
"CMAKE_INTDIR="Debug"" /Gm- /EHsc /MD /GS /fp:precise /Zc:wchar_t /Zc:forScope /Zc:inline /std:c++17 /Fo"namer_app.dir\Debug\"
/Fd"namer_app.dir\Debug\vc143.pdb" /external:W4 /Gd /TP /wd4100 /errorReport:queue
P:\Desktop\flutter_test\namer_app\windows\flutter\generated_plugin_registrant.cc
P:\Desktop\flutter_test\namer_app\windows\runner\flutter_window.cpp
[ +132 ms]   generated_plugin_registrant.cc
[ +333 ms]   flutter_window.cpp
[ +675 ms]   Generating Code...
[ +118 ms] ResourceCompile:
[   +1 ms]   All outputs are up-to-date.
[  +36 ms] Link:
[        ]   C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.39.33519\bin\HostX64\x64\link.exe
/ERRORREPORT:QUEUE /OUT:"P:\Desktop\flutter_test\namer_app\build\windows\x64\runner\Debug\namer_app.exe" /INCREMENTAL
/ILK:"namer_app.dir\Debug\namer_app.ilk" /NOLOGO ..\flutter\Debug\flutter_wrapper_app.lib dwmapi.lib
P:\Desktop\flutter_test\namer_app\windows\flutter\ephemeral\flutter_windows.dll.lib kernel32.lib user32.lib gdi32.lib winspool.lib
shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib /MANIFEST /MANIFESTUAC:"level='asInvoker' uiAccess='false'"
/manifest:embed /manifestinput:P:\Desktop\flutter_test\namer_app\windows\runner\runner.exe.manifest
/PDB:"P:/Desktop/flutter_test/namer_app/build/windows/x64/runner/Debug/namer_app.pdb" /SUBSYSTEM:WINDOWS /TLBID:1 /DYNAMICBASE
/NXCOMPAT /IMPLIB:"P:/Desktop/flutter_test/namer_app/build/windows/x64/runner/Debug/namer_app.lib" /MACHINE:X64
namer_app.dir\Debug\Runner.res
[   +4 ms]   namer_app.dir\Debug\flutter_window.obj
[        ]   namer_app.dir\Debug\main.obj
[        ]   namer_app.dir\Debug\utils.obj
[   +1 ms]   namer_app.dir\Debug\win32_window.obj
[        ]   namer_app.dir\Debug\generated_plugin_registrant.obj
[ +193 ms] flutter_wrapper_app.lib(core_implementations.obj) : error LNK2001: unresolved external symbol __imp__invalid_parameter
[P:\Desktop\flutter_test\namer_app\build\windows\x64\runner\namer_app.vcxproj]
[   +3 ms] flutter_wrapper_app.lib(standard_codec.obj) : error LNK2001: unresolved external symbol __imp__invalid_parameter
[P:\Desktop\flutter_test\namer_app\build\windows\x64\runner\namer_app.vcxproj]
[   +1 ms] flutter_window.obj : error LNK2001: unresolved external symbol __imp__invalid_parameter
[P:\Desktop\flutter_test\namer_app\build\windows\x64\runner\namer_app.vcxproj]
[   +1 ms] main.obj : error LNK2001: unresolved external symbol __imp__invalid_parameter
[P:\Desktop\flutter_test\namer_app\build\windows\x64\runner\namer_app.vcxproj]
[   +1 ms] utils.obj : error LNK2001: unresolved external symbol __imp__invalid_parameter
[P:\Desktop\flutter_test\namer_app\build\windows\x64\runner\namer_app.vcxproj]
[   +1 ms] flutter_wrapper_app.lib(flutter_engine.obj) : error LNK2001: unresolved external symbol __imp__invalid_parameter
[P:\Desktop\flutter_test\namer_app\build\windows\x64\runner\namer_app.vcxproj]
[   +1 ms] flutter_wrapper_app.lib(core_implementations.obj) : error LNK2001: unresolved external symbol __imp__CrtDbgReport
[P:\Desktop\flutter_test\namer_app\build\windows\x64\runner\namer_app.vcxproj]
[   +1 ms] flutter_wrapper_app.lib(standard_codec.obj) : error LNK2001: unresolved external symbol __imp__CrtDbgReport
[P:\Desktop\flutter_test\namer_app\build\windows\x64\runner\namer_app.vcxproj]
[   +1 ms] flutter_window.obj : error LNK2001: unresolved external symbol __imp__CrtDbgReport
[P:\Desktop\flutter_test\namer_app\build\windows\x64\runner\namer_app.vcxproj]
[   +1 ms] main.obj : error LNK2001: unresolved external symbol __imp__CrtDbgReport
[P:\Desktop\flutter_test\namer_app\build\windows\x64\runner\namer_app.vcxproj]
[   +1 ms] utils.obj : error LNK2001: unresolved external symbol __imp__CrtDbgReport
[P:\Desktop\flutter_test\namer_app\build\windows\x64\runner\namer_app.vcxproj]
[   +1 ms] flutter_wrapper_app.lib(flutter_engine.obj) : error LNK2001: unresolved external symbol __imp__CrtDbgReport
[P:\Desktop\flutter_test\namer_app\build\windows\x64\runner\namer_app.vcxproj]
[   +1 ms] P:\Desktop\flutter_test\namer_app\build\windows\x64\runner\Debug\namer_app.exe : fatal error LNK1120: 2 unresolved
externals [P:\Desktop\flutter_test\namer_app\build\windows\x64\runner\namer_app.vcxproj]
[   +1 ms] Done Building Project "P:\Desktop\flutter_test\namer_app\build\windows\x64\runner\namer_app.vcxproj" (default targets) --
FAILED.
[   +1 ms] Done Building Project "P:\Desktop\flutter_test\namer_app\build\windows\x64\ALL_BUILD.vcxproj" (default targets) -- FAILED.
[        ] Done Building Project "P:\Desktop\flutter_test\namer_app\build\windows\x64\INSTALL.vcxproj" (default targets) -- FAILED.
[   +2 ms] Build FAILED.
[   +3 ms] "P:\Desktop\flutter_test\namer_app\build\windows\x64\INSTALL.vcxproj" (default target) (1) ->
[   +1 ms] "P:\Desktop\flutter_test\namer_app\build\windows\x64\ALL_BUILD.vcxproj" (default target) (3) ->
[        ] "P:\Desktop\flutter_test\namer_app\build\windows\x64\runner\namer_app.vcxproj" (default target) (7) ->
[        ] (Link target) ->
[        ]   flutter_wrapper_app.lib(core_implementations.obj) : error LNK2001: unresolved external symbol __imp__invalid_parameter
[P:\Desktop\flutter_test\namer_app\build\windows\x64\runner\namer_app.vcxproj]
[   +1 ms]   flutter_wrapper_app.lib(standard_codec.obj) : error LNK2001: unresolved external symbol __imp__invalid_parameter
[P:\Desktop\flutter_test\namer_app\build\windows\x64\runner\namer_app.vcxproj]
[   +1 ms]   flutter_window.obj : error LNK2001: unresolved external symbol __imp__invalid_parameter
[P:\Desktop\flutter_test\namer_app\build\windows\x64\runner\namer_app.vcxproj]
[   +2 ms]   main.obj : error LNK2001: unresolved external symbol __imp__invalid_parameter
[P:\Desktop\flutter_test\namer_app\build\windows\x64\runner\namer_app.vcxproj]
[   +3 ms]   utils.obj : error LNK2001: unresolved external symbol __imp__invalid_parameter
[P:\Desktop\flutter_test\namer_app\build\windows\x64\runner\namer_app.vcxproj]
[   +1 ms]   flutter_wrapper_app.lib(flutter_engine.obj) : error LNK2001: unresolved external symbol __imp__invalid_parameter
[P:\Desktop\flutter_test\namer_app\build\windows\x64\runner\namer_app.vcxproj]
[   +1 ms]   flutter_wrapper_app.lib(core_implementations.obj) : error LNK2001: unresolved external symbol __imp__CrtDbgReport
[P:\Desktop\flutter_test\namer_app\build\windows\x64\runner\namer_app.vcxproj]
[   +1 ms]   flutter_wrapper_app.lib(standard_codec.obj) : error LNK2001: unresolved external symbol __imp__CrtDbgReport
[P:\Desktop\flutter_test\namer_app\build\windows\x64\runner\namer_app.vcxproj]
[   +1 ms]   flutter_window.obj : error LNK2001: unresolved external symbol __imp__CrtDbgReport
[P:\Desktop\flutter_test\namer_app\build\windows\x64\runner\namer_app.vcxproj]
[   +1 ms]   main.obj : error LNK2001: unresolved external symbol __imp__CrtDbgReport
[P:\Desktop\flutter_test\namer_app\build\windows\x64\runner\namer_app.vcxproj]
[   +1 ms]   utils.obj : error LNK2001: unresolved external symbol __imp__CrtDbgReport
[P:\Desktop\flutter_test\namer_app\build\windows\x64\runner\namer_app.vcxproj]
[   +1 ms]   flutter_wrapper_app.lib(flutter_engine.obj) : error LNK2001: unresolved external symbol __imp__CrtDbgReport
[P:\Desktop\flutter_test\namer_app\build\windows\x64\runner\namer_app.vcxproj]
[   +1 ms]   P:\Desktop\flutter_test\namer_app\build\windows\x64\runner\Debug\namer_app.exe : fatal error LNK1120: 2 unresolved
externals [P:\Desktop\flutter_test\namer_app\build\windows\x64\runner\namer_app.vcxproj]
[   +1 ms]     0 Warning(s)
[        ]     13 Error(s)
[        ] Time Elapsed 00:00:10.15
[  +13 ms] Building Windows application... (completed in 11.7s)
[+1646 ms] Error: Build process failed.
[   +1 ms] "flutter run" took 26,685ms.
[   +2 ms]
#0      throwToolExit (package:flutter_tools/src/base/common.dart:10:3)
#1      RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:815:9)

#2      FlutterCommand.run. (package:flutter_tools/src/runner/flutter_command.dart:1389:27)

#3      AppContext.run. (package:flutter_tools/src/base/context.dart:153:19)

#4      CommandRunner.runCommand (package:args/command_runner.dart:212:13)

#5      FlutterCommandRunner.runCommand.
(package:flutter_tools/src/runner/flutter_command_runner.dart:355:9)

#6      AppContext.run. (package:flutter_tools/src/base/context.dart:153:19)

#7      FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:295:5)

#8      run.. (package:flutter_tools/runner.dart:119:9)

#9      AppContext.run. (package:flutter_tools/src/base/context.dart:153:19)

#10     main (package:flutter_tools/executable.dart:90:3)

[  +18 ms] ensureAnalyticsSent: 16ms
[        ] Running 1 shutdown hook
[   +6 ms] Shutdown hooks complete
[   +1 ms] exiting with code 1

I also checked this on a project in a different drive (my Flutter installation directory at C whilst the project is located at D) but can't see the issue. The Windows app can build and run normally. I'm also on Windows 11 (Version 10.0.22631.2861).
Could you please follow Compiling with Visual Studio to see if there is any other error message to investigate this further?

There are other error messages !
Maybe I should explain that I have two SSD drives on my pc,  C: and P:
I used the Windows OS file "properties/location" feature to change the location of my user account desktop folder to P:/desktop. I did this when I first got this windows 11 box, about a year ago. But, I've relocated my desktop to an alternate drive for as long as Windows has had this feature.
I opened the 'compiling with Visual Studio' link you sent me.  I entered the flutter build windows command from the terminal window in VScode
Here is the transcript of the command I entered, and the errors that followed.
PS P:\Desktop\flutter_test\namer_app> flutter build windows
C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(166,5): error MSB3073: The command "setlocal [P:\Desktop\flutter_test\namer_app\build\windows\x64\INSTALL.vcxproj]
C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(166,5): error MSB3073: "C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin\cmake.exe" -DBUILD_TYPE=Release -P cmake_install.cmake [P:\Desktop\flutter_test\namer_app\build\windows\x64\INSTALL.vcxproj]
C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(166,5): error MSB3073: if %errorlevel% neq 0 goto :cmEnd [P:\Desktop\flutter_test\namer_app\build\windows\x64\INSTALL.vcxproj]
C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(166,5): error MSB3073: :cmEnd [P:\Desktop\flutter_test\namer_app\build\windows\x64\INSTALL.vcxproj]
C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(166,5): error MSB3073: endlocal & call :cmErrorLevel %errorlevel% & goto :cmDone [P:\Desktop\flutter_test\namer_app\build\windows\x64\INSTALL.vcxproj]
C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(166,5): error MSB3073: :cmErrorLevel [P:\Desktop\flutter_test\namer_app\build\windows\x64\INSTALL.vcxproj]
C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(166,5): error MSB3073: exit /b %1 [P:\Desktop\flutter_test\namer_app\build\windows\x64\INSTALL.vcxproj]
C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(166,5): error MSB3073: :cmDone [P:\Desktop\flutter_test\namer_app\build\windows\x64\INSTALL.vcxproj]
C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(166,5): error MSB3073: if %errorlevel% neq 0 goto :VCEnd [P:\Desktop\flutter_test\namer_app\build\windows\x64\INSTALL.vcxproj]
C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(166,5): error MSB3073: :VCEnd" exited with code 1. [P:\Desktop\flutter_test\namer_app\build\windows\x64\INSTALL.vcxproj]
Building Windows application...                                    32.7s
Build process failed.
PS P:\Desktop\flutter_test\namer_app>

Thanks for the update.

I used the Windows OS file "properties/location" feature to change the location of my user account desktop folder to P:/desktop. I did this when I first got this windows 11 box, about a year ago. But, I've relocated my desktop to an alternate drive for as long as Windows has had this feature.

So, per my understanding, your Flutter SDK is located at drive C (on the first SSD) while your Flutter project is located at drive P (on the second SSD). Could you check what the file system of these SSD? (NTFS, FAT32/exFA) (somewhat related case at https://github.com/flutter/flutter/issues/76668).
Also, could you check if .NET has been enabled as well? (see https://github.com/flutter/flutter/issues/98204#issuecomment-1036056244)

Both drives are NTFS. On my computer, P: is drive 0, and C: is drive 1.
My control panel says parts of .NET framework 3.5 and .NET framework 4.8 advanced services are enabled.  My flutter SDK is working fine now with project files on C: ... does that give you any indication if I have the parts of .NET that I need enabled?
Yes, the Flutter SDK is on C:, and this project file is on P: ... However, when I created the project, the flutter SDK was on P: as well.
As part of debugging this problem, and suspecting my C: P: setup, I uninstalled VSCode and Flutter SDK, and reinstalled both of them to C:
It just occurred to me now that the project files left over from my initial set up on P: might not build because the flutter SDK has been removed and reinstalled on C:  -- can you comment on this?  I could create a new project on P: and test this if you want me to.

My flutter SDK is working fine now with project files on C: ... does that give you any indication if I have the parts of .NET that I need enabled?

Ah, you are right, I forgot this. .NET doesn't relate to this issue.

I could create a new project on P: and test this if you want me to.

It could be helpful to do that. Please try and provide concrete steps to reproduce the issue on your end. Thanks!

Alright, I did that, and I have no error messages to report.
Flutter built the tester app for windows from a new project folder on P: and it worked as expected.
Possibly, the original issue I reported occurred because Flutter SDK was installed on P:, but if it's okay with you, can we close this bug report?  I don't really want to rebuild that initial setup I had again.
I hope I didn't waste too much of your time due to my incomplete "steps to reproduce".
regards/peter

Thanks for checking that. I think this can be closed. If you have this issue next time, please write in the comments and I will re-open this to investigate this further.


Update README.md

I think we can keep this PR so if any new changes come up we don't have to create new branch then approve it and so on and so on 😅


#297 Fix for: Getting error in CentOS when building middleman

This is to address question #297

I don't understand this PR...  It appears to be against the wrong base branch, and why delete Gemfile.lock?

@bronson since people fork Slate and expect it to work properly, we ask that PRs are submitted against dev.

@gianebao So sorry about the slow reply. I don't think the new version of middleman in the dev branch uses multi_json, do you think you could check to see if it works now?
I'm going to close this and the issue since I think it should have fixed itself, but please feel free to reopen if you're still having a problem! I appreciate the contribution.


Move form name question to be the first one

Also the page has a different copy and an additional checkbox, which has to be checked if the form name is blank.
Copy review is pending.

Looks good 👍

JS looks fine - nice and tidy. 👍 😄


Does not work at all

I tried the example from the Readme, create a simple HTML file and paste the code. it did not work, only echo i could hear.
`

`

This seems to get fixed bt #14. @foobar404, pls merge!

This seems to get fixed bt #14. @foobar404, pls merge!

Not sure if this is a valid Issue.  Is so the <canvas id="output" ...> is missing. If you just didn't share that part; did you ensure you're not getting stuck on a CORB-related issue by importing the script directly from github? Any hints left in your browser console?

@jbmyid Do you still encounter the issue with #14? If it's solved, please feel free to close it.

Does this work? Stream doesn't work for me

It looks like the CDN was caching an older version of the repo, I have updated everything, there shouldn't be any issues now.


Complex number arithmetics

In the
https://numbas.mathcentre.ac.uk/question/11785/arithmetics-of-complex-numbers-ii/
part A seem to be bugged in some cases:
for 4i*(-7+7i) revealed answer is -28 - - 28i, and the correct answer is not accepted.

Thanks for reporting this. It was fixed in commit 29e98f4717b7fe62feaa2828ab48a8669e4e1019


Location to Restful backend

The calls to backend URL is successful.  But how do I obtain the location json in the backend. We use java for backend.
Consider this php example :
<?php
	$data = file_get_contents('php://input');
	echo $data;
        echo JSON_decode($data, true);
?>

This file is hosted at : http://www.madzz.co.in/loc.php
the url in my options is set the the above value.
Can someone please help me how do I obtain the location json posted to this url. When I run my app I do get all the beep sounds and toast notifications.

Any answers for this?

You could try inspecting the raw http request to observe the nature of the
data sent.
Since you understand Java, you should have no problem understanding the
nature of the HTTP POST.
https://github.com/christocracy/cordova-plugin-background-geolocation/blob/master/src/android/LocationUpdateService.java#L654
The entire request body IS the JSON.
http://stackoverflow.com/questions/5999359/how-to-add-json-to-the-body-of-an-http-post-in-java
On Tue, Jan 13, 2015 at 12:16 AM, SiddharthaRRamesh <
<EMAIL_ADDRESS>wrote:

Any answers for this?
—
Reply to this email directly or view it on GitHub
https://github.com/christocracy/cordova-plugin-background-geolocation/issues/127#issuecomment-69696821
.

--
Chris Scott
Transistor Software http://www.transistorsoft.com

So, what you are saying is whenever the app makes that beep sounds, it will add the json to the body of the url listed?

An url does not have a body.
An HTTP Request HAS_A body.
An HTTP Request HAS_A url.
when you hear beep, that means “I recorded a GeoLocation” and stored the
location in a Queue within plugin.
If your device happens to have a network connection at that point in time,
the Queue will be synced to your configured url, one location-at-a-time.
The nature of the HTTP POST is Content-Type: application/json
Why don’t you keep an eye on the request log of your HTTP server and see
the exact data it receives?
On Tue, Jan 13, 2015 at 12:36 AM, SiddharthaRRamesh <
<EMAIL_ADDRESS>wrote:

So, what you are saying is whenever the app makes that beep sounds, it
will add the json to the body of the url listed?
—
Reply to this email directly or view it on GitHub
https://github.com/christocracy/cordova-plugin-background-geolocation/issues/127#issuecomment-69697995
.

--
Chris Scott
Transistor Software http://www.transistorsoft.com

I know that I typed it in the wrong way I guess !
I am looking at the log, all it does it log the url that the application calls. Thats it.
So the request which is a post request is being sent. But I am not able to get any data from the request body. Why is that happening?

Your question is “In Java, how do retrieve the raw JSON body of an HTTP
response”.
The data is there, it’s up to you fetch it.  I’m not concerned with how any
particular platform retrieves the data data, be it PHP, Java, C# or Ruby.
On Tue, Jan 13, 2015 at 12:59 AM, SiddharthaRRamesh <
<EMAIL_ADDRESS>wrote:

I know that I typed it in the wrong way I guess !
I am looking at the log, all it does it log the url that the application
calls. Thats it.
So the request which is a post request is being sent. But I am not able to
get any data from the request body. Why is that happening?
—
Reply to this email directly or view it on GitHub
https://github.com/christocracy/cordova-plugin-background-geolocation/issues/127#issuecomment-69699371
.

--
Chris Scott
Transistor Software http://www.transistorsoft.com

Ok! Calm  down.

I’m calm as a clam.
On Tue, Jan 13, 2015 at 1:07 AM, SiddharthaRRamesh<EMAIL_ADDRESS>
wrote:

Ok! Calm down.
—
Reply to this email directly or view it on GitHub
https://github.com/christocracy/cordova-plugin-background-geolocation/issues/127#issuecomment-69699813
.

--
Chris Scott
Transistor Software http://www.transistorsoft.com

Ok i figured it out. Thanks for your guidance.
On Jan 13, 2015 11:39 AM, "Chris Scott"<EMAIL_ADDRESS>wrote:

I’m calm as a clam.
On Tue, Jan 13, 2015 at 1:07 AM, SiddharthaRRamesh <
<EMAIL_ADDRESS>
wrote:

Ok! Calm down.
—
Reply to this email directly or view it on GitHub
<
https://github.com/christocracy/cordova-plugin-background-geolocation/issues/127#issuecomment-69699813>

.

--
Chris Scott
Transistor Software http://www.transistorsoft.com
—
Reply to this email directly or view it on GitHub
https://github.com/christocracy/cordova-plugin-background-geolocation/issues/127#issuecomment-69699901
.

Android has been refactored.

significant improvement to battery performance.
plugin no longer does HTTP -- calls javascript callback, just like ios.

http://christocracy.github.io/cordova-background-geolocation/


Enabling Image cropper widget use in CS3D

Context

Changes & Results

Testing

Checklist
PR

[] My Pull Request title is descriptive, accurate and follows the
semantic-release format and guidelines.

Code

[] My code has been well-documented (function documentation, inline comments,
etc.)

[] I have run the yarn build:update-api to update the API documentation, and have
committed the changes to this PR. (Read more here https://www.cornerstonejs.org/docs/contribute/update-api)

Public Documentation Updates

[] The documentation page has been updated as necessary for any public API
additions or removals.

Tested Environment

[] "OS:
[] "Node version:
[] "Browser:

Closed as this repo will be updated with OSS


[DOC] Write local documentation developer guide.

Write steps to build documentation locally.

Mind if i make changes to this? Quite a bit that can be improved on this page IMO.

@MatthewMiddlehurst Yes sure, were you able to build the docs?

@MatthewMiddlehurst  Oh, Okay! I build my docs in the way I wrote and have written this as per my experience. However, if this works, it would be much simpler. :))

Could you please edit accordingly?

absorbed into #2297. Includes your commit so you should still get credit

@all-contributors add @aadya940 for docs


Bug: event name casing is not standard

emit event name "slideClick" - this violates the event naming convention
72:          this.$emit("slideClick", Object.assign({}, e.currentTarget.dataset));
I propose to replace the name of the event "slideClick" with "slideclick"
P.S.Thanks for the interesting gallery !!!

Hey @stokaboka, good catch I'll switch this to a bug report

Hi @quinnlangille
I just started using VueCarousel in a personal project and really love it - thanks very much for the great work!
I was reading the issues and had a quick dive into this one. I see that @stokaboka already submitted a merged PR to change slideClick to slideclick.
With regard to your second point, I did an audit on the code and found three other events that are still formatted in camelCase, namely:

pageChange
transitionStart
transitionEnd

So these would have to be changed as well. Vue's Event Names documentation recommends that events should be in kebab-case; i.e:

page-change
transition-start
transition-end

But this is inconsistent with the other existing lowercased events navigationclick, paginationclick and slideclick.
Therefore I guess it might be more prudent to change events in camelCase events to lowercase:

pagechange
transitionstart
transitionend

Let me know if that's your preference and I can submit a PR!

As an aside, I think some of the events are not documented, but I haven't checked if someone else has opened another issue or PR for this.

Hey @darraghenright, thanks for taking on the issue! I would be fine with non-hyphenated (pagechange vs page-change) but, if you'd like to migrate all events to hyphenated versions feel free. I think meeting the vue style guide is a direction we should be taking. It would be good to maintain backwards compatibility here if we can!
Let me know if you have any questions :octocat:

Yeah, I'd be happy to migrate all events - definitely seems like a good idea to adhere to the Vue style guide there!
In terms of backward compatibility, do you mean we should leave any existing events as-is, and add the new events, in case there is userland code that depends on the old events?
If so, in Carousel.vue we'd do something like:
currentPage(val) {
  this.$emit("pageChange", val);
  this.$emit("page-change", val);
  this.$emit("input", val);
},

With a view to removing the old event for some future, backwards-incompatible release. Or is that a naive reading of the requirement? 😄

Speaking of backwards compatibility - I was re-reading Vue's event naming recommendations, and there was an implication that I didn't pick up previously: event listeners are case insensitive in DOM templates, which of course means it's not possible to listen to emitted events in camelCase and PascalCase as their lowercase variants would be expected.
However, in string templates, event listeners are case-sensitive. So this could mean that there are users out there successfully listening for emitted events pageChange, transitionStart, transitionEnd etc.
Just wondering now, if there would be unitended consequences in changing the existing camelCase events to lowercase for one specific case. I don't know if many people use DOM templates - I don't but I suspect that it's not uncommon.

Sounds great! :sunglasses: I'll get working on this asap

This has been released in 0.18.0 :octocat: Thanks for the contribution!


added few more points

Mainly around a framework or some legal aspects

@devbh  nice changes, now who should be at this Workshop (who are the key players in this world)


Allow non-interactive install of az cli using script

Is your feature request related to a problem? Please describe.
I'm trying to install the az cli using the script approach (curl -L https://aka.ms/InstallAzureCli | bash) in an automated fashion. Unfortunately, the script prompts for a number of directories with no apparent way to provide those values via command line arguments or environment variables so the script can't run headless.
Describe the solution you'd like
Allow the INSTALL_DIR and BIN_DIR values to be provided either as command line arguments or environment variables.
Alternatively, if the CLI could be downloaded as a single binary instead of a python script that must be initialized that would be great.
Describe alternatives you've considered
Installing via a package manager is not viable in this case because 1) we don't have the necessary permissions on the system and 2) need to support a variety operating systems.
Additional context

Any updates on this? We're actively seeking to integrate this in our CI pipeline, but cannot do so for obvious reasons.

https://aka.ms/InstallAzureCli is deprecated.
If you have the sudo permission,
For DEB, you can use curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash.
For other distros, see https://learn.microsoft.com/en-us/cli/azure/install-azure-cli-linux?branch=live&pivots=dnf
If you don't have the permission, use pip https://github.com/Azure/azure-cli/issues/20476


Refactoring of event handling in wire drawing

This is great! Dropping these classes makes the thing a lot clearer. :+1:


[OneDriveSDK] calling xhr failure callback, status: 401

Category

[ ] Question
[ ] Documentation issue
[x] Bug

Expected or Desired Behavior
Using the OneDrive JS file picker v7.2 should return a share url when an accessToken and endpointHint are provided and when the action is set to share
Observed Behavior
It seems like the SDK is receiving a 401 when making its request. It is logging in the browser console, provided below:
[OneDriveSDK] calling xhr failure callback, status: 401
// redacted XMLHttpRequest object
response: {"error":{"innerError":{"code":"invalidSignature"},"code":"unauthenticated","message":"Token contains invalid signature."}}

[OneDriveSDK] Received ajax error.
{
  "errorCode": "webRequestFailure",
  "message": "HTTP error status: 401"
}

[OneDriveSDK] Failed due to unknown error:
TypeError: Cannot read property 'length' of undefined
    at Object.t.shareItems (OneDrive.js:2)
    at OneDrive.js:2
    at OneDrive.js:10
    at H (OneDrive.js:10)
    at A (OneDrive.js:10)
    at MutationObserver.f (OneDrive.js:10)

Steps to Reproduce
Note: secrets like clientId, accessToken and endpointHint, are provided by the server and are redacted in this sample.

Configure the OneDrive file picker with the following options:

  var onedrive_options = {
    clientId: REDACTED-PROVIDED-FROM-SERVER,
    action: 'share',
    multiSelect: true,
    advanced: {
      accessToken: REDACTED-PROVIDED-FROM-SERVER
      endpointHint: REDACTED-PROVIDED-FROM-SERVER
    },
    success: function(data) {
      console.log(data);
    },
    cancel: function(data) {
      console.log(data);
    },
    error: function(e) {
      console.error(e);
    }
  }
}

For convenience, here's a repo you can clone and run yourself: https://github.com/conradmuan/onedrive-bug-report-repo

Opening the picker works fine but after clicking on a file, the SDK logs the errors listed above.
This happens with OneDrive for business accounts (have not confirmed on personal accounts)

Thank you.
(cc @kevintcoughlin)

@conradmuan thank you for the detailed bug report above and the "repro repo" 😄. I can confirm that when the Picker configuration includes endpointHint that an error is thrown. What's interesting is that if you omit only the endpointHint, sharing succeeds.
We will continue to investigate...

Hi @KevinTCoughlin, glad my repro repo helped out! I wanted to isolate this and make it as easy as possible to repo.
What other additional data points do you require? Happy to provide!

Hi @KevinTCoughlin, glad my repro repo helped out! I wanted to isolate this and make it as easy as possible to repo.
What other additional data points do you require? Happy to provide!

Would you be able to test the following with your consumer account?

Set endpointHint = "api.onedrive.com"
Provide a valid accessToken which you can get from query params after signing-in at https://developer.microsoft.com/en-us/graph/graph-explorer
Select a file to "share"
Does the request 401?
Unset endpointHint from the config options
Repeat file sharing
Does the request 401?

@KevinTCoughlin happy to but would like to clarify something (forgive me for my ignorance here)
Is a consumer account a OneDrive personal (non enterprise?)

@KevinTCoughlin happy to but would like to clarify something (forgive me for my ignorance here)
Is a consumer account a OneDrive personal (non enterprise?)

No worries, and yes it is.

after steps 1-3 done:

Does the request 401?

Unfortunately, yes.

Unset endpointHint from the config options
Repeat file sharing

Interesting note here that's out of scope with this issue but I was prompted login in when the picker popped open. I noticed another issue reported by someone else noting that they experience the same thing even when providing an access token and wanted to note that here (but again it's out of scope for this issue)
However, from here, I'm unable to login in the file picker popped window (see screenshot)

I've confirmed that I've copied the access token in the query string params after signing in with a consumer account at the graph explorer and my SDK options are
clientId: creds.clientId,
action: 'share',
multiSelect: true,
advanced: {
  accessToken: creds.accessToken,
},

Mote the ommitted endpoint hint

Ok, let's shelve consumer for now since its unrelated.
I was able to successfully generate a share URL using the above File Picker configuration with a OneDrive for Business account. Here were my steps:

Register and use application's clientId from https://apps.dev.microsoft.com/.
Set endpointHint to https://${tenantId}-my.sharepoint.com/personal/${username}_${tenantId}_onmicrosoft_com/.
Generated a valid accessToken using a debug tool.

Provided https://${tenantId}-my.sharepoint.com as my Resource URL when generating the token.

Loaded index.html in a clean browser and launched the File Picker.
Logged-in with the same account used in the endpointHint above.
Selected a file and clicked "Open".
The response payload was successfully logged to console on the host index.html page.
The payload contained a share webUrl which I then used to access the shared document.

@conradmuan, am I testing the wrong scenario? If not, perhaps there is something incorrect with the endpointHint provided OR the "Resource URL" used for generating the accessToken?
I imagine given the 401 that it is related to the accessToken used.

@conradmuan any update from your end on the above?

sorry @KevinTCoughlin, I am a bit behind. I'm going to try reproing what you provided in shortly.
One thing to note is that we query for the user's endpoint using https://graph.microsoft.com/v1.0/me?$select=mySite on the backend when they auth.
I'm unsure if I get back a mySite from enterprise customers in the form of https://${tenantId}-my.sharepoint.com/personal/${username}_${tenantId}_onmicrosoft_com/ so I'll double check that as well on my end (just a thought, i'm unsure if that's related)
I'll get back to you shortly. Sorry for the delay

Good to know re: mySite! We've had some edge cases with that call related to auth which the back-end is working to address. I would be interested to know whether or not you can fetch or construct that tenant URL or if there is work on our end required.

Hi @KevinTCoughlin sorry for the delay,
I must have missed step 3 when I was reading through the response:

Generated a valid accessToken using a debug tool.

Provided https://${tenantId}-my.sharepoint.com as my Resource URL when generating the token.

did you want me to register a new app and oauth a new accessToken?
If I used an existing accessToken with an existing registered app (Slack), I get a 404 FILE NOT FOUND in the popup window, where endpointHint was https://${tenantId}-my.sharepoint.com/personal/${username}_${tenantId}_onmicrosoft_com/ but I'm actually guessing tenantId and username as my company's name and my username being derived from my email.
Sorry for this back and forth. I'd like to see what you're seeing so if you can tell me:

did you want me to register a new app (new client id)
do an oauth exchange with whatever script I want to get fresh accessToken
Can you explain what this means: Provided https://${tenantId}-my.sharepoint.com as my Resource URL when generating the token.

I have to admit that #3 is curious to me and I think I'm missing something here. What we're doing is a  typical oauth flow on the backend: client id, secret and code being exchanged in a POST to https://login.microsoftonline.com/common/oauth2/v2.0/token and then redirected back to a registered redirect uri. At what point am I supposed to be providing a resource URL?
Sorry for all these questions and the delay!

@etyp @Penspinner see my response in https://github.com/OneDrive/onedrive-api-docs/issues/943#issuecomment-469916583 re: accessToken usage.
I debugged the issue @conradmuan faced and it was due to the accessToken being invalid for the tenant supplied via endpointHint. I'd like to close this issue soon.
Perhaps we can have the accessToken conversation in the above linked issue?
If you are still facing issues unrelated to accessToken bypassing auth, please raise issues separately so I can triage and debug.

@Penspinner re: your analysis of the endpointHint logic, you may be onto something which we'll be in a better position to collaborate and fix soon. The accessToken will still only bypass the SDK wrapper, see above linked comment.

Understood, thanks @KevinTCoughlin -- we'll make sure our customers are aware of the need to double sign in for now. We might even remove the oAuth connection to avoid confusion and the auto closing issue above.
Thanks again for the update

@KevinTCoughlin Thanks for responding.

I debugged the issue @conradmuan faced and it was due to the accessToken being invalid for the tenant supplied via endpointHint.

What do you mean by invalid for the tenant supplied? Should it work if the access token was created with common as a tenant?
https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-oauth2-auth-code-flow#request-an-access-token

What do you mean by invalid for the tenant supplied? Should it work if the access token was created with common as a tenant?

The access token that was being used was for Microsoft Graph not for the tenant it was trying to authenticate against IIRC.
I don't know re: common as a tenant. At the end of the day, you can't bypass authentication today by providing an accessToken.
It only bypasses the round of authentication that the Picker OAuth application does if any.
The framed page will still request authentication if state isn't already stored as a cookie.

Is there any update here?

I'm testing it with a MS personal account
using action: 'share'
providing a valid access token (I tested calling the graph API using Postman).
endpointHint: 'api.onedrive.com'

Everything seems to be working fine, but when I select the file, I still got the 401 error when the file picker perform the API request to get the shareable link.

Here are my findings in the hope that this can be resolved:
This issue is not restricted to the share action alone. I am getting the same issues using the download action. The query action works and returns an object with file details as expected. Using the query action I have noted that the accessToken property is not required. If its not there you are required to authenticate via the popup. If you have a token you are passed through to the endpointHint as expected.
The issue lies when using download or share. If I remove the accessToken property using the  download or share action, I receive:

[OneDriveSDK] Failed due to unknown error

So therefore accessToken is required if using the endpointHint with the download or share action. Using the same process of handing over an accessToken I tested with the query action, if we were to use the download or share action we get the dreaded 401 error back when selecting a document.
The only solution at the moment seems to be not using the endpointHint property in the options (not ideal). Therefore, by default you end up in your OneDrive for Business document store e.g. https://contoso-my.sharepoint.com/personal/foo_contoso_onmicrosoft_com/ (if you select a file here an object with file details is returned to your app as expected) and if you are able to navigate to the sharepoint site or document library required (therefore, don't disable navigation you will get an error). In this scenario you are able to select a file and those details are returned to your app with no errors.
Obviously these findings are related to my requirements of opening the popup at a specific sites document library/store. In an ideal world I would like to disable the navigation sidebar and select the columns disabled.

As part of a repository clean up effort we are closing older issues. If this issue remains, please: open a new issue, reference this issue, and provide any additional details that may help in resolution. Thank you for your understanding as we work to improve our responsiveness.


Added basic template for project1

The template added some basic filters for the feature detection project
Closes #1

Basic template created.


feat: floxEnv: enforce unique packages

Don't allow multiple packages to install the same set of store paths
The only time I can think of it being desirable to have two different references to the same package would be:
floxEnv 1:
nixpkgs-flox.hello = {};
floxEnv 2:
curated-nixpkgs-flox.hello = {};
These two floxEnvs could not be composed.
On the other hand, there are times when it would be confusing to users to have multiple copies of the same package

This is the floxEnv implementation of https://github.com/flox/flox-internal/pull/353
I'm not actually 100% confident this is an improvement - are there many times when it would be confusing for users to have multiple copies of the same package by a different name?

@limeytexan do you agree this should be an error? I think the behavior of flox install will change as in https://github.com/flox/flox-internal/pull/363/commits/8e7caae1fa231b0e043e8862a094d1ec93bab7ce

Don't allow multiple packages to install the same set of store paths
The only time I can think of it being desirable to have two different references to the same package would be:
floxEnv 1: nixpkgs-flox.hello = {};
floxEnv 2: curated-nixpkgs-flox.hello = {};
These two floxEnvs could not be composed.
On the other hand, there are times when it would be confusing to users to have multiple copies of the same package

There will also be times when you have different packages that collide with each other AND are not identical. Eg: moreutils and gnuparallel. This is where traditional profiles use a priority scheme. I’ve often wanted to have both to have sponge and the better parallel. So we might want to expose priority. Again, not critical today.

@limeytexan do you agree this should be an error? I think the behavior of flox install will change as in flox/flox-internal@8e7caae

Something that someone might be trying to say with installing the same package is to change the “originalUrl”. Imaging they already installed hello.2_12. Then they install hello. This likely means they want to replace the version-specific one with a version agnostic one. Or we make them uninstall, reinstall. These cases would be helped by showing the user what outcome their commands are having…. perhaps with a wink diff.

So we might want to expose priority.

We must expose priority. Let's create a test for that and make sure both implementations support it.

These cases would be helped by showing the user what outcome their commands are having…. perhaps with a wink diff.

Sure with exceptions like this it could be helpful to display a diff of the declarative formats and prompt for confirmation. In that case the diff adds clarity to the context of a dispute that is already needing to take place. It's displaying it at all times without explicitly asking for it by way of an env variable or option that would be noisy and undoubtedly attract complaints.

@limeytexan do you agree this should be an error? I think the behavior of flox install will change as in https://github.com/flox/flox-internal/pull/363/commits/8e7caae1fa231b0e043e8862a094d1ec93bab7ce

Thanks for asking; I'm not sure yet. This is where we get into the realm of multiple action flags; floxpm allowed you to "install foo --remove bar" to replace one package with another in one atomic step. I never liked the combination of subcommand and flag to implement what was essentially two subcommands implemented in a single transaction but the functionality was widely used.
In an interactive terminal I expect a good experience here would be to detect duplicates and present the user with a sorted list of just the conflicting packages, inviting them to select which package(s) to keep/discard and in what order of precedence. (Remember you can have collisions with any number of packages.)
The implementation might be a bit tricky because we would need to remember that a package had been involved in a ranking exercise previously and only complain when packages clash that had not previously been compared with each other. In that regard the priority number used in nix profile and nix-env is overly simplistic and fatally flawed; a more correct implementation would be to maintain arrays of the results of former comparisons, e.g. for each collision you record an ordered list of just those names that are permitted to collide in future and if a new package gets involved in a collision that isn't expressly mentioned in the list then that's when we decide to display the interactive prompt, or in a non-interactive terminal throw an error. There should also be a way to set the precedence in a non interactive terminal with option flags but I haven't thought about what that might look like.

I think the conversation may have strayed from the original point of this PR.
The key consideration is this:

it may well be that at a given point in time {stable,staging,unstable}.nixpkgs.hello refer to the same exact package, but
it is essential that users have the opportunity to choose between these options, not because it makes a difference on "day 1", but
because it provides the opportunity to configure environments using different stabilities, and to test the effect of upcoming nixpkgs snapshots in "unstable" and "staging" before it advances to "stable".

I don't understand the inner workings of the patch, but I fear this may prevent the ability to select between {stable,staging,unstable}.nixpkgs.hello when all three of these map to the same package?

i'm missing the nuance of some of this, but why can't these be composed @mkenigs ? I'd expect the behavior of composition to be something like, "the order of composition matters", i.e. whatever the last env passed on the CLI overrides other package versions if they exist. We should provide a note when that occurs.
I'll also note that these mechanics may be more clear to the user if we provided the version numbers in the flox list (#388).

Okay a lot of concerns raised here. I'll try to address them all but yeah I think some of them are
off topic.

More general collisions:

There will also be times when you have different packages that collide with each other AND are not identical. Eg: moreutils and gnuparallel.

We must address the issue of collisions and add a test for it. See my later comment below.

In an interactive terminal I expect a good experience here would be to detect duplicates and present the user with a sorted list of just the conflicting packages, inviting them to select which package(s) to keep/discard and in what order of precedence. (Remember you can have collisions with any number of packages.)

This PR is about identical sets of store paths, not more general collisions. This won't even error if one package installs [ out man ] and another installs [ out lib ], even though the out derivations will be identical. I suppose we could drop this PR in favor of more general handling of collisions, but that wasn't my original intent. My original intent was simply to re-implement https://github.com/flox/flox-internal/pull/353

This likely means they want to replace the version-specific one with a version agnostic one

I think that's a separate issue. That's more of a "what do users mean by flox install hello" kind of question than a "should they be allowed to have hello and hello.2_12 at the same time." In your example they don't want both

diffs - NA

I don't understand the inner workings of the patch, but I am concerned it may take away the ability to select between {stable,staging,unstable}.nixpkgs.hello when all three of these map to the same package?

It takes away the ability have both e.g. stable and unstable hello in the same environment. I'm n
ot sure when having both would be desirable?

i'm missing the nuance of some of this, but why can't these be composed @mkenigs ? I'd expect the behavior of composition to be something like, "the order of composition matters", i.e. whatever the last env passed on the CLI overrides other package versions if they exist. We should provide a note when that occurs.

We could still do that kind of composition (build two separate floxEnvs, but give one higher precedence in PATH). We couldn't do source composition, i.e. merge two separate flox.nix files and build a single floxEnv (this patch will throw an error if it finds two identical packages)


Great work! will you consider open source?

Thanks for your interesting in our work, we are now working on it. Stay tuned！


Cannot read property 'length' of undefined

Issue Id: 5f37060d-2015-46bd-b152-f68a02aee705Versions - 1.10.2Stack TypeError: Cannot read property 'length' of undefined/vs/base/common/strings.ts#L369:14 (length)/vs/workbench/parts/debug/browser/debugActionsWidget.ts#L213:38 (equalsIgnoreCase)/vs/workbench/parts/debug/browser/debugActionsWidget.ts#L164:23 (getActions)/vs/workbench/parts/debug/browser/debugActionsWidget.ts#L90:8 (update)/vs/base/common/callbackList.ts#L63:26 (apply)/vs/base/common/event.ts#L118:26 (call)/vs/workbench/parts/debug/electron-browser/debugService.ts#L456:25 (fire)/vs/workbench/parts/debug/electron-browser/debugService.ts#L262:8 (setStateAndEmit)/vs/base/common/callbackList.ts#L63:26 (apply)/vs/base/common/event.ts#L118:26 (call)

Fixed via 82d5d43


Optional Properties was broken

It was worked  in 1.0.9 , but broken in 1.2.3 .
export const stackProps = z
    .object({
        direction: Direction.optional(),
        horizontalAlign: Alignment.optional(),
        verticalAlign: Alignment.optional(),
        wrap: z.boolean().optional(),
        grow: z.boolean().optional(),
        shrink: z.boolean().optional(),
    })

type PropType = z.TypeOf<typeof stackProps>

Hm, can't replicate this. I assume Direction and Alignment are enums? Can you share that code with me as well? Also what version of TS are you using?

tag: @tuoxiansp

Hm, can't replicate this. I assume Direction and Alignment are enums? Can you share that code with me as well? Also what version of TS are you using?

https://github.com/tuoxiansp/mould/blob/fix-type/components/List.tsx
At 'fix-type' branch, you can see type errors. It' OK in master.
I find some difference of _def between this two versions :

sample code: https://runkit.com/embed/74a5qve0qc61

Should be fixed in 1.2.4 - not sure how that got past my tests :/
Sorry about that!

Thanks for your awesome work!


Passing extra params with login method

Hi,
I have just moved from a different react oidc package to this one, going great so far. I wondered if there was a requirement to be able to pass extra params at login also? it's a requirement I'm looking at currently as used it previously. Like how you can via the configuration, but more dynamic so it can be changed per user. I have checked the following:
/packages/context/src/oidc/vanilla)/oidc.ts
and it would look something like this:
async loginAsync(callbackPath:string=undefined, extras?:StringMap, installServiceWorker=true) {
Then combined this StringMap with the one from the config and then pass to the authRequest.
Is this something you would be able to add? otherwise I might try to implement it myself and see if I can request it be pulled into the source code. But I'm not sure if there is anything else of concern I should consider first.
Thanks Carl

Hi @mrcarl79 , thank you for your issue. It seems to me to be definitly a very nice feature too add !

Hi @mrcarl79 , thank you for your issue. It seems to me to be definitly a very nice feature too add !

Great, I have managed to add this feature locally and tested and got it to work for my requirements. However I'm not sure if what I have coded could affect other areas. I have not contributed to this project yet, but happy to submit a PR of what I changed so you can see. It's fairly simple, if you want to implement what I have tried you are welcome or change it if there was a better way. Thanks Carl

will #753 respond to your need?

will #753 respond to your need?

@guillaume-chervet Yes that looks great, looking forward to testing the new feature :) thanks

@mrcarl79 ,
I have published it. does it respond to your need?

I close the issue, I think it is ok !
Thank you very much for the issue. Feel free to re-open it if you need.


'serialport' close event is not working properly

SerialPort Version: 4.0.7

NodeJS Version: v4.4.4

Operating System and Hardware Platform: Linux on RaspberryPI

Have you checked the right version of the api docs?: Yes

Are you having trouble installing and you checked the Installation Special Cases docs? No

Are you using Electron and have you checked the Electron Docs?: No

Summary of Problem
Disconnect or close event does not work properly !!

close event is not trigerred
application is working fine there after

Even tried using usb-detection npm package, no luck !!
Steps and Code to Reproduce the Issue
Simple NodeJS application with open, close, error and data event functions is enough to reproduce the issue.
var serialport = require("serialport");
serialport.on("open", showPortOpen);
serialport.on("data", initData);
serialport.on("close", showPortClose);
serialport.on("error", showError);
function showPortClose() {
console.log("USB Connection Lost: ");
}
function showError(error) {
console.log("Serial port error: " + error);
}
function showPortOpen() {
console.log("USB Port Succesfully Opened");
}

Do we need to read or write functionality to detect removal? If not, how are going to detect the close event? Let me know.
Thank you in advance,
Gautham

Have you tried with node-serialport version 6.x.x?

No i haven't tried serialport version 6.x.x. Will definitely try and get back.
Do you want me to try any specific version? If so, please let me know the version because there is already an issue reported with 6.x.x version.

https://github.com/node-serialport/node-serialport/issues/1465

serialport v6.0.5 does not have a serialport.list() API for UNIX/Linux?
serialport.list(function(err, ports) {
ports.forEach(function(port) {

Hi @reconbot,
Using below source code but unable to parse incoming data on "data" event. Let me know if I am missing something
var serialport = require('serialport');
var portName = process.argv[2];
var myPort = new serialport(portName, {
baudRate: 9600,
parser: new serialport.parsers.Readline('\r\n')
});
myPort.on('open', onOpen);
myPort.on('data', onData);


docs: add higress-core.gateway.kind configurations docs

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


Update GitHub Actions

Soon, GitHub will deprecate the upload-artifacts v3 action:
https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
This PR updates the action to the latest version, v4.
It also updates the checkout action to the latest version, v4, as well.

The build-tests are failing here, probably because of a CI issue  (which was languishing in the PR queue for 'develop'); I have merged the CI fix, and now duplicated this present PR (#5 )  but for develop (as #6 ). The build-test for the latter is running, and after merging it we can pull 'develop' into 'main'.

I approved #6 so I think you were right about the CI!


Added temporal use cases and handle async responses from Drools

Added time constraints in rules schema
Allow for async communication between Drools and Python
Added

Throttle support via
1. once_within
2. once_after
Time windows for conditions
timeout: nnn seconds
Not all conditions met in a time window

   condition:
             not_all:
                 - condition1
                 - condition2
             timeout: nnn seconds

https://issues.redhat.com/browse/AAP-7354
https://issues.redhat.com/browse/AAP-7360
https://issues.redhat.com/browse/AAP-7284
https://issues.redhat.com/browse/AAP-7706

@Alex-Izquierdo I am not content with the timed_out name either we need to discuss it further and come up with a good name maybe expired. I am trying to add documentation in the JIRA stories once we finalize the names we can make changes to the rst files.

@Alex-Izquierdo I am not sure about the RUN_PLAYBOOK_MAX_DELAY use case @bzwei might have more knowledge about it. In this use cases the time values are configurable per rule instead of globally and they are not specific to any action. The rule engine doesn't know if the action is a run playbook or run module. The unique attributes in the once_within use case allows the author to use specific attributes to make unique sets of events within the time window. For the once_within the event is fired right away and then it would suppress events till the time window expires. It doesn't wait till the once_within time window expires and then trigger the event. The once_within currently only supports 1 condition it doesn't work with multiple conditions we have ongoing discussions with the Drools team to extend this feature as we can come up with more use cases.

@Alex-Izquierdo Changed unique_attributes to group_by_attributes

The once_within use case fires the event immediately and suppress other similar events. RUN_PLAYBOOK_MAX_DELAY use case on the contrary holds the running of a playbook for a while to see whether there are other requests to run the same playbook on different hosts, if yes, then run the playbook only one time but on all selected hosts.
The once_within use case is mainly for easing event storms. The RUN_PLAYBOOK_MAX_DELAY use case is not necessary for event storms.

@Alex-Izquierdo I am not sure about the RUN_PLAYBOOK_MAX_DELAY use case @bzwei might have more knowledge about it. In this use cases the time values are configurable per rule instead of globally and they are not specific to any action. The rule engine doesn't know if the action is a run playbook or run module. The unique attributes in the once_within use case allows the author to use specific attributes to make unique sets of events within the time window. For the once_within the event is fired right away and then it would suppress events till the time window expires. It doesn't wait till the once_within time window expires and then trigger the event. The once_within currently only supports 1 condition it doesn't work with multiple conditions we have ongoing discussions with the Drools team to extend this feature as we can come up with more use cases.

@Alex-Izquierdo @ttuffin Please review this has all the changes that we discussed about 2 weeks back in the dev sync.

@Alex-Izquierdo The examples now have a marker called temporal so they can be skipped if necessary. Most of the clock manipulation to speed tests happen in drools_jpy like here https://github.com/ansible/drools_jpy/blob/2406ad6b2776d0df3b5965a9f7f99b17babff23b/tests/test_ruleset.py#L548. In our examples we can't move the clock forward so these are real working examples to demonstrate the product features.

@Alex-Izquierdo @ttuffin Please re-review I have made the necessary changes


Error "Unrecognized font family 'Material Design Icons'"

Error: "Unrecognized font family 'Material Design Icons'" in iOS application. I'm using Xcode Simulator v11.5 and react-native-vector-icons: v6.6.0
Steps:
npm start
npm run ios:dev

Thank you for your time!

Solved! Removing the app from the device and running it again it works!

Removing the app from the device, result same error, but with another font type. :(


fix ped bugs

closes #208 #186 #183 #161 #146

Codecov Report

Merging #214 (732105a) into master (0599b2c) will decrease coverage by 0.05%.
The diff coverage is 57.14%.

@@             Coverage Diff              @@
##             master     #214      +/-   ##
============================================
- Coverage     68.44%   68.39%   -0.06%
  Complexity      747      747
============================================
  Files           116      116
  Lines          2377     2379       +2
  Branches        278      279       +1
============================================
  Hits           1627     1627
- Misses          636      637       +1
- Partials        114      115       +1

Impacted Files
Coverage Δ

.../java/seedu/address/logic/commands/AddCommand.java
76.47% <ø> (ø)

...el/person/exceptions/DuplicateModuleException.java
0.00% <0.00%> (ø)

...address/logic/commands/SetDefaultGroupCommand.java
75.86% <50.00%> (-5.62%)
:arrow_down:

...el/person/exceptions/DuplicatePersonException.java
100.00% <100.00%> (ø)

...del/person/exceptions/PersonNotFoundException.java
100.00% <100.00%> (ø)

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 0599b2c...732105a. Read the comment docs.


Elastic request aggregation

What is the motivation for adding / enhancing this feature?

By each product or category page request we're currently executing at least few requests for Elastic data:

get product,
get related,
get reviews,
get attributes

How about merging them all into a single request? It could be very easily done at the syncData method level.
I mean if we take all the requests directed to Elastic and merge them into a single one;
instead of:
query no 1: Product
{"query":{"bool":{"filter":{"bool":{"must":[{"terms":{"visibility":[2,3,4]}},{"terms":{"status":[0,1]}},{"terms":{"category_ids":[20,21,23,24,25,26,22,27,28]}}]}}}},"aggs":{"agg_terms_color":{"terms":{"field":"color","size":10}},"agg_terms_color_options":{"terms":{"field":"color_options","size":10}},"agg_terms_size":{"terms":{"field":"size","size":10}},"agg_terms_size_options":{"terms":{"field":"size_options","size":10}},"agg_terms_price":{"terms":{"field":"price"}},"agg_range_price":{"range":{"field":"price","ranges":[{"from":0,"to":50},{"from":50,"to":100},{"from":100,"to":150},{"from":150}]}},"agg_terms_erin_recommends":{"terms":{"field":"erin_recommends","size":10}},"agg_terms_erin_recommends_options":{"terms":{"field":"erin_recommends_options","size":10}}}}

query no 2: Attributes
{"query":{"bool":{"filter":{"bool":{"must":[{"terms":{"attribute_code":["pattern","eco_collection","climate","style_general","performance_fabric","material"]}},{"terms":{"is_user_defined":[true]}},{"terms":{"is_visible":[true]}}]}}}}}

query no 3: Breadcrumbs
{"query":{"bool":{"filter":{"bool":{"must":[{"terms":{"id":[2,35,30,23]}},{"terms":{"is_active":[true]}}]}}}}}

query no 4: Reviews
{"query":{"bool":{"filter":{"bool":{"must":[{"terms":{"product_id":[1385]}},{"terms":{"review_status":[1]}}]}}}}}

query no 5: Related products
{"query":{"bool":{"filter":{"bool":{"must":[{"terms":{"category_ids":[2,35,30,23]}},{"terms":{"visibility":[2,3,4]}},{"terms":{"status":[1]}}]}}}}}

query no 6: Upsell products
{"query":{"bool":{"filter":{"bool":{"must":[{"terms":{"category_ids":[2,35,30,23]}},{"terms":{"visibility":[2,3,4]}},{"terms":{"status":[1]}}]}}}}}

Have single request:
query no 1: Combined query
[
{"query":{"bool":{"filter":{"bool":{"must":[{"terms":{"visibility":[2,3,4]}},{"terms":{"status":[0,1]}},{"terms":{"category_ids":[20,21,23,24,25,26,22,27,28]}}]}}}},"aggs":{"agg_terms_color":{"terms":{"field":"color","size":10}},"agg_terms_color_options":{"terms":{"field":"color_options","size":10}},"agg_terms_size":{"terms":{"field":"size","size":10}},"agg_terms_size_options":{"terms":{"field":"size_options","size":10}},"agg_terms_price":{"terms":{"field":"price"}},"agg_range_price":{"range":{"field":"price","ranges":[{"from":0,"to":50},{"from":50,"to":100},{"from":100,"to":150},{"from":150}]}},"agg_terms_erin_recommends":{"terms":{"field":"erin_recommends","size":10}},"agg_terms_erin_recommends_options":{"terms":{"field":"erin_recommends_options","size":10}}}},

{"query":{"bool":{"filter":{"bool":{"must":[{"terms":{"attribute_code":["pattern","eco_collection","climate","style_general","performance_fabric","material"]}},{"terms":{"is_user_defined":[true]}},{"terms":{"is_visible":[true]}}]}}}}},

{"query":{"bool":{"filter":{"bool":{"must":[{"terms":{"id":[2,35,30,23]}},{"terms":{"is_active":[true]}}]}}}}},

{"query":{"bool":{"filter":{"bool":{"must":[{"terms":{"product_id":[1385]}},{"terms":{"review_status":[1]}}]}}}}},

{"query":{"bool":{"filter":{"bool":{"must":[{"terms":{"category_ids":[2,35,30,23]}},{"terms":{"visibility":[2,3,4]}},{"terms":{"status":[1]}}]}}}}},

{"query":{"bool":{"filter":{"bool":{"must":[{"terms":{"category_ids":[2,35,30,23]}},{"terms":{"visibility":[2,3,4]}},{"terms":{"status":[1]}}]}}}}}
]

Challenges:

concurrency - parallel queries - not all queries can be pooled into single request as some of them are results of another one :)
currently, most of their users are using the GET method for Elastic requests in order of having easier output caching and service workers doing its job. We need to cover this scenario as well and it could be challenging as the GET method will get a really huge one if you combine few requests into one
to check if Service Workers do properly cache POST methods - if so then this is not a big deal

In order to have this feature work we need to extend vue-storefront-api for kind of graphql-like resolvers handling the queries (which would be extremly simple as the queries in the end are just ES queries)

Related to #2167


tensorflow-gpu version?

I can not load the provided checkpoints successully, So I'm wondering the version of tensorflow-gpu? anybody know?

Restoring from checkpoint failed. This is most likely due to a mismatch between the current graph and the graph from the checkpoint. Please ensure that you have not altered the graph expected based on the checkpoint.

Assign requires shapes of both tensors to match. lhs shape= [5,5,16,128] rhs shape= [5,5,19,128]
[[node save/Assign_569 (defined at /mnt/d/mahao/codes/SPADE-Tensorflow/SPADE.py:537) ]]

copy "{(0, 0, 0): 0, (0, 0, 255): 1, (255, 0, 0): 2, (150, 30, 150): 3, (255, 65, 255): 4, (150, 80, 0): 5, (170, 120, 65): 6, (125, 125, 125): 7, (255, 255, 0): 8, (0, 255, 255): 9, (255, 150, 0): 10, (255, 225, 120): 11, (255, 125, 125): 12, (200, 100, 100): 13, (0, 255, 0): 14, (0, 150, 80): 15, (215, 175, 125): 16, (220, 180, 210): 17, (125, 125, 255): 18}" into segmap_label.txt can remove this error. If there is no segmap_label.txt, the code will generate one based on the data in the dataset, the maximum value in the segmap_label.txt is 15 rather than 18. so just creat segmap_label.txt before testing


fix typo

fix typo in Makefile.

Coverage decreased (-0.008%) to 54.862% when pulling 96bc432b4f8435c8df58f6b6d0077135c0b2cb1e on m-masataka-ns:fix-typo into b9422ec60a65ffd568d05b8e1e18df436b7044ae on vmware:master.

let' defer it to post 1.2

Agree, will merge it after release.


Cannot read property 'toLocaleLowerCase' of undefined

Cannot read property 'toLocaleLowerCase' of undefined: TypeError: Cannot read property 'toLocaleLowerCase' of undefined
    at VSCodeConfiguration.getHost (/Users/penlv/.vscode-insiders/extensions/microsoft.vscode-pull-request-github-0.0.11/out/authentication/vsConfiguration.js:46:37)

Duplicate of https://github.com/Microsoft/vscode-pull-request-github/issues/191 😄


Smart ASA Discovery

How will platforms (explorer, wallets etc...) incorporate an ARC-20 seamlessly into a accounts's asset balances?
(Assumption: Most users wont be concerned with the distinction, so they'd likely just want to see an ARC-20 along with all their other ASA's.)
A platform would have to pull an account from algod/indexer and iterate through the app-local-states applying a brittle heuristic to the state to see if they can assume that local state represents an ARC-20.
I propose, why not just be explicit!  Add an additional state field 'isArc20' = 1 (or w/e).  This would make it trivial to identify ARC-20 assets in an account.
(Please tell me if this issue  is better suited to the ARC-20 thread, just thought I'd start here)

Closing, I'd completely forgotten about the underlying asset... that's my bad.


Not quite working, unfortunately -

Hi there, great work on your part, very appreciated for sure.
Upgrading to the latest 3.0 variant, things doesn't quite work. When I try to run it says
ghost-mgr@ghost-caucasusandmercury:~$ ghost-purge-images display --content-key=69891a65807dc1931c98406ded --admin-key=5cefed645c7944048554b2d5:b50084fd0cdda8fa7cb93fb2f17c2537cd294aa1f540b3f307ca6dbedc48da8b
internal/modules/cjs/loader.js:638
    throw err;
    ^

Error: Cannot find module 'jsonwebtoken'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
    at Function.Module._load (internal/modules/cjs/loader.js:562:25)
    at Module.require (internal/modules/cjs/loader.js:692:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Object.<anonymous> (/usr/lib/node_modules/ghost-purge-images/lib/ghost/auth.js:1:13)
    at Module._compile (internal/modules/cjs/loader.js:778:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
ghost-mgr@ghost-caucasusandmercury:~$

before that, when upgrading, I got a message saying:
root@ghost-caucasusandmercury:~# npm install -g ghost-purge-images
/usr/bin/ghost-purge-images -> /usr/lib/node_modules/ghost-purge-images/bin/ghost-purge-images.js
npm WARN notsup Unsupported engine for<EMAIL_ADDRESS>wanted: {"node":"8.12.0","npm":"6.0.0"} (current: {"node":"10.18.1","npm":"6.13.4"})
npm WARN notsup Not compatible with your version of node/npm<EMAIL_ADDRESS>npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/ghost-purge-images/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
+<EMAIL_ADDRESS>added 109 packages from 567 contributors, removed 14 packages and updated 11 packages in 8.765s

And yes, I tried doing the sudo chmod -R a+rw content thing.
...so something about node I guess? Kind regards !

Hi @Caucasus-and-Mercury ,
The issue was not related to Node version but I updated the engines block to avoid the warning 👍
Please install latest version v3.0.2 released some minutes ago and try again
Sorry for the inconvenience, thanks for reporting & your patience :)

Sorry still not working in my case. I've messed around with file permissions before, so it might be only for me? Anyway, when I try to run I'm getting this:
root@ghost-caucasusandmercury:/var/www/ghost# ghost-purge-images display --content-key=69891a65807dc1931c98406ded --admin-key=5cefed645c7944048554b2d5:b50084fd0cdda8fa7cb93fb2f17c2537cd294aa1f540b3f307ca6dbedc48da8b
internal/modules/cjs/loader.js:638
    throw err;
    ^
Error: Cannot find module 'minimist'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
    at Function.Module._load (internal/modules/cjs/loader.js:562:25)
    at Module.require (internal/modules/cjs/loader.js:692:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Object.<anonymous> (/usr/lib/node_modules/ghost-purge-images/lib/ghost/content.js:7:14)
    at Module._compile (internal/modules/cjs/loader.js:778:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
root@ghost-caucasusandmercury:/var/www/ghost# root@ghost-caucasusandmercury:/var/wwwroot@ghost-caucasusandmercury:/var/www/ghoroot@ghost-caucasusandroot@ghorootrootroot@ghost-caucaroot@ghororororoot@ghost-caucasusandmercury:/var/www/ghost#
www/ghosty:/var/www/root@ghost-c

Thanks a lot, as always -

hey @Caucasus-and-Mercury
Just released v3.0.3, please update to this version and try again
Sorry for the inconvenience & thanks for your patience 👏

Almost there!
Now it's working, but not working quite as it should. Pictures are purged, but many pics are purged that are in use and should have been left untouched.
I struggle to find a pattern. Pics in use in post are purged, some but not all, seemingly randomly. Also pics used in drafts are purged, randomly it seems.
Any ideas? When running the end looks like this, if it helps:
(...)
- /var/www/ghost/content/images/2019/11/als-mosmetro-map-v4.0-jpg.jpg (0.83 MB)
- /var/www/ghost/content/images/2019/11/als-mosmetro-map-v4.0-jpg.png (1.41 MB)
📊 Summary:
- 2768 files of 2768 uploaded images (100.00%)
- Total space: 969.44MB
❔ Want to delete this files? Run `ghost-purge-images purge key=YOUR_KEY`
🎁 Open source tool by David Burgos from https://ghostboard.io
ghost-mgr@ghost-caucasusandmercury:/var/www/ghost$

@Caucasus-and-Mercury all the images... pretty weird, let me know which Ghost version are you running. On the other hand, are you running ghost-purge-images version 3.0.3 (latest) ?

@dburgos not all images...although it says so. It purges many pics randomly, but not all.
I'm on the very latest ghost, and yes I suppose I'm running the latest ghost-purge-images version, having updated it according to instructions. Any way to really check which version I'm running?

@Caucasus-and-Mercury In order to check Ghost version have a few ways to check it:

Via command in your blog server: ghost ls will list your ghost blog, in the third column named "Version" can find it
Or in your blog admin interface, go to <yourBlogURL>/ghost/#/about the first line is the Ghost version

In order to check the ghost-purge-images version:

Run in your blog server: npm info ghost-purge-images version

@dburgos well: running the latest 3.03 ghost purge, and the latest 3.6 Ghost. Still getting this issue.
(...) ```

/var/www/ghost/content/images/2019/04/siberiannationalcostumes_yakutiarussia_01.jpg (0.09 MB)
/var/www/ghost/content/images/2019/04/vladimir-kolodenko---aeroport.JPG (0.04 MB)

📊 Summary:

2771 files of 2771 uploaded images (100.00%)
Total space: 969.57MB

❔ Want to delete this files? Run ghost-purge-images purge key=YOUR_KEY
🎁 Open source tool by David Burgos from https://ghostboard.io
ghost-mgr@ghost-caucasusandmercury:/var/www/ghost$

@Caucasus-and-Mercury thanks for your help, I'm going to open another issue and investigate it, right now I can not reproduce it :(