sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: DISABLED test_mm_triton_kernel_benchmark (__main__.TestKernelBenchmark)
Labels: triaged,module: flaky-tests,skipped,module: inductor

Platforms: linux, slow

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

Over the past 3 hours, it has been determined flaky in 6 workflow(s) with 18 failures and 6 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_mm_triton_kernel_benchmark`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.


Test file path: `inductor/test_kernel_benchmark.py`

cc @clee2000 @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @peterbell10 @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @aakhundov @ColinPeppler
Repository: flutter
Issue: Smarter registration of plugin dependencies.
Labels: tool,package,a: build,P3,a: plugins,team-tool,triaged-tool

### Use case

In the current implementation of our plugin-related tooling, all compatible plugin dependencies of a plugin are added to the generated plugin registrar of the platform, regardless of the plugin itself actually supports the target platform.

A concrete example:

if I add `firebase_crashlytics` to my pubspec (this is only compatible Android/iOS/MacOS) and compile for the web, our build system will add `firebase_core` to the plugin web registrant (because it *is* web compatible), but will never add `crashlytics` (which is *not* web compatible), hence making all of `firebase_core` unneeded.

What is worse is that the web plugin registrant generates Dart code that will always call the `registerWith` method of the unused plugin(s), so at least parts of it will fail to tree-shake, increasing the binary size ("how much?" depends on the structure of the unnecessary plugins).

Another problem on the web is that this impedes compiling to `--wasm`, **even if** the App code itself has been written correctly (conditional imports, etc...) to never call the plugin code paths when targeting the web.

### Proposal

Modify the generation of the `plugin_registrar` (at least on the web) to **only include dependencies of the plugins that will be `registerWith` for that platform**. Don't include all its plugin dependencies blindly!
Repository: godot
Issue: TextEdit Node Bug - setting node.text = node.text in a signal call node.connect('text_changed', my_func) reverses printout of node.text
Labels: documentation,topic:gui

### Tested versions

4.2.1.stable

### System information

Godot v4.2.1.stable - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3050 6GB Laptop GPU () - 12th Gen Intel(R) Core(TM) i7-12650H (16 Threads)

### Issue description

For a textedit node I am trying to strip newline characters and limit the length to 15 characters (maybe i'll do a feature request for this). While trying to achieve this I noticed that the text always prints backwards. In the MRP I would expect if you set a variable to itself it would not change, however when you run the project you will observe that the text is reversed. 

### Steps to reproduce

Create a new project using v4.2.1.stable. Add the script in MRP. Run the project and type 'hello' into the textedit. it will read at 'olleh'

### Minimal reproduction project (MRP)

extends Node2D

var textbox : TextEdit = TextEdit.new()

func _ready():
	
	textbox.size = Vector2(200, 50)
	add_child(textbox)
	textbox.connect('text_changed', clip_text)
	
func clip_text() -> void:
	textbox.text = textbox.text
Repository: pytorch
Issue: Unify TEST_WITH_TORCHDYNAMO and PYTORCH_TEST_WITH_DYNAMO
Labels: triaged,module: testing

People are confused by this. I don't know why they're different. We should unify on one of them (PYTORCH_TEST_WITH_DYNAMO).
Repository: flutter
Issue: add matchContent and matchParent attributes to all widgets(Widget base class)
Labels: c: new feature,framework,f: material design,c: proposal,P3,team-design,triaged-design

### Use case

TabBarView is expanded to fill available space, but it can not have a natural size to fit content size.  All widgets need to have attributes matchContent and matchParent like Android does.

### Proposal

It applies to all widgets, and so it needs to be done by flutter directly.
Repository: PowerToys
Issue: Always on Top focus getting stolen by "Replace or Skip Files" when copying files.
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

v0.77.0

### Installation method

PowerToys auto-update, Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

Always on Top

### Steps to reproduce

copy - paste large / multiple files.

### ✔️ Expected Behavior

Always on Top would not allow the "Replace or Skip Files" dialog to take control of the keyboard while typing.

### ❌ Actual Behavior

focus would be swapped to the "Replace or Skip Files" dialog asking "Replace the files in the destination...", "Skip these files", "Let me decide for each file".
this has led to overwriting some files that I did not want.

### Other Software

_No response_
Repository: vscode
Issue: Refactor Indent Detection to set `indentSize` to `auto` rather than `tabSize`
Labels: debt,editor-indent-detection

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

I can tell that VSCode historically used `tabSize` and no `indentSize`. `indentSize` is a relatively new concept ((still) incompletely) introduced in #155450, but Indent Detection (and possibly other features as well) is still in the past and not migrated to use `indentSize` (such as #193811). Problems arise with this inconsistency, such as
* #199630
  (With a whopping (0) upvotes, this bug report will soon get archived as a not-planned feature. At least all but the 2nd bullet point would surface when #5394 gets attention.)
* #200368
  solving #199791 by working the problem around with a new attribute `originalIndentSize` (and merged with no discussion).
* and possibly more

Request: Finish this mess up and migrate Indent Detection from `tabSize: 'auto'` to `indentSize: 'auto'`.

Background: I indent with spaces, yes, but I like my tabs extra long for, well, `tab`ulation, that’s what ‘tab’ stands for.

(Really, if `indentSize` is still half-baked, why is it in production (stable versions) already?)
https://github.com/microsoft/vscode/blob/8b3775030ed1a69b13e4f4c628c612102e30a681/src/vs/editor/common/model/textModel.ts#L678
Repository: pytorch
Issue: DISABLED test_comprehensive_nn_functional_nll_loss_cuda_float64 (__main__.TestDecompCUDA)
Labels: triaged,module: flaky-tests,skipped,module: decompositions

Platforms: rocm, win, windows



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

Over the past 3 hours, it has been determined flaky in 2 workflow(s) with 2 failures and 2 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_comprehensive_nn_functional_nll_loss_cuda_float64`
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_decomp.py`

cc @jeffdaily @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang @clee2000 @SherlockNoMad
Repository: opencv
Issue: [ERROR:0@0.391] global obsensor_uvc_stream_channel.cpp:159 cv::obsensor::getStreamChannelGroup Camera index out of range.... THIS IS THE ERROR IM FACING WHAT SHOULD I DO TO SOLVE IT
Labels: invalid

<!--
If you have a question rather than reporting a bug please go to https://forum.opencv.org where you get much faster responses.
If you need further assistance please read [How To Contribute](https://github.com/opencv/opencv/wiki/How_to_contribute).

This is a template helping you to create an issue which can be processed as quickly as possible. This is the bug reporting section for the OpenCV library.
-->

##### System information (version)
<!-- Example
- OpenCV => 4.2
- Operating System / Platform => Windows 64 Bit
- Compiler => Visual Studio 2017
-->

- OpenCV => :grey_question:
- Operating System / Platform => :grey_question:
- Compiler => :grey_question:

##### Detailed description

<!-- your description -->

##### Steps to reproduce

<!-- to add code example fence it with triple backticks and optional file extension
    ```.cpp
    // C++ code example
    ```
 or attach as .txt or .zip file
-->

##### Issue submission checklist

 - [ ] I report the issue, it's not a question
   <!--
   OpenCV team works with forum.opencv.org, Stack Overflow and other communities
   to discuss problems. Tickets with questions without a real issue statement will be
   closed.
   -->
 - [ ] I checked the problem with documentation, FAQ, open issues,
       forum.opencv.org, Stack Overflow, etc and have not found any solution
   <!--
   Places to check:
   * OpenCV documentation: https://docs.opencv.org
   * FAQ page: https://github.com/opencv/opencv/wiki/FAQ
   * OpenCV forum: https://forum.opencv.org
   * OpenCV issue tracker: https://github.com/opencv/opencv/issues?q=is%3Aissue
   * Stack Overflow branch: https://stackoverflow.com/questions/tagged/opencv
   -->
 - [ ] I updated to the latest OpenCV version and the issue is still there
   <!--
   master branch for OpenCV 4.x and 3.4 branch for OpenCV 3.x releases.
   OpenCV team supports only the latest release for each branch.
   The ticket is closed if the problem is not reproduced with the modern version.
   -->
 - [ ] There is reproducer code and related data files: videos, images, onnx, etc
   <!--
   The best reproducer -- test case for OpenCV that we can add to the library.
   Recommendations for media files and binary files:
   * Try to reproduce the issue with images and videos in opencv_extra repository
     to reduce attachment size
   * Use PNG for images, if you report some CV related bug, but not image reader
     issue
   * Attach the image as an archive to the ticket, if you report some reader issue.
     Image hosting services compress images and it breaks the repro code.
   * Provide ONNX file for some public model or ONNX file with random weights,
     if you report ONNX parsing or handling issue. Architecture details diagram
     from netron tool can be very useful too. See https://lutzroeder.github.io/netron/
   -->
Repository: pytorch
Issue: Tests aren't cleaning up state in test_optim.py 
Labels: module: optimizer,module: tests,triaged

### 🐛 Describe the bug

If you run the whole optim test suite, it appears that the default torch data type is mutated to be torch.float64. 
For example, if you run `python test/test_optim.py -k test_state_dict_deterministic_RAdam_cuda_float32` by itself, the test will pass. However if you run python test/test_optim.py -k RAdam (and run multiple tests) the above singled out test will fail. This is on the branch `mlazos/radam`

### Versions

N/A

cc @vincentqb @jbschlosser @albanD @janeyx99 @crcrpar @mruberry @ZainRizvi
Repository: PowerToys
Issue: Power Rename inprovements?
Labels: Resolution-Helped User

### Description of the new feature / enhancement

Is it possible add to Power Rename this features?
1- add an extension to a selected files (I came from mac os where extension isn't so important, so I have many files to add the extension to work on windows)
2- add the possibility to delete and/or add characters to the beginning or end of the name (e.g. remove the first 5 characters of the name)

### Scenario when this would be used?

Coming from macOs some files don't need extension to work.
When i have to rename files from music library (or other similar scenario) where automatically the used program add track and album number to the file.

### Supporting information

I have no other information.
Thanks for the attention
Repository: transformers
Issue: Load an EncoderDecoderModel as AutoModel
Labels: Feature request

### System Info

- `transformers` version: 4.35.0
- Platform: Linux-5.15.0-91-lowlatency-x86_64-with-glibc2.35
- Python version: 3.10.12
- Huggingface_hub version: 0.17.3
- Safetensors version: 0.4.0
- Accelerate version: 0.24.1
- Accelerate config: 	not found
- PyTorch version (GPU?): 2.1.2+cu121 (False)
- Tensorflow version (GPU?): 2.11.0 (False)
- Flax version (CPU?/GPU?/TPU?): not installed (NA)
- Jax version: not installed
- JaxLib version: not installed
- Using GPU in script?: no
- Using distributed or parallel set-up in script?: no

### Who can help?

@ArthurZucker and @younesbelkada

### Information

- [X] The official example scripts
- [ ] My own modified scripts

### Tasks

- [ ] An officially supported task in the `examples` folder (such as GLUE/SQuAD, ...)
- [ ] My own task or dataset (give details below)

### Reproduction

from transformers import AutoTokenizer, AutoModel

tokenizer = AutoTokenizer.from_pretrained("Bachstelze/instructionRoberta-base")
model = AutoModel.from_pretrained("Bachstelze/instructionRoberta-base", output_attentions=True)

### Expected behavior

Load the EncoderDecoderModel as AutoModel. "BertGenerationConfig" is supported, though this seems outdated.
Repository: rust
Issue: What is the behavior of a place-to-value/reference conversion of a variant place?
Labels: T-opsem

MIR in principle can represent code like this (but custom MIR currently cannot):
```rs
fn enum_shenanigans(_1: S) -> () {
    let mut _0: ();
    let mut _2: ??;
    let mut _3: ??;

    bb0: {
        _2 = (_1 as variant#0);
        _3 = &raw (_1 as variant#0);
        return;
    }
}
```
I think things would explode in all sorts of ways if such MIR was fed to Miri: enum variants [can have ABIs](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=ac760e7763768f57af8554f670615630) that are entirely different from the enum they are contained in, so the projection can produce `ImmTy` that are incoherent. Currently this works because it seems to only affect enum variants without fields / uninhabited variants (but maybe I just haven't found the right example yet), and rustc only generates variant projections that are immediately followed by field projections.

But this is not very satisfying. We have an invariant (an `Immediate::Scalar` must have `Scalar` type, and similar for `ScalarPair`), and that invariant is blatantly violated by valid MIR -- or at least MIR that does not break any documented rule I am aware of. It's also unclear what code like the above should even mean: given that enum variants have no type, what should the type of _2 and _3 be?

I can think of two proper solutions here:
- Instead of a separate Variant projection, have a combined "Variant+Field" projection for accessing enum fields.
- Give enum variants a proper type, and to ensure that downcasts can't go from Scalar to non-Scalar ABI. The fact that downcast places do not have a proper type has already caused me plenty of confusion and pain so this would be a good change to do anyway IMO, even if we don't expose those types to the user. (One day we might want to expose them as well, but that's not the goal of this issue.)

Cc @oli-obk @JakobDegen @tmiasko @cjgillot
Repository: pytorch
Issue: Torch + CUDA installation
Labels: module: cuda,triaged

### 🐛 Describe the bug

If CUDA, torch, graphic card version, etc. don't match up it can the case `torch.cuda.is_available()` but this not means CUDA works as expected. I found I also needed to test some simple CUDA math such as:

```
t = torch.zeros((1000,)).to('cuda')
t2 = t*t
```

to get additional verification and make the install work.

I would suggest adding such a minimal test either to the getting started guide or maybe even inside the cuda.is_available().

### Versions

Various invalid combinations of torch + cuda + python + OS versions.

cc @ptrblck
Repository: godot
Issue: Alt+RMB in Select mode does not show anything
Labels: enhancement,discussion,topic:editor,confirmed,topic:3d

### Tested versions

Tested in v4.2.stable.official [46dc27791]

### System information

Windows 10

### Issue description

When using the Select Mode (via Q) and pressing Alt+RMB in a 3D scene, the promised function "Show list of all nodes at position clicked" does not work - no list is shown. It works in 2D.

![Screenshot_7](https://github.com/godotengine/godot/assets/3142253/5cb15062-ee27-4943-904f-d16ff0f5926b)


### Steps to reproduce

See issue description. If the function is not supposed to work in 3D environments, then the description should reflect that.

### Minimal reproduction project (MRP)

N/A
Repository: next.js
Issue: Allow route handler with only GET method and dynamic behavior to be excluded in build export
Labels: bug

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/stupefied-tree-nmlqg5?file=%2Fapp%2Fapi%2Froute.ts

### To Reproduce

1. Launch the build (`npm run build` / `yarn build`), knowing that its output is `export`
2. Watch it crash with the error message:
```
Error: Page with `dynamic = "error"` couldn't be rendered statically because it used `request.url`
``` 

### Current vs. Expected behavior

It is a real use case of Next.js to have two ways of running the same codebase: one in SSR mode (`output: undefined`), and one in static/SSG mode (`output: 'export'`) .
And in the SSR mode we might want route handlers with "dynamic" GET methods, that we don't care about in static/SSG mode.

(Our use case, which I believe is not that rare, is that in production we use the static mode, i.e. we just put the export on a CDN, but we also want to have an SSR mode so that the writers of our website can preview their changes on a single page, using the [draft mode](https://nextjs.org/docs/app/building-your-application/configuring/draft-mode))

The problem is that currently when running the build in static mode (`output: 'export'`), it crashes.
There is an ugly workaround which is to add a POST method to the route file, so that it is excluded from the build in static mode.
I think a cleaner solution would be to add a new value to the Route Segment option `dynamic`, something like `export const dynamic = 'exclude-from-output-export';`

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
Binaries:
  Node: 20.9.0
  npm: 9.8.1
  Yarn: 1.22.19
  pnpm: 8.10.2
Relevant Packages:
  next: 14.1.1-canary.12 // Latest available version is detected (14.1.1-canary.12).
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.1.3
Next.js Config:
  output: export
```


### Which area(s) are affected? (Select all that apply)

App Router, Static HTML Export (output: "export")

### Which stage(s) are affected? (Select all that apply)

next build (local)

### Additional context

This issue is present at least since version 13.4.
Repository: next.js
Issue: Build fails when importing @mui/material in a workspace that uses type:module in package.json
Labels: bug

### Link to the code that reproduces this issue

https://github.com/wereHamster/nextjs-you-crazy-questionmark

### To Reproduce

`yarn next build`

### Current vs. Expected behavior

Build works when you remove `type:module` from package.json.

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 22.2.0: Fri Nov 11 02:04:44 PST 2022; root:xnu-8792.61.2~4/RELEASE_ARM64_T8103
Binaries:
  Node: 20.10.0
  npm: 10.2.3
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.1.0
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


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

Not sure

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

next build (local), Vercel (Deployed)

### Additional context

_No response_
Repository: godot
Issue: Involuntary object transformations, due to freeform mouse drag handling in viewport
Labels: enhancement,discussion,topic:editor,topic:input

### Tested versions

I'm using v4.2.stable.official [46dc27791]

### System information

Windows 10; only tested in 3D, might be the same in 2D

### Issue description

I often accidentally move or rotate nodes a tiny bit around. I often notice that much later. This is especially annoying with objects that are supposed to be in precise locations, like parts of build kits.

### Steps to reproduce

The four modes Select, Move, Rotateand Scale Mode allow moving/rotating/scaling the currently selected object(s) even when the cursor is not near the gizmo or the object is actually seen on screen. I understand the upside: this allows transforming objects based on the current viewport space, instead of world/object space. But this also makes it very easy to accidentally transform things with one or more misplaced clicks.

Another minor gripe: in Move/Rotate/Scale Mode, even if you just click without actually dragging (mostly because I always forget that I can't select another object if I'm not in Select Mode), it creates an entry in the undo history.

So I guess the main question is if there is a way to block Godot from moving 3D objects in Select or any of the Translation Modes if I click/drag the cursor in the scene but not hovering the gizmo? In any case I would rather propose to extend the "Use Local Space (T)" button to allow switching between global/local/viewport, and get rid of the input recognition outside of the gizmo.

### Minimal reproduction project (MRP)

N/A