sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: App Dir: Avoid intercepted route for hard navigated page
Labels: Parallel & Intercepting Routes

### 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: #22 SMP Tue Jan 10 18:39:00 UTC 2023
    Binaries:
      Node: 18.14.2
      npm: 9.5.0
      Yarn: 1.22.19
      pnpm: N/A
    Relevant packages:
      next: 13.4.7-canary.4
      eslint-config-next: 13.4.7
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.0.4
```


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

App directory (appDir: true)

### Link to the code that reproduces this issue or a replay of the bug

https://codesandbox.io/p/sandbox/dazzling-hooks-fz6pjv

### To Reproduce

1. Run the code sandbox  
2. Navigate to the search modal using the Search button
3. Type a query 
4. Refresh the page, full search page should open
5. Update the search query using input control
6. The search modal should also show up, along with the page updated. 

The search modal should not show up.

### Describe the Bug

1. The home page contains list of articles.
2. There is a Search button that opens the intercepted `/search` route in a Modal
3. On typing in the input, search is supposed to happen (not implemented), url is updated with query string. e.g. /search?q=food

All Good so far.

4. Now when a User refreshes the page, the full search page appears. say for url `/search?q=food`
5. On the page, if user tries to update the search query, the page is updated as well as opens the intercepted `/search` route in a Modal

Since the user is already on the full `/search` page, there should not be any requirement to again open the intercepted route

### Expected Behavior

When updating the route with a new query string, the page should get updated and not show the intercepted route modal. As the page is already loaded and should not be again intercepted.

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

_No response_

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

_No response_
Repository: angular
Issue: Property error in class HttpErrorResponse should be unknown
Labels: feature,breaking changes,area: common/http,feature: insufficient votes

### Which @angular/* package(s) are relevant/related to the feature request?

common/http
(https://github.com/angular/angular/blob/ba0ca42b8c62d64fe0f1e0528663fd5a64c49322/packages/common/http/src/response.ts#L323)

### Description

There is a potential issue where the program tries to access properties of null without proper type inference
Programmer should infer type for this:
```ts
        error: (res: HttpErrorResponse) => {
         // check if res extends ApiErrorResponse interface
          if (this.apiValidator.isApiErrorResponse(res)) {
            this.onError(res.error.errorCode);
          }
        },
```

### Proposed solution

Change 
```ts
readonly error: any | null;
```

to
```
readonly error: undefined;
```

### Alternatives considered

No alternatives
Repository: godot
Issue: Crash when the editor has Save on Focus Loss enabled ("Task 'save' already exists.")
Labels: bug,topic:editor,confirmed,crash

### Godot version

v4.0.3.stable.mono.official [5222a99f5]

### System information

linux rtx 2060

### Issue description

crash when set editor "Save on Focus Loss" On

### Steps to reproduce

1.create a empty project
2. set editor "Save on Focus Loss" On  in "Editor Settings"
3. create 2d or 3d empy scene
4. run, Crash

### Minimal reproduction project

same, 4.1 beta 3
Repository: excalidraw
Issue: expose `props.renderScrollbars` to package api
Labels: package:excalidraw

see https://github.com/excalidraw/excalidraw/pull/6706
Repository: PowerToys
Issue: Mouse Without Borders - New key button not working
Labels: Issue-Bug,Needs-Triage,Product-Mouse Without Borders

### Microsoft PowerToys version

0.70

### Installation method

WinGet

### Running as admin

No

### Area(s) with issue?

Mouse Without Borders

### Steps to reproduce

New Key simply didn't generate keys, the text box keeps empty.

### ✔️ Expected Behavior

A new key to be generated.

### ❌ Actual Behavior

nothing happened.

### Other Software

_No response_
Repository: godot
Issue: First few frames at game start are applying wrong colors
Labels: bug,topic:rendering

### Godot version

e74bf83, Godot 4.1 beta3

### System information

Windows 10

### Issue description

The Godot 4 forward+ and mobile renderer have issues applying the startup colors/scenes to the expected frames.

0 frame - application / launcher starts.
1 frame - it applies the `application/boot_splash/bg_color` but it ignores any transparency this color might have.
2-5 frame - it applies the missing transparency to the bg_color and the `application/boot_splash/show_image` if set.
5-7 frame - it applies the render from the `application/run/main_scene`.

![launchflashes](https://github.com/godotengine/godot/assets/52464204/fb445e26-2faf-4dd5-a7a2-ac393050b1d7)
Screenrecording with backdrop from a FFXVI cutscene running in the window background.

This leads to multiple screen flashes at the game start if the colors are all different.
It also makes transparent starting launchers impossible to make due to color flashes.

Godot 3 does not have those issues.
The first frame is rendered correct in the transparent bg_color with the main scene showing, no flashes.

### Steps to reproduce

Set `application/boot_splash/bg_color` to a transparent debug color.
Set `display/window/size/transparent` = true.
Set `rendering/viewport/transparent_background`  = true

### Minimal reproduction project

[GodotStartBlackFlash.zip](https://github.com/godotengine/godot/files/11834076/GodotStartBlackFlash.zip)
Repository: vscode
Issue: Editor rulers disappear randomly in large files
Labels: bug,editor-core

Repro:

1. Set `"editor.rulers": [ 80, 100, 120 ]`
2. Open vscode.d.ts
3. Scroll

![image](https://github.com/microsoft/vscode/assets/2193314/8c526623-7466-4cf4-965c-a08dccae7ce9)

Ruler element looks correct:

![image](https://github.com/microsoft/vscode/assets/2193314/f67790d5-bc7c-4582-aaac-db8872518ff6)

It looks like a Chromium issue but we're hitting it due to the extremely large `height`, maybe hitting some GPU max texture limit or something?

![Recording 2023-06-22 at 05 56 02](https://github.com/microsoft/vscode/assets/2193314/82efb404-0306-4fb9-bf3d-98229991dcc0)

To workaround this could we do something similar to virtualizing the buffer and reposition it each scroll to +/- x pixels? That may be better for perf as well depending on how the line gets drawn behind the scenes.
Repository: rust
Issue: `rustc_on_unimplemented` is not std-agnostic
Labels: A-diagnostics,C-bug,D-confusing,D-diagnostic-infra

If `rustc_on_unimplemented` contains a path mentioning `std::`, it won't work in `#![no_std]` crates, even if the type exists in the `core`. Similarly if you use `core::` path instead, the diagnostic will *only* work in `#![no_std]` crates.

As an example take this annotation for `?` desugaring: https://github.com/rust-lang/rust/blob/fa06a371b715f137c952577cfded4e49cb7e76c4/library/core/src/ops/try_trait.rs#L250-L260

It should (and does) trigger for the following code:

```rust
fn f() -> Option<()> {
    Err::<(), _>(())?;
    None
}
```
```
error[E0277]: the `?` operator can only be used on `Option`s, not `Result`s, in a function that returns `Option`
 --> src/lib.rs:2:21
  |
1 | fn f() -> Option<()> {
  | -------------------- this function returns an `Option`
2 |     Err::<(), _>(())?;
  |                     ^ use `.ok()?` if you want to discard the `Result<Infallible, ()>` error information
  |
  = help: the trait `FromResidual<Result<Infallible, ()>>` is not implemented for `Option<()>`
  = help: the following other types implement trait `FromResidual<R>`:
            <Option<T> as FromResidual<Yeet<()>>>
            <Option<T> as FromResidual>
```
([play](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=87a24e037a3cd32e2fa805d86ee9b0a7);note the use `.ok()?` label)

However, if you add `#![no_std]` the label disappears:

```rust
#![no_std]

fn f() -> Option<()> {
    Err::<(), _>(())?;
    None
}
```
```
error[E0277]: the `?` operator can only be used in a function that returns `Result` or `Option` (or another type that implements `FromResidual`)
 --> src/lib.rs:4:21
  |
3 | fn f() -> Option<()> {
  | -------------------- this function should return `Result` or `Option` to accept `?`
4 |     Err::<(), _>(())?;
  |                     ^ cannot use the `?` operator in a function that returns `Option<()>`
  |
  = help: the trait `FromResidual<Result<Infallible, ()>>` is not implemented for `Option<()>`
  = help: the following other types implement trait `FromResidual<R>`:
            <Option<T> as FromResidual<Yeet<()>>>
            <Option<T> as FromResidual>
```
([play](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=64e04d094ba1a3ccbccd23c9d14d7443); the error message is also misleading, the function _does_ return option)

---

rustc in general is not great at being std-agnostic in diagnostics, and this is just another annoying example of that.

### Meta

`rustc --version --verbose`:
```
rustc 1.70.0 (90c541806 2023-05-31)
binary: rustc
commit-hash: 90c541806f23a127002de5b4038be731ba1458ca
commit-date: 2023-05-31
host: aarch64-unknown-linux-gnu
release: 1.70.0
LLVM version: 16.0.2
```


<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"DogPawHat"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: stable-diffusion-webui
Issue: [Bug]: AssertionError: Can't scale by because no image is selected
Labels: bug-report,platform:mac

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What happened?

Cannot use regular img2img upscale for 4x of 512x768 picture.
If you select an image for the img2img tab and then go to the batch tab program autodetects size of image but still gives the error.
Selecting Size to limits both dimensions to 2048. To do a 4x upscale of a 512x768 you would be limited to Extras batch which gives A LOT LESS control

### Steps to reproduce the problem

1. img2img
2. batch tab
3. input directory parameters
4. choose Scale by and set to 4 (we want a 4x upscale of a 512x768 picture)
5. make all the rest of your settings
6. Generate
7. get error "AssertionError: Can't scale by because no image is select


### What should have happened?

Either Scale to should allow larger than 2048 dimensions or Scale by should honor the image in the img2img tab.

### Commit where the problem happens

22ad1d3f

### What Python version are you running on ?

Python 3.10.x

### What platforms do you use to access the UI ?

MacOS

### What device are you running WebUI on?

Other GPUs

### What browsers do you use to access the UI ?

Google Chrome

### Command Line Arguments

```Shell
No
```


### List of extensions

adetailer 
deforum 
automatic1111-webui | 
multidiffusion-upscaler-for-automatic1111
openOutpaint-webUI-extension
sd-dynamic-prompts 
sd-webui-controlnet 
sd-webui-infinite-image-browsing 
sd-webui-mov2movsd-webui-regional-prompter 
sd_dreambooth_extension 
stable-diffusion-webui-dataset-tag-editor 
ultimate-upscale-for-automatic1111 

### Console logs

```Shell
Traceback (most recent call last):
  File "/Users/bobpuffer/stable-diffusion-webui/modules/call_queue.py", line 57, in f
    res = list(func(*args, **kwargs))
  File "/Users/bobpuffer/stable-diffusion-webui/modules/call_queue.py", line 37, in f
    res = func(*args, **kwargs)
  File "/Users/bobpuffer/stable-diffusion-webui/modules/img2img.py", line 118, in img2img
    assert image, "Can't scale by because no image is selected"
AssertionError: Can't scale by because no image is selected
```


### Additional information

_No response_
Repository: pytorch
Issue: Improved error checking for custom Function when saving intermediates
Labels: module: double backwards,module: autograd,triaged,actionable

Currently, if users create a custom Function, save intermediate tensors (tensors that are neither inputs nor outputs to the custom function) for backward, and use them in the backward formula to compute gradients, the gradients produced in double backward would be silently incorrect.

We should produce a error in this case instead. One way to do this is to attach an ErrorNode to all non-input/non-output tensors being saved.

https://github.com/pytorch/pytorch/issues/103726#issuecomment-1599015774

cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @Lezcano @Varal7
Repository: TypeScript
Issue: Synthetic comment duplicated 3 times on class with experimental decorators
Labels: Bug,Help Wanted

# Bug Report

### 🔎 Search Terms

setSyntheticLeadingComments, transformer

### 🕗 Version & Regression Information

- This changed between versions 5.0 and 5.1

In 5.0 TypeScript already emitted the comment twice. In 5.1 it emits it 3 times.

(+1 on both if you count the comment on the __decorate call)

### 💻 Code

Repro: https://github.com/frigus02/test-ts-triple-synthesized-comment

```ts
const FILE = ` 
@decorate()
class Foo {}
`;

const myTransformer = () => {
  return (sf) => {
    ts.setSyntheticLeadingComments(sf.statements[0], [
      {text: 'from transformer', kind: ts.SyntaxKind.MultiLineCommentTrivia, pos: -1, end: -1},
    ]);
    return sf;
  };
};

const result = ts.transpileModule(FILE, {
  compilerOptions: {
    experimentalDecorators: true,
    module: ts.ModuleKind.CommonJS,
    target: ts.ScriptTarget.ESNext,
  },
  transformers: {
    before: [myTransformer],
  }
});

console.log(result.outputText);
```

### 🙁 Actual behavior

```
/*from transformer*/ let /*from transformer*/ Foo = /*from transformer*/ class Foo {
};
/*from transformer*/ Foo = __decorate([
    decorate()
], Foo);
```

The comment between `let` and `Foo` is problematic for our use of tsickle and Closure Compiler. But I think the issue is more general. I'd expect the comment to appear only once in the output.

This seems very similar to https://github.com/microsoft/TypeScript/issues/45696

We validated that the same fix (calling `setSyntheticLeadingComments(expression, undefined)`) after `setOriginalNode` [here](https://github.com/microsoft/TypeScript/blob/e69a0b0e38b380677adb83ff0d20d8b8c32b2d9d/src/compiler/transformers/legacyDecorators.ts#L371) and [here](https://github.com/microsoft/TypeScript/blob/e69a0b0e38b380677adb83ff0d20d8b8c32b2d9d/src/compiler/transformers/legacyDecorators.ts#L382) would fix this. Are you open to such a fix? If so, I'd be happy to send a PR.

### 🙂 Expected behavior

```
/*from transformer*/ let Foo = class Foo {
};
Foo = __decorate([
    decorate()
], Foo);
```
Repository: vscode
Issue: Restarting the pty host will sometimes dispose of the new processes
Labels: bug,terminal-process

Repro:

1. Open terminal
2. Run restart pty host command, 🐛 about half of the times the process is killed and panel gets closed
Repository: storybook
Issue: [Bug]: re-exported Story from different file disabling "Show code / Hide code" button
Labels: bug,block: source

### Describe the bug

In Storybook 7 while re-exporting stories via:
```
export { Basic } from "./avatar.basic.story";
```
I can see a story, but I can't preview the source ("Show code / Hide code" button is disabled)

BTW - using old way with asterisk (Storybook 5, 6) in Storybook 7 doesn't show the story, neither the source code:
```
export * from "./avatar.basic.story";
```

Some stories are quite large and I need to keep them in separate tsx files.


### To Reproduce

Storybook preview: 
https://64978ad79679888cd8f5f436-fzgpjawimm.chromatic.com/?path=/docs/example-button--docs

Repository:
https://github.com/Demiurg77/my-storybook-reproduction/tree/main/src/stories

Reproduction build details: 
https://www.chromatic.com/build?appId=64978ad79679888cd8f5f436&number=2

### System

```shell
Environment Info:

  System:
    OS: macOS 13.4
    CPU: (10) arm64 Apple M1 Pro
  Binaries:
    Node: 18.12.1 - ~/.nodenv/versions/18.12.1/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 8.19.2 - ~/.nodenv/versions/18.12.1/bin/npm
  Browsers:
    Chrome: 114.0.5735.133
    Edge: 110.0.1587.57
    Firefox: 114.0.2
    Safari: 16.5
  npmPackages:
    @storybook/addon-essentials: ^7.0.20 => 7.0.20 
    @storybook/addon-interactions: ^7.0.20 => 7.0.20 
    @storybook/addon-links: ^7.0.20 => 7.0.20 
    @storybook/addon-storysource: ^7.0.21 => 7.0.21 
    @storybook/blocks: ^7.0.20 => 7.0.20 
    @storybook/react: ^7.0.20 => 7.0.20 
    @storybook/react-webpack5: ^7.0.20 => 7.0.20 
    @storybook/testing-library: ^0.0.14-next.2 => 0.0.14-next.2
```


### Additional context

_No response_
Repository: go
Issue: proposal: os/exec, syscall: allow child processes to inherit all inheritable handles from the parent process
Labels: OS-Windows,Proposal

On Windows, one must explicitly list the handles that will be inherited by a new process when calling [syscall.StartProcess](https://pkg.go.dev/syscall?GOOS=windows#StartProcess) and [os.StartProcess](https://pkg.go.dev/os#StartProcess). This is problematic for applications that don't know which handles they have inherited from their parent process and want to spawn new child processes with the same inherited handles, as in #53652.

Windows does not provide an API to list all inherited handles, but suggest to use some form of process communication ([source](https://learn.microsoft.com/en-us/windows/win32/procthread/inheritance#inheriting-handles)), so these applications are left behind without a solution other than reimplementing `syscall.StartProcess`.

In fact, before go1.17 we did support this use case, all inheritable handles were passed explicitly. #44011 changed `syscall.StartProcess` to use the more robust approach of passing them implicitly. What I'm proposing here is to allow users to opt into the old behavior by adding a new property to [syscall.SysProcAttr](https://pkg.go.dev/syscall?GOOS=windows#SysProcAttr) property, named `InheritAllInheritableHandles`.

It would look like this:

```go
type SysProcAttr struct {
        // ...
        // Existing props
	NoInheritHandles           bool                // if set, each inheritable handle in the calling process is not inherited by the new process
	AdditionalInheritedHandles []Handle            // a list of additional handles, already marked as inheritable, that will be inherited by the new process
	ParentProcess              Handle              // if non-zero, the new process regards the process given by this handle as its parent process, and AdditionalInheritedHandles, if set, should exist in this parent process
	// New props
	InheritAllInheritableHandles bool // if set and NoInheritHandles is unset, each inheritable handle in the calling process is inherited by the new process
}
```

If `InheritAllInheritableHandles` is set and `NoInheritHandles` is unset, then `syscall.StartProcess` would ignore `AdditionalInheritedHandles` and call the relevant windows APIs as before `CL 288297`. We could also fail in case both `InheritAllInheritableHandles` and `NoInheritHandles` are set, I'm still not sold on this.

Notice that handles passed in `AdditionalInheritedHandles` will still be inherited when `InheritAllInheritableHandles` is set, as they must be marked as inheritable to be usable in `AdditionalInheritedHandles`.

@golang/windows @alexbrainman @zx2c4
Repository: next.js
Issue: @elastic/apm-rum breaks SPA behaviour
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: win32        
      Arch: x64
      Version: Windows 10 Pro
    Binaries:
      Node: 18.12.1
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant packages:       
      next: 13.4.8-canary.1  
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0      
      typescript: N/A        
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

_No response_

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/pierrechevaliercf/NextSPAError

### To Reproduce

Tested with next 13.4.6 

1 - Install  @elastic/apm-rum

`npm i @elastic/apm-rum` (5.12.0)

 2 - Create a client component which will call and use this lib :
```ts
'use client';

 import init from "@elastic/apm-rum";

export function InitApm() {
    const a  = init; // just importing this function and calling it cause the error (commenting this line fix the behaviour)

    return null;
}
```

3 - Call this client component into your layout.tsx

4 - Navigate on your next app

5 - You will see that the SPA behaviour is now broken :

![notspa](https://github.com/vercel/next.js/assets/117263412/ece21bdf-995e-4e2e-abbd-405b3195ee94)



### Describe the Bug

When @elastic/apm-rum is imported in a client component, the SPA behaviour no longer works, and navigation clicks fully reload the pages.


### Expected Behavior

Next links should not reload the full page at each navigation click and works as an SPA even if @elastic/apm-rum is used.

### Which browser are you using? (if relevant)

Chrome (114.0.5735.134) & Firefox (114.0.2 (64 bits))

### How are you deploying your application? (if relevant)

_No response_
Repository: go
Issue: proposal: runtime: flag to disable runtime override of GODEBUG
Labels: Proposal

I would like to make a change to the go runtime to convert the [debug variables parsed from GODEBUG](https://github.com/golang/go/blob/78c3aba4704c86874c36e61224966e7e07706bc0/src/runtime/runtime1.go#L309) to constants, and disable `GODEBUG` overriding at runtime.

Many of these constants are used to gate low level checks in the depths of the garbage collector or runtime, and if they were true constants, some of these checks could be elided by constant propagation. An example is the [findobject](https://github.com/golang/go/blob/78c3aba4704c86874c36e61224966e7e07706bc0/src/runtime/mbitmap.go#L339) function which would be able to skip some checks if `debug.invalidptr` were known to be a fixed constant 0. (internal reference b/288410395, these have substantial cost)

I would like to propose a new flag to `cgo`, strawman `fixed_godebug`, that when provided generates constant values for these fields as-if the `GODEBUG` env var had the value of `fixed_godebug` at runtime.

The work needed to implement this would be:

1) Split out `debug` itself and functions that modify `debug.*` fields into a new file, `runtime/godebug.go`
2) Move all `debug` fields to top level variables named `debug*` and all their usages in the runtime/ package. These are not exported so should not be breaking.
3) When the `fixed_godebug` flag is not empty, have `cgo` generate a replacement for godebug.go that replaces the `var` block with `debug*` values with a `const` block that sets all values inline, and makes all modifying functions log and do nothing.
Repository: pytorch
Issue: "TorchDynamo Deeper Dive" doc is missing some part
Labels: triaged,topic: docs

In https://pytorch.org/docs/main/compile/deep-dive.html#torchdynamo-deeper-dive, the first sentence is

> TorchDynamo operates just-in-time and specializes graphs based on dynamic properties. For example, **the first graph above** has the following guards:

but there's no graph above, so it's not clear what the rest is referring to.

CC @jansel as you seem to be the author