bonedaddy
bonedaddy
This is a known limitation of the Solidity language, so you would only be able to process the most recent 256 block headers. What you could do though is create...
I believe that would be required if you want to analyze blocks outside of the 256 block window. However I imagine that would be expensive as hell.
> Bisecting points to the etcd-client bump in #24159. Reverted in v1.9 here: #25003 It is unlikely that it is the etcd-client bump itself that is the problem, but rather...
hi @kubelvla did you ever figure this out? thanks.
> Hi, thanks for reporting this issue. That sounds pretty bad ... > > by "missing content" - is it that the note is now completely empty, it's missing part...
No problem. You make a good point the solution to this will likely vary depending on your specific needs. > An example where topic management could be pretty rough is...
@vyzo I've [uploaded](https://gateway.temporal.cloud/ipfs/QmPLX8PoHrAE3XPnSHfqE71wzKSHfmux8RanSg3yWPynfD) output from the logs.
Interesting, I suppose that makes sense with me spawning many goroutines that may not complete due to the `Next` hanging. Any ideas why `Next` seems to be hanging the way...
I think `shell` is a nice name. It sounds like you're establishing a shell to interact with the underlying IPFS node :smile:
I like the idea of using an `UnstableAPI` wrapper as well, and second what magik6k said about defining it in `interface-go-ipfs-core`.