Clint Branham f3b06171b2 fix: add -TimeoutSeconds for long-running HTTP calls ...

PveHttpClient was constructed without setting HttpClient.Timeout, so
.NET's 100s default applied to every request. Multi-GB ISO uploads via
Send-PveFile on a real LAN reliably tripped this with TaskCanceledException
after 100 seconds, and there was no way to override it.

- PveSession gains a Timeout (TimeSpan) property, defaulting to 100s.
- PveHttpClient accepts an optional per-instance timeout override that
  takes precedence over the session timeout.
- Connect-PveServer exposes -TimeoutSeconds to set the session default.
- Send-PveFile and Invoke-PveStorageDownload expose -TimeoutSeconds with
  a 30-minute implicit default so large uploads/downloads do not trip
  the 100s default. -TimeoutSeconds 0 means Timeout.InfiniteTimeSpan.

Tracked as F087. Closes #59.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-20 18:08:26 -05:00

..

PveAuthenticatorTests.cs

fix: resolve net48-only nullable warnings (CS8601, CS8602, CS8604)

2026-03-19 08:32:57 -05:00

PveSessionTests.cs

fix: add -TimeoutSeconds for long-running HTTP calls

2026-05-20 18:08:26 -05:00

PveVersionTests.cs

fix: resolve net48-only nullable warnings (CS8601, CS8602, CS8604)

2026-03-19 08:32:57 -05:00