[META] Status page improvements

[jaimergp]

Just so we don't miss these pieces of feedback shared in #2090 and later:

• [x] https://github.com/conda-forge/conda-forge.github.io/issues/2135
• [ ] https://github.com/conda-forge/conda-forge.github.io/issues/2132
• [ ] Contrast issues in migration details in dark mode
• [ ] Wheel-click or "Open link in new tab" action on any migration will take you back to the migrations overview, not the details.
• [ ] Incident titles do not render backticks
• [ ] Migration details table loads up with all entries filtered out. Would be better to either show all by default, or at least print a message that says how many items are filtered out so users don't believe that there are no items.
• [x] add total children & sort feedstocks by it
• [ ] width of stacktrace foldout
• [ ] display paused migrators in status page
• [ ] fix "not redirecting properly" when using link to status page
• [ ] version status errors need same formatting w/ details as migration ones

@GabrielaVives proposed these UX improvements in #2090:

• [ ] Migration table sorts all categories (see alternative proposal with single row of titles above, and category separators)
• [ ] Migration details table colors, tooltips and visibility

[h-vetinari]

I'd like to have the number of children per feedstock in the migrator overviews again, and use that for sorting the tables (with a secondary sort based on the feedstock name; currently this is using reverse alphabetical sorting, which is weird). Even nicer would be to have clickable columns for sorting (e.g. one can choose between num_children and alphabetical; both have their uses).

[beckermr]

I'd be nice to add search bars for the migrations and version status tables on the status page.

[h-vetinari]

I consider the lack of number of total children to be a regression compared to the previous status page (and the reverse alphabetical ordering is annoying too). In particular, it's going to make it hard to know where to focus attention in a big migration like numpy (2800 feedstocks).

I noted this a month ago so I'm wondering if someone (@afshin?) still feel responsible for the new status page, or is this now up to us (=cf/core)?

[jaimergp]

Thanks for flagging that @h-vetinari. Let's see if I understood correctly. Sent https://github.com/conda-forge/conda-forge.github.io/pull/2176.

[h-vetinari]

Just scrolling down to the incidents, I think we should remove the "major outage" / "maintenance" etc. from any incidents that have been resolved. Otherwise it looks confusing - there's a very loud colour saying "problem!", and then you need to read the date and realize it's not a problem anymore. Also there's still a "This is a test" major outage, which should just be removed.

[jakirkham]

The confusing bit is there is no separation between active and past incidents. They are all just incidents

Maybe we should just move past incidents somewhere else and just have a link there

[jaimergp]

Active ones show up at the very top. Maybe the bottom section should be called Past incidents?

[jakirkham]

That's certainly an option

Would note the current incident was also showing up at the bottom. So we may want to change that behavior if we retitle it

Is there an expiration period where some past incidents drop from the list?

[h-vetinari]

@jaimergp, I think possibly as a consequence of #2176, the fold-outs for unsolvable packages in the migration aren't across the full width anymore:

[jaimergp]

oops, yes, some colspan needs a bump there

[jakirkham]

Observed an issue with how status incidents that include URLs are rendered (no hyperlink is added): https://github.com/conda-forge/conda-forge.github.io/issues/2181

[h-vetinari]

I noticed that paused migrations do not show up in the status page. These should not be filtered out. Often, a pause is just to help debug something, including e.g. which set of feedstocks the migrator is targetting.

[h-vetinari]

Also, I regularly get the following when I click on either of these:

[jaimergp]

I noticed that paused migrations do not show up in the status page.

Do you have an example of a paused migration (now or in the past)? Trying to find the bit to check in the JSON payloads.

[h-vetinari]

the numpy2 migration was paused until ~12h ago - does that help? If not, we can merge https://github.com/conda-forge/conda-forge-pinning-feedstock/pull/5855 as paused.

[jaimergp]

Hm, I see the paused: true part in the migration file, but the JSON payloads don't show anything that indicates the paused status as far as I can see. We might need to add that boolean somewhere. It even shows up as "closed" if paused, I think?