sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: storybook
Issue: [Bug]: Deploying to Github Pages is creating `assets/assets` path
Labels: bug,needs triage

### Describe the bug

Hi team 👋 

I'm using Storybook 8 and deploying it to the GitHub Pages. The Storybook works but then it is doubling the `assets/assets` path instead of being just one `assets/`. All the files are correctly there, but for some reason, it is doubling the path 🤔 

![CleanShot 2024-04-16 at 10 49 19@2x](https://github.com/storybookjs/storybook/assets/5109593/fe25a424-f742-4ba8-8017-204648c7ef59)

I already checked for hours old bugs related to it, but couldn't find this scenario or attempt to fix it.

Thank you for the amazing work!!


### To Reproduce

main.ts
```js
import { join, dirname } from 'path';

/**
 * This function is used to resolve the absolute path of a package.
 * It is needed in projects that use Yarn PnP or are set up within a monorepo.
 */
function getAbsolutePath(value) {
  return dirname(require.resolve(join(value, 'package.json')));
}

/** @type { import('@storybook/vue3-vite').StorybookConfig } */
const config = {
  stories: ['../src/**/*.mdx', '../src/**/*.stories.@(js|jsx|mjs|ts|tsx)'],
  addons: [
    getAbsolutePath('@storybook/addon-links'),
    getAbsolutePath('@storybook/addon-essentials'),
    getAbsolutePath('@chromatic-com/storybook'),
    getAbsolutePath('@storybook/addon-interactions'),
  ],
  staticDirs: ['./public'],
  framework: {
    name: getAbsolutePath('@storybook/vue3-vite'),
    options: {},
  },
  docs: {
    autodocs: 'tag',
  },
};
export default config;
```

action.yml:
```yml
name: Build and Publish Storybook to GitHub Pages

on:
  push:
    branches:
      - 'develop'

jobs:
  deploy:
    steps:
      - uses: actions/checkout@v4

      - name: Build
        run: npm run build-storybook
        working-directory: packages/demo-components

      - name: Deploy
        uses: JamesIves/github-pages-deploy-action@v4
        with:
          branch: gh-pages
          folder: packages/demo-components/storybook-static
```

### System

```bash
Storybook Environment Info:

  System:
    OS: macOS 14.4.1
    CPU: (10) arm64 Apple M1 Pro
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.10.0 - ~/.nvm/versions/node/v20.10.0/bin/node
    npm: 10.5.2 - ~/.nvm/versions/node/v20.10.0/bin/npm <----- active
    pnpm: 8.6.2 - ~/.nvm/versions/node/v20.10.0/bin/pnpm
  Browsers:
    Safari: 17.4.1
```


### Additional context

_No response_
Repository: pytorch
Issue: Support `dynamic=True` in torch._dynamo.explain
Labels: low priority,triaged,oncall: pt2,module: dynamo

### 🚀 The feature, motivation and pitch

https://github.com/pytorch/pytorch/blob/main/torch/_dynamo/eval_frame.py#L628

When debugging a model/graph that requires to use `dynamic=True`, one cannot use `dynamo.explain` because the function  doesn't take arguments and the parameters are hardcoded here.

https://github.com/pytorch/pytorch/blob/main/torch/_dynamo/eval_frame.py#L662-L664

This leads to different graphs shown by explain and then later seen in the backend.

No longer passing the model args directly to explain already opened the way to pass the arguments directly to the `optimize` call.


### Alternatives

_No response_

### Additional context

Checked for open issues, but didn't find any.

cc @ezyang @msaroufim @bdhirsh @anijain2305 @chauhang @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng
Repository: neovim
Issue: custom lint rules for Lua code
Labels: enhancement,test,ci,lua

## Problem

We have clint.py for defining custom C lint rules, but we don't have a way to define custom rules for Lua code.

## Expected behavior

Introduce a build/CI task that allows us to define custom lint rules. Examples:

- disallow use of `assert.truthy`, recommend `ok()` / `eq()` / etc
- check `it()` descriptions
- comment format
- naming conventions
- ...

## Related

- https://github.com/Kampfkarren/selene claims to be "Easy to extend and modify".
- `gen_vimdoc.lua` (based on lpeg) has a partial Lua parser.
- `gen_help_html.lua` (based on treesitter) has some hacky custom rules for help files.
- https://github.com/lunarmodules/luacheck/issues/37 describes a way to "extend" Luacheck by forking/vendoring it.
- Related issue proposing LuaLS CI check: https://github.com/neovim/neovim/issues/24563
Repository: PowerToys
Issue: Ideas for resources
Labels: Idea-Enhancement,Area-Build

### Description of the new feature / enhancement

- The Settings file is huge. We can split off the OOBE and Flyout strings to a new file.
  - https://learn.microsoft.com/windows/uwp/app-resources/localize-strings-ui-manifest#factoring-strings-into-multiple-resources-files
  - Maybe OOBE and Flyout should be a separate project?
- There are a few cases where a module's **name** is set in a few redundant strings. We could remove the duplicates and re-use the remaining ones. (think of Settings > ModuleTitle versus OOBE and Navigation strings)
  - This also prevents different translations
- We can "squash" all the "Enable \<module>" into one general "Enable". Same for all the "Learn more about ..." HyperLinks.
  1. use "Enable {0}" where the name is filled in (or...)
  2. is `<Hyperlink><Run x:UID="LearnMore"><Run x:UID="ModuleName"></HyperLink>` possible?
- Every `data name="<modulename>.SecondaryLinksHeader"` is identical and thus redundant.
- Check for unused data.
  - src/modules/fancyzones/FancyZonesLib/Resources.resx
  - src/runner (e.g. STARTUP_DISABLED_BY_USER)
- Should we be using resX or resW?
Repository: storybook
Issue: [Bug]: The accessibility scan encountered an error. {"name":"TypeError"}
Labels: bug,needs triage

### Describe the bug

I am trying to load Storybook with the below plugins:

```js
  "@storybook/addon-a11y": "^7.5.0",
  "@storybook/addon-essentials": "^7.5.0",
  "@storybook/addon-links": "^7.5.0",
  "@storybook/web-components": "^7.5.0",
  "@web/dev-server": "^0.4.3",
  "@web/storybook-builder": "^0.1.7",
  "@web/storybook-framework-web-components": "^0.1.1"
        ......
```        

I am encountering the below error. Not sure if this something related to storybook config or if from the @web-dev-server` side.

![Screenshot 2024-04-16 at 5 00 35 PM](https://github.com/storybookjs/storybook/assets/8790510/8aea850e-a1f9-45de-a82c-0355f9ddacae)



### To Reproduce

Goto [here](https://opensource.adobe.com/spectrum-web-components/storybook/index.html?path=/story/accordion-densities-compact--s)
Press `d`
Check `Accessibility` Tab

### System

```bash
"storybook": "^7.5.0",
```


### Additional context

_No response_
Repository: next.js
Issue: Custom 404 page not used for Server Side Rendered page returning notFound when using the edge runtime
Labels: bug

### Link to the code that reproduces this issue

https://github.com/gabrielf/next-404-repro

### To Reproduce

1. clone repo and run `npm i`
2. `npm run dev`
3. click the http://localhost:3000/

### Current vs. Expected behavior

Expected: To see the _custom_ 404 page
Actual: The _default_ 404 page is shown

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.4.0: Fri Mar 15 00:12:49 PDT 2024; root:xnu-10063.101.17~1/RELEASE_ARM64_T6020
  Available memory (MB): 16384
  Available CPU cores: 12
Binaries:
  Node: 18.18.2
  npm: 9.8.1
  Yarn: 1.22.22
  pnpm: 8.15.5
Relevant Packages:
  next: 14.2.1 // Latest available version is detected (14.2.1).
  eslint-config-next: 14.2.1
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.4.5
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Not sure

### Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local)

### Additional context

A similar bug used to exist for SSR pages but was triggered by i18n, this time it's SSR + the edge router that triggers the same behavior.
Repository: flutter
Issue: Both java and kotlin Android app templates depend on Kotlin Gradle Plugin
Labels: platform-android,tool,t: gradle,P2,team-android,triaged-android

I noticed some time ago that both `android-java.tmpl` nad `android-kotlin.tmpl` templates depend on Kotlin Gradle Plugin:

https://github.com/flutter/flutter/blob/9aea02b7d5a8f5bfd987bc85543d13eae6fe1c53/packages/flutter_tools/templates/app_shared/android.tmpl/settings.gradle.tmpl#L22

https://github.com/flutter/flutter/blob/9aea02b7d5a8f5bfd987bc85543d13eae6fe1c53/packages/flutter_tools/templates/app_shared/android-java.tmpl/app/build.gradle.tmpl#L5

https://github.com/flutter/flutter/blob/9aea02b7d5a8f5bfd987bc85543d13eae6fe1c53/packages/flutter_tools/templates/app_shared/android-kotlin.tmpl/app/build.gradle.tmpl#L5

furthermore the `app/build.gradle.tmpl` file is exactly the same in both Java and Kotlin template.

My aim with this issue is to learn why it's like that. I remember being confused some time ago when I selected "java" during `flutter create` but my project still depended on KGP.

cc @reidbaker
Repository: ui
Issue: Shadcn keeps installing dependecies infinitely in nextj project
Labels: bug

### Describe the bug

Hope you are all fine.

Kindly, I am asking for support related to a problem with shadcn installation.
When I try to run the command **npx shadcn-ui@latest init**, it keeps installing dependecies and no more results for hours. 
Attached there is an image of the scenario.

_System parameters_:
- Windows 11
- Node JS 21.7.3


Can anyone help me with this issue please?

Thanks in advance!

![shadcn](https://github.com/shadcn-ui/ui/assets/100233989/38c0a836-177e-480d-8a42-83659c62df06)


### Affected component/components

Infinite installation

### How to reproduce

Cannot run shadcn command for installation in next js project.

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Windows 11,
Node JS 21.7.3
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: flutter
Issue: go_router: Common interface for type-safe routes to allow passing GoRouteData and calling .go
Labels: c: new feature,package,c: proposal,P3,p: go_router,team-go_router,triaged-go_router

### Use case

I'd like to be able to pass around type-safe go-routes at runtime, so a common page can redirect to new pages, based on what called the common page.

I'd really love to be able to do something like this:

```dart
class RouteButton extends StatelessWidget {
    final GoRouteData route;

    const RouteButton({super.key, required this.route});

    @override
    Widget build(BuildContext context, WidgetRef ref) {
        return ElevatedButton(
            child: Text("Go"),
            onPressed: () => route.go(context),
        );
    }
```

(To be more accurate, I'd love to pass `GoRouteData` to pages so they can easily redirect or go back without relying on the navstack.)

But, `.go(context)` is not a part of the GoRouteData definition; in fact, it's an extension method that's generated and added to every single new route you create, one by one. So there's no shared interface to call `.go` on!

If anyone has any thoughts I'd love to hear them. Cheers.

### Proposal

The example above as written demonstrates what I'd like to be able to achieve.
Repository: material-ui
Issue: [material-ui] Standardize event handler callbacks
Labels: package: material-ui,enhancement

Review, design, and standardize the event handler callback signatures across the library.

Some are marked to be modified: https://github.com/mui/material-ui/blob/next/packages/mui-material/src/internal/SwitchBase.js#L116-L119

While others aren't: https://github.com/mui/material-ui/blob/next/packages/mui-material/src/Select/SelectInput.js#L258

With the Base UI refactor on the horizon, this issue should be handled alongside it, as it will be tightly related. For example, while working on https://github.com/mui/material-ui/pull/40210, one of the blockers was that the Select component's `onChange` second argument was not supported by Base UI.

Overall, we should decide the optimal way to support custom callback signatures or if we should only rely on events API.

**Search keywords**:
Repository: godot
Issue: EditorToaster does not expose `_popup_str` anymore, regression in 4.3.dev3
Labels: discussion,topic:editor

### Tested versions

v4.3.dev3.official [36e943b6b]
v4.3.dev4.official [df78c0636]
v4.3.dev5.official [89f70e98d]

### System information

Godot v4.3.dev5 - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1080 Ti (NVIDIA; 31.0.15.5152) - AMD Ryzen 9 7900X 12-Core Processor (24 Threads)

### Issue description

I try to use the `EditorToaster` from the editor by getting the node and `_editor_toaster.call("_popup_str", message, severity, tooltip)`. Since `v4.3.dev3.official [36e943b6b]` the method is not callable anymore.

The last time it worked was in `v4.3.dev2.official [352434668]`.

### Steps to reproduce

Open the MRP and enable/disable the plugin, which will trigger the toster.

### Minimal reproduction project (MRP)

[toaster_example.zip](https://github.com/godotengine/godot/files/14998120/toaster_example.zip)
Repository: godot
Issue: Godot should pre-compile C# project on load to prevent scene data loss with collaborative workflow
Labels: enhancement,feature proposal,topic:dotnet

### Tested versions

- Reproducible in version 4.3 Dev 5 snapshot

### System information

Windows 10 & 11

### Issue description

I have been working on a personal project of mine using Godot 4.3 Dev 5 between two computers, my main desktop (Windows 10) and my laptop (Windows 11) using Git. The majority of my project is written in C# and feel like this may only affect C#.

What I have been noticing is that when I make substantial changes in classes that utilize Export vars and resources on one machine, when I pull latest on Git on the other machine and load the project, Godot hasn't compiled the new changes and therefore cannot find objects and variables that the Scene is expecting as attached to parent nodes.
So what it ends up doing is removing the references and paths to these Nodes which in turn can cause data loss if you aren't paying attention. A workaround I have found is to look at my Git changelist, revert those tscn files that should not have been changed, and return to Godot and tell it to reload those files from disk.

If my assessment of this issue is correct, then I believe what could fix it is to have Godot try to compile the C# project before loading up the Scene files (and potentially other file types that might benefit from a pre-compile). This should ensure everything is synchronized before-hand.

### Steps to reproduce

- Create a project with a .NET build of Godot.
- Create a C# script and inherit from something like Control. (I'm sure other types will work)
- Create a new scene and add an instance of that node and attach the script
- Save all and commit it to Git
- On a different machine, pull latest, and load up the project
- Alter the C# script so that it has new Export vars 
- Add new nodes of those Export types to the scene and then attach them to your parent node (the one created on the 1st machine)
- Save the project and commit to Git
- Return to the 1st machine and pull latest
- Load up the project and see if Godot fails to find the changes and children paths created on the 2nd machine. (You should also see the warning in the Inspector that you may need to recompile C#)

### Minimal reproduction project (MRP)

I can make a MRP if necessary, though I believe the steps above should be enough to reproduce the issue.
Repository: flutter
Issue: Add option to only expand floating SliverAppBar when scrolled to the top
Labels: c: new feature,framework,f: material design,f: scrolling,c: proposal,P3,team-design,triaged-design

### Use case

Having a SliverAppBar with `pinned: false, floating: true` and a not-null `expandedHeight`, the AppBar is collapsed and hidden when scrolling down and pops in and is expanded again when scrolling up. 

However, I would like for it to stay collapsed until the scroll view is scrolled all the way to the top again, at which point it should expand again.

See also this [StackOverflow post](https://stackoverflow.com/q/72361410/9335596) asking how to achieve this, including two flawed workarounds in the answers.

### Proposal

Implement this behavior, with a corresponding SliverAppBar parameter (for instance `bool expandOnlyAtTop = false`) that enables it.
Repository: next.js
Issue: App router - server side redirect during client side push causes the page to disappear
Labels: bug,Navigation

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/gracious-raman-lf2wwt

### To Reproduce

1. Click the test button
2. Notice the page disappears during the loading sequence

How it's working:
1. Client-side `router.push` to `?test=1` causes the server to redirect to `?test=2`
2. While loading `?test=2` the server delays 2 seconds.
3. During that 2 seconds, you'll see the button (the `page.tsx`) to fully unload.

### Current vs. Expected behavior

I would expect that the page does not change at all. There are no suspense boundaries and the behavior persists if you wrap the `router.push()` in a `startTransition()`. My uneducated guess: this appears to be an issue with how `redirect()` throws an exception and how that fallback is processed through to the client.

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
  Available memory (MB): 32682
  Available CPU cores: 32
Binaries:
  Node: 20.11.1
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.2.1 // Latest available version is detected (14.2.1).
  eslint-config-next: 14.1.0
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.2
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

App Router, Routing (next/router, next/navigation, next/link)

### Which stage(s) are affected? (Select all that apply)

next dev (local), Other (Deployed)

### Additional context

Tested on `4.2.1` and `14.3.0-canary.5`. I updated the sandbox version to `^14.3.0-canary.5`
Repository: vscode
Issue: Explore using tree sitter for syntax highlighting
Labels: feature-request,grammar,exploration

Goals of the explorations:
- Get Aiday's exploration up and running again: https://github.com/microsoft/vscode/pull/161479
- Come up with ideas for a contribution model
- Confirm performance findings from https://github.com/microsoft/vscode/pull/161479 and understand incremental highlighting
Repository: ui
Issue: [bug]: Dark Mode doesn't work with CSS Variables set to false
Labels: bug

### Describe the bug

Before I begin, I would like to apologize if I get anything wrong because it's my second ever Github Issue submission.
Basically, I'm using Astro.js and I followed the installation guide to install shadcn/ui and also followed the guide for how to add a dark-mode switch button. I analysed my code and the code provided by shadcn/ui and it turned out that the "dark" class was being applied to my <html> tag properly and the components had "dark:" tags as well but they wouldn't have any effect. I tried reinstalling shadcn multiple times, freshly creating new astro projects and trying to get it to work on a new, simple astro project (which kind of applied dark mode on some elements but not properly).
It turns out the issue was with CSS variables. Once I re-initialize shadcn and set CSS variables to True, it works again.

### Affected component/components

All

### How to reproduce

N/A

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
N/A
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: ui
Issue: [bug]: Command component key event don't work
Labels: bug

### Describe the bug

The Command key (arrow down/up) event don't work if don't put it in `CommandDialog` when component use groups.

### Affected component/components

Command, ComboBox

### How to reproduce

1. Copy the basic example at [doc](https://ui.shadcn.com/docs/components/command)
2. Choose a hover card to trigger the command show event.
3. press key up or down to see that.

### Codesandbox/StackBlitz link

https://codesandbox.io/p/devbox/shadcn-ui-s9x785?file=%2Fapp%2Fpage.tsx%3A24%2C11

### Logs

_No response_

### System Info

```bash
"dependencies": {
    "@radix-ui/react-dialog": "^1.0.5",
    "@radix-ui/react-hover-card": "^1.0.7",
    "class-variance-authority": "^0.7.0",
    "clsx": "^2.1.0",
    "cmdk": "^0.2.1",
    "lucide-react": "^0.368.0",
    "next": "14.2.1",
    "react": "^18",
    "react-dom": "^18",
    "tailwind-merge": "^2.2.2",
    "tailwindcss-animate": "^1.0.7"
  }
```
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: flutter
Issue: [Proposal] Extend LayoutBuilder to handle full app cases. 
Labels: framework,c: proposal,P3,team-framework,triaged-framework

When talking to an experienced user experience flutter dev about the difficulties in teaching others to build widgets in an adaptive way one of the complaints was that `MediaQuery.of`  the using size is very easy to use but inefficient because it triggers a rebuild on lots of changes unrelated to size. The more efficient way to change layout is `MediaQuery.sizeOf`which rebuilds only on size. 

The wrong way is easy to use and hard to catch in code review because of the similarity. In addition they mentioned that it is unclear what Media the `MediaQuery` object is referring too. 

In contrast if you want a widget to branch on the space available then `LayoutBuilder`'s api works well. 

This proposal suggest adding a sibling object to the existing builder of `LayoutBuilder` that is named something like `appBuilder` that under the hood uses MediaQuery.sizeof and then converts that data into a boxConstraints. In addition to help with discoverability we suggest that there is a localBuilder that has the existing behavior of builder. 

"It took me a long time to discover Dialog.fullscreen. I had no idea existed because it'd never show up in autocomplete."  

With this proposal we could suggest in our adaptive layout docs to only use LayoutBuilder.
Repository: ant-design
Issue: Visual glitch when opening a Modal containing an already opened Select
Labels: help wanted,Inactive,🧶 Low Priority,unconfirmed

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/p/sandbox/antd-reproduction-template-forked-4ygs88?file=%2Findex.js%3A22%2C13)

### Steps to reproduce

Click the "Open modal" button in the reproduction sandbox.

### What is expected?

The opened select should show up in perfect sync with the modal.

### What is actually happening?

Both components open at slightly different places, then are overlapping correctly.

| Environment | Info |
| --- | --- |
| antd | 5.1.6 |
| React | 18.2.0 |
| System | Windows 10 Pro |
| Browser | Firefox 124.0.2 |

---
A fix that works is to use the `getPopupContainer` attribute of `Select`, to specify that the modal content should be the container of the select. Concretely having the `getPopupContainer` callback returning this: `document.getElementsByClassName("ant-modal-content")[0]`.

But we'd rather avoid doing that and have the perfect synchronization working out the box.

Note: the glitch doesn't look that bad on the sandbox, but does look pretty bad in our application.

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->