sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: Request: option to disable rounded corners for normal GUI windows in Win11
Labels: Idea-New PowerToy,Product-Tweak UI Design

### Description of the new feature / enhancement

Windows 11 introduced rounded corners on most windows.  I'd like the option to go back to the Metro-style squared corner windows in Windows 8 through Windows 10.  I really loved the aesthetic -- the Metro design language was beautiful and uniquely Microsoft.  Squared corners, in addition to high contrast, was what made it special.  I can adjust contrast mostly as needed by color selection, but I can't disable rounded corners.  :-(

### Scenario when this would be used?

Anybody who prefers squared windows.

### Supporting information

https://www.elevenforum.com/t/can-i-have-square-corners-in-windows-11.1186/
Repository: ant-design
Issue: Menu增加fieldNames对items数据可以进行映射
Labels: 💡 Feature Request,Inactive

### What problem does this feature solve?

解决数据渲染的时候的映射问题，可以替换label,key, icon, children为数据其他字段

### What does the proposed API look like?

比如我的数据是：

```json
{
  title: "xx",
  iconUrl: "xx",
  id: "xxx",
  child: []
}
```

期望的API如下：

```json
fieldNames={{
  label: "title",
  icon: "iconUrl",
  key: "id",
  children: "child"
}}
```

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: flutter
Issue: List/Grids that can't actually scroll should warn that repaint boundaries are being added, or just avoid adding them.
Labels: framework,f: scrolling,customer: money (g3),P2,team-framework,triaged-framework

Internal: b/292548368

The app at the bottom of this issue adds repaint boundaries by default for the grid view, even though it is not scrollable by itself and is shrink wrapped. This means that some of the entries will be chosen as raster cache entries, but in reality the whole thing could/should be raster cached.

The default behavior of adding repatint boundaries makes sense for grid views that actually scroll. It does not make sense when the grid view is just being used as a static layout mechanism (effectively a set of rows and columns). We should warn developers about this case and encourage them to turn off repaint boundaries for this case.

/cc @flar @jonahwilliams @goderbauer

```dart
import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Material App',
      home: Home(),
    );
  }
}

class Home extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: Center(
        child: SizedBox(
          width: 350,
          child: ListView(
            children: <Widget>[
              Container(
                color: Colors.red,
                height: 45,
                width: 350,
                child: const Text('Header!'),
              ),
              const Divider(),
              Container(
                color: Colors.blue,
                height: 240,
                width: 350,
                child: const Text('Foo!'),
              ),
              const Divider(),
              GridView.count(
                crossAxisCount: 4,
                crossAxisSpacing: 20,
                mainAxisSpacing: 20,
                shrinkWrap: true,
                children: const <Widget>[
                  CircleAvatar(child: Text('AB')),
                  CircleAvatar(child: Text('CD')),
                  CircleAvatar(child: Text('EF')),
                  CircleAvatar(child: Text('GH')),
                  CircleAvatar(child: Text('BA')),
                  CircleAvatar(child: Text('DC')),
                  CircleAvatar(child: Text('FE')),
                  CircleAvatar(child: Text('HG')),
                ],
              ),
              const Divider(),
              Container(
                color: Colors.yellow,
                height: 140,
                width: 350,
                child: const Text('Bar!'),
              ),
              Container(
                color: Colors.green,
                height: 45,
                width: 350,
                child: const Text('Footer!'),
              ),
            ],
          ),
        ),
      ),
    );
  }
}
```
Repository: PowerToys
Issue: Search files for terms which do not appear in the file
Labels: Idea-New PowerToy,Needs-Triage

### Description of the new feature / enhancement

Many documents should appear in a search, but they do not contain the search term.
For example, some parts or owner's manuals apply to a group of items, but the manual does not contain any specific item numbers.
If there are 2 groups of widgets, Group A consists of items 1, 2, and 3.  Group B consists of items 4, 5, and 6.
There is a Group A and a Group B manual, neither of which mentions any item numbers.  If there is a later item 7 that is a Group A item, the manual doesn't have to be reprinted.
I can see 2 ways to fix this.
One would be to add an invisible text block to the file containing the search terms.  The terms would be found by Windows search but would not add any pages to a print-out.
A second way would be to add a field to the document in the File Explorer, similar to the way fields have been added to digital photos  The field would be searchable.


### Scenario when this would be used?

I have thousands of documents that need this added information. 
I need any easy way to add it.
Then it will be searched by many people, so an easy way to search is also needed.

### Supporting information

_No response_
Repository: react-native
Issue: iOS - Image files included in outbound network requests are significantly larger than the original files
Labels: Platform: iOS,Component: Image,Type: Old Architecture,Never gets stale

### Description

When creating a `multipart/form-data` request with a `FormData` object whose parts contain a `uri` property pointing to an image file, the resulting network request is much (~3-4 times) larger than the original image file. 

This issue only occurs on iOS. This is a duplicate of #27099, which has been closed but is not fixed.

### Version

0.67.3

### Output of `npx react-native info`

```
System:
    OS: macOS 12.3.1
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 973.39 MB / 32.00 GB
    Shell: 3.3.1 - /usr/local/bin/fish
  Binaries:
    Node: 16.14.2 - /usr/local/bin/node
    Yarn: 1.22.17 - /usr/local/bin/yarn
    npm: 8.8.0 - /usr/local/bin/npm
    Watchman: 2022.03.21.00 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.11.3 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: DriverKit 21.4, iOS 15.4, macOS 12.3, tvOS 15.4, watchOS 8.5
    Android SDK:
      API Levels: 28, 29, 30, 31
      Build Tools: 28.0.3, 29.0.2, 29.0.3, 30.0.1, 30.0.2, 30.0.3, 31.0.0, 32.0.0, 32.1.0
      System Images: android-23 | Google APIs Intel x86 Atom_64, android-24 | Google APIs Intel x86 Atom, android-24 | Google Play Intel x86 Atom, android-26 | Google Play Intel x86 Atom, android-28 | Google Play Intel x86 Atom, android-29 | Google Play Intel x86 Atom, android-30 | Google Play Intel x86 Atom, android-31 | Google Play Intel x86 Atom_64
      Android NDK: Not Found
  IDEs:
    Android Studio: 2021.1 AI-211.7628.21.2111.8309675
    Xcode: 13.3.1/13E500a - /usr/bin/xcodebuild
  Languages:
    Java: 11.0.11 - /usr/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 17.0.2 => 17.0.2
    react-native: 0.67.3 => 0.67.3
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found
```

### Steps to reproduce

Obtain a URI to any on-disk image, call it `fileUri`.
Create a `FormData` object with the file uri:
```js
const formData = new FormData();
formData.append('file', { type: 'application/octet-stream', name: 'image.jpeg', uri: fileUri });
```
Then, make a request with that form data:
```js
const response = await fetch('https://postman-echo.com/post', { method: 'POST', body: formData })
```
Observe the content-length of the request headers if you control the server, or in this example, observe the response body from postman-echo.

### Snack, code example, screenshot, or link to a repository

Snack demonstrating issue (and current workaround): https://snack.expo.dev/@httpriestess/image-upload-size-repro

It posts an image file to postman-echo, and then displays the content-length header that postman-echo returns.
Repository: flutter
Issue: [web] flutter.js not generated sporadically
Labels: tool,platform-web,P3,team-web,triaged-web

@hterkelsen and @kevmoo have reported that the `flutter.js` file might not end up being generated in their `build/web` directories.

This can break the initialization of a flutter web app if it uses the new embedding method.

## Steps to Reproduce

1. In `flutter master`
2. `flutter build web`
3. ... ?

**Expected results:** <!-- what did you want to see? -->

`flutter/build` should contain a `flutter.js` file (alongside others)

**Actual results:** <!-- what did you see? -->

`flutter.js` missing in `flutter/build`.

<details>
<summary>Code sample (N/A)</summary>
</details>

<details>
  <summary>Logs (N/A)</summary>
</details>

(Creating this as a P1, as it might require a hotfix of the flutter tool if/when confirmed)
Repository: storybook
Issue: addon-docs: Description from docgen doesn't work when using React.memo
Labels: bug,react,argtypes

**Describe the bug**
I am trying show the description from a memoized component in docs page.  Running `react-docgen` cli is possible to confirm that description it's being exported as expected, but it is not displayed at docs page.

**To Reproduce**
Add description to any component and export it memoized. Ex:
```jsx
/**
 * This is a Button Wrapper
 */
const Button = props => <button {...props} />

export default React.memo(Button)
```

**System**
  System:
    OS: macOS 12.3.1
    CPU: (8) arm64 Apple M1 Pro
  Binaries:
    Node: 16.13.1 - ~/.nvm/versions/node/v16.13.1/bin/node
    Yarn: 1.22.18 - ~/.nvm/versions/node/v16.13.1/bin/yarn
    npm: 6.14.6 - ~/projects/sandbox/node_modules/.bin/npm
  Browsers:
    Chrome: 101.0.4951.54
    Safari: 15.4
  npmPackages:
    @storybook/addon-essentials: ^6.4.22 => 6.4.22
    @storybook/react: ^6.4.22 => 6.4.22
    @storybook/storybook-deployer: ^2.8.10 => 2.8.10

**Cause of the issue**
The props are extracted properly by a conditional that checks if the component is memoized in [docs/extractProps](https://github.com/storybookjs/storybook/blob/23ac884c4984aa24527b24de9964be0ee03f731f/app/react/src/client/docs/extractProps.ts#L34). In case, it uses `component.type` instead.
The same conditional was not implemented for description. [Description Block](https://github.com/storybookjs/storybook/blob/8570188f6a623cf31841f1b25179cb593ccae6e1/addons/docs/src/blocks/Description.tsx#L68) calls [extractComponentDescription](https://github.com/storybookjs/storybook/blob/8570188f6a623cf31841f1b25179cb593ccae6e1/lib/docs-tools/src/argTypes/docgen/extractDocgenProps.ts#L104) that always [use the component](https://github.com/storybookjs/storybook/blob/8570188f6a623cf31841f1b25179cb593ccae6e1/lib/docs-tools/src/argTypes/docgen/utils/docgenInfo.ts#L19) to obtain the description.

**Workaround**
Set `Component.type` on CSF export at story file. Ex:
```jsx
export default {
  title: 'Button',
  component: Button.type,
}
```
Repository: pytorch
Issue: TYPEIGNORE lint run locally disagrees with CI
Labels: module: lint,triaged,module: macos

### 🐛 Describe the bug

https://github.com/pytorch/pytorch/pull/76735 is failing TYPEIGNORE lint https://github.com/pytorch/pytorch/runs/6291285337?check_suite_focus=true but when I check out the package and run it locally the TYPEIGNORE lint passes. This is on OSX. cc @malfet @albanD @suo

### Versions

master
Repository: PowerToys
Issue: Ternary Logic and Ternary Computing
Labels: Idea-Enhancement,Run-Results (Programs),Run-Plugin

### Description of the new feature / enhancement

Please include a conversion between binary and different ternary base systems including balanced ternary (-1, 0, and 1) and ternary number system (0,1,2).


### Scenario when this would be used?

DevToys.app has a similar feature for base conversion and this would be a good way to discuss radix efficiency and base 3 computers (3 is closer to 2.7182818284590, Euler's number and is the most efficient integer base).

### Supporting information

_No response_
Repository: pytorch
Issue: Windows CUDA TTS tracking task
Labels: module: ci,triaged

Our goal for CI TTS started at 3hrs this half and was not far from there at the start of 2022. However, now we are noticing some pretty large regressions where our Windows jobs have a TTS of 4hrs (per shard!). At peak times, the TTS goes higher due to stressed queuing times. 

Actionable steps:
- Increase our pool of available Windows runners --> if feasible, this would be the ideal solution.
- Aggressively shard --> this is fine but there is an overhead we'd be eating @clee2000 
- Remove Windows CUDA job from PRs --> this would not be ideal as Windows CUDA build signal is valuable to have on pull requests. We used to have smoke tests to not test so much on Windows GPU machines, but those were not worth maintaining as the process of maintaining them was mostly manual.
- Be able to delineate TTS on the job level so we can confirm results in our metrics (compared to spot checks)

cc @seemethere @malfet @pytorch/pytorch-dev-infra
Repository: storybook
Issue: ArgsTable of={Component} cannot find propTypes
Labels: bug,block: argstable

**Describe the bug**

I've followed directions outlined here https://github.com/storybookjs/storybook/issues/12576 to export my wrapped components directly, however my `<ArgsTable of={Component/}>` component still renders that "No inputs found for this component"

However, when I console.log the component itself, the propTypes + defaultProps seem to be plainly available. 

The way I read this, it should "just work"?
> If you need, you can customize what is displayed in the ArgsTable by extending the ArgTypes data, unless you're using the ArgsTable of={component} />. In this case, Storybook will infer the data automatically from the component.

**Screenshot**

![Screen Shot 2022-05-04 at 1 49 49 PM](https://user-images.githubusercontent.com/15896334/166805210-f5eb4d46-227c-436b-a729-27302727fbc7.png)

I've scoured the issues here, tried various webpack configs, babel configs but nothing seems to clear my issue. I'm working in a monorepo with Expo + React Native + React + storybook, so there's likely some wires crossed somewhere. 

**System**
Please paste the results of `npx sb@next info` here.

<details>
  <summary>Click for System Info</summary>

**Environment Info:**

  System:
    OS: macOS 12.3.1
    CPU: (10) x64 Apple M1 Pro
  Binaries:
    Node: 12.22.0 - ~/.nvm/versions/node/v12.22.0/bin/node
    Yarn: 1.22.18 - /opt/homebrew/bin/yarn
    npm: 6.14.11 - ~/.nvm/versions/node/v12.22.0/bin/npm
  Browsers:
    Chrome: 100.0.4896.127
    Firefox: 100.0
    Safari: 15.4
</details>
Repository: godot
Issue: DEPTH_TEXTURE broken on mobile GLES 3
Labels: bug,platform:android,topic:rendering,needs testing,topic:3d

### Godot version

3.5 beta 5

### System information

Android 12, Adreno 640

### Issue description

When I exported a project using GLES 3, proximity fade materials vanished. I converted the spatial material to a shader material and set it to display the DEPTH_TEXTURE and it's is pure black. Depth texture seems correct on GLES 2, but it's precision is too low to be usable in large meshes.

On PC it look like this:
![image](https://user-images.githubusercontent.com/25274301/166805331-fee96852-5411-46b4-a482-7ec13fc9d40f.png)
On mobile it look like this
![Screenshot_2022-05-04-15-52-05-865_org godotengine proximityfadeissue](https://user-images.githubusercontent.com/25274301/166805735-70ab8463-c533-40e5-8d3d-68a7e23b93ad.jpg)
PC with GLES 2:
![image](https://user-images.githubusercontent.com/25274301/166806234-fa6dc927-9852-4a33-b507-a03052dd5a64.png)
Mobile with GLES 2:
![Screenshot_2022-05-04-15-56-08-007_org godotengine proximityfadeissue](https://user-images.githubusercontent.com/25274301/166806350-93937c4a-99e5-4c02-a284-b6150eb5a7c0.jpg)




### Steps to reproduce

- Add any mesh to a scene.
- Add a spatial material with proximity fade to the mesh.
- Export to mobile using GLES 3 renderer.

### Minimal reproduction project

[ProximityFadeIssue.zip](https://github.com/godotengine/godot/files/8626301/ProximityFadeIssue.zip)
Repository: godot
Issue: No warning, but broken AnimationTree due to shared StateMachinePlayback
Labels: topic:animation

### Godot version

3.4.4.stable.mono.official

### System information

Windows 10, but unrelated

### Issue description

In the attached MRP 'TestScene.tscn' works just fine - playing with the blend parameter in the AnimationTree.
But inside Human.tscn, adjusting the blend slider or trying to click-travel to any state inside the Statemachines doesn't work and just prints cryptic and seemingly nonsensical errors.

By inspecting the tscns and comparing them, i found that at some point there must have been a bug, git error or something else that seems to have assigned a single StateMachinePlayback subresource to both StateMachines in the tree, meaning they share it, but shouldn't.

Now, the bug here is obviously how this could have happened (?). As i can't remember willingly sharing the reference.
But as it's probably very hard to find a potential source here without any hint as to what to look out for, it is probably more helpful to classify the very non-helpful error messages as bugs and try to improve them. In the same way it's hard to even notice them when the AnimationTree editor and the output  share the same bottom panel and one can only swap between them - meaning when changing or clicking on things and errors pop up they cannot be timely correlated.

And without manually traversing the tscns it would be almost impossible to spot this error (and it still is even when doing so).

### Steps to reproduce

Open TestScene.tscn and change the blend parameter, notice everything working fine.
Open Human.tscn and do the same, or actually just anything that influences the preview playback state and notice nothing working correctly.

### Minimal reproduction project

[MRP.zip](https://github.com/godotengine/godot/files/8626709/MRP.zip)
Repository: terminal
Issue: Move InputStateMachineEngine and InteractDispatch into Host
Labels: Product-Terminal,Issue-Task,Area-CodeHealth,Priority-3

These things aren't used in Terminal, and get dropped by LTO anyway. The work in #13024 drives `terminal/adapter` and, to an extent, `terminal/parser` closer to being fully-shared components, so maybe we should beef up that boundary.
Repository: pytorch
Issue: Unify torch.ops argument parsing code with PythonArgParser
Labels: triaged,module: __torch_dispatch__,module: python frontend

### 🐛 Describe the bug

They are implementations of the same thing; we should use the same codepath for each. Relevant for https://github.com/pytorch/pytorch/pull/76835 where scalar arguments were not accepted into wrapped tensors.

### Versions

master

cc @Chillee @ezyang @zou3519 @albanD @samdow
Repository: material-ui
Issue: [Box] Always re-renders sx is changed on the forward ref Div
Labels: new feature,performance,component: Box

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯

Trying to mitigate re-rendering with Box. Normally wrapping in React.memo will do the job for most components

However with Box and Stack they forward their props to a div and so the Box/Stack won't re-render but the `div` will
causing the area to re-render always as well. Always getting props updated with `(children, sx)` changes were the sx is
always changing even then the `sx` value is memoized with `useMemo` which works on normal components.

```javascript
const BOX = React.memo((props) => <Box {...props}/>

function MyComponent() {
   const [state, dispatch] = useReducer({input: ''}, (state, action) => ({...state, ...action}))
   
   const handleChange = useCallback((event) => dispatch({input: event.target.value}), [dispatch])
   
   const width = useMemo(() => ({minWidth: 120}), [])
   return (
   <>
      <Box>
         <TextField
           label={'input'}
           value={state.input}
           onChange={handleChange}
         />
      </Box>
      <Box sx={width}>
          Hello
      </Box>
   </>
   )
}
```

### Expected behavior 🤔

For the wrapping of `Box` or `Stack` with `React.memo` to not cause re-rendering for that component if their props do not change.


### Steps to reproduce 🕹

Steps:

1. Make a component
2. have an input or something that changes the components state to cause a component to re-render
3. have a `Box` or `Stack` wrapped with React.memo with a useMemo sx prop 
4. using the React DevTools Profiler run some input changes and pause profile check and see that in fact the Box and Stack re-rendered


### Context 🔦

There looks to be an issue with the forward ref for Box and Stack

Wanting to add React.memo to Box/Stack as to not always causing a re-render on these components and their children because of them wrapping their children.

I am not completely sure this is a super big deal but wanted to point it out. Its not that its a huge issue its usually .1 ms for each of these to render but if you have a lot that can be a problem. But was wondering if other components might have this issue. 

### Your environment 🌎

<details>
  <summary>`npx @mui/envinfo`</summary>

```
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.
```
</details>