You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue Title: Phantom Order - Order Closed on Contract but Open on Indexer
Description:
We have identified an issue where an order appears as closed on the contract but remains open on the indexer. We refer to this kind of problem as a "phantom order."
Order ID: 0x97ff915f6783fdba0ed03d8dc0b60f90186c08646ebbe0cd1e25863ee700478d
Steps to Reproduce:
Verify Order Status on Contract:
Using this script, we confirmed that the order is closed on the contract: Order Status Script
Verify Order Status on Indexer:
Using the following GraphQL query, we confirmed that the order is still open on the indexer:
In our contract, every order modification triggers an OrderChangeEvent. You can view the event definition here: OrderChangeEvent.
During debugging, we discovered that there were three OrderChangeEvent events emitted on the contract: create, match, and a final match that closed the order. However, the last match event is missing on the indexer.
I've checked the transaction 0xe5f7cddcb82c0de90ec1967f041009fd8678afd8f5268e9398f2426e5323072a in the block explorer https://app.fuel.network/tx/0xe5f7cddcb82c0de90ec1967f041009fd8678afd8f5268e9398f2426e5323072a/simple, and there's only one LOG_DATA receipt.
Please report the issue to the Fuel team so they can continue the investigation. Probably, it was broken, after they changed logId to the type hashes.
Issue Title: Phantom Order - Order Closed on Contract but Open on Indexer
Description:
We have identified an issue where an order appears as closed on the contract but remains open on the indexer. We refer to this kind of problem as a "phantom order."
Order ID: 0x97ff915f6783fdba0ed03d8dc0b60f90186c08646ebbe0cd1e25863ee700478d
Steps to Reproduce:
Verify Order Status on Contract:
Using this script, we confirmed that the order is closed on the contract:
Order Status Script
Verify Order Status on Indexer:
Using the following GraphQL query, we confirmed that the order is still open on the indexer:
Our debug
In our contract, every order modification triggers an
OrderChangeEvent
. You can view the event definition here: OrderChangeEvent.During debugging, we discovered that there were three
OrderChangeEvent
events emitted on the contract: create, match, and a final match that closed the order. However, the last match event is missing on the indexer.To get the list of events on the contract, we used this script: Get Order Change Events by Order.
To fetch the list of events on the indexer, we used the following GraphQL query:
Expected Behavior:
The order should be marked as closed on both the contract and the indexer.
Actual Behavior:
The order is closed on the contract but remains open on the indexer, creating a discrepancy.
Impact:
This issue leads to inconsistencies between the contract state and the indexer state, potentially causing confusion and incorrect data reporting.
Environment:
The text was updated successfully, but these errors were encountered: