gifted-helicopter-98777
01/11/2024, 6:09 PMdry-beach-38304
01/11/2024, 7:48 PMdry-beach-38304
01/11/2024, 7:48 PMnamespace(None) first to see.gifted-helicopter-98777
01/12/2024, 8:28 AMdry-beach-38304
01/12/2024, 8:37 AMgifted-helicopter-98777
01/12/2024, 8:44 AMTask is starting.
Bootstrapping virtual environment...
Environment bootstrapped
<flow DPITForecastInferenceIDCase step load_last_model> failed:
AWS Batch error:
Essential container in task exited This could be a transient error. Use @retry to retry.
Object not found:
Run('DPITForecastTrainIDCase/1704964756701873') does not existgifted-helicopter-98777
01/12/2024, 8:49 AMdry-beach-38304
01/12/2024, 8:53 AMdry-beach-38304
01/12/2024, 8:54 AMRun here) requires a metadata service that is accessible everywhere you are using the client. In your case, you seem to be using a local metadata service so what’s running on batch won’t have access to it.gifted-helicopter-98777
01/12/2024, 9:09 AMdry-beach-38304
01/12/2024, 9:10 AMgifted-helicopter-98777
01/12/2024, 9:15 AMgifted-helicopter-98777
01/12/2024, 9:17 AMgifted-helicopter-98777
01/12/2024, 12:42 PMdry-beach-38304
01/12/2024, 5:25 PMdry-beach-38304
01/12/2024, 5:28 PMdry-beach-38304
01/12/2024, 5:28 PMdry-beach-38304
01/12/2024, 5:30 PMfrom metaflow import get_metadata
get_metadata()
If it prints something like service@<some url> then you are good but I suspect it will print something like local. If that is the case, your Metaflow is wrongly configured for the use case you want for it (ie: cross reference) and if you let me know how you installed it, I may be able to help or will ask some helpful person from OB (they have more experience with setup like that).gifted-helicopter-98777
01/15/2024, 1:59 PMgifted-helicopter-98777
01/18/2024, 12:26 PM