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
update returning "key not found" #355
Comments
It is interesting that running the following code works the first time I run it:
But, when I run the exact same thing again, it fails:
I then modified the code to stop after the first run, saved off the db file, and then the compared it to the db file after a failed run, and there is no difference in the db file. So this seems to indicate it is not a problem in the db data, but rather the code that runs the update. Is there caching or some state that would cause it to work the first time but not the second? Or, am I doing something wrong? For reference, my test program: https://github.com/simpleiot/simpleiot/blob/feature-genji-update/cmd/genji-test9/main.go |
Thanks for the very detailed issue @cbrake, this bug was tricky and your examples helped a lot! |
Thanks -- seems to be working now. Yes that does look a tricky one -- nice work! SIOT is now using latest genji |
@cbrake Awesome! Please keep in mind that next release will contain a breaking change in the storage system, which will render previous databases incompatible. |
@asdine good to know. SIOT is currently in heavy development and I'm not currently deploying anything, so I'll just keep tracking main until I get to that point. I should add a note to the documentation about this for other users. |
What version of Genji are you using?
(current Genji main:HEAD as of 2021-03-08)
Also tried with v0.10.0
Does this issue reproduce with the latest release?
Yes
What did you do?
The following fails unless I remove the index on the type field.
Also, can use: https://play.golang.org/p/G97cg9Usw9f
What did you expect to see?
What did you see instead?
What Go version and environment are you using?
go env
OutputThe text was updated successfully, but these errors were encountered: