Skip to content
#

performance

Here are 3,210 public repositories matching this topic...

k6
SaberStrat
SaberStrat commented Jan 16, 2021

If k6 run aborts due to a JS code error/exception in a portion of script code that's imported as a module, the stack trace k6 prints out is not displaying the correct line numbers of the calls leading to the error.
If the code error happens in the main script file -- i.e. the one that contains the default export -- the line number is correct.

Environment

k6 version: k6 v0.29.0 (2020-11

MrCull
MrCull commented Nov 5, 2020

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

nichalko
nichalko commented Jan 31, 2019

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)">
   
guess
BenchmarkDotNet
Open

Tests

leeoniya
leeoniya commented Dec 14, 2019

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

pizzafox
pizzafox commented Nov 1, 2020

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.

Improve this page

Add a description, image, and links to the performance topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the performance topic, visit your repo's landing page and select "manage topics."

Learn more