Skip to content
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

fix(scan): handle "No: more data" error. #144

Merged
merged 1 commit into from
Dec 17, 2024
Merged

fix(scan): handle "No: more data" error. #144

merged 1 commit into from
Dec 17, 2024

Conversation

iwanbk
Copy link
Member

@iwanbk iwanbk commented Dec 16, 2024

zdb return "No: more data" string when the scan is finished. This commit handle it properly instead of logging an error.

Fixes #143

zdb return "No: more data" string when the scan is finished.
This commit handle it properly instead of logging an error.
@LeeSmet
Copy link
Contributor

LeeSmet commented Dec 17, 2024

I'm extremely uneasy with this. Back when I made this, matching on an exact string. Is this error part of the interface of 0-db? if not it might change at will and break 0-stor because of a patch update on a 0-db

@iwanbk
Copy link
Member Author

iwanbk commented Dec 17, 2024

It is documented at the README https://github.com/threefoldtech/0-db?tab=readme-ov-file#scan

If the dataset is empty, or you reach the end of the chain, -No more data is returned.

if it changed, the only broken thing (for now) is the logging.

@LeeSmet LeeSmet merged commit 1532396 into master Dec 17, 2024
4 checks passed
@LeeSmet LeeSmet deleted the fix-nomoredata branch December 17, 2024 12:25
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.

Could not get meta keys from metastore
2 participants