sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Moving Area2D detects CharacterBody2d but CollisionShapes have not overlapped yet
Labels: bug,topic:physics,needs testing,topic:2d

### Tested versions

Reproducible in:
- v4.2.2.stable.official [15073afe3]
- v4.3.rc1.official [e343dbbcc]

### System information

Godot v4.2.2.stable - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3070 (NVIDIA; 32.0.15.6070) - AMD Ryzen 7 3700X 8-Core Processor (16 Threads)

### Issue description

When an Area2D node is moving it reports collisions with CharacterBody2D nodes that are in front of an area even though they have not overlapped yet. When turning on the visible collision shapes debug setting it is clearly visible that they are not overlapping. The same thing happens when an Area2D node is a child of another node that is moving.

### Steps to reproduce

Load the MRP, run the test scene. The blue squares are CharacterBody2D nodes and the red squares are Area2D nodes. All the nodes move with a constant speed. Note that the output shows that the CharacterBody2D nodes entered the Area2D nodes but this clearly has not happened.

### Minimal reproduction project (MRP)

[Area2DBug.zip](https://github.com/user-attachments/files/16420151/Area2DBug.zip)
Repository: transformers
Issue: Support for Segment Anything 2
Labels: New model

### Model description

The newer version of SAM, https://github.com/facebookresearch/segment-anything-2

### Open source status

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

### Provide useful links for the implementation

https://github.com/facebookresearch/segment-anything-2
Repository: godot
Issue: Invalid NodePath when binding signal argument
Labels: bug,topic:editor,needs testing

### Tested versions

v4.2.2.stable.official [15073afe3]

### System information

macOS 12.6.7

### Issue description

When connecting a signal from editor's UI with binding NodePath argument, it has a relative path from sender, which becomes incorrect once received by other object.
This behavior makes NodePath binding useless in most of cases, because scripts are always attached to receiver.


### Steps to reproduce

1. Open any scene, attach script to it
2. Write simple function, supposed to receive signal with path to sender as argument, for example
```gdscript
func _on_receive_signal(signal_sender: NodePath):
	var sender = get_node(signal_sender)
	assert(sender == $Button)
```
3. Create any child node, for example `Button`, select it
<img width="256" alt="Снимок экрана 2024-07-30 в 02 40 00" src="https://github.com/user-attachments/assets/e3f1fc6f-025d-4d43-adf5-a73c8ec6cefe">

4. Go to `Node` tab, right click on any signal, press `Connect...`
5. `Connect to Node` select root node, where script is attached
6. `Receiver Method` press `Pick`, disable `Compatible Methods Only`, select method from step 2
7. Enable `Advanced` switcher
8. `Add Extra Call Argument`, select `NodePath` from drop-down list, add it
9. Press `Assign...`, choose sender node, press `Connect`. Should be as on image below
<img width="704" alt="Снимок экрана 2024-07-30 в 02 24 18" src="https://github.com/user-attachments/assets/f3e3ea42-05d8-4ad5-a303-602891d9bb0b">

10. Run project and trigger signal


Expected result:
`_on_receive_signal` gets path to sender node


Actual result:
`_on_receive_signal` gets `.`, impossible to get sender node, assertion triggered from example code

### Minimal reproduction project (MRP)

[SignalNodePath.zip](https://github.com/user-attachments/files/16420370/SignalNodePath.zip)
Repository: vscode
Issue: search error
Labels: bug,search,confirmed

<!-- ⚠️⚠️ 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/No

<!-- 🪓 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. -->
This problem occurs on the vscode server. Here is the version information.

Version: 1.91.1
Commit: f1e16e1e6214d7c44d078b1f0607b2388f29d729
Date: 2024-07-09T22:08:03.155Z
Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36

**Question one.**

Steps to Reproduce:

1. Open https://vscode.dev/
2. Open any project
3. Open a file that is not in the current workspace
4. Open the search view and select Search only in  open Editors button
5. Search Keyword

Bug:
1. Select Search only in open Editors. No query result of other files, that is, the opened files are not queried.
2. Nothing Happens When the View as List and View as Tree Buttons Are Clicked

![search-1](https://github.com/user-attachments/assets/d05ef27b-3757-4533-9c1f-b426af9305d0)

**Question two.**

1. Open https://vscode.dev/
2. Open any project
3. Open a file that is not in the current workspace
4. Open the search view and select Search only in  open Editors button
5. The edit area opens only other files, that is, other files are opened, but the files in the current work area are not opened.
6. Search Keyword

Bug: 
No search result is displayed in the search box and an error is reported.

![search-2](https://github.com/user-attachments/assets/d4e8daa6-95e0-49a0-a87f-22c637c02d20)
Repository: node
Issue: `test-net-socket-connect-without-cb` test fails
Labels: net,test

### Version

v23.0.0-pre

### Platform

```text
Ubuntu 24.04 LTS

Linux sendol-Ubuntu 6.8.0-38-generic #38-Ubuntu SMP PREEMPT_DYNAMIC Fri Jun  7 15:25:01 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
```


### Subsystem

net

### What steps will reproduce the bug?

The code located in `./test/parallel/test-net-socket-connect-without-cb.js`
```js
'use strict';
const common = require('../common');

// This test ensures that socket.connect can be called without callback
// which is optional.

const net = require('net');

const server = net.createServer(common.mustCall(function(conn) {
  conn.end();
  server.close();
})).listen(0, common.mustCall(function() {
  const client = new net.Socket();

  client.on('connect', common.mustCall(function() {
    client.end();
  }));

  const address = server.address();
  if (!common.hasIPv6 && address.family === 'IPv6') {
    // Necessary to pass CI running inside containers.
    client.connect(address.port);
  } else {
    client.connect(address);
  }
}));
```

Command:
```
// you should build Node.js from source first
./out/Release/node ./test/parallel/test-net-socket-connect-without-cb.js
```

### How often does it reproduce? Is there a required condition?

Always, but your computer should be configured to allow usage of IPv6 and you shouldn't have `(IPv6 loopback address) localhost` pair in your hosts file.

### What is the expected behavior? Why is that the expected behavior?

Do not print anything and normally terminate.

### What do you see instead?

Following error
```
node:events:495
      throw er; // Unhandled 'error' event
      ^

Error: getaddrinfo ENOTFOUND localhost
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:107:26)
Emitted 'error' event on Socket instance at:
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  errno: -3007,
  code: 'ENOTFOUND',
  syscall: 'getaddrinfo',
  hostname: 'localhost'
}
```

### Additional information

I think this happens because `socket.connect(options[, connectListener])` uses `options.host` as the host the socket should connect to, while the return of `server.address()` has keys of `address`, `family`, and `port`. As `address.host` does not exist on the `client.connect(address);` in the test code, it seems that it tries to connect the default host `'localhost'`.
I'm not sure which one of test code and `net` module should be fixed, but I can try to fix this and make PR  if it is decided.
Repository: tauri
Issue: [bug] Broken positioning with multiwebview (unstable feature) example
Labels: type: bug,platform: Linux,status: needs triage,scope: unstable flag

### Describe the bug

Running the multiwebview example with `cargo run --example multiwebview --features unstable` spawns a GUI with the webviews rendered in a vertical stack instead of positioning each webview into each of the four corners:
![webviews-rendering-incorrectly](https://github.com/user-attachments/assets/86f692b0-d328-479a-8e84-f71040264943)


### Reproduction

1. Setup Tauri development environment and clone https://github.com/tauri-apps/tauri
2. Run the multiwebview example with `cargo run --example multiwebview --features unstable`
3. Observe that the four webviews are stacked vertically on-top of each other and not in the four corners as shown in #8280 

### Expected behavior

The four webviews should be rendered into each of the four corners of the window, like this:
<img width="912" alt="webviews-rendering-correctly" src="https://github.com/user-attachments/assets/85257ae8-e661-42da-98ea-9507429f325b">


### Full `tauri info` output

```text
WARNING: no lock files found, defaulting to npm

[✔] Environment
    - OS: Debian 12.0.0 X64
    ✔ webkit2gtk-4.1: 2.44.2
    ✔ rsvg2: 2.54.7
    ✔ rustc: 1.79.0 (129f3b996 2024-06-10)
    ✔ cargo: 1.79.0 (ffa9cf99a 2024-06-03)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: 1.79.0-x86_64-unknown-linux-gnu (environment override by RUSTUP_TOOLCHAIN)

[-] Packages
    - tauri [RUST]: 2.0.0-beta.23
    - tauri-build [RUST]: 2.0.0-beta.18
    - wry [RUST]: 0.41.0
    - tao [RUST]: 0.28.1
    - tauri-cli [RUST]: 2.0.0-beta.22
    - @tauri-apps/api : not installed!
    - @tauri-apps/cli [NPM]: 2.0.0-beta.22

[-] App
    - build-type: bundle
    - CSP: font-src https://fonts.gstatic.com; img-src 'self' asset: http://asset.localhost blob: data:; style-src 'unsafe-inline' 'self' https://fonts.googleapis.com; connect-src ipc: http://ipc.localhost; default-src 'self' customprotocol: asset:
    - frontendDist: ../dist
    - devUrl: http://localhost:1420/
```


### Stack trace

_No response_

### Additional context

I am running the example inside of a devcontainer, but I don't think that would be an issue here.

Operating System: Arch Linux 
KDE Plasma Version: 6.1.3
KDE Frameworks Version: 6.4.0
Qt Version: 6.7.2
Kernel Version: 6.10.1-arch1-1 (64-bit)
Graphics Platform: Wayland
Repository: deno
Issue: 🐛(WinOS) Unable to open 'CONIN$' or 'CONOUT$' for all versions >= 1.43.0
Labels: bug,windows

Version: Deno 1.43.0+

For versions of Deno >= 1.43.0, it's no longer possible to open the special files *CONIN$* or *CONOUT$*.

```shell
❯ deno --version
deno 1.43.1 (release, x86_64-pc-windows-msvc)
v8 12.4.254.12
typescript 5.4.3
❯ deno eval "const f = Deno.openSync('CONOUT$', {read: true, write:true}); console.log({f, isTTY: f.isTerminal()});"
error: Uncaught (in promise) NotFound: The system cannot find the file specified. (os error 2): open 'CONIN$'
...
```
Repository: godot
Issue: RichTextLabel StyleBox shadow is not fully displayed due to Clip Contents being enabled by default
Labels: bug,topic:rendering,confirmed,topic:gui,topic:2d

### Tested versions

Doesn't work in 4.2 or 4.3 rc

### System information

Windows 11

### Issue description

The RichTextLabel shadow gets cut off by its own size.

![Screenshot 2024-07-29 224328](https://github.com/user-attachments/assets/0c0df3de-0432-4609-93f7-069950a5956b)
![Screenshot 2024-07-29 224407](https://github.com/user-attachments/assets/be1840af-d90f-4110-9fe7-905d96c2cb23)



### Steps to reproduce

If you create a Rich Text label and then set a styleBoxFlat style to it, and then add a shadow and offset it, the shadow gets clipped by the textbox's bounds. This doesn't happen with labels or panels.

### Minimal reproduction project (MRP)

self, explanatory
Repository: ui
Issue: [bug]: Toggle button does not work well on mobile (and confusing on desktop)
Labels: bug

### Describe the bug

The Toggle button has the following background colors for the hover and on states:

- `hover:bg-muted`
- `data-[state=on]:bg-accent`

Unfortunately both these colors map to the same physical color (e.g. `neutral-100` in light mode and `neutral-800` in dark mode). This makes it very difficult to tell if the button is on or off in certain situations. The worst case is the Toggle button on a mobile which is in the off state, but still appears to be on. That's because on the mobile, the button stays in the hover mode even after it is tapped. The issue is less severe on the desktop where the confusion only occurs when you click the button and your cursor is still on it. In this case, even when the button is turned off, it shows the hover color giving the perception that it is on.

The screenshot below is for a outline button on mobile which is turned off, but still looks like it is on:

![IMG_2497](https://github.com/user-attachments/assets/e4d06ebc-0c36-4b01-b6ae-2b083180163d)

You can try this in the docs at https://ui.shadcn.com/docs/components/toggle#outline

### Affected component/components

Toggle, Toggle Group

### How to reproduce

1. Go to https://ui.shadcn.com/docs/components/toggle#outline on a mobile phone
2. Toggle the outline button on
3. Toggle the outline button off

The button appears as if it is on.

### Codesandbox/StackBlitz link

https://ui.shadcn.com/docs/components/toggle#outline

### Logs

_No response_

### System Info

```bash
MacOS / iOS
Chrome
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: flutter
Issue: The generated aar for native plugin in build/host/outputs/repo should have a correct version number.
Labels: platform-android,tool,a: build,team-tool

### Steps to reproduce

1. create a flutter project
2. add a plugin with native code, such as image_picker(It depens on image_picker_android)
3. build AAR for android with `flutter  build aar --build-number 2.0`
4. check the output assets located in `"${projectRoot}/build/host/outputs/repo/io/flutter/plugins/imagepicker/image_picker_android_release/"`. The generated version of aar will be "2.0"(same as `--build-number` specified).
5. check the version number of `image_picker_android` in `${projectRoot}/pubspec.lock`, It might be "0.8.12+1".
6. clean the workspace with `flutter clean`(this will not remove `pubspec.lock`)
7. re-build AAR for android with `flutter  build aar --build-number 3.0`
8. check the output assets again. The generated version of aar will be "3.0" this time.
9. check the version number of `image_picker_android` in `${projectRoot}/pubspec.lock`, It should still be "0.8.12+1".

### Expected results

The generated aar for image_picker_android in `"${projectRoot}/build/host/outputs/repo/io/flutter/plugins/imagepicker/image_picker_android_release/"` should retain it's version number when I rebuild aar without changeing it's version.


### Actual results

It always has the same version of `--build-number`, even though I didn't change the version number of image_picker in pubspec.yaml.

### Code sample

<details open><summary>Code sample for pubspec.yaml</summary>

```yaml
version: 1.0.0+1

environment:
  sdk: ^3.6.0-91.0.dev

dependencies:
  flutter:
    sdk: flutter
  image_picker: 1.0.0

dev_dependencies:
  flutter_lints: ^4.0.0

flutter:
  module:
    androidX: true
    androidPackage: com.example.flutter_project
    iosBundleIdentifier: com.example.flutterProject
```

</details>


### Screenshots or Video

_No response_

### Logs

_No response_

### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
[✓] Flutter (Channel master, 3.24.0-1.0.pre.349, on macOS 14.5 23F79 darwin-x64, locale zh-Hans-CN)
[✓] Android toolchain - develop for Android devices (Android SDK version 35.0.0)
[!] Xcode - develop for iOS and macOS (Xcode 15.4)
    ✗ Unable to get list of installed Simulator runtimes.
[✓] Chrome - develop for the web
[✓] Android Studio (version 2024.1)
[✓] Connected device (3 available)
[✓] Network resources

```

</details>
Repository: tauri
Issue: [bug] [v2] `skipTaskbar` not working on Windows
Labels: type: bug,platform: Windows,status: needs triage

### Describe the bug

`skipTaskbar` doesn't seem to be removing the window from the taskbar on Windows. 

### Reproduction

Reproducible via the default v2 boilerplate (i.e. `pnpm create tauri-app --beta`) and setting `"skipTaskbar": true` in the `tauri.conf.json`. The same occurs when instead using `skip_taskbar(true)` via the `Builder` options in Rust and `skipTaskbar` in the JS window APIs.

![skiptaskbar](https://github.com/user-attachments/assets/c81ef614-ec89-4eab-8815-901a616e35dd)

### Expected behavior

For the window to not appear in the taskbar

### Full `tauri info` output

```text
[✔] Environment
    - OS: Windows 10.0.19045 X64
    ✔ WebView2: 126.0.2592.113
    ✔ MSVC: Visual Studio Community 2022
    ✔ rustc: 1.76.0-nightly (5ac4c8a63 2023-12-20)
    ✔ cargo: 1.76.0-nightly (1a2666ddd 2023-12-17)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: nightly-x86_64-pc-windows-msvc (default)
    - node: 20.11.0
    - pnpm: 9.4.0
    - yarn: 1.22.19
    - npm: 8.17.0

[-] Packages
    - tauri [RUST]: 2.0.0-beta.24
    - tauri-build [RUST]: 2.0.0-beta.19
    - wry [RUST]: 0.41.0
    - tao [RUST]: 0.28.1
    - @tauri-apps/api [NPM]: 2.0.0-beta.15
    - @tauri-apps/cli [NPM]: 2.0.0-beta.22

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:1420/
    - framework: SolidJS
    - bundler: Vite
```


### Stack trace

_No response_

### Additional context

Also tried removing the `WS_EX_APPWINDOW` style and adding `WS_EX_TOOLWINDOW`, but no luck so far 🙃 

```rust
  #[cfg(target_os = "windows")]
  unsafe {
    use windows::Win32::UI::WindowsAndMessaging::*;
    let handle = window.hwnd().unwrap();
    let mut style = GetWindowLongPtrA(handle, GWL_EXSTYLE);
    style |= WS_EX_TOOLWINDOW.0 as isize;
    style &= WS_EX_APPWINDOW.0 as isize;
    SetWindowLongPtrA(handle, GWL_EXSTYLE, style);
  };
```
Repository: electron
Issue: [Feature Request]: Support multiple preload scripts
Labels: enhancement :sparkles:

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a feature request that matches the one I want to file, without success.

### Problem Description

I want to separate my business logic from the main application by moving it to separate packages. To facilitate the reusability of these packages in other applications, I would also provide packages that handle IPC setup (register listeners, expose methods in the frontend, etc.). Each of these packages would contain a preload script, and with no way to execute multiple preload scripts, this is not possible.

### Proposed Solution

`Electron.WebPreferences.preload` could accept array of strings, where each string would be a path to a preload script.

### Alternatives Considered

Polyfilled `require` in preload script could support importing local JavaScript files. This way, it would be possible to have one preload script which imports all other necessary scripts.

### Additional Information

_No response_
Repository: godot
Issue: GPUParticles3D - changing the mesh from a non-trail-mesh to a trail-mesh makes particles disappear
Labels: bug,topic:rendering,topic:3d,topic:particles

### Tested versions

v4.2.2.stable.mono.official [15073afe3]

### System information

Godot v4.2.2.stable.mono - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4080 (NVIDIA; 32.0.15.5599) - AMD Ryzen 9 7950X3D 16-Core Processor (32 Threads)

### Issue description

For a GPUParticles3D if you have trails enabled and change the mesh in a draw pass from a non-trail mesh (e.g. Sphere) to a trail mesh, the particles stop rendering. To fix this you need to either change the trail length or disable and re-enable trails. This can be very confusing for someone new to particle systems as the particle system seems to suddenly stop working.


https://github.com/user-attachments/assets/3ab9711e-b9c4-4d29-965d-99c038924cc2



### Steps to reproduce

- Create a simple GPUParticles3D, set up some spawning pattern (I used ring, but it doesn't really matter).
- Set a sphere as the only draw pass.
- Enable trails
- Change the sphere to some trail mesh

The particles now disappear but instead the particle system should render using the new trail mesh.

### Minimal reproduction project (MRP)

N/A
Repository: storybook
Issue: [Bug]: tsconfig.json in my project is not used when parsing storybook configuration file (v7)
Labels: bug,needs triage

### Describe the bug

It seems that `tsconfig.json` in my project is not used when parsing configuration file (e.g. `.config/main.ts`), instead, storybook is using its own one and causing unexpected behavior.

For example, in my project, `allowSyntheticDefaultImports` is set to false so that `import * as cssnano from 'cssnano';` gives `cssnano` as a function. While in storybook, `cssnano` becomes a object and `cssnano.default` becomes the function that's expected.

### Reproduction link

https://github.com/fa93hws/storybook-allowSyntheticDefaultImports-reproduce

### Reproduction steps

1. Maybe take a look at the README (optional)
2. Run `pnpm storybook`, and it failed.
3. Run `yarn ts-node .storybook/main.ts`, and it's fine.
4. Maybe take a look at the `console.log` output from step 2 and 3.

### System

```bash
Storybook Environment Info:

  System:
    OS: macOS 14.5
    CPU: (10) arm64 Apple M1 Max
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.12.2 - /opt/homebrew/bin/node
    Yarn: 1.22.22 - /opt/homebrew/bin/yarn <----- active
    npm: 10.5.0 - /opt/homebrew/bin/npm
    pnpm: 8.15.5 - ~/Library/pnpm/pnpm
  Browsers:
    Chrome: 127.0.6533.73
    Safari: 17.5
  npmPackages:
    @storybook/addon-essentials: ^7.6.20 => 7.6.20 
    @storybook/addon-interactions: ^7.6.20 => 7.6.20 
    @storybook/addon-links: ^7.6.20 => 7.6.20 
    @storybook/addon-onboarding: ^1.0.11 => 1.0.11 
    @storybook/blocks: ^7.6.20 => 7.6.20 
    @storybook/react: ^7.6.20 => 7.6.20 
    @storybook/react-webpack5: ^7.6.20 => 7.6.20 
    @storybook/test: ^7.6.20 => 7.6.20 
    storybook: ^7.6.20 => 7.6.20
```


### Additional context

_No response_