This is kind of a follow up to #32677 and the PR #34762.

In #34762 we improved the test data source implementation by checking the body of the response from Tempo. The Tempo team is not comfortable making the body of a 404 response part of our stable API, so instead we are currently adding a separate endpoint specifically for testing: /api/echo (grafana/tempo#714).

Issue Description

What are you doing?

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

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

When you run npx prisma init everything executes without problems but the .gitignore file is being overwritten with the following content mentioned in Issue #3400

How to reproduce

1. Create an empty npm project
2. Create and add some contents to .gitignore
3. Run npx prisma init
4. Open the .gitignore file and notice it was overwritten

Expected beha

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

Please search TODO in class StandardBootstrapInitializerTest

Overview of the Issue

vtexplain panics on SHOW TABLES and SHOW FULL TABLES

Reproduction Steps

Steps to reproduce this issue, example:

1. Deploy the following vschema.json:

{
    "ks1": {
        "sharded": true,
        "tables": {
            "user": {
                "column_vindexes": [
                    {
                        "column":

Describe the Bug

Hi. I've added a repeater interface for my JSON object, and set the fields as follows:
itemid: integer
quantity: integer

When requested from the API, the numbers are returned as strings. Example response:
[{"itemid":"3","quantity":"5","stackable":true}]

Note that the boolean type works correctly as opposed to integers.

To Reproduce

• Create a collection with

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
If I pass 'Next 7 days' into the dateRange in query, the response is not a range over the next 7 days but only the day IN 7 days.

To Reproduce
Steps to reproduce the behavior:

1. Build a query like this:

const query: Query = {
    measures: [
      measure
    ],
    timeDimensions: [
      {
        dimension: 'Your.Dimension,
        dateRange: 'Next 7

Let's support at least reading "b3" header from a single string, most commonly traceid-spanid-1
It would also be nice to support optionally writing this, especially in message providers or others with constrained environments.

Expected behavior

As discussed on openzipkin/b3-propagation#21 and first implemented here: https://github.com/openzipkin/brave/blob/master/brave/src/main/java/bra