-
Notifications
You must be signed in to change notification settings - Fork 55
Invalid bytecode generated by neo-boa #40
Comments
I have an update! After many hours of testing and trying different things, I was able to come up with a couple of hacks that work around this issue. I'll post exact steps to reproduce the issue here, which will hopefully be helpful. Here is the commit that works around the two issues we identified, with appropriate notes and comments: NarrativeCompany/tokensale-neo-smartcontract@e50a00f Here is the prior version that is broken: Steps to reproduce the issue: Edit Compile and deploy Run the following to bootstrap the contract:
Then, just run any of the following to see the issue:
You can use any address for Then, try again with the updated version: https://github.com/NarrativeNetwork/tokensale-neo-smartcontract/tree/master You should see that it works properly after the changes. |
I'm running into this problem as well. Is the issue that a function cannot call another function? |
This should be resolved in v0.3.3 |
Going to close this one out. |
We are using neo-boa 0.2.1 in order to work around compiler issues in neo-boa 0.2.2 (see #35).
This issue might have the same root cause as #29, but I'm creating anew since it seems like this issue is manifesting itself in a much worse way, with no identified workaround as of yet.
When issuing a
testinvoke
, we are getting this kind of response, even though the function only ever returns eitherTrue
orFalse
:It seems like the actual value being returned is some kind of full representation of the stack?
If we actually try to invoke it, there are a bunch of different tracebacks as a result:
The text was updated successfully, but these errors were encountered: