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
Now that we have a working API endpoint, prior to a pull request going into main on this repo, we'll require a pre-push check to check all the data files from some branch X pass the jamduna matrix endpoint with "ok" for 100% data files as done here.
The end result of this will be that AT LEAST the data files are consistent with the data files.
This doesn't check for the chainspecs (which contain a genesis state) but it will help teams see the data state_transitions as visibly consistent with the jamduna endpoint.
The text was updated successfully, but these errors were encountered:
Addresses:
* #101 4.7 is the same as 4.17 C
* #100 with prepush check checkstatetransitions.sh
* Uses "fib2" service to explore more host function testing
Addresses:
* #101 4.7 is the same as 4.17 C
* #100 with prepush check checkstatetransitions.sh
* Uses "fib2" service to explore more host function testing
Now that we have a working API endpoint, prior to a pull request going into
main
on this repo, we'll require a pre-push check to check all the data files from some branch X pass the jamduna matrix endpoint with "ok" for 100%data
files as done here.The end result of this will be that AT LEAST the data files are consistent with the
data
files.This doesn't check for the
chainspecs
(which contain a genesis state) but it will help teams see thedata
state_transitions as visibly consistent with the jamduna endpoint.The text was updated successfully, but these errors were encountered: