sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: tauri
Issue: [bug] cant use leptos with mobile in latest beta
Labels: type: bug,status: needs triage

### Describe the bug

Cant use leptos with ssr in mobile but can in desktop, in mobile i just get crashes

### Reproduction

Heres a link to the [repo](https://github.com/Alt-iOS/tailwind-leptos-tauri-template.git)
simply run 

1. `cargo tauri ios init`
2. `cargo tauri ios dev`
3. click the button on the app 

attempt the same on desktop and theres no issue

### Expected behavior

For it to send a response from the server

### Full `tauri info` output

```text
[✔] Environment
    - OS: Mac OS 14.4.1 X64
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.78.0 (9b00956e5 2024-04-29)
    ✔ cargo: 1.78.0 (54d8815d0 2024-03-26)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-aarch64-apple-darwin (environment override by RUSTUP_TOOLCHAIN)
    - node: 22.1.0
    - pnpm: 9.1.0
    - yarn: 1.22.19
    - npm: 10.7.0
    - bun: 1.1.7

[-] Packages
    - tauri [RUST]: 2.0.0-beta.19
    - tauri-build [RUST]: 2.0.0-beta.15
    - wry [RUST]: 0.39.3
    - tao [RUST]: 0.28.0
    - tauri-cli [RUST]: 2.0.0-beta.17
    - @tauri-apps/api : not installed!
    - @tauri-apps/cli [NPM]: 2.0.0-beta.17

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../target/site/pkg/
    - devUrl: http://localhost:8000/

[-] iOS
    - Developer Teams: Víctor Batarse Shija (ID: AZKVA57TK7)
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: ollama
Issue: Model request: Functionary v2.4.
Labels: model request

Hello,

Is there a possibility to run ollama with functionary small v2.4?
It it very good model for tool calling.

BR
Krzysztof
Repository: godot
Issue: No UndoRedo inspector hook callback on multiple simultanious edits.
Labels: bug,topic:plugin

### Tested versions

v4.3.dev5.official [c9c17d6ca]

### System information

Godot v4.3.dev5 - Linux Mint 20.1 (Ulyssa) - X11 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1060 (nvidia; 535.171.04) - Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 Threads)

### Issue description

I am writing A plugin and using 'add_undo_redo_inspector_hook_callback()' to get callbacks on any edit to an objects properties, and when multiple nodes are selected it simply does not callback.
I was expecting this callback to run once for each property edited that way my plugin could react to each property change.

https://github.com/godotengine/godot/assets/85406370/9199e438-700c-46a7-b367-8eaa54125f04



### Steps to reproduce

1: Create an EditorPlugin and put 'add_undo_redo_inspector_hook_callback()' to the _enter_tree method hooking to A function for printing its outputs.(Script provided in MRP)
2: edit any property in the inspector, to see the expected result printed in the output tab.
3: Now highlight more than one node holding control and clicking them, and try editing A property they share in the inspector.
4: No callback, no print function in output.

### Minimal reproduction project (MRP)

plugin.gd

```gdscript
@tool
extends EditorPlugin

func _enter_tree() -> void:
	var callback = Callable(self, "callback")
	add_undo_redo_inspector_hook_callback(callback)
	pass


func _exit_tree() -> void:
	remove_undo_redo_inspector_hook_callback(callback)
	pass


func callback(undo_redo:Object,modifyed_object:Object,property:String,new_value:Variant):
	print(undo_redo.to_string())
	print(modifyed_object.to_string())
	print(property)
	print(new_value)
```
Repository: go
Issue: cmd/cgo/internal/testplugin: TestForkExec failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "cmd/cgo/internal/testplugin" && test == "TestForkExec"
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/f6b063fa08a8abdd0d15632e0478b2366a43b84f)):

    mkdir -p $TMPDIR/alt/src/testplugin
    rsync -a altpath/testdata/ $TMPDIR/alt/src/testplugin
    echo 'module testplugin' > $TMPDIR/alt/src/testplugin/go.mod
    mkdir -p $TMPDIR/src/testplugin
    rsync -a testdata/ $TMPDIR/src/testplugin
    echo 'module testplugin' > $TMPDIR/src/testplugin/go.mod
    cd $TMPDIR/alt/src/testplugin
    ( GOPATH=$TMPDIR/alt PWD=$TMPDIR/alt/src/testplugin /tmp/buildlet/go/bin/go build -gcflags '' -buildmode=plugin -o $TMPDIR/src/testplugin/plugin-mismatch.so ./plugin-mismatch )
    cd $TMPDIR/src/testplugin
    ( GOPATH=$TMPDIR PWD=$TMPDIR/src/testplugin LD_LIBRARY_PATH=$TMPDIR/src/testplugin /tmp/buildlet/go/bin/go build -gcflags '' -buildmode=plugin ./plugin1 )
    ...
    ( GOPATH=$TMPDIR PWD=$TMPDIR/src/testplugin LD_LIBRARY_PATH=$TMPDIR/src/testplugin /tmp/buildlet/go/bin/go build -gcflags '' -o issue53989.exe ./issue53989/main.go )
    ( GOPATH=$TMPDIR PWD=$TMPDIR/src/testplugin LD_LIBRARY_PATH=$TMPDIR/src/testplugin ./issue53989.exe )
    ( GOPATH=$TMPDIR PWD=$TMPDIR/src/testplugin LD_LIBRARY_PATH=$TMPDIR/src/testplugin /tmp/buildlet/go/bin/go build -gcflags '' -buildmode=plugin -o mangle.so ./mangle/plugin.go )
    ( GOPATH=$TMPDIR PWD=$TMPDIR/src/testplugin LD_LIBRARY_PATH=$TMPDIR/src/testplugin /tmp/buildlet/go/bin/go build -gcflags '' -buildmode=plugin -o issue62430.so ./issue62430/plugin.go )
    ( GOPATH=$TMPDIR PWD=$TMPDIR/src/testplugin LD_LIBRARY_PATH=$TMPDIR/src/testplugin /tmp/buildlet/go/bin/go build -gcflags '' -o issue62430.exe ./issue62430/main.go )
    ( GOPATH=$TMPDIR PWD=$TMPDIR/src/testplugin LD_LIBRARY_PATH=$TMPDIR/src/testplugin ./issue62430.exe )
    ( GOPATH=$TMPDIR PWD=$TMPDIR/src/testplugin LD_LIBRARY_PATH=$TMPDIR/src/testplugin /tmp/buildlet/go/bin/go build -gcflags '' -o forkexec.exe ./forkexec/main.go )
    --- FAIL: TestForkExec (15.96s)
        exec.go:193: test timed out while running command: ./forkexec.exe 1
        plugin_test.go:377: running command failed: signal: quit


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: ant-design
Issue: Extend Menu to have Slide menu effect 
Labels: Inactive,🧶 Low Priority,unconfirmed

### What problem does this feature solve?

There are design use case where you can click on submenu and the Menu slides to only show the current active menu like -> https://www.primefaces.org/primereact-v8/slidemenu/

### What does the proposed API look like?

maybe have a new props called mode="slide"

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: rust
Issue: Macro `literal` fragment specifiers should forward to exact tokens
Labels: A-macros,T-lang,A-maybe-future-edition,WG-macros

Motivating example ([playground link](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=21920157cef8d742250d61cf2a34290e)):

```rust
macro_rules! foo {
    ($a:literal) => {
        foo!(@inner $a);
    };
    (@inner true) => {
        println!("true");
    };
    (@inner false) => {
        println!("false");
    };
}

fn main() {
    foo!(true);
    foo!(false);
}
```

The above fails to compile because `literal` does not forward to exact matches, but it doesn't seem like there is any reason it shouldn't. `ident` or `tt` can be used, but loosening restrictions can cause other problems.

This probably couldn't be changed without an edition depending on fallout, but we can probably make sure this works with [macros 2.0](https://github.com/rust-lang/rust/issues/39412).

The reference makes a comment about forwarding here: https://doc.rust-lang.org/nightly/reference/macros-by-example.html#forwarding-a-matched-fragment
Repository: pytorch
Issue: [compile time] AOT Autograd is taking long time in tracing
Labels: high priority,triaged,oncall: pt2,module: aotdispatch,module: pt2-dispatcher

### 🐛 Describe the bug

profile - https://fburl.com/scuba/pyperf_experimental/on_demand/ghc8lpjr
xref - https://fb.workplace.com/groups/1075192433118967/permalink/1425136311457909/
Repro - D57090987

AOT Autograd is taking large amount of time. This is the rough breakdown 

~~~
Finished loading.
Ran eager model.
I0510 16:25:43.544000 139884208832960 torch/_dynamo/utils.py:331] TorchDynamo compilation metrics:
I0510 16:25:43.544000 139884208832960 torch/_dynamo/utils.py:331] Function                                  Runtimes (s)
I0510 16:25:43.544000 139884208832960 torch/_dynamo/utils.py:331] --------------------------------------  --------------
I0510 16:25:43.544000 139884208832960 torch/_dynamo/utils.py:331] _compile.<locals>.compile_inner               962.355
I0510 16:25:43.544000 139884208832960 torch/_dynamo/utils.py:331] OutputGraph.call_user_compiler                923.198
I0510 16:25:43.544000 139884208832960 torch/_dynamo/utils.py:331] create_aot_dispatcher_function                911.898
I0510 16:25:43.544000 139884208832960 torch/_dynamo/utils.py:331] compile_fx.<locals>.fw_compiler_base          377.886
I0510 16:25:43.544000 139884208832960 torch/_dynamo/utils.py:331] compile_fx_inner                              375.881
I0510 16:25:43.544000 139884208832960 torch/_dynamo/utils.py:331] GraphLowering.run                             186.831
I0510 16:25:43.544000 139884208832960 torch/_dynamo/utils.py:331] GraphLowering.compile_to_module               129.836
I0510 16:25:43.544000 139884208832960 torch/_dynamo/utils.py:331] Scheduler.__init__                             60.484
I0510 16:25:43.544000 139884208832960 torch/_dynamo/utils.py:331] Scheduler.codegen                              33.0063
I0510 16:25:43.544000 139884208832960 torch/_dynamo/utils.py:331] WrapperCodeGen.generate                        27.8892
I0510 16:25:43.544000 139884208832960 torch/_dynamo/utils.py:331] cudagraphify                                    0.0035
I0510 16:25:43.544000 139884208832960 torch/_dynamo/utils.py:331] CachingAutotuner.benchmark_all_configs          3.9676
~~~

`create_aot_dispatcher_function` is taking 900 seconds, while `compile_fx_inner` is taking 375 seconds. So, around 500 seconds are spent in AOT Autograd.


### Generator strobelight profile:
use 
TORCH_COMPILE_STROBELIGHT=TRUE buck2 run ...
for more info how to navigate the profile see 
https://fb.workplace.com/groups/257735836456307/posts/669969978566222
### Error logs

_No response_

### Minified repro

_No response_

### Versions

N/A

cc @ezyang @gchanan @zou3519 @kadeng @msaroufim @chauhang @penguinwu @bdhirsh @yf225
Repository: pytorch
Issue: `torch.export` code that includes `torch.autograd.grad`
Labels: module: onnx,triaged,oncall: pt2,oncall: export

### 🐛 Describe the bug

The following minimal example (based on a large real-world model which fails the same way) fails with errors in `torch.export`:
```python
import torch

class F(torch.nn.Module):
    def forward(self, x):
        y = x.square()
        return torch.autograd.grad(y.sum(), x)

f = F()
x = torch.ones(3)
x.requires_grad_(True)
print(f(x))

f = F()
x = torch.ones(3)
x.requires_grad_(True)
print(torch.export.export(f, args=(x,), strict=False))
```
printing (omitting backtraces):
```
(tensor([2., 2., 2.]),)
[...]
RuntimeError: element 0 of tensors does not require grad and does not have a grad_fn
```
With `strict=True`, it errors as
```
Unsupported: 'skip function grad in file site-packages/torch/autograd/__init__.py'
```

Is exporting through a module that includes internal calls to the autograd engine a supported usecase for `torch.export` (and other related APIs, like `torch._export.aot_compile`)?

### Error logs

_No response_

### Minified repro

_No response_

### Versions

PyTorch 2.3.0

cc @ezyang @chauhang @penguinwu @avikchaudhuri @gmagogsfm @zhxchen17 @tugsbayasgalan @angelayi @suo @ydwu4 @msaroufim @bdhirsh @anijain2305
Repository: rust
Issue: Panics don't lock stderr while printing panic info
Labels: C-feature-request,T-libs,A-panic

Panics don't seem to lock stderr while printing, so if multiple threads panic at once, this will happen:
```
thread 'thread 'thread 'thread 'State runner 5 (sync)State runner 1 (sync)State runner 0 (sync)State runner 4 (sync)' panicked at ' panicked at ' panicked at ' panicked at src/circuits/relay.rssrc/circuits/relay.rssrc/circuits/relay.rssrc/circuits/relay.rs::::167167167167::9::9:
99:
not yet implemented:
:
not yet implemented
not yet implementednot yet implemented
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
```

As you can see, i forgot a `todo!()` in the code and 4 threads executed it at the same time

### Meta
`rustc --version --verbose`:
```
rustc 1.79.0-nightly (ccfcd950b 2024-04-15)
binary: rustc
commit-hash: ccfcd950b333fed046275dd8d54fe736ca498aa7
commit-date: 2024-04-15
host: x86_64-unknown-linux-gnu
release: 1.79.0-nightly
LLVM version: 18.1.3
```
Repository: go
Issue: net/http: TestTLSHandshakeTrace failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "net/http" && test == "TestTLSHandshakeTrace"
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/eb498c3890dee2a9d4be257e784e080071898c56)):

    2024/05/10 10:49:48 httptest.Server blocked in Close after 5 seconds, waiting for connections:
      *net.TCPConn 0xc000516238 127.0.0.1:50392 in state active
    --- FAIL: TestTLSHandshakeTrace (0.00s)
        --- FAIL: TestTLSHandshakeTrace/h2 (20.30s)
            transport_test.go:5193: Unexpected error making request: Get "https://127.0.0.1:50389": unexpected EOF


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: ollama
Issue: please show version info on download page
Labels: feature request,ollama.com

<img width="624" alt="截屏2024-05-11 11 09 49" src="https://github.com/ollama/ollama/assets/146583103/f76258d0-2b6c-4ae4-b997-6fa87317ac09">


please show version info on download page.
Repository: ollama
Issue: is there a way to make LLM model say something first, without blank waiting for me to say something?
Labels: feature request
Repository: next.js
Issue: assetPrefix with same name of route with catch-all segments won't work since 14.2 (Using Page Router)
Labels: bug,Pages Router

### Link to the code that reproduces this issue

https://github.com/yanni-fe/nextjs-reproduce-demo

### To Reproduce

1. Create a next.js project
2. Create a test route with catch-all segments
```
 pages
    |- demo
        |- [[...slug]].tsx
```
3. add assetPrefix with same name of route 
```
// next.config.js
const nextConfig = {
    assetPrefix: '/demo',
}
```

open `localhost:3000/demo` will return 404


### Current vs. Expected behavior

For versions before 14.2, it works well. After updating next.js to 14.2.3, it fails.

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 22.5.0
Binaries:
  Node: 18.17
  npm: 9.8.1
  Yarn: 1.22.19
Relevant Packages:
  next: 14.2.3
  eslint-config-next: 14.2.3
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.1.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Pages Router

### Which stage(s) are affected? (Select all that apply)

next dev (local), next start (local)

### Additional context

I think this is caused by this commit https://github.com/vercel/next.js/commit/4efe14238b5ab11935e73aa09631ef5ec8045b13

changes in [packages/next/src/server/lib/router-utils/filesystem.ts](https://github.com/vercel/next.js/commit/4efe14238b5ab11935e73aa09631ef5ec8045b13#diff-54dc0c66a8edd2065b992de624f72f55279f28574f9d87b2977cec6d3ad2694e)  at line 438
Repository: pytorch
Issue: DISABLED test_transformer_training_is_seq_parallel_True (__main__.DistTensorParallelExampleTest)
Labels: oncall: distributed,module: rocm,module: flaky-tests,skipped

Platforms: rocm

This test was disabled because it is failing on main branch ([recent examples](https://torch-ci.com/failure?failureCaptures=%5B%22distributed%2Ftensor%2Fparallel%2Ftest_tp_examples.py%3A%3ADistTensorParallelExampleTest%3A%3Atest_transformer_training_is_seq_parallel_True%22%5D)).

Same as https://github.com/pytorch/pytorch/issues/125918

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 @jeffdaily @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang @clee2000
Repository: PowerToys
Issue: duplicated in plugins list
Labels: Issue-Bug,Product-Settings,Needs-Triage,Run-Plugin Manager

### Microsoft PowerToys version

0.80.1

### Installation method

WinGet

### Running as admin

None

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

just open PowerToys Run settings

### ✔️ Expected Behavior

Im expecting only one name for each plugin

### ❌ Actual Behavior

instead I have duplicated plugins in list... like 2 Calculator, 2 Folder, 2 History, etcetera

### Other Software

_No response_
Repository: ollama
Issue: Feature Request: Support asynchronous pull API endpoint
Labels: feature request,api

It would be helpful if we could instruct ollama to download a model without having to wait for the completion, since the model can be quite large in some cases.  Ideally subsequent requests to pull the same model would avoid doing anything (maybe return the current status message?).  Eventually once it finishes downloading, it shows up in the /api/tags output.

Thanks!
Repository: godot
Issue: Tweener doesn't keep final value from last tweener when combining as_relative and set_delay
Labels: bug,topic:core

### Tested versions

v4.2.1.stable.official [b09f793f5]

### System information

Godot v4.2.1.stable - Windows 10.0.22631 - Vulkan (Forward+) - integrated Intel(R) Iris(R) Xe Graphics (Intel Corporation; 31.0.101.5445) - 12th Gen Intel(R) Core(TM) i5-12500H (16 Threads)

### Issue description

This piece of code:

```gdscript
func _ready() -> void:
	progress_bar.value = 20
	var tween = create_tween()
	tween.tween_property(progress_bar, "value", 30, 1).as_relative()
	tween.tween_property(progress_bar, "value", -10, 1).as_relative().set_delay(1)
```

(if I am right) should tween the value of the progress bar to 50, then 40 in a delay of 1s. But it gets 10 in the end.

It works as expected if I remove `set_delay` and add a `tween_interval`.

It's not a bug of progress bar. It can be reproduced on other objects.

Seems the condition in `PropertyTweener::start()` makes it so?

### Steps to reproduce

Run the main scene

### Minimal reproduction project (MRP)

[TweenerIssue.zip](https://github.com/godotengine/godot/files/15282024/TweenerIssue.zip)
Repository: next.js
Issue: Missing Ecmascript features in webpack
Labels: bug,Webpack

### Link to the code that reproduces this issue

https://github.com/vercel/next.js/pull/65613/files

### To Reproduce

The tests are already added but not all of them are enabled for webpack as webpack fails to parse them in the acorn parse that webpack does.

You can search for `TODO:` here: https://github.com/vercel/next.js/pull/65613/files

### Current vs. Expected behavior

These features should be supported when using webpack.

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.4.0: Wed Feb 21 21:44:43 PST 2024; root:xnu-10063.101.15~2/RELEASE_ARM64_T6000
  Available memory (MB): 32768
  Available CPU cores: 10
Binaries:
  Node: 18.17.1
  npm: 9.6.7
  Yarn: N/A
  pnpm: 8.15.7
Relevant Packages:
  next: 14.3.0-canary.54 // There is a newer canary version (14.3.0-canary.57) available, please upgrade!
  eslint-config-next: 14.3.0-canary.54
  react: 19.0.0-beta-4508873393-20240430
  react-dom: 19.0.0-beta-4508873393-20240430
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


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

Webpack

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

next dev (local), next build (local)

### Additional context

_No response_
Repository: ui
Issue: [bug]: Code block titles hidden in light theme
Labels: bug

### Describe the bug

Title of code blocks in the documentation is not visible in the light theme.

### Affected component/components

docs

### How to reproduce

1. Go to [Data Table > Basic Table](https://ui.shadcn.com/docs/components/data-table#basic-table)
2. Switch to Dark Theme.
3. Notice the code block under *Column Definitions* has a title of "app/payments/columns.tsx"
<img width="812" alt="Screenshot 2024-05-11 at 13 39 13" src="https://github.com/shadcn-ui/ui/assets/15344774/0f835f3c-29e3-45a3-9ee9-bdfc986a491c">
4. Switch to Light theme.
5. Notice that title disappears
<img width="802" alt="Screenshot 2024-05-11 at 13 38 29" src="https://github.com/shadcn-ui/ui/assets/15344774/10f07457-ccbc-4661-bc6a-3ed12c664fea">



### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Any browser
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: ollama
Issue: Pulling Multiple Models at Once
Labels: feature request

It would be nice if it could be possible to pull multiple models in one go in Ollama.

Today, I tried to run 

```
ollama pull llava-phi3 llava-llama3 llama3-gradient phi3 moondream codeqwen
```

and it gave following error:

```
Error: accepts 1 arg(s), received 6
```
Repository: pytorch
Issue: Inform when weights loading promotes types
Labels: module: nn,triaged

### 🚀 The feature, motivation and pitch

This motivates my issue https://discuss.pytorch.org/t/state-dict-and-loading-of-buffers/202015/2
Here is the problem when you do loading of the weights:
```python
def Module(nn.Module):
    def __init__(self, op_mode):
        super().__init__()
        self.register_buffer('running_max', torch.tensor(1)) # the tensor is int
    def forward(x):
         xmax = torch.max(torch.abs(x))
         self.running_max = (1 - self.momentum) * self.running_max + self.momentum * xmax # the tensor becomes float32
```
```python
In [1]: net = Module()

In [21]: state_dict['running_max'] # the serialized dict contains float32
Out[21]: tensor(2.8699, device='cuda:1')

In [23]: net.load_state_dict(state_dict) # It feels like it loaded properly everything
Out[23]: <All keys matched successfully>

In [22]: net.running_max # In reality the buffer does not load correctly because it has a different type
Out[22]: tensor(2)
```

It should not be like this, as it is very hard to diagnose why the loaded model behaves differently now. The message should read like
```python
n [23]: net.load_state_dict(state_dict) # It feels like it loaded properly everything
Out[23]: <All keys matched successfully, some keys 'running_max' need type promotion (demotion)> # or something like this
```

### Alternatives

There maybe needs to be some sort of warning or notification instead of saying "All keys matched successfully", which is clearly not the case

### Additional context

_No response_

cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki