sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: page arises a error everytime when app republished
Labels: bug,Navigation

### Link to the code that reproduces this issue

https://github.com/milvus-io/milvus.io

### To Reproduce

1. deploy the site and visit any page, for example: /docs/milvus_lite.md
2. update any code then rebuild and redeploy the website
3. after the deployment, click on any internal link within the same page



### Current vs. Expected behavior

expecting routing normally but the page encountered an error:
![image](https://github.com/vercel/next.js/assets/41352919/471304c5-50a4-46f4-9143-bab804fdae29)

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: x64
  Version: Darwin Kernel Version 23.5.0: Wed May  1 20:09:52 PDT 2024; root:xnu-10063.121.3~5/RELEASE_X86_64
  Available memory (MB): 16384
  Available CPU cores: 12
Binaries:
  Node: 19.9.0
  npm: 9.6.3
  Yarn: 1.22.21
  pnpm: 8.6.11
Relevant Packages:
  next: 14.2.3 // Latest available version is detected (14.2.3).
  eslint-config-next: 12.2.2
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.4.5
Next.js Config:
  output: export
```


### Which area(s) are affected? (Select all that apply)

Navigation

### Which stage(s) are affected? (Select all that apply)

Other (Deployed)

### Additional context

_No response_
Repository: PowerToys
Issue: Feature request: Simple text note taking feature with auto timestamp recorded whenever previous time stamp is more than, say, 4 minutes.
Labels: Needs-Triage

### Description of the new feature / enhancement

Sample: 
[19-05-2024 09:34]  I've added the foo to the bar namespace.
                                 Made foo blink green
[19-05-2024 10:07]  Fixed bug on the widget showing squiggles
[19-05-2024 12:07]  Completed the button event handler

### Scenario when this would be used?

Onenote does not do auto timestamp, Teams is the wrong place:
 PowerToys seems like the perfect place.
 
 Perhaps a new file every day/week.
 Writing to a textfile on disk not needed, but might be easiest to dump previous entries.

### Supporting information

_No response_
Repository: ui
Issue: [bug]: Todays date is not showing when not selected. 
Labels: bug

### Describe the bug

Todays date is not showing because the text color is the same as the selection box when unselected.

![Screenshot 2024-06-04 at 10 17 43@2x](https://github.com/shadcn-ui/ui/assets/18461079/0502fba1-0d53-40d5-b8fd-4bf2dc7a6438)

When selected it works as expected:
![Screenshot 2024-06-04 at 10 18 58@2x](https://github.com/shadcn-ui/ui/assets/18461079/0e376e12-519f-459e-b7ac-160fe5039f24)

![Screenshot 2024-06-04 at 10 18 36@2x](https://github.com/shadcn-ui/ui/assets/18461079/5cb54d31-ecb6-43c3-9a0f-be60ed26ac7f)



### Affected component/components

Calendar

### How to reproduce

1. install Calendar component as per shadcnui documentation
2. implement it in the project
3. see the unexpected behaviour

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Installed in a project using T3 stack - no real css customization at this point. Only background and text color.
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: storybook
Issue: [Bug]: [Angular] argsToTemplate not showing correct value on "Show code" with input signals 
Labels: bug,needs triage

### Describe the bug

When using input signals and argsToTemplate correctly sets the value for the input. But the value is not shown on the show code tab. Instead only the name of the signal of the input is shown and stays unchanged when selection another value. 

### Reproduction link

https://stackblitz.com/edit/github-gwvtme?file=src%2Fstories%2Ftest.component.ts

### Reproduction steps

I provided a stackblitz url that reproduces this issue. 
You can see on the image that variant `secondary` is set but the code shows `[variant]="variant]`

<img width="1728" alt="image" src="https://github.com/storybookjs/storybook/assets/17096495/a1aac377-716b-4083-9b84-a04e66e4fcce">


### System

```bash
Storybook Environment Info:

  System:
    OS: macOS 14.5
    CPU: (12) arm64 Apple M3 Pro
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.14.0 - ~/.nvm/versions/node/v20.14.0/bin/node
    npm: 10.8.0 - ~/.nvm/versions/node/v20.14.0/bin/npm <----- active
  Browsers:
    Chrome: 125.0.6422.114
    Safari: 17.5
```


### Additional context

_No response_
Repository: rust
Issue: Tracking Issue for `core::iter::chain`
Labels: T-libs-api,C-tracking-issue

<!--
Thank you for creating a tracking issue!

Tracking issues are for tracking a feature from implementation to stabilization.

Make sure to include the relevant RFC for the feature if it has one.

If the new feature is small, it may be fine to skip the RFC process. In that
case, you can use `issue = "none"` in your initial implementation PR. The
reviewer will ask you to open a tracking issue if they agree your feature can be
added without an RFC.
-->

Feature gate: `#![feature(iter_chain)]`

This is a tracking issue for the `core::iter::chain` function that combines two `IntoIterator` arguments together into a `Chain` iterator.



<!--
Include a short description of the feature.
-->

### Public API

<!--
For most library features, it'd be useful to include a summarized version of the public API.
(E.g. just the public function signatures without their doc comments or implementation.)
-->

```rust
// core::iter
pub fn chain<A, B>(a: A, b: B) -> Chain<A::IntoIter, B::IntoIter>
where
    A: IntoIterator,
    B: IntoIterator<Item = A::Item>;
```

### Steps / History

<!--
For larger features, more steps might be involved.
If the feature is changed later, please add those PRs here as well.
-->

- [x] Approved ACP https://github.com/rust-lang/libs-team/issues/154
- [x] Implementation: #106186
- [ ] Final comment period (FCP)[^1]
- [ ] Stabilization PR

<!--
Once the feature has gone through a few release cycles and there are no
unresolved questions left, the feature might be ready for stabilization.

If this feature didn't go through the RFC process, a final comment period
(FCP) is always needed before stabilization. This works as follows:

A library API team member can kick off the stabilization process, at which point
the rfcbot will ask all the team members to verify they agree with
stabilization. Once enough members agree and there are no concerns, the final
comment period begins: this issue will be marked as such and will be listed
in the next This Week in Rust newsletter. If no blocking concerns are raised in
that period of 10 days, a stabilization PR can be opened by anyone.
-->

### Unresolved Questions

<!--
Include any open questions that need to be answered before the feature can be
stabilised. If multiple (unrelated) big questions come up, it can be a good idea
to open a separate issue for each, to make it easier to keep track of the
discussions.

It's useful to link any relevant discussions and conclusions (whether on GitHub,
Zulip, or the internals forum) here.
-->

- None yet.

[^1]: https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html
Repository: rust
Issue: Tracking Issue for `os_string_pathbuf_leak`
Labels: T-libs-api,C-tracking-issue

<!--
Thank you for creating a tracking issue!

Tracking issues are for tracking a feature from implementation to stabilization.

Make sure to include the relevant RFC for the feature if it has one.

If the new feature is small, it may be fine to skip the RFC process. In that
case, you can use `issue = "none"` in your initial implementation PR. The
reviewer will ask you to open a tracking issue if they agree your feature can be
added without an RFC.
-->

Feature gate: `#![feature(os_string_pathbuf_leak)]`

This is a tracking issue for https://github.com/rust-lang/libs-team/issues/389

<!--
Include a short description of the feature.
-->

### Public API

```rust
impl OsString {
    fn leak<'a>(self) -> &'a mut OsStr { ... }
}

impl PathBuf {
    fn leak<'a>(self) -> &'a mut Path { ... }
}
```

### Steps / History

<!--
For larger features, more steps might be involved.
If the feature is changed later, please add those PRs here as well.
-->

- [x] Implementation: #125966 
- [ ] Final comment period (FCP)[^1]
- [ ] Stabilization PR

<!--
Once the feature has gone through a few release cycles and there are no
unresolved questions left, the feature might be ready for stabilization.

If this feature didn't go through the RFC process, a final comment period
(FCP) is always needed before stabilization. This works as follows:

A library API team member can kick off the stabilization process, at which point
the rfcbot will ask all the team members to verify they agree with
stabilization. Once enough members agree and there are no concerns, the final
comment period begins: this issue will be marked as such and will be listed
in the next This Week in Rust newsletter. If no blocking concerns are raised in
that period of 10 days, a stabilization PR can be opened by anyone.
-->

### Unresolved Questions

<!--
Include any open questions that need to be answered before the feature can be
stabilised. If multiple (unrelated) big questions come up, it can be a good idea
to open a separate issue for each, to make it easier to keep track of the
discussions.

It's useful to link any relevant discussions and conclusions (whether on GitHub,
Zulip, or the internals forum) here.
-->

- None yet.

[^1]: https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html
Repository: storybook
Issue: [@storybook/test] Move `@testing-library/dom` to a peerDependency
Labels: question / support,maintenance

### Discussed in https://github.com/storybookjs/storybook/discussions/27501

<div type='discussions-op-text'>

<sup>Originally posted by **MatanBobi** June  1, 2024</sup>
### Is your feature request related to a problem? Please describe.

In React Testing Library, we've experienced multiple issues that occur once people install dom-testing-library on their own (as part of `user-event` for example) and also install a library that bundles DTL (like `@storybook/test` and also `@testing-library/react`). These issues occur once there's a version mismatch and multiple version of DTL get installed.

### Describe the solution you'd like

Moving DTL to a peerDependency will help with solving this issue.

### Describe alternatives you've considered

_No response_

### Are you able to assist to bring the feature to reality?

yes, I can

### Additional context

I'm a member of the testing-library organization and due to multiple issues we had with multiple version of DTL installed, we've decided to create a PR to move DTL to a peerDependency in React-Testing-Library:
https://github.com/testing-library/react-testing-library/pull/1305

This is something we've thought about for quite a long time and we highly recommend other libraries in the testing-library ecosystem to also do.
I'm here and available to assist in any issues that occur or even contribute this change on my own.
Feel free to reach out to me or any of us from the testing-library organization.</div>
Repository: transformers
Issue: Batch size schedulers
Labels: trainer,Feature request

### Feature request

Implement in the trainer the possibility to increment the batch size according to some schedule, similar to how lr can follow a schedule.

### Motivation

It's been shown (e.g. DeepSeek) that slowly increasing the batch size can have a positive effect on learning.

### Your contribution

Unfortunately no time to work on this. It's not trivial to add this, so it's really just an idea to throw out there.
Repository: material-ui
Issue: [material-ui][TextField] When with minRows, it makes the height from small to final height
Labels: bug 🐛,component: text field,package: material-ui,ready to take

### Steps to reproduce

1. open https://stackblitz.com/edit/nextjs-ziwkdm?file=package.json
2. click refresh multiple time

you will see the height of textarea change from:

<img width="1512" alt="image" src="https://github.com/mui/material-ui/assets/41773861/ce981cd4-56c4-483f-9f7d-1988ecd62204">

to: 

<img width="1512" alt="image" src="https://github.com/mui/material-ui/assets/41773861/f8d3fc0e-83d5-4e63-844d-3da01c9ffd1b">


### Current behavior

The height will change from a small height to the final height

### Expected behavior

No height change, it will make web page cls metric bad

### Context

fix the web page cls, you can see the prompt input box height change:


https://github.com/mui/material-ui/assets/41773861/b1b01e6f-ea0b-4015-b33b-c8540849d9ca



### Your environment

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
   System:
    OS: macOS 14.5
  Binaries:
    Node: 20.13.1 - ~/.local/state/fnm_multishells/51935_1717493153731/bin/node
    npm: 10.8.1 - ~/.local/state/fnm_multishells/51935_1717493153731/bin/npm
    pnpm: 9.1.0 - ~/.local/state/fnm_multishells/51935_1717493153731/bin/pnpm
  Browsers:
    Chrome: 125.0.6422.142
  npmPackages:
    @emotion/react: ^11.11.4 => 11.11.4 
    @emotion/styled: ^11.11.5 => 11.11.5 
    @mui/material: ^5.15.19 => 5.15.19 
    @types/react: ^18 => 18.2.75 
    react: ^18 => 18.2.0 
    react-dom: ^18 => 18.2.0 
    typescript: ^5 => 5.4.5 
```
</details>


**Search keywords**: TextField, minRows, height
Repository: ollama
Issue: Add information on RAM and VRAM requirements of model quantization in library
Labels: feature request

this would help to decide which model can run
a) at all
b) at highest-quality although slowly
c) at highest-quality at GPU-speed
before downloading huge files

I think one of the great plus of Ollama is the curated model library. adding memory information would make it even more convenient.

_thank you for this great tool!_
Repository: ollama
Issue: ollama qwen long text problem
Labels: bug

### What is the issue?

When I Use ollama, deploy [qwen:110b-chat-v1.5-q6_K](https://ollama.com/library/qwen:110b-chat-v1.5-q5_K_M) model

When the context (Chinese) exceeds around 3000 characters (not precise), it fails to recognize the system prompt.

I tried increasing num_ctx to 32768 or max_tokens to 32768 through calling ollama itself or via the OpenAI API, but neither had any effect.

I saw someone mention setting a dynamic factor, but couldn't find where to set it in ollama.

How can I resolve this issue? Thank you.

### OS

Linux

### GPU

Nvidia

### CPU

Intel

### Ollama version

0.1.33
Repository: vscode
Issue: Find and focus the previous/next occurrences of a string on an ipynb notebook
Labels: feature-request,notebook-commands,notebook-find

Hello,
It would be very convenient to have commands to find and focus the previous/next occurences of a string on an **ipynb notebook**, or to integrate with the existing commands like `editor.action.nextMatchFindAction`.

see https://stackoverflow.com/questions/78567139/commands-to-find-previous-next-occurence-of-a-string-on-a-ipynb-notebook-on-vsco

+@starball5
Repository: pytorch
Issue: [libtorch] `CppCommInterface` subclasses cannot be instantiated
Labels: oncall: distributed,triaged,enhancement,module: ddp

### 🐛 Describe the bug

Classes from `default_comm_hooks.hpp` cannot be instantiated. They seem to lack some function implementation to be treated as concrete classes:

```c++
#include <torch/torch.h>
#include <torch/csrc/distributed/c10d/reducer.hpp>

int main(int ac, char **av) {
  c10d::AllReduceCommHook h = c10d::AllReduceCommHook(NULL);
}
```
Produces:
```
/usr/lib/gcc/x86_64-pc-linux-gnu/13/../../../../x86_64-pc-linux-gnu/bin/ld: /tmp/cc0DWQWl.o: warning: relocation against `_ZTVN4c10d17AllReduceCommHookE' in read-only section `.text._ZN4c10d17AllReduceCommHookD2Ev[_ZN4c10d17AllReduceCommHookD5Ev]'
/usr/lib/gcc/x86_64-pc-linux-gnu/13/../../../../x86_64-pc-linux-gnu/bin/ld: /tmp/cc0DWQWl.o: in function `c10d::AllReduceCommHook::AllReduceCommHook(c10::intrusive_ptr<c10d::ProcessGroup, c10::detail::intrusive_target_default_null_type<c10d::ProcessGroup> > const&)':
d.cpp:(.text._ZN4c10d17AllReduceCommHookC2ERKN3c1013intrusive_ptrINS_12ProcessGroupENS1_6detail34intrusive_target_default_null_typeIS3_EEEE[_ZN4c10d17AllReduceCommHookC5ERKN3c1013intrusive_ptrINS_12ProcessGroupENS1_6detail34intrusive_target_default_null_typeIS3_EEEE]+0x59): undefined reference to `vtable for c10d::AllReduceCommHook'
/usr/lib/gcc/x86_64-pc-linux-gnu/13/../../../../x86_64-pc-linux-gnu/bin/ld: /tmp/cc0DWQWl.o: in function `c10d::AllReduceCommHook::~AllReduceCommHook()':
d.cpp:(.text._ZN4c10d17AllReduceCommHookD2Ev[_ZN4c10d17AllReduceCommHookD5Ev]+0x13): undefined reference to `vtable for c10d::AllReduceCommHook'
/usr/lib/gcc/x86_64-pc-linux-gnu/13/../../../../x86_64-pc-linux-gnu/bin/ld: warning: creating DT_TEXTREL in a PIE
collect2: error: ld returned 1 exit status
```

Do I miss something ?

### Versions

libtorch 2.3.0

cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @gqchen @aazzolini @osalpekar @jiayisuse @H-Huang @kwen2501 @awgu @penguinwu @fegin @XilunWu @wanchaol @fduwjj @wz337 @tianyu-l @wconstab @yf225 @chauhang @d4l3k
Repository: vscode
Issue: Accessibility Issue : Contrast Ratio of Buttons, Text Boxes and Combo Boxes.
Labels: bug,themes,accessibility,confirmation-pending

<!-- ⚠️⚠️ 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: 
Version: 1.77.3 (user setup)
Commit: 704ed70d4fd1c6bd6342c436f1ede30d1cff4710
Date: 2023-04-12T09:16:02.548Z
Electron: 19.1.11
Chromium: 102.0.5005.196
Node.js: 16.14.2
V8: 10.2.154.26-electron.0
OS: Windows_NT x64 10.0.20348
Sandboxed: No

I have an Extension on VSCode in which I use OJET for webview components. I am running into a Color Contrast Issue in "Solarized Light Theme". I am using "Colour Contrast Analyser (CCA)" to test the contrast ratio between the foreground and the background.

This issue is found even in VSCode's settings page for, buttons and input boxes, although comboboxs have a valid contrast ratio.
Similarly in my Extension the buttons and inputboxes dont meet the contrast ratio.

So is this a bug on VSCodes end? or thats the expected behaviour?
Do all the Themes provided by VSCode have a valid Contrast Ratio? is it even possible?

I used to think VSCode has so many themes to accomodate different contrast ratios, for maybe the visually impared.
Repository: rust
Issue: `dropping_references` lint triggers even for mutable references
Labels: A-lints,C-discussion

When I call `std::mem::drop` on a mutable reference, this is supposed to consume the reference and make it unavailable to following code. And indeed it does, because any following uses trigger a "use of moved value" error.

But when I do this, I get a warning from the compiler:

> warning: calls to `std::mem::drop` with a reference instead of an owned value does nothing
>     --> foo.rs:1602:13
>      |
> 1602 |             mem::drop(mutref);
>      |             ^^^^^^^^^^-------------^
>      |                       |
>      |                       argument has type `&mut Foo`
>      |
>      = note: use `let _ = ...` to ignore the expression or result
>      = note: `#[warn(dropping_references)]` on by default

### Meta

`rustc --version --verbose`:
```
rustc 1.80.0-nightly (7c52d2db6 2024-06-03)
binary: rustc
commit-hash: 7c52d2db6348b038276198e88a835125849f322e
commit-date: 2024-06-03
host: x86_64-unknown-linux-gnu
release: 1.80.0-nightly
LLVM version: 18.1.6
```


<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"tbu-"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: godot
Issue: Animation panel: editor setting default_create_reset_tracks is ignored. Adding a new track manually never creates a RESET track nor prompts to do it
Labels: bug,topic:editor,topic:animation

### Tested versions

- Reproducible in v4.2.2.stable.official [15073afe3]

### System information

Godot v4.2.1.stable - Ubuntu 22.04.4 LTS 22.04 - X11 - Vulkan (Mobile) - dedicated NVIDIA GeForce GTX 860M (nvidia; 535.161.07) - Intel(R) Core(TM) i7-4710HQ CPU @ 2.50GHz (8 Threads)

### Issue description

I don't see where the editor setting editors/animation/default_create_reset_tracks is used:
- when adding a new track manually via the `+ Add track` button, whether the setting is true or false, nothing extra happens: no RESET track is created, and there is no prompt to create one either (maybe because they need an initial value to work on? but adding the first animation key doesn't add RESET either)
- when clicking on the key button near a property, I am always prompted to Create a RESET track (and sometimes Bezier curve), but it is still independent of editors/animation/default_create_reset_tracks
- the only way to auto-generate a RESET track is to select a key, then right-click > Add RESET Value(s) (two clicks are needed due to some limitation of the Animation editor, see https://github.com/godotengine/godot-proposals/issues/7548)

I suppose the intended behavior was to create a RESET track for new tracks added manually, but I don't know if they were supposed to also pick the first key value you added or if user should just fill them later (making the setting much less useful since right-click > Add RESET Value(s) also creates the track anyway...)

### Steps to reproduce

1. Open MWE demo scene
2. Select node: AnimationPlayer without RESET
3. In the Animation panel, Add Track > Property Track... > Node2D > position
4. Check the animation list: no RESET track at all
5. Select node: AnimationPlayer with RESET
6. In the Animation panel, Add Track > Property Track... > Node2D > position
7. Switch to the existing RESET animation
8. There is no track at all inside

### Minimal reproduction project (MRP)

[v4.2.2 - Editor setting default_create_reset_tracks is ignored, create RESET track never prompted.zip](https://github.com/user-attachments/files/15550464/v4.2.2.-.Editor.setting.default_create_reset_tracks.is.ignored.create.RESET.track.never.prompted.zip)