VersionControlService.TextDiff 0.4.0

• net10.0

  • Fable.Core (>= 5.2.0)
  • VersionControlService.Abstractions (= 0.4.0)

### Added

-   `GitExecution.setGitExecutableProvider` lets a host choose the git executable for every Git operation in the process. The selection has to be an absolute path, and `None` uses the git on the PATH. `GitExecution.resetGitExecutableProvider` goes back to automatic discovery.
-   `DependencyStatus.ProbeExecutablePath` names the git executable that `CheckDependencies` ran.
-   The lakeFS provider reports its HTTP requests on `OperationContext.ReportOutput`, with the credentials of the connection removed.
-   `CommandOutput.ObserveNotice` adds a `Notice` line to a command. `OutputReporter.knownSecrets` and `beginCommandWithSecrets` start a command that hides credentials the caller knows as values.
-   `ObjectMaterializationCodes` holds the failure and recovery codes of object materialization. The Git provider reports the same strings as before.
-   `ProgressPhaseCodes` holds the phase codes of steps that more than one provider reports. Both providers report `fetch`, `merge` and `clone`. Only lakeFS reports `download-objects`, `upload-objects` and `publish`, because Git reports those steps under its own codes.
-   The lakeFS provider reports an event when a step starts, with the codes of `ProgressPhaseCodes`. A step that does no work reports nothing.

### Changed

-   `DependencyStatus` has a new `ProbeExecutablePath` field, so record literals have to set it.
-   With an explicit selection, the Git provider's `CheckDependencies` checks that git and does not fall back to the one on the PATH. An unusable selection marks every component as not installed, and the `Remediation` names the path.
-   lakeFS requests that time out fail with the category `Timeout` and the code `timeout`, as in the Git provider. They used to fail as `Network` with `network_failure`.
-   The lakeFS provider removes the credentials of the connection from failure messages built from an error response.
-   `ObjectMaterializationService.Materialize` and `Dematerialize` take an array of paths, so one call covers a single file or a whole folder. A call with one path still fails with that path's own code and message.

### Removed

-   `ObjectBatchMaterializationService`, `WorkspaceSession.ObjectBatchMaterialization` and `ServiceAvailability.ObjectBatchMaterialization` are removed, because `ObjectMaterialization` takes several paths now. Record literals have to drop the field.
-   `TextDiffSupervisorOptions.GitExecutable` is removed, so record literals have to drop it. The text diff supervisor uses the `GitExecution` selection.