Skip to content
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

Closed
jeffkinnison opened this issue Sep 29, 2020 · 4 comments
Closed

500 Error on lookup existing multitext results #56

jeffkinnison opened this issue Sep 29, 2020 · 4 comments

Comments

@jeffkinnison
Copy link
Contributor

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

@nOkuda
Copy link
Collaborator

nOkuda commented Sep 29, 2020

Here's the error:

pymongo.errors.DocumentTooLarge: BSON document too large (21899408 bytes) - the connected server supports BSON document sizes up to 16777216 bytes.

We'll need to take a closer look at why that's happening, but this might be the relevant line:

.../tesserae/utils/multitext.py", line 604, in get_results
  _id=[uid for mr in db_multiresults for uid in mr['units']])

@jeffkinnison
Copy link
Contributor Author

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.

@nOkuda
Copy link
Collaborator

nOkuda commented Oct 6, 2020

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 /parallels/<uuid>/.

@jeffkinnison
Copy link
Contributor Author

Handled by paging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants