sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: Link Component affects tab order when using anchors affecting accessibility
Labels: Navigation

### Link to the code that reproduces this issue

https://codesandbox.io/p/sandbox/modest-babbage-ywzvtv

### To Reproduce

I've included a version using `<a href="#">` and `<Link href="#">` in my example above

Steps to replicate:

- Tab to the any item in the sidebar and hit enter
- Keep hitting tab again 



### Current vs. Expected behavior

When using plain html links `<a href="#">` the behaviour of the page is expected to be: tab to a link with an anchor and hit enter - tabbing continues from that point on the page 

![with-html-link](https://github.com/user-attachments/assets/305eeabc-412c-4a6d-8794-15fea32a973d)

When using `<Link href="#">` however the behaviour is to continue from where you were tabbing before you hit enter so you lose context, this was flagged in one of our accessibility audits.

![with-nextjs-link](https://github.com/user-attachments/assets/8a27b62f-7a53-48ec-972c-4f458f8c7d19)

[The documentation doesn't mention anything special about anchor link functionality](https://nextjs.org/docs/app/api-reference/components/link#scrolling-to-an-id) 

I've tried additional settings eg using `/path#anchor` instead of `#anchor` I've also tried `href={{ hash: 'anchor' }}`. 

If you go directly to an anchor link url tabbing begins as expected on both versions



### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
  Available memory (MB): 4102
  Available CPU cores: 2
Binaries:
  Node: 20.9.0
  npm: 9.8.1
  Yarn: 1.22.19
  pnpm: 8.10.2
Relevant Packages:
  next: 15.1.1-canary.17 // Latest available version is detected (15.1.1-canary.17).
  eslint-config-next: N/A
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Navigation

### Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local), next start (local), Other (Deployed)

### Additional context

This was flagged up in our accessibility audit - our fix for now is to use `<a href="#">`
Repository: rust
Issue: Tracking Issue for `normalize_lexically`
Labels: T-libs-api,C-tracking-issue

Feature gate: `#![feature(normalize_lexically)]`

This is a tracking issue for `Path::normalize_lexically` that is used to normalize a path, including `..` parent references, without touching the filesystem.

### Public API

```rust
// std::path

impl Path {
    pub fn normalize_lexically(&self) -> Result<PathBuf, NormalizeError> {
}
```

### Steps / History

- [x] [API Change Proposal](https://github.com/rust-lang/libs-team/issues/396)
- [ ] Implementation: #134696
- [ ] Final comment period (FCP)[^1]
- [ ] Stabilization PR

### Unresolved Questions

- Should this take `&mut self` and normalize in-place? Normalizing a path just removes components.
- Should this disallow resolving to the empty path or the single `.` path.
- Should this only allow paths without a root or prefix? It may be surprising that `base_path.join(user_path.normalize_lexically()?)` can still escape the base path.

The last two can be summarised as: should this strictly require paths to be sub-paths?

[^1]: https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html
Repository: rust
Issue: Tracking issue for release notes of #83163: Tracking Issue for const_swap
Labels: T-libs-api,relnotes,relnotes-tracking-issue


This issue tracks the release notes text for #83163.

### Steps

- [ ] Proposed text is drafted by PR author (or team) making the noteworthy change.
- [ ] Issue is nominated for release team review of clarity for wider audience.
- [ ] Release team includes text in release notes/blog posts.

### Release notes text

The responsible team for the underlying change should edit this section to replace the automatically generated link with a succinct description of what changed, drawing upon text proposed by the author (either in discussion or through direct editing).

````markdown
# Const stabilized APIs
- [`std::mem::swap`](https://doc.rust-lang.org/stable/std/mem/fn.swap.html)
- [`std::ptr::swap`](https://doc.rust-lang.org/stable/std/ptr/fn.swap.html)
````

> [!TIP]
> Use the [previous releases](https://doc.rust-lang.org/nightly/releases.html) categories to help choose which one(s) to use.
> The category will be de-duplicated with all the other ones by the release team.
>
> *More than one section can be included if needed.*

### Release blog section

If the change is notable enough for inclusion in the blog post, the responsible team should add content to this section.
*Otherwise leave it empty.*

````markdown
````

cc @usbalbin -- origin issue/PR authors and assignees for starting to draft text
Repository: kubernetes
Issue: File name too long
Labels: kind/support,needs-sig,needs-triage

### What happened?

Hi guys,

I need your help with something really weird. I have JupyterHub in an Openshift production environment and one of my users created a notebook with a really long name. Everything was fine, until the next day when he failed to initialize his pod due to this error:

![Captura desde 2024-12-23 11-25-39](https://github.com/user-attachments/assets/02409309-c805-468b-9d25-b9c589f75719)

So if you can help me with this, I would really appreciate it.

### What did you expect to happen?

Start as usual

### How can we reproduce it (as minimally and precisely as possible)?

Create a file with a very long name

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
$ kubectl version
v4.5.7
```

</details>


### Cloud provider

ARO ~ Azure Rethad Openshift


### OS version

```console
# On Linux:
$ cat /etc/os-release
# "Ubuntu 22.04.1 LTS"
$ uname -a
# Linux UBUNTU-MNGR 6.8.0-1018-azure #21~22.04.1-Ubuntu SMP Fri Nov  8 00:21:25 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

I'm using:

JupyterHub: 4.0.2
Image: datascience-notebook:python-3.11.7
Openshift: 4.15.27
Kubernetes: v1.28.11+add48d0
Helm chart: https://hub.jupyter.org/helm-chart version 3.2.1
```
Repository: next.js
Issue: Error importing pure TS packages (with Bun, Turbo, or neither)
Labels: Webpack,TypeScript,Runtime,Turbopack,Module Resolution

### Link to the code that reproduces this issue

https://github.com/ctjlewis/ts-package-example

### To Reproduce

Repro here:

https://github.com/ctjlewis/nextjs-ts-package

It attempts to load this simple mock package:

https://github.com/ctjlewis/ts-package-example

---

Without Bun, Turbo throws:

```
 ⨯ ./node_modules/ts-package-example/index.ts
Module parse failed: Unexpected token (1:7)
> export type GoodNextjsSupport = false;
| export type PossibleSupport = boolean;
| 

Import trace for requested module:
./node_modules/ts-package-example/index.ts
./app/page.tsx
```

When Bun is used *with* Turbo (`bun --bun next dev --turbo`), we get a segfault from Bun:

```
Bun v1.1.41 ([`b8f28ed`](<https://github.com/oven-sh/bun/tree/b8f28ed8afd1c2b60568b2b0158d39a674178027>)) on macos aarch64 [AutoCommand]

Segmentation fault at address 0x4000000002B

- *10 unknown/js code*

<!-- from bun.report: etViGWlalFX_NMfe5SXL -->

<sub>Sentry Issue: <strong><a href="https://bun-p9.sentry.io/issues/5298323857/">BUN-85</a></strong></sub>
```

### Current vs. Expected behavior

It's important that the module resolve and load correctly. It is effectively the simplest possible pure-TS program.

 Is it maybe the `module` export? I will try with `exports` keyword after this, but either way `module` entrypoint is simplest config. 

I doubt it is, since it seems to throw on the `type` keyword - is it actually expecting JS from all `node_modules`?

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.1.0: Thu Oct 10 21:05:14 PDT 2024; root:xnu-11215.41.3~2/RELEASE_ARM64_T8103
  Available memory (MB): 16384
  Available CPU cores: 8
Binaries:
  Node: 21.0.0
  npm: 10.2.0
  Yarn: 1.22.19
  pnpm: 9.7.1
Relevant Packages:
  next: 15.1.1-canary.17 // Latest available version is detected (15.1.1-canary.17).
  eslint-config-next: 15.1.2
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.2
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Module Resolution, Runtime, Turbopack, TypeScript, Webpack

### Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local), next start (local), Vercel (Deployed), Other (Deployed)

### Additional context

cc @/Jarred-Sumner for Bun crash, cc @/jaredpalmer for Turbopack, cc @/leerob for coordination.

(Config issue: Tags removed.)
Repository: godot
Issue: RichTextLabel (RTL): add_text(), append_text(), add_image() (and probably others) do not work on orphan RTL
Labels: bug,needs testing,topic:gui

### Tested versions

Reproducible in: v4.4.dev7.official [46c8f8c5c], v4.3.stable.official [77dcf97d8]

### System information

Godot v4.4.dev7 - Windows 11 (build 22631) - Multi-window, 1 monitor - Vulkan (Forward+) - dedicated NVIDIA GeForce MX450 (NVIDIA; 32.0.15.5613) - 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz (8 threads)

### Issue description

add_text(), append_text(), add_image() and probably other similar functions do not work on orphan RichTextLabel. Setting the text property directly works.

In the Minimal reproduction project, I only used append_text(), but in my current project in v4.3.stable.official add_image() doesn't work either.

I think it's a bug because I didn't find anything that explains why it behaves like that.
It's pretty simple to bypass putting add_child() before add_*(). Deferring the add_* functions works too. However, I think it's not the expected behavior.

<img width="682" alt="Image" src="https://github.com/user-attachments/assets/c626a384-0b45-4619-839b-14d329a00e01" />


### Steps to reproduce

- Create a RichTextLabel by code (instantiating a scene or creating a new RTL with enough size)
- Add some text using add_text() or append_text()
- Add the RTL to the tree with add_child()

Can be done on a brand new project. I added a Minimal reproduction project anyway.

### Minimal reproduction project (MRP)

[orphan_RTL_test.zip](https://github.com/user-attachments/files/18232032/orphan_RTL_test.zip)
Repository: flutter
Issue: [web] --optimization-level 4 breaks web apps on Safari
Labels: in triage

When building my Flutter web application with `--optimization-level=4` (the default), Safari only displays a gray box, whereas Chrome and Firefox show the application correctly. Using `--optimization-level=2` resolves the issue for Safari, suggesting that the optimization level might be causing the bug.

### Steps to Reproduce
1. Visit Non-Working Build (https://bug-report-non-workung.pages.dev/)
   - Compiled with: `flutter build web --release --no-web-resources-cdn --optimization-level=4`(default)
   - Chrome/Firefox: The app runs successfully.
   - Safari: The app shows only a gray box (error).
2. Visit Working Build (https://bug-report-working.pages.dev/)
   - Compiled with: `flutter build web --release --no-web-resources-cdn --optimization-level=2`
   - Chrome/Firefox: The app runs successfully.
   - Safari: The app also runs successfully.

> Note: I was unable to isolate a minimal reproducible example, but I’m happy to attempt it if given further guidance.

### Expected results

Using `--optimization-level=4` (the default) should produce a web build that works on Safari, just like it does in Chrome and Firefox.



### Actual results

With `--optimization-level=4`, the web app fails to render on Safari (displays a gray box), even though it works correctly on Chrome and Firefox.


### Screenshots or Video

<details open>
<summary>Screenshots / Video demonstration</summary>

<img width="1310" alt="Screenshot 2024-12-23 at 19 23 25" src="https://github.com/user-attachments/assets/6a6cfdb9-3486-445f-9058-b1db334215a8" />
<img width="760" alt="Screenshot 2024-12-23 at 19 23 05" src="https://github.com/user-attachments/assets/0eccc17b-f747-4ecd-b085-1b53cc0435c6" />


</details>


### Logs

<details open><summary>Logs</summary>

```console
[Paste your logs here]
```

</details>


### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.27.1, on macOS 14.6.1 23G93 darwin-arm64, locale en-DE)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 16.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2023.3)
[✓] Android Studio (version 2021.3)
[✓] Android Studio (version 2022.2)
[✓] IntelliJ IDEA Community Edition (version 2024.2.3)
[✓] VS Code (version 1.95.3)
[✓] Connected device (4 available)
[✓] Network resources

• No issues found!
```

</details>
Repository: PowerToys
Issue: For the color picker, display the names of at least the X11 color names
Labels: Needs-Triage

### Description of the new feature / enhancement

Red

### Scenario when this would be used?

Crimson
Brown
Coral
...

### Supporting information

https://en.wikipedia.org/wiki/X11_color_names
Repository: godot
Issue: Weird (choppy?) rendering of linear movement
Labels: needs testing,topic:3d

### Tested versions

- Ocurred in v4.4.dev7.official [46c8f8c5c]

### System information

Godot v4.4.dev7 - Linux Mint 22 (Wilma) on X11 - X11 display driver, Multi-window, 1 monitor - Vulkan (Forward+) - integrated Intel(R) Graphics (ADL GT2) - 12th Gen Intel(R) Core(TM) i7-12700H (20 threads)

### Issue description

On the sample scene (see MRP) there are a few meshes that moves to the left with constant speed and a static (immovable) camera that observes given meshes.

The movement itself is dead simple:
```gdscript
func _process(delta: float) -> void:  
    for child in get_children():  
        child.position.x -= move_speed * delta
```

The problem is -- movement appears to be choppy / ragged despite stable frame framerate. This problem can be observed at any VSync mode. This problem persists between different monitors, different refresh rates and different PCs. Also a friend of mine observed same project launching MRP on Win10 using the same build (4.4 dev7 official).

But after I went back from work and launched MRP again I found it somehow fixed itself or idk.

### Steps to reproduce

Just launch MRP and see trees / checkerboard moves in uncanny way. Or not.

Recording 1: MRP w/ ragged movement (compressed by reddit):

https://github.com/user-attachments/assets/d561302b-5187-4c9c-895f-5c506c172405

On this recording monitor supports refresh rate of 75Hz hence the 75 FPS. Without VSync it would be about 500 FPS so I think low/unstable frame rate is not the problem here.

Recoring 2: MRP I recorded just now:
- top-left: MRP running so smooth; 
- bottom-right: MRP running choppy (this is the only recording I had on this PC so it is a bit different from actual MRP but shows exactly this problem);
- on this recording monitor supports refresh rate of 60Hz hence the 60 FPS.
- video: https://youtu.be/ddn8dyUDDMA

### Minimal reproduction project (MRP)

[2024_12_train.zip](https://github.com/user-attachments/files/18232384/2024_12_train.zip)
Repository: go
Issue: go/types: missing error on an edge-case with continue/break with labels
Labels: NeedsFix

Once again, because i am poking around with `go/types` internals, i have spotted a bug in the type-checker.

The code below type-checks without any error:

```go
package test

func test() {
outer:
	for range "aa" {
		break outer
	}

	for range "aa" {
		break outer
	}
}
```

This happens because `lstmt`:

https://github.com/golang/go/blob/b9955f0ad952a22388eead15e3d15610a29e03a0/src/go/types/labels.go#L169

is assigned and never cleared, thus:

https://github.com/golang/go/blob/b9955f0ad952a22388eead15e3d15610a29e03a0/src/go/types/labels.go#L234-L236

is executed with a wrong label (for the second for statement).

CC @adonovan @griesemer
Repository: rust
Issue: Is StdoutLock guranteed to be reentrant?
Labels: T-libs-api,A-docs

### Location

https://doc.rust-lang.org/std/io/struct.Stdout.html#method.lock
https://doc.rust-lang.org/std/io/struct.Stderr.html#method.lock
https://doc.rust-lang.org/std/io/struct.Stdin.html#method.lock

### Summary

Currently code like this is fine and a convenient way to lock stdout to prevent other threads from interrupting while printing is happening (this is especially useful when the printing happens deep inside some library/component, where `StdoutLock` can't be easily passed as an argument):
```rust
let stdout = io::stdout().lock();
println!("a");
println!("b");
println!("c");
drop(stdout);
```
As far as I understand, this works because `Stdout::lock()` is reentrant. However, the documentation does not mention that `Stdout::lock()` is reentrant.

Is `Stdout::lock()` guaranteed to be reentrant in all future Rust versions, or is this an implementation detail that should not be relied on?
Either way it would be nice if the documentation of `Stdout::lock()` made it clear what the expected behavior is and how much of it is an implementation detail.

The same question also applies to `Stderr::lock()` and `Stdin::lock()`.
Repository: go
Issue: x/tools/gopls: report if accepting a completion item will result in auto-import
Labels: FeatureRequest,gopls,Tools

### gopls version

0.17.1

### go env

```shell
..
```


### What did you do?

"os" is not yet imported:
<img width="888" alt="image" src="https://github.com/user-attachments/assets/447f0444-ccd4-48ef-b999-2eaa53dd7a70" />

however, strings are already imported:
<img width="917" alt="image" src="https://github.com/user-attachments/assets/8b1a86f9-7311-4470-b525-8740a6a06415" />


### What did you see happen?

They looks the same.

### What did you expect to see?

Show a hint whether a package is going to be auto-imported, because some package names look similar, I want to use an already imported one, but find myself often accept a wrong name, therefor need to undo auto import.

In clangd, there is a little circle indicating this:
<img width="915" alt="image" src="https://github.com/user-attachments/assets/985723dd-3e34-4646-ac44-6658c9f72b2a" />

after accpeting `printf`, the circle disappears, because `stdio.h` is auto imported
<img width="874" alt="image" src="https://github.com/user-attachments/assets/8e0ce01c-fa24-45ac-94c4-a72cd4b2a3be" />


### Editor and settings

_No response_

### Logs

_No response_
Repository: PowerToys
Issue: Workspaces launches Tor Browser instead of Firefox if both are installed.
Labels: Issue-Bug,Needs-Triage,Needs-Team-Response,Product-Workspaces

### Microsoft PowerToys version

0.87.1

### Installation method

GitHub

### Running as admin

Yes

### Area(s) with issue?

Workspaces

### Steps to reproduce

Workspaces even version 87.1 cannot tell the difference between the Tor Browser and Firefox if both are installed.  It used to be able to do so before somewhere version 84.

It thinks that if both are installed, when it tries to launch Firefox, it launches Tor instead.  Latest version of both browsers are installed.


### ✔️ Expected Behavior

When you pick Firefox, it should launch Firefox and not the Tor browser.

### ❌ Actual Behavior

It launches the Tor browser instead of the Firefox browser.

### Other Software

_No response_
Repository: flutter
Issue: Re-enable network access for AVDs
Labels: platform-android,P1,team-android,triaged-android

The `video_player` driver test `asset videos live stream duration != 0` is failing (see failure: https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_android%20android_platform_tests_shard_6%20master/1962/overview) because https://flutter-review.googlesource.com/c/recipes/+/61440 removed the flag that enables network access. In the long run, this should be re-enabled on a per-test basis (see https://github.com/flutter/flutter/issues/160691), but https://flutter-review.googlesource.com/c/recipes/+/61660 should be landed for now to un-skip the `asset videos live stream duration != 0` test.
Repository: flutter
Issue: [ios]Make engine scenario tests depend on actual frameworks
Labels: a: tests,platform-ios,P2,team-ios,triaged-ios

### Use case

The engine scenario tests rely on fake commands sending to the engine, as we couldn't use framework, which was in a separate repo. This setup doesn't give us enough confidence since it's not testing the whole pipeline. Furthermore, it gives us "false confidence", which IMO is even worse than "no confidence" at all. 



### Proposal

Since the 2 repos are merged, we should have no problem using actual framework in those scenario tests.
Repository: flutter
Issue: `flutter build apk --config-only` prints `Config complete` right before the command exits, which doesn't match other commands
Labels: tool,P3,team-android,triaged-android

```
$ flutter build apk --config-only
Downloading android-arm-profile/darwin-x64 tools...                287ms
Downloading android-arm-release/darwin-x64 tools...                134ms
Downloading android-arm64-profile/darwin-x64 tools...              142ms
Downloading android-arm64-release/darwin-x64 tools...              132ms
Downloading android-x64-profile/darwin-x64 tools...                125ms
Downloading android-x64-release/darwin-x64 tools...                123ms

Config complete.
```
The "Config complete." part is a but odd, since the tool doesn't announce other commands are "complete", including `flutter build ios --config-only` or `flutter build macos --config-only`

This is a really tiny nit, and this command isn't used by most flutter devs.

Suggest removing this log line:
https://github.com/flutter/flutter/blob/5c7d9d01bae7b279b7d95a37577f782c51847d5b/packages/flutter_tools/lib/src/android/gradle.dart#L455
Will have to detect another way that the `config-only` logic stopped there:
https://github.com/flutter/flutter/blob/5c7d9d01bae7b279b7d95a37577f782c51847d5b/packages/flutter_tools/test/integration.shard/flutter_build_config_only_test.dart#L54
Repository: neovim
Issue: defaults: `q` should close floating windows
Labels: enhancement,defaults,needs:discussion

### Problem

Within the plugin ecosystem, `q` (in normal mode) is a common mapping to close floating windows. It's also used within core, to close the LSP Hover window.

Usually, floating windows aren't modifiable, so having `q` mapped to recording a macro isn't all that useful.

### Expected behavior

`q` should be mapped to `:quit` for floats.
Repository: ui
Issue: [bug]: Add button component with yarn fails
Labels: bug

### Describe the bug

npx shadcn@latest add button

✔ Checking registry.
✔ Installing dependencies.
⠋ Updating files.

Something went wrong. Please check the error below for more details.
If the problem persists, please open an issue on GitHub.

The component at https://ui.shadcn.com/r/colors/brand-primary.json was not found.
It may not exist at the registry. Please make sure it is a valid component.

### Affected component/components

Button

### How to reproduce

npx shadcn@latest add button

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
MacOS: 14.7.1 
Chrome: 130.0.6723.117
Node: 20.10.0
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues