sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: Black screen after updating to Version 0.82.1
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.82.1

### Installation method

PowerToys auto-update

### Running as admin

No

### Area(s) with issue?

General

### Steps to reproduce

Update Powertools from the tool itself.
Reboot after install.

### ✔️ Expected Behavior

Nice reboot without any hazzels.

### ❌ Actual Behavior

After update the notice told me to reboot, due to the new features in the File Explorer.
After reboot, I got the login page and I logged in. But only to see a black screen with my mouse pointer on. I waited a looong time, but nothing happend. Ctrl-Alt-Delete let me into the job list, but I could not start anything from there. And I could not see is anything was "hanging" no unusual cpu hoogings.
After three reboots, I tried to do a Fail safe boot, but I was not allowed tue to restrictions. But after 3 reboot, the PC is now running fine.

### Other Software

_No response_
Repository: vscode
Issue: Always collapse directories recursively
Labels: feature-request,tree-widget

<!-- ⚠️⚠️ 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. -->

#32475 added support for alt-clicking directory in order to collapse it recursively. I always prefer this behavior, so I would like to be able to set it as a default.
Repository: rust
Issue: Mutating through `Option::inspect` gives bogus suggestion
Labels: A-diagnostics,T-compiler,D-invalid-suggestion

### Code

```Rust
#[derive(Debug)]
struct A {
    a: u32,
}

fn main() {
    let mut opt = Some(A { a: 123 });
    let ref_mut_opt = opt.as_mut().inspect(|a| {
        a.a += 123;
    });
    dbg!(ref_mut_opt);
}
```


### Current output

```Shell
error[E0594]: cannot assign to `a.a`, which is behind a `&` reference
  --> src/main.rs:18:9
   |
17 |     let ref_mut_opt = opt.as_mut().inspect(|a| {
   |                                             - consider changing this binding's type to be: `&mut &mut A`
18 |         a.a += 123;
   |         ^^^^^^^^^^ `a` is a `&` reference, so the data it refers to cannot be written
```


### Desired output

_No response_

### Rationale and extra context

The compiler suggests to "consider changing this binding's type". But `Option::inspect` is outside my control, and it will give me a `& &mut A`. There is nothing for me to change there.

Here is a playground link: https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=f54e1ae60f8e1a790c6a6379afe746fa

The code comes from a broken `clippy` suggestion which I also raised here: https://github.com/rust-lang/rust-clippy/issues/13185

### Other cases

_No response_

### Rust Version

```Shell
rustc 1.82.0-nightly (7120fdac7 2024-07-25)
binary: rustc
commit-hash: 7120fdac7a6e55a5e4b606256042890b36067052
commit-date: 2024-07-25
host: x86_64-apple-darwin
release: 1.82.0-nightly
LLVM version: 18.1.7
```


### Anything else?

_No response_
Repository: stable-diffusion-webui
Issue: [Feature Request]: Triple mean merge mode
Labels: enhancement

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

I'd like to have the ability to get the mean of three models in one go, this could be added fairly easily.

`extras.py`
```
def run_modelmerger(...):

    def get_sum(theta1, theta2):
        return theta1 + theta2

    def triple_mean(theta0, theta1_2_diff, alpha):
        return (theta0 + theta1_2_diff) / 3

    def filename_triple_mean():
        a = primary_model_info.model_name
        b = secondary_model_info.model_name
        c = tertiary_model_info.model_name

        return f"_triple_mean ({a}) + ({b}) + ({c})"

    theta_funcs = {
        ...
        "Triple mean": (filename_triple_mean, get_sum, triple_mean),
    }

```

`ui_checkpoint_merger.py`
```
    interp_descriptions = {
        ...
        "Triple mean": interp_description_css.format("The mean between three models, M is ignored. Requires three models; A, B and C. Calculated as (A + B + C) / 3"),
    }

# don't forget to update the Radio control
self.interp_method = gr.Radio(choices=["No interpolation", "Weighted sum", "Add difference", "Mean difference", "Weighted difference", "Triple mean"], value="Weighted sum", label="Interpolation Method", elem_id="modelmerger_interp_method")


```

### Proposed workflow

Like other merge modes.

### Additional information

_No response_
Repository: angular
Issue: Angular deprecates `getLocaleDayNames` without providing a compatible alternative in `Intl.DateTimeFormat`
Labels: area: i18n

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

localize

### Is this a regression?

No

### Description

In Angular 18, the `getLocaleDayNames` function has been deprecated in favor of using the `Intl` API for internationalization. This change is intended to make the framework lighter by relying on built-in browser capabilities. However, I've encountered an issue where `Intl.DateTimeFormat` does not provide equivalent short day names as Angular's `getLocaleDayNames`.

### Using Angular:
```ts
import { getLocaleDayNames, FormStyle, TranslationWidth } from '@angular/common';

const angularDayNames = getLocaleDayNames('en-US', FormStyle.Standalone, TranslationWidth.Short);
console.log(angularDayNames); // ["Su", "Mo", "Tu", "We", "Th", "Fr", "Sa"]
```

### Using Intl:
```ts
const intlFormatter = new Intl.DateTimeFormat('en-US', { weekday: 'short' });
const intlDayNames = [];
for (let i = 0; i < 7; i+=1) {
  const date = new Date(Date.UTC(2021, 0, i + 3)); // 3th January 2021 is a Sunday
  intlDayNames.push(intlFormatter.format(date));
}
console.log(intlDayNames); // ["Sun", "Mon", "Tue", "Wed", "Thu", "Fri", "Sat"]
```

In my native language Polish situation is worse, in Intl for Sunday get e.g. "niedz." (small letter, dot) instead of Angular, 3 letters "nie".

## Where Did This Come From?

