Skip to content
#

performance

Here are 4,053 public repositories matching this topic...

fastify
katreniak
katreniak commented Jul 1, 2022

Prerequisites

  • I have written a descriptive issue title
  • I have searched existing issues to ensure the bug has not already been reported

Fastify version

4.1.0

Plugin version

No response

Node.js version

v16.15.1

Operating system

Linux

Operating system version (i.e. 20.04, 11.3, 10)

Fedora release 34 (Thirty Four)

Description

When fastify server

bug good first issue
k6
olegbespalov
olegbespalov commented Jun 15, 2022

What?

Currently, if you're trying to use the k6/execution JS API and try to access some of the properties it's possible to get an error.

// script.js
import { scenario } from 'k6/execution';

console.log(scenario.name);

export default () => { }
 k6 run script

          /\      |‾‾| /‾‾/   /‾‾/
     /\  /  \     |  |/  /   /  /
    /  \/    \    |     (   / 
enhancement good first issue evaluation needed
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

bug good first issue docs
BenchmarkDotNet
systeminformer
immudb
zaza81
zaza81 commented Oct 19, 2021
  • 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
documentation good first issue
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

good first issue
Bluenix2
Bluenix2 commented Aug 7, 2021

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 

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