Mythicaeda

Results 33 issues of Mythicaeda

* **Tickets addressed:** Closes #1441 * **Review:** By commit * **Merge strategy:** Merge (no squash) ## Description Adds a new suite of tests for the case when there are two...

test

* **Tickets addressed:** Hotfix * **Review:** By commit * **Merge strategy:** Merge (no squash) ## Description This PR removes the pre-v2.8.0 Hasura migrations as well as the v2.8.0 database merge...

refactor
database

We don't have any DB tests in the plan collaboration test suite that explicitly test the "merge two sibling plans one after another" case. Since all of activity directives are...

test

Currently, if Aerie-Dev fails a DB migration, we don't know about it until someone happens to stumble across it. It should instead notify us that it failed so that we...

ci
deployment

ActivityExpression has an override for `matches` that translates a `SchedulingActivityDirective` into an `ActivityInstance` before calling another override. As part of that, it sets the interval of the instance to `Interval.between(act.startOffset(),...

scheduling
investigate

Follow-up to #971. Summary taken from "Future Work" of #1141: As mentioned in #971, part of the reason the bug was occurring was due to the structure of this part...

refactor
scheduling

Prerequisite Issue: #928 When a mission model is uploaded, we need to extract the subsystems and put them in the `tags` table, as well as associate ActivityTypes with their subsystems....

feature
soon

It should be called `simulation_request`. [The poor naming choice has lead to UI bugs](https://github.com/NASA-AMMOS/aerie-ui/issues/1121). Rename all columns that refer to this table. Also Rename `simulation`/`simulation_template` to `simulation_specification`/`simulation_specification_template` for consistency/clarity

breaking change
refactor

Follow up from a discussion with @DavidLegg. Having mission models implement `AutoClosable` would allow them to clean up, for example, network resources or, specific to our discussion, save off a...

merlin framework

The `@Export.Parameter` annotation should not be permitted on `static` fields. Permitting Activity Parameters to be static can lead to activities running with parameters that they were not assigned to. The...

bug