Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Confusing CE behavior in case of creating a rule for an activity that doesn't exist #1528

Open
cartermak opened this issue Aug 12, 2024 · 0 comments
Labels
bug Something isn't working clipper Requests from the Europa Clipper project

Comments

@cartermak
Copy link
Member

Checked for duplicates

No - I haven't checked

Is this a regression?

No - This is a new bug

Version

2.11.2

Describe the bug

Small note for error handling behavior. No need for immediate resolution.

When uploading expansion rules and sets via the API, Aerie will allow the user to create an expansion rule in a model where an activity type doesn't exist. The new rule appears in the Aerie UI under the "Rules" page (with the specified parcel and mission model IDs), and the UI doesn't present any errors unless you go into "Edit" mode for the rule, at which point the editor gives an error for the missing ActivityType definition.

When trying to create a set via the API, we get a "No activity with name: in mission model with id:" error. When trying to create via the Aerie UI, it's confusing because the rule appears under "Rules" but it isn't available to select when creating the set.

Reproduction

Logs

No response

System Info

Aerie 2.11.2 on Clipper cloud deployment. API interactions via Aerie-CLI.

Severity

Minor

@cartermak cartermak added the bug Something isn't working label Aug 12, 2024
@parkerabercrombie parkerabercrombie added the clipper Requests from the Europa Clipper project label Aug 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working clipper Requests from the Europa Clipper project
Projects
Status: Todo
Development

No branches or pull requests

2 participants