performance

It would be good to remove this monkey patch:

https://github.com/fastify/fastify/blob/2afc0d757eff238ae5ac0bd91033fe43a83d18d9/lib/server.js#L139-L147

To do this, we need to remove all the fastify.server.unref() calls from the test/ folder and replace it within:

t.teardown(() => { fastify.close() })

The Storybook API has changed quite a lot since Solid's Storybook docs were written in 2019. It would be really helpful (and I think go a loooong way toward helping drive adoption, long-term) if Solid could:

1. Update the docs to reflect the latest Storybo

Feature Description

K6 currently only supports providing cleartext public key and private key for TLS Authentication. This is usually considered insecure in a production system.

  tlsAuth: [
    {
      domains: ['example.com'],
      cert: open('./mycert.pem'),
      key: open('./mycert-key.pem'),
    },
  ],

Please consider adding an additional field, like "passphrase" in

DNS preanalyze is a way to reduce DNS analyze time:

<meta http-equiv="x-dns-prefetch-control" content="on" />
<link rel="dns-prefetch" href="http://www.baidu.com" />

Describe the bug
The markup version of the readme that is displayed in the main page for this repo contains the following links:
Status code [404:NotFound] - Link: https://keyword-2-ecd7b.firebaseapp.com/
Status code [404:NotFound] - Link: https://github.com/GoogleChromeLabs/quicklink/blob/master/#custom-ignore-patterns

(The links in the readme’s markdown may appear different to the link

I tried a lot of ways，but it dosen't show any information in console. I don't know what's wrong.

import { times } from "lodash";
import React from "react";
import ReactDOM from "react-dom";
import whyDidYouRender from "@welldone-software/why-did-you-render";

if (process.env.NODE_ENV === 'development') {
  const whyDidYouRender = require('@welldone-software/why-did-you-rende

Various characters (e.g. |) if used in a Params will end up invalidating the generated markdown, causing it to render incorrectly. It'd be helpful if benchmarkdotnet could escape the markdown output, e.g. output \| instead of |.

• Missing information on how to create other databases
• Missing information on how to switch to other databases
• When using time travel, we don’t know where to get the transaction number from - we should show this to the user after committing data (this may be a missing capability in immudb / tools).
• The last long query example in the quick start is incorrect (incorrect

it's becoming more time-consuming and error-prone to manually re-test all the demos following internal refactorings and API adjustments.

now that the API is fleshed out a bit, it's possible to test a large amount of code (non-granularly) without having to simulate all interactions via Puppeteer or similar.

a lot of code can already be regression-tested by simply running all the demos and val

Expected Behavior

Running validator https://validator.w3.org on basic <picture> elements as per setup config should not result in errors.

Current Behavior

Currently when running validator on:

<picture class="lozad" style="display: block; min-height: 1rem" data-iesrc="images/thumbs/04.jpg" data-alt="">
    <source srcset="images/thumbs/04.jpg" media="(min-width: 1280px)">
   

Is your feature request related to a problem? Please describe.
Many static type checkers have issues finding Cython's stubs.
Here is from running mypy on my current project:

error: Skipping analyzing "cython": found module but no type hints or library stubs

The same issue can be seen when using import Cython as cython:

error: Skipping analyzing "Cython": found module but 

Describe the bug

The "ES2015 exports introduced. Not side-effect free yet, hence limited tree-shake ability." Tooltip in the Size-per-package-Version graph is displayed behind the graphs bars, possibly making the tooltip text unreadable.

To Reproduce

Found on this page: