Octue

Summary
Use service question UUIDs as analysis IDs to allow log messages for a Google Cloud Run service to be filtered for a given question. Also improve the presentation of error messages forwarded from the responding service to the asking service.

Contents

Enhancements
- [x] Use service question UUIDs as analysis IDs
- [x] Dynamically create exception class in `Service._raise_exception_from_responder` if the received type name is unknown to the asker

Minor improvements
- [x] Use a string UUID for question IDs rather than an integer UUID

<!--- START AUTOGENERATED NOTES --->
<!--- END AUTOGENERATED NOTES --->

Contents

Fixes
- [x] Allow non-JSON-encoded items in GCS metadata (this means a `Datafile` can be instantiated from any GCS object with arbitrary metadata rather than raising an error)

<!--- START AUTOGENERATED NOTES --->
<!--- END AUTOGENERATED NOTES --->

Contents

Breaking changes
- [x] Remove the `sequence` and `cluster` attributes from `Datafile` (they were simply tags with unnecessary special treatment)

Refactoring
- [x] Replace `Dataset.get_file_sequence` with added functionality in `FilterContainer.order_by`

Operations
- [x] Ensure breaking change commits increment minor version number in `mkver.conf`

<!--- START AUTOGENERATED NOTES --->
<!--- END AUTOGENERATED NOTES --->

Contents

Enhancements
- [x] Log purely service-caused exceptions in Google Cloud Run without raising them, always returning a `204` response unless there is an error in Google Cloud Run itself
- [x] Forward service-caused exceptions back to local asker and raise them there, separating the local traceback from the remote traceback

Refactoring
- [x] Use built-in `datetime` POSIX time methods instead of custom-written functions

Testing
- [x] Test Cloud Run `answer_question` function locally (it's already tested remotely in the deployment tests but this doesn't show up in the test coverage)

<!--- START AUTOGENERATED NOTES --->
<!--- END AUTOGENERATED NOTES --->

Contents

Refactoring/fixes
- [x] Combine `Datafile.__init__` with `Datafile.from_cloud` for simpler and more robust interface
- [x] Carry out functionality of former `Datafile.from_cloud` method in `Datafile.__init__` if the `path` parameter is a cloud path

Reversions
- [x] Remove ability to override cloud metadata on locally instantiated `Datafile` during instantiation

<!--- START AUTOGENERATED NOTES --->
<!--- END AUTOGENERATED NOTES --->

Contents

Operations
- [x] Use `conventional-commits` repo for CI checks