Build: #228 failed Changes by Florian Schmaus <flo@geekplace.eu>
Code commits
Smack (4.4)
-
Florian Schmaus <flo@geekplace.eu> 881ebe731d720e407ef626d67ae35c6b02d6c60d
[core] Fix typo in javadoc
-
Florian Schmaus <flo@geekplace.eu> 1f5326abb215a7a3c593f3bbaf26607a62d07f05
[core] Inline waitForConditionOrConnectionException
Using any of the two methods is error prone, see 0e0c0a4093ee ("[tcp]
Fix handling in connection exceptions when resuming a stream"), as one
can easily forget to check for connection exceptions after it
returned. There are also no longer any call sites of those methods.
Let's inline both variants of this method. -
Florian Schmaus <flo@geekplace.eu> 0e0c0a4093eeda85c76aafc9497bd357ec12e26c
[tcp] Fix handling in connection exceptions when resuming a stream
Smack would previous run into "assert smResumptionFailed != null;" at
line 407, since if a connection exception was encountered,
waitForConditionOrConnectionException() would return, but we afterards
just assumed that either SM resumption was successful or not.