Cafe137
Cafe137
OK, this seems to be a bug. It should not attempt to download the `00...00` entry, which is not a real chunk, just placeholder for metadata.
By upgrading to the new Bee-JS, this issue seems to have gone away, but there's a different one. The feed indices now contain payloads instead of a reference to the...
This is even more important now: v2.30.0 is required for feeds to work with Bee v2.6.0.
Depends on https://github.com/ethersphere/bee/issues/5126
In my case it is supposed to be a feed: `f69f6bf21e4e97abef7fb52239265373479f14309d70f98f81a335936dd21d8b` ``` "time"="2025-01-22 13:01:13.151150" "level"="error" "logger"="node" "msg"="http: panic serving 127.0.0.1:63738: runtime error: slice bounds out of range [:160] with capacity...
Update: Feeds are resolvable through their manifest address - the panic happens when trying to resolve it via feed address, which is unsupported AFAIK, but the panic still should not...
Unfortunately, this is by design as the API we are using for the updates (https://www.electronjs.org/docs/latest/api/auto-updater) does not support Linux. This does not mean that there are no issues with the...
Root cause: https://github.com/axios/axios/issues/6949 Should be fixed in new Bee-JS versions Dashboard may still need to be updated to new Bee-JS versions
Empirically speaking, it seems that SOC download is also disabled during the first 5 minutes (warmup period).
> Can you describe what the upload sizes are? and which api endpoint are you using? I was uploading the wikipedia, and at this point I was writing the mantaray...