Environment information

CLI:
  Version:                      1.8.1
  Color support:                true

Platform:
  CPU Architecture:             x86_64
  OS:                           linux

Environment:
  BIOME_LOG_DIR:                unset
  NO_COLOR:                     unset
  TERM:                         "xterm-256color"
  JS_RUNTIME_VERSION:           unset
  JS_RUNTIME_NAME:              unset
  NODE_PACKAGE_MANAGER:         unset

Biome Configuration:
  Status:                       Loaded successfully
  Formatter disabled:           false
  Linter disabled:              false
  Organize imports disabled:    false
  VCS disabled:                 false

Workspace:
  Open Documents:               0

Note that this is the environment from my personal machine. The error itself occurs sporadically on our CI runners on which I can't run biome rage easily.

What happened?

Run biome format --files-ignore-unknown=true --no-errors-on-unmatched, got:

Biome encountered an unexpected error 00:05
This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue: 00:05
Source Location: crates/biome_cli/src/execute/traverse.rs:150:14 00:05
Thread Name: main 00:05
Message: failed to initialize the global thread pool: ThreadPoolBuildError { kind: IOError(Os { code: 11, kind: WouldBlock, message: "Resource temporarily unavailable" }) }

We run that command via pre-commit with the following hook definition:

      - id: biome
        name: Biome formatting
        entry: biome format --files-ignore-unknown=true --no-errors-on-unmatched
        language: system

Expected result

No error.

Code of Conduct

• I agree to follow Biome's Code of Conduct