In the ECMAScript Internationalization API ([ecma402](https://tc39.es/ecma402/#datetimeformat-objects)) specification, there is a note:
> It is recommended that implementations use the locale and calendar dependent strings provided by the Common Locale Data Repository (available at https://cldr.unicode.org/), and use CLDR "abbreviated" strings for DateTimeFormat "short" strings, and CLDR "wide" strings for DateTimeFormat "long" strings.

This explains why `Intl.DateTimeFormat`  uses the "abbreviated" format for "short" strings. The ICU library, which `Intl` relies on, follows these guidelines. You can check these values in the ICU data files, such as [this one for English](https://github.com/unicode-org/icu/blob/main/icu4c/source/data/locales/en.txt#L904).
Unfortunately, there is no way to get the "Short" values from `Intl` as its "short" always returns "abbreviated".

### What I Expect

I doubt that ECMA or ICU will change their behavior regarding these formats. Therefore, I would like Angular to provide a solution that is compatible with the old behavior. 



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

_No response_

### Please provide the exception or error you saw

_No response_

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

```true
Angular Version: 18.0.6
```


### Anything else?

Adding a `weekdaysICU` option to `Intl.DateTimeFormat` would provide a much-needed compatibility layer for developers transitioning from Angular's `getLocaleDayNames` to the Intl API, ensuring that day names are formatted as expected without requiring additional libraries or workarounds.
Repository: pytorch
Issue: BuildExtension breaks build because of absolute path
Labels: module: cpp-extensions,triaged

When trying to build a Custom CUDA extension with the [build](https://pypi.org/project/build/) frontend, I ran into this issue : 

```
[...]

error: Error: setup script specifies an absolute path:

    path/to/my/cpp/source.cpp

setup() arguments must *always* be /-separated paths relative to the
setup.py directory, *never* absolute paths.


ERROR Backend subprocess exited when trying to invoke build_wheel
```

This is because `BuildExtension` makes paths to sources absolute for ninja when using the `use_ninja=True` option.
This is tied to the code on this line [torch/utils/cpp_extension.py#L2328](https://github.com/pytorch/pytorch/blob/83db609ee5a35e77e63904c01d6036df41db451c/torch/utils/cpp_extension.py#L2328), and probably any other use of `abspath` in `cpp_extension` .

This is forbidden by `build` because the consensus seems to be that modern packages should be self-contained, the rule seems to be referenced [here](https://github.com/pytorch/pytorch/blob/83db609ee5a35e77e63904c01d6036df41db451c/torch/utils/cpp_extension.py#L1116) in the `torch.utils.cpp_extension` code.

Although the build runs fine when building with `python setup.py build` I think this should be fixed because `python setup.py sdist` and `python setup.py bdist_wheel` are being deprecated as mentionned [here](https://packaging.python.org/en/latest/discussions/setup-py-deprecated/#what-commands-should-be-used-instead)

A temporary fix is to pass ~`partial(BuildExtension, use_ninja=False)`~ `BuildExtension.with_options(use_ninja=False)` to `setup()` to force not using ninja, which is not ideal.

cc @malfet @zou3519
Repository: rust
Issue: bootstrap should be able to fully rely on RUSTC_WRAPPER
Labels: C-cleanup,T-bootstrap

With https://github.com/rust-lang/cargo/pull/13659, cargo now respects RUSTC_WRAPPER for all rustc invocations. So bootstrap should be able to set RUSTC to a non-existing binary and rely on RUSTC_WRAPPER for everything, which could simplift some logic.

~~See https://github.com/rust-lang/rust/pull/127682 for what that could look like. However, this is currently blocked on https://github.com/rust-lang/libc/issues/3772, and there are likely other components that also still use RUSTC (e.g. Miri and/or clippy might rely on it when running in `x.py`).~~
Repository: three.js
Issue: BatchedMesh and gl.LINES, gl.POINTS
Labels: Suggestion

### Description

I am currently using BatchedMesh extensively -- not just with meshes but also with `gl.LINES` and `gl.POINTS`

Note that multidraw does accept a mode: `extension.multiDrawElementsWEBGL( mode, ... )`

It may be unintended, but the `isBatchedMesh` check in `WebGLRenderer` does not set the mode; rather it is set a few lines before with checks on `isPoint` and `isLine`. This is very convenient and everything almost works out of the box. Only the points shader isn't fully compatible.

### Solution

The only snag is that `points.glsl.js` needs to add `	#include <batching_vertex>`

### Alternatives

Well, the shader could be manipulated with a string replace but I think that is a gnarly hack

### Additional context

I do want to note that while I don't actually use the THREE.BatchedMesh class very much, I have my own class with `isBatchedMesh = true` to benefit from access to multidraw
Repository: pytorch
Issue: Adding betainc with backward operation
Labels: triaged,module: special

### 🚀 The feature, motivation and pitch

#58700 and #129836 don't support GPU, due to 'gpu_kernel_with_scalars' with only one scalar value.
The only contribution point in #129836 except re-indentation("./aten/src/ATen/native/BinaryOps.cpp") is 
```
#include <ATen/ops/special_betainc.h>
#include <ATen/ops/special_betainc_native.h>
```
I made this part Co-authored-by @richwomanbtc

### Alternatives

I changed it to 'gpu_kernel_with_scalars_tenary' which is new function I made.

### Additional context

I'll post PR, plz review that. Thanks

cc @mruberry @kshitij12345
Repository: svelte
Issue: spreading with `this` attribute: `<svelte:element>` must have a 'this' attribute with a value
Labels: awaiting submitter

### Describe the bug

When we set the `this` attribute of `svelte:element` explicitly via an object containing the `this` attribute, everything is as expected.
But when we spread that object in the `svelte:element` component the compiler does not consider that `this` attribute.

### Reproduction

https://stackblitz.com/edit/vitejs-vite-w8nmej?file=src%2FApp.svelte

### Logs

_No response_

### System Info

```shell
skipping this as it is happening everywhere, like in stackblitz
```


### Severity

annoyance
Repository: rust
Issue: compiletest: pin or restrict supported external dependency versions
Labels: C-cleanup,E-hard,T-bootstrap,A-compiletest,A-run-make,E-needs-design

To the best of my knowledge, test suites supported by compiletest currently rely on external dependencies in e.g. ui or run-make test suites but we do not have any sanity checks on their versions or even the specific external dependency used. For example, which C/C++ compilers are picked for a given environment usually calls out to something like the `cc` crate, but we don't otherwise pin them down. This makes reproducing the tests locally very challenging or near impossible. Or for Python, I don't think we sanity check which Python versions are "supported" by the test suites.
Repository: opencv
Issue: Problems with DrawAxis function
Labels: bug,category: objdetect

### System Information

OpenCV version: opencv-python 4.7.0.72 and opencv-contrib-python 4.10.0.84
OS: Windows 11
Python version: 3.11.3 

### Detailed description

I am detecting the ChArUco boards using the OpenCV. Once I have detected and estimated its pose, I am trying to plot the axis using the drawFrameAxes function; however, I can see different axis plotted just by changing their lengths even and everything remains the same. The included photo has two axis of different length plotted:
![difference](https://github.com/user-attachments/assets/4375a83e-246e-4e6c-8fbd-933eebf56618)


### Steps to reproduce

original image: 
![Image_20240716153945568](https://github.com/user-attachments/assets/6082edb8-ff1d-4664-8ab9-b88d679367b9)

``` Python

import os
import numpy as np
import matplotlib.pyplot as plt
import cv2

# camera params after calibration
mtx = np.array([[3341.0930071 ,    0.        , 2020.04757797],
   [   0.        , 3332.54238818, 1108.10670945],
   [   0.        ,    0.        ,    1.        ]])
   
dist = np.array([-0.10474984,  0.04565679,  0.00948721,  0.        ,  0.        ])

img_rgb = cv2.imread("some img")
img_rgb = cv2.cvtColor(img_rgb, cv2.COLOR_RGB2BGR)
img = cv2.cvtColor(img_rgb, cv2.COLOR_RGB2GRAY)

# board info
dictionary = cv2.aruco.getPredefinedDictionary(cv2.aruco.DICT_4X4_100)
board = cv2.aruco.CharucoBoard((7, 5), 0.055, 0.041, dictionary)

params = cv2.aruco.DetectorParameters()
detector = cv2.aruco.ArucoDetector(dictionary, params)

# detect markers and charuco corners
marker_corners, marker_ids, rejectedCandidates = detector.detectMarkers(img)

ret, charucoCorners, charucoIds = cv2.aruco.interpolateCornersCharuco(marker_corners, marker_ids, img, board)

ret, rvec, tvec = cv2.aruco.estimatePoseCharucoBoard(charucoCorners, charucoIds, board, mtx, dist, None, None)

# start plotting
axis_size = 0.1
result_short = cv2.drawFrameAxes(np.copy(img_rgb), mtx, dist, rvec, tvec, axis_size)

axis_size = 5
result_long = cv2.drawFrameAxes(np.copy(img_rgb), mtx, dist, rvec, tvec, axis_size)

# plot
plt.subplot(1,2,1)
plt.imshow(result_short)
plt.subplot(1,2,2)
plt.imshow(result_long)

plt.show()

result_both = cv2.drawFrameAxes(np.copy(img_rgb), mtx, dist, rvec, tvec, 0.2)
result_both = cv2.drawFrameAxes(result_both, mtx, dist, rvec, tvec, 2)

### Issue submission checklist

- [X] I report the issue, it's not a question
- [X] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [X] I updated to the latest OpenCV version and the issue is still there
- [X] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: angular
Issue: Base64 placeholder stuck on NgOptimizedImage input change
Labels: area: common,state: has PR,common: image directive

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

common

### Is this a regression?

No

### Description

When using `NgOptimizedImage` with base64 image placeholders, if the `ngSrc` and `placeholder` inputs change, for example due to an observable change, the placeholder will remain stuck after the first change and the correct image will never display.

<img width="1305" alt="Screenshot 2024-07-30 at 15 22 49" src="https://github.com/user-attachments/assets/47ddc950-2132-4073-b2d1-2e2f79d61d29">

When I was trying to locally fix the issue by modifying `NgOptimizedImage` directive code, adding the following lines:

```
if (changes["placeholder"] && !changes["placeholder"].isFirstChange()) {
    this.removePlaceholderOnLoad(this.imgElement);
}
```

after this condition:

https://github.com/angular/angular/blob/dd56270bb373078b8ff3f91753c46ac60e1c30c7/packages/common/src/directives/ng_optimized_image/ng_optimized_image.ts#L522-L533

fixed the issue.

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

https://stackblitz.com/edit/stackblitz-starters-czhgq7?file=src%2Fapp.component.html

### Please provide the exception or error you saw

_No response_

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

```true
Angular CLI: 18.1.2
Node: 20.13.1
Package Manager: npm 10.5.2
OS: darwin arm64

Angular: 18.1.2
... animations, cli, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1801.2
@angular-devkit/build-angular   18.1.2
@angular-devkit/core            18.1.2
@angular-devkit/schematics      18.1.2
@schematics/angular             18.1.2
rxjs                            7.8.1
typescript                      5.5.4
zone.js                         0.14.8
```


### Anything else?

_No response_
Repository: PowerToys
Issue: Text Extractor Problems With Addresses
Labels: Issue-Bug,Needs-Triage,Product-Text Extractor

### Microsoft PowerToys version

0.82.1

### Utility with translation issue

TextExtractor

### 🌐 Language affected

English

### ❌ Actual phrase(s)

Phrase contains sensitive personal information. Can I email it you?

### ✔️ Expected phrase(s)

Phrase contains sensitive personal information. Can I email it you?

### ℹ Why is the current translation wrong

The translation did not correctly translate my last name, and missed the first part of my postal code entirely. Additionally, I found the TextExtractor has problems differentiating a K and 1<
Repository: pytorch
Issue: Expand Examples for torch.autograd.functional.jacobian
Labels: module: docs,module: autograd,triaged,actionable

### 📚 The doc issue

The torch.autograd.functional.jacobian function documentation on the PyTorch website provides a brief overview and some basic examples. However, additional documentation would provide some clarity when working with more complex use cases, like calculating Jacobians for batched inputs or optimizing performance for larger matrices.

### Suggest a potential alternative/fix

The documentation for torch.autograd.functional.jacobian could be improved by adding explanations for complex use cases. This includes examples for higher-dimensional inputs and outputs, batched inputs, and the vectorize=True option. 

cc @svekars @brycebortree @ezyang @albanD @gqchen @pearu @nikitaved @soulitzer @Varal7
Repository: rust
Issue: Obtuse diagnostic: overflow evaluating the requirement `&_ well-formed`
Labels: A-diagnostics,T-compiler

### Code

```Rust
fn main() {
    let v = vec![];
    loop {
        if todo!() {
            let x = v.last().unwrap();
            v.push(x); // NOTE: should be v.push(*x);
        } else {
            v.push(0);
        }
    }
}
```


### Current output

```Shell
error[E0275]: overflow evaluating the requirement `&_ well-formed`
 --> src/main.rs:5:21
  |
5 |             let x = v.last().unwrap();
  |                     ^^^^^^^^
```


### Desired output

```Shell
error[E0308]: mismatched types
    --> src/lib.rs:6:20
     |
6    |             v.push(x); // NOTE: should be v.push(*x);
     |               ---- ^ expected `{?T}`, found `&{?T}`
     |               |
     |               arguments to this method are incorrect
     |
note: method defined here
    --> /playground/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/vec/mod.rs:1994:12
     |
1994 |     pub fn push(&mut self, value: T) {
     |            ^^^^
help: consider dereferencing the borrow
     |
6    |             v.push(*x); // NOTE: should be v.push(*x);
     |                    +
```


### Rationale and extra context

The current error message uses jargon that is probably only understandable by compiler developers, type theory enthusiasts, and possibly some genders of Haskell junkies – in an area of the language very easily encountered by newcomers.

### Other cases

Swapping the order of the branches yields very good output:

```Rust
error[E0308]: mismatched types
    --> src/lib.rs:8:20
     |
5    |             v.push(0);
     |             -      - this argument has type `{integer}`...
     |             |
     |             ... which causes `v` to have type `Vec<{integer}>`
...
8    |             v.push(x);
     |               ---- ^ expected integer, found `&{integer}`
     |               |
     |               arguments to this method are incorrect
     |
note: method defined here
    --> /playground/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/vec/mod.rs:1994:12
     |
1994 |     pub fn push(&mut self, value: T) {
     |            ^^^^
```


### Rust Version

```Shell
rustc 1.82.0-nightly (92c6c0380 2024-07-21)
binary: rustc
commit-hash: 92c6c03805408a1a261b98013304e9bbf59ee428
commit-date: 2024-07-21
host: x86_64-unknown-linux-gnu
release: 1.82.0-nightly
LLVM version: 18.1.7
```


### Anything else?

_No response_