Skip to content

Conversation

@furszy
Copy link

@furszy furszy commented Mar 25, 2020

If a timeout happens while reading the proxy response, this effectively means we timed out while connecting to the remote node. This is very common for Tor, so do not print an error message to the log in that case.

Avoids a flood of

ERROR: Error reading proxy response

while running through Tor, causing users to blame the proxy.

Coming from upstream 9726

furszy added 2 commits March 25, 2020 13:29
If a timeout happens while reading the proxy response, this effectively
means we timed out while connecting to the remote node. This is very
common for Tor, so do not print an error message.

Coming from upstream 3ddfe29
@furszy furszy self-assigned this Mar 25, 2020
Copy link
Collaborator

@Fuzzbawls Fuzzbawls left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK fdca17c

Copy link

@random-zebra random-zebra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK fdca17c

@furszy furszy merged commit 18fa545 into PIVX-Project:master Mar 26, 2020
akshaynexus pushed a commit to ZENZO-Ecosystem/ZENZO-Core that referenced this pull request Mar 30, 2020
… timeouts through proxy

fdca17c Consolidate scattered max peer connection values into single declaration. (furszy)
bd4c713 netbase: Do not print an error on connection timeouts through proxy If a timeout happens while reading the proxy response, this effectively means we timed out while connecting to the remote node. This is very common for Tor, so do not print an error message. (furszy)
f936a2f netbase: Make InterruptibleRecv return an error code instead of bool. (furszy)

Pull request description:

  If a timeout happens while reading the proxy response, this effectively means we timed out while connecting to the remote node. This is very common for Tor, so do not print an error message to the log in that case.

  Avoids a flood of
  ```
  ERROR: Error reading proxy response
  ```

  while running through Tor, causing users to blame the proxy.

  Coming from upstream [9726](bitcoin#9726)

ACKs for top commit:
  Fuzzbawls:
    utACK fdca17c
  random-zebra:
    utACK fdca17c

Tree-SHA512: 6007c544710a0b103712f134c962368bd4704bbea4e1b93ccc55dd5ce65db063089facf3cdd335b132920256a9fe3fe59ed8e81add57f8ba85e9a7589c086961
@random-zebra random-zebra added this to the 4.1.0 milestone Apr 16, 2020
@furszy furszy deleted the 2020_intr_recv_error branch November 29, 2022 14:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants