-
Notifications
You must be signed in to change notification settings - Fork 73
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
Evaluate existing plugin initialize and startup steps #97
Labels
Comments
Closing this request. I've turned it into a product initiative and will create new issues when and if we prioritize specific tasks. |
greg7mdp
added a commit
that referenced
this issue
Dec 15, 2023
131/150 Test #98: producer_schedule_hs_unit_test_eos-vm-jit ..........***Failed 1.36 sec 132/150 Test #97: producer_schedule_hs_unit_test_eos-vm ..............***Failed 1.57 sec 133/150 Test #96: producer_schedule_hs_unit_test_eos-vm-oc ...........***Failed 2.86 sec 144/150 Test #21: api_unit_test_eos-vm-oc ............................***Failed 79.26 sec 146/150 Test #23: api_unit_test_eos-vm-jit ...........................***Failed 96.61 sec 150/150 Test #22: api_unit_test_eos-vm ...............................***Failed 467.14 sec
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Today we believe that plugins should follow the following phases
We'd like to evaluate existing plugins to identify edge cases and confirm that we are or aren't broadly adopting this pattern. From there, we can submit an official proposal to adhere to for new plugins.
The text was updated successfully, but these errors were encountered: