sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: Middleware called redirect but the browser is not redirected
Labels: bug,Middleware

### Link to the code that reproduces this issue

https://github.com/kuanjiahong/nextjs-middleware-redirect-issue-demo

### To Reproduce

1. npm run dev
2. Go to http://localhost:3000
3. Click "Go to Dashboard" on "/" page
4. Click "Set Session Cookie" on "/set-cookie" page
5. Click "Go to Dashboard" on "/" page
6. Click "Remove Session" on "/dashboard" page
7. Click "Call Server Action" on "/dashboard" page

### Current vs. Expected behavior

**Current behavior**
After clicking "Remove Session" and then clicking "My Server Action", the page is not redirected to "/set-cookie" page

**Expected behaviour**
After clicking "Remove Session" and then clicking "My Server Action", the page should be redirected to "/set-cookie" page


### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Home
  Available memory (MB): 16086
  Available CPU cores: 8
Binaries:
  Node: 22.11.0
  npm: 10.9.0
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 15.0.4-canary.27 // Latest available version is detected (15.0.4-canary.27).
  eslint-config-next: N/A
  react: 19.0.0-rc-b01722d5-20241114
  react-dom: 19.0.0-rc-b01722d5-20241114
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


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

Middleware

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

next dev (local), next start (local)

### Additional context

I tested my reproduction on 15.0.4-canary.27 and also 15.0.3. The issues are reproduceable for both of these version.
Repository: vscode
Issue: Let language extensions dynamically configure soft word wrap for long lines
Labels: feature-request,editor-wrapping

<!-- ⚠️⚠️ 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. -->

VS Code currently offers a word wrap option, which breaks lines at a certain fixed length in the editor UI. This works fine, but is intended mainly for written text/comments/markdown and doesn't take language syntaxes into account. The feature isn't very highly used, probably by design.

There are also language-specific autoformatters that understand syntax and do hard line breaks. This is the better option for clearer and more understandable code, and so is very commonly used across most codebases (e.g. using Prettier and/or built-in linters). The drawback is that because the formatting changes are written to disk, the same line length setting must apply to everyone working in a repo regardless of their monitor size and personal preferences.

There's a possible solution that combines both of these by letting custom formatters provide both a hard break (`\n`) _and_ a soft break signal to the editor. The word wrap setting thus doesn't have to be static for the entire editor but can be automatically set per file and per line. The lines themselves can be arbitrarily long on disk, and each end user can configure their own view depending on their setup.

Additional advantages include:
- No surprise formatting of the entire file when changing one line because someone else committed without running the formatter.
- Significantly cleaner diffs.
- Fewer fights between devs working on the same codebase.
Repository: vscode
Issue: Indicate that version property should not be used for reporting telemetry
Labels: debt,telemetry

I have been using version property name to report the version on an extension in my telemetry event and I discovered that this property name is reserved for product version. It would be helpful if there is some indication that this property is reserved and cannot be used.
Repository: go
Issue: x/tools/gopls: "slice bounds out of range" crash in ExtractToNewFile
Labels: NeedsInvestigation,gopls,Tools,gopls/telemetry-wins

```
#!stacks
"goPanicSliceAcap" &&
 ("golang.ExtractToNewFile:+72" || "golang.ExtractToNewFile:+98")
```
Issue created by [stacks](https://pkg.go.dev/golang.org/x/tools/gopls/internal/telemetry/cmd/stacks).

```go
	fileStart := pgf.File.FileStart
	buf.Write(pgf.Src[start-fileStart : end-fileStart]) // slice bounds out of range
```
This stack `fFKP7w` was [reported by telemetry](https://storage.googleapis.com/prod-telemetry-merged/2024-11-22.json):

- `crash/crash`
- [`runtime.gopanic:+69`](https://cs.opensource.google/go/go/+/go1.23.3:src/runtime/panic.go;l=804)
- [`runtime.goPanicSliceAcap:+2`](https://cs.opensource.google/go/go/+/go1.23.3:src/runtime/panic.go;l=141)
- [`golang.org/x/tools/gopls/internal/golang.ExtractToNewFile:+72`](https://cs.opensource.google/go/x/tools/+/gopls/v0.17.0-pre.2:gopls/internal/golang/extracttofile.go;l=155)
- [`golang.org/x/tools/gopls/internal/server.(*commandHandler).ExtractToNewFile.func1:+1`](https://cs.opensource.google/go/x/tools/+/gopls/v0.17.0-pre.2:gopls/internal/server/command.go;l=1139)
- [`golang.org/x/tools/gopls/internal/server.(*commandHandler).run.func2:+3`](https://cs.opensource.google/go/x/tools/+/gopls/v0.17.0-pre.2:gopls/internal/server/command.go;l=381)
- [`golang.org/x/tools/gopls/internal/server.(*commandHandler).run:+77`](https://cs.opensource.google/go/x/tools/+/gopls/v0.17.0-pre.2:gopls/internal/server/command.go;l=412)
- [`golang.org/x/tools/gopls/internal/server.(*commandHandler).ExtractToNewFile:+1`](https://cs.opensource.google/go/x/tools/+/gopls/v0.17.0-pre.2:gopls/internal/server/command.go;l=1135)
- [`golang.org/x/tools/gopls/internal/protocol/command.Dispatch:+81`](https://cs.opensource.google/go/x/tools/+/gopls/v0.17.0-pre.2:gopls/internal/protocol/command/command_gen.go;l=199)
- [`golang.org/x/tools/gopls/internal/server.(*server).ResolveCodeAction:+21`](https://cs.opensource.google/go/x/tools/+/gopls/v0.17.0-pre.2:gopls/internal/server/code_action.go;l=247)
- [`golang.org/x/tools/gopls/internal/protocol.serverDispatch:+46`](https://cs.opensource.google/go/x/tools/+/gopls/v0.17.0-pre.2:gopls/internal/protocol/tsserver.go;l=216)
- [`golang.org/x/tools/gopls/internal/lsprpc.(*streamServer).ServeStream.ServerHandler.func3:+5`](https://cs.opensource.google/go/x/tools/+/gopls/v0.17.0-pre.2:gopls/internal/protocol/protocol.go;l=160)
- [`golang.org/x/tools/gopls/internal/lsprpc.(*streamServer).ServeStream.handshaker.func4:+52`](https://cs.opensource.google/go/x/tools/+/gopls/v0.17.0-pre.2:gopls/internal/lsprpc/lsprpc.go;l=509)
- [`golang.org/x/tools/gopls/internal/protocol.Handlers.MustReplyHandler.func1:+2`](https://cs.opensource.google/go/x/tools/+/gopls/v0.17.0-pre.2:internal/jsonrpc2/handler.go;l=35)
- [`golang.org/x/tools/gopls/internal/protocol.Handlers.AsyncHandler.func2.2:+3`](https://cs.opensource.google/go/x/tools/+/gopls/v0.17.0-pre.2:internal/jsonrpc2/handler.go;l=104)
- `runtime.goexit:+0`
```
golang.org/x/tools/gopls@v0.17.0-pre.2 go1.23.3 linux/amd64 vscode (3)
```
Dups: VdbNJw
Repository: godot
Issue: Shortcut to restart particles doesn't work when multiple particle systems are selected
Labels: topic:editor,topic:particles

### Tested versions

4.3-stable

### System information

Windows

### Issue description

Seleting multiple particle systems disables the shortcut to restart them doens't work

### Steps to reproduce

Open mrp, open node3d scene. Select a single particle node, hit ctrl+r, observe it restart
Select the two particle nodes, hit ctrl+r, nothing happens.

ctrl+r should call restart() on all particles in the current open scene

### Minimal reproduction project (MRP)

[particle-shortcut-mrp.zip](https://github.com/user-attachments/files/17906500/particle-shortcut-mrp.zip)
Repository: deno
Issue: Deno.dlopen cannot open static asset
Labels: feat,compile

Version: Deno 2.1.1

I tried to bundle my native library and script into a single executable file. Of course, I used the --include flag during compilation. After running the executable, I found that Deno.readFile successfully reads the static asset, but Deno.dlopen is unable to open it. Below is an example of the code:

```ts
const data = Deno.readFileSync(
  import.meta.dirname + "/static/libexample.dylib",
);

console.log(data.buffer.byteLength); // return correct size 1955522

const lib = Deno.dlopen(
  import.meta.dirname + "/static/libexample.dylib",
  {
    openWebView: {
      parameters: [],
      result: "void",
      nonblocking: false,
    },
  },
); // but Error: Could not open library: Could not open library

```
Repository: vscode
Issue: Feature Request: Enhance Edit > Find to a dropdown list
Labels: feature-request,editor-find

<!-- ⚠️⚠️ 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. -->
Enhance Edit > Find to a dropdown list

I constantly use Edit > Find with two or three requests again and again. 
It would be great to have The edit > Find textbox enhanced to a dropdown list
of the last five entries. That way, one could simply select the search option from current history.
Copy / Paste doesn't really work when you're working between multiple search options and editing code.

Thanks!

Visual Studio Code
Version: 1.95.3
Repository: PowerToys
Issue: FancyZones - zones created will shift up the height of the taskbar and then shift back down
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.86.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

FancyZones, FancyZones Editor

### Steps to reproduce

Usually on reboot but sometimes I'll go to move a window into a zone and notice that I've got one of two situations appearing - either windows will be behind the taskbar or they will be exactly twice the distance from the bottom of the screen (two taskbar lengths). I have taken to creating two versions of the same layout, one "low" and one "high" that compensate for whichever version of this bug is rearing its head. At one point I had my taskbar set to auto-hide (I have an OLED monitor) but now have it set to static and that's when I first noticed the problem but ever since the bug has haunted me.
![Image](https://github.com/user-attachments/assets/576c7b66-6778-45cb-9fe1-67243258bb69)



### ✔️ Expected Behavior

I expect my zones to all stay where I intended them to be when I first set them up but I've been stuck with this bug for so long that I actually anticipate it happening and have two versions of my FZ layout set up to compensate.

### ❌ Actual Behavior

Zones shift up or down based on how the computer is feeling that day (I honestly can't tell what the trigger is, it seems arbitrary). I have two versions of the same layout that compensate for my computer's mood. Taskbar is currently set to always show, so my desktop remains static and unchanging but Fancy Zones is kind of temperamental about it.

### Other Software

_No response_
Repository: go
Issue: x/tools: Windows build OOM crash
Labels: NeedsInvestigation,Tools

```
#!watchflakes
default <- pkg == "golang.org/x/tools/go/callgraph/vta" && test == "" && goos == "windows"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8730352753718672849)):

    PASS
    ok  	golang.org/x/tools/go/callgraph/vta	14.936s


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: react-native
Issue: RN 0.76: std::__1::bad_function_call
Labels: Needs: Author Feedback,Needs: Repro

### Description

After upgrading to RN 0.76.x the iOS app started crashing.

### Steps to reproduce

1. Build & start

### React Native Version

0.76.3

### Affected Platforms

Runtime - iOS

### Output of `npx react-native info`

```text
System:
  OS: macOS 15.1.1
  CPU: (12) arm64 Apple M2 Max
  Memory: 813.77 MB / 96.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 20.18.0
    path: ~/.nvm/versions/node/v20.18.0/bin/node
  Yarn:
    version: 1.22.19
    path: /opt/homebrew/bin/yarn
  npm:
    version: 10.8.2
    path: ~/.nvm/versions/node/v20.18.0/bin/npm
  Watchman:
    version: 2024.11.04.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.16.2
    path: /opt/homebrew/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 24.0
      - iOS 18.0
      - macOS 15.0
      - tvOS 18.0
      - visionOS 2.0
      - watchOS 11.0
  Android SDK:
    API Levels:
      - "34"
      - "35"
    Build Tools:
      - 34.0.0
      - 35.0.0
    Android NDK: Not Found
IDEs:
  Android Studio: 2024.2 AI-242.23339.11.2421.12550806
  Xcode:
    version: 16.0/16A242d
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 23.0.1
    path: /opt/homebrew/opt/openjdk/bin/javac
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli":
    installed: 15.1.2
    wanted: ^15.1.2
  react:
    installed: 18.3.1
    wanted: 18.3.1
  react-native:
    installed: 0.76.3
    wanted: 0.76.3
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: true
```


### Stacktrace or Logs

```text
2024-11-25 20:35:31.281 requestAuthorizationWithOptions: granted nil
2024-11-25 20:35:31.830 applicationDidBecomeActive
2024-11-25 20:35:31.877 PushCredentials: AF703A956C2754F369DAE139A99C9A6E887EF3DC81FB7D55B29732**********
2024-11-25 20:35:36.088 Device token: 32 bytes
libc++abi: terminating due to uncaught exception of type std::__1::bad_function_call: std::exception
```


### Reproducer

https://github.com/react-native-community/reproducer-react-native

### Screenshots and Videos

<img width="1706" alt="Screenshot 2024-11-25 at 20 46 33" src="https://github.com/user-attachments/assets/c13a72ec-478e-4659-abf0-9724d407b20f">

<img width="351" alt="Screenshot 2024-11-25 at 20 47 10" src="https://github.com/user-attachments/assets/eccb025b-7ea1-4c1a-bc8e-282a194d1c94">
Repository: go
Issue: runtime: make Windows VirtualAlloc failure more informative
Labels: help wanted,OS-Windows,NeedsInvestigation,compiler/runtime

When a Windows build fails due to OOM, the error log looks like this:
https://logs.chromium.org/logs/golang/buildbucket/cr-buildbucket/8730352753718672849/+/u/step/19/log/2
It contains a thread dump of the go test command at the moment after VirtualAlloc failed, but I suspect the real culprits here are the test child processes, among which is x/tools/go/ssa, which is known to have a big appetite for memory. Unfortunately that information is somewhat obscure in the log.

The task of this issue is to consider whether there are ways that the Windows OOM crash could be made more informative, for example by including the committed size of the current process. Alternatively, whether there are changes we could make to go test or the builders that would point the finger of blame more clearly.

@prattmic
Repository: opencv
Issue: cap_aravis: support specifying device by GUID/name
Labels: feature,category: videoio(camera)

### Describe the feature and motivation

currently when using aravis you have to specify the ID of the device:
https://github.com/opencv/opencv/blob/65d4112fa52511cd609a5c794a263bee9b5a8d43/modules/videoio/src/cap_aravis.cpp#L206-L225

it'd be much more usable if it were possible to specify the GUID (aka device name) to then pass that on to `arv_camera_new`.

a workaround might be to manually use Aravis to find the ID of the device (by looping over them and filtering for the GUID) and then pass that to OpenCV (which then loops over the same list again, filtering by ID to get the GUID...).

### Additional context

other Aravis-based tools always use the GUID, e.g. [`camera_aravis2` in ROS 2](https://github.com/FraunhoferIOSB/camera_aravis2/blob/468637ef1b76172ca69c3c47b09778829a3ccbda/camera_aravis2/src/camera_aravis_node_base.cpp#L133)
Repository: vscode
Issue: icon is not colored correctly for failing task terminal
Labels: bug,tasks,terminal-tabs

![Image](https://github.com/user-attachments/assets/fad07903-bda5-4265-b4eb-8c50d3778b4e)
Repository: opencv
Issue: cap_aravis: no image when not explicitly specifying `cv::CAP_PROP_FOURCC`
Labels: bug,category: videoio

### System Information

OpenCV version: 4.10.0 (with `HAVE_ARAVIS`!)
OS: Ubuntu 24.04 (in WSL 2)
Compiler: CLang 18.1.8
camera & driver from [get cameras / VAimaging / Daheng Imaging](https://www.get-cameras.com/)

### Detailed description

when creating a new Aravis `cv::VideoCapture` the image will be empty unless `cv::CAP_PROP_FOURCC` is specified (and _just the right kind_).

this is because `CvCaptureCAM_Aravis::retrieveFrame` only runs if one of four pixel formats is set:
https://github.com/opencv/opencv/blob/65d4112fa52511cd609a5c794a263bee9b5a8d43/modules/videoio/src/cap_aravis.cpp#L321-L334
and it seems that this setting is not kept over camera restarts (i had the camera working just fine using the manufacturer-provided GUI).

### Steps to reproduce

prerequisites:
* USB3 VISION camera or GigE VISION camera (admittedly not something you might just have lying around at home; note that these are *not* normal USB webcams)
* [aravis](https://github.com/AravisProject/aravis) installed
* camera-specific drivers installed (needed so that aravis & co. can see the genIcam API of the USB3/GigE VISION cameras)

1. compile OpenCV with `HAVE_ARAVIS`
2. run the following code:

```cpp
#include <iostream>
#include <opencv2/opencv.hpp>

int main() {
    cv::VideoCapture cap{0, cv::CAP_ARAVIS, {
        cv::CAP_PROP_ARAVIS_AUTOTRIGGER, 1,
        cv::CAP_PROP_AUTO_EXPOSURE, 1,
//        cv::CAP_PROP_FOURCC, cv::VideoWriter::fourcc('G','R','E','Y')
    }};

    if (!cap.isOpened()) {
        std::cerr << "failed to open the camera!" << std::endl;
        return 1;
    }

    uint8_t retry = 0;
    while (true) {
        cv::Mat frame;
        cap >> frame;

        if (frame.empty()) {
            ++retry;
            if (retry > 10) {
                std::cerr << "failed to get a frame 10 consecutive times!" << std::endl;
                return 1;
            }
            continue;
        } else {
            retry = 0;
        }

        cv::imshow("Frame | press q to quit", frame);

        auto key = cv::waitKey(1);
        switch (key) {
            case 'f':
                flip = !flip;
                break;
            case 'q':
                return 0;
            default:
                break;
        }
    }
}
```

with `cv::CAP_PROP_FOURCC` commented out it will fail since all frames are empty. once you uncomment that line it'll start working.

### Issue submission checklist

- [X] I report the issue, it's not a question
- [X] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [X] I updated to the latest OpenCV version and the issue is still there
- [X] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: storybook
Issue: [Bug]: Import Absolute Path in MDX files using Blocks
Labels: bug,mdx

### Describe the bug

I want to use an absolute path alias instead of a relative path in the MDX file for the documentation.

I have this `button.mdx` file:

```mdx
import { Meta, Canvas } from '@storybook/blocks'
import * as ButtonStories from './button.stories'
import * as DropdownButtonStories from '../../dropdown-button/dropdown-button.stories'
import { Typography } from '../../../components'


<Meta of={ButtonStories} />

....

<Typography variant="heading" fontSize={300} fontWeight={400}>
 Related Components
</Typography>

<Canvas
 of={DropdownButtonStories.Default}
/>
``` 

I would like to know if it is possible to use it like this:

```mdx

import { Meta, Canvas } from '@storybook/blocks'
import * as ButtonStories from './button.stories'
import * as DropdownButtonStories from 'components/dropdown-button/dropdown-button.stories'
import { Typography } from 'components'

<Meta of={ButtonStories} />

....

<Typography variant="heading" fontSize={300} fontWeight={400}>
 Related Components
</Typography>

<Canvas
 of={DropdownButtonStories.Default}
/>
``` 

I tried with modification of the main.js file, but it doesn't work: 

```javascript
  async viteFinal(config) {
    return mergeConfig(config, {
      resolve: {
        alias: {
          'components': resolve(__dirname, '../src/components'),
        },
      },
      plugins: [tsconfigPaths()],
    })
  },
``` 

The following error occurs:

![Image](https://github.com/user-attachments/assets/6c9b1ef8-ca4e-41b1-933f-d1df2f8f8f73)






### Reproduction link

https://stackblitz.com/edit/github-xgzeyx?file=vite.config.ts

### Reproduction steps

_No response_

### System

```bash
I'm using Storybook v8.4.2
```

### Additional context

_No response_
Repository: terminal
Issue: x-markdown - right click Select All crashes
Labels: Issue-Bug,Area-UserInterface,Severity-Crash,Product-Terminal

### Steps to reproduce

Load up a markdown document in an `x-markdown` pane. Right click the body text and Select All.

### Actual Behavior

It blow up
Repository: TypeScript
Issue: Dynamically importing JSON should require import attribute with node16/nodenext
Labels: Needs Investigation,Fix Available

### 🔎 Search Terms

dynamic import, import attribute, resolveJsonModule, 

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about [TS 5.7's new checks around importing JSON](https://devblogs.microsoft.com/typescript/announcing-typescript-5-7/)

### ⏯ Playground Link

https://github.com/kirkwaiblinger/repro-TS-dynamic-json-import-validation

### 💻 Code

```ts
// module: node16/nodenext, resolveJsonModule
// .cts or .mts, it doesn't matter.

async function main() {
    const somethingDynamic = await import('./someThing.json');
    console.log('dynamically imported JSON:', somethingDynamic);
}

main();

export {}
```


### 🙁 Actual behavior

No error, even though this is a runtime error in nodejs.

### 🙂 Expected behavior

Error because dynamic [`import('./someThing.json')` requires import attribute](https://nodejs.org/api/esm.html#json-modules).

### Additional information about the issue

Unlike the static import case, this is the case for _both_ commonjs and esm outputs, since [`import()` is available in commonjs modules in node](https://nodejs.org/api/esm.html#import-expressions) and has the same semantics there as the ESM import (and therefore TS doesn't transform the `import()` statement to a `Promise.resolve(require())`).