Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Give the configurations response error messages #774

Open
dhinrichs-scottlogic opened this issue Jan 15, 2024 · 0 comments
Open

Give the configurations response error messages #774

dhinrichs-scottlogic opened this issue Jan 15, 2024 · 0 comments
Labels
bug Something isn't working triage New tickets to be checked by the maintainers

Comments

@dhinrichs-scottlogic
Copy link
Contributor

dhinrichs-scottlogic commented Jan 15, 2024

Bug report

Description

We currently don't have a mechanism to display to the user that the backend call for the configurations failed.
When the backend isn't responding, the configuration buttons can't be toggled, but there is no indication as to why.

Acceptance criteria

GIVEN the frontend is running but the backend isn't
WHEN a user toggles a defence on/off, changes the GPT model or updates a config input
THEN they get an info message in the chat telling them that there is an error

Reproduction steps

Steps to reproduce the behaviour:

  1. Start the backend and frontend
  2. Go to the sandbox and toggle one of the defences (e.g. Character Limit) on. You will see a message in the chatbox saying "character limit defence activated" and in the networks tab of the dev tools you will see the 200 code that your request was successful.
  3. Turn your backend off. Try to turn any of the defences on or off.
  4. Observe that the buttons cannot be toggled, that there is the correct error response in the network, but there is no message in the UI indicating why the buttons can't be toggled, that the backend request wasn't successful.

Expected behaviour

Given the user tries to adjust the defences (on/off, changing the input, adjusting the sliders, changing the model)
When the backend request for the configuration update is failing
Then the user receives an error message in the chatbox.

Screenshots

Image

Additional context

Add any other context about the problem here.

@dhinrichs-scottlogic dhinrichs-scottlogic added bug Something isn't working triage New tickets to be checked by the maintainers labels Jan 15, 2024
@pmarsh-scottlogic pmarsh-scottlogic added this to the Error Handling milestone Jan 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage New tickets to be checked by the maintainers
Projects
None yet
Development

No branches or pull requests

2 participants