sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: ui
Issue: [bug]: Select component when used in form does not populate in first time.
Labels: bug

### Describe the bug

```typescript
<FormField
                control={form.control}
                name="roleId"
                render={({ field }) => (
                  <FormItem>
                    <FormLabel className="font-normal">Role</FormLabel>
                    <div className="flex flex-col p-6 space-y-2 rounded-lg border shadow-sm">
                      <FormLabel>
                        Select Role
                        <span className="text-destructive">*</span>
                      </FormLabel>
                      <FormControl>
                        <Select
                          value={field.value}
                          onValueChange={(value) => field.onChange(value)}
                          disabled={
                            !router.asPath.includes("edit") && id ? true : false
                          }
                        >
                          <SelectTrigger className="max-w-80">
                            <SelectValue placeholder="Select Role" />
                          </SelectTrigger>
                          <SelectContent>
                            {rolesList?.data?.results?.map((role) => (
                              <SelectItem
                                key={role?.id}
                                value={role?.id?.toString()}
                              >
                                {role?.name}
                              </SelectItem>
                            ))}
                          </SelectContent>
                        </Select>
                      </FormControl>
                      <FormMessage />
                    </div>
                  </FormItem>
                )}
              />
``` 
this is the code form select that i've been using. When i go into edit page, the i have populated the fields but the select does not populate.

```typescript
const { data: adminDetail, isLoading: adminDetailLoading } = useQuery<IProps>(
    {
      queryKey: ["adminDetail", router.query?.id],
      queryFn: () => getAdminDetail(router.query?.id as string),
      onSuccess: (data) => {
        form.reset({
          firstName: data?.data?.firstName,
          lastName: data?.data?.lastName,
          email: data?.data?.email,
          contact: data?.data?.contact,
          status: data?.data?.status === "active" ? true : false,
          roleId: data?.data?.role?.id?.toString(),
        });
      },
    }
  );
``` 
i have used react query and the role id is not being set the first time. If i refresh the page then only the select is being populated. What seems to be the issue?

### Affected component/components

Select

### How to reproduce

.

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Chrome
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: neovim
Issue: vim.loader luac cache file names gets too long on ecryptfs
Labels: bug,lua,filetype

### Problem

vim.loader stores files stored in ~/.cache/nvim/luac and compiled files are encoded as full path to the original source file.
On linux OS when ecryptfs is enabled on home directory this leads to file names exceeding max file length (143 characters)
preventing plugin to be loaded.
This is similar but not exactly the same as  #25008

### Steps to reproduce

Enabling telescope with file-browser extension on Linux OS with ecryptfs enabled on home directory leads to the following error:
```
Failed to run `config` for telescope-file-browser.nvim
                                                                                                                                                                
...m/lazy/telescope.nvim/lua/telescope/_extensions/init.lua:10: 'file_browser' extension doesn't exist or isn't installed: vim/loader.lua:0: ENAMETOOLONG: name 
too long: /home/neg/.cache/nvim/luac/%2fhome%2fneg%2f.local%2fshare%2fnvim%2flazy%2ftelescope-file-browser.nvim%2flua%2ftelescope%2f_extensions%2ffile_browser%2
fmake_entry_utils.luac                                                                                                                                          
                                                                                                                                                                
# stacktrace:                                                                                                                                                   
  - /telescope.nvim/lua/telescope/_extensions/init.lua:10 _in_ **load_extension**                                                                               
  - /telescope.nvim/lua/telescope/_extensions/init.lua:62 _in_ **load_extension**                                                                               
  - ~/.config/nvim/lua/plugins/telescope.lua:17 _in_ **config**                                                                                                 
  - ~/.config/nvim/init.lua:17                 
```


### Expected behavior

Cached plugin file names should be wither hashes of target file names or stored in a way that file names does not exceed max file length.

### Neovim version (nvim -v)

v0.10.0

### Vim (not Nvim) behaves the same?

-

### Operating system/version

Debian 6.7.12-1 (2024-04-24) x86_64 GNU/Linux

### Terminal name/version

gnome-terminal

### $TERM environment variable

xterm-256color

### Installation

build from repo / official release binary
Repository: material-ui
Issue: [TextField][Autocomplete] When `autoComplete` prop is set, focus does not move to the next input on Tab in iOS
Labels: bug 🐛,component: text field,component: autocomplete,browser: Safari

On text field component. 

When the variant is set to outline and the auto complete prop is set upon clicking the auto complete suggestion on iOS the next input in the dom is not focused. 

Filled and standard variants work as expected. 


Here's is a example on the themes store I've also located:

https://minimals.cc/auth-demo/split/sign-up

https://github.com/mui/material-ui/assets/35478687/b886760d-f808-4fd4-9a20-658048f7057b

**Search keywords**:
Repository: ant-design
Issue: The tour does not scroll when the reference is hidden by the header component
Labels: Inactive,unconfirmed

### Reproduction link

[![Edit on StackBlitz](https://developer.stackblitz.com/img/open_in_stackblitz.svg)](https://stackblitz.com/edit/react-xpj9uh?file=demo.tsx)

### Steps to reproduce

I am using the Layout with the header form antd and once that I do a scroll in the screen and my antd buttons are hidden by the header, the tour does not force tot he screen to un-hide the button.
For reproduce it only click in the link and do all the scroll that you can, then, click "beging tour" button

### What is expected?

That the tour component force to scroll when the element is hide by another element too

### What is actually happening?

The tour component only force the scroll when is a component that is not in the viewport

| Environment | Info |
| --- | --- |
| antd | 5.16.4 |
| React | 18.2.0 |
| System | Mac |
| Browser | Google Chrome |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: node
Issue: Should node support subcommands?
Labels: feature request,cli

### What is the problem this feature will solve?

currently, node's cli interface is pretty simple and lean,
it mainly accepts flags that start with two dashes, or sometimes a single dash for some aliases.
additionally, many flags depend on each other or imply using another flag.

now that more and more flags are added to node, (and each new flag is heavily considered before adding to avoid options bloat), I propose we support a more complex cli interface with sub-commands.
this issue has come up before [when adding `node --run`](https://github.com/nodejs/node/pull/52190), and to avoid blocking that - the discussion was postponed, so I went ahead and opened this issue.

If I recall, the main concern was `node run` or `node test` is a breaking change since it today runs `node run.js` or `node test.js` accordingly - that can be addressed with releasing this gradually as semver-major with a deprecation warning for a few versions prior to the actual change

some groups/clusters of commands that might fit using sub commands:
- `node --run` 
- `node --watch`, `--watch-path`
- `node --test`
- `node --build-snapshot`

### What is the feature you are proposing to solve the problem?

N/A

### What alternatives have you considered?

_No response_
Repository: electron
Issue: [Bug]: The “backgroundColor” does not take effect immediately when the window is displayed
Labels: platform/macOS,bug :beetle:,has-repro-gist,31-x-y

### Preflight Checklist

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

### Electron Version

31.0.1

### What operating system are you using?

macOS

### Operating System Version

14.5 (23F79)

### What arch are you using?

arm64 (including Apple Silicon)

### Last Known Working Electron version

_No response_

### Expected Behavior

```
  const mainWindow = new BrowserWindow({
    width: 900,
    height: 670,
    show: false,
    autoHideMenuBar: true,
    backgroundColor: '#141414',
    ...(process.platform === 'linux' ? { icon } : {}),
    webPreferences: {
      preload: join(__dirname, '../preload/index.js'),
      sandbox: false
    }
  })
```

After creating the window, the background color should be “#141414”.

### Actual Behavior

The moment the window is displayed, the background color is white and immediately changes to “#141414”.

### Testcase Gist URL

_No response_

### Additional Information

_No response_
Repository: vscode
Issue: The Diff Editor "Next Change" action does not loop if there is a difference in the new line at the end of the files
Labels: bug,help wanted,diff-editor

Does this issue occur when all extensions are disabled? **Yes**

I am able to reproduce this issue on Windows with the latest build as well as on the Insiders Build on the web using https://insiders.vscode.dev/.


## Steps to Reproduce

1. Create 2 files to diff. One file should end with a new line and the other shouldn't.

Example:

**file1.txt**
```
This is the 1st sentence.

This is the second one.

This is number 3.

```

**file2.txt**
```
This is the first sentence.

This is the second one.

This is number 3.
```

2. Use the "Next Change" action to cycle through the changes. Notice how it does not loop back to the beginning after reaching the last difference between the files, which is the end of file new line.

## More Info

The "Previous Change" action works correctly and loops to the last difference when at the first difference. Also, the "Next Change" looping back to the first difference works correctly if the last difference is not a new line.

## Why does it matter?

It might seem like a minor issue, but I need to diff large files where often one of the files is missing the new line at the end. If I use "Previous Change" at the beginning of the files, I am taken to the last difference at the end of the files, and I cannot use "Next Change" to go back to the start.
Repository: PowerToys
Issue: Custom Fancy Zones In Tooltips
Labels: Needs-Triage

### Description of the new feature / enhancement

When a new custom fancy zone is created let it be an option in the tool tip when hovering over maximize window and for the selection of Fancy Zones at the top of the screen. 

### Scenario when this would be used?

Any time that a custom fancy zone is created and intended to be used. I have yet to find a way to use a custom fancy zone. Maybe a bug?

### Supporting information

Given a custom fancy zone has been created. The ability to use it remains elusive. Whatever mechanism exists for custom zones is not apparent and possibly non-functionable. It seems implicate that a created custom fancy zone would be shown in the tooltips when hoovering over maximize window button and the fancy zone layout selector at the top of the screen. Use case: with an ultra wide screen to have a window span two thirds of the right side of the screen (instead of two thirds of the left that is a default zone).
Repository: godot
Issue: Switching back to previously loaded scene fails using load_scene_from_packed
Labels: topic:editor,needs testing

### Tested versions

- 4.2 stable

### System information

Godot v4.2.2.stable.mono - Ubuntu 24.04 LTS 24.04 - Wayland - Vulkan (Forward+) - integrated Intel(R) HD Graphics 4400 (HSW GT2) () - Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz (4 Threads)

### Issue description

When assigning ```PackedScene```s in the inspector, switching from scene ```A``` to scene ```B``` using ```get_tree().change_scene_to_packed(scene)``` will not let you go from ```B``` back to ```A``` using the same method, with the status not being ```OK``` (instead, 31 or ```ERR_INVALID_PARAMETER``` is returned).

Using ```status = get_tree().change_scene_to_file(scene.resource_path)``` throws an error instead.

Tested using 3 scenes instead of 2, but ```A -> B -> C``` again doesn't let you go back to ```A``` from ```C```

**Also discovered**
*In three scene mode*
When the project is re-opened, none of the three scenes can be opened, with the ```Broken Dependencies``` popup showing up, without any broken dependencies. Opening up any of the other two scenes will also show up the same error pointing to the next scene, the scene specified in the export field. This problem persists until the reference is removed from the resource file through a text editor.

### Steps to reproduce

Project given.
In the ```script.gd``` file, a boolean parameter is provided to switch between using ```change_scene_to_packed()``` and ```change_scene_to_file()```. An exported ```PackedScene``` is provided as the scene to transition to. The main page (first scene) is just to select which scene to start with, and has no other effect. Other 2 (3 scenes available) scenes have their numbers put on buttons to differentiate them. Pressing the button takes you to the next scene (scene 2 back to scene 1).

### Minimal reproduction project (MRP)

[godot_bug_circular_scene.zip](https://github.com/user-attachments/files/15863498/godot_bug_circular_scene.zip)
Repository: tauri
Issue: [bug] resource_dir_from() function, used for looking up resource files - not yet implemted for IOS?
Labels: type: bug,status: needs triage,platform: iOS

### Describe the bug

Not sure to classify this as a bug, I know that you are working hard on getting V2 ready. 

I've been looking at adding binary files to my IOS app, but traced the error down to the above mentioned function returning `Err:UnsupportedPlatform`. I'm uncertain how this is intended to work under IOS?

### Reproduction

Calling ```    const allFiles = await readDir('.', {
      baseDir: BaseDirectory.Resource,
    });
``` will throw error `unknown path`

### Expected behavior

Content of resource folder should be returned.

### Full `tauri info` output

```text
[✔] Environment
    - OS: Mac OS 14.5.0 X64
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.77.2 (25ef9e3d8 2024-04-09)
    ✔ cargo: 1.77.2 (e52e36006 2024-03-26)
    ✔ rustup: 1.27.1 (2024-04-24)
    ✔ Rust toolchain: stable-aarch64-apple-darwin (environment override by RUSTUP_TOOLCHAIN)
    - node: 20.14.0
    - pnpm: 9.1.4
    - yarn: 1.22.21
    - npm: 10.7.0

[-] Packages
    - tauri [RUST]: 2.0.0-beta.22
    - tauri-build [RUST]: no manifest (2.0.0-beta.17, 2.0.0-beta.17)
    - wry [RUST]: 0.40.1
    - tao [RUST]: 0.28.1
    - tauri-cli [RUST]: 2.0.0-beta.20
    - @tauri-apps/api [NPM]: 2.0.0-beta.13
    - @tauri-apps/cli [NPM]: 2.0.0-beta.20

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist/spa
    - devUrl: http://localhost:9000/
    - framework: Vue.js (Quasar)
    - bundler: Vite
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: ant-design
Issue: 希望恢复表格设置body固定高度的API
Labels: 💡 Feature Request

### What problem does this feature solve?

解决表格内容变化时，下面的分页部分不会上下随意跳动

### What does the proposed API look like?

bodyHeight或者是style增加body部分，其值可以是数字，百分比

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: next.js
Issue: GlobalError reset issue (Cannot read properties of null (reading 'get'))
Labels: bug

### Link to the code that reproduces this issue

https://github.com/ekerik220/global-error-debug

### To Reproduce

1. Start the application in production mode (pnpm build -> pnpm start).
2. Refresh the page until an error occurs (50% chance).
3. Press the 'Try again' button. A new error should appear (Cannot read properties of null (reading 'get')).

### Current vs. Expected behavior

Following the above steps, I expected the app to be re-rendered (possibly encountering the 50% chance error again and therefore causing the global error to be rendered again with the same error as before, or possibly rendering the root layout content without an error). What actually happened is I encountered a different error after pressing the reset button.

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.1.0: Mon Oct  9 21:28:12 PDT 2023; root:xnu-10002.41.9~6/RELEASE_ARM64_T8103
  Available memory (MB): 16384
  Available CPU cores: 8
Binaries:
  Node: 20.7.0
  npm: 10.2.5
  Yarn: 1.22.18
  pnpm: 8.14.1
Relevant Packages:
  next: 14.2.4 // Latest available version is detected (14.2.4).
  eslint-config-next: 14.2.4
  react: 18.3.1
  react-dom: 18.3.1
  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 start (local)

### Additional context

This is my first time using a GlobalError, so I apologize if I've just made some mistake in how it's supposed to be used. 

I've basically just ran pnpm create next-app and then added a global-error.tsx to the app folder and added a client component to the root layout that has a 50% chance of throwing an error. If I move the client component to page.tsx instead and create an error.tsx for the page the reset seems to work properly.
Repository: ant-design
Issue: Cascader 组件 hover 多层级（超出屏幕），会导致无法选择
Labels: Inactive,unconfirmed

### Reproduction link

[https://codepen.io/eng-LIU/pen/pompOGb](https://codepen.io/eng-LIU/pen/pompOGb)

### Steps to reproduce

如链接所示

### What is expected?

可以任意选择其中一个节点

### What is actually happening?

选择3 4 5 6等等，无法选择（收缩 展开）

| Environment | Info |
| --- | --- |
| antd | 5.18.1 |
| React | latest |
| System | MacOS Ventura 13.5.1 |
| Browser | Chrome 125.0.6422.142 |

---
原因分析：
1. hover 超出屏幕，下拉浮窗会自动计算相对屏幕的偏移量（不断 hover 到最后一层节点）
2. 绑定的 mouseenter 事件在同一个点触发（创建的新节点会触发事件），导致超出外的节点都会显示出来
3. 选择其他元素会产生展开或者收缩，无法选择（例：选择重现链接中3 4 5 6节点）
4. 期待有好的解决方式或者情况说明

### 重现代码（附）

```jsx
const { createRoot } = ReactDOM;

const {  Cascader, Input, Row, Col, Form  } = antd;
const FormItem = Form.Item;
const options = [
  {
    value: 1,
    label: 1,
    children: [
      {
        value: 2,
        label: 2,
        children: [
          {
            value: 3,
            label: 3,
            children: [
              {
                value: 4,
                label: 4,
                children: [
                  {
                    value: 5,
                    label: 5,
                    children: [
                      {
                        value: 6,
                        label: 6,
                        children: [
                          {
                            value: 7,
                            label: 7,
                            children: [
                              {
                                value: 8,
                                label: 8
                              }
                            ]
                          }
                        ]
                      }
                    ],
                  }
                ]
              },
              {
                value: '3-1',
                label: '3-1',
              },
              {
                value: '3-2',
                label: '3-2'
              }
            ],
          }
        ],
      }
    ],
  }
    
];
const onChange = (value) => {
  console.log(value);
};
const App = () => (
  <Form>
    <Row gutter={20}>
      <Col span={18}>
        <FormItem label="Cascader 正常情况">
          <Cascader
            options={options}
            maxTagCount="responsive"
            expandTrigger="hover"
            multiple
            showCheckedStrategy={Cascader.SHOW_CHILD}
            onChange={onChange}
          />
        </FormItem>
      </Col>
      <Col span={6}>
        <FormItem label="Cascader 超出屏幕">
          <Cascader
            options={options}
            maxTagCount="responsive"
            expandTrigger="hover"
            multiple
            showCheckedStrategy={Cascader.SHOW_CHILD}
            onChange={onChange}
          />
        </FormItem>
      </Col>
    </Row>
  </Form>
);
const ComponentDemo = App;

createRoot(mountNode).render(<ComponentDemo />);
```

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: bitcoin
Issue: Setting `bip32derivs` to `false` with `walletprocesspsbt` includes `bip32_derivs` for outputs.
Labels: Feature,Wallet,RPC/REST/ZMQ

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

I'd like an option to remove the `bip32derivs` from outputs as well as inputs when calling `walletprocesspsbt`.

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

I am using Bitcoin Core to create psbt's which are meant to be passed around to multiple users for collaborative transactions. I want to leak as little data as possible. When I set `bip32derivs` to `false` with `walletprocesspsbt` it does not remove the `bip32derivs` for outputs.

### Describe the solution you'd like

I would like to be able to specify whether or not `bip32derivs` are included in outputs with `walletprocesspsbt`.

### Describe any alternatives you've considered

_No response_

### Please leave any additional context

_No response_