-
Notifications
You must be signed in to change notification settings - Fork 4
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
500 Error on lookup existing multitext results #56
Comments
Here's the error:
We'll need to take a closer look at why that's happening, but this might be the relevant line:
|
Oh, fun. We could definitely cut down on the size with a "lookup by match ID" option for multitext results, and that would also help with managing download size/time in the frontend. That could be a good bandage for the time being. |
Update: Firefox declares a Gateway timeout on retrieving all of the multitext results. However, I've implemented paging of the results, which at least allows for retrieving some of the multitext results in less time than the Gateway timeout threshold. Same multitext search results from before, but with paging. My paging did, however, change the format in which the multitext results are sent. I've updated the documentation to describe the details, but essentially, the data comes back more like the results from |
Handled by paging. |
When accessing
multitexts/<multitextID>
, a 500 error is thrown. No other details are provided so it's hard to say why this is happening. Based on the progress bars for the searches, it seems like the results are being computed but not returned.Lucan x Vergil feat. Ammianus that errors
The text was updated successfully, but these errors were encountered: