You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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
The text was updated successfully, but these errors were encountered: