You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure what's going on here, but for some reason the graphing javascript is not working when passed the timespans as calculated by timespans.append(int(current_delta.total_seconds() / 3600)). When I remove the int() from the calculation, there are graph bars appearing, however they're showing negative intervals for the amount of time, whether this is calculated from the seconds, or the hours. So it's not some sort of overflow due to the number of seconds... Not sure what's going on here, but things were working not that long ago, so it can't be too major of an issue.
The text was updated successfully, but these errors were encountered:
Whatever is going on, there is definitely something, when calculated with int(), that is breaking the data that is sent to the graphing routine, because it's not even able to calculate the ticks on the vertical access, which is a sign of that data being corrupted from the format that the D3 library is expecting it to be in. :P
I'm not sure what's going on here, but for some reason the graphing javascript is not working when passed the timespans as calculated by
timespans.append(int(current_delta.total_seconds() / 3600))
. When I remove theint()
from the calculation, there are graph bars appearing, however they're showing negative intervals for the amount of time, whether this is calculated from the seconds, or the hours. So it's not some sort of overflow due to the number of seconds... Not sure what's going on here, but things were working not that long ago, so it can't be too major of an issue.The text was updated successfully, but these errors were encountered: