attachaudit

Documentation

Overview

Package attachaudit names one thing gadak cannot fix and must not hide: an attachment whose bytes were cut off when they were uploaded.

A built-in origin (issuetap) capped stored attachment bytes at 8 MiB before gadak GDK-1614 lifted it, and the cap truncated silently — the row kept the filename and the mime, and the blob held the first 8 MiB. Those bytes are gone: the original file was never stored anywhere else, so there is nothing to recover from. What is left is to stop presenting the remainder as a whole file.

The signal is a size of exactly 8 MiB, which is a suspicion and not a verdict: a file can genuinely be 8388608 bytes long. Every string here says "may be" for that reason. The single owner of both the predicate and the wording lives in this package so `gadak doctor` and `gadak issue` cannot describe the same row differently.

Index

• Constants
• func Summary(n int) string
• func Suspect(size int64) bool

Constants

const Mark = "(exactly 8 MiB — may be truncated)"

Mark is the tag on one attachment line. Short, and hedged: the size alone cannot tell a cut file from a file that is really this long.

const TruncatedSize int64 = 8 << 20 // 8388608

TruncatedSize is the old built-in upload cap, in bytes. An attachment of exactly this size is the suspicion; anything else is not.

Functions

func Summary

func Summary(n int) string

Summary is the doctor line for n suspect attachments in one workspace. It is only true of a built-in-origin workspace: a Jira or Linear workspace never went through that upload cap, so the caller gates on the origin type, not on the count.

func Suspect

func Suspect(size int64) bool

Suspect reports whether size is the truncation signal.