sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: material-ui
Issue: [material-ui] Components with design & DX improvements waiting for a major release
Labels: umbrella,breaking change,package: material-ui

This is an umbrella issue to gather all of the issues & PRs around components with potential design & DX improvement opportunities that can only be released together with a new major version due to breaking changes. They can also be seen on [the Material UI v7 milestone](https://github.com/mui/material-ui/milestone/48).

## Input components

### Autocomplete
- https://github.com/mui/material-ui/issues/36841
- https://github.com/mui/material-ui/issues/39963 
- https://github.com/mui/material-ui/issues/29727
- https://github.com/mui/material-ui/issues/35710
- https://github.com/mui/material-ui/issues/36075

### Button (and variations)
- https://github.com/mui/material-ui/issues/35843
- https://github.com/mui/material-ui/pull/30145
- https://github.com/mui/material-ui/issues/35045
- https://github.com/mui/material-ui/issues/34072
- https://github.com/mui/material-ui/issues/29965
- https://github.com/mui/material-ui/issues/28551
- https://github.com/mui/material-ui/issues/39943
- https://github.com/mui/material-ui/issues/28543

### Others

- https://github.com/mui/material-ui/issues/39286
- https://github.com/mui/material-ui/issues/37310
- https://github.com/mui/material-ui/issues/36211
- https://github.com/mui/material-ui/pull/36188
- https://github.com/mui/material-ui/issues/35488
- https://github.com/mui/material-ui/issues/34039
- https://github.com/mui/material-ui/issues/33006
- https://github.com/mui/material-ui/issues/29892
- https://github.com/mui/material-ui/issues/29596
- https://github.com/mui/material-ui/issues/23216
- https://github.com/mui/material-ui/issues/13898
- https://github.com/mui/material-ui/issues/39134
- https://github.com/mui/material-ui/issues/38932
- https://github.com/mui/material-ui/issues/39135
- https://github.com/mui/material-ui/issues/40143
- https://github.com/mui/material-ui/issues/39497
- https://github.com/mui/material-ui/issues/30139

## Data display

- https://github.com/mui/material-ui/issues/20470
- https://github.com/mui/material-ui/issues/38012
- https://github.com/mui/material-ui/issues/30678

## Feedback components

- https://github.com/mui/material-ui/issues/38595
- https://github.com/mui/material-ui/issues/27851
- https://github.com/mui/material-ui/issues/27306
- https://github.com/mui/material-ui/issues/26795
- https://github.com/mui/material-ui/issues/33146
- https://github.com/mui/material-ui/issues/40185
- https://github.com/mui/material-ui/issues/40198

## Surfaces

- https://github.com/mui/material-ui/pull/31885
- https://github.com/mui/material-ui/issues/39964

## Navigation

- https://github.com/mui/material-ui/issues/37253
- https://github.com/mui/material-ui/issues/35589
- https://github.com/mui/material-ui/issues/33603
- https://github.com/mui/material-ui/issues/28064
- https://github.com/mui/material-ui/issues/15324

## Util components

- https://github.com/mui/material-ui/issues/39965
Repository: flutter
Issue: Linux unit tests crashes in ssh
Labels: platform-linux,a: desktop,P2,team-linux,triaged-linux

The linux unit tests crashes when I run it on my cloud gLinux:
```
[----------] 3 tests from FlPlatformPluginTest
[ RUN      ] FlPlatformPluginTest.PlaySound
[       OK ] FlPlatformPluginTest.PlaySound (0 ms)
[ RUN      ] FlPlatformPluginTest.ExitApplication
[       OK ] FlPlatformPluginTest.ExitApplication (0 ms)
[ RUN      ] FlPlatformPluginTest.ExitApplicationDispose

(flutter_linux_unittests:3309376): Gtk-WARNING **: 11:27:22.393: cannot open display: 
[FATAL:flutter/fml/thread_local.cc(32)] Check failed: false. pthread_setspecific failed (22): Invalid argument
[1]    3309376 IOT instruction  ../out/host_debug_unopt/flutter_linux_unittests
```
 which might be due to the fact that ssh doesn't come with a display device.

Reproduction:
* ~~Ssh into the cloudtop gLinux~~ Open a terminal on Linux.
* Check out the commit 88baf62f1e66e973e919faef7d80fb1a4c3ef90c on the engine
* Compile and run `../out/host_debug_unopt/flutter_linux_unittests`

Bisect shows that the first bad commit is https://github.com/flutter/engine/pull/47713 by @gspencergoog.

If our guess is correct, then we can skip or even fail the test when there's no device, but crashing should still be avoided.
Repository: ollama
Issue: Dark mode for ollama.com
Labels: feature request,ollama.com

Just to protect your eyes, especially during the night.
Repository: vscode
Issue: After pressing Alt+Shift text editor loses focus
Labels: linux

<!-- ⚠️⚠️ 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: 1.85.1
- OS Version: Ubuntu 22.04

Steps to Reproduce:

1. Press Alt+Shift (order is important)

Shift+Alt (and Alt+Shift) is used in my system to switch keyboard layout. The system (and other software) does not distinguish the order of pressing. But VS Code does. After pressing editor lose focus and I need to press Alt or Esc to return it
Repository: next.js
Issue: revalidatePath with middleware doesn't work on multi-tenant project
Labels: bug,Runtime,Pages Router

### Link to the code that reproduces this issue

https://github.com/sergiolamorda/nextjs-issue-revalidatePath-multitenant

### To Reproduce

First, add two domains to your local hostname, for example:

```
127.0.0.1	test1.local
127.0.0.1	test2.local
```

hen, execute the build and start commands:

```
npm run build
npm run start
```

Next, open two different tabs and navigate to http://test1.local:3000/test and http://test2.local:3000/test respectively.

Now, make a POST request to http://localhost:3000/api/revalidate, which will execute revalidatePath('/test2.local/test'). If you reload the previous tab, the content does not update.

Finally, make a POST request to http://localhost:3000/api/revalidate2, which will execute revalidatePath('/test'). If you reload the previous tabs, both will show updated content.

### Current vs. Expected behavior

We're working on a multi-tenant project that employs middleware to rewrite requests, converting the host into a slug.

In Next.js 12, you can perform on-demand revalidation in the API using res.revalidate(), which only invalidates the cache for the domain where the request was made.

However, after migrating to Next.js 14, we encountered issues when trying to invalidate the cache with revalidatePath; it doesn't seem to work as expected.

Attempting revalidatePath('/domain/test') doesn't take the middleware into account and fails to produce any effect.

On the other hand, using revalidatePath('/test') results in invalidating the /test path across all domains.

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
Binaries:
  Node: 20.9.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.0.4
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: N/A
Next.js Config:
  output: N/A
```


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

Data fetching (gS(S)P, getInitialProps), Middleware / Edge (API routes, runtime)

### Additional context

_No response_
Repository: flutter
Issue: [web:a11y] implement didGainFocus & FocusSemanticEvent in the web engine
Labels: engine,a: accessibility,platform-web,P2,customer: castaway,team-web,triaged-web

The engine is now expected to send a `didGainFocus` to the framework to record that previous accessibility focus position when pushing a new route. In return, the framework sends a `FocusSemanticEvent` back to the engine when popping a route so that the engine could put the a11y focus back to where it was. This needs to be implemented in the web engine.

Framework-side change: https://github.com/flutter/flutter/pull/135771
Repository: flutter
Issue: Cocoon dashboard - missing build runs for Linux docs_publish
Labels: team-infra,P3,triaged-infra

### Type of Request

bug

### Infrastructure Environment

Cocoon

### What is happening?

On the [dashboard](https://flutter-dashboard.appspot.com/#/build) we are seeing a failing build:

![image](https://github.com/flutter/flutter/assets/91688203/4cd0187a-c359-4d03-8dd2-f107621cf2fb)

We beleive the original failing build was 12308 (due to a luci issue, which got resolved). The subsequent builds 12309, 12310 (at the same commit) ran successfully:

![image](https://github.com/flutter/flutter/assets/91688203/9f19edae-0117-4229-aa2c-22bf10940e7d)

but the dashboard didn't show success for that build, and it also doesn't show those two builds 12309 and 12310 in the "Open log for ..." list in the build detail dialog (see screenshot above).

### Steps to reproduce

Step 1:
Step 2:
..
Step n:


### Expected results

I expect to see X when Y is finished.
Repository: PowerToys
Issue: Control remap does not interact well with Visual Studio keyboard shortcuts
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.76.2

### Installation method

Microsoft Store

### Running as admin

None

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

I used PowerToys to switch Caps Lock and Left Ctrl. In most places, it works -- for example, I can usually hit "Caps Lock + C" and it will remap as expected to "Ctrl + C" and run a *copy*. 

In Visual Studio there is a shortcut for the command `Edit.ParameterInfo`. You can find it by going to menu: Tools > Options. Then Environment > Keyboard, and typing the command name or some part of it in the field "Show commands containing:".  It shows that the shortcut is "Ctrl+Shift+Space (Text Editor)". When I go back to my code editor, and put the cursor somewhere this should work, after parentheses, for example `foo(|)`, the key command does not work when I hit the keys "Caps Lock + Shift + Space".  If I use the _right_ Ctrl key, which has not been remapped, and combine it with Shift+Space, then the command is activated and the parameter info is shown.

Here's a screenshot showing the command when it is properly activated. 

![image](https://github.com/microsoft/PowerToys/assets/1702134/090c8772-11f0-442c-ac69-41888d0be6b3)

Here's a screenshot of my key mapping in PowerToys:

![image](https://github.com/microsoft/PowerToys/assets/1702134/18f428d8-ca76-426c-aa2c-1e05f3887d83)



### ✔️ Expected Behavior

The Caps Lock key should behave like it's a Ctrl key, reliably.  So hitting the physical keys "Caps Lock + Shift + Space" should be like I hit "Ctrl + Shift + Space" and it should run the Visual Studio command.

### ❌ Actual Behavior

It doesn't trigger the command.

### Other Software

Visual Studio 17.8.3
Repository: godot
Issue: EditorSpinSlider tooltips don't reflect "ground truth" value
Labels: bug,topic:editor

### Tested versions

- Reproducible in 4.2.1.stable

### System information

Godot v4.2.1.stable - Windows 10.0.22621 - Vulkan (Mobile) - dedicated NVIDIA GeForce GTX 1660 SUPER (NVIDIA; 31.0.15.4633) - Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz (16 Threads)

### Issue description

The tooltips on all `EditorSpinSlider` (used for inspecting floats and vector components) do not reflect the underlying "ground truth" value (the expected behaviour).

Instead, they show a higher-precision printout of a value that has already been rounded down according to the EditorSpinSlider's step property.

The value shown by the tooltip is, as of right now, completely useless, since it is neither the value that will be used at runtime, nor a tidy formated string.

The cause is that the `EditorSpinSlider` class is being fed the underlying value by the `EditorProperty` classes, which is then rounded and stored as a local copy in `EditorSpinSlider`. It is this rounded value which is then being shown in full in the tooltips.

### Steps to reproduce

- Make sure that the editor's `Default Float Step` setting is set to the default value of `0.001`.
- Open the `test` scene in attached project.
- Inspect the root node. See that the exported float and vector show `0.001` in all fields.
- Hover cursor over the fields. The tooltips will all show `0.00100000000384`.
- Run the scene. See the ground truth values in the output log: `0.0006` and `(0.0006, 0.0006, 0.0006)`.

The expected behaviour is for the tooltips to show `0.0006`.

### Minimal reproduction project (MRP)

[EditorSpinSliderTooltip.zip](https://github.com/godotengine/godot/files/13733946/EditorSpinSliderTooltip.zip)
Repository: stable-diffusion-webui
Issue: [Bug]: a1111 wont load for whatever reason
Labels: asking-for-help-with-local-system-issues

### Checklist

- [ ] The issue exists after disabling all extensions
- [ ] The issue exists on a clean installation of webui
- [ ] The issue is caused by an extension, but I believe it is caused by a bug in the webui
- [ ] The issue exists in the current version of the webui
- [ ] The issue has not been reported before recently
- [ ] The issue has been reported before but has not been fixed yet

### What happened?

everything was downloaded properly but when it goes to launch i get this error message

### Steps to reproduce the problem

i have zero clue

### What should have happened?

it shouldve just launched, regularly

### What browsers do you use to access the UI ?

Mozilla Firefox

### Sysinfo

?

### Console logs

```Shell
fatal: detected dubious ownership in repository at 'C:/a1111/stable-diffusion-webui'
'C:/a1111/stable-diffusion-webui' is owned by:
        'S-1-5-32-544'
but the current user is:
        'S-1-5-21-1314564024-2096099064-3782412885-1001'
To add an exception for this directory, call:

        git config --global --add safe.directory C:/a1111/stable-diffusion-webui
fatal: detected dubious ownership in repository at 'C:/a1111/stable-diffusion-webui'
'C:/a1111/stable-diffusion-webui' is owned by:
        'S-1-5-32-544'
but the current user is:
        'S-1-5-21-1314564024-2096099064-3782412885-1001'
To add an exception for this directory, call:

        git config --global --add safe.directory C:/a1111/stable-diffusion-webui
Python 3.8.3 (tags/v3.8.3:6f8c832, May 13 2020, 22:37:02) [MSC v.1924 64 bit (AMD64)]
Version: 1.7.0
Commit hash: <none>
Installing xformers
Launching Web UI with arguments: --xformers --autolaunch
Traceback (most recent call last):
  File "launch.py", line 48, in <module>
    main()
  File "launch.py", line 44, in main
    start()
  File "C:\a1111\stable-diffusion-webui\modules\launch_utils.py", line 460, in start
    import webui
  File "C:\a1111\stable-diffusion-webui\webui.py", line 13, in <module>
    initialize.imports()
  File "C:\a1111\stable-diffusion-webui\modules\initialize.py", line 33, in imports
    from modules import shared_init
  File "C:\a1111\stable-diffusion-webui\modules\shared_init.py", line 5, in <module>
    from modules import shared
  File "C:\a1111\stable-diffusion-webui\modules\shared.py", line 5, in <module>
    from modules import shared_cmd_options, shared_gradio_themes, options, shared_items, sd_models_types
  File "C:\a1111\stable-diffusion-webui\modules\options.py", line 80, in <module>
    class Options:
  File "C:\a1111\stable-diffusion-webui\modules\options.py", line 83, in Options
    def __init__(self, data_labels: dict[str, OptionInfo], restricted_opts):
TypeError: 'type' object is not subscriptable
Press any key to continue . . .
```


### Additional information

_No response_
Repository: pytorch
Issue: support Tensor type for scale in scaled_dot_product_attention
Labels: triaged,module: sdpa

### 🚀 The feature, motivation and pitch

# feature request
I would like to scale by Tensor type. Is it possible to support Tensor?
![image](https://github.com/pytorch/pytorch/assets/45687080/e0f51bd4-7973-4ad7-9488-b243c91f55bd)

# Motivation
I tried to replace the attention of SwinV2 with torch scaled_dot_product_attention.
However, there is scaling with the Tensor type which does channel-wise scaling.
> attn = attn * logit_scale

https://github.com/pytorch/vision/blob/5ab80c9e6e2582883ba40ac8cd67fa599a175867/torchvision/models/swin_transformer.py#L186

[scaled_dot_product_attention support for swin in torchvision](https://github.com/pytorch/vision/issues/new?assignees=&labels=&projects=&template=feature-request.yml)

### Alternatives

_No response_

### Additional context

_No response_
Repository: godot
Issue: Engine becomes unresponsive when attempting to add a physics element to a 1x1 tile set
Labels: bug,topic:editor,needs testing,topic:2d

### Tested versions

Godot_v4.2-stable

### System information

Windows 11 - Godot_v4.2-stable

### Issue description

Engine becomes unresponsive when attempting to add a physics element to a 1x1 tile set

### Steps to reproduce

1. Make tilemap
2. Change tile size to 1x1 px
3. attempt to add a physics element

### Minimal reproduction project (MRP)

[FallingSandSim.zip](https://github.com/godotengine/godot/files/13734237/FallingSandSim.zip)
Repository: terminal
Issue: Characters typed into terminal when switching to other windows/tabs
Labels: Needs-Repro,Area-Input,Area-VT,Issue-Bug,Product-Terminal

### Windows Terminal version

1.18.3181.0

### Windows build number

10.0.22631.0

### Other Software

PowerShell 7.4.0 (from microsoft store)

### Steps to reproduce

From the first open tab in Windows Terminal, Alt-tab or use the mouse to switch to another window, or another tab within Windows Terminal.

### Expected Behavior

Nothing typed into the terminal

### Actual Behavior

The first time I switch away, it writes a `[` into the terminal.  If I switch back, it writes `O[`, and if I tab out again it writes `I[`, and continues to do that if I tab in and out repeatedly, so I end up with something like `[O[I[O[I[O[I[O[I[O[I[O[I[O[I[O[I` in my terminal.

It's entirely possible that I (or my toddler) accidentally mashed some key combination to put the terminal in some unexpected mode; this would be the most likely explanation since neither Windows Terminal nor PowerShell have been updated recently, however I'm at a loss as to what exactly could have done this.
Repository: flutter
Issue: HTML renderer produces an exception and stops rendering when receiving an unordered rect
Labels: platform-web,e: web_html,P2,team-web,triaged-web

The legacy behavior of drawRect, drawOval and clipRect has been established by the implementation of Skia which automatically sorts their rects before executing the operation. As we shift our implementations we should verify this behavior at the Flutter framework level.

The problem was initially observed in https://github.com/flutter/flutter/issues/128159 when the engine started using the DisplayList to record operations and fixed for drawRect and drawOval in https://github.com/flutter/engine/pull/42556.

Writing a test case for more coverage of these instances of accepting unordered rects pointed out that we have problems with this in the latest engine as reported in https://github.com/flutter/flutter/issues/140490. The native platform code is being patched in https://github.com/flutter/engine/pull/49309, but there is still a problem in the HTML renderer which stops rendering and outputs an exception:

```
══╡ EXCEPTION CAUGHT BY SCHEDULER LIBRARY ╞═════════════════════════════════════════════════════════
The following DomException object was thrown during a scheduler callback:
  IndexSizeError: Failed to execute 'ellipse' on 'CanvasRenderingContext2D': The major-axis radius
provided (-15) is negative.
```

The canvaskit renderer appears to pass just fine, but it should probably have a test to verify the behavior as well.
Repository: TypeScript
Issue: Native Node.js Integration/Support
Labels: Discussion

### 🔍 Search Terms

native nodejs integration
nodejs support
nodejs integration
run nodejs

### ✅ Viability Checklist

- [X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
- [X] This wouldn't change the runtime behavior of existing JavaScript code
- [X] This could be implemented without emitting different JS based on the types of the expressions
- [X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
- [X] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
- [X] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

### ⭐ Suggestion

I would like Node.js and Typescript to support the following user experience.

```sh
$ node script.ts
"Hello World"
```

This setup requires a seamless integration between Node.js and the TypeScript language. The @nodejs community has a longstanding issue documented [here](https://github.com/nodejs/node/issues/43818) regarding this specific use case. While the majority of the work is anticipated to take place within the Node.js runtime, establishing an effective communication channel between the Node.js and TypeScript communities is crucial for tracking and progressing this feature request. It appears that the Node.js community could benefit from collaboration and support from the TypeScript community, as mentioned in this [comment](https://github.com/nodejs/node/issues/43818#issuecomment-1865452580).

### 📃 Motivating Example

The TypeScript ecosystem is closely integrated with Node.js. It would be fantastic if Node.js could effortlessly consume TypeScript code without the need for additional third-party tools. Both Deno and Bun runtimes have independently implemented this feature. However, Node.js currently lags behind in providing native support for this capability.

### 💻 Use Cases

1. What do you want to use this for?
- Run TypeScript code directly without an additional bundler/compiler step.
- Enable developers to distribute TypeScript-only npm packages, eliminating the need to manage both `.d.ts` and `.js` files in non-browser environments.

2. What shortcomings exist with current approaches?
Additional tooling is required, and there are no defined heuristics.

3. What workarounds are you using in the meantime?
Currently, tools such as [ts-node](https://github.com/TypeStrong/ts-node) or [tsx](https://github.com/privatenumber/tsx) are employed to execute TypeScript code directly in the Node.js ecosystem. Alternatively, developers may opt for alternative runtimes like Deno and Bun.