[go: up one dir, main page]

Skip to content

`expected_old_oid` raises confusing error message when SHA is present in the repo, but not the latest

When an expected_old_oid is passed and the SHA is valid and present in the repo, but is not the most recent SHA, the following error message is returned:

GRPC::FailedPrecondition: 9:reference update: exit status 128. debug_error_string:{UNKNOWN:Error received from peer {grpc_message:"reference update: exit status 128", grpc_status:9, created_time:"2024-08-08T00:17:25.885517-06:00"}}

Ideally the returned error has metadata like here. But currently, it is not defined in userCommitFiles response.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information