This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add local support for the new spaces summary endpoint #10549
Add local support for the new spaces summary endpoint #10549
Changes from 4 commits
7a32220
dcd2533
e98e940
8aefa5e
559e925
e943848
f8c0c86
80f9680
5251484
3f010f7
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is going to go fairly badly wrong when we get two concurrent requests with the same
from_token
, and both end up popping entries from the same Deque. We might need a ResponseCache to provide locking? Or to copy the deque so that we can safely process both requests?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A response cache sounds like it would be good regardless, since this could be a somewhat heavy calculation?