No Visualization in the Early Clinical Development Teal App

[donyunardi]

This is also something breaking the visualizations in the Early Clinical Development Teal App: https://genentech.shinyapps.io/nest_early-dev_stable/

AE Events: AE Overview, Butterfly Plot, AE By Subgroup; Spider Plot, Swimlane Plot, Waterfall Plot, and Patient Profile Plot fail to display. The Common AE Plot is an outlier and displays.

I've done some other deployments in GSK Posit Connect, the visualizations are also broken there.

Interestingly, the plots work before deployment, in my Posit Workbench App.

Originally posted by @jeffreyCarlLong in #204

All failing plots are from teal.osprey so we need to investigate why this happened.
Related with insightsengineering/teal.goshawk#345 where all the failing plots are from teal.goshawk.

Acceptance Criteria

• Investigate why this happens for teal.osprey modules.
• Fix if the scope is small or create new issue if bigger.
• Visualization should shows for AE Events in early-dev app.
• Make sure all visualization shows in early-dev both stable and main version.

[llrs-roche]

Just some basic research on this issue:

The plot in _dev is created by:

<img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAXAAAAMgCAMAAAAN1snTAAAAA1BMVEX///+nxBvIAAAACXBIWXMAAAsSAAALEgHS3X78AAABNUlEQVR4nO3BMQEAAADCoPVPbQZ/oAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA+A4FcAAG+LEq1AAAAAElFTkSuQmCC" height="800" alt="Plot object" width="368">

And in _stable it is by:

<img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAdEAAAMgCAMAAABLTKg8AAAAA1BMVEX///+nxBvIAAAACXBIWXMAAAsSAAALEgHS3X78AAABf0lEQVR4nO3BAQEAAACCIP+vbkhAAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAHwasIsAAeSCKaQAAAAASUVORK5CYII=" height="800" alt="Plot object" width="465">

Both plots are white but the encoding is different. This is different to what we see with teal.goshwak on _stable (see comment) there is no error attribute and this still happens on _dev.

[gogonzo]

Why print is a problem?

If one uses a print(plot) in one of the reactives (technically a function) regardless if it is in qenv or not it will always open a new graphic device. Like in the example below. It doesn't matter what function returns.

fun <- function() {
  print(ggplot2::ggplot())
  1L
}

fun()

In shiny observe* and render* functions are the endpoints which trigger evaluation of a chain of reactives. If renderPlot evaluates reactives then everything is fine as print(plot) is suppressed by renderPlot. Problem arises when we have a qenv/reactive which is used in other endpoints (which is a case in our modules). For example if module uses qenv/reactive to
display plot, display table, show r code etc. then we have renderPlot, renderTable, observeEvent which receives an output this reactive chain (including graphic device info). Other then renderPlot don't suppress gr-dev which means that only solution is to print a plot in IDE.

Optimistic is that servers doesn't have screen, so quartz/x11 won't be opened. Possibly Rplot.pdf will be created for those (i think, but not sure)