Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Print failure when creating local file fails #1646

Closed

Conversation

phss
Copy link
Contributor

@phss phss commented Nov 16, 2015

Fixes #1645. May fix #1069 and #1442.

This only applies when downloading large files. See issue #1645 for more details.

Fix aws#1645

This only applies when downloading large files. See issue aws#1645 for more
details
@phss phss changed the title Print failure when create local file fails Print failure when creating local file fails Nov 16, 2015
@jamesls
Copy link
Member

jamesls commented Nov 17, 2015

Looks good, I'm just going to add a quick integration test before merging. Thanks for the PR.

@jamesls jamesls added the pr:needs-review This PR needs a review from a Member. label Nov 17, 2015
@jamesls
Copy link
Member

jamesls commented Nov 17, 2015

Merged in your PR and added an additional integ test. Tracking over in #1648 .

@jamesls jamesls closed this Nov 17, 2015
@phss
Copy link
Contributor Author

phss commented Nov 17, 2015

Thanks for merging @jamesls. And apologies as I completely forgot about permission issues on Windows.

thoward-godaddy pushed a commit to thoward-godaddy/aws-cli that referenced this pull request Feb 12, 2022
To support debugging for Nodejs10.x and Nodejs12.x, SAM CLI overrides
the entrypoint to the container. In newer runtimes (that are based
on the provided runtime), we overrided the bootstrap file which can
have side-effects. In the case of Nodejs, the bootstrap file adds
the NODE_PATH env var. Since we override this, NODE_PATH does not
get setup on the system and causes modules to not load (in some
cases, aws#1246). With aws#1634 (Java11 Debug support), we added a
capability to attach Env Vars into the container for debug mode
invokes. We will use this to apply the NODE_PATH onto the container
for debug.

I attempted to move all the args we pass into NODE_OPTIONS, which would
make Nodejs work like Java11 for debug. That is, allow us not to override
the entrypoint and still be able to apply the needed flags to the interpreted.
Unfortunately, NODE_OPTIONS restricts values that can be passed in,
which includes `--nolazy`. This flag is used to tell Nodejs to parse
all JavaScript files first instead of on first access. This ensures that
breakpoints to not "jump" to a different location in the file. It could
be worth exploring whether `--nolazy` is strictly required but for now
leaving as is.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr:needs-review This PR needs a review from a Member.
Projects
None yet
2 participants