sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: material-ui
Issue: [material-ui] Deprecate composed CSS classes
Labels: deprecation,package: material-ui,ready to take

Part of #40417 

## Description

Deprecate composed CSS classes, which are planned for removal in v7.

- These are deprecated in favor of using atomic classes and combining them in userland
- If the atomic classes do not exist, they must be implemented in the same PR in which the deprecation is added
- The PR introducing the deprecation must also add:
  - A section in the [migration guide](https://mui.com/material-ui/migration/migrating-from-deprecated-apis/)
  - A [codemod](https://github.com/mui/material-ui/tree/HEAD/packages/mui-codemod#deprecations)

## Example PR

- https://github.com/mui/material-ui/pull/41235

## Contributing

Feel free to take any components that still need to be done or in progress. Please mention this issue in your PR so we can link it in the description and keep it up to date.

## Components to migrate

- [x] AccordionSummary: [#40418](https://github.com/mui/material-ui/pull/40418), [#41006](https://github.com/mui/material-ui/pull/41006)
- [x] Alert: [#40688](https://github.com/mui/material-ui/pull/40688)
- [x] Button: [#40675](https://github.com/mui/material-ui/pull/40675)
- [x] ButtonGroup: [#41259](https://github.com/mui/material-ui/pull/41259)
- [x] Chip: [#41235](https://github.com/mui/material-ui/pull/41235)
- [x] CircularProgress: [#42076](https://github.com/mui/material-ui/pull/42076)
- [ ] Dialog
- [x] Divider:  [#40563](https://github.com/mui/material-ui/pull/40563)
- [ ] Drawer:  [#44870](https://github.com/mui/material-ui/pull/44870)
- [ ] FilledInput
- [x] ImageListItemBar: [#42905](https://github.com/mui/material-ui/pull/42905)
- [ ] Input
- [ ] InputBase
- [x] LinearProgress:  [#44933](https://github.com/mui/material-ui/pull/44933)
- [ ] LoadingButton
- [ ] NativeSelect
- [ ] OutlinedInput
- [x] PaginationItem: [#40673](https://github.com/mui/material-ui/pull/40673), [#41145](https://github.com/mui/material-ui/pull/41145)
- [x] Select: [#42950](https://github.com/mui/material-ui/pull/42950)
- [ ] Slider
- [ ] SpeedDial
- [ ] SpeedDialAction
- [ ] SpeedDialIcon
- [x] StepConnector: [#41740](https://github.com/mui/material-ui/pull/41740)
- [ ] SwipeableDrawer:  [#44870](https://github.com/mui/material-ui/pull/44870)
- [x] TableSortLabel: [#42281](https://github.com/mui/material-ui/pull/42281)
- [ ] TabList
- [ ] Tabs
- [x] ToggleButtonGroup: [#41288](https://github.com/mui/material-ui/pull/41288)
- [ ] Tooltip

**Search keywords**: deprecation composed classes material-ui

**Search keywords**:
Repository: vscode
Issue: "Invalid regular expression" when trying to use Find or Ctrl+D at ~4000 characters
Labels: bug,editor-find

1. Grab this file [some-paths.txt](https://github.com/microsoft/vscode/files/14410803/some-paths.txt)
2. Select the first line
3. Ctrl+D or copy and paste it into the find widget
4. Get an error about an "invalid regular expression"

There is this issue https://github.com/microsoft/vscode/issues/183388, but this seems to trigger at~4056 characters (when I try to select a substring), much less than the reported 150k characters.
Repository: PowerToys
Issue: Submit PowerToys Run and File Action Menu plugin interfaces as NuGet Packages
Labels: Product-PowerToys Run,Area-Build,Needs-Triage,Product-File Actions Menu

### Description of the new feature / enhancement

Submit PowerToys Run and File Action Menu plugin interfaces as NuGet Packages. The version numbers of the packages would be the same as PowerToys version.

### Scenario when this would be used?

This would make it a lot easier to develop plugins for these two modules, as they would no longer have to ship with DLLs or reference the PowerToys source code.

### Supporting information

_No response_
Repository: material-ui
Issue: [joy-ui][Modal] `ModalClose` applies hover and click only outside the button's icon
Labels: component: modal,package: joy-ui

### Steps to reproduce

Steps:
1.  `
  import {
    DialogActions,
    DialogContent,
    Modal,
    ModalClose,
    ModalDialog,
    Typography,
  } from '@mui/joy';
`
2. Hover or Click the X of ModalClose.

https://github.com/mui/material-ui/assets/43346005/52686181-0327-47ee-ba66-44382a291274




### Current behavior

The `<ModalClose />` works when you hover or click outside it's default svg child.

### Expected behavior

It should hover or click when you focus the button or the svg inside button.

### Context

mui/joy default ModalClose

### Your environment

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
System:
    OS: Windows 10 10.0.19045
  Binaries:
    Node: 18.18.0 - C:\Program Files\nodejs\node.EXE   
    npm: 10.2.0 - C:\Program Files\nodejs\npm.CMD      
    pnpm: Not Found
  Browsers:
    Chrome: Not Found
    Edge: Chromium (122.0.2365.52)
  npmPackages:
    @emotion/react: ^11.11.1 => 11.11.1
    @emotion/styled: ^11.11.0 => 11.11.0
    @mui/base:  5.0.0-beta.10
    @mui/core-downloads-tracker:  5.14.4
    @mui/envinfo: ^2.0.18 => 2.0.18
    @mui/icons-material: ^5.14.3 => 5.14.3
    @mui/joy: 5.0.0-beta.29 => 5.0.0-beta.29
    @mui/lab: ^5.0.0-alpha.139 => 5.0.0-alpha.139      
    @mui/material: ^5.14.4 => 5.14.4
    @mui/private-theming:  5.14.4
    @mui/styled-engine:  5.13.2
    @mui/styles: ^5.14.4 => 5.14.4
    @mui/system:  5.14.4
    @mui/types:  7.2.4
    @mui/utils:  5.14.4
    @mui/x-date-pickers: ^6.11.0 => 6.11.0
    @types/react: ^17.0.0 => 17.0.64
    react: ^18.2.0 => 18.2.0
    react-dom: ^18.2.0 => 18.2.0
    styled-components: ^5.1.1 => 5.3.11
    typescript: ^5.1.6 => 5.1.6
```
</details>


**Search keywords**: modal
Repository: tauri
Issue: [feat] expose control over webkit settings
Labels: type: feature request

### Describe the problem

I can see that wry e.g. enables webGL, among other settings:
https://github.com/tauri-apps/wry/blob/91ac2e4b95a373aeb9aa2e2a31662481a21fe0a4/src/webkitgtk/mod.rs#L367

I'm trying to tune the performance of my app, and want to experiment with flags like this.

### Describe the solution you'd like

Expose webkit settings somewhere in the Tauri builder, so that I can control them.

### Alternatives considered

_No response_

### Additional context

I'm coming from Electron, where I'm able to manipulate the command line flags passed into chromium.

I'm brand new to Tauri and Rust, so it's certainly possible I overlooked something! If it is already possible to control the settings, then this might be a doc bug instead :)
Repository: vscode
Issue: Allow "pinning" progress messages in chat responses
Labels: feature-request,api,panel-chat

<!-- ⚠️⚠️ 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 love the UX you get when my chat participant reports progress in a response, with the spinner and text. However, I can't use this right now because the progress message(s) always disappear once I start outputting content. My users will rely on looking at the progress messages to understand whether the AI was doing the right thing, e.g. it describes functions that are being called and with what parameters. If these calls complete too quickly, or the user just isn't looking, they will miss the progress message.

I'd like there to be some option for pinning the progress message and a way to notify of completion (success or error) so the icon switches to something like a green checkmark or red X, and then have the progress message stick around in the UI (I think the underlying chat history can remain the same). Thanks in advance!

@isidorn
Repository: pytorch
Issue: 2 Dynamo test are failing with "Global state changed while dynamo tracing, please report a bug".
Labels: low priority,triaged,oncall: pt2,module: dynamo,dynamo-must-fix

2 Dynamo test are failing with "Global state changed while dynamo tracing, please report a bug".

## Repro

`PYTORCH_TEST_WITH_DYNAMO=1 pytest test_openmp.py -v -k test_one_thread`

You will need to remove the skip or expectedFailure before running the repro command.
This may be deleting a file in https://github.com/pytorch/pytorch/tree/main/test/dynamo_skips or https://github.com/pytorch/pytorch/tree/main/test/dynamo_expected_failures 

## Failing tests

Here's a comprehensive list of tests that fail (as of this issue) with the above message:
<details>
<summary>Click me</summary>
```
test_openmp.py::TestOpenMP_ParallelFor.test_one_thread
test_sort_and_select.py::TestSortAndSelectCPU.test_sort_overflow_cpu_int16
```
</details>


cc @ezyang @anijain2305 @chauhang @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @msaroufim @bdhirsh @aakhundov
Repository: pytorch
Issue: 2 Dynamo test are failing with "Failed running call_method sin(*(FakeTensor(..., size=(), grad_fn=<CosBackward0".
Labels: triaged,oncall: pt2,module: dynamo,dynamo-must-fix

2 Dynamo test are failing with "Failed running call_method sin(*(FakeTensor(..., size=(), grad_fn=<CosBackward0".

## Repro

`PYTORCH_TEST_WITH_DYNAMO=1 pytest test_autograd.py -v -k test_nested_checkpoint_reentrant_backwards_early_stop_True`

You will need to remove the skip or expectedFailure before running the repro command.
This may be deleting a file in https://github.com/pytorch/pytorch/tree/main/test/dynamo_skips or https://github.com/pytorch/pytorch/tree/main/test/dynamo_expected_failures 

## Failing tests

Here's a comprehensive list of tests that fail (as of this issue) with the above message:
<details>
<summary>Click me</summary>
```
test_autograd.py::TestNestedCheckpoint.test_nested_checkpoint_reentrant_backwards_early_stop_True
test_autograd.py::TestNestedCheckpoint.test_nested_checkpoint_same_graph_early_stop_True
```
</details>

cc @ezyang @msaroufim @bdhirsh @anijain2305 @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @aakhundov @kadeng
Repository: flutter
Issue: [RFW] Expose the tap details in events
Labels: c: new feature,package,c: proposal,team-ecosystem,P3,p: rfw,triaged-ecosystem

### Use case


RFW core and material widgets should by default populates the tab details in the events. So that when user interact with the widgets, these data will be passed to  RemoteWidget`onEvent` handler.  

### Proposal

Pass the tap detail data to trigger() callback.
Repository: Python
Issue: Haversine distance may be using the wrong phi1 and phi2 angle
Labels: bug

### Repository commit

2e405f397bbcefccc470f215c7ff024875ef16c5

### Python version (python --version)

NA

### Dependencies version (pip freeze)

NA

### Expected behavior

First of thanks for all the algorithms and the work! 

The current (and initial) implementation of the haversine distance is using [reduced latitudes](https://github.com/TheAlgorithms/Python/blob/master/geodesy/haversine_distance.py#L40) (as one does for Lambert's formula see https://en.wikipedia.org/wiki/Geographical_distance#Lambert's_formula_for_long_lines), however, from my understanding the haversine distance should be using the raw latitudes (in radians like the longitudes are currently being handled). At least that is how it is written in https://en.wikipedia.org/wiki/Haversine_formula#Formulation .

The haversine distance from my understanding is supposed to work on a sphere, however, the notion on reduced latitude and flattening factors exist to deal with the non-spherical nature of the Earth (see https://en.wikipedia.org/wiki/Flattening). I am by no means an expert, I could very well be wrong.

Moreover, reading the wikipage and other implementations the transformation to a reduced latitude is not needed for the haversine distance, the latitude is used directly. Here are some references:
- https://en.wikipedia.org/wiki/Haversine_formula#Formulation (also linked in the implementations comments)
- https://github.com/mapado/haversine/blob/main/haversine/haversine.py#L183 from https://pypi.org/project/haversine/

additional implementations:
- https://gist.github.com/vananth22/888ed9a22105670e7a4092bdcf0d72e4
- https://stackoverflow.com/a/4913653

I think most likely there was some confusion with Lambert's formula. 

I am happy to make a small PR, if there is an agreement with my observation.

### Actual behavior

Use the right angles and the results should slightly be different. I did some test, it is not that significant.
Repository: TypeScript
Issue: Incorrect resolution of CJS types from dual-package dependency in multi-project build with mixed `ESNext/Bundler` and `NodeNext` modules
Labels: Bug,Fix Available

### 🔎 Search Terms

"NodeNext", "ESNext", "Bundler", "module", "moduleResolution", "ESM", "CJS", "multi-project", "dual package"

### 🕗 Version & Regression Information

- This is the behavior in every version I tried (5.0.4, 5.1.6, 5.2.2, 5.3.3, and 5.5.0-dev.20240226), and I reviewed the FAQ for entries about ESM


### ⏯ Playground Link

https://github.com/haines/typescript-dual-package-esnext-bundler-nodenext

### 💻 Code

It's probably less confusing to look at the repo, sorry 🙈 I've tried to make it as minimal as possible.

This bug occurs in a multi-project build where one project (`app`) is configured to use `ESNext` module and `Bundler` module resolution, and another (`lib`) is using `NodeNext`. Everything is set up to use ESM with `"type": "module"` in package.json.

If both projects depend on the same dual-packaged dependency (`dep`), then when `app` imports `dep` directly, TypeScript correctly resolves the ESM types. However, transitive imports of `dep` through `lib` are resolved to the CJS types.

### 🙁 Actual behavior

TypeScript resolves the CJS types for transitive imports of the dual-packaged dependency. If the CJS types are not perfectly compatible with the ESM types, then this causes compile errors.

### 🙂 Expected behavior

TypeScript resolves the ESM types for all imports of the dual-packaged dependency.

### Additional information about the issue

Originally encountered in `@bufbuild/protobuf`: https://github.com/bufbuild/protobuf-es/issues/718

Our `app` is full-stack and built with Vite, which is why we want to use `ESNext/Bundler`, but our `lib` is consumed by other Node.js-only projects that are built with tsc and therefore it makes sense for that to be built with `NodeNext`.
Repository: godot
Issue: No unit tests for GDScript code highlighter
Labels: enhancement,topic:gdscript,topic:tests

### Tested versions

4.3.dev and all previous

### System information

N/A

### Issue description

The GDScript unit tests currently do not cover syntax highlighting, despite covering other editor-related features like code completion. There have recently been some fixes to syntax highlighting: https://github.com/godotengine/godot/pull/86176 and the changes have already introduced one known regression: https://github.com/godotengine/godot/pull/88876. In light of this, a small suite of unit tests to cover syntax highlighting seems appropriate. It would also probably be a good first issue for a new contributor I'm guessing.

### Steps to reproduce

N/A

### Minimal reproduction project (MRP)

N/A
Repository: flutter
Issue: Support Android Hybrid Composition without converting to ImageVIew
Labels: a: platform-views,platform-views: hc,team-android

Using [SurfaceControl.Transaction.reparent](https://developer.android.com/reference/android/view/SurfaceControl.Transaction#reparent(android.view.SurfaceControl,%20android.view.SurfaceControl)) we might be able to construct a hierarchy of Surfaces for SurfaceFlinger to composite. It may be possible to avoid using an ImageView in the Hybrid Composition case.
Repository: pytorch
Issue: Triton kernel unexpectedly gets 1.35x slower by more specializaiton
Labels: module: performance,triaged,oncall: pt2,upstream triton

This triton kernel https://gist.github.com/shunting314/9bcd806bdcda7f58ab4bae57ab6f80ad (call it v1) uses ks0 as stride. If we replace ks0 with the only possible value in this test, the new kernel https://gist.github.com/shunting314/063eb3c6bf16c1b947d7608eae87381c (call it v2) get 1.35x slower.

I can verify that the slower kernel uses vectorized load/store while the faster does not. This is very counter-intuitive since vectorized load/store should help perf in general.

Actually there is an alternative change to make v2 kernel as faster as v1: we can remove in_ptr0 and out_ptr1 from the divisible_by_16 list. This by effect disables vectorized load/store as well. Here is the kernel (v3): https://gist.github.com/shunting314/827b482a0407425565051538633aa095

Overall the numbers I get seems to suggest that vectorized load/store here is bad for perf.

@bertmaher  @htyu  let me know if I should cut the issue in the triton repo instead.

UPDATE TO AVOID CONFUSION: the root cause of the slowness is not vectorization. Vectorization still help in general. The root cause is the slow kernel uses an sub-optimal layout that harm memory coalescing. 

cc @ezyang @msaroufim @bdhirsh @anijain2305 @zou3519 @chauhang @jansel @Chillee @eellison
Repository: flutter
Issue: Consider: "Use Android Test Orchestrator" for Scenario App
Labels: platform-android,engine,P3,team-engine,triaged-engine,e: scenario-app

![image](https://github.com/flutter/flutter/assets/168174/550045ae-2786-4969-abd9-fd24607bd8ac)


See https://developer.android.com/training/testing/instrumented-tests/androidx-test-libraries/runner#use-android:

> Android Test Orchestrator offers the following benefits for your testing environment:
>
> **Minimal shared state**: Each test runs in its own Instrumentation instance. Therefore, if your tests share app state, most of that shared state is removed from your device's CPU or memory after each test. To remove all shared state from your device's CPU and memory after each test, use the clearPackageData flag. See the [Enable from Gradle](https://developer.android.com/training/testing/instrumented-tests/androidx-test-libraries/runner#enable-gradle) section for an example.
>
> **Crashes are isolated**: Even if one test crashes, it takes down only its own instance of Instrumentation. This means that the other tests in your suite still run, providing complete test results.

Apparently we might be able to [enable it from the command-line](https://developer.android.com/training/testing/instrumented-tests/androidx-test-libraries/runner#enable-command)?

/cc @reidbaker If you have any experience with this?
Repository: flutter
Issue: Dropping platform message on channel: `flutter/localization`
Labels: platform-android,engine,P2,team-engine,triaged-engine,e: scenario-app

... happens on every invocation of `scenario_app`, making the console harder to interpret:

> 02-26 17:22:51.420 [W] flutter: [WARNING:flutter/shell/common/engine.cc(339)] Dropping platform message on channel: flutter/localization

I am guessing we should be able to instrument the dummy app in a way that does not hit this branch.
Repository: ant-design
Issue: 在Safari浏览器中，Tooltip和disabled Button一起使用，mouseout的时候Tooltip没有隐藏 
Labels: 🐛 Bug,Inactive

### Reproduction link

[![Edit on StackBlitz](https://developer.stackblitz.com/img/open_in_stackblitz.svg)](https://stackblitz.com/edit/react-aevpwm?file=index.js)

### Steps to reproduce

在Safari浏览器中Tooltip和disabled Button一起使用

### What is expected?

mouseout的时候Tooltip隐藏 

### What is actually happening?

mouseout的时候Tooltip没有隐藏 

| Environment | Info |
| --- | --- |
| antd | 5.14.2 |
| React | 18 |
| System | mac 14 |
| Browser | safari 16 |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: rust
Issue: Support for tvOS arm64e target
Labels: C-enhancement,T-compiler,O-tvos

Currently, rust has support for arm64e-apple-ios and arm64e-apple-darwin targets in PR #115526. Hope to also add support for tvOS arm64e target.


https://github.com/rust-lang/rust/issues/73628
Repository: PowerToys
Issue: Setup Failed
Labels: Issue-Bug,Area-Setup/Install,Needs-Triage,Needs-Team-Response

### Microsoft PowerToys version

0.76.0

### Installation method

GitHub

### Running as admin

Yes

### Area(s) with issue?

General

### Steps to reproduce

Since three/four versions before, i can't update my powertoys even i download it from github and run as admin.  I used geek uninstaller to uninstall the old version and run the new version, but It said that setup failed because one or more issues caused the setup  to fail. Please fix the issues and then retry setup. For more information see the log file. Powertoys is already installed on this stystem for all users. We recommend first uninstalling that version before installing this one.  I really need it so i hope you can help me figure this problem.
![X9S`2YO6ET1A4M`V$%IB$T9](https://github.com/microsoft/PowerToys/assets/127008073/28cfc739-c725-4fb3-8abe-9214e1e50670)


### ✔️ Expected Behavior

update successfully

### ❌ Actual Behavior

setup failed

### Other Software

_No response_
Repository: TypeScript
Issue: Declaration merging in plain JS with JSDoc
Labels: Suggestion,Awaiting More Feedback

### 🔍 Search Terms

jsdoc declaration merging

### ✅ 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

Ability to merge declarations. 

### 📃 Motivating Example

For example, this is a declaration merge in TS:

```ts
export const Foo = makeFooClass()
export type Foo = InstanceType<typeof Foo>
```

In JS we can't do this. I was hoping for something similar to this to achieve the same:

```js
export const Foo = makeFooClass() // returns a class
/** @export {InstanceType<typeof Foo>} Foo */
```

### 💻 Use Cases

1. What do you want to use this for? To merge declarations in certain cases.
2. What shortcomings exist with current approaches? There's no way to do it AFAICT
3. What workarounds are you using in the meantime? None