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 driver gets stuck fetching new balances (keeps sending outdated balances) and we do not know why it happens.
Suggested solution
Add more logs (debug/trace logs, we can enabled them on the fly) around the balance fetching in order to figure out where it fails/why it fails.
Alternatives considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
For context: In order to allow solvers to “internalize” trades (trade with settlement balances instead of an AMM). For this we query the balance of relevant tokens and put them in the auction. These balances don’t get updated anymore. I.e. the balance etherscan reports is no longer identical to the balance we send in the /solve request.
Acceptance criteria
We add more logs which potentially will allow us debug better why the balances are stuck when it happens again.
The text was updated successfully, but these errors were encountered:
Problem
The driver gets stuck fetching new balances (keeps sending outdated balances) and we do not know why it happens.
Suggested solution
Add more logs (debug/trace logs, we can enabled them on the fly) around the balance fetching in order to figure out where it fails/why it fails.
Alternatives considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
For context: In order to allow solvers to “internalize” trades (trade with settlement balances instead of an AMM). For this we query the balance of relevant tokens and put them in the auction. These balances don’t get updated anymore. I.e. the balance etherscan reports is no longer identical to the balance we send in the /solve request.
Acceptance criteria
We add more logs which potentially will allow us debug better why the balances are stuck when it happens again.
The text was updated successfully, but these errors were encountered: