Changed workflow temp location from `$(HOME)/workspaces_tmp` (`/root/workspaces_tmp` in the container) to `/tmp/workspaces_tmp`

Daniel Lyons authored 3 years ago and Nathan Hertz committed 3 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

Make the workflow_info and workflow_service singletons the same way their upper-division peers are in the capability service

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

- Datafetcher runs in container and retrieves data
- Delivery can deliver data to a directory within the container

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

Previously, it ran the default, ingress mode, which is used for swarm routing mesh
This makes services available to every service running in the swarm regardless of the node.
Because of this, we ran into port-in-use errors.

- simplified branch and image tagging in CI
- minor cleanup of CI scripts

 - Add columns to tables workflow_requests and capability_requests
 - Make the updated_at column auto-update in the database for both
 - Use in the __repr__ method for Python for human-friendliness

Manually verified that the timezone manipulations were correct

 - REST API for Workflows is significantly revamped
 - REST API is now documented with Swagger
 - JSON Arguments to workflows and capabilities are now saved in Postgres properly

This reverts commit 68320db2.

Updated `testing/utils/conftest.py` with reliable mock data that can be used in tests; added `shared/workspaces` tests

WS-101: figured out how to write pytest tests. test_load_engine works, stubs for other tests created

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)

and capability request)

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