probelabs/goreplay · error
binary output is only available in PRO version
Error message
binary output is only available in PRO version
What it means
Sentinel error from the open-source BinaryOutput.PluginWrite: binary output is a paywalled PRO feature, so every write attempt in the OSS build returns this error instead of sending data to the replay address.
Source
Thrown at output_binary.go:38
TrackResponses bool `json:"output-binary-track-response"`
}
// BinaryOutput plugin manage pool of workers which send request to replayed server
// By default workers pool is dynamic and starts with 10 workers
// You can specify fixed number of workers using `--output-tcp-workers`
type BinaryOutput struct {
address string
}
// NewBinaryOutput constructor for BinaryOutput
// Initialize workers
func NewBinaryOutput(address string, config *BinaryOutputConfig) PluginReadWriter {
return &BinaryOutput{address: address}
}
// PluginWrite writes a message to this plugin
func (o *BinaryOutput) PluginWrite(msg *Message) (n int, err error) {
return 0, errors.New("binary output is only available in PRO version")
}
// PluginRead reads a message from this plugin
func (o *BinaryOutput) PluginRead() (*Message, error) {
return nil, errors.New("binary output is only available in PRO version")
}
func (o *BinaryOutput) String() string {
return "Binary output: " + o.address + " (PRO version required)"
}
// Close closes this plugin for reading
func (o *BinaryOutput) Close() error {
return nil
}
View on GitHub (pinned to 251e45abd2)
Solutions
- Use the PRO version of gor if binary output is required
- Switch to --output-file or --output-tcp which are available in the OSS build
- Remove --output-binary flags from the command line
Defensive patterns
Strategy: fallback
When it happens
Trigger: Thrown at output_binary.go:38 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of probelabs/goreplay@251e45abd2 (2026-09-02).
Data as JSON: /api/errors/ed5587bbbcadac80.
Report an issue: GitHub.