Details
-
Type:
Task
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Story Points:1
-
Epic Link:
-
Sprint:Fall 6 2022 Nov 7
Description
Situation: The Search endpoint has been going down on CyVerse with the following error:
{"error":"no available connection: no Elasticsearch node available"}
Currently, if a user attempts to use the Search bar they are logged out of BioViz Connect, most likely due to us not handling the error.
Task: Handle the above error and display a popup to the user stating that there is a problem with Search at this time. The response should be similar to what we are showing for View in IGB and Manage Link for Community/Shared, as they also use the Search endpoint.
Sorry! An error occured while searching your search phrase. Please try a different phrase or try again after some time.
Attachments
Activity
Merged
New code is deployed. https://bvctest3.bioviz.org is up to date.
Searching in Home/Shared/Community when the search endpoint is down shows a modal with "Sorry! Unable to search for files/folders at the moment. Please try again later." and then allows the user to continue to interact with BioViz Connect.
Selecting Manage Link in Community when the search endpoint is down shows a modal with "Sorry! We could not check if you have the permission to modify this file. Please try again after some time." and then the right panel shows the file as being private (in place of the ouroboros spinning forever).
Clicking View in IGB in Community when the search endpoint is down shows a modal with "Sorry! An error occurred while searching your search phrase. Please try a different phrase or try again after some time".
My one thought is that generally, but not always, the community files are supposed to be public. So we could make the assumption that if the file is in Community and the Search endpoint is down, we default to assuming that the files are public. This would allow a user to still view the file in IGB (assuming it is actually public) while the search endpoint is down. However, if the file is not public, it may result in an error within IGB. Thoughts on this Karthik Raveendran? If it seems like something that is easy to do we could do it as part of this ticket.
Changes for the above comment has been made. PR submitted. https://bitbucket.org/nfreese/bioviz-connect/pull-requests/285/igbf-3219-enable-view-in-igb-for-community
Merged
Playbooks are run and new code is deployed to https://bvctest3.bioviz.org.
Working correctly. I am able to view Community files in IGB when the Search endpoint is down.
Closing ticket.
Error has been handled (See [commit | https://bitbucket.org/KarthikRavee91/karthikdjango-cyversedev/commits/861df6ea4243b04bfa1f25b53f573a6cac787e2a) however as the search functionality is down, I was not able to test if normal search functionality is affected by this or not. The error handling is specific so I was able to make some assumptions about that.
PR submitted. https://bitbucket.org/nfreese/bioviz-connect/pull-requests/282