sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Using CapsuleShape2D in CollisionShape2D cancels out the collision area when baking NavigationRegion2D
Labels: bug,topic:navigation,topic:2d

### Tested versions

Reproducible - v4.3.stable.official [77dcf97d8]

### System information

Godot v4.3.stable - Windows 10.0.19045 - Vulkan (Mobile) - dedicated NVIDIA GeForce GTX 1070 (NVIDIA; 32.0.15.6094) - AMD Ryzen 7 3700X 8-Core Processor (16 Threads)

### Issue description

When baking NavigationPolygon, if a CapsuleShape2D is either completely or partially overlapped with a collision area, the overlapping part of the CapsuleShape2D will cancel out the collision area and become part of the navigation polygon. The issue is only happening with CapsuleShape2D, not other shapes. 

![Screenshot 2024-10-31 230124](https://github.com/user-attachments/assets/0f700b41-5012-4fe2-b395-a5b3b12dd2bf)


### Steps to reproduce

1. Create a NavigationRegion2D 
2. Under the NavigationRegion2D, create a StaticBody2D with a child CollisionPolygon2D, draw the collision polygon
3. Under the NavigationRegion2D, create another StaticBody2D with a child CollisionShape2D, use CapsuleShape2D as its shape
4. Make the 2 StaticBody2D overlaps
5. Bake NavigationPolygon on NavigationRegion2D
6. Observe that the overlapping part is recognized as a navigation polygon instead of a collision area

### Minimal reproduction project (MRP)

[test-project.zip](https://github.com/user-attachments/files/17596571/test-project.zip)
Repository: deno
Issue: Resize event on stdout not invoked in TTY on macOS
Labels: bug,node compat

Version: Deno 2.0.4
macOS: 14.2.1

# Repro steps

1. `deno` in Alacritty
2. `process.stdout.on('resize', () => { console.log(`${process.stdout.columns}x${process.stdout.rows}`) })`
3. Resize Alacritty window

# Expected

Printed console output with the process columns and rows.

# Actual

Nothing happens.

# Additionally

If you run the same `process.stdout.on('resize', () => { console.log(`${process.stdout.columns}x${process.stdout.rows}`) })` in `node` (I'm using v20), then you'll see the expected results.

Also, I've tested in Warp and Terminal TTY apps as well and got the same bug.
Repository: vscode
Issue: Intellisense text can't be worked when I installed Snippet feature and I created the script of Snippet
Labels: info-needed

<!-- ⚠️⚠️ 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. -->
- VS Code Version: 
- OS Version: 

Steps to Reproduce:

1. Installed Snippet feature on VS Code
2. Created new snippet
3. Intellisense Text doesn't work when I enter the words
Repository: transformers
Issue: Compile Grounding DINO
Labels: Feature request,Vision,Compilation,Multimodal

### Feature request

I found that the Gounding DINO model `IDEA-Research/grounding-dino-base` cann't be compiled.
When I use `torch.comple(<The model>)`, it raises many error, such as `TypeError: unhashable type: 'dict'`.
can this be implemented?

### Motivation

It's very slow for Grounding DINO to perform batch inference, so I want some way to speed it up.

### Your contribution

Not sure.
Repository: vscode
Issue: Webview: throttling of `setTimeout` and `setInterval`
Labels: upstream,webview,chromium

<!-- ⚠️⚠️ 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.95.1 (Universal), Commit: 65edc4939843c90c34d61f4ce11704f09d3e5cb6
- OS Version: Darwin arm64 24.1.0

We make heavy use of Webviews via the VS Code API. We have observed that `setTimeout` and `setInterval` calls are throttled. When the time is less than 1000ms, the time will be overridden to 1000ms as a minimum.

We can reproduce the problem on both MacOS and Windows.

We found that the problem is much harder (and sometimes impossible) to reproduce when display refresh rate is higher. With a refresh rate of 60hz, the problem is fairly easy to reproduce.

We have created a sample repo that shows the problem.

Steps to Reproduce:

1. Download the sample repo to reproduce from https://github.com/wallabyjs/webview-issue
2. Open this example in VS Code 1.47+
3. Run `npm install`
4. Run `npm run watch` or `npm run compile`
5. `F5` to start debugging
6. Run the `Webview Issue: Reproduce Webview Issue` command to create the webview.
7. Note the time displayed in the webview:

```
Expected time to update: 500ms
Actual time to update: 500ms
```

The two times should be similar.

8. If you do not have the issue, close and re-open the webview multiple times. Eventually, the actual time will update at ~1000ms instead of 500ms.

_Note: it can sometimes take a few times before the throttling starts to occur._
Repository: vscode
Issue: Toggling views/panels has inconsistent focus behaviour
Labels: bug,ux,layout

While investigating https://github.com/microsoft/vscode/issues/198293 I noticed that our action to toggle visibility of primary or secondary side bar or panel has inconsistent behaviour when it comes to passing focus to the view that becomes visible or not.

Notice when the explorer is active how focus remains in the editor:

![Image](https://github.com/user-attachments/assets/a18f64dd-6d9c-4def-b62d-26ad32d14810)

And now with the SCM view:

![Image](https://github.com/user-attachments/assets/de572695-04b1-4333-ae7c-cc2e06325caa)

First of all, these actions seem to call into methods to toggle visibility of the container via layout service which eventually calls into `openPaneComposite`, e.g. for the primary sidebar:

https://github.com/microsoft/vscode/blob/4520d915c98954dc96dd0bc00b8bb68181cbf2b6/src/vs/workbench/browser/layout.ts#L1750

The last parameter is a `true` to indicate that focus should move to that pane.

However, at the point where we want to focus the pane, it is not yet visible because the grid only updates a few lines below:

https://github.com/microsoft/vscode/blob/4520d915c98954dc96dd0bc00b8bb68181cbf2b6/src/vs/workbench/browser/layout.ts#L1756

Any view that implements `focus` by e.g. focussing the list will be a no-op because the DOM nodes are not yet visible. The SCM view is probably a bit async and that is why it works by chance.

I am actually not sure how to address this: people might have gotten used to the fact that these commands typically preserve focus for most of our views. I still think that the implementation is currently buggy around focussing the pane when the container becomes visible, so maybe a fix would need to be:
* handle focus properly after the container in the grid is visible
* make focus more explicit so that the toggling actions can explicitly pass in `focus: false` to preserve todays behaviour

//cc @sbatten
Repository: next.js
Issue: Turbopack: failed to load chunk error
Labels: bug,Lazy Loading,Turbopack

### Link to the code that reproduces this issue

https://github.com/moonlitgrace/next-turbopack-issue-repro

### To Reproduce

1. run dev server with `--turbopack`
2. open console (make sure you've checked 'Persists logs')
3. refresh browser multiple times

### Current vs. Expected behavior

When refresh many times, error boundary shows and hides, when we check browser console, get this error:

```console
13:48:32.648 Uncaught (in promise) Error: Failed to load chunk static/chunks/[turbopack]_browser_dev_hmr-client_d6d8d4._.js from module [turbopack]/browser/dev/hmr-client/hmr-client.ts [app-client] (ecmascript, async loader)
    NextJS 51
undefined:472:15
```

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Tue, 22 Oct 2024 18:31:38 +0000
  Available memory (MB): 7849
  Available CPU cores: 4
Binaries:
  Node: 23.1.0
  npm: 10.9.0
  Yarn: N/A
  pnpm: 9.12.3
Relevant Packages:
  next: 15.0.2 // Latest available version is detected (15.0.2).
  eslint-config-next: 15.0.2
  react: 19.0.0-rc-02c0e824-20241028
  react-dom: 19.0.0-rc-02c0e824-20241028
  typescript: 5.6.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Lazy Loading, Turbopack

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

running dev server without `--turbopack` flag works fine as wine.
Repository: electron
Issue: desktopCapturer.getSources returns empty thumbnail in some window
Labels: platform/macOS,bug :beetle:,has-repro-gist,33-x-y,34-x-y

### 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 bug report that matches the one I want to file, without success.

### Electron Version

33.0.2

### What operating system(s) are you using?

macOS

### Operating System Version

macOS

### What arch are you using?

arm64 (including Apple Silicon)

### Last Known Working Electron version

26.6.10

### Expected Behavior

every window return its own thumbnail

### Actual Behavior

some windows return its own thunbnail, others only return base64 prefix 'data:image/png;base64,'

### Testcase Gist URL

https://gist.github.com/8eb6ea5620a0b2a271ff456f8933ac12

### Additional Information

_No response_
Repository: vscode
Issue: Layout Controls: move them to respective corners
Labels: feature-request,layout,workbench-auxsidebar

An idea from @sbatten to split up our layout controls into respective controls per corner:

![Image](https://github.com/user-attachments/assets/c32b4571-d55d-4555-ab17-8c06a4222693)

I.e. have them appear at the corners where the view or panel is.

Probably drop the layout picker button.
Repository: vscode
Issue: Auto-Fill of Highlighted Text in Go-to-File (CTRL + P) Search
Labels: help wanted,feature-request,search

<!-- ⚠️⚠️ 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. -->
Currently, when text is highlighted and CTRL + F is pressed, the search menu opens with the highlighted text automatically filled as the search term. I would like this functionality extended to the Go menu, so that when I highlight text in a file and press CTRL + P, it automatically searches for files with the selected text as the filename.
Repository: ui
Issue: [bug]: Charts not working in next-15
Labels: bug

### Describe the bug

I've tried to used shadcn provided charts in the same way as in version 14 but it doesn't work. The chart is not visible in the browser, same code works in next-14 but not in next-15. The console says:
Hydration failed because the server rendered HTML didn't match the client. As a result this tree will be regenerated on the client. This can happen if a SSR-ed Client Component used

here is the example of the what the chart renders like:
![image](https://github.com/user-attachments/assets/fccaef0f-aff7-4620-9a51-3dbe0f765667)


### Affected component/components

component/chart

### How to reproduce

1. go to sandbox with the following url
2. run `npm run dev` or start dev server
3. then check the dev environment in the browser

### Codesandbox/StackBlitz link

https://codesandbox.io/p/devbox/ntv547

### Logs

```bash
Hydration failed because the server rendered HTML didn't match the client. As a result this tree will be regenerated on the client. This can happen if a SSR-ed Client Component used
See more info here: https://nextjs.org/docs/messages/react-hydration-error

- A server/client branch `if (typeof window !== 'undefined')`.
- Variable input such as `Date.now()` or `Math.random()` which changes each time it's called.
- Date formatting in a user's locale which doesn't match the server.
- External changing data without sending a snapshot of it along with the HTML.
- Invalid HTML tag nesting.

It can also happen if the client has a browser extension installed which messes with the HTML before React loaded.
```


### System Info

```bash
All browsers produce this error
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: vscode
Issue: Drag and drop from operating system doesn't work (Ubuntu 24)
Labels: electron,workbench-dnd

<!-- ⚠️⚠️ 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: 1.95.1
- OS Version: Ubuntu 24.04

Steps to Reproduce:

I am using stock VS Code, freshly installed, from the debian file on the official website. When I drag and drop a file from my file manager (I'm using Nemo), it doesn't open in VSCode. If a file is open already, it pastes the new file in as a link.

https://github.com/user-attachments/assets/32fb4b09-3681-4056-b9e4-4c5c0f63637a

As you can see in this video, the behavior is actually a bit random - the functionality works as expected maybe 10% of the time.

I couldn't reproduce it in the video, but I've noticed if I drag a file into the tab area above the open editor panes in VS Code, often the file will open but with a bad filename, with a bunch of numbers after it:

![Image](https://github.com/user-attachments/assets/ae22045f-d92a-4777-81db-053167b36cfa)
Repository: neovim
Issue: snippet can't stop at $0 section
Labels: bug,snippet

### Problem

After accept a lsp snippet like `namespace` in c++, press `<tab>` jump to section `$0` in there is newline. and press `<tab>` again it jump to section `$1` instead insert a indent. 

### Steps to reproduce

`nvim --clean -u test.lua test.cc`

```lua
vim.g.loaded_matchparen = 1

vim.api.nvim_create_autocmd("FileType", {
        pattern = 'cpp',
	callback = function()
		local id = vim.lsp.start({
			cmd = { "clangd" },
			root_dir = vim.uv.cwd(),
		})
		vim.lsp.completion.enable(true, id, 0, { autotrigger = false })

		vim.keymap.set("i", "<C-j>", function()
			vim.lsp.completion.trigger()
		end)
	end,
})
```

1. type `namespace` then `<C-J>`
2. select namespace snippet and accept by `<C-y>`
3. type something for namespace name and then press `<tab> <tab>` cursor back to $1 name section

commented  this line `vim.g.loaded_matchparen = 1` will works fine.

![Image](https://github.com/user-attachments/assets/398f6aa8-33d6-44a0-a018-ac4877a81b58)


### Expected behavior

`tab` should insertion a indent instead jump to next snippet section.

### Nvim version (nvim -v)

v0.11.0-dev-1075+gb34e137e4

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

no

### Operating system/version

macos

### Terminal name/version

alacritty

### $TERM environment variable

alacritty

### Installation

build frome source
Repository: node
Issue: [v18] `source` value is ignored from the loader's `load` function with `format: 'commonjs'`
Labels: loaders,v18.x

> [!NOTE]
> This issue is limited to v18. Works fine on v20.

### Version

Confirmed: v18.19.0, v18.20.3

### Platform

```text
Darwin pro-m3-2023-36gb.local 24.0.0 Darwin Kernel Version 24.0.0: Tue Sep 24 23:37:25 PDT 2024; root:xnu-11215.1.12~1/RELEASE_ARM64_T6030 arm64

`source` value from the loader's `load` function with `format: 'commonjs'` is ignored in v18.
```

### Subsystem

_No response_

### What steps will reproduce the bug?

Repro: https://github.com/devjiwonchoi/repro-nodejs-loader-cjs-source

The Node.js loader hook function `load` can return properties: `format` and `source`. When running on Node.js v18 with `format` set to `commonjs`, the `source` property is ignored and does not affect the loaded module.

```js
// index.js
console.log('hello from index.js');

// loader.mjs
export async function load() {
  return {
    format: 'commonjs',
    shortCircuit: true,
    source: `console.log("hello from loader.mjs");`,
  }
}

// optional: register.js
const { register } = require('node:module')
const { pathToFileURL } = require('node:url')

register('./loader.mjs', pathToFileURL(__filename))
```

#### Run with `--import ./register.js`

```
node --import ./register.js ./index.js
```

#### Run with `--loader ./loader.mjs`

```
node --loader ./loader.mjs ./index.js
```

### How often does it reproduce? Is there a required condition?

This issue is present on Node.js v18. Works fine on v20. (v19 doesn't support `module.register` API.)

### What is the expected behavior? Why is that the expected behavior?

The stdout must be:

```
{ format: 'module' }
hello from loader.mjs
```

### What do you see instead?

The source is from the `index.js`, not modified from the loader.

```
{ format: 'commonjs' }
hello from index.js
```

### Additional information

_No response_
Repository: opencv
Issue: Drivers for USB3 Vision and GigE Vision
Labels: feature,category: videoio(camera)

### Describe the feature and motivation

OpenCV needs generic standards-compliant drivers for "GigE Vision" and "USB3 Vision" compliant cameras.

GigE Vision and USB3 Vision are industry standards. OpenCV does not appear to have drivers for these, which excludes the use of a lot of very capable industrial cameras.

### Additional context

Occasionally people would like to use their expensive industrial cameras with OpenCV. They always run into the problem that these cameras aren't just simple USB Unified Video Class (UVC) devices, so they aren't exposed to system media APIs (V4L2, DSHOW, MSMF, ...), and OpenCV doesn't know how to talk to these.

OpenCV has, or has had, drivers for "Ximea" and "genicam/GenTL". I think it'd be a good idea to investigate if those `videoio` backends could be extended, or they're just binary libraries or license-encumbered.
Repository: deno
Issue: Slow types warning for a non-public API when publishing
Labels: needs investigation,publish

Version: Deno 2.0.3

I am using [zod](https://www.npmjs.com/package/zod) for validations. Zod relies a lot on the type inference feature of typescript which is why I can do something as shown below:

```ts
import { z } from "zod";

export const roles = ["admin", "manager", "user"] as const;

export const Role = z.enum(roles);

export type Role = z.infer<typeof Role>;
```

Now, deno gets upset when I try to publish the above to jsr because of slow-types. 

```
  |
5 | export const Role = z.enum(roles);
  |              ^^^^ this symbol is missing an explicit type
  |
  = hint: add an explicit type annotation to the symbol
```

To fix this issue, I replaced all references to the Zod instance from public API with my custom types that don't rely on type inference.

```diff
import { z } from "zod";

export const roles = ["admin", "manager", "user"] as const;

- export const Role = z.enum(roles);
+ const Role = z.enum(roles);

- export type Role = z.infer<typeof Role>;
+ export type Role = (typeof roles)[number];

+ export function isValidRole(role: unknown): [true] | [false, string[]] {
+   const res = Role.safeParse(role);
+   if (res.success) {
+     return [true];
+   }
+   return [false, res.error.errors.map((e) => e.message)];
+ }
```

However, when I try to publish the above code, I still see the following error:

```
  |
5 | const Role = z.enum(roles);
  |       ^^^^ this symbol is missing an explicit type
  |
  = hint: add an explicit type annotation to the symbol
```

I suspected that this could be happening because of the name collision of `Role` object and `Role` type. So, I renamed the `Role` object to `ZodRole` and now I am able to publish.

```diff
import { z } from "zod";

export const roles = ["admin", "manager", "user"] as const;

- const Role = z.enum(roles);
+ const ZodRole = z.enum(roles);

export type Role = (typeof roles)[number];

export function isValidRole(role: unknown): [true] | [false, string[]] {
-   const res = Role.safeParse(role);
+   const res = ZodRole.safeParse(role);
    if (res.success) {
        return [true];
    }
    return [false, res.error.errors.map((e) => e.message)];
}
```

Would it be possible for Deno to be able to differentiate between a type name and object name while publishing to avoid the mis-leading public API slow-types warning?
Repository: godot
Issue: "Toggle Animation Skeleton Visibility" enabled/disabled icons appear to be inverted
Labels: bug,topic:editor,topic:import,topic:3d

### Tested versions

Godot v4.4.dev (c6c464cf9)

### System information

Godot v4.4.dev (c6c464cf9) - Windows 10.0.22631 - Multi-window, 1 monitor - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4070 Laptop GPU (NVIDIA; 31.0.15.4683) - AMD Ryzen 7 7840HS w/ Radeon 780M Graphics (16 threads)

### Issue description

"Toggle Animation Skeleton Visibility" enabled/disabled icons appear to be inverted. It is colored when disabled and grey when enabled. When you compare it with the light icons, they are grey when disabled and while when enabled.

https://github.com/user-attachments/assets/68b1921f-9093-42fc-b490-4c82e2afc3e6

### Steps to reproduce

Open the import view for a gltf file with a skeleton animation included.

### Minimal reproduction project (MRP)

[toggle_skeleton_button_issue.zip](https://github.com/user-attachments/files/17599341/toggle_skeleton_button_issue.zip)