^{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

Chore

Describe the chore

We already have an Expo guide here:

And an example here: https://github.com/supabase/supabase/blob/master/examples/expo-todo-list

It would be great to have something similar for React Native. The code will be mostly the same, but it will be helpful for anyone who is new to RN and doesn't know how to translate the Expo examples to RN.

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

Bug description

On windows, I run prisma format and note the unusual file ending. The lines are all LF, but the very last line is CRLF.

This causes issue on my Linux CI where it formats it ending in LF's only, causing a diff to occur and the build to fail.

How to reproduce

1. On windows do prisma format
2. Open in HxD or similar
3. See attached:

![image](https://user-images.g

Describe the bug

No response

To reproduce

create table pricetable2
(ts timestamp,symbolname SYMBOL CACHE ,price Double,aggregateTradeId Long,firstTradeId Long,lastTradeId Long,buyerMaker Boolean,qty Double) 
partition by day;

Executes without error and crates table without designated timestamp partitioned by DAY

Expected Behavior

Create table query should fail. Pa

Currently, if a plugin implements the onAction function, it will receive every action triggered.

However, a more optimal approach would be to receive only actions that the user specifies they want the plugin to run on, as is the case with webhooks.

Hence, here's the rough solution I'm envisioning:

On the action page, around where the webhook stuff is, add a section allowing the user to

No way to override migrations directory for CLI.

• On every push to main branch, we should build a Docker image with the tag main.
• On every new git tag, we should build a Docker image with tag matching git tag without leading v, and also tag it as latest.

That should be done with GitHub Actions.

ref: frappe/erpnext#28979

These kinda failures can be detected much early if get_attr is done while migrating to verify that specified path is valid.

The problem faced currently?

While adding an ingress route, or a target in ingress route.
If by mistake white space gets added to the route or host. We get the error specified route not found or unable to reach the specified target

How can we solve it?

Mission control should remove the white space if present before saving the config

If you want this feature to be implemented, gi