sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: Moving from a pages router page to app directory through NextLink duplicates base path on built app
Labels: bug,Navigation

### 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.5.0: Mon Apr 24 20:53:19 PDT 2023; root:xnu-8796.121.2~5/RELEASE_ARM64_T6020
    Binaries:
      Node: 18.14.0
      npm: 9.3.1
      Yarn: 1.22.19
      pnpm: N/A
    Relevant Packages:
      next: 13.4.20-canary.12
      eslint-config-next: 13.4.19
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.6
    Next.js Config:
      output: N/A
```


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

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

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

https://github.com/Artsu/next-app-directory-with-legacy-pages-router

### To Reproduce

- run `npm install`
- run `npm run build`
- run `npm start`
- open site at `http://localhost:3000/demo`
- click the `Pages example` link, this works
- click the `Landing page` link. The url is http://localhost:3000/demo but it opens http://localhost:3000/demo/demo instead

### Describe the Bug

In a project with set `basePath` that uses both app directory and legacy pages router, any `next/link` from legacy page to app directory page will have the correct route when hovered in browser but duplicates the base path when clicked. This only happens on built site running `next start` or on exported static site. On development mode with `next dev` the issue does not occur

### Expected Behavior

After clicking the link users should be correctly directed to the app directory page with the basePath only getting added once 

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

Firefox 116.0.2 (64-bit)

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

next start, static s3
Repository: stable-diffusion-webui
Issue: [Bug]: 1.6.0-RC: Refiner InputAccordion always gets closed after reusing prompt, after restart, sending pnginfo and ist not saved to config
Labels: bug-report

### Is there an existing issue for this?

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

### What happened?

The refiner InputAccordion allwyas gets closed after clicking an the button to reuse the last prompt and genration params. The state of the accordion is also not saved to the config

### Steps to reproduce the problem

1. open refiner InputAccordion, generate some image 
2. click an the button to reuse the last prompt
3. refiner gets closed
4. or restart automatic1111
5. refiner gets closed


### What should have happened?

The stat of the refiner should be saved to the config, an properly restored from pnginfo, and restore from the reuse last prompt button.

### Version or Commit where the problem happens

Version 1.6.0-RC

### 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?

_No response_

### Cross attention optimization

Automatic

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

Apple Safari

### Command Line Arguments

```Shell
--autolaunch --skip-torch-cuda-test --skip-install --no-download-sd-model --upcast-sampling --use-cpu interrogate --them dark
```


### List of extensions

No

### Console logs

```Shell
.
```


### Additional information

_No response_
Repository: storybook
Issue: [Bug]: Uncaught TypeError: Converting circular structure to JSON when opening Storybook (Vue.js)
Labels: bug,telemetry,sev:S3

### Describe the bug

After opening Storybook in the browser there's an following error:
```
Uncaught TypeError: Converting circular structure to JSON
    --> starting at object with constructor 'Array'
    |     index 0 -> object with constructor 'Object'
    |     property 'errorProperties' -> object with constructor 'Object'
    |     ...
    |     property 'data' -> object with constructor 'Object'
    --- property 'telemetryError' closes the circle
    at JSON.stringify (<anonymous>)
    at stringify (chunk-UBOPZ7EI.js:34:6072)
    at WebsocketTransport.sendNow (chunk-UBOPZ7EI.js:39:9200)
    at WebsocketTransport.send (chunk-UBOPZ7EI.js:39:9098)
    at chunk-UBOPZ7EI.js:39:9338
    at Array.forEach (<anonymous>)
    at WebsocketTransport.flush (chunk-UBOPZ7EI.js:39:9318)
    at WebsocketTransport.socket.onopen (chunk-UBOPZ7EI.js:39:8786)
stringify @ chunk-UBOPZ7EI.js:34
sendNow @ chunk-UBOPZ7EI.js:39
send @ chunk-UBOPZ7EI.js:39
(anonymous) @ chunk-UBOPZ7EI.js:39
flush @ chunk-UBOPZ7EI.js:39
WebsocketTransport.socket.onopen @ chunk-UBOPZ7EI.js:39
```
It doesn't seem to break any functionality. I got this error after upgrading Storybook but it also occurred when I tried to install it on the project that doesn't have SB in the past. Tested with node 16.17.0 and 18.17.1

### To Reproduce

1. Run Storybook locally
2. Open Storybook in the browser
3. Check the console

### System

```bash
System:
    OS: Windows 10 10.0.19045
    CPU: (12) x64 Intel(R) Core(TM) i7-10850H CPU @ 2.70GHz
  Binaries:
    Node: 16.17.0 - C:\Program Files\nodejs\node.EXE
    npm: 8.15.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.1266.0), Chromium (116.0.1938.62)
  npmPackages:
    @storybook/addon-essentials: ^7.4.0 => 7.4.0
    @storybook/addon-interactions: ^7.4.0 => 7.4.0
    @storybook/addon-links: ^7.4.0 => 7.4.0
    @storybook/blocks: ^7.4.0 => 7.4.0
    @storybook/testing-library: ^0.2.0 => 0.2.0
    @storybook/vue3: ^7.4.0 => 7.4.0
    @storybook/vue3-vite: ^7.4.0 => 7.4.0
```


### Additional context

_No response_
Repository: rust
Issue: Object lifetime defaults of GATs are not respected
Labels: A-lifetimes,A-associated-items,T-compiler,C-bug,T-types,A-trait-objects,A-GATs

To infer the [default trait object lifetime](https://doc.rust-lang.org/reference/lifetime-elision.html#default-trait-object-lifetimes) of a trait object type, we first look at the bounds on the relevant type parameter of the containing generic type. According to my interpretation of the Reference, [RFC 599](https://github.com/rust-lang/rfcs/blob/master/text/0599-default-object-bound.md) and [RFC 1156](https://github.com/rust-lang/rfcs/blob/master/text/1156-adjust-default-object-bounds.md), any kind of generic type can be an elegible container type, not just ADTs. However, if the containing generic type is a GAT, the compiler doesn't properly take into consideration the bounds on its type parameters. The RFCs obviously predate GATs.

For example, I expected the following code to compile since `dyn Inner` in `g`'s signature should be equivalent to `dyn Inner + 'r` given that `'r` is the object lifetime default due to the bound `T: 'a` at least according to my reading of the Reference and according to `#[rustc_object_lifetime_default]` but it fails because the default is actually inferred to be `'static` leading me to assume that rustc completely ignores the GAT param bounds.

```rs
trait Outer {
    type Ty<'a, T: ?Sized + 'a>;
}
impl Outer for () {
    type Ty<'a, T: ?Sized + 'a> = &'a T;
}
trait Inner {}

fn f<'r>(x: <() as Outer>::Ty<'r, dyn Inner + 'r>) { g(x) } //~ ERROR lifetime may not live long enough
fn g<'r>(_: <() as Outer>::Ty<'r, dyn Inner>) {}
```

```
error: lifetime may not live long enough
  --> src/lib.rs:10:56
   |
10 | fn f<'r>(x: <() as Outer>::Ty<'r, dyn Inner + 'r>) { g(x) }
   |      -- lifetime `'r` defined here                     ^ cast requires that `'r` must outlive `'static`
```

As attested by `#[rustc_object_lifetime_default]`, we seem to (be able to) *compute* the object lifetime defaults for GATs (but we don't *use* them during resolution):

```
error: 'a
 --> src/lib.rs:5:17
  |
5 |     type Ty<'a, T: ?Sized + 'a>;
  |                 ^
```

---

Is this an oversight in the current implementation or does this work as intended?
Note that it would be a breaking change to fix this, I'm almost certain.

@rustbot label C-bug T-compiler A-lifetimes A-trait-objects A-associated-items F-generic_associated_types
Repository: godot
Issue: focused panel display is broken in multi-window mode
Labels: bug,topic:gui

### Godot version

4.1.1

### System information

linux

### Issue description

[simplescreenrecorder-2023-08-30_14.27.36.webm](https://github.com/godotengine/godot/assets/71937306/f2151dea-b6d4-41e4-b3ff-9e5b9110ccfa)

[simplescreenrecorder-2023-08-30_14.28.40.webm](https://github.com/godotengine/godot/assets/71937306/1894167d-391a-4716-857e-80e7fc40b4ca)

as you can see in multi window mode the unfocused docks still have their focus border visible

### Steps to reproduce

1. make docks floating
2. click on them
3. notice the focus border doesn't disapear when a dock is not focused anymore

### Minimal reproduction project

any
Repository: godot
Issue: Calling set_process(false) when NOTIFICATION_EXIT_TREE emits error in terminal
Labels: discussion,topic:core

### Godot version

v4.1.1.stable.official [bd6af8e0e]

### System information

Ubuntu 20.04 LTS

### Issue description

See title.

### Steps to reproduce

1. Create a new scene with one node
2. Attach a script to any node type that includes the following:
```
func _process(delta):
  pass


func _notification(what):
  if what == NOTIFICATION_EXIT_TREE:
    set_process(false)
```
4. Run this command in the terminal (replace `./path/to/godot` and `path/to/project` with valid paths on your machine)
```
./path/to/godot --headless --quit --path path/to/project
```
5. See this error in the terminal
```
ERROR: Condition "!found" is true.
   at: _remove_node_from_process_group (scene/main/scene_tree.cpp:1122)
```

**Notes**
1. I understand that it is redundant to call `set_process(false)` when exiting the tree, since `_process(delta)` won't be called until it is added back.  However I think this is still a bug since it's valid code.
2. The error occurs every time the node is removed from the scene tree (assuming it calls `set_process(true)` sometime before it is removed again), not just during shutdown.
3. The error only appears when run via the command line.  It does not appear in the editor's console.
4. Running this in the editor (with `--editor`) will also emit the error in the terminal and still not in the editor's console.
5. You don't have to run with `--headless --quit`.  Removing the two, then manually closing the window, will also repro the bug.

### Minimal reproduction project

[set_process_bug.zip](https://github.com/godotengine/godot/files/12475459/set_process_bug.zip)
Repository: next.js
Issue: Poppins font displayed badly on iOS
Labels: bug,Font (next/font)

### 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.6.0: Wed Jul  5 22:21:53 PDT 2023; root:xnu-8796.141.3~6/RELEASE_ARM64_T6020
    Binaries:
      Node: 20.3.0
      npm: 9.6.7
      Yarn: 1.22.19
      pnpm: N/A
    Relevant Packages:
      next: 13.4.19
      eslint-config-next: 13.4.19
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.2.2
    Next.js Config:
      output: 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://perdu.com/

### To Reproduce

```jsx
import { Poppins } from "next/font/google";

const poppins = Poppins({
	subsets: ["latin"],
	weight: ["100", "200", "300", "400", "500"]
});
```

### Describe the Bug

Hi,

I'm using nextjs with google font (@next/font), and the font I use is Poppins.

### Expected Behavior

On iOS the font seems badly displayed, looks not good like in the desktop.

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

_No response_

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

_No response_
Repository: TypeScript
Issue: transpileModule does not elide type only "import equals" under emitDecoratorMetadata
Labels: Bug,Domain: Decorators,Rescheduled

### 🔎 Search Terms

isolatedModules import alias

### 🕗 Version & Regression Information

- This is the behavior in every version I tried: v5.1.1, v5.2.2, v5.3.0-dev.20230830

### ⏯ Playground Link

https://www.typescriptlang.org/play?importHelpers=true&experimentalDecorators=true&emitDecoratorMetadata=true&isolatedModules=true&noResolve=true&ts=5.3.0-dev.20230830#code/JYWwDg9gTgLgBAbwJIDsYFMoDMCGBjdAXziyghDgHIA6AehgE8x0BnSgbgChPRJY4AcqwwATVBmz50cALxxxmXAWpCWohZIJdOI9HgA2OKNLwQUa+SjABXGAC44OFA23oAHn3gGcLFnABiEBCInHBhcAACqDbwYGRgAIQOqupoilJchEA

### 💻 Code

```ts
import {Interface} from './types';

import NestedInterface = Interface.NestedInterface;

declare const Input: any;

export class Foo {
    @Input prop!: NestedInterface;
}
```


### 🙁 Actual behavior

```js
var _a;
import { __decorate, __metadata } from "tslib";
import { Interface } from './types';
var NestedInterface = Interface.NestedInterface; // <-- this can throw at runtime
export class Foo {
}
__decorate([
    Input,
    __metadata("design:type", typeof (_a = typeof NestedInterface !== "undefined" && NestedInterface) === "function" ? _a : Object)
], Foo.prototype, "prop", void 0);
```

### 🙂 Expected behavior

Either of the following would work, I think:

- Make this pattern an error, possibly requiring sth like `import type NestedInterface = Interface.NestedInterface;`
- Elide import equals
- Emit `var NestedInterface = ...` using a runtime check, similarly as in the decorator metadata code

### Additional information about the issue

Very similar to https://github.com/microsoft/TypeScript/issues/49450
Repository: vscode
Issue: Visual Studio Code installer fails to register file associations for supported file types
Labels: bug,help wanted,install-update,windows

<!-- ⚠️⚠️ 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

<!-- 🪓 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: 1.81.1
- OS Version: Windows 10.0.19045.3393

**Steps to Reproduce:**

1. Create a virtual machine containing a clean version of Windows 10
2. Log in with a user account with admin privileges.
3. Download `VSCodeSetup-x64-1.81.1.exe`. (If enough time has passed and version 1.81.1 isn't available download the latest machine-wide installer.)
4. Run the installer.
5. Proceed with installation but be sure to check "Register Code as an editor for supported file types."
6. Create a new standard user account (without administrative privileges)
7. Log out
8. Log in with the new standard user account
9. Create the following blank files. You can do so on the desktop.
    - Test.cpp
    - Test.cs
    - Test.css
    - Test.html
    - Test.html
    - Test.js
    - Test.json
    - Test.markdown
    - Test.md
    - Test.ps1
    - Test.svg
    - Test.xml
    - Test.yaml

**Expected results:** Not all of them are associated with Visual Studio Code but the user should be able to associate them via the Settings app → Apps and Features → Default Apps → Set defaults by app.

**Actual results:** Not all of them are associated with Visual Studio Code and the user cannot adjust the association via the Settings app → Apps and Features → Default Apps → Set defaults by app.

Please resist the temptation to tell me "you can drag and drop files into VSCode" or "you can use the Open With command." Users can do all of those things without putting a checkmark next to "Register Code as an editor for supported file types." So, what does that checkmark even do?
Repository: TypeScript
Issue: Module is present in declarations even though it is unused.
Labels: Bug,Domain: Declaration Emit

### 🔎 Search Terms

module unused declarations

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ



### ⏯ Playground Link

https://www.typescriptlang.org/play?ts=5.2.2#code/KYDwDg9gTgLgBAbwL4CgAmwDGAbAhlYOAWwjQFdtCS0BGRFORuUSWOGATzEJmAGcYdALxwBUAJYA7AOYBuFKgw58VUhVVoATPSZxxRVvF4DhxUjQB0xwfN0to8BO36C4SeUiA

### 💻 Code

```ts
export {}
declare module mod1 {
    export type test1 = string;
}
declare module mod2 {
    import test1 = mod1.test1;
    export { test1 };
}
```


### 🙁 Actual behavior

`mod1` is kept in the declaration.

### 🙂 Expected behavior

`mod1` is not kept in the declaration file since it is only used  in `mod2` which is omitted from the declaration file.

### Additional information about the issue

Found while working on isolated declarations in test `reExportAliasMakesInstantiated.ts`  added by #54816 (cc @andrewbranch )
Repository: pytorch
Issue:  DistributedSampler class: Change total_size into num_samples
Labels: oncall: distributed,triaged

https://github.com/pytorch/pytorch/blob/68b518c13e128997a0c7c9ab8ce9508cc4062e3a/torch/utils/data/distributed.py#L118C42-L118C52

This line can be:
 indices = indices[self.rank:self.**num_samples**:self.num_replicas]

cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @H-Huang @kwen2501 @awgu @penguinwu
Repository: bitcoin
Issue: Seek more/different peers when ours all have too high feefilter
Labels: Feature,P2P

While investigating an issue with a non-propagating transaction with @TheBlueMatt, it occurred to us that it can be a problem for a node to get its transactions relayed when it's surrounded solely by low-mempool-limit peers (which correspondingly have a high announced minfeefilter value). And it appears this is detectable too, as our own `mempoolminfee` would be lower.

While obviously relay can't be guaranteed, this is a detectable situation, and it could factor into the outbound replacement logic and/or trigger something similar to the "seek more peers" behavior we exhibit when we appear to be not getting blocks.
Repository: storybook
Issue: 'npm run storybook' failed with problem of 'import type'
Labels: bug,needs triage

### Describe the bug

Hello ! 😄 

I tried to create a story in another folder than the one created by storybook during the init, but I have an error when I want to launch the server:

![image](https://github.com/storybookjs/storybook/assets/103406827/60713661-409d-44e2-9ff0-da660579a04b)

**main.ts :**

```ts
const config: StorybookConfig = {
    stories: ["../src/**/*.mdx", "../src/**/*.stories.@(js|jsx|mjs|ts|tsx)", "../assets/**/*.stories.@(js|jsx|mjs|ts|tsx)"],
    addons: [
        "@storybook/addon-links",
        "@storybook/addon-essentials",
        "@storybook/addon-onboarding",
        "@storybook/addon-interactions",
        "@storybook/preset-create-react-app",
        "@storybook/theming",
        "@storybook/manager-api",
        "@storybook/addon-console",
        "@storybook/addon-a11y",
        "storybook-addon-mantine",
    ],
    framework: {
        name: "@storybook/react-webpack5",
        options: {},
    },
    docs: {
        autodocs: "tag",
        defaultName: "Doc",
    },
    core: {
        disableWhatsNewNotifications: true,
    },
    features: {
        storyStoreV7: true,
    },
};
```

**.babelrc config :**

```json
{
  "sourceType": "unambiguous",
  "presets": [
    [
      "@babel/preset-env",
      {
        "targets": {
          "chrome": 100,
          "safari": 15,
          "firefox": 91
        }
      }
    ],
    "@babel/preset-typescript",
    "@babel/preset-react"
  ],
  "plugins": []
}
```

**Tree of my environment :**

```bash
/
├── .storybook/
├── .assets/
│   ├── test.stories.tsx ( problem file )
├── src/
│   ├── stories/
│   │   ├── one.stories.tsx
│   │   ├── two.stories.tsx
│   │   ├── three.stories.tsx
├── .babelrc
```

I want to specify that it is an Symfony environment !

Does anyone have an idea?

Available if you have any questions !

### To Reproduce

_No response_

### System

```bash
System:
    OS: Windows 10 10.0.19045
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
  Binaries:
    Node: 17.9.1 - ~\Documents\GIT\ACEoyA\node_modules\.bin\node.CMD
    npm: 9.8.1 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.1266.0), Chromium (116.0.1938.62)
  npmPackages:
    @storybook/addon-a11y: ^7.2.1 => 7.4.0
    @storybook/addon-console: ^2.0.0 => 2.0.0
    @storybook/addon-essentials: ^7.2.1 => 7.4.0
    @storybook/addon-interactions: ^7.2.1 => 7.4.0
    @storybook/addon-links: ^7.2.1 => 7.4.0
    @storybook/addon-onboarding: ^1.0.8 => 1.0.8
    @storybook/blocks: ^7.2.1 => 7.4.0
    @storybook/manager-api: ^7.2.1 => 7.4.0
    @storybook/preset-create-react-app: ^7.2.1 => 7.4.0
    @storybook/react: ^7.2.1 => 7.4.0
    @storybook/react-webpack5: ^7.2.1 => 7.4.0
    @storybook/testing-library: ^0.2.0 => 0.2.0
    @storybook/theming: ^7.2.1 => 7.4.0
```


### Additional context

_No response_
Repository: TypeScript
Issue: Resolve documentation for type aliases
Labels: Suggestion,Awaiting More Feedback

### 🔍 Search Terms

type alias hover documentation 

### ✅ Viability Checklist

- [X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
- [X] This wouldn't change the runtime behavior of existing JavaScript code
- [X] This could be implemented without emitting different JS based on the types of the expressions
- [X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
- [X] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

### ⭐ Suggestion

When a type is a literal type alias of another type **without** any generics, it should take over the documentation of the aliased type.

I originally proposed this in https://github.com/microsoft/TypeScript/issues/49798#issuecomment-1228787745, but I think this deserves its own issue.

### 📃 Motivating Example

Type aliases should resolve the documentation of the type they alias.

```ts
/**
 * A boolean, number, or string literal
 */
type PrimitiveLiteral = boolean | number | string

type Primitive = PrimitiveLiteral

// hovering on 'Primitive' should show "A boolean, number, or string literal"
let value: Primitive
```

### 💻 Use Cases

1. What do you want to use this for?

Type aliases are a common way to import types when using types in JSDoc. For example:

```js
/**
 * @typedef {import('unist').Point}  Point
 */

/**
 * @param {Point} point
 */
function stringifyPoint(point) {}
```

2. What shortcomings exist with current approaches?

Hovering `Point` in the example, provides no documentation. When type definitions are generated, they create a type alias which has the same problem.

3. What workarounds are you using in the meantime?

Navigate to the original type to read its documentation, or look it up online.