mzhangmzz
mzhangmzz
This is to track all improvements we wished we had when we were debugging the testnet incident. Debug page: - [ ] https://github.com/near/nearcore/issues/7861 - [ ] https://github.com/near/nearcore/issues/7859 - [ ]...
# Feature to stabilize With this feature, blocks produced with protocol versions older than the current protocol version in the network will be considered invalid. This is to ban blocks...
Move the check for is_height_processed before process_block_header. Previously, this check happens after, which means, the node will re-process the block header (which takes a few ms) and re-broadcast an invalid...
2022-05-17T09:05:30.301533Z WARN chunks: Part ord 59 for chunk `2dL8x1wiWsUmUX76NvxFpmDY9Qn4hvNzvgBAdQnEC2ME` was forwarded multiple times 2022-05-17T09:05:30.301566Z WARN chunks: Part ord 123 for chunk `2dL8x1wiWsUmUX76NvxFpmDY9Qn4hvNzvgBAdQnEC2ME` was forwarded multiple times 2022-05-17T09:05:30.301571Z WARN chunks: Part...
Right now, to request a chunk, a node may send up to 400 messages, two for each part. This is a bottleneck in our system because it takes time for...
In [https://github.com/near/nearcore/pull/6747](https://github.com/near/nearcore/pull/6747), we moved the function to be called to after apply_chunks. It's better if the check that no block on the chain is challenged is performed before apply_chunks. We...