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

422 Unprocessable Entity in Descendant Tree and Family Descendent Tree report. #517

Open
ccrighton opened this issue May 14, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@ccrighton
Copy link

ccrighton commented May 14, 2024

Gramps details:

Gramps 5.2.2
Gramps Web API 2.3.0
Gramps Web Frontend 24.5.0
Gramps QL 0.3.0
locale: en
multi-tree: false
task queue: true

Steps to trigger error:

  • Select Reports->Descendent Tree or Family Descendent Tree
  • Set the The main family for the report to any family from the list.
  • Click Generate

Result:

422 Unprocessable Entity
The request was well-formed but was unable to be followed due to semantic errors.

Other details:

This behaviour can be triggered in the demo system by following these steps. Demo System

If the The main family for the report is left unset, a report is generated by not from the family that is needed.

@DavidMStraub
Copy link
Member

Can you please provide the error that is shown in the logs?

@DavidMStraub DavidMStraub added the bug Something isn't working label May 31, 2024
@ccrighton
Copy link
Author

There is no error in the logs. I have a docker deployment of gramps. I'm seeing the same behaviour at demo.grampsweb.org.

This is the raw response from my server:

HTTP/1.1 422 UNPROCESSABLE ENTITY
Server: gunicorn
Date: Sat, 01 Jun 2024 02:56:09 GMT
Connection: close
Content-Type: text/html; charset=utf-8
Content-Length: 190
Vary: Accept-Encoding

From the demo system:

HTTP/2 422 
server: nginx/1.25.3
date: Sat, 01 Jun 2024 03:02:10 GMT
content-type: text/html; charset=utf-8
content-length: 190
vary: Accept-Encoding
strict-transport-security: max-age=31536000
X-Firefox-Spdy: h2

There isn't an obvious way to turn on debug logging in the docker image.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants