sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Opening Asset Library or the Asset Library Projects overloads my CPU
Labels: bug,topic:editor,confirmed,topic:assetlib,topic:network,performance

*Bugsquad edit: Related to https://github.com/godotengine/godot/issues/35868.*

### Godot version

3.3

### System information

Windows 10, GLES3, Nvidia NVS 5200/Intel HD 4000

### Issue description

When I open the Asset browser in the project manager or in a project itself, and as soon as the icons start showing up. My Godot CPU usages jumps up by 500%+ and completely lags everything else on my computer.

Just to say:
- Yes, I tried different versions of Godot.
- Yes, I even had this same problem with a different operating system,
 "Windows 8".
- Yes, I tried running Godot on my second GPU, did nothing.

https://user-images.githubusercontent.com/57871912/129115686-815e82d9-f197-43ad-a61b-391627d55cd4.mp4

### Steps to reproduce

(ノಠ益ಠ)ノ彡┻━┻

### Minimal reproduction project

_No response_
Repository: terminal
Issue: Upgrade auto-generated UIA testing to include more API tests
Labels: Area-Accessibility,Product-Terminal,Issue-Task

#10886 follow-up

Right now, we only generate tests for `Move()`. That's great! But we could/should easily adapt it to test some other APIs like:
- `ExpandToEnclosingUnit()`
- `MoveEndpointByUnit()`

We may also be able to add tests that make sure we work with clones properly. Like...
- create a clone --> "move" the clone --> clone should not be the same as original
- create a clone --> "move" the clone --> "move" the original the same way --> both should be the same
Repository: opencv
Issue: cv::countNonZero fails with UMat and non-OpenCL allocation (e.g. StdMatAllocator)
Labels: bug,category: core,category: ocl

While debugging another PR, I discovered that `cv::countNonZero` fails when given a `UMat` that has any allocator other than `OpenCLAllocator`.  For example, if given a UMat created when opencl is disable/unavailable...then this function will fail.

#### System information (version)

- OpenCV => 4.5.3
- Operating System / Platform => all
- Compiler => all

#### Detailed description

https://github.com/opencv/opencv/blob/4d63a89fa6611a69c1999328375f39afde1b1696/modules/core/src/count_non_zero.dispatch.cpp#L134-L138

The bug above is in the boolean logic to choose to run/not the OCL version of the counter. Errant code only checks if the `InputArray` is a UMat. It is insufficient. It needs to also confirm that this UMat is allocated by OpenCL. It is required to do that check here so that if it isn't allocated by OpenCL, then it will not run the OCL counter and fallback to code further down.

The fix is generally easy. Just add a test similar to `u->currAllocator == ocl::getOpenCLAllocator()`
However, I am also concerned with the current code having `OCL_PERFORMANCE_CHECK(_src.isUMat())`. It is essential to always in all cases check for both UMat and the Allocator. It isn't a choice of which path is faster/bypass. Instead, one path is impossible. So that macro seems improper in this situation.

#### Steps to reproduce

I found it when running the standard OpenCV test case `Core UMat.setOpenCL` on my laptop with...
```
OPENCV_OPENCL_DEVICE=NVIDIA:GPU:
OPENCV_OPENCL_SVM_FORCE_UMAT_USAGE=TRUE
```

1. `opencv_test_cored.exe --gtest_filter=UMat.*`

#### Result

```
[ RUN      ] UMat.setOpenCL
[ERROR:0] global ..\modules\core\src\ocl.cpp (3966) cv::ocl::Kernel::set OpenCL: Kernel(reduce)::set(arg_index=0, flags=258): can't create cl_mem handle for passed UMat buffer (addr=000000318CCFDE80)
```

#### Expected

No error. Test case to complete successfully.

#### 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 solution
 - [X] I updated to latest OpenCV version and the issue is still there
 - [X] There is reproducer code and related data files: videos, images, onnx, etc
Repository: pytorch
Issue: torch.jit.trace quantized bigbird leads to 0INTERNAL ASSERT FAILED runtime error
Labels: oncall: jit

## 🐛 Bug

Attempt to torch jit trace and save a quantized bigbird model leads to 0INTERNAL ASSERT FAILED runtime error. 

## To Reproduce

Steps to reproduce the behavior:

1. Git clone this [repo](https://github.com/matthiaslmz/quantized_bigbird_issue) 
2. Run `example.ipynb`

Stacktrace:
```
---------------------------------------------------------------------------
RuntimeError                              Traceback (most recent call last)
<ipython-input-4-1dfdd2340788> in <module>
      4 )
      5 
----> 6 traced_model = torch.jit.trace(model, (input_ids, attention_mask))
      7 torch.jit.save(traced_model, "traced_bigbird.pt")

/opt/conda/lib/python3.7/site-packages/torch/jit/_trace.py in trace(func, example_inputs, optimize, check_trace, check_inputs, check_tolerance, strict, _force_outplace, _module_class, _compilation_unit)
    742             strict,
    743             _force_outplace,
--> 744             _module_class,
    745         )
    746 

/opt/conda/lib/python3.7/site-packages/torch/jit/_trace.py in trace_module(mod, inputs, optimize, check_trace, check_inputs, check_tolerance, strict, _force_outplace, _module_class, _compilation_unit)
    957                 strict,
    958                 _force_outplace,
--> 959                 argument_names,
    960             )
    961             check_trace_method = module._c._get_method(method_name)

RuntimeError: 0INTERNAL ASSERT FAILED at "/pytorch/torch/csrc/jit/ir/alias_analysis.cpp":532, please report a bug to PyTorch. We don't have an op for aten::constant_pad_nd but it isn't a special case.  Argument types: Tensor, int[], bool, 

```
## Expected behavior
Quantized bigbird should be able to be saved. 

## Environment

 - PyTorch Version: 1.9.0+cu111
 - OS: Debian GNU/Linux 10 (buster)
 - How you installed PyTorch: `pip3 install torch==1.9.0+cu111 torchvision==0.10.0+cu111 torchaudio==0.9.0 -f https://download.pytorch.org/whl/torch_stable.html`
 - Python version: 3.7.9
 - CUDA/cuDNN version: 11.0.194
 - GPU models and configuration: NVIDIA Tesla V100 16GB

cc @gmagogsfm
Repository: ant-design
Issue: Accessibility: Fix Screen Reader Functionality of FormItem; Remove title attribute from FormItemLabel
Labels: Inactive,⌨️ Accessibility

- [x] I have searched the [issues](https://github.com/ant-design/ant-design/issues) of this repository and believe that this is not a duplicate.

### Reproduction link
[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/antd-reproduction-template-forked-gjgf0?file=/index.js)

### Steps to reproduce
1. Open the reproduction link in Chrome
2. Enable MacOS VoiceOver utility and focus the "First Name" field - the form label is not read aloud
3. Inspect the Form.Item "First Name" label in your browser dev tools 
4. Delete the "title" attribute on the label element in dev tools
5. Focus the "First Name" field - the form label is read aloud



### What is expected?
The field label should be read aloud by MacOS VoiceOver utility when the field is focused 

### What is actually happening?
The field label is not read aloud by MacOS VoiceOver utility

| Environment | Info |
|---|---|
| antd | 4.16.11 |
| React | react |
| System | MacOS |
| Browser | Chrome |

---
The fix seems as simple as removing `title={typeof label === 'string' ? label : ''}` from the FormItemLabel.tsx component. But, I can't tell from the git history why the label element received the title attribute. I'm happy to create a PR, but I want to validate that attribute is not necessary for other use cases before creating a PR.


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: TypeScript
Issue: Narrow indexing variable when type-testing indexed access expressions
Labels: Suggestion,Awaiting More Feedback

# Bug Report

<!--
  Please fill in each section completely. Thank you!
-->

### 🔎 Search Terms
type, inference, object, never
<!--
  What search terms did you use when trying to find an existing bug report?
  List them here so people in the future can find this one more easily.
-->

### 🕗 Version & Regression Information
4.3.5

### ⏯ Playground Link

[Playground link with relevant code](https://www.typescriptlang.org/play?#code/JYOwLgpgTgZghgYwgAgKoGdoEkQwPZQC2cYweIOADgK5jIDeAsAFDJvLWZRYAmAXMnRgooAOYBuFu2RxREASGqEARtEnMAvixYxqIBKXLJIQgBSh8AjNlwFihiiBpgAlAynsE5dHgA2EADpfPFFTACIAIQh8KBQLPGQsSCgSMhA+MIAaZHiXdWl-OgBrASKIAE88GGNyyggqnNt89hjkUyLGxvw3JlZpdmBq0zBa+ur4gG0igF1kAF4F5DChERBRMJ6Pfv7Jmfml4kO4YjDxZAB6c+QAHgBaW+QAUSgoAgBCZC3t75+fy+QACqjZAAchWYhBOXQyBAeDocHQ6GAohAcGU-mMCRGdVBIAgADdoCCAl9pFo+tsIL5MO4Kb9drM5sgAMwARma23JZK+XhAPn8QRC4QAgjBkl0EkloKlyBlsrl1OSWCYwKZetJONh+EsETwYFkvrJ5MhWayWBoXEA)

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
interface UserInformationInput {
    userId: string;
    age: number;
}

function test(info: UserInformationInput) {
    console.log("Before info Iteration:", info);
    let k: keyof typeof info;
    for (k in info) {
        if (typeof info[k] === "string") {
            info[k] = "mamamama"; // <-- Error! 
                             // Type 'string' is not assignable to type 'never'.
        }
        else {
            info[k] = 31; // <-- Error!
                        // Type 'number' is not assignable to type 'never'.
        }
    }
    console.log("After info Iteration:", info);
}

test({
    userId: "asdf",
    age: 11
})
```

### 🙁 Actual behavior
<!-- What happened, and why it was wrong -->
"typeof info[k]" is inferred to be "never"
But at the line 10(if typeof info[k] === "string), "typeof info[k]" was string or number.

Furthermore, after making sure the type of "info[k]" by using "if", it still remains to be "never".

And, although compiler throws an Error above, when I executed the code, it runs very well with the result below
`[LOG]: "Before info Iteration:",  {
  "userId": "asdf",
  "age": 11
} `
`
[LOG]: "After info Iteration:",  {
  "userId": "mamamama",
  "age": 31
} `

### 🙂 Expected behavior
<!-- What you expected to happen instead, and why -->
I think "typeof info[k]" should be "string | number", not 'never'
Repository: TypeScript
Issue: Incorrect warning for synchronousWatchDirectory in tsconfig editor.
Labels: Bug,Help Wanted

<!-- ⚠️⚠️ 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/No
Yes. Ish. Half of the issue. The warning about the boolean is still there.

<!-- 🪓 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. -->
Version: 1.59.0
Commit: 379476f0e13988d90fab105c5c19e7abc8b1dea8
Date: 2021-08-04T23:14:40.191Z (1 day ago)
Electron: 13.1.7
Chrome: 91.0.4472.124
Node.js: 14.16.0
V8: 9.1.269.36-electron.0
OS: Darwin x64 20.6.0

Steps to Reproduce:

1. Install latest ts.
2. create tsconfig.json in root, like so:
```json
{
    "extends": "@tsconfig/node12/tsconfig.json",
    "compilerOptions": {
        "outDir": "./dist",
        "declaration": true,
        "resolveJsonModule": true,
        "noFallthroughCasesInSwitch": true,
        "esModuleInterop": true,
        "downlevelIteration": true,
    },
    "include": [
        "src"
    ],
    "watchOptions": {
        "watchFile": "useFsEvents",
        "watchDirectory": "useFsEvents",
        "fallbackPolling": "dynamicPriority",
        "synchronousWatchDirectory": true,
        "excludeDirectories": [
            "**/node_modules",
            "dist"
        ]
    }
}
```

Notice this warning:
![error](https://user-images.githubusercontent.com/2660021/128514941-2c0dfa0e-0558-47b9-85e1-2e8777dc1bc8.jpg)

The docs themselves (linked in that message):
![docs](https://user-images.githubusercontent.com/2660021/128514962-7b216f8b-675c-4885-a063-f46df1a2ebdd.jpg)

And if you make it a string value:
![error-string](https://user-images.githubusercontent.com/2660021/128514992-a0405633-4812-4d8a-ba2d-0963777c87b4.jpg)

(this last does not appear to show with extensions disabled)

Anyhow, according to the docs and examples I've seen, it should be boolean.
Repository: vscode
Issue: SCM - Display "Repo folder name" in the "Source Control" part of Status bar
Labels: feature-request,scm

<!-- ⚠️⚠️ 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. -->

For Visual Studio, I can check both my current working repo folder name and git branch name:

![Visual studio status bar](https://i.imgur.com/pmskooG.png)

This is very convenient for this situation:

1. I clone two copies of one big repo:

    `git clone https://github.com/some/repo_name.git repo_name-1`
    `git clone https://github.com/some/repo_name.git repo_name-2`

1. Inside the working directory, say: `repo_name-1/subdir/module_x`, I open VS Code at it.

1. And I also open VS Code at `repo_name-2/subdir/module_x`.

This is common for me to work on multiple instances for different features/bugs.

But for VS Code, the status bar only displays branch name, no repo-folder-name, which makes it confusing when I need to know which "local repo" I'm working on, especially when I open the same branch in multiple local repo clones in multiple VS Code instances.

The following screenshot shows the VS Code status bar with the extension "Workspace name in status bar", the extension just displays the "workspace folder name", not the "repo folder name", which as for my case, is not useful, because the workspace name is the folder name in side the repo, which is always the same for me.

![VS Code status bar with extension: Workspace name in status bar](https://i.imgur.com/QgWtkNK.png)

Is it possible to add the "repo folder name" like Visual Studio has? Thanks!
Repository: flutter
Issue: [webview_flutter] Unable to get autocomplete for credit cards data (cc-number) to work in android
Labels: a: text input,p: webview,package,team-ecosystem,has reproducible steps,P3,found in release: 2.2,found in release: 2.5,triaged-ecosystem

## Description

I'm unable to get autocomplete to work **especially for credit cards data like cc-number** in WebView text input fields on Android device. The example page works browsers on mobile devices but for some reason when trying to input data in a WebView in a Flutter app autocomplete does not trigger.

## Steps to Reproduce

Test link: https://justprodev.com/partners/silk/1.html

Clone https://github.com/justprodev/testpayform.git

Run app either in a physical device. Tap on number field.

Maybe you should have some credit card used before.

Expected result:

Something like this (opening https://justprodev.com/partners/silk/1.html in chrome)

![image](https://user-images.githubusercontent.com/58386042/129130963-7d8d3c2b-58ab-4961-bc9d-19e142547869.png)

(Android 10)

## Version

webview_flutter: ^2.0.12

## flutter doctor

```console 
C:\Development_git\silkpayapp>flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 2.2.3, on Microsoft Windows [Version 10.0.19043.1165], locale ru-KZ)
[√] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
[√] Chrome - develop for the web
[√] Android Studio (version 4.1.0)
[√] IntelliJ IDEA Ultimate Edition (version 2020.3)
[√] VS Code, 64-bit edition (version 1.54.1)
[√] Connected device (2 available)
• No issues found!
```
Repository: rust
Issue: Better diagnostic for unaligned reference in `println!`
Labels: A-diagnostics,T-compiler

Tried with current master (ccffcafd55e).

This builds without warnings:

```rust
#[repr(packed)]
pub struct ObjInd {
    _header: u32,
    field: u32,
}

pub unsafe fn test(obj: *const ObjInd) {
    let field = (*obj).field;
    println!("{}", field);
}
```

But this generates a "ref to packed field" warning:

```rust
#[repr(packed)]
pub struct ObjInd {
    _header: u32,
    field: u32,
}

pub unsafe fn test(obj: *const ObjInd) {
    println!("{}", (*obj).field);
}
```

Output:

```
   Compiling packed_field_ptr v0.1.0 (/home/omer/rust/packed_field_ptr)
warning: reference to packed field is unaligned
 --> src/lib.rs:8:20
  |
8 |     println!("{}", (*obj).field);
  |                    ^^^^^^^^^^^^
  |
  = note: `#[warn(unaligned_references)]` on by default
  = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
  = note: for more information, see issue #82523 <https://github.com/rust-lang/rust/issues/82523>
  = note: fields of packed structs are not properly aligned, and creating a misaligned reference is undefined behavior (even if that reference is never dereferenced)

warning: `packed_field_ptr` (lib) generated 1 warning
    Finished dev [unoptimized + debuginfo] target(s) in 0.11s
```

Same with similar macros like `writeln`.

My guess is `println` is taking reference of its arguments, to avoid moving. No idea how to fix these warnings or if it's even possible without breaking backwards compat by making `println` move the args.
Repository: godot
Issue: VIEWPORT_SIZE has wrong values in Shadow Map Render Pass
Labels: bug,usability,topic:shaders,topic:3d

### Godot version

3.3.2

### System information

GLES3 on macos 11, windows 10, fedora 32

### Issue description

I have written a raymarching shader that renders a sphere. Adding a direcitonal light (mode: Orthogonal, depth range: optimized) to the scene produces broken shadows for that sphere (the red one):

![scene_orthogonal](https://user-images.githubusercontent.com/22035786/129149649-feaa2c11-f33f-421f-b831-253b5e8dcb42.PNG)

The reason for this is that in the fragment shader the world space positions for the rays are not calculated correctly, but only in the shadow map depth render pass. They are derived from clip space positions which in turn are calculated using `FRAGCOORD` and `VIEWPORT_SIZE`. 

Using RenderDoc I checked the shadow map. Its size is 4096x4096 but the `viewport_size` uniform was set to 1024x600. For that reason I cannot calculate clip space positions correctly when my shader is run during the shadow map pass.

I hope you can follow this, but in essence the issue is this: `VIEWPORT_SIZE` is not set to the actual viewport size in the shadow map render pass.

### Steps to reproduce

This is reproduceable with any scene that has a directional light. If you check the uniforms using RenderDoc or similar tools you will see that `viewport_size` in the `SceneData` struct is not set correctly in the shadow map render passes (they are depth passes).

### Minimal reproduction project

_No response_
Repository: godot
Issue: EditorFileSystem `update_script_classes`, `scan_sources` has no affect
Labels: bug,topic:editor,topic:plugin

### Godot version

v3.3.2.stable.official

### System information

Windows10, MacOS

### Issue description

Using the EditorFileSystem to force reload script classes not working.

I tryed to use EditorFileSystem.update_script_classes() to force a update of the internal class cache without success.
Also using scan has no success
```
	fs.scan()
	while fs.is_scanning():
		prints("scan progress", fs.get_scanning_progress())
		yield(get_tree(), "idle_frame")
````
The progress is also invalid and shows always `0`


update_file(<file>) has also no affect



### Steps to reproduce

Use the attached project

+ install the plugin 
+ activate
+ use tools -> update

See console log
```
Godot Engine v3.3.2.stable.official (c) 2007-2021 Juan Linietsky, Ariel Manzur & Godot Contributors.
--- GDScript language server started ---
class before update_pressed
------------------------------------------------------------------
class_name TestClass
extends Resource


func foo() -> String:
	return "foo"

------------------------------------------------------------------

process update ...
Closing all currently opened scripts ..
update source res://addons/update//TestClass.gd
resource is cached! res://addons/update//TestClass.gd
force resource load without cache ...
 Another resource is loaded from path 'res://addons/update/TestClass.gd' (possible cyclic resource inclusion).
reloaded -----------------------------
class_name TestClass
extends Resource


func foo() -> String:
	return "fooV2"

func bar() -> String:
	return "bar"

--------------------------------------
force file update on res://addons/update//TestClass.gd
scan progress 0
scan progress 0

class after update
------------------------------------------------------------------
class_name TestClass
extends Resource


func foo() -> String:
	return "foo"

------------------------------------------------------------------
foo


```

### Minimal reproduction project

[class-update-issue.zip](https://github.com/godotengine/godot/files/6973527/class-update-issue.zip)
Repository: flutter
Issue: [Internalization] Support for Soninke language 
Labels: c: new feature,framework,a: internationalization,c: proposal,P3,team-framework,triaged-framework

When generating localizations, I get the following error output:

The following .arb file's locale could not be determined: 
../lib/l10n/app_snk.arb 
Make sure that the locale is specified in the file's '@@locale' property or as part of the filename (e.g. file_en.arb)
Generating synthetic localizations package has failed.
Repository: rust
Issue: array::IntoIter does not get optimized as well as vec::IntoIter
Labels: A-array

I found a situation where creation, conversion into an iterator and consuming the iterator gets optimized for a `Vec`, but not for an array.

[Compiler explorer](https://rust.godbolt.org/z/nPraPsdEr)

The snipped on the left works well; the `abstracted` function compiles down to the same code as the `goal` function. The snipped on the right has the `Vec` usage replaced by an array. The assembler for the `abstracted` function is now more complicated than `goal` function.

Note that if one removes the `Enum::Single` variant, it does work.

I attempted to make the above example minimal. A more elaborate example is [here](https://rust.godbolt.org/z/nf9nn3dda).

Should this be mentioned in https://github.com/rust-lang/rust/issues/84513?