Skip to content
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

[Bug]: restore the position resolution event #10173

Closed
EVODelavega opened this issue Nov 24, 2023 · 1 comment
Closed

[Bug]: restore the position resolution event #10173

EVODelavega opened this issue Nov 24, 2023 · 1 comment
Assignees
Labels

Comments

@EVODelavega
Copy link
Contributor

Problem encountered

When parties are distressed, we used to emit a position resolution event containing the mark price, number of distressed parties, and the number of parties that were closed out (the difference between the two being the parties that were able to keep their position after their orders were closed)

Observed behaviour

No position resolution event is emitted

Expected behaviour

The event should be emitted if parties are distressed

Steps to reproduce

Run any test that results in parties getting closed out, and capture the events. The event is not there

Software version

develop

Failing test

No response

Jenkins run

No response

Configuration used

No response

Relevant log output

No response

@vega-issues vega-issues moved this to Waiting Review in Core Kanban Nov 24, 2023
@EVODelavega EVODelavega assigned EVODelavega and unassigned gordsport Nov 24, 2023
@vega-issues vega-issues moved this from Waiting Review to Approved in Core Kanban Nov 27, 2023
@gordsport gordsport moved this from Approved to In Progress in Core Kanban Jan 2, 2024
@gordsport
Copy link
Contributor

implemented in another PR

@github-project-automation github-project-automation bot moved this from In Progress to Merged in Core Kanban Jan 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants