Run processes in background

[Jeff-Thompson12]

Addresses #711

[codecov]

Codecov Report

Attention: Patch coverage is 79.53488% with 44 lines in your changes are missing coverage. Please review.

Project coverage is 78.78%. Comparing base (6bdf82d) to head (0db252b).

Files	Patch %	Lines
R/mod_downloadHandler.R	53.33%	35 Missing ⚠️
R/mod_downloadHandler_utils.R	93.38%	9 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##              dev     #731      +/-   ##
==========================================
- Coverage   79.20%   78.78%   -0.43%     
==========================================
  Files          33       34       +1     
  Lines        5112     5171      +59     
==========================================
+ Hits         4049     4074      +25     
- Misses       1063     1097      +34     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[Jeff-Thompson12]

Looking for some feedback on this PR. Interested in what features you guys think should be added or what already needs to be changed.

[AARON-CLARK]

Hi @Jeff-Thompson12,

This is pretty sweet! In my first test, I ran html reports for 3 reports, then 5 reports. When downloading 3 reports, I noticed I was still able to do things in the app, which was not expected. Is that normal?

When rendering 5 reports, I was able to download a new package to the db while it was running, which is amazing. However, when it finished, the app crashed and there was an error in the console:

[Jeff-Thompson12]

@aclark02-arcus something else I forgot to mention is that since downloading a report is now a separate event from the report creation it is possible for the report downloader or another user to change outputs. This could be as low risk as adding comments but could also include actions like deleting a package from the database, which now that I mention it could crash the app.

[aclark02-arcus]

Converting to draft while we consider some alternatives, like grabbing info from database and injecting it into a list for rendering all our reports. If we can strip out the riskmetric layout "things", it may become really efficient too.