Best use
Share one scoped Go artifact: Single-package reproductions.
Go pastebin for code and goroutine traces
Services, tools, and goroutine traces. Pastebin.ai preserves the submitted source, adds a line-numbered reading view, and lets you choose retention and access before sharing.
Go sharing decisions at a glance
Check the source, runtime context, and privacy risks that matter when you share Go text.
Context to include
Name the source: Common inputs include .go, test failures, panic output, and goroutine dumps. State the tool or runtime that reads them.
Details to remove
Review before upload: Inspect each Go value, comment, path, and identifier; the checklist below names the format-specific risks.
What to include in a reviewable Go paste
Common inputs include .go, test failures, panic output, and goroutine dumps. Limit the artifact to the lines and context a recipient needs to understand its purpose.
Single-package reproductions
Keep the Go example limited to this review goal and its required inputs.
Concurrency questions
For Go review, Name the producing tool or runtime, preserve exact source text, and include only the context another person needs to understand the artifact.
Test and panic diagnostics
Use representative placeholders so this Go example preserves structure without exposing live values.
A small Go paste example
The Go sample below uses a small, representative form of .go, test failures, panic output, and goroutine dumps. Replace live values with clear placeholders while keeping the structure another reader needs.
ctx, cancel := context.WithTimeout(context.Background(), time.Second)
defer cancel()
result, err := client.Fetch(ctx, id)Add the context a reviewer needs
Include the Go version, operating system and architecture when relevant, module dependencies, race-detector status, and exact test or run command. Keep goroutine states around a deadlock.
- Name the tool or runtime that consumes this Go text.
- Show the command and the expected versus actual Go result.
- Keep only the smallest Go artifact that preserves the issue.
Review the paste before it leaves
Review environment output, module paths, service endpoints, request payloads, credentials, user data, and goroutine arguments before sharing traces.
- Start a Go review with unlisted visibility.
- Match expiry to the window for single-package reproductions.
- Encrypt this Go paste when readable server storage is outside the trust boundary.
Next Go step: Code-sharing workflow adds this context: Turn a focused snippet or diagnostic into a reviewable link.
Go paste questions
Short answers about Go formatting, runtime context, and safer sharing.
What helps reproduce a Go concurrency bug?+
Include the Go version, race-detector result, minimal goroutines and channels, and the exact command that triggers the issue.
Should a goroutine dump be public?+
Usually no. It can expose paths, arguments, endpoints, and operational structure; redact it and use limited visibility and retention.