Anna Shaleva

One more example: ``` 2024-10-24 06:10:41.740 Successfully uploaded batch of blocks: from 1960000 to 1969999 2024-10-24 06:14:17.712 Processing batch from 1980000 to 1989999 2024-10-24 06:14:17.712 Successfully uploaded batch of blocks:...

But sometimes it works differently (logs are from the same mainnet service): ``` 2024-10-24 06:37:08.145 Chain block height: 6235291 2024-10-24 06:54:58.627 Processing batch from 0 to 9999 2024-10-24 06:54:58.627 First...

Well, of course it's a bug in *fetchLatestMissingBlockIndex* only if our batches are full and don't have gaps. > can be connected https://github.com/nspcc-dev/neo-go/issues/3615 Check currently uploaded data for N3 mainet....

Checked, depends on #3615 resolution.

To resolve this issue, we need to adopt the SEARCH completeness marker once https://github.com/nspcc-dev/neofs-node/issues/2721 implemented.

See also https://github.com/nspcc-dev/neofs-node/issues/2721#issuecomment-2435121374: for situations where all SNs from REP policy are dead, we need to shut down BlockFetcher, because it won't be able to receive even block OIDs and...

Within the scope of this issue we need to revert changes made by https://github.com/nspcc-dev/neo-go/issues/3670 and fall back from per-object SEARCH to SEARCH for the range of objects.

> state differs at 5800000, block fe5278cd6dce728384a2c2ed40c511e5813c56a67c499eecef758709a8234065 OK, it's just came to my mind that it's a hardfork height. @AliceInHunterland, what is your node configuration? Does it have Domovoi enabled?...

Config is correct, and just for future, it's better to take the same version of NeoGo that runs in NeoFS. But for 0.106.3-pre-16-gda40f2de it doesn't matter because there were no...

I just leave it here so that it's possible to reference this comment, an outdated config is used for NeoFS mainnet nodes. ``` anna@kiwi:~$ curl -d '{ "jsonrpc": "2.0", "id":...