Skip to content

drivers: fix utubettl next_event after release - #261

Open
Col-Waltz wants to merge 1 commit into
masterfrom
Col-Waltz/delayed-ttl-after-release
Open

Col-Waltz wants to merge 1 commit into
masterfrom
Col-Waltz/delayed-ttl-after-release

Conversation

@Col-Waltz

Copy link
Copy Markdown
Collaborator

Each task has next_event value in microseconds. At the release of the task without delay this value was again converted to microseconds which resulted in multiplication by 10^6. For task in READY status after release
next_event means time to delete task.

@Col-Waltz
Col-Waltz force-pushed the Col-Waltz/delayed-ttl-after-release branch from ded4e51 to 04c1a39 Compare September 15, 2026 12:27
Comment thread CHANGELOG.md Outdated
Comment thread CHANGELOG.md Outdated
Comment thread t/040-utubettl.t
@Col-Waltz
Col-Waltz force-pushed the Col-Waltz/delayed-ttl-after-release branch from 04c1a39 to fb4b10a Compare September 15, 2026 14:57
Comment thread t/040-utubettl.t Outdated
Comment thread t/040-utubettl.t Outdated
Comment thread t/040-utubettl.t Outdated
Each task has `next_event` value in microseconds. At the
release of the task without delay this value was again
converted to microseconds which resulted in multiplication
by 10^6. For task in `READY` status after release
`next_event` means time to delete task.
@Col-Waltz
Col-Waltz force-pushed the Col-Waltz/delayed-ttl-after-release branch from fb4b10a to 7218200 Compare September 15, 2026 21:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants