cellmap_flow.portable.publish_calls
===================================

.. py:module:: cellmap_flow.portable.publish_calls

.. autoapi-nested-parse::

   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
---------

.. autoapisummary::

   cellmap_flow.portable.publish_calls.publication
   cellmap_flow.portable.publish_calls.repo_refusal
   cellmap_flow.portable.publish_calls.hub_refusal
   cellmap_flow.portable.publish_calls.published_links


Module Contents
---------------

.. py:function:: 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.


.. py:function:: repo_refusal(args, arrays)

   ``publish.repo_refusal``: why a publish to ``repo`` by ``user`` (of
   ``orgs``) is refused before it starts, or null.


.. py:function:: hub_refusal(args, arrays)

   ``publish.hub_refusal``: what a publish to ``repo`` says when Hugging
   Face refuses its token (``status`` 401) or its writing there (403), by
   ``via``, or null for any other ``status``.


.. py:function:: published_links(args, arrays)

   ``publish.published_links``: where the model ``folder`` of ``repo``
   is (its ref and its repository's page) and the links that open it in
   the app at ``app`` with ``dataset`` (or null).