Convert Enzyme test to RTL in Azure Monitor InsightsConfig

Requirement for Grafana to move to React 18 (see grafana/grafana#48253)

Chore

Describe the chore

https://supabase.com/company

This page says that we have raised $36M:

We need to :

• Update the number to $116 M
• Add Felicis to the logos

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

Scenario

A user is ingesting some data (~300M rows) into a table with 270K distinct symbol values. For each of these 270K symbols we end up with at least one posix_fallocate() necessary to add a new value block. See the below flamegraph - it's quite illustrative.

![Screenshot from 2022-05-27 13-03-10](https://user-images.githubusercontent.com/37772591/170937576-b6abdd41-c585-42df-9aa8-

Hi, I'm sure this is probably some configuration error on my end, but am not sure what to do.

I have my project compiling perfectly on my local machine with the compile-time query checks, but when I deploy it to my server I start getting these errors:

error: error occurred while decoding column 0: mismatched types; Rust type `sqlx_core::types::json::Json<[sqlx_core::postgres::connection

{
  "Checksum": 0,
  "FlagBits": 0,
  "Sections": [
    {
      "Document": {
        "$k": [
          "listDatabases",
          "nameOnly",
          "$db"
        ],
        "listDatabases": 1,
        "nameOnly": null,
        "$db": "admin"
      },
      "Kind": 0
    }
  ]
}

nameOnly is documented to be a boolean, but at least [one real application](htt

These files when added magically but not part of git tracked files causes update failure.

reference: frappe/bench#1225

related: frappe/frappe#16616 (you'll find which function create this file in this PR)

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