reqstorm 2.4.0

See what a long batch is doing while it runs.

• Logging: each retry with its reason and wait, hosts paused after a 429, token refreshes, retry rounds, rejected records and final failures; every attempt at DEBUG. Without options it follows your application's logging setup through the "reqstorm" logger.
• Per-run logging, independent of the application: log_level="INFO", log_file="logs/", log_format="json". Log files are never overwritten: a directory or {time} gives a time-stamped file per run, and an existing run.log becomes run-2.log.
• A progress line that keeps moving: refreshed on a timer, with requests in flight, retries, the rate over the last minute, retry rounds, paused hosts and the time left. progress= also takes a function (ProgressInfo), stream() supports it, and total= gives generators a percentage.
• Read the output during the run: results are written at least once a second (flush_interval), never with half a line, and SQLite files use WAL mode so they can be read meanwhile.
• Command line: -v / -vv, -q, --log-file, --log-json, --flush-interval; --help now explains every option with its default, examples, exit codes and a link to the guide.

Guide: https://reqstorm.github.io/guide/observability/