hasura / hasura/graphql-engine

setting "hasura.tracecontext" is not allowed

Open
#10,218 0 comments 0 reactions 0 assignees View on GitHub
k/bug
Dominant language
TypeScript
Stars
32.1k
Forks
3k
PR merge metrics
PR metrics pending

Description

### Version Information

Server Version: 2.38.0
CLI Version (for CLI related issue):

### Environment

Cent OS 7

### What is the current behaviour?

Just installed hasura on a vps, connected a postgres db, now when i try to create a schema i got this error
```
{
"arguments": [],
"error": {
"description": null,
"message": "setting \"hasura.tracecontext\" is not allowed",
"status_code": null
},
"prepared": false,
"statement": "SET LOCAL \"hasura.tracecontext\" = '{\"sampling_state\":\"1\",\"span_id\":\"83d863f4b0b56f59\",\"trace_id\":\"9dcc87ad5677171bb4dc1288cd1d6220\"}'"
}

```
### What is the expected behaviour?

should create a schema

### How to reproduce the issue?

1. fresh hasura installation on a vps
2.connect a postgres db
3.try to create schema for the db

Contributor guide

Open the contributing guide

Research direction

Start by reproducing schema creation with the reported Hasura and PostgreSQL setup, then inspect the failing SET LOCAL "hasura.tracecontext" statement shown in the error. Done means creating a schema succeeds without the setting error.

Written by the indexing model from the issue text.

Assessment

Tech stack
graphql, postgres
Domain
backend-api-design, databases
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.