Devtrack pulse/fixes

[mahesh-solanke]

DevTrack SDK v0.4.1 - Bugfix Release

🐛 Issues Fixed

Issue 1: Dashboard Displaying Incorrect Summary Statistics

Problem:

• Dashboard KPI cards were showing malformed data like {"1": 10} instead of proper metrics
• Users couldn't see correct values for total requests, unique endpoints, average latency, etc.
• This made the dashboard essentially unusable for monitoring

Root Cause:

• DuckDB's conn.description sometimes returns generic column names like ["1"] or ["NUMBER"] instead of actual SQL column names
• The code was directly using these invalid column names to create dictionaries, resulting in wrong keys
• This affected get_stats_summary(), get_logs_by_path(), and get_logs_by_status_code() methods

Fix:

• Added robust fallback mechanism that uses known column names when DuckDB returns invalid descriptions
• Applied consistent error handling across all database query methods
• Ensures proper field names are always used regardless of DuckDB's column description quirks

Impact:

• ✅ Dashboard now displays correct metrics (total requests, unique endpoints, avg/min/max duration, success/error counts)
• ✅ KPI cards are fully functional and show accurate data
• ✅ All database queries work consistently across different DuckDB versions
• ✅ Users can now properly monitor their API health through the dashboard

---

Issue 2: Request Detail View Not Displaying Styles in New Window

Problem:

• When users clicked on request IDs to view details in a new window, some saw a plain white screen without any styling
• The detail view appeared broken, making it impossible to read request information
• This was particularly problematic for users with certain browser configurations or CSP policies

Root Cause:

• document.write() method can fail in certain browser environments or with Content Security Policies
• HTML escaping issues could break the document structure
• No fallback mechanisms if the primary method failed

Fix:

• Implemented multiple fallback methods for maximum compatibility:
  1. Blob URL (primary) - Works with CSP, no size limits
  2. Data URL (fallback) - For older browsers
  3. document.write() (final fallback) - Universal support
• Improved HTML escaping with manual escaping function for better security
• Enhanced HTML structure with proper meta tags and viewport settings
• Better error handling with automatic fallback to modal view

Impact:

• ✅ Request detail views now display correctly with full styling across all browsers (Chrome, Firefox, Safari, Edge)
• ✅ Works with Content Security Policies enabled
• ✅ Improved security with proper HTML escaping
• ✅ Better user experience - users can now properly inspect request details

---

📊 Additional Improvements

• Enhanced API Logging: Improved logging in fetchStats() for better debugging
• Database Query Robustness: All database query methods now handle DuckDB quirks consistently
• Better Error Handling: More graceful error recovery across the codebase

---

✅ Testing

• 48/48 automated tests passing (100% pass rate)
• All fixes verified across multiple browsers and environments
• DuckDB compatibility tested with different versions
• CSP compatibility verified

---

🔄 Migration

No breaking changes! This is a backward-compatible bugfix release.

Simply upgrade:

pip install --upgrade devtrack-sdk

All existing functionality remains the same. The fixes are automatically applied.

---

📝 Summary

This release fixes two critical bugs that were preventing users from properly using the dashboard:

1. Dashboard statistics now display correctly - Users can see accurate metrics
2. Request detail views work across all browsers - Users can inspect request details properly

Both issues are now resolved, and the dashboard is fully functional for monitoring API health.

[codacy-production]

Codacy's Analysis Summary

8 new issues (≤ 0 issue)
7 new security issues
5 complexity
6 duplications

Review Pull Request in Codacy →

✨ AI Reviewer available: add the codacy-review label to get contextual insights without leaving GitHub.

[mahesh-solanke]

I have reviwed Codacy Production / Codacy Static Code Analysis carefully, these shall not be blocker for this merge as

• Specified lines does not have any risk