sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: material-ui
Issue: [Text Field] Validity pseudo classes should apply styling
Labels: new feature,component: text field

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Summary 💡

MUI should style form inputs on the `:invalid` and `:valid` pseudo classes, similar to how bootstrap works for form validation: https://getbootstrap.com/docs/4.6/components/forms/#validation.

This way, I can use the [native html form validation](https://developer.mozilla.org/en-US/docs/Learn/Forms/Form_validation) and things just work.



### Examples 🌈

E.g., if I have any rendered input under the hood with props like `<input type="text" pattern="[0-9]*" required/>`, any time the value changes to an empty value or a non number, it will be marked as `:invalid`. This should auto-style the input into the error state as described [here](https://mui.com/components/text-fields/#validation). Bonus points if you could also set custom validity messages on props that in turn calls `setCustomValidity(message)`.

### Motivation 🔦

Without this feature, I'm stuck doing manual form validation. That is, I am required to have some function `onValidate` that will check the form input validity and toggle the error property. If MUI worked this way, I could just use all native html input validation properties and things would just work.
Repository: rust
Issue: Can't compile libc on m68k-unknown-linux-gnu: LLVM ERROR: unable to allocate function return #2
Labels: A-LLVM,I-ICE,T-compiler,O-motorola68k

Building libc for m68k-unknown-linux-gnu currently fails an LLVM error:

```
Building stage1 std artifacts (x86_64-unknown-linux-gnu -> m68k-unknown-linux-gnu)
   Compiling core v0.0.0 (/data/home/glaubitz/rust-m68k/library/core)
   Compiling compiler_builtins v0.1.67
   Compiling libc v0.2.116
   Compiling memchr v2.4.1
   Compiling unwind v0.0.0 (/data/home/glaubitz/rust-m68k/library/unwind)
   Compiling std v0.0.0 (/data/home/glaubitz/rust-m68k/library/std)
   Compiling rustc-std-workspace-core v1.99.0 (/data/home/glaubitz/rust-m68k/library/rustc-std-workspace-core)
   Compiling alloc v0.0.0 (/data/home/glaubitz/rust-m68k/library/alloc)
   Compiling cfg-if v0.1.10
   Compiling adler v0.2.3
   Compiling rustc-demangle v0.1.21
LLVM ERROR: unable to allocate function return #2
error: could not compile `libc`
warning: build failed, waiting for other jobs to finish...
LLVM ERROR: unable to allocate function return #2
rustc: /data/home/glaubitz/llvm-project/llvm/lib/Target/M68k/M68kInstrInfo.cpp:763: virtual void llvm::M68kInstrInfo::storeRegToStackSlot(llvm::MachineBasicBlock&, llvm::MachineBasicBlock::iterator, llvm::Register, bool, int, const llvm::TargetRegisterClass*, const llvm::TargetRegisterInfo*) const: Assertion `MF.getFrameInfo().getObjectSize(FrameIndex) == 4 && "Stack slot too small for store"' failed.
rustc exited with signal: 6 (core dumped)
rustc: /data/home/glaubitz/llvm-project/llvm/lib/Target/M68k/M68kInstrInfo.cpp:763: virtual void llvm::M68kInstrInfo::storeRegToStackSlot(llvm::MachineBasicBlock&, llvm::MachineBasicBlock::iterator, llvm::Register, bool, int, const llvm::TargetRegisterClass*, const llvm::TargetRegisterInfo*) const: Assertion `MF.getFrameInfo().getObjectSize(FrameIndex) == 4 && "Stack slot too small for store"' failed.
rustc exited with signal: 6 (core dumped)
rustc: /data/home/glaubitz/llvm-project/llvm/lib/Target/M68k/M68kInstrInfo.cpp:763: virtual void llvm::M68kInstrInfo::storeRegToStackSlot(llvm::MachineBasicBlock&, llvm::MachineBasicBlock::iterator, llvm::Register, bool, int, const llvm::TargetRegisterClass*, const llvm::TargetRegisterInfo*) const: Assertion `MF.getFrameInfo().getObjectSize(FrameIndex) == 4 && "Stack slot too small for store"' failed.
rustc exited with signal: 6 (core dumped)
rustc: /data/home/glaubitz/llvm-project/llvm/lib/CodeGen/LiveVariables.cpp:129: void llvm::LiveVariables::HandleVirtRegUse(llvm::Register, llvm::MachineBasicBlock*, llvm::MachineInstr&): Assertion `MRI->getVRegDef(Reg) && "Register use before def!"' failed.
rustc exited with signal: 6 (core dumped)
error: build failed
Build completed unsuccessfully in 0:06:30
```

Not sure whether this is a Rust or an LLVM bug.

CC @mshockwave @0x59616e @jrtc27 @ricky26 @AnnikaCodes
Repository: vscode
Issue: Debug Console Filter is a bit confusing
Labels: feature-request,debug,debug-console

The Debug Filter, on the top right corner of the Debug Console output window, could use a little TLC in my opinion. I think it is a bit confusing and is missing some key functionality. 

***Better indication filter is active***
The main problem I have with the window is that when you quickly look at your debug output, it isn't immediately clear that a filter might be active. Dozens of times I wondered: where the heck is my output? Only to find out that a filter was active and I forgot about it.

***Clear filter button missing***
Located directly next to the filter is an icon, meant for clearing the whole debug console. But intuitively I thought it was to clear the filter. Accidentally pressing that while in the middle of an important debugging session is definitely not great, and has caused some cursing on my part :) It would be great if you could add a (X) button inside the filter box, so that mistake is not made again

***Cursor moves to end when clearing filter***
There is no "find" option in the Debug Console, only filter is supported. But I often just want to search for a very specific string inside a large chunk of debug output. When using the filter for that, it indeed shows me that string. But I have no context. I want to know what was also being output near that found string. So intuitively I clear the filter and bam, the output is back to the full output again and I have literally no idea on where to find that string again. 

I often find myself just copying all the debug text to a separate window and search in there, which is obviously not ideal.

If there is a way to let the filter behave like a normal search (perhaps switch modes between "Find" or "Filter"?), please let me know as I'm currently often more confused by its current functionality than that it helps me.
Repository: godot
Issue: Exporting packs, patches, and mods did not work on HTML5 exports
Labels: platform:web,topic:porting,needs testing

### Godot version

3.4.2

### System information

Window10, GLES3

### Issue description

I tried splitting the PCK package to make the FIRST load of the HTML5 game faster, and also to update the content quickly, but 
I tried to make the HTML5 game load faster first time by splitting the PCK package and also hoping that it would update the content quickly, but the following code doesn't work, I hope to give me a solution, thanks.
###	print("loading pck!" )
var success = ProjectSettings.load_resource_pack("res://mods/cube.pck")
if success:
var imported_scene:PackedScene = load("res://Spatial.tscn")
self.add_child(imported_scene.instance())
print("load_success")
# # #

### Steps to reproduce

#

### Minimal reproduction project
All the source code was executed in the main scene,  but since the export package too big to be uploaded, I uploaded a brief description of the Markdown file.Just check the code.Haha
[the_func_of_load_resource_pack_Testing.zip](https://github.com/godotengine/godot/files/8054977/the_func_of_load_resource_pack_Testing.zip)
#
Repository: material-ui
Issue: Problem with the latest MUIv5 and classes overrides of nested elements
Labels: package: styles,v5.x migration

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯

Some of the MUI components have sub-components which are mentioned in the CSS section of the component with a statement like: "Styles applied to the deleteIcon element.". But when migrating from MUIv4 to v5, I found out that I cannot keep using it the same way in `classes` props because of increased specificity. There is no additional comment for such cases and it doesn't seem to be specific only to `Chip` component.

In the minimal example below I'm using `makeStyles` from `tss-react`, but I think the issue will be there even with other solutions.

```ts
const useStyles = makeStyles()((theme) => ({
  root: {
    backgroundColor: theme.palette.primary.main,
  },
  deleteIcon: {
    color: theme.palette.primary.contrastText,
  },
}));

function App() {
  const { classes } = useStyles();

  return (
    <Chip label="Chip with classes" onDelete={() => {}} classes={classes} />
  );
}
```

### Expected behavior 🤔

Here's a demo page with actual & expected sections: https://muiv5-problem-with-classes.vercel.app/

In a nutshell, I would expect that I can pass `deleteIcon` in `classes` and be able to override `color` to whatever I need.

### Steps to reproduce 🕹

https://github.com/synaptiko/muiv5-problem-with-classes/blob/master/src/App.tsx

FYI, I've created similar issue on `tss-react` as I initially thought it's related to that library: https://github.com/garronej/tss-react/issues/62.

### Context 🔦

I'd like an easy way to override styles of nested elements/components, without guessing where specificity need to be increased. According to documentation my understanding was that `classes` is exposed for that purpose.

If it's not technically possible then I would at least expect some note in the CSS section of each component.

Sorry if it's a duplicate of https://github.com/mui/material-ui/issues/28664 but it seems slightly different to me. I can also provide other components for which I had the same issue.

### Your environment 🌎

<details>
  <summary>`npx @mui/envinfo`</summary>

```
  System:
    OS: Linux 5.16 Arch Linux
  Binaries:
    Node: 17.3.0 - /usr/bin/node
    Yarn: 1.22.17 - /usr/bin/yarn
    npm: 8.4.1 - /usr/bin/npm
  Browsers:
    Chromium: 98.0
    Firefox: 97.0
  npmPackages:
    @emotion/react: ^11.7.1 => 11.7.1 
    @emotion/styled: ^11.6.0 => 11.6.0 
    @mui/base:  5.0.0-alpha.68 
    @mui/material: ^5.4.1 => 5.4.1 
    @mui/private-theming:  5.4.1 
    @mui/styled-engine:  5.4.1 
    @mui/system:  5.4.1 
    @mui/types:  7.1.1 
    @mui/utils:  5.4.1 
    @types/react: ^17.0.20 => 17.0.39 
    react: ^17.0.2 => 17.0.2 
    react-dom: ^17.0.2 => 17.0.2 
    typescript: ^4.4.2 => 4.5.5 
```
</details>
Repository: storybook
Issue: Documentation updates for Essentials Documentation category
Labels: documentation

An average developer doesn't know what an "essential" addon is. That makes it tough to understand what the benefits of the addons are and to understand how to use them. 

What we can do to mitigate this issue: 
- Rename "essential addons" to "tools" 
- Move "tools" into "Writing stories" section

Why
An average developer doesn't know what an "essential" addon is. That makes it tough to understand what the benefits of the addons are and to understand how to use them. Bringing in the following benefits:
- Showcase the value of essential addons when users need it most (writing stories)
- Streamlines the documentation organization and reduces noise from the top-level categories
Repository: pytorch
Issue: Add NCCL and MPI version printing to torch.utils.collect_env
Labels: module: collect_env.py,triaged,module: mpi,enhancement,module: nccl

### 🚀 The feature, motivation and pitch

When working on distributed training jobs on multiple node setup, the version mismatch for NCCL and MPI poses many issues. It will be great if we can start printing output of the versions for NCCL and MPI as part of `python -m torch.utils.collect_env` and also plan to add a utility for checking version compatibility of dependent libraries

### Alternatives

_No response_

### Additional context

_No response_
Repository: storybook
Issue: Migration of Structuring your Storybook into the official documentation
Labels: documentation

The recent release of the "Structuring your Storybook" [blog post](https://storybook.js.org/blog/structuring-your-storybook/) presented some valuable insights that our readers can use while creating/publishing their Storybook. With this, we can incorporate it into our official documentation and showcase best practices that can be adopted.

What needs to happen in terms of documentation:
- We have a couple of options to address this:
   1. Add the documentation within the Sharing Section, before Publishing.
   2. Create a new Sidebar category named How-tos and guides as mentioned in (#17495).
 - Create the documentation featuring valuable information (e.g., how to set up a contribution guide to their Storybook, a changelog, etc.)


Before this change can happen, we will need to make some changes to our UI, more specifically to the way Storybook organizes /structures the stories, as the way it's currently set up is misidentifying the components containing folders. As an example:

<img width="640" alt="component-level-structure-1" src="https://user-images.githubusercontent.com/22988955/153724741-1b4ffd02-f54d-41d8-a30c-6a0a9a5475ec.png">

If the "Features" element is, in fact, a folder containing component stories, the UI is displaying it incorrectly. 

Addressing this issue will bring additional benefits to our users as they're presented with a cleaner, more streamlined UI.
Repository: PowerToys
Issue: Change border color when not in focus
Labels: Idea-Enhancement,Product-Always On Top

### Description of the new feature / enhancement

Ok I admit I didn't quite get the use case immediately, but ever since WFT I now rely on 100% on the windows calculator and it has made me bat shit crazy.  Saw some blog about it and I'm all in.  

It would be nice if the border was different when it has facus vs does not have focus

### Scenario when this would be used?

??????????????????????????????????????????

### Supporting information

?????????????????????????????????????????
Repository: flutter
Issue: [Android] TextField text selection toolbar not shown on long Press
Labels: a: text input,platform-android,framework,f: material design,platform-web,has reproducible steps,P2,found in release: 2.10,found in release: 2.11,team-design,triaged-design

### **Steps to Reproduce**

1. Have a TextField in a Flutter web app 
2. Open the app with Android web browser (Chrome) 
3. Tap the field and enter text
4. Short press a word to display the handle
5. Long press to copy/cut

**Expected results:**

- On short press, only one handle should be displayed (the light blue native handle)
- On long press, only native handles should be displayed and a toolbox should be displayed for copying/cutting

**Actual results:**

- On short press, the native handle is drawn behind the Flutter handle (there are 2 handles)
- On long press, only Flutter handles are displayed. The copy/cut toolbox is not displayed.
- If i long press on the Flutter's handles, the native handles are displayed and the copy/cut toolbox is displayed.

**Information:**

- The result is the same on Android emulators, on a Google Pixel 6 Pro and on an Xperia XZ1 Compact (Android 9).
- The result is the same on the examples in the documentation (like [https://api.flutter.dev/flutter/material/TextField-class.html](url))
- If I run the app on an Android device with Flutter run, everything works fine except the issues in #[98265](https://github.com/flutter/flutter/issues/98265)
- The result seems to work fine on Safari of iOS simulators (Cupertino handles).

**Code:**

```dart
import 'package:flutter/material.dart';

class TestTextField extends StatelessWidget {
  const TestTextField({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        body: SafeArea(
          child: TextField(
            minLines: null,
            maxLines: null,
          ),
        ),
      ),
    );
  }
}
```

**Flutter doctor:**
```
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 2.10.1, on macOS 12.1 21C52 darwin-arm, locale fr-FR)
[✓] Android toolchain - develop for Android devices (Android SDK version 32.0.0-rc1)
[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2020.3)
[✓] VS Code (version 1.64.2)
[✓] Connected device (2 available)
[✓] HTTP Host Availability

• No issues found!
```


https://user-images.githubusercontent.com/64663143/153729346-099a42ab-f1c4-4fe9-951b-3e814af0c490.mov
Repository: godot
Issue: intersect_point does not work with trimesh / ConcavePolygonShape or CSG nodes with Use Collision enabled
Labels: bug,confirmed,topic:physics,topic:3d

### Godot version

3.4.3

### System information

windows 10

### Issue description

When trying to find if a point is inside a ConcavePolygonShape, it fails to find any. Instead it only finds intersection if the point is directly on the surface of the mesh.

### Steps to reproduce

Perform the operation: "Create Trimesh Collision Sibling" to create a collision shape of a model.
Then try to perform an intersection_point within it.
It will fail to return any results.


### Minimal reproduction project

[pointBugTest.zip](https://github.com/godotengine/godot/files/8054836/pointBugTest.zip)
Repository: flutter
Issue: Add fit, alignment properties to CircleAvatar
Labels: c: new feature,framework,f: material design,c: proposal,has partial patch,team-design,triaged-design

## Use case
backgroundImageFit > Chaning the default fit for background image to values other than the default (BoxFit.cover)
backgroundImageAlignment > Chaning the default alignment for background image to values other than the default (Center)

foregroundImageFit > Chaning the default fit for foreground image to values other than the default (BoxFit.cover)
foregroundImageAlignment > Chaning the default alignment for foreground image to values other than the default (Center)

Just like on Image widgets, we need to choose the alignment in which we scale the image to fit the circle or change the fit entirely (like fit Height or fit Width).

## Proposal
Add CircleAvatar optional parameters [ Alignment, Fit ] with the default values as is now for both background/foreground images.
Repository: go
Issue: x/crypto/ssh: host key algorithm selection prefers DSA over ED25519
Labels: NeedsInvestigation

When a server provides both a DSA host key and an ED25519 host key, the Go ssh library will select DSA instead. But DSA has been deprecated in OpenSSH (and in other libraries, I suppose).

This is because in crypto/ssh/common.go, ED25519 is at the end of `supportedHostKeyAlgos`, which is supposed to be in preference order:

```go
var supportedHostKeyAlgos = []string{
	CertSigAlgoRSASHA2512v01, CertSigAlgoRSASHA2256v01,
	CertSigAlgoRSAv01, CertAlgoDSAv01, CertAlgoECDSA256v01,
	CertAlgoECDSA384v01, CertAlgoECDSA521v01, CertAlgoED25519v01,

	KeyAlgoECDSA256, KeyAlgoECDSA384, KeyAlgoECDSA521,
	SigAlgoRSASHA2512, SigAlgoRSASHA2256,
	SigAlgoRSA, KeyAlgoDSA,

	KeyAlgoED25519, // <-- lowest preference, unlike the other algo list constants that place ED25519 much higher
}
```
Repository: vscode
Issue: [css] Allow extensions to choose to use whether to use CSS default data provider
Labels: help wanted,feature-request,css-less-scss

<!-- ⚠️⚠️ 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. -->
The CSS language service has had the parameter of whether to use the default data provider ([`useDefaultDataProvider`](https://github.dev/microsoft/vscode-css-languageservice/blob/c29c007451cd10d3c565250efd8aba44c54b2485/src/languageFacts/dataManager.ts#L36-L37)) for long while now and more recently [the exposing of `css.customData` for extensions](https://github.com/microsoft/vscode/issues/135459) which is lovely. However the bundled `css-language-features` extension [sets data providers with `useDefaultDataProvider` forced to `true`](https://github.dev/microsoft/vscode/blob/c64daad0ff2e7b5fd5e423e54af8a1da7aa2d712/extensions/css-language-features/server/src/cssServer.ts#L204).

Considering these go together in setting data providers, it would be fantastic to expose `useDefaultDataProvider` in the same way. This would make it very simple for extensions to support languages/frameworks that deviate from spec. Seems like it would be simple to do as well.
Repository: opencv
Issue: vs 2022 + opencv 4.5.5 load opencv_highgui_gtk455_64.dll => FAILED
Labels: question (invalid tracker)

<!--
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/
   -->