sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: VS Code continuously crashes on Windows 11 for more than month
Labels: under-discussion

<!-- ⚠️⚠️ 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: 1.94.2 and above (previous versions are also affected, but not quite certain which exactly)
- OS Version: Windows 11 Enterprise v. 24H2, build 26100.2033

Steps to Reproduce:

1. Run VS Code, work with it
2. Put your machine to the sleep mode or hibernation, then wake it up
3. [Optionally] Try to search something across the folders:
    - You will see ENOENT error when trying to spawn search process
4. Close VS Code and try to open it again
    - Observe error message:
     ![Image](https://github.com/user-attachments/assets/a8be1f06-66d9-4b1b-af4e-8549bb517760)
    - Observe unstopped VS Code processes:
    ![Image](https://github.com/user-attachments/assets/c17dbfd9-e2b1-48b9-a1ff-a5f2f1a39339)
5. Computer restart doesn't help
6. The only workaround is to uninstall VS Code and reinstall it again
    - Executing `unins000.exe` doesn't uninstall VS Code folder completely after incident occurred - You need to double-check for running processes in task manager, kill them and remove the rest of files manually
8. **Repro is not stable**: It might appear once-twice per week - Update of VS Code doesn't seem to be related
    - Update of OS doesn't seem to be related
Repository: ui
Issue: [bug]: MenuBar inside ContextMenu close issue
Labels: bug

### Describe the bug

When I use a context menu within the menu bar, when the context menu closes, the menu bar content also closes, or when I open the context menu again, the menubar content closes again.

Actually, there is no problem in its operation, but when I click outside, only the context menu should close.

### Affected component/components

ContextMenu

### How to reproduce

When I use a context menu within the menu bar, when the context menu closes, the menu bar content also closes, or when I open the context menu again, the menubar content closes again.
```jsx
<Menubar>
 <MenubarTrigger>Menu</MenubarTrigger>
 <MenubarContent>
  <ContextMenu>
   <ContextMenuTrigger asChild>
    <MenubarItem>Menu Item</MenubarItem>
   </ContextMenuTrigget/>
   <ContextMenuContent>
   </ContextMenuContent>
  </ContextMenu>
 </MenubarContent>
</Menubar>
```

Actually, there is no problem in its operation, but when I click outside, only the context menu should close.

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
shadcn@2.1.3
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: godot
Issue: `.app` files can't be deleted from the browse files window
Labels: discussion,topic:editor

### Tested versions

4.3.stable

### System information

Godot v4.3.stable - macOS 15.0.1 - Vulkan (Mobile) - integrated Apple M3 Max - Apple M3 Max (14 Threads)

### Issue description

Whether you consider this bug report an issue at all depends on your answer to this question: is a file with the `.app` extension a file or a folder? 

One could argue: both. It's a package that Finder usually considers to be a single file, unless you right click on the `.app` file and choose Show Package Contents, after which you open the file as a folder.

This is perhaps a funny edge case, but I am of the opinion that the browser should be able to delete the `.app` file, hence why I'm issuing a bug report on it. I specifically right-mouse-clicked on it to delete it, so why shouldn't it work?


https://github.com/user-attachments/assets/bc65681d-95a3-43f9-af3e-22bc2757f441



### Steps to reproduce

Try to remove an `.app` file from the browse file window in Godot. It won't work.

### Minimal reproduction project (MRP)

n/a
Repository: react
Issue: [Compiler Bug]: 
Labels: Type: Bug,Status: Unconfirmed,Component: Optimizing Compiler

### What kind of issue is this?

- [X] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhASwLYAcIwC4AEwBUYCAsghhADQlkBKCAZnaQgMICGANjwEZc4AawIBfAsxgQMBADogYCIXgUBuOQDtMOfEQJ4AFtLx4eCcZOmyFPCABMuYQ+q1aEAD12F7LLlB5CZihNODw0CE0CcgBPAEEsLAAKAEoiLQICOEiwQiVmAgBeegQmZlSNKIysnMIjEzMEewAxCDhSIpLKaiTqzNSigD4+zINjCFNzXqjR2YHCwYJ8gDp2mCVNPAB+ZeY20lSaEdmAVgAGM6OZ2czgY5vzLns0TQBzZEleMiubm7wYLhoHgvd4GGBQBA-X7iKGzFKwggAbT27TAAF0oSlKtV2ABRZjMBBhJLzRbAeoTRotfZgVJiOiIimTJqtVFolJuGZKPCwKIAHmeADclixCsB8mJBgAJBB8CAEADquB49j5AHohYNKmItCAxEA

### Repro steps

The compiler assumes that `ref.current` is called during render when inside of `useMemo()`, even when `useMemo` is returning a callback that is only called in a `useEffect` and never during render. See playground for the code.

The most common use case for specifying a callback with `useMemo` instead of `useCallback`, is when the callback is wrapped in a debouncing technique, like `lodash/throttle`:

```tsx
  const throttledFocus = useMemo(
    () =>
      throttle(
        () => ref.current?.focus(),
        500,
        {
          leading: false,
          trailing: true,
        },
      ),
    [focus],
  );
```
It's as if the compiler isn't differentiating the closure that returns the memoized value (and thus is indeed firing during render), and `useMemo` returning a callback 🤔 

### How often does this bug happen?

Every time

### What version of React are you using?

^18.3.1

### What version of React Compiler are you using?

19.0.0-beta-6fc168f-20241025
Repository: angular
Issue: tutorial offers solutions but not answers
Labels: area: docs

### Which @angular/* package(s) are relevant/related to the feature request?

_No response_

### Description

![Image](https://github.com/user-attachments/assets/0e30b606-c6bc-4d82-8dce-ccf7577da314)
I am keen to learn something practical and plodding into the tutorials for angular.dev, early on. I notice that the answers are in the tutorials which is maybe helpful due to syntax, but this time I decide to look at the answer as well despite solving and the answer is correct in the output but not possible in the code of the supposed solution. Am I looking at an issue or that the learning is not useful or supported I wonder now.

### Proposed solution

The lessons are helpful so being all up to date and accurate is a good fix, ie just repair.

### Alternatives considered

It cannot be left innacurate, it shows the code is not balanced.
Repository: godot
Issue: [macOS] Export to Windows doesn't start unless I click on the Wine app
Labels: bug,platform:windows,platform:macos,topic:export

### Tested versions

4.3.stable

### System information

Godot v4.3.stable - macOS 15.0.1 - Vulkan (Mobile) - integrated Apple M3 Max - Apple M3 Max (14 Threads)

### Issue description

https://github.com/user-attachments/assets/f0b4b566-b330-4581-8987-950dfab62217

### Steps to reproduce

Export to Windows on macOS.

### Minimal reproduction project (MRP)

n/a
Repository: deno
Issue: deno.land & jsr.io "403 Forbidden" and "os error 104"
Labels: bug,needs investigation,jsr

Version: Deno 2.0.4

Recently I've been trying to deploy a Fresh project on my own infrastructure which I setup in Hetzner Cloud. Currently I am facing an issue when installing dependencies from `deno.land` and `jsr.io`.

The initial issue that I faced was identical to the one described in this issue: https://github.com/denoland/deno/issues/23530. That being an issue with IPV6. However after disabling IPV6 on both of my VPS, the same issues persist:

### deno.land
```
error: client error (Connect): Connection reset by peer (os error 104)
```
and
```
error: Import 'https://deno.land/x/fresh@1.7.3/dev.ts' failed: error sending request for url (https://deno.land/x/fresh@1.7.3/dev.ts): client error (Connect): tls handshake eof` when installing dependencies from `deno.land
```


### jsr.io
```
JSR package manifest for '@luca/esbuild-deno-loader' failed to load. Import 'https://jsr.io/@luca/esbuild-deno-loader/meta.json' failed: 403 Forbidden
```

Interestingly if I try to manually `curl` these packages from the VPS there is no issue (for example: `curl https://deno.land/x/fresh@1.7.3/dev.ts`).

I've emailed support@deno.com with the IP addresses of the machines that are failing, but haven't heard back in a few days.

For now I will say that I have worked around the issue by changing the imports to deno.land dependencies to use the `raw.githubusercontent.com` urls:

```json
"imports": {
  "$fresh/": "https://raw.githubusercontent.com/denoland/fresh/1.7.3/"
}
```

But this feels less than ideal. Any help with this would be greatly appreciated. Thank you!
Repository: deno
Issue: Deno task cannot run a script when it contains "~"
Labels: bug,task runner

Version: Deno 2.0.4

I have the following script in `package.json`, where when I run `deno task sync`, `deno` returns an error (see below): Am I doing something wrong?

**Script:**
```
"scripts": {
    "sync": "watch rsync -av --delete ./build/ server-dns:~/dir/build/"
},
```

**Error:**
```
error: Error parsing script 'sync:wildnis'.

Caused by:
    Unexpected character.
      ~/dir/build/
      ~
```
Repository: terminal
Issue: Enhance pane context menu
Labels: Issue-Feature,Area-UserInterface,Product-Terminal

### Description of the new feature

Add split pane up/down/left/right context menus as submenu.
Add split pane with profile up/down/left/right context menus as submenu.
Add swap panes up/down/left/right context menus as submenu.
Add toggle pane zoom context menu.
Add close other panes context menu.

The motivation is that Windows users are more accustomed to working with GUI Menus using a mouse, unlike Linux users.

- Relevant PR: (#18126)

### Proposed technical implementation details

Implemented it - PR (#18126)
Repository: react
Issue: Bug: Incorrect Checkbox Toggle on Mobile Devices
Labels: Status: Unconfirmed

### Issue: Incorrect Checkbox Toggle on Mobile Devices


---

**Summary**  
I noticed this bug in lists containing two or more checkboxes, tapping on a checkbox sometimes toggles a different one. This issue appears to be isolated to mobile and touch-based devices.

**Observed Behavior**  
When interacting with checkboxes on mobile, there is an inconsistency: clicking on one checkbox may inadvertently toggle another. For instance, tapping in sequence may result in the prior checkbox activating or deactivating instead of the one currently being clicked.

**Technical Details**  
- This problem occurs specifically in React version 18.3.1.
- The error does not appear to exist in React 16.14.0, where toggling functions as expected.
- The bug might relate to how touch event listeners are handled in React 18.3.1, given its absence in earlier versions.

**Steps to Reproduce**  
1. Access the app on a mobile device (e.g., iPhone 15 Pro) using Safari, Orion, or Firefox.
2. Select multiple checkboxes in sequence.
3. Notice that the expected toggle behavior is disrupted, with the wrong checkbox sometimes activating.

**Expected Result**  
Each checkbox should respond only to its respective tap or click, toggling exclusively as the user interacts with it.

**Live Demonstration**  
- **Correct Behavior (React 16.14.0)**:  
  [React 16 Example Sandbox](https://codesandbox.io/s/react-16-checkboxes-xzzl96)  
  [Live Preview](https://xzzl96.csb.app/)

- **Incorrect Behavior (React 18.2.0)**:  
  [React 18 Example Sandbox](https://codesandbox.io/s/react-18-checkboxes-zrhpfp)  
  [Live Preview](https://zrhpfp.csb.app/)
Repository: godot
Issue: Can't Quick Open multiple files at once anymore in 4.4
Labels: enhancement,discussion,topic:editor,confirmed,usability

### Tested versions

- v4.4.dev.custom_build [c6c464cf9]

### System information

Windows 10 - Vulkan

### Issue description

After the Quick Open panel change at some point in 4.4 I think, I can no longer multiple select different files to open, for example 'Quick Open Scripts', I used to be able to hold `Shift` or `Control` and select several files and then they'd all open.
With this new panel it no longer works, it just opens the one I click on:
![image](https://github.com/user-attachments/assets/6d1e4a37-9abe-49a6-a921-fb32b0b05f35)


### Steps to reproduce

Scene -> Quick Open Script: try to select several files to open.

### Minimal reproduction project (MRP)

Any
Repository: three.js
Issue: BatchedMesh.InstancedBufferGeometry instead BatchedMesh.BufferGeometry possible ?
Labels: Suggestion

### Description

BatchedMesh.InstancedBufferGeometry instead BatchedMesh.BufferGeometry possible ?

### Solution

Change buffergeometry to InstancedBufferGeometry and recompute draw range after frustum culling

### Alternatives

Maybe without raycasting. Its need for grass rendering with big amount

### Additional context

_No response_
Repository: material-ui
Issue: Support for disabling some shadows
Labels: v6.x,customization: theme,enhancement

### Summary

Currently, MUI does not allow overriding the `Shadows` without augmenting the interface.
24 values are quite a lot to choose from. In our use case, we are okay with 3 values.

Since the current `Shadows` does not allow overrides unless you override the whole list of 24 values.
It would be beneficial to have a way of turning off the values that are not used.

### Examples

For example, in the `Typography` component, we override the `variants` and disable them via the `TypographyPropsVariantOverrides` interface. 

See the docs [Adding & disabling variants](https://mui.com/system/typography/#adding-amp-disabling-variants). This functionality could be extended to the `Shadows`.

### Motivation

The use case varies across different applications. However, the chances that a design system will have 24 shadow values are almost zero. In our design system, we agreed to have 2 to 3 shadow values.

Hence, being able to disable the ones that are not used is beneficial. 

My suggestion is a bit related to this: https://github.com/mui/material-ui/issues/28820, but not the same thing.

**Search keywords**: shadow overrides
Repository: godot
Issue: Translations are not updated when dynamically loading PCK
Labels: discussion,documentation,topic:gui

### Tested versions

Reproducible in 4.4.dev [ef8d981267702de38ffc24136f9d823d31781c60]

### System information

Windows 11 (10.0.22631)

### Issue description

When including updated translation files as part of an exported PCK file that's meant to be dynamically loaded at runtime, you currently have to manually load each `*.translation` file after having loaded the PCK in order for the updated translations to actually have any effect.

The expected behavior would be for the updated translations to be loaded as part of loading the PCK.

### Steps to reproduce

(The MRP includes a `patch.pck` file that was exported using the patch system introduced in #97118, where the translation with key `HELLO` was changed from "Hello" to "Howdy" before exporting.)

1. Open the MRP.
2. Run the main scene.
3. Note how the label says "Hello".
4. Uncomment the `ResourceLoader.load` line in `main.gd`.
5. Run the main scene again.
6. Note how the label now says "Howdy".

### Minimal reproduction project (MRP)

[localization-patching.zip](https://github.com/user-attachments/files/17600771/localization-patching.zip)
Repository: deno
Issue: Properly support verbatim module syntax
Labels: bug

It's not hooked up properly.
Repository: deno
Issue: Source maps don't work with maybe cjs files
Labels: bug

https://github.com/denoland/deno/pull/26558#discussion_r1825375077
Repository: flutter
Issue: Camera plugin: Custom codecs & container format support
Labels: p: camera,package,c: proposal,team-ecosystem,P2,design doc,triaged-ecosystem,:scroll:

### Document Link

https://flutter.dev/go/camera-custom-codecs

### What problem are you solving?

Camera plugin users don’t have control over the output codecs (both video and audio) and the container output format. This prevents them from getting a video specific to their needs, since they are instead limited to the choice made by the system. 

How can this be a problem:

- Maybe you need your files in a specific codec / container for further processing 
- Maybe your app is used by a lot of older devices and doesn’t support certain codecs or struggles with fast decoding due to older hardware
- Maybe you are just like me and don’t want to pay license fees for the new mpeg versions if you want to add additional metadata later on
- Maybe you need your video or audio file to use a certain codec to get a certain quality
- Maybe your users expect to have the option to choose the codes in which they record
Repository: next.js
Issue: Build error with dynamicIO enabled
Labels: linear: next,dynamicIO

### Link to the code that reproduces this issue

https://github.com/revnelson/next-dynamicio-debug

### To Reproduce

Build from repo

### Current vs. Expected behavior

When building a PayloadCMS starter with `dynamicIO` enabled, the following error is produced:

```console
Error occurred prerendering page "/admin/[[...segments]]". Read more: https://nextjs.org/docs/messages/prerender-error
Error: Route "/admin/[[...segments]]" has a `generateMetadata` that depends on Request data (`cookies()`, etc...) or external data (`fetch(...)`, etc...) but the rest of the route was static or only used cached data (`"use cache"`). If you expected this route to be prerenderable update your `generateMetadata` to not use Request data and only use cached external data. Otherwise, add `await connection()` somewhere within this route to indicate explicitly it should not be prerendered.
Export encountered an error on /(payload)/admin/[[...segments]]/page: /admin/[[...segments]], exiting the build.
```

I have opened an [issue](https://github.com/payloadcms/payload/issues/8897) with Payload as they may need to update the core to handle the new dynamicIO paradigm. It was stated in that issue, however, that dynamic APIs (`headers()`) are being used that should exclude the route from pre-rendering.

At a bare minimum, the error produced is unhelpful as you can see in the repo I created for this issue. I have added the suggested `await connection()` at the top of the default exported component but still get the same error.

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.0.0: Tue Sep 24 23:39:07 PDT 2024; root:xnu-11215.1.12~1/RELEASE_ARM64_T6000
  Available memory (MB): 32768
  Available CPU cores: 10
Binaries:
  Node: 22.9.0
  npm: 10.8.3
  Yarn: 1.22.19
  pnpm: 9.12.3
Relevant Packages:
  next: 15.0.3-canary.3 // Latest available version is detected (15.0.3-canary.3).
  eslint-config-next: 15.0.0
  react: 19.0.0-rc-603e6108-20241029
  react-dom: 19.0.0-rc-603e6108-20241029
  typescript: 5.6.3
Next.js Config:
  output: N/A
```


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

dynamicIO

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

next build (local)

### Additional context

_No response_
Repository: vscode
Issue: inline chat a11y diff view causes scroll down in document
Labels: bug,inline-chat

1. set `"inlineChat.accessibleDiffView": "on"`
2. request a change at the top of a file
3. switch tabs and switch back

🐛 view is scrolled down, and it also takes more space than needed


https://github.com/user-attachments/assets/b9737d9f-690f-482e-bf8a-05851559a69d
Repository: vscode
Issue: Chat: Allow a way for participants to direct requests to other participants
Labels: feature-request,api,chat

<!-- ⚠️⚠️ 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. -->

Currently there is intent detection built in so that if a request is not directed at any particular participant, the intent detection will try to direct it to the appropriate participant. However, it would be very helpful if participants could tell VSCode "I'm not the right participant to answer this query", allowing it to perform intent detection and assign to a different participant. I think this approach--where a participant just says it can't answer a query--mitigates some of the security risk of allowing participants to call each other.

For example, `@azure` gets asked a lot of workspace-related questions that would be much better answered by the `@workspace` participant. If we could redirect the questions to `@workspace` that would be helpful to end users.

/cc @isidorn