mirror of
https://github.com/hanzoai/s3.git
synced 2026-10-30 14:59:09 +00:00
zooqueen
dd74d3e6d6
hanzoai/s3 was an AGPL-3.0 MinIO fork whose network-copyleft blocks embedding
and reselling as a managed service. Replace it wholesale with a fork of
SeaweedFS (github.com/seaweedfs/seaweedfs, Apache-2.0, Go) which ships a
built-in S3 gateway + Filer.
- License: AGPL-3.0 -> Apache-2.0 (upstream LICENSE kept verbatim, incl.
"Copyright 2025 Chris Lu"); NOTICE added crediting SeaweedFS. No AGPL/BUSL/
SSPL/GPL or enterprise ("ee") files remain.
- Module: go.mod path set to github.com/hanzoai/s3 with a self-replace
(replace github.com/seaweedfs/seaweedfs => ./) so the ~1800 internal Go files
keep their upstream import paths with zero churn. Internal identifiers and
import paths are intentionally NOT renamed.
- CLI rebrand: the binary is built as `s3` (was `weed`); root usage, per-command
help/usage/flag strings, shell autocomplete program name, and the product name
in CLI output now read "Hanzo S3" / `s3`. Users never see `weed`.
(e.g. `s3 server`, `s3 filer`, `s3 master`, `s3 volume`, `s3 s3`, `s3 mount`.)
- Build: `make` (or `go build -o s3 ./weed`) builds the `s3` binary green;
`cmd/weed-db` and `cmd/weed-sql` also build; `go vet ./weed/command/` clean.
- README/LLM.md rewritten for Hanzo S3; AGENTS.md/CLAUDE.md symlinks preserved.
- Dropped a 33MB prebuilt Mach-O `stress` binary upstream had committed; `.gitignore`
updated to ignore the `s3` build output.
48 lines
1.5 KiB
Go
48 lines
1.5 KiB
Go
package reader
|
|
|
|
import (
|
|
"testing"
|
|
|
|
"github.com/seaweedfs/seaweedfs/weed/pb/filer_pb"
|
|
"github.com/stretchr/testify/assert"
|
|
)
|
|
|
|
// IsCreate / IsDelete are the small but routing-critical predicates
|
|
// the dispatcher uses to decide which match path applies. Both were
|
|
// previously exercised only through end-to-end Tick/Match tests; pin
|
|
// them directly here.
|
|
|
|
func TestEventIsCreate_PopulatedNewEntryNoOldEntry(t *testing.T) {
|
|
e := &Event{NewEntry: &filer_pb.Entry{Name: "k"}}
|
|
assert.True(t, e.IsCreate())
|
|
assert.False(t, e.IsDelete())
|
|
}
|
|
|
|
func TestEventIsDelete_PopulatedOldEntryNoNewEntry(t *testing.T) {
|
|
e := &Event{OldEntry: &filer_pb.Entry{Name: "k"}}
|
|
assert.True(t, e.IsDelete())
|
|
assert.False(t, e.IsCreate())
|
|
}
|
|
|
|
func TestEventBothEntries_NeitherCreateNorDelete(t *testing.T) {
|
|
// An update event carries both old and new; the predicates are
|
|
// strict (one or the other, not both) so the router can route
|
|
// updates through the dedicated path rather than treating them
|
|
// as creates or deletes.
|
|
e := &Event{
|
|
OldEntry: &filer_pb.Entry{Name: "k"},
|
|
NewEntry: &filer_pb.Entry{Name: "k"},
|
|
}
|
|
assert.False(t, e.IsCreate(), "update event must not classify as create")
|
|
assert.False(t, e.IsDelete(), "update event must not classify as delete")
|
|
}
|
|
|
|
func TestEventNoEntries_NeitherCreateNorDelete(t *testing.T) {
|
|
// A degenerate event with neither side populated must not classify
|
|
// as either; otherwise a metadata-only filer event with no bucket
|
|
// payload could trigger spurious dispatches.
|
|
e := &Event{}
|
|
assert.False(t, e.IsCreate())
|
|
assert.False(t, e.IsDelete())
|
|
}
|