-
Notifications
You must be signed in to change notification settings - Fork 5
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
Dagster job ensure_job_triggered
is failing due to invalid usage of >
comparator
#349
Comments
The other failing run (Run ID |
Based upon that stack trace, I think the issue is:
nmdc-runtime/nmdc_runtime/site/ops.py Line 409 in dc668ea
Given that the issue involves types, I suspect it stems from the recent update from Pydantic v1 to v2. CC: @dwinston |
ensure_job_triggered
is failing due to invalid usage of >
comparator
Assuming this won't be completed today so will move to the next sprint to complete. @dwinston @eecavanna @PeopleMakeCulture |
Related to: #339 |
First will try to reproduce locally. I see, from the landing page for the dagster job-run in dagit, i.e., https://dagit.microbiomedata.org/runs/052af738-7a04-4fe1-a305-5692455a313b, one of the run tags is |
I am able to reproduce. Submitting the above changesheet via
|
ensures `model_dump` preserves python `datetime`s, which are handled by pymongo. reverts mode='json' option to model_dump, to preserve datetimes. fixes #349
* fix: use @field_serializer for pydantic `Url`s ensures `model_dump` preserves python `datetime`s, which are handled by pymongo. reverts mode='json' option to model_dump, to preserve datetimes. fixes #349 * fix: preserve exclude_unset * style: remove `print` for debugging * fix: remove stale comment
@sujaypatil96 reported that he submitted a changesheet but it hadn't been applied yet. When I check dagit i see that changesheets hasn't run since ~8 AM this morning and when looking at the activity tab it shows failures b/w 1-2pm for ensure_job_triggered
Please see if you can debug the ensure_job_triggered failures so we can get the changesheets applied. This is blocking workflows that will trigger once part_of is fixed (via the changesheet submission).
cc @Michal-Babins @shreddd
env:prod
The text was updated successfully, but these errors were encountered: