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
Local runs attached to an S3 metadata store integrate seamlessly with the HTML card. Utilizing the Netflix Metaflow extensions, we also install metaflow-card-html within the Flow-level @pip_base decorator. Take this example of running a monitoring job:
We will see the card for the corresponding run in the Metaflow UI.
However, once we register this in a flow as a step-function w/ Batch tasks, we receive the following error: MetaflowCard named html not found. Check the type attribute in @card
Note this error references the attribute name html regardless of what option is set in the decorator, which to me implies that the underlying Batch runner doesn't know about this card extension.
Question
For Step Function flow deployments, do we need to have the HTML card module installed anywhere else within our Metaflow infra? Is there a recommended way of debugging this card rendering fail, regardless of the answer to the aforementioned question?
The text was updated successfully, but these errors were encountered:
Issue
Local runs attached to an S3 metadata store integrate seamlessly with the HTML card. Utilizing the Netflix Metaflow extensions, we also install
metaflow-card-html
within the Flow-level@pip_base
decorator. Take this example of running a monitoring job:We will see the card for the corresponding run in the Metaflow UI.
However, once we register this in a flow as a step-function w/ Batch tasks, we receive the following error:
MetaflowCard named html not found. Check the
typeattribute in @card
Note this error references the attribute name
html
regardless of what option is set in the decorator, which to me implies that the underlying Batch runner doesn't know about this card extension.Question
For Step Function flow deployments, do we need to have the HTML card module installed anywhere else within our Metaflow infra? Is there a recommended way of debugging this card rendering fail, regardless of the answer to the aforementioned question?
The text was updated successfully, but these errors were encountered: