fix(xpc): prevent startup hangs with proper timeout handling (#561)

[swiftveteran]

• Add timeout to XPCClient.send() that cancels connection on expiry
• Use .timeout error code with helpful message suggesting system start
• Skip blocking default network creation during apiserver startup
• Add 5-second timeouts to all NetworkClient XPC calls
• Fix NetworksService init to continue on network failure, not return

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update

Motivation and Context

The apiserver could hang indefinitely during startup if the vmnet plugin failed or was unresponsive. XPC calls now have proper timeout handling that cancels the connection on expiry and returns a helpful error message. The apiserver no longer blocks on default network creation during startup, and NetworkClient XPC calls have 5-second timeouts. Additionally, NetworksService initialization now continues processing remaining networks when one fails instead of returning early.

container system start would hang on startup waiting for the apiserver.

Testing

• Tested locally
• Added/updated tests
• Added/updated docs

[swiftveteran]

• Add timeout to XPCClient.send() that cancels connection on expiry
• Use .timeout error code with helpful message suggesting system start
• Skip blocking default network creation during apiserver startup
• Add 5-second timeouts to all NetworkClient XPC calls
• Fix NetworksService init to continue on network failure, not return

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update

Motivation and Context

The apiserver could hang indefinitely during startup if the vmnet plugin failed or was unresponsive. XPC calls now have proper timeout handling that cancels the connection on expiry and returns a helpful error message. The apiserver no longer blocks on default network creation during startup, and NetworkClient XPC calls have 5-second timeouts. Additionally, NetworksService initialization now continues processing remaining networks when one fails instead of returning early.

container system start would hang on startup waiting for the apiserver.

Testing

• Tested locally
• Added/updated tests
• Added/updated docs

[swiftveteran]

• Add timeout to XPCClient.send() that cancels connection on expiry
• Use .timeout error code with helpful message suggesting system start
• Skip blocking default network creation during apiserver startup
• Add 5-second timeouts to all NetworkClient XPC calls
• Fix NetworksService init to continue on network failure, not return

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update

Motivation and Context

The apiserver could hang indefinitely during startup if the vmnet plugin failed or was unresponsive. XPC calls now have proper timeout handling that cancels the connection on expiry and returns a helpful error message. The apiserver no longer blocks on default network creation during startup, and NetworkClient XPC calls have 5-second timeouts. Additionally, NetworksService initialization now continues processing remaining networks when one fails instead of returning early.

container system start would hang on startup waiting for the apiserver.

Testing

• Tested locally
• Added/updated tests
• Added/updated docs

[swiftveteran]

• Add timeout to XPCClient.send() that cancels connection on expiry
• Use .timeout error code with helpful message suggesting system start
• Skip blocking default network creation during apiserver startup
• Add 5-second timeouts to all NetworkClient XPC calls
• Fix NetworksService init to continue on network failure, not return

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update

Motivation and Context

The apiserver could hang indefinitely during startup if the vmnet plugin failed or was unresponsive. XPC calls now have proper timeout handling that cancels the connection on expiry and returns a helpful error message. The apiserver no longer blocks on default network creation during startup, and NetworkClient XPC calls have 5-second timeouts. Additionally, NetworksService initialization now continues processing remaining networks when one fails instead of returning early.

container system start would hang on startup waiting for the apiserver.

Testing

• Tested locally
• Added/updated tests
• Added/updated docs

[swiftveteran]

• Add timeout to XPCClient.send() that cancels connection on expiry
• Use .timeout error code with helpful message suggesting system start
• Skip blocking default network creation during apiserver startup
• Add 5-second timeouts to all NetworkClient XPC calls
• Fix NetworksService init to continue on network failure, not return

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update

Motivation and Context

The apiserver could hang indefinitely during startup if the vmnet plugin failed or was unresponsive. XPC calls now have proper timeout handling that cancels the connection on expiry and returns a helpful error message. The apiserver no longer blocks on default network creation during startup, and NetworkClient XPC calls have 5-second timeouts. Additionally, NetworksService initialization now continues processing remaining networks when one fails instead of returning early.

container system start would hang on startup waiting for the apiserver.

Testing

• Tested locally
• Added/updated tests
• Added/updated docs

[swiftveteran]

• Add timeout to XPCClient.send() that cancels connection on expiry
• Use .timeout error code with helpful message suggesting system start
• Skip blocking default network creation during apiserver startup
• Add 5-second timeouts to all NetworkClient XPC calls
• Fix NetworksService init to continue on network failure, not return

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update

Motivation and Context

The apiserver could hang indefinitely during startup if the vmnet plugin failed or was unresponsive. XPC calls now have proper timeout handling that cancels the connection on expiry and returns a helpful error message. The apiserver no longer blocks on default network creation during startup, and NetworkClient XPC calls have 5-second timeouts. Additionally, NetworksService initialization now continues processing remaining networks when one fails instead of returning early.

container system start would hang on startup waiting for the apiserver.

Testing

• Tested locally
• Added/updated tests
• Added/updated docs

[swiftveteran]

• Add timeout to XPCClient.send() that cancels connection on expiry
• Use .timeout error code with helpful message suggesting system start
• Skip blocking default network creation during apiserver startup
• Add 5-second timeouts to all NetworkClient XPC calls
• Fix NetworksService init to continue on network failure, not return

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update

Motivation and Context

The apiserver could hang indefinitely during startup if the vmnet plugin failed or was unresponsive. XPC calls now have proper timeout handling that cancels the connection on expiry and returns a helpful error message. The apiserver no longer blocks on default network creation during startup, and NetworkClient XPC calls have 5-second timeouts. Additionally, NetworksService initialization now continues processing remaining networks when one fails instead of returning early.

container system start would hang on startup waiting for the apiserver.

Testing

• Tested locally
• Added/updated tests
• Added/updated docs

[swiftveteran]

• Add timeout to XPCClient.send() that cancels connection on expiry
• Use .timeout error code with helpful message suggesting system start
• Skip blocking default network creation during apiserver startup
• Add 5-second timeouts to all NetworkClient XPC calls
• Fix NetworksService init to continue on network failure, not return

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update

Motivation and Context

The apiserver could hang indefinitely during startup if the vmnet plugin failed or was unresponsive. XPC calls now have proper timeout handling that cancels the connection on expiry and returns a helpful error message. The apiserver no longer blocks on default network creation during startup, and NetworkClient XPC calls have 5-second timeouts. Additionally, NetworksService initialization now continues processing remaining networks when one fails instead of returning early.

container system start would hang on startup waiting for the apiserver.

Testing

• Tested locally
• Added/updated tests
• Added/updated docs