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

Verify Termination Behavior of Cookie Cutter Applications #123

Open
sklose opened this issue May 28, 2020 · 0 comments
Open

Verify Termination Behavior of Cookie Cutter Applications #123

sklose opened this issue May 28, 2020 · 0 comments
Labels
bug Something isn't working M-core This issue is related to the core module P3 Priority 3
Milestone

Comments

@sklose
Copy link
Collaborator

sklose commented May 28, 2020

If any input source of a Cookie Cutter Application throws an Error from within the start function / the message iterator then the entire Application should shut down. This is potentially not working in version 1.2 with Concurrent Message Processor and multiple input sources. Let's add unit tests that verify this behavior for all permutations of

Modes

  1. Serial
  2. Concurrent
  3. RPC

Input Sources

  1. Single
  2. Multiple

Error Handling Modes

  1. LogAndContinue
  2. LogAndFail
@sklose sklose added the bug Something isn't working label May 28, 2020
@sklose sklose added this to the 1.3 milestone May 28, 2020
@sklose sklose modified the milestones: 1.3, 1.4 Oct 13, 2020
@plameniv plameniv added M-core This issue is related to the core module P3 Priority 3 labels Jul 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working M-core This issue is related to the core module P3 Priority 3
Development

No branches or pull requests

2 participants