-
Task
-
Resolution: Done
-
Major
-
None
-
None
-
False
-
None
-
False
-
-
ElapsedTimeStrategy::hasElapsed is confusing for variety of reasons:
- creating ElapsedTimeStrategy is incomplete if it's not followed by calling hasElapsed
- it doesn't do any wait, while one may can expect it does
- the main task is actually it's side effect to set new upper time limit for the strategy
Refactor it to avoid side affects.
- links to
-
RHEA-2024:129636 Red Hat build of Debezium 2.5.4 release
Since the problem described in this issue should be resolved in a recent advisory, it has been closed.
For information on the advisory (Red Hat build of Debezium 2.5.4 release), and where to find the updated files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHEA-2024:1726