sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: [NEXT-1141] Next router / link not working when redirecting with new search params [Regression]
Labels: bug,linear: next

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.1.0: Sun Oct  9 20:19:12 PDT 2022; root:xnu-8792.41.9~3/RELEASE_ARM64_T6020
    Binaries:
      Node: 18.15.0
      npm: 9.5.0
      Yarn: N/A
      pnpm: 8.0.0
    Relevant packages:
      next: 13.4.0
      eslint-config-next: 13.3.0
      react: 18.2.0
      react-dom: 18.2.0
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

_No response_

### Link to the code that reproduces this issue

https://codesandbox.io/p/sandbox/eloquent-https-5slx4d

### To Reproduce

Navigate to the same URL with a new search param either via router.push() or the link component.

In the reproduction, wait for the initial page to load - then try and change to page 2, or 3, or use the search input. 

### Describe the Bug

The bug first appeared in 13.3.5-canary.2, prior versions works correctly.

**Navigating to the same page with new search params no longer renders the loading.tsx.**
    Looking at the URL / network tab - it seems that the router does kick off the fetch for the new page, but then waits for the full body response before updating the URL, or rendering the loading page.

### Expected Behavior

Prior to 13.3.5-canary.2, the behaviour was working correctly:

Navigating to the same page with new search params should show the loading.tsx, if the page is slow to fetch.

Video of this working previously:

https://user-images.githubusercontent.com/3614846/236453767-429cec22-46bc-436f-8377-2a597243a866.mov

### Which browser are you using? (if relevant)

N/A

### How are you deploying your application? (if relevant)

N/A

