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

Error propagation logic prints error with run number microservice #230

Closed
PawelPlesniak opened this issue Aug 29, 2024 · 2 comments
Closed

Comments

@PawelPlesniak
Copy link
Contributor

When running with the run number usvc, statements of missing mandatory parameters are still supplied.
Giovanna ran with a config on CRP4 and got messages about missing arguments. Need to get a handle to check if the run number service is being used and amend the mandatory arguments as necessary in here

@plasorak
Copy link
Collaborator

plasorak commented Sep 2, 2024

I would advocate using the server-side controller to do that. It's a bit more complicated but that way all the sequences come from the configuration.

@plasorak
Copy link
Collaborator

This was an artefact of the old implementation of the FSM sequences. See: #285

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants