Redundant timezone conversion in feast materialize logs
When executing feast materialize, the given timestamp is converted to the local timezone using astimezone(). This conversion appears redundant and somewhat confusing.
Expected Behavior
# feast materialize 2025-04-04T21:00:00 2025-04-05T15:00:00
Materializing 1 feature views from 2025-04-04 21:00:00 to 2025-04-05 15:00:00 into the postgres online store.
Current Behavior
# feast materialize 2025-04-04T21:00:00 2025-04-05T15:00:00
Materializing 1 feature views from 2025-04-05 02:30:00+05:30 to 2025-04-05 20:30:00+05:30 into the postgres online store.
Possible Solution
Removing .astimezone() from log statement.