docs: socket guidance requires distinct paths, not merely explicit ones - #104
Merged
Conversation
Two daemons handed the same explicit --socket path collide exactly as they do on the default; distinctness is the property that matters. Observed live during the d0pt investigation when two agents were prescribed the same scratch path. Refs: aae-orc-t6da
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #103, one sentence: the guidance said one
--socketper concurrent daemon, but two daemons handed the same explicit path collide exactly as they do on the default (observed live when two agents were prescribed the same scratch path and the later daemon took the listener). Distinctness is the property that matters, so the guidance now says so.Refs: aae-orc-t6da