mirror of
https://github.com/hasura/graphql-engine.git
synced 2024-12-16 01:44:03 +03:00
dd46aa6715
When upgrading to GHC v9.4, we noticed a number of failures because the sort order of HashMaps has changed. With this changeset, I am endeavoring to mitigate this now and in the future. This makes one of two changes in a few areas where we depend on the sort order of elements in a `HashMap`: 1. the ordering of the request is preserved with `InsOrdHashMap`, or 2. we sort the data after retrieving it. Fortunately, we do not do this anywhere where we _must_ preserve order; it's "just" descriptions, error messages, and OpenAPI metadata. The main problem is that tests are likely to fail each time we upgrade GHC (or whatever is providing the hash seed). [NDAT-705]: https://hasurahq.atlassian.net/browse/NDAT-705?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ PR-URL: https://github.com/hasura/graphql-engine-mono/pull/9390 GitOrigin-RevId: 84503e029b44094edbbc298651744bc2843c15f3 |
||
|---|---|---|
| .. | ||
| actions | ||
| apollo_federation | ||
| compression | ||
| endpoints | ||
| event_triggers | ||
| explain | ||
| graphql_introspection | ||
| graphql_mutation | ||
| graphql_query | ||
| graphql_validation | ||
| heterogeneous | ||
| horizontal_scale/basic | ||
| inconsistent_objects | ||
| logging | ||
| naming_conventions | ||
| openapi | ||
| query_cache | ||
| remote_schemas | ||
| scheduled_triggers | ||
| schema/duplication | ||
| subscriptions | ||
| unauthorized_role | ||
| v1 | ||
| v2 | ||
| webhooks/request_context | ||
| clear_db_bigquery.yaml | ||
| clear_db_citus.yaml | ||
| clear_db_mssql.yaml | ||
| clear_db.yaml | ||