-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Impossible to change timeframe window #680
Comments
Same issue on debian 10 |
Same here, just running latest Docker image on x86_64. Will probably revert until fixed. |
Same issue in docker on Unraid (linux/amd64) |
Ok so it's not just me! Damnit. I've logged a duplicate of this. Sorry. |
Dupe here, sorry. |
Does anyone know how to pull an old version, this is occurring at the WORST possible time for me! I need to provide data for a line fault to my ISP :( I only see 4 versions here?! Do I just pull dev? |
The dev doesn't upload each individual version on Docker hub for some reason... But I looked through my |
I have pulled the 4 month old 'dev' release and it has fixed nothing, the image appears to be identical somehow. Anyone got any idea, how I can get back to the old edition, I need to convince my ISP I have a line fault and I'd really like to be able to produce some nice graphs. |
I'm an idiot who cleans up disk space by purging and pruning old stuff! :( EDIT Ok I apologise I've just re-read your post and it's clear, they're not available for me to snatch again (honestly, I didn't know this was even possible!) Any tips how I can spin up an old one? |
I've uploaded a tar.gz of the image on my server here: https://files.cutelab.space/f/ebb317bf98074fe78340/ I don't know how to prove this is the official release... I just want to help out. The owner of this project should really push the version tag and then latest tag to Docker hub. wget -O speedtest-tracker-1.10.4.tar.gz "https://files.cutelab.space/f/ebb317bf98074fe78340/?dl=1"
docker load -i speedtest-tracker-1.10.4.tar.gz |
You might have to backup your data in the webui settings first, then remove your data volume, start the container fresh and import your data back in. It will break if you try to downgrade. |
I <3 linux, open source stuff, docker and you! Magic, just wonderful. Did indeed have to backup data, been a bit of a mess but I have graphs now to show my ISP my line is stuffed. |
I'm really glad I could help! I prune things pretty often too and I'm not afraid of going cutting edge. But this project definitely needs a Docker overhaul. It's not done correctly. Not only do versions not get released, but the owner copies the root of the main branch into a separate branch in a weird way, compile on their machine and then build the image. I might send in a pr so you can |
They probably don't know any better (I know I don't) so any help for the original developer is probably quite helpful. The only reason I'm using this, is because this guy broke this one. It need a fork or some such which updates a file. |
Also having this issue |
Building a fix for this now lads. Was an issue with the refresh happening before the state was change, if u update the number of days again it has the right value the second time |
#680: Fix issue where the data would refresh before the react state had updated
Right turns out there was another issue, but have pushed a new |
dev build 12.1 working now for down/upload and ping. But not for successful/faild graph. |
can confirm, same results as db77x. Also i might be wrong, but if i remember correctly, it used to show the timeline on all graphs and currently they're empty on the bottom |
confirm (dev) working Download,Upload,Ping Graphs on Unraid (linux/amd64) but not the Failure graph |
v 1.12.2 dev all graphs is working now in Unraid (linux/amd64) |
I take it this one isn't published as official yet, right? (where can I check? Sorry for hassling!) |
Can I just confirm, this is still broken, in both latest and dev docker builds, right? (It's still dead for me) |
It is working for me on the dev branch. Running in docker on Linux server.
…Sent from my iPhone
On Sep 18, 2021, at 10:53, jaxjexjox ***@***.***> wrote:
Can I just confirm, this is still broken, in both latest and dev docker builds, right? (It's still dead for me)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Ok that's a bit odd, perhaps I need to nuke my data directory. I also notice this one sure chews some disk space. |
Yeah looks like I needed a fresh data directory, no biggie, I could do with a fresh folder anyhow. Thanks for hard work henry. |
Mine is around 337MB which includes 2.7MB .db file.
…Sent from my iPhone
On Sep 18, 2021, at 11:11, jaxjexjox ***@***.***> wrote:
Yeah looks like I needed a fresh data directory, no biggie, I could do with a fresh folder anyhow. Thanks for hard work henry.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
I mean look, disk space is cheap, I'll get over it, but I'll say the CSV file from other apps is in the kilobytes, I'm not sure why so much is on the disk but no big deal, at least this works! Unlike roests one. |
When will this bug fix merge with latest for docker? |
Describe the bug
No effect when changing "Show results for the last" to a different value from 7. Working fine before the upgrade.
Context
Version : 1.12.0
Synology - DSM7
The text was updated successfully, but these errors were encountered: