Fix tmux socket name length exceeding filesystem limits #204
Conversation
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
Truncate session names to prevent 'File name too long' errors when project names or branch names are very long. The tmux socket path has a limit of 108 characters total, so session names are now truncated to 50 characters to ensure the full socket path stays within filesystem limits.
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.
Problem
When using overmind with long project names or branch names, the tmux socket path can exceed the Unix filesystem limit of 108 characters, causing a 'File name too long' error.
Example error:
Solution
Truncate session names to 50 characters before creating the socket name. This ensures the full socket path stays within filesystem limits while still preserving uniqueness through the nanoid.
Changes