sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: material-ui
Issue: Cannot use input as label for TextField in AutoComplete 
Labels: new feature,component: autocomplete

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯

The label for a TextField can be any ReactNode. However if the label is an <input /> and the TextField is used in renderInput for Autocomplete, then the <input /> element cannot be focused. 

![code](https://user-images.githubusercontent.com/25811049/181132119-9cb23020-63a0-4e0e-9634-ab908a76a08f.png)


### Expected behavior 🤔

An input used as a label for a TextField should be focusable, even when used inside of AutoComplete renderInput.

### Steps to reproduce 🕹

Steps:

1. Go to https://stackblitz.com/edit/react-ts-wuuatm?file=App.tsx
2. Click on the label for the top field. Notice the input receives focus
3. Click on the label for the bottom field. Notice the input does not receive focus


### Context 🔦

Working on an Application where the label for fields should be editable by admin users. In my app, when the user clicks an icon, the label should become editable. This is working for all fields except for AutoCompletes, where the label input cannot be focused. 

### Your environment 🌎

StackBlitz https://stackblitz.com/edit/react-ts-wuuatm?file=App.tsx
Repository: pytorch
Issue: `torch.matrix_exp` doesn't handle NaN properly
Labels: module: cuda,triaged,module: NaNs and Infs,module: linear algebra

### 🐛 Describe the bug

When calling `torch.matrix_exp`  on a value containing `nan` values, the result is strange and different on CPU and on CUDA with the same input.

Based on similar discussion in https://github.com/pytorch/pytorch/issues/61251 , I think `torch.matrix_exp` should also check input for `nan`.

```
import torch
torch.random.manual_seed(420)
input = torch.randn(3, 3, dtype=torch.float32)
print("Intermediate: ", torch.log(input * 2 - 1)) # Contains nan
output = torch.matrix_exp(torch.log(input * 2 - 1))
print("cpu output: ", output)
input = input.cuda()
output = torch.matrix_exp(torch.log(input * 2 - 1))
print("gpu output: ", output) 
```

Outputs:
```
Intermediate:  tensor([[    nan, -1.2915,     nan],
        [    nan,  0.7102,     nan],
        [-0.3755,     nan,     nan]])
cpu output:  tensor([[ 7.2619e+11,  0.0000e+00, -8.4379e-01],
        [-1.8280e+00,  2.0343e+00, -9.0547e-01],
        [ 6.8693e-01, -1.4521e+00, -9.3093e-01]])
gpu output:  tensor([[-4.3953,  0.2749, -0.8438],
        [-1.8280,  2.0343, -0.9055],
        [ 0.6869, -1.4521, -0.9309]], device='cuda:0')
```

### Versions

pytorch: 1.12.0

cc @ngimel @jianyuh @nikitaved @pearu @mruberry @walterddr @IvanYashchuk @xwang233 @Lezcano
Repository: godot
Issue: Light2D additive blending mode is broken
Labels: discussion,topic:rendering,confirmed,topic:2d

___

***Bugsquad note:** This issue has been confirmed several times already. No need to confirm it further.*

___

### Godot version

3.4.4.stable

### System information

Win10

### Issue description

![LightVSSprite](https://user-images.githubusercontent.com/2248500/181136302-21bcff2b-05c9-4618-ad6c-3113ef0da75c.png)

Both images are the same texture with the same blending mode "ADD". Left one is Light2D, right one is Sprite2D
It seems like it acts weird and there is some hard cutoff for background lightness:

![image](https://user-images.githubusercontent.com/2248500/181136621-d4359446-0395-4aad-82b0-d22a9156dc95.png)

This is a light with maximum energy - 16. I expect to see white circle. 

### Steps to reproduce

Add Light2D over black background. 
Use Add / Mix mode
Light is completely invisible

### Minimal reproduction project

_No response_
Repository: go
Issue: compress: add AppendCompress and AppendDecompress
Labels: Performance,Proposal,Proposal-Accepted

There are situations where we have the entire input on hand and want to compress/decompress it into a buffer we already have on hand. I propose the addition of the following functions to `gzip`, `flate`, `zlib`:
```go
// AppendEncoded appends the compressed form of src to the end of dst
// using the specified compression level.
// It returns an error only if the specified level is invalid.
func AppendEncoded(dst, src []byte, level int) ([]byte, error)

// AppendDecoded appends the decompressed form of src to the end of dst.
// If the decompressed output exceeds maxSize, it returns an error.
// If maxSize is negative, then there is no limit on the output size.
func AppendDecoded(dst, src []byte, maxSize int) ([]byte, error)
```

At face value, this appears to be yet another proposal for convenience functions (which has been proposed and rejected before: #16504). However, there are CPU and memory performance benefits to this API that is impossible to achieve otherwise.

Compression is the combination of LZ77 and Huffman encoding. The memory used by LZ77 is essentially the last 32KiB of uncompressed data. When operating with an `io.Reader` or `io.Writer`, the compressor/decompressor is responsible for maintaining a copy of the LZ77 window. This is quite a bit of copying and extra memory usage. The advantage of the APIs above is that there is zero work that needs to be done to maintain the LZ77 window separately since the `AppendEncoded.src` and `AppendDecoded.dst` are the LZ77 windows. When decompressing, the only memory required is the memory for the Huffman decoder, which is relatively small. When compressing, the only memory required is the memory for the LZ77 search structure and Huffman encoder, which is still sizeable, but still smaller than the entire LZ77 window.

Other considerations: The `flate` and `zlib` APIs provide the ability to specify a dictionary and the proposed APIs have no means of specifying such a feature. It appears that dictionaries are rarely used such that adding it as part of the API is probably not worth it. Usage of dictionaries can still use the `io.Reader` and `io.Writer` based APIs.
Repository: flutter
Issue: [camera_windows] Windows camera does not handle duplicate calls to `StartPreview` properly 
Labels: platform-windows,p: camera,a: desktop,P3,team-windows,triaged-windows

Duplicate calls to `CaptureControllerImpl::StartPreview` on the same camera cause unexpected results. This scenario is only possible if using the C++ APIs directly. This issue does not impact any real customer scenarios.

1. If the first preview has already started, the second `StartPreview` will [fail an assertion](https://github.com/flutter/plugins/blob/278bc6668567adb5c20dc17a71f03ef404b0d8c8/packages/camera/camera_windows/windows/preview_handler.cpp#L158).
2. If the first preview has completed its initialization, the second `StartPreview` [sends an error](https://github.com/flutter/plugins/blob/278bc6668567adb5c20dc17a71f03ef404b0d8c8/packages/camera/camera_windows/windows/capture_controller.cpp#L586) which stops the preview as it [destroys the preview handler](https://github.com/flutter/plugins/blob/278bc6668567adb5c20dc17a71f03ef404b0d8c8/packages/camera/camera_windows/windows/capture_controller.cpp#L759-L762).

Ideally the first `StartPreview` should work as expected while the second `StartPreview` should result in an error.
Repository: go
Issue: x/pkgsite: golang.org redirects /pkg/foo/ to another redirect
Labels: pkgsite

The golang.org /pkg/ redirect pages redirect to another redirect:

```
bradfitz@book1pro ~ % curl -I https://golang.org/pkg/crypto/tls/
HTTP/2 301 
content-type: text/html; charset=utf-8
location: https://go.dev/pkg/crypto/tls/
date: Wed, 27 Jul 2022 02:23:28 GMT
server: Google Frontend
```

But that location (`https://go.dev/pkg/crypto/tls/`) serves another redirect:

```
bradfitz@book1pro ~ % curl -I https://go.dev/pkg/crypto/tls/
HTTP/2 307 
content-type: text/html; charset=utf-8
location: https://pkg.go.dev/crypto/tls
date: Wed, 27 Jul 2022 02:24:40 GMT
server: Google Frontend
```

Just have golang.org redirect to the version without the trailing slash instead?
Repository: go
Issue: x/time/rate: document the behavior of negative n
Labels: Documentation,help wanted,NeedsInvestigation

The methods `AllowN`, `ReserveN`, `WaitN` take in a user-specified number of tokens to take. [The documentation](https://pkg.go.dev/golang.org/x/time/rate) does not specify what happens when the number of tokens is negative.

Without digging into the details, it appears that you can actually specify a negative n, in which case it returns that number of tokens to the rate limiter.
Repository: rust
Issue: Unhelpful missing try type annotation help suggestion
Labels: A-diagnostics,T-compiler,requires-nightly,F-try_blocks

<!--
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: [[playground]](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=2d7c85eb820226381a345a97d46bd65b)

```rust
#![feature(try_blocks)]

fn main() {
    let _ = try {
        Err::<(), _>("lol")?
    };
}
```

The current output is:

```
error[[E0284]](https://doc.rust-lang.org/nightly/error-index.html#E0284): type annotations needed
 --> src/main.rs:4:9
  |
4 |     let _ = try {
  |         ^
5 |         Err::<(), _>("lol")?
  |         -------------------- type must be known at this point
  |
  = note: cannot satisfy `<_ as Try>::Residual == _`
help: consider giving this pattern a type
  |
4 |     let _: _ = try {
  |          +++
```

... alright, I'll try it

```
error[[E0282]](https://doc.rust-lang.org/nightly/error-index.html#E0282): type annotations needed
 --> src/main.rs:4:12
  |
4 |     let _: _ = try {
  |            ^ cannot infer type
```

The same `<_ as Try>::Residual == _` error and `: _` help occurs with just `Err("lol")?`, but the example here gives the `Ok` type to give the compiler maximal information to present a better error. Unless I misunderstand the `try` desugaring (likely), the error should at least be `<_ as Try>::Residual == Result<Infallible, &str>`?

The suggestion is perhaps fine, since it's (probably?) not possible to give a better suggestion, but if the suggestion is kept, at a minimum the follow-up error after applying the hint shouldn't lose information; ideally it should be possible to notice that this is a `try` block type ascription and provide a hint as to what the compiler _does_ know, and why it needs help.

The minimum amount of type information that I could get to compile is `let _: Result<_, &str> = try { Err("lol")? };`.

This will likely get better "for free" if `try` is changed to be less general. (I recall a discussed possibility about requiring the `Residual` type to match, in order to make type inference work in more cases, of which I think this is one that's ideally supposed to work without further annotation.)

<!--
If the problem is not self-explanatory, please provide a rationale for the
change.
-->

<!--
If dramatically different output is caused by small changes, consider also
adding them here.

If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions. The output might also be
different depending on the Edition.
-->

@rustbot label +F-try_blocks +requires-nightly +D-invalid-suggestion

(rather, D-unhelpful-suggestion)
Repository: excalidraw
Issue: docker excalidraw/excalidraw cannot upload own asset packs
Labels: docker

docker excalidraw/excalidraw cannot upload own asset packs
Repository: create-react-app
Issue: Error "Module not found" for a private scoped npm package
Labels: needs triage,issue: bug report

I have installed a package from my private registry and imported my code in react. It is installed correctly because i can see the right folder in node_modules and the intellisense of my IDE correcly shows the info and files related to the package.

When i do `npm start` the console returns the error:

<img width="906" alt="image" src="https://user-images.githubusercontent.com/11465611/181177498-f5dd888c-62e9-40ec-b4cc-47215c0cf75b.png">

I tried to delete the folder node_modules, package-lock.json and i also did `npm cache clean -f` but nothing changed.

I noticed that if i downgrade react-scripts to a previous verison like 4.0.3 everything works correctly.

### Environment
```
Environment Info:

  current version of create-react-app: 5.0.1
  running from /Users/marcosalafia/.npm/_npx/c67e74de0542c87c/node_modules/create-react-app

  System:
    OS: macOS 12.4
    CPU: (10) arm64 Apple M1 Pro
  Binaries:
    Node: 16.14.2 - ~/.nvm/versions/node/v16.14.2/bin/node
    Yarn: 1.22.15 - ~/.nvm/versions/node/v16.14.2/bin/yarn
    npm: 8.15.0 - ~/.nvm/versions/node/v16.14.2/bin/npm
  Browsers:
    Chrome: 103.0.5060.134
    Edge: Not Found
    Firefox: 101.0.1
    Safari: 15.5
  npmPackages:
    react: ^18.2.0 => 18.2.0 
    react-dom: ^18.2.0 => 18.2.0 
    react-scripts: 5.0.1 => 5.0.1 
  npmGlobalPackages:
    create-react-app: Not Found
```

### Expected behavior

The private scoped npm packaged should be imported regularly like any other scoped npm package.

### Actual behavior

The Module is not found.
Repository: terminal
Issue: Terminal crashes when opening Settings
Labels: Help Wanted,Needs-Repro,Issue-Bug,Severity-Crash,Product-Terminal,Area-SettingsUI

### Windows Terminal version

1.14.1962.0

### Windows build number

10.0.19044.1826

### Other Software

_No response_

### Steps to reproduce

Open Windows Terminal
Either press `Ctrl + ,` or open Settings from the dropdown menu

### Expected Behavior

Expected to open the Settings Tab

### Actual Behavior

Windows terminal crashed, sometimes it became unresponsive and crashed after a few seconds

Extra note: Opening settings(JSON) works fine through command palette
Repository: deno
Issue: Incorrect type checking of objects throughout JS codebase
Labels: bug,web

Example:
```js
const buffer = new ArrayBuffer(100);
// remove prototype
Reflect.setPrototypeOf(buffer, null);
structuredClone(buffer, { transfer: [buffer] });
// restore prototype
Reflect.setPrototypeOf(buffer, ArrayBuffer.prototype);
// assert that {structuredClone} transferred the buffer
console.log(0 === buffer.byteLength);
```
This throws in Deno as of 1.24.0, but not the browsers, or Node.js.
A `TypeError` occurs under the belief that, as the object does not have the `ArrayBuffer` prototype, it is not transferable.
Caused by the use of `Object#isPrototypeOf`. (V8 and the BlinkIDL bindgen do not use prototypes for checking object types)
Repository: go
Issue: x/pkgsite: Redirects of certain packages lose version information
Labels: NeedsInvestigation,pkgsite

### What is the URL of the page with the issue?

https://pkg.go.dev/http@go1.16.13   
 
 
### What did you expect to see?

It should have redirected to https://pkg.go.dev/net/http@go1.16.13
 
 
### What did you see instead?

It redirected to https://pkg.go.dev/net/http
Repository: go
Issue: crypto/tls: support RFC8998 SM3
Labels: NeedsDecision,Proposal-Crypto


can tls support RFC8998

include TLS_SM4_GCM_SM3
Repository: ant-design
Issue: Form Provider should allow error handling and scrolling to first error
Labels: Inactive,improvement

### What problem does this feature solve?

In our case, we have a page with multiple sections and each section has a form in it. The page has an overall submit button that when clicked, should submit all the forms. If all forms successfully validate, we submit all the data to the server at once. If a single one fails, we need to scroll up to the first invalid field on the page. Most of these can be done through workarounds, but it would be nice if the Form Provider supported these.

### What does the proposed API look like?

Form Provider could have the following additional props
- scrollToFirstError (boolean): scrolls to the first invalid field within the first invalid form.
- onFinishAll (function): gets called when all forms validate successfully upon submission.
- onFinishFailed (function): gets called when one of the forms fails to validate upon submission.

Maybe a Form Provider instance could be provided which would have the following properties
- submit (function): submits all forms within the form provider
- validateForms (function): validates all forms, but does not submit them
- reset (function): resets all fields within all forms

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: vscode
Issue: Smooth scrolling has limited upper speed and causes skipping to make up
Labels: bug,editor-scrollbar

Issue Type: <b>Bug</b>

I have a Logitech mouse which allows the scroll wheel to "flywheel" very fast if spun fast enough. When doing this in VSCode, it seems that I can "cap out" the scroll speed of the smooth scrolling support. This means that the longer you've been scrolling, the bigger distance between the "real" scrolled position and the currently-interpolating position is.

This is very problematic, especially because *stopping* the scrolling (via either the real position hitting the top/bottom of the file, or just stopping the mouse wheel) then suddenly causes the scrollbar position to jerk to the position it should have been at.

Video showing the behavior: 

https://user-images.githubusercontent.com/8107459/181236790-7b6aa3f4-cf00-4bec-aaac-6d2fa64c22ea.mp4

The correct solution here would be to uncap the smooth scrolling speed so that it actually keeps up with the mouse wheel.

VS Code version: Code 1.69.2 (Universal) (3b889b090b5ad5793f524b5d1d39fda662b96a2a, 2022-07-18T16:12:57.074Z)
OS version: Darwin arm64 21.3.0
Restricted Mode: No

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Apple M1 Pro (8 x 24)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: disabled_off<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>metal: disabled_off<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_renderer: enabled_on<br>video_decode: enabled<br>video_encode: enabled<br>webgl: enabled<br>webgl2: enabled|
|Load (avg)|2, 3, 3|
|Memory (System)|16.00GB (0.08GB free)|
|Process Argv|--crash-reporter-id 9e7aea1c-a402-443f-9dfc-aa89619d8e05|
|Screen Reader|no|
|VM|0%|

Extension|Author (truncated)|Version
---|---|---
systemd-unit-file|coo|1.0.6
erb|Cra|0.0.1
terraform|has|2.23.0
better-cpp-syntax|jef|1.15.19
remote-ssh|ms-|0.84.0
remote-ssh-edit|ms-|0.80.0
vscode-icons|vsc|11.13.0

(1 theme extensions excluded)

</details><details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonvspyt551cf:30345471
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30525688
vsaa593cf:30376535
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
vscscmwlcmt:30465135
cppdebug:30492333
pylanb8912:30529769
vsclangdf:30486550
c4g48928:30534994

```

</details>

<!-- generated by issue reporter -->
Repository: godot
Issue: Regression: Custom node inheriting BaseButton does not appear in Create New Node dialog
Labels: bug,topic:editor,topic:plugin

### Godot version

v3.4.4.stable.official [419e713a2]

### System information

Ubuntu 2022.04, GeForce GTX 765M

### Issue description

Regression of issue [#8034](https://github.com/godotengine/godot/issues/8034).
Last comment says it's fixed in 3.1 but custom nodes extending abstract classes like `BaseButton` are still / again missing.


### Steps to reproduce

Follow either the steps from the original report or the [custom node example](https://docs.godotengine.org/en/stable/tutorials/plugins/editor/making_plugins.html?highlight=custom%20node#a-custom-node) with a a script extending `BaseButton` instead of `Button`.

### Minimal reproduction project

see original report.
Repository: rust
Issue: libtest's junit formatter does not produce valid XML for doctests
Labels: T-compiler,A-libtest,C-bug,T-testing-devex

<!--
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.
-->

This issue is related to #85563. The junit formatter of libtest does not produce correct XML for some doctests. Take the following as an example:

```rust
use std::marker::PhantomData;


pub struct WithGeneric<A> {
    marker: PhantomData<A>
}

impl<A> WithGeneric<A> {
    /// 
    /// This is a doctest:
    /// 
    /// ```
    /// let _ = hello_world::WithGeneric::<()>::new();
    /// ```
    /// 
    pub fn new() -> Self {
        WithGeneric { marker: PhantomData }
    }
}
```

When running `cargo +nightly-2022-07-26 test --doc -- -Z unstable-options --format junit`, the following (invalid) XML is generated (formatted with an external tool):

```xml
<?xml version="1.0" encoding="UTF-8"?>
<testsuites>
	<testsuite name="test" package="test" id="0" errors="0" failures="0" tests="1" skipped="0" >
		<testcase classname="src/lib.rs" name="WithGeneric<A>::new (line 12)" time="0"/>
		<system-out/>
		<system-err/>
	</testsuite>
</testsuites>
```
The XML is invalid because of the `name` attribute of the `testcase` element. It contains the invalid characters `<` and `>`, which should be escaped to `&lt;` and `&gt;` as far as I understand.

### Proposed solution
In a quick and dirty way I would implement something similar to what the [JSON formatter does](https://github.com/rust-lang/rust/blob/181d28bb6110dc974879db20d433f21aa142db3a/library/test/src/formatters/json.rs#L195) to escape the strings to valid XML attributes - I just did not have time to make a PR so far.

Apart from that I never contributed to this repository, nor am I specifically familiar with libtest. What would it take to implement the serialization based on serde and a crate like [serde_xml_rs](https://crates.io/crates/serde-xml-rs)? Could I just add these crates as a dependency? I feel like this would be much cleaner than just repeating what the json formatter does.
Repository: pytorch
Issue: Add more Vulkan operations
Labels: triaged,module: vulkan,ciflow/periodic

### 🚀 The feature, motivation and pitch

I got an error while trying to host my model into mobile using Vulkan
`Could not run aten::max_pool2d_with_indices`

And I found the list of operations of vulkan quite short.

### Alternatives

_No response_

### Additional context

_No response_

cc @jeffdaily @sunway513