-
Notifications
You must be signed in to change notification settings - Fork 824
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
Move Artifact Register FrameInfo #4011
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.
I don't feel comfortable approving here, because I don't know the code and context.
Is @syrusakbary familiar with this?
Otherwise will dig in a bit more to understand it properly.
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.
Would it be possible to have a test verifying that the collision is fixed?
Not sure how. The minimal test written by cosmos doesn't crash all the time. And it's a mater of timing here. |
I started to run this patch in infinite loop in our full test suite. There the issue popped up consistently before. Looks good for now. Will let you know if I find something. |
With this change I cannot reproduce the issue #3793 anymore. I ran the project's tests for more than 1000 times now. Looking good 🎉 |
Move Artifact Register FrameInfo to a more fitting place. Also register_frameinfo needs a
&mut self
now to reflect it change a state (even if it's a global static)