imsnif/bandwhich

Feature: dump current state to logfile

Open

#123 opened on Jan 16, 2020

View on GitHub
 (8 comments) (1 reaction) (0 assignees)Rust (7,686 stars) (237 forks)batch import
enhancementhelp wanted

Description

Sometimes when troubleshooting a network issue, it might be useful to log all the information the tool currently has in a log file for parsing and perhaps a more thorough look than can fit in the UI.

Note that this should work both for when paused and not paused.

A good key binding might be "d", but other ideas are welcome as well.

The format for dumping to a file should be the same one we use for "raw_mode".

Contributor guide

Tech stack
rust
Domain
cli
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Rust programmingUnderstanding of bandwhich codebaseRaw mode format
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Start by examining the existing 'raw mode' output format in the codebase (likely in src/ or similar) to understand the data structure. Then implement a new command or keybinding that writes the current state to a log file in the same format, ensuring it works both when paused and unpaused. Review the issue comments for discussion on keybinding preferences and any edge cases.