Bug description
ADD filters type is value ,Minified React error #31; visit https://reactjs.org/docs/error-decoder.html?invariant=31&args[]=object%20with%20keys%20%7Bs%2C%20e%2C%20c%7D&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
How to reproduce the bug
- Go Dashboards
- add type is value filter , save!
- click filter
Screenshots/recordings
Superset version
master / latest-dev
Python version
3.9
Node version
16
Browser
Chrome
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
Is this a customized version of Superset? Or could you give us an example filter (using example datasets) that causes this? I/we haven't seen this... and it seems like everyone would be running into it.
Comment From: tamarinkeisari
Did you manage to solve your problem?
I'm encountering the same issue as this
Thank you!
Comment From: ChristophSonnleitner
I am also facing the same issue
Comment From: rusackas
I think we need some reproducible steps here, otherwise this might be closed as inactionable.
Meanwhile let's see if @dosu has any advice.
Comment From: dosubot[bot]
Based on the codebase and recent changelogs, there have been a lot of changes and fixes around filters, especially in the 4.x series. The filter components (like Select, Range, and Time) all use standard React patterns and default exports, and I didn't find any recent changes that would obviously cause React error #31 by themselves.
This error is often triggered by either a misconfigured build (like multiple React versions loaded), or by a race condition or invalid child/component being renderedāsomething that can happen if filter state updates and re-renders overlap in just the wrong way. The recent refactors and performance tweaks to filter state, modals, and rendering increase the risk of these edge cases, especially if your environment has any customizations or non-standard dependencies.
If you can, try running Superset in development mode (non-minified) to get the full error message and stack trace. Also, double-check your node_modules for duplicate React versions and make sure your environment matches the expected versions for master/latest-dev. If you have any custom plugins or modifications, try disabling them to see if the issue persists.
If you can share the exact filter configuration (dataset, column, filter type, and any special settings) that triggers the error, that would help narrow it down further. Right now, the most likely causes are either a subtle race in filter state/rendering or an environment/build issue, not a single recent code change.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report š | Other 
