it's a balance of course -- in this case the error happens fairly often if network is fiddly and putting trace in console i think makes it harder to follow what is going on and user risks missing serious exceptions, hence the change

we could go with a strategy of a separate file-only logger for exceptions like this (or use a marker on the logging API, or disable traces altogether in console if either of those are possible?) so it can be enabled even if debug is disabled in general (eg production mode)