Details
-
New Feature
-
Status: Resolved
-
Medium
-
Resolution: Done
-
None
-
None
-
None
Description
Now that the registrar is being used in more general code flows there really needs to be a safety mechanism in the form of a timeout just in case the specific expected event never happens.
Attachments
Issue Links
- blocks
-
GENIUS-119 Auto tunnels: race between creation of tun port and bridge ref, port not created
-
- Verified
-
| # | Subject | Branch | Project | Status | CR | V |
|---|---|---|---|---|---|---|
| 70985,10 | add timeout support to DataTreeEventCallbackRegistrar | master | genius | Status: MERGED | +2 | +1 |
| 71585,3 | copy MoreAnswers from yangtools/common/testutils, and intro. Partials | master | infrautils | Status: MERGED | +2 | +1 |
| 71586,1 | introduce TestableScheduledExecutorService (incl. TDD self test) | master | infrautils | Status: ABANDONED | 0 | +1 |
| 71587,5 | introduce TestableDataBroker (with TestableDataBrokerTest) | master | genius | Status: MERGED | +2 | +1 |
| 71588,1 | fix concurrency edge case in DataTreeEventCallbackRegistrar with timeout | master | genius | Status: ABANDONED | 0 | 0 |
| 72146,3 | add timeout support to DataTreeEventCallbackRegistrar | stable/oxygen | genius | Status: MERGED | +2 | +1 |
