Posit Connect Content Logging

meztez · November 17, 2023, 11:13pm

Make defaultErrorHandler more verbose in the Connect application logs

opened 08:05AM - 17 Nov 23 UTC

On Connect when a 500 error occurs we don't get any error messages in our logs. … I think this `print` in the `defaultErrorHandler` could instead be a `message` so that application admins can be alerted to unexpected problems: https://github.com/rstudio/plumber/blob/e829af6a94380cb897441c1c56129504afb9564f/R/default-handlers.R#L7C1-L7C1 ``` defaultErrorHandler <- function(){ function(req, res, err){ print(err) ... ``` We have overriden this using `pr_set_error()` in some of our APIs (including a full rlang backtrace in one case) - however, I would also be keen for the default handler to log at least something here.

Let's say a log is produced to stdout that looks like this.

<simpleError in (function () {    stop("bob")})(): bob>

I will not display in the connect UI since it is wrapped in a <span> tag as is.

I wonder if it would make sense to convert some characters to html entities before populating the <span> tags.

It might be a browser, OS, or Connect issue. I would not know.