Hamidcha-Mosaab commented on issue #41528: URL: https://github.com/apache/superset/issues/41528#issuecomment-4831360333
@dosu Confirmed and resolved. The root cause was the **config variable name**: I had set `DASHBOARD_POSITION_DATA_LIMIT` (no prefix). `app.config` reflected my value (131072), but the frontend reads `dashboardInfo.common.conf.SUPERSET_DASHBOARD_POSITION_DATA_LIMIT` — the **`SUPERSET_`-prefixed** key, which is the one propagated via `FRONTEND_CONF_KEYS`. The non-prefixed variable was silently ignored, so the frontend kept falling back to the default 65535. After setting the correct key in `superset_config.py`: ```python SUPERSET_DASHBOARD_POSITION_DATA_LIMIT = 131072 ``` then restarting and doing a hard refresh, the blocking error is gone and I can move/resize charts and save. ✅ (PostgreSQL backend, so the larger `text` size is not a storage concern.) This makes the documentation/UX gaps even more worth addressing: 1. **Error message** should show the actual size vs. the limit *and* the exact config key name to change. 2. The **non-prefixed `DASHBOARD_POSITION_DATA_LIMIT` being silently ignored** is a real footgun — either accept both names or warn on startup if the deprecated/non-prefixed one is set. 3. **Document** `SUPERSET_DASHBOARD_POSITION_DATA_LIMIT` (correct name, default rationale, PostgreSQL note) in the config reference. I'm happy to open a PR for the improved error message (it already has `positionJSONLength` and `limit` in scope). Thanks for the pointers! -- 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]
