An error message like the following gets stuck in the Discovery View
ERROR: (503) Could not connect to the core, uri: http://localhost:8984/solr/sage-discovery
This problem has been reported in the past and closed due to being unable to be reproduced.
I have identified that the problem persists and have found a way to consistently reproduce.
To Reproduce
Steps to reproduce the behavior:
Start up a local Solr instance.
Create or Edit a Discovery View and point it to that local Solr instance.
Turn off that Solr instance and load the Discovery View to trigger the error.
Edit that Discovery View to point to a different and functional Solr instance (such as demos).
Opening and closing the Discovery View should show that the error message still appears and it is still for the old Solr instance that is no longer being pointed to.
Opening up a different Discovery View can also show the message.
Expected behavior
Clear the error message on modal close.
Opening a new modal should not maintain the error from a previous modal instance.
Describe the bug
An error message like the following gets stuck in the Discovery View
This problem has been reported in the past and closed due to being unable to be reproduced. I have identified that the problem persists and have found a way to consistently reproduce.
To Reproduce Steps to reproduce the behavior:
Expected behavior Clear the error message on modal close. Opening a new modal should not maintain the error from a previous modal instance.