chore: drop tool-name markers from source comments
Seventeen comments opened with a tag naming the tool that wrote them. The tag goes and each comment keeps its reasoning, now starting as a plain sentence. None of the reasoning changes. The AGENTS.md note in .gitignore drops the story of how the file got into the tree and keeps the one fact a reader needs: its advice to run go fmt is destructive on this CRLF working tree. Comments only; no code, build or test changes.
This commit is contained in:
13 files changed
+19
-20
No files matched your search
@@ -180,7 +180,7 @@ type Backuper struct {
|
||||
// just-finished Job still inside its TTL window. ErrAlreadyExists is kept only as a
|
||||
// defensive no-op against the astronomically unlikely suffix collision.
|
||||
//
|
||||
// ponytail: unique names mean two truly simultaneous taps can schedule two backup
|
||||
// Unique names mean two truly simultaneous taps can schedule two backup
|
||||
// Pods; both mount the world PVC read-only so neither corrupts anything, and if they
|
||||
// land on different nodes the RWO attach fails one cleanly. Add single-flight-on-
|
||||
// running only if a real double-tap storm ever shows up.
|
||||
@@ -200,7 +200,7 @@ func (b *Backuper) Backup(ctx context.Context, serverName, formerOwner string) e
|
||||
func jobNameSuffix() string {
|
||||
var b [4]byte
|
||||
if _, err := rand.Read(b[:]); err != nil {
|
||||
// ponytail: crypto/rand only fails if the OS RNG is gone — unrecoverable.
|
||||
// crypto/rand only fails if the OS RNG is gone — unrecoverable.
|
||||
panic("backupjob: crypto/rand: " + err.Error())
|
||||
}
|
||||
return hex.EncodeToString(b[:])
|
||||
|
||||
Reference in new issue
Block a user