search

iotaledger / inx-chronicle

IOTA permanode implemented using the IOTA Node Extension (INX) interface.
Apache License 2.0
14 stars 14 forks source link

Chronicle doesn't return outputs compared to Hornet #1165

Closed msarcev closed 1 year ago

msarcev commented 1 year ago

Bug description

There is a case found where the response from Chronicle is different from the Hornet response.

Endpoint: /api/indexer/v1/outputs/basic

Usage with tag query param.

Example: tag: "Soonaverse" (0x536f6f6e617665727365) Chronicle -> https://chronicle.testnet.shimmer.network/api/indexer/v1/outputs/basic?tag=0x536f6f6e617665727365 VS Hornet -> https://api.testnet.shimmer.network/api/indexer/v1/outputs/basic?tag=0x536f6f6e617665727365

Steps to reproduce the bug

  1. View and compare the responses of links above

Expected behaviour

Chronicle should return the outputs. Response should be identical as when using Hornet for same input.

Actual behaviour

Chronicle return an empty array.

DaughterOfMars commented 1 year ago

Our API accepts the string tag, not the bytes.

https://chronicle.testnet.shimmer.network/api/indexer/v1/outputs/basic?tag=Soonaverse

If this is not acceptable, let us know.

shufps commented 1 year ago

It seems the indexer-specification allows only hex-encoded strings:

image

Chronicle should implement the API accordingly.

https://editor.swagger.io/?url=https://raw.githubusercontent.com/iotaledger/tips/main/tips/TIP-0026/indexer-rest-api.yaml