sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: Compile time regression from loop ordering after fusion
Labels: triaged,oncall: pt2,module: inductor

![image](https://github.com/user-attachments/assets/14d1aa3a-150a-405c-8dd4-fbe5c77e8b62)
![image](https://github.com/user-attachments/assets/a6ba57a8-b546-4796-a86b-b0d98f6eb026)

Git bisect points to #126254

We expected some regression, but we should look into ways to fix it.  I was a bit surprised that the regression happened even though it was disabled.

cc @ezyang @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire
Repository: vscode
Issue: textsearchprovider - Fix API wording
Labels: bug,search,search-api

Some nits from https://github.com/microsoft/vscode/issues/226775
> 
> > ```
> >    * If explicitly contains a newline character (`\n`), the default search behavior
> > ```
> 
> ```
> 	 * will automatically enable {@link isMultiline}.
> 	 */
> ```
> 
> For clarity, I'd propose:
> 
> ```
> - * If explicitly contains a newline character
> + * If pattern contains a newline character
> ```
> 

...

> 
> > ```
> >    * `pattern` contains a newline character (`\n`).
> > ```
> 
> maybe could use `{@link pattern}`
> 


These are from https://github.com/microsoft/vscode/blob/a554d9e7e1353b2fbf16696a08ad25cb873dc2ac/src/vscode-dts/vscode.proposed.textSearchProviderNew.d.ts
Repository: vscode
Issue: textsearchprovider - clarify that `includes` are relative to `folder`
Labels: search,polish,search-api

https://github.com/microsoft/vscode/blob/a554d9e7e1353b2fbf16696a08ad25cb873dc2ac/src/vscode-dts/vscode.proposed.textSearchProviderNew.d.ts#L67-L70

It is unclear why the `includes` is a different shape than `excludes`. This is because `includes` are relative to the `folder` and cannot have a different `baseUri`.

From https://github.com/microsoft/vscode/issues/226775
Repository: vscode
Issue: search APIs- deep links to interface fields do not resolve
Labels: bug,debt,search,search-api

https://github.com/microsoft/vscode/blob/a554d9e7e1353b2fbf16696a08ad25cb873dc2ac/src/vscode-dts/vscode.proposed.textSearchProviderNew.d.ts#L96

`@link` references to things like `TextSearchProviderOptions.useIgnoreFiles.local` do not resolve to the correct object. I should check these over to make sure that they are correct.

From https://github.com/microsoft/vscode/issues/226775
Repository: vscode
Issue: Custom controls need to provide proper textual name, role, and state information 
Labels: bug,accessibility,editor-folding

<!-- ⚠️⚠️ 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/No

<!-- 🪓 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.92.2
- OS Version: 14.6.1 (23G93)

Steps to Reproduce:

The current monaco-editor has some accessibility issues where few users will have the impact on the content they are viewing.
   1. Controls to expand or collapse lines in the code editor lack accessible name, role, and state information, which prevents screen reader users from determining that these controls are meant to expand and collapse content or whether they are currently expanded or collapsed. To address this, ensure that custom controls provide proper textual name, role, and state information. These controls should either be `<button>` elements or have `role="button"`, include` aria-expanded="true/false"`, and have an accessible name set through aria-label or another means.
   
<img width="497" alt="codeeditor" src="https://github.com/user-attachments/assets/cc5d7f86-e4f6-46cb-ba5d-3704851a9677">

<img width="465" alt="codeeditor 2" src="https://github.com/user-attachments/assets/cb7a09b3-93ae-4c51-b37e-00798506ad63">
Repository: deno
Issue: deno install'd script re-downloads jsr typechecking dependencies on every run
Labels: bug,cli

Version: Deno 1.46.2

### repro steps
install the script
`deno install --global --allow-run=ffprobe,ffmpeg --unstable-ffi --check --allow-read --allow-write --allow-ffi --allow-env=DENO_SQLITE_LOCAL,DENO_SQLITE_PATH,HOME,DENO_DIR,XDG_CACHE_HOME --allow-net --name forager-cli --force jsr:@forager/cli@0.4.2`

then run the following
`forager-cli 2>&1 | tee output.txt`

This will show
```
Download https://jsr.io/@forager/web/runtime/control.js
Download https://jsr.io/@forager/web/0.0.6/types
Download https://jsr.io/@forager/web/0.0.6/@sveltejs/kit
Download https://jsr.io/@forager/web/0.0.6/types.js
Download https://jsr.io/@forager/web/0.0.6/page/types.js
```
on every run. This output appears to go away when I remove the `--check` flag from the install command:
`deno install --global --allow-run=ffprobe,ffmpeg --unstable-ffi --check --allow-read --allow-write --allow-ffi --allow-env=DENO_SQLITE_LOCAL,DENO_SQLITE_PATH,HOME,DENO_DIR,XDG_CACHE_HOME --allow-net --name forager-cli --force jsr:@forager/cli@0.4.2`

I believe this is because the script compiles with typing references that are non-existent https://jsr.io/@forager/web/0.0.6/server.js#L40972
```ts
    /** @type {import('../runtime/control.js').Redirect | HttpError | SvelteKitError | Error} */
```

I think this is possibly something I can fix with my build system to strip out these bad typing references (this is an autogenerated file deep inside my library, so typing isnt really important). It does feel like there is a deno bug if it continually tries to download a non existent dependency and fails to warn about that anywhere. Also more generally, I don't like that I have control over when my script reaches out to the internet (`--allow-net`) but I have no control over when deno reaches out to the internet. There is `DENO_NO_UPDATE_CHECK`, and `deno cache ...` but that is different than a kind of `DENO_NO_NET` env var or some such field that I can turn on when I want to avoid any network traffic from deno
Repository: neovim
Issue: apply extmark hl_group in breakindent "gap" space
Labels: enhancement,marks,highlight

### Problem

To reproduce current behavior:

1. `echo "    Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer ut eleifend metus. Proin velit dui, suscipit in viverra eu, scelerisque dictum elit." > test.txt`
2. `nvim -u NONE test.txt`
3. `:lua vim.api.nvim_buf_set_extmark(0, vim.api.nvim_create_namespace('test'), 0, 0, { end_row = 1, hl_group = 'DiffChange', hl_eol = true })`
4. `:set columns=50`
5. `:set breakindent`

This results in:

| Before setting `breakindent` | After setting `breakindent` |
| ----------------------------- | --------------------------- |
| <img width="449" alt="before-breakindent" src="https://github.com/user-attachments/assets/32f4348f-906c-4685-a0cc-5270928ce8dc"> | <img width="443" alt="after-breakindent" src="https://github.com/user-attachments/assets/3f7fdee1-3e1a-4698-9861-691dac1bf066"> |

### Expected behavior

Ideally the space created by `breakindent` would have the same highlight applied as any overlapping `extmark`s.

This is kind of similar in concept to: https://github.com/neovim/neovim/issues/23108, however rather than repeating virtual text on wrapped lines it repeats the highlight on any space created by wrapped lines, if that makes sense.

I'm unsure if this is technically feasible and the use case is rather small.

Related issue cut to a plugin I own: https://github.com/MeanderingProgrammer/render-markdown.nvim/issues/149.

- If there's a way I can highlight this space on the plugin side I'd love to know, I was unable to figure one out
Repository: PowerToys
Issue: ACOUNT
Labels: Needs-Triage

### Description of the new feature / enhancement

CUENTRA ENLAZAADA A CUENTA DE MICROSOFT, BACKUP DE PORTAPALES, Y BACKUP DE ATAJOS DE TECLADO

### Scenario when this would be used?

CUENTRA ENLAZAADA A CUENTA DE MICROSOFT, BACKUP DE PORTAPALES, Y BACKUP DE ATAJOS DE TECLADO

### Supporting information

_No response_
Repository: terminal
Issue: Window Terminal sporadically fails to trim trailing white spaces.
Labels: Issue-Bug,Area-TerminalControl,Product-Terminal,Priority-2

### Windows Terminal version

1.20.11781.0

### Windows build number

10.0.19043 Build 19043

### Other Software

This happens  no matter where I am copying from.

### Steps to reproduce

Open terminal, copy and paste into a new terminal window.  The behavior is sporadic, but happens with often.  It makes it very hard to work in the terminal.  

### Expected Behavior

pasted text will have the excess white space at the end of the line removed 

### Actual Behavior

pasted text  is treated like it was a single line that wrapped around, leading to long white spaces and no line breaks.  

Behavior is sporadic.  The problem is on the copy window side.

Example:  Below data was copied and pasted.  Some of the white space is removed, some is not. 


```
                                                                                                                               secondary={}                                                                                                                      r=requests.get(HTML).content.decode().split("\n")                                                                                 for x in r[1:]:
    if x:
        if "NONE" not in x:
            x=re.split("[\t ]",x)
            pos=x[0].replace("_"," ")
            if pos not in secondary:
                secondary[pos]=set()
            for v in x[1:]:
                if "(" not in v:
                    secondary[pos]=secondary[pos]|set([v])
```

I add a few newlines above the text and now it copies correctly, but this is not a consistent fix

```
secondary={}
r=requests.get(HTML).content.decode().split("\n")
for x in r[1:]:
    if x:
        if "NONE" not in x:
            x=re.split("[\t ]",x)
            pos=x[0].replace("_"," ")
            if pos not in secondary:
                secondary[pos]=set()
            for v in x[1:]:
                if "(" not in v:
                    secondary[pos]=secondary[pos]|set([v])
```
Repository: godot
Issue: rcedit Fails to Modify Resources with Console Wrapper Enabled
Labels: bug,platform:windows,topic:export

### Tested versions

- Reproducible in v4.3.stable.mono and v4.2.x.stable.mono
- rcedit v2.0.0

### System information

Windows 11

### Issue description

When exporting a Godot project for Windows with the console wrapper enabled, the first executable (which is the console wrapper) properly has its icon and other metadata set by `rcedit`. But the second executable, (the executable without the wrapper) fails to have any of the its resources modified such as the icon and metadata and falls back to Godot defaults.

This is the error that it gives:

```
editor/export/editor_export_platform.h:179 - Resources Modification: rcedit failed to modify executable: Fatal 
error: Unable to commit changes
```

`rcedit` appears to work as intended when the console wrapper is disabled such as when the release build is used since the default is to not include the console wrapper. It seems this may be an issue with having more than one executable to modify at one time since the console wrapper is the executable that's produced first.

### Steps to reproduce

- Create Godot project.
- Set up Windows export by specifying all metadata under the `Application` header.
- This includes things like specifying an `.ico` file, company name, etc.
- Export with console wrapper enabled.

### Minimal reproduction project (MRP)

N/A
Repository: transformers
Issue: oom when using adafactor optimizer in deepspeed
Labels: Usage,Good First Issue,bug

### System Info

```python
- `transformers` version: 4.44.2
- Platform: Linux-5.15.0-105-generic-x86_64-with-glibc2.31
- Python version: 3.10.0
- Huggingface_hub version: 0.23.4
- Safetensors version: 0.4.2
- Accelerate version: 0.33.0
- Accelerate config:    not found
- PyTorch version (GPU?): 2.3.0+cu118 (True)
- Tensorflow version (GPU?): not installed (NA)
- Flax version (CPU?/GPU?/TPU?): not installed (NA)
- Jax version: not installed
- JaxLib version: not installed
- Using distributed or parallel set-up in script?: <fill in>
- Using GPU in script?: <fill in>
- GPU type: NVIDIA A800 80GB PCIe
```

### Who can help?

_No response_

### Information

- [ ] The official example scripts
- [ ] My own modified scripts

### Tasks

- [ ] An officially supported task in the `examples` folder (such as GLUE/SQuAD, ...)
- [X] My own task or dataset (give details below)

### Reproduction

i'm running train_xl.sh in [this repo](https://github.com/yisol/IDM-VTON). and i change the 8bit adam optimizer to adafactor optimizer using transformers.optimization.Adafactor. i'm using two 40GB a100, deepspeed stage 2, batchsize=1,VTON-HD dataset. 

the adafactor optimizer should use less gpu memory, because of less optimizer states than 8bit adam, but it get oom in [this line](https://github.com/huggingface/transformers/blob/ecd61c62862f925a18b4f063dc17fcaf01826e25/src/transformers/optimization.py#L877)

and oom happens after 10 steps, i don't know what happen in 10th step, i call the ```accelerate.backward()``` and``` optimizer.step()``` every step.

and in 10th step, the memory usage increased from 29GB to 39GB when using 8bit adam optimizer, and get oom when using adafactor optimizer



### Expected behavior

could anybody explain this phenomenon
Repository: vscode
Issue: Tooltips Missing Name and Role Information
Labels: bug,accessibility,workbench-hover

<!-- ⚠️⚠️ 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/No

<!-- 🪓 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.92.2
- OS Version: 14.6.1 (23G93)

**Description**: Certain tooltips, such as "Ln 13, Col 14," "Spaces: 2," and "UTF-8," lack proper name and role information, making them inaccessible to screen reader users.

**Steps to Reproduce:**

1. Hover over content in the status bar showing "Ln 13, Col 14," "Spaces: 2," or "UTF-8."
2. Observe that these tooltips do not have corresponding name and role information for screen reader users.

**User Impact**: Screen reader users are unable to determine the presence of these tooltips, limiting accessibility.

**Expected Behavior**: Tooltip-triggering controls should have `aria-describedby` set to the tooltip’s ID, and the tooltip element should have `role="tooltip"` to provide the necessary accessibility information.

**Actual Behavio**r: Tooltips are displayed without proper accessibility attributes, making them invisible to assistive technologies.

**Recommendation**: Ensure all tooltips have proper name, role, and state information. The control that opens the tooltip should use `aria-describedby`, and the tooltip element must include `role="tooltip"`.

<img width="555" alt="footer" src="https://github.com/user-attachments/assets/f721dff5-1406-4a82-8ed0-6ee1501df50b">
Repository: ollama
Issue: nvidia/NV-Embed-v2 support
Labels: model request

Can you support the NVIDIA/NV-Embed-v2 model?
https://huggingface.co/nvidia/NV-Embed-v2
Repository: pytorch
Issue: Inplace addmm within Inductor
Labels: triaged,actionable,oncall: pt2,module: inductor

### 🚀 The feature, motivation and pitch

```
import torch
a = torch.randn(8, 8)
b = torch.randn(8, 8)
c = torch.randn(8, 8)
print(torch.addmm(a,b,c))
print(torch.addmm_(a,b,c))
```

### Alternatives

_No response_

### Additional context

_No response_

cc @ezyang @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire
Repository: svelte
Issue: "default" is imported from external module "svelte-autosize" but never used
Labels: needs discussion

### Describe the bug

"default" is imported from external module "svelte-autosize" but never used

![CleanShot 2024-09-04 at 11 46 10](https://github.com/user-attachments/assets/8a67e437-8dd7-483f-a6d6-3b212684010f)


### Reproduction

```
<script lang="ts">
	import autosize from 'svelte-autosize'
</script>

<textarea use:autosize></textarea>
```

### Logs

_No response_

### System Info

```shell
Version: 1.92.1 (Universal)
Commit: eaa41d57266683296de7d118f574d0c2652e1fc4
Date: 2024-08-07T20:16:39.455Z
Electron: 30.1.2
ElectronBuildId: 9870757
Chromium: 124.0.6367.243
Node.js: 20.14.0
V8: 12.4.254.20-electron.0
OS: Darwin arm64 23.4.0
```


### Severity

annoyance
Repository: neovim
Issue: delete mapping by LHS only
Labels: enhancement,api,compatibility,mappings

### Problem

`unmap` or `nvim_del_keymap` will delete all mapping with matched lhs or rhs, there should be a way to only delete mapping with matched lhs.

For example:
```lua
vim.api.nvim_set_keymap("n","ge","q",{})
vim.api.nvim_del_keymap("n","q")
print(vim.api.nvim_command("verbose map ge")) -- No mapping found
```

nvim_del_keymap will delete mapping `normal: ge -> q`  even its lhs doesn't match.

There is no way to keep other mapping has `q` as rhs after unmap or nvim_del_keymap `q`.

### Expected behavior

A api to delete mapping with matched lhs only.
Repository: pytorch
Issue: Any support for sparse linear layer in the future?
Labels: module: sparse,triaged,enhancement

### 🚀 The feature, motivation and pitch

Hello, I am currently training a deep learning model that requires first hidden layer to be sparse layer which connects to the input layer with some weights (connection) absent. I searched across the Internet and there are a few open-source implementation about that, ex [SparseLinear](https://github.com/hyeon95y/SparseLinear). I am wondering if there is any plan for Pytorch official implementation of that. Thanks in previous!

### Alternatives

_No response_

### Additional context

_No response_

cc @alexsamardzic @nikitaved @pearu @cpuhrsch @amjames @bhosmer @jcaip
Repository: PowerToys
Issue: Workspaces: Does Not Open PWA Windows Correctly
Labels: Issue-Bug,Needs-Triage,Needs-Team-Response,Tracker,Product-Workspaces

### Microsoft PowerToys version

0.84.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Workspaces

### Steps to reproduce

Open Edge and multiple (PWA) windows (I normally open five spread across two monitors, but this is not necessary to demonstrate the problem). Create a workspace with the layout. Close all the windows and activate the workspace.  

### ✔️ Expected Behavior

The workspace should open with the PWA windows in the same location they were when the workspace was created.

### ❌ Actual Behavior

The location of each PWA window in the workspace shows a generic instance of Edge with a tab opened to the new tab page.

### Other Software

_No response_
Repository: vscode
Issue: Content Lacks Proper Heading Markup
Labels: bug,accessibility,settings-editor

<!-- ⚠️⚠️ 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/No

<!-- 🪓 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.92.2
- OS Version: 14.6.1 (23G93)

Description:
Certain content, such as "Extensions," "HTML" visually functions as headings but does not use proper heading markup, making navigation difficult for screen reader users.

Steps to Reproduce:

* Navigate to content like "Extensions" in VSCode.
* Use a screen reader to navigate and notice the lack of heading structure.

**User Impact**: Screen reader users will have difficulty efficiently navigating and gaining an accurate overview of the page due to missing heading markup.

**Expected Behavior**: Text that visually functions as a heading should use appropriate heading elements (`<h1>, <h2>, etc.`), with levels that reflect the visual hierarchy. For example:

"Extensions" should be `<h2>`,
"HTML" should be `<h3>`,
"HTML: Auto Closing Tags" should be `<h4>`.

**Actual Behavior**: Text visually appears as a heading but lacks the proper HTML heading tags, reducing accessibility.

**Recommendation**: Ensure that text functioning as headings uses appropriate heading tags (`<h1>, <h2>, etc.`) to improve navigation for screen reader users.

<img width="807" alt="headings" src="https://github.com/user-attachments/assets/5a319f16-072e-4a9a-ad97-360d3f0dcf2f">
Repository: PowerToys
Issue: Mouse screen wraparound (not mouse without borders or mouse jump)
Labels: Needs-Triage

### Description of the new feature / enhancement

This would be used on a single PC with multiple monitors, so if you have two or three monitors when you get to the right edge of your far right monitor, cursors wraps around to the most left one. Basically Pacman.
I know there's Mouse Jump, but it's not nearly the same.

### Scenario when this would be used?

For anyone with multiple monitors who make many mouse miles daily.

### Supporting information

_No response_
Repository: vscode
Issue: [Accessibility] Remove unnecessary role="tree", role="treeitem" and related aria-aatributes of tree structure in Settings.
Labels: bug,accessibility,settings-editor,confirmation-pending

- VS Code Version: 1.88.0
- OS Version: MacOS Sonoma (v14.6.1)

**Issue**: The main section of Extension's contributed in Vscode OSS through `package.json` has unnecessary `role="tree"` and r`ole="treeitem"` and other `aria-atttributes `of a tree structure. Please remove these `role="tree"` and other tree structure related attributes from the VSCode's main extension's settings section in order for assistive technologies to parse the content properly.

Screenshot of issue:
![Screenshot 2024-09-03 at 11 13 09 PM](https://github.com/user-attachments/assets/27b5304a-1082-4028-a911-2eba36b31329)