You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(rename): skip stateless objects in PathsGenerator to prevent panic
When a manifest entry exists for a config that has neither local nor
remote state (e.g. an orphaned scheduler config after its target
orchestrator was deleted), PathsGenerator.doUpdate called
LocalOrRemoteState() which panicked unconditionally.
Two guards added to doUpdate:
1. Skip the object itself when both HasLocalState and HasRemoteState
are false.
2. Skip the object when its parent is stateless, since a valid path
cannot be resolved without a resolved parent.
Reproduces the crash in PSGO-233 / SUPPORT-15941 where kbc pull
panicked on "object Local or Remote state must be set" for clients
with an existing local manifest containing an orphaned scheduler entry.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
0 commit comments