NASA-AMMOS / NASA-AMMOS/plandev
Timeout error checking constraints
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 128
- Forks
- 33
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 12
Description
I'm getting a timeout error when running constraint checks against a simple test plan, using Aerie 1.0.2. The constraint check has worked on other plans, and for another user on this plan.
Seeing this error in the hasura log:
{
"detail": {
"http_info": {
"content_encoding": null,
"http_version": "HTTP/1.1",
"ip": "137.79.200.77",
"method": "POST",
"status": 200,
"url": "/v1/graphql"
},
"operation": {
"error": {
"code": "unexpected",
"error": "http exception when calling webhook",
"internal": {
"error": {
"message": "Response timeout",
"request": {
"host": "aerie_merlin",
"method": "POST",
"path": "/constraintViolations",
"port": 27183,
"queryString": "",
"requestHeaders": {
"Content-Type": "application/json",
"User-Agent": "hasura-graphql-engine/v2.12.1",
"X-B3-ParentSpanId": "29f1f34f10e61493",
"X-B3-SpanId": "6483a86012540eca",
"X-B3-TraceId": "f4e2efe74ae6b1c3"
},
"responseTimeout": "ResponseTimeoutMicro 30000000",
"secure": false
},
"type": "http_exception"
},
"request": {
"body": {
"action": {
"name": "constraintViolations"
},
"input": {
"planId": 4
},
"request_query": "#graphql\n query CheckConstraints($planId: Int!) {\n checkConstraintsResponse: constraintViolations(planId: $planId) {\n violationsMap: constraintViolations\n }\n }\n ",
"session_variables": {
"x-hasura-role": "admin"
}
},
"headers": [],
"transformed_request": null,
"url": "http://aerie_merlin:27183/constraintViolations"
},
"response": null
},
"path": "$"
},
"query": {
"query": "#graphql\n query CheckConstraints($planId: Int!) {\n checkConstraintsResponse: constraintViolations(planId: $planId) {\n violationsMap: constraintViolations\n }\n }\n ",
"variables": {
"planId": 4
}
},
"request_id": "9f3002ed-aa52-4e7f-95b2-a8603946f9b4",
"request_mode": "error",
"response_size": 984,
"user_vars": {
"x-hasura-role": "admin"
}
},
"request_id": "9f3002ed-aa52-4e7f-95b2-a8603946f9b4"
},
"level": "error",
"timestamp": "2023-01-31T18:21:26.046+0000",
"type": "http-log"
}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report names the Hasura GraphQL request to Aerie's /constraintViolations endpoint for planId 4, but no source file or test. Start by reproducing that request and tracing the 30-second response timeout through the constraint-checking entry point. Done means the constraint check completes successfully for the affected plan without the reported timeout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, java
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100