sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: False positive `dead_code` lint when type is only used via destructuring
Labels: A-lints,A-diagnostics,T-compiler,L-dead_code

### Code

```Rust
struct Foo(usize);

fn get_thing<T>() -> T { todo!() }

pub fn foo() {
    let Foo(_x) = get_thing();
    
    // no warning if the type is explicitly used when calling get_thing
    // let Foo(_x) = get_thing::<Foo>();
}
```

### Current output

```Shell
warning: struct `Foo` is never constructed
 --> src/lib.rs:1:8
  |
1 | struct Foo(usize);
  |        ^^^
  |
  = note: `#[warn(dead_code)]` on by default
```

### Desired output

```Shell
(nothing)
```

### Rationale and extra context

For context, the specific "get_thing" function I originally ran into this was with [`zerocopy::FromBytes::read_from_bytes`]( https://docs.rs/zerocopy/latest/zerocopy/trait.FromBytes.html#method.read_from_bytes).

### Other cases

```Rust

```

### Rust Version

```Shell
$ rustc --version --verbose
rustc 1.82.0 (f6e511eec 2024-10-15)
binary: rustc
commit-hash: f6e511eec7342f59a25f7c0534f1dbea00d01b14
commit-date: 2024-10-15
host: x86_64-unknown-linux-gnu
release: 1.82.0
LLVM version: 19.1.1
```

### Anything else?

_No response_

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

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

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: rust
Issue: The run-make/version-verbose-commit-hash test doesn't reliably detect when the commit hash is missing
Labels: A-testsuite,T-bootstrap,C-bug,A-run-make

We recently had pre-nightly builds without a commit hash in the verbose version info (https://github.com/rust-lang/rust/issues/132845). This is despite the fact that we have a [test](https://github.com/rust-lang/rust/blob/5c9cc0cfbb11a97d084e5a09bb47cc5566421460/tests/run-make/version-verbose-commit-hash/rmake.rs#L0-L1) fully dedicated to preventing exactly that. Clearly, something is wrong with the test.

The issue with the test is that it has `//@ needs-git-hash`, which means it gets only run when bootstrap self-reports to compiletest that a git hash is available. This means if there is a bootstrap bug where a hash is never available, the test is skipped. Oopsie. Clearly, we shouldn't trust bootstrap on whether there should be a hash or not.

I don't know what exactly the conditions are under which a hash is legitimately missing. Probably it involves a build from the released tarball, or so?

I would suggest to remove the ``//@ needs-git-hash`` directive (it is only used by that one test), and instead have the test itself decide whether it can run or not. Maybe it can just check whether a `.git` folder exists? Maybe it can check whether it runs on CI, or runs on *our* CI? I don't know all the context here, but I hope it should be possible to independently determine whether the binary is supposed to have a hash.

Or maybe the simplest answer is to change [this](https://github.com/rust-lang/rust/blob/f42fb435179a01bef886bd187576e73bad35e289/src/bootstrap/src/core/build_steps/test.rs#L2121) code to always pass `--git-hash` on CI. But it seems cleaner to me to not have to trust bootstrap when we are testing whether bootstrap did the right thing.

Cc @rust-lang/bootstrap
Repository: next.js
Issue: [Turbopack] No Media Queries breakpoints in Chrome Device Emulation mode
Labels: bug,Turbopack,linear: turbopack

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/turbopack-forked-plfd58

### To Reproduce

1. Add media quires with CSS Modules
2. Start the dev server via turbopack (next dev --turbo)
3. Open the Chrome and go to the device emulation section in the DevTools
4. Toggle media queries in options

![image](https://github.com/user-attachments/assets/cf75fc63-924e-472c-88ac-8031a68acc66)

5. Created media queries breakpoints will not shown. But all media queries still work

### Current vs. Expected behavior

Current (With Turbopack):

![image](https://github.com/user-attachments/assets/906be968-1584-47b7-b8cb-ffe7ceb1fb78)

Expected (If using without Turbopack): 

![image](https://github.com/user-attachments/assets/1c4a11f7-0424-4dee-a952-295bd645182e)

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
  Available memory (MB): 32601
  Available CPU cores: 12
Binaries:
  Node: 22.11.0
  npm: 10.9.0
  Yarn: N/A
  pnpm: 9.5.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-5c56b873-20241107
  react-dom: 19.0.0-rc-5c56b873-20241107
  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

The problem is that Turbopack, for example, when using `@media screen and (max-width: 768px)` converts this to `@media screen and (width <= 768px)`. Because of this, Chrome doesn't show media breakpoints
Repository: vscode
Issue: Git - Built in git plugin does not work with symlink
Labels: bug,git

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

Version: 1.94.2 (user setup)
Commit: 384ff7382de624fb94dbaf6da11977bba1ecd427
Date: 2024-10-09T16:08:44.566Z
Electron: 30.5.1
ElectronBuildId: 10262041
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Windows_NT x64 10.0.22631

Steps to Reproduce:

1.  init a directory `A` with git 
2.  Use `ln -s` to build a soft link from `A` to `B`
3.  Use vscode to open folder `B`

If I modify something, I cannot see the built in git plugin work. For example, I cannot see the color bar.
Repository: rust
Issue: Documentation uses HRTB lifetime before declaring it
Labels: T-rustdoc,C-bug,A-cross-crate-reexports,A-higher-ranked

The [`str::rsplit_once`](https://doc.rust-lang.org/nightly/std/primitive.str.html#method.rsplit_once) docs say `<P as Pattern>::Searcher<'a>: for<'a> ReverseSearcher<'a>` where the code it's documenting says `for<'a> P::Searcher<'a>: ReverseSearcher<'a>`.

This almost certainly shows up in other places but this is where I first noticed it.
Repository: tauri
Issue: [bug] Run tauri in Linux container over ssh -X fails
Labels: type: bug,platform: Linux,status: needs triage

### Describe the bug

I am building and running it is a Linux Container (incus) using ssh with X forwarding ssh -X name@host.

I have no idea where to look for the problem, every other X application works using X forwarding.
Where do I look for the problem?

   Info Watching /home/svvs/tauri-app/src-tauri for changes...
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 8.18s
Gtk-Message: 20:53:51.344: Failed to load module "canberra-gtk-module"
Gtk-Message: 20:53:51.347: Failed to load module "canberra-gtk-module"
libEGL warning: DRI3: failed to query the version
libEGL warning: DRI2: failed to authenticate

(tauri-app:373): Gdk-WARNING **: 20:53:51.413: The program 'tauri-app' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 282 error_code 1 request_code 155 (unknown) minor_code 1)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)



### Reproduction

I create a incus container
incus init images:debian/12 tauri
I install rust and then tauri according to the directions
Then run $ cargo tauri dev

### Expected behavior

I expect to see a tauri window popup

### Full `tauri info` output

```text
svvs@guirust:~$ cargo tauri info

[✔] Environment
    - OS: Debian 12.0.0 x86_64 (X64)
    ✔ webkit2gtk-4.1: 2.46.3
    ✔ rsvg2: 2.54.7
    ✔ 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-unknown-linux-gnu (environment override by RUSTUP_TOOLCHAIN)
    - node: 18.19.0
    - npm: 9.2.0

[-] Packages
    - tauri 🦀: 2.1.0
    - tauri-build 🦀: 2.0.3
    - wry 🦀: 0.47.0
    - tao 🦀: 0.30.6
    - tauri-cli 🦀: 2.0.4
    - @tauri-apps/api : 2.1.0
    - @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

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:1420/
    - framework: Vue.js
    - bundler: Vite
```


### Stack trace

```text
No stack trace
```


### Additional context

_No response_
Repository: neovim
Issue: Windows and Linux Remote Wezterm Rendering Bug
Labels: bug,tui,display

### Problem

When scrolling horizontally - graphical artifacts left behind if line is longer than screen width.
Sometimes happens when scrolling vertically.
Artifacts can be seen throughout text field, but usually appear in left column where line numbers are housed.
Refer to:
https://github.com/wez/wezterm/issues/6314
After playing with configurations with `nvim --clean` - I observed less artifacts with `set nonumber` and more with `set number`

### Steps to reproduce

Open Wezterm
SSH to a remote Linux server
Open file with characters on one line longer than the width of the window in Neovim with clean or not
Scroll right until horizontal scrolling is triggered

### Expected behavior

No artifacts should be left behind on scrolling.

### Nvim version (nvim -v)

.10.2

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

no

### Operating system/version

Windows or WSL Ubuntu local, Rhel 7, 8, 9 remote via ssh

### Terminal name/version

Wezterm/20241104-083404-51c794ac and current release: 20241015-083151-9ddca7bd

### $TERM environment variable

xterm-256color

### Installation

Both Wezterm builds via Windows and Ubuntu and installed via zip or tar. Version .10.2

Vulkan and DX12 Discreet GPU.
Repository: next.js
Issue: Turbopack loader ignores resource query on aliased imports
Labels: bug,Turbopack

### Link to the code that reproduces this issue

https://github.com/sam3d/turbopack-resource-query-repro

### To Reproduce

Start the application usng `pnpm dev` (turbopack is enabled by default)

### Current vs. Expected behavior

I'd expect both a relative and aliased import to behave the same way:

```tsx
import isHello from "./example.txt?hello";
import shouldBeWorld from "@/app/example.txt?world";

export default async function Page() {
  return (
    <ul>
      <li>isHello: {isHello}</li>
      <li>shouldBeWorld: {shouldBeWorld}</li>
    </ul>
  );
}
```

However they do not, as the resource query is not passed to the loader when accessing with `@/app/...`:

<img width="336" alt="image" src="https://github.com/user-attachments/assets/b96cd793-3b50-4189-9d0c-e5757f78bd0b">


### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.0.0: Mon Aug 12 20:51:54 PDT 2024; root:xnu-11215.1.10~2/RELEASE_ARM64_T6000
  Available memory (MB): 65536
  Available CPU cores: 10
Binaries:
  Node: 20.11.1
  npm: 10.2.4
  Yarn: 1.22.19
  pnpm: 9.12.3
Relevant Packages:
  next: 15.0.4-canary.4 // Latest available version is detected (15.0.4-canary.4).
  eslint-config-next: 15.0.4-canary.4
  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: vscode
Issue: Can’t use Cmd-W to close editors/windows on iPad
Labels: bug,keybindings,ios-ipados

Hi, not sure if this is a Safari, iPadOS or VSCode issue, but as the title says, pressing Cmd-W doesn’t do anything on iPadOS (using vscode.dev as a PWA).
iPad Pro 13-inch (M4), iPadOS 18.1.
Can’t add a custom shortcut either, it doesn’t take Cmd-W (creating a shortcut for other key combos such as Cmd-E seems to work fine).

Version: 1.95.2
Commit: e8653663e8840adaf45af01eab5c627a5af81807
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/18.1 Safari/605.1.15
Embedder: codespaces

<!-- generated by web issue reporter -->
Repository: godot
Issue: Layout / position of children of SubViewportContainer not editable
Labels: bug,topic:gui

### Tested versions

- Reproducible in v4.4.dev.custom_build [40e7fe519]

### System information

Godot v4.4.dev (40e7fe519) - Windows 10.0.19045 - Multi-window, 1 monitor - Vulkan (Forward+) - dedicated Radeon RX 580 Series (Advanced Micro Devices, Inc.; 31.0.21912.14) - AMD Ryzen 5 2600 Six-Core Processor (12 threads)

### Issue description

It is not possible to position other children of a SubViewportContainer other than the SubViewport using the editor. It is however possible to do so via script. If more than the SubViewport child is inside the SubViewportContainer it seems like the preview in the editor is broken as well as the layout of nested nodes in the other SubViewportContainer child node.

![image](https://github.com/user-attachments/assets/ac0f3403-94e4-4b35-afa5-dfa890757f16)

In the image above the selected red area should be positioned inside the `vp_container` node with its layout intact (notice the space between the left and right side of the nested nodes)

Running the project reveals the following result:

![image](https://github.com/user-attachments/assets/532ae2d2-a79e-4d2a-ab90-31465af9e8c6)

The layout of the nested nodes is lost. This can be circumvented by running 
```gd
set_anchors_and_offsets_preset(Control.PRESET_FULL_RECT, Control.PRESET_MODE_MINSIZE, 2)
```
on the ``viewport_hbox`` node. This is also done in the C++ source code for the [Advanced import settings dialog](https://github.com/godotengine/godot/blob/0f5f3bc9546b46b2029fc8896dc859697f1eab97/editor/import/3d/scene_import_settings.cpp#L1621-L1778). Another option would be to save the ``viewport_hbox`` node as a separate scene and edit the layout there to full rect anchor. 

Both are workarounds though. This should be possible in-editor as well. The SubviewportContainer doesn't offer these solutions though and this bug results.

### Steps to reproduce

1. Open the MRP
2. Try to move the position / layout of the children inside the ``vp_container`` node.

### Minimal reproduction project (MRP)

[MRP-SubViewportContainer-Bug.zip](https://github.com/user-attachments/files/17693924/MRP-SubViewportContainer-Bug.zip)
Repository: langchain
Issue: DOC: DSPy integration with LangChain
Labels: 🤖:docs

### URL

https://python.langchain.com/docs/integrations/providers/dspy/

### Checklist

- [X] I added a very descriptive title to this issue.
- [X] I included a link to the documentation page I am referring to (if applicable).

### Issue with current documentation:

Hi, 
I noticed from DSPy side, this integration is no longer supported. 
[DSPy reference](https://github.com/stanfordnlp/dspy/blob/main/examples/tweets/compiling_langchain.ipynb)

As mentioned in the notebook:

> This integration with LangChain is no longer supported.

May I clarify if it is same from LangChain side? Does this integration still supported? Thanks in advance.


### Idea or request for content:

_No response_
Repository: terminal
Issue: How to avoid changing cursorShape when focus terminal window if I set `unfocusedAppearance`
Labels: Help Wanted,Issue-Bug,Area-TerminalControl,Product-Terminal

### Windows Terminal version

1.21.2911.0

### Windows build number

10.0.22631.0

### Other Software

NVIM v0.10.2

### Steps to reproduce

1. snippet in settings.json
  ```json
   "opacity": 50,
   "cursorShape": "underscore",
   "unfocusedAppearance": {
        "opacity": 90
   },
   ```
2. open `nvim`, current cursor shape is `block`
3. press `alt`+`tab` to focus another window, then press it again to focus back to terminal
4. cursor shape changes to `underscore`. (If I delete the `unfocusedAppearance` in settings.json, the cursor shape does not change after focus back)

### Expected Behavior

When I set `unfocusedAppearance`, do not change my cursor shape after focus back to terminal window.

### Actual Behavior

Cursor shape changes to `underscore` that I set in `cursorShape`.
Repository: ollama
Issue: vram usage does not go back down after model unloads
Labels: bug,amd,needs more info

### What is the issue?

when i set keep alive to 0 the memory usage does not go all the way back down. also it uses system ram when vram still avalible

gpu 7800xt
platform windows
rocm version 6.1

### OS

Windows

### GPU

AMD

### CPU

AMD

### Ollama version

0.4.1
Repository: rust
Issue: Code size regression (opt-level=z) after 1.82.0
Labels: A-LLVM,P-low,T-compiler,C-bug,regression-untriaged

Code:

```rust
#![no_main]
#[no_mangle]
pub struct Point {
    x: i32,
    y: i32,
}

#[no_mangle]
pub fn f(a: Point) -> i32 { 
    if a.x > 0 && a.y < 0 || a.x < 0 && a.y > 0 {
        a.x * a.y
    } else {
        a.x + a.y
    }
}
```

Link: https://godbolt.org/z/ocs7aGMxK
Repository: PowerToys
Issue: In v0.86.0 unbounded mouse cannot drag-and-drop sort re-layout
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

v0.86.0

### Installation method

GitHub

### Running as admin

None

### Area(s) with issue?

Mouse Without Borders

### Steps to reproduce

In v0.86.0 unbounded mouse cannot drag and drop to sort and re-layout, as shown below:
![Image](https://github.com/user-attachments/assets/b5e5a7e5-e045-4727-bfed-0c9a1c58a003)
This is my actual computer location layout, which is normal on the machine:
![Image](https://github.com/user-attachments/assets/2df555e5-da02-41f3-85ff-eccad82f6479)
However, the display on the main controller is the opposite, and it cannot be dragged. Obviously, the controller is on the right, but I can only move the mouse from the left to another controller, which is very awkward. In fact, the other computer is on my right. Shouldn't it slide from the left to the right?
![Image](https://github.com/user-attachments/assets/ec576207-a47e-4b80-b782-bddd3159f340)




### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: PowerToys
Issue: Keyboard and Mouse Freeze
Labels: Needs-Triage

### Description of the new feature / enhancement

Quick shortcut to disable all input from keyboard and mouse except the hotkey combination.

### Scenario when this would be used?

Useful when cleaning keyboard or watching movie to prevent distraction.

### Supporting information

[BlueLife KeyFreeze](https://www.sordum.org/7921/bluelife-keyfreeze-v1-4-block-keyboard-and-mouse/)
Repository: rust
Issue: Code size regression iterating an array (opt-level=z) after 1.82.0
Labels: A-LLVM,P-low,T-compiler,C-bug,I-heavy,regression-untriaged

Code:

```rust
#![no_main]
#[no_mangle]
pub fn f(a: i32) -> i32 { a + a }

#[no_mangle]
pub fn g(a: [i32; 5]) -> i32 {
    let mut sum = 0;
    let arr = [1, 2, 3, 4, 5];
    for i in a.iter().chain(arr.iter()) {
        sum += i;
    }
    sum
}
```

Link: https://godbolt.org/z/14KM5KnPx
Repository: rust
Issue: A release store operation synchronizes with an acquire load operation instead of the reverse
Labels: A-docs,T-libs

### Location

In the document [park](https://doc.rust-lang.org/std/thread/fn.park.html#memory-ordering)
> Calls to park synchronize-with calls to unpark, meaning that memory operations performed before a call to unpark are made visible to the thread that consumes the token and returns from park. 
>
> In atomic ordering terms, unpark performs a Release operation and park performs the corresponding Acquire operation. Calls to unpark for the same thread form a release sequence.


Since the memory order in Rust is from C++, in C++ standard, [[atomics.order] p2](https://eel.is/c++draft/atomics.order#2) says: 
> An atomic operation A that performs **a release operation** on an atomic object M **synchronizes with** an atomic operation B that performs an **acquire operation** on M and takes its value from any side effect in the release sequence headed by A.


Since unpark performs a Release operation and park performs the corresponding Acquire operation, by the definition of the wording *synchronizes with*, we should say
> calls to unpark synchronize-with calls to park.

### Summary

> calls to unpark synchronize-with calls to park.

because a release store operation synchronize with an acquire load operation
Repository: terminal
Issue: The weight of CJK characters in the title of the active tab is inappropriate
Labels: Issue-Bug,Area-UserInterface,Product-Terminal

### Windows Terminal version

Source

### Windows build number

22621/27744

### Other Software

_No response_

### Steps to reproduce

The default font in Simplified Chinese user environments is Microsoft Yahei UI. The current font weight causes the Chinese characters in the titles to be unclear.

### Expected Behavior

![Image](https://github.com/user-attachments/assets/9b346f03-7bc9-42e6-8305-e5bcb723b3ef)
100% DPI scale, right is the active tab
![Image](https://github.com/user-attachments/assets/4221ff2f-71ab-4545-9d5b-0446573751db)
200% DPI scale, right is the active tab

### Actual Behavior

Set FontWeight to Normal, Medium, or Bold (instead of Default or SemiLight).
Repository: langchain
Issue: DOC: sql-ollama leads to removed page
Labels: 🤖:docs

### URL

https://python.langchain.com/docs/templates/sql-ollama/

### Checklist

- [X] I added a very descriptive title to this issue.
- [X] I included a link to the documentation page I am referring to (if applicable).

### Issue with current documentation:

I noticed that the link to the SQL-Ollama documentation (https://python.langchain.com/v0.1/docs/templates/sql-ollama) suggests checking a newer version, but the link seems to lead to a removed page.
Can you let me know if there’s an updated version available, or if this is just a temporary removal?

### Idea or request for content:

_No response_