Sync stops after initial sync
What happened?
devspace sync --config devspace.yaml command exists after initial sync
[info] Using namespace 'my-namespace'
[info] Using kube context 'my-context'
[info] Waiting for pods...
[info] Starting sync...
[info] Start syncing
[done] √ Sync started on /local/path <-> /remote/path (Pod: my-pod-name)
[info] Waiting for initial sync to complete
[info] Helper - Use inotify as watching method in container
[info] Downstream - Initial sync completed
[info] Upstream - Upload 11244 create change(s) (Uncompressed ~38456.75 KB)
[info] Upstream - Successfully processed 11244 change(s)
[info] Upstream - Initial sync completed
What did you expect to happen instead?
expected it to keep running and keep syncing
How can we reproduce the bug? (as minimally and precisely as possible)
devspace.yaml
version: v1beta10
dev:
sync:
- labelSelector:
app: myapp
containerName: my-container
namespace: my-namespace
containerPath: /app
uploadExcludePaths:
- "have/44/paths/under/upload/exclude"
downloadExcludePaths:
- "have/75/paths/under/download/exclude"
Local Environment:
- DevSpace Version: 5.14.4
- Operating System: mac
/kind bug
use devspace dev --config devspace.yaml
Hi, can we reopen this issue? I'm having the same problem on version 5.14.4 for devspace sync and devspace dev.
When using devspace dev, my config looks like this:
version: v1beta10
dev:
sync:
- labelSelector:
app.kubernetes.io/name: mylabel
app.kubernetes.io/component: appserver
containerName: django-uwsgi
excludePaths:
- .git/
- node_modules/
This used to work before upgrading versions.
Local Environment:
DevSpace Version: 5.14.4 Operating System: mac
@atainter could you post the complete output of devspace dev? Does it work if you use polling instead?
it happens to me on some windows OS's too, but the same config works on Mac/Linux...
@DanArlowski does it just stop after the Initial sync completed message or how does the output look exactly?
I am seeing this issue happening with latest devspace 5.16.2, OS - Mac Catalina
It has been working for a month and now only downstream sync happens for any file changes inside the container.
Upstream sync is not happening after the initial sync. No output after the Initial sync completed message.

even tried with 5.16.0 which was working for me well last week. Now upstream sync is currently broken.
@FabianKramm What could stop upstream sync after initial sync ? and only downstream sync works.
I'm seeing the same problem as @EdwinPhilip above. I'm running macOS Monterey Version 12.4 (21F79) and devspace version 5.18.5.