Closed lacabra closed 5 years ago
@lacabra I deployed several contracts and ran many executions but was unable to reproduce this. if there is any way to locate the actual behavior that leads to this bug, it will be very helpful.
@AvishaiW I tried hard to trigger this error, and it's not appearing for me either now. Let's leave this issue open for the time being, should it appear again.
I'm marking it invalid
for the time being.
I have seen it today while trying to deploy secret contracts. I deployed 3 successfully, and this appeared on the 4th deployment. Then I tried redeploying it, and it succeeded; which is consistent with prior observations.
I saw it while on a network with NODES=3
, in case it makes a difference.
Removing the invalid
tag, as it seems to be relevant again.
@lacabra after a lot of work and research of @elichai we were able to locate the bug leading to this error. the getDerivedKey function on the client side was implemented in a way that if the x coordinate of the derived key started with a 0, it ignored it, so it explains why there was an error that was nondeterministic. @elichai is adding a PR which will fix this. @lacabra great catch!
Describe the bug The following error appears at random, and I have not been able to correlate it to any other event. But I have seen it appear consistently every 5 to 10 operations, either with deploy or compute. It appears in operations that otherwise run fine in previous or later runs. Whenever a deploy/compute task is sent to the network, everything unfolds fine, until it reaches
core
, and it reports:To Reproduce Steps to reproduce the behavior:
discovery-integration-tests
network01_init.spec.js
testExpected behavior This error should not happen, and
core
should successfully compute the requested taskBacktrace Including here a much longer backtrace, though I don't think there is any additional useful information in it:
Desktop (please complete the following information):