bigquery

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

Describe the bug
Using a time dimension on a runningTotal measure on Snowflake mixes quoted and unquoted columns in the query. This fails the query, because Snowflake has specific rules about quoted columns. Specifically:

• All unquoted column names are treated as upper case
• Quoted column names are case sensitive.

So "date_from" <> date_from

To Reproduce
Steps to reproduce

Currently when you sort the list of features (or experiments) it only kept for that session and not saved. We would like to persist this sort state to local storage.

we should validate updates to the site by running sbt mdoc on relevant PRs

The functions in this file should be factored out to a separate utility lib as they are reused in bitcoin-etl https://github.com/blockchain-etl/ethereum-etl/blob/develop/ethereumetl/misc_utils.py

It would be great to do a somewhat rigorous analysis of whether there are performance issues when query is written in Logica vs SQL.

Sending a rest call to delete a job specification throws 404 where as grpc call works fine. Steps to reproduce

curl -X DELETE "http://localhost:9100/v1/project/my-project/namespace/kush/helloworld" -H  "accept: application/json"

Task Overview

• Currently timestamp_column is the only configuration that is needed to be configured globally in the model config section (usually it's being configured in the properties.yml under elementary in the config tag).
• Passing the timestamp_column as a test param will enable running multiple tests with different timestamp columns. For example running a test with updated_at colum

To encourage readers to share chapters, let's add support for the Web Share API. Browser support is mostly mobile-only, so we should use feature detection before adding the UI.

We should also add an analytics event when someone uses the share button.

Over time we've had some things leak into the diff methods that make it more cumbersome to use BigDiffy via code instead of CLI.

For example diffAvro here https://github.com/spotify/ratatool/blob/master/ratatool-diffy/src/main/scala/com/spotify/ratatool/diffy/BigDiffy.scala#L284

User has to manually pass in schema otherwise we they receive a non-informative error regarding null schema, add

Broken Links

basedosdados.github.io/mais/style_data/

• Failed: HTTP Status 403 at normalizadas
  \n---\nGSheets

@medvedev1088
Hi,
I found that there ara two kinds of output in transactions.json.
One is nonstandard, and the other is pubkeyhash.
I thought the nonstandard output is the op_return output, but i found outputs of many (not all ) coinbase txs also are nonstandard. And address of miner is like“nonstandard3318537dfb3135df9f3d950dbdf8a7ae68dd7c7d”.
Here is an example:
transaction: {
"hash":