-
Notifications
You must be signed in to change notification settings - Fork 103
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
Queries get lost when creating a case #1179
Comments
Screen recording showing the issue. In the recording a refresh does not include the queries. Sometimes it does. Screen.Recording.2025-01-16.at.12.11.38.mov |
I thought it was this issue, which is that you load the case, and the queries sit there and never complete running, and you refresh and they do, and it's cuase we have the wrong params: However, what you are seeing, if you look in console is deadlocks ;-(. Which I ignored. :-( |
wow! This was a legit bug. We were deadlocking in the database by writing each query seperately as a call. I have migrated it to the bulk API for persisting a query, and have also chased down that we were storing a score mulitple times if you pick the same case mutliple times... weird angular messaging issues. This is deployed now in quepid-staging.herokuapp.com, would you mind giving it a try and confirming my fixes? |
Confirming that the behavior does not occur any more on quepid-staging.herokuapp.com 👍 |
thanks. Just fixed lint and unit test error, and pushing that out. |
Describe the bug
One query gets lost when going through the case setup and adding multiple queries to the case. They apparently are in the case and show up when refreshing the page. But they are not listed initially.
To Reproduce
Steps to reproduce the behavior:
star wars
,harrison ford
, andbest action movie
Expected behavior
All queries are listed after finishing the case setup (if there are less than the maximum page size)
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: