What happened:
Following the instructions on this page, I configure my alert with severity and component tags. I then configured PagerDuty side. However, the notification that I got in PagerDuty didn't include the correct field values. Specifically, the component
and severity fields wer

Feature request

Is your feature request related to a problem? Please describe.

I'm using the SMS OTP feature for a progressive web application to be used on mobiles and would like to use the WebOTP API to automatically handle the SMS. The new templating feature gets me almost there – but only almost since it does not allow newlines (\n).

Describe

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

The JSON response sent back over HTTP doesn't encode certain characters correctly.

For example, if a value in a string column contains the char \1 the byte value is copied verbatim in the response, breaking the client:

>>> json.loads('"\1"')
...
json.decoder.JSONDecodeError: Invalid control character at: line 1 column 2 (char 1)

Instead, we shou

The macros can emit code directly referencing serde_json::Value which may trigger compilation errors if the user doesn't have it in their own dependencies: https://discord.com/channels/665528275556106240/665528275556106243/969377568685981716

I'm surprised we haven't encountered this before now, probably because if someone wants to use serde_json::Value in their code deliberately then they p

For #420, we need to:

• ensure that we use only zap for logging with a centralized configuration;
• ensure that we correctly deriver loggers;
• implement a zap hook that keeps up to 1024 entries in memory in a circular buffer;
• initialize that hook for the whole loggers' tree.

Those kept entries will be used by #420.

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