MEM-62: workshop MemWal friction fixes#187
Merged
harrymove-ctrl merged 1 commit intoMay 23, 2026
Merged
Conversation
harrymove-ctrl
approved these changes
May 23, 2026
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
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
*AndWaitguidance, namespace/key handling, recall distance filtering, and 401 troubleshooting.MEMWAL_PRIVATE_KEYand removes the oldMEMWAL_KEYfallback to avoid credential ambiguity.Deployment note
Railway/services that use MemWal memory must set
MEMWAL_PRIVATE_KEYnow;MEMWAL_KEYis no longer read.Verification
./node_modules/.bin/tsc --noEmit./node_modules/.bin/tscpython3 -m pytest packages/python-sdk-memwal/tests/test_client.py -qgit diff --checkNote: npm latest for
@mysten-incubation/memwalis still0.0.4; local package is already0.0.5, so no new TS changeset was added to avoid bumping to0.0.6.