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
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
The text was updated successfully, but these errors were encountered:
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
Software version
develop
Failing test
No response
Jenkins run
No response
Configuration used
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: