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

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

Is this related to a new or existing framework?

New framework - remix.run

Is this related to a new or existing API?

Storage

Is this related to another service?

S3

Describe the feature you'd like to request

Was able to integrate the Auth section with no issue, but was trying to integrate Storage in remix data loaders, but because amplify do

Bug description

If you open the events table the items have a human description e.g. "2 minutes ago"

If you leave the page open and then load new events in at the top of the table (at least with auto load turned on) we don't update the humanised descriptions so the first row can be "2 minutes ago" and the second "a few seconds ago" even though their timestamps are correct

![2022-03-03

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.

Syntax for changing Iceberg table properties

ALTER TABLE an-iceberg-table SET PROPERTIES a-property-name = 'a-value'

Implementation tips

Implement the method io.trino.spi.connector.ConnectorMetadata#setTableProperties in io.trino.plugin.iceberg.IcebergMetadata.

Use org.apache.iceberg.BaseTable#updateProperties for updating table properties.

Test tips

Add

Is your feature request related to a problem? Please describe.
There seems to be duplication of logic in the code for Cloud Plugins. This is an opportunity for us to streamline the codebase and refactor these classes. This issue stems from these comments in #2096.

Describe the solution you'd like

Related with nunomaduro/phpinsights#23 will be a great idea to allow set all commands parameters from config/insights.php when is used with php artisan insights.

Maybe something like:

'parameters' => '--format=json -d memo