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
It was used in the test which was removed since the claimed spec (RTL2f) is vague on this ("A test should exist to ensure that resumed is always false when a channel first becomes ATTACHED, it is true when the channel is ATTACHED following a successful connection recovery, and is false when the channel is ATTACHED following a failed connection recovery"), and the test wasn't testing connection recovery mentioned. I've created an issue in the specs repo for this.
It was introduced as part of no-connection-serial PR. But was erroneously removed during review process.
It was used in the test which was removed since the claimed spec (RTL2f) is vague on this ("A test should exist to ensure that resumed is always false when a channel first becomes ATTACHED, it is true when the channel is ATTACHED following a successful connection recovery, and is false when the channel is ATTACHED following a failed connection recovery"), and the test wasn't testing connection recovery mentioned. I've created an issue in the specs repo for this.
┆Issue is synchronized with this Jira Task by Unito
The text was updated successfully, but these errors were encountered: