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
{{ message }}
This repository was archived by the owner on May 11, 2026. It is now read-only.
Running the sanity check is the main blocker before tagging the code with v1.
At the moment running the sanity scripts seems to have a few problems that need to be solved:
figure out how to run the sanity checks only for the latest commit not for all changes
Find the best way to run the sanity checks between the commit and push (using bash or directly from python)
Enable the sanity checks by default and fail the action if they fail
The first point is the most problematic.
It is the reason why I set them to be optional.
At the moment when the sanity checks are run they will run on the whole wrapdb.
In other words they compile every project in the wrapdb.
I don't know why they do this and how to prevent it but it is a problem.
Running the sanity check is the main blocker before tagging the code with v1.
At the moment running the sanity scripts seems to have a few problems that need to be solved:
The first point is the most problematic.
It is the reason why I set them to be optional.
At the moment when the sanity checks are run they will run on the whole wrapdb.
In other words they compile every project in the wrapdb.
I don't know why they do this and how to prevent it but it is a problem.