profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/tirumaraiselvan/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Tirumarai Selvan tirumaraiselvan @hasura Bangalore, IN https://twitter.com/Tirumarai

hasura/gitkube 3582

Build and deploy docker images to Kubernetes using git push

hasura/3factor-example 359

Canonical example of building a 3factor app : a food ordering application

hasura/hasura-aws-stack 180

A complete production ready 100% serverless stack on AWS with Hasura

hasura/graphql-serverless 64

Example boilerplates for GraphQL backends hosted on serverless platforms

hasura/preview-actions 16

Starter kit to try out actions

k8s-platform-hub/hub-hdfs 6

Sample project to deploy HDFS on a Hasura cluster

hasura/preview-remote-joins 4

Starter kit to try out Remote Joins

pull request commenttirumaraiselvan/graphql-engine

rfc transforms

@ssbothwell Can this be merged? I think few changes might be required to account for the name (kriti) etc

ssbothwell

comment created time in 3 days

issue commenthasura/graphql-engine

Failed to Import Metadata Exported from v1.3.1

@b3tts32 Could you help us with the questions above if you are still facing this error?

zprobs

comment created time in 4 days

issue commenthasura/graphql-engine

support multiple JWT secrets

Hey folks, is it okay to assume that the issuer will be different for each of the JWT secrets?

kkshyu

comment created time in 8 days

issue closedhasura/graphql-engine

"database query error" with event trigger when mutation happens through v1/query or v2/query

{
	"type": "http-log",
	"timestamp": "2021-06-19T18:33:42.160+0000",
	"level": "error",
	"detail": {
		"operation": {
			"user_vars": {
				"x-hasura-role": "admin"
			},
			"error": {
				"internal": {
					"statement": "\n           SELECT hdb_catalog.insert_event_log($1, $2, $3, $4, $5)\n                ",
					"prepared": true,
					"error": {
						"exec_status": "FatalError",
						"hint": null,
						"message": "invalid input syntax for type json",
						"status_code": "22P02",
						"description": "The input string ended unexpectedly."
					},
					"arguments": ["(Oid 25,Just (\"public\",Binary))", "(Oid 25,Just (\"medical_providers\",Binary))", "(Oid 25,Just (\"MP\",Binary))", "(Oid 25,Just (\"MANUAL\",Binary))", "(Oid 114,Just (\"{\\\"row\\\":{\\\"is_direct_billing\\\":false,\\\"email\\\":null,\\\"status\\\":0,\\\"phone\\\":null,\\\"expired_at\\\":null,\\\"latitude\\\":\\\"10.68894\\\",\\\"address\\\":null,\\\"is_excluded\\\":false,\\\"name\\\":\\\"an giang\\\",\\\"medical_provider_id\\\":\\\"130a52ef-e155-4879-9a67-5c98672917c8\\\",\\\"updated_at\\\":\\\"2021-06-19T18:02:17.232539+00:00\\\",\\\"deleted_at\\\":null,\\\"geocode_data\\\":{\\\"Municipality\\\":\\\"Ch\\195\\162u \\196\\144\\225\\187\\145c\\\",\\\"Country\\\":\\\"VNM\\\",\\\"SubRegion\\\":\\\"An Giang\\\",\\\"Geometry\\\":{\\\"Point\\\":[105.148,10.68894]},\\\"Label\\\":\\\"B\\225\\187\\135nh Vi\\225\\187\\135n \\196\\144a Khoa Khu V\\225\\187\\177c T\\225\\187\\137nh An Giang, Ch\\195\\162u \\196\\144\\225\\187\\145c, Vi\\225\\187\\135t Nam\\\",\\\"Neighborhood\\\":\\\"Ph\\198\\176\\225\\187\\157ng V\\196\\169nh M\\225\\187\\185\\\"},\\\"province\\\":null,\\\"created_at\\\":\\\"2021-06-19T17:54:08.038602+00:00\\\",\\\"type\\\":\\\"BVDK_C\\\",\\\"warning_level\\\":0,\\\"longitude\\\":\\\"105.148\\\",\\\"description\\\":null}}\",Binary))"]
				},
				"path": "$.args",
				"error": "database query error",
				"code": "unexpected"
			},
			"request_id": "08561e4b-f940-44c4-af1f-22159fcd051a",
			"response_size": 1643,
			"query": {
				"resource_version": null,
				"args": {
					"payload": {
						"row": {
							"is_direct_billing": false,
							"email": null,
							"status": 0,
							"phone": null,
							"expired_at": null,
							"latitude": "10.68894",
							"address": null,
							"is_excluded": false,
							"name": "an giang",
							"medical_provider_id": "130a52ef-e155-4879-9a67-5c98672917c8",
							"updated_at": "2021-06-19T18:02:17.232539+00:00",
							"deleted_at": null,
							"geocode_data": {
								"Municipality": "Châu Đốc",
								"Country": "VNM",
								"SubRegion": "An Giang",
								"Geometry": {
									"Point": [105.148, 10.68894]
								},
								"Label": "Bệnh Viện Đa Khoa Khu Vực Tỉnh An Giang, Châu Đốc, Việt Nam",
								"Neighborhood": "Phường Vĩnh Mỹ"
							},
							"province": null,
							"created_at": "2021-06-19T17:54:08.038602+00:00",
							"type": "BVDK_C",
							"warning_level": 0,
							"longitude": "105.148",
							"description": null
						}
					},
					"name": "MP",
					"source": "default"
				},
				"version": 1,
				"type": "pg_invoke_event_trigger"
			}
		},
		"request_id": "08561e4b-f940-44c4-af1f-22159fcd051a",
		"http_info": {
			"status": 500,
			"http_version": "HTTP/1.1",
			"url": "/v1/metadata",
			"ip": "172.19.0.1",
			"method": "POST",
			"content_encoding": null
		}
	}
}

closed time in 9 days

deathemperor

issue commenthasura/graphql-engine

"database query error" with event trigger when mutation happens through v1/query or v2/query

This has now been fixed in 2.0.9 and rollout of the same version is happening on Cloud as well.

Sorry for the delay on this, there were 2 issues in this report and the second one turned out to be quite complicated.

deathemperor

comment created time in 9 days

issue openedhasura/graphql-engine

CLI: support `network` metadata used for tls_allowlist

Spec:

"network": {
     "tls_allowlist": [
       "certtest.dev.hasura.io",     // Can specify entire domain as a string
       {"host":"certtest.dev.hasura.io","port":443, "permit": ["self-signed"]} // Or use an object for finer-grained control.
     ]
 }

Server PR: https://github.com/hasura/graphql-engine-mono/pull/2153

created time in 10 days

issue commenthasura/graphql-engine

Correctly support the postgres "serializable" and "repeatable read" isolation levels

The lack of this retry behavior makes it impractical to use repeatable read or serializable in real applications with concurrency, as the error will bubble up the clients who will have no clue if the mutation should be attempted again or not.

We should atleast be surfacing serialization errors to the client through the code in the error. Will that work?

lorenzo

comment created time in 10 days

issue commenthasura/graphql-engine

Trackable custom function shows as non-trackable in the console

You are right. The console doesn't show non-SET OF as trackable. We will fix this.

lorenzo

comment created time in 10 days

issue commenthasura/graphql-engine

DB deadlocks during migration

@ifokeev Hasura doesn't truncate or drop the hdb_catalog.event_log table because it contains your historical events. We are figuring out a way to make the size of this table NOT affect the upgrade process.

matty-v

comment created time in 10 days

issue commenthasura/graphql-engine

DB deadlocks during migration

@ifokeev Can you give us the count of the hdb_catalog.event_log table

matty-v

comment created time in 10 days

created taghasura/graphql-engine

tagv2.0.9

Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.

created time in 10 days

push eventhasura/graphql-engine

Ikechukwu Eze

commit sha 8ca110b5bb2af799eda9649b7ed093c0b3bd2362

console: fix data sidebar not updated when a table is renamed https://github.com/hasura/graphql-engine-mono/pull/2237 GitOrigin-RevId: 53ee0ab1b786e8364df3af73396c97c6acb5470f

view details

Swann Moreau

commit sha 4887f70caa1b348db033b0d187b788a9e15b53d0

[server] revert #2078 "server/postgres: optimize SQL query generation with LIMITs" Fixes https://github.com/hasura/graphql-engine/issues/7453, by reverting #2078 (commit 47eaccdbfb3499efd2c9f733f3312ad31c77916f). https://hasurahq.slack.com/archives/CKFUG6RCH/p1629900718181700 https://github.com/hasura/graphql-engine-mono/pull/2204 GitOrigin-RevId: 53d5fee9c6008b26bc14213e5a16f6aba6d9c6b1

view details

Tirumarai Selvan

commit sha 9d592fde8760fba825fdf7b6723e0b96bca9c648

tag release v2.0.8 GitOrigin-RevId: 7e2c6333183ebf763ff37bda114219f5e7bf0951

view details

Kali Vara Purushotham Santhati

commit sha b50df8a24b0b96b7b2016068cc55646672caee0f

cli: add progress bar to migrate apply https://github.com/hasura/graphql-engine-mono/pull/1673 Co-authored-by: Aravind K P <8335904+scriptonist@users.noreply.github.com> GitOrigin-RevId: 59b8258557b2769853d0ca64032f453780a3cd7e

view details

Rakesh Emmadi

commit sha 7ca48decfb3718301a2fcdf4515db70fc6f0d05d

server/mssql: integrate insert mutation schema parser for MSSQL backend > ### Description > This PR is an incremental work towards [enabling insert mutations on MSSQL](https://github.com/hasura/graphql-engine-mono/pull/1974). In this PR, we generate insert mutation schema parser for MSSQL backend. ### Changelog - [ ] `CHANGELOG.md` is updated with user-facing content relevant to this PR. If no changelog is required, then add the `no-changelog-required` label. ### Affected components - [x] Server https://github.com/hasura/graphql-engine-mono/pull/2141 GitOrigin-RevId: 8595008dece35f7fded9c52e134de8b97b64f53f

view details

Sameer Kolhar

commit sha afbc30fec5992adf2fec89b2005c14ea264b5263

server: set `tracecontext` and `userInfo` for DML actions on PG sources https://github.com/hasura/graphql-engine-mono/pull/2174 GitOrigin-RevId: e8cfb4e330938e7dfb7232e58d2c1fc07bf97896

view details

Rakesh Emmadi

commit sha 10e01a4669982ef41a27c502aac8373cec39dbf8

server/mssql: refine aggregate field SQL generation code > ### Description > Correctly alias the aggregate field projections in site instead of aliasing them later stage. PS: I discovered this required change while [developing SQL generation for MSSQL inserts](https://github.com/hasura/graphql-engine-mono/pull/2248). ### Changelog - [ ] `CHANGELOG.md` is updated with user-facing content relevant to this PR. If no changelog is required, then add the `no-changelog-required` label. ### Affected components - [x] Server https://github.com/hasura/graphql-engine-mono/pull/2271 GitOrigin-RevId: 0d90fd8d8c0541b18ca9cb1197e413f3454bb227

view details

Vishnu Bharathi

commit sha 4b7a035012c624d685cbc96e49d51a9324c5582a

ci: introduce docker image scans https://github.com/hasura/graphql-engine-mono/pull/2177 GitOrigin-RevId: 03cbcbd0cdf1ec20941b7eed8842e5075ccee94d

view details

Nicolas Beaussart

commit sha 1b90360bb3b23d9d9af89f5132c8eda6cb871b39

console: add fixed height to html https://github.com/hasura/graphql-engine-mono/pull/2073 Co-authored-by: Martin Mark <74692114+martin-hasura@users.noreply.github.com> GitOrigin-RevId: b13f9e478b2569a5bd9b6c845c80df81a560cdc4

view details

Robert

commit sha f9dfb84c55d46e9502f69f332c449a4f0475e8fb

server: sort and prune error codes This sorts the constructors in `Hasura.Base.Error.Code`, and removes unused ones. https://github.com/hasura/graphql-engine-mono/pull/2277 GitOrigin-RevId: 2faf68edf70492c21a846d626951e65012a37e7c

view details

Shahidh K Muhammed

commit sha a41d34c62fe912bef06e10e91ad5fc1673005a05

docs: add a note about cloudflare to custom domains https://github.com/hasura/graphql-engine-mono/pull/2285 GitOrigin-RevId: 83561117c8ad939e5098db9bb285d8853f8d9b41

view details

Sooraj

commit sha d06dd037be5cb77ca272756c0d2e419bb1557131

add oss issue template https://github.com/hasura/graphql-engine-mono/pull/2178 GitOrigin-RevId: 8c5a181bb087d118164af962f4d5874a795255b8

view details

paritosh-08

commit sha 8c05efb6d97eb06ecc1fb7dcf66a7b692e817a61

