sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: SymInt shouldn't be in dynamic_type.h
Labels: module: cpp,triaged

### 🐛 Describe the bug

We don't expect symbolic ints to ever show up in mobile, so they shouldn't be taking up space in the bitset. cc @jbschlosser @Krovatkin 

### Versions

master
Repository: PowerToys
Issue: .gcode preview: Show Text when No Thumbnail Available
Labels: Idea-Enhancement,Product-File Explorer,Needs-Triage

### Description of the new feature / enhancement

When the .gcode preview is turned on, if there is no preview image in the .gcode file, Show the .gcode file as Text



### Scenario when this would be used?

As of now, the only thing shown in the preview window is a message stating there is no preview image available.  Since I do not have any .gocde files with a preview image, the preview feature has no benefit and is turned off on my systems in order to allow my .reg preferences to show the .gcode text in the preview pane.

### Supporting information

_No response_
Repository: go
Issue: x/build: `git` errors with `gnutls_handshake() failed: Error in the pull function.`
Labels: Builders,NeedsInvestigation

```
#!watchflakes
post <- pkg ~ `^cmd/go` && `Error in the pull function`
```

```
            > go get -d insecure.go-get-issue-15410.appspot.com/pkg/p
            [stderr]
            # cd $WORK/gopath/src/insecure.go-get-issue-15410.appspot.com; git clone -- http://insecure.go-get-issue-15410.appspot.com/ $WORK/gopath/src/insecure.go-get-issue-15410.appspot.com/pkg
            Cloning into '$WORK/gopath/src/insecure.go-get-issue-15410.appspot.com/pkg'...
            fatal: unable to access 'http://insecure.go-get-issue-15410.appspot.com/': gnutls_handshake() failed: Error in the pull function.
            package insecure.go-get-issue-15410.appspot.com/pkg/p: exit status 128
```

greplogs -l -e 'gnutls_handshake\(\) failed: Error in the pull function\.'`
[2022-05-09T20:57:58-3f43096/linux-386-longtest](https://build.golang.org/log/0c5eb108f51f9c5e712650da1a751409ead6606a)
[2021-12-13T16:44:13-acc65b4/linux-amd64-longtest](https://build.golang.org/log/ba4a2ab1d75ff73cb9e28b7b5cb1d74363c37667)
[2021-11-08T14:49:56-ab31dbc/linux-386-longtest](https://build.golang.org/log/9f30837a04d06039e9fce96e7faefcbef7d6dd65)
[2021-10-26T15:20:53-1b2362b/linux-386-longtest](https://build.golang.org/log/806b10d9726a8b0aaa6d887221e965aaf75a92bc)
[2021-10-23T16:18:15-12e4404/linux-386-longtest](https://build.golang.org/log/6ad18092e94d62b139d9169d5db267fce7fc1971)
[2021-10-20T20:39:29-1dff8f0/linux-386-longtest](https://build.golang.org/log/797b2e0843baa6c3b253f3569d670c04dce8cfac)
[2021-10-20T05:28:45-b091189/linux-386-longtest](https://build.golang.org/log/4cdeec91a856e9866c369ec95e550f661717ea79)
[2021-10-20T05:28:45-b091189/linux-amd64-longtest](https://build.golang.org/log/f38388882069087148aae06ed6ae56738319b510)
[2021-10-19T18:56:08-07e5527/linux-386-longtest](https://build.golang.org/log/d92cffbc97d18f4cd9a611618508d679ab2bbe48)
[2021-10-19T18:43:08-1d63052/linux-386-longtest](https://build.golang.org/log/a89c1108c260a2caac8c422bf2d2dadc99ff5f9b)
[2021-10-19T18:18:37-9820602/linux-386-longtest](https://build.golang.org/log/250fe94f75022c8fc58ee8420afa6017e06a47fb)
[2021-10-11T22:34:49-d90f0b9/linux-386-longtest](https://build.golang.org/log/21f7a9f659a21129619038096f019534b25ddf38)
[2021-09-08T11:57:03-9295723/linux-386-longtest](https://build.golang.org/log/86edd3670f8be646044d096341086f0fb63ed2fe)
[2021-04-11T15:56:20-189c694/linux-amd64-longtest](https://build.golang.org/log/e82921ae7d917dd6f5c815f6edb632c482ade762)
[2021-04-06T21:25:55-0bc4605/linux-386-longtest](https://build.golang.org/log/22399010fe4f615afce350150af8687ded6db220)
[2021-04-03T21:06:18-9e7bc80/linux-386-longtest](https://build.golang.org/log/7227ebc394ec22dac893f1462ee1537f353d8435)
[2020-10-29T16:26:43-25d28ec/linux-386-longtest](https://build.golang.org/log/de5c563febaf2e4140128f24c648c7973b54e04d)
Repository: node
Issue: AsyncLocalStore looses context in MakeCallback
Labels: async_hooks

### Version

18.1.0, 14.19.1 (and most likely a lot others)

### Platform

Tested on `Microsoft Windows NT 10.0.22000.0 x64` but very likely platform independent.

### Subsystem

async_hooks

### What steps will reproduce the bug?

Use `node::MakeCallback()` with a receiver different to the `AsyncResource`.

See e.g. [snappy 6.x](https://github.com/kesla/node-snappy/blob/53bdf54e6e84e3d898b2f6cd00baeb9f16e9fb43/src/binding.cc#L13-L43) which uses [`Nan::AsyncWorker`](https://github.com/nodejs/nan/blob/16fa32231e2ccd89d2804b3f765319128b20c4ac/nan.h#L1909-L2026).

In this setup the complete callback is not called with the `AsyncResource` as target and this results in setting the wrong object as current resource in [`MakeCallback`](https://github.com/nodejs/node/blob/76499898763102272a47d642f905e47c0cc41df0/src/api/callback.cc#L282).

Calling callbacks with undefined/null/global as target is not that uncommon.

The before/after callbacks are called with the correct asyncId but `AsyncLocalStore` relies on the current resource.

```js
const { executionAsyncId, AsyncLocalStorage } = require("async_hooks")
const snappy = require("snappy")
const als = new AsyncLocalStorage()

als.run(15, () => {
  snappy.compress("Hello World!", () => {
    const cbId = executionAsyncId()
    console.log(`compressed: ${cbId}, als: ${als.getStore()}`)
  })
})
```

### How often does it reproduce? Is there a required condition?

Always if `MakeCallback` is used with a receiver different then the `AsyncResource` object.

### What is the expected behavior?

no context loss

### What do you see instead?

context loss 

### Additional information

_No response_
Repository: pytorch
Issue: Automate cleanup of header includes
Labels: module: internals,triaged

Many files currently include unnecessary headers, or include non-specific headers like `ATen.h` or `Functions.h` instead of the specific per-operator header e.g. `ATen/ops/sum.h`. It would be nice to have tools which can clean these up automatically. A fully automatic solution would also greatly simplify syncing header changes with meta-internal.

Currently there are configs for running `include-what-you-use` in `tools/iwyu` but this still requires a lot of manual tweaks,
- sometimes need to manually remove system-specific headers like `<bits/foo.h>` instead of `<foo>` for C++ stdlib
- it isn't aware of build configurations e.g.  `ATen/ops` includes need to be guarded with `#ifdef AT_PER_OPERATOR_HEADERS`
- it can't be run on files in `ATen/native/cpu/` since these files aren't built by the build system directly, so it can't determine build flags

cc @ezyang @bhosmer @smessmer @ljk53 @bdhirsh @albanD
Repository: pytorch
Issue: torch.cholesky has been deprecated in favour of torch.linalg.cholesky. However, torch.cholesky_inverse remains as is. It should also be moved to torch.linalg
Labels: triaged,module: linear algebra

### 🐛 Describe the bug

Not sure where this should be filed under. But I noticed that, in the most recent version of pytorch `1.11.0+cu102`, when using `torch.cholesky`, it says it's deprecated in favour of `torch.linalg.cholesky`, and will getting phased out in future versions. However, the complementary function `torch.cholesky_inverse` still runs with no deprecation warning. Indeed, there's currently no `torch.linalg.cholesky_inverse`, nor does it seem like there are any such plans. If you saw it fit to move `cholesky` to `torch.linalg`, then it seems only right that `cholesky_inverse` should join it there.

### Versions

Running PyTorch 1.11.0+cu102 on WSL.

cc @jianyuh @nikitaved @pearu @mruberry @walterddr @IvanYashchuk @xwang233 @Lezcano
Repository: rust
Issue: Tracking Issue for  RFC 3239: Add target configuration
Labels: C-tracking-issue

This is a tracking issue for the RFC "3239" (rust-lang/rfcs#3239).
The feature gate for the issue is `#![feature(cfg_target)]`.

### About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

### 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] Implement the RFC (https://github.com/rust-lang/rust/pull/96909 and https://github.com/rust-lang/rust/pull/96913)
- [ ] Adjust documentation ([see instructions on rustc-dev-guide][doc-guide])
- [ ] Stabilization PR ([see instructions on rustc-dev-guide][stabilization-guide])

[stabilization-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#stabilization-pr
[doc-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#documentation-prs

### Unresolved Questions
<!--
Include any open questions that need to be answered before the feature can be
stabilised.
-->

- How do we ensure a project does not miss configurations similar to the ones
  being `#[cfg]`-ed against with this feature? Perhaps this should be added as a
  Clippy lint that's off by default.


### Implementation history

<!--
Include a list of all the PRs that were involved in implementing the feature.
-->


<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

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

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: pytorch
Issue: Move the MPSGuardImpl to inherit from NoOpDeviceGuardImpl
Labels: triaged,module: backend,module: mps

### 🐛 Describe the bug

Currently the MPSGuardImpl is inheriting from:

```
struct TORCH_API MPSGuardImpl final : public c10::impl::DeviceGuardImplInterface {
  static constexpr DeviceType static_type = DeviceType::MPS;
```

This could be moved to NoOpDeviceGuardImpl. This issue is tracking that cleanup.

### Versions

```
Python version: 3.8.11 (default, Aug  6 2021, 08:56:27)  [Clang 10.0.0 ] (64-bit runtime)
Python platform: macOS-10.16-x86_64-i386-64bit
Is CUDA available: N/A
CUDA runtime version: Could not collect
GPU models and configuration: Could not collect
Nvidia driver version: Could not collect
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: N/A

Versions of relevant libraries:
[pip3] mypy==0.812
[pip3] mypy-extensions==0.4.3
[pip3] numpy==1.20.0
[pip3] torch==1.12.0a0+gitcfd4b64
[conda] mkl                       2021.4.0           hecd8cb5_637
[conda] mkl-include               2022.0.0           hecd8cb5_105
[conda] mkl-service               2.4.0            py38h9ed2024_0
[conda] mypy-extensions           0.4.3                    pypi_0    pypi
[conda] nomkl                     3.0                           0
[conda] numpy                     1.21.2           py38h0fa1045_0
[conda] numpy-base                1.21.2           py38hbbe2e76_0
[conda] torch                     1.12.0a0+git64704d5          pypi_0    pypi
```
Repository: pytorch
Issue: Allow users to express fused matmul/bias/relu
Labels: triaged,enhancement,needs research,module: python frontend

### 🚀 The feature, motivation and pitch

We should let users have the benefit of `_addmm_activation` (fused matmul/bias/relu; also matmul/bias/gelu if/when that is fixed in cublasLt) from #74490 in their models. Some ideas on how we might do this:

- add a LinearReLU module that calls addmm + relu in training and just _addmm_activation in inference
- add a backward & documentation for _addmm_activation and make it public
- both?
- something else?

CC @ngimel 

### Alternatives

- Do nothing and rely on nvfuser; doesn't help eager mode
- Do nothing and let users implement their own solution if they want it

### Additional context

_No response_
Repository: node
Issue: AES-256-CBC-HMAC-SHA256 and similar ciphers are not recognized as authenticated ciphers
Labels: confirmed-bug,crypto,openssl

### Version

18.1.0

### Platform

Microsoft Windows NT 10.0.19044.0 x64

### Subsystem

crypto

### What steps will reproduce the bug?

Run the following code:

```js
import crypto from 'crypto';

let cipher = crypto.createCipheriv('AES-256-CBC-HMAC-SHA256', crypto.randomBytes(32), crypto.randomBytes(16));
let encrypted = cipher.update('My beautiful data', 'utf8', 'hex');
encrypted += cipher.final('hex');
```

### How often does it reproduce? Is there a required condition?

This only reproduces when using:
- aes-128-cbc-hmac-sha1
- aes-128-cbc-hmac-sha256
- aes-256-cbc-hmac-sha1
- aes-256-cbc-hmac-sha256

### What is the expected behavior?

On Node 17.1.0:
```
d8d390a8554e2ca579a1946447c8144509495f521458996db711dd6c9595080d
```

### What do you see instead?

```
node:internal/crypto/cipher:180
  const ret = this[kHandle].update(data, inputEncoding);
                            ^

Error: Trying to add data in unsupported state
    at Cipheriv.update (node:internal/crypto/cipher:180:29)
    at file:///C:/Users/myuser/Documents/GitHub/something/test/playground.js:22:24
    at ModuleJob.run (node:internal/modules/esm/module_job:198:25)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:409:24)
    at async loadESM (node:internal/process/esm_loader:85:5)
    at async handleMainPromise (node:internal/modules/run_main:61:12)
```

### Additional information

It seems to work on LTS and above (tested until 17.1.0), but not on V18.
Repository: flutter
Issue: Identify framework post-submit iOS tests which catch `dart` regressions
Labels: team-infra,P3,triaged-infra

Dart/flutter engprod team is working on a HHH repo to run tests from dart, engine, and also framework to catch potential `dart` regressions quickly without waiting until rolled into downstreams.

This bug aims to collect a small subset of framework iOS tests that are suitable for the above purpose.

/cc @whesse
Repository: godot
Issue: Performance issues with C# Control node scripts that don't override HasPoint and _ClipsInput
Labels: needs testing,topic:dotnet,performance

### Godot version

v3.4.4.stable.mono.official [419e713a2]

### System information

Windows 10

### Issue description

I saw this issue in a project I'm working on, where performance absolutely plummeted whenever I moved the mouse over the scene. I poked around a bit on a custom build to see if I could figure out what was causing the performance issue so I could mitigate it, and this is what I found out:

Seems the problem was caused by a compounding of issues, but primarily is just some inefficient engine code that checks if the C# script has overridden HasPoint and _ClipsInput. If it does, it calls the function and stops, but if it doesn't it goes on a journey of checking assemblies and parent classes until it finds someone that does override it. So I changed my scripts to override HasPoint and _ClipsInput and the problem evaporated.

I don't know, I guess this is pretty standard for a C# call? But it's very inefficient when we're talking about Control node overrides that are called potentially hundreds of times a second whenever there's mouse movement. My project breaks down with about 250 visible control nodes. It's just repeating the same work over and over again so I don't see why it couldn't be cached, plus most of my instanced nodes are the same type too, so they'd all presumably yield the same result.

I did my profiling on a custom build based off 3.4.4. I glanced at the master code and it doesn't seem any different, so I suspect it'd be reproducible on master as well. I attached a screenshot from the visual studio profiler showing what I gathered as the most relevant slice of the problem.

![image](https://user-images.githubusercontent.com/753186/167681300-a88ae999-35e9-49a2-ba17-b09a3fecca08.png)



### Steps to reproduce

Basic reproduction steps:
- Make a C# script inherit from Control
- Don't override HasPoint or _ClipsInput
- Instantiate a bunch of them visible on screen
- Wiggle the mouse over the screen to generate input events
- ???
- Profile it

Sorry I don't have anything more specific than that. Although from reading the code I believe there's a compounding of circumstances that could make the problem more noticeable.
- I suspect the problem would be more visible with higher refresh rates.
- I suspect the performance hit is worse when the C# script has a long-ish chain of inheritance down to Control or whatever godot control node type it inherits from.
- I suspect the performance is worse when a project imports a bunch of C# libraries, as I see code here that iterates over a list of C# assemblies.

### Minimal reproduction project

I tried to make a minimal reproduction project, but I couldn't get anywhere near the performance impact I'm seeing in my working project. I'm hoping I provided enough other details to make up for it, but if the team has trouble reproducing the problem I'd gladly give it another try.
Repository: pytorch
Issue: Improve the overall design of MPSGraphCache
Labels: triaged,enhancement,module: backend,module: mps

### 🐛 Describe the bug

Currently the MPSGraphCache uses string keys to retrieve the Graphs which can be error-prone. Instead, storing the string in the Graph can alleviate some of these issues and takes care of situations where collisions happen. This issue tracks to improve the design of MPSGraphCache. 

```
struct MPSGraphCache
{
  typedef MPSCachedGraph * (^CreateCachedGraphBlock)();

  struct CacheEntry {
    CacheEntry(std::string key, MPSCachedGraph *cachedGraph) : cachedGraph_(cachedGraph), key_(key) {}
    MPSCachedGraph* cachedGraph_ = nullptr;
    std::string key_ = nullptr;
  };

 public:

  static MPSGraphCache* getInstance() {
    if(_instance_cache == nullptr) {
      _instance_cache = new MPSGraphCache();
    }
    return _instance_cache;
  }

....
```


### Versions

Python version: 3.8.11 (default, Aug  6 2021, 08:56:27)  [Clang 10.0.0 ] (64-bit runtime)
Python platform: macOS-10.16-x86_64-i386-64bit
Is CUDA available: N/A
CUDA runtime version: Could not collect
GPU models and configuration: Could not collect
Nvidia driver version: Could not collect
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: N/A

Versions of relevant libraries:
[pip3] mypy==0.812
[pip3] mypy-extensions==0.4.3
[pip3] numpy==1.20.0
[pip3] torch==1.12.0a0+gitcfd4b64
[conda] mkl                       2021.4.0           hecd8cb5_637
[conda] mkl-include               2022.0.0           hecd8cb5_105
[conda] mkl-service               2.4.0            py38h9ed2024_0
[conda] mypy-extensions           0.4.3                    pypi_0    pypi
[conda] nomkl                     3.0                           0
[conda] numpy                     1.21.2           py38h0fa1045_0
[conda] numpy-base                1.21.2           py38hbbe2e76_0
[conda] torch                     1.12.0a0+git64704d5          pypi_0    pypi


cc @albanD @malfet @DenisVieriu97 @razarmehr @abhudev
Repository: rust
Issue: rustdoc: micro scroll bars on "all" page
Labels: T-rustdoc,A-rustdoc-ui

Steps to reproduce:

1. Visit https://doc.rust-lang.org/1.60.0/std/all.html on Google Chrome Version 101.0.4951.54 (Official Build) (64-bit), Ubuntu 21.04
2. Observe grey boxes to the right of each item (these are tiny scrollbars).

![image](https://user-images.githubusercontent.com/220205/167684672-6ed0c873-c040-4601-b92d-727788f4011b.png)

This reproduces on beta and nightly as well.
Repository: vscode
Issue: Problems without column information are always shown as column 1,1
Labels: tasks,under-discussion

This happens always as it is in-built.
It was previously tracked in #110561.

-----------------------
> The idea is to change the model to get a not-wrong column zero inserted - and the question is: What could the UI show in this case?

IMO UI shall show what the model has especially we have multiple UIs rendering diagnostics. 

CCing @jrieken for model change

_Originally posted by @sandy081 in https://github.com/microsoft/vscode/issues/110561#issuecomment-971427817_

-----------------------

So, please either (preferably) reopen the currently locked issue or lets continue here...
Repository: PowerToys
Issue: Add a Window Title preview when holding [WIN] + [PgUp]/[PgDn] to page through windows in a FancyZone.
Labels: Idea-Enhancement,FancyZones-Hotkeys,Product-FancyZones

### Description of the new feature / enhancement

It would be useful to see a preview of all windows in a zone when holding `[WIN] + [PgUp]/[PgDn]` to scroll through windows in a FancyZone. 

It would not need to be a full card view of the window (though that would also be nice), it could be a text based list of window titles in the zone.

On hold of [WIN] + [PgUp]/[PgDn] A list shows:

> Outlook
> Teams
> [Firefox] - currently selected
> Windows Terminal

Continued hold of [WIN], with a key-up, key-down of [PgDn] flips to:

> Outlook
> Teams
> Firefox
> [Windows Terminal] - currently selected

Tap [PgDn] again:

> [Outlook] - currently selected
> Teams
> Firefox
> Windows Terminal

Releasing the chord will always bring the selected window to focus in that zone.

### Scenario when this would be used?

When switching between windows pinned to a FancyZone.

### Supporting information

Similar features:

1. Windows has built-in support for this, when holding `[ALT] + [Tab]` a preview of all windows is shown, and continuing to tab through them changes the focus. 
2. Firefox shows a Tab preview when using `[CTRL] + [Tab]` to scroll through tabs.