sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: kubernetes
Issue: Declarative defaults should handle cases where a field is feature-gated 
Labels: sig/api-machinery,kind/feature,area/code-generation,triage/accepted

Given a non-gated field, I can say `// +default=12345`, which will generate code like:

```
    if obj.Field == nil {
        var val int64 = 12345
        obj.Field = &val
    }
````

If I have a feature-gated field, I want the default value ONLY IF allowed by the gate.  For example:

pkg/apis/core/v1/defaults.go:
```
      if utilfeature.DefaultFeatureGate.Enabled(features.ImageVolume) && obj.Image != nil && obj.Image.PullPolicy == "" {
          // PullPolicy defaults to Always if :latest tag is specified, or IfNotPresent otherwise.
          _, tag, _, _ := parsers.ParseImageName(obj.Image.Reference)
          if tag == "latest" {
              obj.Image.PullPolicy = v1.PullAlways
          } else {
              obj.Image.PullPolicy = v1.PullIfNotPresent
          }
      }
```

It would be nice if I could say something like:
```
// +default=12345
// +featureGate=MyGateName
Field *int64
```

And have the generator produce:

```
    if utilfeature.DefaultFeatureGate.Enabled(features.MyGateName) && obj.Field == nil {
        var val int64 = 12345
        obj.Field = &val
    }
````
 
xref https://github.com/kubernetes/kubernetes/issues/120847

cc @jpbetz
Repository: godot
Issue: 2D HDR makes scenes significantly darker
Labels: bug,topic:rendering,topic:2d

### Tested versions

Godot 4.3 Stable

### System information

Windows 10 x64, RTX 3060 Ti, Ryzen 5600x

### Issue description

Enabling “HDR” makes everything (and especially HDRi) significantly darker. I've tried several methods to locate any relevant side of the issue (physical light units, auto exposure, etc). Nothing changes that, it's just right away darker. No screen shaders are applied. It also compresses the image significantly (almost making it look like 6-bit)

