sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: node
Issue: WeakRef has slow performance & degrades runtime performance
Labels: performance

### Version

21.7.2

### Platform

Linux logos 6.8.4-arch1-1 #1 SMP PREEMPT_DYNAMIC Fri, 05 Apr 2024 00:14:23 +0000 x86_64 GNU/Linux

### Subsystem

V8?

### What steps will reproduce the bug?

Install & run the following benchmark as a file.

https://github.com/btakita/weakref-benchmark

Notice that the bunjs is consistent. The Nodejs runtime has a dramatic degradation in performance as soon as WeakRef enters the benchmark.

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

Every time many `WeakRef` objects are instantiated.

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

`WeakRef` should not cause performance degradation in the nodejs runtime.

### What do you see instead?

`WeakRef` causes performance degradation in the nodejs runtime.

### Additional information

I have not done any profiling yet.
Repository: next.js
Issue: Attempted import error: 'useRef' is not exported from 'react' (imported as 'React').
Labels: bug,Runtime,Module Resolution

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/eloquent-hertz-yhpg54

### To Reproduce

Launch the application with `next dev` and access the link.
The problem log will then be output to the terminal.

### Current vs. Expected behavior

I expected nothing to be displayed, but it says `Attempted import error: 'useRef' is not exported from 'react' (imported as 'React').`.

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #102-Ubuntu SMP Wed Jan 10 09:33:48 UTC 2024
  Available memory (MB): 15952
  Available CPU cores: 8
Binaries:
  Node: 21.7.2
  npm: 10.5.0
  Yarn: N/A
  pnpm: 8.15.6
Relevant Packages:
  next: 14.2.0-canary.64 // Latest available version is detected (14.2.0-canary.64).
  eslint-config-next: 13.5.6
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.4.3
Next.js Config:
  output: N/A
```


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

App Router, Middleware / Edge (API routes, runtime), Module resolution (CJS / ESM, module resolving)

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

next dev (local), next build (local)

### Additional context

Very similar to this issue (https://github.com/vercel/next.js/issues/60890)
I think the difference is whether the runtime is edge or not.
Repository: ant-design
Issue: dropdown 组件希望添加分组单选的功能
Labels: 💡 Feature Request,Inactive,unconfirmed

### What problem does this feature solve?

对于分组内数据互斥的情况，限制每个分组内的options为单选，整体上多选


<img width="367" alt="image" src="https://github.com/ant-design/ant-design/assets/72842677/4db620ea-1edb-4bab-9dc1-2cb7cab3a3de">


### What does the proposed API look like?

```jsx
  <Dropdown menu={{ items, selectable:true,multiple:true,exclusiveGroupSelect:true }}>
      ...
  </Dropdown>
<Select mode="multiple" exclusiveGroupSelect/>

```

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: deno
Issue: WeakRef benchmark cause deno panic: Fatal JavaScript out of memory: Reached heap limit
Labels: perf,upstream

```
deno --version
deno 1.42.1 (release, x86_64-unknown-linux-gnu)
v8 12.3.219.9
typescript 5.4.3
```

See https://github.com/btakita/weakref-benchmark

When running `deno ./index.js`, the process panics with `Fatal JavaScript out of memory: Reached heap limit`. Bun runs the benchmark with the least impact. Nodejs has runtime performance degradation.
Repository: ant-design
Issue: Ability to customize styles for List.Item["extra"] 
Labels: 💡 Feature Request,Inactive,unconfirmed

### What problem does this feature solve?

`extra` element wrapper gets margin-bottom added when `sm` breakpoint is hit. Which is unnecessary

### What does the proposed API look like?

```
type List.Item = {
      // here all ListItem props
      styles: {
            extra: CSSProperties
      }
}
```
<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: tensorflow
Issue: tf.raw_ops.Unbatch aborts with "Check failed: d < dims()"
Labels: stat:awaiting tensorflower,type:bug,comp:ops,TF 2.16

### Issue type

Bug

### Have you reproduced the bug with TensorFlow Nightly?

Yes

### Source

binary

### TensorFlow version

tf 2.17

### Custom code

Yes

### OS platform and distribution

Linux Ubuntu 20.04.3 LTS

### Mobile device

_No response_

### Python version

Python 3.11.8

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

`tf.raw_ops.Unbatch` aborts with "Check failed: d < dims()"

### Standalone code to reproduce the issue

```shell
import tensorflow as tf

tf.raw_ops.Unbatch(batched_tensor=tf.random.uniform([], dtype=tf.dtypes.float32, maxval=100000000),batch_index=tf.random.uniform([1], dtype=tf.dtypes.int64, minval=-100000000, maxval=1000000000),id=tf.random.uniform([4], dtype=tf.dtypes.int64, minval=-100000000, maxval=1000000000),timeout_micros=30,container="N/J,",shared_name="&o0n7W",)
```


### Relevant log output

```shell
2024-04-10 06:36:02.435578: F tensorflow/core/framework/tensor_shape.cc:357] Check failed: d < dims() (1 vs. 1)
Aborted (core dumped)
```
Repository: bitcoin
Issue: ci: Lower and unify default stack size
Labels: Brainstorming,Tests

Default stack size differs across operating systems. E.g. the defaults for thread stack sizes: Linux: 8MiB, Windows 1MiB, FreeBSD 2MiB, OpenBSD 512 KiB.

It would be sensible to lower the stack size used in all CI jobs to the lowest default, so we don't miss stack overflow bugs that only occur with small stack sizes.
Repository: godot
Issue: Typed array assignment fails on unambiguous case
Labels: discussion,topic:gdscript

### Tested versions

v4.3.dev.custom_build [a7b860250]

### System information

linux

### Issue description

```gdscript
var untyped: Array = PackedStringArray() # works
var typed: Array[String] = PackedStringArray() # doesn't work
``` 
![image](https://github.com/godotengine/godot/assets/71937306/8bdb1a12-59fb-40fa-ae7c-a46a70384175)

I think it should work, we know it's all strings.

### Steps to reproduce

see above

### Minimal reproduction project (MRP)

any
Repository: next.js
Issue: Navigating from `not-found` page in production doesn't work when server-rendered on demand
Labels: bug,Navigation

### Link to the code that reproduces this issue

https://github.com/paalprogger/nextjs-not-found-ssr-link-bug

### To Reproduce

1. Build the application (`npm run build`)
2. Start the application (`npm run start`)
3. Navigate to a page that doesn't exist (Ex. `http://localhost:3000/test`)
4. Press the "Go back" link

### Current vs. Expected behavior

Following the steps from the previous section, I expected to navigate back to the landing page, instead only the pathname changed and the `not-found` page is still displayed. A refresh is needed to display the correct page.

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.3.0: Wed Dec 20 21:31:00 PST 2023; root:xnu-10002.81.5~7/RELEASE_ARM64_T6020
Binaries:
  Node: 21.4.0
  npm: 10.5.1
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.1.4
  eslint-config-next: 14.1.4
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.4.4
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

App Router, Routing (next/router, next/navigation, next/link)

### Which stage(s) are affected? (Select all that apply)

next build (local), next start (local), Vercel (Deployed)

### Additional context

I found this issue by having a component in my root layout which uses `getServerSession` from `next-auth`. The `getServerSession` uses the `headers` function from `next/headers` which causes the `not-found` page to be server rendered because the root layout wraps the `not-found` page.
Repository: godot
Issue: Autoload global variable disabled not working 
Labels: enhancement,documentation

### Tested versions

Only tested with Godot v4.3.dev5

### System information

Godot v4.3.dev5 - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1070 (NVIDIA; 31.0.15.4617) - AMD Ryzen 5 3600 6-Core Processor (12 Threads)

### Issue description

I have an autoload and by default the global variable is enabled, but it appears to still be enabled even when unchecked I haven't tested with a script but tested with a scene and the only way for it to not be enabled was removing it and I don't think that's how It's supposed to work? 

### Steps to reproduce

Autoload a scene and uncheck enable, and it still works but removing it disables it

### Minimal reproduction project (MRP)

n/a
Repository: vscode
Issue: Rename Extension Telemetry log to Telemetry (Extensions)
Labels: debt,file-explorer

Rename Extension Telemetry log to Telemetry (Extensions) so that they will be next to each other.

![Image](https://github.com/microsoft/vscode/assets/10746682/9a1d4353-df45-4210-90d7-9fc585ddd039)
Repository: rust
Issue: `rustc` suggests `for<'a>` when lifetime param already exists
Labels: A-diagnostics,A-resolve,A-lifetimes,T-compiler,A-suggestion-diagnostics,D-incorrect

### Code

```Rust
fn abs<'a, T>(x: &'a T) -> T
where
    &'a T: Ord + core::ops::Neg<Output = &T>,
    T: Clone,
{
    x.max(-x).clone()
}
```


### Current output

```Shell
Compiling playground v0.0.1 (/playground)
error[E0637]: `&` without an explicit lifetime name cannot be used here
 --> src/lib.rs:3:42
  |
3 |     &'a T: Ord + core::ops::Neg<Output = &T>,
  |                                          ^ explicit lifetime name needed here
  |
help: consider introducing a higher-ranked lifetime here
  |
3 |     &'a T: Ord + for<'a> core::ops::Neg<Output = &'a T>,
  |                  +++++++                          ++

For more information about this error, try `rustc --explain E0637`.
error: could not compile `playground` (lib) due to 1 previous error
```


### Desired output

```Shell
Compiling playground v0.0.1 (/playground)
error[E0637]: `&` without an explicit lifetime name cannot be used here
 --> src/lib.rs:3:42
  |
3 |     &'a T: Ord + core::ops::Neg<Output = &T>,
  |                                          ^ explicit lifetime name needed here
  |
help: consider introducing a higher-ranked lifetime here
  |
3 |     &'a T: Ord + core::ops::Neg<Output = &'a T>,
  |                                           ++

For more information about this error, try `rustc --explain E0637`.
error: could not compile `playground` (lib) due to 1 previous error
```


### Rationale and extra context

Following the compiler's suggestion:
```Shell
   Compiling playground v0.0.1 (/playground)
error[E0496]: lifetime name `'a` shadows a lifetime name that is already in scope
 --> src/lib.rs:3:22
  |
1 | fn abs<'a, T>(x: &'a T) -> T
  |        -- first declared here
2 | where
3 |     &'a T: Ord + for<'a> core::ops::Neg<Output = &'a T>,
  |                      ^^ lifetime `'a` already in scope

For more information about this error, try `rustc --explain E0496`.
error: could not compile `playground` (lib) due to 1 previous error
```

### Other cases

_No response_

### Rust Version

```Shell
From playground:
1.79.0-nightly

(2024-04-08 ab5bda1aa70f707014e2)
```


### Anything else?

_No response_
Repository: storybook
Issue: [Bug]: vue compiler failed because props type reference to an imported type
Labels: bug,needs triage

### Describe the bug

@vue/compiler-sfc In version 3.2 and below the generic type parameter for defineProps() were limited to a type literal or a reference to a local interface.
This limitation has been resolved in 3.3, please update latest version to fix this problem.

### To Reproduce

![屏幕截图 2024-04-10 173216](https://github.com/storybookjs/storybook/assets/79828139/aca6c0bb-fb0f-438f-826c-927a4b4429f3)
![屏幕截图 2024-04-10 173315](https://github.com/storybookjs/storybook/assets/79828139/1e7c81a9-57fd-4152-8ccf-9e305220717b)


### System

```bash
Need to install the following packages:
storybook@8.0.6
```


### Additional context

_No response_
Repository: vscode
Issue: editorGutter.background doesn't apply to sticky scroll but I feel like it should
Labels: polish,editor-sticky-scroll

I'm on VS Code 1.88.0 on Ubuntu Snap. `editorGutter.background` does not apply to the editor sticky scroll area's gutter, but I feel like it either should, or a dedicated colour customization point be added for it.
Repository: PowerToys
Issue: Add a mode to automatically disable Remap Key when using your computer via Remote Desktop.
Labels: Product-Keyboard Shortcut Manager,Needs-Triage

### Description of the new feature / enhancement

Add to Keyboard Manager a mode to automatically disable Remap Key when using a computer via Remote Desktop. But it would be even better if it were possible to add a second set of Remap Keys to work via Remote Desktop.

### Scenario when this would be used?

I use my home iMac or MacBook for remote work. And every time you log in via Remote Desktop, you have to turn off the Keyboard Manager in order to work comfortably, since on my working keyboard, for convenience, the Ctrl Win Alt -> Ctrl Alt Win keys have been replaced (imitation of Apple Keyboard), which does not work well together with Remote Desktop.
And if it were possible to automatically turn off, or a second set of settings (which is much better), then this would greatly simplify the process!

### Supporting information

_No response_
Repository: three.js
Issue: Expose 'count' property in BatchedMesh
Labels: Suggestion

### Description

`BatchedMesh` doesn't have a public `count` property, `InstancedMesh` does though (https://threejs.org/docs/#api/en/objects/InstancedMesh.count).

Without it it becomes pretty complicated to know how many objects/geometries have been added to a `BatchedMesh` instance and do operations like traversing all of them to set the matrices, make sure you are in the range before updating one of them, etc.

### Solution

I see that the `BatchedMesh` implementation is already using a private `_geometryCount` property, it should be as easy as to rename it as `count` and update the docs.

### Alternatives

I think the proposed solution is the best as it would converge the API with `InstancedMesh`.

### Additional context

_No response_
Repository: react-native
Issue: TypeError: _reactNative.AccessibilityInfo.announceForAccessibilityWithOptions is not a function
Labels: API: AccessibilityInfo,Needs: Triage :mag:,Needs: Repro,Needs: Attention

### Description

When using AccessibilityInfo.announceForAccessibility no problems come when I run jest, but when I change it to  AccessibilityInfo.announceForAccessibilityWithOptions I get: `TypeError: _reactNative.AccessibilityInfo.announceForAccessibilityWithOptions is not a function`
I checked node_modules/react-native/jest/setup.js file I can see that under AccessibilityInfo there is no announceForAccessibilityWithOptions mocking, but when I change announceForAccessibility -> announceForAccessibilityWithOptions in that file then tests run without issues (not going to obviously leave it like this, just tested if that helps).

I tried to mock announceForAccessibilityWithOptions within my own jest.setup file, but that created a lot of different issues.

### Steps to reproduce

Use AccessibilityInfo.announceForAccessibilityWithOptions() and run jest and you'll get an issue `TypeError: _reactNative.AccessibilityInfo.announceForAccessibilityWithOptions is not a function`

### React Native Version

0.73.6

### Affected Platforms

Build - MacOS

### Output of `npx react-native info`

```text
info Fetching system and libraries information...
System:
  OS: macOS 14.2.1
  CPU: (10) arm64 Apple M2 Pro
  Memory: 613.63 MB / 32.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 20.11.0
    path: ~/.nvm/versions/node/v20.11.0/bin/node
  Yarn:
    version: 1.22.19
    path: /opt/homebrew/bin/yarn
  npm:
    version: 10.2.4
    path: ~/.nvm/versions/node/v20.11.0/bin/npm
  Watchman:
    version: 2023.12.04.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.14.2
    path: /Users/jonnesten/.asdf/shims/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.2
      - iOS 17.2
      - macOS 14.2
      - tvOS 17.2
      - visionOS 1.0
      - watchOS 10.2
  Android SDK: Not Found
IDEs:
  Android Studio: 2023.1 AI-231.9392.1.2311.11076708
  Xcode:
    version: 15.2/15C500b
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.9
    path: /usr/bin/javac
  Ruby:
    version: 3.2.2
    path: /Users/jonnesten/.asdf/shims/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.73.6
    wanted: 0.73.6
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: false
```


### Stacktrace or Logs

```text
`TypeError: _reactNative.AccessibilityInfo.announceForAccessibilityWithOptions is not a function`
```


### Reproducer

n/a

### Screenshots and Videos

_No response_
Repository: deno
Issue: Socket equivalent class is not implemented in FakeSocket class
Labels: bug,needs investigation,node compat,node API

Versions:
```
deno 1.42.0 (release, aarch64-apple-darwin)
v8 12.3.219.9
typescript 5.4.3
```

# Overview

The FakeSocket class does not implement a Socket equivalent.

[FakeSocket](https://github.com/denoland/deno/blob/2ec366f54423dc577379b9245e498681fccf3050/ext/node/polyfills/http.ts#L273)

[Socket Class](https://github.com/denoland/deno/blob/a4f3e7436e81cd229f85657f2fee2caaa0e3b05e/ext/node/polyfills/dgram.ts#L155)

In my example, the unref() method is not implemented and an exception was raised by referencing undefined in the Node.js package of testcontainers.

If all is well, I will create a PR to add dummy methods (`()=>{}`) to FakeSocket from the Socket class definition.

What do you think of this approach?

# Related Issue

https://github.com/testcontainers/testcontainers-node/issues/753

https://github.com/denoland/deno/issues/19571
Repository: rust
Issue: [MacOS] UDP Multicast: Can't assign requested address on interface 0 (as suggested in the documentation)
Labels: O-macos,C-bug,T-libs

So far tested on:
- windows 11: **works**
- macos 14.4: **doesn't work**

The following code
```rust
use std::net::{Ipv6Addr, SocketAddrV6, UdpSocket};
use std::str::FromStr;