<sub>[NEXT-1141](https://linear.app/vercel/issue/NEXT-1141/next-router-link-not-working-when-redirecting-with-new-search-params)</sub>
Repository: next.js
Issue: Dynamic page not updating on subsequent navigations using Link component
Labels: bug,Navigation

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Next.js version: next@canary
Node.js version: 18.13
Operating System: Mac OS 13.3.1 (22E261)
Browser: Chrome 112
```


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

Routing (next/router, next/navigation, next/link)

### Link to the code that reproduces this issue

https://github.com/Livog/next-link-app-dir-bug

### To Reproduce

1. Hard navigate to: http://localhost:3000/dynamic
2. Update the input and click submit (this will save the data to the body.json in root)
3. Click on Home
4. Click on Dynamic
5. You should now see the updated value
6. Update the value again to something else
7. Click on "Home" again
8. Click "Dynamic", now the value is not updated while the last value you input is actually saved to the body.json

### Describe the Bug

The value on the dynamic page does not update on subsequent navigation to the page using the Next.js Link component. The expected behaviour is that the value should always be up to date on every Link click. This issue persists even when setting
```
export const dynamic = 'force-dynamic'
export const revalidate = 0
```

This can cause errors in situations where users need to see updated data, such as when updating user information on an /account page. It is important to note that in the provided example, one needs to navigate back and forth more than once to reproduce the bug. However, in another project where Prisma, a database, and NextAuth are used, and user content is fetched directly from the database, the issue manifests after just one save and navigation back to the account page.

Additionally, there is no network activity in the Chrome DevTools Network tab on the third request, indicating that there is no network request being made when navigating to a force-dynamic page or layout. This behaviour is inconsistent with the expected behaviour.

A workaround for this issue is to remove the Link component and use a regular anchor (`<a>`) tag instead. However, this approach removes any loading animations that might be present when using the Link component.

### Expected Behavior

The expected behaviour is for the dynamic pages to always display the most recent, updated value on every navigation using the Link component. This should occur regardless of how many times the user navigates to the dynamic page. Additionally, there should be network activity when navigating to a force-dynamic page or layout, ensuring the most up-to-date data is fetched and displayed.

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

Chrome 112

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

next start, next dev
Repository: kubernetes
Issue: workqueue: loop variables captured by 'func' literals in 'go' statements
Labels: kind/bug,area/test,sig/api-machinery,triage/accepted

### What happened?

target file: https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/client-go/util/workqueue/queue_test.go
```

1. for _, test := range tests {
2. 	const producers = 50
3. 	producerWG := sync.WaitGroup{}
4. 	producerWG.Add(producers)
5. 	for i := 0; i < producers; i++ {
6. 		go func(i int) {
7. 			defer producerWG.Done()
8. 			for j := 0; j < 50; j++ {
9. 				test.queue.Add(i)
10. 				time.Sleep(time.Millisecond)
11. 			}
12. 		}(i)
13. 	}
14. 
15. 	// Start consumers
16. 	const consumers = 10
17. 	consumerWG := sync.WaitGroup{}
18. 	consumerWG.Add(consumers)
19. 	for i := 0; i < consumers; i++ {
20. 		go func(i int) {
21. 			defer consumerWG.Done()
22. 			for {
23. 				item, quit := test.queue.Get()
24. 				if item == "added after shutdown!" {
25. 					t.Errorf("Got an item added after shutdown.")
26. 				}
27. 				if quit {
28. 					return
29. 				}
30. 				t.Logf("Worker %v: begin processing %v", i, item)
31. 				time.Sleep(3 * time.Millisecond)
32. 				t.Logf("Worker %v: done processing %v", i, item)
33. 				test.queue.Done(item)
34. 			}
35. 		}(i)
36. 	}
37. 
38. 	producerWG.Wait()
39. }

```

**In the func TestBasic(), the loop variable `test` is captured by 'func' literals in 'go' statements (at Line9 and Line33), it may cause a data race.  Creating local copy can avoid potential race condition. It also apply to the func TestAddWhileProcessing(). I don't know whether it is accurate, so I 'm looking forward to your reply.**

### What did you expect to happen?

Data race

### How can we reproduce it (as minimally and precisely as possible)?

nil

### Anything else we need to know?

_No response_

### Kubernetes version

latest


### Cloud provider

nil

### OS version

nil


### Install tools

nil


### Container runtime (CRI) and version (if applicable)

nil


### Related plugins (CNI, CSI, ...) and versions (if applicable)

nil
Repository: vscode
Issue: Highlights don't line up with the text they are highlighting
Labels: bug,font-rendering

When I highlight text in my code, the highlight doesn't line up with the code. The highlight gets more and more offset, as text goes further to the right in the row. This seems to just be a miscalculation of the displayed text's position in the row. The script that draws the highlights is getting understated values for some reason. I am guessing that something with the way the highlighter handles font width is wrong.

Version: 1.78.0
Commit: 252e5463d60e63238250799aef7375787f68b4ee
User Ag
![Screenshot 2023-05-05 9 07 07 AMv2](https://user-images.githubusercontent.com/64504202/236466175-8c2b7b37-058d-48ed-8a08-dc3b984fdba7.png)
ent: Mozilla/5.0 (X11; CrOS x86_64 14541.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.0.0 Safari/537.36
Embedder: github.dev

<!-- generated by web issue reporter -->
Repository: bitcoin
Issue: psbt: set global_xpubs (at least for multisig descriptors)
Labels: Feature

### Please describe the feature you'd like to see added.

The `walletcreatefundedpsbt`, `walletprocesspsbt` and `send`* RPC, as well as the send dialog* in the GUI should populate the `PSBT_GLOBAL_XPUB` field (defined in [BIP 174](https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki)).

At least when used in a multisig context, e.g. when spending from a `multi()` descriptor.

The Ledger Bitcoin app enforces this as of version 2.1.1., see https://github.com/bitcoin-core/HWI/issues/671

`*` = when used with an external signer

### Is your feature related to a problem, if so please describe it.

Multisig funds (P2WSH and P2SH-P2WSH) are trapped on a Ledger if you update it's Bitcoin app to 2.1.1, unless you use some additional tooling to set this field.

### Describe the solution you'd like

_No response_

### Describe any alternatives you've considered

_No response_

### Please leave any additional context

_No response_
Repository: kubernetes
Issue: Allow selecting system namespaces
Labels: kind/feature,sig/architecture,lifecycle/frozen,needs-triage

### What would you like to be added?

Add a mechanism (ie, a registered label that is automatically applied) that lets a cluster operator write a selector for namespaces.

The selector should be able to either include all system namespaces, or exclude them all.

---

Optionally, prevent people from overwriting this label.

### Why is this needed?

This lets people select system namespaces in a future proof way.

We could suggest that people use `kubernetes.io/metadata.name in (kube-system,kube-public,kube-node-lease)` but this might lead to snags if / when a 4th system namespace is added.
Repository: godot
Issue: Cannot build in headless mode for iOS
Labels: platform:ios,topic:editor,topic:export

### Godot version

4.0.2

### System information

macOS

### Issue description

I cannot build in headless mode on a server in my CI/CD. The build works fine on my computer. This is not related to the project structure, I got the same error unrelated to the projects.

1. I "trick" Godot into a false build to re-create the import (**there should be a command to do it, but well, that works for now**, see https://github.com/godotengine/godot-proposals/issues/1362#issuecomment-1379140108)
2. I run the `export-release` and it fails with almost no logs, so it is impossible to debug

### Steps to reproduce

(*bash*)
```
# Create the build_ipa folder
# First, do a fake build to re-create the import
${GODOT_EXEC} --path mobile-game/ --headless --export-pack "${EXPORT_TYPE}"  ./build_pck/app.pck || true

# Do the real build
${GODOT_EXEC} --path mobile-game/ --headless --export-release "${EXPORT_TYPE}" ./build_ipa/app.ipa
```

That outputs (without firing errors, which is the most suspicious)

```
2023-05-05 13:25:21.470 Godot[1209:8260] *** +[NSString stringWithUTF8String:]: NULL cString
Godot Engine v4.0.2.stable.official.7a0977ce2 - https://godotengine.org
 
WARNING: Custom cursor shape not supported by this display server.
     at: cursor_set_custom_image (servers/display_server.cpp:480)
export: begin: Exporting for iOS steps: 5
export: end
ERROR: Project export for preset "iOS Production" failed.
   at: _fs_changed (editor/editor_node.cpp:1044)
```

### Minimal reproduction project

N/A, any will work
Repository: electron
Issue: [Feature Request]: Remember last opened location based on title in showOpenDialog
Labels: enhancement :sparkles:

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a feature request that matches the one I want to file, without success.

### Problem Description

When I try to open very different folders for different input fields,
it sets the file opener to the last location I have used it in,
and not the last location specific to that field / title.


### Proposed Solution

What I'd like to see is a unique location based on the title of the `showOpenDialog` parameter.

So that when I set it once for that title, I don't have to retrace my steps in the file explorer / finder.

### Alternatives Considered

The only alternative I can think of, is if I do this via the renderer web based inputs. But I'd like to be as native as possible.

### Additional Information

_No response_
Repository: rust
Issue: Rustdoc generate files for items not used in documentation
Labels: T-rustdoc,C-bug

As demonstrated in the following codes:

```rust
// @!has 'foo/hidden/index.html'

// The following two should not fail!
// @!has 'foo/hidden/inner/index.html'
// @!has 'foo/hidden/inner/trait.Foo.html'
#[doc(hidden)]
pub mod hidden {
    pub mod inner {
        pub trait Foo {
            /// Hello, world!
            fn test();
        }
    }
}

// @has 'foo/visible/index.html'
// @has 'foo/visible/trait.Foo.html'
#[doc(inline)]
pub use hidden::inner as visible;

// @has 'foo/struct.Bar.html'
// @count - '//*[@id="impl-Foo-for-Bar"]' 1
pub struct Bar;

impl visible::Foo for Bar {
    fn test() {}
}
```

And the other example:

```rust
// None of the following checks should fail.
// @!has 'foo/hidden/index.html'
// @!has 'foo/hidden/inner/index.html'
// @!has 'foo/hidden/inner/trait.Foo.html'
#[doc(hidden)]
pub mod hidden {
    pub mod inner {
        pub trait Foo {
            /// Hello, world!
            fn test();
        }
    }
}

// @has 'foo/trait.Foo.html'
#[doc(inline)]
pub use hidden::inner::Foo;

// @has 'foo/struct.Bar.html'
// @count - '//*[@id="impl-Foo-for-Bar"]' 1
pub struct Bar;

impl Foo for Bar {
    fn test() {}
}
```

Examples come from https://github.com/rust-lang/rust/issues/111249.
Repository: next.js
Issue: Module imported in different files re-evaluated
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: linux
      Arch: x64
      Version: #1 SMP Wed Mar 2 00:30:59 UTC 2022
    Binaries:
      Node: 17.9.0
      npm: 8.19.3
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 13.4.1-canary.2
      eslint-config-next: 13.4.1
      react: 18.2.0
      react-dom: 18.2.0
```


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

_No response_

### Link to the code that reproduces this issue

https://github.com/jesinmat/next-reimport

### To Reproduce

Build and run the project. Open the app in your browser. You should see the following:

```
Current ID: 1
<Change ID>
```

In the server log, you will see that a cache has been created (by importing `lib/cache.ts`):

```
Creating a cache
Loading data from database
Returning data 1
```

Now, click on the "Change ID" button. You should see the following in the server log:

```
Creating a cache
API request received
Setting data to 2
```

Now refresh the page. Client will still see `1` as the ID as there are now two caches, since it was imported twice and evaluated upon each import. This should not happen.

### Describe the Bug

According to ECMAScript specification, importing a module from different places should only evaluate it once.
I wanted to use this fact to create a "cache", but it seems like the imported file is re-evaluated during imports from different files,
which makes it impossible to use as a singleton.

The file in question is located at `lib/cache.ts` and it's imported in `app/page.tsx` and `pages/api/change/index.ts`. Importing from these two files causes Cache constructor to be called twice, effectively exporting two completely separate instances of the class.

### Expected Behavior

File `lib/cache.ts` is only evaluated once and the result is exported and shared between all places.

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

_No response_

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

_No response_
Repository: tauri
Issue: [feat] Allow either CORS, or tauri:// custom domain support
Labels: type: feature request

### Describe the problem

Currently, it is impossible to have a sandboxed iframe whose resources are in the dist folder
> E.g `index.html` trying to sandbox an iframe to `iframe/index.html`

The reason is that if the iframe tries to load a local resource, it does not pass CORS checks
> E.g `iframe/index.html` loads `script.js`, fails with CORS error

### Describe the solution you'd like

The most obvious workaround is to allow setting CORS headers to the dev server and production "server" (asset loader)
If that were to be implemented, it would also make sense to allow setting other important headers too (e.g Cache-Control)

Another solution would be to allow other domains than just `localhost`
This already works on the dev server, but it would be immesurably helpful to also allow other domains (e.g `tauri://iframe.localhost` or `tauri://usercontent.localhost:100`), which would have their own separate `localStorage` and be treated as a different origin in general
Something I would really like to see is the ability to map different domains to different dist folders (e.g `tauri://localhost` maps to main `../dist`, but we could also, for example, map `tauri://other.component` to `../component2`

### Workarounds

At the moment, there is a workaround specifically for iframes, but it is very limited and works by abusing a bug where the request domain isn't checked properly.
Specifically, say we make a request `tauri://localhost.other/abc`. The protocol handler strips the expected `tauri://localhost`, which would normally leave a path like `/abc/def`, where the first character `/` is stripped. In this case, the leftover path is actually `.other/abc`, and then the "`/`" is stripped, despite not actually being checked if it is really a `/`. Ultimately, the path looks like `other/abc` and that asset is loaded
This bug essentially maps `tauri://localhost.*` to `../dist/*`
I am not asking that this bug be fixed (at least not yet, since it is the only workaround), but that first a solution to the above iframe problem is provided, while we use this workaround.


One last thing to consider, I haven't done any testing on windows, and I know that protocols are handled differently on windows. Please let me know below!
Repository: kubernetes
Issue: [klog] internal error during logging when trying to convert a map to a something printable
Labels: priority/backlog,sig/instrumentation,sig/architecture,triage/accepted

Please see the following internal error:
```
I0505 14:12:12.827065  190662 kuberuntime_manager.go:1014] "computePodActions got for pod" podActions="<internal error: json: unsupported type: map[container.ContainerID]kuberuntime.containerToKillInfo>" pod="kube-system/coredns-8f5847b64-mzw46"
```

This seems to be coming from:
https://cs.k8s.io/?q=computePodActions%20got%20for%20pod&i=nope&files=&excludeFiles=&repos=kubernetes/kubernetes
Repository: godot
Issue: Vive Focus 3 Android: Default mobile renderer does not start correctly on HMD
Labels: bug,platform:android,topic:rendering,topic:thirdparty,needs testing,topic:xr

### Godot version

4.0.2 stable

### System information

Vive Focus 3 Release 5.5

### Issue description

The current master godot-xr-tools sets the mobile renderer by default, but only gl_compatibilty starts correctly on the Vive Focus 3. Mobile results in a black start screen, then holding the controller trigger loads the first scene but as a corrupted 2d display.

### Steps to reproduce

Import the godot-xr-tools master
Leave renderer as mobile
Install godot_openxr_loaders
Export as Android Khronos with Open XRKHR plugin selected
Run on the HMD
Corrupted display

Change renderer to gl_compatible and rebuild
Display is now correct.


### Minimal reproduction project

N/A
Repository: storybook
Issue: [Bug]: Automatic naming is not working with grouped named exports
Labels: bug,core,csf,sev:S4

### Describe the bug

When using grouped named exports like
```js
const LargeButton = { ... };
const SmallButton = { ... };

export { LargeButton, SmallButton };
```
the automatic naming does not work because only the variable names are displayed:

<img width="155" alt="image" src="https://user-images.githubusercontent.com/7893762/236508531-7759024d-2df4-4221-9465-6153cf5515c3.png">

When I change it to individual exports, it works as expected and spaces are added to the story name.
```js
export const LargeButton = { ... }
export const SmallButton = { ... }
```

### To Reproduce

https://stackblitz.com/edit/github-rjf2b8?file=src/stories/Button.stories.js

The reproduction was created via [storybook.new](https://storybook.new/), and the only change I made was to the exports in the `Button.stories.js` file.

### System

```shell
Environment Info:

  System:
    OS: macOS 13.3.1
    CPU: (10) arm64 Apple M1 Max
  Binaries:
    Node: 16.17.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 8.18.0 - /usr/local/bin/npm
  Browsers:
    Chrome: 113.0.5672.63
    Firefox: 112.0.2
    Safari: 16.4
```


### Additional context

_No response_
Repository: material-ui
Issue: Building and publishing an add-on utility component for MUI
Labels: support: question

Hey folks, I've built a small (TypeScript-enabled) utility component that extends MUI and I want to publish it on npm for easy installation. The component and its dependencies work fine if I copy and paste the files into a project (so far I've tested with Next.js and CRA), but I'm struggling to get it to transpile into a packagable format that doesn't cause a cornucopia of errors. 

I've tried babel-loader, ts-loader, a combo of both, with and without webpack, and even though I can get it to generate files, they don't seem to work with React. 

Trouble is I'm flying blind and just trying random things hoping they'll work. Now out of desperation, I'm hoping you might be able to point me in the direction of a build system or even documentation I could read that would help me?

Thanks!
Repository: go
Issue: bootstrap/internal/abi: unrecognized failures
Labels: NeedsInvestigation,FrozenDueToAge

```
#!watchflakes
post <- pkg == "bootstrap/internal/abi" && test == ""
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/9edfa410bf5150edbd1af66edf5c313931a01c17)):

    /tmp/workdir-host-linux-loong64-3a5000/go/src/internal/abi/unsafestring_go120.go:13: unsafe.String requires go1.20 or later (-lang was set to go1.16; check go.mod)
    /tmp/workdir-host-linux-loong64-3a5000/go/src/internal/abi/unsafestring_go120.go:17: unsafe.Slice requires go1.17 or later (-lang was set to go1.16; check go.mod)
    go tool dist: FAILED: /usr/lib/go-linux-loong64-bootstrap/bin/go install -tags=math_big_pure_go compiler_bootstrap purego bootstrap/cmd/...: exit status 1


— [watchflakes](https://go.dev/wiki/Watchflakes)