8000 Transport does not use client's hub · Issue #118 · getsentry/sentry-python · GitHub
[go: up one dir, main page]
Skip to content
Transport does not use client's hub #118
New issue
New issue
Closed
Bug
Closed
Transport does not use client's hub#118
Bug
Assignees
untitaker
@untitaker

Description

@untitaker
untitaker
opened on Oct 10, 2018

The default HTTP Transport lives on its own thread and will not inherit the debug settings of the hub where the message was captured. It's basically impossible to enable debugging for threaded transports unless you make your hub the main one

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions
    0