- Notifications
You must be signed in to change notification settings - Fork294
fix: syncronously create the symlink to the requirements zip#862
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Open
cyberavyss wants to merge1 commit intoserverless:masterChoose a base branch
base:master
Could not load branches
Branch not found:{{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline, and old review comments may become outdated.
Uh oh!
There was an error while loading.Please reload this page.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
Currently, the symlink is created asynchronously. On a 14-CPUs MacBook Pro the current code leads to a raise condition - the symlink not yet existing during subsequent attempy to use it, but existing afterward. This happens in ~90% of the invocations:Serverless: Packaging Python Requirements Lambda Layer...Serverless: Found cached Python Requirements Lambda Layer file Exception ----------------------------------------------- OperationalError: ENOENT: no such file or directory, open '/Users/XXXX/git/YYYY/.serverless/pythonRequirements.zip' Patching the code locally as proposed, fixes the problem.Also, making the symlinkSync() call will be consistent with making the copySync() call in the adjacent if(...) statement branch.
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Labels
None yet
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Currently, the symlink is created asynchronously. On a 14-CPUs MacBook Pro the current code leads to a raise condition - the symlink not yet existing during subsequent attempy to use it, but existing afterward. This happens in ~90% of the invocations:
Serverless: Packaging Python Requirements Lambda Layer...
Serverless: Found cached Python Requirements Lambda Layer file
Exception -----------------------------------------------
OperationalError: ENOENT: no such file or directory, open '/Users/XXXX/git/YYYY/.serverless/pythonRequirements.zip'
Patching the code locally as proposed, fixes the problem.
Also, making the symlinkSync() call will be consistent with making the copySync() call in the adjacent if(...) statement branch.