sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: [dtensor] ops coverage tracker
Labels: oncall: distributed,triaged,module: dtensor

This issue is the overall tracker of the ops we are implementing currently and plan to implement soon, when we plan to add new ops we'll also try to update this issue to keep things in sync. 

### Current supported ops consolidation
replace the existing ops that implemented in rule with op strategy to increase op sharding coverage
- [x] aten.slice_backward.default, 
- [x] aten.bernoulli.default/aten.bernoulli_.float
- [ ] aten.split.Tensor, aten.split_with_sizes.default, aten.split_with_sizes_copy.default
- [x] aten.cat.default
- [ ] aten.index.Tensor
- [ ] aten.index_select.default
- [x] aten.squeeze.default, aten.squeeze.dim
- [x] aten.view.default, aten._unsafe_view.default, aten.reshape.default
- [x] aten.unsqueeze.default
- [x] aten.expand.default
- [x] aten.permute.default
- [x] aten.transpose.int, aten.t.default
- [ ] aten.repeat.default
- [ ] aten.convolution.default
- [ ] aten.convolution_backward.default


### Ops to be implemented (planned)
- [x] #120333
- [x] aten._scaled_dot_product_flash_attention_backward.default
- [ ] complex ops
- [x] clip_grad_norm_
- [x] aten.stack
- [ ] non_zero

cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @H-Huang @kwen2501 @awgu @penguinwu @fegin @XilunWu @fduwjj @wz337 @tianyu-l @wconstab @yf225
Repository: godot
Issue: [TRACKER] Wayland issues
Labels: platform:linuxbsd,topic:porting,tracker

### Tested versions

- Reproducible in: 4.3.dev3 and later

### System information

Linux/BSD - Wayland backend

### Issue description

A new, experimental and opt-in Wayland backend got merged in 4.3.dev3.

While it got tested plenty, there are still quite a bunch of missing features and lots of things to improve, which are tracked in this issue.

```[tasklist]
- [ ] https://github.com/godotengine/godot/issues/87747
- [ ] https://github.com/godotengine/godot/issues/87749
- [ ] https://github.com/godotengine/godot/issues/87963
- [ ] https://github.com/godotengine/godot/issues/88113
- [ ] https://github.com/godotengine/godot/issues/88151
- [ ] https://github.com/godotengine/godot/issues/88246
- [ ] https://github.com/godotengine/godot/issues/88248
- [ ] https://github.com/godotengine/godot/issues/88333
- [ ] https://github.com/godotengine/godot/issues/88364
- [ ] https://github.com/godotengine/godot/issues/88550
- [ ] https://github.com/godotengine/godot/issues/89257
- [ ] https://github.com/godotengine/godot/issues/89793
- [ ] https://github.com/godotengine/godot/issues/90612
- [ ] https://github.com/godotengine/godot/issues/91371
- [ ] https://github.com/godotengine/godot/issues/91921
- [ ] https://github.com/godotengine/godot/issues/92014
- [ ] https://github.com/godotengine/godot/issues/92594
- [ ] https://github.com/godotengine/godot/issues/92643
- [ ] https://github.com/godotengine/godot/issues/93098
- [ ] https://github.com/godotengine/godot/issues/93472
- [ ] https://github.com/godotengine/godot/issues/93788
- [ ] https://github.com/godotengine/godot/issues/93981
- [ ] https://github.com/godotengine/godot/issues/94157
- [ ] https://github.com/godotengine/godot/issues/94204
- [ ] https://github.com/godotengine/godot/issues/94218
- [ ] https://github.com/godotengine/godot/issues/94228
- [ ] https://github.com/godotengine/godot/issues/94445
- [ ] https://github.com/godotengine/godot/issues/95144
- [ ] https://github.com/godotengine/godot/issues/95256
- [ ] https://github.com/godotengine/godot/issues/92823
- [ ] https://github.com/godotengine/godot/issues/95566
- [ ] https://github.com/godotengine/godot/issues/95830
- [ ] #96074
- [ ] https://github.com/godotengine/godot/issues/96214
- [ ] https://github.com/godotengine/godot/issues/95649
- [ ] https://github.com/godotengine/godot/issues/96647
- [ ] https://github.com/godotengine/godot/issues/101408
- [ ] https://github.com/godotengine/godot/issues/100713
- [ ] https://github.com/godotengine/godot/issues/99392
- [ ] https://github.com/godotengine/godot/issues/101099
- [ ] https://github.com/godotengine/godot/issues/100747
```

### Steps to reproduce

From the CLI: start the engine with the `--display-driver wayland` flag.

Alternatively, for the editor: set the `run/platforms/linuxbsd/prefer_wayland` editor setting to `true` or, for running projects, set the `display/display_server/driver.linuxbsd` project setting to `wayland`.

### Minimal reproduction project (MRP)

N/A
Repository: rust
Issue: JavaScript code fence for documentation
Labels: T-rustdoc,C-feature-request,A-rustdoc-ui

I am using `wasm-bindgen` and in my documentation I would like to provide examples on how to call the function from JavaScript.

So I would like it to be able to specify JavaScript or TypeScript as the language for code fence block in the Markdown documentation and have it syntax highlighted in the generated Cargo documentation.

```rust
/// Calculates the sum of two integers.
/// 
/// # Examples
///
/// ```javascript
/// const result = add(10, 10);
/// ```
#[wasm_bindgen]
pub fn add(a: i32, b: i32) -> i32 {
    return a + b;
}
```
Repository: vscode
Issue: parentTerminal doesn't always work 
Labels: bug,help wanted,terminal-tabs

<!-- ⚠️⚠️ 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.86.1 (system setup)
Commit: 31c37ee8f63491495ac49e43b8544550fbae4533
Date: 2024-02-07T09:08:20.941Z
Electron: 27.2.3
ElectronBuildId: 26495564
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: 11.8.172.18-electron.0
OS: Windows_NT x64 10.0.19045
- OS Version: 
Edition	Windows 10 Enterprise
Version	22H2
Installed on	‎1/‎15/‎2021
OS build	19045.3930
Experience	Windows Feature Experience Pack 1000.19053.1000.0


Steps to Reproduce:

This is precisely the same as #131594.  The OP-provided code opens terminals that are separate from each other (not split).  Ditto for the very similar code quoted in response (the last block).  Unfortunately the OP did not follow up but I'm seeing exactly the same issue.

I've definitely seen `parentTerminal`  work when creating two terminals at the same moment and making one the `parentTerminal` of the other.  The option seems to be ignored if the supplied terminal was not created at the same moment, i.e. stored and used in a subsequent call.
Repository: pytorch
Issue: DISABLED test_tensor_subclasses (__main__.TestScript)
Labels: oncall: jit,triaged,module: flaky-tests,skipped,oncall: pt2,module: dynamo

Platforms: dynamo

This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_tensor_subclasses&suite=TestScript&limit=100) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/21580312991).

Over the past 3 hours, it has been determined flaky in 4 workflow(s) with 4 failures and 4 successes.

**Debugging instructions (after clicking on the recent samples link):**
DO NOT ASSUME THINGS ARE OKAY IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_tensor_subclasses`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.


Test file path: `test_jit.py`

cc @EikanWang @jgong5 @wenzhe-nrv @sanchitintel @clee2000 @wdvr @chauhang @penguinwu @voznesenskym @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @jiayisunx @chenyang78 @kadeng @amjames @ezyang @gchanan @zou3519 @msaroufim @bdhirsh @anijain2305
Repository: rust
Issue: Test `polymorphic_recursion.rs` takes a long time to compile with a `debug-assertions=true` compiler
Labels: A-testsuite,T-compiler,A-mir-opt,A-contributor-roadblock,T-types

#120912 reported that `tests/mir-opt/inline/polymorphic_recursion.rs` became very slow after #120584. A workaround for that slowness was added by a hack in #120942.

However, the test is still very slow when the compiler is built with `[rust] debug-assertions=true`.

On my system (Apple M2 Pro):
- Before the original change, it was fast enough that I never noticed it being slow when running `x test mir-opt`.
- After the original change but before the hack, it appeared to hang indefinitely (though perhaps it was just running very very slowly).
- After the hack, it still takes about **45 seconds** to complete.

```rust
// skip-filecheck
// Make sure that the MIR inliner does not loop indefinitely on polymorphic recursion.
// compile-flags: --crate-type lib

// Randomize `def_path_hash` by defining them under a module with different names
macro_rules! emit {
    ($($m:ident)*) => {$(
        pub mod $m {
            pub trait Tr { type Next: Tr; }

            pub fn hoge<const N: usize, T: Tr>() {
                inner::<N, T>();
            }

            #[inline(always)]
            fn inner<const N: usize, T: Tr>()
            {
                inner::<N, T::Next>();
                inner::<N, T::Next>();
            }
        }
    )*};
}

// Increase the chance of triggering the bug
emit!(m00 m01 m02 m03 m04 m05 m06 m07 m08 m09 m10 m11 m12 m13 m14 m15 m16 m17 m18 m19);
```
Repository: excalidraw
Issue: Website embed whitelist request gsheets 
Labels: Embeddable

Hello, I would like to embed a google sheet into my whiteboard. Could someone edit the [whitelist](https://github.com/excalidraw/excalidraw/blob/5245276409b8d163c656c9d3a5e9028b8322a59b/packages/excalidraw/element/embeddable.ts#L48) to allow gsheet links? Thanks!
Repository: pytorch
Issue: Error on trying to run detectron2 on Mac M1 with device set to "mps" (Metal Performance Shaders)
Labels: triaged,module: mps

### 🐛 Describe the bug

I am trying to run detectron2 on Mac M1 with device set to "mps" (Metal Performance Shaders)

The problem is that every time I set up to mps the following error shows up:

Error: command buffer exited with error status.
	The Metal Performance Shaders operations encoded on it may not have completed.
	Error: 
	(null)
	Internal Error (0000000e:Internal Error)
	<AGXG13GFamilyCommandBuffer: 0x28bad31a0>
    label = <none> 
    device = <AGXG13GDevice: 0x14ed4ca00>
        name = Apple M1 
    commandQueue = <AGXG13GFamilyCommandQueue: 0x14fded000>
        label = <none> 
        device = <AGXG13GDevice: 0x14ed4ca00>
            name = Apple M1 
    retainedReferences = 1

Anyone else with the same problem? I believe there is currently an incompatibility of "mps" with detectron2. Because when you set to "cpu" it works normally, but it is cpu and therefore slower for training.

### Versions

Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 2606:50c0:8003::154, 2606:50c0:8001::154, 2606:50c0:8002::154, ...
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|2606:50c0:8003::154|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 22068 (22K) [text/plain]
Saving to: ‘collect_env.py’

collect_env.py      100%[===================>]  21.55K  --.-KB/s    in 0.001s  

2024-02-14 22:32:30 (20.7 MB/s) - ‘collect_env.py’ saved [22068/22068]

zsh: command not found: #
Collecting environment information...
PyTorch version: 2.2.0
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: macOS 14.2.1 (arm64)
GCC version: Could not collect
Clang version: 15.0.0 (clang-1500.1.0.2.5)
CMake version: Could not collect
Libc version: N/A

Python version: 3.10.13 | packaged by conda-forge | (main, Oct 26 2023, 18:09:17) [Clang 16.0.6 ] (64-bit runtime)
Python platform: macOS-14.2.1-arm64-arm-64bit
Is CUDA available: False
CUDA runtime version: No CUDA
CUDA_MODULE_LOADING set to: N/A
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
Apple M1

Versions of relevant libraries:
[pip3] mypy-extensions==1.0.0
[pip3] numpy==1.26.4
[pip3] torch==2.2.0
[pip3] torchaudio==2.2.0
[pip3] torchvision==0.17.0
[conda] numpy                     1.26.4          py310hd45542a_0    conda-forge
[conda] pytorch                   2.2.0                  py3.10_0    pytorch
[conda] torch                     2.2.0                    pypi_0    pypi
[conda] torchaudio                2.2.0                    pypi_0    pypi
[conda] torchvision               0.17.0                   pypi_0    pypi

cc @kulinseth @albanD @malfet @DenisVieriu97 @razarmehr
Repository: pytorch
Issue: Non core ATen ops are getting dispatched as it is instead of mapping/docmposing to other ATen ops.
Labels: triaged,module: dispatch

### 📚 The doc issue

We are observing few non core ATen ops are getting dispatched as it is without mapping/decomposed to other ATen ops (ex: aten._pdist_backward).
We are refereeing the document ( https://pytorch.org/docs/main/torch.compiler_ir.html )  for core ATen ops. Is this is the only place we need to look for core ATen ops or is there any other place we have to look for?

Versions of relevant libraries:
[pip3] numpy==1.26.4
[pip3] torch==2.1.1a0+git0d9f80e
[pip3] torch_tb_profiler==0.4.0
[pip3] torchaudio==2.1.0+6ea1133
[pip3] torchdata==0.7.0+c5f2204
[pip3] torchmetrics==1.2.1
[pip3] torchtext==0.16.0a0+4e255c9
[pip3] torchvision==0.16.0+fbb4cc5
[conda] Could not collect

### Suggest a potential alternative/fix

_No response_
Repository: vscode
Issue: RTL: WTF! Code is Reversed!
Labels: bug,editor-RTL

<!-- ⚠️⚠️ 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. -->

```
Version: 1.86.1 (user setup)
Commit: 31c37ee8f63491495ac49e43b8544550fbae4533
Date: 2024-02-07T09:08:20.941Z
Electron: 27.2.3
ElectronBuildId: 26495564
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: 11.8.172.18-electron.0
OS: Windows_NT x64 10.0.22621
```

The code:

```
content: "ویرایش"; /* Edit */
```

How it looks like:

![image](https://github.com/microsoft/vscode/assets/44144724/09040daa-f8a9-45b7-be39-1f924234d39e)

It's fine, don't add RTL support, but what the hell is this? You are breaking the defaults!

---

Update

This issue happens when this option is set to `true`:

```json
{
    "editor.fontLigatures": true,
}
```
Repository: vscode
Issue: VSCode start-up slow
Labels: info-needed,perf-startup

I disabled most of the plugins that I am not actively using, but start-up is still very slow.

[prof-RMo1xW0S.main.cpuprofile.txt](https://github.com/microsoft/vscode/files/14292016/prof-RMo1xW0S.main.cpuprofile.txt)
[prof-RMo1xW0S.renderer.cpuprofile.txt](https://github.com/microsoft/vscode/files/14292017/prof-RMo1xW0S.renderer.cpuprofile.txt)
Repository: PowerToys
Issue: Add "File History" Feature
Labels: Idea-New PowerToy,Needs-Triage

### Description of the new feature / enhancement

**This feature can backup all the files in the directory(s) which selected by the user and record the changements.**
<img width="742" alt="image" src="https://github.com/microsoft/PowerToys/assets/62378385/962cea6f-96ab-40ee-9944-334918acc007">
<img width="308" alt="image" src="https://github.com/microsoft/PowerToys/assets/62378385/479b9b4c-217c-43a5-a9bb-2234391bd11b">

### Scenario when this would be used?

This feature will be very practical in dealing with the following situations:

- Need to know the modification history of the file
- Missaved/deleted by mistake
- SMB. It can record the operation of shared folders and prevent accidental deletion. Note: Users need to be reminded that if this folder is a shared folder or it is isolated from other locations on the compute, this operation may back up harmful files (such as exe) uploaded from the outside to an unprotected folder.
- When writing papers or creating, one can understand their own thoughts by reviewing history.

### Supporting information

Rendering
<img width="742" alt="image" src="https://github.com/microsoft/PowerToys/assets/62378385/962cea6f-96ab-40ee-9944-334918acc007">
<img width="308" alt="image" src="https://github.com/microsoft/PowerToys/assets/62378385/479b9b4c-217c-43a5-a9bb-2234391bd11b">
Repository: tensorflow
Issue: Could not find device for node GenerateBoundingBoxProposals
Labels: type:bug,comp:ops,TF 2.15

### Issue type

Bug

### Have you reproduced the bug with TensorFlow Nightly?

Yes

### Source

source

### TensorFlow version

2.15.0

### Custom code

Yes

### OS platform and distribution

_No response_

### Mobile device

_No response_

### Python version

_No response_

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

When using tf.image.generate_bounding_box_proposals in CPU, it raises the following error: 

```
NotFoundError: Could not find device for node: {{node GenerateBoundingBoxProposals}} = GenerateBoundingBoxProposals[post_nms_topn=300]
All kernels registered for op GenerateBoundingBoxProposals:
  device='GPU'
 [Op:GenerateBoundingBoxProposals] name: 
```

### Standalone code to reproduce the issue

```shell
import tensorflow as tf

scores = tf.constant([[0.9, 0.8, 0.7], [0.6, 0.5, 0.4]])
bbox_deltas = tf.constant([[1, 1, 1, 1], [2, 2, 2, 2]])
image_info = tf.constant([100, 100, 1])
anchors = tf.constant([[10, 10, 20, 20], [30, 30, 40, 40], [50, 50, 60, 60]])

result = tf.image.generate_bounding_box_proposals(scores, bbox_deltas, image_info, anchors)

print(result)
```


### Relevant log output

_No response_
Repository: vscode
Issue: Folded file gets unfolded if the problem is removed in a opened folder
Labels: bug,error-list

Steps to reproduce:

- New untitled file 1 > Type `a\nb\bc\n`. Change lang to TS
- New untitled file 2 > Type `d\ne\bf\n`. Change lang to TS
- Open Problems view. Fold first untitled file. Select second problem from second untitled file
- Delete the second line from second untitled file
🐛 First file gets unfolder

Type: <b>Bug</b>

If you look at the gif the problems for the other file are folded and when I remove one problem in the current file the problems-view unfolds the other file and selects the first problem there.

In my opinion the problems for the other file should stay folded until all problems for the current file are gone. Currently this leads me to keep folding the problems for the other file over and over since I'm not done fixing the current file.

I did try this with extensions disabled too with the same result.

![Recording 2024-02-15 at 09 10 18](https://github.com/microsoft/vscode/assets/4050133/c1ad8ab0-38cf-423e-8afd-0b7553644431)

VS Code version: Code - Insiders 1.87.0-insider (Universal) (e587755905208e47725c5196539c4ca898255fe6, 2024-02-15T05:48:48.139Z)
OS version: Darwin arm64 23.3.0
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Apple M1 (8 x 24)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled|
|Load (avg)|4, 6, 10|
|Memory (System)|16.00GB (0.44GB free)|
|Process Argv|--crash-reporter-id 9ac6c7bc-b48e-47ef-abeb-49baab3cba45|
|Screen Reader|no|
|VM|0%|
</details><details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vsc_aacf:30263846
vscod805cf:30301675
vsaa593cf:30376535
py29gd2263:30784851
vscaat:30438846
c4g48928:30535728
a9j8j154:30646983
962ge761:30841072
pythongtdpath:30726887
welcomedialog:30812478
pythonidxpt:30768918
pythonnoceb:30776497
asynctok:30898717
dsvsc013:30777762
dsvsc014:30777825
dsvsc015:30821418
pythontestfixt:30866404
pythonregdiag2:30926734
pyreplss1:30879911
pythonmypyd1:30859725
pythoncet0:30859736
pythontbext0:30879054
accentitlementst:30870582
dsvsc016:30879898
dsvsc017:30880771
dsvsc018:30880772
pydisww2:30959801
cppperfnew:30963552
8082a590:30961435
b1063948:30943794
fegfb526:30952798
7j2b6412:30951517
bg6jg535:30946824
8f97e687:30959763
ccp2r3:30958153

```

</details>

<!-- generated by issue reporter -->
Repository: godot
Issue: How to understand what actually is causing shader compilation?
Labels: enhancement,discussion,documentation,topic:shaders

### Tested versions

- Reproducible in 3.5.3.stable.

### System information

Windows 11 - Godot v3.5.3.stable - GLES3 - Nvidia Geforce GT1030

### Issue description

```
Async. shader compiles: 8
Async. shader compiles: 7
Async. shader compiles: 6
Async. shader compiles: 5
Async. shader compiles: 4
Async. shader compiles: 3
Async. shader compiles: 2
Async. shader compiles: 4
Async. shader compiles: 3
Async. shader compiles: 2
Async. shader compiles: 1
Async. shader compiles: 3
Async. shader compiles: 2
Async. shader compiles: 1
Async. shader compiles: 0
```

So, it's been a long time i've been reading about shader compilation and for the most part i fixed it, however, it is still unclear what actually can cause the shader compilation. Maybe i missed something? Is there any way to see what actually is causing it (meshes, materials, particles, animated meshes, etc)? I couldn't find anything in docs, but, again, maybe i missed something?

### Steps to reproduce

1. Make a complex scene
2. Catch cases when shader compilation happens
3. Maybe stumble across cases when you are not sure what actually is happening

### Minimal reproduction project (MRP)

I would like to provide it later if needed