sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: Turbopack "unreachable code" string causing warnings in Firefox
Labels: Turbopack,Module Resolution

### Link to the code that reproduces this issue

https://github.com/OleSkaar/with-turbopack-app

I've used the [with-turbopack](https://github.com/vercel/next.js/tree/canary/examples/with-turbopack) example here, with two dependencies that were giving the same error in my project: 

`"@tanstack/react-query": "5.62.2",
    "@tanstack/react-query-devtools": "5.62.2",`

### To Reproduce

1. Start the application with `pnpm run dev`
2. Open the app at `localhost:3000`
3. Check the browser console in Firefox. You should see several warnings about unreachable code:

![Screenshot 2024-12-20 at 12 59 10](https://github.com/user-attachments/assets/57bd77a3-77cf-4538-8c2b-b24e6eec39e6)

This is happening because of the `"TURBOPACK unreachable";` statement that's inserted after the return statement in the code from react query dev tools: 

![Screenshot 2024-12-20 at 12 49 38](https://github.com/user-attachments/assets/8a674e26-393a-421d-ba6c-da65abf49bd4)



### Current vs. Expected behavior

I expect being able to load up this project without warnings in the console. 

I believe Firefox is detecting the `"TURBOPACK unreachable";` string as unreachable code and therefore reporting a warning (see [this page](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Errors/Stmt_after_return)). 

The string appears before a function declaration, and this seemed to be the case for the other warnings reported here as well. This function is declared below the return the statement, but because of hoisting it is reachable (and used) higher up in the code. Could the `"TURBOPACK unreachable";` string be inserted after the function declaration instead?

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.6.0: Mon Jul 29 21:14:30 PDT 2024; root:xnu-10063.141.2~1/RELEASE_ARM64_T6030
  Available memory (MB): 36864
  Available CPU cores: 12
Binaries:
  Node: 20.13.1
  npm: 10.5.2
  Yarn: 1.22.22
  pnpm: 9.14.4
Relevant Packages:
  next: 15.1.2 // Latest available version is detected (15.1.2).
  eslint-config-next: N/A
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.7.2
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Developer Experience, Module Resolution, Turbopack

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

_No response_
Repository: vscode
Issue: Does not remember minimized windows nor Z order
Labels: feature-request,workbench-window

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
As the title says. For example, if I have 5 windows in total with 3 of them being minimized at the time of exit, then upon starting VSCode those 3 minimized windows are not minimized as they were previously, moreover windows seem to be spawned in random order, so it doesn't respect their previous Z order too (I find this a bit annoying). This is on Windows 10 x64 (in case that matters).

Another issue where this was mentioned in is (about virtual desktops): #146915

**But there's more bad news**, I found that VSCode does not work correctly for that kind of windows which you drag-n-drop (from the tab bar) to create a single/minimal code editor window, and if you resize/move and then minimize such minimal window, then upon starting VSCode it will bring such minimal window to the middle of the primary screen/monitor with wrong size too, so it doesn't remember minimal window's location either. 🐛

Care to fix this finally?
Repository: storybook
Issue: [Bug]: Сonsecutive channel events on storybook@8 with "@storybook/react-webpack5" cause page to reload
Labels: bug,needs triage

### Describe the bug

When using storybook@8, react-webpack@5, emitting some consecutive events leads page to reload.
The problem does not reproduce when using react-vite.

"page reload" is the problem here

### Reproduction link

https://stackblitz.com/edit/github-axcvs6ro

### Reproduction steps

1. Go to above link
2. Open "example-button--primary" story
3. Execute the following script in devtools inside "storybook-preview-iframe" frame:

```js
window.__STORYBOOK_ADDONS_CHANNEL__.emit("updateGlobals", {globals: window.__STORYBOOK_ADDONS_CHANNEL__.data.setGlobals[0].globals})
window.__STORYBOOK_ADDONS_CHANNEL__.emit("setCurrentStory", { storyId: "" })
window.__STORYBOOK_ADDONS_CHANNEL__.emit("setCurrentStory", { storyId: "example-button--primary" })
```

This leads page to reload.

after removing "updateGlobals" call or "setCurrentStory" call, page won't reload.

### System

```bash
Storybook Environment Info:

  System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.20.3 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn <----- active
    npm: 10.2.3 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    @storybook/addon-essentials: ^8.5.0-beta.3 => 8.5.0-beta.3 
    @storybook/addon-interactions: ^8.5.0-beta.3 => 8.5.0-beta.3 
    @storybook/addon-onboarding: ^8.5.0-beta.3 => 8.5.0-beta.3 
    @storybook/addon-webpack5-compiler-swc: ^1.0.5 => 1.0.5 
    @storybook/blocks: ^8.5.0-beta.3 => 8.5.0-beta.3 
    @storybook/react: ^8.5.0-beta.3 => 8.5.0-beta.3 
    @storybook/react-webpack5: ^8.5.0-beta.3 => 8.5.0-beta.3 
    @storybook/test: ^8.5.0-beta.3 => 8.5.0-beta.3 
    storybook: ^8.5.0-beta.3 => 8.5.0-beta.3
```

### Additional context

_No response_
Repository: neovim
Issue: 'shelltemp' is broken in MSYS2/MINGW64
Labels: bug,platform:windows

### Problem

Also reported here https://github.com/msys2/MINGW-packages/issues/16301
Summary:
1. Paste the following into an empty buffer:
```
first name,last name,email
john,smith,john@example.com
drew,neil,drew@vimcasts.org
jane,doe,jane@example.com
```
2. Sort rows 2 to $ using external [gnu sort](https://www.gnu.org/software/coreutils/sort)
3. `:2,$!sort -k2 -t,`
```
shell returned 127

E485: Can't read file C:\msys64\tmp\nvim.0\...
```

### Steps to reproduce

Run from MINGW64 shell.
```help
nvim --clean config.lua
i
```
```lua
vim.o.shelltemp = true
vim.o.shellcmdflag = '-c'
vim.o.shellxquote = ''
vim.o.shellquote = ''
```
```help
<ESC>:x<CR>
TMPDIR=any/temp/folder nvim --clean -u config.lua
i
```
```txt
first name,last name,email
john,smith,john@example.com
drew,neil,drew@vimcasts.org
jane,doe,jane@example.com
```
```help
<ESC>:2,$!sort -k2 -t,<CR>
```

### Expected behavior

The buffer is sorted by column 2 starting from row 2:
```
first name,last name,email
jane,doe,jane@example.com
drew,neil,drew@vimcasts.org
john,smith,john@example.com
```

The `'shell'` is set to `$SHELL` = `/usr/bin/bash` which MSYS2 converts to Windows-style `C:\msys64\usr\bin\bash.exe`.
I'm not sure why, but the following workaround works with the same `config.lua` from above.
```lua
vim.o.shell = 'cmd.exe /s /c C:\\msys64\\usr\\bin\\bash.exe'
```

### Nvim version (nvim -v)

v0.11.0-dev-1388+g39781be14b

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

no, vim 9.1.0866-1 compiled by MSYS2

### Operating system/version

Windows 11; MINGW64_NT-10.0-26100

### Terminal name/version

Windows Terminal 1.21.3231.0

### $TERM environment variable

xterm-256color

### Installation

Nightly build for Windows
Repository: TypeScript
Issue: Add JSDoc `@export` tag
Labels: Suggestion,Awaiting More Feedback,Domain: JSDoc

### 🔍 Search Terms

`jsdoc @export `

### ✅ Viability Checklist

- [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
- [x] This wouldn't change the runtime behavior of existing JavaScript code
- [x] This could be implemented without emitting different JS based on the types of the expressions
- [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
- [x] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
- [x] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

### ⭐ Suggestion

TypeScript 5.5 added the [`@import`](https://devblogs.microsoft.com/typescript/announcing-typescript-5-5/#the-jsdoc-import-tag) JSDoc tag which can be used for type-only imports. It would be useful to add an analogous `@export` tag for type-only exports.

### 📃 Motivating Example

Let’s say you maintain a library that contains the following file:

```js
// types.js
/**
 * @typedef {string} Username
 */

/**
 * @typedef {number} UserId
 */
```

Maybe you want to expose these types in the main entry point. You can now do this with the JSDoc `@export` tag. It works the same as type-only exports in TypeScript files.

```js
// index.js
/**
 * @import { Username } from './types.js'
 */

/**
 * @export { Username }
 * @export { UserId } from './types.js'
 */
```

### 💻 Use Cases

This is useful to have full control over exports in a library. Also this is just parity between JSDoc based types and TypeScript files.

I can think of 3 workarounds, all of which are not great.

1. Define a new type in the index file using `@typedef`
   ```js
   // index.js
   /**
    * @typedef {import('./types.js').Username} Username
    * @typedef {import('./types.js').UserId} UserId
    */
   ```
   Pros:
     - It works

   Cons:
     - It defines a new type
     - Hover/autocompletion information is lost (#55572)
     - Type parameters must be redefined

2. In addition to `index.js`, create a TypeScript file, e.g. `exports.ts`. Then in `exports.ts` write something along the lines of:
   ```ts
   export { someValue, anotherValue } from './index.js'
   export { Username, UserId } from './types.js'
   ```
   and in `package.json`, write something like:
   ```json
   {
     "types": "./types/exports.d.ts",
     "exports": {
       "types": "./types/exports.d.ts",
       "default": "./lib/index.js",
     }
   }
   ```

   Pros:
     - It works
     - No new types are defined, but actual exports
     - Hover information is preserved
     - Type parameters are preserved

   Cons:
     - Exports from `index.js` need to be synced to `exports.ts` manually.
     - You’re essentially tricking TypeScript into thinking `exports.ts` is the main entry, whereas in reality it’s `index.js`

3. Manually write the declaration file.

   Pros:
     - It works
     - No new types are defined

   Cons:
     - You need to author the declaration files manually.
Repository: go
Issue: proposal: crypto: ignore rand io.Reader where behavior is not specified
Labels: Proposal,Proposal-Crypto

There are a few crypto APIs that take an `io.Reader` as a source of random bytes, but that don't commit to how those bytes are used. This caused issues over and over, for example any time we wanted to change the algorithm. These days we both document that they are not deterministic, and use `randutil.MaybeReadByte` to somewhat enforce it. See #58637.

Now that we have GODEBUGs, it might be time to rip the band-aid off. I propose we start ignoring the random `io.Reader` parameter of the following APIs, and always use the system random source (`crypto/internal/sysrand.Read`, *not* `crypto/rand.Reader` which may be overridden by the application).

* `rsa.GenerateKey` and `rsa.GenerateMultiPrimeKey`
* `rsa.EncryptPKCS1v15`
* `ecdsa.GenerateKey`
* `ecdsa.SignASN1`, `ecdsa.Sign`, and `ecdsa.PrivateKey.Sign`
* `ecdh.Curve.GenerateKey`

Using `GODEBUG=cryptocustomrand=1` restores the old behavior. (Suggestions for a better name welcome.) This is a GODEBUG that I would like to remove in a few releases.

`rsa.SignPKCS1v15` is not randomized, while `rsa.SignPSS` and `rsa.EncryptOAEP` have a fairly well-specified way to use random bytes. Aside from those and `ed25519.GenerateKey` (see below), I think I listed all APIs in non-deprecated packages that take a random `io.Reader`.

This might be an issue for the crypto/tls tests, which defuse `MaybeReadByte` by producing a stream of identical bytes. That's an abuse of GenerateKey anyway, because there is no guarantee that algorithms that expect random inputs will work with constant repeating streams. See for example #70643.

`ed25519.GenerateKey` is a weird exception in that it is well defined, but also documented to use `crypto/rand.Reader` if nil is passed. This is annoying because it forces a dependency on `crypto/rand` and therefore on `math/big`. We can't just use `crypto/internal/sysrand.Read` because the user might have overridden `crypto/rand.Reader`. I am tempted to also propose replacing "`crypto/rand.Reader`" with "the system random source" but it's probably not worth the risk.

/cc @golang/security
Repository: ant-design
Issue: Typography.Paragraph Ellipsis not consistent when using icon for expand/contract when within Row
Labels: unconfirmed

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/p/sandbox/antd-reproduction-template-forked-jyh2k9)

### Steps to reproduce

Include the ellipsis property for a Typography.Paragraph element with symbol set to provide icons for expanding/contracting the text and place the element within a Row tag

### What is expected?

It is expected that the element only ever takes up the number of rows specified and expands and contracts consistently.

### What is actually happening?

The shortened text is displayed correctly on initial render with icon appearing at the end of the row.  On expanding and then contracting the text, the contracted version changes to include more text and pushes the icon onto the next row.

| Environment | Info |
| --- | --- |
| antd | 5.22.5 |
| React | 18.3.1 |
| System | Windows 10 Enterprise 19045.5131 |
| Browser | Google Chrome 131.0.6778.205 |

---
The functionality is correct and consistent when no symbol is used (i.e. the default text is displayed to expand/contract)

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: deno
Issue: VSCode LSP Panic in Unsaved Jupyter Notebook
Labels: bug,deno jupyter,panic

Version: Deno 2.1.4

When I open a new Jupyter Notebook in VSCode by doing the following
- Open Command Palette (`Ctrl + Shift + P`) 
- Click `Create: New Jupyter Notebook`
- Select the `Deno` kernel

I get the following error messages

![image](https://github.com/user-attachments/assets/de6a264c-d639-4705-9cfb-fec481698324)

Here are the Deno Language Server logs

```
Starting Deno language server...
  version: 2.1.4 (release, x86_64-pc-windows-msvc)
  executable: C:\Users\Student\.deno\bin\deno.EXE
Connected to "Visual Studio Code" 1.96.2
Enabling import suggestions for: https://deno.land
Refreshing configuration tree...
  Resolved Deno configuration file: "file:///E:/Documents/AdventOfCode2024/deno.json"
  Resolved lockfile: "file:///E:/Documents/AdventOfCode2024/deno.lock"

============================================================
Deno has panicked. This is a bug in Deno. Please report this
at https://github.com/denoland/deno/issues/new.
If you can reliably reproduce this panic, include the
reproduction steps and re-run with the RUST_BACKTRACE=1 env
var set and include the backtrace in your report.

Platform: windows x86_64
Version: 2.1.4
Args: ["C:\\Users\\Student\\.deno\\bin\\deno.EXE", "lsp"]

thread 'main' panicked at C:\a\deno\deno\resolvers\node\package_json.rs:88:41:
called `Option::unwrap()` on a `None` value
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
[Error - 1:50:08 PM] Client Deno Language Server: connection to server is erroring. Shutting down server.
[Error - 1:50:08 PM] Connection to server got closed. Server will not be restarted.
[Error - 1:50:08 PM] Stopping server failed
  Message: Pending response rejected since connection got disposed
  Code: -32097 
[Error - 1:50:08 PM] Stopping server failed
  Message: Pending response rejected since connection got disposed
  Code: -32097 
Error retrieving config tasks: Error: Client is not running
```

**NB: This only happens when the Notebook is UNSAVED. It works correctly on saved files when there is a deno.json file in the same directory.**
Repository: ant-design
Issue: Make XXXL breakpoint available from Grid.useBreakpoint
Labels: unconfirmed

### What problem does this feature solve?

XXXL breakpoint has been introduced for the Grid in 2022 in the following PR but isn't available from Grid.useBreakpoint hook.

The commit that introduced XXXL breakpoint https://github.com/ant-design/ant-design/pull/39105/commits/ee3fb62f9b5df949a898eb96db7c7f6cf5daeb1b

### What does the proposed API look like?

The same as today `useBreakpoint()` should return `xxxl` as a boolean such as:

```ts
const { xxxl } = useBreakpoint();
```

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: vscode
Issue: Let's stop using Icons for Secondary Sidebar views
Labels: under-discussion,layout,workbench-views,workbench-auxsidebar,workbench-copilot

Icons make the Copilot Edits view not discoverable.

Right now

![Image](https://github.com/user-attachments/assets/708a2d64-ab30-48cf-9ae3-19ef4603c49e)

My proposal

![Image](https://github.com/user-attachments/assets/9cbf7de9-c221-4f64-be1f-5c8063fe3644)

Code pointer to change (`true` to `false`) https://github.com/microsoft/vscode/blob/main/src/vs/workbench/browser/parts/auxiliarybar/auxiliaryBarPart.ts#L162

What do you think? I am happy to provide a PR to change this.

Along with this it would be good if we change "Chat" -> "Copilot Chat"

fyi @roblourens @pierceboggan
Repository: angular
Issue: Export @defer typescript primitives for use in component codebehind
Labels: area: core,core: defer

### Which @angular/* package(s) are relevant/related to the feature request?

core

### Description

The `@defer` syntax is great, but the some of the triggers would also be useful in typescript, such as via a decorator to call a typescript function.

I have a lazy-loaded component that is fetched via the `async import` in my typescript, which is fed into a dynamic dialog service. This should follow the same logic/heuristics as the template-based defer, and I would love to be able to reuse:
* [`IdleScheduler`](https://github.com/angular/angular/blob/main/packages/core/src/defer/idle_scheduler.ts)
* [`TimerScheduler`](https://github.com/angular/angular/blob/main/packages/core/src/defer/timer_scheduler.ts)

It'd be great if somehow the dom triggers could also be considered.

### Proposed solution

Minimal: export `IdleScheduler` and `TimerScheduler` from `@angular/core`
Best: create and provide a `@defer` decorator that can be used from TypeScript code that works with all the same functionality as the `@defer` block in templates

### Alternatives considered

I can re-implement what I need in user-land, but would prefer to reuse Angular internals for consistency.
Repository: material-ui
Issue: [docs][Alert] Missing root slot for style customization
Labels: docs,component: alert

### Summary

Currently, the `MuiAlert` component does not support the `paper` slot for direct styling customization int the theme file. Other MUI components, such as `MuiAutocomplete`, use the `slotProps` API to allow passing specific props to subcomponents like `paper`. Adding support for this in `MuiAlert` would simplify the application of custom `Paper` variants and other styles directly to the alert’s underlying `Paper` element.

### Examples

```
MuiAlert: {
  defaultProps: {
    slotProps: {
      paper: {
        variant: 'overlay',  // Apply the overlay variant directly to the paper slot
      },
    },
  },
  styleOverrides: {
    // Default styles for MuiAlert can still be used
  },
}

```

### Motivation

1. Simplified Styling: Currently, developers need to override `styleOverrides` to apply specific styles such as custom `Paper` variants. Introducing the `paper` slot would allow this styling to be applied more easily through the `slotProps` API, similar to other components like `MuiAutocomplete`. This would streamline styling customization and reduce the need for manual overrides.
2. Consistency with Other Components: Other components in MUI, such as `MuiAutocomplete`, support the `slotProps` API to customize internal elements (e.g., `paper`). Adding this capability to `MuiAlert` would align the API across different MUI components, enhancing consistency and developer experience.
3. Improved Maintainability: By allowing developers to pass props directly to the `paper` element (e.g., `variant`: 'overlay'), this approach reduces the need for duplicate code and manual style overrides, making the codebase easier to maintain and less prone to errors.

**Search keywords**: alert, slot, defaultProps, paper variant
Repository: godot
Issue: BoneAttachment3D doesn't update position / rotation of attachment correctly
Labels: bug,needs testing,topic:animation

### Tested versions

Reproducible in 4.4Dev-5, 4.4Dev-7

### System information

Godot v4.4.dev7 - Manjaro Linux #1 SMP PREEMPT_DYNAMIC Tue Oct  8 03:24:49 UTC 2024 on X11 - X11 display driver, Multi-window, 1 monitor - Vulkan (Mobile) - integrated Intel(R) HD Graphics 4600 (HSW GT2) - Intel(R) Core(TM) i7-4700HQ CPU @ 2.40GHz (8 threads)

### Issue description

if I move around or look around the attachment doesn't follow correctly if I force it it looks it attached correctly with slight off how it should be

### Steps to reproduce

simply play the project and look around and move around

the arrow will move not as it should
if you comment the IProjectile the else statement it moves even weirder

### Minimal reproduction project (MRP)

I couldn't get MRP less than 10MB because the FBX files were large enough
and they are essential for the MRP

[MRP](https://drive.proton.me/urls/CT1T16RYM4#K1FdBXektiPR)
Repository: PowerToys
Issue: PowerToys 0.87.1-x64 does not install
Labels: Issue-Bug,Area-Setup/Install,Needs-Triage,Needs-Team-Response

### Microsoft PowerToys version

0.87.1

### Installation method

GitHub

### Running as admin

Yes

### Area(s) with issue?

Installer

### Steps to reproduce

Attempted to install PowerToys as Admin and received a popup message that it could not be installed as the previous version must be uninstalled first. I tried to uninstall PowerToys with Control Panel - Programs and Features and got the same popup. I then used Iobit Uninstaller to remove it and all residual files, then rebooted the PC. The same error window came up when attempting to install PowerToys 0.87.1 and 0.87![Image](https://github.com/user-attachments/assets/36036dcc-0341-474c-b031-8a235af3e7b5)


### ✔️ Expected Behavior

Expected PowerToys to update as usual.

### ❌ Actual Behavior

Unable to update or install PowerToys

### Other Software

_No response_