sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: useParams values are stale when conditionally rendering parallel routes (version 13.4.2)
Labels: bug,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: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.3.0: Thu Jan  5 20:48:54 PST 2023; root:xnu-8792.81.2~2/RELEASE_ARM64_T6000
    Binaries:
      Node: 16.19.1
      npm: 9.4.0
      Yarn: 1.22.19
      pnpm: N/A
    Relevant packages:
      next: 13.4.3
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 4.9.5

warn  - Latest canary version not detected, detected: "13.4.3", newest: "13.4.5-canary.2".
        Please try the latest canary version (`npm install next@canary`) to confirm the issue still exists before creating a new issue.
        Read more - https://nextjs.org/docs/messages/opening-an-issue
```


### 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/cmugla/next-parallel-routes-issue

### To Reproduce

At a high level, with [this directory setup](https://github.com/cmugla/next-parallel-routes-issue), the repro steps are:

- say we have the following app structure `/:assetId/:nestedAssetId`
- click a link to go from `/123/456` to `/123`

Expected Result:
- the `useParams` hook returns `{ assetId: 123 }` & the correct layout is rendered

Bug Result:
- within all client components, the `useParams` hook will still return { assetId: '123', nestedAssetId: '456' } & therefore, the incorrect layout is rendered

https://github.com/vercel/next.js/assets/19141291/939df3de-0ace-46b9-8cd2-3e0f3499057b




### Describe the Bug

This works as expected in version `13.4.1` (started happening in `13.4.2`). And the browser back/forward buttons work as expected. 

This doesn't happen for a typical directory layout (without the conditional render & conditional parallel routes). The problem we are trying to solve by conditionally rendering based on param key is so that the data can be fetched on the server and the component is not re-mounted every time the id in the URL changes. Plus, in order to render the component on the server, we need to know whether we are fetching for the `nestedAssetId` or not. 

Disclaimer: we are not fans of this solution, but it was a thing that worked 😳 .... If we had access to the url from the server, we wouldn't need the conditional render. Perhaps there is a better solution already for this kind of thing? 🤔 Open to alternative ideas

Link to [example of the directory structure](https://github.com/cmugla/next-parallel-routes-issue/tree/main/app/%5BoneLevel%5D)

### Expected Behavior

`useParams` would always match what is in the URL.

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: storybook
Issue: [Feature Request]: Addons use interface type merging to typesafe Parameters
Labels: feature request,api: addons,typescript

### Is your feature request related to a problem? Please describe

When configuring storybook addons, a lot of the control options exist in the parameters property. For example, parameters.actions.argTypesRegex or parameters.controls.expanded. The Parameters type (from @storybook/types) is a simple record interface allowing for any inputs, but no type safety or property hinting.

I am making this issue here as making 10 issues across 10 addons would cause the conversation to be more scattered. Also, I think this change lives in the addons, not in the type package, as that way the addons are still responsible for their own types when making changes, and the interface merging would only happen if that addon package is actually installed.

### Describe the solution you'd like

If addons came with declaration files, then TS would automatically type merge interfaces, creating a much better intellisense and developer experience. Case in point:

```ts
declare module '@storybook/types {
  interface Parameters {
    /**
    * Controls FOO thing
    */
    myOptionalConfig?: boolean;
  }
}
```

Now, when using the Parameters type across the repo, that optional type is available everywhere, type safe, and easily understandable/discoverable for developers.

I am using this exact approach with a custom decorator, where the decorator lives at the top level preview.ts file, but each story can adjust the rendered options by passing the right property to parameters.myCustomDecorator, and it works as expected.

### Describe alternatives you've considered

_No response_

### Are you able to assist to bring the feature to reality?

yes, I can

### Additional context

I have used this approach with @storybook/react module declaration, and @storybook/types, but adding it to @storybook/types will make the changes more framework agnostic.
Repository: kubernetes
Issue: Removal of intree storage plugin is causing us to lose important test coverage
Labels: kind/bug,sig/storage,kind/api-change,help wanted,needs-triage

### What happened?

When we removed the intree plugins - https://github.com/kubernetes/kubernetes/pull/116301 

We are also removing the e2es and in-process losing coverage such as for pre-provisioned or inline volumes. This causes those code paths to be error prone.

IMO - my naive thinking was to remove the plugin actively from `kubernetes/pkg` etc, but at the same time keep the vendored dependencies so as we can build the e2e and keep using it.



### What did you expect to happen?

Run e2e and I would expect inline, pre-provisioned volume tests to still be running.

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

Run e2e and

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
$ kubectl version
# paste output here
```

</details>


### Cloud provider

<details>

</details>


### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


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

<details>

</details>


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

<details>

</details>
Repository: PowerToys
Issue: PowerToys does not appear in Startup App Settings or Task Manager
Labels: Issue-Bug,Area-Setup/Install,Priority-2

### Microsoft PowerToys version

0.70.0

### Installation method

Microsoft Store

### Running as admin

No

### Area(s) with issue?

General

### Steps to reproduce

PowerToys does not appears in Windows Settings under Apps > Startup Apps or Startup section under Task Manager. Afaik PowerToys starts up with using Task Scheduler, but it should still extend an entry under these two endpoints like it shows entry in PowerToys Settings Page.

### ✔️ Expected Behavior

An app entry for PowerToys in Windows Settings > Apps > Startup or Task Manager

### ❌ Actual Behavior

No entry appears under the above mentioned points.

### Other Software

_No response_
Repository: storybook
Issue: [Bug]: Story not selected on initial load
Labels: bug,help wanted,compatibility with other tools,has workaround,build-storybook

### Describe the bug

I've recently upgraded a Storybook project from version 6.5 to 7. I've noticed an issue with the production build, where if I refresh my browser while on a story page, I get the message, **"Sorry, but you either have no stories or none are selected somehow.".** A story won't show up until I click on another in the sidebar.

I cloned Storybook's [design system](https://github.com/storybookjs/design-system) repo, built a production build and saw the same issue. If, for example, I'm looking at the Button docs or if I paste this [URL](http://localhost:3000/?path=/docs/button--docs) directly into the browser, the story / docs don't show.

Is this a feature, or is there a way to get around this issue? Or maybe I'm missing something else?

### To Reproduce

Issue can be recreated with Storybook's [design system](https://github.com/storybookjs/design-system) repo.

```sh
$ npm run build-storybook
$ npx serve storybook-static
```

### System

```shell
Environment Info:

  System:
    OS: macOS 12.5
    CPU: (8) arm64 Apple M2
  Binaries:
    Node: 18.16.0 - /usr/local/bin/node
    npm: 9.5.1 - /usr/local/bin/npm
  Browsers:
    Chrome: 113.0.5672.126
    Safari: 15.6
  npmPackages:
    @storybook/addon-a11y: ^7.0.2 => 7.0.2 
    @storybook/addon-actions: ^7.0.2 => 7.0.2 
    @storybook/addon-docs: ^7.0.2 => 7.0.2 
    @storybook/addon-essentials: ^7.0.2 => 7.0.2 
    @storybook/addon-storysource: ^7.0.2 => 7.0.2 
    @storybook/eslint-config-storybook: ^3.1.2 => 3.1.2 
    @storybook/linter-config: ^3.1.2 => 3.1.2 
    @storybook/react: ^7.0.2 => 7.0.2 
    @storybook/react-webpack5: ^7.0.2 => 7.0.2 
    @storybook/theming: ^7.0.2 => 7.0.2
```


### Additional context

_No response_
Repository: PowerToys
Issue: TextExtractor option ☑ Dim screen outside the selected area
Labels: Needs-Triage

### Description of the new feature / enhancement

Would you add a _new_ **setting** to enable or **disable** ☑ **Dim** screen _outside_ the selected area?
This option would be enabled by default like in the current behavior 0.70

### Scenario when this would be used?

However some users do **not** like that the screen becomes **darker** _even_ temporarily.

Changing the **contrast** between the selected area and the rest of the darker screen _strongly_ increases **eye-strain** and eye **fatigue**.
So **un**checking the option ☐ **Dim** screen _outside_ the selected area 
keeps the overall brightness of the screen like the user wishes.

### Supporting information

_No response_
Repository: vscode
Issue: Add jump to previous/next bracket commands
Labels: feature-request,editor-bracket-matching

I don't think this is possible currently, we have `editor.action.jumpToBracket` but that jumps to the outer bracket and then to the matching bracket (which is good, just not what I'm after). I'd like to try ctrl+up/down to speed up navigating between chunks faster and more precisely than page up/down.
Repository: stable-diffusion-webui
Issue: [Feature Request]: Opt out from loadsave "Default" system when making an extension ?
Labels: enhancement

### Is there an existing issue for this?

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

### What would your feature do ?

Is there a way to opt out from the system that save the UI state of gradio elem when making an extension ?

```
for interface, _label, ifid in interfaces:
                if ifid in ["extensions", "settings"]:
                    continue

                loadsave.add_block(interface, ifid)
```

Regards

### Proposed workflow

1. Go to .... 
2. Press ....
3. ...


### Additional information

_No response_
Repository: svelte
Issue: Logical (writing direction aware) transitions
Labels: transition/animation

### Describe the problem

I recently had to translate an app I'm writing to different languages, with different writing directions.
So I had to replace all of my `fly` transitions to use this `logical_fly` function instead of the `fly` transition provided by svelte.

```typescript
import { fly } from "svelte/transition";

export const logical_fly: typeof fly = (node, params = {}) => {
  let { x, ...rest } = params;
  if(getComputedStyle(node).direction === "rtl") x = -x; 
  return fly(node, {
    ...rest,
    x,
  })
}
```

This a little example for explanaition only, a better approach could be taken, like handling vertical wiritng modes.

### Describe the proposed solution

Extend the transitions with logical parameters that are writing direction aware.

```typescript
export type FlyParams = {
   /// same old x, y, duration, etc
   /// and the new ones
  inline?: number,
  block?: number
}
```

This won't be a breaking change because if not provided, the logical parameters could be ignored

### Alternatives considered

Do nothing and let this be solved in user code.

### Importance

nice to have
Repository: pytorch
Issue: torchscript dataclasses have bad support for class types as fields
Labels: oncall: jit

### 🐛 Describe the bug

In `_dataclass_impls.py`, there's a step where the `__init__` function signature is collected and then serialized as a string. During that process, it seems like the serialized names are not always readable by PyTorch. In the example below, the type for `MyClass` gets serialized as `__main__.MyClass`. I'm assuming that the failure happens later on when Torchscript's RCB  isn't able to find `__main__.MyClass`.

A fix for this might be to find a different way to annotate the signature when it is serialized, e.g. by using the annotation types found on the dataclass fields themselves.

```python
from dataclasses import dataclass

from typing import Dict

import torch


class MyClass:
    x: int
    y: float

    def __init__(self, x: int, y: float):
        self.x = x
        self.y = y

    def eval(self) -> float:
        return self.y**self.x


@torch.jit.script
@dataclass
class Batch:
    float_features: Dict[int, torch.Tensor]
    mc: MyClass

    def __eq__(self, other: "Batch") -> bool:
        for k in self.float_features:
            if k in other.float_features:
                if not torch.equal(self.float_features[k], other.float_features[k]):
                    return False
            else:
                return False

        return self.mc == other.mc


class ASD(torch.nn.Module):
    def __init__(self) -> None:
        super().__init__()

    def forward(self, batch: Batch) -> torch.Tensor:
        return batch.float_features


model = ASD()
torch.jit.script(model)
```

### Versions

pytorch 2.0 / main branch as of submission

cc @EikanWang @jgong5 @wenzhe-nrv @sanchitintel
Repository: rust
Issue: Missing trait bound for defaulted types parameters should mention them
Labels: A-diagnostics,T-compiler,D-confusing

### Code

```Rust
use ::core::ops::Add;

trait Trait: Add {}
```


### Current output

```Shell
error[E0277]: the size for values of type `Self` cannot be known at compilation time
 --> src/lib.rs:3:14
  |
3 | trait Trait: Add {}
  |              ^^^ doesn't have a size known at compile-time
  |
note: required by a bound in `Add`
 --> /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/core/src/ops/arith.rs:77:1
help: consider further restricting `Self`
  |
3 | trait Trait: Add + Sized {}
  |                  +++++++

For more information about this error, try `rustc --explain E0277`.
```


### Desired output

```Shell
error[E0277]: the size for values of type `Self` cannot be known at compilation time
 --> src/lib.rs:3:14
  |
3 | trait Trait: Add {}
  |                ^ the `Rhs = Self` default type parameter doesn't have a size known at compile-time
  |
note: required by a bound in `Add`
 --> /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/core/src/ops/arith.rs:77:1
help: given the default type parameter, this is the same as:
 --> src/main.rs:4:26
  |
4 | trait Trait: Add<Self> {}
  |                 ++++++
help: consider further restricting `Self`
  |
3 | trait Trait: Add + Sized {}
  |                  +++++++

For more information about this error, try `rustc --explain E0277`.
```

@rustbot modify labels to: +D-confusing
Repository: godot
Issue: Export AAB to Android failed caused by audio file
Labels: bug,platform:android,topic:export

### Godot version

3.5.2 stable

### System information

Kubuntu 22.04

### Issue description

When exporting AAB to Android, the build fails due to one small audio file. It was hard to find because no related debug info was shown and all other audio files works fine. Even the audio file itself works fine. Desktop Linux, Windows and even Android apk builds work great with it. So the main problem was that a bug like this was really hard to recognize because no proper feedback was found in the engine output. After removing this file from the project, the build completed successfully, but it does not work on the device - just a black screen and a frozen application. The file was still used by AudioStreamPlayer and AnimationPlayer. After clearing all occurrences of this audio, the export finally works fine. The issue is open as no information was found about this behavior and maybe this will help someone. 

The problematic audio file has been added to the MRP.

### Steps to reproduce

- Install android build template.
- Set export to android settings with keystore and AAB export. 
- Connect phone and export project. 
- Build should be failed.

### Minimal reproduction project

[AAB_failed_by_audio.zip](https://github.com/godotengine/godot/files/11619382/AAB_failed_by_audio.zip)
Repository: flutter
Issue: Enable developers to run heapprofd traces on Flutter applications
Labels: c: new feature,tool,P3,team-tool,triaged-tool

I'm not sure if this is just a documentation bug or something we want to actively make easier.

It's possible to run a Perfetto native heap trace on Android 9+. However, to get symbols in the trace, you need either an unstripped libflutter.so or be on Linux.

Here are the steps to get a symbolicated heapprofd trace today:

1. Build the engine locally, using a gn invocation like the following: `flutter/tools/gn --android --android-cpu arm64 --no-strip` (with your preferred runtime mode/unopt settings).
2. Add the following to your Flutter application's `android/app/build.gradle`:
```gradle
  android {
    // Other options...
    packagingOptions {
        doNotStrip '**/libflutter.so'
    }
  }
```
3. Do a `flutter run --local-engine=android_debug_arm64` (replace the runtime mode to match the runtime from your locally built engine).
4. Clone https://github.com/google/perfetto
5. Invoke the Perfetto `tools/trace_heap` script: `tools/trace_heap -n com.example.myAppName`
6. Interact with your application.

Perfetto will tell you where it put the heap trace file at the end. Googlers can upload that to pprof, or anyone else can upload it to https://ui.perfetto.dev/#!/viewer

It is possible for Perfetto to apply the symbols, but currently that only works on Linux (a limitation in Perfetto itself). 

We should either better document how to do this somewhere, or ideally make it easier for developers to do this. For example, if Perfetto can be made to add symbols for Mac/Windows, we could instruct developers to download the symbols for their particular engine build.  It may also be more feasible to just provide unstripped artifacts for e.g. debug and profile mode, and provide instructions or flags to the tool to download them and use them for heap tracing.

/cc @terrylucas @jacob314 
/cc @liyuqian 
/cc @segfaulthunter fyi
/cc @zanderso @jonahwilliams for input on tooling options.
Repository: flutter
Issue: [docs] explain how to configure servers to distinguish between routes and static files
Labels: engine,d: api docs,f: routes,platform-web,P2,team-web,triaged-web

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Use case

Currently, when using the [`go_router 7.1.1`] package to resolve the link required for `Apple Pay` domain verification (`https://[DOMAIN_NAME]/.well-known/apple-developer-merchantid-domain-association`), per [this guide](https://developer.apple.com/documentation/applepaywebmerchantregistrationapi/preparing_merchant_domains_for_verification), the package attempts to resolve the URL as a buildable Widget page route, rather than the file contents at this location. 

<img width="1091" alt="Screenshot 2023-05-31 at 6 31 37 PM" src="https://github.com/flutter/flutter/assets/32310695/fe3e38f8-3eb8-4309-8747-4dca4c576226">

------
The contents of this file is a single encrypted string, an example of which can be downloaded [here](https://stripe.com/docs/stripe-js/elements/payment-request-button#verifying-your-domain-with-apple-pay) under step 1 of the walkthrough.

 
<img width="690" alt="Screenshot 2023-05-31 at 6 57 08 PM" src="https://github.com/flutter/flutter/assets/32310695/b08e2215-1409-4dad-a09a-1b608c10902b">

------
Files formatted as JSON are still able to be displayed correctly, despite the similar lack of a corresponding file type as in the URL format above.
<img width="848" alt="Screenshot 2023-05-31 at 7 06 29 PM" src="https://github.com/flutter/flutter/assets/32310695/d1ce6414-b20b-4baa-942e-79c963de8617">




### Proposal

Currently, the constructor for a `GoRoute` as of `GoRouter 7.1.1` is as follows:

```
(new) GoRoute GoRoute({
  required String path,
  String? name,
  Widget Function(BuildContext, GoRouterState)? builder,
  Page<dynamic> Function(BuildContext, GoRouterState)? pageBuilder,
  GlobalKey<NavigatorState>? parentNavigatorKey,
  FutureOr<String?> Function(BuildContext, GoRouterState)? redirect,
  List<RouteBase> routes = const <RouteBase>[],
})
package:go_router/src/route.dart

Constructs a [GoRoute].
```

Adding a boolean parameter to the constructor to ignore the specified route for building as a Widget could be a potential solution to this issue.
Repository: pytorch
Issue: Investigate the perf drop on timm for dynamic shape when layout optimization is enabled
Labels: module: performance,feature,triaged,oncall: pt2,module: inductor

### 🚀 The feature, motivation and pitch

We see 14% perf win on timm models with layout optimization. But enabling dynamic shape cause 6% perf drop instead.

Theoretically we should also see wins with dynamic shape.

I've done some early investigation on gernet_l.

Here are the perf numbers:
static shape + layout opt: 1.474x
static shape without layout opt: 1.165x

dyn shape + layout opt: 0.912x
dyn shape without layout opt: 1.102x


Dive into the dynamic shape runs further.
For dyn shape + layout opt
- Abs latency: 80.241734 ms
- Fwd wrapper: https://gist.github.com/shunting314/147285c6ba55576ad528b6bc3c02aff7
- Fwd wrapper profiling result: ​​https://gist.github.com/shunting314/dcb6d8a80739487a8a782f84a3c01976 
- Fwd wrapper total wall time 28.636 ms
- Bwd wrapper: https://gist.github.com/shunting314/6218248272f9519d497a91403b676103 
- Bwd wrapper profiling result: https://gist.github.com/shunting314/d7afef45fcfa7e5b7b776b61ed9fa7a2 
- Bwd wrapper Total wall time 49.491 ms

For dyn shape without layout opt:
- Abs latency: 66.486952 ms
- Fwd wrapper: https://gist.github.com/shunting314/f0a0c038850a94283ae3a87975e75e2b 
- Fwd wrapper profiling result: https://gist.github.com/shunting314/e649dc72df2c9a247952d91e60a8de10
- Fwd wrapper Total wall time 20.838 ms
- Bwd wrapper: https://gist.github.com/shunting314/5dbc4ae04c1b8c695d31651af6185509 
- Bwd wrapper profiling result: https://gist.github.com/shunting314/41adfa37fd1cde3600f40ffebe4532fc
- Bwd wrapper Total wall time 44.032 ms 

We can see that with layout opt, overall we slow down by ~14ms. While the fwd wrapper slows downs by ~8ms and bwd wrapper slows down by ~5.5 ms. I'll dive into the fwd wrapper as the next step.

cc @ezyang @msaroufim @wconstab @bdhirsh @anijain2305 @zou3519 @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @peterbell10 @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @aakhundov @ColinPeppler @Xia-Weiwen @ngimel @jansel @Chillee @eellison 



### Alternatives

_No response_

### Additional context

_No response_