Nikhil Dabas
Nikhil Dabas
I agree - the HTTP status code should be used to determine error status. The issue is [here](https://github.com/livelycode/aws-lib/blob/0f12996ebbf6c3422c1adab7ffafa03c3d6c8403/lib/aws.js#L79). With SES, the error is returned in the result as `Error` instead...
We're using this on Windows to find pre-compiled binaries for pioasm and elf2uf2 -- just dropping a comment here so that I am in the loop on what resolution comes...
I think a workaround might be to set [`CMAKE_FIND_USE_SYSTEM_ENVIRONMENT_PATH`](https://cmake.org/cmake/help/latest/variable/CMAKE_FIND_USE_SYSTEM_ENVIRONMENT_PATH.html) to `FALSE` to stop it from scanning everything in the system PATH. Not sure if that will interfere with the compiler...
Looks like this was [changed](https://github.com/microsoft/vscode-cmake-tools/blob/main/CHANGELOG.md) in the [Nov 2023 release](https://github.com/microsoft/vscode-cmake-tools/releases/tag/v1.16.29) of v1.16.29. We'll need to update the pico-setup-windows installer as well, https://github.com/raspberrypi/pico-setup-windows/issues/38 might be related.
Microsoft's guidelines explicitly say that installers, when performing a system-wide install, should not install anything per-user. Not sure what this installer is doing exactly but it should really only be...
> Those guidelines do not apply if you are not seeking Windows certification - which we are not. I can see no advantage to our users of doing so at...
The forward slashes are correct, but you need to use the [configured profile](https://github.com/raspberrypi/pico-setup-windows/tree/master/packages/pico-examples/ide/vscode) for debugging, so the debug button on the bottom bar does not work. Our VS Code configuration...
Yes, you're not supposed to use the debug button on the bottom status bar, the .vscode configuration that we provide is supposed to hide that for this reason. I'll see...
Yes. We haven't validated that the toolchain (which is all built for x64) works correctly under emulation.
Thanks for the report, we will look at removing this limitation from the installer for the next release.