This repository has been archived by the owner on Jul 13, 2023. It is now read-only.
Add tests for the Rust connection handling #1060
Comments
9 tasks
bbangert
added a commit
that referenced
this issue
Jan 18, 2018
Adds the following functionality for capability parity: - Skip sending messages if the message is expired - Properly handle legacy messages in a message stream - Set appropriate flags for a uaid not found in the db - Always return a timestamp when querying into timestamp messages - Send messages in the order they're retrieved from the db - Accept messages from endpoint while waiting for acks - Don't save TTL:0 messages in the db if the client fails to ack them - Allow TTL:None from endpoint and treat as TTL:0 - Closes #1060
bbangert
added a commit
that referenced
this issue
Jan 18, 2018
Adds the following functionality for capability parity: - Skip sending messages if the message is expired - Properly handle legacy messages in a message stream - Set appropriate flags for a uaid not found in the db - Always return a timestamp when querying into timestamp messages - Send messages in the order they're retrieved from the db - Accept messages from endpoint while waiting for acks - Don't save TTL:0 messages in the db if the client fails to ack them - Allow TTL:None from endpoint and treat as TTL:0 - Closes #1060
bbangert
added a commit
that referenced
this issue
Jan 18, 2018
Adds the following functionality for capability parity: - Skip sending messages if the message is expired - Properly handle legacy messages in a message stream - Set appropriate flags for a uaid not found in the db - Always return a timestamp when querying into timestamp messages - Send messages in the order they're retrieved from the db - Accept messages from endpoint while waiting for acks - Don't save TTL:0 messages in the db if the client fails to ack them - Allow TTL:None from endpoint and treat as TTL:0 Closes #1060
bbangert
added a commit
that referenced
this issue
Jan 18, 2018
Adds the following functionality for capability parity: - Skip sending messages if the message is expired - Properly handle legacy messages in a message stream - Set appropriate flags for a uaid not found in the db - Always return a timestamp when querying into timestamp messages - Send messages in the order they're retrieved from the db - Accept messages from endpoint while waiting for acks - Don't save TTL:0 messages in the db if the client fails to ack them - Allow TTL:None from endpoint and treat as TTL:0 Closes #1060
bbangert
added a commit
that referenced
this issue
Jan 18, 2018
Adds the following functionality for capability parity: - Skip sending messages if the message is expired - Properly handle legacy messages in a message stream - Set appropriate flags for a uaid not found in the db - Always return a timestamp when querying into timestamp messages - Send messages in the order they're retrieved from the db - Accept messages from endpoint while waiting for acks - Don't save TTL:0 messages in the db if the client fails to ack them - Allow TTL:None from endpoint and treat as TTL:0 Closes #1060
bbangert
added a commit
that referenced
this issue
Jan 18, 2018
Adds the following functionality for capability parity: - Skip sending messages if the message is expired - Properly handle legacy messages in a message stream - Set appropriate flags for a uaid not found in the db - Always return a timestamp when querying into timestamp messages - Send messages in the order they're retrieved from the db - Accept messages from endpoint while waiting for acks - Don't save TTL:0 messages in the db if the client fails to ack them - Allow TTL:None from endpoint and treat as TTL:0 Closes #1060
bbangert
added a commit
that referenced
this issue
Jan 18, 2018
Adds the following functionality for capability parity: - Skip sending messages if the message is expired - Properly handle legacy messages in a message stream - Set appropriate flags for a uaid not found in the db - Always return a timestamp when querying into timestamp messages - Send messages in the order they're retrieved from the db - Accept messages from endpoint while waiting for acks - Don't save TTL:0 messages in the db if the client fails to ack them - Allow TTL:None from endpoint and treat as TTL:0 Closes #1060
bbangert
added a commit
that referenced
this issue
Jan 18, 2018
Adds the following functionality for capability parity: - Skip sending messages if the message is expired - Properly handle legacy messages in a message stream - Set appropriate flags for a uaid not found in the db - Always return a timestamp when querying into timestamp messages - Send messages in the order they're retrieved from the db - Accept messages from endpoint while waiting for acks - Don't save TTL:0 messages in the db if the client fails to ack them - Allow TTL:None from endpoint and treat as TTL:0 Closes #1060
bbangert
added a commit
that referenced
this issue
Jan 18, 2018
Adds the following functionality for capability parity: - Skip sending messages if the message is expired - Properly handle legacy messages in a message stream - Set appropriate flags for a uaid not found in the db - Always return a timestamp when querying into timestamp messages - Send messages in the order they're retrieved from the db - Accept messages from endpoint while waiting for acks - Don't save TTL:0 messages in the db if the client fails to ack them - Allow TTL:None from endpoint and treat as TTL:0 Closes #1060
10 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The Rust connection handler needs testing, both some unit tests, and the application of the integration testing.
The text was updated successfully, but these errors were encountered: