sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: AOTAutograd should detect aliasing of inputs that happens *below* subclasses
Labels: triaged,module: __torch_dispatch__,oncall: pt2,module: aotdispatch,module: pt2-dispatcher

Example:
```
import torch
import torch.utils._pytree as pytree
from torch.utils._python_dispatch import return_and_correct_aliasing

class SubclassTensor(torch.Tensor):
    @staticmethod
    def __new__(cls, a):
        shape = a.shape
        kwargs = {}
        kwargs["strides"] = a.stride()
        kwargs["storage_offset"] = a.storage_offset()
        kwargs["device"] = a.device
        kwargs["layout"] = a.layout
        kwargs["requires_grad"] = a.requires_grad
        kwargs["dtype"] = a.dtype
        out = torch.Tensor._make_wrapper_subclass(cls, shape, **kwargs)
        return out

    __torch_function__ = torch._C._disabled_torch_function_impl

    def __init__(self, a):
        self.a = a

    def __repr__(self):
        a_repr = repr(self.a)
        return f"SubclassTensor({a_repr})"

    def __tensor_flatten__(self):
        return ["a"], None

    @staticmethod
    def __tensor_unflatten__(inner_tensors, meta):
        a = inner_tensors["a"]
        return SubclassTensor(a)

    @classmethod
    def __torch_dispatch__(cls, func, types, args, kwargs):
        if kwargs is None:
            kwargs = {}
        args_a = pytree.tree_map(lambda x: x.a if isinstance(x, SubclassTensor) else x, args)
        kwargs_a = pytree.tree_map(lambda x: x.a if isinstance(x, SubclassTensor) else x, kwargs)
        out_a = func(*args_a, **kwargs_a)
        out = pytree.tree_map(lambda x: SubclassTensor(x) if isinstance(x, torch.Tensor) else x, out_a)
        return return_and_correct_aliasing(func, args, kwargs, out)



@torch.compile
def f(x1, x2):
    x1.mul_(2)
    return x1 + x2


x = torch.ones(2)
subclass1 = SubclassTensor(x)
subclass2 = SubclassTensor(x)

out = f(subclass1, subclass2)
# WRONG
# prints:                 SubclassTensor(tensor([3., 3.]))
# correct answer: SubclassTensor(tensor([4., 4.]))
print(out)
```

This currently gives wrong results. The issue is that:

(1) AOTAutograd tries to detect this situation by checking to see if any inputs alias any other inputs, and "regenerating" that aliasing relationship while running functionalization, to ensure that mutations to the first input affect the second input inside the graph

(2) However, this aliasing detection only happens at the top level, before we desugar any subclass inputs

(3) In this example, the original two inputs to the graph do not alias (they are two distinct subclasses). However, after we desugar the subclass inputs and end up with two "plain" tensor inputs, we should see that these plain tensor inputs are indeed aliased.

Today this gives wrong results, so at the very least we should detect and raise an error in this situation. This case should (hopefully) be unlikely for people to hit though.

cc @Chillee @ezyang @zou3519 @albanD @samdow @msaroufim @wconstab @anijain2305
Repository: vscode
Issue: Changing actions.find's "when" to "editorFocus || !!editorIsOpen" creates a duplicate user shortcut that can't be removed
Labels: bug,keybindings-editor

Type: <b>Bug</b>

1. Go to the keyboard shortcuts GUI
1. Turn on record keys
1. Press ctrl + F on your keyboard
1. Modify `actions.find`'s when expression to `editorFocus || !!editorIsOpen`
1. Press enter
1. A duplicate `actions.find` will be created with a "User" source and a `-` for its "When"
1. Try to delete it with "right click->remove key binding" or "reset key binding" or pressing the delete key.

Expected: The user keyboard shortcut is removed
Actual: The row remains and these actions have no effect

VS Code version: Code 1.84.2 (1a5daa3a0231a0fbba4f14db7ec463cf99d7768e, 2023-11-09T10:51:52.184Z)
OS version: Windows_NT x64 10.0.19045
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|AMD Ryzen 7 2700X Eight-Core Processor          (16 x 3700)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled|
|Load (avg)|undefined|
|Memory (System)|31.93GB (23.43GB free)|
|Process Argv|--disable-extensions --remote=wsl+Ubuntu|
|Screen Reader|no|
|VM|0%|
</details>Extensions disabled
<!-- generated by issue reporter -->
Repository: vscode
Issue: When actions.find has a "User" source, workbench.action.terminal.focusFind stops working
Labels: bug,keybindings,keybindings-editor

Type: <b>Bug</b>

1. Go to the keyboard shortcuts GUI
1. Turn on record keys
1. Press ctrl + F on your keyboard
1. Modify `actions.find`'s "When" expression to `editorFocus || editorIsOpen || terminal.active`
1. Press enter to save your edit
1. Modify `actions.find`'s back to the way it was: `editorFocus || editorIsOpen`
1. Press enter to save your edit. Note: The source column will still say "User"
1. Open a terminal
1. Press ctrl + F on your keyboard

Expected: workbench.action.terminal.focusFind executes, opening a search box in your terminal
Actual: The keyboard shortcut has no effect

I turned on keyboard shortcut troubleshooting and it printed this:
```
log.ts:421  INFO [KeybindingService]: / Soft dispatching keyboard event
log.ts:421  INFO [KeybindingService]: \ Keyboard event cannot be dispatched
log.ts:421  INFO [KeybindingService]: / Received  keydown event - modifiers: [ctrl], code: ControlLeft, keyCode: 17, key: Control
log.ts:421  INFO [KeybindingService]: | Converted keydown event - modifiers: [ctrl], code: ControlLeft, keyCode: 5 ('Ctrl')
log.ts:421  INFO [KeybindingService]: \ Keyboard event cannot be dispatched in keydown phase.
log.ts:421  INFO [KeybindingService]: / Soft dispatching keyboard event
log.ts:421  INFO [KeybindingService]: | Resolving ctrl+F
log.ts:421  INFO [KeybindingService]: \ From 11 keybinding entries, matched actions.find, when: editorFocus || editorIsOpen, source: user.
log.ts:421  INFO [KeybindingService]: / Soft dispatching keyboard event
log.ts:421  INFO [KeybindingService]: | Resolving ctrl+F
log.ts:421  INFO [KeybindingService]: \ From 11 keybinding entries, matched actions.find, when: editorFocus || editorIsOpen, source: user.
log.ts:421  INFO [KeybindingService]: / Soft dispatching keyboard event
log.ts:421  INFO [KeybindingService]: \ Keyboard event cannot be dispatched
log.ts:421  INFO [KeybindingService]: + Ignoring single modifier ctrl due to it being pressed together with other keys.
```

VS Code version: Code 1.84.2 (1a5daa3a0231a0fbba4f14db7ec463cf99d7768e, 2023-11-09T10:51:52.184Z)
OS version: Windows_NT x64 10.0.19045
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|AMD Ryzen 7 2700X Eight-Core Processor          (16 x 3700)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled|
|Load (avg)|undefined|
|Memory (System)|31.93GB (23.43GB free)|
|Process Argv|--disable-extensions --remote=wsl+Ubuntu|
|Screen Reader|no|
|VM|0%|
</details>Extensions disabled
<!-- generated by issue reporter -->
Repository: deno
Issue: Feature Requests: Deno KV Queues
Labels: suggestion,ext/kv

Taking a look at Deno KV Queues there are a few things that appear to be missing to me to make it an effective solution:

- Ability to "peek" into the queue without consuming any messages.
- Ability to get some information about the queue, like the length. Especially with deploy having a max queue size, there is potentially a user land need to deal queue sizes preemptively instead of dealing with a hard fail on the message.
- Ability to support multiple queues/topics. Any sort of complex application could easily need to segment queues by type and messages, allowing a specialised listener.

Nice to haves:

- Setting the "dead letter" key per message enqueued is not super ergonomic.
- If having multiple queues/topics is created where there is a "queue" instance, it could unlock a few other usability options like strongly typing the message via TypeScript or other queuing mechanisms (FIFO is obviously the most common, but there are use cases for FILO queues as well) and ability to manage/change retry behaviours.
- A pull model versus just a listener model.
Repository: nvm
Issue: Add `nvm rm` as an alias for `nvm uninstall`
Labels: feature requests

Here's an excerpt from my bash history:

```bash
nvm i v20.10
nvm rm v20.9.0
nvm uninstall v20.9.0
```

`npm rm` is a synonym for `npm uninstall`, so naturally I try the same thing for `nvm`. Every single time, it barfs out a help string and I have to re-run the command with the full name. It would be more convenient if that alias existed.
Repository: vscode
Issue: Auto re-login needs a very long time
Labels: bug,microsoft-authentication

<!-- ⚠️⚠️ 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: 

> Version: 1.84.2
> Commit: 1a5daa3a0231a0fbba4f14db7ec463cf99d7768e
> Date: 2023-11-09T10:52:57.054Z
> Electron: 25.9.2
> ElectronBuildId: 24603566
> Chromium: 114.0.5735.289
> Node.js: 18.15.0
> V8: 11.4.183.29-electron.0
> OS: Darwin arm64 23.1.0

- OS Version: 

> Apple M1 Max 64 GB
> Version 14.1 (23B74)

Steps to Reproduce:
1. Restart vscode with all windows closed but dock light still on
2. Or restart vscode with all process quited

The GitHub Account will auto re-login in 1 second, regardless of whether I'm using (enabled or disabled) Copilot.
The Microsoft Account needs maybe 30 seconds to be active, before that, there is always a blue light on settings icon to remind me login to sync settings.
Repository: pytorch
Issue: There seems to be redundant calling of findOp in findSchemaOrThrow method of Dispatcher.cpp
Labels: triaged,module: dispatch

### 🐛 Describe the bug

In Dispatcher.cpp:
`
c10::optional<OperatorHandle> Dispatcher::findSchema(const OperatorName& overload_name) {
  auto it = findOp(overload_name);
  if (it.has_value()) {
    if (it->hasSchema()) {
      return it;
    } else {
      return c10::nullopt;
    }
  } else {
    return it;
  }
}

OperatorHandle Dispatcher::findSchemaOrThrow(const char* name, const char* overload_name) {
  auto it = findSchema({name, overload_name});
  if (!it.has_value()) {
    // Check if we have ANYTHING; if that's the case, that means you're
    // missing schema
    auto it2 = findOp({name, overload_name});
    if (!it2.has_value()) {
      TORCH_CHECK(false, "Could not find schema for ", name, ".", overload_name);
    } else {
      TORCH_CHECK(false, "Could not find schema for ", name, ".", overload_name,
        " but we found an implementation; did you forget to def() the operator?");
    }
  }
  return it.value();
}
`

* findSchemaOrThrow will call findSchema first (which in turn call findOp method and check whether it has schema).
* if the queried overload_name is not registered or has no schema, the findSchema method will return c10::nullopt, where the output c10::optinal object will return false when calling it's has_value method
* the findSchemaOrThrow will call findOp , this is the second time, this method is called.

Although, in most of time an operator will have a schema attached to, i think this logic still looks not that intuitive (maybe i am wrong..)



### Versions

main branch:
commit:c4a22d6918b7ca218f2712d7e7e147aca7127fa3
Repository: next.js
Issue: Fully specified imports incorrectly cause a compile error
Labels: bug

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/next-bug-ts-config-module-resolution-bundler-fully-specified-import-n225y6?file=%2Fpages%2Findex.tsx%3A1%2C40

### To Reproduce

1. In the `tsconfig.json`, set `compilerOptions.module` to `"esnext"` and `compilerOptions.moduleResolution` to `"bundler"`.
2. Export a React component from a module with a `.tsx` file extension, e.g. `components/Foo.tsx`.
3. In page module, import and use that component with a fully specified import path, e.g:

   ```tsx
   import Foo from "./components/Foo.js";
   ```
4. Attempt a dev or production Next.js build, and see a build failure `Failed to compile` webpack error message, e.g. `Module not found: Can't resolve '../components/Foo.js'`.

### Current vs. Expected behavior

In a Next.js project with TypeScript config `compilerOptions.moduleResolution` set to `"bundler"`, within a TypeScript module importing from another project TypeScript module with a fully specified import path that includes `.js` results in a webpack compile error that the module can't be found because it could't be resolved.

The expected behavior, is that there should be no compile error. Fully specified import paths are not only valid according to TypeScript (note the fully specified import paths resolve ok without a TypeScript error in VS Code), they are actually best practice. In my projects, Typescript mode `bundler` is just a temporary stepping stone while dependencies like Material UI don't support Node.js ESM correctly; once they do the TypeScript config will be set to the more correct `nodenext` mode which actually enforces fully specified imports.

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.1.0: Mon Oct  9 21:27:24 PDT 2023; root:xnu-10002.41.9~6/RELEASE_ARM64_T6000
Binaries:
  Node: 20.9.0
  npm: 10.1.0
  Yarn: 1.22.19
  pnpm: N/A
Relevant Packages:
  next: 14.0.3
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.2
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Not sure

### Additional context

_No response_
Repository: godot
Issue: Rename node box doesn't move when scrolling the scene dock
Labels: bug,discussion,usability,topic:gui

### Godot version

v4.1.3.stable.official [f06b6836a]

### System information

Godot v4.1.3.stable - Windows 10.0.22631 - Vulkan (Forward+) - integrated Intel(R) Iris(R) Plus Graphics (Intel Corporation; 31.0.101.2125) - Intel(R) Core(TM) i5-1035G7 CPU @ 1.20GHz (8 Threads)

### Issue description

If you rename a node in the scene dock then scroll, the name box doesn't follow the node.
![image](https://github.com/godotengine/godot/assets/85214318/a789cd22-8690-42c1-aae2-8fa09765f52a)


### Steps to reproduce

Create a scene with a lot of nodes in it. There needs to be enough for the scroll bar to appear. Then double click on a node to rename it. Move you mouse off the name editing box and scroll over the scene dock. The name box should fail to follow the node you are renaming.

### Minimal reproduction project

[issue_min_rep.zip](https://github.com/godotengine/godot/files/13446110/issue_min_rep.zip)
Repository: stable-diffusion-webui
Issue: [Feature Request]: Implement 'Concept Sliders: LoRA Adaptors for Precise Control in Diffusion Models'
Labels: enhancement

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

Implement 'Concept Sliders: LoRA Adaptors for Precise Control in Diffusion Models'

Basically allows fine grained image tweaks using 'sliders'

- Paper: https://arxiv.org/abs/2311.12092
  - > We present a method to create interpretable concept sliders that enable precise control over attributes in image generations from diffusion models. Our approach identifies a low-rank parameter direction corresponding to one concept while minimizing interference with other attributes. A slider is created using a small set of prompts or sample images; thus slider directions can be created for either textual or visual concepts. Concept Sliders are plug-and-play: they can be composed efficiently and continuously modulated, enabling precise control over image generation. In quantitative experiments comparing to previous editing techniques, our sliders exhibit stronger targeted edits with lower interference. We showcase sliders for weather, age, styles, and expressions, as well as slider compositions. We show how sliders can transfer latents from StyleGAN for intuitive editing of visual concepts for which textual description is difficult. We also find that our method can help address persistent quality issues in Stable Diffusion XL including repair of object deformations and fixing distorted hands. Our code, data, and trained sliders are available at [this https URL](https://sliders.baulab.info/)
- Project Page: https://sliders.baulab.info/
- Code: https://github.com/rohitgandikota/sliders
- Weights: https://sliders.baulab.info/weights/xl_sliders/
- https://twitter.com/RohitGandikota/status/1727410973638852957
- https://www.reddit.com/r/StableDiffusion/comments/180zon7/concept_sliders_lora_adaptors_for_precise_control/

### Proposed workflow

N/A

### Additional information

See Also:

- https://github.com/comfyanonymous/ComfyUI/issues/2028
Repository: deno
Issue: op leak detection works in a confusing way when they are disabled at test step level.
Labels: testing

Context: https://github.com/denoland/deno_std/issues/3512

If the sanitization is disabled at test step level like the below example:
```js
Deno.test("reproduce", async (t) => {
  await t.step({
    name: "reproduce",
    sanitizeOps: false,
    sanitizeResources: false,
    fn: () => {
      setTimeout(() => {}, 100);
    },
  });
});
```

The step succeeds by ignoring op leak, but the parent test case still detects the op leak and the test case fails.

By this design, when the user want to disable sanitization at a test step, they also need to disable it for all the parent steps/cases. This doesn't seem ideal situation.

Is it possible to ignore the op leaks at parent level when they are already ignored at child level?
Repository: ant-design
Issue: Form 组件设置 disabled 时表单内的 Tree 组件没有被禁用
Labels: Inactive,improvement

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/biao-dan-jin-yong-antd-5-11-2-forked-r9gy2t?file=/demo.tsx)

### Steps to reproduce

1. 表单中使用 Tree 组件
2. 设置 Form.Item 的 valuePropName 为 checkedKeys，trigger 为 onCheck

### What is expected?

Form 设置 disabled 后 Tree 也被禁用

### What is actually happening?

Tree 未被禁用

| Environment | Info |
| --- | --- |
| antd | 5.11.3 |
| React | 18.2.0 |
| System | macOS |
| Browser | Chrome |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: opencv
Issue: Extand primitive core operations to support new types: CV_16BF, CV_Bool, CV_64U, CV_64S and CV_32U
Labels: feature,category: core

### Describe the feature and motivation

At least cv::LUT(), cv::minMaxLoc(), cv::minMaxIdx(), cv::countNonZero(), cv::findNonZero() and cv::hasNonZero()

### Additional context

_No response_
Repository: vscode
Issue: terminal.integrated.cwd failed to function on remote workspace: Starting directory (cwd) does not exist.
Labels: bug,remote,terminal-process

<!-- ⚠️⚠️ 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 (except necessary plugin like SSH)

<!-- 🪓 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.84.2
- OS Version: macOS 14.1.1 (23B81)

Steps to Reproduce:

1. Open a remote workspace using the `Remote - SSH` plugin.
2. Set `terminal.integrated.cwd` to any existing folder, such as `/root`.
3. When clicking the terminal '+' button, an error occurs: `The terminal process failed to launch: Starting directory (cwd) does not exist`. However, it works fine when using the drop-down menu to select a terminal profile.

Debug Trace:

- without cwd set
```
2023-11-23 14:00:23.850 [trace] [8c6ca65] terminalInstance#ctor (instanceId: 15) [{"executable":"/usr/bin/zsh","cwd":{"$mid":1,"fsPath":"/root","external":"vscode-remote://ssh-remote%2Bworkspace/root","path":"/root","scheme":"vscode-remote","authority":"ssh-remote+workspace"}}]
```
- with cwd set
```
2023-11-23 13:34:09.473 [trace] [8c6ca65] terminalInstance#ctor (instanceId: 7) [{"executable":"/usr/bin/zsh","cwd":{"$mid":1,"external":"vscode-remote:/root","path":"/root","scheme":"vscode-remote"}}]
```

It seems `ssh-remote%2Bworkspace` is missing from scheme.

![20231123152421_rec_](https://github.com/microsoft/vscode/assets/13400521/88057b4a-6bff-4317-b921-08e2d7ea3bee)