-
Notifications
You must be signed in to change notification settings - Fork 44
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
putSync returning Promise #235
Comments
kriszyp
added a commit
that referenced
this issue
May 21, 2023
Good catch, thank you. |
You are welcome. As I recall removeSync currently has a similar pattern in the write.js file. Thanks for your prompt responses. |
anywhichway
added a commit
to anywhichway/lmdb-index
that referenced
this issue
May 21, 2023
This was referenced May 21, 2023
@kriszyp See repository https://github.com/anywhichway/lmdb-issues |
kriszyp
added a commit
that referenced
this issue
Jun 12, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
putSync is occasionally returning a Promise rather than a regular value. A review of the source shows the below at line 709 in write.js, so unless some other core code manages to force Promise resolution before returning, I can see how this would happen.
Is this expected? In the meantime, I am avoiding the use of
putSync
, which is relatively inconsequential.The text was updated successfully, but these errors were encountered: