-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Add support for Aggregate signatures in PyVelox and Signatures.py #9104
Conversation
✅ Deploy Preview for meta-velox canceled.
|
94c2977
to
488c980
Compare
@kgpai has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
1 similar comment
@kgpai has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
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.
LGTM. Please also let @assignUser take a look.
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.
LGTM I can rebase #9191 on this and prepare the actual sig checking too
488c980
to
a8e160a
Compare
@kgpai has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
a8e160a
to
3a461c0
Compare
3a461c0
to
8e2a32e
Compare
@kgpai has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
Conbench analyzed the 1 benchmark run on commit There were no benchmark performance regressions. 🎉 The full Conbench report has more details. |
…cebookincubator#9104) Summary: **What** This PR adds support for aggregate signatures in PyVelox and export these signatures using signature.py **Why** Support for aggregate signatures was missing previously in our biasing logic to make sure that changes in aggregate functions are backwards compatible. This first PR adds support for these aggregate signatures so that we can use them to track changes in aggregate signatures across commits. A subsequent PR will add support for biasing and erroring if we detect compatible/incompatible changes with newly added or modified aggregates. Pull Request resolved: facebookincubator#9104 Reviewed By: kagamiori Differential Revision: D54977056 Pulled By: kgpai fbshipit-source-id: aff940ff3b7b7eca2b825f67d3c6de2b10a0baad
…cebookincubator#9104) Summary: **What** This PR adds support for aggregate signatures in PyVelox and export these signatures using signature.py **Why** Support for aggregate signatures was missing previously in our biasing logic to make sure that changes in aggregate functions are backwards compatible. This first PR adds support for these aggregate signatures so that we can use them to track changes in aggregate signatures across commits. A subsequent PR will add support for biasing and erroring if we detect compatible/incompatible changes with newly added or modified aggregates. Pull Request resolved: facebookincubator#9104 Reviewed By: kagamiori Differential Revision: D54977056 Pulled By: kgpai fbshipit-source-id: aff940ff3b7b7eca2b825f67d3c6de2b10a0baad
What
This PR adds support for aggregate signatures in PyVelox and export these signatures using signature.py
Why
Support for aggregate signatures was missing previously in our biasing logic to make sure that changes in aggregate functions are backwards compatible. This first PR adds support for these aggregate signatures so that we can use them to track changes in aggregate signatures across commits. A subsequent PR will add support for biasing and erroring if we detect compatible/incompatible changes with newly added or modified aggregates.