You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
issue description:
for an unknown reason, on customer instance(not reproduced locally), we have a note which is deleted on database, but still indexed in ES; what leads to a problem while filtering notes from tree drawer, when a specific note matches the typed keyword.
When this note is is retreived as a result and get itereated at this specific line
it generate an exception EntityNotFoundException which is catch outside the loop, here. Then the notes fetching is stopped before the end related line.
(ps: it is a swallowed error, without a correct LOG.error trace. We should add a line to log the error)
proposed solution: (discussed with Romain)
To make the code more robust, we should improve the error management, by adding a try catch around the for loop which will prevent the REST service to fail with error 500 even if a old note is still indexed
feedback:
77341
The text was updated successfully, but these errors were encountered:
hthabti
changed the title
add try catch bloc to handle thrown exceprion while searching nots
deleted not page which is indexed in serach result throws an exception and lead to the exit of the loop
Mar 7, 2025
rdenarie
changed the title
deleted not page which is indexed in serach result throws an exception and lead to the exit of the loop
deleted note page which is indexed in search result throws an exception
Mar 7, 2025
azayati
changed the title
deleted note page which is indexed in search result throws an exception
Deleted note page which is indexed in search result throws an exception
Mar 12, 2025
issue description:
for an unknown reason, on customer instance(not reproduced locally), we have a note which is deleted on database, but still indexed in ES; what leads to a problem while filtering notes from tree drawer, when a specific note matches the typed keyword.
When this note is is retreived as a result and get itereated at this specific line
it generate an exception EntityNotFoundException which is catch outside the loop, here. Then the notes fetching is stopped before the end related line.
(ps: it is a swallowed error, without a correct LOG.error trace. We should add a line to log the error)
proposed solution: (discussed with Romain)
To make the code more robust, we should improve the error management, by adding a try catch around the for loop which will prevent the REST service to fail with error 500 even if a old note is still indexed
feedback:
77341
The text was updated successfully, but these errors were encountered: