DAGs & Artifacts not showing up in Metaflow UI REC...
# ask-metaflow
w
DAGs & Artifacts not showing up in Metaflow UI RECAP Errors:
- Artifact not currently displayable in the UI, use the client to access it.
- Since this run uses local datastore instead of cloud services, some information may be incomplete.
- TypeError: expected str, bytes or os.PathLike object, not NoneType
Going through the channel this is due to the Datastore is not configured with s3 However typing datastore in the official documentation : https://docs.metaflow.org/internals/technical-overview#datastore I see β€œ_The AWS S3 is a perfect solution for this need. Secondarily, Metaflow supports using a local disk as a data store_” which I don’t know if that is entirely accurate πŸ™‚ Another couple of observations two links seems to be broken datastore.py and s3.py Finally the solution I see in the channel is the proposed article by @bulky-artist-49977 https://medium.com/@rezashabrang.m/configuring-metaflow-for-on-prem-deployment-f8c4da24a097 Unless there is another πŸ™‚ Currently facing with this (completely local setup )
a
correct - you can use local file system as your datastore; however the UI won't work perfectly because of that
βœ… 1
re:
Copy code
Another couple of observations two links seems to be broken
good catch - we should fix that
βœ… 1
re: completely local setup - are you setting up the metadata service or relying on the local filesystem for setting up your metadata? in the latter scenario, the UI won't work. I can walk you through the options when we speak tomorrow if you would like.
🫢 1
w
I believe I’m relying on my local filesystem:
Copy code
"METAFLOW_DEFAULT_METADATA": "service"
That would be amazing thank you very much. Looking forward for our talk