-
Notifications
You must be signed in to change notification settings - Fork 38
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
upd/Neo-go to v0.103.0 #2635
upd/Neo-go to v0.103.0 #2635
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2635 +/- ##
=======================================
Coverage 29.21% 29.21%
=======================================
Files 416 416
Lines 31328 31330 +2
=======================================
+ Hits 9152 9154 +2
- Misses 21376 21377 +1
+ Partials 800 799 -1
... and 1 file with indirect coverage changes 📣 Codecov offers a browser extension for seamless coverage viewing on GitHub. Try it in Chrome or Firefox today! |
e033eb7
to
da1fad5
Compare
da1fad5
to
538ed75
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there any other places where emit
NeoGo package is uses for custom scripts creation instead of smartcontract
's Builder? If so, then we should also adjust them (if possible).
Amount: initialProxyGASAmount, | ||
from := c.CommitteeAcc.Contract.ScriptHash() | ||
|
||
tx, err := createNEP17MultiTransferTx(c.Client, c.CommitteeAcc, gas.Hash, []nep17.TransferParameters{{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe then createNEP17MultiTransferTx
can be removed completely? And you transfer it from the committee account anyway, so you can use committee actor directly from c.CommitteeAct
without creating simple actor. Is there any pitfalls?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe then createNEP17MultiTransferTx can be removed completely?
can be done, ok
Is there any pitfalls?
do not think there are any
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we've agreed to implement Builder-related changes in a separate PR, then let's fix this issue, and otherwise LGTM.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe then createNEP17MultiTransferTx can be removed completely?
fixed
There are some for sure. @roman-khimov, do we need it? How long |
|
538ed75
to
472b197
Compare
Done. |
Closes #2626. Signed-off-by: Pavel Karpy <[email protected]>
Closes #2429. Signed-off-by: Pavel Karpy <[email protected]>
472b197
to
802373c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM otherwise.
emit.AppCall(w.BinWriter, nnsCs.Hash, "resolve", callflag.ReadOnly, | ||
getAlphabetNNSDomain(i), | ||
int64(nns.TXT)) | ||
b.InvokeMethod(nnsCs.Hash, "resolve", getAlphabetNNSDomain(i), int64(nns.TXT)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
BTW, builder invokes this with callflag.All
, and it was ReadOnly before. But anyway, it's our contract and there's no harm in it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh, yeah, forgot to ping you about that. @roman-khimov, yes, in some cases there were readonly calls for readonly operations but nothing should break because of it. tbh, i really do not see much difference b/w InvokeMethod
and AppCall
except the call flags (and sometimes we need them)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's OK to have this RO -> ALL replacement in Adm.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've seen this, it doesn't matter much for these calls, most of them are test invocations only.
Signed-off-by: Pavel Karpy <[email protected]>
802373c
to
6da2ec2
Compare
No description provided.