-
Notifications
You must be signed in to change notification settings - Fork 52
Fixed a bug in the channel that was not detecting out of seq messages #663
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
Conversation
This pull request was exported from Phabricator. Differential Revision: D79044526 |
…pytorch-labs#663) Summary: This was because we need to check for out of seq messages only if it is not the first message of the connection (even if it is for subsequent sessions). Differential Revision: D79044526
9717486
to
bbc9258
Compare
…pytorch-labs#663) Summary: This was because we need to check for out of seq messages only if it is not the first message of the connection (even if it is for subsequent sessions). Differential Revision: D79044526
bbc9258
to
f0b8b45
Compare
This pull request was exported from Phabricator. Differential Revision: D79044526 |
…pytorch-labs#663) Summary: Pull Request resolved: pytorch-labs#663 This was because we need to check for out of seq messages only if it is not the first message of the connection (even if it is for subsequent sessions). Differential Revision: D79044526
f0b8b45
to
ab59d0e
Compare
This pull request was exported from Phabricator. Differential Revision: D79044526 |
…pytorch-labs#663) Summary: Pull Request resolved: pytorch-labs#663 1) This was because we need to check for out of seq messages only if it is not the first message of the connection (even if it is for subsequent sessions). 2) There was another bug in which we don't exactly mutate session state into the session manager correctly. We clone the session state and don't mutate. This particular case is NOT taken care of the tcp_reconnect test: in this test, we shut down the entire server and reenter the listen loop thereby resetting the entire session manager. The only way we can test (2) is if we can disconnect the underlying connection and reconnect altogether while the listen stays alive. Differential Revision: D79044526
ab59d0e
to
6682e28
Compare
…pytorch-labs#663) Summary: 1) This was because we need to check for out of seq messages only if it is not the first message of the connection (even if it is for subsequent sessions). 2) There was another bug in which we don't exactly mutate session state into the session manager correctly. We clone the session state and don't mutate. This particular case is NOT taken care of the tcp_reconnect test: in this test, we shut down the entire server and reenter the listen loop thereby resetting the entire session manager. The only way we can test (2) is if we can disconnect the underlying connection and reconnect altogether while the listen stays alive. Differential Revision: D79044526
6682e28
to
2a97f6d
Compare
This pull request was exported from Phabricator. Differential Revision: D79044526 |
2a97f6d
to
fd2696c
Compare
…pytorch-labs#663) Summary: 1) This was because we need to check for out of seq messages only if it is not the first message of the connection (even if it is for subsequent sessions). 2) There was another bug in which we don't exactly mutate session state into the session manager correctly. We clone the session state and don't mutate. This particular case is NOT taken care of the tcp_reconnect test: in this test, we shut down the entire server and reenter the listen loop thereby resetting the entire session manager. The only way we can test (2) is if we can disconnect the underlying connection and reconnect altogether while the listen stays alive. Differential Revision: D79044526
fd2696c
to
d6d8df2
Compare
…pytorch-labs#663) Summary: 1) This was because we need to check for out of seq messages only if it is not the first message of the connection (even if it is for subsequent sessions). 2) There was another bug in which we don't exactly mutate session state into the session manager correctly. We clone the session state and don't mutate. This particular case is NOT taken care of the tcp_reconnect test: in this test, we shut down the entire server and reenter the listen loop thereby resetting the entire session manager. The only way we can test (2) is if we can disconnect the underlying connection and reconnect altogether while the listen stays alive. Differential Revision: D79044526
This pull request was exported from Phabricator. Differential Revision: D79044526 |
…pytorch-labs#663) Summary: Pull Request resolved: pytorch-labs#663 1) This was because we need to check for out of seq messages only if it is not the first message of the connection (even if it is for subsequent sessions). 2) There was another bug in which we don't exactly mutate session state into the session manager correctly. We clone the session state and don't mutate. This particular case is NOT taken care of the tcp_reconnect test: in this test, we shut down the entire server and reenter the listen loop thereby resetting the entire session manager. The only way we can test (2) is if we can disconnect the underlying connection and reconnect altogether while the listen stays alive. Differential Revision: D79044526
d6d8df2
to
b0a21c7
Compare
This pull request was exported from Phabricator. Differential Revision: D79044526 |
…pytorch-labs#663) Summary: Pull Request resolved: pytorch-labs#663 1) This was because we need to check for out of seq messages only if it is not the first message of the connection (even if it is for subsequent sessions). 2) There was another bug in which we don't exactly mutate session state into the session manager correctly. We clone the session state and don't mutate. This particular case is NOT taken care of the tcp_reconnect test: in this test, we shut down the entire server and reenter the listen loop thereby resetting the entire session manager. The only way we can test (2) is if we can disconnect the underlying connection and reconnect altogether while the listen stays alive. Differential Revision: D79044526
ed44d80
to
9576e50
Compare
…pytorch-labs#663) Summary: 1) This was because we need to check for out of seq messages only if it is not the first message of the connection (even if it is for subsequent sessions). 2) There was another bug in which we don't exactly mutate session state into the session manager correctly. We clone the session state and don't mutate. This particular case is NOT taken care of the tcp_reconnect test: in this test, we shut down the entire server and reenter the listen loop thereby resetting the entire session manager. The only way we can test (2) is if we can disconnect the underlying connection and reconnect altogether while the listen stays alive. Differential Revision: D79044526
…pytorch-labs#663) Summary: 1) This was because we need to check for out of seq messages only if it is not the first message of the connection (even if it is for subsequent sessions). 2) There was another bug in which we don't exactly mutate session state into the session manager correctly. We clone the session state and don't mutate. This particular case is NOT taken care of the tcp_reconnect test: in this test, we shut down the entire server and reenter the listen loop thereby resetting the entire session manager. The only way we can test (2) is if we can disconnect the underlying connection and reconnect altogether while the listen stays alive. Differential Revision: D79044526
9576e50
to
2162ba4
Compare
This pull request was exported from Phabricator. Differential Revision: D79044526 |
…pytorch-labs#663) Summary: Pull Request resolved: pytorch-labs#663 Now, we break the session if we detect an out of seq message. This was disabled because of a failing test. But it turns out the test is wrong. The test stops NetRx but that should kill NetTx because netrx failure results in the entire session state nullified on the receiver side. Differential Revision: D79044526
2162ba4
to
7ad4261
Compare
This pull request was exported from Phabricator. Differential Revision: D79044526 |
…pytorch-labs#663) Summary: Pull Request resolved: pytorch-labs#663 Now, we break the session if we detect an out of seq message. This was disabled because of a failing test. But it turns out the test is wrong. The test stops NetRx but that should kill NetTx because netrx failure results in the entire session state nullified on the receiver side. Differential Revision: D79044526
4c50da7
to
b79a68d
Compare
…pytorch-labs#663) Summary: Now, we break the session if we detect an out of seq message. This was disabled because of a failing test. But it turns out the test is wrong. The test stops NetRx but that should kill NetTx because netrx failure results in the entire session state nullified on the receiver side. Reviewed By: pzhan9, mariusae Differential Revision: D79044526
b79a68d
to
e0e7fe2
Compare
…pytorch-labs#663) Summary: Now, we break the session if we detect an out of seq message. This was disabled because of a failing test. But it turns out the test is wrong. The test stops NetRx but that should kill NetTx because netrx failure results in the entire session state nullified on the receiver side. Reviewed By: pzhan9, mariusae Differential Revision: D79044526
This pull request was exported from Phabricator. Differential Revision: D79044526 |
e0e7fe2
to
9297e9e
Compare
…pytorch-labs#663) Summary: Pull Request resolved: pytorch-labs#663 Now, we break the session if we detect an out of seq message. This was disabled because of a failing test. But it turns out the test is wrong. The test stops NetRx but that should kill NetTx because netrx failure results in the entire session state nullified on the receiver side. Reviewed By: pzhan9, mariusae Differential Revision: D79044526
…pytorch-labs#663) Summary: Pull Request resolved: pytorch-labs#663 Now, we break the session if we detect an out of seq message. This was disabled because of a failing test. But it turns out the test is wrong. The test stops NetRx but that should kill NetTx because netrx failure results in the entire session state nullified on the receiver side. Reviewed By: pzhan9, mariusae Differential Revision: D79044526
This pull request was exported from Phabricator. Differential Revision: D79044526 |
9297e9e
to
0dd142d
Compare
This pull request has been merged in 434137a. |
Summary:
This was because we need to check for out of seq messages
only if it is not the first message of the connection (even if it is
for subsequent sessions).
Differential Revision: D79044526