Bug description
In the course of regular Superset usage this appears frequently in the logs:
parsedatetime:eval now with context - False, False
Searching Superset issues for that line returns dozens of places where people have posted a log with that in it.
It's unclear to me what that means or how we could remove it. But if it's not necessary, this could be a good place to tidy up logging.
Screenshots/recordings
No response
Superset version
4.1.2
Python version
3.9
Node version
16
Browser
Not applicable
Additional context
No response
Checklist
- [x] I have searched Superset docs and Slack and didn't find a solution to my problem.
- [x] I have searched the GitHub issue tracker and didn't find a similar bug report.
- [x] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
Comment From: rusackas
@sadpandajoe @michael-s-molina wondering if y'all are seeing this too.
Comment From: thaikoh
I can confirm that issue with version 4.0.2:
2025-07-31 13:51:09,106:DEBUG:parsedatetime:eval now with context - False, False
... ~15 lines with this debug message
2025-07-31 13:51:09,232:DEBUG:parsedatetime:eval now with context - False, False
The field `timeseries_limit` is deprecated, please use `series_limit` instead.
2025-07-31 13:51:09,246:WARNING:superset.common.query_object:The field `timeseries_limit` is deprecated, please use `series_limit` instead.
Comment From: rusackas
@dosu any ideas how best to fix this or if there are any inherent dangers in removing/silencing these?
Comment From: dosubot[bot]
The "parsedatetime:eval now with context - False, False" messages come from the parsedatetime library, not Superset itself, and are logged at DEBUG level. There are no inherent dangers in silencing these—they're just verbose debug logs from a dependency.
To suppress them, set the parsedatetime logger to WARNING or higher in your Python logging config. For example, add this to your Superset config or your WSGI entrypoint:
import logging
logging.getLogger("parsedatetime").setLevel(logging.WARNING)
This will keep your logs clean without affecting Superset or parsedatetime functionality.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other 
Comment From: msyavuz
These logs are generated by the parsedatetime library, specifically from this line. They appear every time parse() is called.
Since the logging is coming from a dependency, our options are limited. Changing the log level or opening an issue upstream would be the most appropriate steps if this is causing disruption.