You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "rabindragogoi (via GitHub)" <gi...@apache.org> on 2023/12/28 09:35:09 UTC

[I] Receiving: werkzeug.exceptions.RequestEntityTooLarge: 413 Request Entity Too Large: The data value transmitted exceeds the capacity limit. [superset]

rabindragogoi opened a new issue, #26373:
URL: https://github.com/apache/superset/issues/26373

   When I am trying to add permissions to an existing role it is returning me 
    File "/opt/app-root/lib64/python3.11/site-packages/werkzeug/sansio/multipart.py", line 203, in next_event
       raise RequestEntityTooLarge()
   werkzeug.exceptions.RequestEntityTooLarge: 413 Request Entity Too Large: The data value transmitted exceeds the capacity limit.
   
   #### How to reproduce the bug
   
   1. Go to 'Roles'
   2. Click on 'any role that is created'
   3. Add a policy
   4. Click on Save
   
   ### Expected results
   
   The role should get save properly with the new permission.
   
   ### Actual results
   
    File "/opt/app-root/lib64/python3.11/site-packages/werkzeug/sansio/multipart.py", line 203, in next_event
       raise RequestEntityTooLarge()
   werkzeug.exceptions.RequestEntityTooLarge: 413 Request Entity Too Large: The data value transmitted exceeds the capacity limit.
   
   
   ### Additional context
   
   By default the max decoded part what wrekzeug support is 1000. Since the size of the decoded part is more that 1000, it is throwing up the error.
   https://forum.checkmk.com/t/request-entity-too-large-the-data-value-transmitted-exceeds-the-capacity-limit-web-log/40116
   
   Superset Team: need a quick fix for this.
   


-- 
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: notifications-unsubscribe@superset.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


Re: [I] Receiving: werkzeug.exceptions.RequestEntityTooLarge: 413 Request Entity Too Large: The data value transmitted exceeds the capacity limit. [superset]

Posted by "pashtet04 (via GitHub)" <gi...@apache.org>.
pashtet04 commented on issue #26373:
URL: https://github.com/apache/superset/issues/26373#issuecomment-1971062215

   Do we need to increase `max_form_parts` for werkzeug? -- https://github.com/pallets/werkzeug/blob/817aac4d2c71b83752e451d23f96ac26cfd7bbcd/src/werkzeug/wrappers/request.py#L94
   
   And how to achieve it?


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


Re: [I] Receiving: werkzeug.exceptions.RequestEntityTooLarge: 413 Request Entity Too Large: The data value transmitted exceeds the capacity limit. [superset]

Posted by "mertalpt (via GitHub)" <gi...@apache.org>.
mertalpt commented on issue #26373:
URL: https://github.com/apache/superset/issues/26373#issuecomment-3442828544

   @rusackas I am dealing with this now. Manual operations are a workaround but not a clean one. Do you know if there has been any development regarding this since the last update?


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


Re: [I] Receiving: werkzeug.exceptions.RequestEntityTooLarge: 413 Request Entity Too Large: The data value transmitted exceeds the capacity limit. [superset]

Posted by "kekwan (via GitHub)" <gi...@apache.org>.
kekwan commented on issue #26373:
URL: https://github.com/apache/superset/issues/26373#issuecomment-3470730747

   +1. This is still an issue, at least on Superset 3.0.3. Have not tested on newer versions


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


Re: [I] Receiving: werkzeug.exceptions.RequestEntityTooLarge: 413 Request Entity Too Large: The data value transmitted exceeds the capacity limit. [superset]

Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas closed issue #26373: Receiving:   werkzeug.exceptions.RequestEntityTooLarge: 413 Request Entity Too Large: The data value transmitted exceeds the capacity limit.
URL: https://github.com/apache/superset/issues/26373


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


Re: [I] Receiving: werkzeug.exceptions.RequestEntityTooLarge: 413 Request Entity Too Large: The data value transmitted exceeds the capacity limit. [superset]

Posted by "pashtet04 (via GitHub)" <gi...@apache.org>.
pashtet04 commented on issue #26373:
URL: https://github.com/apache/superset/issues/26373#issuecomment-2022297768

   I edit role directly in database
   
   ```
   insert into ab_permission_view_role (id, permission_view_id, role_id)
   values ('<id>', '<permission_view_id>', '<role_id>')
   ```
   
   Where:
   - <id> is a primary key
   - <permission_view_id> is a id from `public.ab_permission_view`. You need to lookup for necessary pair of `permission_id` and `view_menu_id`, for example `permission_id = 121`, where `121 == can_execute_sql_query` and `view_menu_id = 4448`, where `4448 == SQLLab`
   - <role_id> is a Role id in superset, you can view them from roles pages in url or in `ab_role` table


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


Re: [I] Receiving: werkzeug.exceptions.RequestEntityTooLarge: 413 Request Entity Too Large: The data value transmitted exceeds the capacity limit. [superset]

Posted by "giacomochiarella (via GitHub)" <gi...@apache.org>.
giacomochiarella commented on issue #26373:
URL: https://github.com/apache/superset/issues/26373#issuecomment-3878602831

   this is still an issue on Superset 6.0.0. When there are many users and many permissions (e.g. default role attached to a user through AUTH_USER_REGISTRATION_ROLE) I get 
   `{"errors": [{"message": "413 Request Entity Too Large: The data value transmitted exceeds the capacity limit.", "error_type": "GENERIC_BACKEND_ERROR", "level": "error", "extra": {"issue_codes": [{"code": 1011, "message": "Issue 1011 - Superset encountered an unexpected error."}]}}]}`
   the default role is basically a role attached to all users, hence the payload will increase very easily, on top of that the default role has default permissions which increases as long as new public dashboard is create for example


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


Re: [I] Receiving: werkzeug.exceptions.RequestEntityTooLarge: 413 Request Entity Too Large: The data value transmitted exceeds the capacity limit. [superset]

Posted by "dd-willgan (via GitHub)" <gi...@apache.org>.
dd-willgan commented on issue #26373:
URL: https://github.com/apache/superset/issues/26373#issuecomment-2433538127

   For me, this was happening because we had too many users, but the number of permissions the role had was small. We patched our Superset changing this [line](https://github.com/apache/superset/blob/e0172a24b85f172b04cb37c4c94a5bb5e533e325/superset/security/manager.py#L144)
   
   ```
   RoleModelView.edit_columns = ["name", "permissions", "user"]
   ```
   
   to
   
   ```
   RoleModelView.edit_columns = ["name", "permissions"]
   ```
   
   Disables editing users in the List Roles page but let us edit the permissions again


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


Re: [I] Receiving: werkzeug.exceptions.RequestEntityTooLarge: 413 Request Entity Too Large: The data value transmitted exceeds the capacity limit. [superset]

Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas commented on issue #26373:
URL: https://github.com/apache/superset/issues/26373#issuecomment-2813298620

   Assuming nobody is still dealing with this since it's been silent for about half a year. Correct me if I'm wrong and this needs to be revisited/reopened!


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


Re: [I] Receiving: werkzeug.exceptions.RequestEntityTooLarge: 413 Request Entity Too Large: The data value transmitted exceeds the capacity limit. [superset]

Posted by "torzsmokus (via GitHub)" <gi...@apache.org>.
torzsmokus commented on issue #26373:
URL: https://github.com/apache/superset/issues/26373#issuecomment-6168052364

   still an issue on Superset 5.0.0 , @rusackas I suggest to reopen.
   worked around by adding the permissions in `superset shell`, which is kind of suboptimal.
   [patching out the user list](https://github.com/apache/superset/issues/26373#issuecomment-2433538127) looks like a good direction for me (possibly behind a feature flag).


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org