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

fix: distinguish server timeouts from transport timeouts #43

Merged
merged 6 commits into from Mar 9, 2020

Commits on Feb 25, 2020

  1. fix: distinguish transport and query timeouts

    A transport layer timeout is made independent of the query timeout,
    i.e. the maximum time to wait for the query to complete.
    
    The query timeout is used by the blocking poll so that the backend
    does not block for too long when polling for job completion, but
    the transport can have different timeout requirements, and we do
    not want it to be raising sometimes unnecessary timeout errors.
    plamut committed Feb 25, 2020
    Copy the full SHA
    75e459a View commit details
    Browse the repository at this point in the history
  2. Apply timeout to each of the underlying requests

    As job methods do not split the timeout anymore between all requests a
    method might make, the Client methods are adjusted in the same way.
    plamut committed Feb 25, 2020
    Copy the full SHA
    ceb9690 View commit details
    Browse the repository at this point in the history

Commits on Mar 2, 2020

  1. Copy the full SHA
    89e5c2e View commit details
    Browse the repository at this point in the history

Commits on Mar 4, 2020

  1. Copy the full SHA
    7dac01f View commit details
    Browse the repository at this point in the history
  2. Copy the full SHA
    9210abd View commit details
    Browse the repository at this point in the history

Commits on Mar 9, 2020

  1. Copy the full SHA
    fb187b9 View commit details
    Browse the repository at this point in the history