Improve documentation

Link

https://supabase.com/blog/2022/03/31/supabase-edge-functions

Describe the problem

Links to https://deno.land/manual/tools/testing which results in a 404.

Describe the improvement

I think it should link to https://deno.land/manual/testing instead.

Additional context

Super exciting to see a partnership between Supabase and Demo Deploy

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

Currently keys written to server.conf go undetected.

This means that not only typos go undetected, but lack of validation is a risk during version migration as settings that used to apply in a previous version have no effect in a newer one without warning -- even if new settings are supposed to be used.

To reproduce

• Create a key with a typo.
• Watch the QuestDB

currently I'm unable to implement decode for My Type:

impl Decode<'_, Postgres> for MyType {
    fn decode(value: PgValueRef<'_>) -> Result<Self, BoxDynError> {
        // because this is private
        match value.format() {
            PgValueFormat::Binary => todo!(),
            PgValueFormat::Text => todo!(),
        }
    }
}

Support $mod evaluation query operator for all data types.

For 2 reasons:

1. It doesn't exist on postgres
2. since innodb is the default this key shouldn't appear in doctype schema files 😄

Example: https://github.com/frappe/frappe/blob/19fb8cd409ac32a18c53bcbcf650a5fbc1a87eae/frappe/email/doctype/newsletter_attachment/newsletter_attachment.json#L7

Probable change in this function:

https://github.com/frappe/frappe/blob/abd421fa02fe3a86a65df

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