sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: ant-design
Issue: Chaning value field via Fieldnames prop disabling the search feature on TreeSelect
Labels: Inactive,unconfirmed

### Reproduction link

[![Edit on StackBlitz](https://developer.stackblitz.com/img/open_in_stackblitz.svg)](https://stackblitz.com/edit/react-pjmgfx?file=demo.tsx)

### Steps to reproduce

Change tree data to this 
```   
{
    key: 'parent 1',
    title: 'parent 1',
    children: []
}
```

and give `fieldNames={{ value: 'key' }}` to the `<TreeSelect/>`

### What is expected?

I expect to work as same as we use "value" insted of changed field.

### What is actually happening?

Search does not find any result.

| Environment | Info |
| --- | --- |
| antd | 5.17.3 |
| React | 18.3.1 |
| System | MacOs |
| Browser | Chrome Version 124.0.6367.201 (Official Build) (x86_64) |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: rust
Issue: Tracking issue for migrating from Glacier to compiletest ICE/crash tracking
Labels: A-testsuite,T-compiler,C-tracking-issue,A-compiletest

Tracks the necessary steps to "fully"[^1] transition from [rust-lang/glacier] to `compiletest` ICE/crash tracking inside `tests/crashes/`.
See also [this Zulip topic][zulip].

### Steps

- [x] Implement `rustc` ICE/crash tracking: #122997
- [ ] Implement `rustdoc` ICE/crash tracking
- [ ] ~~Implement `rustfmt` ICE/crash tracking~~ (questionable)
- [ ] Implement ICE/crash tracking via `run-make`/`rmake` (to supersede Glacier's shell scripts)
- [x] Archive [rust-lang/glacier]: rust-lang/team#1459
- [ ] Sunset [triagebot] support for Glacier
- [ ] Update the [rustc-dev-guide]
  * Remove mentions of Glacier
  * Add small section about `tests/crashes/`: Overview, rough procedure (adding `//@ known-bug`, https://github.com/rust-lang/rust/labels/S-bug-has-test)
  * Mention `tests/crashes/` in places where we reference https://github.com/rust-lang/rust/labels/E-needs-test
- [ ] Update the [Rust Forge][forge]
  * Remove mentions of Glacier (namely the [triagebot section](https://forge.rust-lang.org/triagebot/glacier.html))
  * Maybe mention the new system in the [issue triaging chapter](https://forge.rust-lang.org/release/issue-triaging.html) 
- [ ] If technically feasible, add a CI check that a PR fixing crash tests mentions all fixed issues via GH auto-close keywords like *Fixes* to prevent the accumulation of "ghost issues".

### Unresolved Questions

* Should we implement `rustdoc` support via subdirectories/tests suites (e.g., `tests/crashes/rustdoc/`) or via a new compiletest directive (e.g., `//@ bin: rustdoc`)
  * If we do the former, should we move `rustc` tests from `tests/crashes/` to `tests/crashes/rustc/`?
* Should we define *precise* procedures for adding new tests to `tests/crashes`?

[rust-lang/glacier]: https://github.com/rust-lang/glacier/
[rustc-dev-guide]: https://rustc-dev-guide.rust-lang.org/
[forge]: https://forge.rust-lang.org/
[triagebot]: https://github.com/rust-lang/triagebot/
[zulip]: https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/where.20to.20mass-add.20known.20ices.20.2F.20merging.20glacier.20into.20rust/near/429082963
[^1]: Glacier|_{rust-lang/rust}, i.e., restriction of Glacier to rust-lang/rust (excluding git submodules/subtrees), i.e., Glacier without support for rustfmt, Cargo, Clippy, Miri ICE/crash tracking
Repository: godot
Issue: GLB/GLTF Import Rendering Issues on both Mobile/GL Compatible renders.
Labels: bug,topic:rendering,confirmed,topic:3d

### Tested versions

- Reproducible in Godot 4.2.2 Stable and 4.0.2 Stable

### System information

Windows 10 - Godot 4.2.2 Stable - Vulkan(Mobile) and GL Compatible

### Issue description

I have uploaded a small issue on Reddit about me uploading my models from Blender to Godot (GLTF).
[Link to Thread](https://www.reddit.com/r/godot/comments/1cz0hyh/rendering_issue_on_import_is_this_a_bug_godot_422/)
I managed to try and dig for what was the issue and it turns out I was only getting this rendering bug in every renderer except the default Forward+ mode. Below I'll attach in-editor shots where some models render properly while others aren't
![RenderingBug_ForwardPlus](https://github.com/godotengine/godot/assets/7853845/ef316ff3-a110-4b65-ac1d-714fa1a5b96c)
![RenderingBug_VKMobile](https://github.com/godotengine/godot/assets/7853845/183e8210-5f13-46d6-a36e-b7bb1fe1a6b0)
![RenderingBug_CMB](https://github.com/godotengine/godot/assets/7853845/f2cdc4ac-a5b4-4aa1-8b88-314c26abaac9)


### Steps to reproduce

As of right now, I'm using Blender 3.6 LTS
Export Mesh to GLTF 2.0 into Godot.
Set Renderer type to either Vulkan(Mobile) or GL Compatible.
Check in see in both In Editor and Import Mesh Window if the mesh is properly rendering correctly.

### Minimal reproduction project (MRP)

Unfortunately, the compression of my file is too large (106 MB) in size. I tried 7Zip, but Github does not except that file format.
Repository: create-react-app
Issue: Don't replace CRA
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?

the most known problem of the CRA of course. maintenance, debugging and speed. 



### Describe the solution you'd like


referring to this issue at react dev [#11262](https://github.com/reactjs/react.dev/pull/5487#issuecomment-1409720741)

I think we've gone so far with front end, and it was unnecessary. open source is beautiful but causing fragmentation now, especially with this CRA case.

from my understanding, the main reason why developers are getting excited by Vite or build tools like that are 2 reasons:

they are faster
they are less buggy
so, there's no need to really ditch CRA or convert it to something completely new. with proper and updated tools, it will be ok.



### Describe alternatives you've considered

 as a developer, I chose web development as a job not hobby and I'm sure me and thousands of other developers have a life to live. I can't really afford, hacking with Vite config and submitting issues and diving into plugin eco system. create-react-app offered an amazing zero config way to just set the project up and running and now we are losing this tool. I haven't touched webpack config or any bundler config for 3 years and that saved lots of time. it was perfect.

my suggestion might look naive, but I suggest ditching all deprecated dependencies and replacing old and slow tools with newer ones.
there's no force to do all of them at 1 night.
if there are no qualified libraries and dependencies to replace the old ones, it's ok. it can stay that way for a while.


### Additional context

we can keep it simple. we don't really need top to bottom 100% revolutionary reconstruction. CRA needs a bit of housekeeping. I think other proposed solutions are either exteremly complex or hard to deploy. 


please consider updating underlying dependencies and their vulnerabilities. this step itself, will add convince to further improvements and replacing slow libraries with newer and faster ones.
Repository: pytorch
Issue: Add ability to pass `MAP_NORESERVE` to`mmap(2)` call in `torch.serialization.set_default_mmap_options`
Labels: module: serialization,triaged

### 🚀 The feature, motivation and pitch

https://github.com/pytorch/pytorch/pull/124889 added the ability to set the default `torch.load(mmap=True)` behavior to use `MAP_SHARED`. 

Another potentially useful flag is `MAP_NORESERVE` ([see mmap(2) docs](https://man7.org/linux/man-pages/man2/mmap.2.html)).

> Do not reserve swap space for this mapping.  When swap
    space is reserved, one has the guarantee that it is
    possible to modify the mapping.  When swap space is not
    reserved one might get SIGSEGV upon a write if no physical
    memory is available.  See also the discussion of the file
    /proc/sys/vm/overcommit_memory in [proc(5)](https://man7.org/linux/man-pages/man5/proc.5.html).  Before Linux
    2.6, this flag had effect only for private writable
              mappings.

This does not reserve swap space for a given mapping upfront, but does so lazily, which can be useful (e.g. when a process mmaps a file with `MAP_PRIVATE` but does not intend to write to that mapping).

Contrary to `MAP_SHARED`, this has not yet been threaded to the eventual `mmap(2)` call, so the work here would also involve plumbing to the `mmap` call. The eventual `mmap` call that this is [here in `MapAllocator.cpp`](https://github.com/pytorch/pytorch/blob/3008ab7ae8394f0e54867c19c7e332e2fe540486/aten/src/ATen/MapAllocator.cpp#L317-L321)

### Alternatives

_No response_

### Additional context

_No response_

cc @mruberry @msaroufim
Repository: flutter
Issue: Add separated variant to SliverFixedExtentList widget
Labels: c: new feature,framework,f: scrolling,c: proposal,P3,team-framework,triaged-framework

### Use case

I am using `SliverList.separated` inside `CustomScrollView`. All my list items are of same height, so I wanted to use `prototypeItem` property. But, that is available only in `SliverPrototypeExtentList.builder` widget which doesn't have the `separatorBuilder` property which I need to show `Divider` widgets.

### Proposal

Add `SliverPrototypeExtentList.separated` construct similar to `ListView.separated` and `SliverList.separated`.
Repository: pytorch
Issue: xpu: can't build XPU backend without sourcing oneAPI environment variables (/opt/intel/oneapi/setvars.sh)
Labels: triaged,module: xpu

Current instructions to build XPU backend:
* https://github.com/pytorch/pytorch?tab=readme-ov-file#intel-gpu-support
* https://www.intel.com/content/www/us/en/developer/articles/tool/pytorch-prerequisites-for-intel-gpus.html (linked from readme)

User who will be directly following these instructions will actually build pytorch without XPU backend support. To actually build XPU backend one must source oneAPI environment variables, i.e. procedure should be:
1. Step 1: Install Intel GPU Drivers (from intel.com instruction)
1. Step 2: Install Intel Support Packages (from intel.com instruction)
1. **Configure oneAPI environment variables**:
```
source /opt/intel/oneapi/setvars.sh
```

I believe that as a minimum environment setup step should be described in documentation. However, optimally this step should not be required and environment should have been setup on a moment when user installed respective packages, i.e. during step 2 package installation:
```
sudo apt install intel-for-pytorch-gpu-dev intel-pti-dev
```

CC: @gujinghui @EikanWang @fengyuan14 @guangyey @jgong5

cc @gujinghui @EikanWang @fengyuan14 @guangyey
Repository: pytorch
Issue:  `indices_or_sections` parameter of `dsplit()` doesn't work while `sections` or `indices` parameter works
Labels: triaged,module: python frontend,topic: fuzzer

### 📚 The doc issue

[The doc](https://pytorch.org/docs/stable/generated/torch.dsplit.html) of `dsplit()` says that there is `indices_or_sections` parameter as shown below but there isn't:

> indices_or_sections ([int](https://docs.python.org/3/library/functions.html#int) or [list](https://docs.python.org/3/library/stdtypes.html#list) or [tuple](https://docs.python.org/3/library/stdtypes.html#tuple) of ints) – See argument in

Actually, `indices_or_sections` parameter doesn't work while `sections`(`int`) or `indices`(`tuple` of `int` or `list` of `int`) parameter works as shown below:

```python
import torch

my_tensor = torch.tensor([[[0, 1, 2, 3],
                           [4, 5, 6, 7],
                           [8, 9, 10, 11]]])
torch.dsplit(input=my_tensor, indices_or_sections=1) # Error
torch.dsplit(input=my_tensor, indices_or_sections=(1, 2)) # Error

torch.dsplit(input=my_tensor, sections=1)
# (tensor([[[0, 1, 2, 3],
#           [4, 5, 6, 7],
#           [8, 9, 10, 11]]]),)

torch.dsplit(input=my_tensor, indices=(1, 2))
# (tensor([[[0], [4], [8]]]),
#  tensor([[[1], [5], [9]]]),
#  tensor([[[2, 3], [6, 7], [10, 11]]]))
```

### Suggest a potential alternative/fix

So, [the doc](https://pytorch.org/docs/stable/generated/torch.dsplit.html) of `dsplit()` should be as shown below:

> `indices`(`tuple` of `int` or `list` of `int`) or `sections`(`int`) – See argument in

cc @albanD
Repository: flutter
Issue: Add-to-app should support predictive back route transitions
Labels: c: new feature,platform-android,framework,f: routes,a: existing-apps,c: proposal,P2,team-text-input,triaged-text-input

### Use case

As of https://github.com/flutter/engine/pull/52302, predictive back works in Android add-to-app everywhere except within Flutter routes (predictive back route transitions was added in https://github.com/flutter/flutter/pull/141373). Add-to-app should support predictive back route transitions too.

### Proposal

Support route transitions in FlutterFragment. This would be similar to how it was added for FlutterActivity in https://github.com/flutter/engine/pull/49093, but in FlutterFragment like https://github.com/flutter/engine/pull/52302, which added basic predictive back support there.

Predictive back route transitions within Flutter look like this:


https://github.com/flutter/flutter/assets/8436039/96b6dc20-89c9-45db-b8b4-aec7e996477b

### How to reproduce

Run an add-to-app Flutter app where the Flutter part has multiple routes, like this: https://github.com/justinmc/flutter-add-to-app

Perform a back gesture to go from one Flutter route to another. You should be able to peek at the previous route and cancel the gesture, but instead you just get the typical ZoomPageTransition.
Repository: PowerToys
Issue: Activate Zone Mode with shortcut before the click
Labels: Needs-Triage

### Description of the new feature / enhancement

I hold down a shortcut (I would end up making it a macro) key combination, then move my cursor to any area on a window I want to resize/move.
The shortcut key combo + mouse button (any button on mouse would work) would activate the move command on the active/clicked on window and bring up zone view all in one swoop.

### Scenario when this would be used?

Expedite the time it takes to move a window.

I would set up the shortcut to either:
- A few random key strokes, then map a macro onto my mouse to be able to hold down mapped button on mouse, and hold down left click to begin dragging window WITHOUT aiming the mouse for the top bar of the window
- Left and right click at same time and hold to auto move the window and bring up fancy zones while both buttons are held would be nice too

### Supporting information

_No response_
Repository: pytorch
Issue: `indices_or_sections` parameter of `tensor_split()` doesn't work while `sections`, `indices` or `tensor_indices_or_sections` parameter works
Labels: triaged,module: python frontend,topic: fuzzer

### 📚 The doc issue

[The doc](https://pytorch.org/docs/stable/generated/torch.tensor_split.html) of `tensor_split()` says that there is `indices_or_sections` parameter as shown below but there isn't:

> indices_or_sections ([Tensor](https://pytorch.org/docs/stable/tensors.html#torch.Tensor), [int](https://docs.python.org/3/library/functions.html#int) or [list](https://docs.python.org/3/library/stdtypes.html#list) or [tuple](https://docs.python.org/3/library/stdtypes.html#tuple) of ints) –

Actually, `indices_or_sections` parameter doesn't work while `sections`(`int`), `indices`(`tuple` of `int` or `list` of `int`) or `tensor_indices_or_sections`(`tensor` of `int`) parameter works as shown below:

```python
import torch

my_tensor = torch.tensor([[0, 1, 2, 3],
                          [4, 5, 6, 7],
                          [8, 9, 10, 11]])
torch.tensor_split(input=my_tensor, indices_or_sections=1) # Error
torch.tensor_split(input=my_tensor, indices_or_sections=(1, 2)) # Error
torch.tensor_split(input=my_tensor, indices_or_sections=torch.tensor(1)) # Error
torch.tensor_split(input=my_tensor, indices_or_sections=torch.tensor([1, 2])) # Error

torch.tensor_split(input=my_tensor, sections=1)
# (tensor([[0, 1, 2, 3],
#          [4, 5, 6, 7],
#          [8, 9, 10, 11]]),)

torch.tensor_split(input=my_tensor, indices=(1, 2))
# (tensor([[0, 1, 2, 3]]),
#  tensor([[4, 5, 6, 7]]),
#  tensor([[8, 9, 10, 11]]))

torch.tensor_split(input=my_tensor, tensor_indices_or_sections=torch.tensor(1))
# (tensor([[0, 1, 2, 3],
#          [4, 5, 6, 7],
#          [8, 9, 10, 11]]),)

torch.tensor_split(input=my_tensor, tensor_indices_or_sections=torch.tensor([1, 2]))
# (tensor([[0, 1, 2, 3]]),
#  tensor([[4, 5, 6, 7]]),
#  tensor([[8, 9, 10, 11]]))
```

### Suggest a potential alternative/fix

So, [the doc](https://pytorch.org/docs/stable/generated/torch.tensor_split.html) of `tensor_split()` should be as shown below:

> `indices`(`tuple` of `int` or `list` of `int`), `sections`(`int`) or `tensor_indices_or_sections`(`tensor` of `int`) –

cc @albanD
Repository: pytorch
Issue: [CI] Download android and ios dependencies from pip instead of conda
Labels: oncall: mobile

All the packages, except mkl-include and blas are already on pypi
We shouldn't need the above two to build android or ios
Repository: pytorch
Issue:  `indices_or_sections` parameter of `vsplit()` doesn't work while `sections` or `indices` parameter works
Labels: triaged,module: python frontend,topic: fuzzer

### 📚 The doc issue

[The doc](https://pytorch.org/docs/stable/generated/torch.vsplit.html) of `vsplit()` says that there is `indices_or_sections` parameter as shown below but there isn't:

> indices_or_sections ([int](https://docs.python.org/3/library/functions.html#int) or [list](https://docs.python.org/3/library/stdtypes.html#list) or [tuple](https://docs.python.org/3/library/stdtypes.html#tuple) of ints) – See argument in

Actually, `indices_or_sections` parameter doesn't work while `sections`(`int`) or `indices`(`tuple` of `int` or `list` of `int`) parameter works as shown below:

```python
import torch

my_tensor = torch.tensor([[0, 1, 2, 3],
                          [4, 5, 6, 7], 
                          [8, 9, 10, 11]])
torch.vsplit(input=my_tensor, indices_or_sections=1) # Error
torch.vsplit(input=my_tensor, indices_or_sections=(1, 2)) # Error

torch.vsplit(input=my_tensor, sections=1)
# (tensor([[0, 1, 2, 3],
#          [4, 5, 6, 7],
#          [8, 9, 10, 11]]),)

torch.vsplit(input=my_tensor, indices=(1, 2))
# (tensor([[0, 1, 2, 3]]),
#  tensor([[4, 5, 6, 7]]),
#  tensor([[8, 9, 10, 11]]))
```

### Suggest a potential alternative/fix

So, [the doc](https://pytorch.org/docs/stable/generated/torch.vsplit.html) of `vsplit()` should be as shown below:

> `indices`(`tuple` of `int` or `list` of `int`) or `sections`(`int`) – See argument in

cc @albanD
Repository: pytorch
Issue:  `indices_or_sections` parameter of `hsplit()` doesn't work while `sections` or `indices` parameter works
Labels: triaged,module: python frontend,topic: fuzzer

### 📚 The doc issue

[The doc](https://pytorch.org/docs/stable/generated/torch.hsplit.html) of `hsplit()` says that there is `indices_or_sections` parameter as shown below but there isn't:

> indices_or_sections ([int](https://docs.python.org/3/library/functions.html#int) or [list](https://docs.python.org/3/library/stdtypes.html#list) or [tuple](https://docs.python.org/3/library/stdtypes.html#tuple) of ints) – See argument in

Actually, `indices_or_sections` parameter doesn't work while `sections`(`int`) or `indices`(`tuple` of `int` or `list` of `int`) parameter works as shown below:

```python
import torch

my_tensor = torch.tensor([[0, 1, 2, 3],
                          [4, 5, 6, 7], 
                          [8, 9, 10, 11]])
torch.hsplit(input=my_tensor, indices_or_sections=1) # Error
torch.hsplit(input=my_tensor, indices_or_sections=(1, 2)) # Error

torch.hsplit(input=my_tensor, sections=1)
# (tensor([[0, 1, 2, 3],
#          [4, 5, 6, 7],
#          [8, 9, 10, 11]]),)

torch.hsplit(input=my_tensor, indices=(1, 2))
# (tensor([[0], [4], [8]]),
#  tensor([[1], [5], [9]]),
#  tensor([[2, 3], [6, 7], [10, 11]]))
```


### Suggest a potential alternative/fix

So, [the doc](https://pytorch.org/docs/stable/generated/torch.hsplit.html) of `hsplit()` should be as shown below:

> `indices`(`tuple` of `int` or `list` of `int`) or `sections`(`int`) – See argument in

cc @albanD
Repository: angular
Issue: Vim/Neovim Language Service Setup Removed?
Labels: area: language-service

### Describe the problem that you experienced

The new angular.dev docs seem to have removed Vim/Neovim language server setup.

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

https://angular.dev/tools/language-service#angular-language-service-in-your-editor

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

_No response_

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

Neovim v0.10 seems to be encountering a segfault when trying use the new control-flow syntax. This led me to looking for the language service setup documentation which used to be at https://angular.io/guide/language-service#neovim.

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

_No response_

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

_No response_

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

_No response_

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

_No response_

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

_No response_
Repository: go
Issue: cmd/compile: "panic: unification reached recursion depth limit" with recursive type constraint
Labels: NeedsInvestigation,early-in-cycle,compiler/runtime

### Go version

go version go1.22.3 darwin/arm64

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

```shell
GO111MODULE=''
GOARCH='arm64'
GOBIN=''
GOCACHE='/Users/cameronmartin/Library/Caches/go-build'
GOENV='/Users/cameronmartin/Library/Application Support/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='arm64'
GOHOSTOS='darwin'
GOINSECURE=''
GOMODCACHE='/Users/cameronmartin/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='darwin'
GOPATH='/Users/cameronmartin/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/Users/cameronmartin/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.22.3.darwin-arm64'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='go1.22.3+auto'
GOTOOLDIR='/Users/cameronmartin/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.22.3.darwin-arm64/pkg/tool/darwin_arm64'
GOVCS=''
GOVERSION='go1.22.3'
GCCGO='gccgo'
AR='ar'
CC='clang'
CXX='clang++'
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/k3/7h82b52d2gz972yl3nppjdtw0000gn/T/go-build29573479=/tmp/go-build -gno-record-gcc-switches -fno-common'
```


### What did you do?

https://go.dev/play/p/_dEZsvc-bV-

### What did you see happen?

`<unknown line number>: internal compiler error: panic: unification reached recursion depth limit`

### What did you expect to see?

I expected a non-panic compilation error.

(But maybe I shouldn't have; with a couple of tweaks, a similar program is valid: https://go.dev/play/p/jJ8fTc7Uhie)
Repository: pytorch
Issue: Make grid_sample a bit more intuitive to use 
Labels: module: docs,module: nn,triaged

### 🚀 The feature, motivation and pitch

Hello

I used [torch.nn.functional.grid_sample](https://pytorch.org/docs/stable/generated/torch.nn.functional.grid_sample.html) for the first time today.

IIt took me a while to realize that the values of the `grid` parameter should be (mostly) in the [-1, 1] interval. It's well written in the documentation but not really highlighted and I missed this information on my first reading.

I think the best thing would be to add a "grid_scale" parameter that could handle cases where the values are between [0,1] or [0,(h or w)].
The modification seems simple to implement. If the idea is approved, I can propose a PR.

What do you think?  

### Alternatives

_No response_

### Additional context

_No response_

cc @svekars @brycebortree @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki