search

ethersphere / swarm-cli

Manage your Bee node and interact with the Swarm network via the CLI
BSD 3-Clause "New" or "Revised" License
48 stars 21 forks source link

feed print --list fails #545

Open ldeffenb opened 1 month ago

ldeffenb commented 1 month ago

The following feed print command fails to list the updates on the feed manifest reference.

swarm-cli feed print --address 0xbc1d30e299e1c6beb1f470c171db11246ed94bdf -t 053822aeb5f1e905019add41b51494de5c398ce18ac3def3b4c4d531b76cb068 --bee-api-url http://localhost:1633 --list where localhost:1633 is a sepolia testnet node.

It successfully shows the most recent value, but fails when asked to --list all updates.

Note that earlier updates to this feed were on a stamp that has since expired, but I would expect --list to at least report that the expected update was unavailable.

Further, repeated executions of this command, at least on my sepolia testnet nodes, gives alternating number of updates between 8 and 14 as well as different Chunk References when -v is used. I'm wondering if the redundancy retrieval or some other change in bee 2.2.0 has broken the manifest feed SOC retrievals?

swarm-cli feed print --address 0xbc1d30e299e1c6beb1f470c171db11246ed94bdf -t 053822aeb5f1e905019add41b51494de5c398ce18ac3def3b4c4d531b76cb068 --bee-api-url http://192.168.10.20:1630 -v
Feed Manifest URL: http://192.168.10.20:1630/bzz/fdfd170f73953bc262d936d3a5329b787980335dc0547032bb2a6239ebe95a76/
Chunk Reference: e472a46bc4fda22819622bebb9ae73045920787b5ba61cf2a2991b353fca8cc0
Chunk Reference URL: http://192.168.10.20:1630/bzz/e472a46bc4fda22819622bebb9ae73045920787b5ba61cf2a2991b353fca8cc0/
Feed Index: 000000000000000d
Next Index: 000000000000000e
Feed Manifest: fdfd170f73953bc262d936d3a5329b787980335dc0547032bb2a6239ebe95a76
Topic: 053822aeb5f1e905019add41b51494de5c398ce18ac3def3b4c4d531b76cb068
Number of Updates: 14
Run with --list to see all updates
swarm-cli feed print --address 0xbc1d30e299e1c6beb1f470c171db11246ed94bdf -t 053822aeb5f1e905019add41b51494de5c398ce18ac3def3b4c4d531b76cb068 --bee-api-url http://192.168.10.20:1630 -v
Feed Manifest URL: http://192.168.10.20:1630/bzz/fdfd170f73953bc262d936d3a5329b787980335dc0547032bb2a6239ebe95a76/
Chunk Reference: 5cacd1a6ae2b96c9cd07d9cec0205c35acd8a787e1798d18b9132df93da3fe80
Chunk Reference URL: http://192.168.10.20:1630/bzz/5cacd1a6ae2b96c9cd07d9cec0205c35acd8a787e1798d18b9132df93da3fe80/
Feed Index: 0000000000000007
Next Index: 0000000000000008
Feed Manifest: fdfd170f73953bc262d936d3a5329b787980335dc0547032bb2a6239ebe95a76
Topic: 053822aeb5f1e905019add41b51494de5c398ce18ac3def3b4c4d531b76cb068
Number of Updates: 8
Run with --list to see all updates

The following is the errors that show up when using --list.

swarm-cli feed print --address 0xbc1d30e299e1c6beb1f470c171db11246ed94bdf -t 053822aeb5f1e905019add41b51494de5c398ce18ac3def3b4c4d531b76cb068 --bee-api-url http://192.168.10.20:1630 --list
Feed Manifest URL: http://192.168.10.20:1630/bzz/fdfd170f73953bc262d936d3a5329b787980335dc0547032bb2a6239ebe95a76/
Topic: 053822aeb5f1e905019add41b51494de5c398ce18ac3def3b4c4d531b76cb068
Number of Updates: 14

Update 0: 65e66b4d0e4bb016ab53bce987ba0f7735ee0d25f217d709b8670f877723d224
http://192.168.10.20:1630/bzz/65e66b4d0e4bb016ab53bce987ba0f7735ee0d25f217d709b8670f877723d224/
ERROR Feed topic lookup error: Request failed with status code 500

There may be additional information in the Bee logs.
swarm-cli feed print --address 0xbc1d30e299e1c6beb1f470c171db11246ed94bdf -t 053822aeb5f1e905019add41b51494de5c398ce18ac3def3b4c4d531b76cb068 --bee-api-url http://192.168.10.20:1630 --list
Feed Manifest URL: http://192.168.10.20:1630/bzz/fdfd170f73953bc262d936d3a5329b787980335dc0547032bb2a6239ebe95a76/
Topic: 053822aeb5f1e905019add41b51494de5c398ce18ac3def3b4c4d531b76cb068
Number of Updates: 8

Update 0: 65e66b4d0e4bb016ab53bce987ba0f7735ee0d25f217d709b8670f877723d224
http://192.168.10.20:1630/bzz/65e66b4d0e4bb016ab53bce987ba0f7735ee0d25f217d709b8670f877723d224/
ERROR Feed topic lookup error: Request failed with status code 500

There may be additional information in the Bee logs.
ldeffenb commented 1 month ago

Executing this same command against a mainnet swarm node is even more interesting as it (at least on my mainnet nodes) lists all updates regardless of the fact that the underlying SOC chunks were stored with a long-expired stamp! I'm guessing the required chunks are still in various node caches, but this makes --list appear to work fine on mainnet, but fails on the testnet when individual update chunks are no longer available in the swarm.