sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: tauri
Issue: decorations(false) work wrong
Labels: type: bug,status: needs triage,scope: unstable flag

### Describe the bug

decorations(false) have bug，the web content is not fullSize，have a border in the right，just like the pic
![001](https://github.com/user-attachments/assets/ca213fd9-a2aa-4bb3-ac83-e380738f2f0b)
![002](https://github.com/user-attachments/assets/39da8ac5-1492-4fa2-8149-8c2b1e5e0269)


### Reproduction

_No response_

### Expected behavior

_No response_

### Full `tauri info` output

```text
[✔] Environment
    - OS: Windows 10.0.19045 x86_64 (X64)
    ✔ WebView2: 126.0.2592.68
    ✔ MSVC: Visual Studio Professional 2019
    ✔ 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: stable-x86_64-pc-windows-msvc (default)
    - node: 18.19.0
    - pnpm: 9.3.0
    - yarn: 1.22.22
    - npm: 10.2.3

[-] Packages
    - tauri 🦀: 2.1.1
    - tauri-build 🦀: 2.0.3
    - wry 🦀: 0.47.0
    - tao 🦀: 0.30.8
    - @tauri-apps/api : 2.1.1
    - @tauri-apps/cli : 2.1.0

[-] Plugins
    - tauri-plugin-shell 🦀: 2.0.2
    - @tauri-apps/plugin-shell : 2.0.1

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:1420/
    - framework: Vue.js
    - bundler: Vite
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: next.js
Issue: Cannot debug Next15 using turbopack on windows
Labels: bug,Turbopack

### Link to the code that reproduces this issue

https://github.com/leandroluk/bug-next15-debug-with-turbopack

### To Reproduce

1. Install dependencies
2. Select "turbo" in "Run and Debug" menu
3. Select "Browser Debug" in running bar and this error message will appear:

![image](https://github.com/user-attachments/assets/1988dd02-06c5-4aef-acbe-98a826a5221b)

4. When select "webpack" in "Run and Debug" menu and look for "Browser Debug" the error doesnt appear and any breakpoint works.


### Current vs. Expected behavior

Are expected to debug works like webpack.

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Home Single Language
  Available memory (MB): 32453
  Available CPU cores: 20
Binaries:
  Node: 20.17.0
  npm: 10.9.0
  Yarn: 1.22.22
  pnpm: 9.11.0
Relevant Packages:
  next: 15.0.3 // Latest available version is detected (15.0.3).
  eslint-config-next: 15.0.3
  react: 19.0.0-rc-66855b96-20241106
  react-dom: 19.0.0-rc-66855b96-20241106
  typescript: 5.6.3
Next.js Config:
  output: N/A
```


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

Turbopack

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

next dev (local)

### Additional context

_No response_
Repository: stable-diffusion-webui
Issue: [Feature Request]: New fork for support of intel processors
Labels: enhancement

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

I have an intel pc and would like to be able to use the newest versions of WebUI, the current fork for intel processors is stuck at 1.6.0 and doesn't seem like it will be updated again. I was wondering if someone could help by making a new one for the current version. I would do this myself, but I have absolutely no idea what I'm doing. My PC specs are as follows if it's helpful to you.

Processor:	12th Gen Intel(R) Core(TM) i5-12500H   2.50 GHz
Installed RAM:	8.00 GB (7.68 GB usable)
System type:	64-bit operating system, x64-based processor
Edition:	Windows 11 Pro
Version:	23H2
Installed on:	‎10/‎11/‎2022
OS build:	22631.4391
Experience:	Windows Feature Experience Pack 1000.22700.1047.0

### Proposed workflow

Just a version for intel processers that will actually be updated.

### Additional information

_No response_
Repository: ui
Issue: [bug]: Passing in a custom component into the popover component does not behave as expected
Labels: bug

### Describe the bug

I've create a custom component `SidebarPopover` whose props include `popoverTrigger` of type `React.ReactNode`. Component essentially looks like this:
```tsx
<Popover>
  <PopoverTrigger asChild>
    {popoverTrigger}
  </PopoverTrigger>
  <PopoverContent className="w-80 h-80">
    {popoverContent}
  </PopoverContent>
</Popover>
```
I've been attempting to pass in a custom component that I created, `SidebarButton`, into my custom `SidebarPopover` component through the `popoverTrigger` prop. `SidebarButton` looks something like this:
```tsx
<Button className="max-w-fit h-18 rounded-none p-2 m-1">
  <Image src={imageIcon} alt={alt} width={50} height={50} />
</Button>
```
Passing in `SidebarButton` into `SidebarPopover` does not display the popover as expected. HOWEVER, if I directly pass in:
```tsx
const popover = <Button className="max-w-fit h-18 rounded-none p-2 m-1"><Image src={button.image} alt={button.alt} width={50} height={50}/></Button>
```
into my custom `SidebarPopover`, the popover appears?!? I would expect that passing in the above, and the `SidebarButton` component should yield the same behavior, but this is not the case.

In both cases `Button` is the shadcn ui component and `Image` is from Next.js' libraries.

### Affected component/components

Popover

### How to reproduce

1. Create the sidebar popover custom component mentioned in the description
2. Create the custom sidebar button mentioned in the description above
3. Pass in the custom sidebar button into the sidebar popover custom component as a prop
4. Observe that no popover appears when clicking on the sidebar button
5. Pass in the JSX directly into the sidebar popover custom component and observe that the popover now appears

### Codesandbox/StackBlitz link

https://codesandbox.io/p/github/carolinar7/react-practice/shadcn-bug-popover-bug-report

### Logs

_No response_

### System Info

```bash
Windows 11, Chrome
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: ant-design
Issue: form.list 中form.item 单独使用layout="vertical" 会失去高度
Labels: 🐛 Bug,Inactive

### Reproduction link

[![Edit on StackBlitz](https://developer.stackblitz.com/img/open_in_stackblitz.svg)](https://stackblitz.com/edit/vitejs-vite-zrnbko?file=src%2FApp.tsx)

### Steps to reproduce

form.list 中form.item 单独使用layout="vertical" 会失去高度

### What is expected?

正常撑开

### What is actually happening?

item部分失去高度

| Environment | Info |
| --- | --- |
| antd | 5.22.1 |
| React | 18 |
| System | win10 |
| Browser | edge |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: tauri
Issue: [bug]  Socket Io doesn't work in tauri+angular app with ALB node socket server
Labels: type: bug,status: upstream,platform: macOS,status: needs triage

### Describe the bug

Getting socket Id unknown
Getting error only in mac.
working fine for linux and windows

Issue with ALB sticky session

On mac it doesn't allow cookies

![Untitled design](https://github.com/user-attachments/assets/4f90eca9-a6c8-46aa-b1fe-69f30facb6d8)



### Reproduction

_No response_

### Expected behavior

_No response_

### Full `tauri info` output

```text
[✔] Environment
    - OS: Mac OS 15.1.0 x86_64 (X64)
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.82.0 (f6e511eec 2024-10-15)
    ✔ cargo: 1.82.0 (8f40fc59f 2024-08-21)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-x86_64-apple-darwin (default)
    - node: 18.20.4
    - npm: 10.9.0

[-] Packages
    - tauri 🦀: 2.0.6
    - tauri-build 🦀: 2.0.2
    - wry 🦀: 0.46.3
    - tao 🦀: 0.30.5
    - @tauri-apps/api : 2.0.3 (outdated, latest: 2.1.1)
    - @tauri-apps/cli : 2.0.5 (outdated, latest: 2.1.0)

[-] Plugins
    - tauri-plugin-shell 🦀: 2.0.2
    - @tauri-apps/plugin-shell : 2.0.1
    - tauri-plugin-log 🦀: 2.0.2
    - @tauri-apps/plugin-log : not installed!
    - tauri-plugin-fs 🦀: 2.0.3
    - @tauri-apps/plugin-fs : not installed!
    - tauri-plugin-dialog 🦀: 2.0.3
    - @tauri-apps/plugin-dialog : 2.0.1
    - tauri-plugin-process 🦀: 2.0.1
    - @tauri-apps/plugin-process : 2.0.0
    - tauri-plugin-updater 🦀: 2.0.2
    - @tauri-apps/plugin-updater : 2.0.0

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist/cooper
    - devUrl: http://localhost:4200/
    - framework: Angular
    - bundler: Webpack
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: deno
Issue: `deno check` does not respect top level `exclude` in `deno.json`
Labels: needs investigation,tsc,workspaces

Version: Deno 2.0.6

Running `deno check .` in the project root directory checks files within a directory `foo/bar` specified in `exclude`. `deno fmt` and `deno lint` respect the `exclude` configuration.

Running `deno check foo/bar` where `foo/bar/` is the excluded directory will return a warning that no matching files were found.

TLDR:

- `foo/bar/` in top level `exclude` in `deno.json`
- `deno check .` reports errors in `foo/bar/baz.ts`
- `deno check foo/bar` returns warning that no matching files were found.
Repository: ant-design
Issue: vertical布局的Form的labelCol.offset无效
Labels: 🐛 Bug,help wanted

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/p/sandbox/antd-reproduction-template-forked-sdgg8r)

### Steps to reproduce

直接查看效果

### What is expected?

![image](https://github.com/user-attachments/assets/c57a7688-4f43-4ccb-9634-0866e2f32fa1)


### What is actually happening?

未对齐

| Environment | Info |
| --- | --- |
| antd | 5.22.1 |
| React | 18 |
| System | windows11 |
| Browser | chrome |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: vscode
Issue: Git - Expose `Repository#getEmptyTree()` in Git extension API
Labels: feature-request,git

This would allow extensions that depend on the Git extension to accurately handle getting changed files in commits with no parent, e.g. Copilot Chat which uses the Git extension to compute related files for the Copilot Edits working set.
Repository: angular
Issue: Missleading zoneless documentation
Labels: P5,area: docs

### Describe the problem that you experienced

[In https://github.com/angular/angular/blob/190b4d7763e2953b63b478cc749846a5d5423795/adev/src/content/guide/zoneless.md?plain=1#L61](https://github.com/angular/angular/blob/190b4d7763e2953b63b478cc749846a5d5423795/adev/src/content/guide/zoneless.md?plain=1#L61C1-L62C448) it says:

"**When a library component is a host for user-components which might use `ChangeDetectionStrategy.Default`, it cannot use `OnPush` because that would prevent the child component from being refreshed if it is not `OnPush` compatible and relies on ZoneJS to trigger change detection.**"

In my understanding, an app developer will use my library component in a template he has control of. This means, the app developer can determine the change detection strategy himself.

My library component can host the content of the app developer in form of content projection or by providing a template. In both cases, the information has to be provided by the app developer, in a context he has control of. The template and/or projected content will be parsed by angular in the context it was "written in" by the app developer. 

Imagine the following situation: 

Component A `Default`, our root component.
Component B `Default`, a component that relies on zone.js for change detection
Component C `OnPush`, projects content or prints a template.

Component A.html:
`
<component-c> 
  <ng-template #template>
    <component-b></component-b>
  </ng-template>
  <component-b></component-b>
</component-c>
`

This will work as long as Component A is set to `Default`.

See https://github.com/fl-mueller/zonelessTest/tree/angular-issue-showcase



### Enter the URL of the topic with the problem

_No response_

### Describe what you were looking for in the documentation

_No response_

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```
Repository: deno
Issue: question: confusion about adding developer/dev dependencies
Labels: install,triage required 👀

I am not quite sure how Deno knows if the dependencies I am adding is a dev dependency or not. Here is a reproduction.

```bash
deno init dev-dependency-test
cd dev-dependency-test
deno add --dev jsr:@denosaurs/argontwo
```
But there is no actual separation of which is a dev dependency in `deno.json`.

```json
{
  "tasks": {
    "dev": "deno run --watch main.ts"
  },
  "imports": {
    "@denosaurs/argontwo": "jsr:@denosaurs/argontwo@^0.2.0",
    "@std/assert": "jsr:@std/assert@1"
  }
}
```
And in `deno.lock`.

```json
{
  "version": "4",
  "specifiers": {
    "jsr:@denosaurs/argontwo@0.2": "0.2.0",
    "jsr:@denosaurs/lz4@0.1.4": "0.1.4",
    "jsr:@std/assert@1": "1.0.8",
    "jsr:@std/encoding@0.221": "0.221.0",
    "jsr:@std/internal@^1.0.5": "1.0.5"
  },
  "jsr": {
    "@denosaurs/argontwo@0.2.0": {
      "integrity": "1ce2f4c90ba3643e6fffd0d9be059f7cacfb62cf1b314049b6c7c71d87cb92a1",
      "dependencies": [
        "jsr:@denosaurs/lz4",
        "jsr:@std/encoding"
      ]
    },
    "@denosaurs/lz4@0.1.4": {
      "integrity": "ad5d556c02eb01fe1e0f2e953d7be066a14870afe149b1aed1ced019460f6aa1"
    },
    "@std/assert@1.0.8": {
      "integrity": "ebe0bd7eb488ee39686f77003992f389a06c3da1bbd8022184804852b2fa641b",
      "dependencies": [
        "jsr:@std/internal"
      ]
    },
    "@std/encoding@0.221.0": {
      "integrity": "d1dd76ef0dc5d14088411e6dc1dede53bf8308c95d1537df1214c97137208e45"
    },
    "@std/internal@1.0.5": {
      "integrity": "54a546004f769c1ac9e025abd15a76b6671ddc9687e2313b67376125650dc7ba"
    }
  },
  "workspace": {
    "dependencies": [
      "jsr:@denosaurs/argontwo@0.2",
      "jsr:@std/assert@1"
    ]
  }
}
```

In Node, there is a field called `devDependencies` which makes it easy to track which dependency is a dev dependency or not. Maybe this `--dev` flag was supposed to declare a package as a dev dependency in `deno.lock`. Was this overlooked or something that is still being worked on?
Repository: go
Issue: net: TestLookupNoSuchHost/LookupSRV_NXDOMAIN/forced_cgo_resolver failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "net" && test == "TestLookupNoSuchHost/LookupSRV_NXDOMAIN/forced_cgo_resolver"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8731319005757721169)):

    === RUN   TestLookupNoSuchHost/LookupSRV_NXDOMAIN/forced_cgo_resolver
        lookup_test.go:1599: IsNotFound is set to false
        lookup_test.go:1603: error message is not equal to: no such host
        lookup_test.go:1612: backoff 1s after failure lookup _unknown._tcp.invalid.invalid. on 8.8.8.8:53: read udp 162.231.98.115:15878->8.8.8.8:53: i/o timeout
        lookup_test.go:1599: IsNotFound is set to false
        lookup_test.go:1603: error message is not equal to: no such host
        lookup_test.go:1612: backoff 5s after failure lookup _unknown._tcp.invalid.invalid. on 8.8.8.8:53: read udp 162.231.98.115:1702->8.8.8.8:53: i/o timeout
        lookup_test.go:1599: IsNotFound is set to false
        lookup_test.go:1603: error message is not equal to: no such host
        lookup_test.go:1612: backoff 30s after failure lookup _unknown._tcp.invalid.invalid. on 8.8.8.8:53: read udp 162.231.98.115:19387->8.8.8.8:53: i/o timeout
        lookup_test.go:1599: IsNotFound is set to false
        lookup_test.go:1603: error message is not equal to: no such host
        lookup_test.go:1617: unexpected error: lookup _unknown._tcp.invalid.invalid. on 8.8.8.8:53: read udp 162.231.98.115:47538->8.8.8.8:53: i/o timeout
    --- FAIL: TestLookupNoSuchHost/LookupSRV_NXDOMAIN/forced_cgo_resolver (76.13s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: godot
Issue: 3D Navigation Scheme Takes alot of time to set the proper shortcut for Orbit, Pan, and Zoom mouse buttons
Labels: bug,topic:editor,usability,topic:input,topic:3d

### Tested versions

Reproducable in: 4.4.dev[277cb68e1]

### System information

Godot v4.4.dev (277cb68e1) - Windows 10.0.19045 - Multi-window, 1 monitor - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1080 Ti (NVIDIA; 32.0.15.6603) - 11th Gen Intel(R) Core(TM) i5-11400F @ 2.60GHz (12 threads)

### Issue description

If you go to Editor settings and change editors/3d/navigation/navigation_scheme, Orbit Mouse Button, Pan Mouse Button, and Zoom Mouse Button all change their mouse buttons first, then after saving change their key modifiers.

https://github.com/user-attachments/assets/fa143a1c-2353-41ce-8142-80bd1f71194e



### Steps to reproduce

N/A

### Minimal reproduction project (MRP)

N/A
Repository: godot
Issue: Can't set 3D Navigation Mouse Buttons modifiers in Editor Settings  
Labels: bug,topic:editor,usability,topic:input

### Tested versions

4.4.dev.custom_build [76fa7b291]

### System information

Godot v4.4.dev (76fa7b291) - Windows 10.0.19045 - Multi-window, 1 monitor - OpenGL 3 (Compatibility) - NVIDIA GeForce GTX 1080 Ti (NVIDIA; 32.0.15.6603) - 11th Gen Intel(R) Core(TM) i5-11400F @ 2.60GHz (12 threads)

### Issue description

User is unable to set the 3D Navigation mouse button modifier keys and is only able to change them according to the Default Navigation Schemes.

https://github.com/user-attachments/assets/d9dec110-c895-428d-b7a6-690ab2fcaf43

### Steps to reproduce

N/A

### Minimal reproduction project (MRP)

N/A
Repository: storybook
Issue: [Bug]: Tags filter visual bug when there are empty value tags
Labels: bug,tags

### Describe the bug

If a story has tags like so:
```ts
export const MyStory = {
  tags: ['']
}
```

It results in those `''` being indexed and are shown like this in the UI:
<image src="https://github.com/user-attachments/assets/8c72d9e6-59e7-4dcf-91d0-c3b9de69f3fb" width="350"/>

### Reproduction link

https://stackblitz.com/edit/github-yjmnux?file=src%2Fstories%2FButton.stories.js&preset=node

### Reproduction steps

_No response_

### System

```bash
-
```

### Additional context

_No response_
Repository: rust
Issue: Renaming targets might be a breaking change
Labels: T-compiler,C-discussion,A-targets,O-wasi

Hi all,

I am unsure if this is the right place for this sort of issue and apologize if it isn't. I would also like to stress that I fully understand this issue is not currently actionable, but I want to bring it to the attention of the maintainers in case this is a blind spot. If this has been discussed to death elsewhere (that I could not find) I also apologize for the extra noise.

Recently, through compiler warnings I have been made aware of: https://blog.rust-lang.org/2024/04/09/updates-to-rusts-wasi-targets.html#renaming-wasm32-wasi-to-wasm32-wasip1

Namely, renaming the `wasm32-wasi` target to `wasm32-wasip1`. In Zellij, we bundle minor applications that we call plugins - compiled to this target - within our executable. This is how we compile and distribute our software and represents a compromise of various factors. Renaming this target represents a breaking change for us. It means we will no longer be able to compile the same project for the newer rust version, and that if we upgrade our toolchain, we will no longer be able to compile the same project for a (much) older version.

This is not a big deal for us. Making the change should be a trivial search/replace, and we don't absolutely have to support much older toolchains. However, as a user of the language I assumed (perhaps mistakenly) that targets are an external user-facing API. That any non-backwards-compatible changes to them would be considered breaking changes and should only be expected in major version bumps. Since this was not the case here, it gets me a little worried that perhaps either I do not understand the breaking changes policy (even after reading the relevant RFC) or there is some sort of miscommunication going on between the language developers and at least some of its users. Or - of course - this is a blind spot.

In case this is the latter, I wanted to bring it to the attention of the maintainers. Not for this change of course - as I understand it's already very much underway - but at least for future changes.

Thanks for all the work everyone is doing.
Repository: PowerToys
Issue: Add Show/Hide Window Toggle to Keyboard Manager -> Remap Shortcut -> Run Program -> If running,
Labels: Needs-Triage

### Description of the new feature / enhancement

In the Keyboard manager, a remapped shortcut can have a setting of "Show Window" (Keyboard Manager -> Remap Shortcut -> Run Program -> If running)

It would be great to be able to press a second time and make it go away for ease of use.

### Scenario when this would be used?

If the window is left running in the background, the scenario can be that you're swapping in and out of the app. On a laptop you may not leave the app at the forefront of the screen, so having the option to get rid of it quickly (not to interrupt your flow) would be useful.

### Supporting information

_No response_
Repository: vscode
Issue: When hover contains one hover provider result, increase/decrease verbosity commands should work on that provider result
Labels: polish,editor-hover

# Description

I created these keybindings to control hover verbosity: 

```json
  {
    "key": "up",
    "command": "editor.action.increaseHoverVerbosityLevel",
    "when": "editorHoverFocused"
  },
  {
    "key": "down",
    "command": "editor.action.decreaseHoverVerbosityLevel",
    "when": "editorHoverFocused"
  }
```

When I focus hover (`cmd+k cmd+i` and then again `cmd+k cmd+i`) and invoke these commands using keybindings, they get invoked, but they don't do anything (because the hover provider result within hover widget is not focused).

I would assume that when there is only one hover result, the commands should work without me doing more gestures to focus the only provider result. 

Additionally, I would expect that even when there are multiple hover results but only one of them allows increasing/decreasing verbosity, the commands should work without me focusing specific result.