sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: storybook
Issue: [Bug]: Badge with numbers are different sizes between sidebar and addon tab
Labels: bug,ui,sev:S4

### Describe the bug

In the addon tab: the badge is incorrect. I'd expect it to have similar padding as the "2" badge.

In the sidebar: the badge is correct, but I'd expect the font-size for "Changes" to be 13px instead of 12px.

<img width="382" alt="image" src="https://github.com/storybookjs/storybook/assets/263385/dbcf9ef6-3c58-46fe-8655-f78e498bc5b9">

Heads up @cdedreuille we chatted about this!

### To Reproduce

The addon badge size currently happens in SB7 and SB8.

Go to the static Storybook [here](https://65b92cb13e8a879533e43807-adhtspowzl.chromatic.com/?path=/story/example-button--primary).

Then compare the badge size in the addon with the badge size in the sidebar (correct)

### System

This effects the SB UI layer and is present on every SB.

### Additional context

_No response_
Repository: storybook
Issue: [Bug]: Top toolbar lacking semantics
Labels: bug,help wanted,ui,accessibility,sev:S4

### Describe the bug

The HTML markup for the top toolbar needs semantics. The buttons should be marked up as an unordered list to indicate the number of items clearly, and ideally, this would be grouped into a labeled `<section>`. 
![bug1](https://github.com/storybookjs/storybook/assets/76465110/d79383b3-aa50-440d-b7d0-5b6ccf5f3a83)



### To Reproduce

Inspect top toolbar elements.

### System

_No response_

### Additional context

_No response_
Repository: vscode
Issue: on-enter rule not applying on reload
Labels: bug,editor-autoindent


Type: <b>Bug</b>

1. Create `file.jsx` with the content:

```jsx
const a = <div onclick={bla}>
```

2. Open and reload VS Code
3. Put cursor at end of line and press return

# Expected:

```jsx
const a = <div onclick={bla}>
    |
```

# Actual:
```jsx
const a = <div onclick={bla}>
|
```

If you add a single semicolon to the initial document like so


```js
const a = <div onclick={bla}>;
```

and then delete it, the scenarior starts working 

VS Code version: Code - Insiders 1.87.0-insider (Universal) (ec291c126878742ad640055ce604a58129cd088c, 2024-02-05T05:47:43.946Z)
OS version: Darwin arm64 23.3.0
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Apple M2 Max (12 x 24)|
|GPU Status|2d_canvas: unavailable_software<br>canvas_oop_rasterization: disabled_off<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: disabled_software<br>multiple_raster_threads: enabled_on<br>opengl: disabled_off<br>rasterization: disabled_software<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: disabled_software<br>video_encode: disabled_software<br>webgl: unavailable_software<br>webgl2: unavailable_software<br>webgpu: unavailable_software|
|Load (avg)|5, 5, 5|
|Memory (System)|64.00GB (2.08GB free)|
|Process Argv|--crash-reporter-id 0fffb5da-9cd7-46fd-9e7f-a1564e8c5fda|
|Screen Reader|no|
|VM|0%|
</details>
<!-- generated by issue reporter -->
Repository: angular
Issue: Angular 17 Prerendering (Static Site Generation (SSG)) does not wait until the request is done when using with Firebase
Labels: area: server,state: needs more investigation

### Which @angular/* package(s) are the source of the bug?

platform-server

### Is this a regression?

Yes

### Description

Hi

I'm pre-rendering an angular site with 100+ pages and each page has a simple call to Firebase to get data and then display them on the page. I put all routes in routes.txt

 "prerender": {
   "routesFile": "routes.txt"
 },

It worked well until I realized that some of pre-render pages had empty content. Every time I run the prerender, it has random results, some pages works some pages don't. if I only have 2-5 routes, the pre-render works fine and consistent. My suspicious is that when pre-render, angular just blasts calls to Firebase and doesn't wait until Firebase returns the data, hence the empty pre-render page.

Is there a way to set pre-render to do it synchronously or a way for prerender to wait until each page is finished?

Thank you so much in advance


### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true
no error
```


### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI: 17.1.2
Node: 20.11.0
Package Manager: npm 10.2.4
OS: darwin arm64

Angular: 17.1.2
... animations, cli, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, platform-server
... router, ssr

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1701.2
@angular-devkit/build-angular   17.1.2
@angular-devkit/core            17.1.2
@angular-devkit/schematics      17.1.2
@angular/fire                   17.0.1
@schematics/angular             17.1.2
rxjs                            7.8.1
typescript                      5.2.2
zone.js                         0.14.2
```


### Anything else?

_No response_
Repository: next.js
Issue: Content Security Policy (CSP) nonce's only work when using app router
Labels: bug,Navigation,Runtime

### Link to the code that reproduces this issue

https://github.com/ivanvanderbyl/next-js-broken-nonce-issue

### To Reproduce

Load up the reproduction app and inspect the source of these two pages:

1. `/` — this uses app router and contains nonces on the scrip tags
2. `/anotherpage` — this uses the pages router and does not contain nonces

### Current vs. Expected behavior

According to the [docs on configuring your application for CSP](https://nextjs.org/docs/app/building-your-application/configuring/content-security-policy), adding the middleware should be all that is required, however, it fails to mention that this only works for app router and is not supported by pages router.

**When using pages router:**

**Current behaviour:** nonces are not applied to script tags that import next components.
**Expected:** Next should detect the CSP headers in the request and apply them to the next script tags.

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.2.0: Wed Nov 15 21:53:18 PST 2023; root:xnu-10002.61.3~2/RELEASE_ARM64_T6000
Binaries:
  Node: 21.6.1
  npm: 10.2.4
  Yarn: 1.22.19
  pnpm: 8.15.1
Relevant Packages:
  next: 14.1.1-canary.36 // Latest available version is detected (14.1.1-canary.36).
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Middleware / Edge (API routes, runtime), Routing (next/router, next/navigation, next/link)

### Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local), Vercel (Deployed)

### Additional context

_No response_
Repository: go
Issue: cmd/compile: compiler assumes `[2]T` does not alias with `struct{a, b T}` which might be allowed by the `unsafe` package
Labels: Documentation,NeedsFix

### Go version

go version devel go1.23-6076edc55c Mon Feb 5 20:59:15 2024 +0000 linux/amd64

### Output of `go env` in your module/workspace:

```shell
GO111MODULE=''
GOARCH='amd64'
GOBIN=''
GOCACHE='/home/hugo/.cache/go-build'
GOENV='/home/hugo/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/home/hugo/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/home/hugo/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/home/hugo/k/go'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/home/hugo/k/go/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='devel go1.23-6076edc55c Mon Feb 5 20:59:15 2024 +0000'
GCCGO='/usr/bin/gccgo'
GOAMD64='v3'
AR='ar'
CC='gcc'
CXX='g++'
CGO_ENABLED='1'
GOMOD='/dev/null'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build1276548902=/tmp/go-build -gno-record-gcc-switches'
```


### What did you do?

While investing #65495 I noticed that the compiler makes assumptions about aliasing of structs which are not documented in `unsafe`.

See this piece of code:
```go
package main

import "unsafe"
import "fmt"

type S0 struct{ a, b S1 }
type S1 struct{ a, b S2 }
type S2 struct{ a, b S3 }
type S3 struct{ a, b S4 }
type S4 struct{ a, b S5 }
type S5 struct{ a, b S6 }
type S6 struct{ a, b S7 }
type S7 struct{ a, b S8 }
type S8 struct{ a, b int }

//go:noinline
func Copy(a, b *S0) {
	*a = *b
}

func main() {
	var arr [3]S1
	arr[0].a.a.a.a.a.a.a.a = 42
	arr[1].a.a.a.a.a.a.a.a = 43
	arr[2].a.a.a.a.a.a.a.a = 44
	Copy((*S0)(unsafe.Pointer(&arr[1])), (*S0)(unsafe.Pointer(&arr[0])))
	fmt.Println(arr[2].a.a.a.a.a.a.a.a)
}
```

### What did you see happen?

```
42
```

### What did you expect to see?

```
43
```
Repository: rust
Issue: Investigate getting rid of the `AsyncFn*` family of traits in favor of `LendingFn*`
Labels: C-cleanup,C-enhancement,F-async_closure,T-types

This will allow us to avoid annoying trait duplication if we want to add `gen ||` and `async gen ||` closures.

We need to lower `impl async Fn()` bounds to `LendingFn` bounds using the `associated_type_bounds` feature. This doesn't work currently until:
* #120584 fixes associated type bounds in some positions
* We fix #109924 (well, the general problem of HRTB with projections that have infer vars in them)
* Figure out if we want to add a new associated type to `Fn`/`FnMut`, or just have two new traits, i.e. figure out how to unify the fact that `LendingFnMut` doesn't necessarily have `FnOnce` as a supertrait.
Repository: vscode
Issue: internalConsole does not work for "attach" mode
Labels: bug,debug,debug-console

The debug console does not render control characters (such as "\r") correctly.

![image](https://github.com/microsoft/vscode/assets/10172392/559f7d4e-86af-4158-9db0-aa01dfe4bb76)

To avoid garbled output display, I set {"console": "internalConsole"} in `launch.json`. Unfortunately, that does not work in "remote attach" mode. I hope this can be supported as well. Thanks!
Repository: PowerToys
Issue: mouse without border cannot connect 
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.78.0

### Installation method

GitHub

### Running as admin

No

### Area(s) with issue?

Mouse Without Borders

### Steps to reproduce

just install program on 2 devices and type security key and device name in power toy (not mouse without borders in system tray)
[PowerToysReport_2024-02-06-12-23-01.zip](https://github.com/microsoft/PowerToys/files/14174340/PowerToysReport_2024-02-06-12-23-01.zip)
[MagicMouse.log](https://github.com/microsoft/PowerToys/files/14174342/MagicMouse.log)

second thing is generated by mouse wihtout borders in system tray in device A


### ✔️ Expected Behavior

can control device B in device A

### ❌ Actual Behavior

if i type device B's security code in device A, device B's status borad color is blue (in document, it is handshaking)
and device B was constantly notifying that device A was named and connected

### Other Software

| | device A |
| - | - |
| device | desktop |
| OS | Windows 11 |
| CPU | Intel |

| | device B |
| - | - |
| device | laptop |
| OS | Windows 10 and 11 (i tried both)
| CPU | Intel |
Repository: rust
Issue: `uncommon_codepoints` is only checked post-NFC
Labels: A-lints,A-diagnostics,A-Unicode,T-compiler,C-bug,L-uncommon_codepoints

### Code

```Rust
#![forbid(uncommon_codepoints)]
pub const L·L: u32 = 7;
```


### Current output

(compiles successfully)

### Desired output

```Shell
error: identifier contains an uncommon Unicode codepoint: '·'
 --> src/lib.rs:2:11
  |
2 | pub const L·L: u32 = 7;
  |           ^^^
  |
```


### Rationale and extra context

The `·` in the above code snippet is [U+0387 GREEK ANO TELEIA](https://util.unicode.org/UnicodeJsps/character.jsp?a=0387), which has an `Identifier_Status` of `Restricted` and should therefore trigger the `uncommon_codepoints` lint. However, U+0387 has an NFC decomposition to U+00B7 ( · ) MIDDLE DOT, which has an `Identifier_Status` of `Allowed`, and is therefore not flagged by the lint. Because the compiler applies NFC normalization to identifiers before checking `uncommon_codepoints`, the lint incorrectly fails to fire in this case. 


### Rust Version

```Shell
rustc 1.75.0 (82e1608df 2023-12-21)
binary: rustc
commit-hash: 82e1608dfa6e0b5569232559e3d385fea5a93112
commit-date: 2023-12-21
host: x86_64-unknown-linux-gnu
release: 1.75.0
LLVM version: 17.0.6
```

@rustbot label A-unicode
Repository: PowerToys
Issue: Feature request: Quick enable/disable of trackpad (and possible other items that are usually buried in settings)
Labels: Needs-Triage

### Description of the new feature / enhancement

A switch (via the system tray and an optional keyboard shortcut) to enable/disable the trackpad.
As a bonus, it would also be useful to be able to enable/disable other input devices (eg. Mouse, Keyboard, etc).


### Scenario when this would be used?

On many devices (especially those with large trackpads like the Surface Laptop Studio and Laptop Studio 2) it is very easy to accidentally graze the trackpad while typing, leading to frequent accidental input and errors.

Windows already has a feature to disable trackpad when a mouse is connected, but with wireless (dongle) mice and bluetooth mice, it doesn't make sense to be physically disconnecting and reconnecting the mouse all the time, just to disable the trackpad.

Personally, I like to move fluidly between trackpad and mouse use, depending on the precise task I'm completing at any given moment, and the level of control it needs.

If it doesn't need lots of control or is a quick move (eg. quick scroll or zoom), I'll often use the trackpad. But if I'm doing bigger moves (eg. dragging long distances around a Miro board) it's much better to use the mouse for reliable control.

Thus, the ability to very quickly via a shortcut enable/disable the trackpad would greatly improve workflow.

(The Windows sensitivity settings help a little, but don't solve the problem)


### Supporting information

https://www.reddit.com/r/LenovoLegion/comments/14q7e28/accidental_trackpad_clicks_with_palm_while_typing/
https://www.howtogeek.com/223404/how-to-stop-accidental-trackpad-clicks-in-windows-10-and-other-mouse-enhancements/
https://www.reddit.com/r/Windows10/comments/78tjns/windows_10_disable_touchpad_while_typing_possible/


### Related Issues / Feature Requests

https://github.com/microsoft/PowerToys/issues/24219
https://github.com/microsoft/PowerToys/issues/25644
Repository: node
Issue: `BigIntStats` not actually exported from `fs`.
Labels: fs

### Version

v21.4.0

### Platform

Darwin chug.lan 22.6.0 Darwin Kernel Version 22.6.0: Tue Nov  7 21:42:27 PST 2023; root:xnu-8796.141.3.702.9~2/RELEASE_ARM64_T8103 arm64

### Subsystem

fs

### What steps will reproduce the bug?

Shell command: `node -e 'console.log(fs.BigIntStats)'`


### How often does it reproduce? Is there a required condition?

Always reproduces.

### What is the expected behavior? Why is that the expected behavior?

I would expect this to output the usual representation of a class / constructor named `BigIntStats`, which is a class named in the documentation for the `fs` module, e.g. at <https://nodejs.org/docs/latest/api/fs.html#class-fsstats> under "`bigint` version."

(What I _actually_ want to do is stuff like `if (stats instanceof fs.BigIntStats) ...`.)

### What do you see instead?

```console
$ node -e 'console.log(fs.BigIntStats)'
undefined
$
```

### Additional information

Compare to:

```console
$ node -e 'console.log(fs.Stats)'
[Function: Stats]
$
```
Repository: go
Issue: cmd/compile: exponential behavior for deeply nested structs
Labels: ToolSpeed,NeedsFix,compiler/runtime

### Go version

tip

### Output of `go env` in your module/workspace:

```shell
GO111MODULE=""
GOARCH="arm64"
GOBIN=""
GOCACHE="/Users/khr/Library/Caches/go-build"
GOENV="/Users/khr/Library/Application Support/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="arm64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/khr/gopath/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/khr/gopath"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/Users/khr/go1.20.6"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/Users/khr/go1.20.6/pkg/tool/darwin_arm64"
GOVCS=""
GOVERSION="go1.20.6"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/dev/null"
GOWORK=""
CGO_CFLAGS="-O2 -g"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-O2 -g"
CGO_FFLAGS="-O2 -g"
CGO_LDFLAGS="-O2 -g"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/z9/dty110711l9cr9w3ktv1_2380000gn/T/go-build2801687852=/tmp/go-build -gno-record-gcc-switches -fno-common"
```


### What did you do?

`test.go`:
```
package a

type S0 struct{ a, b S1 }
type S1 struct{ a, b S2 }
type S2 struct{ a, b S3 }
type S3 struct{ a, b S4 }
type S4 struct{ a, b S5 }
type S5 struct{ a, b S6 }
type S6 struct{ a, b S7 }
type S7 struct{ a, b S8 }
type S8 struct{ a, b S9 }
type S9 struct{ a, b S10 }
type S10 struct{ a, b S11 }
type S11 struct{ a, b S12 }
type S12 struct{ a, b S13 }
type S13 struct{ a, b S14 }
type S14 struct{ a, b S15 }
type S15 struct{ a, b S16 }
type S16 struct{ a, b S17 }
type S17 struct{ a, b S18 }
type S18 struct{ a, b S19 }
type S19 struct{ a, b S20 }
type S20 struct{ a, b S21 }
type S21 struct{ a, b S22 }
type S22 struct{ a, b S23 }
type S23 struct{ a, b int }
```
Compile with
```
go tool compile -cpuprofile=foo.prof ~/gowork/test.go
```
It takes a surprisingly long time. The pprof output points to `cmd/compile/internal/types/alg.go:AlgType` as the culprit. It is walking the exponential-sized object to determine its algorithm class. It should probably memoize the computation somehow so it isn't exponential.

Add more lines to the example to make it even more slower.

Found during discussion in #65495.


### What did you see happen?

```
      flat  flat%   sum%        cum   cum%
    2330ms 28.14% 28.14%     7470ms 90.22%  cmd/compile/internal/types.AlgType
    2040ms 24.64% 52.78%     2070ms 25.00%  cmd/compile/internal/types.(*Type).Fields
    1010ms 12.20% 64.98%     3850ms 46.50%  cmd/compile/internal/types.IsPaddedField
     640ms  7.73% 72.71%      790ms  9.54%  cmd/compile/internal/types.PtrDataSize
```


### What did you expect to see?

Fast compilation.
Repository: kubernetes
Issue: kubelet ignores optional CRI runtime conditions (kubelet will not rely on them, but it should somehow make them visible via kubectl)
Labels: sig/node,kind/feature,triage/accepted

### What happened?

The CRI API states that optional runtime conditions will be "exposed to users to help
them understand the status of the system", but the conditions are not visible via `kubectl get nodes -o yaml`. (Still visible via `crictl info`)

https://github.com/kubernetes/cri-api/blob/v0.29.1/pkg/apis/runtime/v1/api.proto#L1496-L1518
```protobuf
// RuntimeCondition contains condition information for the runtime.
// There are 2 kinds of runtime conditions:
// 1. Required conditions: Conditions are required for kubelet to work
// properly. If any required condition is unmet, the node will be not ready.
// The required conditions include:
//   * RuntimeReady: RuntimeReady means the runtime is up and ready to accept
//   basic containers e.g. container only needs host network.
//   * NetworkReady: NetworkReady means the runtime network is up and ready to
//   accept containers which require container network.
// 2. Optional conditions: Conditions are informative to the user, but kubelet
// will not rely on. Since condition type is an arbitrary string, all conditions
// not required are optional. These conditions will be exposed to users to help
// them understand the status of the system.
message RuntimeCondition {
    // Type of runtime condition.
    string type = 1;
    // Status of the condition, one of true/false. Default: false.
    bool status = 2;
    // Brief CamelCase string containing reason for the condition's last transition.
    string reason = 3;
    // Human-readable message indicating details about last transition.
    string message = 4;
}
```


### What did you expect to happen?

The conditions should be visible via `kubectl get nodes -o yaml`

### How can we reproduce it (as minimally and precisely as possible)?

1. Implement an optional runtime condition https://github.com/containerd/containerd/pull/9767
2. Make sure that the added condition is visible via `crictl info`
3. But the condition is not visible via `kubectl get nodes -o yaml`

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
$ kubectl version
Client Version: v1.29.1
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.29.1
```

</details>


### Cloud provider

<details>
None
</details>


### OS version

<details>

```console
Linux
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>
containerd  v2 pre-release (https://github.com/containerd/containerd/pull/9767)
</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>
Repository: deno
Issue: `deno publish` triple slash directions allowed in dry-run.
Labels: bug,publish,jsr

```
divy@mini ~/g/pasteboard (main)> deno publish
Checking fast check type graph for errors...
Ensuring type checks...
Check file:///Users/divy/gh/pasteboard/pasteboard.ts
Visit https://jsr.io/auth?code=XXXX to authorize publishing of @divy/pasteboard
Waiting...
Authorization successful. Authenticated as Divy Srivastava
Publishing @divy/pasteboard@0.0.1 ...
giterror: Failed to publish @divy/pasteboard@0.0.1

Caused by:
    Failed to publish @divy/pasteboard at 0.0.1: Triple slash directives that modify globals (for example, '/// <reference no-default-lib="true" />' or '/// <reference lib="dom" />') are not allowed. Instead instruct the user of your package to specify these directives. file:///objc.ts:15:1
```

`objc.ts` had a triple slash directive:
```ts
/// <reference lib="deno.unstable" />
```

The issue is that dry run passes.