sfirke commented on issue #24561: URL: https://github.com/apache/superset/issues/24561#issuecomment-1621822736
I agree it seems like a bug in Superset. There's not really anyone "from Superset" because it's an open-source project without a single owner. Anyone could submit a pull request to fix this. I don't think it will be a priority for most people because it doesn't affect anyone who isn't using old year values. If you're able to poke around in the Superset code to figure this out, that would be ideal. Otherwise one thing you might be able to do is try testing this on different versions of Superset. If it's fixed in the new 3.0.0rc1, great. If nothing else, try other date values and see if you can learn anything. Does 1838 work? Is there a max date that returns this same NaN? I thought it could be related to Pandas dates out of bounds, but 1938 seems too modern for that: https://pandas.pydata.org/docs/user_guide/timeseries.html#timestamp-limitations -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
