sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: Interferes with browser tabs causing dragged/detached tabs to jump to the latest window instance
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.78.0

### Installation method

GitHub

### Running as admin

Yes

### Area(s) with issue?

General

### Steps to reproduce

Have 2 chrome windows open side by side, Window A and Window B. Open an extra tab inside window A and drag it so that it detaches from that window slightly, you will notice it instantly pops over into Window B. This happens across all browsers (Chrome, firefox, brave, edge). 

### ✔️ Expected Behavior

When dragging/detaching a tab outside of a browser window, it should not be instantly appearing in the latest browser window instance. 

### ❌ Actual Behavior

The detached tab should just hover over the first window (A), it shouldn't be instantly appearing over the latest browser window (B) instance. 

### Other Software

Windows 10. Chrome Version 122.0.6261.58 (Official Build) (64-bit).
Repository: vscode
Issue: Prompt input field extends beyond common padding
Labels: ux,panel-chat

<img width="673" alt="image" src="https://github.com/microsoft/vscode/assets/103326/4edf25ed-83cf-4bd3-802c-f79106177010">
Repository: PowerToys
Issue: Remapping Browser Search Key (MS Natural Keyboard 4000) to Ctrl + F opens "Project" Panel
Labels: Issue-Bug,Product-Keyboard Shortcut Manager,Needs-Triage,Needs-Team-Response

### Microsoft PowerToys version

0.78.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

Have a MS Natural Ergonomic Keyboard 4000 (maybe works with others with the Browser Search Button)

Remap it to Ctrl + F

When you use the key, it always opens the "Project" Panel (the one from windows that you open with Win + P) after sending the correct keystrokes, meaning you can't just start typing your search terms.

Tested it with the focus on Chrome, Desktop and Notepad ++ always same behavior.

### ✔️ Expected Behavior

Ctrl + F

### ❌ Actual Behavior

When you use the key, it always opens the "Project" Panel (the one from windows that you open with Win + P) after sending the correct keystrokes, meaning you can't just start typing your search terms.

Tested it with the focus on Chrome, Desktop and Notepad ++ always same behavior.

### Other Software

Windows 11 Dev Channel
Chrome Dev
Chrome Beta
Notepad++

![image](https://github.com/microsoft/PowerToys/assets/61247454/667f1f4b-df9f-441c-b31e-9b3d0aaad251)
Repository: terminal
Issue: Acrilyc tabrow glitch when terminal change focus
Labels: Issue-Bug,Product-Terminal,Area-Theming

### Windows Terminal version

1.19.10302.0

### Windows build number

10.0.26058.0

### Other Software

_No response_

### Steps to reproduce

Just set background opacity to something lower than 100 and use acrylic.

"opacity": 50,
"useAcrylic": true,
"useAcrylicInTabRow": true

### Expected Behavior

When lose focus, tab row should be opaque with the defined background color.
After regain focus, tab row should be semitransparent with acrylic effect.

### Actual Behavior

✅ When lose focus, tab row is opaque with the defined background color.
❌ After regain focus, tab row is semitransparent with intermittent acrylic effect (sometimes has blur, sometimes not).

- I noticed that if the opacity is 100% the issue do not happens

| Opacity in 50%  | Opacity in 100% |
| ------------- | ------------- |
| <video src="https://github.com/microsoft/terminal/assets/39845798/4751d697-a6ea-4676-b454-4a6f630ac213"> | <video src="https://github.com/microsoft/terminal/assets/39845798/35f4b170-0f25-4b17-85c3-e55996539c57"> |

---
The issue started after the last update. Previously worked fine. Not sure if is related to the new aways on acrylic.
Repository: ollama
Issue: Integrated AMD GPU support
Labels: feature request,amd

Opening a new issue (see https://github.com/ollama/ollama/pull/2195) to track support for integrated GPUs. I have a AMD 5800U CPU with integrated graphics. As far as i did research ROCR lately does support integrated graphics too.

Currently Ollama seems to ignore iGPUs in general.
Repository: angular
Issue: No docs about how to test effects in component constructor
Labels: P3,area: docs

### Which @angular/* package(s) are the source of the bug?

compiler, core

### Is this a regression?

Yes

### Description

I'm trying to assert a method of the component is called when a signal emits `true` inside `effect`. 

Since no one else reported such an issue yet I assume I might be doing something wrong, but then again there are no docs explaining how to do these things right. So there.

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz-starters-p37z7j?description=An%20angular-cli%20project%20based%20on%20@angular/animations,%20@angular/common,%20@angular/compiler,%20@angular/core,%20@angular/forms,%20@angular/platform-browser,%20@angular/platform-browser-dynamic,%20@angular/router,%20core-js,%20rxjs,%20tslib%20and%20zone.js&file=package.json,setup-jest.ts,jest.config.js,tsconfig.spec.json,src%2Fmain.ts,src%2Fapp.component.spec.ts&template=node&title=Angular%20Starter

### Please provide the exception or error you saw

```true
Message:
      expect(jest.fn()).toHaveBeenCalled()
    
    Expected number of calls: >= 1
    Received number of calls:    0
```


### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular 17.2
Node 18
Package Manager: npm / pnpm
OS: Linux, Mac, Windows
```


### Anything else?

I tried:

- wrapping the test with `fakeAsync`
- Moving `TestBed.flushEffects()` around
Repository: rust
Issue: Bound on iterator suggests invalid code to call `iter()` on the `impl` 
Labels: A-diagnostics,T-compiler

### Code

```Rust
pub struct Foo<I>  
      where I: Iterator, 
  { 
   
      iter: I, 
  } 
   
   
  pub trait Bar: Iterator + Sized {  
      fn sprawl(self) -> Foo<Self> { 
          Foo {  
              iter: self 
          } 
      } 
  } 
   
  impl<T> Bar for Vec<T>
  where 
      T: Iterator, 
  {} 
   

It suggests you to call `iter()` on `Vec<T>`  in the impl, which is invalid code
```


### Current output

```Shell
Error[E0277]: `Vec<T>` is not an iterator
  --> src/lib.rs:17:19
   |
17 |   impl<T> Bar for Vec<T>
   |                   ^^^^^^ `Vec<T>` is not an iterator; try calling `.into_iter()` or `.iter()`
   |
   = help: the trait `Iterator` is not implemented for `Vec<T>`
note: required by a bound in `Bar`
  --> src/lib.rs:9:18
   |
9  |   pub trait Bar: Iterator + Sized {  
   |                  ^^^^^^^^ required by this bound in `Bar`

For more information about this error, try `rustc --explain E0277`.
```

### Rationale and extra context
[Playground link](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=4ada37178d90dffb292aec10dde67e69)

### Rust Version

```Shell
1.78.0 nightly, but also present on the latest nightly and stable
```


<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"veera-sivarajan"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: pytorch
Issue: DISABLED test_record_stream_on_shifted_view (__main__.TestCuda)
Labels: module: cuda,module: rocm,triaged,module: flaky-tests,skipped

Platforms: rocm

This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_record_stream_on_shifted_view&suite=TestCuda&limit=100) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/21807122842).

Over the past 3 hours, it has been determined flaky in 2 workflow(s) with 2 failures and 2 successes.

**Debugging instructions (after clicking on the recent samples link):**
DO NOT ASSUME THINGS ARE OKAY IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_record_stream_on_shifted_view`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.


Test file path: `test_cuda.py`

cc @ptrblck @jeffdaily @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang @clee2000
Repository: angular
Issue: Pending APP_INITIALIZER doesn't trigger Hydration warning after APPLICATION_IS_STABLE_TIMEOUT
Labels: area: core,core: hydration

### Which @angular/* package(s) are the source of the bug?

core, platform-server

### Is this a regression?

Yes

### Description

When using an `APP_INITIALIZER`  that returns a promise pages refreshes always end up being requested from the server. I also noticed that it breaks dev tools.

### Please provide a link to a minimal reproduction of the bug

https://github.com/tsteuwer-accesso/angular-ssr-issue/

### Please provide the exception or error you saw

```true
Clone the repository, `npm ci` then run the app with `npx ng s`.

Open the browser to http://localhost:4200

Open the network tab, click Route 1. Notice it does a full page refresh.
Click Route 2. Notice it does a full page refresh.

Now, open up `app.config.ts` and comment-out `provideAppEnvironment()` from the providers. Refresh the page and everything starts working. It no longer does full page refreshes from the server and dev tools works.
```


### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI: 17.2.0
Node: 20.10.0
Package Manager: npm 10.2.3
OS: linux x64

Angular: 17.2.1
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, platform-server
... router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1702.0
@angular-devkit/build-angular   17.2.0
@angular-devkit/core            17.2.0
@angular-devkit/schematics      17.2.0
@angular/cli                    17.2.0
@angular/ssr                    17.2.0
@schematics/angular             17.2.0
rxjs                            7.8.1
typescript                      5.3.3
zone.js                         0.14.4
```


### Anything else?

This also break dev tools somehow.
Repository: deno
Issue: When sanitizeExit is false, don't exit without printing a message
Labels: bug,testing

We treat `sanitizeExit` as if the exit sanitizer were disabled. Instead we should abort all tests and print a message. This will also fix the issue w/the exit sanitizer stdout/stderr not being reliably printed.

Follow-up from  https://github.com/denoland/deno/pull/22515/
Repository: go
Issue: cmd/go: toolchain directive in go.mod being updated unnecessarily
Labels: NeedsInvestigation,GoCommand

There doesn't seem to be a way to stop the `toolchain` directive from being updated when running various `go` commands

In our OSS project we rely on the `go` directive in the go.mod to ensure a min go version. We do not want to use the `toolchain` directive as we always expect it to match the `go` directive. 

some user feedback
- https://gophers.slack.com/archives/C0VPK4Z5E/p1704471476388119
- https://gophers.slack.com/archives/C9BMAAFFB/p1708525315637839

## Go Version
> go version go1.22.0 darwin/amd64


## Go ENV
<details>
<summary> expand </summary>

```
GO111MODULE=''
GOARCH='amd64'
GOBIN=''
GOCACHE='/Users/dprotasowski/Library/Caches/go-build'
GOENV='/Users/dprotasowski/Library/Application Support/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='darwin'
GOINSECURE=''
GOMODCACHE='/Users/dprotasowski/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='darwin'
GOPATH='/Users/dprotasowski/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/usr/local/Cellar/go/1.22.0/libexec'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/usr/local/Cellar/go/1.22.0/libexec/pkg/tool/darwin_amd64'
GOVCS=''
GOVERSION='go1.22.0'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='cc'
CXX='c++'
CGO_ENABLED='1'
GOMOD='/Users/dprotasowski/work/test/go.mod'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -ffile-prefix-map=/var/folders/xs/xfp1z4cn643c46w69lv8bv8w0000gp/T/go-build4163821748=/tmp/go-build -gno-record-gcc-switches -fno-common'
```
</details>


## Scenario 1 - creating a new module and downgrading go

### What did you do
```
$ mkdir test && cd test
$ go mod init blah
$ go get go@1.21
```
### What did you see happen?

- Tool chain directive of 1.22.0 was added - but this isn't necessary
- min go version set to 1.21.7

### What did you expect to happen?

- No `toolchain` directive to be added 
- Min go version set to `1.21` - since I didn't specify the point release


## Scenario 2 - pulling a new dependency that upgraded the go version

### What did you do


Project structure
```go
--- go.mod
module blah

go 1.19

---- main.go
package main

import "fmt"

func main() {
	fmt.Println("vim-go")
}
```

Fetch a dependency that updates the go min version
```
$ go get knative.dev/pkg@9f033a7
```

### What did you see happen?

console output
```
go: upgraded go 1.19 => 1.21
go: added toolchain go1.22.0
go: added knative.dev/pkg v0.0.0-20240221065059-9f033a7b77f7
```

go.mod output
```go
module blah

go 1.21

toolchain go1.22.0

require knative.dev/pkg v0.0.0-20240221065059-9f033a7b77f7 // indirect
```


### What did you expect to happen?

`toolchain` directive shouldn't appear. We want it to always default to the same as the `go` directive
Repository: ollama
Issue: 🚀🔍 GPU Mystery: Unleashing the Power on Small Models but Stuck on Idle with Giants like MiXtral8x7B & Llama 70B on Ubuntu 22 🧩💡
Labels: bug

Hi

Using Ubuntu 22.
both commands nvcc --version and nvidia-smi are showing valied outputs.

I've noticed that the GPU is not utilized when running larger models (e.g., MiXtral8x7B, Llama 70B), yet it functions well with smaller models like Mistral and Llama 7B. Is this issue known to others, or is it just me experiencing it? By the way, I tested this on both RTX 3090 and RTX 2080, and both exhibited the same issue with the larger models.

Additionally, with the larger models (Mistral and Llama 70B), the GPU RAM is almost fully utilized, but not the GPU itself (which is very strange), while the CPU is fully utilized.

Here is the summary:

Larger models MiXtral8x7B, Llama 70B
GPU: Not utalised
GPU RAM: utalised
CPU: utalised
RAM: Not utalised

Small models Mistral and Llama 7B
GPU: utalised
GPU RAM: utalised
CPU: not utalised
RAM: not utalised

in summary i can use the power of GPU on small models only unfortuntly.
Repository: vscode
Issue: Column selection is reset when selecting with arrow keys
Labels: bug,editor-core,editor-columnselect

Type: <b>Bug</b>

Steps to reproduce:

1. Enable column selection mode. 
2. Put cursor to beginning of a line and select several lines. 
3. Press `Ctrl+Shift+Right` several times to select several words in each line. 

   ![image](https://github.com/microsoft/vscode/assets/6237024/45a4ad78-61a2-4faf-a7ff-0bfd31417955)

4. Press `Shift+Left` to unselect the character to the left of the cursor in each line. 
    -  Expected: one character is unselected in each line.
       
       ![image](https://github.com/microsoft/vscode/assets/6237024/17abb1c5-1b3a-4dcc-a9e0-85545fdcd8ca)

    - Actual: the column selection is lost and the character is unselected only in the first line. 

      ![image](https://github.com/microsoft/vscode/assets/6237024/03e99a50-63ac-4b30-91da-65e7c092f9b4)

`Shift+Right` in Step 4 breaks it the same way. 

If you start the column selection with `Shift+Right` rather than `Ctrl+Shift+Right`, then everything works. It looks like the combinatoin of word selection with subsequent character selection breaks it. 

VS Code version: Code 1.86.2 (903b1e9d8990623e3d7da1df3d33db3e42d80eda, 2024-02-13T19:40:56.878Z)
OS version: Windows_NT x64 10.0.22621
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz (8 x 2112)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled|
|Load (avg)|undefined|
|Memory (System)|15.82GB (5.32GB free)|
|Process Argv|--crash-reporter-id 78edb399-aebd-4224-8197-f1211e83f080|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (7)</summary>

Extension|Author (truncated)|Version
---|---|---
scratchpads|bue|1.0.0
gitlens|eam|2024.2.2104
intellij-idea-keybindings|k--|1.5.13
debugpy|ms-|2024.0.0
python|ms-|2024.0.1
vscode-pylance|ms-|2024.2.2
remote-wsl|ms-|0.86.0


</details><details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:30899288
c4g48928:30535728
azure-dev_surveyone:30548225
vscrpc:30673769
a9j8j154:30646983
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
pythontbext0:30879054
accentitlementsc:30887149
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
pydisww2:30959801
edj9j583:30969295
a89i1917:30961429
7j2b6412:30969109
bg6jg535:30958357

```

</details>

<!-- generated by issue reporter -->
Repository: PowerToys
Issue: Control Awake's Keep Screen On Feature via Policy
Labels: Idea-Enhancement,Help Wanted,Cost-Small,Area-Enterprise,Product-Awake

### Description of the new feature / enhancement

As of version 0.78, the existing group policy templates allow you to disable utilities via the **Configure enabled state for individual utilities** policy. This means that the Awake utility can be disabled entirely. However, it would be useful to control just the **Keep Screen On** setting within the Awake utility. This ensures that screen lock timeout policies can still be enforced even in scenarios where you don't want your computer to go to sleep.

### Scenario when this would be used?

This is useful in an organization where your computer's lock screen automatically turns on after X minutes. Having the ability to prevent keeping the screen on allows a computer to still use the Awake utility while also protecting data behind a login.

### Supporting information

[Existing group policy documentation](https://learn.microsoft.com/en-us/windows/powertoys/grouppolicy)
Repository: puppeteer
Issue: [Feature]: Expose `request.urlFragment()` on HTTPRequest
Labels: feature,confirmed,P3

### Minimal, reproducible example

```TypeScript
import puppeteer from 'puppeteer'; // TS/ESM are all supported.

(async () => {
  const browser = await puppeteer.launch();
  const page = await browser.newPage();
  
  page.on('requestfinished', (request) => {
    // expected to print `https://example.com/#foo`, but `https://example.com/` is printed
    console.log(request.url());
  });

  await page.goto('https://example.com/#foo');

  await browser.close();
})();
```


### Error string

no error

### Bug behavior

- [ ] Flaky
- [ ] PDF

### Background

`Protocol.Network.Request` can contain `urlFragment` property, but it's ignored during url construction in `HTTPRequest` class

https://github.com/puppeteer/puppeteer/blob/ceab7a9042fe5fc3f71875e75327bb370f1c43a5/packages/puppeteer-core/src/cdp/HTTPRequest.ts#L100

### Expectation

`console.log(request.url())` expected to print `https://example.com/#foo`

### Reality

`console.log(request.url())` prints `https://example.com/`

### Puppeteer configuration file (if used)

_No response_

### Puppeteer version

22,1.0

### Node version

20.10.0

### Package manager

npm

### Package manager version

10.2.3

### Operating system

macOS
Repository: vscode
Issue: Monitors constantly flickering when interacting with the VSCode window
Labels: bug,upstream,windows,gpu,chromium

<!-- ⚠️⚠️ 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?: **Yes**

<!-- 🪓 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. -->
- VS Code Version: (first noticed with the latest monthly update)
  - Version: 1.86.2 (user setup)
  - Commit: 903b1e9d8990623e3d7da1df3d33db3e42d80eda
  - Date: 2024-02-13T19:40:56.878Z
  - Electron: 27.2.3
  - ElectronBuildId: 26908389
  - Chromium: 118.0.5993.159
  - Node.js: 18.17.1
  - V8: 11.8.172.18-electron.0
  - OS: Windows_NT x64 10.0.19045
- OS Version: Windows 10 version 22H2, OS build 19045.4046
- GPU: NVIDIA GeForce RTX 2080 Ti, driver version 537.42

Steps to Reproduce:

1. Launch VSCode
2. Click off of VSCode and on to a program/windows on a different monitor OR toggle the zoom level (control, +) OR launch a new window via something like "Help: About" from the command palette 
3. Observe monitor flickering off then on (80% of the time, so very frequently when switching between windows)

Demo videos: https://photos.app.goo.gl/KmYpcfEbPETTbwMj6

This does _not_ reproduce when running with `code --disable-gpu`