We don't really distinguish between 2: CLOSING and 3: CLOSED in lib/socket.react.js, but don't think it hurts to add this here.
Details
Details
Diff Detail
Diff Detail
- Repository
- rCOMM Comm
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
native/cpp/CommonCpp/grpc/ClientGetReadReactor.cpp | ||
---|---|---|
25–27 ↗ | (On Diff #9333) | Should this mutex also stay locked for the TryCancel call? |
native/cpp/CommonCpp/grpc/ClientGetReadReactor.cpp | ||
---|---|---|
25–27 ↗ | (On Diff #9333) | You're right, this could cause issues. I was setting readyState before the call to TryCancel to ensure that readyState would be set to 2: CLOSING before 3: CLOSED. However, the mutex stays locked during the TryCancel call, and if TryCancel is blocked on OnDone (I really doubt that it is, but I haven't explicitly checked), we would have a deadlock. Since we never consider the distinction between 2: CLOSING and 3: CLOSED, it seems like the safest thing to do is just get rid of this diff? |
native/cpp/CommonCpp/grpc/ClientGetReadReactor.cpp | ||
---|---|---|
25–27 ↗ | (On Diff #9333) | You can just wrap it in a block |