sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: neovim
Issue: LSP: user can easily discover, define client commands
Labels: enhancement,lsp,architecture

# Problem

LSP servers have various custom capabilities and commands that are not part of the LSP spec, e.g.:

- "go to source definition" (typescript) [#28328](https://github.com/neovim/neovim/issues/28328)
- "update imports" [#20784](https://github.com/neovim/neovim/issues/20784)
- "open docs" (rust) [#1921](https://github.com/neovim/nvim-lspconfig/pull/1921)

The current situation with nvim-lspconfig is that 10+ lines of code are needed to define each command or custom capability. That's unsustainable, we can't maintain that for 100s of LSP servers.


See also:

- https://github.com/neovim/neovim/pull/30932
- https://github.com/neovim/nvim-lspconfig/issues/1937
- https://github.com/neovim/neovim/issues/26045#issuecomment-1811489889
- https://github.com/neovim/neovim/pull/18506

# Expected behavior

Reduce friction for users to use custom (off-spec) server capabilities/commands:

1. Provide a way to discover/iterate through ~~server capabilities~~ custom (off-spec) commands.
2. Improve the `commands` interface and/or provide util functions so that defining commands/aliases to call custom (off-spec) server commands requires 2x less code.

## Questions

- `vim.lsp.get_active_clients()[1].server_capabilities` and `vim.lsp.get_active_clients()[1].commands` already exist. What is the remaining friction? Why do we get requests like [this](https://github.com/neovim/nvim-lspconfig/pull/1921)? Do we simply need some hints in the documentation that guide users? Do we need a util function that makes it easy for users to define mappings around server commands/capabilities?
    - Answer: see https://github.com/neovim/neovim/issues/28329#issuecomment-2054151019

## Possible interface

From https://github.com/neovim/nvim-lspconfig/issues/1937#issuecomment-1481033025 (the names don't matter right now, they are just pseudo-code; the point is that we need a generic interface for (1) iterating custom shit from the LSP server and (2) enabling users to create their own mappings to this stuff): 

> some sort of "sub-command" entrypoint so that langserver-specific commands can be discovered. E.g. 
>
> * `:Lsp <tab>` would complete available langserver-specific commands. 
> * `:LspCapabilties <tab>` would show... something.
Repository: flutter
Issue: Proposal for  `SwitchListTile` to Support setting the switch size
Labels: c: new feature,framework,f: material design,c: proposal,P3,team-design,triaged-design

### Use case

SwitchListTile Supports setting the switch size

i can wrap SwitchListTile with Transform.scale, but the scale would be applied to entire widget, ie, to the text as well, that messes up the size of entire SwitchListTile widget,


This will affect the layout of the entire SwitchListTile. How can I only change the switch size

### Proposal

SwitchListTile Supports setting the switch size
Repository: stable-diffusion-webui
Issue: [Feature Request]: Release with embedded Python
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 ?

Some projects releases on Windows that I use have **embedded Python**, such as [RVC-GUI](https://github.com/Tiger14n/RVC-GUI/releases/tag/Windows-pkg) or [ComfyUI](https://github.com/comfyanonymous/ComfyUI/releases). Can this be implemented for this project as well?

### Proposed workflow

Embed required packages and put them in the `Releases` tab (or create a different branch for such)

### Additional information

_No response_
Repository: rust
Issue: Missed Optimization when Matching on Complete Unicode Character Ranges with an Unreachable Arm
Labels: I-slow,A-codegen,T-compiler,C-bug,I-heavy,C-optimization

Hello, I've noticed a bug with rustc:
```rust
#[inline(never)]
pub fn with_unreachable(c: char) -> bool {
    match c {
        ('\0'..='\u{d7ff}') => true,
        ('\u{e000}'..='\u{10ffff}') => true,
        _ => false
    }
}

#[inline(never)]
pub fn without_unreachable(c: char) -> bool {
    match c {
        ('\0'..='\u{d7ff}') => true,
        ('\u{e000}'..='\u{10ffff}') => true,
    }
}
```
which outputs:
```assembly
example::with_unreachable::hd01eb55f04576fdc:
  cmp edi, 55296
  setb cl
  add edi, -57344
  cmp edi, 1056768
  setb al
  or al, cl
  ret

example::without_unreachable::h31c5b4f665ccfd93:
  mov al, 1
  ret
```

Gives a compiler warning telling us that `_ => false` is unreachable, but it seems that the optimiser isn't privy to this? We'd expect `without_unreachable` and `with_unreachable` to give the same assembly output.

### Meta
The above is built with rustc 1.77.0 and flags `-C debuginfo=1 --emit asm -Cllvm-args=--x86-asm-syntax=intel --crate-type rlib --color=always --edition 2021 -C opt-level=3`

A link to the godbolt snippet: https://godbolt.org/z/hf7jje83W
Repository: godot
Issue: Printing in the same frame the window closes gives no output
Labels: discussion,topic:editor

### Tested versions

- Tested in: 4.2.2 rc2 and 4.2.2 rc3

### System information

Godot v4.2.2.rc3 - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3050 6GB Laptop GPU (NVIDIA; 31.0.15.4601) - 13th Gen Intel(R) Core(TM) i5-13450HX (16 Threads)

### Issue description

If I try to print anything on the same frame the game window closes in the editor, nothing gets printed. For example, if I run a scene with the following script attached, I would expect to see "I'm exiting the tree" in the output console after pressing ESCAPE:

```gdscript
extends Node


func _process(_delta: float) -> void:
	if Input.is_action_just_pressed("ui_cancel"):
		print("I'm exiting the tree")
		get_tree().quit()
```

However, upon testing, the output console is empty. If I add an `await get_tree().create_timer(0.1).timeout` statement after the print line, however, it prints to the output as expected:

```gdscript
extends Node


func _process(_delta: float) -> void:
	if Input.is_action_just_pressed("ui_cancel"):
		print("I'm exiting the tree")
		await get_tree().create_timer(0.1).timeout
		get_tree().quit()
```

It also works if I add a `breakpoint` in place of the `await get_tree().create_timer(0.1).timeout`, so it seems that Godot just doesn't like printing stuff in the same frame the window closes.

I have also tested using the `_exit_tree` function and the behaviour is the same. The following code does not print anything when I press ESCAPE:

```gdscript
extends Node


func _process(_delta: float) -> void:
	if Input.is_action_just_pressed("ui_cancel"):
		get_tree().quit()


func _exit_tree() -> void:
	print("I'm exiting the tree")
```

But if I add a breakpoint, it works correctly:


```gdscript
extends Node


func _process(_delta: float) -> void:
	if Input.is_action_just_pressed("ui_cancel"):
		get_tree().quit()


func _exit_tree() -> void:
	print("I'm exiting the tree")
	breakpoint
```

### Steps to reproduce

1. Create a new scene with a root node of type `Node`;
2. Attach the following script to that node:
```gdscript
extends Node


func _process(_delta: float) -> void:
	if Input.is_action_just_pressed("ui_cancel"):
		print("I'm exiting the tree")
		get_tree().quit()
```
3. Press play, then press the ESCAPE key;
4. Check the output console and verify that nothing got printed;
5. Change the script to the following:
```gdscript
extends Node


func _process(_delta: float) -> void:
	if Input.is_action_just_pressed("ui_cancel"):
		print("I'm exiting the tree")
		await get_tree().create_timer(0.1).timeout
		get_tree().quit()
```
6. Press play, then press the ESCAPE key;
7. Check the output console and verify that "I'm exiting the tree" was printed correctly.

### Minimal reproduction project (MRP)

[print-on-close-test.zip](https://github.com/godotengine/godot/files/14971212/print-on-close-test.zip)
Repository: tensorflow
Issue: `Check failed` in `tf.raw_ops.ScatterNd` and `tf.scatter_nd` when the rank of `indices` > 2. 
Labels: stat:awaiting tensorflower,type:bug,comp:ops,TF 2.16

### Issue type

Bug

### Have you reproduced the bug with TensorFlow Nightly?

Yes

### Source

binary

### TensorFlow version

tf 2.15

### Custom code

No

### OS platform and distribution

Linux Ubuntu 20.04

### Mobile device

_No response_

### Python version

3.10

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

`Check failed` in `tf.raw_ops.ScatterNd` and `tf.scatter_nd` when the rank of `indices` > 2, which causes the program to crash. See the colab link below for details.

### Standalone code to reproduce the issue

```shell
https://colab.research.google.com/drive/1rr8w5IOzVdjs07YECnyOsnFu3ouUFkBs?usp=sharing
```


### Relevant log output

```shell
Check failed: d < dims() (1 vs. 1)
```
Repository: three.js
Issue: EXRLoader: Add support for `B44_COMPRESSION`.
Labels: Enhancement,Loaders

### Description

[Luminance/Chroma Images](https://openexr.com/en/latest/TechnicalIntroduction.html#luminance-chroma-images)

> Chroma information is stored in two channels, `RY` and `BY`, which are computed like

[Channel Names](https://openexr.com/en/latest/TechnicalIntroduction.html#channel-names)

> `Y` luminance, used either alone, for gray-scale images, or in combination with RY and BY for color images.

> `RY`, `BY` chroma for luminance/chroma images, see above.

[Chromaticities, Luminance/Chroma Test Images](https://openexr.com/en/latest/test_images/index.html#chromaticities)

### Reproduction steps

1. Bug EXR Luminance/Chroma Images
2. Error B44 Compression (lossy data compression)

### Code

```js
// Luminance Y Chroma RY, BY
```


### Live example

* [gainmap-creator.monogrid.com](https://gainmap-creator.monogrid.com/)

### Screenshots

![Untitled32](https://github.com/mrdoob/three.js/assets/156521906/0fcdae9c-8793-43dd-a3ca-bfc776951e76)

Error message:
![Untitled33](https://github.com/mrdoob/three.js/assets/156521906/28247a0f-e060-44ce-97e4-ffb5848f8864)


### Version

r163

### Device

Desktop

### Browser

Chrome

### OS

Windows
Repository: PowerToys
Issue: [PTRun] Create a powertoys run plugins store
Labels: Idea-Enhancement,Product-PowerToys Run,Needs-Triage

### Description of the new feature / enhancement

**This issue is intended to be a discussion, not a bug report or feature suggestion. If this topic has a negative impact, I will close it.**

> I love powertoys run and want to contribute to the ecosystem. I wrote a [plugin](https://github.com/Daydreamer-riri/PowerToys-Run-WebSearchShortcut) that works great for me (and I've seen a lot of people need it), but I think we can go a step further now.

For a long time, powertoys run lacked a convenient platform or tool to track, download, install, and update various plugins.

This can be broken down into the following steps:

1. Create a manifest repository similar to: https://github.com/Flow-Launcher/Flow.Launcher.PluginsManifest

2. Create a command line tool that can get the manifest file, download the plugin and put it to the corresponding plugin directory, and also has functions such as checking for updates and uninstalling.

3. A further step is to implement a GUI, or another PTRun plugin to call this tool.

In other aspects, I hope to allow developers to write plugins in other languages ​​(such as JavaScript, Python). This can greatly accelerate the evolution of the ecosystem. Wox itself supports plugins in different languages, and I think this is achievable.

We can start a community organization to do these things.

### Scenario when this would be used?

When you look for more PTRun plugins.

### Supporting information

#3200
Repository: ollama
Issue: MacOS not saving 0.0.0.0 between hardware restarts
Labels: bug,macos

### What is the issue?

When I set launchctl setenv OLLAMA_HOST "0.0.0.0" and restart the Ollama ap everything works as expected and I can access the API from other devices on my network. 

However when I reboot my Mac the OLLAMA_HOST reverts back to 127.0.0.1 and I have to run launchctl setenv OLLAMA_HOST "0.0.0.0" again.

### What did you expect to see?

When I run launchctl setenv OLLAMA_HOST "0.0.0.0" and restart my Mac I expected the OLLAMA_HOST to still be set at 0.0.0.0

### Steps to reproduce

1. Run  launchctl setenv OLLAMA_HOST "0.0.0.0"
2. Restart Ollama App
3. Check the logs to make sure it says "Listening on [::]:11434 (version 0.1.31)"
4. Reboot the Mac
5. Check the logs again and it now says "Listening on 127.0.0.1:11434 (version 0.1.31)"

### Are there any recent changes that introduced the issue?

_No response_

### OS

macOS

### Architecture

arm64

### Platform

_No response_

### Ollama version

0.1.31

### GPU

Apple

### GPU info

_No response_

### CPU

Apple

### Other software

_No response_
Repository: pytorch
Issue: CUDA kernel failed: no kernel image is available for execution on the device
Labels: module: cuda,triaged

### 🐛 Describe the bug

Type "help", "copyright", "credits" or "license" for more information.
>>> import torch
>>> torch.cuda.is_available()
True
>>> 

# I encountered this problem when trying to run the code of Pointnet2
# https://github.com/facebookresearch/votenet

### Versions

I encountered this problem:
![image](https://github.com/pytorch/pytorch/assets/104718152/e633166c-6493-4551-90a6-8ec6b5bbb8ab)

This is my configuration:
![image](https://github.com/pytorch/pytorch/assets/104718152/1c444c3c-a764-4aae-b135-896fe507fff7)
![image](https://github.com/pytorch/pytorch/assets/104718152/d4b44885-9f52-4dd9-80f6-bdbd4e575870)

PyTorch: pip install torch==1.9.0+cu111 torchvision==0.10.0+cu111 torchaudio==0.9.0 -f https://download.pytorch.org/whl/torch_stable.html

To fix this solution, I tried to change other PyTorch versions, but It didn't work.
Has anyone encountered this problem?


cc @ptrblck
Repository: tensorflow
Issue: `Check failed` in `tf.raw_ops.TensorScatterUpdate` and `tf.tensor_scatter_nd_update` when the rank of `indices` > 2.
Labels: stat:awaiting tensorflower,type:bug,comp:ops,TF 2.15

### Issue type

Bug

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

Yes

### Source

binary

### TensorFlow version

tf 2.15

### Custom code

No

### OS platform and distribution

Linux Ubuntu 20.04

### Mobile device

_No response_

### Python version

3.10

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

`Check failed` in `tf.raw_ops.TensorScatterUpdate` and `tf.tensor_scatter_nd_update` when the rank of `indices` > 2, which causes the program to crash. See the colab link below for details.

### Standalone code to reproduce the issue

```shell
https://colab.research.google.com/drive/1PLVxv-jQDZ15P4lrd3AhyVU-RAesammI?usp=sharing
```


### Relevant log output

```shell
Check failed: d < dims() (1 vs. 1)
```
Repository: next.js
Issue: Next.js Instrumentation can not import and resolve the node-bindings module.
Labels: bug,Instrumentation

### Link to the code that reproduces this issue

https://github.com/PrinOrange/reproduction-app

### To Reproduce

First, install a node-binding package, like the `@napi-rs/tar`, which provides the rust bindings and `.node` bytecode module.

```
npm i @napi-rs/tar
```

And then enable the next.js instrumentation with [the official document](https://nextjs.org/docs/app/building-your-application/optimizing/instrumentation)

In next.config.js
```javascript
/** @type {import("next").NextConfig} */
const nextConfig = {
  reactStrictMode: true,
  experimental: {
    instrumentationHook: true,
  },
};

module.exports = nextConfig;
```

In instrumentation.ts, import the node-binding module
```typescript
import tar from '@napi-rs/tar';

export function register() {
  console.log(tar.Entry)
}
```

Then run project in dev, it crashed
```
 ✓ Starting...
 ○ Compiling /instrumentation ...
 ⨯ ./node_modules/@napi-rs/tar-win32-x64-msvc/tar.win32-x64-msvc.node
**Module parse failed: Unexpected character '�' (1:2)**
**You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders**
(Source code omitted for this binary file)

Import trace for requested module:
./node_modules/@napi-rs/tar-win32-x64-msvc/tar.win32-x64-msvc.node
./node_modules/@napi-rs/tar/index.js
Error: An error occurred while loading instrumentation hook: Cannot find module 'E:\frontend-projects\reproduction-app\.next\server\instrumentation'
```


### Current vs. Expected behavior

It should import the node-bindings module in `instrumentation.ts`

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Pro
  Available memory (MB): 36670
  Available CPU cores: 8
Binaries:
  Node: 20.10.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.2.1-canary.4 // Latest available version is detected (14.2.1-canary.4).
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.1.3
Next.js Config:
  output: N/A
```


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

Not sure

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

next dev (local)

### Additional context

_No response_
Repository: godot
Issue: Mouse input in the editor is not registered when the editor is on a sway workspace that has a negative offset
Labels: bug,platform:linuxbsd,topic:porting,topic:input

### Tested versions

Reproducible in Godot_v4.2.1-stable_linux.x86_64
with
Debian sway/unstable,now 1.9-1+b1 amd64

### System information

Godot v4.2.1.stable - Debian GNU/Linux trixie/sid trixie - Wayland - GLES3 (Compatibility) - AMD Radeon Graphics (radeonsi, renoir, LLVM 17.0.6, DRM 3.57, 6.7.9-amd64) () - AMD Ryzen 7 PRO 4750U with Radeon Graphics (16 Threads)

### Issue description

The editor doesn't react to mouse input (no highlighting and clicks are not registered) when coordinates are negative


When the outputs are configured as:
output DP-2     pos     0    0 res 3840x2160
output eDP-1    pos -1920 1080 res 1920x1080
output HDMI-A-1 pos -1920    0 res 1920x1080

Mouse clicks and hover highlighting doesn't work on eDP-1 and HDMI-A-1


If they are configured as:
output DP-2     pos  1920    0 res 3840x2160
output eDP-1    pos     0 1080 res 1920x1080
output HDMI-A-1 pos     0    0 res 1920x1080
The mouse works as expected

Also if an output is placed to have negative coordinate roughly halfways accross the outpur, the mouse works as expected on the "positive" part of the monitor/output.

I would assume that the mouse coordinates are being treated as unsigned somewhere

### Steps to reproduce

Start godot and move the workspace to and output that has negative screen coordinates 

### Minimal reproduction project (MRP)

N/A, bug is in the editor
Repository: tensorflow
Issue: `Check failed` in `tf.raw_ops.TensorScatterSub` and `tf.tensor_scatter_nd_sub` when the rank of `indices` > 2.
Labels: stat:awaiting tensorflower,type:bug,comp:ops,TF 2.16

### Issue type

Bug

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

Yes

### Source

binary

### TensorFlow version

tf 2.15

### Custom code

No

### OS platform and distribution

_No response_

### Mobile device

_No response_

### Python version

3.10

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

`Check failed` in `tf.raw_ops.TensorScatterSub` and `tf.tensor_scatter_nd_sub` when the rank of `indices` > 2, which causes the program to crash. See the colab link below for details.

### Standalone code to reproduce the issue

```shell
https://colab.research.google.com/drive/1wqe_qe71oLucYiq1WS8s9GkZiVsNlaMz?usp=sharing
```


### Relevant log output

```shell
Check failed: d < dims() (1 vs. 1)
```
Repository: tensorflow
Issue: `Segmentation Fault` in `tf.raw_ops.TensorListScatter` and `tf.raw_ops.TensorListScatterV2` when the value of `indices` is too large.
Labels: stat:awaiting tensorflower,type:bug,comp:ops,TF 2.15

### Issue type

Bug

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

Yes

### Source

binary

### TensorFlow version

tf 2.15

### Custom code

No

### OS platform and distribution

Linux Ubuntu 20.04

### Mobile device

_No response_

### Python version

3.10

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

When the value of `indices` is too large,  `tf.raw_ops.TensorListScatter` and `tf.raw_ops.TensorListScatterV2` triggers `Segmentation Fault` due to RAM being full.

### Standalone code to reproduce the issue

```shell
https://colab.research.google.com/drive/1BOVVbofLSB2x_chg_WuFIdTWZXS9hiw0?usp=sharing
```


### Relevant log output

```shell
segmentation fault (core dumped)
```
Repository: PowerToys
Issue: crop and lock Reparent Issue
Labels: Issue-Bug,Needs-Triage,Product-CropAndLock

### Microsoft PowerToys version

0.80.1

### Installation method

GitHub, Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

Crop and Lock

### Steps to reproduce

like when is use this crop and lock (reparent) thing on the browser . for like yotube music site. to crop it play/pause button , then it totally crash the browser  , like total blackout screen.
![image](https://github.com/microsoft/PowerToys/assets/74504923/31ed600f-3b31-4bfa-a55f-343dc99037fe)


### ✔️ Expected Behavior

In this module , the expecting behaviour is to crop the particula segment of any page and that will shown on the top of main screen with that user can toggle or use the particular cropped piece if their is any clickable thing present.

### ❌ Actual Behavior

![image](https://github.com/microsoft/PowerToys/assets/74504923/ab6dfe58-8ac1-49fd-9f49-5d9ee0d7d23c)
it actually behave like , nothing showing on the top front screen and also hang the browser if i use this module on the browser then , and not able to control or access the browser again  , i have to restart it to use .

### Other Software

_No response_
Repository: tensorflow
Issue: Some `Check Failed` errors in `tf.raw_ops.MatrixSetDiagV3`
Labels: awaiting review,type:bug,comp:ops,TF 2.15

### Issue type

Bug

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

Yes

### Source

binary

### TensorFlow version

tf 2.15

### Custom code

No

### OS platform and distribution

Linux Ubuntu 20.04

### Mobile device

_No response_

### Python version

3.10

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

Some `Check Failed` errors in `tf.raw_ops.MatrixSetDiagV3`, which causes the program to crash. See the colab link below for details.

### Standalone code to reproduce the issue

```shell
https://colab.research.google.com/drive/11e72xipp_lz6fHcp7bN2MQy3Kw5KqHpL?usp=sharing
```


### Relevant log output

```shell
# Check failed: d < dims() (1 vs. 1)
# Check failed: d < dims() (2 vs. 2)
```