improve error messages when comppose files aren't parseable #4538
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
kzys
reviewed
Aug 29, 2025
| return nil, fmt.Errorf("failed to parse compose file: %w", err) | ||
| // Try to extract more detailed error information from yaml.TypeError | ||
| if typeErr, ok := err.(*yaml.TypeError); ok && len(typeErr.Errors) > 0 { | ||
| return nil, fmt.Errorf("YAML syntax error in compose file %s: %s", composePath, typeErr.Errors[0]) |
There was a problem hiding this comment.
Wouldn't it have multiple errors in Errors?
There was a problem hiding this comment.
It could, I'm fine with returning only the first error. Do you see this as a problem?
There was a problem hiding this comment.
Yes. If the parser can detect multiple errors, it makes sense to show all of them instead of hiding.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
See https://community.fly.io/t/docker-compose-compatibility-the-journey-begins/25285/22?u=rubys