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

SB functional test - limit exceeded still sends to other pipes #1826

Closed
skliper opened this issue Aug 16, 2021 · 0 comments · Fixed by #1876 or #1885
Closed

SB functional test - limit exceeded still sends to other pipes #1826

skliper opened this issue Aug 16, 2021 · 0 comments · Fixed by #1876 or #1885
Assignees
Milestone

Comments

@skliper
Copy link
Contributor

skliper commented Aug 16, 2021

Is your feature request related to a problem? Please describe.
Missing functional checks that a limit reached on one pipe will still send to the others (requirement).

Describe the solution you'd like
Add a check that a message limit reached on one pipe will still transmit to another
Add a check that a pipe full reached on one pipe will still transmit to another

Describe alternatives you've considered
None

Additional context
None

Requester Info
Jacob Hageman - NASA/GSFC

@skliper skliper added this to the 7.0.0 milestone Aug 16, 2021
@jphickey jphickey self-assigned this Aug 17, 2021
jphickey added a commit to jphickey/cFE that referenced this issue Aug 24, 2021
Add test cases to confirm that when multiple pipes are subscribed
to the same message ID, that:

1. Broadcasting (transmit side) is successful even if some of the pipes
   are not deliverable.
2. MsgLimit (from subscription) and PipeDepth (from pipe create) are honored.
3. If some pipes are undeliverable for any reason, delivery to open pipes is
   not affected.
astrogeco added a commit that referenced this issue Aug 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants