Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 wonder how do we ensure that we've captured all the cases where the position health is updated. Note, this function has a few returns that skips this emit.
And is it possible the position health will be updated outside of this function?
This function only queues the update,
asyncUpdatePositionis actually the function updating the position. Should we emit event there instead?And this is when the position is updated from internally. What about externally? For instance, since position health depends on the price oracle, so the position health is changed as soon as the price oracle updates the price.
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.
Your concerns are valid and discussed in this PR. This PR is to be closed. We're going to gather position health factors via a script.