Conversation
During the zig 0.16.0 upgrade a `allocator.free` was not defered. This caused the origins not to be configured correctlly. Signed-off-by: Jim Fitzpatrick <jimfity@gmail.com>
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
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.
Summary
Fixes a bug where the working path allocated by
realPathFileAllocwas immediately freed instead of being deferred, causing the path memory to be deallocated before it was used in the subsequent git command. This resulted in origins not being configured correctly.The fix changes
allocator.free(_path)todefer allocator.free(_path)in bothsetupOriginandfetchOrigin, ensuring the path remains valid for the lifetime of the function and is properly cleaned up on exit.This bug was introduced during the Zig 0.16.0 upgrade.