-
Notifications
You must be signed in to change notification settings - Fork 4
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
Combine 0.2.x branch with master #124
Conversation
…bmiport-envvar-55 Singularity from notebook 56 bmiport envvar 55
Created GitHub release from wrong branch
By manual cherry-pick of 6661451
By merging changes in https://github.com/eWaterCycle/grpc4bmi/pull/69/files into 0.2.x branch
Extra volumes 0.2.x
This reverts commit 8c2a915.
This reverts commit 9189b46.
0.2.x: Handle when model value is too big for message
Added sleep to BmiClientSingularity
Seems singularity version on cartesius.surfsara.nl no longer accepts parent env. Fixes #84
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.
Great to merge these diverging branches! Since most of the changes have already been reviewed separately, in this review I tried to focus on how this merge affects the user experience.
Tried locally with example marrmot case, with apptainer, docker, and through ewatercycle. All work. It would be helpful to have a couple of example calls in the documentation that work out of the box by copy-pasting in https://grpc4bmi.readthedocs.io/en/bmi2/api/grpc4bmi.bmi_client_docker.html. I was also able to successfully run the ewatercycle test suite with this branch (using eWaterCycle/ewatercycle#339).
How do we envision future development? Will we only maintain the main branch from now on? I think it might be helpful to write something like a changelog entry about this merge, and what it means for legacy bmi containers.
docs/server/python.rst
Outdated
$ run-bmi-server --bmi-version 0.2 --name mypackage.mymodule.MyLegacyBmi | ||
|
||
The functions only present in v0.2 will not be callable. |
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.
So this means that people that were installing grpc4bmi with the v0.2 bmi will loose this functionality when they change over to the new master branch release. Should we somehow provide update instructions for them?
One option is to make a last release of the v0.2 branch with a message that this will be the last release and people are encouraged to update to the latest version of grpc4bmi and remove the deprecated bmi calls in their models
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.
Also, is there a diff somewhere to see which functions differ between bmi v2 and v0.2?
|
SonarCloud Quality Gate failed. |
The 0.2.x branch:
The master branch
This PR combines the v0.2.x branch with master.
Also