-
Notifications
You must be signed in to change notification settings - Fork 6.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixed manifest_dump issues when printing keys and values containing null characters #8378
Fixed manifest_dump issues when printing keys and values containing null characters #8378
Conversation
You can see CircleCI failed on your test. (The regex does seem so specific that I was afraid it would be fragile.) |
…ll characters directly, which wasnt working properly because of the python subprocess call.
The latest CircleCI failures are unrelated to this change |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The test is slightly obscure but gets the job done. 👍
…rify that key with null character in it is present in the manifest_dump output.
@bjlemaire has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator. |
@bjlemaire merged this pull request in d61a449. |
Changed fprintf function to fputc in ApplyVersionEdit, and replaced null characters with whitespaces.
Added unit test in ldb_test.py - verifies that manifest_dump --verbose output is correct when keys and values containing null characters are inserted.