sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: ollama
Issue: HIP_VISIBLE_DEVICES vs ROCR_VISIBLE_DEVICES
Labels: bug,amd,needs more info

### What is the issue?

I have 8 AMD 7900XTX cards in llama.cpp to limit access to certain GPUs, I use the HIP_VISIBLE_DEVICES command and it works correctly. However, if I want to limit GPU access for Ollama, I get an error with llama3.2-vision. To make it work correctly, I have to give it access to all GPUs and then limit access via ROCR_VISIBLE_DEVICES.

### OS

Linux

### GPU

AMD

### CPU

AMD

### Ollama version

0.4.0-pre
Repository: tauri
Issue: [bug] Issue with app.handle().exit(0) Not Working When Running as Windows Service
Labels: type: bug,platform: Windows,status: needs triage

### Describe the bug

I am currently running my Tauri app as a Windows service (without a window), and I am encountering an issue when trying to close the app using the app.handle().exit(0) command.

### Reproduction

https://github.com/arihav/tauri-app-example

### Expected behavior

The app should exit successfully without any issues.

### Full `tauri info` output

```text
[✔] Environment
    - OS: Windows 10.0.22631 x86_64 (X64)
    ✔ WebView2: 130.0.2849.56
    ✔ MSVC: Visual Studio Build Tools 2022
    ✔ 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 (environment override by RUSTUP_TOOLCHAIN)
    - node: 21.1.0
    - yarn: 1.22.22
    - npm: 10.2.0

[-] Packages
    - tauri 🦀: git+https://github.com/tauri-apps/tauri?rev=ae024b829972609ac565e54bf4b03d4e4b5e2524#ae024b829972609ac565e54bf4b03d4e4b5e2524 (2.0.6)
    - tauri-build 🦀: No version detected
    - wry 🦀: 0.46.3
    - tao 🦀: 0.30.3
    - tauri-cli 🦀: 2.0.4
    - @tauri-apps/api : 1.6.0 (outdated, latest: 2.0.3)
    - @tauri-apps/cli : 2.0.4

[-] Plugins
    - tauri-plugin-log 🦀: 2.0.1
    - @tauri-apps/plugin-log : 2.0.0
    - tauri-plugin-autostart 🦀: 2.0.1
    - @tauri-apps/plugin-autostart : 2.0.0
    - tauri-plugin-localhost 🦀: 2.0.1
    - @tauri-apps/plugin-localhost : not installed!

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../out
    - devUrl: http://localhost:3002/
    - framework: React (Next.js)
    - bundler: Webpack
```


### Stack trace

_No response_

### Additional context

The exit process should trigger two events: RunEvent::ExitRequested and RunEvent::Exit. Currently, RunEvent::ExitRequested is called, but RunEvent::Exit is not. I think the issue might be occurring within the event loop of TAO.
Repository: PowerToys
Issue: EXR and HDR Thumbnail Support
Labels: Needs-Triage

### Description of the new feature / enhancement

Is there anyone who contributes that could add EXR and HDR image thumbnail support to PowerToys? Perhaps there are more 32bit image filetypes that could be integrated also.

I feel like this is something that has been requested to Microsoft for quite some time without any result.


### Scenario when this would be used?

In File Explorer it would be great to see preview thumbnails of .exr files. And perhaps .hdr image files too. These are image file formats often used by VFX professionals but thumbnails for these are not native supported in Windows 11 - despite EXR being an open source file format (as far as I am aware).

### Supporting information

_No response_
Repository: pytorch
Issue: nn.LSTM documentation
Labels: module: nn,triaged,topic: docs

### 📚 The doc issue

Hi. Could you please check if there are any inaccuracies in the documentation of [nn.LSTM](https://pytorch.org/docs/stable/generated/torch.nn.LSTM.html#torch.nn.LSTM) related to the main description and output:

### **main description**:
> If `proj_size > 0` is specified, LSTM with projections will be used. This changes the LSTM cell in the following way. First, the dimension of $h_{t}$ will be changed from `hidden_size` to `proj_size` (dimensions of $W_{hi}$ will be changed accordingly).
Second, the output hidden state of each layer will be multiplied by a learnable projection matrix: $h_{t}=W_{hr}h_{t}$.

From the description it may seem that the projection applies only to output hidden state (after the last step), but in fact, judging by the size of **output**, it is applied after each step.

Also it is probably necessary to indicate that the dimensions also change for matrices **W_hf|W_hg|W_ho|W_ii|W_if|W_ig|W_io** (not only for $W_{hi}$) as can be seen from the description **weight_ih_l[k]** и **weight_hh_l[k]**.

the description should probably be:
> If `proj_size > 0` is specified, LSTM with projections will be used. This changes the LSTM cell in the following way.
The dimension of hidden state of each step of each layer will be changed from `hidden_size` to `proj_size` by multiplying by a learnable projection matrix: $h_{t}=W_{hr}h_{t}$ (dimensions of other matrices will be changed accordingly).



### **h_0**, **c_0**:
> tensor of shape ... for unbatched input or ... containing the final hidden state for each element in the sequence.

In fact, it does not contain a hidden state for each element of the sequence (only for the last element, that is, the last step).

> When bidirectional=True, h_n will contain a concatenation of the final forward and reverse hidden states, respectively.

Perhaps it would be better to clarify that the concatenation is along the 1st axis so that it is not analogous to the concatenation for `output` where the output directions are concatenated for each step.
Or remove word 'concatenation' since it doesn't actually happen (the hidden vectors of the forward and backward passes are simply enumerated along the 1st axis)











### Suggest a potential alternative/fix

_No response_

cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki
Repository: TypeScript
Issue: The error for allowImportingTsExtensions does not reference rewriteRelativeImportExtensions
Labels: Suggestion,Help Wanted

### 🔎 Search Terms

- error TS5096
- allowImportingTsExtensions
- rewriteRelativeImportExtensions
- tsconfig
- diagnostics
- intellisense

### 🕗 Version & Regression Information

- This changed between versions N/A and 5.7.0-beta
- This changed in commit or PR https://github.com/microsoft/TypeScript/pull/59767
- This is the behavior in every version I tried, and I reviewed the FAQ for entries for `allowImportingTsExtensions` and `rewriteRelativeImportExtensions`
- I was unable to test this on prior versions because it was only introduced in 5.7


### ⏯ Playground Link

_No response_

### 💻 Code

tsconfig.json with diagnostic error:

```json
{
  "compilerOptions": {
    "module": "Node16",
    "moduleResolution": "Node16",
    "allowImportingTsExtensions": true,
  }
}
```

### 🙁 Actual behavior

When specifying `allowImportingTsExtensions` as above, I get an error, as intended:

```
tsconfig.json:5:35 - error TS5096: Option 'allowImportingTsExtensions' can only be used when either 'noEmit' or 'emitDeclarationOnly' is set.
``` 

However, if I add `"rewriteRelativeImportExtensions": true` to the same tsconfig, the error goes away, which is contrary to the error message.

The _behavior_ seems correct, but the error message seems incomplete or inconsistent.

---

At the same time, intellisense for `allowImportingTsExtensions` in VSCode reports:

> Allow imports to include TypeScript file extensions. Requires '--moduleResolution bundler' and either '--noEmit' or '--emitDeclarationOnly' to be set.

This is only mentioned as a requirement in intellisense, but not in the error message.

### 🙂 Expected behavior

I would expect the message to reference `rewriteRelativeImportExtensions` as one of the conditions that allow for `allowImportingTsExtensions`. 

I am not sure whether `--moduleResolution bundler` is required, but at least unifying the intellisense and diagnostic would be good. 

The combination of factors seems to be "`noEmit` or `emitDeclarationOnly` or `rewriteRelativeImportExtensions`", but I am not sure what the exact new diagnostic message should be 😅

(I don't mean to be nitpicky! I tend to learn best from intellisense and the diagnostics errors, so I was on the lookout for them when trying out the `5.7.0-beta` and `rewriteRelativeImportExtensions` 😌)

### Additional information about the issue

_No response_
Repository: neovim
Issue: Treesitter `on_changedtree` has no changes if lines are dropped
Labels: bug,treesitter

### Problem

The `on_changedtree` callback gets called, but the table of ranges if empty if lines were removed. If the lines were instead changed or new ones added there will be ranges.

### Steps to reproduce

Take this `init.lua` file:

```lua
local ts = vim.treesitter

local parser = ts.get_parser(0, 'lua')
parser:register_cbs {
	on_changedtree = function(changes, tree)
		print(vim.inspect(changes), vim.inspect(tree))
	end
}
vim.treesitter.start()
```

Now open this Lua file:

```lua
print {
	{
	},
	{
	},
}
```

Execute this command: `%s/\v\{\n\s+/{` to remove the line break after the opening brace. The callback will print `{}, <userdata 1>`. On the other hand, if we add an extra line break (`%s/\v\{\n\s+/{\r\r`) or even a space (`%s/\v\{/{ ` note the trailing space) we do get ranges.

### Expected behavior

Something should be reported since we are not merely deleting lines. In my example the existing lines do change, so I would expect to at least get ranges for them.

### Nvim version (nvim -v)

NVIM v0.10.2

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

N/A

### Operating system/version

Void Linux

### Terminal name/version

alacritty 0.14.0

### $TERM environment variable

alacritty

### Installation

Void repos
Repository: rust
Issue: Tracking issue for release notes of #129347: #[inline(never)] does not work for async functions
Labels: A-LLVM,A-codegen,T-lang,relnotes,A-async-await,relnotes-tracking-issue


This issue tracks the release notes text for #129347.

### Steps

- [ ] Proposed text is drafted by PR author (or team) making the noteworthy change.
- [ ] Issue is nominated for release team review of clarity for wider audience.
- [ ] Release team includes text in release notes/blog posts.

### Release notes text

The responsible team for the underlying change should edit this section to replace the automatically generated link with a succinct description of what changed, drawing upon text proposed by the author (either in discussion or through direct editing).

````markdown
# Category (e.g. Language, Compiler, Libraries, Compatibility notes, ...)
- [#[inline(never)] does not work for async functions](https://github.com/rust-lang/rust/issues/129347)
````

> [!TIP]
> Use the [previous releases](https://doc.rust-lang.org/nightly/releases.html) categories to help choose which one(s) to use.
> The category will be de-duplicated with all the other ones by the release team.
>
> *More than one section can be included if needed.*

### Release blog section

If the change is notable enough for inclusion in the blog post, the responsible team should add content to this section.
*Otherwise leave it empty.*

````markdown
````

cc @michaelwoerister -- origin issue/PR authors and assignees for starting to draft text
Repository: rust
Issue: tweak search result order
Labels: T-rustdoc,C-enhancement,A-rustdoc-search

a search for [`Result::Ok`](https://doc.rust-lang.org/nightly/std/index.html?search=Result%3A%3AOk) will show first the method `result::Result::ok`, then several aliases such as `io::Result::Ok`, then `result::Result::Ok`, then more aliases.

there are two changes required to present a more logical order:
* [ ] prioritize variants over methods (inspired by [this discussion](https://github.com/rust-lang/rust/pull/132569#issuecomment-2453571537))
* [ ] de-prioritize type aliases and variants/fields thereof.

![search results](https://github.com/user-attachments/assets/a4906442-0c9a-4790-a7b3-136601b7f732)
Repository: rust
Issue: temporary value dropped while borrowed
Labels: T-compiler,regression-from-stable-to-stable,C-bug,WG-const-eval

### Code

I tried this code:

```rust
pub const fn concat(_x: &[u8], _y: &[u8]) -> [u8; 1024] {
    [0u8; 1024]
}

const _: &[u8] = &concat(
    if b"".len() > 0 {
        &concat(b"", b"")
    } else {
        b""
    },
    b""
);
```

I expected to see this happen: compiles

Instead, this happened: fails to compile with the following error:

```
error[E0716]: temporary value dropped while borrowed
 --> <source>:7:10
  |
5 | const _: &[u8] = &concat(
  |                   ------ borrow later used by call
6 |     if b"".len() > 0 {
7 |         &concat(b"", b"")
  |          ^^^^^^^^^^^^^^^^ creates a temporary value which is freed while still in use
8 |     } else {
  |     - temporary value is freed at the end of this statement
  |
  = note: consider using a `let` binding to create a longer lived value
```

### Version it worked on

It most recently worked on: 1.78.0

### Version with regression

<!--
Provide the version you are using that has the regression.
-->

`rustc --version --verbose`:
```
rustc 1.79.0 (129f3b996 2024-06-10)
```

@rustbot modify labels: +regression-from-stable-to-stable -regression-untriaged
Repository: excalidraw
Issue: Change keybind for panning
Labels: keyboard

The 3 ways of panning I am aware of are h, middle mouse, and spacebar.
I have a split keyboard and the spacebar and h key are located on the right keyboard and mouse is accessible with my right hand only. This means I can't pan without putting my stylus down and either pushing the spacebar, h key, or mouse with my right hand. 

Other keybinds work in combination with a stylus because they are located on the left side of the keyboard: text is on t, brush is on x, eraser is on e, arrow is on a.

I looked at another issue and it doesn't seem like keyboard shortcuts will be added soon, but I want to open this issue to potentially get a better keybind for panning specifically that is located on the left side of the keyboard.
Repository: godot
Issue: WebRTCMultiplayerPeer reports as server when initialized with create_client
Labels: bug,topic:multiplayer

### Tested versions

- Reproduced in v4.3.stable.official [77dcf97d8]

### System information

Godot v4.3.stable - macOS 15.0.0 - GLES3 (Compatibility) - Intel(R) Iris(TM) Plus Graphics OpenGL Engine - Intel(R) Core(TM) i7-1068NG7 CPU @ 2.30GHz (8 Threads)

### Issue description

**tldr**: When using `WebRTCMultiplayerPeer` initialized with `create_client`, the `multiplayer.is_server()` call can return true after the connection to the server is closed.

This seems to happen if a client-server connection is established, and then the server is disconnected. [`WebRTCMultiplayerPeer::get_unique_id()` will return 1, regardless of the network mode](https://github.com/godotengine/godot/blob/1bffd6c73b44b85e5889f54e14b2193940cf5bb1/modules/webrtc/webrtc_multiplayer_peer.cpp#L256). Before the disconnect, `multiplayer.is_server()` will return `false`. When a disconnect happens, it will start returning `true` ( [because it compares the result of `get_unique_id` to 1](https://github.com/godotengine/godot/blob/1bffd6c73b44b85e5889f54e14b2193940cf5bb1/scene/main/multiplayer_api.h#L76) )

Two issues with this are:
- this is undocumented
- there seems to be an inconsistency in behaviour with other multiplayer peers (e.g. [WebSocketMultiplayerPeer](https://github.com/godotengine/godot/blob/1bffd6c73b44b85e5889f54e14b2193940cf5bb1/modules/websocket/websocket_multiplayer_peer.cpp#L173) will never flip; [ENetMultiplayerPeer](https://github.com/godotengine/godot/blob/1bffd6c73b44b85e5889f54e14b2193940cf5bb1/modules/enet/enet_multiplayer_peer.cpp#L439) I think would flip in the opposite direction when inactive)

I spotted this because I was relying on `multiplayer.is_server()` to determine when to make some RPC calls, or which signals to subscribe to. There is an error message about the disconnect state, but it was not obvious that it would affect the network mode reporting.

While this seems like a bug to me, I don't know enough about Godot or WebRTC to be confident this needs a change. If you think this is not an issue, I'm happy to open a godot-docs PR to clarify this behaviour.

### Steps to reproduce

- Create a new multiplayer peer: `var rtc_mp = WebRTCMultiplayerPeer.new()`
- Initialize as a client: `rtc_mp.create_client(2)`
- Assign to multiplayer `multiplayer.multiplayer_peer = rtc_mp`
- `multiplayer.is_server()` will return `false` until the server disconnects
- Disconnect server
- Verify that `multiplayer.is_server()` returns `true` (but it should return `false`, because we initialized with `create_client`)

There is an attached MRP, which you can just run and wait a few seconds, and see the console output.

### Minimal reproduction project (MRP)

[webrtcrepro.zip](https://github.com/user-attachments/files/17612222/webrtcrepro.zip)

To run this locally you might need the [webrtc-native](https://github.com/godotengine/webrtc-native) extension. I'm not including it in the MRP cause it's ~300 mb with all the libs.
Repository: electron
Issue: Linux - Provide window borders and title bar buttons approprate for the user's desktop environment
Labels: enhancement :sparkles:

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

### Problem Description

It is my understanding that Windows and macOS impose window border shapes and appearances through their respective window managers. These operating systems also provide native title bar buttons upon request or overlay them automatically.

In contrast, Linux platforms delegate the responsibility for border styles, title bar buttons, their positioning, appearance, and quantity to the Electron application itself.

This approach shifts the burden of proper desktop integration to the application developer. Often, developers opt for a simplified solution: an undrawn square border with three generic buttons (minimize, maximize, and close) positioned in the top-right corner. However, this generic approach may not align with user preferences or conform to the conventions of the current desktop environment.

![Image](https://github.com/user-attachments/assets/80f489c3-9db0-457a-a93a-0eabc7695a59)

### Proposed Solution

Electron should provide a platform-specific window border and apply two sets of title bar buttons (left and right) to the application upon request.

This system could support multiple desktop environments with unique title bar styling, including but not limited to:
* GNOME
* KDE
* Elementary
* COSMIC

While the extent of matching user preferences may vary, this approach would require exposing a generic interface to the underlying application. This interface would automatically apply the correct title bar button styling and appearance using a strategy pattern.

### Alternatives Considered

I've explored the possibility of developing a Web Components library that would provide three key components:

1. A window wrapper component:
   - Implements the correct border (and shadow, if necessary) for the platform
   - Optionally includes a simple title bar

2. A component for the left bank of title bar buttons

3. A component for the right bank of title bar buttons

This approach would enable developers to incorporate environment-specific window controls without the need to create custom solutions specifically for the Linux platform.


### Additional Information

_No response_
Repository: terminal
Issue: [Terminal Chat] The LLM receives confusing information about shell
Labels: Issue-Bug,Product-Terminal,Needs-Tag-Fix,Area-Chat

### Windows Terminal version

1.23.3061.0

### Windows build number

10.0.22631.0

### Other Software

- Ubuntu 22.04.5 LTS - installed as the default Ubuntu distribution in WLS2, then gradually updated
- GNU bash, version 5.1.16(1)-release (x86_64-pc-linux-gnu)
- GitHub Copilot

### Steps to reproduce

1. Use the default Ubuntu distribution in WSL.
2. Open a terminal for it.
3. Start a Terminal Chat.
4. After few interactions it could mention that it has information that I am using a shell named `ubuntu.exe`.
5. It seems that a sequence of these two user messages lead to responses like below: `Hello`, `Please explain the error.`

![Image](https://github.com/user-attachments/assets/efd246b4-67bf-4f0e-943b-979006b409e9)

### Expected Behavior

The chatbot should not behave is if it received wrong information about the shell being used. It should either have information that I am using Ubuntu distribution of Linux (and maybe version) or that I am using Bash shell in Ubuntu Linux.

It should probably be allowed to modify parts of the initial prompt including information about the shell and operating system. This setting should be per profile.

### Actual Behavior

The Terminal Chat probably receives confusing information about the shell in the terminal window in its preconfigured initial prompt.

When I am using the default Ubuntu WSL distribution with the default `bash` shell the GitHub Copilot responds as if it received information that I am using shell named `ubuntu.exe`:

![Image](https://github.com/user-attachments/assets/efd246b4-67bf-4f0e-943b-979006b409e9)

With Ubuntu 24.04 GitHub Copilot is confused even more:

![Image](https://github.com/user-attachments/assets/eb803aec-d4ac-4a24-9001-f1f0804d9e4f)
Repository: next.js
Issue: Turbopack fails to pack css.modules with utf8-bom encoding
Labels: bug,Turbopack,linear: turbopack

### Link to the code that reproduces this issue

https://github.com/Martinii89/nextjs-turbo-bom-bug

### To Reproduce

1. Start the application in dev mode using the --turbo option
2. The one page uses two identical css classes from two different css module files. One is encoded with utf8. The other with utf8-bom
3. Only the css module with utf8 encoding is applied correctly
![image](https://github.com/user-attachments/assets/23194bed-2b6b-4e7b-8cb0-92bcb5eae193)

Screenshot of the css styles in the devtools of chrome shows a error on one of the styles
![image](https://github.com/user-attachments/assets/be0de444-3b2d-4d20-9bfd-a92e32c5066f)



### Current vs. Expected behavior

Expected behaviour is that the css modules with utf8-bom encoding does not fail to apply. Currently the first selector will become invalid when utf8-bom is used. 

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Home
  Available memory (MB): 16222
  Available CPU cores: 12
Binaries:
  Node: 20.13.1
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 15.0.3-canary.4 // Latest available version is detected (15.0.3-canary.4).
  eslint-config-next: N/A
  react: 19.0.0-rc-7c8e5e7a-20241101
  react-dom: 19.0.0-rc-7c8e5e7a-20241101
  typescript: 5.3.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_