Skip to content

Fix ordering between initSentry() and WriteableTmpDir.getInstance().determine() #3418

Description

Fix the Sentry/logging bootstrap ordering so initSentry()'s first getSentryScope() call
can't fire a log write before determine() resolves. Do this through moving the initSentry() call in extension.ts to after await WriteableTmpDir.getInstance().determine() and place a comment as to why ("// Logging calls within initSentry() depend on first knowing a writeable tmp dir").

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions