sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: node
Issue: Confusing error message when using `import` inside CJS file
Labels: esm

### Version

23.6.0

### Platform

```text
n/a
```

### Subsystem

esm

### What steps will reproduce the bug?

- Create a `file.cjs` file containing `import "path";`
- Run `node file.cjs`


### How often does it reproduce? Is there a required condition?

/

### What is the expected behavior? Why is that the expected behavior?

It should tell me that to use `import` inside file I need to use `.mjs` and not `.cjs`

### What do you see instead?

```
Warning: To load an ES module, set "type": "module" in the package.json or use the .mjs extension.
```

It also offers the solution of setting "type": "module" in the package.json, but that is wrong since my file is .cjs.

### Additional information

_No response_
Repository: langchain
Issue: DOC: <Issue related to /v0.2/docs/tutorials/rag/>
Labels: 🤖:docs

### URL

https://python.langchain.com/v0.2/docs/tutorials/rag/

### Checklist

- [X] I added a very descriptive title to this issue.
- [X] I included a link to the documentation page I am referring to (if applicable).

### Issue with current documentation:

https://python.langchain.com/v0.2/docs/tutorials/rag/
The installation guide seems to have a typo for conda

The packages are called in conda langchain-community, langchain-chroma, that is with an "-" and not with "_".  With "-", I cpould install them. (As of 2025 January 8th)

![image](https://github.com/user-attachments/assets/17acc88d-789f-48b8-9923-bc4e109093bc)


### Idea or request for content:

_No response_
Repository: react
Issue: [React 19] Error when use create-react-app
Labels: React 19

## Summary

When you try to run the command 'npx create-react-app .' and proceed to install the dependencies with npm it returns an error code ERESOLVE Unable to resolve dependency tree as it generates the package.json with React version 19 but @testing-library/react@13.4.0 is compatible exclusively with React 18.

## Screenshots
![image](https://github.com/user-attachments/assets/84032909-4490-4df7-8c94-3714ff8bc042)
Repository: rust
Issue: Generic trait bound hides concrete type associated type
Labels: A-trait-system,C-bug,T-types,needs-triage

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

I tried this code:

```rust
trait Tr<'x> {
    type Out;
    fn build() -> Self::Out;
}

struct Foo;

impl<'x> Tr<'x> for Foo {
    type Out = i32;
    fn build() -> Self::Out {
        42
    }
}

fn test<'x>() -> i32
where
    Foo: Tr<'x>, // commenting out this line fixes the error
{
    Foo::build()
}
```

I expect this to compile, but it gives the following error:

```
error[E0308]: mismatched types
  --> src/lib.rs:19:5
   |
15 | fn test<'x>() -> i32
   |                  --- expected `i32` because of return type
...
19 |     Foo::build()
   |     ^^^^^^^^^^^^ expected `i32`, found associated type
   |
   = note:         expected type `i32`
           found associated type `<Foo as Tr<'_>>::Out`
   = help: consider constraining the associated type `<Foo as Tr<'_>>::Out` to `i32`
   = note: for more information, visit https://doc.rust-lang.org/book/ch19-03-advanced-traits.html
```
The code also works if the trait is made non-generic.

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.86.0-nightly (ad211ced8 2025-01-07)
binary: rustc
commit-hash: ad211ced81509462cdfe4c29ed10f97279a0acae
commit-date: 2025-01-07
host: x86_64-unknown-linux-gnu
release: 1.86.0-nightly
LLVM version: 19.1.6
```
same result on stable
Repository: langchain
Issue: DOC: <Issue related to  --upgrade  flag in the lang chain documentation / >
Labels: 🤖:docs

### URL

https://python.langchain.com/docs/integrations/memory/google_firestore/

### Checklist

- [X] I added a very descriptive title to this issue.
- [X] I included a link to the documentation page I am referring to (if applicable).

### Issue with current documentation:

URL : https://python.langchain.com/docs/integrations/memory/google_firestore/

The installation guide seems to have a small typo mistake : 

The installation guide for this particular package 'langchain-google-firestore' should have --upgrade but in documentation it is only upto -upgrade

![Screenshot from 2025-01-08 20-21-31](https://github.com/user-attachments/assets/4a2d5c30-8fb2-4e77-baa2-b4ea855fa81d)


The error that a developer gets whenever he/she follows the documented installation guide : 

![Screenshot from 2025-01-08 20-23-33](https://github.com/user-attachments/assets/c3c50dab-5133-417d-9d92-bf7e0fc6f212)


### Idea or request for content:

_No response_
Repository: vscode
Issue: Accessibility: Screen readers cut off lines in latest insider build
Labels: bug,accessibility


Type: <b>Bug</b>

In this latest insiders build, screen readers (tested with both JAWS and NVDA) started cutting off lines of code. the amount read is a bit longer than what is visible on screen, but still it's nearly impossible to work because before the whole line was read no matter what.
Please fix or revert this.

VS Code version: Code - Insiders 1.97.0-insider (9b0b13d9bfe21c3dfd227bfaa8ed5693e309a2e0, 2025-01-08T05:06:32.681Z)
OS version: Windows_NT x64 10.0.26100
Modes:

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

|Item|Value|
|---|---|
|CPUs|12th Gen Intel(R) Core(TM) i7-1270P (16 x 2496)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|15.24GB (6.47GB free)|
|Process Argv|--disable-extensions . --crash-reporter-id 798ba14e-190a-4e22-8cdc-4ff2f816f42d|
|Screen Reader|yes|
|VM|0%|
</details>Extensions disabled<details>
<summary>A/B Experiments</summary>

```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
vsaa593cf:30376535
py29gd2263:31024238
vscaat:30438846
c4g48928:30535728
a9j8j154:30646983
962ge761:30841072
pythonnoceb:30776497
dsvsc014:30777825
dsvsc015:30821418
pythonmypyd1:30859725
2e7ec940:31000449
pythontbext0:30879054
cppperfnew:30980852
pythonait:30973460
dvdeprecation:31040973
dwnewjupyter:31046869
newcmakeconfigv2:31071590
nativerepl1:31134653
pythonrstrctxt:31093868
nativeloc1:31118317
cf971741:31144450
parsetypescript:31116713
e80f6927:31120813
iacca1:31150324
notype1:31143044
dwcopilot:31158714
h409b430:31177054
2j25a237:31183119
c3hdf307:31184662
6074i472:31201624

```

</details>

<!-- generated by issue reporter -->
Repository: vscode
Issue: "outline.icons" stops working for jupyter notebook
Labels: bug,notebook-toc-outline


Type: <b>Bug</b>

Setting "outline.icons=false" no longer hides icons (e.g. "M↓" for md cell) in outline of .ipynb files. It still works in json and markdown.
![Image](https://github.com/user-attachments/assets/d56d6bd6-2aab-4533-b20f-f2c5ecbe1d16)


VS Code version: Code 1.96.2 (Universal) (fabdb6a30b49f79a7aba0f2ad9df9b399473380f, 2024-12-19T10:22:47.216Z)
OS version: Darwin arm64 24.2.0
Modes:

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

|Item|Value|
|---|---|
|CPUs|Apple M3 Pro (12 x 2400)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|8, 8, 8|
|Memory (System)|36.00GB (4.44GB free)|
|Process Argv|--disable-extensions --crash-reporter-id 74c3d86a-e745-43aa-b70f-ed871a8590b7|
|Screen Reader|no|
|VM|0%|
</details>Extensions disabled<details>
<summary>A/B Experiments</summary>

```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
14424-chatv3:31212864
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
pythonnoceb:30805159
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
dvdeprecation:31068756
dwnewjupytercf:31046870
nativerepl2:31139839
pythonrstrctxt:31112756
nativeloc1:31192215
cf971741:31144450
iacca1:31171482
notype1:31157159
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530
6074i472:31201624

```

</details>

<!-- generated by issue reporter -->
Repository: rust
Issue: rust-lld: error: undefined symbol: __gxx_personality_v0
Labels: A-linkage,T-compiler,C-bug,requires-nightly,regression-untriaged,S-has-mcve,A-linkers

We encountered a bug, where the experimental rust-lld currently activated under nightly linux / x86-64, can't links certain executables in release mode with the "intel_tex_2" crate. Switching to the old linker solves the problem.

I created a small repository which includes a minimal example.

https://github.com/hasenbanck/rust_lld_bug

It will crash when compiled via:

```rust
cargo run --release
```

Normaly it should compile fine, but we instead get the following error:

```rust
error: linking with `cc` failed: exit status: 1
  |
  = note: LC_ALL="C" PATH=".....*A LOT OF PATHS*...."
  = note: some arguments are omitted. use `--verbose` to show all linker arguments
  = note: rust-lld: error: undefined symbol: __gxx_personality_v0
          >>> referenced by ispc_texcomp_astc.cpp
          >>>               ispc_texcomp_astc.o:(DW.ref.__gxx_personality_v0) in archive /mnt/c/Development/rust_lld_bug/target/release/deps/libintel_tex_2-2caaaa92d5e41391.rlib
          collect2: error: ld returned 1 exit status

error: could not compile `rust_lld_bug` (bin "rust_lld_bug") due to 1 previous error
```

We used the nightly toolchain 2025-01-07, but older nightly versions are also affected.
We reproduces this error under WSL Ubuntu 24.04 and Fedora 41 running on bare metal.

The old linker works fine:

```rust
RUSTFLAGS="-Z linker-features=-lld" cargo run --release
```
Repository: go
Issue: x/tools/gopls: "negative WaitGroup counter" panic in diagnoseChangedViews
Labels: NeedsInvestigation,gopls,Tools,compiler/runtime,gopls/telemetry-wins,BugReport

```
#!stacks
"runtime.gopanic" && "sync.(*WaitGroup).Add:+19" && "diagnoseChangedViews.func1:+16`"
```
Issue created by [stacks](https://pkg.go.dev/golang.org/x/tools/gopls/internal/telemetry/cmd/stacks).
```go
func (wg *WaitGroup) Add(delta int) {
...
	state := wg.state.Add(uint64(delta) << 32)
	v := int32(state >> 32)
	w := uint32(state)
...
	if v < 0 {
		panic("sync: negative WaitGroup counter") // <---------- here
	}
```
This stack `OKWeGA` was [reported by telemetry](https://storage.googleapis.com/prod-telemetry-merged/2025-01-03.json):

- `crash/crash`
- [`runtime.gopanic:+69`](https://cs.opensource.google/go/go/+/go1.23.3:src/runtime/panic.go;l=804)
- [`sync.(*WaitGroup).Add:+19`](https://cs.opensource.google/go/go/+/go1.23.3:src/sync/waitgroup.go;l=64)
- [`sync.(*WaitGroup).Done:=89`](https://cs.opensource.google/go/go/+/go1.23.3:src/sync/waitgroup.go;l=89)
- [`golang.org/x/tools/gopls/internal/server.(*server).diagnoseChangedViews.func1:+16`](https://cs.opensource.google/go/x/tools/+/gopls/v0.17.1:gopls/internal/server/diagnostics.go;l=169)
- [`golang.org/x/tools/gopls/internal/server.(*server).diagnoseChangedViews.gowrap1:+16`](https://cs.opensource.google/go/x/tools/+/gopls/v0.17.1:gopls/internal/server/diagnostics.go;l=169)
- `runtime.goexit:+0`
```
golang.org/x/tools/gopls@v0.17.1 go1.23.3 linux/amd64 vscode (1)
```
Repository: vscode
Issue: User settings UI does not update when configuration changes
Labels: bug,settings-editor,confirmation-pending

Does this issue occur when all extensions are disabled?: Yes

Version: 1.96.2 (Universal)
Commit: fabdb6a30b49f79a7aba0f2ad9df9b399473380f
Date: 2024-12-19T10:22:47.216Z
Electron: 32.2.6
ElectronBuildId: 10629634
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Darwin arm64 24.2.0

Steps to Reproduce:

1. Implement configuration change handler for a configuration value that will update a configuration value dynamically (so that when the user has the user settings window open a configuration value will update)
2. Update a configuration value in the user settings UI that will trigger an update to a setting while the user settings window is opened and focused.

Note that the UI will become stale.  If the UI loses focus it will update but it will not update as long as the UI is focused.
Repository: transformers
Issue: Add cosmos from Nvidia
Labels: New model

### Model description

https://www.nvidia.com/en-us/ai/cosmos/ on model is autoregressive, all open source

We might have a PR coming directly from NVIDIA! 

### Open source status

- [X] The model implementation is available
- [X] The model weights are available

### Provide useful links for the implementation

_No response_
Repository: vscode
Issue: Allow default folder setting for "load workspace from file"
Labels: feature-request,workbench-workspace

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
For those like me that have many workspace settings files, allow a default folder setting which contains all the .code-workspace files.  When File→Open File From Workspace is selected, open this folder as the default.  If the setting has no value, then use the default as currently implemented.
Repository: neovim
Issue: ci: run benchmark test suite in CI
Labels: enhancement,performance,ci

### Problem

The `test/benchmark` test suite is not run in CI, which means the code there could break or "bit rot".

### Expected behavior

Add a benchmark job in CI. It's only intended to keep the benchmarks in a "runnable state", so I suggest:

- 1 job only (linux).
- only runs on master, not PRs.
- only checks that the suite didn't exit non-zero. doesn't assert any sort of performance goals.
Repository: flutter
Issue: [monorepo] Google test doesn't pick up engine change.
Labels: team-infra,monorepo

### Type of Request

bug

### Infrastructure Environment

google test

### What is happening?

This for example https://github.com/flutter/flutter/pull/161265 which adds new API in dart ui and call it on the frameowrk side. The google test however failed because it didn't pick up the dart ui change. It seems to me the google test is not using the engine from the source code.

### Steps to reproduce

pr that change dart ui and calls it on the framework side

### Expected results

google test should use the engine build from the source code.
Repository: next.js
Issue: dev --turbo in monorepo can't resolve alias import 
Labels: Turbopack

### Link to the code that reproduces this issue

https://github.com/adr-x/next-turbo

### To Reproduce

```
pnpm dev -F web
```

vs

```
pnpm dev-turbo -F web
```

### Current vs. Expected behavior

Expected behavior is to work like on production and resolve the import.

`dev --turbopack` 

![image](https://github.com/user-attachments/assets/fdd24d05-e831-4169-bf93-387452d651b0)

`dev` and `start

![image](https://github.com/user-attachments/assets/8d3873f0-8cfb-4e2c-bfa3-6a49b3540b04)


### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Home
  Available memory (MB): 65444
  Available CPU cores: 12
Binaries:
  Node: 18.20.5
  npm: 10.8.2
  Yarn: N/A
  pnpm: 9.1.2
Relevant Packages:
  next: 15.2.0-canary.1 // Latest available version is detected (15.2.0-canary.1).
  eslint-config-next: N/A
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.5.4
Next.js Config:
  output: N/A
```


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

Turbopack

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

next dev (local)

### Additional context

_No response_
Repository: neovim
Issue: Weird `scrolloff` behavior when virtual lines are present before line 1
Labels: bug,marks

### Problem

When there are virtual lines (extmarks) before line 1 of a buffer, and `scrolloff` is nonzero, scrolling line 1 into view via `scrolloff` will cause a large and unexpected scroll jump.

### Steps to reproduce

1. Open a clean neovim `nvim -u NONE`
2. Insert some lines `ihello<ESC>yy9p`
3. Insert an extmark line above line 1 `:lua vim.api.nvim_buf_set_extmark(0, vim.api.nvim_create_namespace("vline"), 0, 0, { virt_lines={{{"Virt Line", "Comment"}}}, virt_lines_above=true })`
4. Add some more virtual lines `9@:`
5. Set scrolloff `:set scrolloff=4`
6. Set line numbering to make it a bit easer to see `:set nu`
7. Scroll down a little `<C-e><C-e>`
8. Now is when you can witness the bug. Press `k` a couple times and notice that when line 1 gets into the scrolloff range, the buffer jumps all the way up.

### Expected behavior

I would expect pressing `k` with `scrolloff=4` set to still only scroll the buffer up by 1 line when the cursor is already positioned at row 4 of the window.

### Nvim version (nvim -v)

NVIM v0.11.0-dev

### Vim (not Nvim) behaves the same?

yes

### Operating system/version

WSL

### Terminal name/version

WSLTTY

### $TERM environment variable

xterm-256color

### Installation

Neovim PPA
Repository: kubernetes
Issue: [FG:InPlacePodVerticalScaling] avoid checking the configuration of resource managers to learn their expected behavior
Labels: kind/bug,priority/backlog,sig/node,triage/accepted

### What happened?

The VPA logic needs to know if resource managers (cpumanager, memory manager) can allocate exclusively resources.
To do so, it peeks in their configuration and second-guesses their expected behavior.
This is unfortunate and due to the lack of resource manager API which can report the same information

As result of this approach, there's an actual bug in the current VPA logic: this check is wrong https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/kubelet.go#L2856 because the name of the policy for cpumanager is `static` (lowercase "s") while for memory manager is `Static` (uppercase "s")

### What did you expect to happen?

VPA should be able to learn about resource manager behavior in a safe and supported way

### How can we reproduce it (as minimally and precisely as possible)?

configure memory manager with `Static` policy and enable VPA. the `canResizePod` logic will behave incorrectly

### Anything else we need to know?

behavior introduced in 2d8939c4aef8f060d413bb27272ba38cd7171fbe

a new API to expose this information is proposed in https://github.com/kubernetes/kubernetes/pull/128728

### Kubernetes version

<details>

```console
$ kubectl version
# paste output here
```

</details>


### Cloud provider

<details>

</details>


### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>
Repository: godot
Issue: Unable to engage debugger during execution - `Parameter "script_lang" is null.`
Labels: bug,topic:editor,confirmed,regression

### Tested versions

- Reproducible in 4.3.stable and later, not reproducible in 4.2.2



### System information

Godot v4.4.dev7 - Windows 10 (build 19045) - Multi-window, 2 monitors - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1660 SUPER (NVIDIA; 32.0.15.6094) - AMD Ryzen 7 2700X Eight-Core Processor (16 threads)

### Issue description

It appears that when you run a scene in the editor and hit a blocking operation (a large while loop seems to recreate this issue nicely), the editor becomes unable to pause execution, instead returning (on my example script, for instance):

```
E 0:00:01:0489   node_2d.gd:7 @ _ready(): Parameter "script_lang" is null.
  <C++ Source>   core/debugger/remote_debugger.cpp:420 @ debug()
  <Stack Trace>  node_2d.gd:7 @ _ready()
```

I'm not certain if this is something that changed on my end recently, as I only noticed it with dev6, but testing reveals that I can go back as early as 4.3 to recreate the issue in the same way, while 4.2.2 properly pauses execution.

### Steps to reproduce

- Add the code below to a Node2D, run the program.
- Attempt to pause the code before the output prints, in either the scene run buttons or the debugger buttons

### Minimal reproduction project (MRP)

The below script is enough to recreate the issue:
```
extends Node2D

func _ready() -> void:
	var i : int = 0
	while i < 100000000:
		i += 1
	print("loop complete")
```
Repository: godot
Issue: [Windows] Godot console wrapper fails to launch in certain paths
Labels: bug,platform:windows,topic:editor

### Tested versions

4.3.stable
4.4.dev [2582793d408ade0b6ed42f913ae33e7da5fb9184]

### System information

Windows 11

### Issue description

Godot fails to launch the console wrapper when in specific folders, it seems specific to `C:\\Users\\` and doesn't happen in some other paths, but specifically happens with paths with spaces in it

### Steps to reproduce

Try to launch Godot console in a path under `C:\\Users\\` with an username with a space in it, like `C:\\Users\\Foo Bar\\`

### Minimal reproduction project (MRP)

N/A
Repository: PowerToys
Issue: 'PowerToys.Awake.exe --use-pt-config' opens a debug message window
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.87.1

### Installation method

PowerToys auto-update

### Running as admin

No

### Area(s) with issue?

Awake

### Steps to reproduce

Run from a cmd shell:
"\Program Files\PowerToys\PowerToys.Awake.exe" --use-pt-config

This opens a black window with awake debug messages.

This does not happen when running awake with other options. For example, there's no such problem with:
"\Program Files\PowerToys\PowerToys.Awake.exe" --use-parent-pid


### ✔️ Expected Behavior

No debug window with the --use-pt-config, like for the --use-parent-pid option, or with no option at all.

Maybe add a new option enabling debugging messages, if actual debug messages ARE desired?


### ❌ Actual Behavior

_No response_

### Other Software

Windows 11 2024H2 with all the latest updates. [Version 10.0.26100.2605]
Repository: PowerToys
Issue: Theme reversion (Left shift + Alt + PrtScrn) error message
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.87.1

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

General

### Steps to reproduce

Theme reversion (Left shift + Alt + PrtScrn)

### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

[2025-01-08.txt](https://github.com/user-attachments/files/18351802/2025-01-08.txt)