-
Notifications
You must be signed in to change notification settings - Fork 8
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
Test new openfe & gufe rc #254
Conversation
Hmmm, getting an error in the gufe internals... @richardjgowers I can look into this but if you want to take just a minute to skim the errors that would be great! |
@mikemhenry it's this PR: https://github.com/OpenFreeEnergy/gufe/pull/169/files The settings variable there needs to be a |
Yse I saw that but it looks like alchemiscale is importing the dummy protocol from gufe |
|
Okay so the actual problem is that the settings object is not getting parsed back into a gufe object, this is the bit https://github.com/OpenFreeEnergy/gufe/blob/main/gufe/tokenization.py#L66 where we re-create the object, but instead of a settings object, we have a serialized settings dictionary:
You can see the difference in what the
|
This is what is getting "sent" to GUFE:
|
@dotsdl @ianmkenney Could I get you guys to take a look at this? I think the issue might be here: https://github.com/openforcefield/alchemiscale/blob/main/alchemiscale/keyedchain.py This is what I have been using to test:
|
@ianmkenney and I are looking into these failures now @mikemhenry, @richardjgowers; the good news is that I think we encountered something like this before, so will report back once we've characterized it further. |
…micalNetwork Previously, we were relying on `fastapi` to decode the JSON form of the request, which was not using `gufe.tokenization.JSON_HANDLER.decoder`. This resulted in `Settings` objects not being turned into `pydantic` models from `dict` form, which silently worked until now before changes in `gufe` for 1.0, in which `Protocol` now requires `settings` to be an actual `Settings` object on init.
Think I may have fixed the problem you encountered @mikemhenry; see notes in 328aa66. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #254 +/- ##
=======================================
Coverage 82.28% 82.29%
=======================================
Files 26 26
Lines 3066 3079 +13
=======================================
+ Hits 2523 2534 +11
- Misses 543 545 +2 ☔ View full report in Codecov by Sentry. |
Awesome! I see how that used to work just fine by accident as well 🙃 |
@ianmkenney will lead the charge here on getting |
* devtools/conda-envs/alchemiscale-client.yml * devtools/conda-envs/alchemiscale-compute.yml * devtools/conda-envs/alchemiscale-server.yml
Reviewing this next! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is finally ready to go! Thanks @mikemhenry and @ianmkenney for your work on this!
No description provided.