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
In the light of current xz incident, I think it would be great to provide dinner kind of health status monitoring across containers we contain. And run it not only when we add a container but correspondingly when we add a new check. So in some ways similar to https://github.com/dandi/dandisets-healthstatus?tab=readme-ov-file in that we want
establish collection of tests with each test versioned (eg output'ing --version)
specification of tests to run for a file type (regex )
per each file/version contain a list of tests and versions of the tests
We will need to run it where we have container images but such a tool sounds generic and could run as CI as well .
@jwodder do you may be know already existing framework? If not, it is for us to create one I think. Now I am thinking even may be dandi healthstatus potentially could be generalized into it eventually.
The text was updated successfully, but these errors were encountered:
Now I am thinking even may be dandi healthstatus potentially could be generalized into it eventually.
I don't think so. Much of dandisets-healthstatus deals with mounting & traversing file hierarchies to run tests on individual files, which doesn't seem to apply here.
In the light of current xz incident, I think it would be great to provide dinner kind of health status monitoring across containers we contain. And run it not only when we add a container but correspondingly when we add a new check. So in some ways similar to https://github.com/dandi/dandisets-healthstatus?tab=readme-ov-file in that we want
We will need to run it where we have container images but such a tool sounds generic and could run as CI as well .
@jwodder do you may be know already existing framework? If not, it is for us to create one I think. Now I am thinking even may be dandi healthstatus potentially could be generalized into it eventually.
The text was updated successfully, but these errors were encountered: