maddie
maddie
Wondering the same question here, and there seems to be no way to set the position of Y axis either.
I think this is due to the fact that the binary is UPX compressed. You can try decompress it using `upx -d` to see if Windows is still complaining.
What's the database type you've configured in the `settings.toml`?
The data store logic for `bolt` type hasn't been changed in the last few commits. Can you confirm if there's any error being printed in the backend program or frontend...
The current implementation has these sizes hardcoded: https://github.com/librespeed/speedtest-cli/blob/eb7f5cb43a7f6034ae34b548c37e1e6bfba3f8de/defs/defs.go#L3-L8 I can make these configurable I guess, but it's not time-based, though it should meet your requirement (extending test time)
Sorry, been busy IRL. There might be a timeout somewhere in the code, I'll have to look later.
@bpalob I've pushed a commit dc6eb0f with three new options: - `--duration` for setting test duration, it was hardcoded 15s, I think that's why you always get ~30s - `--chunks`...
Hmm... if the current payload is being uploaded completely, it should just start from the beginning and upload it again (shouldn't hang), or else the default value (1024 KiB) wouldn't...
Sorry for the late reply, been too busy IRL. I'll see what I can do, or PR is welcomed! :)