-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running metaflow-service and UI locally sees artifacts and DAG not displayable #334
Comments
Diving into the error log, i can see:
could it be that either metaflow-service or metaflow made some changes and caused to sort of conflicts in paths? So that it doesn't find it? |
The same error is seen in DAG section.
|
@charlesdong1991 ... did you ever manage to get this working. I'm hitting the same issue. |
I have the same issue :( I am running metaflow-service and metaflow-ui locally and the error is the same for the DAG
|
I was able to see my DAG after setting AWS S3 in the metaflow configuration file (Configuring Metaflow) and setting my AWS_PROFILE in both the metaflow-ui and metaflow-service. It would be nice to have an option to run things locally without the use of the cloud. |
Setting up metaflow-service and UI locally and run an example flow, I can see the Flow information. However, all artifacts are NOT displayed, see
'NoneType' object has no attribute 'get'
. But locally on notebook, I am able to get the artifacts, e.g.Task('Flow/8/start/23', attempt=0)['df'].data
.Having a look at the chrom inspect, I can see a 500 internal error related to CORS:
But in the code, i can see there is loose setting for it already:
metaflow-service/services/utils/__init__.py
Line 119 in 9c1d587
I think this results in the artifacts not displayable. Can anyone help with that and point out where i might do wrong?
Thank you!
The text was updated successfully, but these errors were encountered: