Skip to content

Cover no longer thread-safe #16

@jba

Description

@jba

Previously, Cover could be invoked concurrently. Now (a18cfb0), thanks to the shared state in Checker, it can't.

The particular error I saw was "concurrent map read and map write", with one offender at normalize.go:57.

This isn't that important since checking is now a lot faster, but it still takes about 30s to run on about 29K licenses.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions