Skip to content

Conversation

@dtm2451
Copy link
Contributor

@dtm2451 dtm2451 commented Jul 8, 2025

Adds a Connection Status Check on visit, with display in the Nav Bar.

This API includes 3 elements:

  1. a real check of if there is an active c4 conenction
  2. sourced from the app config, a call of whether downage might be 'expected' or not at this time
  3. sourced from the app config, a message for describing current or future maintenance windows

The UI in the NavBar then uses the MUI Alert component where icon&color can be easily adjusted based on the current situation. Scroll is used to keep this element constrained within our standard NavBAr height our standard messaging system.

Config Elements:
Within the ':ssh' set where the c4 connection setup is established

:ssh:
    :downage_expected: false #true
    :downage_message: 'Our compute cluster will be down for maintenance starting on 7/21, potentially lasting until 7/25'

A bit of work left:

  • Rather than true/false for the :downage_expected element, using dates to mark the start/end of the maintenance window could reduce the need to adjust this element manually at the start and end of known maintenance.
  • Styling adjustments?
  • Tests for the check_connection endpoint and the cluster_status API

Outdated examples:

see comment below for current versions!
Known Maintenance Coming:
image
Connection Failure that's expected:
expected-failure
Failure that's NOT expected:
unexpected-failure

@amadeovezz
Copy link
Contributor

backend code looks good to me! although the code is super simple - its probably worth just adding one quick spec. Happy to help here!

@dtm2451
Copy link
Contributor Author

dtm2451 commented Jul 9, 2025

backend code looks good to me! although the code is super simple - its probably worth just adding one quick spec. Happy to help here!

I welcome your help on the ruby spec! I've made my last push here for the day at this point.

@dtm2451
Copy link
Contributor Author

dtm2451 commented Jul 9, 2025

Updated the UI to just make use of our normal messaging system in all cases:

Known Maintenance Coming:
image
Connection Failure that's expected:
image
Failure that's NOT expected:
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants