sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: "Add a folder to Workspace" stops working when opening multiple folders
Labels: bug,linux,electron,native-file-dialog

<!-- ⚠️⚠️ 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.92.0
- OS Version: Ubuntu 22.04.4

Steps to Reproduce:

1. Click "Add a folder to Workspace"
2. Select multiple folders
3. Click "Open"

Nothing opens and the "Add a folder to Workspace" no longer works, requires a reload of VS code
When selecting a single folder, works fine.. but multiple folders prevents it from working until a restart

I did not see any errors in the logs
Repository: rust
Issue: generated call to core::fmt::Arguments::new_const fails to constant fold
Labels: T-compiler,A-fmt,C-optimization

normal code:
```rust
pub fn main() {
    println!("hello");
}
```

code that should be equivalent, but is actually more efficient
```rust
#![feature(print_internals)]
#![feature(const_fmt_arguments_new)]

pub fn main() {
    ::std::io::_print(const { format_args!("hello\n") }); 
}
```

[godbolt link for asm comparison](https://rust.godbolt.org/z/bYvr38Pv3)

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":null}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: tensorflow
Issue: Presubmit checks for Windows Failing
Labels: stat:awaiting tensorflower,type:build/install,subtype:windows,2.17

### Issue type

Bug

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

Yes

### Source

source

### TensorFlow version

TF 2.17

### Custom code

Yes

### OS platform and distribution

Windows 10/11

### Mobile device

_No response_

### Python version

3.11

### Bazel version

6.5.0

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

Windows Presubmit seems to be failing for every commit. 

![image](https://github.com/user-attachments/assets/c67d6fb7-19ac-4680-bab4-20221f4a31f2)


### Standalone code to reproduce the issue

```shell
I am unable to see the log or the command running which is Google internal. Whenever I try to go to the details, it gives me a permission denied error.
```


### Relevant log output

_No response_
Repository: kubernetes
Issue: Slow FSGroup recursive permission changes cause customer confusion
Labels: kind/bug,sig/storage,triage/accepted

### What happened?

[FSGroup volume permission setting](https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#configure-volume-permission-and-ownership-change-policy-for-pods) is very useful for making NFS volumes just work in spite of the impedance between containers and traditional user id based linux file permissions. 

However, in practice with large volumes, fsgroup settings can cause workloads to effectively get stuck, as it can take hours or days to recursively change permissions on multi-terabyte servers. The fsGroupChangePolicy has helped that (onRootMismatch is a win), but this has still been a perennial source of customer issues.

The [kubelet does log when a long fsgroup change is in progress](https://github.com/kubernetes/kubernetes/blob/master/pkg/volume/volume_linux.go#L49), but this does not provide enough actionable information.


### What did you expect to happen?


The kubelet logging could be extended to provide updates of long-running fsgroup recursion, and maybe even some kind of progress (eg, some estimates of how much of the file tree has been walked).

### How can we reproduce it (as minimally and precisely as possible)?

Reproduction requires a large volume with many files, but it can be done with any volume type, eg RWO.

### Anything else we need to know?

_No response_

### Kubernetes version

<details>
All versions
</details>


### Cloud provider

<details>
We've seen customer complaints on GKE, but I imagine it happens on all providers.
</details>


### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>
Repository: material-ui
Issue: joyui + nextjs + template some theme colors loads after initial page load
Labels: on hold,package: joy-ui,nextjs

### Steps to reproduce

Link to live example: ([Stackblitz](https://stackblitz.com/edit/stackblitz-starters-j56ysq))

Steps:
1. Using https://github.com/mui/material-ui/tree/master/docs/data/joy/getting-started/templates/order-dashboard as inspiration
2. And nextjs integration [here](https://mui.com/joy-ui/integrations/next-js-app-router/)
3. The "Used Space" w/ warning color loads using primary color and then changes to warning color after load. 
4. This can be somewhat mitigated by setting color property to all children of the card component. Even doing that some elements children change their color after the page has loaded. For example, setting LinearProgress border still flickers / changes color when it's color property is set to warning.
5. Make sure browser is wide enough (Desktop experience) to see the side navigation

![nextjs-joyui](https://github.com/user-attachments/assets/d76dfe42-5511-439a-972f-78daaed97955)


### Current behavior

Theme color is loaded after initial nextjs render

### Expected behavior

Theme color is loaded during initial page render

### Context

Not have theme color flickering on page load

### Your environment

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```

  System:
    OS: macOS 14.6
  Binaries:
    Node: 20.15.1 - ~/.nvm/versions/node/v20.15.1/bin/node
    npm: 10.7.0 - ~/.nvm/versions/node/v20.15.1/bin/npm
    pnpm: 9.6.0 - ~/.nvm/versions/node/v20.15.1/bin/pnpm
  Browsers:
    Chrome: 127.0.6533.89
    Edge: 127.0.2651.86
    Safari: 17.6
  npmPackages:
    @emotion/react: catalog: => 11.13.0 
    @emotion/styled: catalog: => 11.13.0 
    @mui/icons-material: catalog: => 5.16.6 
    @mui/joy: catalog: => 5.0.0-beta.48 
    @types/react: catalog: => 18.3.3 
    react: catalog: => 18.3.1 
    react-dom: catalog: => 18.3.1 
    typescript: catalog: => 5.5.4 

```
</details>


**Search keywords**: joyui nextjs theme reload flicker
Repository: ui
Issue: [bug]: When using Popover with PopoverAnchor instead of PopoverTrigger, onOpenChange is *never* called with true, only false.
Labels: bug

### Describe the bug

See: https://github.com/shadcn-ui/ui/discussions/1684

And: https://github.com/shadcn-ui/ui/issues/2798

When using `<PopoverAnchor>` instead of `<PopoverTrigger>` in order to manually/programmatically open the Popover (via passing a boolean state to the `open` prop) from unrelated components, `onOpenChange` is only ever called with `false`, and at no point will be called with `true`.

As a workaround, I am using a 200ms timeout when calling setting the `open` prop state.

### Affected component/components

Popover

### How to reproduce

```tsx
const [open, setOpen] = useState(false);

[...]

<Popover
  open={open}
  onOpenChange={(isOpen) => {
    console.log('isOpen', isOpen); // is ALWAYS false
  }}
>
  <PopoverAnchor>
    [...]
  </PopoverAnchor>
  <PopoverContent>[...]</PopoverContent>
</Popover>

[...]

<div onClick={() => setOpen(true)}>some div</div>
```

### Codesandbox/StackBlitz link

Your v0 doesn't allow dependencies to be changed, and I couldn't figure out how to get shadcn up and running on codesandbox.

### Logs

_No response_

### System Info

```bash
Chrome on 2023 MacBook Pro w/ macOS 14.1, 36GB RAM, and M3 Max
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: vscode
Issue: Can't open folder from breadcrumbs in secondary view
Labels: feature-request,breadcrumbs

<!-- ⚠️⚠️ 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: 
```
code-insiders --version
1.93.0-insider
39d98602020ddefe53ed217a8c50b9040673a737
arm64
```

- OS Version: 
```
14.5 (23F79)
```

Steps to Reproduce:

1. Click on a foldername in the breadcrumb, or double click it, or right click it
2. No way for me to open the folder in the secondary sidebar in my folder/file explorer
Repository: pytorch
Issue: DISABLED test_warn_on_invalid_torch_function_tensor_subclass (__main__.TestTorchFunctionWarning)
Labels: triaged,module: flaky-tests,skipped,module: __torch_function__

Platforms: asan, linux, mac, macos, win, windows, rocm, slow



This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_warn_on_invalid_torch_function_tensor_subclass&suite=TestTorchFunctionWarning&limit=100) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/28372612055).

Over the past 3 hours, it has been determined flaky in 62 workflow(s) with 186 failures and 62 successes.

**Debugging instructions (after clicking on the recent samples link):**
DO NOT ASSUME THINGS ARE OKAY IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_warn_on_invalid_torch_function_tensor_subclass`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.



<details><summary>Sample error message</summary>

```
Traceback (most recent call last):
  File "/var/lib/jenkins/workspace/test/test_overrides.py", line 1159, in test_warn_on_invalid_torch_function_tensor_subclass
    with self.assertWarnsRegex(UserWarning, "as a plain method is deprecated"):
  File "/opt/conda/envs/py_3.10/lib/python3.10/unittest/case.py", line 295, in __exit__
    self._raiseFailure("{} not triggered".format(exc_name))
  File "/opt/conda/envs/py_3.10/lib/python3.10/unittest/case.py", line 163, in _raiseFailure
    raise self.test_case.failureException(msg)
AssertionError: UserWarning not triggered

To execute this test, run the following from the base repo dir:
    python test/test_overrides.py -k TestTorchFunctionWarning.test_warn_on_invalid_torch_function_tensor_subclass

This message can be suppressed by setting PYTORCH_PRINT_REPRO_ON_FAILURE=0
```

</details>


Test file path: `test_overrides.py`

cc @clee2000 @hameerabbasi @rgommers @ezyang
Repository: ant-design
Issue: Table sticky 使用 components.header.table 样式异常
Labels: Inactive,improvement,🧶 Low Priority

### Reproduction link

[![Edit on StackBlitz](https://developer.stackblitz.com/img/open_in_stackblitz.svg)](https://stackblitz.com/edit/react-jpxw83?file=demo.tsx)

### Steps to reproduce

查看 demo，阴影超出了

![image](https://github.com/user-attachments/assets/70009837-dc83-4bc5-9012-658981f5d242)


### What is expected?

阴影不超过 header

### What is actually happening?

阴影超过  header 了

| Environment | Info |
| --- | --- |
| antd | 5.20.0 |
| React | latest |
| System | mac |
| Browser | chrome |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: godot
Issue: Godot freezes for a while after left alone for longer periods of time
Labels: bug,topic:editor,needs testing

### Tested versions

v4.3.rc2.official [3978628c6]
Never noticed it in 4.2

### System information

Mac Mini M1 with newest MacOS

### Issue description

When Godot stays on the screen unattended for a period of time (a few hours… or at least enough for the screen saver to play for a while) and work is resumed, it freezes for quite some time (the cursor turns into a rainbow spinning wheel) and nothing can be clicked (other apps react normally if switched to). It eventually unfreezes and normal work can be resumed.

It does not look like #95104 because in my case I barely started the project and don't have any big assets. No other application behaves like that, even very asset-heavy apps like iMovie.

But it sounds like https://github.com/godotengine/godot/issues/95150#issuecomment-2269812504

### Steps to reproduce

It looks like it always happens when there's a `@tool` involved. As a test, yesterday I left Godot overnight and it didn't freeze, today I added a simple

```gdscript
@tool
extends Node
```

…left the IDE open on the scene containing this Node and found it frozen in the morning.

### Minimal reproduction project (MRP)

( n/a )
Repository: tauri
Issue: [bug] The MSI and NSIS installers fail to install WebView2 on Windows 7.
Labels: type: bug,platform: Windows,status: needs triage

### Describe the bug

![image](https://github.com/user-attachments/assets/65d9ae07-8b4e-4be5-a7d1-17e1f35a5e82)
"windows": {
    "webviewInstallMode": {
        "type": "embedBootstrapper"
    }
}

### Reproduction

_No response_

### Expected behavior

_No response_

### Full `tauri info` output

```text
N/A
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: next.js
Issue: Metadata not being generated for intercepting routes but generated for parallel routes
Labels: bug,Metadata,Parallel & Intercepting Routes

### Link to the code that reproduces this issue

https://codesandbox.io/p/sandbox/intercepting-route-metadata-sample-mglmyj

### To Reproduce

1. Start the development 
2. On the default page shown, click on the any of the category link
3. On the intercepted route shown, notice metadata is not generated
4. On the parallel route, metadata is generated

### Current vs. Expected behavior

Following the examples in the doc, I expected that a metadata should be generated for the intercepting route but this does not get generated, I do not want to use the client side approach for proper SEO

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
  Available memory (MB): 8073
  Available CPU cores: 4
Binaries:
  Node: 20.5.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.2.5 // Latest available version is detected (14.2.5).
  eslint-config-next: 14.1.2
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Metadata, Parallel & Intercepting Routes

### Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local), next start (local)

### Additional context

_No response_
Repository: godot
Issue: server_disconnected emits on client when authentication is failed
Labels: bug,topic:multiplayer

### Tested versions

- Reproducible in: v4.0.beta17.official [c40020513], v4.1.4.stable.official [fe0e8e557], v4.2.2.stable.official [15073afe3],  v4.3.rc2.official [3978628c6]

### System information

Godot v4.3.rc2 - Ubuntu 24.04 LTS 24.04 - X11 - GLES3 (Compatibility) - Mesa Intel(R) Graphics (ADL GT2) - 12th Gen Intel(R) Core(TM) i5-1235U (12 Threads)

### Issue description

`server_disconnected` signal emits on client when authenticating is failed, and I think this is not correct, because `connected_to_server` doesn't emit.

### Steps to reproduce

1. Set authenticate callback which rejects clients with `multiplayer.multiplayer_peer.disconnect_peer(<peer>)` (if clients gets rejected with timeout, this also works).
2. On one game instance, create server.
3. On other game instance, try to connect.
4. Observe both `peer_authentication_failed` and `server_disconnected` emitted on client.

### Minimal reproduction project (MRP)

[mrp.zip](https://github.com/user-attachments/files/16505288/mrp.zip)
1. Run 2 instances.
2. On first, click "create".
3. On second, click "join".
4. Observe both `peer_authentication_failed` and `server_disconnected` emitted on client (visible in console).
Repository: godot
Issue: AnimatedSprite2D SpriteFrames importer does not support trackpad zoom (pinch/pull) gestures
Labels: enhancement,topic:editor,usability,topic:2d

### Tested versions

v4.2.2.stable.mono.official [15073afe3], v4.1.4.stable.mono.official [fe0e8e557], v4.3.rc2.mono.official [3978628c6]

### System information

macOS 14.6 (23G80), M2 Max, v4.2.2.stable.mono.official [15073afe3]

### Issue description

The `SpriteFrames`' sprite sheet importer does not accept the zoom (pinch/pull) trackpad gestures. The scroll gestures from the trackpad do work, as does control-scrolling the mouse wheel.

### Steps to reproduce

1. Create a new `AnimatedSprite2D` and add a new `SpriteFrames` resource.
2. On the animation pane, click on the `Add frames from sprite sheet` button and choose a sprite sheet.
3. Pinch and pull on the trackpad. The window does not zoom in or out. `Ctrl + scrollwheel` on the mouse does work.

### Minimal reproduction project (MRP)

[Animation Import Test.zip](https://github.com/user-attachments/files/16505349/Animation.Import.Test.zip)
Repository: storybook
Issue: [Bug]: React developer tools "Inspect element" feature doesn't work with Storybook.
Labels: help wanted,compatibility with other tools

### Describe the bug

This issue was described in detail in this previous bug report which has been closed without being fixed: https://github.com/storybookjs/storybook/issues/4769

In short, the React developer tools provide a convenient "Inspect" function to allow you to view the state of a component in detail simply by clicking on it. Storybook somehow breaks this, so that only components which are part of the Storybook user interface can be inspected, and not any of the custom components which Storybook users are developing.

There is a workaround which involves popping out the story to a new tab without the Storybook UI, at which point it's then possible to inspect the components. This is not particularly convenient, and it's hard to discover if you don't know about it already.

I think this should be considered as a priority, as not providing fast and convenient access to development tools for the most widely used frontend framework significantly detracts from Storybook's stated purpose as a "frontend workshop for building UI components and pages in isolation".

### Reproduction link

https://wpds-ui-kit-storybook.preview.now.washingtonpost.com/?path=/docs/accordion--docs

### Reproduction steps

1. Install the react developer tools extension for your browser
2. Switch to the "Components" panel
3. Click on the icon at the top left to "inspect" components
4. Click on a component within the story

The component which you clicked on should be selected, but instead some other component which is part of the Storybook UI is selected.

### System

```bash
Storybook Environment Info:

  System:
    OS: Linux 6.9 Fedora Linux 40 (Workstation Edition)
    CPU: (20) x64 12th Gen Intel(R) Core(TM) i7-12700H
    Shell: 5.2.26 - /bin/bash
  Binaries:
    Node: 20.12.2 - /usr/bin/node
    Yarn: 4.1.0 - /usr/local/bin/yarn <----- active
    npm: 10.8.2 - /usr/local/bin/npm
  npmPackages:
    @storybook/addon-essentials: ^8.2.7 => 8.2.7
    @storybook/addon-interactions: ^8.2.7 => 8.2.7
    @storybook/addon-links: ^8.2.7 => 8.2.7
    @storybook/blocks: ^8.2.7 => 8.2.7
    @storybook/react: ^8.2.7 => 8.2.7
    @storybook/react-vite: ^8.2.7 => 8.2.7
    @storybook/testing-library: ^0.2.2 => 0.2.2
    chromatic: ^11.7.0 => 11.7.0
    storybook: ^8.2.7 => 8.2.7
```


### Additional context

_No response_
Repository: ollama
Issue: Please add CodeShell to Ollama/library, as llama.cpp already supports it
Labels: model request

Hi, 
The codeshell model: https://huggingface.co/WisdomShell/CodeShell-7B-Chat-int4 
Since CodeShell is already supported by llama.cpp, please help add CodeShell to ollama/library. Thanks!

<img width="896" alt="image" src="https://github.com/user-attachments/assets/0b125b59-17f0-44a4-83e7-98a13f849543">
Repository: flutter
Issue: Consider deprecating `CupertinoSegmentedControl`
Labels: framework,a: fidelity,f: cupertino,c: proposal,P2,team-design,triaged-design

`CupertinoSegmentedControl` is modelled after pre-iOS 13 `UISegmentedControl`. On iOS 13 (released September 2019, according to https://developer.apple.com/support/app-store/ ~97% users are now on iOS 16+) it received significant visual updates.

There doesn't seem to be a lot of reasons to keep using `CupertinoSegmentedControl` over `CupertinoSlidingSegmentedControl` (the API is similar if not identical). `CupertinoSegmentedControl` should probably be deprecated at this point, so people don't use it by accident.