When tasks "complete" ie. show 100%, they continue in the running state for several minutes.

I found out they go from 30% to 100% back down to 31% and so on... It happens multiple times per tasks.
I think it's a small bug, but the tasks will finish if you let them run :)

---

Same here;)

Unfortunately this bug triggers the BOINC client to fetch work unnecessarily
(especially if you run with no cache on purpose)
Please fix this if possible

May be we catch the bug. :)

May be we catch the bug. :)

Are you talking about this commit? Well I'm no C++ programmer but to me that does not look like a proper fix. Has it been tested?

To hard to cache it ...

Got the 100% bug on some tasks.
corona_Eprot_v1_run_2_nb3di_109561_4_1

On Linux, can look at BOINC slots files. Slot number may be different. Hex 0a is a new line.

while :
do
hexdump -C /var/lib/boinc-client/slots/2/docking_out.progress
sleep 30
done
00000000  30 2e 31 32 38 32 35 37 0a 0a 0a  |0.128257...|
00000000  30 2e 31 33 32 0a 35 37 0a 0a 0a  |0.132.57...|
00000000  30 2e 31 33 36 32 37 33 0a 0a 0a  |0.136273...|

Looks like CmDock seek to beginning of file and wrote 0.132 which is fewer characters. Then, I guess BOINC wrapper read the last line containing a number as 57, which is 5700% if BOINC didn't limit max number of 100%.

The extra new lines ( 0a 0a ) is when it lost 2 digits as the number went from 0.00999999 to 0.0111111, then to 0.111111.

For now, can temporary override the progress for some time, mostly just 1 minute then it goes back to showing actual progress.
printf "0.5\n" > /var/lib/boinc-client/slots/2/docking_out.progress

Would like to see a fix. Preferably can write the same number of characters "0.13200000". I guess a possibly easier fix is to add spaces to clear away extra digits "0.132 ".

Thanks sam6861!

Hopefully this helps SiDock fix this.

When will this issue be addressed? The pb is pointless if it is stuck at 100% for the majority of its runtime. If the bug pointed out below will already solve this issue, could you please implement it? Thanks

Hello! :)

When will this issue be addressed? The pb is pointless if it is stuck at 100% for the majority of its runtime. If the bug pointed out below will already solve this issue, could you please implement it? Thanks

We reported about problem and offer solution (slightly different, but for this case).

Is this solution you are talking about already implemented in the latest app version or do I need to act on the client side? I do still have this issue on my Win10 host regularly.

Hello folks! The new version of the application should be released in the next two or three weeks.

Great! Thanks for the update :)

Hello folks! The new version of the application should be released in the next two or three weeks.

Thanks!

Hello folks! The new version of the application should be released in the next two or three weeks.

Any news on this?

Dear colleagues,

we are working constantly on future relleases of the software to be more effective and user friendly. To release the official version for MacOS we need developer with license to sign
the release.

All the best,

Crtomir

Any progress with this?

Since there's not currently a Mac OS version of the CurieMarieDock on BOINC + zipped input, checkpoints and progress bar application https://www.sidock.si/sidock/apps.php is it essential to wait for the Mac OS version?

Thanks!

Just wanted to report that I do still experience this issue with the latest Windows app.

However, it seems that I didn't look closely enough. During the task, the progress bar might suddenly jump to a 100% and stay there for several seconds up to a few minutes and then usually reverts back to the normal progress. This can happen several times per task but now with this behavior, the progress bar issue seems somewhat alleviated. Any way to bring the progress bar behavior all the way back to its normal behavior? Thx anyway in the meantime for the current solution.