Ogmios findIntersection request returns nothing

[mpizenberg]

I’m not sure what’s the issue here. I have a running dolos instance, which is synced up and configured to keep the whole history. Yet when I’m looking for an intersection point (old) with ogmios, it returns nothing. Is that expected?

Here is the example with both the request on koios, and on local ogmios.

❯ curl -X POST "https://api.koios.rest/api/v1/ogmios" \
      -H "accept: application/json" \
      -H "content-type: application/json" \
      -d '{"jsonrpc":"2.0","method":"findIntersection","params":{"points":[{"slot":90914081,"id":"2f7784ab8eee0e3d81223b9bd482195617cbee662ed6c412b123568251aac67a"}]}}'
{"jsonrpc":"2.0","method":"findIntersection","result":{"intersection":{"slot":90914081,"id":"2f7784ab8eee0e3d81223b9bd482195617cbee662ed6c412b123568251aac67a"},"tip":{"slot":166037493,"id":"592447a77a7eb5f9752c3a87cd517c144b1c512fa00145ecaa1bfd18fbd783ec","height":12376772}},"id":null}⏎

❯ curl -X POST "localhost:1337" \
      -H "accept: application/json" \
      -H "content-type: application/json" \
      -d '{"jsonrpc":"2.0","method":"findIntersection","params":{"points":[{"slot":90914081,"id":"2f7784ab8eee0e3d81223b9bd482195617cbee662ed6c412b123568251aac67a"}]}}'
{"jsonrpc":"2.0","method":"findIntersection","error":{"code":1000,"message":"No intersection found.","data":{"tip":{"slot":166037493,"id":"592447a77a7eb5f9752c3a87cd517c144b1c512fa00145ecaa1bfd18fbd783ec","height":0}}},"id":null}⏎

And here is my dolos config (relevant part).

[upstream]
peer_address = "backbone.mainnet.cardanofoundation.org:3001"
network_magic = 764824073
is_testnet = false

[storage]
version = "v1"
path = "data"
max_wal_history = 129600

[genesis]
byron_path = "byron.json"
shelley_path = "shelley.json"
alonzo_path = "alonzo.json"
conway_path = "conway.json"

[sync]
pull_batch_size = 100
sync_limit = "NoLimit"

[submit]

[serve.ouroboros]
listen_path = "dolos.socket"
magic = 764824073

I’m using Ogmios 6.8.0 and Dolos 0.32.0

[mpizenberg]

Am I the only one having this issue? Could you confirm if you can reproduce it?

[gonzalezzfelipe]

@mpizenberg Sory for the delayed response. This is a known bug that we will be solving promptly, it has to do with how we've changed the internal structure of the historical data on the filesystem. It used to be persisted on the WAL, but now it remains minimal with only the mutable part of the chain whilst the archive keeps the historical data. The ouroboros interface still only interacts with the WAL to perform the intersection. This is already fixed on the U5C API, we have to migrate these changes onto the ouroboros part.