sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: Functorch functionalization causes increased memory usage
Labels: triaged,module: functionalization,module: functorch

### 🐛 Describe the bug

Functorch functionalization causes more memory usages. It was turned on in PR #84435

See script below. It's a TIMM resnet50 model and was working fine with batch size 128 on a 16 GB V100, with or without functorch fusion.

However, after that PR, if we do `memory_efficient_fusion` on that model, it gets OOM.

```python
import torch
import timm

from functorch.compile import memory_efficient_fusion

x = torch.randn(128, 3, 224, 224, dtype=torch.float, device='cuda')
model = timm.create_model('resnet50')
model = model.cuda()

model = model.train()

# model = memory_efficient_fusion(model)

out = model(x)
out.sum().backward()

torch.cuda.synchronize()
```

### Versions

pytorch https://github.com/pytorch/pytorch/commit/e68df8e4a14ce1fbedf6b20e132b11ec7b151f8a
timm https://github.com/rwightman/pytorch-image-models/commit/fa8c84eede55b36861460cc8ee6ac201c068df4d
torchvision https://github.com/pytorch/vision/commit/84dcf695d64c15f8a0be845ac65901bdde845429
torchdynamo https://github.com/pytorch/torchdynamo/commit/fe3173f7e6c804e6330ac187ea8e4101f45ff9a2

V100 16 GB

cc @bdhirsh @ezyang @soumith @zou3519 @Chillee @samdow @ngimel @ptrblck @csarofeen @kevinstephano
Repository: TypeScript
Issue: Undefined entity with immediate and prototype assignments causes language service errors
Labels: Bug,Help Wanted,Effort: Moderate,Fix Available,Rescheduled,Old-Crawler-Detected

In a JavaScript file:

```js
Thing.abc = 123

Thing.prototype.def = 456

new Thing/**/();
```

Go-to-definition or find-all-refs on `Thing`

```
<semantic> Response received: definitionAndBoundSpan (3200). Request took 4 ms. Success: false . Message: Error processing request. Debug Failure. Expected declaration to have at least one class-like declaration
Error: Debug Failure. Expected declaration to have at least one class-like declaration
    at getConstructSignatureDefinition (c:/Users/Daniel/.vscode-insiders/extensions/ms-vscode.vscode-typescript-next-4.9.20220911/node_modules/typescript/lib/tsserver.js:142175:89)
    at getDefinitionFromSymbol (c:/Users/Daniel/.vscode-insiders/extensions/ms-vscode.vscode-typescript-next-4.9.20220911/node_modules/typescript/lib/tsserver.js:142170:20)
    at getDefinitionAtPosition (c:/Users/Daniel/.vscode-insiders/extensions/ms-vscode.vscode-typescript-next-4.9.20220911/node_modules/typescript/lib/tsserver.js:141951:120)
    at Object.getDefinitionAndBoundSpan (c:/Users/Daniel/.vscode-insiders/extensions/ms-vscode.vscode-typescript-next-4.9.20220911/node_modules/typescript/lib/tsserver.js:142082:31)
    at Object.getDefinitionAndBoundSpan (c:/Users/Daniel/.vscode-insiders/extensions/ms-vscode.vscode-typescript-next-4.9.20220911/node_modules/typescript/lib/tsserver.js:167969:38)
    at Session.getDefinitionAndBoundSpan (c:/Users/Daniel/.vscode-insiders/extensions/ms-vscode.vscode-typescript-next-4.9.20220911/node_modules/typescript/lib/tsserver.js:179350:83)
    at Session.handlers.ts.Map.ts.getEntries._a.<computed> (c:/Users/Daniel/.vscode-insiders/extensions/ms-vscode.vscode-typescript-next-4.9.20220911/node_modules/typescript/lib/tsserver.js:178594:61)
```

Found at https://github.com/meteor/meteor/blob/511538e15abcc34f8cfcc206ffdd738ca4c12ddd/packages/mongo/remote_collection_driver.js#L4
Repository: go
Issue: x/website: outdated module introduction blog post
Labels: Documentation,NeedsDecision,modules,website

https://go.dev/blog/using-go-modules is outdated.

In the blog entry it's supposed to work like this:
$ go test
PASS
ok      _/home/gopher/hello 0.020s

but with 1.18 and 1.19 it works like this:
$ go test
go: go.mod file not found in current directory or any parent directory; see 'go help modules'

I believe an introductory blog should be working as described.
Repository: flutter
Issue: [linux] Do not use header bar by default on Wayland
Labels: engine,a: fidelity,platform-linux,c: proposal,P3,team-engine,triaged-engine

By default, Linux applications use a GTK 3 header bar instead of a traditional title bar when running on GNOME, but also more generally when running on Wayland (independently of the desktop environment). Hence, a KDE Plasma session on Wayland uses a header bar, which looks distinctively different from the window decorations of the rest of the system. To illustrate this point, below I show the titelbar for the system files app, an example Flutter app on X11, and an example Flutter app on Wayland, on my KDE neon machine, running KDE Plasma 5.25.

![neon_files](https://user-images.githubusercontent.com/47532112/189707700-c0850775-4957-4e0d-84e5-3eaf67c04084.png)
![neon_x11](https://user-images.githubusercontent.com/47532112/189707727-06109a24-39ff-460a-a3ce-bcca75ce7fda.png)
![neon_wayland](https://user-images.githubusercontent.com/47532112/189707748-72c611e4-fd18-4bea-8ba3-ea39f349734d.png)

Evidently, the Flutter titlebar on X11 (second image) matches the general style of the system files app (first image). However, the same is not true for the **same** Flutter app on Wayland (third image). In this case, the title is centered, the app icon is missing, the height of the titelbar is too large, and additional icons next to the close button etc. (which are chosen by the user) are missing. **This problem can be mitigated by using a traditional titelbar instead of a header bar in this Wayland environment, which I have tested by modifying the code in ``linux/my_application.cc``.** I therefore advocate for not using a header bar on Wayland by default, but only when running in a Gnome environment.

As mentioned above, I am aware of the fact that I can manually disable this behavior in ``linux/my_application.cc``, and this is exactly what I am doing for my app. However, every Flutter app, which uses the default behavior will lead to a subpar experience on Plasma Wayland, which should not be the default behavior.

Moreover, there are also problems when using a header bar on GNOME (Wayland and X11), especially when packaging the app as a flatpak. I can elaborate more on this if requested. However, I have tested that a traditional titelbar looks good in every environment. Hence, it might even be an option to disable the header bar by default on every system and only enable it via plugins if it is really needed, i.e. if elements like buttons are meant to be placed in the header bar. Otherwise it does not have a purpose anyway, as far as I am aware.
Repository: pytorch
Issue: `is_pinned()` support in PrimTorch and FakeTensor.
Labels: triaged,module: primTorch,module: fakeTensor

### 🚀 The feature, motivation and pitch

Trying to add `Tensor.to` in PrimTorch in #84802. ATen implementation supports pin_memory, which is unfortunately not supported by FakeTensor nor PrimTorch.

See comment here: https://github.com/pytorch/pytorch/pull/84802#issuecomment-1244155840

Without `is_pinned()` supported in FakeTensor or PrimTorch, we can't safely implement/fallback `Tensor.to` in Prim. Looking at this comment here (https://github.com/pytorch/pytorch/blob/7a9ab5c232f54430704456d18a22f99838489817/torch/_subclasses/fake_tensor.py#L849-L850) seems like it's something planned for FakeTensor already. Would be nice if we can prioritize it.

### Alternatives

_No response_

### Additional context

_No response_

cc @ezyang @mruberry @ngimel @Lezcano @fdrocha
Repository: vscode
Issue: Shell integration ignores env overrides when opening from SCM panel?
Labels: bug,scm

<!-- ⚠️⚠️ 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

<!-- 🪓 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. -->
- VS Code Version: 1.70.2
- OS Version: Windows 10 21H1

### Initial conditions

Set up a custom profile (globally):
```json
    "terminal.integrated.profiles.windows": {
        "cmd14": {
            "path": "cmd",
            "overrideName": false,
            "env": {
                "PATH": "path\\to\\nodejs14npm7;${env:PATH}"
            }
        }
    },
```

Make this profile default (in workspace):
```json
    "terminal.integrated.defaultProfile.windows": "cmd14",
```

### Correct behavior

1. Disable shell integration
2. Open a terminal using Ctrl+~, execute `node` – it is found and executed
3. Open a terminal from the context menu on a repository in the SCM panel, execute `node` – it is found and executed

### Incorrect behavior

1. Enable shell integration
2. Open a terminal using Ctrl+~, execute `node` – it is found and executed
3. Open a terminal from the context menu on a repository in the SCM panel, execute `node` – it is **not found**

In both cases here, Code reports that shell integration failed to activate.  When printing _PATH_, I can see that the first terminal has it augmented, while the second one doesn't.
Repository: neovim
Issue: virtual line not rendering if it's beyond the last line
Labels: bug,display,marks

### Neovim version (nvim -v)

v0.8.0-dev-984-g568737d5b3

### Vim (not Nvim) behaves the same?

vim doesn't support the feature

### Operating system/version

archlinux

### Terminal name/version

foot version: 1.13.1

### $TERM environment variable

foot

### Installation

AUR

### How to reproduce the issue

```lua
local ns = vim.api.nvim_create_namespace("test-ns")
local opts = {
	virt_lines = {
		{{"text", "teststyle"}}
	},
}
vim.api.nvim_buf_set_extmark(0, ns, 7, 0, opts)
```

### Expected behavior

The virtual line should render because the line it's within the buffer.

### Actual behavior

The virtual line doesn't render at all and doesn't show any errors.
Repository: neovim
Issue: Move codelens out from lsp package and allow plugin to register codelens 
Labels: enhancement,lua,lsp

### Feature already in Vim?

no

### Feature description

It is similar to what neovim has done with diagnostics. 

Here is one user scenario: 
Suppose codelens from lsp have `run test` for each test function. Plugins write can also add `debug test`, `view test result` codelens for unit tests; update the codelens signs based on test results or code coverage etc.

![image](https://user-images.githubusercontent.com/1681295/189885920-86ad822c-3c8b-4331-976a-6c960176f6d3.png)


The idea is from vs-code. In vs code, codelens do not restrict to LSP codelens. Any plugins can register a codelens. E.g. code coverage, the beloved git lens (https://github.com/gitkraken/vscode-gitlens), vscode-go, rest-lens, version-lens, npm-info-lens etc
Repository: neovim
Issue: lsp: Dynamic registration for textDocument/didSave
Labels: enhancement,lsp

## Feature description

Dynamic registration of textDocument/didSave is convenient for language servers to be made aware of configuration changes in files with different file types. An example of this is `rust-analyzer`, which reloads on changes to `Cargo.toml`, which is not a rust file:

```json
"registrations": [
        {
            "id": "textDocument/didSave",
            "method": "textDocument/didSave",
            "registerOptions": {
                "includeText": false,
                "documentSelector": [
                    {
                        "pattern": "**/*.rs"
                    },
                    {
                        "pattern": "**/Cargo.toml"
                    },
                    {
                        "pattern": "**/Cargo.lock"
                    }
                ]
            }
        }
    ]
```
Repository: ant-design
Issue: form.validateFields可否支持忽略校验的namePath
Labels: 💡 Feature Request,Inactive

### What problem does this feature solve?

现在有一些奇怪的需求,想要展示出某些必填项,但是点击提交或者某个方法时触发校验忽略那些必填项
希望可以对form.validateFields的第一个参数进行下功能上的优化 或者通过传递第二个参数 实现不校验某些值这个功能

### What does the proposed API look like?

https://codesandbox.io/s/ji-ben-shi-yong-antd-4-23-1-forked-n4zf5g?file=/demo.js 
1. form.validateFields可否加个第二个参数,比如(namePath?:namePath[],isIgnore?:boolean)=>Promise<any>;
- 用作是否对form表单整体校验忽略某个字段的校验
2. 只传递多层级节点的某个层级或者根节点,而不是完整节点 
- 存在3个子组件name分别为["a","b"],["a","c"],["d","e"]
- 我只给namePath传[["a"]]或者基于上面的实现传递 [["d"],true]/[["d","e"],true]
- 则可以只校验a,b和a,c从而忽略d,e字段,
- 现在好像只能做到[["a","b"],["a","c"]]才可以得到我想要的结果

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: flutter
Issue: [camera_android] Add support to manipulate focus distance and focus mode manually
Labels: c: new feature,platform-android,p: camera,package,c: proposal,P3,team-android,triaged-android


## Use case
in https://pub.dev/packages/camera
I need to manipulate focus distance manually 
specifically this feature --
set(CaptureRequest.CONTROL_AF_MODE, CaptureRequest.CONTROL_AF_MODE_OFF)
set(CaptureRequest.LENS_FOCUS_DISTANCE, value)
these methods are available on android camera2 for CaptureRequest.Builder

thanks in advance
Repository: godot
Issue: AudioStreamPlayer changes stream_paused internally
Labels: discussion,topic:audio

### Godot version

3.5.stable

### System information

Windows 10

### Issue description

`AudioStreamPlayer` changes the `stream_paused` property internally when `NOTIFICATION_PAUSED` and `NOTIFICATION_UNPAUSED` is being propagated. While it seems to be desired behaviour to pause the `AudioStreamPlayer` if the `pause_mode` doesn't allow it to process further if the SceneTree is paused, the information if it was paused before the SceneTree was paused is lost. This way you cannot revert to the previous value after the SceneTree is unpaused again (Currently `stream_paused` is always set to false).
```
if (p_what == NOTIFICATION_PAUSED) {
	if (!can_process()) {
		// Node can't process so we start fading out to silence
		set_stream_paused(true);
	}
}

if (p_what == NOTIFICATION_UNPAUSED) {
	set_stream_paused(false);
}
```
audio_stream_player.cpp
(I wasn't able to find out how to quote the actual code)

This makes setting the `stream_paused` property manually very unreliable to use if you also want to pause your game and you are left with no good option to pause a `AudioStreamPlayer` temporarily.

### Steps to reproduce

1) Create a new project
2) Add a `AudioStreamPlayer` to your scene
3) Call `play()` and set `stream_paused` to true
4) Pause the SceneTree with `get_tree().paused = true`
5) Unpause the SceneTree with `get_tree().paused = false`
6) `stream_paused` will be set to false again

### Minimal reproduction project

_No response_
Repository: vscode
Issue: Option to change size of every scrollbar
Labels: feature-request,layout

<!-- ⚠️⚠️ 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. -->
I would like to resize every scrollbar, not just the ones from the editor.

A global setting would be cool and the specific ones would inherit from it.
Repository: TypeScript
Issue: Unexpected overload signature rejection since TypeScript 4.8.x
Labels: Needs Investigation,Fix Available,Rescheduled

# Bug Report

### 🔎 Search Terms

- This overload signature is not compatible with its implementation signature.
- HTMLElementTagNameMap

### 🕗 Version & Regression Information

- This changed between versions 4.7.4 and 4.8.2

### ⏯ Playground Link

[Playground link with relevant code](https://www.typescriptlang.org/play?ts=4.8.2&ssl=16&ssc=55&pln=16&pc=54#code/KYDwDg9gTgLgBAMwK4DsDGMCWEVzQC0wBsATAIQE8AVAQwHMAeAaTlBmBRIGc4BVMMMChoaXYAwDWwChARwAElQCyAGQCiRYAFsOMWnQByNHUppgAfOYAUAKDitNOlDABccDdt0AaO3Bj0jHTcmHwBKN0VVDyc9AONgUzAAbRUIAHchETFmcwBdOAAfOBQkIiIAbhtQSFhEVAxsXAJicmp6K2BHXTdo7z84oLguGChMFDpw9y7nQuLSiqrwaHhkdCwcPEJSSn0O6dcpz2cvfsN4t2HR8cnemaKSsrgAb18EaDgrTXhMOABeOAADOU4D8GA4jjAAHTNUi3GAAYQgqBgwMwAGo0aFnr57Jg5HsIdCtiQoBwkphcpCUBASMBAsA-r9-v4zjosS97Jy4KSYEgoLhOoSYSSyRTKlyAL6+KW+Hl83APBYytA4YZwGjofDvf7CnbtEgQNBIGKQg1GmJwk4AcgAglbQpU8R8NQRoOzfCqUFwIJpIUQIHQrC6tVBIfhSQgHTYJeUgA)

### 💻 Code

```ts repro
export function childByTag<K extends Uppercase<keyof HTMLElementTagNameMap>>(
  element: Element,
  tagName: K,
): HTMLElementTagNameMap[Lowercase<K>] | null; // this overload is rejected
export function childByTag(element: Element, tagName: string): Element | null;
export function childByTag(element: Element, tagName: string): Element | null {
  for (let i = 0; i < element.childElementCount; i++) {
    if (element.children[i].nodeName === tagName) {
      return element.children[i];
    }
  }

  return null;
}

const anchor = childByTag(document.documentElement, 'A');
if (anchor) {
  console.log(anchor.href); // Would be rejected without the first overload.
};
```

### 🙁 Actual behavior

TypeScript rejected the first function overload, because "This overload signature is not compatible with its implementation signature".

### 🙂 Expected behavior

I didn't expect the code to be rejected, because:

- To my understanding all the values in `HTMLElementTagNameMap` are subtypes of `Element`, thus being a covariant return type.
- All the keys in `HTMLElementTagNameMap` are strings, thus matching a strict subset of all possible strings that may be passed to `tagName`. The remaining strings are matched by the second overload.

------

If the rejection is valid and my analysis is wrong, then I would have expected the error message to be more helpful in pointing out the problem.
Repository: rust
Issue: no compilation error on impossible bitshift if not used
Labels: A-lints,T-compiler,C-bug,A-const-eval

When creating a library that contains an impossible bitshift, e.g. `1u32 << 32`

I expected to see this happen: the library doesn't compile.

Instead, this happened: the library compiles as long as the code is never used in the library but does fail to compile when used in another crate.

Other ways to fail compilation like `compile_error!` or `let a: u8 = -5` do stop the library from compiling even when the code is not in use.

### Meta
rustc version: `rustc 1.63.0 (4b91a6ea7 2022-08-08)`

minimal repro: https://github.com/jonay2000/compile-error-bug
Repository: pytorch
Issue: Separate doc and binaries build
Labels: triaged,module: doc infra

### 🚀 The feature, motivation and pitch

At the moment, if we would want to update a stable version of the docs after the release, we'd have to build new binaries and add a new tag. We need to be able to update just the stable versions of  the docs w/o building everything else. 

### Alternatives

_No response_

### Additional context

_No response_

cc @ezyang @zou3519 @holly1238 @malfet
Repository: PowerToys
Issue: Network quick settings
Labels: Idea-New PowerToy

### Description of the new feature / enhancement

Quick menu for network interfaces, to modify ip address, like NetSetMan, mabye more simple without profile and other.. just quick change ip.

### Scenario when this would be used?

it tech working with multiple network or configuration, Tlc tech also.

### Supporting information

_No response_
Repository: flutter
Issue: [plugins/package] Design a better system for branch-specific exclusion
Labels: team,p: tooling,package,team-ecosystem,P2,triaged-ecosystem

Currently the tooling supports skipping packages via yaml files that contain a flat list of excluded packages. This works well, and has substantially improved the situation over trying to maintain it manually in .cirrus.yaml.

However, we've had a number of cases where we want to exclude a package only for a specific channel, usually because either a package is deliberately becoming `master`-only temporarily, or because it's impossible to run a specific set of tests on one channel for some reason. Our de-facto solution for that to embed conditional logic in .cirrus.yaml (like [this](https://github.com/flutter/packages/blob/6df723ca4cb1a3592ade218245c07983ed006d3b/.cirrus.yml#L266-L270)), which is annoying to get right and scales poorly.

Some options:
- Don't change the tooling, but make `exclude_foo_master.yaml` and `exclude_foo_stable.yaml` files (one of which would be empty) and pass `exclude_foo.yaml,exclude_foo_$CHANNEL.yaml` in the script.
  - This would be slightly cumbersome, but doesn't add any new tooling.
- Change the format of the YAML files to include channel-specific exclusions. E.g., change the current list to a dictionary where the keys are lists of channels (with empty meaning all channels).
  - This would require a way to get the channel into the script. If we go this route we should add a flag to use (`--channel=$CHANNEL`) since picking up env variables automagically inside the script makes things much harder to understand.
Repository: rust
Issue: Diagnostic for duplicate `#[panic_handler]` shouldn't talk about lang items
Labels: A-diagnostics,T-compiler

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.

If you cannot produce a minimal reproduction case (something that would work in
isolation), please provide the steps or even link to a repository that causes
the problematic output to occur.
-->

Given the following code: <!-- Please provide a link to play.rust-lang.org -->

https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=eda11ad1f58bb9579e1a515f26b30846

```rust
#![no_std]
#![no_main]

use core::panic::PanicInfo;

#[panic_handler]
fn panik(_: &PanicInfo) -> ! {
    loop {}
}

#[panic_handler]
fn panik2(_: &PanicInfo) -> ! {
    loop {}
}

```

The current output is:

```
error[E0152]: found duplicate lang item `panic_impl`
  --> src/lib.rs:12:1
   |
12 | fn panik2(_: &PanicInfo) -> ! {
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
note: the lang item is first defined here
  --> src/lib.rs:7:1
   |
7  | fn panik(_: &PanicInfo) -> ! {
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^

For more information about this error, try `rustc --explain E0152`.
```

"lang items" are an internal, perma-unstable implementation detail and should not be mentioned in this error message.

The error should probably also suggest a resolution, namely removing one of the panic handler functions.

This error is hit fairly often by people new to bare-metal Rust.