server: disable mutation for materialised views The materialized views cannot be mutated, so this commit removes the option to run mutation on the materialized views via graphql endpoint. Before this, users could have tried running mutation for the materialized views using the graphql endpoint (or from HGE console), which would have resulted in the following error: ``` JSON { "errors": [ { "extensions": { "internal": { "statement": "WITH \"articles_mat_view__mutation_result_alias\" AS (DELETE FROM \"public\".\"articles_mat_view\" WHERE (('true') AND (((((\"public\".\"articles_mat_view\".\"id\") = (('20155721-961c-4d8b-a5c4-873ed62c7a61')::uuid)) AND ('true')) AND ('true')) AND ('true'))) RETURNING * ), \"articles_mat_view__all_columns_alias\" AS (SELECT \"id\" , \"author_id\" , \"content\" , \"test_col\" , \"test_col2\" FROM \"articles_mat_view__mutation_result_alias\" ) SELECT json_build_object('affected_rows', (SELECT COUNT(*) FROM \"articles_mat_view__all_columns_alias\" ) ) ", "prepared": false, "error": { "exec_status": "FatalError", "hint": null, "message": "cannot change materialized view \"articles_mat_view\"", "status_code": "42809", "description": null }, "arguments": [] }, "path": "$", "code": "unexpected" }, "message": "database query error" } ] } ``` So, we don't want to generate the mutation fields for the materialized views altogether. https://github.com/hasura/graphql-engine-mono/pull/2226 GitOrigin-RevId: 4ef441764035a8039e1c780d454569ee1f2febc3

view details

Karthikeyan Chinnakonda

commit sha 94f3ad041cf43bbe2d88f61636c2568d0e248804

server: generalize event triggers - incremental PR 1 https://github.com/hasura/graphql-engine-mono/pull/2269 GitOrigin-RevId: c4ea0cc41a1c66d418219cc1d41bf95656426733

view details

Anon Ray

commit sha dc1ac69dac502a91f324043ada5067fcb2efa934

server: add parameterized query hash for websocket logs https://github.com/hasura/graphql-engine-mono/pull/2061 Co-authored-by: Naveen Naidu <30195193+Naveenaidu@users.noreply.github.com> GitOrigin-RevId: bf26b804d93b19ef7fc15c71fec80fb6d6632e64

view details

Sameer Kolhar

commit sha 3bd7b9049d428ef3db003951985cb400fa18b317

server: don't propogate `tracecontext` and `userinfo` for GraphQL queries on PG backends https://github.com/hasura/graphql-engine-mono/pull/2294 GitOrigin-RevId: c4be1c04a676154a233e75b31ff00b689443b933

view details

Robert

commit sha 565e816716ce63f8c5748ea78e8d7468ebdae2b5

server: don't use Show to encode error codes This moves the previous (illegal) `Show` instance for `Hasura.Base.Error.Code` to a `ToJSON` instance, and uses that in the error `ToJSON` instances. Addressing https://github.com/hasura/graphql-engine-mono/pull/2277#issuecomment-911557169. This PR is against #2277. It adds a replacement derived `Show` instance, which is used: - in the derived `Show` instance for `QErr` - in some unit tests Mostly verified that we didn't otherwise rely on the hand-rolled `Show` instance by compiling without it (and a faked `QErr` instance), and seeing that the only compile failures were in tests. (Compare the individual commits.) https://github.com/hasura/graphql-engine-mono/pull/2279 GitOrigin-RevId: 678fe241a14bd0c9aaf5b267efc510ad9d619dd7

view details

Sameer Kolhar

commit sha f6af5796191c5f7411d8c505b1682728cd23a317

server,docs,tests: add support for `connection_parameters` to `pg_add_source` API https://github.com/hasura/graphql-engine-mono/pull/1690 GitOrigin-RevId: a7be66c9af3143b34133d197f7858ba22f442a41

view details

Vishnu Bharathi

commit sha 2329c16ce909051f1226fe4be8f72267bdf30e8b

cli: embed cli-ext as exe in case of windows https://github.com/hasura/graphql-engine-mono/pull/2295 Co-authored-by: Kali Vara Purushotham Santhati <72007599+purush7@users.noreply.github.com> GitOrigin-RevId: 16a03d33d5bf4d45a71ba79b3b775fba3176a1e8

view details

push time in 10 days

issue commenthasura/graphql-engine

Hasura 2.0: cannot insert NULL on nullable column

Ah, sorry. I thought you wanted to insert a relationship row as well. So, basically you want one query which inserts a parent row and optionally children rows.

@nicuveo Any thoughts here?

tokestermw

comment created time in 11 days

IssuesEvent

issue commenthasura/graphql-engine

