Release v0.9.0 #245
Merged
Release v0.9.0 #245
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Check if args are passed to MatchedClient
Add an explicit copy of the requirements file and call the pip install on it earlier so that on modification of the ocs package we don't have to download all dependencies again. This'll improve turn around time when iterating on building OCS Docker images locally for testing during development.
If the Aggregator Agent runs into a permissions error creating the data directories to store .g3 files we should exit the Agent cleanly, stopping the reactor.
Shutdown AggregatorAgent on PermissionError
Reorganize Dockerfile to leverage build cache
This reverts commit 2cbc63c.
Deal gracefully with crossbar not being found
Neded to faciliate MatchedClients instantiated from scripts with their own command line args.
The session.success should be one of (None, True, False), with False indicating that the Operation has exited with error. It's thus appropriate to return False in the case that the Operation code has crashed somehow and raised an exception.
- Eliminates RET_VALS dict in favor of a ResponseCode enum. - Documents ResponseCode and OpCode enums. - Import both enums to ocs. module level in __init__.py
MatchedClient Tests, Rename, and Documentation Updates
Marking these as private may be helpful to users. However the docstrings are useful as reference material for people using clients.
Perhaps we should deprecate the other get_* functions, and eventually remove them.
…=... I have checked all Agent use of this function and I do not expect any surprising side effects.
Docstring already claimed as much ... defaults to [].
This is backwards compatible but should provide a bit more structure for those who want it.
Core updates, prelude for major ocsbow
These won't work in the long description on PyPI. It seems common to simply hardcode these full links to the main branch in this instance.
For the deploy and develop workflows, all steps were previously kept in a single job. This is now split up into multiple jobs, testing first, then building and deploying in a separate job that 'needs' the test job to succeed in order to run.
Build and Deploy to PyPI
Prepare for v0.9.0 release
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR merges the current develop branch into master, which will be marked as the release of v0.9.0. The change log is below. One notable change that requires some attention is in #236, where
MatchedClientis renamed toOCSClient.MatchedClientwill still work for now, but is marked as deprecated. User scripts that useMatchedClientshould be updated to useOCSClient.Change Log
New Features
Documentation Updates
Bug Fixes
Misc.