mirror of
https://github.com/hanzoai/forge.git
synced 2026-10-30 15:00:39 +00:00
zeekayandHanzo Dev
27cde39e36
Storage buckets, indexer names, the bleve analyzer, the lock prefix, SSH host keys, the markdown front-matter key, the container data paths, the RPM repo id and the API security scheme all read as this product now, and app.example.ini matches the code again. The upstream maintainer list and the changelog generator config went with the release history they belonged to, and the citation comments state the fact rather than link the issue. Three inert rules turn out to have been inert because they named a module path this tree does not use: gci grouped no first-party imports under prefix(), and depguard let models/migrations import models and modules/structs. They now name github.com/hanzoai/git. The config example also documented .gitea/workflows while the code has read .hanzo/workflows for some time. The authorized_keys marker follows the delegate-hook precedent: the new name is written and the old one is still recognised, because a marker we do not know is copied through as a hand-added key and leaves a revoked key authorized. The stored user_setting key keeps its value; only a migration may change that. Co-authored-by: Hanzo Dev <[email protected]>
39 lines
2.1 KiB
Go
39 lines
2.1 KiB
Go
// Copyright 2026 Hanzo AI, Inc. All rights reserved.
|
|
// SPDX-License-Identifier: MIT
|
|
|
|
package mirror
|
|
|
|
import (
|
|
"testing"
|
|
|
|
"github.com/stretchr/testify/assert"
|
|
)
|
|
|
|
func Test_checkRecoverableSyncError(t *testing.T) {
|
|
cases := []struct {
|
|
recoverable bool
|
|
message string
|
|
}{
|
|
// A race condition in http git-fetch where certain refs were listed on the remote and are no longer there, would exit status 128
|
|
{true, "fatal: remote error: upload-pack: not our ref 988881adc9fc3655077dc2d4d757d480b5ea0e11"},
|
|
// A race condition where a local gc/prune removes a named ref during a git-fetch would exit status 1
|
|
{true, "cannot lock ref 'refs/pull/123456/merge': unable to resolve reference 'refs/pull/134153/merge'"},
|
|
// A race condition in http git-fetch where named refs were listed on the remote and are no longer there
|
|
{true, "error: cannot lock ref 'refs/remotes/origin/foo': unable to resolve reference 'refs/remotes/origin/foo': reference broken"},
|
|
// A race condition in http git-fetch where named refs were force-pushed during the update, would exit status 128
|
|
{true, "error: cannot lock ref 'refs/pull/123456/merge': is at 988881adc9fc3655077dc2d4d757d480b5ea0e11 but expected 7f894307ffc9553edbd0b671cab829786866f7b2"},
|
|
// A race condition with other local git operations, such as git-maintenance, would exit status 128 (well, "Unable" the "U" is uppercase)
|
|
{true, "fatal: Unable to create '/data/repositories/foo-org/bar-repo.git/./objects/info/commit-graphs/commit-graph-chain.lock': File exists."},
|
|
// Missing or unauthorized credentials, would exit status 128
|
|
{false, "fatal: Authentication failed for 'https://example.com/foo-does-not-exist/bar.git/'"},
|
|
// A non-existent remote repository, would exit status 128
|
|
{false, "fatal: Could not read from remote repository."},
|
|
// A non-functioning proxy, would exit status 128
|
|
{false, "fatal: unable to access 'https://example.com/foo-does-not-exist/bar.git/': Failed to connect to configured-https-proxy port 1080 after 0 ms: Couldn't connect to server"},
|
|
}
|
|
|
|
for _, c := range cases {
|
|
assert.Equal(t, c.recoverable, checkRecoverableSyncError(c.message), "test case: %s", c.message)
|
|
}
|
|
}
|