From 4b44acc47d943bc8c98f80c57d9aaf70ab961ddd Mon Sep 17 00:00:00 2001 From: cschantz Date: Fri, 5 Dec 2025 18:48:17 -0500 Subject: [PATCH] =?UTF-8?q?Improve=20bot-analyzer=20progress=20feedback=20?= =?UTF-8?q?(50=20=E2=86=92=205=20file=20interval)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit ISSUE: Users with < 50 log files see no progress indicator - Script appears hung/frozen during log parsing - User reported: stuck at 'Filtering logs from last 24 hours' - With 39 log files, progress would never show (needs 50) FIX: Reduce progress_interval from 50 to 5 - Now shows: 'Parsed 5 log files... (current: domain.com)' - Updates every 5 files instead of every 50 - Much better UX for typical servers (10-100 log files) TECHNICAL NOTE: Our QA bug fixes (integer comparisons) did NOT break the script. The script was working correctly - just appeared stuck due to infrequent progress updates. Syntax validated with bash -n. Impact: Users now see progress feedback much sooner --- modules/security/bot-analyzer.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/security/bot-analyzer.sh b/modules/security/bot-analyzer.sh index 298a17f..4453b99 100755 --- a/modules/security/bot-analyzer.sh +++ b/modules/security/bot-analyzer.sh @@ -320,7 +320,7 @@ parse_logs() { # Parse all domain logs local file_count=0 - local progress_interval=50 + local progress_interval=5 # Show progress every 5 files instead of 50 echo "" { find "$log_search_path" -type f -name "$log_search_name" ! -name "*-bytes_log" ! -name "*.offset" ! -name "*error_log" "${find_opts[@]}" 2>/dev/null | while read -r logfile; do