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

If a file is removed during the sync process, livepush will cancel with an error #48

Open
CameronDiver opened this issue Sep 10, 2019 · 3 comments
Assignees

Comments

@CameronDiver
Copy link
Contributor

ref: https://forums.balena.io/t/test-livepush-change/31462/14

[Error]   An error occured whilst trying to perform a livepush: 
[Error]      ENOENT: no such file or directory, lstat '.goutputstream-4LFQ7Z'

The .gooutputstream... seems to be a temporary file, so when this is created, livepush will trigger (if a copy command will implicitly reference the directory containing this file, for example COPY . .) and if the file is removed before the copy occurs, livepush will fail.

@CameronDiver CameronDiver self-assigned this Sep 10, 2019
@balena-ci
Copy link
Contributor

[gelbal] This issue has attached support thread https://jel.ly.fish/#/support-thread~00c5ac6f-4317-4514-a3e8-c0f4f76d5d9e

@srlowe
Copy link
Contributor

srlowe commented Nov 18, 2019

Ran into this issue myself with PopOS (Ubuntu 19.10) - In my case it was happening when I modified files using gedit. Other text editors did not show the same problem (both terminal (nano) and GUI based (Jetbrains Webstorm)).

@CameronDiver
Copy link
Contributor Author

Yeah, I think the best way to handle this is to ignore when a file is added but is removed by the time livepush attempts to ship it into the running container. Honestly we could probably re-examine all of the failure modes when using livepush, I guess as a developement tool sometimes it can be a bit heavy handed in what it does not allow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants