mirror of
https://github.com/quasar/Quasar.git
synced 2026-04-26 07:45:57 +03:00
[GH-ISSUE #346] Client with a long up-time doesn't return the correct up-time #161
Labels
No labels
bug
bug
cant-reproduce
discussion
duplicate
easy
enhancement
help wanted
improvement
invalid
need more info
pull-request
question
wont-add
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Quasar#161
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @yankejustin on GitHub (Aug 22, 2015).
Original GitHub issue: https://github.com/quasar/Quasar/issues/346
Originally assigned to: @MaxXor on GitHub.
Issue Context
I have a machine that I rarely shut down (normally place into a sleep state). The up-time is around 7-9 weeks.
Issue Description
An up-time greater-than ~48-49 days will not correctly be returned to the server; the server will reveal an up-time that is not accurate.
Cause of the issue
Because
Environment.TickCountis anint, it is not capable of functioning after ~48-49 days. It is giving me a negative value for the days due to my up-time.Solution
A functional alternative can be found here. It is a method that is very similar to the methods we use to obtain other information of the client's machine.
@yankejustin commented on GitHub (Aug 22, 2015):
While on the topic of system information, I just wanted to point out this: perhaps the client should append each antivirus name that is not null or empty to a
StringBuilder(using a newline after each valid name) before returning. Might be good to know if a client has multiple anti-viruses installed.@MaxXor commented on GitHub (Aug 23, 2015):
I'm aware of this. For me it's not even returning the correct value when I have my Win8.1 in VM running for 1h. This needs to be fixed asap. I gonna do this.
@yankejustin commented on GitHub (Aug 23, 2015):
Alrighty. :)
@MaxXor commented on GitHub (Aug 23, 2015):
Can you tell me if it's working with your long-uptime system? My longest uptime is just 35 days.^^