sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: storybook
Issue: [Bug]: Storybook composition doesn't work properly on a screen width of less than 600px
Labels: bug,needs triage

### Describe the bug

The storybook composition does not work correctly on a screen less than 600px wide. The problem does not occur on a standalone storybook instance.
<img width="1727" alt="Screenshot 2024-09-06 at 11 37 09" src="https://github.com/user-attachments/assets/ea392f5c-6f37-4973-aca0-2797c77db641">


### Reproduction link

https://github.com/tosesek/storybook-composition-issue

### Reproduction steps

1. Clone this repository
2. Install the dependencies
3. Run `npm run storybook`
4. Open the preview of any component
5. Resize your browser so that the window width is less than 600px

### System

```bash
Storybook Environment Info:

  System:
    OS: macOS 14.6.1
    CPU: (10) arm64 Apple M1 Pro
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.18.2 - ~/.nvm/versions/node/v18.18.2/bin/node
    npm: 9.8.1 - ~/.nvm/versions/node/v18.18.2/bin/npm <----- active
    pnpm: 9.7.0 - ~/Library/pnpm/pnpm
  Browsers:
    Chrome: 128.0.6613.119
    Safari: 17.6
  npmPackages:
    @storybook/addon-essentials: ^8.2.9 => 8.2.9
    @storybook/addon-links: ^8.2.9 => 8.2.9
    @storybook/blocks: ^8.2.9 => 8.2.9
    @storybook/react: ^8.2.9 => 8.2.9
    @storybook/react-vite: ^8.2.9 => 8.2.9
    @storybook/test: ^8.2.9 => 8.2.9
    eslint-plugin-storybook: ^0.8.0 => 0.8.0
    storybook: ^8.2.9 => 8.2.9
```


### Additional context

_No response_
Repository: storybook
Issue: [Bug]: expect.poll is missing
Labels: bug,needs triage

### Describe the bug

(It might be a feature request, rather than a bug report)
Docs says that Storybook exposes vitest's API, but [`expect.poll`](https://vitest.dev/api/expect.html#poll) is missing.

### Reproduction link

https://stackblitz.com/edit/github-eut88f?file=src%2Fstories%2FPage.stories.ts

### Reproduction steps

1. Go to above link
2. hover `expect.poll`

### System

```bash
Storybook Environment Info:

  System:
    OS: Linux 5.0 undefined
    CPU: (6) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.20.3 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm <----- active
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    @storybook/addon-essentials: ^8.3.0-beta.3 => 8.3.0-beta.3 
    @storybook/addon-interactions: ^8.3.0-beta.3 => 8.3.0-beta.3 
    @storybook/addon-links: ^8.3.0-beta.3 => 8.3.0-beta.3 
    @storybook/addon-onboarding: ^8.3.0-beta.3 => 8.3.0-beta.3 
    @storybook/blocks: ^8.3.0-beta.3 => 8.3.0-beta.3 
    @storybook/react: ^8.3.0-beta.3 => 8.3.0-beta.3 
    @storybook/react-vite: ^8.3.0-beta.3 => 8.3.0-beta.3 
    @storybook/test: ^8.3.0-beta.3 => 8.3.0-beta.3 
    storybook: ^8.3.0-beta.3 => 8.3.0-beta.3
```


### Additional context

_No response_
Repository: storybook
Issue: [Bug]: Angular provider recreation differs between docs & story view
Labels: bug,has workaround,angular

### Describe the bug

When defining Angular providers in the `moduleMetadata` of the `render` function, the recreation of them differs between the docs and the story page.
In the docs page, they get recreated on every change of the Controls, but this doesn't happen on the story page.

We need this recreation to mock values of services or e.g. NgRx Store based on Storybook Controls.

### Reproduction link

https://stackblitz.com/edit/github-yzh9ef?file=src%2Fstories%2Fbutton.stories.ts

### Reproduction steps

1. Open the Storybook from the Reproduction.
2. Go to docs page of the Button component.
3. Change input & service value via controls.  
  -> Both values are updated in the story view.
5. Go to the single story of the Button component.
6. Change input & service value via controls.  
  -> Only input value changes are represented in the story view
     and service value changes doesn't have any effect.

### System

```bash
System:
    OS: Windows 10 10.0.19045
    CPU: (12) x64 12th Gen Intel(R) Core(TM) i7-1265U
  Binaries:
    Node: 20.17.0 - C:\Program Files\nodejs\node.EXE
    npm: 10.8.2 - C:\Program Files\nodejs\npm.CMD <----- active
  Browsers:
    Edge: Chromium (127.0.2651.74)
  npmPackages:
    @storybook/addon-designs: 8.0.3 => 8.0.3 
    @storybook/addon-essentials: 8.2.9 => 8.2.9 
    @storybook/addon-interactions: 8.2.9 => 8.2.9 
    @storybook/addon-mdx-gfm: 8.2.9 => 8.2.9 
    @storybook/addon-themes: 8.2.9 => 8.2.9 
    @storybook/angular: 8.2.9 => 8.2.9 
    @storybook/core-server: 8.2.9 => 8.2.9 
    @storybook/manager-api: 8.2.9 => 8.2.9 
    @storybook/test-runner: 0.19.1 => 0.19.1 
    @storybook/theming: 8.2.9 => 8.2.9 
    eslint-plugin-storybook: 0.8.0 => 0.8.0 
    storybook: 8.2.9 => 8.2.9
```


### Additional context

_No response_
Repository: transformers
Issue: Accelerate x Trainer issue tracker:
Labels: Good First Issue,trainer,Good Second Issue,DeepSpeed,Good Difficult Issue,PyTorch FSDP,HACKTOBERFEST-ACCEPTED,Accelerate

A bunch of issues are a bit stale, and @SunMarc + @muellerzr are a bit short on bandwidth! 
Thus we would love to have community support to solve the following: 

### Help needed
- [x] #27830
- [ ]  #30911
- [x] #30702
- [x] #30239
- [x] #29348
- [ ]  #33157
- [x] #28469 
- [x] #30663 
- [x] #30811
- [ ] #30819
- [x] #31313 
- [x] #31457
- [ ] #30859
- [x] #31897
- [x] #30340 
- [x] #31892
- [x] #28914 
- [x] #29518 
- [x] #30277
- [x] #33376

### Feature request

- [ ] #30725


### Replied with potential fix and following 
- [ ] #31734 followed by @irislin1006 
- [ ] #32312 followed by @irislin1006 
- [x] #31818 followed by @mekkcyber
- [x] #31439 followed by @nnilayy
- [ ] #28124 followed by @muellerz and @WizKnight
- [ ] #30767 followed by @SunMarc 
- [ ] #33147 followed by @SunMarc 
- [x] #33400 followed by @SunMarc 
- [ ] #26413 followed by @muupan, @muellerzr and @SunMarc 
- [x] #28808 followed by @Ben-Schneider-code
- [x] #31357 followed by @mekkcyber
- [x] #33733 resolved by the author
- [ ] #30330 followed by @SunMarc 
- [ ] #30913 followed by @mekkcyber
- [ ] #27487 followed by @SunMarc 
- [ ] #33336 followed by @MekkCyber 
- [ ] #25695 followed by @MekkCyber 
- [ ] #31278 followed by @muellerzr
- [ ] #32427 followed by @muellerzr and @SunMarc 
- [ ] #31034 followed by @muellerzr
- [ ] #30822 followed by @muellerzr
- [ ] #31867 followed by @Ben-Schneider-code and @SunMarc
Repository: vscode
Issue: Split right when previewing markdown files results in an empty tab
Labels: bug,webview

<!-- ⚠️⚠️ 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.93.0
- OS Version: MacOS Sonoma 14.6.1 

Steps to Reproduce:

1. Preview markdown file
2. Right click on the markdown file and click "Split Right"
3. Empty tab opened on the right (check image)
<img width="1078" alt="image" src="https://github.com/user-attachments/assets/a40e1004-c4a7-4f8c-bba0-276947a32f3d">
Repository: rust
Issue: `should_panic` does not capture allocation-induced panics
Labels: A-libtest,C-bug,T-libs

When writing tests for custom allocators, I ran into the problem that an allocation-induced panic is not captured properly by should_panic. This is in my opinion a bug, as the behaviour the test shows is still very much like a panic.

Example code to trigger the issue:
```
use core::alloc::Layout;
use alloc::alloc::handle_alloc_error

#[test]
#[should_panic]
fn sample_test() {
    let layout = Layout::new::<u64>();
    handle_alloc_error(layout);
}
```
this uses an explicit call to handle_alloc_error, but the actual test cases I am writing create Vectors with a custom allocator that limits the amount of memory that can be allocated, which is a more realistic use case.

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.83.0-nightly (9c01301c5 2024-09-05)
binary: rustc
commit-hash: 9c01301c52df5d2d7b6fe337707a74e011d68d6f
commit-date: 2024-09-05
host: x86_64-unknown-linux-gnu
release: 1.83.0-nightly
LLVM version: 19.1.0
```
Repository: pytorch
Issue: dynamo fails to wrap distributions with lazy property
Labels: triaged,oncall: pt2,module: dynamo

### 🐛 Describe the bug

To reproduce:
```python
import torch.distributions


