sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Runtime use of the inspector to modify the size and elements of arrays in multiple threads has a probability of causing an internal editor error
Labels: discussion,topic:editor,needs testing

### Tested versions

Can be reproduced in the following versions:
`v4.3.stable.official` [77dcf97d8]
`v4.4.dev3.official` [f4af8201b]

### System information

Godot v4.4.dev3 - Windows 10.0.22631 - Multi-window, 2 monitors - Vulkan (Forward+) - integrated Intel(R) UHD Graphics (Intel Corporation; 31.0.101.4502) - 12th Gen Intel(R) Core(TM) i5-12450H (12 threads)

### Issue description

Using the remote inspector to modify the data and array length of an array that is being modified by a thread **other** than the `main thread` has a probability of triggering an error inside the editor.
Sample video:

https://github.com/user-attachments/assets/df9f7156-41b8-4edc-a8a5-1e05cfb8b0e3


Personally, it may be caused by 
> traversing containers in multiple threads is thread-unsafe behavior

### Steps to reproduce

* Open and run the project
* Open the `Remote` Tab at the top of the `Node list` on the left
* Click on the `MainScene` node and make sure that the `Inspector` on the right shows the current information for this node correctly
* Attempt to modify the data and size of an array with attribute name `Number Arr` and size 100

If you reproduce the error, you may see the following error message in the debugger:
```
MainScene.gd:34 @ mainForThread(): Condition "!success" is true.
MainScene.gd:34 @ mainForThread(): Parameter "_fp" is null.
MainScene.gd:34 @ mainForThread(): Parameter "_fp" is null.
```

### Minimal reproduction project (MRP)

[MultithreadDebugError.zip](https://github.com/user-attachments/files/17285325/MultithreadDebugError.zip)
Repository: deno
Issue: Web Workers use 7x more memory than in Chrome, and terminating them doesn't remove all the memory
Labels: bug,needs investigation

Version: Tested in Deno `1.46.x` and `2.x`

The code below creates 100 workers, then waits 5 seconds, then terminates them, and repeats.
* In Chrome the memory usage spikes to +150mb, and then back down to zero each cycle. 
* In Deno, it spikes to +1000mb, but doesn't go back down to zero. It accumlates memory per cycle
  * **EDIT**: up to a maximum of +1500mb, so this extra 500mb is potentially just due to some sort of resource pool, or something - maybe expected behavior
  * **EDIT 2**: It does continue creeping up slowly - after 100k workers created+destroyed, it's now at 700mb
  * **EDIT 3**: After 500k workers created+destroyed, it's now at about 2000mb leaked.
```js
if(self.Deno) {
  console.log(Deno.memoryUsage());
  setInterval(() => {
    console.log(Deno.memoryUsage());
  }, 1000);
}

while(1) {

  let workers = [];
  for(let i = 0; i < 100; i++) {
    const workerBlob = new Blob([`
      delete globalThis.Deno;
      self.onmessage = async function(e) {
        self.postMessage('Hello from Worker!');
      }
    `], {type:"application/javascript"});

    const workerURL = URL.createObjectURL(workerBlob);
    const worker = new Worker(workerURL, {type:"module"});

    worker.onmessage = function(e) {
      URL.revokeObjectURL(workerURL);
      console.log('Received from worker:', e.data);
    };
    worker.postMessage('Hello from main thread!');

    workers.push(worker);
  }

  await new Promise(r => setTimeout(r, 5*1000));

  for(let w of workers) w.terminate();
  workers = [];

}
```
Repository: godot
Issue: Transparent windows become permanently opaque when opened on an HDR-enabled monitor in Windows
Labels: bug,platform:windows,topic:gui

### Tested versions

- Reproducible in: v4.3.stable

### System information

Godot v4.3.stable - Windows 10.0.22631 - GLES3 (Compatibility) - AMD Radeon RX 6600 (Advanced Micro Devices, Inc.; 32.0.12011.1036)

### Issue description

Transparent windows become permanently opaque if they open on an HDR-enabled monitor in Windows. Disabling "Auto HDR" in Windows has no effect.

### Steps to reproduce

Requires an HDR monitor. Not tested on Windows 10 or Nvidia GPUs.

To create MRP, create project with the following settings:

```
[display]

window/size/transparent=true
window/per_pixel_transparency/allowed=true

[rendering]

renderer/rendering_method="gl_compatibility"
renderer/rendering_method.mobile="gl_compatibility"
viewport/transparent_background=true
```

#### With MRP:
Run project on HDR-enabled monitor in Windows -> **black background** ❌
Run project on HDR-disabled monitor -> transparent background ✅
Run project on HDR-disabled monitor and move window to HDR-enabled monitor -> transparent background ✅
Run project on HDR-disabled monitor and enable HDR on that monitor -> transparent background ✅

### Minimal reproduction project (MRP)

[mrp-godot-hdr-transparency.zip](https://github.com/user-attachments/files/17285445/mrp-godot-hdr-transparency.zip) (Godot v4.3.stable, 2 KiB)
Repository: react-native
Issue: Transform (scale, rotate and skew) not working correctly on Android 8.1 and below!
Labels: Platform: Android,Newer Patch Available

### Description

I've encountered inconsistent behavior with scaling, rotation, and skewing transformations on older Android versions. Specifically, none of these transformations work on Android 7 and below, while scaling works on Android 8 and 8.1 but rotation and skewing do not. The issue seems to be resolved on Android 10 and above. Is this a known limitation or bug, and are there any documented workarounds?
![Screenshot_2024-10-07-19-02-34](https://github.com/user-attachments/assets/78d5001e-6edb-419b-b970-a3347beed3ee)



### Steps to reproduce

1. `npx create-expo-app@latest --template blank`
2. copy the code from [transform doc](https://reactnative.dev/docs/transforms#example)
3. start the app on Android 8.1 and below
4. saw a weird behavior of scaling, rotation, and skewing

### React Native Version

0.75.4

### Affected Platforms

Runtime - Android

### Output of `npx react-native info`

```text
System:
  OS: Windows 10 10.0.19045
  CPU: (2) x64 Intel(R) Core(TM)2 Duo CPU     E7500  @ 2.93GHz
  Memory: 975.01 MB / 7.75 GB
Binaries:
  Node:
    version: 20.11.1
    path: C:\Program Files\nodejs\node.EXE
  Yarn:
    version: 1.22.21
    path: ~\AppData\Roaming\npm\yarn.CMD
  npm:
    version: 10.2.5
    path: C:\Program Files\nodejs\npm.CMD
  Watchman: Not Found
SDKs:
  Android SDK: Not Found
  Windows SDK:
    AllowDevelopmentWithoutDevLicense: Enabled
IDEs:
  Android Studio: AI-241.18034.62.2411.12071903
  Visual Studio: Not Found
Languages:
  Java:
    version: 21.0.1
    path: /c/Program Files/Common Files/Oracle/Java/javapath/javac
  Ruby: Not Found
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.75.4
    wanted: 0.75.4
  react-native-windows: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: Not found
  newArchEnabled: Not found
iOS:
  hermesEnabled: Not found
  newArchEnabled: Not found
```


### Stacktrace or Logs

```text
none
```


### Reproducer

https://github.com/Ammar1999y/react-native-transforms

### Screenshots and Videos

_No response_
Repository: TypeScript
Issue: Add Temporal (Stage 3) types
Labels: Domain: lib.d.ts

### ⚙ Compilation target

ESNext

### ⚙ Library

n/a

### Missing / Incorrect Definition

- `Temporal`
- `Temporal.Now`
- `Temporal.Instant`
- `Temporal.ZonedDateTime`
- `Temporal.PlainDate`, `Temporal.PlainTime`, `Temporal.PlainDateTime`
- `Temporal.PlainYearMonth`, `Temporal.PlainMonthDay`
- `Temporal.Duration`

### Sample Code

```TypeScript
const now = Temporal.Now.instant();
const past = Temporal.Instant.from('1969-07-20T20:17Z');
```


### Documentation Link

https://tc39.es/proposal-temporal/docs/index.html

The API itself is quite stable. It is calendar that is blocking implementation.
Repository: godot
Issue: No warning when attempting to access native enum types from instance.
Labels: bug,discussion,topic:gdscript

### Tested versions

v4.2.2.stable.official [15073afe3]

### System information

Godot v4.2.2.stable - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1060 6GB (NVIDIA; 32.0.15.5612) - Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz (4 Threads)

### Issue description

The GDScript analyzer does not warn about accessing Enum types from an instance. 

For example, in a script that extends `Node`, `print(self.ConnectFlags)` does not raise a warning from the analyzer, yet produces the runtime error "Invalid get index 'ConnectFlags'". This behavior feels inconsistent with how accessing other global properties work. For example `print(self.Object)` raises the analyzer warning "The property "Object" is not present on the inferred type". On the other hand accessing an Enum value from an instance, e.g., `print(self.CONNECT_DEFERRED)` runs without error and prints the correct value.

### Steps to reproduce

```gdscript
extends Node

func _ready():
	print(self.ConnectFlags)
```

### Minimal reproduction project (MRP)

N/A
Repository: next.js
Issue: SWC minify bug
Labels: bug,SWC

### Link to the code that reproduces this issue

https://github.com/luixo/receipt-app/commits/swc-minify-bug

### To Reproduce

Unfortunately, this bug is quite hard to reproduce with a minimal version due to a bunch of mechanisms involved in building process.
You can reproduce the bug in my project repo or via injecting code in SWC minification.

With my project:
1. Checkout project on a given branch
1. `corepack enable && yarn install`
1. Copy `.env.example` as `.env.local`
1. `NODE_ENV=test npx dotenv -c -- yarn web:build`
1. `NODE_ENV=test npx dotenv -c -- yarn web:start`

With a SWC minification:
1. Create a next project (v14, it seems to be fixed in v15)
1. Get to SWC minify function (`node_modules/next/dist/build/swc/index.js`)
1. Add `const failingSrc = '...'` from additional context to the file
1. Add `minify(failingSrc, { compress: true, mangle: true, output: { comments: false } }).then(({code}) => console.log(code))` somewhere in the end of the file
1. Run `rm -rf .next && npm run build`

### Current vs. Expected behavior

Expected: Compiled version doesn't have an undefined variable
Current: Compiled version does have an undefined variable

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.0.0: Tue Sep 24 23:37:25 PDT 2024; root:xnu-11215.1.12~1/RELEASE_ARM64_T6030
  Available memory (MB): 36864
  Available CPU cores: 12
Binaries:
  Node: 20.15.1
  npm: 10.7.0
  Yarn: 3.6.2
  pnpm: N/A
Relevant Packages:
  next: 14.2.14 // Latest available version is detected (14.2.14).
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.5.4
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

SWC

### Which stage(s) are affected? (Select all that apply)

next build (local)

### Additional context

The failing src code:
```js
const foo = function(fn) {
    const options = {
        param: {
            value: "",
        },
    };
    const store = (obj) => obj[options.param.value];
    fn(() => store);
}
```
It's compiled to:
```js
let foo=function(e){let l=e=>e[options_param.value];e(()=>l)};
```
Or beautified:
```js
let foo = function(e) {
    let l = e => e[options_param.value];
    e(() => l)
};
```
You can witness that `options_param` is an undefined value that is lost from the context.

The real example is way bigger, so this is the smallest I could make still fail.
Repository: ollama
Issue: openai: support max_completion_tokens due to deprecation of max_tokens
Labels: feature request,api

max_tokens is now deprecated for max_completion_tokens. I suspect we should support both. One way is to define another field in our request object and then default if one or the other isn't set https://github.com/ollama/ollama/blob/defbf9425af8228f3420d567e9eeaa29d8ac87e3/openai/openai.go#L77

See https://platform.openai.com/docs/api-reference/chat/create#chat-create-max_tokens
See https://github.com/openai/openai-openapi/blob/10053bef25cd50a7424f5265ba51a7a63ba95b48/openapi.yaml#L9854-L9866
Repository: flutter
Issue: [go_router_builder]: Since `go_router: 14.2.9`, generated locations are different for route paths with or without slash
Labels: package,has reproducible steps,P2,p: go_router,p: go_router_builder,team-go_router,triaged-go_router,found in release: 3.24

### Steps to reproduce

Define a route with child route . all child route contains '/' in their path
ex: "/abc", "/edg"

### Expected results

.g.dart file cannot generate correct path for child

### Actual results

generate correct path

### Code sample

<details open><summary>Code sample</summary>

```dart

TypedGoRoute<ProfileRoute>(
          path: "/profile",
          routes: [
            TypedGoRoute<SettingRoute>(
              path: "/setting",
              ....      
```

</details>


### Screenshots or Video

<details open>
<summary>Screenshots / Video demonstration</summary>

[Upload media here]

</details>


### Logs

<details open><summary>Logs</summary>

```console
[Paste your logs here]
```

</details>


### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
[✓] Flutter (Channel stable, 3.24.3, on macOS 14.5 23F79 darwin-arm64, locale vi-VN)
    • Flutter version 3.24.3 on channel stable at /Users/hieucg/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 2663184aa7 (4 weeks ago), 2024-09-11 16:27:48 -0500
    • Engine revision 36335019a8
    • Dart version 3.5.3
    • DevTools version 2.37.3

[✓] Android toolchain - develop for Android devices (Android SDK version 35.0.0)
    • Android SDK at /Users/hieucg/Library/Android/sdk
    • Platform android-35, build-tools 35.0.0
    • ANDROID_HOME = /Users/hieucg/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.11+0-17.0.11b1207.24-11852314)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 16.0)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 16A242d
    • CocoaPods version 1.15.2

[✓] Android Studio (version 2024.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.11+0-17.0.11b1207.24-11852314)

[✓] VS Code (version 1.94.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.98.0
```

</details>
Repository: flutter
Issue: Need a health check that warns if a test is not covered by a GN rule
Labels: P3,c: tech-debt,team-engine,triaged-engine,e: engine-tool

For C++ this is at least more obvious (it can't run locally either), but for other languages (i.e. Dart) it will be possible to run these tests locally but a GN rule might not exist, meaning (eventually) it won't run on CI. We should try to (including for C++) lint the repo for test entrypoints that do not have a test GN rule.

Needs a discussion before it can be started.
Repository: ant-design
Issue: Cascader.Panel  组件希望能增加defaultExpand功能
Labels: 💡 Feature Request,Inactive

### What problem does this feature solve?

当级联选择器当做面板功能使用时，希望能默认展开一个节点，而不是需要手动一层层点击才能展示末级节点

### What does the proposed API look like?

增加defaultExpand 功能，以便Cascader.Panel组件可以默认展开节点

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: pytorch
Issue: Add support for using NestedTensors with linalg operations
Labels: triaged,module: linear algebra,module: nestedtensor

### 🚀 The feature, motivation and pitch

I have a scenario where I'm currently calling `torch.linalg.ldl_factor` on a bunch of tensors and then repeatedly calling `torch.linalg.ldl_solve` as part of an iterative linear systems solver. Currently I have to do this in a loop for each tensor, as all my tensors may not have exactly the same dimensions. For example, one tensor may be 1024x1024 and another may be 1019x1019, so I can't create a batch and use that.

It would be really handy to be able to use NestedTensor's with these operations to batch the call (to take advantage of multiprocessing of batched operations, and to optionally ship it to the GPU), as I could then store a single NestedTensor with the factorisations (ideally having a slick, inbuilt method to store only the elements from the lower triangle, to save memory when there's no real need to store the upper triangle of zeros) and then be able to repeatedly call the solver during the iterations with the NestedTensor factorisations (and have it parse the lower triangle back to the solver as required).

### Alternatives

Currently has to be performed individually for each tensor in a loop.

### Additional context

_No response_

cc @jianyuh @nikitaved @pearu @mruberry @walterddr @xwang233 @Lezcano @cpuhrsch @jbschlosser @bhosmer @drisspg @soulitzer @davidberard98 @YuqingJ
Repository: PowerToys
Issue: In a borderless mouse, the mouse can become one-way.（境界のないマウスにおいて、マウスが一方通行になってしまう。）
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.85.1 (Both PC)

### Installation method

Other (please specify in "Steps to Reproduce")

### Running as admin

Yes

### Area(s) with issue?

Mouse Without Borders

### Steps to reproduce

Always

### ✔️ Expected Behavior

Control a PC B using the mouse connected to PC A.
AのPCに接続しているマウスからBのPCを操作できるようにする。

### ❌ Actual Behavior

The mouse connected to PC A cannot be moved to PC B, while the mouse connected to PC B can be moved to PC A. If PC B is functioning normally but PC A is not, could this be a bug? This issue occurs constantly, not just at certain times.

The PowerToys version has been updated to the latest, the Firewall has been set to exclude, and the options are the same on both sides. The network IP addresses also match on the first three digits, which has been confirmed. The operating system being used is Windows 11 Home Edition.
![2024-10-08_12h24_34](https://github.com/user-attachments/assets/eb235678-5949-4fa3-aa77-53d05b3f1ffa)

※The following is the Japanese text translated into English:The text below is in Japanese.

AというPCに接続しているマウスはBのPCに移動できず、BというPCに接続しているマウスはAのPCに移動できます。Bが正常に機能しているのにAが正常に機能していないのは何かバグではないでしょうか？ 何かのタイミングで発生する訳ではなく常時そのようになっております。
PowerToysのバージョンも最新に合わせており、Firewallも除外設定済み、オプションも両方同じ設定です。ネットワークも IPアドレスの頭3つは双方合っており同じであることは確認済です。使用しているのはWIN11 HomeEditionです。

### Other Software

_No response_
Repository: PowerToys
Issue: Peek: Expand Navigation Keyboard Shortcuts
Labels: Needs-Triage

### Description of the new feature / enhancement

Current shortcuts include the keys Up, Down, Left and Right, and they are used interchangeably for navigating through files and file content.
Adding support for CTRL + arrow keys would double the total shortcuts and make navigation easier and more functional.
For instance, single arrow keys could be used strictly to control file navigation, eg, going from a file to another, while CTRL+arrow keys could be used to control navigation through the file content.
A switch could be added to the Peek settings to let the user switch behaviors, making single arrows control content navigation, for example.

### Scenario when this would be used?

Files such as PDFs, text files and videos require the user to be able to browse through the content during preview, which is already possible, but introduces additional steps to mitigate the absense of exclusive shortcuts. As of now, to switch between file navigation and content navigation, it is required to use the Tab key to switch keyboard focus across the Peek UI. Far from optimal, but possible.
With a wider set of shortcuts, it would be possible to control file navigation using single arrow keys, while using CTRL+arrow keys would control the file content, such as scrolling through a TXT or PDF file, or controling playback for video files.

For instance, CTRL+Right or CTRL+Down could be used to jump forward (skip N seconds) or scroll down on a text file, while CTRL+Left and CTRL+Up could be used to jump backwards or scroll up.

### Supporting information

_No response_
Repository: create-react-app
Issue: create-expo-app fails
Labels: needs triage

I get this error when trying to create a new expo-app

5183 verbose pkgid babel-plugin-react-compiler@0.0.0-experimental-7779988-20241007
5184 error code 1
5185 error path C:\Users\isaac\Documents\projects\Payjon\node_modules\babel-plugin-react-compiler
5186 error command failed
5187 error command C:\windows\system32\cmd.exe /d /s /c ./scripts/link-react-compiler-runtime.sh
5188 error '.' nï¿½o ï¿½ reconhecido como um comando interno
5188 error ou externo, um programa operï¿½vel ou um arquivo em lotes.
5189 silly unfinished npm timer reify 1728359810537
5190 silly unfinished npm timer reify:build 1728359826985
5191 silly unfinished npm timer build 1728359826987
5192 silly unfinished npm timer build:deps 1728359826987
5193 silly unfinished npm timer build:run:postinstall 1728359827074
5194 silly unfinished npm timer build:run:postinstall:node_modules/babel-plugin-react-compiler 1728359827074
5195 verbose cwd C:\Users\isaac\Documents\projects\Payjon
5196 verbose os Windows_NT 10.0.22631
5197 verbose node v20.16.0
5198 verbose npm  v10.9.0
5199 verbose exit 1
5200 verbose code 1
5201 error A complete log of this run can be found in: C:\Users\isaac\AppData\Local\npm-cache\_logs\2024-10-08T03_56_50_130Z-debug-0.log
Repository: vscode
Issue: Help -> Report Issue -> Create on GitHub silently fails
Labels: bug,issue-reporter

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
#### VS Code Version: 
  Version: 1.94.0
  Commit: d78a74bcdfad14d5d3b1b782f87255d802b57511
  Date: 2024-10-02T13:08:12.626Z
  Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) 
  AppleWebKit/537.36 (KHTML, like Gecko) Code/1.94.0 
  Chrome/124.0.6367.243 Electron/30.5.1 Safari/537.36

#### OS Version: 
15.0.1 (24A348)

#### Steps to Reproduce:

1. Open the Report Issue window via `Help` -> `Report Issue`
2. Fill in the fields
3. Press `Create on GitHub`

Nothing happens. Nada. Zilch.

#### **Log (best I could do with `log show`):**

[vscode-log.txt](https://github.com/user-attachments/files/17287841/vscode-log.txt)

#### **Screen recording:**

https://github.com/user-attachments/assets/2086de0f-d120-493b-ae84-13e52efe526c