-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix svm slow conclusion #292
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is not the fix we had in mind. what changed?
} | ||
|
||
/// This one concludes an auction by getting the auction transaction status from the chain. | ||
#[tracing::instrument(skip_all, fields(auction_id, tx_hash, bid_ids))] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggest removing this instrumentation.
tx_hash is a bit misleading now since auction can have multiple transactions.
The rest is traced inside the conclude_auction_with_statuses
call.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I removed the fields, but kept the instument itself.
This PR aims to fix the svm slow conslusion issue
Sometimes the websocket hears about confirmation before the RPC client. In the previous version the conclude auction was dependent on RPC client also seeing the confirmation transaction. Now in the conclusion log listener worker, the code only use the log to conclude the auction.