![image](https://github.com/user-attachments/assets/21994fcb-b192-4fdf-8ff8-ad12d4b0d23c)


### Steps to reproduce

Select 3D scene
Enable 2D HDR

### Minimal reproduction project (MRP)

N/A
Repository: vscode
Issue: Pytest Test Discovery Issue in Multi-root Workspace with Folder-specific Settings
Labels: bug,workbench-multiroot,testing,python

I'm encountering an issue with Pytest test discovery in a multi-root workspace setup in Visual Studio Code. My workspace includes two folders: api and authorizer. Each folder contains its own set of tests within a tests subdirectory.

For each folder, I have a settings.json file located in the .vscode directory with the following configuration:

{
    "python.testing.pytestArgs": [
        "tests"
    ],
    "python.testing.unittestEnabled": false,
    "python.testing.pytestEnabled": true,
    "python.envFile": "${workspaceFolder}/tests/dev.env"
}

Despite this setup, when I open the Testing tab in VSCode, the paths to the test files are incorrect. The tests directory is missing from the paths, resulting in errors such as:

CRIT pytest at 'authorizer': Execution of the test "....../authorizer/application/test_authorizer_token.py" failed: Error: Process exited with code 4: ERROR: file or directory not found: ....../authorizer/application/test_authorizer_token.py

The correct path should be:
....../authorizer/tests/application/test_authorizer_token.py

I've ensured that each folder has its own .vscode/settings.json with the correct pytestArgs, and I've tried using absolute paths as well. All extensions and VSCode itself are up to date.

Has anyone experienced a similar issue or have any suggestions on how to resolve this path resolution problem?

Thank you!

![Image](https://github.com/user-attachments/assets/c00978b3-635a-4374-b030-bf6c17c8e35d)
Repository: tauri
Issue: [bug] Different Path for APK and AAB file after build
Labels: type: feature request,priority: 3 low

### Different Filepath for android Build

![image](https://github.com/user-attachments/assets/c9028502-2d1a-4a57-839d-fa88ac9d5ba2)


### Reproduction

https://github.com/Algostract/portfolio-shirsendu


### Expected behavior

To have one folder path either universal/release or universalRelease

### Full `tauri info` output

```text
[✔] Environment
    - OS: Windows 10.0.22631 x86_64 (X64)
    ✔ WebView2: 130.0.2849.56
    ✔ MSVC: Visual Studio Build Tools 2022
    ✔ rustc: 1.81.0 (eeb90cda1 2024-09-04)
    ✔ cargo: 1.81.0 (2dbb1af80 2024-08-20)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
    - node: 20.18.0
    - pnpm: 9.12.3
    - npm: 10.8.2
    - deno: deno 2.0.4

[-] Packages
    - tauri 🦀: 2.0.6
    - tauri-build 🦀: 2.0.2
    - wry 🦀: 0.46.3
    - tao 🦀: 0.30.3
    - @tauri-apps/api : 2.0.3
    - @tauri-apps/cli : 2.0.5

[-] Plugins
    - tauri-plugin-log 🦀: 2.0.1
    - @tauri-apps/plugin-log : not installed!

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:3000/
    - framework: Vue.js (Nuxt)
    - bundler: Vite
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: TypeScript
Issue: Destructuring into an empty object vs an object with existing properties yields different results
Labels: Bug,Help Wanted

### 🔎 Search Terms

"destructuring", "record"

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ.


### ⏯ Playground Link

https://www.typescriptlang.org/play/?ts=5.6.3#code/MYewdgzgLgBATgU1HAJgdQJZQBYGUpwZgDmEAXDAEpIioA80hJANDI0cQHwwC8MA3gF8A3AChRCAB4AHWrFCRYiZOizYAcgFcAtgCMEcclRr12LGGB3643Pv1EwYUggEMACnBDSDUAJ4UABmYHGAA6cOVaVRx8JlJgkSA

### 💻 Code

This raises a type error:

```ts
const recordWithStrings: Record<string, string> = {};

export const recordWithNumbers: Record<string, number> = {
  ...recordWithStrings,
};
```

and this doesn't:

```ts
const recordWithStrings: Record<string, string> = {};

export const recordWithNumbers: Record<string, number> = {
  extraProperty: 0,
  ...recordWithStrings,
};
```

Is there a sound reason for that?

### 🙁 Actual behavior

The 2nd example doesn't raise a type error.

### 🙂 Expected behavior

The 2nd example should raise a type error.

### Additional information about the issue

_No response_
Repository: bitcoin
Issue: CI: Improve documentation around replicating CI locally
Labels: Brainstorming,Docs,Build system,Tests

I've received some feedback that replicating CI jobs locally isn't straightforward. Perhaps the documentation can be improved in this area?

@maflcko I understand you had some improvements in mind? Happy to also work on this.
Repository: bitcoin
Issue: CI: Make failure message easier to spot
Labels: Brainstorming,Tests

Sometimes during a CI failure the actual error message can be buried in a wall of log output and not immediately clear. Ideally it should be obvious why a CI job has failed.

CC @maflcko
Repository: transformers
Issue: VLMs Processors are not fully consistent in the inputs formats they accept
Labels: bug,Processing

### Summary of accepted inputs for image-text-to-text-models
| Model | Uses Image Tokens | Accepts URL | Accepts PIL | Accepts Path | Accepts Non-Nested Batched Images (one per text) | Accepts Nested Images (one per text) | Accepts Nested Images (Multiple images per text, same number for each text) | Accepts Nested Images (Multiple images per text, different number for each text) |
|---|---|---|---|---|---|---|---|---|
| Pix2Struct | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ |
| BLIP | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ |
| Donut | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ |
| UDOP | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ |
| GIT | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ |
| KOSMOS-2 | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ |
| Idefics | ❌ | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ |
| FUYU | ❌ | ❌ | ✅ | ❌ | ✅ | ✅ | ❌ | ❌ |
| Llava | ✅ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ |
| VipLlava | ✅ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ |
| BLIP2 | ✅ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ |
| Qwen2-VL | ✅ | ❌ | ✅ | ❌ | ✅* crash when padding set to True | ❌ | ✅ | ✅ |
| Chameleon | ✅ | ❌ | ✅ | ❌ | ❌* works when padding manually set to True | ✅ | ✅ | ✅ |
| Pixtral | ✅ | ✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ❌ |
| Paligemma | ✅ | ❌ | ✅ | ❌ | ✅ | ✅ | ✅ | ✅ |
| Llava-Next | ✅ | ❌ | ✅ | ❌ | ✅ | ✅ | ✅ | ✅ |
| LLaVA-OneVision | ✅ | ❌ | ✅ | ❌ | ✅ | ✅ | ✅ | ✅ |
| Mllama | ✅ | ❌ | ✅ | ❌ | ✅ | ✅ | ✅ | ✅ |
| InstructBLIP | ✅ | ❌ | ✅ | ❌ | ✅ | ✅ | ✅ | ✅ |
| Idefics2 | ✅ | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ✅ |
| Idefics3 | ✅ | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ✅ |

### Reproduction

For instance, with these inputs:
```python
import requests
from PIL import Image

image_ny = "https://cdn.britannica.com/61/93061-050-99147DCE/Statue-of-Liberty-Island-New-York-Bay.jpg"
image_chicago = "https://cdn.britannica.com/59/94459-050-DBA42467/Skyline-Chicago.jpg"
url_pokemon = "https://huggingface.co/datasets/sayakpaul/sample-datasets/resolve/main/pokemon.png"

image_pokemon = Image.open(requests.get(url_pokemon, stream=True).raw)
text_batched_image_tokens = [
    "<image> <image> Are these the same cities? If not what cities are these?",
    "<image> Describe what you see in this image. I see",
]

```

This will crash at the processor level:

```python
from transformers import pipeline

pipe = pipeline(task="image-text-to-text", model="llava-hf/llava-interleave-qwen-0.5b-hf")

pipe(
    images=[[image_ny, image_chicago], [image_pokemon]],
    text=text_batched_image_tokens,
)

```

But this will work:

```python
from transformers import pipeline

pipe = pipeline(task="image-text-to-text", model="llava-hf/llava-onevision-qwen2-0.5b-ov-hf")

pipe(
    images=[[image_ny, image_chicago], [image_pokemon]],
    text=text_batched_image_tokens,
)
```

### Expected behavior

Except for model-specific limitations or features, vlms used for similar tasks should accept a similar set of inputs format
Repository: rust
Issue: Tracking issue for release notes of #131477: macOS: Always pass SDK root when linking with `cc`, and pass it via `SDKROOT` env var
Labels: T-compiler,relnotes,O-apple,relnotes-tracking-issue


This issue tracks the release notes text for #131477.

### Steps

- [ ] Proposed text is drafted by PR author (or team) making the noteworthy change.
- [ ] Issue is nominated for release team review of clarity for wider audience.
- [ ] Release team includes text in release notes/blog posts.

### Release notes text

The responsible team for the underlying change should edit this section to replace the automatically generated link with a succinct description of what changed, drawing upon text proposed by the author (either in discussion or through direct editing).

````markdown
# Category (e.g. Language, Compiler, Libraries, Compatibility notes, ...)
- [macOS: Always pass SDK root when linking with `cc`, and pass it via `SDKROOT` env var](https://github.com/rust-lang/rust/pull/131477)
````

> [!TIP]
> Use the [previous releases](https://doc.rust-lang.org/nightly/releases.html) categories to help choose which one(s) to use.
> The category will be de-duplicated with all the other ones by the release team.
>
> *More than one section can be included if needed.*

### Release blog section

If the change is notable enough for inclusion in the blog post, the responsible team should add content to this section.
*Otherwise leave it empty.*

````markdown
````

cc @madsmtm, @nnethercote -- origin issue/PR authors and assignees for starting to draft text
Repository: flutter
Issue: [impeller] opengles golden tests don't have antialiasing
Labels: P1,e: impeller,team-engine,triaged-engine,e: opengl

seen in dcc8c65eb3d1d43decb52d276b7f29390ea67c9d
test: impeller_Play_AiksTest_FilledEllipsesRenderCorrectly

## metal
![impeller_Play_AiksTest_FilledEllipsesRenderCorrectly_Metal](https://github.com/user-attachments/assets/ddc694d3-d8d2-4aad-b7ce-ea16790825cd)


## opengles
![impeller_Play_AiksTest_FilledEllipsesRenderCorrectly_OpenGLES](https://github.com/user-attachments/assets/7fe64c88-2abe-4428-a536-592c32da08a2)
Repository: flutter
Issue: [impeller] AiksTest_ColorFilterAdvancedBlend is blurry on opengles
Labels: P2,e: impeller,team-engine,triaged-engine,e: opengl

seen in dcc8c65eb3d1d43decb52d276b7f29390ea67c9d
test: AiksTest_ColorFilterAdvancedBlend

Look at the details in the image of the town.  They are more crisp on vulkan and metal.

## metal
![impeller_Play_AiksTest_ColorFilterAdvancedBlend_Metal](https://github.com/user-attachments/assets/2daa7c5c-cb71-44d6-9a4c-883db35124ae)

## opengles
![impeller_Play_AiksTest_ColorFilterAdvancedBlend_OpenGLES](https://github.com/user-attachments/assets/e9ca760e-2806-4069-b66b-62806883dc95)
Repository: flutter
Issue: [impeller] AiksTest_ColorMatrixFilterSubpassCollapseOptimization missing outline on opengles
Labels: P2,e: impeller,team-engine,triaged-engine,e: opengl

seen in dcc8c65eb3d1d43decb52d276b7f29390ea67c9d
test: AiksTest_ColorMatrixFilterSubpassCollapseOptimization

## metal
![impeller_Play_AiksTest_ColorMatrixFilterSubpassCollapseOptimization_Metal](https://github.com/user-attachments/assets/1caaf8c7-ed4f-4e91-8f8b-7ec9914e0dce)



## opengles
![impeller_Play_AiksTest_ColorMatrixFilterSubpassCollapseOptimization_OpenGLES](https://github.com/user-attachments/assets/a50b5100-6d7e-44a0-97b1-b6f7b97bff4d)
Repository: pytorch
Issue: Add 'no_type_conversion' flag to register_buffer()
Labels: module: onnx,triaged

### 🚀 The feature, motivation and pitch

Some modules need to keep float32/float64/float16 constant Tensors (registered as buffers) unaffected by .to(dtype=float16, etc) operations.  The most straightforward way to implement that is  to add a flag to register_buffer that would mark it as guarded from type conversion (no assumptions on underlying implementation).

### Alternatives

Currently, the only consistent way to keep those constants from being flipped on module type conversion is to declare those Tensors as matching length integers (int32 for float32 etc.) and use cast. Overriding a single module to() does not work as the conversion does not honor module hierarchy so that override would be ignored if to() is invoked by the containing Module. 

Using the cast works fine for eager execution, but introduces issues with ONNX export ( see https://github.com/pytorch/pytorch/issues/126921)


### Additional context

_No response_

cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki
Repository: flutter
Issue: [impeller] CanRenderSweepGradientManyColorsRepeat has artifact on opengles
Labels: P2,e: impeller,team-engine,triaged-engine,e: opengl

seen in dcc8c65eb3d1d43decb52d276b7f29390ea67c9d
test: AiksTest_CanRenderSweepGradientManyColorsRepeat

The artifact is on the north east line radiating from the center of the gradient.

## metal
![impeller_Play_AiksTest_CanRenderSweepGradientManyColorsRepeat_Metal](https://github.com/user-attachments/assets/62a50283-2a66-4beb-a8f6-0af1366cbe61)


## opengles
![impeller_Play_AiksTest_CanRenderSweepGradientManyColorsRepeat_OpenGLES](https://github.com/user-attachments/assets/30ffce94-27ab-4292-8b7e-db68c0dd322c)
Repository: flutter
Issue: Impeller golden tests (and others?) require developers to manually update the list of goldens
Labels: team,c: proposal,P2,c: tech-debt,team-engine,triaged-engine

There are a couple of golden mechanisms in the engine that have lists of the expected golden file outputs. At least one of these was created when we discovered that sometimes a golden file might be missing and therefore not checked. This manual check of which files were generated solves that issue, but it seems like we should be able to rely on the golden tests to throw an exception or expectation failure which fails the test if a golden file isn't written (for whatever reason).
Repository: flutter
Issue: ci/format.sh should verify that Impeller golden test list is sorted
Labels: a: tests,engine,c: proposal,P3,e: impeller,team-engine,triaged-engine

Part of the Impeller golden test suite is to verify if the list of generated goldens is complete and it uses the `impeller_golden_tests_output.txt` file to double check the list.

Unfortunately, that check will also fail if the list is complete, but not sorted correctly. We should have `ci/format.sh` check this condition to help developers head these errors off at an early pass.
Repository: flutter
Issue: building `Profile-ios-Flutter.xcframework` took 40m
Labels: team-infra,P2,c: flake,triaged-infra

Expected time is 16s.

## problem example
https://ci.chromium.org/ui/p/flutter/builders/try/Mac%20mac_ios_engine/36781/overview

## positive example
https://ci.chromium.org/ui/p/flutter/builders/try/Mac%20mac_ios_engine/36735/overview
Repository: flutter
Issue: Implement Zones at the framework level (e.g. as a Widget)
Labels: c: new feature,framework,c: proposal,P3,team-framework,triaged-framework

### Use case

Allow coarse-grained management of async requests and dependency injection

Example 1: A user logs in, some widgets create some async requests and other local state, and the user logs out. How do we guarantee that all authenticated async requests and streams are canceled or at least will not interfere with the next user?

Example 2: We can use a top-level error handler to manage async errors at a global level, and asyncGuard https://github.com/flutter/flutter/blob/1050959d198bf6843ab6ec256fa4f58fc7009c57/packages/flutter_tools/lib/src/base/async_guard.dart#L11 on every single await to manage them at a local level, but there is no way to composably manage errors at the subtree level.

Example 3: Flutter DI usually uses the BuildContext for scope, but in complex apps we can see that BuildContexts are not exactly the right abstraction for this purpose, for example for ContextActions whose `invoke` has a nullable BuildContext (https://api.flutter.dev/flutter/widgets/ContextAction/invoke.html), or for example running some asynchronous work before or after navigating away from a screen when a user presses a button or dismisses a Dismissible. The direction of newer frameworks is often to introduce codegen, magical APIs and globals to manage services separately from widget trees. https://pub.dev/packages/scoped_deps shows how to do very simple DI with zones in simple Dart apps, but it does not work in a widget tree context. Nested zones could achieve dynamic scoping while decoupling from small widget lifecycles.

### Proposal

Integrate a Zone() widget into the foundational libraries, such that all the framework's work of a child of a Zone(Widget) takes place in the affiliated (Dart) Zone. 

For example, Inherited{Widget/Element} would need to look up the correct zone for its dependents and ensure that their didChangeDependencies() were called in the right zone.
Repository: flutter
Issue: Investigate whether Web can listen to "pointermove" events on `_viewTarget`
Labels: engine,platform-web,a: mouse,P2,team-web,triaged-web

Since https://github.com/flutter/engine/pull/38477, Web listens to "pointermove" events on `_globalTarget` instead of the standard `_viewTarget` because of the default event capturing behaviors. However, the default web capture behavior might be configurable. We might want to revisit it and possibly simplify the code.

This is an issue for a TODO.

See also: https://github.com/flutter/engine/pull/56075#discussion_r1825222209
Repository: tensorflow
Issue: `tf.linalg.lstsq` producing outputs with large inconsistencies between CPU and GPU with `float32` tensors
Labels: type:bug,comp:ops,TF 2.18

### Issue type

Bug

### Have you reproduced the bug with TensorFlow Nightly?

No

### Source

source

### TensorFlow version

2.18.0

### Custom code

Yes

### OS platform and distribution

Linux Ubuntu 20.04

### Mobile device

_No response_

### Python version

3.10

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

12.3

### GPU model and memory

_No response_

### Current behavior?

Passing tensors of `float32` to 'tf.linalg.lstsq' is producing very different output from CPU and GPU.

### Standalone code to reproduce the issue
[colab](https://colab.research.google.com/drive/1Fyh3HQs39NhGlOLEdzpqPKVkznBe6Fe9?usp=sharing)
```shell
import tensorflow as tf
import numpy as np

A = tf.constant([[[[0.37454012, 0.9507143, 0.7319939, 0.5986585, 0.15601864], [0.15599452, 0.05808361, 0.8661761, 0.601115, 0.7080726,], [0.02058449, 0.96990985, 0.83244264,
                0.21233912, 0.18182497], [0.1834045, 0.30424225, 0.52475643, 0.43194503, 0.29122913], [0.6118529, 0.13949387, 0.29214466, 0.36636186, 0.45606998]]]], dtype=tf.float32)

B = tf.constant([[[[0.59241456, 0.04645041], [0.94888556, 0.965632,], [0.684233, 0.4401525,], [
                0.9093204, 0.25877997], [0.54671025, 0.18485446]]]], dtype=tf.float32)

with tf.device("/gpu:0"):
    output_gpu = tf.linalg.lstsq(A, B)
    
with tf.device( "/cpu:0"):
    output_cpu = tf.linalg.lstsq(A, B)

np.testing.assert_allclose(output_cpu, output_gpu.cpu(), atol=100) # AssertionError
```


### Relevant log output

```shell
AssertionError: 
Not equal to tolerance rtol=1e-07, atol=100

Mismatched elements: 2 / 10 (20%)
Max absolute difference: 112.95715
Max relative difference: 0.2963447
 x: array([[[[-170.69518 ,   28.379017],
         [ 164.85085 ,  -28.04222 ],
         [-273.4264  ,   46.952198],...
 y: array([[[[-241.07059 ,   40.25023 ],
         [ 232.80626 ,  -39.505226],
         [-386.38354 ,   66.00629 ],...
```
Repository: pytorch
Issue: CPU support for FlexAttention
Labels: triaged,oncall: pt2,module: higher order operators,oncall: cpu inductor,module: pt2-dispatcher,module: flex attention

# Add CPU Compile Support for Flex Attention

There are two implementations of Flex Attention. An unfused Eager Mode implementation that works on most device and, under torch.compile,  Inductor will lower to a Triton template. This Triton template is only supported on CUDA and ROCM devices. We currently don't have any support for CPU backends. 

We can either update the lowering to dispatch to a fused  CPU implementation or we can look to support this via [Triton-CPU](https://github.com/triton-lang/triton-cpu)

cc @ezyang @chauhang @penguinwu @zou3519 @ydwu4 @bdhirsh @yf225 @Chillee @yanboliang @BoyuanFeng
Repository: pytorch
Issue: Graph break due to unsupported builtin torch._C._distributed_c10d.PyCapsule._broadcast_coalesced
Labels: oncall: distributed,triaged,module: ddp,oncall: pt2,module: dynamo,module: graph breaks,pt2d-triage-nov2024

### 🐛 Describe the bug

Compiling a whole ddp wrapped model I got this graph break

### Error logs

```python 
/opt/conda/lib/python3.11/site-packages/torch/_dynamo/variables/functions.py:743: UserWarning: Graph break due to unsupported builtin torch._C._distributed_c10d.PyCapsule._broadcast_coalesced. This function is either a Python builtin (e.g. _warnings.warn) or a third-party C/C++ Python extension (perhaps created with pybind). If it is a Python builtin, please file an issue on GitHub so the PyTorch team can add support for it and see the next case for a workaround. If it is a third-party C/C++ Python extension, please either wrap it into a PyTorch-understood custom operator (see https://pytorch.org/tutorials/advanced/custom_ops_landing_page.html for more details) or, if it is traceable, use torch.compiler.allow_in_graph.
```

### Minified repro

_No response_

### Versions

nightly

cc @H-Huang @awgu @kwen2501 @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @c-p-i-o @ezyang @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @amjames