Server reachability message is easy to misread

Created on 7 September 2022, over 2 years ago
Updated 25 March 2024, 9 months ago

Problem/Motivation

Today is not the first time I have misread this message and tried to debug a non-existent problem:

The Elasticsearch server could be reached

The could/could not messages are quite similar.

Steps to reproduce

Proposed resolution

Change the message to something like "The Elasticsearch server was reached successfully"

Remaining tasks

User interface changes

API changes

Data model changes

📌 Task
Status

Fixed

Version

8.0

Component

User interface

Created by

🇬🇧United Kingdom longwave UK

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024