Problem with logging in HTTP storage client #4013

Closed
opened 2023-04-14 14:07:11 +00:00 by itamarst · 3 comments
Exception ignored in: <coroutine object [StorageClient](wiki/StorageClient).request at 0x7f6c76ada570>
Traceback (most recent call last):
> File "/home/itamarst/devel/tahoe-lafs/src/allmydata/storage/http_client.py", line 403, in request
    with start_action(
> File "/home/itamarst/devel/tahoe-lafs/venv/lib/python3.10/site-packages/eliot/_action.py", line 432, in *exit*
    _ACTION_CONTEXT.reset(self._parent_token)
[ValueError](wiki/ValueError): <Token var=<ContextVar name='eliot.action' at 0x7f6c7a07d670> at 0x7f6c765b4ec0> was created in a different Context
``` Exception ignored in: <coroutine object [StorageClient](wiki/StorageClient).request at 0x7f6c76ada570> Traceback (most recent call last): > File "/home/itamarst/devel/tahoe-lafs/src/allmydata/storage/http_client.py", line 403, in request with start_action( > File "/home/itamarst/devel/tahoe-lafs/venv/lib/python3.10/site-packages/eliot/_action.py", line 432, in *exit* _ACTION_CONTEXT.reset(self._parent_token) [ValueError](wiki/ValueError): <Token var=<ContextVar name='eliot.action' at 0x7f6c7a07d670> at 0x7f6c765b4ec0> was created in a different Context ```
itamarst added the
unknown
normal
defect
n/a
labels 2023-04-14 14:07:11 +00:00
itamarst added this to the HTTP Storage Protocol milestone 2023-04-14 14:07:11 +00:00
Author

Note this happened when I run trial allmydata.test.test_system.HTTPSystemTest.test_filesystem with 20% of CPU quota, after it times out. So possibly this is just artifact of a particular failure mode when the tests stop and the reactor shuts down.

Note this happened when I run `trial allmydata.test.test_system.HTTPSystemTest.test_filesystem` with 20% of CPU quota, after it times out. So possibly this is just artifact of a particular failure mode when the tests stop and the reactor shuts down.
Author

Doesn't show up in local run of the get/put integration tests (on a branch for #4009, so lots of logging), which gives credence to the theory that it's not a real issue.

Doesn't show up in local run of the get/put integration tests (on a branch for #4009, so lots of logging), which gives credence to the theory that it's not a real issue.
Author

I've never seen this happen outside of test timeouts, so going to close.

I've never seen this happen outside of test timeouts, so going to close.
itamarst added the
fixed
label 2023-07-05 14:25:27 +00:00
Sign in to join this conversation.
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#4013
No description provided.