Worker repository synchronization

Workers validate the requested source revision before launching a routine. This keeps execution tied to a coherent installation rather than a partial download or an interrupted update. Repository addresses, credentials and revision selections belong to each installation; none are supplied by this guide.

Validation and updates

Validation rejects unfinished source-control operations, held Git lock files, unresolved conflicts, missing requirements and invalid interpreter installations. Updates use a verified upstream revision and fast-forward-only synchronization. The worker does not silently discard edits, force a reset, remove Git locks or hide conflicts in a stash. An operator must inspect and repair an interrupted installation before retrying it.

New downloads use a staging directory and become available only after completion. If an update cannot be applied, a previously verified installation may remain usable; the worker reports the reason. An unreachable remote and an invalid local installation are different conditions. Offline operation never bypasses coherence checks or starts installing packages against an unavailable remote.

Shared checks and concurrency

A short-lived cache shares upstream checks across callers for the same resolved installation and requested revision. It reduces repeated network queries, not local validation. Every launch checks local coherence. An explicit refresh can request a new remote check when a newly published revision must be used immediately.

A bounded advisory process lock serializes synchronization for one installation. A busy lock refuses a start on timeout rather than taking over an active update. Cache-state writes use atomic replacement, and malformed or unwritable state falls back to ordinary checks. Keep that state outside source directories.

Timeouts and diagnostics

Git queries, object transfers and package installation have separate configurable timeouts. A timeout is not proof that an interrupted installation is usable; any remaining source-control lock requires operator review. Commands and logs must not include remote URLs containing credentials or dump subprocess environments.

Inspect the routine's final status and logs after a refused or degraded update. A successfully queued start is not proof that synchronization or execution succeeded.