You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While playing aroud with mutable.put, I was trying to force an error for not updating seq while updating a value. I did expect this to raise an error, but instead the callback has been called with err undefined.
When calling mutable.get to get the value, I've received the value that was set with the initial put call. Is this intended behaviour?
While playing aroud with
mutable.put
, I was trying to force an error for not updatingseq
while updating a value. I did expect this to raise an error, but instead the callback has been called witherr
undefined.When calling
mutable.get
to get the value, I've received the value that was set with the initialput
call. Is this intended behaviour?This can easily be replicated by removing the sequence update from the
mutable-put-get
example: https://github.com/hyperswarm/dht/blob/master/examples/mutable-put-get.js#L26The text was updated successfully, but these errors were encountered: