old name    new name
---         ---
ready       created
executing   submitted
?           in_progress

removed EXPOSE cmd in frontend's Dockerfile.dev and added empty dependencies to CI stages that don't need artifacts for efficiency

Daniel Lyons authored 4 years ago and Nathan Hertz committed 4 years ago

Added the ability to compare capability executions by their creation timestamp; made it so encountering exceptions when receiving messages does not block the system

Charlotte Hausman authored 4 years ago and Nathan Hertz committed 4 years ago

Messaging system is now running on a more robust foundation:
- `kombu` package for AMQP networking
- New Messenger and Router objects
- New message format
- Easy-to-use callback subscribing
- Can now get messages anywhere in the system easily and send replies back easily

Nathan Hertz authored 4 years ago and Nathan Hertz committed 4 years ago

existing executions cannot be deleted (they must be disabled instead,
which will have to be implemented)

Refactored execution management logic out of `CapabilityService` into a new class `ExecutionManager`

`CapabilityService.create_request` instead of duplicating that logic
within the view; changed tests and mocks to go along with the changes

forgot to add in the previous MR

Added two new Pyramid views, the first of the capability request views: `view_capability_request` and `create_capability_request`

added views directory that will hold logic for views

null.cap with arguments

object and create a request from there

conflicts and circular imports

helper.py; added from_string constructor to CapabilityStepType