go.mod: fix compattest/peercfg version #77
Merged
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
Since this was only accessed via a go.mod replace directive, it worked fine for tests, etc. running in galaxycache's repo, but, since the replace directive doesn't propagate outside the original repo, go commands doing deep resolution complain because they can't resolve the zero-valued version. Note: Since the dependency on peercfg is only via tests, this didn't actually affect building anything depending on Galaxycache, just commands like that run by GoLand at startup: ```sh go list -modfile=go.mod -m -json -mod=mod all ```
Gigioliva
approved these changes
Dec 16, 2025
sergiosalvatore
approved these changes
Dec 16, 2025
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.
Since this was only accessed via a go.mod replace directive, it worked
fine for tests, etc. running in galaxycache's repo, but, since the
replace directive doesn't propagate outside the original repo, go
commands doing deep resolution complain because they can't resolve the
zero-valued version.
Note: Since the dependency on peercfg is only via tests, this didn't
actually affect building anything depending on Galaxycache, just
commands like that run by GoLand at startup: