sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: Fancy Zones are changing Border-Style of windows (making it transparent)
Labels: Needs-Triage

### Description of the new feature / enhancement

When using any grid on fancy zones there is ALWAYS a gap between the windows (look pictures). This is not a Problem of my system, because it appears only with fancy-zones snapping-system and NOT with windows default one. It looks like a gap, but when i make a screenshot and zoom in you can see that it is actually not a gap, it is just transparent. But it is NOT transparent in my windows default snapping. I made 2 screenshots: One with a default windows-snap (with 4 windows) and one with a fancy-zone-snap (6 windows). I did move one window to beeing able to make a screenshot and to see the background (for comparing to the transparent gaps). And i did make a picture of each one with 800% zoom to see, that it is actually not a gap, it is just transparent on fancy-zones.

![fancyzones-gap (Groß)](https://github.com/microsoft/PowerToys/assets/66878092/08a7ae23-9a1a-4931-b816-eb7e0d8ee697)
![fancyzones-gap_zoomed (Groß)](https://github.com/microsoft/PowerToys/assets/66878092/07ea6783-d414-469c-be08-e75a74ca42af)
![defaultwindows-no-gap (Groß)](https://github.com/microsoft/PowerToys/assets/66878092/d2d276f8-bcaa-4bfd-9036-a7878ec3ea36)
![defaultwindows-no-gap_zoom (Groß)](https://github.com/microsoft/PowerToys/assets/66878092/cd72e226-c244-4631-92a4-50357c83fc2a)


### Scenario when this would be used?

Fancy-Zones should not change my windows-style, it should only snap windows and not change style of them. 

### Supporting information

_No response_
Repository: bitcoin
Issue: Pause IBD during AssumeUTXO snapshot load
Labels: Feature

### Please describe the feature you'd like to see added.

The `loadtxoutset` RPC call should cause IBD to pause until the snapshot is loaded and the snapshot chain is activated.

### Is your feature related to a problem, if so please describe it.

When I start a fresh node and load a mainnet shapshot (#28553) any progress is completely buried in the log.

More importantly, I get the strong impression, though haven't properly tested this, that the IBD process slows down the snapshot load. This makes sense given the amount of I/O involved. It's definitely slower than the process of creating the snapshot.

On my AMD Ryzen 7950x machine the IBD reaches block 300,000 while the snapshot has only loaded 71.2% (where is triggers a cache flush). By the time 100% is loaded IBD is at 324,000. When the snapshot chainstate is saved IBD reaches 362,000.

### Describe the solution you'd like

Pause IBD until the snapshot is loaded and the snapshot chain is activated.

### Describe any alternatives you've considered

1. Do nothing
2. Keep IBD going but at low priority (how???)

### Please leave any additional context

_No response_
Repository: tauri
Issue: [bug] bundle builder should not use conditional compilation to determine target platform
Labels: type: bug,status: needs triage

### Describe the bug

When attempting to cross-compile from Linux to Windows, I am encountering errors about lacking the GTK "appindicator". Looking at the code in tooling/cli/src/build.rs, it is clear that the platform-specific bundling decisions are mode when tauri cli gets built, not during the target app build. The causes incorrent bundling decisions to be made with host and target platforms differ.

### Reproduction

Follow the guide on cross-compiling Tauri from linux to windows, and notice that tauri.windows.conf.json does not get used during build. If you happen to not have any appindicator installed for linux, you will also see a tauri crash.

### Expected behavior

_No response_

### Full `tauri info` output

```text
WARNING: Only one package manager should be used, but found npm and yarn.
         Please remove unused package manager lock files, will use npm for now!

[✘] Environment
    - OS: Debian 12.0.0 X64
    ✘ webkit2gtk-4.0: not installed
      Visit https://tauri.app/v1/guides/getting-started/prerequisites to learn more about tauri prerequisites
    ✘ rsvg2: not installed
      Visit https://tauri.app/v1/guides/getting-started/prerequisites to learn more about tauri prerequisites
    ✔ rustc: 1.77.2 (25ef9e3d8 2024-04-09)
    ✔ cargo: 1.77.2 (e52e36006 2024-03-26)
    ✔ rustup: 1.27.0 (bbb9276d2 2024-03-08)
    ✔ Rust toolchain: stable-x86_64-unknown-linux-gnu (environment override by RUSTUP_TOOLCHAIN)
    - node: 18.19.0
    - yarn: 1.22.22
    - npm: 9.2.0

[-] Packages
    - tauri [RUST]: 1.6.2
    - tauri-build [RUST]: 1.5.1
    - wry [RUST]: 0.24.8
    - tao [RUST]: 0.16.9
    - tauri-cli [RUST]: 1.5.12
    - @tauri-apps/api [NPM]: 1.5.3 (outdated, latest: 1.5.4)
    - @tauri-apps/cli [NPM]: 1.5.12

[-] App
    - build-type: build
    - CSP: unset
    - distDir: ../dist/spa
    - devPath: http://127.0.0.1:9000/
    - framework: Vue.js (Quasar)
    - bundler: Vite
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: vscode
Issue: Mark cache directories with a CACHEDIR.TAG file to avoid backing up unnecessary data
Labels: feature-request,workbench-os-integration

<!-- ⚠️⚠️ 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. -->

Please could you add the file `CACHEDIR.TAG` to any directories that contain ephemeral cache files so that our backups don't contain lots of useless files?

More information at https://bford.info/cachedir/ and this duplicates https://github.com/microsoft/vscode/issues/144028 which was unfortunately closed due lack of votes, but the issue is still relevant.

This would seem to be a very trivial feature to implement, whereas it causes a fair bit of work for anyone to work around, considering the various and numerous directories used by VS Code to cache files.

This is not solved by https://github.com/microsoft/vscode/issues/3884 although a workaround would be made simpler if VS Code didn't put cache files in the user's `/home/<username>/.config` directory and instead put them in a dedicated cache location.
Repository: vscode
Issue: Assertion Failure When Extension Throws Error
Labels: bug,custom-editors

Implementation:
```ts
public async resolveCustomTextEditor(
		document: TextDocument,
		webviewPanel: WebviewPanel,
		token: CancellationToken
	): Promise<void> {
		throw new Error("invalid document extension!");
}
```
Error message when I open such a custom text editor:

![Code_-_Insiders_g0TzYbmo5j](https://github.com/microsoft/vscode/assets/2931520/31f6d384-eb16-43ee-9f90-53a163e53c97)

![Code_-_Insiders_1FScZwOBtv](https://github.com/microsoft/vscode/assets/2931520/c2fb4ec8-85ac-46ef-af29-e0e790851f1a)

I think the extension error message should be shown instead and not the internal assertion failure message.
Repository: flutter
Issue: [Impeller] GLES Worker upload of textures isn't thread safe.
Labels: P3,e: impeller,team-engine,triaged-engine

See: https://github.com/flutter/engine/pull/52430

Refactoring to remove the IO thread upload of images broke the GLES renderer. We'll need to investigate why this is required only for the GLES backend.
Repository: next.js
Issue: Error 500: The detected locale does not match the locale in the query
Labels: bug,Internationalization (i18n),Pages Router

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/distracted-bouman-y6rzfc

### To Reproduce

1. Setup the `next.config.js` like this
```
const nextConfig = {
  i18n: {
    locales: ["en", "de", "fr"],
    defaultLocale: "en",
  },
};
```
2. Use a `[...page].tsx` in `pages directory (for more details check the reproducible sandbox associated to this ticket
3. Start the server
4. In the URL type `/fr/en` 
5. Error 500 appears with this title: `Error: Invariant: The detected locale does not match the locale in the query. Expected to find 'fr' in '/en' but found 'en'}`

### Current vs. Expected behavior

We expect to receive a 200 issue instead of 500, because this page should render with the query parameter set to value `en` and locale set to `fr`

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
  Available memory (MB): 4102
  Available CPU cores: 2
Binaries:
  Node: 20.12.0
  npm: 10.5.0
  Yarn: 1.22.19
  pnpm: 8.15.6
Relevant Packages:
  next: 14.2.3 // Latest available version is detected (14.2.3).
  eslint-config-next: 14.2.1
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.4.5
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Internationalization (i18n), Pages Router

### Which stage(s) are affected? (Select all that apply)

next dev (local), next start (local), Vercel (Deployed), Other (Deployed)

### Additional context

![image](https://github.com/vercel/next.js/assets/42861634/390bda18-c070-42fd-a6f3-2063b8223004)

**This issue affects 14 and 13 versions of NextJs**

This issue has been reported on `13.5.6` to here: https://github.com/vercel/next.js/issues/52314
Repository: angular
Issue: FormGroup.reset() input typings are incorrect
Labels: help wanted,area: forms,good first issue,P3,area: docs

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

Don't known / other

### Is this a regression?

No

### Description

The example for resetting a FormGroup that is given [here](https://angular.io/api/forms/FormGroup#reset-the-form-group-values-and-disabled-status) does not match the typing of `FormGroup.reset()`. According to the typings, that `{value: 'name', disabled: true}` is invalid.

The typing of `FormGroup.reset()` should accept `{value: T, disabled: boolean}` for a FormControl<T> because that is how the functionality works. 

![image](https://github.com/angular/angular/assets/86434286/bd0809f5-eb47-4aad-affa-558140af2d09)


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

https://replit.com/@david-snyder-in/Typing-Issues#src/app/app.component.ts

### Please provide the exception or error you saw

```true
Type '{ value: string; disabled: true; }' is not assignable to type 'string'.
```


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

```true
Angular CLI: 17.3.2
Node: 20.9.0
Package Manager: npm 10.1.0
OS: win32 x64

Angular: 17.3.2
... animations, cdk, cli, common, compiler, compiler-cli, core
... forms, language-service, material, platform-browser
... platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1703.2
@angular-devkit/build-angular   17.3.2
@angular-devkit/core            17.3.2
@angular-devkit/schematics      17.3.2
@angular/fire                   17.0.1
@schematics/angular             17.3.2
rxjs                            7.8.1
typescript                      5.4.3
zone.js                         0.14.4
```


### Anything else?

_No response_
Repository: vscode
Issue: Certain Edit menus should not be active without a selection (macOS)
Labels: bug,macos,menus

Type: <b>Bug</b>

1. Open a new document in VS Code and a new document in TextEdit
2. Look at the Edit menu in both apps
3. See that Copy and Cut are active in VS Code, but not active in TextEdit

This is standard behavior for any well behaved macOS app, because without a selection, you cannot copy or cut. Beyond aesthetics, having those menus enabled all the time breaks automation tools such as Keyboard Maestro.

In Keyboard Maestro, you can use an action to check on a menu's status, so you can have macros that are only functional when there's a selection: If the Copy menu is avaialble, then the macro should be able to work.

Those macros break in VS Code, and they really should work fine. I can sort of work around it by just trying the Copy command first, and then comparing the before-and-after clipboards, but that's a pain.

The menus should not be active unless there's a selection.

VS Code version: Code 1.88.1 (Universal) (e170252f762678dec6ca2cc69aba1570769a5d39, 2024-04-10T17:42:52.765Z)
OS version: Darwin arm64 23.4.0
Modes:


<!-- generated by issue reporter -->
Repository: flutter
Issue: [Impeller] AHB swapchains on emulators are not functional.
Labels: P3,e: impeller,team-engine,triaged-engine

Rendering to AHB swapchains on emulators via a Vulkan command buffer doesn't populate the buffer.
Repository: go
Issue: x/tools/go/analysis/passes/unusedwrite: detect dead stores to local vars
Labels: NeedsFix,Analysis

During review of https://go.dev/cl/581555, @timothy-king pointed out that I had defined a local variable using an if/else statement and then failed to use it after the statement, something like this:

```go
 func f(pass *Pass), filename string) {
 	readFile := pass.ReadFile
 	if readFile == nil {
 		readFile = os.ReadFile
 	}
 	os.ReadFile(filename) // oops, I meant readFile
 }
```

The assignment to readFile is a dead store. We should flag this as a likely error.
Repository: rust
Issue: `#![feature(generic_const_exprs)]` does not compile stable code related to lifetimes
Labels: T-compiler,C-bug,A-const-generics,F-generic_const_exprs,S-has-mcve

Concretely, consider the following code which compiles perfectly fine under both stable and nightly rust
```rust
use std::marker::PhantomData;

const CONSTANT_M: usize = 4;

struct Foo<T, const GENERIC_M: usize> {
    content: PhantomData<[T; GENERIC_M]>
}

struct Foobar<'a, T>
    where T: 'a
{
    data: &'a T
}

fn create_foo<'a, F>(_: F) -> &'a Foo<i32, CONSTANT_M>
    where F: FnMut(i64) -> ()
{
    Box::leak(Box::new(Foo { content: PhantomData }))
}

fn create_foobar() -> Foobar<'static, Foo<i32, CONSTANT_M>> {
    let create = |_: i64| ();
    Foobar { data: create_foo::<'static, _>(|y| create(y)) }
}
```
[Playground](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=1a709c7f4592fd0e3c94dd8122e5656a)

This makes complete sense, since the lifetime parameters on the function `create_foo()` clearly specify that `F` must be valid in the body of the function, but not necessarily for the whole lifetime `'a`. Note also that the code uses const generics, but only the subset that has been stabilized.

However, just adding `#![feature(generic_const_exprs)]` without changing anything else gives a compiler error
```text
closure may outlive the current function, but it borrows `create`, which is owned by the current function
```
within `create_foobar()`. This should not be the case, as the closure stored in the variable `create` does not have to outlive the current function, or even live for `'static`.
[Playground](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=366376a3dc7ef45926642e86054b8410)

I am using rustc 1.77.0-nightly.

**Edit** Significantly simplified example code.
Repository: godot
Issue: Uses system keyboard layout with index 0 on wayland 
Labels: bug,platform:linuxbsd,topic:editor,topic:input

### Tested versions

Reproducible in 4.3 dev5 [c9c17d6ca]

### System information

Arch Linux 6.8.7 - Vulkan (Mobile) - Wayland (GNOME) - dedicated AMD Radeon RX 6700 XT

### Issue description

The Godot editor, when set to "Prefer Wayland" within the editor settings, will always use the system's first keyboard layout on editor startup, not the currently selected one

The following image will result in the editor using the colemak layout
![image](https://github.com/godotengine/godot/assets/47639983/b63f3f9f-a5d3-4a19-ad3e-c3b0101e66ff)

This will make the editor use qwerty
![image](https://github.com/godotengine/godot/assets/47639983/beaf245e-2c48-47e0-8096-e0c92ed9e7e8)



### Steps to reproduce

Have a non qwerty keyboard layout selected, with qwerty still saved as the "default" layout

Enable "Prefer Wayland" within the editor settings

Reload the editor

The scripting tab should now be using qwerty

### Minimal reproduction project (MRP)

N/A
Repository: PowerToys
Issue: FancyZones no setting to allow popup windows snapping
Labels: Issue-Bug,Idea-Enhancement,Product-FancyZones,Needs-Triage

### Microsoft PowerToys version

0.80.1

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

FancyZones

### Steps to reproduce

![Screenshot 2024-04-29 123932](https://github.com/microsoft/PowerToys/assets/168468878/211b0b9d-855d-4586-ba3c-28c2620ba552)


### ✔️ Expected Behavior

setting to show allow popup windows snapping

### ❌ Actual Behavior

no box appears to enable setting. I tried manually enabling in %LocalAppData%\Microsoft\PowerToys\FancyZones\settings but still did not work

### Other Software

_No response_
Repository: PowerToys
Issue: FancyZones doesn't properly distinguish between main and sub-windows like Thunderbird "send dialogue"
Labels: Issue-Bug,Product-FancyZones,Needs-Triage

### Microsoft PowerToys version

0.80.1

### Installation method

PowerToys auto-update

### Running as admin

No

### Area(s) with issue?

FancyZones

### Steps to reproduce

Open Thunderbird and snap main window to a zone.
Start writing a new message and snap the opened dialogue to a different zone.
(optionally) let a task alarm go off, focus the alarm dialogue and snap it to a different zone.
Close the sub-window dialogues.
Close Thunderbird.
Reopen Thunderbird.
Write a new message.
![image](https://github.com/microsoft/PowerToys/assets/12367437/cf8730c1-084d-458d-80dd-df61774efaf5)


### ✔️ Expected Behavior

Thunderbird should remain snapped to the initial zone,
Message composition dialogue should open in the second zone, that it was snapped to.
Alarm dialogue should open in the third zone.

### ❌ Actual Behavior

Thunderbird reopens in either the second or third zone, instead of remaining in its own assigned zone.
Upon re-assigning of Thunderbird to the initial zone, the other dialogues are opened also in the initial zone.
There doesn't seem to be a distinction made between the different windows.

### Other Software

Thunderbird 115.10.1 64-Bit.
Repository: TypeScript
Issue: Removing `node_modules`, running `npm ci` leaves diagnostics behind in ts and tsconfig files
Labels: Needs Investigation

### Acknowledgement

- [X] I acknowledge that issues using this template may be closed without further explanation at the maintainer's discretion.

### Comment

I've been having quite a few watcher problems recently, and have been collecting log files to try and report the problem.

- https://gist.github.com/jakebailey/af583ce2d14b6a1a30339769a3300416
- https://gist.github.com/jakebailey/573e83c9a81a0e0c950c603722e3ed29
- https://gist.github.com/jakebailey/4ad4ce74fbd86e9588a5775e9c89fe2e

The last two come from doing `npm ci` inside of https://github.com/jakebailey/every-ts and https://github.com/jakebailey/hereby, but the first one is a very very simple project: https://github.com/jakebailey/ts-watcher-issue-1

In that one, the first trace is just me opening the already-installed repo, running `rm -rf node_modules`, waiting for the errors to appear in `index.ts` and `tsconfig.json`, and then doing `npm ci`. The errors in `tsconfig.json` do not disappear.

![image](https://github.com/microsoft/TypeScript/assets/5341706/cd1f640f-eb1b-4577-8542-ee97b5a7f876)

In this example, it also reproduces in `--watch` mode.

![ts-watcher-issue-1](https://github.com/microsoft/TypeScript/assets/5341706/4a5795f8-9998-49ea-be59-9281fb7a9fb1)

I also experience this within the TS repo, but I haven't been able to get a trace of that one yet.

@sheetalkamat
Repository: rust
Issue: Different ways of writing `Option::or` codegen differently
Labels: A-LLVM,A-codegen,T-compiler,C-optimization

Copying this here from https://github.com/rust-lang/rust/issues/101210#issuecomment-1732470941 cc @veber-alex 

Demo: https://rust.godbolt.org/z/96W4h87Yn

The currently-optimized form isn't allowed to be transformed into the better one: https://alive2.llvm.org/ce/z/DXXRPX

A couple thoughts on things that might help in the codegen:
- The parameters should be marked `noundef` (this will hopefully be addressed by #123183 )
- While we do seem to emit the `!range` metadata (<https://rust.godbolt.org/z/KKTKTa1qs>), we're hitting the classic problem of us emitting
```llvm
  %4 = load i8, ptr %opta, align 1, !range !3, !noundef !4
  %5 = trunc i8 %4 to i1
  %_3 = zext i1 %5 to i64
  switch i64 %_3, label %bb1 [
    i64 0, label %bb2
    i64 1, label %bb3
  ]
```
And LLVM forgetting *both* different ways that we told it that inputs like `0x00_05` (the one Alive found) are UB.

Maybe us emitting [`trunc nuw`](https://discourse.llvm.org/t/rfc-add-nowrap-flags-to-trunc/77453?u=scottmcm) will be the eventual solution here?  If the `trunc nuw`+`zext` could fold to just `zext` rather than `and `+`zext` maybe it'd be enough...

---

Adding some assumes does give LLVM enough information to be *allowed* to optimize again (<https://alive2.llvm.org/ce/z/e6NWxA>) though seemingly it doesn't from that starting point
```llvm
  %discr0 = and i16 %0, 255
  %discr1 = and i16 %1, 255
  %discr0bound = icmp ult i16 %discr0, 2
  %discr1bound = icmp ult i16 %discr1, 2
  call void @llvm.assume(i1 %discr0bound)
  call void @llvm.assume(i1 %discr1bound)
```
Repository: flutter
Issue: Create developer documention/codelab on lifecycle aware plugin creation
Labels: c: new feature,platform-android,d: api docs,c: proposal,P3,a: plugins,team-android,triaged-android

### Use case

For certain use cases, plugins may need to be aware of Android lifecycle events. (e.g. https://github.com/flutter/flutter/issues/131767) However, it is not clear what the recommended approach is.

### Proposal

We should create documentation or a codelab on how to create lifecycle aware plugins.
Repository: node
Issue: Re-enable test-ubsan.yml
Labels: help wanted,meta

During the latest Node.js major release (https://github.com/nodejs/node/pull/52505) we have had to disable `test-ubsan.yml` due to failing tests on a recent V8 update (https://github.com/nodejs/node/pull/52560).

I have tried to make it work, but due to the short time frame I had to fix it, we have decided to simply disable it for now.

Some insights:

* It seems clang provides a better output and some docs we could use in the suppressions file.
  * Changing from g++ to clang for UBSAN will require changing all the suppression file
Repository: pytorch
Issue: QR Decomposition for Sparse Matrix
Labels: module: sparse,triaged,module: linear algebra

### 🚀 The feature, motivation and pitch

I am working on a problem whose solution needs to run QR decomposition of matrices. The matrices involved in the problem are huge but sparse, which end up occupying a lot of RAM. Because currently pytorch doesn't support QR decomposition of sparse tensors, it is not being possible to use the sparse representation of tensors.

### Alternatives

_No response_

### Additional context

_No response_

cc @alexsamardzic @nikitaved @pearu @cpuhrsch @amjames @bhosmer @jcaip @jianyuh @mruberry @walterddr @xwang233 @Lezcano