more graceful error handling of services after 10PM

[clintonlunn]

currently the user is able to see these errors after 10PM when they shut off

I am proposing we find a way to handle these errors more gracefully so that the user does not get exposed to this

@shodge17 thoughts?

[shodge17]

when you get to working on this I want to talk about it first. As you have noted, its low priority, but I want to better understand the issue before we tackle it.

[clintonlunn]

What I mean is wrapping things in a try/catch block, where we catch this error in the catch block and silence it so the user doesn't see it. It might be more complicated than that, I haven't done much research into it yet, just always bothered me to see that.

You can also see a favicon error in there, that just means the icon isn't on the server (or in the wrong spot) where it can be found.