Skip to content
This repository has been archived by the owner on Apr 6, 2020. It is now read-only.

Fix levelup NotFoundError handling #83

Merged
merged 1 commit into from
Jan 3, 2019
Merged

Conversation

s1na
Copy link
Contributor

@s1na s1na commented Jan 3, 2019

VM tests are failing on the iterate method of Blockchain. I think the reason is different versions of levelup being used in the two projects. VM passes its db to Blockchain, which checks the error by err instanceof level.errors.NotFoundError on a more recent version of levelup.

The modified condition seems to work, but it's probably a good idea to update levelup in VM as well.

Signed-off-by: Sina Mahmoodi <itz.s1na@gmail.com>
@coveralls
Copy link

Coverage Status

Coverage remained the same at 97.934% when pulling 9fd4bba on fix/level-err-handling into 6095dc9 on master.

Copy link
Member

@holgerd77 holgerd77 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, will directly do a bug fix release.

@holgerd77 holgerd77 merged commit 7b5deb7 into master Jan 3, 2019
@holgerd77 holgerd77 deleted the fix/level-err-handling branch January 3, 2019 21:35
@holgerd77
Copy link
Member

Can you also prepare a PR towards the VM? We should also update the merkle-patricia-tree dependencies along the way. There was a levelup modernization PR lately merged along with a general library modernization, but I haven't done the release yet. Will try to do soon.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants