sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: Overly verbose output on invalid for loop due to recovery
Labels: C-enhancement,A-diagnostics,A-parser,P-low,T-compiler,D-verbose

Given code like

```rust
fn main() {
    for (int i; i<10; i++) {}
}
```

the current output is

```
error: expected one of `)`, `,`, `@`, or `|`, found `i`
 --> src/main.rs:2:14
  |
2 |     for (int i; i<10; i++) {}
  |             -^ expected one of `)`, `,`, `@`, or `|`
  |             |
  |             help: missing `,`

error: expected one of `)`, `,`, `@`, or `|`, found `;`
 --> src/main.rs:2:15
  |
2 |     for (int i; i<10; i++) {}
  |               ^
  |               |
  |               expected one of `)`, `,`, `@`, or `|`
  |               help: missing `,`

error: expected one of `)`, `,`, `@`, or `|`, found `<`
 --> src/main.rs:2:18
  |
2 |     for (int i; i<10; i++) {}
  |                  ^
  |                  |
  |                  expected one of `)`, `,`, `@`, or `|`
  |                  help: missing `,`

error: expected one of `)`, `,`, `...`, `..=`, `..`, or `|`, found `;`
 --> src/main.rs:2:21
  |
2 |     for (int i; i<10; i++) {}
  |                     ^
  |                     |
  |                     expected one of `)`, `,`, `...`, `..=`, `..`, or `|`
  |                     help: missing `,`

error: expected one of `)`, `,`, `@`, or `|`, found `+`
 --> src/main.rs:2:24
  |
2 |     for (int i; i<10; i++) {}
  |                        ^ expected one of `)`, `,`, `@`, or `|`

error: missing `in` in `for` loop
 --> src/main.rs:2:24
  |
2 |     for (int i; i<10; i++) {}
  |                        ^ help: try adding `in` here

error: expected expression, found `+`
 --> src/main.rs:2:24
  |
2 |     for (int i; i<10; i++) {}
  |                        ^ expected expression

error: aborting due to 7 previous errors
```

Ideally the output would be much less verbose. An option could be to track in `ParseSess` how many parse errors have occurred and only once recovery has been successful for a whole item allow further parse errors. For parse errors inside of any item we swallow every token until the closing `}`, but in this case multiple layers of recovery cause cascading parse errors.

A potential output that should be attainable without overly complicating the parser could be:

```
error: expected one of `)`, `,`, `@`, or `|`, found `i`
 --> src/main.rs:2:14
  |
2 |     for (int i; i<10; i++) {}
  |             -^ expected one of `)`, `,`, `@`, or `|`
  |             |
  |             help: missing `,`

error: malformed `for` loop expression
 --> src/main.rs:2:15
  |
2 |     for (int i; i<10; i++) {}
  |     ---       ^ expected one of `)`, `,`, `@`, or `|`
  |     |         
  |     parsing this `for` loop
  |
help: for loops are written as `for PATTERN in EXPRESSION { BODY }`
```

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

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

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: PowerToys
Issue: Port C++/CX projects to C++/WinRT
Labels: Help Wanted,Priority-1,Area-Build,External Dependency-WinUI 3

For the great conversion to WinUI3, we'll need to shift any project from C++/CX to C++/WinRT
Repository: rust
Issue: Tracking Issue for expose force_quotes in CommandExt on Win32
Labels: O-windows,T-libs-api,C-tracking-issue

<!--
Thank you for creating a tracking issue!

Tracking issues are for tracking a feature from implementation to stabilization.

Make sure to include the relevant RFC for the feature if it has one.

If the new feature is small, it may be fine to skip the RFC process. In that
case, you can use use `issue = "none"` in your initial implementation PR. The
reviewer will ask you to open a tracking issue if they agree your feature can be
added without an RFC.
-->

Feature gate: `#![feature(windows_process_extensions_force_quotes)]`

This is a tracking issue for expose force_quotes in CommandExt on Win32

Forces all arguments to be wrapped in quote (`"`) characters.

This is useful for passing arguments to [MSYS2/Cygwin][1] based
executables: these programs will expand unquoted arguments containing
wildcard characters (`?` and `*`) by searching for any file paths
matching the wildcard pattern.

Adding quotes has no effect when passing arguments to programs
that use [msvcrt][2]. This includes programs built with both
MinGW and MSVC.

[1]: <https://github.com/msys2/MSYS2-packages/issues/2176>
[2]: <https://msdn.microsoft.com/en-us/library/17w5ykft.aspx>


### Public API


```rust
// std::process

pub trait CommandExt: Sealed {
    #[unstable(feature = "windows_process_extensions_force_quotes", issue = "82227")]
    fn force_quotes(&mut self, enabled: bool) -> &mut process::Command;
}
```

### Steps / History

<!--
For larger features, more steps might be involved.
If the feature is changed later, please add those PRs here as well.
-->

- [x] Implementation:  https://github.com/rust-lang/rust/pull/77728
- [ ] Final commenting period (FCP)
- [ ] Stabilization PR

<!--
Once the feature has gone through a few release cycles and there are no
unresolved questions left, the feature might be ready for stabilization.

If this feature didn't go through the RFC process, a final commenting period
(FCP) is always needed before stabilization. This works as follows:

A library team member can kick off the stabilization process, at which point
the rfcbot will ask all the team members to verify they agree with
stabilization. Once enough members agree and there are no concerns, the final
commenting period begins: this issue will be marked as such and will be listed
in the next This Week in Rust newsletter. If no blocking concerns are raised in
that period of 10 days, a stabilzation PR can be opened by anyone.
-->

### Unresolved Questions

<!--
Include any open questions that need to be answered before the feature can be
stabilised. If multiple (unrelated) big questions come up, it can be a good idea
to open a separate issue for each, to make it easier to keep track of the
discussions.

It's useful to link any relevant discussions and conclusions (whether on GitHub,
Zulip, or the internals forum) here.
-->

- None yet.
Repository: godot
Issue: Android template build fails with cmake error
Labels: bug,platform:android,topic:buildsystem

<!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->

**Godot version:**
<!-- Specify commit hash if using non-official build. -->
Godot_v3.2.3-stable

**OS/device including version:**
<!-- Specify GPU model, drivers, and the backend (GLES2, GLES3, Vulkan) if graphics-related. -->
Windows 10

**Issue description:**
<!-- What happened, and what was expected. -->
I managed to follow the tutorial in https://docs.godotengine.org/es/stable/development/compiling/compiling_for_android.html.
The scons part is all right, both released for armv7 y arm64v8 compiled ok.
So, I run .\gradlew generateGodotTemplates from designed folder. It starst to download a handfull of thing, install them, everything ok.
But suddenly the process stops and throws this error:
>Could not determine the dependencies of task : Godot:lib:mergeReleaseNativeLibs.
>CMake 3.6.0 was not found in PATH or by cmake.dir property.

Funny thing is gradle installed CMake 3.6.4111459, not 3.6.0. 

I´m no expert with gradle. I guess the CMake in use has to be changed, but no clue how to do that.
I didn´t install Android Studio, just the command line tools as instructed in the tutorial.
NDK is r21e, not r22.

So, how do I do to skip this error?

Thx!
Repository: electron
Issue: [Feature Request]: AutoFill enabled in the <webview> tag for in-app purchases
Labels: enhancement :sparkles:

**Preflight Checklist**

* [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [X] I have searched the issue tracker for a feature request that matches the one I want to file, without success.


**Problem Description**

If a Chrome user is logged into Google and autofill for passwords, payment methods and addresses are turned on, when Electron triggers a webview, I would like to have autofill populate these fields in the Electron webview.

I've looked over the docs and prior issues but nothing seems to be coming up. For in-app purchases, this is a vital feature since it reduces friction for a sale.

**Proposed Solution**

I would like to be able to sync google chrome, or the browser data with the chromium engine, since when opening internet tabs it's suppose to have base features such as autofill.

**Alternatives Considered**

Tried all the configs of the <webview> tag, and even the chrome extentions for electron. Used other ways to open the purchase page in  also, such as calling the external browser. But then its not an in-app purchase.

**Additional Information**

Background:

Electron version: 9.2
Mac OS 10.13
Win 10
Repository: rust
Issue: `x.py test --bless` should not ignore tests
Labels: A-testsuite,C-enhancement,T-bootstrap,A-contributor-roadblock,A-compiletest

Some `ignore` directives in tests (such as `needs-profiler-support`) direct `compiletest` to skip over tests when certain conditions are not present.

If a compiler change also requires rebuilding "blessed" (expected) test results, those results may need to be rebuild, regardless of the developer's local configuration choices.

For instance, tests that include `needs-profiler-support` will be ignored if the developer has not enabled `profiler = true`. When the developer runs `x.py test --bless`, the subject tests will not run, and updated results will not be generated, but the `x.py test` run will appear to have succeeded.

For some tests that only run under a full `bors` CI run, the test will eventually fail (perhaps hours or days later), with potentially mysterious results (to the developer), since they passed locally.

I suggest ignoring "ignore" when "--bless" is specified.

If the developer is unable to recreate all required configurations, the developer should at least get feedback, via error messages, about the tests that failed, and can either adjust their environment to compensate, or visually verify that their changes should not affect the failed tests (and may not require blessing them).

cc: @jyn514
Repository: PowerToys
Issue: [KBM] Remap based on input language
Labels: Idea-Enhancement,Product-Keyboard Shortcut Manager

Hello, this is a problem which has been plaguing international community for years, but now, PowerToys has almost managed to solve it, ALMOST but not yet.

What's the key problem here (pun intended):

_Shortcuts aren't connected to physical keyboard buttons, but instead to letters which are assigned to them._

I'll give you practical example. I am from a European country (Serbia) which uses QWERTZ layout instead of QWERTY. So on my PC, I use Serbian keyboard for writing comments and articles online, writing documents inside MS Word, etc. However, when I do programming, I switch to English keyboard, because useful symbols like ;':"[] are much more accessible. Plus, the painted layout on my keyboard is English, so even if I don't know where is which symbol located, I can look on my keyboard, whereas if I use Serbian keyboard, I have to memorize which letter is located where.

Anyhow, two of the most commonly used shortcuts, **Undo and Redo (Ctrl+Z and Ctrl+Y) directly depend from the fact whether I use Serbian (QWERTZ) or English (QWERTY) keyboard**. Ctrl+Z is made to be Undo on purpose, because Z is the nearest key located to the Ctrl button, so fingers don't have to travel far in order to trigger it, and that's how I used to use it, I'm used to Ctrl+Z where Z is in the bottom left corner of the keyboard (in QWERTY layout). However, my keyboard spends more than half of its time in Serbian, and when I use programs such as MS Word or Photoshop, I don't really have the need to switch to English keyboard the same way I would need it if I was using, let's say, Visual Studio. So when I use those programs, My Undo and Redo shortcuts are actually flipped, because the Z and Y keys' location is switched.

So to combat that, **I installed PowerToys hoping that I could switch Ctrl+Z and Ctrl+Y via Remap shortcuts option**, but tough luck.
This only flipped the thing around, because now, I fixed the problem for Serbian keyboard, where Undo is indeed switched from Ctrl+Y to Ctrl+Z, but now I introduced the same problem to English keyboard, because Ctrl+Z is now switched to Ctrl+Y on it. There is no condition whether this shortcut remapping only works for certain inputs, where it really should be.

**There should be an option to make a shortcut depend on input language**. We should be able to select "All", or just checkbox certain languages (assuming we have multiple input languages on our list), so we can choose to switch Ctrl+Z on QWERTZ inputs, but leave it as it is on QWERTY ones.

I can only imagine what kind of problems do multilingual French people have, when they have to switch from QWERTY to AZERTY layout.
Repository: TypeScript
Issue: Problems panel lists 4 problems for jsconfig.json in my project
Labels: Needs Investigation

*TS Template added by @mjbvz*

**TypeScript Version**: 4.1.5

**Search Terms**
- configdiag

---

<!-- ⚠️⚠️ 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. -->
- VS Code Version: 1.53.2
- OS Version: Windows 10

Steps to Reproduce:

1. Create a new Gatsby project, or clone from [my repo](https://github.com/lewisgauss/lewischan.dev)
2. Open VSCode
3. Create a new jsconfig.json file if it does not exist
4. Problems panel will randomly show errors on the jsconfig.json file
![image](https://user-images.githubusercontent.com/8966669/107747793-fcbe2e00-6d52-11eb-93d9-f3cc08935d89.png)

The jsconfig.json file contains this:
```json
{
    "compilerOptions": {
        "module": "commonjs",
        "jsx": "preserve",
        "baseUrl": "./src"
    },
    "include": ["src"],
    "exclude": [
        "node_modules",
        "**/node_modules/*",
        "node_modules/**/*",
        "public"
    ]
}
```

Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported direct to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
Repository: PowerToys
Issue: Enable RDP to different sets of monitors
Labels: Idea-New PowerToy

From: https://www.hanselman.com/blog/how-to-remote-desktop-fullscreen-rdp-with-just-some-of-your-multiple-monitors

Turns out that you CAN span n monitors but it's just buried/internal and has no UI.

Save your RDP file, and open it in Notepad. Everyone's RDP file is different but yours may look like this:

```
full address:s:x.x.x.x:3389
prompt for credentials:i:1
administrative session:i:1
screen mode id:i:2
span monitors:i:1
use multimon:i:1
selectedmonitors:s:0,1
```

I can put on selectedmonitors:s:x,y and then use the zero-based numbers to indicate my monitors. To get a list of monitors, I can run mstsc /l to LIST out all my monitors on my machine. I can also use mstsc /multimon as a command line to use multiple monitors.

MSTSC /l showing a list of my monitors
Repository: rust
Issue: Tracking Issue for `#[repr(align(...))]` on function items (fn_align)
Labels: T-lang,T-compiler,C-tracking-issue,A-rust-for-linux,F-fn_align,A-align

<!--
NOTE: For library features, please use the "Library Tracking Issue" template instead.

Thank you for creating a tracking issue! 📜 Tracking issues are for tracking a
feature from implementation to stabilisation. Make sure to include the relevant
RFC for the feature if it has one. Otherwise provide a short summary of the
feature and link any relevant PRs or issues, and remove any sections that are
not relevant to the feature.

Remember to add team labels to the tracking issue.
For a language team feature, this would e.g., be `T-lang`.
Such a feature should also be labeled with e.g., `F-my_feature`.
This label is used to associate issues (e.g., bugs and design questions) to the feature.
-->
This feature allows specifying an alignment for function items by adding the `#[repr(align(...))]` attribute to them.
The feature gate for the issue is `#![feature(fn_align)]`

### Example

```rust
#[repr(align(16))]
fn requires_alignment() {
    // ...
}
```

### Steps
<!--
Include each step required to complete the feature. Typically this is a PR
implementing a feature, followed by a PR that stabilises the feature. However
for larger features an implementation could be broken up into multiple PRs.
-->

- [X] Implementation (https://github.com/rust-lang/rust/pull/81234)
- [ ] Adjust documentation
- [ ] Stabilization PR
Repository: TypeScript
Issue: Unsupported expando pattern in commonjs prevents parent function from being called
Labels: Bug

# Bug Report

From npm@7, repros at least in 4.1 and 4.3-dev. It's likely to have been around since late 3.* _at least_

### 💻 Code

```js
// @checkjs: true
// @filename: mod1.js
module.exports.json = fetchJSON
function fetchJSON () {
}

module.exports.json.stream = fetchJSONStream
function fetchJSONStream () {
}

// @filename: test.js
const npmFetch = require('./mod1')
let u2 = npmFetch.json()
```

### 🙁 Actual behavior
Error: 'typeof json' has no call signatures.

BUT quick info for json is:

```
module json
(alias) function json(): void
import json
```

### 🙂 Expected behavior
no error and `u2: void`

Inlining `fetchJSON` to be `module.exports.json = function fetchJSON() { }` fixes the problem because it's correctly treated as a expando.
Repository: TypeScript
Issue: Rename refactor fails when renaming an object key to a string with a space in it
Labels: Bug,Domain: Refactorings

# Bug Report

Using "rename symbol" on a key of an object and renaming it to a name that has a space produces incorrect TypeScript code.

I'm sure this exists somewhere but I couldn't find it while searching. 

### 🔎 Search Terms

refactor, rename, object, key, space, string

### 🕗 Version & Regression Information

4.2.0

### ⏯ Playground Link

[Playground link with relevant code](https://www.typescriptlang.org/play?#code/FAGwpgLgBAHlC8UDewpqgMwPZYFxQEZgBfYYAYywDsBnLcAOhCwHMAKGB7LASiA)

### 💻 Code

```ts

let x = {
    foo: 1
}

console.log(x.foo)
```

### 🙁 Actual behavior

After using F2 in VSCode to rename `foo` to `foo bar`


```ts

let x = {
    foo bar: 1
}

console.log(x.foo bar)
```

### 🙂 Expected behavior

```ts
let x = {
    "foo bar": 1
}

console.log(x["foo bar"])
```
Repository: PowerToys
Issue: PT Run Plugin Referencing Wox.Infrastructure
Labels: Product-PowerToys Run,Area-Quality,Run-Plugin,Issue-Task

As @mykhailopylyp noted in this comment https://github.com/microsoft/PowerToys/pull/9538#discussion_r572783293
PT Run plugin are referencing `Wox.Infrastructure`.
`ISavable` and `PluginJsonStorage` used by plugins are in `Wox.Infrastructure`.
Let's discuss pros and cons of making plugins dependent only on `Wox.Plugin`.
Low priority! 😃
Repository: material-ui
Issue: Add multiple border radii to theme
Labels: design

In the default theme there is a shape property with a single borderRadius. Many many designs employ at least two different border radii, e.g. one for modals and one for buttons. A custom theme could certainly add a second property, but any component using it will break in any situation where the default theme is used.

- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.

## Summary 🔘

I can imagine various different implementations, but worth noting that [Material Design implies](https://material.io/design/shape/about-shape.html#shape-customization-tool) that there could be different radii for small, medium, and large components.

## Motivation 🐲

We need multiple border radii; currently we are solving this by having one in the theme and one as an independent constant. Considering adding the second one to the theme, but then doing a null check every time it's used. Not great options.
Repository: go
Issue: cmd/vet: printf analyzer cannot analyze anonymous functions
Labels: NeedsInvestigation,Analysis

<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.16 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ docker run --rm golang:1.16 go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/root/.cache/go-build"
GOENV="/root/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.16"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build813662227=/tmp/go-build -gno-record-gcc-switches"
GOROOT/bin/go version: go version go1.16 linux/amd64
GOROOT/bin/go tool compile -V: compile version go1.16
uname -sr: Linux 4.19.121-linuxkit
/lib/x86_64-linux-gnu/libc.so.6: GNU C Library (Debian GLIBC 2.28-10) stable release version 2.28.
</pre></details>

### What did you do?

Ran `go vet` on a package containing the following:

```go
package vetexample

import "fmt"

func BuggyCode() error {
	failf := func(format string, args ...interface{}) error {
		return fmt.Errorf(format, args)
	}
	return failf("%v")
}

```

### What did you expect to see?

`go vet` catches the mismatch between the format string and argument list in the `failf` call.

### What did you see instead?

The package passed vetting.

---

This pattern of wrapping a printf-family function in a closure can also be found in the Go sources.
https://github.com/golang/go/blob/2f0da6d9e29d9b9d5a4d10427ca9f71d12bbacc8/src/cmd/go/internal/modfetch/coderepo.go#L324-L332

While I would not expect `go vet` to be able to analyze in general whether a function value wraps (or is) a printf-family function, might it be viable to analyze the more limited case of a function-scoped local variable which is assigned a function literal value?