-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New files are not synced to running container. #5110
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
Comments
Suspect PR: #5016 |
Another suspect: #4896 |
I'm experiencing this too allthough strangely only on one artifact of 5 I have running in a build |
I just realised I was running 1.17.0 and upgrading to 1.17.1 seems to have solved this for me. |
I'm experience this issue with 1.17.1 (running pop/ubuntu20.10 & minikube). However, going back to 1.16.0 I don't have any sync issues with newly created files. |
@martinseanhunt 1.17.1 should also have the same issue. |
Thanks so much for the quick turnaround on this! |
When a new file which matches the glob in sync.manual is created, it is not synced to the running container. Changes to existing files are synced as expected.
This behaviour first appears in 1.17
Expected behavior
New files which match sync.manual are synced to the running container.
Actual behavior
The new file is not picked up
Information
The text was updated successfully, but these errors were encountered: