-
Notifications
You must be signed in to change notification settings - Fork 239
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
Automated status checks of the resolvers #187
Comments
Thanks for the constructive feedback. It's always helpful to hear how we can improve the Universal Resolver to benefit the community. Regarding your bullets points:
We don't know yet how we will display the results of the automated checks but thanks for the suggestions. There will be at least one session on IIW next week about that topic, so feel free to jump in. |
@BernhardFuchs maybe there is a chance to use actions with a schedule to do this. Sounds cool, will check up if I have time for IIW! |
@cre8 yes, my idea was to use a cron job to collect the results. Not sure yet which interval but I'm happy to get some input on this topic. |
We discussed this on the 29 Sep 2021 Universal Resolver work item call and thought that most of the items in this issue have been addressed (e.g. by updating the Driver Development page). We created two new issues about remaining smaller topics, and propose to close this one. @cre8 do you agree? |
@peacekeeper sounds good :) |
Since some networks seems to be down or loose support over the time, it would be useful to have a tool that checks for availability and correctness of time. This could be useful for the future since the amount of did methods will grow.
Reporting tool:
The repository offers a tool that will run the code under quickstart and validates the results. The table includes the following rows:
The tool could be used to update the drivers table by adding another row like (check). The value can be updated by a commit but the better solution would be to use badges. When using badges we need a hosted service that will check the information.
The text was updated successfully, but these errors were encountered: