Closed darylteo closed 1 year ago
Approaching the issue from 2 angles.
Please refer to this issue: https://github.com/swift-server/vscode-swift/issues/522
Building from the same folder while working in VS Code causes race collisions with VS Code extension Package Resolution.
I suspect this is due to Swift repulling down dependencies in amazonlinux, but I could be wrong.
This can be worked around by disabling the auto resolver in the VSCode extension.
https://imgur.com/a/E4OL2fd
swift build
swift package archive
https://github.com/darylteo/bug-vscode-swift-lambda
swift-aws-lambda-runtime
1.0.0.alpha-1
1.62.15 Apple Swift version 5.7.2 (swiftlang-5.7.2.135.5 clang-1400.0.29.51)
No response
This has been resolved on the plugin side.
Expected behavior
Approaching the issue from 2 angles.
Please refer to this issue: https://github.com/swift-server/vscode-swift/issues/522
Building from the same folder while working in VS Code causes race collisions with VS Code extension Package Resolution.
I suspect this is due to Swift repulling down dependencies in amazonlinux, but I could be wrong.
This can be worked around by disabling the auto resolver in the VSCode extension.
Actual behavior
https://imgur.com/a/E4OL2fd
Steps to reproduce
swift build
worksswift package archive
does notswift package archive
now worksIf possible, minimal yet complete reproducer code (or URL to code)
https://github.com/darylteo/bug-vscode-swift-lambda
What version of this project (
swift-aws-lambda-runtime
) are you using?1.0.0.alpha-1
Swift version
1.62.15 Apple Swift version 5.7.2 (swiftlang-5.7.2.135.5 clang-1400.0.29.51)
Amazon Linux 2 docker image version
No response