PoolTimeout exceptions on requests to Tumblr #4
Labels
bug
Something isn't working
Comments
|
Related: encode/httpx#1171 |
|
Seems like the problem is not just limited to media requests. The regular client used for requesting Tumblr's API seems to also be affected. |
|
According to the upstream issue, it seems like the problem is due to the fact that clients aren't released from the connection pool when the request is canceled. Shielding the request from being canceled is reported as a workaround for the issue. |
syeopite
added a commit
that referenced
this issue
Jan 4, 2024
#4 appears to be caused by faulty connections that aren't properly released which will result in a PoolTimeout exception when attempting to fetch one. When enough of a pool gets poisoned, all requests will fail due to the PoolTimeout exceptions. This commit implements a workaround by detecting and then reinitializing poisoned connection pools which would clear all of the faulty connections.
syeopite
added a commit
that referenced
this issue
Jan 4, 2024
#4 appears to be caused by faulty connections that aren't properly released which will result in a PoolTimeout exception when attempting to fetch one. When enough of a pool gets poisoned, all requests will fail due to the PoolTimeout exceptions. This commit implements a workaround by detecting and then reinitializing poisoned connection pools which would clear all of the faulty connections.
syeopite
changed the title
syeopite
changed the title
syeopite
added a commit
that referenced
this issue
Jan 13, 2024
#4 appears to be caused by faulty connections that aren't properly released which will result in a PoolTimeout exception when attempting to fetch one. When enough of a pool gets poisoned, all requests will fail due to the PoolTimeout exceptions. This commit implements a workaround by detecting and then reinitializing poisoned connection pools which would clear all of the faulty connections.
|
Issue still seems to occur |
|
httpx has reportedly fixed the issue here encode/httpcore#880 It should be fine for us to switch back to httpx now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Priviblur can sometimes stop working randomly due to a permanent pool timeout exception. Directly accessing Tumblr works as expected
This is most commonly seen in the media requests, meaning that all pages still works fine just without any media assets loaded. However, it seems like regular requests can also be affected resulting in a pool timeout exception page on all Priviblur routes.
It seems to be reproducible after extensive usage.
A restart is able to fix this.
More investigation needed.
The text was updated successfully, but these errors were encountered: