id,summary,reporter,owner,description,type,status,milestone,component,version,severity,resolution,keywords,cc
2447,get_due_time returns incorrect due_time if boost::date_time resolution is nanoseconds,rwightman@…,Anthony Williams,"There is a bug in the calculation of due_time (line 343 in thread.cpp) where the calculation to add the fractional seconds will always add 0 if the boost::date_time library has been configured to use nanosecond resolution.

The integer division of hundred_nanoseconds_in_one_second/target_time.abs_time.time_of_day().ticks_per_second() will be 0 when date_time uses nanosecond resolution since the denominator will be 10**9 and always greater than the numerator which is 10**7. At the default date_time resolution of 10**6 this works fine.

Facilities like boost::condition::timed_wait which rely on this function will not block for the desired amount of time if the wait time is < 1 sec.

This issue has been present since 1.35.0.
",Bugs,closed,Boost 1.41.0,thread,Boost 1.40.0,Problem,fixed,,