[1003.1(2016/18)/Issue7+TC2 0001781]: Factual error due to mis-wording with regard to timed wait functions?
The following issue has a resolution that has been APPLIED. == https://austingroupbugs.net/view.php?id=1781 == Reported By:dannyniu Assigned To: == Project:1003.1(2016/18)/Issue7+TC2 Issue ID: 1781 Category: Rationale Type: Clarification Requested Severity: Editorial Priority: normal Status: Applied Name: DannyNiu/NJF Organization: User Reference: C181.pdf Section:B.2.8 Realtime >> Rationale for the Monotonic Clock Page Number:3622 Line Number:123529-123533 Interp Status: --- Final Accepted Text:https://austingroupbugs.net/view.php?id=1781#c6563 Resolution: Accepted As Marked Fixed in Version: == Date Submitted: 2023-10-17 08:53 UTC Last Modified: 2023-11-14 10:41 UTC == Summary:Factual error due to mis-wording with regard to timed wait functions? == Issue History Date ModifiedUsername FieldChange == 2023-10-17 08:53 dannyniu New Issue 2023-10-17 08:53 dannyniu Name => DannyNiu/NJF 2023-10-17 08:53 dannyniu Organization => 2023-10-17 08:53 dannyniu User Reference=> C181.pdf 2023-10-17 08:53 dannyniu Section => B.2.8 Realtime >> Rationale for the Monotonic Clock 2023-10-17 08:53 dannyniu Page Number => 3622 2023-10-17 08:53 dannyniu Line Number => 123529-123533 2023-10-17 09:12 dannyniu Note Added: 0006542 2023-11-02 15:18 geoffclare Note Added: 0006563 2023-11-02 15:19 geoffclare Interp Status => --- 2023-11-02 15:19 geoffclare Final Accepted Text => https://austingroupbugs.net/view.php?id=1781#c6563 2023-11-02 15:19 geoffclare Status New => Resolved 2023-11-02 15:19 geoffclare Resolution Open => Accepted As Marked 2023-11-02 15:19 geoffclare Tag Attached: tc3-2008 2023-11-14 10:41 geoffclare Status Resolved => Applied ==
[1003.1(2016/18)/Issue7+TC2 0001781]: Factual error due to mis-wording with regard to timed wait functions?
A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1781 == Reported By:dannyniu Assigned To: == Project:1003.1(2016/18)/Issue7+TC2 Issue ID: 1781 Category: Rationale Type: Clarification Requested Severity: Editorial Priority: normal Status: New Name: DannyNiu/NJF Organization: User Reference: C181.pdf Section:B.2.8 Realtime >> Rationale for the Monotonic Clock Page Number:3622 Line Number:123529-123533 Interp Status: --- Final Accepted Text: == Date Submitted: 2023-10-17 08:53 UTC Last Modified: 2023-11-02 15:18 UTC == Summary:Factual error due to mis-wording with regard to timed wait functions? == -- (0006563) geoffclare (manager) - 2023-11-02 15:18 https://austingroupbugs.net/view.php?id=1781#c6563 -- Change:The pthread_cond_timedwait() function is given a relative timeout; the timeout may represent a deadline for an event. When these functions are given relative timeouts, the timeouts are typically for error recovery purposes and need not be so precise.to:The pthread_cond_timedwait() function is given an absolute timeout; the timeout may represent a deadline for an event. When other functions are given relative timeouts, the timeouts are typically for error recovery purposes and need not be so precise. Issue History Date ModifiedUsername FieldChange == 2023-10-17 08:53 dannyniu New Issue 2023-10-17 08:53 dannyniu Name => DannyNiu/NJF 2023-10-17 08:53 dannyniu Organization => 2023-10-17 08:53 dannyniu User Reference=> C181.pdf 2023-10-17 08:53 dannyniu Section => B.2.8 Realtime >> Rationale for the Monotonic Clock 2023-10-17 08:53 dannyniu Page Number => 3622 2023-10-17 08:53 dannyniu Line Number => 123529-123533 2023-10-17 09:12 dannyniu Note Added: 0006542 2023-11-02 15:18 geoffclare Note Added: 0006563 ==
[1003.1(2016/18)/Issue7+TC2 0001781]: Factual error due to mis-wording with regard to timed wait functions?
The following issue has been RESOLVED. == https://austingroupbugs.net/view.php?id=1781 == Reported By:dannyniu Assigned To: == Project:1003.1(2016/18)/Issue7+TC2 Issue ID: 1781 Category: Rationale Type: Clarification Requested Severity: Editorial Priority: normal Status: Resolved Name: DannyNiu/NJF Organization: User Reference: C181.pdf Section:B.2.8 Realtime >> Rationale for the Monotonic Clock Page Number:3622 Line Number:123529-123533 Interp Status: --- Final Accepted Text:https://austingroupbugs.net/view.php?id=1781#c6563 Resolution: Accepted As Marked Fixed in Version: == Date Submitted: 2023-10-17 08:53 UTC Last Modified: 2023-11-02 15:19 UTC == Summary:Factual error due to mis-wording with regard to timed wait functions? == Issue History Date ModifiedUsername FieldChange == 2023-10-17 08:53 dannyniu New Issue 2023-10-17 08:53 dannyniu Name => DannyNiu/NJF 2023-10-17 08:53 dannyniu Organization => 2023-10-17 08:53 dannyniu User Reference=> C181.pdf 2023-10-17 08:53 dannyniu Section => B.2.8 Realtime >> Rationale for the Monotonic Clock 2023-10-17 08:53 dannyniu Page Number => 3622 2023-10-17 08:53 dannyniu Line Number => 123529-123533 2023-10-17 09:12 dannyniu Note Added: 0006542 2023-11-02 15:18 geoffclare Note Added: 0006563 2023-11-02 15:19 geoffclare Interp Status => --- 2023-11-02 15:19 geoffclare Final Accepted Text => https://austingroupbugs.net/view.php?id=1781#c6563 2023-11-02 15:19 geoffclare Status New => Resolved 2023-11-02 15:19 geoffclare Resolution Open => Accepted As Marked ==
[1003.1(2016/18)/Issue7+TC2 0001781]: Factual error due to mis-wording with regard to timed wait functions?
A NOTE has been added to this issue. == https://www.austingroupbugs.net/view.php?id=1781 == Reported By:dannyniu Assigned To: == Project:1003.1(2016/18)/Issue7+TC2 Issue ID: 1781 Category: Rationale Type: Clarification Requested Severity: Editorial Priority: normal Status: New Name: DannyNiu/NJF Organization: User Reference: C181.pdf Section:B.2.8 Realtime >> Rationale for the Monotonic Clock Page Number:3622 Line Number:123529-123533 Interp Status: --- Final Accepted Text: == Date Submitted: 2023-10-17 08:53 UTC Last Modified: 2023-10-17 09:12 UTC == Summary:Factual error due to mis-wording with regard to timed wait functions? == -- (0006542) dannyniu (reporter) - 2023-10-17 09:12 https://www.austingroupbugs.net/view.php?id=1781#c6542 -- My bad, it (probably should) say: > the pthread_cond_timedwait() function is given an absolute timeout; the timeout may represent a deadline for an event. When *other* functions are given relative timeouts ... typically for error recovery ... Issue History Date ModifiedUsername FieldChange == 2023-10-17 08:53 dannyniu New Issue 2023-10-17 08:53 dannyniu Name => DannyNiu/NJF 2023-10-17 08:53 dannyniu Organization => 2023-10-17 08:53 dannyniu User Reference=> C181.pdf 2023-10-17 08:53 dannyniu Section => B.2.8 Realtime >> Rationale for the Monotonic Clock 2023-10-17 08:53 dannyniu Page Number => 3622 2023-10-17 08:53 dannyniu Line Number => 123529-123533 2023-10-17 09:12 dannyniu Note Added: 0006542 ==
[1003.1(2016/18)/Issue7+TC2 0001781]: Factual error due to mis-wording with regard to timed wait functions?
The following issue has been SUBMITTED. == https://www.austingroupbugs.net/view.php?id=1781 == Reported By:dannyniu Assigned To: == Project:1003.1(2016/18)/Issue7+TC2 Issue ID: 1781 Category: Rationale Type: Clarification Requested Severity: Editorial Priority: normal Status: New Name: DannyNiu/NJF Organization: User Reference: C181.pdf Section:B.2.8 Realtime >> Rationale for the Monotonic Clock Page Number:3622 Line Number:123529-123533 Interp Status: --- Final Accepted Text: == Date Submitted: 2023-10-17 08:53 UTC Last Modified: 2023-10-17 08:53 UTC == Summary:Factual error due to mis-wording with regard to timed wait functions? Description: At the aforementioned line range, this is said: > It was decided that the features of CLOCK_MONOTONIC are not as critical to these functions as they are to pthread_cond_timedwait(). The pthread_cond_timedwait() function is given a relative timeout; the timeout may represent a deadline for an event. When these functions are given relative timeouts, the timeouts are typically for error recovery purposes and need not be so precise. The `pthread_cond_timedwait()` is specified with absolute time-outs, and the later sentence doesn't make sense with the earilier parts of the paragraph. It probably should say: > the *other* function is given an absolute timeout; the timeout may represent a deadline for an event. When other functions are given relative timeouts ... typically for error recovery ... Desired Action: Clarify the intended wording. BTW, my previous reported issue should probably be moved to Issue7+TC2 as well, I forgot to select the correct project. == Issue History Date ModifiedUsername FieldChange == 2023-10-17 08:53 dannyniu New Issue 2023-10-17 08:53 dannyniu Name => DannyNiu/NJF 2023-10-17 08:53 dannyniu Organization => 2023-10-17 08:53 dannyniu User Reference=> C181.pdf 2023-10-17 08:53 dannyniu Section => B.2.8 Realtime >> Rationale for the Monotonic Clock 2023-10-17 08:53 dannyniu Page Number => 3622 2023-10-17 08:53 dannyniu Line Number => 123529-123533 ==
