sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: material-ui
Issue: [link] Link component adds additional class with custom styles without any reason
Labels: component: link,status: expected behavior

### Current behavior 😯

Link component adds a class named css-XXXXXXX-MuiTypography-root-MuiLink-root to "a" tag with custom styles, this breaks all my markup because it has "margin: 0" rule and it always comes last and rewrites all other styles. The documentation doesn't mention this behavior.

```html
<a class="MuiTypography-root MuiTypography-inherit MuiLink-root MuiLink-underlineAlways css-1iwtne7-MuiTypography-root-MuiLink-root" href="/">Link</a>
```

### Expected behavior 🤔

A tag without additional class
```html
<a class="MuiTypography-root MuiTypography-inherit MuiLink-root MuiLink-underlineAlways" href="/">Link</a>
```

### Steps to reproduce 🕹

Steps:

1. Create new project
2. Add Link component

https://codesandbox.io/s/react-mui-forked-0sewm


### Context 🔦

_No response_

### Your environment 🌎

<details>
  <summary>`npx @mui/envinfo`</summary>

```
  System:
    OS: Linux 5.13 Ubuntu 21.10 21.10 (Impish Indri)
  Binaries:
    Node: 16.13.1 - /usr/bin/node
    Yarn: 1.22.15 - /usr/bin/yarn
    npm: 8.1.2 - /usr/bin/npm
  Browsers:
    Chrome: 96.0.4664.93
    Firefox: 94.0
  npmPackages:
    @emotion/react: ^11.7.0 => 11.7.0 
    @emotion/styled: ^11.6.0 => 11.6.0 
    @mui/base:  5.0.0-alpha.59 
    @mui/material: ^5.2.3 => 5.2.3 
    @mui/private-theming:  5.2.3 
    @mui/styled-engine:  5.2.0 
    @mui/system:  5.2.3 
    @mui/types:  7.1.0 
    @mui/utils:  5.2.3 
    @types/react: ^17.0.0 => 17.0.37 
    react: ^17.0.2 => 17.0.2 
    react-dom: ^17.0.2 => 17.0.2 
    typescript: ^4.1.2 => 4.5.3 
```
</details>
Repository: PowerToys
Issue: [Power Rename] Predefined names
Labels: Idea-Enhancement,Product-PowerRename

### Description of the new feature / enhancement

Maybe we could have a list of most used names or predefined list of names. I rename a lot of files, but use the same names, repetitive process. Or perhaps we could even have a context menu with a predefined list, so we would just right-click on the file and rename it automatically.

### Scenario when this would be used?

For stuff that repeats a lot, renaming files and using same names. 

### Supporting information

_No response_
Repository: pytorch
Issue: JIT: Support for `torch.autograd.functional.jacobian` in TorchScript
Labels: oncall: jit,Stale

### 🚀 The feature, motivation and pitch

As I've mentioned in [previous issues ](https://github.com/pytorch/pytorch/issues/68621#issuecomment-978140881) the forward pass of our scientific models includes using the autograd engine to compute the gradient of a predicted quantity. This is happily well supported in TorchScript.

We now want to be able to deploy a model whose forward pass involves the _Jacobian_ of a predicted quality in the forward pass. This does not appear to be supported:
```
import torch

@torch.jit.script
def f(x):
    return (x + x[..., ::-1]).square()

@torch.jit.script
def g(x):
   return torch.autograd.functional.jacobian(
       func=f,
       inputs=(x,)
   )

g(torch.randn(4))
```
gives various TorchScript language errors.

### Alternatives

One option is to explicitly, in TorchScript, call `torch.autograd.grad` _N_ times (one for each entry in the output tensor) and then reassemble the Jacobian using `torch.cat`. This would only involve calls already supported in TorchScript and some simple loops, but has the worse-case performance of calling the autograd engine _N_ independent times.

Much preferable would be some kind of interface to PyTorch's own implementation that would allow taking advantage of `vmap` and `vectorize=True` for the Jacobian.

### Additional context

_No response_
Repository: pytorch
Issue: Add ability to ignore arguments/outputs in `torch.autograd.functional.jacobian`
Labels: module: autograd,triaged,enhancement,Stale

### 🚀 The feature, motivation and pitch

Currently, [`torch.autograd.functional.jacobian`](https://pytorch.org/docs/stable/generated/torch.autograd.functional.jacobian.html) takes the Jacobian of (each of) the outputs with regard to (each of) the inputs. 

Sometimes, however, we only want to compute the Jacobian of _some_ output with regard to _some_ inputs while still keeping the other outputs of the function, and also providing other inputs.

This could look like some kind of optional `which_inputs`/`which_outputs` parameters, either as lists of indexes into the input/output tuples or as boolean masks of them.

### Alternatives

In pure Python, this can be achieved through the (rather unpleasant) use of closures:
```python
all_inputs = [some, tensor, tuple]
all_outputs = None

def wrapper(inp1):
    nonlocal all_inputs, all_outputs
    all_inputs[1] = inp1
    all_outputs = thefunc(*all_inputs)
    return all_outputs[0]

torch.autograd.functional.jacobian(
    func=wrapper
    inputs=(all_inputs[1],)
)
```

But this has no hope of being TorchScript compatible (see https://github.com/pytorch/pytorch/issues/69741) and is also pretty ugly.

### Additional context

_No response_

cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7
Repository: rust
Issue: Allowing/denying rustc internal lints silently fails
Labels: A-lints,T-compiler,C-bug

I would think it'd give a feature-gate error.

```rust
#![deny(rustc::default_hash_types)]

type Foo = std::collections::HashSet<()>;
```

```
   Compiling playground v0.0.1 (/playground)
warning: type alias is never used: `Foo`
 --> src/lib.rs:3:1
  |
3 | type Foo = std::collections::HashSet<()>;
  | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  |
  = note: `#[warn(dead_code)]` on by default

warning: `playground` (lib) generated 1 warning
    Finished dev [unoptimized + debuginfo] target(s) in 2.21s
```
Repository: deno
Issue: Proposal: `Deno.spawnDeno`
Labels: suggestion

Relies on #11618.

This proposal proposes a function that would allow to spawn a "sandboxed" deno subprocess. This function would not require the `allow-run` function. Permissions would work the same way as they do for WebWorkers. This would be equivalent to node's `child_process.fork`, while keeping Deno's security.

The first pass of this proposal would only allow for `deno run` to be spawned, to keep things simple. This later on can be expanded to allow spawning various other subcommands.

```ts
interface SpawnDenoOptions {
  /** Arguments that will be passed to the script. */
  scriptArgs?: string[],
  permissions?: "inherit" | "none" | {
    env?: "inherit" | boolean | string[];
    hrtime?: "inherit" | boolean;
    net?: "inherit" | boolean | string[];
    ffi?: "inherit" | boolean | Array<string | URL>;
    read?: "inherit" | boolean | Array<string | URL>;
    run?: "inherit" | boolean | Array<string | URL>;
    write?: "inherit" | boolean | Array<string | URL>;
  },
  compat?: boolean,
  /** Requires the unstable flag to be set to use */
  unstable?: boolean,
  logLevel?: "debug" | "info",
  quiet?: boolean,
  inheritLocation?: boolean,
  noRemote?: boolean,
  cachedOnly?: boolean,
  noCheck?: boolean,
  seed?: number,
  watch?: boolean,
}

function spawnDeno(script: string | URL, options?: SpawnDenoOptions): Command;
```

Currently, with this set of options, the permissions can be escalated beyond what the parent process has access to with `Deno.permissions.request`, so i propose to add a `no-permission-request` flag, which would disallow the usage of `Deno.permissions.request`.
Repository: flutter
Issue: Linux: respect system preferences for overlay scrollbar toggle
Labels: c: new feature,f: scrolling,f: inspector,platform-linux,c: proposal,a: desktop,P3,team-linux,triaged-linux

<!-- Thank you for using Flutter!

     If you are looking for support, please check out our documentation
     or consider asking a question on Stack Overflow:
      * https://flutter.dev/
      * https://api.flutter.dev/
      * https://stackoverflow.com/questions/tagged/flutter?sort=frequent

     If you have found a bug or if our documentation doesn't have an answer
     to what you're looking for, then fill out the template below. Please read
     our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports
-->

## Use case

I run `gsettings set org.gnome.desktop.interface overlay-scrolling false` to make all scrollbars visible and full-width in GTK3/GTK4 apps. Flutter uses GTK for some platform integration on Linux, but that doesn't currently extend to reading scrollbar preferences.

## Proposal

Flutter should read this gsettings preference and make scrollbars visible (instead of auto-hiding) if the pref is set to "false".
Repository: vscode
Issue: Strange things happen when using the keyboard button `Page Up` / `Page Down` in the search box
Labels: bug,editor-find

<!-- ⚠️⚠️ 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 - I test on fresh and clean portable installation

<!-- 🪓 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. -->
**Env:**
```
Version: 1.63.0
Commit: 7db1a2b88f7557e0a43fec75b6ba7e50b3e9f77e
Date: 2021-12-07T06:26:56.179Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.19043
```

**Issue description:**

1. When I type something in the search box and then use the `Page Up` key on my keyboard, the tabs get smaller
2. As i continue to press the `Page Up` and `Page Down` buttons, the editor begins to scroll

**Steps to Reproduce:**
![vsvsvs](https://user-images.githubusercontent.com/30685349/145528455-c714f9bb-7a03-4b92-aa0f-c9c799a2228a.gif)
Repository: next.js
Issue: Stacktrace using typescript aren't using sourcemaps ? (client-side: in the browser)
Labels: bug,Webpack

### What version of Next.js are you using?

12.0.4

### What version of Node.js are you using?

v16.13.0

### What browser are you using?

Chrome

### What operating system are you using?

macOS

### How are you deploying your application?

none

### Describe the Bug

Hi! After a while searching through nextjs documentation and google I still have trouble configuring sourcemap with stacktraces in typescript.

Here is a video, as you can see I can dive into a console.log entry and the sourcemap are used, however with stacktrace this is not the case:

https://youtu.be/REL19Hz246I

### Expected Behavior

The stacktrace must use correctly the sourcemaps

### To Reproduce

https://codesandbox.io/s/funny-star-d4yv1?file=/src/pages/index.tsx

Here in the console you can see that there is an error, but the line didn't matches at all, the error tell us that there is a problem  at MyApp (webpack-internal:///./src/pages/_app.tsx:42:27) but there isn't a line 42 in the _app.tsx ...
Repository: create-react-app
Issue: Creating a new app is broken with node 17 because of postcss version
Labels: needs triage,issue: bug report

### Describe the bug

After creating a new app with `create-react-app` it won't start:

```
yarn run v1.22.17
$ react-scripts start
node:internal/modules/cjs/loader:488
      throw e;
      ^

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './lib/tokenize' is not defined by "exports" in /home/pawel/dev/baz/node_modules/postcss-safe-parser/node_modules/postcss/package.json
    at new NodeError (node:internal/errors:371:5)
    at throwExportsNotFound (node:internal/modules/esm/resolve:429:9)
    at packageExportsResolve (node:internal/modules/esm/resolve:683:3)
    at resolveExports (node:internal/modules/cjs/loader:482:36)
    at Function.Module._findPath (node:internal/modules/cjs/loader:522:31)
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:919:27)
    at Function.Module._load (node:internal/modules/cjs/loader:778:27)
    at Module.require (node:internal/modules/cjs/loader:999:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at Object.<anonymous> (/home/pawel/dev/baz/node_modules/postcss-safe-parser/lib/safe-parser.js:1:17) {
  code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
}

Node.js v17.1.0
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
```
It seems that the version of `postcss-safe-parser` used by `create-react-app` is not working with node 17: https://github.com/postcss/postcss-safe-parser/issues/29

### Steps to reproduce


1. Install node 17
2. Create a new app with `create-react-app foo`
3. `cd foo`
4. `yarn start` or `npm start`
5. The app won't start, the error above is the reason
Repository: pytorch
Issue: last_epoch parameter of CyclicLR and OneCycleLR is not the number of epochs
Labels: module: optimizer,triaged,Stale,module: LrScheduler

From the [docs](https://pytorch.org/docs/stable/generated/torch.optim.lr_scheduler.CyclicLR.html#torch.optim.lr_scheduler.CyclicLR), `last_epoch` in `CyclicLR` and `OneCycleLR` corresponds to the number of batches (or the number of steps / updates), not the number of epoch:


> last_epoch (int) – The index of the last batch. This parameter is used when resuming a training job. Since step() should be invoked after each batch instead of after each epoch, this number represents the total number of batches computed, not the total number of epochs computed. When last_epoch=-1, the schedule is started from the beginning. Default: -1


A lot of the other scheduler also accept a `last_epoch` parameter, e.g. [StepLR](https://pytorch.org/docs/stable/generated/torch.optim.lr_scheduler.StepLR.html#torch.optim.lr_scheduler.StepLR). According to their docs, `last_epoch` is indeed the number of epochs:

> last_epoch (int) – The index of last epoch. Default: -1.


In the original PR for `CyclicLR` https://github.com/pytorch/pytorch/pull/2016, this parameter was named `last_batch_idx`, which seems more descriptive and consistent with its doc description.


Is there a specific reason why this ended up being `last_epoch`? If not, should we consider deprecate this parameter and rename it to `last_batch_idx` instead?

cc @vincentqb @jbschlosser @albanD
Repository: flutter
Issue: Add the ability to toggle directionality from the terminal + IDEs in debug mode
Labels: c: new feature,framework,c: proposal,d: devtools,P3,team-tool,triaged-tool

This was requested by @lukepighetti at https://github.com/Dart-Code/Dart-Code/issues/3720. It would be useful to be able to toggle directionality during debugging without needing to modify the code.

I think it would require a VM Service to toggle this (as well as the ability for it to be overridden), similar to how the debug banner works.
Repository: pytorch
Issue: Introduction of nn.LazyRNNs
Labels: module: nn,module: rnn,triaged,enhancement,Stale

### 🚀 The feature, motivation and pitch

`nn.Lazy*` modules assist in making model design more efficient when experimenting with various feature vector sizes within different blocks of a model as it avoids the need to pre-calculate and hardcode values such as, for example, `nn.Linear() `that is after a convolutional block. 

It would further increase the ease of experimentation if there were also a `nn.Lazy` implementation of the RNNs as these layers are also common within the hidden sections of a model and whose input relies on the output shape of an earlier layer.  

This would allow easier experimentation with feature vector sizes and hyperparameter tuning without the need to constantly adjust code within a model.



### Alternatives

_No response_

### Additional context

_No response_

cc @albanD @mruberry @jbschlosser @walterddr @kshitij12345 @zou3519
Repository: pytorch
Issue: [Feature request] nn.Model API: Standard model interface
Labels: module: nn,triaged,needs research

### 🚀 The feature, motivation and pitch

Feature: common model interface intended for adoption by PyTorch frameworks to improve their interoperability.

Motivation: There are several PyTorch libraries and frameworks, even within the same field (e.g., machine translation). Usually, each framework implements its own model abstractions. Interoperability, while possible, is many times painful. Users have to write ad hoc conversion scripts or wrappers. PyTorch hub is not compatible out of the box with for instance Huggingface hub.

Cons: It's difficult to define a general enough interface across domains, etc. Still, it could be worth exploring. Almost all frameworks (and even users) end up implementing extremely similar (but incompatible) methods.

Pitch: Define a common model interface with the bare minimum functionality intended to be adopted by other PyTorch frameworks and users.

It could look like:

```
class nn.Model(nn.Module):

    def save(self, path):
         # Save checkpoint. Handles:
         a) saving the weights themselves, even in distributed scenarios (e.g., tensor parallel)
         b) saving the hyperparameters and auxiliary objects required by the model.
    
    def load(self, path):
        # Reverse of save().

    def encode(self, x):
        # Transforms raw data (strings, PIL images....) into tensors or containers (tuples, dicts...)
        # of tensors.
        # For instance, tokenizes text or normalizes images.
  
    def decode(self, x):
        # Reverse of encode().

    def extract_features(self, *args, **kwargs):
       # Interface to return features. 
       # See https://github.com/pytorch/fairseq/blob/main/fairseq/models/fairseq_model.py#L95
       # https://github.com/rwightman/pytorch-image-models/blob/master/timm/models/vision_transformer.py#L343
       # https://github.com/facebookresearch/ClassyVision/blob/main/classy_vision/models/classy_model.py#L284

    @property
    def shapes_in(self):
        # Returns set of accepted tensor shapes in forward().
        # See https://github.com/facebookresearch/ClassyVision/blob/main/classy_vision/models/classy_model.py#L409
    
    @property
    def shapes_out(self):
        # Returns set of return tensor shapes in forward().
        # See https://github.com/facebookresearch/ClassyVision/blob/main/classy_vision/models/classy_model.py#L409


     
```

### Alternatives

Write ad hoc conversion scripts (e.g., https://github.com/huggingface/transformers/blob/master/src/transformers/models/bart/convert_bart_original_pytorch_checkpoint_to_pytorch.py) or wrappers (https://github.com/pytorch/fairseq/blob/main/fairseq/models/huggingface/hf_gpt2.py).

### Additional context

_No response_

cc @albanD @mruberry @jbschlosser @walterddr @kshitij12345
Repository: material-ui
Issue: [ButtonBase] Keyboard triggered onClick on non-button element does not bubble
Labels: bug 🐛,component: ButtonBase

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯

When a Menu has an onClick prop, clicking on a nested MenuItem triggers the onClick, but pressing spacebar or enter while a nested MenuItem is focused does not.

### Expected behavior 🤔

When a Menu has an onClick prop, clicking on a nested MenuItem triggers the onClick, and so does pressing spacebar or enter while a nested MenuItem is focused

### Steps to reproduce 🕹

https://codesandbox.io/s/basicmenu-material-demo-forked-34vqi?file=/demo.js:849-866
Steps:

1. Click on the menu
2. Click on a button - notice that "clicked menu" is logged to the console
3. Click on the menu
4. Navigate to a button using the mouse
5. Press spacebar - notice that "clicked menu" is not logged to the console


### Context 🔦

I was trying to create a custom ActionMenu component that by default closed whenever any buttons inside of it were clicked because I didn't want to have to call handleClose from the click handler of every single menu item.

### Your environment 🌎

_No response_
Repository: go
Issue: cmd/cover: display method receiver (when any) in `go tool cover` output
Labels: NeedsInvestigation,compiler/runtime

<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go1.17.3 darwin/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>
$ go env

GO111MODULE="on"
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/kushuh/Library/Caches/go-build"
GOENV="/Users/kushuh/Library/Application Support/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/kushuh/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/kushuh/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/Users/kushuh/go/go1.17.3"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/Users/kushuh/go/go1.17.3/pkg/tool/darwin_amd64"
GOVCS=""
GOVERSION="go1.17.3"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/kushuh/GolandProjects/anlog/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/_f/pdvtdvc50q9b2jr_l_trnbf00000gn/T/go-build2228551702=/tmp/go-build -gno-record-gcc-switches -fno-common"

</pre></details>

### What did you do?

```
$ go test -count=1 -coverprofile coverage.out ./... -v -coverpkg=./...
$ go tool cover -func=coverage.out
```

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on go.dev/play is best.
-->

Example file:

```go
package errors

type CustomError1 struct {}

func (e *CustomError1) Error() string {
    return "error 1 description"
}

type CustomError2 struct {}

func (e *CustomError2) Error() string {
    return "error 2 description"
}
```

### What did you expect to see?

```
gitlab.com/a-novel/tools/logs/internal/errors/errors.go:5:         CustomError1.Error                   100.0%
gitlab.com/a-novel/tools/logs/internal/errors/errors.go:11:        CustomError2.Error                   100.0%
```

### What did you see instead?

```
gitlab.com/a-novel/tools/logs/internal/errors/errors.go:5:         Error                   100.0%
gitlab.com/a-novel/tools/logs/internal/errors/errors.go:11:        Error                   100.0%
```

### Description

More a suggestion than an actual issue, but I think it would be nice if `go tool cover` could display methods receivers (when any) when logging results to console.

It will make output more readable and convenient for codes highly relying on interfaces and structs :)