sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: material-ui
Issue: [Dialog] Remove `disableEscapeKeyDown` prop, in favor of using the `onClose` callback
Labels: discussion,breaking change,component: dialog

Is there any particular reason that the `disableBackdropClick` prop is deprecated on the [Dialog](https://github.com/mui-org/material-ui/tree/next/packages/material-ui/src/Dialog) component but the `disableEscapeKeyDown` prop is not?

I feel like they should either both be deprecated and handled the same way via the `handleClose` function, or neither should be deprecated.

Docs (v4.12.1) are currently showing:

![Screen Shot 2021-07-15 at 2 23 31 PM](https://user-images.githubusercontent.com/6536941/125838684-711e3aa3-a5a9-4349-bd74-e6b7ba944ea8.png)
Repository: PowerToys
Issue: [Settings] recap: Navigation items
Labels: Product-Settings,Area-User Interface

### Description of the new feature / enhancement

I commented something in Niels' issue (about new Windows 11 style for settings) that got me thinking. The most direct question was:

> Items are "hard-coded" alphabetically, but when "File Explorer" is translated, this breaks. Can this be done automatically, after translation/rendering?

Then I had the bigger question: WHY is it alphabetically? I mean, it's pretty neutral, but is this the only/best logic? For example: It just happens to be the case that File Explorer and Image Resizer are together, but I consider Power Rename an "Explorer-thingy" too. So, idea for new Settings: Can Image Resizer and Power Rename be considered sub-modules of File Explorer? They keep their own Page, just thinking about a Navigation hierarchy:
- File Explorer _(drop-down only, no Page bind to this item)_
  - plug-ins / add-ons
  - Image Resizer
  - Power Rename

Even bigger idea: ~If both Settings and OOBE are going to use the colored icons in the future,~ wouldn't it be **way** easier if both used the exact same source? Would solve/prevent pretty much all issues regarding sorting, translations, icons et cetera...

_Off-topic question: Why are FancyZones and PowerRename the only ones who do not have a `space` in their name? It feels inconsistent to the others._

### Scenario when this would be used?

- Updating styles, navigation
- Solve/prevent other issues

### Supporting information

![image](https://user-images.githubusercontent.com/65828559/125840853-ae60870a-5b3f-46ff-989b-b6a36635923c.png)
This is in 0.41.4
Repository: create-react-app
Issue: [Testing]: `npm test` invokes error : `too many open files, watch`
Labels: stale,needs triage,issue: bug report

I want to test my component using [Enzyme](https://enzymejs.github.io) and Jest but I got this error:

```
node:events:371
      throw er; // Unhandled 'error' event
      ^

Error: EMFILE: too many open files, watch
    at FSEvent.FSWatcher._handle.onchange (node:internal/fs/watchers:204:21)
Emitted 'error' event on FSWatcher instance at:
    at FSEvent.FSWatcher._handle.onchange (node:internal/fs/watchers:210:12) {
  errno: -24,
  syscall: 'watch',
  code: 'EMFILE',
  filename: null
}
```

### Package.json

```json
{
   "name": "react-toast",
   "version": "0.1.0",
   "private": true,
   "dependencies": {
      "@testing-library/jest-dom": "^5.14.1",
      "@testing-library/react": "^11.2.7",
      "@testing-library/user-event": "^12.8.3",
      "react": "^17.0.2",
      "react-dom": "^17.0.2",
      "react-icons": "^4.2.0",
      "styled-components": "^5.3.0",
      "web-vitals": "^1.1.2"
   },
   "devDependencies": {
      "enzyme": "^3.11.0",
      "enzyme-adapter-react-16": "^1.15.6",
      "react-scripts": "^1.1.5"
   },
   "scripts": {
      "start": "react-scripts start",
      "build": "react-scripts build",
      "test": "react-scripts test",
      "eject": "react-scripts eject"
   },
   "eslintConfig": {
      "extends": [
         "react-app",
         "react-app/jest"
      ]
   },
   "browserslist": {
      "production": [
         ">0.2%",
         "not dead",
         "not op_mini all"
      ],
      "development": [
         "last 1 chrome version",
         "last 1 firefox version",
         "last 1 safari version"
      ]
   }
}

```

### jest.config.json

```json
{
   "jest": {
      "setupFilesAfterEnv": ["<rootDir>src/setupTests.js"]
   }
}
```
### setupTests.js

```javascript

// jest-dom adds custom jest matchers for asserting on DOM nodes.
// allows you to do things like:
// expect(element).toHaveTextContent(/react/i)
// learn more: https://github.com/testing-library/jest-dom
import '../jest.config.json';

```


### Command test

```
npm test 

```
Repository: flutter
Issue: Building/running with a local profile/release engine should automatically select profile/release mode unless otherwise specified.
Labels: tool,a: quality,P3,team-tool,triaged-tool

Today you need to run ` flutter run -d windows --profile --local-engine=host_profile`. You should be able to type ` flutter run -d windows  --local-engine=host_profile` and have it just work (tm) instead.

Allow manually overriding the mode to support folks doing weird stuff of course
Repository: flutter
Issue: [ReorderableListView] Problem after upgrade Flutter 2.2.3
Labels: c: regression,framework,f: material design,f: scrolling,has reproducible steps,P2,found in release: 2.2,found in release: 2.4,team-design,triaged-design

I have now completed the migration and updated to the latest version of flutter 2.2.3 (before I had 2).
After this update I noticed that while before the ReorderableListView widget worked as I expected, that is, if I dragged an element out of the reorderable list space it was hidden, now if I drag it, it remains visible and this is not nice to see. I tried masking with clipRect etc. but when with the longPress the element becomes draggable it is no longer possible to mask it and can be dragged to the top of the screen.
In your opinion it is a bag or there may be a way to solve it.
Thanks

<img width="375" alt="Schermata 2021-07-05 alle 11 27 59" src="https://user-images.githubusercontent.com/46923349/125849203-5dfeda54-c7b9-4421-be6d-f7e5a61517c8.png">
Repository: go
Issue: gccgo: issue19182 test hangs with large initial CPU count
Labels: NeedsInvestigation

<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ gccgo -v
Using built-in specs.
COLLECT_GCC=gccgo
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/11/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-redhat-linux
Configured with: ../configure --enable-bootstrap --enable-languages=c,c++,fortran,objc,obj-c++,ada,go,d,lto --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-shared --enable-threads=posix --enable-checking=release --enable-multilib --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-gnu-unique-object --enable-linker-build-id --with-gcc-major-version-only --with-linker-hash-style=gnu --enable-plugin --enable-initfini-array --with-isl=/builddir/build/BUILD/gcc-11.1.1-20210531/obj-x86_64-redhat-linux/isl-install --enable-offload-targets=nvptx-none --without-cuda-driver --enable-gnu-indirect-function --enable-cet --with-tune=generic --with-arch_32=i686 --build=x86_64-redhat-linux
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 11.1.1 20210531 (Red Hat 11.1.1-3) (GCC) 
</pre>

or ppc64le
<pre>
Using built-in specs.
COLLECT_GCC=/opt/at14.0/bin/gccgo
COLLECT_LTO_WRAPPER=/opt/at14.0/libexec/gcc/powerpc64le-linux-gnu/10.3.1/lto-wrapper
Target: powerpc64le-linux-gnu
Configured with: /build/at14.0_RHEL8_ppc64le-ppc64le/103/at14.0-3.redhat-8_ppc64le_ppc64le/sources/gcc/configure --build=powerpc64le-linux-gnu --host=powerpc64le-linux-gnu --target=powerpc64le-linux-gnu --with-cpu=default64 --prefix=/opt/at14.0 --with-long-double-128 --enable-secureplt --disable-multilib --with-advance-toolchain=at14.0 --with-glibc-version=2.32 --with-local-prefix=/opt/at14.0 --enable-threads=posix --enable-languages=c,c++,fortran,go --enable-__cxa_atexit --enable-shared --enable-checking=release --enable-lto --enable-gnu-indirect-function --enable-initfini-array --enable-linker-build-id --with-system-zlib --with-gmp-include=/opt/at14.0/include --with-gmp-lib=/opt/at14.0/lib64 --with-mpfr-include=/opt/at14.0/include --with-mpfr-lib=/opt/at14.0/lib64 --with-mpc-include=/opt/at14.0/include --with-mpc-lib=/opt/at14.0/lib64 --without-ppl --without-cloog --without-libelf --with-host-libstdcxx='-L/opt/at14.0/lib64 -lstdc++ -lsupc++ -lgmp -lgmpxx -lm' --with-cpu=power8 --with-tune=power8
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 10.3.1 20210412 (Advance-Toolchain 14.0-3) [9c2461a2d5de] (GCC) 
</pre>

### What operating system and processor architecture are you using (`go env`)?

ppc64le and amd64.

### What did you do?
`gccgo -o issue19182 issue19182.go`
`GOMAXPROCS=400 ./issue19182`

### What did you expect to see?

Program termination

### What did you see instead?

Program does not terminate.
Repository: neovim
Issue: Allow vim.notify to take a table of notifications
Labels: enhancement,api,lua

All that would change is that usage could look something like this:
```lua
vim.notify({
    { "some message", log_level, opts }
    { "another message", a_different_log_level, other_opts }
}
```

This stems from a discussion we are having here: https://github.com/nvim-lua/plenary.nvim/pull/188. The general idea is that we split notifications into two components. For lack of a better term call them a "provider" and a "consumer." What would happen is that notifications are sent through `vim.notify`, the same way it is used right now, but then users could override that with a consumer to render notifications as they'd like. For more details see the discussion linked above.

@clason correct me if I've described anything inaccurately :)
CC @teto
Repository: flutter
Issue: flutter drive not stop in linux/docker
Labels: tool,t: flutter driver,P2,team-tool,triaged-tool

## Steps to Reproduce

Im use `cirrusci/flutter:stable` docker image for CI.
In this package im installing chrome and chrome-driver like this:

```console 
  script:
    - apt-get update
    - apt-get install -y wget gnupg gpg-agent
    - wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | apt-key add -
    - sh -c 'echo "deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main" >> /etc/apt/sources.list.d/google.list'
    - apt-get update
    - apt-get install -y google-chrome-stable fonts-ipafont-gothic fonts-wqy-zenhei fonts-thai-tlwg fonts-kacst fonts-freefont-ttf libxss1  --no-install-recommends
    - wget https://chromedriver.storage.googleapis.com/91.0.4472.101/chromedriver_linux64.zip
    - unzip chromedriver_linux64.zip
    - cp chromedriver /usr/local/bin/
```

Then, i run `flutter drive`, like this: 

```console 
chromedriver --port=4444 & flutter drive --driver=test_driver/integration_test.dart  --target=integration_test/login_text_test.dart -d web-server
```

Then tests not finish and the last massage is `Application finished.`, no errors, no info about what heppens.

Also I tried to install chrome-driver with [web_installers](https://github.com/flutter/web_installers), with same result.


On my local machine (masOS)  integrations test works good.

---

Update by @christopherfujino 

Minimal repro repo [here](https://github.com/karabanovbs/integration_test_example)
Repository: go
Issue: x/website/tour: installing @latest gets older version
Labels: NeedsInvestigation,modules

A reasonable way to install the latest version of the `tour` binary from its latest location is by using `go install`:

```
go install golang.org/x/website/tour@latest
```

However, doing so currently gets a slightly older version of the tour, before the x/website/tour nested module was merged into the x/website module in [CL 323897](https://golang.org/cl/323897).

<details><br>

```
$ go install golang.org/x/website/tour@latest
go: downloading golang.org/x/website v0.0.0-20210715154925-11adafea15f8
go: downloading golang.org/x/website/tour v0.0.0-20210616181959-e0d934b43647

$ go version -m $(which tour) | head -n 3
/Users/dmitshur/go/bin/tour: go1.16.6
	path	golang.org/x/website/tour
	mod	golang.org/x/website/tour	v0.0.0-20210616181959-e0d934b43647	h1:IFK+1/z6bm51XIJD3ksijCgwsZXJJxliWFiIYVEG6F8=
```

Note that module path is `golang.org/x/website/tour` and version is a month-old `v0.0.0-20210616181959-e0d934b43647`, rather than the latest commit on `master` branch:

```
$ go install golang.org/x/website/tour@HEAD
$ go version -m $(which tour) | head -n 3  
/Users/dmitshur/go/bin/tour: go1.16.6
	path	golang.org/x/website/tour
	mod	golang.org/x/website	v0.0.0-20210715154925-11adafea15f8	h1:xRFLa1Fo4NnOCH0yKaPu6H36MmmA/GJEZyTEO+HOWlI=
```

</details>

A workaround is to specify `@HEAD` or the exact version of tour one wants.
Repository: terminal
Issue: Leverage the Windows Info Protection APIs to unblock enterprise clipboard contents
Labels: Issue-Feature,Area-UserInterface,Product-Meta,Priority-3

We should be able to afford terminal the ability to read clipboard contents as [documented in the Windows Info Protection docs](https://docs.microsoft.com/en-us/previous-versions/windows/desktop/EDP/wip-developer-guide#read-data-from-the-clipboard).

However: we may not want to blindly do so. Terminal should not be able to enter/exit an "enterprise" context, and we have no control over what the application on the receiving end does with the pasted content. We can neither vouch for nor evaluate the veracity of those applications.
Repository: pytorch
Issue: `make_tensor` tracking issue
Labels: triaged,module: testing,tracker

This issue tracks progress and features related to `make_tensor`. This is in the direction of exposing it to the users, and hence a tracker to invite discussions/inputs as well as document progress.

## Features Tracker

* [ ] Fix inputs `low/high` given: don't clamp to default values when given valid values. (being pursued in #61108)
* [ ] Investigate tensor generation strategy. (being pursued in #61108)
* [ ] Generic `exclude_values` and `include_values` for tensor generation.
* [ ] Add `include_percent` like argument to populate the output with given percent of `include_values` from the 3rd task.
* [ ] Add `include_lhs` (default True) and `include_rhs` (default False) to the function.
* [x] Document `make_tensor`

## Description

`make_tensor` is planned (and expected) to go public to the user API in coming releases. The idea behind `make_tensor` is to allow generation of tensors with random (currently: uniformly distributed) values for given `dtype` and `device`. Keeping the user's requirements in mind as well as the extensive use of `make_tensor` in the PyTorch test suite, this issue is supposed to document the progress as well as invite discussions on the features listed above.

cc: @mruberry @pmeier
Repository: create-react-app
Issue: [v5] Use webpack 5 asset modules also for svgr
Labels: issue: proposal,tag: enhancement,needs triage

### Is your proposal related to a problem?

This issue is related to Webpack 5 and the svg loader part of the configuration. Webpack 5 now use [Asset modules](https://webpack.js.org/guides/asset-modules/) to replace raw/url/file loaders.

Most of file loading is already converted into asset modules in the new CRA webpack 5 config but theres on outstanding regarding loading svg.

### Describe the solution you'd like

When converting to webpack 5 I didn't manage to convert the svgr loader setup to be using asset modules, for now it's using file-loader still. It would be great if it could be converted into the asset module pattern, ideally by setting the asset type instead of using other loaders to be webpack 5 native.

### Describe alternatives you've considered

@marella mentioned that he did a [new-url-loader](https://github.com/marella/new-url-loader#readme) as an alternative [see comment for more details](https://github.com/facebook/create-react-app/pull/11201#discussion_r670448728)

### Additional context

Reading the webpack 5 documentation I would imagine that something like this would have worked:
*(Also note that we might have to think about [url assets](https://webpack.js.org/guides/asset-modules/#url-assets) maybe thats out of scope for now?)*

```js
  test: /\.svg$/,
  use: [
    {
      loader: '@svgr/webpack',
      options: {
        prettier: false,
        svgo: false,
        svgoConfig: {
          plugins: [{ removeViewBox: false }],
        },
        titleProp: true,
        ref: true,
      },
    },
    type: 'asset/resource',
    generator: {
      filename: 'static/media/[name].[hash].[ext]',
    }
/* replacing:
    {
      loader: 'file-loader',
      options: {
        name: 'static/media/[name].[hash].[ext]',
      },
    },
*/
  ],
```
Repository: go
Issue: proxy.golang.org: support git-lfs
Labels: NeedsInvestigation,FeatureRequest,proxy.golang.org

The Google-hosted `proxy.golang.org` does not smudge git-lfs pointer files in public repos.  This results in broken builds when modules include binary syso files that are hosted under git-lfs.  (The linker sees a text file instead of the object file, ignores it, then explodes with a lot of missing symbol errors which isn't very intuitive.)

While it might be unreasonable to expect every git extension be supported on `proxy.golang.org`, git-lfs is quite common: it's supported by many of the major git hosts (e.g. GitHub, GitLab, Bitbucket, Azure Repos) with many others having a pending feature-request for it.

## Workarounds

1. Use `GOPRIVATE` for all packages that need git-lfs.  This can result in a complex configuration environment for the developer who now needs to track this across possibly many dependencies, some of which may be transitory.

1. The nuclear option: turn off the proxy with `GOPROXY=direct`.

1. Change all modules to avoid git-lfs and commit all binary syso files directly into each repo.

None of these options are great...

## Similar issues

Issue #41708 talks about a mod checksum mismatch between proxy and direct.  One solution is to ignore the smudge and get matching checksums, which can work in that case because the git-lfs file(s) are inconsequential to the build.  That approach doesn't work in the scenario described above.

The following issues are related to git-lfs, but aren't as relevant:

* #38941: This is checksum mismatch; but for a private repo (not using `proxy.golang.org`) and where skipping the smudge worked for them.
* #29987: OP wanted to exclude large git-lfs files in a repo that were not consequential for a build, so they put them in a git submodule instead.
* #39720: `git archive` didn't smudge git-lfs files using `go get`.  Worked when I tried the `git archive` it on a GitHub repo with git-lfs files... perhaps they have used an old git version?
Repository: godot
Issue: Project Settings are ordered differently depending on whether the Advanced Settings toggle is enabled
Labels: enhancement,topic:editor,usability

### Godot version

v4.0.dev.custom_build [072777df6]

### System information

Windows 10, Vulkan, Nvidia Quadro K2000 461.92

### Issue description

In project settings, when switching Advanced Settings on and off, you can notice that the ordering of the settings is different between the two.. Layer names for example, are practically at the bottom with the AS on (Below rendering), but with AS off, Layer names are higher up (above rendering)

### Steps to reproduce

Go to Project settings and switch between Advanced Settings On and Off, and observe how the category placements are different

### Minimal reproduction project

_No response_
Repository: pytorch
Issue: How to save tensors on mobile (lite interpreter)?
Labels: oncall: mobile

## Issue description

Based on the discussion in https://github.com/pytorch/pytorch/pull/30108 it's clear that `pickle_save` is not supported on mobile, because `/csrc/jit/serialization/export.cpp` is not included when building for lite interpreter; producing the following runtime error:

```c++
#else
  AT_ERROR(
      "pickle_save not supported on mobile "
      "(see https://github.com/pytorch/pytorch/pull/30108)");
#endif
```
 
For loading there's an option of using `torch::jit::_load_for_mobile`. 

**However, are there any methods, or alternative approaches, of serialising and saving `c10::IValue` objects on the mobile device?**

---

Mobile code compiled with libraries at `master: 5c1505076bfa764088e2ccef19d7f18336084530`
Repository: TypeScript
Issue: Allow to Override Import Paths For Auto-Import
Labels: Suggestion,Awaiting More Feedback

`IDisposable`, `Emitter` and `Event` are very common types in the VS Code codebase.
Unfortunately, you have to be very careful when importing them through autocomplete.
Even worse, sometimes all the places to import from are suggested except the correct one.

In 99% of cases, we are importing `IDisposable` from `vs/base/common/lifecycle`. As you can see here, TypeScripts suggests all places except the right one:

![image](https://user-images.githubusercontent.com/2931520/125929194-90382bb5-db2e-4bbc-b25c-b6c3900c4a37.png)

It would be very practical if one could override where to import unresolved symbols from.
E.g.
```json
"typescript.importFromOverrides": {
  "src/vs/editor/**": {
    "IDisposable": "vs/base/common/lifecycle",
    "Event": "vs/base/common/events"
  }
}
```

Alternatively, TypeScript could figure out where the Symbol has been imported from in adjacent files.
Maybe a disallow-list would also make sense (never import `IDisposable` from `node-pty`, or never import anything from `vs/workbench/workbench.web.api`).

This is now the second codebase where I ran into the permanent problem of importing a common symbol from a wrong module, which makes me believe this is a common problem.
I run into this problem one to ten times per day.

Here is another example:
![image](https://user-images.githubusercontent.com/2931520/125940758-328dd9d5-09c0-49aa-8c7b-6bdae92e9bf1.png)
We never want to import from `vscode`.
Being able to customize the preferred import would be a huge deal (especially for the quickfix "add all missing imports").
Repository: rust
Issue: Not detailed error message when trying to move self-referential vector
Labels: A-diagnostics,A-borrow-checker,T-compiler,D-newcomer-roadblock,D-terse

Given the following code: https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=30b9592e45402507ee43723a5ddd6146

```rust
enum Foo<'a>{Bar, Baz(&'a Foo<'a>)}

fn main() {
    let mut v = vec![Foo::Bar, Foo::Bar];
    {
        let r = &mut v[..];
        match r.split_first_mut() {
            None => panic!("Impossible"),
            Some((head, tail)) => {
                tail[0] = Foo::Baz(head);
            },
        };
    };
    let v2 = v;
}
```

The current output is:

```
warning: unused variable: `v2`
  --> src/lib.rs:14:9
   |
14 |     let v2 = v;
   |         ^^ help: if this is intentional, prefix it with an underscore: `_v2`
   |
   = note: `#[warn(unused_variables)]` on by default

error[E0505]: cannot move out of `v` because it is borrowed
  --> src/lib.rs:14:14
   |
6  |         let r = &mut v[..];
   |                      - borrow of `v` occurs here
...
14 |     let v2 = v;
   |              ^
   |              |
   |              move out of `v` occurs here
   |              borrow later used here
```

I used 1.55.0-nightly, Rust 2018.

This code, of course, should not work. But error message is too small. The error says "borrow later used here", but it doesn't explain how the borrow used there.

The message surely doesn't print all context that caused the error. If I comment line 10, the error will disappear. But the original error doesn't mention line 10!