-
Notifications
You must be signed in to change notification settings - Fork 143
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
Vea problem 3 core implementation #350
Conversation
This reverts commit 6701422.
Co-Authored-By: Rob Rix <robrix@github.com>
Co-Authored-By: Rob Rix <robrix@github.com>
Co-Authored-By: Rob Rix <robrix@github.com>
Co-Authored-By: Rob Rix <robrix@github.com>
Co-Authored-By: Rob Rix <robrix@github.com>
Co-Authored-By: Rob Rix <robrix@github.com>
Co-Authored-By: Rob Rix <robrix@github.com>
Co-Authored-By: Rob Rix <robrix@github.com>
Co-Authored-By: Rob Rix <robrix@github.com>
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.
Adds new stack graph rules and some rust code changes to make tests work.
Were these tests in Aleph, and were these new tests in https://github.com/github/aleph/pull/3165 that required this? I'm curious to understand what the problematic behavior was.
All old tests seem to pass unchanged?
That is surprising 🤔. I cannot immediately remember why this might be there, though.
Since none of the tests changed, and also none of the existing Aleph tests changed in https://github.com/github/aleph/pull/3165 either, this should be okay, I suppose :)
Overlapping changes w/ other PRs; want confirmation that nothing is broken
Adds new stack graph rules and some rust code changes to make tests work. All old tests seem to pass unchanged?