Currently, we have the custom templating function for grafana alerting right in the code https://github.com/grafana/grafana/blob/8053f770c1ff83827748b53edafb0a8257fb4a45/pkg/services/ngalert/state/template.go#L60-L68

To do better validation etc. we need to centralize those functions so that we can reuse them were ever we need them.

Chore

Describe the chore

We have some "Notes" callouts in our docs (see here) which look good in light mode:

But not great in dark mode because the left edge is the sam

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

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

We should provide .rpm and .deb packages. Let's build them with https://nfpm.goreleaser.com.

We should make a task target release-build-packages that would build packages into build/rpm and build/deb directories (that should be in .gitignore). That target should be stable, so the external package maintainers can rely on it. That target should be mentioned in the documentation.

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