Dashboard Data Failure for Positive Timezones

[ay-bh]

Bug Description

The dashboard fails to display data due to backend endpoints /api/power & /api/terros generating 500 errors when handling requests with positive timezone offsets (+XX:XX). Requests with negative offsets (-XX:XX) work as expected.

Issue Demonstration:

• Failing case (with +05:30 offset): Link to failing request
• Successful case (with -02:00 offset): Link to successful request

Local server logs suggest a ValidationError related to startTime and endTime query parameters, indicating an issue with datetime format validation (Marshmallow schema). Server logs

Steps to Reproduce

1. Set your browser's timezone to a location with a positive offset (e.g., Mumbai). Guide to change timezone in Chrome
2. Attempt to access datasets via the dashboard.

Alternatively:

• Directly send GET requests to the aforementioned endpoints.

Expected Behavior

The backend should correctly process requests across all timezones or potentially become timezone agnostic by standardising to a single timezone.

Screenshots

Environment

• OS: macOS Sonoma 14.0
• Browser: Brave, Version 1.63.162