sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: ICE: (probably unbound recursion) failed to resolve instance for ...
Labels: I-ICE,T-compiler,C-bug

<!--
Thank you for finding an Internal Compiler Error! 🧊  If possible, try to provide
a minimal verifiable example. You can read "Rust Bug Minimization Patterns" for
how to create smaller examples.
http://blog.pnkfx.org/blog/2019/11/18/rust-bug-minimization-patterns/
-->

### Code

Unfortunately, it's a closed source code base.


### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.72.0-nightly (101fa903b 2023-06-04)
binary: rustc
commit-hash: 101fa903bb9209d270086da279247625a2869211
commit-date: 2023-06-04
host: x86_64-unknown-linux-gnu
release: 1.72.0-nightly
LLVM version: 16.0.4
```

### Error output

```
error: internal compiler error: compiler/rustc_middle/src/ty/instance.rs:413:18: failed to resolve instance for <std::iter::Map<std::iter::Map<ZipValidity<bool, BitmapIter<'_>, BitmapIter<'_>>, [closure@path/to/file.rs:195:26: 195:43]>, &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&fn(std::option::Option<std::cmp::Ordering>) -> bool {constraint::Constraint::<T>::mask_chunk::eq}> as IntoIterator>::into_iter

thread 'rustc' panicked at 'Box<dyn Any>', /rustc/101fa903bb9209d270086da279247625a2869211/compiler/rustc_errors/src/lib.rs:1650:9

note: we would appreciate a bug report: https://github.com/rust-lang/rust/issues/new?labels=C-bug%2C+I-ICE%2C+T-compiler&template=ice.md

note: rustc 1.72.0-nightly (101fa903b 2023-06-04) running on x86_64-unknown-linux-gnu

note: compiler flags: -C embed-bitcode=no -C debuginfo=2 -C linker=clang -C incremental=[REDACTED] -C link-arg=-fuse-ld=/home/dzenan/Code/extern/mold-1.4.1-x86_64-linux/bin/mold

note: some of the compiler flags provided by cargo are hidden

query stack during panic:
#0 [collect_and_partition_mono_items] collect_and_partition_mono_items
end of query stack
```

The backtrace is longer than the max issue length, so I abused [the playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=329a22084fff85ed6352bd3a38815090) to share it.
Repository: pytorch
Issue: [question] [docs] Short/mid/long-term status of TorchScript / JIT / torch.jit.trace / FX / symbolic tracing and its replacement by Dynamo
Labels: oncall: jit,module: docs,triaged

### 📚 The doc issue

At OP https://github.com/pytorch/vision/pull/7624#discussion_r1233691474 I stumbled that there might be lack of official communication on short-term / mid-term / long-term status of TorchScript / JIT interpreter.

In that OP case, need to support TorchScript necessitated use of inelegant indexing instead of simpler `tensor[..., perm, :, :]` which seems not supported by TorchScript (btw is this construct supported by Dynamo?)

Any official information on need to support TorchScript in new code of domain libraries / in general? Does TorchScript continue to receive development? Any deprecation calendar? I would propose that this information / overview (even if no decisions made yet) made very clear directly on main page of https://pytorch.org/docs (preferrably at the top of this long page)

This question comes from the fact that PyTorch had offered many tracing/scripting/compilation technologies over the years, their recipes/tutorials are still all available, and the users need to have information at least about mid-term level plans and recommendations of the core team. My related question on deployment as well: https://discuss.pytorch.org/t/torch-compiles-deployment-story-to-non-python-host-processes/180943/4 - would be good to have this explained very clearly as well

cc @EikanWang @jgong5 @wenzhe-nrv @sanchitintel @svekars @carljparker @ezyang @albanD
Repository: terminal
Issue: DEC double-height lines do not properly reset
Labels: Area-Output,Area-VT,Issue-Bug,Product-Terminal,Priority-3

### Windows Terminal version

1.17.11461.0

### Windows build number

 10.0.19045.3086

### Other Software

_No response_

### Steps to reproduce

Create DEC double-height text via an echo command. (It can be tricky to echo the escape character.)

Clear screen, do a directory.

Watch as double-height line artifacts that shouldn't be there are there.
Not just once. Multiple double-height lines can keep reoccurring.

* Even issuing the ANSI reset ("0m") code fails to remove the artifacting behavior.
* Even clearing the screen multiple times fails to remove the artifacting behavior.


![image](https://github.com/microsoft/terminal/assets/789591/8ce91c37-56cc-430d-af45-be520e17691a)


![image](https://github.com/microsoft/terminal/assets/789591/a450818b-0fa8-426f-9f05-1a0fb84d6a14)
![image](https://github.com/microsoft/terminal/assets/789591/5feeefab-3100-42c5-abf8-849cbea918e3)


### Expected Behavior

The expected behavior is one the line is finished rendering, no double-height letters would ever appear again except if another line is issued with the escape code to turn that double-height letters on.

### Actual Behavior

The actual behavior is that after the line is finished rendering, double-height letters still keep appearing -- often many many many times -- even without another line issued with the escape code to turn double-height letters on.
Repository: PowerToys
Issue: Allow for targeted left/right keys for activation (alt,ctrl,win....)
Labels: Idea-Enhancement,Product-Peek

### Description of the new feature / enhancement

As suggested in #26726, here an feature/enhancement request for this feature: Currently the `Print-Key` is detected as `Apps/Menu`, which is a not allowed base key. In addition the key `Alt Gr` is detected as `Ctrl Alt` and the right `Strg` key is detected as normal `Strg` key, which allows limited keybinds, where keys like the `space` key are included because I need these features many times a day in the bottom line of my keyboard (`Ctrl + Alt + Space` == PT Run and now I want PT Peek to use the keys `Alt Gr + Space` for activation).

If anyone has any more suggestions for "base" keys, just name them and I will add them to the list.

It would be great if following keys could be used as "base" key:
- `Alt Gr`
- `Print`
- Right `Strg` AND Left `Strg`
- Right `Windows` AND Left `Windows`

### Scenario when this would be used?

When setting activation keys for features there would be more possibilities for users to set there prefered keybinds.

### Supporting information

_No response_
Repository: pytorch
Issue: Missing examples in some API docs
Labels: module: docs,triaged,actionable

### 📚 The doc issue

torch.nn.functional.mse_loss、torch.are_deterministic_algorithms_enabled、torch.nn.functional.batch_norm、torch.nn.functional.triplet_margin_loss、torch.nn.RNNBase missing examples in API docs.

### Suggest a potential alternative/fix

_No response_

cc @svekars @carljparker
Repository: vscode
Issue: Git - VS Code doesn't act correctly when re-using a merged PR's branch
Labels: bug,git

This is being opened as a continuation of #179978.  (Less than even,) 2 weeks is not a lot of time to allow somebody to respond to an issue.  People can be quite busy and responding to issues might not be their highest priority task and responding might take some effort.  Closing an issue that is unable to be reopened after such a short period of time is just nasty.  Please refer to #179978 for details related to this issue.  I will not repeat that info here.

This issue can be seen simply by creating a new branch (`git checkout -b …`) via the CLI.  Once the new branch is created/checked out, VS Code is inconsistent in it's display of the branch and actions.  Witness:

![image](https://github.com/microsoft/vscode/assets/559317/0a050b7e-b23f-422d-a3f7-549eefe45d45)

As you can see, VS Code sees that it is on the new branch, but also displays that the branch is 1 commit behind and 91 commits ahead of the branch it was created from.  But after a `git checkout -b foobar/test-with-el8.7 origin/some-other-branch`, why would I want to push that to the branch that it was created from?.  99.9% of the time, any push of a newly created branch created from another branch will be to the new branch, not the one it was created from.

Very simply to reproduce.  Just open a terminal window and run a `git checkout -b ...` and see if you think how VS Code is displaying and handling the result is what you would expect.

After the above, I would expect VS Code to act as if I had created the branch using the VS Code UI's _Create new branch from_ facility.  It should show that a branch is new and pushable and once that is done should do the regular process of prompting to create a PR, etc.

Tagging @lszomoru per #179978.
Repository: pytorch
Issue: The document style is inconsistent with other documents, and the parameter type is not clearly highlight
Labels: module: docs,triaged,actionable

### 📚 The doc issue

The document style is inconsistent with other documents, and the parameter type is not clearly highlight in torch.nn.functional.conv_transpose3d、torch.nn.functional.conv_transpose2d、torch.nn.functional.bilinear、torch.nn.functional.conv1d、torch.nn.functional.max_unpool3d、torch.nn.functional.max_pool3d、torch.nn.functional.conv3d、torch.nn.MultiheadAttention、torch.nn.functional.avg_pool1d、torch.nn.functional.avg_pool3d、torch.nn.functional.max_pool2d、torch.nn.functional.linear、torch.nn.functional.max_pool1d.
![image](https://github.com/pytorch/pytorch/assets/45327670/f61a1fc2-d70c-4b6a-ad38-9a8579305cd6)
![image](https://github.com/pytorch/pytorch/assets/45327670/d04ebb60-305f-41de-89ec-50dc7e2ba42e)


### Suggest a potential alternative/fix

_No response_

cc @svekars @carljparker
Repository: rust
Issue: add assert that `dyn TraitEngine` is used correctly
Labels: C-cleanup,T-types

There are currently 2 failure modes of our fulfillment contexts which don't get detected:
- we use a fulfillment context after `select_where_possible` returned errors at least once
- we don't use a fulfillment context even though it still contains unresolved obligations, i.e. we don't call `select_everything_or_error`.

We should guard against both these misuses, an issue happens when using `ObligationCtxt::implied_wf_types` and then never actually proving the nested obligations of normalization. I don't expect that to cause any exploitable soundness issues but it is still worrying and something we should guard against.
Repository: rust
Issue: Variable scoping sometimes inconsistent when debugging
Labels: A-debuginfo,O-windows-msvc,C-bug

I tried this code:

```rust
fn main() {
  let a = 5;
  let b = 6;
  let c = a + b;
  println!("Hello world {c}");
}
```

I expected to see this happen:
When setting a breakpoint on the line 2, no variables should be in scope. Then stepping forward one line shows just `a` in scope, etc.

Instead, this happened:
Both `a` and `b` were in scope but "unavailable". `c` was correctly not in scope until the `println!()`. 

### Meta

`rustc --version --verbose`:
```
rustc 1.70.0 (90c541806 2023-05-31)
binary: rustc
commit-hash: 90c541806f23a127002de5b4038be731ba1458ca
commit-date: 2023-05-31
host: x86_64-pc-windows-msvc
release: 1.70.0
LLVM version: 16.0.2
```

This may be a Windows specific debugging issue.
Repository: PowerToys
Issue: Quick Accent from host PC does not apply when using Remote Desktop Connection
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.70.1

### Installation method

WinGet

### Running as admin

None

### Area(s) with issue?

Quick Accent

### Steps to reproduce

- Set "Quick Accent" to "On" in PowerToys settings
- Connect to a remote desktop session without being in full screen mode, i.e. in a restored window that does not take over the whole screen, allowing the "host" PC keyboard shortcuts to still work
- Try typing an accented letter
- The accent bar appears, allowing selection of accent
- The accent does not apply in the target window on the remote desktop

### ✔️ Expected Behavior

The selected accent from the Host PC (running Powertoys) should apply in the text box / entry field being used in the Guest PC.

### ❌ Actual Behavior

No accent applies

### Other Software

Host OS - Windows 10 Pro 22H2 19045.3086
mstsc.exe 10.0.19041.2075

Guest OS - Windows 10 Pro 21H1 19043.1165
Repository: PowerToys
Issue: Frequent hiccups in the second computer
Labels: Issue-Bug,Priority-1,Product-Mouse Without Borders

### Microsoft PowerToys version

0.70.1

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Mouse Without Borders

### Steps to reproduce

I got my two computers in the same network (IPV4 is enabled) and I'm a former user of MouseWithoutBorders previous (standalone) version.

In both versions (the standalone MWB) and the one embedded in PowerToys I face the same issue, when I move from the main computer to the second one I got hiccups in that second computer.

It also disconnects sometimes but the hiccup behavior is the normal situation. 
It's usable though but not fluent and I would like to have a good multi-monitor/PCs experience.

Any ideas how I could get this solved?

Thanks.

### ✔️ Expected Behavior

Fluent transition between the PCs (notebooks) without hiccups in the second (slave?) computer.

### ❌ Actual Behavior

Frequent hiccups in the second (slave?) computer.

### Other Software

Windows 11Pro 22H2
Repository: godot
Issue: DirAccess.rename_absolute doesn't work in Android
Labels: bug,platform:android,topic:core,needs testing

### Godot version

4.0.3.stable

### System information

Windows 10, Android 9

### Issue description

I want to move files on my Android device from user folder to an external one, but `DirAccess.rename_absolute` doesn't work in Android like it does in my Windows device.

I had to use `DirAccess.copy_absolute` and `DirAccess.remove_absolute` to get my goal. I think this does more work than a move process, and `DirAccess.rename_absolute` should work.

### Steps to reproduce

1. Runs the project on Android device.
2. Use Move button to move the file and check output if it is `File not moved...`.
3. Use Copy button to copy the file and check output if it is `File copied!`.
4. Runs the project on Windows device.
5. Do the above steps and check if output is OK.

### Minimal reproduction project

[Android Rename.zip](https://github.com/godotengine/godot/files/11790013/Android.Rename.zip)
Repository: vscode
Issue: Get the product name from product.json for builtin walkthrough content
Labels: debt,getting-started

              Suggested to get the product name from product.json

_Originally posted by @sandy081 in https://github.com/microsoft/vscode/pull/185373#discussion_r1234154272_
Repository: next.js
Issue: [NEXT-1307] Preloaded CSS files not used within a few seconds
Labels: linear: next,CSS

### Verify canary release

* [x] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```
Operating System:
      Platform: darwin
      Arch: x64
      Version: Darwin Kernel Version 19.6.0: Sun Jul  5 00:43:10 PDT 2020; root:xnu-6153.141.1~9/RELEASE_X86_64
    Binaries:
      Node: 16.14.0
      npm: 7.24.2
      Yarn: 1.22.19
      pnpm: 8.6.2
    Relevant packages:
      next: 13.4.7-canary.1
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 4.9.4
```

### Which area(s) of Next.js are affected? (leave empty if unsure)

App directory (appDir: true)

### Link to the code that reproduces this issue or a replay of the bug

[https://github.com/JasperAlexander/nextjs-preloadwarning-example](https://github.com/JasperAlexander/nextjs-preloadwarning-example)

### To Reproduce

1. Clone [https://github.com/JasperAlexander/nextjs-preloadwarning-example](https://github.com/JasperAlexander/nextjs-preloadwarning-example).
2. Run `pnpm i` in the project directory.
3. Run `pnpm run dev` in the project directory.
4. Open [http://localhost:3000/](http://localhost:3000/) in Google Chrome.
5. Open the console of Google Chrome DevTools.
6. Hover your mouse over the link. You will see the following warning in the console: `` The resource http://localhost:3000/_next/static/css/app/child/page.css?v=1687197477239 was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally ``.

![](https://uploads.linear.app/099ed59a-06c6-472f-9977-4798721bda90/26bf6fb1-1e81-4c4a-b43f-01ccc4efbb2c/549a6b44-0cb2-49dd-b319-5455e53e6db9)

### Describe the Bug

Because of a change in the router behaviour during prefetching introduced in #49077 at [v13.3.5-canary.6](https://github.com/vercel/next.js/releases/tag/v13.3.5-canary.6), styles are preloaded but not used. This causes lots of warnings in the Chrome DevTools when you're making an app with multiple pages and links. There is a lot of discussion about this issue (#49607).

![](https://uploads.linear.app/099ed59a-06c6-472f-9977-4798721bda90/1ae62e92-9884-4f7f-a659-02ebb959dba4/554ac8b8-5126-42fe-a7ee-ad03c393992e)

### Expected Behavior

No more preload warnings.

### Which browser are you using? (if relevant)

Chrome 114.0.5735.133

### How are you deploying your application? (if relevant)

*No response*

<sub>From [SyncLinear.com](https://synclinear.com) | [NEXT-1307](https://linear.app/vercel/issue/NEXT-1307/preloaded-css-files-not-used-within-a-few-seconds)</sub>
Repository: stable-diffusion-webui
Issue: [Bug]: Grid images of batch runs have incorrect metadata when the prompt changes over the batch (e.g. using wildcards)
Labels: bug-report

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What happened?

This is halfway between a bug and feature request. I have a fix already implemented and will submit a PR later today.

The grid image of a batch run currently gets metadata identical to the first image of the batch. This is generally useful, because users can send the grid image to txt2img and reproduce the whole batch.

But there are extensions that modify the prompt for different images of a batch, e.g. wildcard extensions like [stable-diffusion-webui-wildcards](https://github.com/AUTOMATIC1111/stable-diffusion-webui-wildcards) or [sd-dynamic-prompts](https://github.com/adieyal/sd-dynamic-prompts), or another that I'm currently working on. The hardcoded webui behavior is slightly broken for these extensions since the grid image no longer contains the original prompt with the wildcard templates (it gets overwritten by the randomly generated tokens in the first image). The extension dev can work around this problem by duplicating the original prompt in `extra_generation_params` but this is awkward, pollutes the metadata with another huge prompt string and requires additional save/reload infrastructure by the extension dev.

Instead I think the batch grid should retain the original prompt used to create it (i.e. including the templates). Then the wildcards user can reproduce either individual images by sending the image to tx2img or the entire batch by sending the grid image instead.

The fix involves using `p.prompt` for grid images and `all_prompts[index]` for other images, see [line 587 of processing.py](https://github.com/stablegeniusdiffuser/stable-diffusion-webui/blob/baf6946e06249c5af9851c60171692c44ef633e0/modules/processing.py#L587).

### Steps to reproduce the problem

1. Create a batch using wildcards.
2. Examine the metadata of the grid image.


### What should have happened?

Keep the original prompt in the grid image metadata as described above.

### Commit where the problem happens

baf6946e (master) or 59419bd6 (dev)

### What Python version are you running on ?

Python 3.10.x

### What platforms do you use to access the UI ?

Windows

### What device are you running WebUI on?

Nvidia GPUs (RTX 20 above)

### What browsers do you use to access the UI ?

Google Chrome

### Command Line Arguments

```Shell
no
```


### List of extensions

https://github.com/adieyal/sd-dynamic-prompts

### Console logs

```Shell
no
```


### Additional information

_No response_
Repository: TypeScript
Issue: jsdoc: Picks up @errors comment inside a code snippet inside jsdoc as a tag
Labels: Help Wanted,Possible Improvement

# Bug Report

<!--
  Please fill in each section completely. Thank you!
-->

### 🔎 Search Terms

jsdoc @errors comment as tag inside code snippet

### 🕗 Version & Regression Information

I noticed after upgrading from 4.9.4 to 5.1.3

### ⏯ Playground Link

https://ts-ast-viewer.com/#code/JYOwLgpgTgZghgYwgAgMoHsC2EAqALUAc2QG8AoASAoHoAqWyi5W5AQRGXQCMArCBMMgTpwcUEWQAvaOk5RkmdFBRwANsDgBnCJuQBXbQBNkYWcoAOqxCgBuavTuShkAA2CZzSsC+SawcSGxwTQA6ZHwdFXUtRzhlZDg9U0wA4AQ1VQBPZHMtIxNZADVgSASQYxxM8whUBChgczAQxmYWlhcOnk025GpqZAABaCglTQAuZDwIVVV0Hr7+mGBVCAnNG2nIEOEQJcIQrvm+kyrVpw8vAAoAcgH1zYgu6gBrEuuAShCAYRE9np2-EJfsBiABeUg9ZDIV5gCbkKjMKFItQacYQhEsJFI45gAi6ADuy1UCgCCDwCWQSxWkKxyGumEyAFoqRBrhNrrlcdRTNQGczlhADpprgAaNo0rE4vHIQkzElgMkUwzAZQCJTZODlJxgXQ7SDBCXY-qXFx85Wq0xQTLUAAePmUmnQqg2ulMrk5eG56F5TPN-Et1rt70NUPpvpV-vVbLpHq9PsZfrVVtF4oxtKhx01CWiugg5QkdBlRM4ICy8rJId6-VxKD1eZ1nBgSojScyIuQIHQghryETAe12lUMErYYTLYDdGjHICnp5ZvH6snhoAvjTV2nlwBuHodFyppgsAB84SmyC4emWYEZzhcABJ1FwfCitE5dSIwCMZhBjFxsi4dnsIQwiELKhA+T66CUr76PkMBKDkiDPHAhBEM0GI9MeACa6B6EWcogBA34FMgUB6BwLggOYmAkWRvYQDYPhungcAbGgGyqJAADSUGJMkqTpDM2SEHm0ABCgPbKAAjheyjGM+b67CCehQKkIhOORXQASCQoiD48EuDqWn7F0uloQegyGBA8B6BxpDrge1CMPJAD8EwAEr8EohgADx+PUICEO2flEIe27LkAA

As you can see, if you click on JSDoc part of tree, @errors is given its own `tag`, even thought it is inside

![CleanShot 2023-06-20 at 00 02 00@2x](https://github.com/microsoft/TypeScript/assets/47742487/f260ec8a-5ca3-4259-86e3-c1bf3c164d32)


### 💻 Code

```ts
interface SomeThing {
		/**
		 * An object containing zero or more aliases used to replace values in `import` statements. These aliases are automatically passed to Vite and TypeScript.
		 *
		 * ```js
		 * // @errors: hello
		 * /// file: svelte.config.js
		 * /// type: import('@sveltejs/kit').Config
		 * const config = {
		 *   kit: {
		 *     alias: {
		 *       // this will match a file
		 *       'my-file': 'path/to/my-file.js',
		 *
		 *       // this will match a directory and its contents
		 *       // (`my-directory/x` resolves to `path/to/my-directory/x`)
		 *       'my-directory': 'path/to/my-directory',
		 *
		 *       // an alias ending /* will only match
		 *       // the contents of a directory, not the directory itself
		 *       'my-directory/*': 'path/to/my-directory/*'
		 *     }
		 *   }
		 * };
		 * ```
		 *
		 * > The built-in `$lib` alias is controlled by `config.kit.files.lib` as it is used for packaging.
		 *
		 * > You will need to run `npm run dev` to have SvelteKit automatically generate the required alias configuration in `jsconfig.json` or `tsconfig.json`.
		 * @default {}
		 */
		alias?: Record<string, string>;
}
```

### 🙁 Actual behavior

@errors in the code snippet was marked as a JSDoc tag

### 🙂 Expected behavior

<!-- What you expected to happen instead, and why -->

@errors is inside a code snippet, should not be parsed as a JSDoc tag at all
Repository: pytorch
Issue: Long PR description leads to "Argument list too long" error from docker
Labels: module: ci,triaged,module: devx

### 🐛 Describe the bug

Per title. 

Also, if your PR description contains a error message it can trick the hud into highlighting that line.

An example: https://github.com/pytorch/pytorch/pull/103735 (I've since updated to link to the error message in a gist, see edit history for the original PR description)

### Versions

main

cc @seemethere @malfet @pytorch/pytorch-dev-infra @ZainRizvi @kit1980 @huydhn @clee2000