Sanaz Taheri
Sanaz Taheri
Given that the network issue is not reproducible in local tests (where it behaves as expected), I will use this opportunity to address the other issue i.e., https://github.com/celestiaorg/celestia-core/issues/1134 that was...
I believe I've pinpointed a possible cause for the duplication of blockparts in each peer-to-peer connection. My hypothesis is that the InfluxDB client might be resubmitting duplicates of the same...
> > entries for the same height, round, step, and node_id > > sorry I think I'm missing something simple, it looks like the example is a different round? In...
I am including an additional view from the past hour (which is different from the prior snapshot, yet the pattern is the same) to further clarify the data: ![Screenshot 2023-12-06...
Reassigning myself once I actively begin working on it.
cc: @evan-forbes @cmwaters @rootulp would be interested to know your pov
>If we want to have an unbounded test, we could use a different docker image that we build specifically for our tests. This would allow us to make other alterations...
To outline the next steps required to implement this change, following actions seem necessary for a long-term sustainable solution (please let me know your thoughts): - Create a separate branch...
The resolution for the current issue is captured in https://github.com/celestiaorg/celestia-app/issues/3370. Therefore, we can close this one.
Since reactors may be responsible for different channel IDs, it would be more insightful to get "percentage of bandwidth used by each _channel ID_ and per _peer_ over time" (in...