sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: angular
Issue: docs:  Version dropdown on v18.angular.dev redirects to incorrect URL and lacks clarity in version listing
Labels: help wanted,good first issue,area: docs-infra

### Describe the problem that you experienced

The problem is with the version dropdown on https://v18.angular.dev/. 
When selecting v18 from the dropdown, it incorrectly redirects users to https://angular.dev/ instead of staying on https://v18.angular.dev/. 

Additionally, the dropdown lists versions from v2 to v18 and next, but it doesn't clarify the stable version or provide explicit links for versions beyond v18. This behavior causes confusion for users seeking version-specific documentation.

### Enter the URL of the topic with the problem

https://v18.angular.dev

### Describe what you were looking for in the documentation

_No response_

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

I would like the following improvements to address the problem:

1. **Correct Redirection**: Selecting v18 from the version dropdown on https://v18.angular.dev/ should not redirect to https://angular.dev/. Instead, it should stay on https://v18.angular.dev/.
2. **Stable Version Clarity**: The dropdown should include an option labeled stable, which links to the latest stable documentation version, currently https://angular.dev/.
3.  **Comprehensive Version Listing**: The dropdown should explicitly list all versions, including those beyond v18 (e.g., v19, v20) as they are released, for easy navigation without ambiguity.

These changes will ensure a more intuitive and seamless user experience when navigating between Angular versions.

### Add a screenshot if that helps illustrate the problem

![Image](https://github.com/user-attachments/assets/03c3929e-7ed4-4a5a-be33-d6ac988f343a)


### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```
Repository: langchain
Issue: GraphCypherQAChain Issue with Node Names Containing Spaces
Labels: 🤖:bug

### Checked other resources

- [X] I added a very descriptive title to this issue.
- [X] I searched the LangChain documentation with the integrated search.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I am sure that this is a bug in LangChain rather than my code.
- [X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

### Example Code

from langchain.chains import GraphCypherQAChain
chain = GraphCypherQAChain.from_llm(graph=graph, llm=llm, verbose=True, allow_dangerous_requests=True)
response = chain.invoke({"What is Lana Fathima current  Medical Condition "})

### Error Message and Stack Trace (if applicable)

 {code: Neo.ClientError.Statement.SyntaxError} {message: Invalid input 'Condition': expected a parameter, '&', ')', ':', 'WHERE', '{' or '|' (line 2, column 70 (offset: 76))
"MATCH (p:Person {id: 'Lana Fathima'})-[:DIAGNOSED_WITH]->(mc:Medical Condition)"

### Description

If the node Name is having space in between the genrated cypher query should have
 MATCH (p:Person {id: 'Lana Fathima'})-[:DIAGNOSED_WITH]->(mc:'Medical Condition')
 rather it is genration cypher query "MATCH (p:Person {id: 'Lana Fathima'})-[:DIAGNOSED_WITH]->(mc:Medical Condition)"
 hence it is throughting syntax error

### System Info


System Information
------------------
> OS:  Linux
> OS Version:  #1 SMP PREEMPT_DYNAMIC Fri Jul 12 20:45:27 UTC 2024
> Python Version:  3.9.20 (main, Sep  9 2024, 00:00:00) 
[GCC 11.5.0 20240719 (Red Hat 11.5.0-2)]

Package Information
-------------------
> langchain_core: 0.3.18
> langchain: 0.3.7
> langchain_community: 0.3.7
> langsmith: 0.1.143
> langchain_experimental: 0.3.3
> langchain_huggingface: 0.1.2
> langchain_milvus: 0.1.7
> langchain_ollama: 0.2.0
> langchain_openai: 0.2.9
> langchain_text_splitters: 0.3.2
> langchainhub: 0.1.21
> langgraph: 0.2.52

Optional packages not installed
-------------------------------
> langserve

Other Dependencies
------------------
> aiohttp: 3.11.0
> async-timeout: 4.0.3
> dataclasses-json: 0.6.7
> httpx: 0.27.2
> httpx-sse: 0.4.0
> huggingface-hub: 0.26.2
> jsonpatch: 1.33
> langgraph-checkpoint: 2.0.4
> langgraph-sdk: 0.1.36
> numpy: 1.26.4
> ollama: 0.3.3
> openai: 1.54.4
> orjson: 3.10.11
> packaging: 24.2
> pydantic: 2.9.2
> pydantic-settings: 2.6.1
> pymilvus: 2.4.9
> PyYAML: 6.0.2
> requests: 2.32.3
> requests-toolbelt: 1.0.0
> sentence-transformers: 3.3.1
> SQLAlchemy: 2.0.35
> tenacity: 9.0.0
> tiktoken: 0.8.0
> tokenizers: 0.20.3
> transformers: 4.46.3
> types-requests: 2.32.0.20241016
> typing-extensions: 4.12.2
Repository: kubernetes
Issue: is disk block io support?
Labels: kind/support,sig/node,needs-triage

### What would you like to be added?

As we can know that cgroupv2 is support blow config:
```json
"blockIO": {
    "weight": 10,
    "leafWeight": 10,
    "weightDevice": [
        {
            "major": 8,
            "minor": 0,
            "weight": 500,
            "leafWeight": 300
        },
        {
            "major": 8,
            "minor": 16,
            "weight": 500
        }
    ],
    "throttleReadBpsDevice": [
        {
            "major": 8,
            "minor": 0,
            "rate": 600
        }
    ],
    "throttleWriteIOPSDevice": [
        {
            "major": 8,
            "minor": 16,
            "rate": 300
        }
    ]
}
```
I want add disk io limit at the pod devicemount part,but is not support.

This is my idea about how to support it.

1. CRI runtime use the containerd which is open the nri.
2. Add the annotations to the pod which is Representative disk io set.
3. Write the custom nri plugin (change the annotations to the oci.runtime.spec block io part).

### Why is this needed?

If some pods in the same node is io busy, The performance of other Pods will be affected.
Repository: deno
Issue: Streams: writableStreamDefaultControllerGetChunkSize undefined strategy case slightly broken
Labels: web

See https://github.com/whatwg/streams/pull/1333.

Per https://github.com/denoland/deno/blob/4700f12ddc5427797333278d2a1d3a8e1195ebfc/ext/web/06_streams.js#L4445, Deno has the same bug as the reference implementation did: it catches the exception caused by trying to call `undefined` as a function, and then attempts to error the stream with it.

I don't believe this is observable since the stream is already erroring so the "TypeError: cannot call undefined" will not actually be exposed to the web developer.

However, it's probably best to fix this.
Repository: vscode
Issue: Toggle comment doesn't work on new PHP file
Labels: bug,editor-comments

<!-- ⚠️⚠️ 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.95.3
- OS Version: Windows 11

Steps to Reproduce:

1. open VSCode
2. create PHP file (don't type anything inside)
3. press ctrl+/ (`editor.action.commentLine`)

Expected:
The line to be commented

Actual:
nothing

![Image](https://github.com/user-attachments/assets/8e133294-aa20-4e1c-a73f-9db38d7b9105)


type anything inside the file
now ctrl+/ works

it used to work in VSCode 1.75.1, but broke in 1.76.0

does not affect any other language
Repository: PowerToys
Issue: Switch all `[DataTestMethod]` to `[TestMethod]`
Labels: Needs-Triage

See https://github.com/microsoft/testfx/issues/4166
Repository: vscode
Issue: Support workspace-folder matching for `files.exclude` in user settings
Labels: feature-request,file-explorer

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
# Background

`files.exclude` matches files under the opened workspace-folder now and cannot use absolute path to match the specified workspace-folder. For example:
```json
{
  "files.exclude": {
    "pnpm-lock.yaml": true
  }
}
```
This user settings will exclude all `pnpm-lock.yaml` files in every workspace.
Why not use workspace settings? Because `.vscode` isn't ignored by git in my project, the changes of `files.exclude` is extremely apt to cause conflicts.

# Expected

Like this: 
```json
{
  "files.exclude": {
    "pnpm-lock.yaml": {
      "when": {
        "workspaceFolder.name": "<specified-name>"
      }
    }
  }
}
```
Or support absolute path matching:
```json
{
  "files.exclude": {
    "/absolute/path/to/workspace-folder/pnpm-lock.yaml": true
  }
}
```
Repository: rust
Issue: Deprecate `std::time::Instant::saturating_duration_since()`?
Labels: T-libs-api,T-libs,C-discussion

As previously suggested here: https://github.com/rust-lang/rust/pull/84448#issuecomment-944421516

Starting from #89926, [`std::time::Instant::duration_since()`](https://doc.rust-lang.org/1.82.0/std/time/struct.Instant.html#method.duration_since) effectively does the same thing as the later introduced [`std::time::Instant::saturating_duration_since()`](https://doc.rust-lang.org/1.82.0/std/time/struct.Instant.html#method.saturating_duration_since) (they are now literally identical). Given that this was a possibly breaking change that has already passed, I propose the latter function for deprecation and subsequent removal, as it currently creates the false ambiguity.

The only objection I see is that the current state of affairs allows to bring back `panic!` in the future, as mentioned in a comment here:
https://doc.rust-lang.org/1.82.0/src/std/time.rs.html#143-144
Repository: ant-design
Issue: ConfigProvider组件里注入的组件className是否能支持组件的popupClassName
Labels: Inactive,👷🏻‍♂️ Someone working on it

### What problem does this feature solve?

现在在ConfigProvider中为组件注入的className只会被添加到组件本身，但是对于像Select组件，它携带了下拉列表，这种脱离了Select组件，因此注入的className没法对下拉弹窗进行样式覆盖，需要单独给Select组件传递popupClassName去对下拉列表进行样式覆盖

### What does the proposed API look like?

ConfigProvider支持为组件注入popupClassName，满足开发者能够覆盖下下拉列表样式

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: angular
Issue: ResourceStatus of the resource should be string literal instead of enum
Labels: area: core,core: reactivity,cross-cutting: signals

### Which @angular/* package(s) are relevant/related to the feature request?

core

### Description

Enums in TS are not great. Even though there are use-cases where they are appropriate, most of the time string literals do the job better. I believe `ResourceStatus` should be a string literal.

Keeping `ResourceStatus` as `enum` will result in increased boilerplate without any added benefits:

Example using enum:
```ts
import { ResourceStatus } from '@angular/core'; // this import could be removed with string literals

@Component({
  template: `
    <-- this could be simply comparing to string literal without any lose of strict type checking --/>
    @if (countriesResource.status() === status.Resolved) {
      ...
    }
  `,
})
export class AppComponent {
  readonly #http = inject(HttpClient);
  status = ResourceStatus; // // this property could be removed with string literals
  countriesResource = rxResource({
    loader: () =>
      this.#http.get<Country[]>('https://restcountries.com/v3.1/all'),
  });
}
```

Example using string literal:
```ts
@Component({
  template: `
    @if (countriesResource.status() === 'resolved') {
      ...
    }
  `,
})
export class AppComponent {
  readonly #http = inject(HttpClient);
  countriesResource = rxResource({
    loader: () =>
      this.#http.get<Country[]>('https://restcountries.com/v3.1/all'),
  });
}
```

There is already confusion about how to check the value of the status in the template [here](https://github.com/angular/angular/issues/58854#issuecomment-2498674168)

### Proposed solution

```ts
export type ResourceStatus =
  | 'idle'
  | 'error'
  | 'loading'
  | 'reloading'
  | 'resolved'
  | 'local';
```

### Alternatives considered

none
Repository: go
Issue: x/net: incorrect parsing of rt_msghdr errno on Darwin
Labels: NeedsInvestigation

### Go version

x/net v0.31.0

### Output of `go env` in your module/workspace:

```shell
GO111MODULE=''
GOARCH='arm64'
GOBIN=''
GOCACHE='/Users/spike/Library/Caches/go-build'
GOENV='/Users/spike/Library/Application Support/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='arm64'
GOHOSTOS='darwin'
GOINSECURE=''
GOMODCACHE='/Users/spike/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='darwin'
GOPATH='/Users/spike/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/opt/homebrew/Cellar/go@1.21/1.21.8/libexec'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/opt/homebrew/Cellar/go@1.21/1.21.8/libexec/pkg/tool/darwin_arm64'
GOVCS=''
GOVERSION='go1.21.8'
GCCGO='gccgo'
AR='ar'
CC='cc'
CXX='c++'
CGO_ENABLED='1'
GOMOD='/dev/null'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -ffile-prefix-map=/var/folders/53/zffdtv3x7lg_pyhrk85p7_nw0000gn/T/go-build2233440794=/tmp/go-build -gno-record-gcc-switches -fno-common'
```


### What did you do?

I read the source and spotted an error.

### What did you see happen?

I believe the parsing of route messages in https://go.googlesource.com/net/+/refs/tags/v0.31.0/route/route_classic.go is incorrect for Darwin (presumably other BSD variants). In particular it parses the errno from `28:32` in the header.

However, the header (https://github.com/apple-oss-distributions/xnu/blob/33de042d024d46de5ff4e89f2471de6608e37fa4/bsd/net/route.h#L158) looks like:

```
struct rt_msghdr {
	u_short rtm_msglen;     /* to skip over non-understood messages */
	u_char  rtm_version;    /* future binary compatibility */
	u_char  rtm_type;       /* message type */
	u_short rtm_index;      /* index for associated ifp */
	int     rtm_flags;      /* flags, incl. kern & message, e.g. DONE */
	int     rtm_addrs;      /* bitmask identifying sockaddrs in msg */
	pid_t   rtm_pid;        /* identify sender */
	int     rtm_seq;        /* for sender to identify action */
	int     rtm_errno;      /* why failed */
	int     rtm_use;        /* from rtentry */
	u_int32_t rtm_inits;    /* which metrics we are initializing */
	struct rt_metrics rtm_rmx; /* metrics themselves */
};
```

`errno` is immediately after the `rtm_seq`, which are sliced as `20:24`, meaning it should be `24:28`.



### What did you expect to see?

errno should be parsed from bytes `24:28` on Darwin
Repository: rust
Issue: Missed optimization when looping over bytes of a value
Labels: A-LLVM,T-compiler,llvm-fixed-upstream,C-optimization

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

I tried this code, which contains 3 functions which check if all the bits in a u64 are all ones:

```rust
#[no_mangle]
fn ne_bytes(input: u64) -> bool {
    let bytes = input.to_ne_bytes();
    bytes.iter().all(|x| *x == !0)
}

#[no_mangle]
fn black_box_ne_bytes(input: u64) -> bool {
    let bytes = input.to_ne_bytes();
    let bytes = std::hint::black_box(bytes);
    bytes.iter().all(|x| *x == !0)
}

#[no_mangle]
fn direct(input: u64) -> bool {
    input == !0
}
```

I expected to see this happen: `ne_bytes()` should be optimized to the same thing as `direct()`, while `black_box_ne_bytes()` should be optimized slightly worse

Instead, this happened: I got the following assembly, where `ne_bytes()` is somehow optimized worse than `black_box_ne_bytes()`

```asm
ne_bytes:
        mov     rax, rdi
        not     rax
        shl     rax, 8
        sete    cl
        shr     rdi, 56
        cmp     edi, 255
        setae   al
        and     al, cl
        ret

black_box_ne_bytes:
        mov     qword ptr [rsp - 8], rdi
        lea     rax, [rsp - 8]
        cmp     qword ptr [rsp - 8], -1
        sete    al
        ret

direct:
        cmp     rdi, -1
        sete    al
        ret
```

[Godbolt](https://godbolt.org/z/31nvsa3Ye)

### Meta

Reproducible on godbolt with stable `rustc 1.82.0 (f6e511eec 2024-10-15)` and nightly `rustc 1.85.0-nightly (7db7489f9 2024-11-25)`
Repository: PowerToys
Issue: Give the option to omit minimized windows when cycling through windows of the same zone
Labels: Needs-Triage

### Description of the new feature / enhancement

When the user presses `win+pgup/pgdn` on the currently focused window, which belongs to the same zone as other windows, it would be nice to be able to omit any minimized windows (of the same zone) from the cycle.

### Scenario when this would be used?

I often want to switch fast between 2 central windows that i use often and that need a larger space so they can't be put next to each other at the same time. At the same time, there might be other windows in the same zone, which are at the time minimized. They should be allowed to stay minimized!

### Supporting information

_No response_
Repository: three.js
Issue: WebGPURenderer: Models with morphs are less performant
Labels: WebGPU,Needs Investigation

### Description

I'm trying to improve the rendering performance of [three-vrm](https://github.com/pixiv/three-vrm) on WebGPURenderer.

During my profiling, I found that models with morphs have much lesser GPU performance compared to the same model without morphs.


### Reproduction steps

1. Load a GLTF model with morphs
2. Render
3. See the value `renderer.info.render.timestamp`


### Code

```js
const loader = new GLTFLoader();
const gltf = await loader.loadAsync(url); // a model with morphs
scene.add(gltf.scene);
```


### Live example

Here is my fixture.

This loads the same model under 4 different finishes (without skins and morphs, with morphs, with skins, with both) and calculates the runtime CPU/GPU performance. Each model is rendered for 100 frames and does the same profiling for five sets.
On the "result" row of the textarea, the second column indicates the model name, the third is the mean CPU time, and the fourth is the mean GPU time.

I used `renderer.info.render.timestamp` to profile the GPU performance on WebGPU; I'm not sure how reliable this value is.

https://three-webgpu-profile-morphs.glitch.me/
https://glitch.com/edit/#!/three-webgpu-profile-morphs

Here is the result on my machine (Alienware x16 r1, Intel i9-13900HK, NVIDIA RTX 4070 Laptop):

model | webgl cpu (ms) | webgpu cpu (ms) | webgl gpu (ms) | webgpu gpu (ms)
-- | -- | -- | -- | --
AvatarSample_B_.glb | 0.5560000007 | 0.7353999989 | 0.160837632 | 0.52953088
AvatarSample_B_morph.glb | 0.4741999991 | 0.7295999993 | 0.08183808 | 1.796866048
AvatarSample_B_skin.glb | 0.5308000017 | 0.7617999989 | 0.151005184 | 0.383254528
AvatarSample_B_both.glb | 0.6412000004 | 0.8019999999 | 0.12335872 | 1.027211264


### Screenshots

_No response_

### Version

r170

### Device

Desktop

### Browser

Chrome

### OS

Windows
Repository: ollama
Issue: Ddos of parsing markdown in frontend & images
Labels: bug

### What is the issue?

if the frontend converts markdown strings to supported html elements, on every token the frontend is requesting the same image over and over again and start downloading all images on every new token.

So markdown conversion should be done on the backend to avoid ddos attacks through wrong javascript versions.

also a rate limiter on your image server should be applied, if this gets fired you can amplify the load on servers real easily, example on youtube

### OS

_No response_

### GPU

_No response_

### CPU

_No response_

### Ollama version

0.4.1
Repository: godot
Issue: Geometry2D Union generates invalid Polygon2D/Self-intersection Transitivity
Labels: needs testing,topic:2d

### Tested versions

Reproducible in 4.3 and back in 3.x

### System information

Godot v4.3.stable - Windows 10.0.22631 - GLES3 (Compatibility) - NVIDIA GeForce RTX 4050 Laptop GPU (NVIDIA; 32.0.15.6070) - Intel(R) Core(TM) Ultra 7 155H (22 Threads)

### Issue description

So I've been experimenting with Polygon2D in the editor and managed to create some shapes that will disappear.
I'm not quite sure what the issue is since the polygon does not intersect itself, but if we move any of the points then it will reappear.

![Image](https://github.com/user-attachments/assets/03691fbd-3788-4ed9-ab07-35e7fb1dcaaf)
![Image](https://github.com/user-attachments/assets/c9767167-5db4-464c-a7b3-d8a757d0baf0)


### Steps to reproduce

Copy these points into a Polygon2D and notice it doesn't render:
```
polygon = PackedVector2Array(450, 300, 550, 300, 550, 450, 600, 450, 600, 300, 550, 300, 550, 250, 700.68, 249, 700, 450, 700.68, 506, 449.68, 500)
```

### Minimal reproduction project (MRP)

I gave the points to the Polygon2D in reproduce steps.
Repository: flutter
Issue: Linux_android_emu_34 android views is 3.00% flaky
Labels: P1,c: flake

<!-- meta-tags: To be used by the automation script only, DO NOT MODIFY.
{
  "name": "Linux_android_emu_34 android views"
}
-->

The post-submit test builder `Linux_android_emu_34 android views` had a flaky ratio 3.00% for the past (up to) 100 commits, which is above our 2.00% threshold.

One recent flaky example for a same commit: https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_android_emu_34%20android%20views/1373
Commit: https://github.com/flutter/flutter/commit/d39c3532578a05d208e16d080a234a5f2c40e4ba

Flaky builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_android_emu_34%20android%20views/1373
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_android_emu_34%20android%20views/1371
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_android_emu_34%20android%20views/1344

Recent test runs:
https://flutter-dashboard.appspot.com/#/build?taskFilter=Linux_android_emu_34%20android%20views

Please follow https://github.com/flutter/flutter/blob/master/docs/infra/Reducing-Test-Flakiness.md#fixing-flaky-tests to fix the flakiness and enable the test back after validating the fix (internal dashboard to validate: go/flutter_test_flakiness).
Repository: ant-design
Issue: RangePicker初始值如果开始值属于disabledDate，导致结束值不能修改为有效的非禁用日期
Labels: unconfirmed

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/p/sandbox/antd-reproduction-template-forked-h8gxnd)

### Steps to reproduce

1. 点击结束日期
2. 选择一个可选日期
3. 点击日历上的OK
4. 此时，开始日期focus, 需要选择开始日期
5. 点击页面其他部位，日历收起
6. 结束日期重置为原始值

### What is expected?

结束日期可以修改成功

### What is actually happening?

结束日期被重置为初始值

| Environment | Info |
| --- | --- |
| antd | 5.22.2 |
| React | 18 |
| System | Windows 11 |
| Browser | 130.0.2849.80 Edge |

---
4.x版本是可以单独修改结束日期的

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->