What happened:
I have UTC selected for my dashboard, but traces show in local time.

(also the seconds and milliseconds are in gray, which strikes me as odd though doesn't impact usability)

What you expected to happen:
Trace times should respect my selected time.

**How

• global_kill_test.go
• graceshutdown_test.go
• readonly_test.go

Issue Description

What are you doing?

I am trying to strongly type my application using Typescript and Sequelize. I have noticed th

Issue split from hasura/graphql-engine#6951

our pytest output has a pretty low signal:noise ratio, and it's often difficult to understand the cause of a test failure, if there is one. [Example: a 8600-line log for what turned out to be a flaky test that passed on a second run](https://app.circleci.com/pipelines/github/hasura/graphql-engine-mono/10008/workflows/5e17c7

Sometimes it is needed to store compressed data in the DB. Unfortunately not all the DBs have built-in compression and FUSE compressed FSes are not available for every OS. So it may make sense to store compressed binary blobs in the DB.

Unfortunately when one sees them in DBeaver he sees them compressed, but often they are needed uncompressed. So it'd be nice to have a feature to decompress the

Bug description

On windows, I run prisma format and note the unusual file ending. The lines are all LF, but the very last line is CRLF.

This causes issue on my Linux CI where it formats it ending in LF's only, causing a diff to occur and the build to fail.

How to reproduce

1. On windows do prisma format
2. Open in HxD or similar
3. See attached:

![image](https://user-images.g

Environment

Knex version: 0.21.1
OS: docker node:latest

I'd like to be able to write my migrations (and seed) files as es modules with the .mjs file extension like I'm doing with all my other javascript files.

I'd like to be able to run these migrations from within node (not via the cli) like this:

db/migrations/00001-users-table.mjs:
    export const up = knex => knex.sche

This issue is for adding unit tests for DefaultDataSourceCreator.
If you are interested, please leave a message.

Scenario:

• Single vttablet, connecting to external MySQL (happens to be RDS Aurora, but I doubt it matters).
• Single unsharded keyspace (keyspace3), no vschema, with a single table, containing a single row
• Test program using the Python pymysql driver, using the CLIENT.FOUND_ROWS flag, and updating a single row to it's current key value (i.e. no rows are updated, but a single row

Preflight Checklist

• I have completed all Troubleshooting Steps.
• I'm on the latest version of Directus.
• There's no other issue that already describes my problem.

Describe the Bug

I know this is

Issue description

This option will improve performance in many scenarios
https://dev.mysql.com/worklog/task/?id=8134

https://www.facebook.com/weixiang.zhai/posts/678596755543802

Describe the bug

Serverless: Deprecation warning: Variables resolver reports following resolution errors:
              - Cannot resolve variable at "provider.environment.CUBEJS_APP": Value not found at "self" source,
              - Cannot resolve variable at "functions.cubejsProcess.events.0.event.resource": Value not found at "self" source
            From a next major this will be

Skipped bats test here: #2035

1. dolt conflicts cat on a table with no conflicts should return empty
2. Running SQL on an active merge where conflicts are resolved with --ours or --theirs should not throw conflict warnings.