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" />
WebSocket connections don't use https://k6.io/docs/using-k6/options/#user-agent
I expected my WebSocket URLs to use userAgent setting.
User agent is set to "Go-http-client/1.1"
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
Running validator https://validator.w3.org on basic <picture> elements as per setup config should not result in errors.
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)">
There's a lot of place for improvement of the documentation.
ngx-build-plusThe content of the documentation is in the GitHub page [repo](https://github.com/guess-js/guess-
The original issue was reported in dotnet/performance#1701:
// Benchmark Process Environment Information:
// Runtime=.NET 6.0.0 (6.0.21.11801), X64 RyuJIT
// GC=Concurrent Workstation
// Job: Job-AQTFSE(PowerPlanMode=00000000-0000-0000-0000-000000000000, IterationTime=250.0000 ms, MaxIterationCount=20, MinIterationCount=15, WarmupCount=1)
OverheadJitting
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
I currently have a very big hook, with dozens of useStates, lots of them have empty arrays which trigger unncesary re-renders. But I don't know which is the one doing it each time wdyr logs it's output. I get:
Re-rendered because of hook changes:
[hook useState result]
...diff
When would be very useful for me is:
Re-rendered because of hook changes:
[hook useState result]
The current documentation stems mostly from a time when Pure Python Mode wasn't even being thought of and aims to present the special cdef syntax that Cython uses. The Pure Python Syntax is only presented on the pure Python tutorial page.
Today, more and more new users come from a Python background that uses type annotations. We shoul
Describe the bug
When using an image URL like https://bundlephobia.com/api/stats-image?name=convert&version=1.0.1&wide=true for a version that isn't published the image returns a placeholder, but the placeholder gets cached. After the version is published the placeholder image stays cached.
To Reproduce
Visit an image URL for a version that didn't exist at image generation time.
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:
Add a description, image, and links to the performance topic page so that developers can more easily learn about it.
To associate your repository with the performance topic, visit your repo's landing page and select "manage topics."
Prerequisites
Fastify version
3.13
Plugin version
No response
Node.js version
14.16
Operating system
Linux
Operating system version (i.e. 20.04, 11.3, 10)
20.04
Description
if a route definition passe