bigquery

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

If you add multiple projects in GrowthBook, the dropdown list in the left navigation is sorted by creation date. We should instead sort them alphabetically. The dropdown is rendered in packages/front-end/components/Layout/ProjectSelector.tsx

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.

Bigquery external table API supports auto schema detection for external table source by a boolean property - ref.

If the target field names are the same as the source fields in the Google Spreadsheet, it should be better not to supply any schema rather than sp

Support copy into queries

check-translations-lengths.yml is a GH action that helps ensure consistent line numbers for translations of chapter contents. It's triggered on any change to HTML or MD files.

However, there are many MD files that are unrelated to chapter contents in this repo and

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":