Suggesting gvm to fix Go version SIGSEV on README prepare-your-dev-environment.md #3426
Conversation
This file contains 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
azoppiserpa
requested review from
jewzaam,
bennerv,
hawkowl,
rogbas,
jharrington22,
cblecker,
cadenmarchese,
UlrichSchlueter,
s-amann,
SudoBrendan,
Shivkumar13,
yjst2012,
jaitaiwan,
anshulvermapatel,
hlipsig and
dofinn
as code owners
|
For awareness and to prevent de-duplication, do changes proposed in #3385 fix this issue? There are also other changes coming soon (tm) where all build processes will happen inside containers, removing the need for any local tools other than |
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.
Which issue this PR addresses:
Doesn't address an issue, it's just a minor update to our README based on my experience trying to setup the repo with Go 1.22 instead of Go 1.18.
What this PR does / why we need it:
Would be good to let other developers know Go > 1.18 can cause issues while Go = 1.18 works fine.
Test plan for issue:
Not applicable.
Is there any documentation that needs to be updated for this PR?
Not applicable.