-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Show request id on test failures #3556
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
Conversation
Right now on errors, only the expected and the actual responses are shown. The actual response sometimes may not have all the information, and you may have to look at the logs. In this case, request id would be of great help to get the extra information from the logs.
|
Deploy preview for hasura-docs ready! Built with commit 2a637e1 |
|
Review app for commit 541dbfc deployed to Heroku: https://hge-ci-pull-3556.herokuapp.com |
|
Review app for commit af53a02 deployed to Heroku: https://hge-ci-pull-3556.herokuapp.com |
|
Review app for commit c8c0290 deployed to Heroku: https://hge-ci-pull-3556.herokuapp.com |
|
Review app for commit 4e45edd deployed to Heroku: https://hge-ci-pull-3556.herokuapp.com |
|
Review app for commit 2a637e1 deployed to Heroku: https://hge-ci-pull-3556.herokuapp.com |
|
Review app https://hge-ci-pull-3556.herokuapp.com is deleted |
Right now on errors, only the expected and the actual responses are shown. The actual response sometimes may not have all the information, and you may have to look at the logs. In this case, request id would be of great help to get the extra information from the logs.
Right now on errors, only the expected and the actual responses are
shown. The actual response sometimes may not have all the information,
and you may have to look at the logs. In this case, request id would be
of great help to get the extra information from the logs.
Description
Affected components
Related Issues
Solution and Design
Server checklist
Catalog upgrade
Does this PR change Hasura Catalog version?
Metadata
Does this PR add a new Metadata feature?
run_sqlauto manages the new metadata through schema diffing?run_sqlauto manages the definitions of metadata on renaming?export_metadata/replace_metadatasupports the new metadata added?GraphQL
Breaking changes
No Breaking changes
There are breaking changes:
Metadata API
Existing
querytypes:argspayload which is not backward compatibleJSONschemaGraphQL API
Schema Generation:
NamedTypeSchema Resolve:-
nullvalue for any input fieldsLogging
JSONschema has changedtypenames have changedSteps to test and verify
Limitations, known bugs & workarounds