search

cygnusxi / hfm-net

Automatically exported from code.google.com/p/hfm-net
2 stars 0 forks source link

Slowly decreasing credit and wrong project recognized #178

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
- If F5 was pressed repeatedly the client information displayed alternated
between all zeros and the current client information but with a
continuously decreasing credits and consequently PPD. It looks like credit
was wrong (too high, about 124k points) and then it was slowly decreasing
to the correct value.

When the values displayed were zero the credit displayed was 25403 and when
the client information was filled the above-expected credit values (about
124k points and decreasing) were displayed.

At the time I noticed this issue the server was down so the finished bigadv
unit (25403 points with kfactor = 2.0) couldn't be sent and another unit
(475 points with kfactor = 2.1) was being processed. Notice that the wrong
project was recognized and therefore this can be a dupe of issue 153 which
was fixed on version 0.4.9.154.

What is the expected output? What do you see instead?
Every time F5 (refresh) is pressed the client data should be refreshed
(updated). The credits and PPD displayed should be almost constant because
the source data is not changing.

What version of the product are you using? On what operating system?
- Windows 7 Ultimate 64 bit 6.1.7600 (English w/ Portuguese language pack)
- HFM.NET v0.4.8 revision 121
- vmware player 3.0.0 build 203739

Please provide any additional information below.
- Files attached.
- When I repeatedly press F5 in the new version (0.4.9.154) the information
does not alternate to zeros, but I don't know if the decreasing credits
would happen if other (unknown?) criteria were met.

Original issue reported on code.google.com by carlos.c...@gmail.com on 12 Mar 2010 at 6:21

Attachments:

GoogleCodeExporter commented 8 years ago 
Thanks for the logs carlos... both issues should be fixed in Revision 154.  
However,
please advise if you see this behavior again.

I'll leave this issue open for at least 7 days and then just mark it WontFix if 
it
cannot be reproduced again.

Just FYI, for the future... when submitting log files and screen shots, please 
also
send me the HFM.log file.

Original comment by harlam357 on 15 Mar 2010 at 4:07

GoogleCodeExporter commented 8 years ago 
Already Fixed in Revision 154.

Original comment by harlam357 on 28 Mar 2010 at 8:31

GoogleCodeExporter commented 8 years ago

Original comment by harlam357 on 23 Mar 2012 at 4:32