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.

Sign up for GitHub

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

feat: HTTP SenderPool with asyncio support #66

Draft
wants to merge 6 commits into
base: main
Choose a base branch
from

Merge remote-tracking branch 'origin/main' into async_pool

5b7f946
Select commit
Loading
Failed to load commit list.
Draft

feat: HTTP SenderPool with asyncio support #66

Merge remote-tracking branch 'origin/main' into async_pool
5b7f946
Select commit
Loading
Failed to load commit list.
Azure Pipelines / questdb.py-questdb-client (1) failed Nov 23, 2024 in 1h 5m 42s

Build #20241123.1 had test failures

1 errors / 2 warnings

Details

Tests

  • Failed: 1 (0.01%)
  • Passed: 10,547 (91.53%)
  • Other: 975 (8.46%)
  • Total: 11,523

Annotations

Check failure on line 18728 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / questdb.py-questdb-client (1)

Build log #L18728 

Bash exited with code '1'.

Check failure on line 1 in test_http_request_timeout (__main__.TestSenderEnv)

See this annotation in the file changed.

@azure-pipelines azure-pipelines / questdb.py-questdb-client (1)

test_http_request_timeout (__main__.TestSenderEnv) 

Test failed
Raw output 
questdb.ingress.IngressError: Could not flush buffer: http://localhost:53975/write?precision=n: Network Error: Network Error: Error encountered in the status line: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (os error 10060)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "D:\a\1\s\test\test.py", line 1002, in test_http_request_timeout
    with self.assertRaisesRegex(qi.IngressError, 'timed out reading response'):
AssertionError: "timed out reading response" does not match "Could not flush buffer: http://localhost:53975/write?precision=n: Network Error: Network Error: Error encountered in the status line: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (os error 10060)"
View more details on Azure Pipelines