sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: kubernetes
Issue: fix test for filesystem size when restoring snapshot to larger size pvc on Windows
Labels: sig/storage,help wanted,kind/failing-test,needs-triage

### Which jobs are failing?

ci-windows-2019-provider-gcp-compute-persistent-disk-csi-driver

### Which tests are failing?

"should provision correct filesystem size when restoring snapshot to larger size pvc [Feature:VolumeSnapshotDataSource]"

### Since when has it been failing?

Never - test is skipped on Windows since it's been added.

### Testgrid link

N/A

### Reason for failure (if possible)

Test is currently using `stat` Linux command which won't work on Windows.

### Anything else we need to know?

Issue originated here: https://github.com/kubernetes/kubernetes/pull/110304#discussion_r1003427897

### Relevant SIG(s)

/sig storage
Repository: pytorch
Issue: `torchtyping` annotations make saving to Torchscript fail
Labels: oncall: jit

### 🐛 Describe the bug

It seems that there is already some interest in offering a type-annotation system for PyTorch.
[This issue](https://github.com/pytorch/pytorch/issues/73359) mentions [torchtyping](https://github.com/patrick-kidger/torchtyping). However, on trying to save a `nn.Module` that includes such annotations, to TorchScript, I get an issue that looks like this:
```
RuntimeError:
       Unknown type constructor TensorType:
         File "my/code/vae.py", line 34
           def forward(
               self, x: TensorType["batch_size", "input_dim"]
                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ <--- HERE
           ) -> TensorType["batch_size", "input_dim"]:
```
It's very unclear to me why a type annotation would impact the TorchScript saving process, but I don't know anything about TorchScript.

However, the `torchtyping` maintainer seems to have looked into it and they mentioned a year ago that the issue lies with the TorchScript implementation. See the full discussion here: <https://github.com/patrick-kidger/torchtyping/issues/13>. Since they recommended contacting the TorchScript maintainers, and I could not find an issue about it in this project, I'd like to bring this to the attention to whom it may concern, if they're not already aware of this.

Some kind people have shared [workarounds](https://github.com/patrick-kidger/torchtyping/issues/13#issuecomment-1243725436) in the comments of this issue, and they seem to work.

Thanks for your attention!

### Versions

PyTorch version: 1.12.1
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: macOS 12.5.1 (x86_64)
GCC version: Could not collect
Clang version: 14.0.0 (clang-1400.0.29.102)
CMake version: version 3.24.2
Libc version: N/A

Python version: 3.10.7 (main, Sep 15 2022, 01:51:29) [Clang 14.0.0 (clang-1400.0.29.102)] (64-bit runtime)
Python platform: macOS-12.5.1-x86_64-i386-64bit
Is CUDA available: False
CUDA runtime version: No CUDA
CUDA_MODULE_LOADING set to: N/A
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

Versions of relevant libraries:
[pip3] numpy==1.23.3
[pip3] pytorch-lightning==1.7.7
[pip3] torch==1.12.1
[pip3] torchmetrics==0.10.0
[pip3] torchtyping==0.1.4
[conda] Could not collect

cc @EikanWang @jgong5 @wenzhe-nrv @sanchitintel
Repository: pytorch
Issue: Libtorch windows binaries publishing
Labels: module: ci,triaged,topic: binaries

### 🐛 Describe the bug

Looks like following libtorch configuations are missing from windows while present in linux.
Research if they are required. And if they are add make sure we build them:

Windows Libtorch missing:
```
libtorch_variants = [
            "shared-without-deps",
            "static-with-deps",
            "static-without-deps",
        ]
```

### Versions

1.14

cc @seemethere @malfet @pytorch/pytorch-dev-infra
Repository: go
Issue: proposal: x/exp/jsonrpc2: add LocalAddr & RemoteAddr methods to *jsonrpc2.Connection
Labels: Proposal

With a `*jsonrpc2.Connection` instance, it is not possible to know at least the remote network address.

The proposal here, is to add:
```go
LocalAddr() net.Addr
RemoteAddr() net.Addr
```
methods to `*jsonrpc2.Connection` type.

Without breaking the compatibility they can easily be implemented as:
```go
func (c *Connection) LocalAddr() net.Addr {
	if conn, ok := c.closer.(interface{ LocalAddr() net.Addr }); ok {
		return conn.LocalAddr()
	}
	return nil
}

func (c *Connection) RemoteAddr() net.Addr {
	if conn, ok := c.closer.(interface{ RemoteAddr() net.Addr }); ok {
		return conn.RemoteAddr()
	}
	return nil
}
```
Repository: rust
Issue: No rust-std support for s390x-unknown-linux-musl
Labels: O-musl,O-SystemZ

My understanding is that the rust compiler and library sources should now contain everything needed to support Rust on the `s390x-unknown-linux-musl` target.  In fact, the s390x Alpine distro now comes with a Rust package.

However, I still get:
```
$ rustup target add s390x-unknown-linux-musl
error: toolchain 'stable-x86_64-unknown-linux-gnu' does not contain component 'rust-std' for target 's390x-unknown-linux-musl'
note: not all platforms have the standard library pre-compiled: https://doc.rust-lang.org/nightly/rustc/platform-support.html
```

What would need to be done to enable this target?
Repository: opencv
Issue: CAP_PROP_CONVERT_RGB is not properly explained in document
Labels: category: documentation

### System Information

- OpenCV version: 4.6.0
- Operating System / Platform: Ubuntu 22.04
- Compiler & compiler version: GCC 11.2.0

### Detailed description

In OpenCV document, `CAP_PROP_CONVERT_RGB` is explained as follows

> Boolean flags indicating whether images should be converted to RGB.

https://docs.opencv.org/4.6.0/d4/d15/group__videoio__flags__base.html#ggaeb8dd9c89c10a5c63c139bf7c4f5704dad0bb457c76e2b01024ecb3a85e75af29

However, it is actually converted to BGR.  
https://github.com/opencv/opencv/blob/4.6.0/modules/videoio/src/cap_v4l.cpp#L1535-L1639

I think that it is a typo in the document.

### Steps to reproduce

This report is about document of OpenCV.
So, there is no code to reproduce.

### 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: rust
Issue: Hint for missing lifetime bound on trait object is missing if type alias is used
Labels: A-diagnostics,A-lifetimes,T-compiler,D-terse,A-trait-objects

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.

If you cannot produce a minimal reproduction case (something that would work in
isolation), please provide the steps or even link to a repository that causes
the problematic output to occur.
-->

Given the following code: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=a0979812dc1acbc732481dd2d3185637

```rust
trait Greeter {
    fn greet(&self);
}

type BoxedGreeter = Box<dyn Greeter>;

struct FixedGreeter<'a>(pub &'a str);

impl Greeter for FixedGreeter<'_> {
    fn greet(&self) {
        println!("{}", self.0)
    }
}

struct Greetings(pub Vec<String>);

impl Greetings {
    pub fn get(&self, i: usize) -> BoxedGreeter {
        Box::new(FixedGreeter(&self.0[i]))
    }
}
```

The current output is:

```
error: lifetime may not live long enough
  --> src/lib.rs:19:9
   |
18 |     pub fn get(&self, i: usize) -> BoxedGreeter {
   |                - let's call the lifetime of this reference `'1`
19 |         Box::new(FixedGreeter(&self.0[i]))
   |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ returning this value requires that `'1` must outlive `'static`
```

However, by removing the type alias: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=bfde1cf5c8a72349b117aa21bbd61c3d

```rust
trait Greeter {
    fn greet(&self);
}

struct FixedGreeter<'a>(pub &'a str);

impl Greeter for FixedGreeter<'_> {
    fn greet(&self) {
        println!("{}", self.0)
    }
}

struct Greetings(pub Vec<String>);

impl Greetings {
    pub fn get(&self, i: usize) -> Box<dyn Greeter> {
        Box::new(FixedGreeter(&self.0[i]))
    }
}
```

The output looks like this, which is much more helpful:

```
error: lifetime may not live long enough
  --> src/lib.rs:17:9
   |
16 |     pub fn get(&self, i: usize) -> Box<dyn Greeter> {
   |                - let's call the lifetime of this reference `'1`
17 |         Box::new(FixedGreeter(&self.0[i]))
   |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ returning this value requires that `'1` must outlive `'static`
   |
help: to declare that the trait object captures data from argument `self`, you can add an explicit `'_` lifetime bound
   |
16 |     pub fn get(&self, i: usize) -> Box<dyn Greeter + '_> {
   |                                                    ++++
```

Without the hint, this error isn't very helpful for beginners, as it doesn't do anything to explain *why* `'1` must outlive `'static`. It would be helpful if a similar hint could be provided when a type alias is used.

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"yanchen4791"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: next.js
Issue: TypeError: Cannot set property Headers of #<Object> which has only a getter
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: win32
      Arch: x64
      Version: Windows 10 Pro
    Binaries:
      Node: 16.15.0
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 12.3.2-canary.43
      eslint-config-next: 13.0.0
      react: 18.2.0
      react-dom: 18.2.0

### What browser are you using? (if relevant)

Brave 1.45.113

### How are you deploying your application? (if relevant)

_No response_

### Describe the Bug

When upgrading to next.js 12 -> 13 (everything else being equal) I am getting an error that I did not before:

```js
TypeError: Cannot set property Headers of #<Object> which has only a getter
```

I've tracked this to a third-party package, and to a line that modifies the `global` object in a way that does not seem to be permitted: https://github.com/spacebudz/lucid/blob/main/src/core/core.ts#L19

Looking at this, https://nodejs.org/api/globals.html#class-headers, it seems that there is a `Headers` object on the `global` nodejs environment since node.js >= 16.15.0, so the error might be legit, if the `Headers` object is read-only, but if so, why am I only seeing this issue with the latest version of next.js? (again, everything else being equal, also cannot reproduce this in an isolated node.js project with same node version)


### Expected Behavior

For the application to work as with next.js 12

### Link to reproduction

https://github.com/GGAlanSmithee/nextjs-13-cardano-lucid-repro

### To Reproduce

Simply run the app and visit `http://localhost:3000`.

PS. the next.config file was modified to allow for top level awaits, if that affects anything
Repository: tauri
Issue: [bug] App#run_iteration is not working correctly on macOS and seg-faults
Labels: type: bug,platform: macOS,status: backlog

### Describe the bug

A Repo for the Repro: https://github.com/sinistersnare/tauri_bug_repro

Running on macOS 12.6 Monterey on a 2021 MBP w/ M1 Pro CPU.

Unless the window is resized, or some other thing is done to force a window refresh, the page is blank and unloaded.

Running this repro has intermittent success, but just as often behaves in at least one of these ways:

* index.html does not load until the window is resized (or some other events like opening the 'about APP' modal)
* Upon exiting the window, either a ***segmentation fault*** or a bus-error occurs, crashing the app.
* Cmd+W does not seem to work to close the window. Even pressing the close window button in the top-bar does not work.

related to #4299

### Reproduction

1. clone https://github.com/sinistersnare/tauri_bug_repro
2. `cargo run`
3. If everything works, re-run, it should fail more than half the time.


### Expected behavior

`App#run_iteration` as it is described in the docs should function normally (just like `#run` should), and not crash.

### Platform and versions
```
$ cargo tauri info

Environment
  › OS: Mac OS 12.6.0 X64
  › Node.js: 16.14.2
  › npm: 8.5.0
  › pnpm: Not installed!
  › yarn: 1.22.19
  › rustup: 1.25.1
  › rustc: 1.66.0-nightly
  › cargo: 1.66.0-nightly
  › Rust toolchain: nightly-aarch64-apple-darwin 

Packages
WARNING: no lock files found, defaulting to npm
  › @tauri-apps/cli [NPM]: 1.1.1
  › @tauri-apps/api [NPM]: Not installed!
  › tauri [RUST]: 1.1.1,
  › tauri-build [RUST]: 1.1.1,
  › tao [RUST]: 0.14.0,
  › wry [RUST]: 0.21.1,

App
  › build-type: bundle
  › CSP: unset
  › distDir: ./www
  › devPath: ./www
package.json not found
```

### Stack trace

```shell
[1]    43644 bus error  cargo run
```


### Additional context

_No response_
Repository: godot
Issue: Bug: KinematicBody property motion/sync_to_physics works only with one animation track
Labels: topic:physics,needs testing,topic:animation

### Godot version

3.5.1.stable

### System information

Windows 10

### Issue description

I have an elevator (KinematicBody) moving up/down and rotating.

When I switch on `motion/sync_to_physics = true` only one track of my animation is played, here track rotation_degrees, and not track translation.

Is this a bug?

<img width="1290" alt="godot_351_KinematicBody_animation_trouble_when_sync_to_physics_is_on" src="https://user-images.githubusercontent.com/50963378/198096127-64532ea2-627f-429b-9055-9441ad492d8d.png">

### Steps to reproduce

open the project

1. play it
2. change in node Elevator/KinematicBody the property **Sync to Physics** to On.

### Minimal reproduction project

[godot221026_3d_physics_elevator_plus_rotation_test.zip](https://github.com/godotengine/godot/files/9872307/godot221026_3d_physics_elevator_plus_rotation_test.zip)
Repository: stable-diffusion-webui
Issue: [Feature Request]:  overall fixing of some tabs and things
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 like your platform, it is constantly updated and there are many good things in it.
There are also noticeable disadvantages.

inpainting - only one color of the brush, no zoom. It is not possible to cancel everything and return to the original image.
It is not possible to make a match between before and after (possible only with Script)

The option to move the numbers (which are next to the slider) with the mouse wheel simply does not work as it should.

In the category of image to image you can reduce space and move some of the options to the right side instead of only to the left side.

And there are many other things. But step by step. Let's start with the little things.


Thanks to everyone who works on this project. He is amazing and has huge potential.

### Proposed workflow

mention above if you have any questions I can reply with more detailed answers.

### Additional information

_No response_
Repository: flutter
Issue: Support for M3 Docked `DatePicker`
Labels: c: new feature,framework,f: material design,team-design,triaged-design

A follow on to #101481, we need to add support for the new [docked date picker](https://m3.material.io/components/date-pickers/specs#822a6970-db2a-422b-b391-4e9c5641046e) for Material 3: 

<img width="400" alt="Screen Shot 2022-10-26 at 11 28 07 AM" src="https://user-images.githubusercontent.com/19588/198106881-ad2a2a92-a23e-4d6c-9e67-4e3065b29030.png">

We should hopefully be able to use some of same components that the modal date pickers are using, but this has some UI differences.
Repository: flutter
Issue: Modify DisplayList and LayerStateStack naming conventions to match Flutter style guidelines
Labels: engine,c: proposal,P2,team-engine,triaged-engine

As pointed out in https://github.com/flutter/engine/pull/36458, parts of the DL source code have been following a mix of Skia and Flutter style guidelines and as we move more towards hiding or eliminating the Skia APIs behind or in favor of DL APIs, we should be adhering more closely to the Flutter style.

The PR was for the new LayerStateStack mechanism that will be central to our migration to DL APIs throughout the layer code, so both mechanisms should be recast with fresh API names.
Repository: next.js
Issue: Next 13: setting headers in middleware causes full page reload between navigations
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: Mon Aug 22 20:17:10 PDT 2022; root:xnu-8020.140.49~2/RELEASE_X86_64
    Binaries:
      Node: 16.13.1
      npm: 8.19.1
      Yarn: 1.22.17
      pnpm: 7.12.0
    Relevant packages:
      next: 13.0.0
      eslint-config-next: 13.0.0
      react: 18.2.0
      react-dom: 18.2.0
```

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

Chrome

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

Version 105.0.5195.125 (Official Build) (x86_64)

### Describe the Bug

#41380 introduced a way to override headers from middleware.

Using this functionality causes `next/link` to trigger full-page reload between navigations.

This is only an issue for `next dev`.  There is no bug when it's deployed on Vercel.

### Expected Behavior

There should not be a full-page reload when `next/link` is used.

### Link to reproduction

https://github.com/colinclerk/appdir-middleware-bug

### To Reproduce

Clone the repo and start the dev server, then click the links between "Index" and "Page 2" - you should see full-page reloads

If helpful, here's the deployed version that doesn't exhibit the issue: https://appdir-middleware-bug.vercel.app/
Repository: vscode
Issue: [scss] Sass modules intellisense when using @use at-rules.
Labels: feature-request,css-less-scss

<!-- ⚠️⚠️ 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: 1.72.2
- OS Version: MacOS 12.6

Steps to Reproduce:

1. Create an empty folder
2. Run npm init inside
3. Install sass `npm install sass`
4. Create a `main.scss` file
5. Try to use a Sass built-in module like `@use 'sass:math'` 

I get no intelliSense to autocomplete the built-in sass modules when typing  `@use 'sas...'` and i get no intellisense from `math.`

I've tried on a fresh insider build with no extensions and no user settings.

From what i could find, it should be supported currently
- https://github.com/microsoft/vscode-css-languageservice/pull/183
- https://github.com/microsoft/vscode-docs/blob/vnext/release-notes/v1_41.md#sass-module-support
Repository: stable-diffusion-webui
Issue: [Feature Request]: Stacking or mixing variation seeds to refine a result
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 ?

Something I like in InvokeAI is the ability to keep stacking variation seeds upon each other. I’d use this to refine a seed that was working well with ever decreasing variation strengths.

### Proposed workflow

1. Generate an image
2. Enable a variation seed and strength
3. Generate the variant
4. Lock the previous variant seed and strength, then add a new variation seed on top of that, at even lower strength
5. Repeat to refine the image using multiple variations at decreasing strengths.


### Additional information

_No response_
Repository: go
Issue: cmd/compile: optimize append with string concatenation
Labels: Performance,NeedsInvestigation,compiler/runtime

[Consider the following benchmark](https://go.dev/play/p/H51HzN4tsEl):
```go
const prefix = "some sufficiently long prefix "
var something = "something"
const suffix = " some sufficiently long suffix"

var sink []byte

func BenchmarkNaive(b *testing.B) {
	b.ReportAllocs()
	for i := 0; i < b.N; i++ {
		sink = append(sink[:0], prefix+something+suffix...)
	}
}
```
There's a number of string concatenations going on, some from variables and others from constants,
which runs in:
```
BenchmarkNaive-24        	23387558	        45.20 ns/op	      80 B/op	       1 allocs/op
```

However, the benchmark is semantically equivalent to:
```go
func BenchmarkOptimized(b *testing.B) {
	b.ReportAllocs()
	for i := 0; i < b.N; i++ {
		sink = append(append(append(sink[:0], prefix...), something...), suffix...)
	}
}
```
which runs in:
```
BenchmarkOptimized-24    	191343406	         6.218 ns/op	       0 B/op	       0 allocs/op
```

That is a 100% reduction in allocations, and a dramatic speedup.

The compiler should implicitly perform this transformation for me.
Repository: godot
Issue: Xbox One/Series gamepad "View" button is not detected on android 12+
Labels: bug,platform:android,needs testing,topic:input

### Godot version

3.5.1 stable

### System information

Android 12 - Samsung A12

### Issue description

On android 12+, the "view" button doesn't work.

### Steps to reproduce

Create a new Godot Project and assign an action to view button (select-playstation, "-" button on switch). Export and install on android (I tested on Android 12) It's the only button that doesn't work.


### Minimal reproduction project

_No response_
Repository: vscode
Issue: Please document how problem matcher problems are cleared
Labels: feature-request,tasks

<!-- ⚠️⚠️ 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. -->

I have some custom problem matchers for my tasks that create problems fine, but then the problems do not go away when rerunning the task even if they are no longer generated by the build task. I have tried to read the documentation for problem matchers.

I see there are many issues related to clearing problems, but they keep getting closed with a note that it is the plugin or problem matcher's job to make sure issues clear. For example, #129341.

In many cases, there is some oblique reference to "owner" but there is nothing about what the owner field means or how it is used to determine when problems go away.

Perhaps this could be added to the questions here:

https://code.visualstudio.com/docs/editor/tasks

Thank you