cellmap_flow.portable.publish_calls
What the browser calls to publish a model to Hugging Face: the functions
web/src/backend/routes/publish.ts runs through chunkmirage’s
Engine.call("cellmap_flow.portable.publish_calls:<name>", args, arrays)
(calls.py says the shape). Each takes JSON and answers JSON; what they
answer is publish.py’s, which the server’s publish route calls in its
process, so a model published from either mode has the same card, the same
manifest and the same links.
Functions
|
The model card and the manifest of the publish |
|
|
|
|
|
|
Module Contents
- cellmap_flow.portable.publish_calls.publication(args, arrays)
The model card and the manifest of the publish
args["pub"](publish.publication_files):[{path, text}], in the order they are uploaded, before the model’s own file.
- cellmap_flow.portable.publish_calls.repo_refusal(args, arrays)
publish.repo_refusal: why a publish torepobyuser(oforgs) is refused before it starts, or null.
- cellmap_flow.portable.publish_calls.hub_refusal(args, arrays)
publish.hub_refusal: what a publish toreposays when Hugging Face refuses its token (status401) or its writing there (403), byvia, or null for any otherstatus.
- cellmap_flow.portable.publish_calls.published_links(args, arrays)
publish.published_links: where the modelfolderofrepois (its ref and its repository’s page) and the links that open it in the app atappwithdataset(or null).