"database query error" with event trigger when mutation happens through v1/query or v2/query

@joserocha3 @frandiox Yes, we have a fix in progress and expect to land in few days. I will re-open this issue and change the title to reflect the same.

deathemperor

comment created time in 11 days

issue commenthasura/graphql-engine

Return 1000 after the event is locked

Related: https://github.com/hasura/graphql-engine/issues/7425

pl1094602077a

comment created time in 15 days

issue commenthasura/graphql-engine

Hasura 2.0: cannot insert NULL on nullable column

In 2.0, we introduced not allowing null values to column operators. This is based on the discussion here: https://github.com/hasura/graphql-engine/issues/704

We also introduced a flag: HASURA_GRAPHQL_V1_BOOLEAN_NULL_COLLAPSE: true for preserving the older behaviour but it doesn't work over columns/relationships. For more details, refer to this comment: https://github.com/hasura/graphql-engine/issues/704#issuecomment-864727792

Unfortunately, the only solution is to rewrite the query as so:

mutation MyMutation {
  insert_tableA(objects: {relationship: {data: {}}}) {
    returning {
      relationship {
        id
        rel_text
      }
    }
  }
tokestermw

comment created time in 16 days

issue commenthasura/graphql-engine

DB deadlocks during migration

@ifokeev That could be a likely cause since we create an index on the event_log table in the v1.3 to v2.0 migration. We recommend cleaning up historical events before upgrading: https://hasura.io/docs/latest/graphql/core/event-triggers/clean-up.html

matty-v

comment created time in 16 days

issue closedhasura/graphql-engine

Hasura Action to Self-Signed Cert

I need to be able to use Hasura Actions to post to a server with a self-signed cert which I do not control. Or more generically, using Actions to a certificate that isn't trusted and which I do not have the ability ahead of time to get the certs for. Many programming languages or tools have an option for --insecure or some way to say either generically (or for a specific site) to ignore the cert chain. Is that possible in Hasura?

closed time in 17 days

its-a-feature

issue commenthasura/graphql-engine

Hasura Action to Self-Signed Cert

This is now possible in v2.0.8. Go to console -> Settings page (top right gear icon) -> Insecure TLS Allowlist

its-a-feature

comment created time in 17 days

issue commenthasura/graphql-engine

DB deadlocks during migration

@zee-hussain @matty-v Unfortunately, this is getting pretty hard to replicate on our end. Would it be possible to "clone" your prod environment and try it out there? The database locks query that I shared earlier will reveal what is blocking that query.

matty-v

comment created time in 18 days

created taghasura/graphql-engine

tagv2.0.8

Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.

created time in 18 days

push eventhasura/graphql-engine

Sandeep Raj Kumar

commit sha dc952cc872e7e89758975108b962bcf99ed9054a

Docs: Add Azure monitor APM integration docs https://github.com/hasura/graphql-engine-mono/pull/2074 Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Rikin Kachhia <54616969+rikinsk@users.noreply.github.com> GitOrigin-RevId: b0f26f61563fa3dd2a85730afe83f9a2101bd898

view details

Rakesh Emmadi

commit sha fa152d842deb24786d8591a8f347b2f2f78f62b4

server/postgres: optimize SQL query generation with LIMITs > ### Description > This PR supersedes https://github.com/hasura/graphql-engine-mono/pull/1484. Apply `limit` to the table selection before joining relationship rows to improve query performance. ### Changelog - [x] `CHANGELOG.md` is updated with user-facing content relevant to this PR. If no changelog is required, then add the `no-changelog-required` label. ### Affected components - [x] Server ### Related Issues -> Fix https://github.com/hasura/graphql-engine/issues/5745 ### Solution and Design > Prior to this change, we apply `LIMIT` and `OFFSET` to the outer selection from sub-query which includes joins for relationships. Now, we move `LIMIT` and `OFFSET` (if present) to inner selection of base table. But, this isn't done always! If there are order by relationships' columns we apply at the outer selection. To know more, please refer to [source code note](https://github.com/hasura/graphql-engine-mono/pull/2078/files#diff-46d868ee45d3eaac667cebb34731f573c77d5c9c8097bb9ccf1115fc07f65bfdR652). ```graphql query { article(limit: 2){ id title content author{ name } } } ``` Before: ```sql SELECT coalesce(json_agg("root"), '[]') AS "root" FROM ( SELECT row_to_json( ( SELECT "_4_e" FROM ( SELECT "_0_root.base"."id" AS "id", "_0_root.base"."title" AS "title", "_0_root.base"."content" AS "content", "_3_root.or.author"."author" AS "author" ) AS "_4_e" ) ) AS "root" FROM ( SELECT * FROM "public"."article" WHERE ('true') ) AS "_0_root.base" LEFT OUTER JOIN LATERAL ( SELECT row_to_json( ( SELECT "_2_e" FROM ( SELECT "_1_root.or.author.base"."name" AS "name" ) AS "_2_e" ) ) AS "author" FROM ( SELECT * FROM "public"."author" WHERE (("_0_root.base"."author_id") = ("id")) ) AS "_1_root.or.author.base" ) AS "_3_root.or.author" ON ('true') LIMIT 2 ) AS "_5_root" ``` cost ``` Aggregate (cost=0.73..0.74 rows=1 width=32) -> Limit (cost=0.15..0.71 rows=2 width=32) -> Nested Loop Left Join (cost=0.15..223.96 rows=810 width=32) -> Seq Scan on article (cost=0.00..18.10 rows=810 width=72) -> Index Scan using author_pkey on author (cost=0.15..0.24 rows=1 width=36) Index Cond: (article.author_id = id) SubPlan 1 -> Result (cost=0.00..0.01 rows=1 width=32) SubPlan 2 -> Result (cost=0.00..0.01 rows=1 width=32) ``` After: ```sql SELECT coalesce(json_agg("root"), '[]') AS "root" FROM ( SELECT row_to_json( ( SELECT "_4_e" FROM ( SELECT "_0_root.base"."id" AS "id", "_0_root.base"."title" AS "title", "_0_root.base"."content" AS "content", "_3_root.or.author"."author" AS "author" ) AS "_4_e" ) ) AS "root" FROM ( SELECT * FROM "public"."article" WHERE ('true') LIMIT 2 ) AS "_0_root.base" LEFT OUTER JOIN LATERAL ( SELECT row_to_json( ( SELECT "_2_e" FROM ( SELECT "_1_root.or.author.base"."name" AS "name" ) AS "_2_e" ) ) AS "author" FROM ( SELECT * FROM "public"."author" WHERE (("_0_root.base"."author_id") = ("id")) ) AS "_1_root.or.author.base" ) AS "_3_root.or.author" ON ('true') ) AS "_5_root" ``` cost: ``` Aggregate (cost=16.47..16.48 rows=1 width=32) -> Nested Loop Left Join (cost=0.15..16.44 rows=2 width=100) -> Limit (cost=0.00..0.04 rows=2 width=72) -> Seq Scan on article (cost=0.00..18.10 rows=810 width=72) -> Index Scan using author_pkey on author (cost=0.15..8.18 rows=1 width=36) Index Cond: (article.author_id = id) SubPlan 1 -> Result (cost=0.00..0.01 rows=1 width=32) SubPlan 2 -> Result (cost=0.00..0.01 rows=1 width=32) ``` https://github.com/hasura/graphql-engine-mono/pull/2078 Co-authored-by: Evie Ciobanu <1017953+eviefp@users.noreply.github.com> GitOrigin-RevId: 47eaccdbfb3499efd2c9f733f3312ad31c77916f

view details

Sooraj

commit sha c0ea2b0a04d82e7235fc9c59a3142658da8c3f60

console: oss test optimisation https://github.com/hasura/graphql-engine-mono/pull/1837 GitOrigin-RevId: e638ca400a275a2cba7fec64f157c989b2147b8e

view details

Vijay Prasanna

commit sha 479c0b3980a6683947a6cb651f14bb35e444e3ab

console: add quotes to column names https://github.com/hasura/graphql-engine-mono/pull/2127 GitOrigin-RevId: 6c1596ad132a400f2c2864712d7ffa3a4a7ae2f2

view details

Rikin Kachhia

commit sha 47f8bc9b42f93d0a9ad1e3995600ef42ec2260fd

server: update non-existent object error messages https://github.com/hasura/graphql-engine-mono/pull/2098 GitOrigin-RevId: 61a10560a9df50afd80a6186e0d23b74874e3265

view details

Rakesh Emmadi

commit sha 11a31b3a753aaa0c399377d8d66fe968ae532f54

server/rfc: mutations on MSSQL backend [rendered](https://github.com/hasura/graphql-engine-mono/blob/rakeshkky/rfc/mssql-mutations/rfcs/mutations-mssql.md) Open for suggestions/improvements. Please comment. https://github.com/hasura/graphql-engine-mono/pull/1974 GitOrigin-RevId: 4c27d9da99e6b41efafa1c6e5557731cb16c488f

view details

Rikin Kachhia

commit sha 53703a24b84c9b344a7605c78797378581ca1ac2

docs: remove use of 'default' in column presets page https://github.com/hasura/graphql-engine-mono/pull/2129 GitOrigin-RevId: d3d3d3974ef39215dc9ecefba5cb643887ff980a

view details

Aniket Deshpande

commit sha 27005544126ddd8671c37c7179b493a7e36b3bcc

bq: test table customization features https://github.com/hasura/graphql-engine-mono/pull/2062 Co-authored-by: Rikin Kachhia <54616969+rikinsk@users.noreply.github.com> GitOrigin-RevId: 5573efd1b28e088d5730c7d22e16889dc852b5fe

view details

Rikin Kachhia

commit sha e0fd67ef8f1cc8753f81189b9cf9c16cec4eeb17

docs: fix graphiql rendering https://github.com/hasura/graphql-engine-mono/pull/2138 GitOrigin-RevId: 38b53507714d04d1fbc6db651df9dce1c5c64e71

view details

Karthikeyan Chinnakonda

commit sha eaf02117874ccc139e5efe1d26a71866ba134dc9

docs: document clean up steps for scheduled triggers https://github.com/hasura/graphql-engine-mono/pull/2077 Co-authored-by: Rikin Kachhia <54616969+rikinsk@users.noreply.github.com> GitOrigin-RevId: 7f4fae18052b46122106a0fb57ab4b5c0c000b18

view details

Praveen Durairaju

commit sha 40f4b8003ee1604da1605a0e668b194b99636067

community: fix sample apps metadata for v3 config https://github.com/hasura/graphql-engine-mono/pull/2137 GitOrigin-RevId: 83c2ef3a24a57a53f33e9b272bebf20341c5fc9b

view details

Sai Krishna Prasad Kandula

commit sha d7a52b9342a90d28a0e2b1db63199a23fb772006

readme: use cloud signup endpoint for "Deploy to Hasura" CTA https://github.com/hasura/graphql-engine-mono/pull/2142 GitOrigin-RevId: 212d766978841d5609d726f8359586185f3cbb59

view details

Divi

commit sha 20b2814a02e3bd30c6a3eed187d24ede9bc5ada2

ci: add job to build and push base image https://github.com/hasura/graphql-engine-mono/pull/1924 GitOrigin-RevId: dd402886e67a535aa90afa13f8d9714d92a5daf7

view details

hasura-bot

commit sha 50a9dae13bd3c24b5b82c91d5fa1759a8c0e745f

server/bigquery: run tests in CI GITHUB_PR_NUMBER: 7398 GITHUB_PR_URL: https://github.com/hasura/graphql-engine/pull/7398 https://github.com/hasura/graphql-engine-mono/pull/2106 Co-authored-by: Abby Sassel <3883855+sassela@users.noreply.github.com> GitOrigin-RevId: 8a20401040c0ca216f8c3c2416243ff4a92b166d

view details

David Overton

commit sha 20f7a6e726ffde20559985d3cd3ef11731ae35de

server: fix untrack_function for non-default source https://github.com/hasura/graphql-engine-mono/pull/2152 GitOrigin-RevId: 339b365044443cec6a83e1a6b3ec06677dc51e1d

view details

Funmilayo E. Olaiya

commit sha 313e4e1a52c8a15dc83efac172e2a37dd4e91d50

docs: updates doc for `_eq`, `_ne` operators to include a caveat for null values ### Description This PR adds an info. on the `eq` and `ne` operators to include a caveat for null values. ### Changelog - [x] `CHANGELOG.md` is updated with user-facing content relevant to this PR. If no changelog is required, then add the `no-changelog-required` label. ### Affected components - [x] Docs ### Related Issues https://github.com/hasura/graphql-engine/issues/2167 ### Affected pages https://deploy-preview-352--hasura-docs-mono.netlify.app/graphql/core/queries/query-filters.html https://github.com/hasura/graphql-engine-mono/pull/352 Co-authored-by: Rikin Kachhia <54616969+rikinsk@users.noreply.github.com> GitOrigin-RevId: 2d707d6496b76866e3510ef7969c9877e606a9dd

view details

Nicolas Beaussart

commit sha 582ebcca9c73e3811a437e44190e87b825b2f96c

console: move to dart-sass https://github.com/hasura/graphql-engine-mono/pull/2155 GitOrigin-RevId: 2c86a617314d9c308c295c18cdbcba8060e2075c

view details

Ikechukwu Eze

commit sha 4330798a71e9ec62924da4e7ae4e8b0b00523441

console: fix error due too rendering inconsistent object's message https://github.com/hasura/graphql-engine-mono/pull/2116 GitOrigin-RevId: a2d8230bf685a201991adfe33f548c9e9c24e44b

view details

hasura-bot

commit sha 80ea4875a176c5b690863ff2df4471bf1c54dbec

docs: Add source in pg_dump docs GITHUB_PR_NUMBER: 7421 GITHUB_PR_URL: https://github.com/hasura/graphql-engine/pull/7421 https://github.com/hasura/graphql-engine-mono/pull/2160 Co-authored-by: Prashant Shahi <11138844+prashant-shahi@users.noreply.github.com> GitOrigin-RevId: 21bea209d0dad658d2512565c8dddb8e72f19399

view details

Auke Booij

commit sha 3fb7d9bc3de3b8a4753e09af7771935ade8fb299

server: remove unused bahnql test This removes the file `bahnql_query.yaml`, which is no longer being used. a509a86eaa791439c5c090bdc3796b3f9a07753c (hasura/graphql-engine#1117) changed the way we test the remote schema feature from using external GraphQL services to running our own mini GraphQL server for testing purposes. This gives us a lot of in-codebase flexibility on the behavior of "remote" GraphQL servers. During this work, the `bahnql_query.yaml` test was swapped out for the `simple2_query.yaml` test. The former essentially tests if a field from a remote schema can be fetched, whereas the latter tests whether an entry can be fetched from the (non-remote!) database. It's not clear to me why `bahnql_query.yaml` was no longer used. In any case, the relevant setup code was removed, and this test can no longer be run. Presumably we test such basic functionality already in many other ways. https://github.com/hasura/graphql-engine-mono/pull/2102 GitOrigin-RevId: c01b7f7ec5c767c874bca2ddad991eb81a0e2809

view details

push time in 18 days

issue commenthasura/graphql-engine

DB deadlocks during migration

Hmm, would you be able to run the following query to check which query is blocking the above DDL:

SELECT
    activity.pid,
    activity.usename,
    activity.query,
    blocking.pid AS blocking_id,
    blocking.query AS blocking_query
FROM pg_stat_activity AS activity
JOIN pg_stat_activity AS blocking ON blocking.pid = ANY(pg_blocking_pids(activity.pid));
matty-v

comment created time in 22 days

issue commenthasura/graphql-engine

[sql-server] Support event triggers on SQL Server

This is being worked on currently. We expect it to be available in few weeks (3-4).

coco98

comment created time in 22 days

issue commenthasura/graphql-engine

Cannot combine a JWT token with other X-Hasura-* headers

Related to https://github.com/hasura/graphql-engine/issues/1601

ledburyb

comment created time in 23 days

issue commenthasura/graphql-engine

DB deadlocks during migration

@matty-v What is the size (num of rows) in your hdb_catalog.event_log table? In 2.0, we add an index to this table and it could be a costly operation if the event_log table is huge. We recommend pruning this table to remove historical events before doing the upgrade: https://hasura.io/docs/latest/graphql/core/event-triggers/clean-up.html

matty-v

comment created time in 23 days

issue openedhasura/graphql-engine

document `delete_scheduled_event` API

created time in 25 days

issue commenthasura/graphql-engine

[Console] Hasura v2.0.0 beta 2 - Error when manually trigger events from console

@frandiox Thanks for the confirmation. The original issue was for manual event trigger which has been fixed in 2.0.7

We have found another issue when mutation happens through v1/query or v2/query which is related to your comment. We will fix this ASAP. Sorry for the inconvenience.

deathemperor

comment created time in a month

issue openedhasura/graphql-engine

event_trigger: show better errors during http_error

Currently, when we don't receive a proper response from event trigger (say, connection timeout, response timeout, etc), then the invocation log has something like this:

{
"type":"client_error",
"version": 2,
"data": {}
}

We should change client_error to something like http_error and have another key, inside data, called error_type which can be the Show of the HTTPExceptionContent: https://hackage.haskell.org/package/http-client-0.7.8/docs/Network-HTTP-Client.html#t:HttpExceptionContent

created time in a month