logits = torch.randn(10)
def make_categorical(logits):
    return torch.distributions.Categorical(logits=logits).sample()
torch.compile(make_categorical, fullgraph=True)(logits)
```
Error:
```
  File "/Users/vmoens/venv/rl/lib/python3.11/site-packages/torch/_dynamo/symbolic_convert.py", line 3011, in inline_call
    return cls.inline_call_(parent, func, args, kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/vmoens/venv/rl/lib/python3.11/site-packages/torch/_dynamo/symbolic_convert.py", line 3061, in inline_call_
    raise ArgsMismatchError(  # noqa: B904
torch._dynamo.exc.ArgsMismatchError: too many positional arguments.
  func = '__get__' /Users/vmoens/venv/rl/lib/python3.11/site-packages/torch/distributions/utils.py:145, args = [<class 'torch.distributions.utils.lazy_property'>, <class 'torch.distributions.utils.lazy_property'>, <class 'torch.distributions.categorical.Categorical'>, <class 'type'>], kwargs = {}
```

### Versions

nightly

cc @ezyang @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @amjames @rec
Repository: rust
Issue: The inference problem caused by `Option::filter` on function result
Labels: T-compiler,A-inference,A-result-option,C-discussion

**no error case**:
```rust
pub fn true_pred<T>(_: T) -> bool {
    true
}

pub fn foo<T, F>(ele: &T, mut f: F) -> Option<& T>
where F: FnMut(&T) -> bool,
{
    [ele].into_iter()
        .fold(None, |acc, _| {
            acc.filter(|min| f(min))
        })
        //.filter(true_pred) // error!
}
```

**error case**:
```rust
pub fn true_pred<T>(_: T) -> bool {
    true
}

pub fn foo<T, F>(ele: &T, mut f: F) -> Option<& T>
where F: FnMut(&T) -> bool,
{
    [ele].into_iter()
        .fold(None, |acc, _| {
            acc.filter(|min| f(min))
        })
        .filter(true_pred) // error!
}
```

**cargo check output**:
```rust
error[E0308]: mismatched types
  --> src/lib.rs:8:5
   |
5  |   pub fn foo<T, F>(ele: &T, mut f: F) -> Option<& T>
   |              - found this type parameter ----------- expected `Option<&T>` because of return type
...
8  | /     [ele].into_iter()
9  | |         .fold(None, |acc, _| {
10 | |             acc.filter(|min| f(min))
11 | |         })
12 | |         .filter(true_pred) // error!
   | |__________________________^ expected `Option<&T>`, found `Option<T>`
   |
   = note: expected enum `Option<&_>`
              found enum `Option<_>`
help: try using `.as_ref()` to convert `Option<T>` to `Option<&T>`
   |
12 |         .filter(true_pred).as_ref() // error!
   |                           +++++++++

For more information about this error, try `rustc --explain E0308`.
error: could not compile `test1` (lib) due to 1 previous error
```

**rustc version**:
```
rustc 1.82.0-nightly (1f12b9b0f 2024-08-27)
binary: rustc
commit-hash: 1f12b9b0fdbe735968ac002792a720f0ba4faca6
commit-date: 2024-08-27
host: aarch64-unknown-linux-gnu
release: 1.82.0-nightly
LLVM version: 19.1.0
```
Repository: ui
Issue: [feat]: choose your own base color
Labels: area: request

### Feature description

When initialising shadcn-ui on a project already setup with my own styles in the tailwind config, I want that the base colour that shadcn-ui uses to be one of my existing ones, not one from the set of colours given by the repo itself.

### Affected component/components

_No response_

### Additional Context

Whenever I add a component, I have to go through and update all of the styles that exist (that's the point, but a little less work OOTB would be nice)

### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues and PRs
Repository: ollama
Issue: on ollama.com , the centrate new profile picture page , looked on andro chrome canary , out of bound
Labels: bug,ollama.com

### What is the issue?

when upload profile pic , a page to move the pic into o round place .. the canvas doesnt fit into the display , of andro chrome canary

![IMG_20240906_125448_752](https://github.com/user-attachments/assets/56ce834d-575a-4570-9052-3cf683bb2b19)


### OS

_No response_

### GPU

_No response_

### CPU

_No response_

### Ollama version

_No response_
Repository: ui
Issue: [bug]: ComboBox item scroll (Mouse wheel) is not working inside Dialoge Box
Labels: bug

### Describe the bug

ComboBox item scroll (Mouse wheel) is not working inside Dialoge Box

https://github.com/user-attachments/assets/da1a3ce8-a543-4de5-a9b4-4eb19ac36246



### Affected component/components

Combobox, Dialog

### How to reproduce

1. Click on Filter
2. Click on Combobox
3. Scroll inside the combobox for more items, mouse scroll wheel not working.

https://github.com/user-attachments/assets/38e3781a-b5e8-4979-9c94-56d1820e9911



### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Chrom, Windows 11
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: neovim
Issue: Lua Vimscript bridge memory leak
Labels: performance,vimscript,has:repro,lua

### Problem

Memory that is consumed by Lua code and subsequently freed by an automatic garbage collection cycle or manually with `collectgarbage("collect")` often doesn't result in the memory used being released back to the operating system. This causes Neovim to use more memory than necessary, even after memory intensive code has finished running.

The effect of this issue is that when a plugin such as Telescope is used to search a large project multiple times (which is a normal use case), the memory usage will climb to many times what is necessary, and will remain high even after the user has finished searching and the results no longer need to be kept in memory. I have seen memory usage climb up to and exceed 1 GB because of this issue (although typically excess memory usage is around 100-500 MB).

### Steps to reproduce

1. Launch Neovim with `nvim --clean`
2. Run the following commands and monitor memory usage with a system monitor, leaving 5-10 second gaps between each execution:
   `:lua local nums = {} for i = 1, 10000000 do nums[i]=i end vim.g.foo = nums`
   [repeat the previous command two more times]
   `:lua vim.g.foo = nil`
   `:lua collectgarbage("collect")`
   `:lua print(collectgarbage("count"))`
3. Memory usage should have increased to around 1.4 GB, then decreased to around 960 MB, where it remains. The output of the last command should show that only around 323 KB of memory remains in use by Lua, even though the Neovim process is still using 960 MB.

### Expected behavior

Memory usage by the Neovim process should be released or begin decreasing soon after it is no longer in use by Lua.

### Neovim version (nvim -v)

NVIM v0.11.0-dev-714+g220b8aa6f

### Vim (not Nvim) behaves the same?

N/A

### Operating system/version

Arch Linux with kernel 6.9.3

### Terminal name/version

Alacritty 0.13.2

### $TERM environment variable

alacritty

### Installation

appimage
Repository: ui
Issue: [feat]: Add support for Templ Golang templating library 
Labels: area: request

### Feature description

The new CLI is amazing in adding new components to whatever framework one is using. 
A new library that is getting traction with Golang is called Templ.
Templ is a Go templating engine used to render HTML or other text-based formats by dynamically injecting data into predefined templates. The Go html/template and text/template packages are the most common built-in options for templating in Go applications.

Templating engines like Templ allow developers to separate code logic from presentation, which is especially useful in web development. The template syntax in Go is simple and provides control over output formatting. Go templates support conditionals, loops, and functions for more complex rendering.

if there any chance to have support for this Golang templating library?

### Affected component/components

_No response_

### Additional Context

[Templ library](https://templ.guide/)

### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues and PRs
Repository: PowerToys
Issue: Slow Launch Time and Workspace Resizing Issue
Labels: Issue-Bug,Needs-Triage,Product-Workspaces

### Microsoft PowerToys version

0.84.0

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

Workspaces

### Steps to reproduce

	1.	Open Cinema 4D.
	2.	Observe the loading process and the time it takes for the application to fully open.
	3.	Once the app is open, notice that the workspace does not resize properly, skipping the expected resizing behavior.

### ✔️ Expected Behavior

the workspace should resize properly once the application is fully loaded.

### ❌ Actual Behavior

Cinema 4D takes a significant amount of time to open, and the workspace appears to skip the resizing process, leading to display issues.

### Other Software

_No response_
Repository: pytorch
Issue: DISABLED test_cat_slice_cat_cuda_dynamic_shapes_cuda_wrapper (__main__.DynamicShapesCudaWrapperCudaTests)
Labels: triaged,skipped,oncall: pt2

Platforms: linux

This test was disabled because it is failing on main branch ([recent examples](https://torch-ci.com/failure?failureCaptures=%5B%22'test%2Finductor%2Ftest_cuda_cpp_wrapper.py%3A%3ADynamicShapesCudaWrapperCudaTests%3A%3Atest_cat_slice_cat_cuda_dynamic_shapes_cuda_wrapper'%22%5D)).

cc @ezyang @chauhang @penguinwu
Repository: godot
Issue: Emulate 3 Button Mouse is broken.
Labels: bug,topic:editor,topic:3d

### Tested versions

4.4 master

### System information

Windows 11

### Issue description

When "Emulate 3 Button Mouse" is checked,  the 3D View is rotating when I hover it with the mouse.

Usually, we need to presse ALT, or SHIFT or CTRL for the 3D View to rotate/pan/zoom.

### Steps to reproduce

Open Godot, enable "Emulate 3 Button Mouse" in the Editor Settings. Move your mouse in the 3D View.

### Minimal reproduction project (MRP)

Any Project
Repository: pytorch
Issue: 2.4 version give an extra output when running inference in CPU with a Huggingface model.. traced to a dynamo bug
Labels: triaged,module: regression,oncall: pt2,module: dynamo

### 🐛 Describe the bug

When running Roberta Question Answering (and also other Huggingface models) in CPU inference mode, I get an extra output returned by dynamo, that did not happen in a previous 2.3.1 version (see yellow extra output):
![image](https://github.com/user-attachments/assets/d3ea3750-7ca1-44a0-ad0f-7017d0cb116f)

This is a bug in _dynamo/symbolic_convert.py, which seems to be picking out an extra item "hidden_states_95" item, even though we know that output.hidden_states is Null:


[bug.txt](https://github.com/user-attachments/files/16908602/bug.txt)



### Versions

2.4.0, 2.4.1

cc @ezyang @gchanan @zou3519 @kadeng @msaroufim @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @amjames @rec
Repository: kubernetes
Issue: topologySpreadConstraints not working as expected
Labels: kind/bug,sig/scheduling,kind/support,lifecycle/stale,needs-triage

### What happened?

After an upgrade where the deployment restarts, we have identified that the ingress-nginx pods didn't spread across all three AWS AZ's although we have topologyspeadcontraint defined, which resulted in a failure.
While doing a NSlookup of NLB, we observed that only 2 public IP's were returned, even though NLB has 3 public IP's. The third one is supposed to be on availability zone 1b of K8S NLB, but we don't have any ingress pods running in 1b AZ. 
As a fix we added more pods to ingress-nginx controller, which added new pods to 1b AZ, then we did the nslookup again and found three IP's.

Attached the topologyspeadcontraint as defined in our nginx pod deployment-

      nodeSelector:
        dedicated: system
      restartPolicy: Always
      schedulerName: default-scheduler
      topologySpreadConstraints:
      - labelSelector:
          matchLabels:
            app.kubernetes.io/name: ingress-nginx
        maxSkew: 1
        topologyKey: topology.kubernetes.io/zone
        whenUnsatisfiable: DoNotSchedule






### What did you expect to happen?

The pods are supposed to be evenly spread across all 3 AZs

### How can we reproduce it (as minimally and precisely as possible)?

Pod deployment with topologySpreadConstraints has this issue

### Anything else we need to know?

Seems to be an issue when node Selector is defined

### Kubernetes version

EKS version v1.28.3

### Cloud provider

AWS

### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>

```[tasklist]
### Tasks
```
Repository: langchain
Issue: Add support for non-OpenAI models on Azure
Labels: Ɑ:  models,04 new feature

### Privileged issue

- [X] I am a LangChain maintainer, or was asked directly by a LangChain maintainer to create an issue here.

### Issue Content

Models like llama-3 are now hosted on azure.
Repository: godot
Issue: Standalone expression "text.right(-50)" not caught by debugger
Labels: enhancement,discussion,topic:gdscript

### Tested versions

4.3

### System information

Godot v4.3.stable - Ubuntu 22.04.4 LTS 22.04 - X11 - GLES3 (Compatibility) - llvmpipe (LLVM 15.0.7, 256 bits) - AMD EPYC 7763 64-Core Processor (2 Threads)

### Issue description

Instead of writing
```
func add_text(msg)
	text += msg + "\n"
	while len(text)>10000:
		text = text.right(-50)
```
I accidentally wrote
```
func add_text(msg)
	text += msg + "\n"
	while len(text)>10000:
		text.right(-50)		#no assignment
```
When ```text``` is long enough, this loops forever.

I think the debugger should have picked this up as a standalone expression.

### Steps to reproduce

Create a project with this code and run it.

```
func _ready():
	var text = "ABCD"
	while len(text)>2:
		text.right(-1)
```

You won't get a warning or an error, and it will loop forever

### Minimal reproduction project (MRP)

See above