sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Glitching happens when the camera moves continuously, on sprites or ColorRects with hard edges
Labels: topic:rendering,documentation,topic:2d

### Tested versions

Reproducible in 4.2.2

### System information

Godot v4.2.2.rc (2fdeeead5) - Windows 10.0.22621 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 2060 SUPER (NVIDIA; 31.0.15.3713) - Intel(R) Core(TM) i9-14900KF (32 Threads)

### Issue description

When camera moves continuously(for example, moved by the position of mouse cursor), any sprite or colorrect start glitching obviously.
![glitch](https://github.com/godotengine/godot/assets/38549764/6b0f0813-a5a6-4b4a-b63e-8e5d1bf8b0ec)
Currently, My way to fix this is use a "pre-rendered" soft edge rect, with several pixels of blur edge. (It performs like below)
![temp_solution](https://github.com/godotengine/godot/assets/38549764/d3de079e-1369-428b-b3a2-3c2e5a82b1d0)
![屏幕截图 2024-05-14 203329](https://github.com/godotengine/godot/assets/38549764/6a41f23e-346b-4fce-87b1-a97e98c9bd4b)

I am curious if any one can make "build-in linear render" possible.

### Steps to reproduce

Here is the "pre-rendered" sprite:
![rect_blur_edge](https://github.com/godotengine/godot/assets/38549764/2626a294-32de-4267-bbe8-fbbb194f451d)

### Minimal reproduction project (MRP)

N/A
Repository: vscode
Issue: Port is being added twice to Microsoft dev tunnel in VsCode with absolute URLs
Labels: bug,remote-tunnel

<!-- ⚠️⚠️ 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: 
- OS Version: 

I am working with the NextJs framework, where I have a link that redirect the users to it in my App. The link works well with the local machine, yet when I use the de tunnel, it adds the port twice to the URL, and it does not work. 

Here is my JS code: 

```js
 function redirectToLogin(locale: string) {
    return NextResponse.redirect(
      new URL(`/${locale}/login`, hostURL)
    );
  }
```

Here is the result that I got from the dev tunnels: 

```bash
https://k630pqpg-3000.euw.devtunnels.ms:3000/tr/login
```

Here is what I expect: 

Either
```bash
https://k630pqpg-3000.euw.devtunnels.ms/tr/login
```
Or
```bash
https://k630pqpg.euw.devtunnels.ms:3000/tr/login
```

My workaround to solve this was to modify the URL by hand, yet it would be great to fix this bug or know a permanent solution. (thanks to this issue for getting the workaround (https://github.com/microsoft/vscode/issues/190020))

Is there a way to define the URL that I got from the dev tunnels? or fix that duplicate port issue?


```[tasklist]
### Tasks
```
Repository: tauri
Issue: [bug] Android os error 2 with sidecar
Labels: type: bug,status: needs triage,platform: iOS,platform: Android

### Describe the bug

**Error**: Uncaught (in promise) No such file or directory (os error 2)
**Event**: Command.sidecar("bin/pipy", args)  ...call sidecar
**Sidecar position:** src-tauri/bin/pipy-aarch64-linux-android
**Sidecar package** position: src-tauri/target/aarch64-linux-android/debug/pipy
**Sidecar bundle:** tauri.conf.json => bundle > "externalBin": ["bin/pipy"]

Simply put, I saw that the sidecar had been packaged in a reasonable location, but when running on the Android emulator, I couldn't find the file. What I can confirm is that other programs can run as usual, and on Mac OS and Windows, my sidecar still works as usual, but it can't be found on the Android emulator

Here is my Cargo.toml configuration：
```toml
[lib]
name = "ztm_lib"
crate-type = ["lib", "cdylib", "staticlib"]

[build-dependencies]
tauri-build = { version = "2.0.0-beta", features = [] }

# tauri = { version = "2.0.0-beta", features = ["devtools"] }
[dependencies]
fix-path-env = { git = "https://github.com/tauri-apps/fix-path-env-rs" }
tauri = { version = "=2.0.0-beta.19", features = [] }
tauri-plugin-shell = "2.0.0-beta.4"
serde = { version = "1", features = ["derive"] }
serde_json = "1"
tauri-plugin-process = "2.0.0-beta.3"
tauri-plugin-http = "2.0.0-beta.3"
tauri-plugin-os = "2.0.0-beta.3"
tauri-plugin-fs = "=2.0.0-beta.7"

[target."cfg(not(any(target_os = \"android\", target_os = \"ios\")))".dependencies]
tauri-plugin-cli = "2.0.0-beta"

[target.'cfg(any(target_os = "android"))']
linker = "~/Library/Android/sdk/ndk/27.0.11718014/toolchains/llvm/prebuilt/darwin-x86_64/bin"
```

### Reproduction

_No response_

### Expected behavior

_No response_

### Full `tauri info` output

```text
[✔] Environment
    - OS: Mac OS 12.0.1 X64
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.77.0 (aedd173a2 2024-03-17)
    ✔ cargo: 1.77.0 (3fe68eabf 2024-02-29)
    ✔ rustup: 1.27.0 (bbb9276d2 2024-03-08)
    ✔ Rust toolchain: stable-aarch64-apple-darwin (default)
    - node: 21.7.1
    - pnpm: 8.10.5
    - yarn: 1.22.17
    - npm: 6.14.17

[-] Packages
    - tauri [RUST]: 2.0.0-beta.19
    - tauri-build [RUST]: 2.0.0-beta.15
    - wry [RUST]: 0.39.5
    - tao [RUST]: 0.28.0
    - @tauri-apps/api [NPM]: 2.0.0-beta.11
    - @tauri-apps/cli [NPM]: 2.0.0-beta.17

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../../agent/gui
    - devUrl: http://localhost:1420/
    - framework: Vue.js
    - bundler: Vite
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: storybook
Issue: [Bug]: @storybook/blocks > `<Canvas>` > 'Show code' doesn't display props that have `false`
Labels: bug,react,block: source,sev:S2

### Describe the bug

A component with boolean prop `<Button isInvalid>` and `<Button isInvalid={false}>` relies on `Canvas` from `@storybook/blocks` to auto-generate code example needed for users to copy/paste.

For `<Button isInvalid />` generated code example is:
`<Button isInvalid />`

For `<Button isInvalid={false} />` generated code example is:
`<Button />`
but it should be
`<Button isInvalid={false} />`


### To Reproduce

https://stackblitz.com/edit/github-ehbp3d?file=src%2Fstories%2FButton.tsx,src%2Fstories%2FButton.stories.ts,src%2Fstories%2FConfigure.mdx&preset=node

### System

```bash
Storybook Environment Info:
(node:26201) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)

  System:
    OS: macOS 14.4.1
    CPU: (10) arm64 Apple M1 Pro
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.1.0 - /opt/homebrew/bin/node
    Yarn: 4.1.1 - /opt/homebrew/bin/yarn <----- active
    npm: 10.7.0 - /opt/homebrew/bin/npm
  Browsers:
    Chrome: 124.0.6367.207
    Safari: 17.4.1
  npmPackages:
    @storybook/addon-a11y: ^8.1.0 => 8.1.0 
    @storybook/addon-docs: ^8.1.0 => 8.1.0 
    @storybook/addon-essentials: ^8.1.0 => 8.1.0 
    @storybook/addon-webpack5-compiler-babel: ^3.0.3 => 3.0.3 
    @storybook/blocks: ^8.1.0 => 8.1.0 
    @storybook/manager-api: ^8.1.0 => 8.1.0 
    @storybook/react: ^8.1.0 => 8.1.0 
    @storybook/react-webpack5: ^8.1.0 => 8.1.0 
    @storybook/theming: ^8.1.0 => 8.1.0 
    chromatic: ^11.3.0 => 11.3.0 
    msw-storybook-addon: ^2.0.0 => 2.0.0 
    storybook: ^8.1.0 => 8.1.0
```


### Additional context

_No response_
Repository: storybook
Issue: [Bug]: `summary: undefined` type issue
Labels: bug,good first issue,help wanted,typescript,sev:S4

### Describe the bug

Hello,
We are using storybook with Typescript. When trying to upgrade to v8.0.10, we encountered a type issue when we want to suppress the automatic `summary` generated for Controls. Previously, we would make it `null` like so:

```typescript
argTypes: {
  myArg: {
    table: {
      type: { summary: null },
    },
  },
},
```

With the change introduced at commit [3f7e1c2b84324ca24bc5bc968a6ab3245b11b757][0], `null` is no longer allowed. So we tried to use `undefined` instead. But since we use the stricter `exactOptionalPropertyTypes: true` configuration in our `tsconfig.json`, TypeScript raises the following error:

```log
Type '{ summary: undefined; }' is not assignable to type '{ summary?: string; detail?: string; }' with 'exactOptionalPropertyTypes: true'. Consider adding 'undefined' to the types of the target's properties.
  Types of property 'summary' are incompatible.
    Type 'undefined' is not assignable to type 'string'.(2375)
```

Could you please change the type of `summary` to `summary?: string | undefined` so that we can keep our strict settings as well as disable the summary in controls ?

[0]: https://github.com/storybookjs/storybook/compare/3f7e1c2b84324ca24bc5bc968a6ab3245b11b757%5E...3f7e1c2b84324ca24bc5bc968a6ab3245b11b757#diff-8bc72f33d4abe1b637206dbcd55cfab39fcdf51f27e1fbcf92aff021ea3730c2

### To Reproduce

Here is a link to reproduce: https://stackblitz.com/edit/github-wuwtca-dcgxst?file=src%2Fstories%2FButton.stories.ts

TypeScript raises an error in `src/stories/Button.stories.ts`, in `argTypes` property of `meta`.

### System

```bash
Storybook Environment Info:

  System:
    OS: Linux 6.8 Fedora Linux 40 (Workstation Edition)
    CPU: (12) x64 12th Gen Intel(R) Core(TM) i7-1255U
    Shell: 5.2.26 - /bin/bash
  Binaries:
    Node: 20.11.1 - /nix/store/lajyj1j3bkzcpiqra4phhs810zxglcp6-build-tools-js/bin/node
    pnpm: 8.7.0 - /nix/store/lajyj1j3bkzcpiqra4phhs810zxglcp6-build-tools-js/bin/pnpm <----- active
  npmPackages:
    eslint-plugin-storybook: ^0.8.0 => 0.8.0
```


### Additional context

_No response_
Repository: ant-design
Issue: Menu 中的 `inlineIndent` 缩进对 MenuGroupItem 不生效
Labels: Inactive,improvement

![image](https://github.com/ant-design/ant-design/assets/525658/f8cc5657-d35a-40f5-995f-c5c5d8660267)

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/p/sandbox/antd-reproduction-template-forked-kn26s4?file=%2Findex.js%3A91%2C7-91%2C25)

### Steps to reproduce

1. 对包含 group 类型 items 的 Menu 设置 `inlineIndent` 属性为 `100`

### What is expected?

分组标题也按 `inlineIndent` 的值分层缩进。

### What is actually happening?

分组的标题没有缩进。

| Environment | Info |
| --- | --- |
| antd | 5.17.2 |
| React | 18.0.0 |
| System | macOS 12 |
| Browser | Chrome 120 |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: vscode
Issue: When an extension uses a reserved participant name, the warning shows ExtensionID.participantID
Labels: under-discussion

1. Chat sample
2. Change it to contribute an "office" participant name
3. Notice all the warnings in the UI are showing `chat-sample` twice 🐛 

This is due to the fact that the warning shows `ExtensionID.participantID`

Should we instead show `ExtensionID.partipantName`?

Or we want to keep showing the `participantID`, maybe I should change the cat sample so the participant id is not `chat-sample.cat`, but just `cat`?

![Image](https://github.com/microsoft/vscode/assets/1926584/b699f8b4-ef20-41f3-ac93-1571eb48351a)



![Image](https://github.com/microsoft/vscode/assets/1926584/2d4d8080-b809-4f07-a15e-15e4d730048a)
Repository: transformers
Issue: Add data2vec 2.0
Labels: New model,Audio

### Model description

Hello,

The data2vec 2.0 paper has been released quite a while and achieved impressive performance across different modalities: speech, text, and image (results similar or better than data2vec 1.0 but much more efficient). Especially, the audio-only model seems to be one of the best SSL speech models using base architecture (93M parameters). Therefore, I think it would be a nice addition to the `transformers` library.

### Open source status

- [X] The model implementation is available
- [X] The model weights are available

### Provide useful links for the implementation

Paper: https://arxiv.org/abs/2212.07525
Code: https://github.com/facebookresearch/fairseq/tree/main/examples/data2vec
Authors: @alexeib @michaelauli @wnhsu
Repository: flutter
Issue: Flakes in GaussianBlurMipMapImageFilter and GaussianBlurMipMapNestedLayer
Labels: P1,e: impeller,team-engine,triaged-engine

https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8747956743136702833/+/u/test:_Host_Tests_for_host_debug/stdout

Both failed with:
```
[FATAL:flutter/impeller/base/validation.cc(57)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create render pipeline for TextureFill Pipeline :Compiler encountered an internal error
```
Repository: angular
Issue: ngsp is not working properly with control flow syntax
Labels: area: compiler,core: control flow

### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

Yes

### Description

The following template uses `*ngIf` and generates 2 span elements with a space between them:

```html
  <div id="ng-if">
    <span *ngIf="true">Hello</span>
    &ngsp;
    <span *ngIf="true">World</span>
  </div>
```

This results in `<span>Hello</span> <span>World</span>`, which is expected


When running the control flow migration, we end up with this template:
```html
  <div id="if-outside">
      @if (true) {<span>Hello</span>}
      &ngsp;
      @if (true) {<span>World</span>}
  </div>
```

which results in this HTML, with no space: `<span>Hello</span><span>World</span>`.

It looks like the `&ngsp;` is ignored by the control-flow syntax.

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz-starters-hzrodb?file=src%2Fmain.ts

### Please provide the exception or error you saw

_No response_

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI: 17.3.7
Node: 18.20.1
Package Manager: npm 9.7.1
OS: darwin arm64

Angular: 17.3.8
... animations, cdk, common, compiler, compiler-cli, core, forms
... localize, platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1703.7
@angular-devkit/build-angular   17.3.7
@angular-devkit/core            17.3.7
@angular-devkit/schematics      17.3.7
@angular/cli                    17.3.7
@schematics/angular             17.3.7
rxjs                            7.8.1
typescript                      5.3.3
zone.js                         0.14.5
```


### Anything else?

Note that moving the `&ngsp;` inside the `@if` does work:

```html
  <div id="if-inside">
      @if (true) {<span>Hello</span>&ngsp;}      
      @if (true) {<span>World</span>}
  </div>
```
Repository: TypeScript
Issue: Isolated declarations uses type information when emitting computed object keys 
Labels: Domain: Declaration Emit,Possible Improvement,Domain: Isolated Declarations

### 🔎 Search Terms

- isolated declarations
- computed keys
- object literals

### 🕗 Version & Regression Information

5.5.0-dev.20240514

### ⏯ Playground Link

https://www.typescriptlang.org/play/?isolatedDeclarations=true&ts=5.5.0-dev.20240514#code/KYDwDg9gTgLgBAYwgOwM7wNLAJ5wLxwBEMAFsFtoQNwBQNAJsAgDYCGUwcA5sxAEatmcAN4044uKEixEKdHADivAcwr4ipYEv6CKhMRKnR4SNPACqyAJYBHAK7AAytgC2fCMwBccO9fudUV3dmWglJcGNZMzgAORRLWwdnNw9vQJSQmgBfOiMZU3kAQXVRMIBtCgBdbxgoBwAaA3Ey5OCAOhgIR1qrZC4AFVYuargAM0FUYEbyhP9WjxHx5knpiTLtFSrvJZXsmiA

### 💻 Code

```ts
export const Key = "theKey";

declare global {
    export const GlobalKey = "theGlobalKey"
    export const UniqueSymbol: unique symbol;
    export const NonUniqueSymbol: symbol;
}

export const A = {
    [Key]: true,
    [Symbol.toStringTag]: false,
    [UniqueSymbol]: false,
    [GlobalKey]: false,
}
```


### 🙁 Actual behavior

TypeScript is emitting the computed property keys with type information that can not be determined without a type checker.

```ts
export declare const Key = "theKey";
declare global {
    export const GlobalKey = "theGlobalKey";
    export const UniqueSymbol: unique symbol;
    export const NonUniqueSymbol: symbol;
}
export declare const A: {
    theKey: boolean;
    [Symbol.toStringTag]: boolean;
    [UniqueSymbol]: boolean;
    theGlobalKey: boolean;
};
```

### 🙂 Expected behavior

```ts
export declare const Key = "theKey";
declare global {
    export const GlobalKey = "theGlobalKey";
    export const UniqueSymbol: unique symbol;
    export const NonUniqueSymbol: symbol;
}
export declare const A: {
    [Key]: true,
    [Symbol.toStringTag]: false,
    [UniqueSymbol]: false,
    [GlobalKey]: false,
};
```

### Additional information about the issue

_No response_
Repository: vscode
Issue: `vscode.workspace.openNotebookDocument` sporadically fails with `Error: NO notebook document for 'untitled:Untitled-1.ipynb?jupyter-notebook'`
Labels: bug,notebook-api

This doesn't always happen, but I see it frequently when running in the degugger. The code I use is

```
const notebookDocument = await vscode.workspace.openNotebookDocument('jupyter-notebook', createNotebookData());

function createNotebookData(): vscode.NotebookData {
	return new vscode.NotebookData(
		[
			new vscode.NotebookCellData(vscode.NotebookCellKind.Code, '# This program prints Hello, world!' , 'python'),
			new vscode.NotebookCellData(vscode.NotebookCellKind.Code, 'print(\'Hello, world!\')', 'python')
		],
	);
}
```

What is interesting as well is the fact that if I do that in n test cases all calls fail with the same notebook document URI `untitled:Untitled-1.ipynb?jupyter-notebook`.
Repository: go
Issue: log/slog: log.Fatal() reports wrong source location when both log.Lshortfile or log.Llongfile and slog with source is enabled
Labels: NeedsInvestigation

### Go version

go version go1.21.5 darwin/arm64

### Output of `go env` in your module/workspace:

```shell
GO111MODULE=''
GOARCH='arm64'
GOBIN=''
GOCACHE='/Users/andrew/Library/Caches/go-build'
GOENV='/Users/andrew/Library/Application Support/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='arm64'
GOHOSTOS='darwin'
GOINSECURE=''
GOMODCACHE='/Users/andrew/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='darwin'
GOPATH='/Users/andrew/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/opt/homebrew/Cellar/go/1.21.5/libexec'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/opt/homebrew/Cellar/go/1.21.5/libexec/pkg/tool/darwin_arm64'
GOVCS=''
GOVERSION='go1.21.5'
GCCGO='gccgo'
AR='ar'
CC='cc'
CXX='c++'
CGO_ENABLED='1'
GOMOD='/Users/andrew/src/go.mod'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -ffile-prefix-map=/var/folders/8b/qq9znh551qv_r0lhlj8bs0hr0000gn/T/go-build2100671700=/tmp/go-build -gno-record-gcc-switches -fno-common'
```


### What did you do?

Our applications have `log.Lshortfile` set and while migrating to `log/slog`, we noticed that in a few spots where we call `log.Fatal()` that the source line information points to inside the standard library as opposed to the line where the log was called.

Other package-level functions such as `log.Print()` report the correct source line location.

`log.Llongfile` exhibits the same bug.

Playground: https://go.dev/play/p/k-eOzUuhr1f

```go
package main

import (
	"log"
	"log/slog"
	"os"
)

func main() {
	log.SetFlags(log.Lshortfile)
	slog.SetDefault(slog.New(slog.NewTextHandler(os.Stderr, &slog.HandlerOptions{
		AddSource: true,
	})))
	log.Print("hello")
	log.Fatal("world")
}
```

### What did you see happen?

When slog is enabled with source location, we see the following:
```
time=2009-11-10T23:00:00.000Z level=INFO source=/tmp/sandbox1731373776/prog.go:14 msg=hello
time=2009-11-10T23:00:00.000Z level=INFO source=/usr/local/go-faketime/src/log/log.go:412 msg=world
```

### What did you expect to see?

When slog is disabled, we see the following:
```
prog.go:12: hello
prog.go:13: world
```

I would expect with slog enabled, we should see the following:
```
time=2009-11-10T23:00:00.000Z level=INFO source=/tmp/sandbox1731373776/prog.go:14 msg=hello
time=2009-11-10T23:00:00.000Z level=INFO source=/tmp/sandbox1731373776/prog.go:15 msg=world
```
Repository: next.js
Issue: Page props not passed for Index page when Middleware and basePath in use
Labels: bug,Pages Router

### Link to the code that reproduces this issue

https://github.com/gavb17/next-index-bug

### To Reproduce

- `npm run dev`
- Open index route under `basepath` in browser, text on page shows value of prop being passed "Page #"
- Use text to click through to second page, works as expected "Page #"
- Click link on second page to go back to `index`, page loads but passed prop does not show in text (no "Page #" text) nor console output

### Current vs. Expected behavior

**Expect** `getServerSideProps` to trigger when navigating back to Index page from within the app, and props passed into the page
**Current** Props are not being passed

### Provide environment information

```bash
System:
OS: macOS 14.4.1
CPU: (10) arm64 Apple M1 Max
Memory: 279.94 MB / 32.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 18.18.0 - ~/.nvm/versions/node/v18.18.0/bin/node
npm: 9.8.1 - ~/.nvm/versions/node/v18.18.0/bin/npm
Browsers:
Chrome: 124.0.6367.203
Safari: 17.4.1
npmPackages:
next: 14.2.3 => 14.2.3
react: ^18.2.0 => 18.2.0
```


### Which area(s) are affected? (Select all that apply)

Pages Router

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

App uses `middleware.ts` file and `basePath` in `next.config`, when navigating from a page back to index route the request for pageProps (index.json) in the browser returns a 308 status (expected a 200), and the props from getServerSideProps are lost on page load.
Repository: neovim
Issue: lastused property for windows/buffers/tabpages ("MRU history")
Labels: enhancement

### Problem

I'm trying to add a `lastused` property to `vim.fn.getwininfo`, like in `vim.fn.getbufinfo`.

It's just a timestamp for when a windown was last entered into

I've made a start: https://github.com/neovim/neovim/pull/28742 and for the most part it works, however, there's one case where it doesn't work as expected;

If a buffer is opened in multiple windows, the timestamp (`w_last_used`) won't get updated when you enter any of the other windows, apart from the first window that the buffer was opened in and all the windows display the same timestamp as the first window.

**Please note** I'm completly new to this codebase and any help to pointing me to the right direction, or just any tips/guidance in general would be greatly appreciated

## Background
In case anyone is curious as to why I want this;

It's to do with the qf window, specifically what happens when you select an item in the qf window that's open in multiple windows.

When I'm developing, I may have multiple windows open of the same buffer (due to me jumping around the code).

If there's an item in the qf window that's open in multiple windows, I would like that item to open in the windown that was most reccently accessed, see; https://github.com/kevinhwang91/nvim-bqf/pull/140/files

### Expected behavior

I expect each window to have it's timestamp updated each time I enter it