sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: `Result<u32, u32>` uses less efficient ABI than `Result<i32, u32>`
Labels: C-enhancement,T-compiler,A-layout

I noticed this while writing a codegen test for https://github.com/rust-lang/rust/issues/37939#issuecomment-1218345560.
It seems that `Result<u32, u32>` and `Result<i32, i32>` are passed as two 32-bit numbers, while `Result<i32, u32>` and `Result<u32, i32>` are passed as a single 64-bit number.

Compiler: `rustc 1.65.0-nightly (86c6ebee8 2022-08-16)`

<details>
<summary>Code</summary>

```rust
pub fn result_nop_match_i32(x: Result<i32, i32>) -> Result<i32, i32> {
    match x {
        Ok(x) => Ok(x),
        Err(x) => Err(x),
    }
}
pub fn result_nop_match_u32(x: Result<u32, u32>) -> Result<u32, u32> {
    match x {
        Ok(x) => Ok(x),
        Err(x) => Err(x),
    }
}
pub fn result_nop_match_i32_u32(x: Result<i32, u32>) -> Result<i32, u32> {
    match x {
        Ok(x) => Ok(x),
        Err(x) => Err(x),
    }
}
pub fn result_nop_match_u32_i32(x: Result<u32, i32>) -> Result<u32, i32> {
    match x {
        Ok(x) => Ok(x),
        Err(x) => Err(x),
    }
}
```
</details>

<details>
<summary>LLVM IR</summary>

```llvm-ir
define { i32, i32 } @_ZN7example20result_nop_match_i3217h90973337e0ea1f0bE(i32 noundef %0, i32 %1) unnamed_addr #0 !dbg !6 {
  %2 = insertvalue { i32, i32 } undef, i32 %0, 0, !dbg !11
  %3 = insertvalue { i32, i32 } %2, i32 %1, 1, !dbg !11
  ret { i32, i32 } %3, !dbg !11
}

define { i32, i32 } @_ZN7example20result_nop_match_u3217ha367bf54ac4241a2E(i32 noundef %0, i32 %1) unnamed_addr #0 !dbg !12 {
  %2 = insertvalue { i32, i32 } undef, i32 %0, 0, !dbg !13
  %3 = insertvalue { i32, i32 } %2, i32 %1, 1, !dbg !13
  ret { i32, i32 } %3, !dbg !13
}

define i64 @_ZN7example24result_nop_match_i32_u3217h0912c9953cfa7e17E(i64 returned %0) unnamed_addr #0 !dbg !14 {
  ret i64 %0, !dbg !15
}

define i64 @_ZN7example24result_nop_match_u32_i3217h8fc452067b26b8ddE(i64 returned %0) unnamed_addr #0 !dbg !16 {
  ret i64 %0, !dbg !17
}
```
</details>

https://rust.godbolt.org/z/n91oWdjMh

I'm not sure if there's something stopping `Result<u32, u32>` from being coerced to a single 64-bit number (maybe some heuristic for auto-vectorization?), but this seemed a bit odd to me. It's also a bit surprising to me that `Result<u32, u32>` is represented as `define { i32, i32 }`, but I don't really know a lot about the Rust ABI.
Repository: pytorch
Issue: Unhelpful error message from torch.linalg.ldl_factor
Labels: triaged,module: linear algebra,module: edge cases

### 🐛 Describe the bug

When performing an ldl_factor on a matrix of zeros (or entries smaller than some epsilon value), I get the following error:
RuntimeError: false INTERNAL ASSERT FAILED at ```../aten/src/ATen/native/BatchLinearAlgebra.cpp":1504, please report a bug to PyTorch. torch.linalg.ldl_factor: Unknown error code: 1.```


Here is a simple example:

import torch
ld,pivot=torch.linalg.ld_factor(torch.zeros(5,5)) 

I wouldn't expect this to work, of course, because L is undefined in this case.  But perhaps it could do a saner exception check before (instead of) passing the input to LAPACK.  Incidentally, not sure why it's giving me a positive error code as I believe this conflicts with the LAPACK documentation...

### Versions

[pip3] numpy==1.21.5
[pip3] pytorch-lightning==1.7.0
[pip3] pytorch-wavelets==1.3.0
[pip3] rotary-embedding-torch==0.1.5
[pip3] torch==1.12.0
[pip3] torch-geometric==2.0.4
[pip3] torchfile==0.1.0
[pip3] torchinfo==1.7.0
[pip3] torchmetrics==0.9.3
[pip3] torchvision==0.13.0
[conda] numpy                     1.21.5                   pypi_0    pypi
[conda] pytorch-lightning         1.7.0                    pypi_0    pypi
[conda] pytorch-wavelets          1.3.0                    pypi_0    pypi
[conda] rotary-embedding-torch    0.1.5                    pypi_0    pypi
[conda] torch                     1.12.0                   pypi_0    pypi
[conda] torch-geometric           2.0.4                    pypi_0    pypi
[conda] torchfile                 0.1.0                    pypi_0    pypi
[conda] torchinfo                 1.7.0                    pypi_0    pypi
[conda] torchmetrics              0.9.3                    pypi_0    pypi
[conda] torchvision               0.13.0                   pypi_0    pypi
I am using the nightly build and running on the CPU.

cc @jianyuh @nikitaved @pearu @mruberry @walterddr @IvanYashchuk @xwang233 @Lezcano
Repository: next.js
Issue: getStaticProps doesn't revalidate when redirect is returned
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```
    Operating System:
      Platform: darwin
      Arch: x64
      Version: Darwin Kernel Version 21.6.0: Sat Jun 18 17:07:25 PDT 2022; root:xnu-8020.140.41~1/RELEASE_X86_64
    Binaries:
      Node: 16.15.0
      npm: 8.9.0
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 12.2.6-canary.1
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
```

### What browser are you using? (if relevant)

Chrome 104.0.5112.79

### How are you deploying your application? (if relevant)

next start

### Describe the Bug

I'm querying the DB for redirects added via CMS, if a record is found `getStaticProps` should return a redirect but instead it is returning the cached version of that particular page even if the revalidation is triggered manually with ISR.

I noticed this happening only when `isrMemoryCacheSize` is set within the `experimental` config in `next.config.js` with a value less than 75.

### Expected Behavior

- Access a built page: `/test`
- Enable redirect and revalidate page
- Revalidated page should redirect to `/`

### Link to reproduction

https://github.com/ramirorinaldi/next-redirect-bug

### To Reproduce

- npm run build && npm run start
- go to http://localhost:3000/test
- enable redirect via api http://localhost:3000/api/enable
- go to http://localhost:3000/test to trigger revalidation
- refresh http://localhost:3000/test (should redirect instead of keep loading the page)
Repository: flutter
Issue: Next steps for Dirty Region Management within the Embedder API.
Labels: c: new feature,engine,e: embedder,P3,team-engine,triaged-engine

The next steps for the implementation of Dirty Region Management within the Embedder API include:

- [ ] https://github.com/flutter/flutter/issues/109723 Adding Metal support.
- [ ] https://github.com/flutter/flutter/issues/109724 Adding Vulkan support.

## Background
Dirty Region Management is already supported in the Embedder API for OpenGL-based embedders (https://github.com/flutter/engine/pull/35022). The framework used in this implementation should be used as a guideline for the Metal and Vulkan implementations as well.

## Impact
Rendering every pixel on the screen at every frame is a slow and demanding process. Making sure that embedders can perform partial repaint would significantly improve raster times and apps' energy consumption.
Repository: flutter
Issue: Add Dirty Region Management to Metal-based embedders.
Labels: c: new feature,engine,e: embedder,P3,team-engine,triaged-engine

At the moment, Metal-based embedders have no way to perform partial repaint. Only rendering the parts of the screen that need updating should great reduce raster time and the energy consumption of applications.

- The design document for this implementation can be found at: [flutter.dev/go/drm-embedder-metal](http://flutter.dev/go/drm-embedder-metal)
- A prototype of the implementation can be found at: https://github.com/flutter/engine/pull/35193
Repository: godot
Issue: Load png from same pck not working
Labels: topic:core,needs testing

### Godot version

4.0 dev

### System information

Windows 10

### Issue description

When you loading png image in gd script which is inside of same pck you will get error, that resource didn't exists

When you try to load the same image from root project, everything works great 

### Steps to reproduce

1. Create a project A
2. Add png image to project A
3. Add scene to project A
4. Attach script to scene from step 3, and load png form step 2
5. Export project as pck or zip
6. Create a project B
7. Add scene to project B
8. Attach script to scene from step 7
9. Load pck file in project B
10. Add scene from project A to project B as child
11. Run project B

### Minimal reproduction project

_No response_
Repository: flutter
Issue: Add Dirty Region Management to Vulkan-based embedders. 
Labels: c: new feature,engine,e: embedder,P3,team-engine,triaged-engine

At the moment, Vulkan-based embedders have no way to perform partial repaint. Only rendering the parts of the screen that need updating should great reduce raster time and the energy consumption of applications.

- The design document for this implementation can be found at: [flutter.dev/go/drm-embedder-vulkan](http://flutter.dev/go/drm-embedder-vulkan)
- A prototype of the implementation can be found at: https://github.com/flutter/engine/pull/35148
Repository: excalidraw
Issue: panning on trackpad on chrome tends to trigger history bf behavior
Labels: bug,high priority

Panning canvas (two fingers) on touchpad works fine (no back/forward history behavior triggered), until you hover over a non-canvas DOM element (which we likely don't prevent in various ways we do with canvas), which triggers browser bf behavior. That's fine.

But in chrome (at least on MacOS), if you cancel the bf change (or it doesn't leave the app domain and you go back to canvas, e.g. in case of Excalidraw+), even panning the canvas tends to trigger the bf behavior.

- [ ] does it reproduce on Windows laptop trackpad?
Repository: TypeScript
Issue: "used before its declaration" errors not reported when variable/enum/class is used as decorator parameter on class member
Labels: Bug,Help Wanted

# Bug Report

### 🔎 Search Terms
decorator
enum
used before its declaration
TS2448, TS2449, TS2450
isolatedModules
preserveConstEnums

### 🕗 Version & Regression Information

- This is a crash: In the transpiled JavaScript, not in tsc itself.
- This is the behavior in every version I tried (3.1 through 4.7), and I reviewed the FAQ for entries about decorators (https://github.com/Microsoft/TypeScript/wiki/FAQ#decorators)

### ⏯ Playground Link

[Workbench Repro](https://www.typescriptlang.org/dev/bug-workbench/?target=1&ssl=18&ssc=2&pln=3&pc=1#code/PTAEAEFMA8AdIE4EsC2kB2AXAhgGwCKQDGA9gtpmQM4BcomCArpALABQ7AZo+kZkiXSg0mABYkAJoVLlKCABQA3PMzpUGSdAHMAlHWzoAnqADe7AJAJImRgiHydoALwA+UwF8A3O3ft2qWDJMU2FrcSliMgoyUHdQTgQSFFAAIgA6YBFw6Si5FO8ONhBwLMkc2TJ5AFlDAFF0RhQ05VxmAEZHEFAAYTIrPlxjK0CETCpQesbQAHIayZRp0EYqSAlQACNITjJIUCQx0AliXGxZAXsAFQBlACYAFgBWAAYddhgR4KITqnGa7u-xmY2KAQRBShEZNEFHMGk0Wu1OmAAHIkUCIRIIUDDIKrdig0CwRjrXBIIjxEgkBx0RQkJBrIH43xsJlvWGgGFTBmg+GQNrOVI8topAA0PiAA)

### 💻 Code

```ts repro
// @experimentalDecorators: true

function methodDecorator(value: string): any {
	return () => {};
}

//@methodDecorator(MyEnum.value1) // Correctly reports Enum 'MyEnum' used before its declaration (TS2450)
export class MyClass {
    @methodDecorator(MyEnum.value1) // No error reported
    public foo(): void {
    }
}

enum MyEnum {
    value1 = "value1",
}
```


### 🙁 Actual behavior

- No TS2450 "Enum 'MyEnum' used before its declaration" is reported.
- At runtime, this code crashes during the initial script execution:
```
C:\repos\TS2450_decorator_repro\program.js:19
        methodDecorator(MyEnum.value1) // No error reported
                               ^

TypeError: Cannot read properties of undefined (reading 'value1')
    at C:\repos\TS2450_decorator_repro\program.js:19:32
    at Object.<anonymous> (C:\repos\TS2450_decorator_repro\program.js:22:2)
    at Module._compile (node:internal/modules/cjs/loader:1101:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
    at node:internal/main/run_main_module:17:47
```


### 🙂 Expected behavior

TS2450 (and other similar errors like 2448 for Block-scoped variables or 2449 for classes) should be correctly reported.
Repository: yt-dlp
Issue: Option to delete original file after postprocessing while using --split-chapter
Labels: enhancement,triage

### DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

- [X] I understand that I will be **blocked** if I remove or skip any mandatory\* field

### Checklist

- [X] I'm requesting a feature unrelated to a specific site
- [X] I've looked through the [README](https://github.com/yt-dlp/yt-dlp#readme)
- [X] I've verified that I'm running yt-dlp version **2022.08.14** ([update instructions](https://github.com/yt-dlp/yt-dlp#update)) or later (specify commit)
- [X] I've searched the [bugtracker](https://github.com/yt-dlp/yt-dlp/issues?q=) for similar issues **including closed ones**. DO NOT post duplicates
- [X] I've read the [guidelines for opening an issue](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#opening-an-issue)

### Provide a description that is worded well enough to be understood

Suppose we want to download a channel or playlist that contains individual videos of full albums. We attempt to download the all of its content using,
`yt-dlp -x --split-chapter <channel/playlist url>`
yt-dlp will extract audio and then split the chapters into individual tracks as desired, but the original full-album file from which the individuals tracks were produced remains. If we are using yt-dlp for music archival purposes (as I am), this can end up taking up a lot of unnecessary storage and can be quite a pain to clean up after the fact. It would be nice to have an option, `--no-keep-unsplit` for example, that will remove the unsplit file after splitting is complete. 

### Provide verbose output that clearly demonstrates the problem

- [ ] Run **your** yt-dlp command with **-vU** flag added (`yt-dlp -vU <your command line>`)
- [ ] Copy the WHOLE output (starting with `[debug] Command-line config`) and insert it below

### Complete Verbose Output

_No response_
Repository: vscode
Issue: Continue Working On from a multi-root workspace 
Labels: feature-request,workbench-multiroot

<!-- ⚠️⚠️ 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. -->
Repository: kubernetes
Issue: Relinquish leadership during zonal outage
Labels: kind/bug,sig/api-machinery,triage/accepted

### What happened?

A kubernetes cluster deployed in AWS is subject to occasional zonal [outages](https://aws.amazon.com/premiumsupport/technology/pes/). In the most kubernetes cluster setup usecases(e.g kops), all control plane components(e.g kube-apiserver, kube-scheduler, kube-controller-manager) are setup as static pods. Depending on how the cluster is setup further, there could be more components(e.g webhooks, authenticator, cloud-controller-manager, etc) running as static pods too. If the kubernetes control plane(master) instances are part of a zone experiencing outage, the cluster can have undesired experience based on behavior of the specific component failing during the outage.

During zonal outages that do not affect apiserver to etcd connectivity, any controller that depends on leader election and is currently hosted on an instance in the affected zone continues to renew its lease. Continuing to hold the lease is fine as long as the controller's workload is only dependent on apiserver objects. In cases where the controller's work depends on aws api calls(e.g. cloud-controller-manager), success of the controller is not guaranteed. In such cases the workloads would benefit from lease transfer.

As an operator of clusters in AWS, it might be beneficial if there was a way to indicate the controllers using abstract rules (that work across cloud) to exclude controllers from taking lease if certain rules match. The rule can be created as a separate api object that cluster admin can control. During zonal outages, the operator can refer to the aws status page and indicate any lease based controllers to evacuate from the bad zone. 

What are your thoughts on the idea. Is there any prior art around this to explore.
Repository: rust
Issue: Tracking Issue for refined trait implementations
Labels: T-lang,C-tracking-issue,F-refine

<!--
NOTE: For library features, please use the "Library Tracking Issue" template instead.

Thank you for creating a tracking issue! 📜 Tracking issues are for tracking a
feature from implementation to stabilisation. Make sure to include the relevant
RFC for the feature if it has one. Otherwise provide a short summary of the
feature and link any relevant PRs or issues, and remove any sections that are
not relevant to the feature.

Remember to add team labels to the tracking issue.
For a language team feature, this would e.g., be `T-lang`.
Such a feature should also be labeled with e.g., `F-my_feature`.
This label is used to associate issues (e.g., bugs and design questions) to the feature.
-->

This is a tracking issue for the RFC "Refined trait implementations" (rust-lang/rfcs#3245).
The feature gate for the issue is `#![feature(refine)]`.

### About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

### Steps
<!--
Include each step required to complete the feature. Typically this is a PR
implementing a feature, followed by a PR that stabilises the feature. However
for larger features an implementation could be broken up into multiple PRs.
-->

- [ ] Implement the RFC (cc @rust-lang/compiler -- can anyone write up mentoring
      instructions?)
- [ ] Adjust documentation ([see instructions on rustc-dev-guide][doc-guide])
- [ ] Stabilization PR ([see instructions on rustc-dev-guide][stabilization-guide])

[stabilization-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#stabilization-pr
[doc-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#documentation-prs

### Unresolved Questions
<!--
Include any open questions that need to be answered before the feature can be
stabilised.
-->

- [ ] Should `#[refine]` be required in future editions? Options:
  - Required
  - Recommended (by a lint that can be disabled on refined impls without a `#[refine]`)
  - Not recommended (refined APIs are available without the attribute)

See the RFC for more information.

### Implementation history

<!--
Include a list of all the PRs that were involved in implementing the feature.
-->
Repository: PowerToys
Issue: Powertoy Run adds to the add-on market/增加插件市场
Labels: Idea-Enhancement,Product-PowerToys Run,Needs-Triage

### Description of the new feature / enhancement

1. Open the Powertoy Run API/开放api
2. Powertoy Run adds to the add-on market/增加插件市场

### Scenario when this would be used?

Add custom plug-in translation/增加自定义插件翻译

### Supporting information

_No response_
Repository: vscode
Issue: Option to prevent quickpicks from dismissing other quickpicks
Labels: feature-request,quick-pick

From https://github.com/microsoft/vscode/issues/141514

The basic problem is that two processes are running in parallel, which may both require some input from the user. If a quickpick/input is shown while another one is visible, the second one will cause the first to be dismissed. This shows up in launch configs, there is probably a task scenario that would show the same issue, or you could imagine other extension-based workflows that end up interrupting each other.

For launch configs, we will add a queue to work around this, but when I am queueing two unrelated pieces of code just because they might trigger quick inputs way downstream, then it seems like I am solving the problem at the wrong layer. I'm not blocked by this issue, I just feel like it might come up again at some point.

However, changing this for all quickpicks at this point seems odd and could possibly be a breaking change for some extension that relies on the dismissing behavior, even on accident.
Repository: godot
Issue: Vulkan: OmniLight3D nodes render improperly after reaching greater than 44 shadow-enabled sources in a scene
Labels: bug,topic:rendering,topic:3d

### Godot version

4.0.alpha14

### System information

Windows 10, Vulkan Clustered, RTX 2060 (516.94)

### Issue description

If there are greater than 44 (?) OmniLights with shadows enabled in a 3D scene, some will begin to attenuate improperly. It also appears to be partly influenced by the range of the light source, and the camera position, with more lights acting strangely as their range is decreased.

Lights will render properly until turning shadows on. Once turned on, the visual bug will appear on some lights ~and will not disappear even if shadows are then turned off, until the scene has been reloaded~. **Edit:** Appears to be unrelated to this issue in specific, mentioned in [#50343](https://github.com/godotengine/godot/issues/50343).

![image](https://user-images.githubusercontent.com/18225391/185286719-44129230-5f8b-46b5-a49b-6001bfa32aa1.png)


Here's a video as well: https://www.youtube.com/watch?v=vL94p9ZuduA

I'm unsure if this is the result of a built-in engine limit, just thought it was a bit too unusual to be intentional.

### Steps to reproduce

- Create a new project
- Add some geometry to be able to see the lights (in the attached project a simple plane mesh was used)
- Begin adding OmniLight3D nodes to the scene (at least 45)
- Enable shadows on all lights
- Observe some lights failing to attenuate properly

### Minimal reproduction project

[lighting-bug.zip](https://github.com/godotengine/godot/files/9367370/lighting-bug.zip)
Repository: go
Issue: runtime: higher system cpu cost by runtime.freespan
Labels: NeedsInvestigation,compiler/runtime

<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.19 darwin/arm64
</pre>

### Does this issue reproduce with the latest release?

yes

### What operating system and processor architecture are you using (`go env`)?
```
$ perf script --header
# arch : x86_64
# nrcpus online : 104
# nrcpus avail : 104
# cpudesc : Intel(R) Xeon(R) Platinum 8269CY CPU @ 2.50GHz
# cpuid : GenuineIntel,6,85,7
```

### What did you do?
running my program


### What did you expect to see?
lower system cpu usage.

### What did you see instead?
system cpu cost about 30 core. 
user cpu cost is only 60 core!

![截屏2022-08-18 下午12 58 05](https://user-images.githubusercontent.com/52686065/185297342-f4f16b26-bf1e-4b76-82f3-dc99edfe6819.png)

i use perf to record callstack and tran it to pprof.

the pprof top means that function native_queued_spin_lock_slowpath cost most cpu.
![截屏2022-08-18 下午12 54 31](https://user-images.githubusercontent.com/52686065/185296869-6a795c52-666b-4618-b048-9d6816042474.png)

hear is the pprof flamegraph, seems that runtime.freespan is the reason.
![截屏2022-08-18 下午12 53 18](https://user-images.githubusercontent.com/52686065/185296721-8011cb51-dde9-44d0-9c38-30d3bab9d104.png)

the memory usage of my machine.

the pprof file:
[cpu.pprof.gz](https://github.com/golang/go/files/9367748/cpu.pprof.gz)