nearcore
nearcore copied to clipboard
Known problems in the 1.37 release
As we transition to the new release process, we will no longer wait for features before the release cut (unless they are vitally important for the network). This issue now tracks known release problems.
### List of observed issues in 1.37 release
- [ ] #10749
- [ ] #10750
- [ ] #10751
- [ ] https://github.com/near/nearcore/issues/10753
- [ ] https://github.com/near/nearcore/issues/10755
- [ ] https://github.com/near/nearcore/issues/10767
~~This a dependancy tracker issue for the next release. Please, add any features and fixes you want to be included in the release.~~
[DEPRECATED] Previous issue description
### List of **required** features for mainnet release
- [ ] Split storage/big archival nodes in mocknet
- [ ] Merge [Shard_id refactoring](https://github.com/near/nearcore/commit/276b7e78afbf743ea964f11fcae8487c4c14df73) in master
- [x] Proper resharding restart during all stages
- [x] State snapshot management on split storage nodes
### List of **required** features
- [ ] https://github.com/near/nearcore/pull/10373
- [ ] https://github.com/near/nearcore/pull/10409
- [x] Change `TESTNET_MIN_BLOCK_PRODUCTION_DELAY` (not a blocker for cut, can be cherry-picked)
- [x] configure shard cache size in the new shard layout for children of shard 3 [zulip](https://near.zulipchat.com/#narrow/stream/407288-pagoda.2Fcore.2Fresharding/topic/Trie.20cache.20for.20shard.203.20with.20new.20shard.20layout/near/410844172)
- [x] ~~Verify if we see validator kickouts we've seen when testing for 1.36 & if reproducible still revert #9244 or pick up #10402 and verify that it helps~~ All indications point to this not being a problem
### List of **optional** features
- [ ] Split storage/big archival nodes in mocknet (not a blocker for cut, but it is useful to test archival resharding not in vacuum)
- [x] Fix the `epoch_manager: Unexpected error in is_last_block_in_finished_epoch` warning popping up on every block
- [x] Remove spammy info logs: `client: BlockResponse` and `INFO garbage_collection: GC`
@gmilescu @akhi3030 @walnut-the-cat Please add anything you want to be included in 1.37 @wacban @shreyan-gupta Please add any resharding-specific issues for 1.37.
I added two tasks to the wishlist about some warnings and info messages being spammy, this can be observed on a mainnet canary node.
@wacban, @gmilescu can we include in 1.37 the Cold storage copy loop optimizations as required? We will need to backport this to 1.36 as well