VITAS changed the topic of #spacedock to: Problems?: https://github.com/KSP-SpaceDock/SpaceDock/issues | Matrix/Riot Chat: https://im.52k.de +spacedock:52k.de Feel free to ask for help, we only bite a little bit! | If you want to help, please check https://github.com/KSP-SpaceDock/SpaceDock-Backend/issues/5 :) | <VITAS> inet users have the attentionspan of a squirrel....oh a nut!
aradapilot has quit [Remote host closed the connection]
im52kde has quit [Remote host closed the connection]
im52kde has joined #spacedock
VITAS[m]1 has joined #spacedock
* VITAS[m]1 uploaded an image: t-shirt-front.png (236KB) < https://52k.de/_matrix/media/v1/download/52k.de/aCvbWxPQrYhYRfFXwpMPPhgS >
<VITAS[m]1> yay i can upload media again :)
aradapilot has joined #spacedock
aradapil_ has joined #spacedock
aradapilot has quit [Read error: Connection reset by peer]
aradapil_ has quit [Remote host closed the connection]
aradapilot has joined #spacedock
VITAS[m]1 has quit [Quit: Idle timeout reached: 10800s]
politas has quit [Ping timeout: 190 seconds]
politas has joined #spacedock
RockyTV[m] has joined #spacedock
<RockyTV[m]> AllisTauri I was looking at HebaruSan 's PR and I couldn't understand why we're not using `ConfigParser.get<type>`. the PR ignores the exceptions that will be thrown for invalid values so why not do that as well for ConfigParser?
AllisTauri[m] has joined #spacedock
<AllisTauri[m]> I also prefer to handle parsing errors in configuration framework itself, not delegating it to the bushes logic, instead always providing the choice of default value and logging the errors. But that is a matter of taste.
Technicalfool has joined #spacedock
politas has quit [Ping timeout: 190 seconds]
politas has joined #spacedock
RockyTV[m] has quit [Quit: Idle timeout reached: 10800s]
AllisTauri[m] has quit [Quit: Idle timeout reached: 10800s]