sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: Incorrect CPU implementation of CTCLoss backward step
Labels: module: autograd,module: loss,triaged

### 🐛 Describe the bug

The ATen CTCLoss backward step seems to produce incorrect gradients. The following code snippet reproduces this issue. It computes the differences of the output with respect to every input parameter `input`, and compares them with the backpropagated gradients. The results shall be approximately equal. 

``` python
#!/usr/bin/env python3
import torch

torch.manual_seed(0)
torch.set_printoptions(precision=10)

T, C, S = 5, 3, 4

input = torch.randn(T, C).log_softmax(1).detach().requires_grad_()
target = torch.randint(low=1, high=C, size=(S,), dtype=torch.long)

loss = torch.nn.functional.ctc_loss(
    input, target, torch.tensor(T), torch.tensor(S))
loss.backward()

for i in range(T):
    for j in range(C):
        new_input = input.clone().detach()
        new_input[i][j] += 0.01

        new_loss = torch.nn.functional.ctc_loss(
            new_input, target, torch.tensor(T), torch.tensor(S))

        print((new_loss - loss).detach(), input.grad[i][j] * 0.01) # expected to be approximately equal
```

The actual output is shown below, and the two columns differ significantly.

```
tensor(0.) tensor(0.0021115856)
tensor(0.) tensor(0.0003372314)
tensor(-0.0024995804) tensor(-0.0024488156)
tensor(0.) tensor(0.0018777853)
tensor(-0.0024995804) tensor(-0.0021404340)
tensor(0.) tensor(0.0002626498)
tensor(0.) tensor(0.0008711107)
tensor(0.) tensor(0.0013454026)
tensor(-0.0024995804) tensor(-0.0022165121)
tensor(-0.0025000572) tensor(-0.0018093735)
tensor(0.) tensor(0.0005692409)
tensor(0.) tensor(0.0012401351)
tensor(0.) tensor(0.0002813108)
tensor(0.) tensor(0.0019916897)
tensor(-0.0024998188) tensor(-0.0022729994)
```

It seems that 

https://github.com/pytorch/pytorch/blob/4bb7e148c46167cb2b0beedf4332eb6eae5b03cc/aten/src/ATen/native/LossCTC.cpp#L330

shall be corrected to

``` c++
res = -std::exp(res + nll - lp) * gr;
```

### Versions

PyTorch version: 1.12.0
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: macOS 12.5 (x86_64)
GCC version: Could not collect
Clang version: 13.1.6 (clang-1316.0.21.2.5)
CMake version: version 3.18.2
Libc version: N/A

Python version: 3.8.5 (default, Jul 21 2020, 10:48:26)  [Clang 11.0.3 (clang-1103.0.32.62)] (64-bit runtime)
Python platform: macOS-10.16-x86_64-i386-64bit
Is CUDA available: False
CUDA runtime version: No CUDA
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.19.2
[pip3] torch==1.12.0
[conda] Could not collect

cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7
Repository: pytorch
Issue: Libtorch C++ torch::stack error
Labels: needs reproduction,module: cpp,triaged

#include <iostream>
#include <torch/torch.h>

int main()
{
	torch::Tensor a = torch::rand({ 1, 4 });
	torch::Tensor b = torch::rand({ 1, 4 });
	std::cout << " a = " << a << std::endl;
	std::cout << " b = " << b << std::endl;
	torch::Tensor c = torch::stack({ a, b }, 0);
	std::cout << " c = " << c << std::endl;
	return 0;
}
![image](https://user-images.githubusercontent.com/52875069/182019591-5d343c91-faa5-4d4e-b02d-3fbd8664ab27.png)


cc @jbschlosser
Repository: material-ui
Issue: [Popper] Placeholder text from `TextField` is appearing inside `Popper`.
Labels: component: Popper

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯

When a `Popper` component is displayed above an `TextField` component, the place holder text of `TextField` is appearing inside the `Popper`.

### Expected behavior 🤔

No content of the `TextField` component should appear on the `Popper` when `Popper` displays above `TextField`.

### Steps to reproduce 🕹

Live Example: https://codesandbox.io/s/determined-black-85vufb?file=/demo.js


Steps:

1. Make sure the `Popper` displays above a `TextField`
2. Click on "Toggle Popper" button to display `Popper`.
3. See that placeholder text of `TextField` being displayed inside the `Popper`.


### Context 🔦

I am trying to display a `Popper` to help the user when filling a form thus the issues with `Popper` and `TextField`.

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  System:
    OS: Linux 5.18 undefined
  Binaries:
    Node: 18.7.0 - /usr/bin/node
    Yarn: 1.22.19 - /usr/bin/yarn
    npm: 8.15.1 - /usr/bin/npm
  Browsers:
    Chrome: Not Found
    Firefox: 103.0
  npmPackages:
    @emotion/react: ^11.9.3 => 11.9.3 
    @emotion/styled: ^11.9.3 => 11.9.3 
    @mui/base:  5.0.0-alpha.91 
    @mui/icons-material: ^5.8.4 => 5.8.4 
    @mui/material: ^5.9.2 => 5.9.2 
    @mui/private-theming:  5.9.1 
    @mui/styled-engine:  5.8.7 
    @mui/system:  5.9.2 
    @mui/types:  7.1.5 
    @mui/utils:  5.9.1 
    @types/react:  18.0.15 
    react: ^18.2.0 => 18.2.0 
    react-dom: ^18.2.0 => 18.2.0 
    typescript:  4.7.4 
```
</details>

I used Firefox. The issue is same with chromium based browsers.
Repository: godot
Issue: Error notifications out of sync with Output console
Labels: discussion,topic:gdscript,topic:editor

### Godot version

4.0.alpha13

### System information

Windows 10

### Issue description

Errors that are displayed on startup via the notification popup do not appear in the error console:

![Capture](https://user-images.githubusercontent.com/822035/182021248-466a5aab-0309-405f-8ab4-768962780a13.JPG)

I would expect these errors to be shown in the Output but it shows 0 errors.

### Steps to reproduce

1. open any Godot 4 project that has a lot of errors (e.g. while migrating over to Godot 4)
2. An overwhelming amount of error notifications is shown
3. The notification errors do not align with what is shown in the Output console

### Minimal reproduction project

[GUT_Godot4_WithErrors.zip](https://github.com/godotengine/godot/files/9228626/GUT_Godot4_WithErrors.zip)
Repository: PowerToys
Issue: Image thumbnail control in explorer
Labels: Idea-Enhancement,Product-File Explorer,Needs-Triage

### Description of the new feature / enhancement

First I want to thank everyone who works on PowerToys. It really is an amazing extension I use every single day.

My request is about the file explorer thumbnails.
In my research I've found out people are asking for larger images / thumbnails in file explorer for years now.

I work a lot with images, and I find myself constantly switching between 'content view', 'XL images' and details view. 
For larger monitors the images are just to small at their max 256px. 

A really welcome feature would be to be able to preview images larger than the current XL images.

When using the content view --> where you can see the file size and image sizes in one view, having the possibility to see them with XL thumbnails as well would make a huge difference for people working with a lot of images. 

I haven't been able to find a software solution that solves this.


### Scenario when this would be used?

For me personally; everyday when working on websites. 
Sorting images, seeing what quality they are, having the image specs while having a clear view. 

But I would say daily for almost anyone who works with pictures on a regular basis.

### Supporting information

If you google: "windows explorer larger images then XL" you'll see pages full of topics about this.
Repository: pytorch
Issue: make_fx is broken for all tracing modes
Labels: high priority,module: crash,triaged,module: fx,fx

### 🐛 Describe the bug

Running the script from https://gist.github.com/zou3519/3869d460f8bcb12799967e08a5998d9c raises an error on the `make_fx` call for `symbolic` and `real` tracing modes and segfaults for `tracing_mode="fake"`.

`tracing_mode="real"` :
```py
File ~/dev/pytorch/master/torch/fx/experimental/proxy_tensor.py:134, in proxy_call(func_overload, args, kwargs)
    132     if t.constant is not None:
    133         with maybe_disable_fake_tensor_mode():
--> 134             return t.constant.item()
    135     raise RuntimeError("It appears that you're trying to get value out of a tracing tensor - erroring out! "
    136                        "It's likely that this is caused by data-dependent control flow or similar."
    137                        "Try torch.fx.experimental.proxy_tensor.enable_strict(False) to disable this check")
    139 def unwrap_proxy(e):

AttributeError: 'list' object has no attribute 'item'
```
using `tracing_mode="symbolic"` raises another error:
```py
File ~/dev/pytorch/master/functorch/functorch/_src/vmap.py:484, in _flat_vmap(func, batch_size, flat_in_dims, flat_args, args_spec, out_dims, randomness, **kwargs)
    483 def _flat_vmap(func, batch_size, flat_in_dims, flat_args, args_spec, out_dims, randomness, **kwargs):
--> 484     vmap_level = _vmap_increment_nesting(batch_size, randomness)
    485     try:
    486         batched_inputs = _create_batched_inputs(flat_in_dims, flat_args, vmap_level, args_spec)

TypeError: _vmap_increment_nesting(): incompatible function arguments. The following argument types are supported:
    1. (arg0: int, arg1: str) -> int

Invoked with: <torch.SymIntNode object at 0x7f6275eec3f0>, 'error'
```
and `tracing_mode="fake"` segfaults.

### Versions

Latest master branch.

cc @ezyang @gchanan @zou3519 @SherlockNoMad
Repository: godot
Issue: Type hinting does not help to detect invalid match cases
Labels: enhancement,topic:gdscript

### Godot version

4.0 dev (5352cf8e2f)

### System information

Linux Mint 20

### Issue description

GdScript 2.0 match statement does not take full advantage of type hints. Consider following code:
```
	var some_int: int = 1
	match(some_int):
		1.0:
			print("matched with float")
		1: 
			print("matched with int")
```
As you can see variable `some_int` will be always of type `int`. Match statement below does not really take advantage of this information and allows creation of branch that matches index against float pattern. This pattern will never be matched obviously as match statement is strongly typed. Code like that is likely to be the result of programmer error, syntax checker should help us to detect this either by preventing this code from compiling or at least issuing warning.





### Steps to reproduce

put this code in gd script editor
```
	var some_int: int = 1
	match(some_int):
		1.0:
			print("matched with float")
		1: 
			print("matched with int")
```

### Minimal reproduction project

_No response_
Repository: vscode
Issue: Allow Word Seperator Selection
Labels: feature-request,editor-commands

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
Hi there! I'm using vscode writing Python, and then I find that **I can't select '=' by double click on the words in the editor**, like this:
![vscode1](https://user-images.githubusercontent.com/38586229/182025510-0b6b4f75-c401-4d0b-a025-c961b63ae856.gif)

I noticed that there is a setting called `editor.wordSeparators`, but if I delete '=' from seperator chars, I can select '=', but I got wrong word selection at other places:
![vscode2](https://user-images.githubusercontent.com/38586229/182025511-8daa5e8f-437a-49da-b8f5-abc1457c9655.gif)

**So are there any missing settings for doing this? If no, can we add a setting for "Allowing Word Seperator Selection"?**
P.S. Just Like in Notepad++
![npp](https://user-images.githubusercontent.com/38586229/182025520-a49cdac5-233d-4721-b98b-acd45ea310ec.gif)

<details>
<summary>VSCode Version Info</summary>

+ version: 1.69.2 (system setup)
+ commit: 3b889b090b5ad5793f524b5d1d39fda662b96a2a
+ Electron: 18.3.5
+ Chromium: 100.0.4896.160
+ Node.js: 16.13.2
+ V8: 10.0.139.17-electron.0
+ OS: Windows 10
</details>
Repository: rust
Issue: Confusing diagnostic when typoing `Wrapper(t): Wrapper<t>` in a function signature
Labels: A-diagnostics,T-compiler

Given the following code:

https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=57d52025a7f3f79dae1ff241d9e7a243

```rust
struct Wrapper<T>(T);
struct Foo;

fn takes_a_wrapped_foo(Wrapper(foo): Wrapper<foo>) { // << was supposed to be Wrapper<Foo>
}
```

The current output is:

```
error[[E0435]](https://doc.rust-lang.org/stable/error-index.html#E0435): attempt to use a non-constant value in a constant
 --> src/lib.rs:4:46
  |
4 | fn takes_a_wrapped_foo(Wrapper(foo): Wrapper<foo>) {
  |                                ---           ^^^
  |                                |
  |                                this would need to be a `const`
```

Ideally the output should look like:

Something like "did you mean `Wrapper<Foo>`?"

CC @estebank
Repository: deno
Issue: `Atomics.waitAsync` does not bind to event loop
Labels: bug,deno_core

The `waitAsync` call does not bind to Tokio event loop in any way. Deno has no idea that `waitAsync` is creates a Promise that should be polled nor that the Promise should keep Deno from exiting.

As a result, this code will exit with a warning about pending ops:
```ts
// mod.ts
const sab = new SharedArrayBuffer(4);
const int32 = new Int32Array(sab);
await Atomics.waitAsync(int32, 0, 0, 2).value;
```

An alternative method to verify the bug is to open REPL, setup the `int32` buffer as above, and then do repeated calls like this, one at at ime:
```ts
let i = 0; // Only init this once
Atomics.waitAsync(int32, 0, 0, 2).value.then(() => console.log(`Call ${++i}`));
```
One would expect the first call to be quickly followed by a log `Call 1` but instead no log appears. After the second call the `Call 1` appears, while `Call 2` appears only after the third call etc.
Repository: TypeScript
Issue: Unhelpful TS2322 error message when assigning a type to another type.
Labels: Bug,Help Wanted

# Bug Report

### 🔎 Search Terms
TS2322 unhelpful message

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about `TS2322`

### ⏯ Playground Link

[Playground link with relevant code](https://www.typescriptlang.org/play?ts=4.8.0-beta#code/C4TwDgpgBAysBOBLAdgcwLIEMxQLxQG8BYAKAEgBtADwC4oBnBFVAXTsaTQG5SBfU0qEhR0EevUyoIAHgAqWHBCrAIyACb1YTNAoA0UWVCUr1mgNYQQAewBmBhQD48hUmQBGmeHQBEH+N55yIQg6WUD+EkFwaFFxSQgACQgAG0h4OQUjZVUNLU4MbH1DYxzzS1t7bCdcV2Ls0ygLazt5bCgAflcyWIkpDMKDJxou5AgANwh4QNIbAFdkAGNgRCtkKBsrK37Fety4fL0DLJNcporWsAcACmDQgEoXcgXVxigAWzFe6Doe+O2i6qPMjuTw+PzeXRdYKQ8gRVzPZCvD5xKQAJigP0+8SSqUm-0GzmRX0CZAA9KSoJSoAA9Wl02kAWiZzIZBmiUAA5L8+hcARyoIhNMgrMAoJhxIhUMhMG5ktBgFYoMFOdzEik0vjZA4OQA6ATkInxHXBLhQclHEoNM4tBSuQ1o43RU3mq7Wyo4ABkDG0qAeAB8oK7yja2l7kLM3m5Jv7A26LlAvfQQJGrMk7vqyPaII7hPgs6icxASebqQYABaCgWaN5WeDQMvqubJfRuWaigCSUDLmDUSsVACsIzhgGX4FZZqgy1AAI6zRAqBhWD5dzZgTQK9YoTDJZIgTeoWZ11zm8eikeVgDu4qVDagC0ws3o2b4+qAA)

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
type StringMap = {
	[x: string]: string;
}

type Message<TMap extends StringMap, T extends keyof TMap> = {
	bar: "bar";
	type: T;
}

type MessageHelper<TMap extends StringMap, T extends keyof TMap> =
	T extends keyof TMap ?
		Message<TMap, T> :
		never;

function foo<TMap extends StringMap, T extends keyof TMap>(type: T) {
	const message : Message<TMap, T> = {
		bar: "bar",
		type,
	}

	const message2 : MessageHelper<TMap, T> = message;
	//    ^^^^^^^^------- Type 'Message<TMap, T>' is not assignable to type 'MessageHelper<TMap, T>'.

	message.type; // T extends keyof TMap
	message2.type; // (keyof TMap & string) | (keyof TMap & number) | (keyof TMap & symbol)

	message.type = message2.type;
	// ^^^^^^^^^ This is more helpful, but I had to jump through quite some hoops to finally figure
	// out this was the cause.
}


```

### 🙁 Actual behavior

The error that occurs when assigning `message` to `message2` shows just
```
Type 'Message<TMap, T>' is not assignable to type 'MessageHelper<TMap, T>'.
```

### 🙂 Expected behavior

A better explanation of why the types are not assignable. I'm assuming it's because the types of `message.type` are different. But this isn't clearly shown in the error message.
Repository: godot
Issue: Android plugin failing to load
Labels: platform:android,topic:plugin,needs testing

### Godot version

3.4.4-stable

### System information

Windows 11

### Issue description

I've created an Android plugin named `StepsPlugin`. The GoDot editor recognizes this plugin and lets me enable it, but when I try to load it via `Engine.get_singleton("StepsPlugin")`, I get `null`.

### Steps to reproduce

Create an Android plugin, like so:
```java
package com.mylittlewordland.walkandbuild.stepsplugin;

import androidx.annotation.NonNull;
import org.godotengine.godot.Godot;
import org.godotengine.godot.plugin.GodotPlugin;
import org.godotengine.godot.plugin.UsedByGodot;

public class StepsPlugin extends GodotPlugin {

    public StepsPlugin(Godot godot) {
        super(godot);
    }

    @UsedByGodot
    public String test() {
        return "usedByGodotTest";
    }

    public String otherTest() { return "otherTest"; }

    @NonNull
    @Override
    public String getPluginName() {
        return "StepsPlugin";
    }
}

```

Build the plugin.

Create a `.gdap` file, like so:
```ini
[config]
name="StepsPlugin"
binary_type="local"
binary="StepsPlugin-release.aar"
```

In the Godot editor, enable custom Android builds and enable the plugin:
![steps plugin](https://user-images.githubusercontent.com/10658081/182033905-5cfa1e40-45a2-4e74-b70b-692ea3721355.png)

Add a script to the root node that tries to load `StepsPlugin` and call a method on it:

```
extends Node2D

func _ready():
	print("getting StepsPlugin")
	var stepsPlugin = Engine.get_singleton("StepsPlugin")
```

Export the `.apk`.

In Android Studio, open the project and run it on the Android phone. I get this error:

```
I/godot: getting StepsPlugin
E/godot: ERROR: Failed to retrieve non-existent singleton 'StepsPlugin'.
E/godot:    at: get_singleton_object (core/engine.cpp:202) - Condition "!E" is true. Returned: nullptr
```

### Minimal reproduction project

I'd be happy to provide a repo, if it'd be helpful :)
Repository: godot
Issue: Dropdown GUI freezes and fails (DisplayServer regression)
Labels: bug,platform:windows,topic:editor,topic:porting,regression

### Godot version

4.0 alpha13

### System information

Windows 8.1

### Issue description

Dropdown menus, both in the project selector and after loading a project, freeze the window for a couple seconds and fail to actually present the dropdown in latest alpha, but work fine on the same machine in stable.

### Steps to reproduce

No example project because it happens before even opening a project. Attempting to select the "sort by [date/name/etc]" dropdown freezes the window for a second or two, but when it revives I never actually see the dropdown. All in-project dropdowns I tried behaved like this as well. However, attempting to change the language also freezes for a couple seconds, but successfully loads the language dropdown behind the main window; I can still select languages normally where they stick out. It's the only dropdown I've found in or out of a project that works at all in alpha13. Multiple attempts don't fix the issue, nor does restarting so it's not https://github.com/godotengine/godot/issues/61758. It's also not https://github.com/godotengine/godot/issues/61773 as far as I understand that issue, as all other use of the editor is functional, and alt-tabbing doesn't affect the symptoms. 

3.4.4 stable works just fine, so I tried 4.0 alpha1. Dropdowns still cause hangs, but all dropdowns except language work normally after the hang. When trying to change language in alpha1, after clicking exactly once, without ever showing a dropdown, after the hang it changes my language and a popup asks if I'd like to restart. It seems to be whichever one would be behind where I clicked on the dropdown UI, despite only clicking once--consistently the first is Bengali, then as I keep choosing "continue" and changing language again, it went down to Czech, then Catalan, and it looked alphabetical so I stopped.

So it broke somewhere between 3.4 and 4.0, and broke a little more somewhere between alpha1 and alpha9 (first alpha I tried to use, same symptoms on both alpha12 and alpha13). I can try testing the 7 alphas between them if necessary, but I want to just get this bug report out for now.

### Minimal reproduction project

_No response_
Repository: node
Issue: Node API core consolidation
Labels: node-api

People are complaining that the node-api core implementation is deviating from node.js core conventions and has a lot of workarounds and non-conventional mechanisms, especially around the finalizers. It makes it harder to maintain the node-api code base.

I'm working with the @nodejs/node-api team on the document https://docs.google.com/document/d/1Bqm05PWQni65FVdSKiaVAkqCAOD9HIfCqG_Y4CAYTbo/edit?usp=sharing to list the problems we are facing and try to figure out what approaches we can apply.

@addaleax thanks for bringing the topic up at https://github.com/nodejs/node/pull/36510#discussion_r830628160.

Opening this issue to track the progress.
Repository: rust
Issue: Download a pre-compiled bootstrap from CI
Labels: E-mentor,T-bootstrap,E-medium

Currently, we unconditionally recompile bootstrap on all builds, like libstd. In most cases, this is unnecessary: bootstrap is rarely changed and it's confusing that we have to build a whole rust program before processing `x.py --help`. Additionally, it means that when we add the new shell script entrypoints, we'd have to replicate all of bootstrap.py's logic for finding config.toml and the build directory. If we can download bootstrap through rustup, it will greatly simplify all that logic.

Most of this work has already been done in https://github.com/rust-lang/rust/pull/98483. The work left is to actually download the generated artifact in bootstrap.py.

cc @dvtkrlbs

Mentoring instructions:
1. Add a new `download_or_build_bootstrap` function to `src/bootstrap/bootstrap.py`.
2. If there are changes to src/bootstrap (you can find these with `git diff-index --quiet HEAD -- src/bootstrap`), then always rebuild it from source.
3. Otherwise, download it from ci-artifacts.rust-lang.org, as configured by `stage0.json` - you may have to modify the `Stage0Toolchain` python object to load this configuration.

Helps with https://github.com/rust-lang/rust/issues/94829.

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"dvtkrlbs"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->