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

^{Originally posted by sunker December 17, 2021}
When support for Metrics Insights was added to the GetMetricData api, a few new error codes were introduced. These should be handled as an error or possibly as a warning.

![Screenshot 2021-12-09 at 18 46 54](https://user-ima

When using the Superset cli, the import-datasources command using the "-s"/"--sync" flag does not work as intended. It seems as though the command runs as if the flag is not present.

How to reproduce the bug

1. Add an existing yaml file to superset by using the Superset cli
   superset import-datasources -p ~/datasets/data.yaml
2. Once the yaml file has been added, try using the comm

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

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.

Bug description

When in edit mode, this popup appears in the bottom right of the screen. If you are trying to rearrange by pulling from the bottom right of the screen (or in the case where you have multiple small insights), it can get in the way. Indicating edit mode might be better done another way

![image](https://user-images.githubusercontent.com/56287180/148297264-d5ab6f55-dd35-4f5e-b

ClickHouse supports renaming schemas using RENAME DATABASE command.

It's only supported for databases created using the ATOMIC engine - see https://clickhouse.com/docs/en/sql-reference/statements/rename/

Atomic engine has been available since v20.4.2.9-stable (see ClickHouse/ClickHouse@7928f2e) and has become the default since

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

Describe the bug
A clear and concise description of what the bug is.

Using ignore_malformed on a dynamic_template mapping of ip_range data_type throwing mapper_parsing_exception when trying to index a document with a new field that matches the template.
This used to work fine with elasticsearch 7.1.1 but creating an issue with opensearch 1.2.2.

Seems this is a known issue in elastic