sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: tensorflow
Issue: segmentation fault when tf.histogram_fixed_width receives large `value_range` and `nbins` on CPU mode 
Labels: stat:awaiting tensorflower,type:bug,comp:ops,TF 2.16

### Issue type

Bug

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

Yes

### Source

source

### TensorFlow version

tf 2.16.1

### Custom code

Yes

### OS platform and distribution

_No response_

### Mobile device

_No response_

### Python version

_No response_

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

When setting the `nbins` to a large value and the value range to [-np.inf, np.inf], the API `tf.histogram_fixed_width` will raises a segmentation fault.
Interestingly, I found this issue only occurs on CPU backend while this API works fine on GPU.

### Standalone code to reproduce the issue

```shell
import os
os.environ['CUDA_VISIBLE_DEVICES'] = ''
import numpy as np
import tensorflow as tf
input = tf.constant([1.,2,3])
bins = 23
out = tf.histogram_fixed_width(input, [-np.inf, np.inf], nbins=bins)  # Segmentation fault (core dumped)
print(out)
```
```


### Relevant log output

_No response_
Repository: rust
Issue: More instructions generated for `Ord::clamp` than manual `max(X).min(Y)` for saturating truncating cast from `i32` to `u8`
Labels: A-codegen,T-compiler,S-has-mcve,A-autovectorization,C-optimization

_Originally reported here_
https://github.com/rust-lang/rust-clippy/issues/12826
_Related PR spawned from that issue_
https://github.com/rust-lang/rust/pull/125455

cc @blyxyas

Clamping and casting from `i32` to `u8`, using `clamp(0, 255) as u8` produces unnecessary instructions compared to `.max(0).min(255) as u8` when a loop is autovectorized.

`clippy`'s `manual_clamp` lint in the beta toolchain warns on this pattern to use `clamp` instead which can regress performance.

### Minimal example
```rust
#[inline(never)]
pub fn manual_clamp(input: &[i32], output: &mut [u8]) {
    for (&i, o) in input.iter().zip(output.iter_mut()) {
        *o = i.max(0).min(255) as u8;
    }
}

#[inline(never)]
pub fn clamp(input: &[i32], output: &mut [u8]) {
    for (&i, o) in input.iter().zip(output.iter_mut()) {
        *o = i.clamp(0, 255) as u8;
    }
}
```
https://rust.godbolt.org/z/zf73jsqjq

<details><summary>Manual clamp</summary>

```asm
.LBB0_4:
        movdqu  xmm0, xmmword ptr [rdi + 4*r8]
        packssdw        xmm0, xmm0
        packuswb        xmm0, xmm0
        movdqu  xmm1, xmmword ptr [rdi + 4*r8 + 16]
        packssdw        xmm1, xmm1
        packuswb        xmm1, xmm1
        movd    dword ptr [rdx + r8], xmm0
        movd    dword ptr [rdx + r8 + 4], xmm1
        add     r8, 8
        cmp     rsi, r8
        jne     .LBB0_4
```
</details>

<details><summary>`Ord::clamp`</summary>

```asm
.LBB0_4:
        movdqu  xmm6, xmmword ptr [rdi + 4*r8]
        movdqu  xmm5, xmmword ptr [rdi + 4*r8 + 16]
        pxor    xmm3, xmm3
        pcmpgtd xmm3, xmm6
        packssdw        xmm3, xmm3
        packsswb        xmm3, xmm3
        pxor    xmm4, xmm4
        pcmpgtd xmm4, xmm5
        packssdw        xmm4, xmm4
        packsswb        xmm4, xmm4
        movdqa  xmm7, xmm6
        pxor    xmm7, xmm0
        movdqa  xmm8, xmm1
        pcmpgtd xmm8, xmm7
        pand    xmm6, xmm8
        pandn   xmm8, xmm2
        por     xmm8, xmm6
        packuswb        xmm8, xmm8
        packuswb        xmm8, xmm8
        pandn   xmm3, xmm8
        movdqa  xmm6, xmm5
        pxor    xmm6, xmm0
        movdqa  xmm7, xmm1
        pcmpgtd xmm7, xmm6
        pand    xmm5, xmm7
        pandn   xmm7, xmm2
        por     xmm7, xmm5
        packuswb        xmm7, xmm7
        packuswb        xmm7, xmm7
        pandn   xmm4, xmm7
        movd    dword ptr [rdx + r8], xmm3
        movd    dword ptr [rdx + r8 + 4], xmm4
        add     r8, 8
        cmp     rsi, r8
        jne     .LBB0_4
```
</details>

Real code examples from functions in the `image-webp` crate
https://rust.godbolt.org/z/3rnY8d94v
https://rust.godbolt.org/z/53T7n9PGx
Repository: pytorch
Issue: PyTorch version agnostic C++ extensions
Labels: module: cpp-extensions,triaged,module: custom-operators,oncall: pt2,module: pt2-dispatcher

Today, C++ extensions in PyTorch need a separate build per PyTorch version per Python version. This is because they link against libtorch.

However, AOTInductor has an ABI-compatible c-shim for calling into custom ops. In theory we could use this to allow people to write PyTorch version agnostic C++ extensions.

cc @malfet @ezyang @msaroufim @bdhirsh @anijain2305 @chauhang
Repository: ollama
Issue: Code models like codestral should have a lower temperature
Labels: feature request

This makes the code more correct
Repository: ollama
Issue: s390x build ollama : running gcc failed 
Labels: bug

### What is the issue?
ollama build fails on undefined llama references

```
# github.com/ollama/ollama
/usr/local/go/pkg/tool/linux_s390x/link: running gcc failed: exit status 1
/usr/bin/ld: /tmp/go-link-778429479/000019.o: in function `_cgo_3eac69a87adc_Cfunc_llama_free_model':
/tmp/go-build/cgo-gcc-prolog:63: undefined reference to `llama_free_model'
/usr/bin/ld: /tmp/go-link-778429479/000019.o: in function `_cgo_3eac69a87adc_Cfunc_llama_load_model_from_file':
/tmp/go-build/cgo-gcc-prolog:79: undefined reference to `llama_load_model_from_file'
/usr/bin/ld: /tmp/go-link-778429479/000019.o: in function `_cgo_3eac69a87adc_Cfunc_llama_model_default_params':
/tmp/go-build/cgo-gcc-prolog:96: undefined reference to `llama_model_default_params'
/usr/bin/ld: /tmp/go-link-778429479/000019.o: in function `_cgo_3eac69a87adc_Cfunc_llama_model_quantize':
/tmp/go-build/cgo-gcc-prolog:117: undefined reference to `llama_model_quantize'
/usr/bin/ld: /tmp/go-link-778429479/000019.o: in function `_cgo_3eac69a87adc_Cfunc_llama_model_quantize_default_params':
/tmp/go-build/cgo-gcc-prolog:134: undefined reference to `llama_model_quantize_default_params'
/usr/bin/ld: /tmp/go-link-778429479/000019.o: in function `_cgo_3eac69a87adc_Cfunc_llama_print_system_info':
/tmp/go-build/cgo-gcc-prolog:151: undefined reference to `llama_print_system_info'
/usr/bin/ld: /tmp/go-link-778429479/000019.o: in function `_cgo_3eac69a87adc_Cfunc_llama_token_to_piece':
/tmp/go-build/cgo-gcc-prolog:176: undefined reference to `llama_token_to_piece'
/usr/bin/ld: /tmp/go-link-778429479/000019.o: in function `_cgo_3eac69a87adc_Cfunc_llama_tokenize':
/tmp/go-build/cgo-gcc-prolog:203: undefined reference to `llama_tokenize'
collect2: error: ld returned 1 exit status
```

**Tools version**

```
[linux1@r ollama]$ cmake --version
cmake version 3.26.5

CMake suite maintained and supported by Kitware (kitware.com/cmake).
[linux1@r ollama]$ go version
go version go1.22.3 linux/s390x
[linux1@r ollama]$ gcc --version
gcc (GCC) 11.4.1 20231218 (Red Hat 11.4.1-3)
Copyright (C) 2021 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
```



### OS

`Linux r 5.14.0-362.8.1.el9_3.s390x #1 SMP Tue Oct 3 09:00:29 EDT 2023 s390x s390x s390x GNU/Linux`

### GPU

None

### CPU

s390x (IBM/S390 on IBM z15 8561 mainframe)

### Ollama version

git version v0.1.39+
Repository: vscode
Issue: Allow Developer to get command description from API
Labels: feature-request,menus

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
# The Issue
Being able to get the command description programmatically would be incredibly useful for extension developers. Currently, `vscode.commands.getCommands()` only returns the name of a command when searching in the command palette uses the description. Being able to run something like `vscode.commands.getCommandDescription(commandName)` would help extension developers in executing and searching for the specific command to run.


# Mentions of wanting this feature
https://github.com/microsoft/vscode/issues/160263
https://stackoverflow.com/questions/58367207/list-of-all-available-commands-in-vscode
Repository: go
Issue: x/telemetry: merge `sidecar.log` and the uploader's debug log
Labels: NeedsFix,telemetry

* Sidecar logging: https://github.com/golang/telemetry/blob/39ace7a40ae7adf90bd106518be3e8d9c21bc6ff/start.go#L201
* Uploader's debug logging: https://github.com/golang/telemetry/blob/39ace7a40ae7adf90bd106518be3e8d9c21bc6ff/internal/upload/run.go#L93

Sidecar logging is done by the parent, while the uploader's logging is done by the upload process.
They also fight for the log prefix. 
 Sidecar process: https://github.com/golang/telemetry/blob/39ace7a40ae7adf90bd106518be3e8d9c21bc6ff/start.go#L230
 Uploader: https://github.com/golang/telemetry/blob/39ace7a40ae7adf90bd106518be3e8d9c21bc6ff/internal/upload/run.go#L112 

Since now we have only one way to trigger upload, let's keep only one way.
Repository: pytorch
Issue: Add way to annotate a raw triton kernel using the triton kernel HOP so that it becomes make_fx-traceable
Labels: triaged,oncall: pt2,module: pt2-dispatcher,module: user triton

@eellison had a use case for writing a replacement pass (pre-grad or joint) where a user would want to replace a sequence of operations with 1+ triton kernels (perhaps wrapped in an autograd.Function)

One cannot actually trace a triton kernel without wrapping it in a custom op or the triton kernel HOP. We should offer a probably-one-line decorator to wrap a triton kernel so that it can actually be traced

cc @bdhirsh @oulgen @aakhundov @ezyang @msaroufim @anijain2305 @chauhang
Repository: vscode
Issue: ctrl+alt+pagedown not working in accessible view
Labels: bug,accessibility

1. Turn screen reader on
2. Focus a chat response
3. alt+f2
4. ctrl+alt+pgdown to jump to next codeblock
5. screenreader reads "not in a table cell" :bug: I think this is because it triggers the 'Move Editor Right' command
Repository: next.js
Issue: "trailingSlash" causing CORS errors
Labels: bug

### Link to the code that reproduces this issue

https://github.com/tippfelher/nextjs-redirect-issue

### To Reproduce

Open https://nextjs-permanent-redirect-issue.vercel.app/something
The response header correctly contains Access-Control-Allow-Origin: *

Open https://nextjs-permanent-redirect-issue.vercel.app/something/
The response header contains no Access-Control-Allow-Origin: *

### Current vs. Expected behavior

Open https://nextjs-permanent-redirect-issue.vercel.app/something/
The response header also contains Access-Control-Allow-Origin: *

Configuring https://nextjs.org/docs/pages/api-reference/next-config-js/trailingSlash is obviously no solution.

### Provide environment information

```bash
```


### Which area(s) are affected? (Select all that apply)

Not sure

### Which stage(s) are affected? (Select all that apply)

Vercel (Deployed), Other (Deployed)

### Additional context

Repo for reproduction: https://github.com/tippfelher/nextjs-redirect-issue

1) Added route (/src/app/something/route.ts)
2) Added headers in nextjs.config.js
Repository: three.js
Issue: [WebGPU] Control Access Barriers
Labels: WebGPU

### Description

At some point, I think it would be great to have the ability to set control access barriers and access more of the WGSL specific functionality within a TSL function. I've tried implementing some of these access barriers myself in a personal branch, using an approach similar to that of the 'vec2', 'vec3', 'etc' ConvertTypes in ShaderNode.js. However, it seems like the node system is heavily weighted towards nodes that explicitly represent some kind of mathematical operation, so, at least from my end, it's not as simple as just adding another node type. 

### Solution

```
export const workgroupBarrier = new BarrierType('workgroup');
```

And then be accessed from a tslFn like so...

```
tslFn( () => {
	...
	workgroupBarrier()
	...
})
```

I'm not sure if there's currently a relevant use case for these barriers, but once subgroups become stable, I imagine commands like workgroupBarrier() or subgroupBarrier() would be very useful for things like prefix sums for spatial hash grids.

### Alternatives

*No response*

### Additional context

_No response_
Repository: next.js
Issue: Version 15 breaks select form element
Labels: bug

### Link to the code that reproduces this issue

https://github.com/vercel/next-learn/tree/main/dashboard/final-example

### To Reproduce

1. Install and run https://github.com/vercel/next-learn/tree/main/dashboard/final-example
2. Remove redirect when a invoice is updated
3. Open an invoice
4. Select a different customer from the select.
5. Click Edit Invoice

-> The select shows the old value again. After page refresh the new correct option is shown.

In Version < 15 the newly selection options stays after submitting a form. Does not happen wir input fields.


### Current vs. Expected behavior

Options stays after submitting a form

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.2.0: Wed Nov 15 21:55:06 PST 2023; root:xnu-10002.61.3~2/RELEASE_ARM64_T6020
  Available memory (MB): 16384
  Available CPU cores: 10
Binaries:
  Node: 20.12.2
  npm: 10.8.0
  Yarn: 1.22.21
  pnpm: 9.1.3
Relevant Packages:
  next: 15.0.0-rc.0 // Latest available version is detected (15.0.0-rc.0).
  eslint-config-next: 14.0.0
  react: 19.0.0-rc-38e3b23483-20240529
  react-dom: 19.0.0-rc-38e3b23483-20240529
  typescript: 5.2.2
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), next build (local), next start (local), Vercel (Deployed)

### Additional context

_No response_
Repository: transformers
Issue: Understanding loss in Training LLM
Labels: Feature request

### Feature request

Hi,

I have a misunderstanding regarding training LLMs. When we train the model, we calculate the loss by having the model predict the next word and then compute the difference between the true and predicted values.

What I want to know is: when making the model predict the next words, it generates a new word based on the previously generated words. If a generated word is wrong, won't the subsequent predictions continue down the wrong path?

### Motivation

![LLMTrain-ezgif com-webp-to-jpg-converter](https://github.com/huggingface/transformers/assets/76405917/a35dd000-5c10-480f-9972-150870a43ca9)


### Your contribution

.
Repository: vscode
Issue: Inline chat rendering issue when using accessibility mode
Labels: bug,diff-editor,inline-chat

1. Enable accessibility mode
1. New empty file
2. `Cmd + i` to open inline chat
3. "Write sorting function"
4. 🐛 weird rendering:

<img width="753" alt="image" src="https://github.com/microsoft/vscode/assets/2644648/2975754f-0a92-4b31-aefc-737c425325ca">

There's a vertical scroll bar that doesn't scroll anything... just the big white space.

_Originally posted by @TylerLeonhardt in https://github.com/microsoft/vscode/issues/213614#issuecomment-2138376956_
Repository: pytorch
Issue: Cannot fakeify a tensor who's .grad field is a tensor subclass
Labels: triaged,module: __torch_dispatch__,oncall: pt2,module: fakeTensor,module: pt2-dispatcher

The repro is:
```
import torch
from torch.testing._internal.two_tensor import TwoTensor

class Mod(torch.nn.Module):
    def __init__(self):
        super().__init__()
        self.register_parameter("p", torch.nn.Parameter(torch.ones(4, 4, requires_grad=True)))
    def forward(self, x):
        return (x + self.p).sum()

a = torch.ones(4, requires_grad=True)
a2 = a.clone().detach().requires_grad_()
aa = TwoTensor(a, a2)
#aa2 = aa.clone().detach().requires_grad_()
#aaaa = TwoTensor(aa, aa2)

m = Mod()
out = m(aa)
out.backward()
print(isinstance(m.p.grad, TwoTensor))
print(isinstance(m.p.grad.a, TwoTensor))
print(isinstance(m.p.grad.b, TwoTensor))

compiled_m = torch.compile(m, backend="aot_eager")
compiled_out = compiled_m(aa)
compiled_out.backward()
print(isinstance(compiled_m.p.grad, TwoTensor))
print(isinstance(compiled_m.p.grad.a, TwoTensor))
print(isinstance(compiled_m.p.grad.b, TwoTensor))
```

Which gives a pretty obscure error (found by @tugsbayasgalan):
```
  File "/home/hirsheybar/local/b/pytorch/torch/_dynamo/variables/builder.py", line 2288, in <lambda>
    lambda: tx.fake_mode.from_tensor(
  File "/home/hirsheybar/local/b/pytorch/torch/_subclasses/fake_tensor.py", line 1841, in from_tensor
    return self.fake_tensor_converter.from_real_tensor(
  File "/home/hirsheybar/local/b/pytorch/torch/_subclasses/fake_tensor.py", line 314, in from_real_tensor
    out = self.meta_converter(
  File "/home/hirsheybar/local/b/pytorch/torch/_subclasses/meta_utils.py", line 1479, in __call__
    r = self.meta_tensor(
  File "/home/hirsheybar/local/b/pytorch/torch/_subclasses/meta_utils.py", line 1401, in meta_tensor
    r.grad = self.meta_tensor(
  File "/home/hirsheybar/local/b/pytorch/torch/_subclasses/meta_utils.py", line 1284, in meta_tensor
    r = empty_create_subclass(
  File "/home/hirsheybar/local/b/pytorch/torch/_subclasses/meta_utils.py", line 650, in empty_create_subclass
    assert symbolic_context is None or isinstance(
AssertionError:
```

We should either fix this, or at least make the error better (saying that we don't support this case for now)

cc @Chillee @ezyang @zou3519 @albanD @samdow @msaroufim @anijain2305 @chauhang @eellison
Repository: neovim
Issue: Undercurl behavior is inconsistent due to flaky detection of the terminal (Konsole)
Labels: bug,tui

### Problem

I noticed that using undercurl isn't really working consistently depending on the terminal session. For me in particular this happens with konsole. When running it directly it works, when being in the ssh session (even on the localhost), it doesn't. This happens due to nvim relying on detecting `KONSOLE_VERSION` variable which isn't set when in the ssh session.

### Steps to reproduce

Run nvim from konsole locally.

Then enable this highlighting:

```vim
:lua vim.api.nvim_set_hl(0, 'SpellBad', { sp = 'red', undercurl = true } )
```

Try spellchecking some invalid text like `zzzz` (with something like `:setlocal spell! spelllang=en_us`).

It works fine:

![image](https://github.com/neovim/neovim/assets/310927/d0ee58c8-cfbf-425d-8c47-2ceba8de8221)

Use ssh (even to localhost) and try the same thing, the result is underline fallback:

![image](https://github.com/neovim/neovim/assets/310927/9a15c5f4-aea7-4e48-8fad-31fdfd1d498a)



### Expected behavior

I'm already forcing `set termguicolors` in general.

Undercurl should work more consistently. Or may be there is a setting that may be simply forces that behavior if user knows that terminal supports it? As a workaround I can simply export KONSOLE_VERSION inside the ssh session, but that's messy.


### Neovim version (nvim -v)

v0.10.0

### Vim (not Nvim) behaves the same?

---

### Operating system/version

Debian testing Linux

### Terminal name/version

Konsole 23.08.1

### $TERM environment variable

xterm-256color

### Installation

appimage from Github build
Repository: vscode
Issue: web issue reporter create issue not working when logged in
Labels: bug,issue-reporter

Testing #213597

while logged in, cannot `create issue`, but can only preview issue.
Repository: deno
Issue: Add test for lsp changes with `no-unused-vars`
Labels: tests,chore,lsp

There were some changes in the PR that seem like they should have a test for regressions:

https://github.com/denoland/deno/pull/24034/files#diff-6151a261fd9c2392730354eebad671a7c713591b9318accbf612d12496c29875R1059-R1061
Repository: go
Issue: time: AfterFunc doesn't inherit parent goroutine labels
Labels: NeedsInvestigation

### Go version

`go version go1.22.3` or tip.

### What did you do?

Run this code: https://go.dev/play/p/Yf7N3XhKsdF?v=gotip

### What did you see happen?

```
goroutine profile: total 3
1 @ 0x42dcb1 0x4674fd 0x4b8a91 0x4b88c5 0x4b58eb 0x4ccf65 0x437d2b 0x46f581
# labels: {"myownlabel":"label"}
#	0x4b8a90	runtime/pprof.writeRuntimeProfile+0xb0	/usr/local/go-faketime/src/runtime/pprof/pprof.go:767
#	0x4b88c4	runtime/pprof.writeGoroutine+0x44	/usr/local/go-faketime/src/runtime/pprof/pprof.go:726
#	0x4b58ea	runtime/pprof.(*Profile).WriteTo+0x14a	/usr/local/go-faketime/src/runtime/pprof/pprof.go:368
#	0x4ccf64	main.main+0x1c4				/tmp/sandbox135271070/prog.go:24
#	0x437d2a	runtime.main+0x28a			/usr/local/go-faketime/src/runtime/proc.go:272

1 @ 0x46806e 0x46b4e5 0x4ccfbd 0x46f581
#	0x46b4e4	time.Sleep+0xe4		/usr/local/go-faketime/src/runtime/time.go:285
#	0x4ccfbc	main.main.func1+0x1c	/tmp/sandbox135271070/prog.go:18

1 @ 0x46806e 0x46b4e5 0x4ccffd 0x46f581
# labels: {"myownlabel":"label"}
#	0x46b4e4	time.Sleep+0xe4		/usr/local/go-faketime/src/runtime/time.go:285
#	0x4ccffc	main.main.func2+0x1c	/tmp/sandbox135271070/prog.go:20```
```

### What did you expect to see?

```
goroutine profile: total 3
1 @ 0x42dcb1 0x4674fd 0x4b8a91 0x4b88c5 0x4b58eb 0x4ccf65 0x437d2b 0x46f581
# labels: {"myownlabel":"label"}
#	0x4b8a90	runtime/pprof.writeRuntimeProfile+0xb0	/usr/local/go-faketime/src/runtime/pprof/pprof.go:767
#	0x4b88c4	runtime/pprof.writeGoroutine+0x44	/usr/local/go-faketime/src/runtime/pprof/pprof.go:726
#	0x4b58ea	runtime/pprof.(*Profile).WriteTo+0x14a	/usr/local/go-faketime/src/runtime/pprof/pprof.go:368
#	0x4ccf64	main.main+0x1c4				/tmp/sandbox135271070/prog.go:24
#	0x437d2a	runtime.main+0x28a			/usr/local/go-faketime/src/runtime/proc.go:272

1 @ 0x46806e 0x46b4e5 0x4ccfbd 0x46f581
# labels: {"myownlabel":"label"}
#	0x46b4e4	time.Sleep+0xe4		/usr/local/go-faketime/src/runtime/time.go:285
#	0x4ccfbc	main.main.func1+0x1c	/tmp/sandbox135271070/prog.go:18

1 @ 0x46806e 0x46b4e5 0x4ccffd 0x46f581
# labels: {"myownlabel":"label"}
#	0x46b4e4	time.Sleep+0xe4		/usr/local/go-faketime/src/runtime/time.go:285
#	0x4ccffc	main.main.func2+0x1c	/tmp/sandbox135271070/prog.go:20
```

I think it's kinda confusing that this way you can bypass labels inheriting.
Repository: flutter
Issue: [Game] Flutter support for Gamesnacks
Labels: a: gamedev,team-games
Repository: PowerToys
Issue: Start menu opens when remapping Win+C to URI
Labels: Issue-Bug,Product-Keyboard Shortcut Manager,Needs-Triage

### Microsoft PowerToys version

0.81.1

### Installation method

PowerToys auto-update

### Running as admin

No

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

When I used "Remap a shortcut" to map Win+C to the URI `https://copilot.microsoft.com/`.

### ✔️ Expected Behavior

When I use Win+C, open `https://copilot.microsoft.com/` on my default browser (Chrome)

### ❌ Actual Behavior

Expected happens, but also start menu opens.

### Other Software

Google Chrome 125.0.6422.113
Windows 22H2 build 19045.4412
Repository: transformers
Issue: Request for Static Cache Support for XLA Compiler in Transformers
Labels: Feature request

### Feature request

I am requesting static cache support for the XLA compiler for transformer models. This will prevent recompilation at each step caused by slicing

### Motivation

To enhance the efficiency of autoregressive generation in transformer models, static cache support for the XLA can be implemented to mitigate the need for recompilation at each generation step. 

### Your contribution

[Use the Index_copy method to update static cache inplace](https://github.com/huggingface/transformers/pull/31129)

- Additionally, While out-of-place operations could offer further improvements, they introduce new tensors with different addresses, complicating calculations. Addressing this issue is crucial for fully leveraging the potential of XLA.