#67
Fix container sync failure caused by missing project file reference
Status: closed
·
Summary
Every ~5 seconds, the container reconciliation service fails across all 12 running containers with an Errno 2 error when trying to copy a project file that no longer exists at the referenced path.
Steps to Reproduce
- Observe the container service logs for any of the 12 running containers.
- Wait approximately 5 seconds.
- Note the repeated error referencing the missing file
/home/retoor/projects/devplacepy/data/uploads/project_files/6a/98/019f46f5-d8df-7132-8c1a-a42b4601986a.jpg.
Expected Behaviour
The container sync should complete successfully, copying only existing files into each container's filesystem.
Actual Behaviour
The sync operation fails for every container because it attempts to copy a file that does not exist at the given path. The error aborts the entire sync for that container, preventing legitimate file updates from being applied.
Environment
- Service: Container reconciliation service
- Affected containers: All 12 running containers
- Error first observed: ~16:00 on 2026-07-12
- Error frequency: Every ~5 seconds per container (~144 errors/minute total)
- File path:
/home/retoor/projects/devplacepy/data/uploads/project_files/6a/98/019f46f5-d8df-7132-8c1a-a42b4601986a.jpg
Reported by retoor via DevPlace.
Updates & comments
I am picking this ticket up now.
First I will bring up an isolated workspace with a fresh checkout and investigate whether the ticket matches the current state of the code before planning any change. I will announce every step here before I take it.
Starting research round 1 of at most 5.
I am now reading the relevant source, tests, and prior work in the live checkout to verify the ticket and gather the context needed for a concrete plan. This can take a while; I will post periodic progress updates until it completes.
Ticket 1024 describes a
FileNotFoundErroraborting the container sync. I compared the ticket against the current source and tests; commit6fc0114already catches that specific error and logs a warning, allowing the sync to complete normally. The reported failure pattern no longer exists in the codebase.Based on this mismatch, could you confirm whether the ticket still represents an active issue, or should it be closed as resolved?
I am picking this ticket up now.
First I will bring up an isolated workspace with a fresh checkout and investigate whether the ticket matches the current state of the code before planning any change. I will announce every step here before I take it.
I need input to continue.
What I tried: Retried this step 3 times.
What I found: Each attempt failed for internal reasons unrelated to this ticket. The details are in the operator's logs; this is not a judgment about the ticket.
The system needs operator attention before I can continue. Reply here once things are healthy and I will resume from where I left off.
I am picking this ticket up now.
First I will bring up an isolated workspace with a fresh checkout and investigate whether the ticket matches the current state of the code before planning any change. I will announce every step here before I take it.
Starting research round 1 of at most 5.
I am now reading the relevant source, tests, and prior work in the live checkout to verify the ticket and gather the context needed for a concrete plan. This can take a while; I will post periodic progress updates until it completes.
After comparing the ticket against the current source and tests, we found that the codebase already handles the described missing file references in both
_export_node()andexport_to_dir()by downgrading the error to a logged warning, allowing sync to continue without failure. This means the reported bug appears to have been fixed in a prior change.Given this mismatch between the ticket description and the current state of the code, it seems no further work is needed. Could you confirm whether this ticket still reflects an active issue, or should it be closed as already resolved?
Oke, clos ten.
Posted by retoor via DevPlace.
This ticket has been cancelled and closed at your request. The decision was made after the initial research round, with no execution or implementation attempts. No further action is expected.
Log in to comment.