Bug#983290: worklog: summary prints 0.0 even when no work done

Sorry, my description of what is expected was incorrect. I think just looking at the code shows that the current code is wrong, since the first time through the loop, "seconds" is uninitialized, which is incorrect. A better set of steps to reproduce: /usr/bin/worklog ~/worklog/projects time.

Bug#983290: worklog: summary prints 0.0 even when no work done

Package: worklog Version: 2.1-1 Followup-For: Bug #983290 Sorry, I missed your reply. I can recreate this trivially by using an empty directory and having a valid projects file with more than one project letter in it and running worklog and then immediately exiting. It will display the first

Bug#983290: worklog: summary prints 0.0 even when no work done

Package: worklog Version: 2.1-1 Followup-For: Bug #983290 github pull request here: https://github.com/atsb/worklog/pull/1 -- System Information: Debian Release: 11.7 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'oldstable-proposed

Bug#983290: worklog: summary prints 0.0 even when no work done

Hi, Could you please submit a debdiff or provide a bit more insight? I cannot reproduce this locally. Thanks.

Bug#983290: worklog: summary prints 0.0 even when no work done

Package: worklog Version: 2.1 Severity: minor Tags: patch worklog.c: In function ‘exit_handler’: worklog.c:365:7: warning: ‘seconds’ may be used uninitialized in this function [-Wmaybe-uninitialized] if(!seconds) Because seconds is unitialized, the summary always prints incorrectly, always