sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: kubernetes
Issue: API streaming feature tracking
Labels: sig/api-machinery,triage/accepted

This is a tracking issue for the work that needs to be cleaned-up after API streaming is implemented ([KEP]: https://github.com/kubernetes/enhancements/issues/3157)

TODO: 

- [ ] apiserver: once the `WatchList` feature gate is always on register `SetListOptionsDefaults` function in the scheme ([xref](https://github.com/kubernetes/kubernetes/pull/115402#discussion_r1092190472))
- [ ]  apiserver: when `SetListOptionsDefaults` is registered in the scheme remove all callers of this method.
- [ ] reflector/watchlist: retry with an increased timeout
- [ ] reflector/watchlist: unify error handling
- [ ] reflector: add e2e/integration-tests for the new feature
- [ ] cacher: more efficient removal of closed watchers when `lastProcessedResourceVersion==0` ([xref](https://github.com/kubernetes/kubernetes/pull/117014))
- [ ] In order to graduate the WatchList feature to beta, the etcd3 implementation must/should also support it. ([xref](https://github.com/kubernetes/kubernetes/pull/117862)) (fixed in https://github.com/kubernetes/kubernetes/pull/119557)
- [ ] refactor the `verifyStore` method with e2e/apimachinery/watchlist (xref: https://github.com/kubernetes/kubernetes/pull/120971)
- [ ] Consider making `reflector.UseWatchList` a private field. Since we implemented "api streaming" on the etcd storage layer it should work. (https://github.com/kubernetes/kubernetes/blob/4b3915017950a114124a88c5d308bd8bfb9ec48e/staging/src/k8s.io/client-go/tools/cache/reflector.go#L110)
- [ ] cleanup `kubernetes-e2e-gce-cos-alpha-features` job, remove `WatchList` from https://github.com/kubernetes/test-infra/pull/29271/files
- [ ] consider validating request parameters (i.e sendInitialEvents) for rest.WatchList method ([xref](https://github.com/kubernetes/kubernetes/pull/122657))
- [ ] move `NoopTicker` to `k8s.io/utils` https://github.com/kubernetes/kubernetes/pull/124614#pullrequestreview-2047469125
Repository: flutter
Issue: [pigeon] Investigate driving test plugins with repo tooling
Labels: team,package,team-ecosystem,p: pigeon,P3,triaged-ecosystem

Currently Pigeon has a lot of custom tooling for driving tests, which has a fair amount of overlap with the repo tooling. It also has some gaps relative to repo tooling (like the inability to use FTL for Android tests as discussed in https://github.com/flutter/flutter/issues/111505).

Ideally we would remove most of the custom test logic, and drive the `test_plugin` and `alternate_language_test_plugin` via the repo tooling. Some things we would need to do to make that work:
- Deal with the generated code. Either:
  - Eliminate the need for CI generation in those plugin (which https://github.com/flutter/flutter/issues/115168 would likely accomplish now that core_tests is checked in for ease of reviews, but we would need https://github.com/flutter/flutter/issues/119835 to ensure we were testing the correct thing), or
  - Add a "pre-test" hook, where the tooling would run a script at a known location, if present, before running tests
- Find a way to include the plugins in the tests, since they currently won't be discovered due to being inside another package. Possibilities:
  - Special case Pigeon in the tooling (not ideal)
  - Add a way for packages to opt in specific subpackages to package enumeration (e.g., a Yaml file at a specific location in a package).
- Potentially opt those packages out of some tests. Not all tests make sense, but maybe making them unpublished would handle enough of those things for it to work?

Then the logic of the test script would be significantly reduced. We could keep the existing affordance to easily run all tests by replacing the current implementation logic in Pigeon's test scripts with calls to the relevant repo tooling command.
Repository: next.js
Issue: Android Chrome version 69 not working - no input event trigger
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

Go to https://beta.nextjs.org/docs with an android less version api 28 with a google chrome in less 69.

### Which area(s) of Next.js are affected? (leave empty if unsure)

_No response_

### Link to the code that reproduces this issue

Default code of beta.nextjs.org

### To Reproduce


Android Chrome v103 (left) --- Android Chrome v69 (right)

https://user-images.githubusercontent.com/117950047/216393302-4b902b37-d759-42bd-b8ee-519406dc9002.mov



### Describe the Bug

No trigger event like onChange is trigger.

### Expected Behavior

Should trigger all input event in android chrome 69.

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: go
Issue: crypto/x509: support SCT/OCSP passthrough when using platform verifiers
Labels: Proposal,Proposal-Accepted,Proposal-Crypto

During TLS handshakes, in particular, additional inputs to verification can be sent alongside the certificate chain, typically a set of SCTs and/or a stapled OCSP response, that can be used to resolve additional trust constraints on the chain. The native Go verifier currently has no support for these additional inputs, but when platform verifiers are used (on Windows and macOS) these inputs could be utilized.

#51991 is an example of when ignoring these additional inputs (in particular SCTs) causes verification failures when using a platform verifier, because the platform applies additional restrictions on verification which require the inputs to resolve.

I propose that we add fields to `x509.VerifyOptions` that allow passing through these inputs to `Certificate.Verify`. These will be explicitly documented to only be considered when using platform verifiers, but at some point in the future we may want to add additional functionality to the native verifier to consider them (in particular OCSP responses). Once these fields are added the TLS implementation can be configured to pass through any additional inputs passed during the handshake.

```
type VerifyOptions struct {
	...

	// SignedCertificateTimestamps is a list of DER encoded SCTs for the
	// certificate to be verified. These SCTs are only considered if a platform
	// verifier is being used for verification. When using the native Go
	// verifier, SCTList is curently ignored.
	SignedCertificateTimestamps [][]byte

	// OCSPResponse is a DER encoded OCSPResponse, containing an OCSP response
	// for the certiifcate to be verified. The response is only considered if a
	// platform verifier is being used for verification. When using the native
	// Go verifier, OCSPResponse is currently ignored.
	OCSPResponse []byte
}
```

cc @FiloSottile
Repository: pytorch
Issue: [RFC] Support Huge Model Init Without mallocs for Compile/Distributed Use Cases
Labels: oncall: distributed,triaged

### 🚀 The feature, motivation and pitch

<todo -- lets gather existing thoughts here and develop the RFC>

### Alternatives

_No response_

### Additional context

_No response_

cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @H-Huang @kwen2501 @awgu
Repository: godot
Issue: ViewportTexture doesn't update (either pink or unresponsive to changes in it's material)
Labels: bug,topic:core,topic:rendering

### Godot version
4 beta 17

### System information
Windows 10, GTX 970

### Issue description
When rendering a instanced 2D scene as a child of a SubViewport, there are conditions when either the SubViewport-texture stays pink (in my case: on a MeshInstance3D/PlaneMesh/LocalMaterial/Albedo), or won't update changes in the "LocalMaterial"s material (like metallic or roughness). 

![grafik](https://user-images.githubusercontent.com/52791267/216401727-b1ee6b04-3729-4d3e-a1ae-17a782221052.png)

Trees:
![grafik](https://user-images.githubusercontent.com/52791267/216401056-0ca999a3-014d-4dbd-b377-3db136e39d20.png)
![grafik](https://user-images.githubusercontent.com/52791267/216401111-a6005ab1-9c45-4672-8323-5450c837b4ff.png)

Some bugs seem to be related to the "Viewport Texture must be set to use it."- error- but not always in consistent ways.
![grafik](https://user-images.githubusercontent.com/52791267/216398403-5cc743ca-a1cf-466c-9580-7f7109e00040.png)

The bugs are occuring on the "Mobile" renderer, independently of the SubViewports "Clear Mode" and "Update Mode".

### Steps to reproduce
1. Create scene 2D
2. add label-control to it
3. (optional: -> add naive @tool-script, which live-updates a rendered string on the label. The one in the example project is naively written, but the editor should handle it nevertheless.)

`@tool
extends Control

@export var thing_to_write : String = "Test" : set = set_thing_to_write
func set_thing_to_write(str : String) -> void:
	thing_to_write = str
	$Panel/Label.text = thing_to_write
`

4. Create scene 3D
5. add SubViewport
6. add 2d scene as instance (child of SubViewport)
7. add MeshInstance3D
8. new PlaneMesh

9. new Material
10. make Material local to scene
11. set Albedo to "NewViewportTexture"
12. set Viewport Path to "SubViewport" 

### Minimal reproduction project
[RenderingportBug.zip](https://github.com/godotengine/godot/files/10571645/RenderingportBug.zip)
Repository: vscode
Issue: [Feature Request] Mouse Gestures Support
Labels: feature-request,keybindings

I open this feature request in favor of this one https://github.com/microsoft/vscode/issues/49823 which was closed for duplicate of https://github.com/microsoft/vscode/issues/3130 
But both issues are different, one is *mouse gestures* and the other is *mouse modifiers in shortcuts*

Mouse gestures is the ability to trigger a shortcut drawing a pattern over the screen.  
Here I've made this conceptual video to show you an example:



https://user-images.githubusercontent.com/2827383/216445483-a85f779d-a64b-4358-892c-0e501806c975.mp4



I discovered mouse gestures in Whale Browser, and since I've installed plugins in Chrome. It's simply impossible for me to use a browser without mouse gestures anymore, since it did increase my productivity like 5 times.

Mouse gestures helps in this regard :
- When already having too much shortcuts assigned on the keyboard,
- When I will use the mouse anyway (so I don't have to mouse-keyboard-mouse move my hand just to trigger a shortcut)
- When a mouse pattern is easier to remember

I'm really looking up for this
Repository: PowerToys
Issue: FancyZones improperly sizes some windows when shift-dragging
Labels: Issue-Bug,Product-FancyZones,Needs-Triage,Needs-Team-Response

### Microsoft PowerToys version

0.67.0

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

FancyZones

### Steps to reproduce

Shift-drag an app window (demoed below with GIMP and Audacity) into a FancyZones zone.

### ✔️ Expected Behavior

Any window correctly fills the zone it's dragged into.

### ❌ Actual Behavior

Some windows don't correctly fill the zone they're dragged into. Windows can become too small, too large, and/or in the wrong position.

<img width="2360" alt="fancyzones-bug" src="https://user-images.githubusercontent.com/10392584/216417813-8ef4166e-ab90-461b-85e4-951860fe1e2e.png">
In the screenshot above, I've outlined my screens and zones. GIMP is improperly sized in (1,1), Calculator is correctly sized in (1,2), and Audacity is improperly sized in (2,1).

This is just a hunch, but it may have to do with Win32 apps. I didn't have this problem with version 0.66.
[PowerToysReport_2023-02-02-10-35-48.zip](https://github.com/microsoft/PowerToys/files/10572281/PowerToysReport_2023-02-02-10-35-48.zip)

### Other Software

- GIMP 2.10.32
- Calculator 11.2210.0.0
- Audacity 3.1.3
Repository: flutter
Issue: Link widget should have link semantics
Labels: a: accessibility,p: url_launcher,package,c: proposal,team-ecosystem,P3,triaged-ecosystem

The link widget doesn't have correct semantics https://pub.dev/documentation/url_launcher/latest/link/Link-class.html
We should make sure it put `link: true` in semantics properties.
Repository: godot
Issue: Selecting objects in 3D editor viewport by clicking on them has a noticeable delay
Labels: enhancement,topic:editor,confirmed,topic:3d,performance

### Godot version

4.0 Beta 17 mono

### System information

Windows 10, Nvidia GTX 1660Ti, Vulkan

### Issue description

Check the video here: https://youtu.be/6xk_54SK0PU I tried to add mouse sounds too but my mic didn't pick them up for some reason.

You can see that picking objects has quite a delay in 3D, this is particularly highlighted when you pick objects in the node tree which is instantaneous (I udnerstand picking in 3D takes a bit more than processing the node tree, I'm just trying it to show somethign to contrast the delay with).

### Steps to reproduce

Open a 3d scene add some a MeshInstance (assign it a shape, for example sphere or a box), click on it, observe a delay before the gizmo appears after you click.

### Minimal reproduction project

-
Repository: pytorch
Issue: `linalg.lstsq` fails the gradient computation in forward mode
Labels: triaged,module: forward ad

### 🐛 Describe the bug

`linalg.lstsq` fails the gradient computation in forward mode but succeed in the reverse mode

```py
import torch
from torch.autograd.functional import jacobian

A = torch.randn(2, 3, 3)
b = torch.randn(2, 3)

def func(A, b):
    x = torch.linalg.lstsq(A, b, )
    return x

print(jacobian(func, (A, b), vectorize=True, strategy="reverse-mode"))
# succeed
print(jacobian(func, (A, b), vectorize=True, strategy="forward-mode"))
# fail
# RuntimeError: mat1 and mat2 shapes cannot be multiplied (6x3 and 2x3)
```

### Versions

```
PyTorch version: 2.0.0.dev20230105
Is debug build: False
CUDA used to build PyTorch: 11.7
ROCM used to build PyTorch: N/A

OS: Ubuntu 22.04.1 LTS (x86_64)
GCC version: (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
Clang version: Could not collect
CMake version: version 3.22.1
Libc version: glibc-2.35

Python version: 3.9.15 (main, Nov 24 2022, 14:31:59)  [GCC 11.2.0] (64-bit runtime)
Python platform: Linux-5.15.0-56-generic-x86_64-with-glibc2.35
Is CUDA available: True
CUDA runtime version: 11.7.99
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration:
GPU 0: NVIDIA GeForce RTX 3090
GPU 1: NVIDIA GeForce RTX 3090
GPU 2: NVIDIA GeForce RTX 3090

Nvidia driver version: 515.86.01
cuDNN version: Probably one of the following:
/usr/lib/x86_64-linux-gnu/libcudnn.so.8.4.1
/usr/lib/x86_64-linux-gnu/libcudnn_adv_infer.so.8.4.1
/usr/lib/x86_64-linux-gnu/libcudnn_adv_train.so.8.4.1
/usr/lib/x86_64-linux-gnu/libcudnn_cnn_infer.so.8.4.1
/usr/lib/x86_64-linux-gnu/libcudnn_cnn_train.so.8.4.1
/usr/lib/x86_64-linux-gnu/libcudnn_ops_infer.so.8.4.1
/usr/lib/x86_64-linux-gnu/libcudnn_ops_train.so.8.4.1
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

Versions of relevant libraries:
[pip3] numpy==1.23.5
[pip3] torch==2.0.0.dev20230105
[pip3] torchaudio==2.0.0.dev20230105
[pip3] torchvision==0.15.0.dev20230105
[conda] blas                      1.0                         mkl
[conda] mkl                       2021.4.0           h06a4308_640
[conda] mkl-service               2.4.0            py39h7f8727e_0
[conda] mkl_fft                   1.3.1            py39hd3c417c_0
[conda] mkl_random                1.2.2            py39h51133e4_0
[conda] numpy                     1.23.5           py39h14f4228_0
[conda] numpy-base                1.23.5           py39h31eccc5_0
[conda] pytorch                   2.0.0.dev20230105 py3.9_cuda11.7_cudnn8.5.0_0    pytorch-nightly
[conda] pytorch-cuda              11.7                 h67b0de4_2    pytorch-nightly
[conda] pytorch-mutex             1.0                        cuda    pytorch-nightly
[conda] torchaudio                2.0.0.dev20230105      py39_cu117    pytorch-nightly
[conda] torchtriton               2.0.0+0d7e753227            py39    pytorch-nightly
[conda] torchvision               0.15.0.dev20230105      py39_cu117    pytorch-nightly
```
Repository: go
Issue: net/http: TestTransportConnectionCloseOnResponse/h2 failures with `unexpected bodiesDiffer=false`
Labels: NeedsInvestigation

```
#!watchflakes
post <- pkg == "net/http" && test == "TestTransportConnectionCloseOnResponse" && `unexpected bodiesDiffer=false`
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/2330dc8ea9a2f72e4e33eac6b0f07bdb7b92fb57)):

    --- FAIL: TestTransportConnectionCloseOnResponse (0.00s)
        --- FAIL: TestTransportConnectionCloseOnResponse/h2 (0.82s)
            transport_test.go:238: error in connectionClose=true. unexpected bodiesDiffer=false; body1="127.0.0.1:13438"; body2="127.0.0.1:13438"


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: x/build: OOM on linux-ppc64le-power10osu builder
Labels: Builders,NeedsInvestigation

```
#!watchflakes
post <- builder == "linux-ppc64le-power10osu" && log ~ `signal: killed`
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/02810fb86b3b1176210cf1b1a93e33fab298f670)):

    # go run run.go -- rotate1.go
    exit status 1
    command-line-arguments: /workdir/go/pkg/tool/linux_ppc64le/compile: signal: killed


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: PowerToys
Issue: Taskbar manager to setup taskbar settings for opacity/visibility
Labels: Needs-Triage

### Description of the new feature / enhancement

I've used several taskbar managers to make my screen look better but they all break whenever there is a new version of Windows 11 published. The two that I've used successfully in the past (that are now broken by 22H2), are TranslucentTB and TaskbarX which are both available on the Microsoft Store app.

It would be nice if this capability was included in PowerToys so that it will continue to work across Win11 version updates. 

### Scenario when this would be used?

Every day. I would use it to make my taskbar invisible so that I can see the entire desktop wallpaper without having a dark section across the screen that is the taskbar. 

### Supporting information

_No response_
Repository: rust
Issue: Consider simulation testing for math on 16-bit targets
Labels: A-testsuite,O-AVR,C-discussion,O-msp430,E-needs-design

We have a few tier 3 targets that are 16-bit, AVR and MSP430. These have numerous issues but a number of them have been resolved recently. It's almost like you can really compile for them! Unfortunately these targets have almost no regression testing, as they are bare-metal, cross-compile-only targets. If we are serious about supporting them, it would be prudent to run tests. Fortunately, AVR has a sophisticated simulation testing ecosystem which several users report as reliable-enough for "the program builds and functions, and maybe even as-intended". However, as these are tier 3 targets, it would be somewhat of a policy change to add testing for much more than "you can technically build code for them ever".

_On the other hand_, the simulation testing in this case would probably be for bare minimums like "arithmetic and bitwise operators work". Embedded users are often willing to work around the inadequacy of `std` and the language, but it's hard to expect them to build around us if they don't have access to even basic computation primitives.

It may be surprising these targets need regression testing for such minimums, but nonetheless it's hard to expect them to be elevated past even tier 3 if we don't allow regression testing for those basics. On the other hand, if they break, _very few_ compiler programmers will know how to fix them, and the policy of not running testing for tier 3 targets is there for a reason. So, this may need an MCP or something like that? I don't know. I'm just raising it as an issue here to, for now, track issues that either currently or would enjoy this. Or maybe this will just wait until we elevate support for these targets past tier 3.

- https://github.com/rust-lang/rust/issues/77131
- https://github.com/rust-lang/rust/issues/82242
- https://github.com/rust-lang/rust/issues/82380
- An apparent regression introduced by virtually no regression testing for AVR:
  - https://github.com/rust-lang/rust/issues/102278
  - https://github.com/rust-lang/rust/issues/76930
Repository: go
Issue: net: dialing a loopback address sometimes fails with `ECONNRESET` on NetBSD
Labels: OS-NetBSD,NeedsInvestigation

```
#!watchflakes
post <- goos == "netbsd" && `connect: connection reset by peer`
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/3c092b52b858bcb1b3ba3174cf331af51106b519)):

    --- FAIL: TestFileCloseRace (0.00s)
        file_test.go:321: dial tcp 127.0.0.1:65102: connect: connection reset by peer


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: deno
Issue: fetch across multiple apps on same domain
Labels: needs investigation

I'm attempting to `fetch` various resources on the same domain.  The resources are provided by different applications using different context roots (`app-A` and `app-B` in my examples below).  Each application requires its own authentication.  I'm experiencing an error which feels like a bug in Deno.  Am I doing something wrong?

# Notes

- I don't know how to reproduce outside of my corporate environment
- Executing the exact same code in Firefox or Chrome works

# Error Message

```
error: Uncaught (in promise) TypeError: error sending request for url (https://my-domain/app-B/bar.json): connection error: An existing connection was 
forcibly closed by the remote host. (os error 10054)
const responseAppB = await fetch(`https://my-domain/app-B/bar.json`, {
                     ^
    at async mainFetch (deno:ext/fetch/26_fetch.js:267:14)
    at async fetch (deno:ext/fetch/26_fetch.js:491:9)
    at async file:///C:/.../deno-api-scripting/test.ts:10:22
```

# Deno Version Info

```shell
$ deno --version
deno 1.30.1 (release, x86_64-pc-windows-msvc)
v8 10.9.194.5
typescript 4.9.4
```

# Script That Errors

```typescript
const responseAppA = await fetch(`https://my-domain/app-A/foo.json`, {
    headers: {
        'Authorization': 'Bearer app-a-token',
        'Content-Type': 'application/json',
    }
})

const responseDataAppA = await responseAppA.json()  // 🔴 The next fetch will error if this .json() is executed.

const responseAppB = await fetch(`https://my-domain/app-B/bar.json`, {
    headers: {
        'Authorization': 'Bearer app-b-token',
    }
})

const responseDataAppB = await responseAppB.json()
```

# Script Does Not Error

```typescript
const responseAppA = await fetch(`https://my-domain/app-A/foo.json`, {
    headers: {
        'Authorization': 'Bearer app-a-token',
        'Content-Type': 'application/json',
    }
})

const responseAppB = await fetch(`https://my-domain/app-B/bar.json`, {
    headers: {
        'Authorization': 'Bearer app-b-token',
    }
})

const responseDataAppA = await responseAppA.json()  // 🟢 Everything works when .json() executes after the second fetch.
const responseDataAppB = await responseAppB.json()
```
Repository: go
Issue: runtime: lock ordering problems
Labels: NeedsInvestigation,compiler/runtime

```
#!watchflakes
post <- builder ~ `.*-staticlockranking` && log ~ `lock ordering problem`
```

(Pulled out from #55167, because these issues tend to be easier to diagnose; CC @golang/runtime)