Generate warnings in report

[adelavega]

Closes #441 #704

Adds a warnings field to the Report model. This field is update if any warnings are generated, and even if the Report ends up crashing.

We should display these above the traceback using ant's alerts, such as this one:

If each warning is pretty short, we should be able to stack them above the traceback (if any).

Sometimes warnings will be spit out even when there are no errors and the design matrix is compiled.

Maybe they can go after Correlation Matrix? These are not going to be subject specific so they should not be included within a Run tab.

I will next add a warning for #704 to test this out.

[codecov-io]

Codecov Report

❗ No coverage uploaded for pull request base (master@64d8c8c). Click here to learn what that means.
The diff coverage is 60%.

@@            Coverage Diff            @@
##             master     #725   +/-   ##
=========================================
  Coverage          ?   85.87%           
=========================================
  Files             ?       67           
  Lines             ?     3022           
  Branches          ?        0           
=========================================
  Hits              ?     2595           
  Misses            ?      427           
  Partials          ?        0

Impacted Files	Coverage Δ
neuroscout/tasks/upload.py	54.92% <ø> (ø)
neuroscout/tasks/utils/io.py	96.22% <100%> (ø)
neuroscout/tasks/report.py	75.67% <50%> (ø)
neuroscout/tasks/utils/warnings.py	88.46% <66.66%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 64d8c8c...b5b07bf. Read the comment docs.

[adelavega]

Cool, it's working on the backend

[adelavega]

Alright, all is looking good. @rwblair please take a look next week and test & see if there's a cleaner way to do things.

On the backend, still need to catch errors in the warnings module. Uncaught errors in Reports will result in Report hanging indefinitely.

Otherwise, just need to add more warnings. For now, focus on checking if n/as are handled correctly.

[adelavega]

• Try to generalize as many warning as possible into a Validator class in fitlins that checks all internal arguments that starts with _check

• Add wrapper that points to Neurostars / Github issues. Possibly hide traceback by default

• Could also catch specific pybids Exception by text, and replace them with friendlier text when possible.