Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error reports can not be sent because too large #15146

Closed
williamdes opened this issue Apr 2, 2019 · 11 comments
Closed

Error reports can not be sent because too large #15146

williamdes opened this issue Apr 2, 2019 · 11 comments
Assignees
Labels
Bug A problem or regression with an existing feature
Milestone

Comments

@williamdes
Copy link
Member

Describe the bug

Reproduce issue #14611 and try to send error report

Error report cannot be sent because 413 (Request Entity Too Large)

Github does not allow me to post the request as CURL (in the comment) because it is too long.

There was an error creating your Issue: body is too long (maximum is 65536 characters).

@williamdes williamdes changed the title Error reports can not be sent because to large Error reports can not be sent because too large Apr 2, 2019
@williamdes williamdes added the Bug A problem or regression with an existing feature label Apr 2, 2019
@williamdes
Copy link
Member Author

exception[incomplete]: false
exception[partial]: true

This seems like total nonsense.

@williamdes
Copy link
Member Author

williamdes commented Apr 2, 2019

REQUEST_AS_HAR_ISSUE_15146.json

Use show report details

@kartik1000
Copy link
Contributor

I am trying to do it @williamdes

@williamdes
Copy link
Member Author

Okay, I was working on it, but I let you fix it ;)

Do not forget to check that the stack property exists and is an array

And find an arbitrary length to truncate context lines :)

See attached exception for tests
stackObject.json.txt

Do not forget to use : https://caniuse.com

That would be stupid to have an error at the error reporting level.

@williamdes
Copy link
Member Author

cc @kartik1000

@kartik1000
Copy link
Contributor

Hey, I tried but I . don't know why I am getting Network Error while opening JS error report, although there is actually no network issue i assure. This was done on demo server
Screenshot 2019-04-02 at 8 26 28 PM
This was from localhost
Screenshot 2019-04-02 at 8 31 58 PM

@kartik1000
Copy link
Contributor

I am onto it @williamdes :)

@williamdes
Copy link
Member Author

williamdes commented Apr 2, 2019

@kartik1000 You successfully reproduced the error, this is a network error caused by an very very long request body :)

@williamdes williamdes self-assigned this Apr 28, 2019
@williamdes williamdes added this to the 4.8.6 milestone Apr 28, 2019
williamdes added a commit that referenced this issue Apr 28, 2019
[ci skip]
Signed-off-by: William Desportes <williamdes@wdes.fr>
@kartik1000
Copy link
Contributor

Sorry @williamdes, couldn't work on this one :(

@williamdes
Copy link
Member Author

No problem @kartik1000 this one is not very funny to solve :)

williamdes added a commit to williamdes/phpmyadmintest that referenced this issue May 1, 2019
Fixes phpmyadmin#15146
See: 926a9f4

Aligned with php code (that does quite the same truncate on the context stack)

Signed-off-by: William Desportes <williamdes@wdes.fr>
@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 21, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Bug A problem or regression with an existing feature
Projects
None yet
Development

No branches or pull requests

2 participants