mirror of
https://github.com/moghtech/komodo.git
synced 2026-05-06 08:40:30 -05:00
[GH-ISSUE #676] [Feature] Improve resource sync self handling #3503
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @satwell on GitHub (Jul 22, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/676
I've gotten Komodo stuck in a state where resource syncs cannot execute and fail with a "ResourceSync busy" error. To resolve, I've tried deleting the Komodo Core container, and I've also tried deleting and recreating the Sync in the UI. Neither fixes the issue. The Sync is stuck in state "pending" and every sync or execute attempt fails.
Here's how I got stuck in this state:
resources/directory in the repo. In git, I changedresource_path = ["resources/"]and movedmain.tomltoresources/main.toml. I pushed to my gitea server, which triggered the "execute sync" webhook. (This was a dumb mistake on my part--obviously I can't move the file before applying the change toresource_path.)Now every resource sync execution fails with a ""ResourceSync busy" error.
This is similar to the resource sync getting stuck that I reported in #672, but in that case restarting Komodo Core cleared it. In this case, I can't find an obvious way to clear the stuck ResourceSync. But in both cases, there's a failure loading resources from the sync, and it seems like the error handling does not properly terminate the task that's running.
@mbecker20 commented on GitHub (Jul 22, 2025):
Resource sync has quirk that it cannot execute a sync in which it is defined, if there are changes to itself. You can resolve it either by removing the sync declaration from toml, or updating by hand with toml exactly matching the config in Komodo (navigate to sync and grab Toml using top right button)
@satwell commented on GitHub (Jul 23, 2025):
Oh, that makes sense. I updated the sync config so that they match in the UI and in git, and now the sync works correctly again. Thank you!
Would it be possible for Komodo to provide a more descriptive error than "ResourceSync busy" for this case? Maybe something like, "ResourceSync cannot update itself." Maybe even tell the user that they need to manually update the resource themselves.
Given this limitation, it would be nice to have a way to exclude syncing the
resource_syncitself as part of the sync. Maybe aninclude_selfoption that would include or exclude that specific sync? Or this could be a use case for exclude tags as requested in #669.@mbecker20 commented on GitHub (Jul 24, 2025):
I think combo of improving the error log in this case, and eventual #669 implementation should solve this issue.