fn main() {
    let local = SocketAddrV6::new(Ipv6Addr::UNSPECIFIED, 61666, 0, 0);
    let multicast = Ipv6Addr::from_str("ff02::fb").unwrap();
    let udp = UdpSocket::bind(&local).expect("Unable to bind!");
    udp.join_multicast_v6(&multicast, 0).expect("Unable to join to multicast...");

    match udp.send_to(b"Hello", "[::1]:61666") { // Trying to send a packet to multicast address...
        Ok(bytes_sent) => println!("Sent {} bytes", bytes_sent),
        Err(err) => eprintln!("Error sending data: {}", err),
    }
}
```
produces the following error:
> Unable to join to multicast...: Os { code: 49, kind: AddrNotAvailable, message: "Can't assign requested address" }

It is expected for the socket to join the group (in documentation it also says setting interface to 0 allows for the OS to decide on the interface).

However instead of that, on macOS the above error happens. On windows however, it does not and works as expected.

### 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.77.2 (25ef9e3d8 2024-04-09)
binary: rustc
commit-hash: 25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04
commit-date: 2024-04-09
host: aarch64-apple-darwin
release: 1.77.2
LLVM version: 17.0.6
```
Repository: TypeScript
Issue: "Output generation failed" when transpiling "test.d.abc.ts"
Labels: Suggestion,Domain: Error Messages,Experience Enhancement

### 🔎 Search Terms

"Output generation failed", "transpileModule"

### 🕗 Version & Regression Information

- This is a crash
- This changed between versions 5.0.0-dev.20230109 and 5.0.0-dev.20230110
- This is the behavior in every version I tried, and I reviewed the FAQ for entries about file names



### ⏯ Playground Link

_No response_

### 💻 Code

```ts
const TS = require('typescript')

const res = TS.transpileModule('export const x = 6;', {
    fileName: 'test.d.tsp.ts',
});

console.log(res)
```


### 🙁 Actual behavior

The Typescript compiler crashes. The compiler should allow files that contain .d. in their name.

### 🙂 Expected behavior

The compilation succeeds

### Additional information about the issue

```
c:\Users\osv\Downloads\test>npm i typescript@5.0.0-dev.20230110

changed 1 package, and audited 2 packages in 5s

found 0 vulnerabilities

c:\Users\osv\Downloads\test>node main.js
c:\Users\osv\Downloads\test\node_modules\typescript\lib\typescript.js:1772
          throw e;
          ^

Error: Debug Failure. Output generation failed
    at Object.transpileModule (c:\Users\osv\Downloads\test\node_modules\typescript\lib\typescript.js:127318:20)
    at Object.<anonymous> (c:\Users\osv\Downloads\test\main.js:3:16)
    at Module._compile (node:internal/modules/cjs/loader:1376:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1435:10)
    at Module.load (node:internal/modules/cjs/loader:1207:32)
    at Module._load (node:internal/modules/cjs/loader:1023:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:135:12)
    at node:internal/main/run_main_module:28:49

Node.js v20.11.1

c:\Users\osv\Downloads\test>npm i typescript@5.0.0-dev.20230109

changed 1 package, and audited 2 packages in 745ms

found 0 vulnerabilities

c:\Users\osv\Downloads\test>node main.js
{
  outputText: '"use strict";\r\n' +
    'Object.defineProperty(exports, "__esModule", { value: true });\r\n' +
    'exports.x = void 0;\r\n' +
    'exports.x = 6;\r\n',
  diagnostics: [],
  sourceMapText: undefined
}
```