Anna Shaleva
Anna Shaleva
## Is your feature request related to a problem? Please describe. Currently `upload-bin` finds latest incomplete batch of blocks and starts reuploading from the first block in this batch. Due...
## Is your feature request related to a problem? Please describe. Some of our example contracts are not tested although they are complicated. In fact, only NNS contract has some...
## Current Behavior Some blocks are uploaded to NeoFS, then restart of the script happens. The script starts to upload from 0 block, not from the latest incomplete batch: ```...
After https://github.com/nspcc-dev/neo-go/issues/3631 NeoFSBlockFetcher service missing a network magic check for the configured container, similar to the one implemented in https://github.com/nspcc-dev/neo-go/pull/3637/commits/c47d4e6c5b75b54f7a3c8ff1f3986fb98198d9fa.
Close #3490. @roman-khimov, what do you think? Another option is to cache size for every emitted notification and then check the overall notifications size every time we're going to emit...
## Current Behavior Debug info sequence points are not generated for some kind of statements. For example, calls to interops, builtins and syscalls don't have their own sequence points. Neotest...
Extend `./config/...` configurations for N3 mainnet/testnet and NeoFS mainnet/testnet with NeoFSBlockFetcher sections and appropriate containers info. Make BlockFetcher disabled by default.
## Current Behavior Our compiler does not include anonymous functions into the `methods` list of debug info: ```go func PublicContractMethod() { var f = func() { runtime.Log("bla") } f() f()...
## Current Behavior The original issue is posted in https://github.com/nspcc-dev/neo-go/pull/3462#issuecomment-2291269916 ## Expected Behavior Block coverage matches the expectations
## Current Behavior For some RET instructions our compiler generates sequence points with improper boundaries, for example for void functions (if there's no explicit `return` keyword in the code), also...