analytics

Hi,

first thanks for this awesome software. But I have some trouble and I don't know how to proceed. First I try to find out what else I could provide for this report to be a good bug report.

First, I use the latest version (v1.14.0) from openSUSE build Service. I know, I should compile it by my self to avoid any other causes for this behavior. But for now I still use this package from there

Issue:

When adding a new dimension, we can't select the ne operator on the UI as shown below:

But we can add it in the json model like below (work around)

The Mixed Time-Series chart type allows for configuring the title of the primary and the secondary y-axis.
However, while only the title of the primary axis is shown next to the axis, the title of the secondary one is placed at the upper end of the axis where it gets hidden by bar values and zoom controls.

How to reproduce the bug

1. Create a mixed time-series chart
2. Configure axi

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

Before opening, please confirm:

• I have searched for duplicate or closed issues and discussions.
• I have read the guide for submitting bug reports.
• I have done my best

Is your feature request related to a problem?

Person display name is not customizable. Currently we show email if that property exists, then name and otherwise User <id>. Code https://github.com/PostHog/posthog/blob/b1f304754fa37a2f72fe4b3ad51f8ed6bdf707b7/frontend/src/scenes/persons/PersonHeader.tsx#L17

Describe the solution you'd like

Would be nice if that could be customizable.

it's becoming more time-consuming and error-prone to manually re-test all the demos following internal refactorings and API adjustments.

now that the API is fleshed out a bit, it's possible to test a large amount of code (non-granularly) without having to simulate all interactions via Puppeteer or similar.

a lot of code can already be regression-tested by simply running all the demos and val

When entering a repository path, users should be able to hit TAB for autocomplete, like in bash.

Instead of creating on the fly an Iceberg table with Trino and run queries against it, use static resources for setting up an Iceberg test environment which can be used to read Iceberg v1 / v2 tables and guard trino-iceberg plugin against regresssions.

Related discussion: trinodb/trino#11642 (comment)

Describe the bug
OpenSearch is able to warn a use about upcoming deprecation of API used. Some of deprecation messages refers to Elasticsearch version instead of OpenSearch.
There are deprecations seen by .Net client automated test:

299 OpenSearch-1.3.0-e45991597c86ba1bbcc36ee1dfdc165197a913af "Parameter [boost] on field [name] is deprecated and will be removed in 8.0"
299 OpenS

In Big Query there is a function array_concat_agg that aggregates array fields by concatenating the arrays. In Snowflake there is a flatten function that can unnest nested arrays into single array. I am looking for similar functionality in duckdb.

select flatten([[1, 2], [2, 3], [4, 5]] would return [1, 2, 2, 3, 4, 5]
I would also need a distinct option:
`select flatten(DISTINCT [[1, 2],