Tim Visée

Yes, merge requests essentially work the same on GitLab as pull requests on GitHub. You've to fork the repository to your own account, make changes, then submit a merge request....

That's weird! I didn't catch this before. I'll try to see if I can reproduce this.

I cannot reproduce this with `ffsend 0.2.74`. Are you using a custom instance? And, does it work fine on the public instance (`--host https://send.vis.ee/`)?

A Redis misconfiguration could be the issue, especially when using Docker to host Send. If using Docker, please make sure files are still available when you restart all containers.

Thanks for your suggestion! Sadly, I currently don´t have (enough) time to allocate to this, due to other activities. I therefore don´t plan to implement this anytime soon. The current...

Thanks for the report. This shows up on all systems and configurations. This is related to error handling. In order to properly fix this I'd like to upgrade to using...

Seeing this as well, for weeks already. Running through [gamemode](https://github.com/FeralInteractive/gamemode). Tried to disable other network devices/interfaces, didn't seem to help.

@spider3000 these property changes don't seem to change anything in my case. There's possibly a wider set of issues that is causing these error messages.

The current `Duration` type seems to be: https://docs.rs/chrono/0.4.19/chrono/struct.Duration.html Is there any reason for it not supporting `Serialize`/`Deserialize` yet other than development time? Are there implementation details I should know about?...

I did some investigation, here are my findings: - `chrono` still uses the `Duration` type provided by the `time` crate. - `chrono` currently uses `time` `0.1`, which doesn't provide `serde`...