sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: Strengthen the follow-set rule for macros
Labels: T-lang,C-discussion,I-lang-radar

Over in:

- https://github.com/rust-lang/rust/pull/130635

@compiler-errors describes this general problem:

> The breakage specifically represents an inherent limitation to the "macro follow-set" formulation which is _supposed_ to make us more resilient against breakages due to extensions to the grammar like this.
> 
> Given two macro matcher arms:
> 
> * `($ty:ty) => ...`
> * `(($tt:tt)*) => ...`
> 
> And given tokens like:
> 
> * `&` `pin` `mut` [...more tokens may follow...]
> 
> On nightly today, `&pin` gets parsed as a type. However, we run out of matchers but still have tokens left (the `mut` token is next), so we fall through to the next arm. Since it's written like `($tt:tt)*`, everything is allowed, and we match the second arm successfully...
> 
> I think that's weird, because if this second arm were written like `$ty:ty mut`, that would be illegal, since `mut` is not in the follow-set of the `:ty` matcher. Thus, we can use `:tt` matchers to observe whether the compiler _actually_ parses things not in our grammar that should otherwise be protected against, which seems pretty gross.

And @Noratrieb proposes a general solution:

> I believe a solution to this would be the following new logic:
> 
> * after the end of a macro matcher arm has been reached
> * and there are still input tokens remaining
> * and if the last part of the matcher is a metavar
> * ensure that the first remaining token is in the follow set of this metavar
> * if it is, move on to the next arm
> * if it is not, **emit an error**
> 
> What this semantically does is strengthen the "commit to fully matching metavars or error" behavior such that it extends past the end. I don't know how many macros rely on this, but it seems like emitting an FCW (instead of error) on such macro invocations would find all these cases and ensure that the follow-set logic is actually robust past the end. But imo this shouldn't block this PR (which should probably just ship as-is) and can be done separately.

This issue is to track the proposal for this FCW.

cc @Noratrieb @compiler-errors @eholk @rust-lang/lang
Repository: pytorch
Issue: Setting a wrong value to `dropout` argument of `nn.RNN()` gets an indirect error message
Labels: module: nn,module: rnn,triaged

### 🐛 Describe the bug

Setting the wrong value `0.+0.j` to `dropout` argument of [nn.RNN()](https://pytorch.org/docs/stable/generated/torch.nn.RNN.html) gets the indirect error message as shown below. *It also happens with `dropout` argument of [nn.LSTM()](https://pytorch.org/docs/stable/generated/torch.nn.LSTM.html) and [nn.GRU()](https://pytorch.org/docs/stable/generated/torch.nn.GRU.html):

```python
import torch
from torch import nn

my_tensor = torch.tensor([[8., -3., 5.]])

torch.manual_seed(42)
                                                # ↓↓↓↓↓↓
rnn = nn.RNN(input_size=3, hidden_size=2, dropout=0.+0.j) # Error
```

> TypeError: float() argument must be a string or a real number, not 'complex'

So, it should directly say something like below:

> `dropout` must be `int` or `float` between 0 <= x <= 1



### Versions

```python
import torch

torch.__version__ # '2.3.0'
```

cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki
Repository: next.js
Issue: next package can't be found when using --turbo and deno 2 rc in a monorepo
Labels: bug,Turbopack,linear: turbopack,Module Resolution

### Link to the code that reproduces this issue

https://github.com/hamlim/deno-monorepo

### To Reproduce

1. Clone the repo
2. Upgrade to deno 2 release candidate: `deno upgrade rc` (using at least `2.0.0-rc.7`)
3. Run `deno install` to install dependencies
4. Run `deno task dev --filter=docs` (runs the docs Next app in development mode)
5. Try to visit `localhost:3000`
6. See error in terminal

### Current vs. Expected behavior

Following the above steps - I'd expect the app to boot correctly, however it instead shows the following error in the terminal:

```sh
docs:dev: $ next dev --turbo
docs:dev:   ▲ Next.js 15.0.0-canary.140 (turbo)
docs:dev:   - Local:        http://localhost:3000
docs:dev:
docs:dev:  ✓ Starting...
docs:dev: [Error: Next.js package not found
docs:dev:
docs:dev: Debug info:
docs:dev: - Execution of get_entrypoints_with_issues failed
docs:dev: - Execution of Project::entrypoints failed
docs:dev: - Execution of PagesProject::to_endpoint failed
docs:dev: - Execution of PagesStructureItem::new failed
docs:dev: - Execution of FileSystemPath::join failed
docs:dev: - Execution of get_next_package failed
docs:dev: - Next.js package not found] {
docs:dev:   code: 'GenericFailure'
docs:dev: }
```

Note:

Removing `--turbo` on the dev task within `apps/docs/package.json` makes it work as expected.

My assumption is that turbopack (maybe) is unable to resolve the symlinked `next` package from the root `node_modules` (next is installed somewhere else with `deno` and then symlinked _I think_)

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: 24.0.0
  Available memory (MB): 24576
  Available CPU cores: 8
Binaries:
  Node: 20.11.1
  npm: 10.8.2
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 15.0.0-canary.140 // There is a newer canary version (15.0.0-canary.173) available, please upgrade!
  eslint-config-next: N/A
  react: 19.0.0-rc-7771d3a7-20240827
  react-dom: 19.0.0-rc-7771d3a7-20240827
  typescript: 5.4.5
Next.js Config:
  output: N/A
 ⚠ There is a newer canary version (15.0.0-canary.173) available, please upgrade!
   Please try the latest canary version (`npm install next@canary`) to confirm the issue still exists before creating a new issue.
   Read more - https://nextjs.org/docs/messages/opening-an-issue
```


### Which area(s) are affected? (Select all that apply)

Module Resolution, Turbopack

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

Will attempt to replicate with the latest canary!
Repository: PowerToys
Issue: Close all windows
Labels: Needs-Triage

### Description of the new feature / enhancement

Sometimes you just want to have a fresh start. Things clutter up and you want to just close all windows and have a fresh screen to work with. This feature allows users to close all windows with ease.

### Scenario when this would be used?

Power users tend to have bunch of windows open but sometimes, like i said, it's just too much and it feels claustrophobic. Having a button to just have a fresh start will definitely help everyone

### Supporting information

This could be a tray icon that you can click and select "Close all windows" or "Force close all windows" (Much like PowerToys Awake)
Repository: TypeScript
Issue: Find All References fails for CommonJS named exports in checkJs Mode
Labels: Bug,Help Wanted

### 🔎 Search Terms

"export", "references", "commonjs", "checkJs", "allowJs", 

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about _________
This bugs reproduces in typescript@3,4,5

### ⏯ Playground Link

_No response_

### 💻 Code

Request find all references for the symbol `f` in `f.js`

```js
// f.js:
function f() {}
module.exports = {
  f,
};

// main.js
const { f } = require("./f");
f();

```

Reproduction repo: https://github.com/golopot/testcommonjs

### 🙁 Actual behavior

Doesn't find the reference from the dependent `./main.js`.

### 🙂 Expected behavior

Do find the reference from the dependent `./main.js`.

### Additional information about the issue

```json
{
  "compilerOptions": {
    "target": "es2016",                                 
    "module": "commonjs",                                
    "allowJs": true,                                 
    "checkJs": true,                                  
    "noEmit": true,                                  
    "esModuleInterop": true,                            
    "forceConsistentCasingInFileNames": true,            
    "strict": false,                                    
    "skipLibCheck": true                          
  }
}
```
Repository: vscode
Issue: Ability to toggle panel
Labels: feature-request,api,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. -->

I am working on an extension and would love the ability to focus on my panel as well as "unfocus" my panel. I can use the VSCode provided `<panel name>.focus` command to open and focus on my extensions panel, but I can't then close that panel.

The use case: I'd like to provide a command that, when run, will toggle the panel. This is useful when the UI is helpful for short interactions.

A possible implementation of this command would follow the steps of:

- Is the panel currently focused?
    - No:
        - Open the appropriate sidebar, if necessary, and focus on the panel
    - Yes:
        - Is there a previous panel in the history stack?
            - Yes: Focus on that panel
            - No: Close the sidebar OR go to a default panel

This feature request could be achieved in two ways:

1. Provide lower-level APIs, allowing developers to implement the above flow. The missing APIs, from what I can tell, are:
    - An ability to tell which sidebar a panel is in
    - An ability to determine the history of panels in a sidebar (i.e. identify which panel to focus on)
2. Offer a higher-level command similar to `<panel name>.focus` (for example, a `<panel name>.toggle` command)
Repository: rust
Issue: rustdoc: methods on type aliases do not properly link to themselves
Labels: T-rustdoc,C-bug,A-rustdoc-ui

example: https://docs.rs/oauth2/5.0.0-alpha.1/oauth2/basic/type.BasicClient.html#method.set_token_uri

broken html:
```html
<section id="method.set_token_uri" class="method"><a class="src rightside" href="../../src/oauth2/client.rs.html#348-376">source</a><h4 class="code-header">pub fn <a href="../../oauth2/struct.Client.html#tymethod.set_token_uri" class="fn">set_token_uri</a>(
    self,
    token_url: <a class="struct" href="../../oauth2/struct.TokenUrl.html" title="struct oauth2::TokenUrl">TokenUrl</a>
) -&gt; <a class="struct" href="../../oauth2/struct.Client.html" title="struct oauth2::Client">Client</a>&lt;TE, TR, TT, TIR, RT, TRE, HAS_AUTH_URL, HAS_DEVICE_AUTH_URL, HAS_INTROSPECTION_URL, HAS_REVOCATION_URL, true&gt;</h4></section>
```

note that the id is `method.set_token_uri` but the href uses `tymethod` (and also links to the page for the base type, not the page for the alias).
Repository: realworld
Issue: [Bug]: 404 page
Labels: bug

### Relevant scope

Frontend specs

### Description

Getting page 404 not found for this URL
https://realworld-docs.netlify.app/specifications/backend/api-response-format.md#users-for-authentication
I got this URL from this page https://realworld-docs.netlify.app/specifications/backend/endpoints/

When I click on the User anchor tag, I get redirected to a page that shows 404.
![image](https://github.com/user-attachments/assets/313dbddf-6dac-4729-ab8a-33fcbbc96f10)

![image](https://github.com/user-attachments/assets/6d84228b-db95-498c-aa20-af8ab4daaf8f)
Repository: ui
Issue: [bug]: Electron vite init 
Labels: bug

### Describe the bug

I'm trying to install shadcn on [electron vite](https://electron-vite.org/) but when I use `bunx --bun shadcn@latest init` I get Verifying framework error
```
✔ Preflight checks.
✖ Verifying framework.

We could not detect a supported framework at I:\Nodejs\test-app2.
Visit https://ui.shadcn.com/docs/installation/manual to manually configure your project.
Once configured, you can use the cli to add components.
```

I know there are other module for electron, vite and shadcn but I want to use officials 

When I use shadcn cli 0.8.0 I can install successful but not for latest version

### Affected component/components

None

### How to reproduce

1. init electron vite project
2. install tailwind
3. try to init shadcn using bunx

### Codesandbox/StackBlitz link

_No response_

### Logs

```bash
✔ Preflight checks.
✖ Verifying framework.

We could not detect a supported framework at I:\Nodejs\test-app2.
Visit https://ui.shadcn.com/docs/installation/manual to manually configure your project.
Once configured, you can use the cli to add components.
```


### System Info

```bash
Windows 10
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: neovim
Issue: multigrid UI: wrong command line position when multigrid UI reconnects
Labels: bug,ui,has:workaround,ui-extensibility

### Problem

When a multigrid UI reconnects, the command line is at the top of the screen and invisible.

### Steps to reproduce

1. Start a server `nvim --headless --listen /tmp/nvim.socket`
2. Connect with a multigrid UI like Neovide `neovide --server /tmp/nvim.socket`
3. Disconnect from the server `:call chanclose(nvim_list_uis()[0].chan)`
4. Reconnect  `neovide --server /tmp/nvim.socket`
5. Press `:` to enter command mode, and type something

Observe that the cursor is at the top, and the typed text is invisible. The code completion menu on the other hand is in the correct place.

![image](https://github.com/user-attachments/assets/27e1687e-0880-44b9-afb3-3acd8ccaf631)



### Expected behavior

The UI should work like normal.

### Nvim version (nvim -v)

0.10.1 and latest master

### Vim (not Nvim) behaves the same?

N/A

### Operating system/version

Arch Linux

### Terminal name/version

Neovide 0.13.3

### $TERM environment variable

N/A

### Installation

pacman
Repository: neovim
Issue: multigrid UI: floating windows move when multigrid UI reconnects
Labels: bug,ui,ui-extensibility

### Problem

When a multigrid UI reconnects, the floating windows move and the contents becomes empty.


### Steps to reproduce

1. Start a server `nvim --headless --listen /tmp/nvim.socket`
2. Connect with a multigrid UI like Neovide `neovide --server /tmp/nvim.socket`
3. Open a floating window like telescope
4. Disconnect from the server `:call chanclose(nvim_list_uis()[0].chan)`
5. Reconnect  `neovide --server /tmp/nvim.socket`
6. Observe that the layout has changed like below

Before:
![image](https://github.com/user-attachments/assets/d70122b3-c744-4beb-aaea-0296ad15b3b9)
After:
![image](https://github.com/user-attachments/assets/85c230f4-247c-48b0-9026-1aa457a06577)


### Expected behavior

The layout and the contents should not change

### Nvim version (nvim -v)

0.10.1 and latest master

### Vim (not Nvim) behaves the same?

N/A

### Operating system/version

Arch Linux

### Terminal name/version

Neovide 0.13.3

### $TERM environment variable

N/A

### Installation

pacman
Repository: neovim
Issue: multigrid UI: window contents disappear when multigrid UI reconnects
Labels: bug,ui,ui-extensibility

### Problem

When a multigrid UI reconnects, the window content disappears and only the background is visible

### Steps to reproduce

1. Start a server `nvim --headless --listen /tmp/nvim.socket`
2. Connect with a multigrid UI like Neovide `neovide --server /tmp/nvim.socket`
3. Open a buffer
4. Disconnect from the server `:call chanclose(nvim_list_uis()[0].chan)`
5. Reconnect  `neovide --server /tmp/nvim.socket`

Observe that the window is empty:
Before:
![image](https://github.com/user-attachments/assets/4c6d6bc8-d7df-45cb-8cd4-546ba1a027e5)
After:
![image](https://github.com/user-attachments/assets/1b423cd0-21f4-4f3c-bc71-3aa6c0ff1f86)


### Expected behavior

The window should keep it's contents.

### Nvim version (nvim -v)

0.10.1 and latest master

### Vim (not Nvim) behaves the same?

N/A

### Operating system/version

Arch Linux

### Terminal name/version

Neovide 0.13.3

### $TERM environment variable

N/A

### Installation

pacman
Repository: neovim
Issue: UI protocol: expose floatwin composition order (comp_index) to UIs
Labels: enhancement,ui-extensibility,floatwin

### Problem

Neovim uses a hidden internal composition order, which determines the order the floating windows with the same z-index are drawn. Many UIs, including the very widespread telecope relies on this order to build the UIs. In particular, a there's no alpha blending between the windows of the same z-index, the last window in the index will always be used.

A GUI like, Neovide, need to respect this order and do the same type of rendering, or things will look wrong. So that's in fact what we are doing right now, I reverse engineered the algorithm and duplicated it in Neovide [here](https://github.com/neovide/neovide/pull/2612). But it only works when the UI is connected from the start, and we receive absolutely all the events. It's also very fragile.

### Expected behavior

The internal composition order is exposed in the UI protocol.

NOTE: Another solution would be to require the whole plugin world to stop using overlapping z-indices. But this does still not work correctly in Neovide, because then we need a way to control the shadow casting and blur. Threating the whole z-index as one layer, is much easier to understand and does not require plugin authors to add additional Neovide specific annotations.
Repository: svelte
Issue: Consider switching to a more mature parser
Labels: compiler,needs discussion

### Describe the problem

There are many issues that have `acorn-typescript` as the upstream cause (#13179, #13125, #13409, #13188, [more](https://github.com/sveltejs/svelte/issues?q=acorn)), but `acorn-typescript` is [abandoned](https://github.com/TyrealHu/acorn-typescript/issues/61). It also has several open issues that would need to be addressed once forked or collaboration access is granted.

### Describe the proposed solution

One of the following:
- Fork `acorn-typescript`. The svelte team would become the primary maintainers but it wouldn't require any changes to the svelte source code.
- Use an alternate parser, such as [`swc`](https://swc.rs/docs/usage/core#parse) or [`oxc`](https://github.com/oxc-project/oxc?tab=readme-ov-file#-ast-and-parser). SWC seems to use the same AST types as acorn, but oxc advertises faster speeds. These parsers are much more mature than `acorn-typescript` and are obviously actively maintained. (note: oxc would require changes to both esrap and the svelte source)

My vote would be for the latter. The downsides (bigger dependencies and changes to svelte's source) are outweighed by the long-term advantage of using a more reliable library.

### Importance

nice to have
Repository: vscode
Issue: `editor.fontLigatuers`  doesn't wotk if the string is long
Labels: bug,font-rendering,confirmation-pending

<!-- ⚠️⚠️ 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.93.1
- OS Version:  windows 10

Steps to Reproduce:

1.  Install `iosevka` font https://github.com/be5invis/Iosevka/releases/tag/v31.7.1 which has many variants 
2.  use the font in vscode and apply a long `fontLigatures` setting:
```
"editor.fontLigatures": "'dlig','ss20','cv06' 1,'cv08' 2,'cv09' 1,'cv10' 6,'cv17' 11,'cv19' 3,'cv20' 1,'cv26' 8,'cv27' 21,'cv28' 4,'cv36' 4,'cv37' 4,'cv39' 7,'cv42' 6,'cv44' 8,'cv45' 1,'cv47' 8,'cv48' 30,'cv49' 8,'cv50' 4,'cv51' 9,'cv52' 5,'cv54' 3,'cv55' 8,'VSAJ' 7,'VSAK' 2,'VSAL' 7,'VSAM' 7,'VLAG' 2",
```
The variant features do not work in this case, however, they will work if the string is sufficiently shortened:
```
"editor.fontLigatures": "'dlig','cv06' 1,'cv44' 8,'cv45' 1,'cv47' 8,'cv49' 8,'cv50' 4,'cv51' 9,'cv52' 5,'cv54' 3,'cv55' 8,'VSAJ' 7,'VSAK' 2,'VSAL' 7,'VSAM' 7,'VLAG' 2,'cv48' 30",
```
There seems to be a length limit on this string around 150 bytes, maybe increase it to 1024, etc.
Repository: svelte
Issue: Slide transition of svelte 5 does not work correctly on iOS
Labels: transition/animation

### Describe the bug

A slide transition on iOS/Safari does not „slide in“ an element step by step. Instead the content is show in one step and then the height is increased step by step. But as the content might overflow this results in an effect that does Not Look Like „slide in“. 
All other browsers work as expected.

As a graphic is better than words look at this screencast: 
https://www.screencast.com/t/W7aQv2SZK5K

### Reproduction

https://svelte-5-preview.vercel.app/#H4sIAAAAAAAACqVRTUvEMBD9K2MUdheUrh77BSILHsQVPHiwHrLNtIZNk5JMV5bQ_27TUPcHeJuZN_Pe441njVToWPrpmeYdspQ99j27ZXTuQ-NOqAin3pnB1mGSC3kqK12Rv5YNmB41ijH0FQUoVhWR5dpJkkanTkmBhfcgBsvnCTxst1sYx2XZ0VlhUbGO21ZO8D12GRx4fWytGbS4q40yNgUl229qjRKorRFnVMr8ZBWLLOVCNht8DiB8GKtEniyO_4deap_IZvK-DPLDQGQ0GF0rWR8Lv95AUcI6ZgMFXMVqM5b7t91r8vSyf9_lSbwKhDp3tZU9geK6nWIgV7FZSHa9sQQe5ghhhMaaDlbxKckl4lUWthUS_GneOOKE64Yrh5ssmI0aE-_0zc4I2UgULCU74Pg1_gJaN3c8CAIAAA==



### System Info

```shell
System:
    OS: Windows 11 10.0.22631
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
    Memory: 7.03 GB / 31.75 GB
  Binaries:
    Node: 20.17.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.17 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 10.8.2 - C:\Program Files\nodejs\npm.CMD
    pnpm: 9.11.0 - C:\Program Files\nodejs\pnpm.CMD
  Browsers:
    Edge: Chromium (127.0.2651.74)
    Internet Explorer: 11.0.22621.3527
```


### Severity

blocking an upgrade
Repository: PowerToys
Issue: Keyboard manager broke down after latest update
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.84.1

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

[PowerToysReport_2024-09-29-21-27-26.zip](https://github.com/user-attachments/files/17182358/PowerToysReport_2024-09-29-21-27-26.zip)

I'm not entirely sure if this is what caused it, but after installing the last update, I try to use a shortcut I had previously set up that worked just fine and it worked once before edge started using its default shortcut for that key combination that i didn't even know was a thing because I always used the shortcut I made. In the moment I had ctrl + NumPad1 and ctrl + NumPad3 assigned to send the text ">" and "<", respectively. I tried on other apps besides edge and it still didn't work at all.

### ✔️ Expected Behavior

I was expecting for the shortcuts that I had already and used to work well to keep working.

### ❌ Actual Behavior

None of the shortcuts I tried making nor the key rebindings worked after that, except for one or two, but for some reason the expected output of the latest shortcut was that of the prior shortcut, even when all prior shortcuts were deleted.

### Other Software

_No response_