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
alternatively the accept action doesn't just move the folder on s3 but actually triggers the publish workflow that takes care of the full process and updates the logs accordingly as well.
This would make it a bit easier to keep track of what happened (also because then there is a CI log entry)
I know the initial motivation to skip the publish workflow (that essentially just does the moving) was to speed up publication on bioimage.io, but if the collection.json isn't updated this doesn't work at all instead.
(We've been disussing this issue elsewhere already, just couldn't find it rn)
To clarify the current issue:
with the draft overview generated from collection_draft.json the accepted model is still listed there and looking at it's details will trigger a 404 as the files have been moved.
The collection.json that holds the content for bioimage.io does not know about this move, so the model is still not listed there after this kind of publishing..
The text was updated successfully, but these errors were encountered:
https://github.com/bioimage-io/collection/actions/workflows/generate_collection_json.yaml
needs to run to update collection_draft.json and collection.json accordingly.
alternatively the accept action doesn't just move the folder on s3 but actually triggers the publish workflow that takes care of the full process and updates the logs accordingly as well.
This would make it a bit easier to keep track of what happened (also because then there is a CI log entry)
I know the initial motivation to skip the publish workflow (that essentially just does the moving) was to speed up publication on bioimage.io, but if the collection.json isn't updated this doesn't work at all instead.
(We've been disussing this issue elsewhere already, just couldn't find it rn)
To clarify the current issue:
with the draft overview generated from
collection_draft.json
the accepted model is still listed there and looking at it's details will trigger a 404 as the files have been moved.The
collection.json
that holds the content for bioimage.io does not know about this move, so the model is still not listed there after this kind of publishing..The text was updated successfully, but these errors were encountered: