sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: material-ui
Issue: [List] Allow adding multiple secondary actions
Labels: new feature,component: list

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Summary 💡

The ListItem component provides a property for setting a secondary action. This works fine if you only add a single IconButton, but if multiple buttons are added, the content of the ListItem can overlap with the left IconButton. This is caused by the padding of the ListItem which is set to a fixed 48px if a secondary action is set.

The secondary action should allow setting an array of IconButtons. Depending on the length of the array, the padding should be calculated. As an alternative, it could also be a fragment which is checked for the amount of IconButtons inside it.

A workaround at the moment would be to override the padding, but I think it would be much more convenient to have this handled by mui, especially because this is not directly documented.

### Examples 🌈

Current Behavior:
[Code Sample](https://codesandbox.io/s/checkboxlist-material-demo-forked-yb0b4b?file=/demo.tsx)
![image](https://user-images.githubusercontent.com/23380519/158897376-2756802a-7b81-4a69-9217-9bbe11e39060.png)

New Behavior:
![image](https://user-images.githubusercontent.com/23380519/158897424-4644c5ce-b2d4-4a2d-9d5b-0b549fcb2f89.png)


### Motivation 🔦

We have applications which often contain lists of objects which can be edited or deleted. To allow both actions, we add two IconButtons to the list items (see example above). Our application is mainly used on desktop browsers, so we have enough room for both buttons to be displayed all the time.

I have already tried to implement this, and it looks to be easy to support this case. If you think this feature could be integrated into mui I could create a PR. 😊
Repository: go
Issue: runtime: FuncForPC FileLine returns autogenerated instead of actual path
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
go version go1.18 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=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/vearutop/Library/Caches/go-build"
GOENV="/Users/vearutop/Library/Application Support/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/vearutop/go/pkg/mod"
GONOPROXY="github.com/adjust,github.com/vearutop,github.com/Unbotify"
GONOSUMDB="github.com/adjust,github.com/vearutop,github.com/Unbotify"
GOOS="darwin"
GOPATH="/Users/vearutop/go"
GOPRIVATE="github.com/adjust,github.com/vearutop,github.com/Unbotify"
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/Users/vearutop/sdk/go1.18"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/Users/vearutop/sdk/go1.18/pkg/tool/darwin_amd64"
GOVCS=""
GOVERSION="go1.18"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/vearutop/gohack/github.com/cucumber/godog/go.mod"
GOWORK=""
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/n7/jv2b0zv57jzc8y6zhmfzbn7c0000gn/T/go-build1890007164=/tmp/go-build -gno-record-gcc-switches -fno-common"
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on go.dev/play is best.
-->

I was getting file and line of struct method.

https://go.dev/play/p/VFs8FKAkTLf

```go
package main

import (
	"reflect"
	"runtime"
)

type s struct{}

func (tc *s) f() {}

func main() {
	tc := &s{}

	v := reflect.ValueOf(tc.f)
	ptr := v.Pointer()
	f := runtime.FuncForPC(ptr)
	file, line := f.FileLine(f.Entry())
	name := f.Name()

	println(file, line, name)
}
```

### What did you expect to see?

```
.../main.go 10 main.(*s).f-fm
```

### What did you see instead?

```
<autogenerated> 1 main.(*s).f-fm
```

The issue is reproducible with `go1.18` and `gotip`, however `go1.18rc1` and below (`go1.17`) works as expected.
Repository: pytorch
Issue: Can this cudaDeviceSynchronize call be removed?
Labels: module: cuda,triaged

### 🐛 Describe the bug

Can this cudaDeviceSynchronize call be removed?

https://github.com/pytorch/pytorch/blob/e785c0a1ab689737ae3c202342c4a729f9e89bcf/aten/src/ATen/native/sparse/cuda/SparseCUDATensorMath.cu#L764-L768

If it can't be removed, it should at least be wrapped with `AT_CUDA_CHECK`.

Related https://github.com/pytorch/pytorch/pull/33430

### Versions

e785c0a1ab689737ae3c202342c4a729f9e89bcf

cc @kurtamohler @ngimel
Repository: go
Issue: x/pkgsite: improve search ranking heuristics or add a way to search by package name
Labels: NeedsInvestigation,pkgsite,pkgsite/search

### What is the URL of the page with the issue?

https://pkg.go.dev/search
  
### What did you do?
 
I searched for `constraints`, `slices`, and `maps` on pkg.go.dev in hopes of finding golang.org/x/exp/constraints, golang.org/x/exp/slices, and golang.org/x/exp/maps.
  
### What did you expect to see?

Since I'm searching for the exact package name, and the packages I'm looking for are from golang.org, I would expect my desired results to be near or at the top of the search results.

### What did you see instead?

For `constraints`, the search worked pretty well. golang.org/x/exp/constraints was the second result.

![screen_20220317141503](https://user-images.githubusercontent.com/318501/158896384-1a196d11-86b3-45ee-b871-89ef4ee24d16.png)

The first place result doesn't actually say "constraints" in the package name, import path, or top-level doc comment, but it does contain the word "constraints" in the README as well as a `Constraints` type.

For `slices` the search worked less well -- golang.org/x/exp/slices was the 16th result. Most of the first 15 results do not contain the word "slices" in the import path; typically it appears in the README or documentation text.

When searching for `maps`, golang.org/x/exp/maps doesn't even appear on the page. I have to hit "Show more results" and then the package is number 59.

I think these search results could be improved. For a start, if the search query exactly matches the package name, I think that should push the ranking up a lot higher. Also, I think that golang.org packages ought to rank pretty highly in general.

As an alternative to changing the ranking, the search page could provide a special syntax for searching by exact package name. I appreciate that when I put in a full import path, it takes me directly to the page for that package -- but typing out `golang.org/x/exp/maps` is pretty tedious, so being able to type something shorter like `/maps` and get shown a list of packages named "maps" would be pretty helpful.

Finally, FWIW, a general comment about how I use the pkg.go.dev search functionality. One kind of search (we could call it a "discovery search") is where I type in a search concept hoping to find a list of popular packages related to this concept. For instance, I might type "b-tree" and hope to find the popular packages implementing a B-tree. This seems to be the main kind of searching that pkg.go.dev is optimized for. For me, **these kinds of searches are exceedingly rare** -- <1% of my search volume. For most searches, I know exactly the package that I want to call up, and I'm trying to get to the page as efficiently as possible, and I feel that the search tool could help me more in this regard.
Repository: pytorch
Issue: Quantized cannot inference with cuda
Labels: oncall: quantization,module: cuda,triaged

I am using latest version of PyTorch, I have considered dynamic quantization. After converting I am trying to do inference of the model. But I am getting errors as 
 `
 Could not run 'quantized::embedding_byte' with arguments from the 'CUDA' backend.
quantized:: embedding_byte is only available for these backends: [CPU, BackendSelect, Named, AutogradOther, AutogradCPU, AutogradCUDA, AutogradXLA, Tracer, Autocast, Batched, VmapMode].

`

I have seen a post from 2019 where it says quantized model with cuda is not supposed. Is this still not supported??

### Versions

PyTorch version 1.11

cc @jerryzh168 @jianyuh @raghuramank100 @jamesr66a @vkuzo @ngimel
Repository: TypeScript
Issue: Can we reuse SourceFiles across projects more aggressively?
Labels: Domain: Performance

 1. Clone https://github.com/mui-org/material-ui (I'm at f2d6337305b75df97d49e58f19288429b7f767e5)
 2. `yarn --ignore-scripts`
 3. `yarn docs:typescript:check`
 4. Open `docs\src\components\typography\GradientText.tsx` in VS Code
 5. Wait for loading to finish (~10s)
 6. F12 on `styled` to jump to `packages\mui-material\src\styles\styled.d.ts`

`docs\tsconfig.json` includes many files from `packages\mui-material` but the `SourceFile` objects are not reused when the upstream project is opened because `docs` has `"resolveJsonModule": true` and `mui-material` does not.  Ironically, this means you can cut the load time of `mui-material` down from ~1750ms to ~900ms by _adding_ `"resolveJsonModule": true`.

This happens because `resolveJsonModule` has `affectsModuleResolution: true` and that's what the `DocumentRegistry` uses to determine whether reuse is appropriate.

If we could get away with a looser definition of `affectsModuleResolution` in the language service, we could potentially save a lot of time.  (Note that TS itself had an issue with failing to reuse files: #47687).
Repository: flutter
Issue: Several painting.dart image APIs do not correctly propagate errors
Labels: engine,P2,team-engine,triaged-engine

For example, try:
```
decodeImageFromPixels(Uint8List.fromList(<int>[10, 30, 40]), 10, 10, PixelFormat.rgba8888, (Image image) { });
```

or

```
decodeImageFromList(Uint8List(0), (Image image) { });
```

Notice how you see something like "Shell: [ERROR:flutter/lib/ui/painting/image_decoder.cc(88)] Could not create image from decompressed bytes." without any stack trace. This is because the hidden async work results in uncaught exceptions in the zone.


There are a few ways to fix this:

1. Break the API signatures to return a future that could complete with an error
2. Deprecate and introduce new versions that correctly return a future (And probably use that future for the image too)
Repository: tauri
Issue: [feat] Arch support for tauri bundler
Labels: type: feature request

### Describe the problem

Currently, tauri bundler can't make Arch packages

### Describe the solution you'd like

I would like to add support for Arch packages

### Alternatives considered

_No response_

### Additional context

I'd love to add this myself, but the contributing guide says to open an issue first
Repository: go
Issue: cmd/go:  add prefix to errors when using -x
Labels: NeedsInvestigation,GoCommand

For normal compiles, the output is sparse, and so errors are quite obvious. The fact that sometimes compiling will continue on to other files is not too important.

However, in verbose mode, there is a lot of output and it is very very _very_ difficult to find an error in the sea of verbosity, especially when multiple files were compiled after the actual error. If errors had an `error:` prefix or similar, it would be far easier to find the source of the problem.
Repository: PowerToys
Issue: Switch Screen
Labels: Idea-New PowerToy

### Description of the new feature / enhancement

when we are using multi display setups then we can switch the contents of the display from one screen to another with the help of single button or a shortcut key, if it can be customizable that would be amazing.

### Scenario when this would be used?

in a multi- screen setups 

### Supporting information

_No response_
Repository: pytorch
Issue: UserWarning: size_average and reduce args will be deprecated, please use reduction='mean' instead.
Labels: module: nn,triaged

### 🐛 Describe the bug

```python
class CrossEntropyLoss2d(nn.Module):
    def __init__(self, weight=None, size_average=True, ignore_index=255):
        super(CrossEntropyLoss2d, self).__init__()
        self.nll_loss = nn.NLLLoss(weight, size_average, ignore_index)

    def forward(self, inputs, targets):
        return self.nll_loss(torch.log(inputs), targets)  
```
**UserWarning: size_average and reduce args will be deprecated, please use reduction='mean' instead.**

When I don't pay attention to this warning, it will cause loss to be `nan`!

I think this is where improvements are needed, including the official API DOC.


### Versions

```
PyTorch version: 1.10.1+cu102
Is debug build: False
CUDA used to build PyTorch: 10.2
ROCM used to build PyTorch: N/A

OS: Ubuntu 20.04.1 LTS (x86_64)
GCC version: (Ubuntu 9.4.0-1ubuntu1~20.04) 9.4.0
Clang version: 10.0.0-4ubuntu1 
CMake version: version 3.21.3
Libc version: glibc-2.31

Python version: 3.8.3 (default, Jul  2 2020, 16:21:59)  [GCC 7.3.0] (64-bit runtime)
Python platform: Linux-5.8.0-63-generic-x86_64-with-glibc2.10
Is CUDA available: True
CUDA runtime version: Could not collect
GPU models and configuration: 
GPU 0: NVIDIA GeForce RTX 2080
GPU 1: NVIDIA GeForce RTX 2080

Nvidia driver version: 495.44
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

Versions of relevant libraries:
[pip3] mypy-extensions==0.4.3
[pip3] numpy==1.18.5
[pip3] numpydoc==1.1.0
[pip3] torch==1.10.1
[conda] blas                      1.0                         mkl  
[conda] mkl                       2020.1                      217  
[conda] mkl-service               2.3.0            py38he904b0f_0  
[conda] mkl_fft                   1.1.0            py38h23d657b_0  
[conda] mkl_random                1.1.1            py38h0573a6f_0  
[conda] mypy-extensions           0.4.3                    pypi_0    pypi
[conda] numpy                     1.18.5           py38ha1c710e_0  
[conda] numpy-base                1.18.5           py38hde5b4d6_0  
[conda] numpydoc                  1.1.0                      py_0  
[conda] torch                     1.10.1                   pypi_0    pypi
```

cc @albanD @mruberry @jbschlosser @walterddr @kshitij12345
Repository: TypeScript
Issue: [suggestions] Add autofix suggestion for "does not satisfy the constraint" when passing a type parameter to one with a constraint
Labels: Suggestion,Awaiting More Feedback

# Suggestion

## 🔍 Search Terms

autofix, "does not satisfy the constraint"

## ✅ Viability Checklist

My suggestion meets these guidelines:

* [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [x] This wouldn't change the runtime behavior of existing JavaScript code
* [x] This could be implemented without emitting different JS based on the types of the expressions
* [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).

## ⭐ Suggestion

Currently when passing a type parameter to another generic that has a constraint produces an error. A small example to show this:

```ts
type Valtype = "i32" | "i64";

class WasmASTLocal<Type extends Valtype> {
    // ...
}

class WasmASTLoadInstr<Type> {
    // ! Type 'Type' does not satisfy the constraint 'Valtype'
    readonly local: WasmASTLocal<Type>;

    // ...
}
```

This error is of course to be expected, but it would be nice if there were an autofix suggestion that would automatically add the constraint to the currently unconstrained type variable.

i.e. I would like there to be a suggestion that when selected causes `Type` to be constrained as such:

```ts
// After fix the constraint is lifted to this type parameter
class WasmASTLoadInstr<Type extends Valtype> {
    // ! Type 'Type' does not satisfy the constraint 'Valtype'
    readonly local: WasmASTLocal<Type>;

    // ...
}
```

## 📃 Motivating Example

The above example gives a simplified usage of where I'm hitting this at the moment (as there are *a lot* of constrained generic parameters throughout the AST).

This would just be generally useful though when you're dealing with any classes/types that have a constrained generic, and you want some object that mirrors that generic but with additional wrapping.

## 💻 Use Cases

This is purely an autofix, it simply makes it simpler to fix these errors rather than having to go into the file where the generic constraint is defined, copy it out and paste it into the location we're wrapping.

## Notes

This fix probably shouldn't be shown if the type parameter that caused the failure *already has* a different incompatible constraint. In those cases it is more likely to be a typing error rather than just an incomplete type parameter.
Repository: neovim
Issue: nvim_create_autocmd: silent! Lua callback (silence errors)
Labels: enhancement,api,has:workaround,lua,events

### Feature already in Vim?

No

### Feature description

I found this new API amazing, specially the possibility to use a lua callback instead of a vim command, but by using this it restricts the ability to call it silently. I would like to be able to make the callback be called silently instead of having to define the vim command instead. 

Instead of doing this:

```lua
autocmd("BufEnter,InsertLeave", {
            description = "Auto show code lens",
            pattern = "<buffer>",
            command = "silent! lua vim.lsp.codelens.refresh()"
})
```

I'd like something like this for example

```lua
autocmd("BufEnter,InsertLeave", {
            description = "Auto show code lens",
            pattern = "<buffer>",
            callback = vim.lsp.codelens.refresh,
            silent = true
})
```

If this is already supported, I'm sorry, but I couldn't find it in the docs.
Repository: material-ui
Issue: [Slider] Firing extra `onChange` with incorrect value after `ChangeCommitted` on mobile
Labels: bug 🐛,component: slider

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯

Tested on iOS 15.3 and 15.4. The bug appears in the latest Chrome and Safari apps

When using the Slider component, if you only slide by a few steps, then after the onChangeCommit an 'extra' onChange is triggered with the original start value in, resetting the slider back to where it was before the user interaction. Larger changes don't trigger this error.

Here's a very simple demo: [https://5xdrfw.csb.app/](https://5xdrfw.csb.app/) There's a bit of logging so you can see the extra onChange trigger. To see the console logs on mobile chrome, open a new tab and go to chrome://inspect and click the button to start logging.

Note that you have to be using a mobile device to trigger this. If you make a large change (e.g. swipe all the way to the left/right) then it works fine, but if you make a smaller change, then the slider 'springs back' to where you started due to an erroneous onChange firing after the onChangeCommitted. 

### Expected behavior 🤔

No matter how big the change, it should 'stick.

### Steps to reproduce 🕹

To reproduce, use the demo above and start swiping. You can even go to the MUI demo page here as it suffers the same problem [https://mui.com/components/slider/#main-content](https://mui.com/components/slider/#main-content)


### Context 🔦

_No response_

### Your environment 🌎

_No response_
Repository: react
Issue: [Enhancement] Imply empty array of dependencies
Labels: Type: Discussion

Sometimes I receive following warning, even if my `useCallback` does not need external dependencies.

```
React Hook useCallback does nothing when called with only one argument. Did you forget to pass an array of dependencies?
```

This requires an extra working-step to add an empty array for dependencies.

Would it not be possible to internally imply an empty dependency array by default?
Repository: vscode
Issue: Comments API: allow specifying whether reply can / will be Markdown & only style conditionally in reply input box
Labels: feature-request,comments

<!-- ⚠️⚠️ 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. -->

This is a follow-up from #140967.

The reply input box for comments currently unconditionally interprets and styles input as Markdown, e.g. bolding & italicizing while typing or highlighting. Not all code review systems that interact with VS Code through the API support Markdown, so ideally their extensions would be able to prevent the reply input box from suggesting that content will be interpreted as Markdown after saving, to reduce confusion.

For the most basic approach, this could be a property on `CommentController`, e.g. `CommentController.markdownReplies: boolean`.

---

When these code review system start to support Markdown, they might allow users to opt-in individual comment threads in their respective UIs, e.g. through a `[x] Use Markdown` checkbox under the input box. For flexibility, it would be great if VS Code provided similar functionality.

To limit UI complexity, this could be governed by a setting on `CommentController` extending the basic approach above, e.g. `CommentController.markdownReplies: 'always'|'never'|'prefer_markdown'|'prefer_plaintext'` with the default being `always`.

* `always` – no checkbox shown, comment content is interpreted and styled as Markdown in input box
* `never` – no checkbox shown, comment content is interpreted as plain text and not styled
* `prefer_markdown` – checkbox shown, default on (i.e. use Markdown)
* `prefer_plaintext` – checkbox shown, default off (i.e. use plain text)

`CommentReply` would need a new property `CommentReply.isMarkdown: boolean` to transport what the user selected when a checkbox was shown.
Repository: bitcoin
Issue: wallet getbalance is slow with 3K addresses and 3M transactions
Labels: Feature,Wallet,Resource usage

**getbalance almost blocks bitcoin deamon on first call**
<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
I think that's a pretty common use case (and the recommended practice) for bitcoin businesses: to generate a new bitcoin address any time your customer wants to deposit something. After a while wallet has thousands of addresses and millions of transactions. 
After bitcoind starts, getbalance needs to be called (in case of bitcoin-qt it done in background).
Service gets stuck as it takes a lot of time (im my case 11 hours) to calculate and cache the balance.

**It would be good to cache the wallet balance in order to speed up spin-up time**
I have made wallet in testnet with 3K watch only addresses (with lot of transactions)
In total it has ~3M transactions

**Caching would help a lot**
Speed-up can bee achieved by storing m_amounts next to transaction data in the wallet DB.

**Any other ideas, recommendations are more than welcome**
Repository: animate.css
Issue: Rename delay classes (Improvement)
Labels: v5

**Problem**

The classes for delaying are currently called `animate__delay-2s, animate__delay-3s, ...`

Which also implies that it is always "seconds", which basically is wrong and confusing, as it is a multiplier for a variable delay parameter.

**Improvement**

The classes should be named i.e. `animate__delay-2x, animate__delay-3x, ...` to better reflect, that they just delay for a specific multiplier.