Skip to content

Conversation

@sundb
Copy link
Collaborator

@sundb sundb commented Apr 25, 2024

For my mistake, in the last revert commit in #13231, I originally wanted to revert the last one, but reverted the penultimate fix.
Now that we have fix another potential memory read issue in 743f1dd (#13231), now it just seems to avoid confusion, i will verify in the future whether it will have any impact, if so we will add this PR to backport.

Failed CI: https://github.com/sundb/redis/actions/runs/8826731960

@sundb
Copy link
Collaborator Author

sundb commented Apr 25, 2024

Fully CI for this PR: https://github.com/sundb/redis/actions/runs/8826731960

@sundb sundb merged commit f95031c into redis:unstable Apr 25, 2024
@sundb sundb deleted the fix-test-failed branch April 25, 2024 06:11
funny-dog pushed a commit to funny-dog/redis that referenced this pull request Sep 17, 2025
For my mistake, in the last revert commit in redis#13231, I originally wanted
to revert the last one, but reverted the penultimate fix.
Now that we have fix another potential memory read issue in [`743f1dd`
(redis#13231)](redis@743f1dd),
now it just seems to avoid confusion, i will verify in the future
whether it will have any impact, if so we will add this PR to backport.

Failed CI: https://github.com/sundb/redis/actions/runs/8826731960
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants