-
Notifications
You must be signed in to change notification settings - Fork 3
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
Update ingestor to add dummy email if dataset has bad email #49
Comments
Ok, this could be an easier fix than I thought. In stead of
|
I was able to quickly put together a fix for the default email this morning (#50), but I have been running into blockers when trying to test locally. First, I was having trouble logging in to scicatlive to test the file ingestion. It appears it could stem from this git issue I found: SciCatProject/pyscicat#61 I tried with a few versions of scicatlive (2.8.0, 3.1.1, 3.2.5) in case an older version might work, but I was getting this error:
I was using the following env variables based on the scicat documentation:
I decided to work around this by calling the ScicatClient like this in
But now I get a different error...
My patch may work, but it would be nice to verify locally. I will try to get the version of scicat installed that matches what is in production. |
Not sure if the issue is that we're not getting email or if email is coming with a bad format, but we sometimes see scicat ingestion fail. We should put a check here, since we-formatted email is a requirement. We can add
[email protected]
if the dataset doesn't have a good email.splash_flows_globus/orchestration/flows/bl832/ingest_tomo832.py
Line 91 in 121aef5
The text was updated successfully, but these errors were encountered: