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
The missing field is base_offer_id or counter_offer_id. I think the bug (if it is a bug or me missing something) was introduced in #3857 which removed synthetic offer ID. The new code is missing the else branch:
@bartekn I allowed base_offer_id and counter_offer_id to be NULL when there is no offer involved in the trade (e.g. liquidity pool trades). What is the purpose of having synthetic offer ids?
Shouldn't we have this still for non-LP trades? AFAIR, synthetic offer IDs are there for offers which are immediately traded so aren't assigned a specific ID.
Synthetic offer IDs were added in #667 and motivation was:
This should allow easier audit trails for offers and trades. When offer ids are not created in the protocol level (fully consumed offers and path payments) a synthetic offer id will be created (...).
What version are you using?
release-horizon-v2.9.0
branchWhat did you do?
Run verify-range tests for range: [13494463, 13494591].
What did you expect to see?
No diff when comparing to 2.8.3 (DB dump contains
offer_id
column removed in 2.9.0 - I manually removed it, will add a PR tomorrow).What did you see instead?
Diff:
The missing field is
base_offer_id
orcounter_offer_id
. I think the bug (if it is a bug or me missing something) was introduced in #3857 which removed synthetic offer ID. The new code is missing theelse
branch:go/services/horizon/internal/ingest/processors/trades_processor.go
Lines 292 to 294 in e55e42a
present in the old code:
go/services/horizon/internal/db2/history/trade_batch_insert_builder.go
Lines 65 to 69 in e6f322c
@tamirms can you check it out? Was it removed accidentally? I can't see any AMM issue mentioning removal of synthetic offer IDs.
The text was updated successfully, but these errors were encountered: