fix(main): Avoid adding package list to nil module #29
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
- Check if mod is nil before appending to mod.Pkgs - Prevent potential nil pointer dereference errors If the first line of modules.txt is a replace directive, for example: ```txt # dm v0.0.0 => ../db/drivers/dm/8.1.4.80/dm ``` In this case, the variable mod may not be initialized, causing a nil pointer error. Therefore, check if mod is nil before appending to avoid this issue.
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.
If the first line of modules.txt is a replace directive, for example:
# dm v0.0.0 => ../db/drivers/dm/8.1.4.80/dmIn this case, the variable mod may not be initialized, causing a nil pointer error. Therefore, check if mod is nil before appending to avoid this issue.