IRC chat logs for #ltsp on (webchat)

Channel log from 4 February 2021   (all times are UTC)

02:46AppleMuncy has left IRC (AppleMuncy!
04:17vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
05:59GodFather has left IRC (GodFather!, Ping timeout: 246 seconds)
07:48ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
09:01jgee8 has joined IRC (jgee8!~jgee@
09:02jgee has left IRC (jgee!~jgee@, Ping timeout: 264 seconds)
09:02jgee8 is now known as jgee
13:05lucascastro has joined IRC (lucascastro!
13:05Aison has left IRC (Aison!~Asion0@2a02:168:200f:110:69c6:120a:877c:5a19, Ping timeout: 260 seconds)
14:21GodFather has joined IRC (GodFather!
15:02GodFather has left IRC (GodFather!, Ping timeout: 265 seconds)
15:17GodFather has joined IRC (GodFather!
15:40RaphGro has joined IRC (RaphGro!~raphgro@fedora/raphgro)
16:02yanu has left IRC (yanu!, Ping timeout: 240 seconds)
16:03yanu has joined IRC (yanu!
17:44Aison has joined IRC (Aison!~Asion0@2a02:168:200f:110:69c6:120a:877c:5a19)
17:45sutula has left IRC (sutula!~sutula@, Ping timeout: 260 seconds)
17:49sutula has joined IRC (sutula!~sutula@
18:52yanu has left IRC (yanu!, Ping timeout: 276 seconds)
18:52yanu has joined IRC (yanu!
19:01GodFather has left IRC (GodFather!, Ping timeout: 264 seconds)
19:28vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
Yeah, improving the errors would be nicer. ==> something like this?
:P :D
19:42* alkisg prefers the python advice, "don't hide exceptions / call stacks"
huh, was never under the impression that a python traceback was considered good practice ... by python programmers they always found it as a failure to not handle an exception more meaningfully
but there's only so much time available, and can't catch everything
I wouldn't mind writing the exception to a log file, and telling the user "things failed, look at the log file" like windows does, but I can't say it's my first choice...
I always have a hard time troubleshooting programs on windows, while linux programs with their stderr are always much easier to debug
i guess the difference is between hiding an exception vs. handling it :)
but anyways, your proposal to be more verbose about what failed sounded good
Handling an exception is a bad thing to do if all you're going to show is a generic message, that hides 1000 different possible errors
Now, the exception showed "keyerror 1027", the exact number where the group was missing
i loved the gnome login error "Something went wrong"
19:54* alkisg tries to think of linux console programs that write their stderr elsewhere, in order to show more user friendly messages...
Not gui ones, console ones
22:02ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
22:40Aison has left IRC (Aison!~Asion0@2a02:168:200f:110:69c6:120a:877c:5a19, Ping timeout: 260 seconds)