Skip to content

setupNat not thread safe and can only be called once #845

@arnetheduck

Description

@arnetheduck

setupNat is not thread safe because:

  • it passes GC memory across thread boundary
  • it overwrites global vars without coordination

This prevents it from being used by more than one thread, such as happens when running unified nimbus node and execution/consensus each wants their ports.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    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