You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Shinylogs is an amazing tool to track the logs of an app, so thanks for developing it!
One issue I encountered was that if an app is significantly large (lots of input/output) it can trigger an out-of-memory error in the browser/client. I believe it could be caused by shinylogs saving the inputs/outputs at the client-side before it is written to the storage_mode under track_usage.
Would there be a way to prevent accumulation of memory? Or a way to directly write the gather logs to the output files?
Thanks for considering!
The text was updated successfully, but these errors were encountered:
Shinylogs is an amazing tool to track the logs of an app, so thanks for developing it!
One issue I encountered was that if an app is significantly large (lots of input/output) it can trigger an out-of-memory error in the browser/client. I believe it could be caused by shinylogs saving the inputs/outputs at the client-side before it is written to the storage_mode under track_usage.
Would there be a way to prevent accumulation of memory? Or a way to directly write the gather logs to the output files?
Thanks for considering!
The text was updated successfully, but these errors were encountered: