-
Notifications
You must be signed in to change notification settings - Fork 566
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
More cache fixes #3955
More cache fixes #3955
Conversation
Signed-off-by: flakey5 <73616808+flakey5@users.noreply.github.com>
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.
The cache tests are not run automatically yet as part of CI, right? Can you add them (and maybe flag the failing ones as expected failures, or just implement those behaviors)?
// TODO (fix): Should we resume even if was paused downstream? | ||
controller.resume() |
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.
Let's aim to keep it in sync with the controller as possible; at the end it is what allow to apply back pressure while consuming the body
this.#writeStream | ||
.on('drain', () => controller.resume()) | ||
.on('error', function () { | ||
// TODO (fix): Make error somehow observable? |
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.
If we cannot store the response's body, best will be to just handover the body to the caller and fail silently; I'm thinking on some sort of on error
event here?
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'm thinking on some sort of on error event here?
Where would this be?
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.
Good question; maybe the cache-handler
itself? I believe we do not have reference to the dispatcher at this point but the dispatch method.
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.
Let's explore it in further PR
Co-authored-by: Carlos Fuentes <me@metcoder.dev>
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.
lgtm
new Date('Wed, aa Dec 2024 23:20:57 GMT')
, the day defaults to 1 instead of it being marked as an invalid date)last-modified
With this, we're passing 65% of the tests in the suite. The two main behaviors that are left are invalidating the urls given in the
Location
header and some behaviors regarding status codes other than 200 and 307 (note these are still optional)cc @mcollina