format not solvable error messages

[jaimergp]

Comes from https://matrix.to/#/!mPxkHLLyiXutAGtuaf:gitter.im/$0AVaD6APc2TPw1OsZoEPH76C86zjexoe1tV0gTTssxQ?via=gitter.im&via=matrix.org

The current output is a bit unreadable:

This hopefully improves it a bit.

[jaimergp]

Currently trying to reproduce by hand on the HTML canvas. Wait before merge.

[codecov]

Codecov Report

Attention: 4 lines in your changes are missing coverage. Please review.

Comparison is base (c021530) 68.65% compared to head (cfb2452) 68.80%.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1886      +/-   ##
==========================================
+ Coverage   68.65%   68.80%   +0.15%     
==========================================
  Files          93       93              
  Lines        8769     8754      -15     
==========================================
+ Hits         6020     6023       +3     
+ Misses       2749     2731      -18     

Files	Coverage Δ
conda_forge_tick/auto_tick.py	0.00% <0.00%> (ø)

... and 2 files with indirect coverage changes

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

[jaimergp]

This is more or less what it should look like, to the best of my manual HTML edition abilities:

Collapsed:

Revealed:

I can't use <summary> because for some reason the triangle toggle is missing 🤷 I guess it's been overridden by some CSS rule in the site, but current approach works well enough.

[beckermr]

Where does the newline before the details tag come from? Can we remove it?

[beckermr]

Ohh nvm this might not be in the final thing. LGTM!

[beckermr]

Ideally we should do this formatting in the front-end and not here. That is my bug and I will try to fix it at some point.

[jaimergp]

Ideally we should do this formatting in the front-end and not here

Agreed, something more structured would be better (e.g. a platform-to-error dict instead of the list of str) and would allow for a nicer collection of collapsible blocks. I'm not happy with the align=left stuff either here, we can move that to the status site if you want.

[jaimergp]

Ideally we would have something like:

- vpri["new_version_errors"][_new_ver] = _solver_err_str
+ vpri["new_version_errors"][_new_ver] = {
+     "error_type": "not solvable",
+     "job_url": os.getenv("CIRCLE_BUILD_URL"),
+     "base_branch": base_branch,
+     "messages": {
+          "platform_identifier": "string of problems",
+          ...
+     },
+ }

[jaimergp]

Where does the newline before the details tag come from?

I think that's the default details block formatting. We can't customize the title with a summary because the style has been overridden in the frontend somehow.

[beckermr]

Yolo.