Currently, in provisioning, we always update structs if they already exist. This introduces some load to the database. In the future, we would like to have a function that compares the internal state with the external state.

• Alert rules
• Contact points
• Templates
• Mute timings

Chore

Describe the chore

Update the rest of the monorepo to use common assets.

Tasks

• Find away to get favicons working fully
• Update the rest of the monorepo

When browsing wide data tables in the dashboard (which I do a lot) it is very inconvenient because the browser's horizontal scrollbar is hidden unless you scroll to the very bottom of the page.
If I am at a page like /console/data/schema/public/tables/[tablename]/browse

I won't be able to scroll the table right (to see other columns) unless I first scroll vertically to the bottom of the page

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

In the documentation, it is written that we can get the day of year using the to_str(time, 'D') approach. However, using the latest docker images, this will return the string 'D' as a result. See https://questdb.io/docs/reference/function/date-time/#date-and-timestamp-format

I assume this may be tracked down somewhere around here, where the capital D is never being regist

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 make a task target release-build-bins that would build release binaries into build/bin directory (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.

We should also update our [release checklist](https://github.com/FerretDB/FerretDB/blob/main/.github/RELEASE_CHECKLI

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