fix: use correct env var names in memguardian init#744
Merged
Mzack9999 merged 1 commit intoMay 19, 2026
Conversation
Neo - PR Security ReviewNo security issues found Comment |
Mzack9999
approved these changes
May 19, 2026
Member
Mzack9999
left a comment
There was a problem hiding this comment.
good catch, both env vars were silently dead
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
2 participants
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.
Fixed incorrect env var names used in memguardian init() function.
Bug: The init() function was using the wrong env var names:
Fix: Changed both to use their respective, correctly-named env vars.
Before:
After:
This ensures that the documented env vars ( and ) actually work as intended.