sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: Rename DropdownButtonFormField.value to initialValue
Labels: c: new feature,framework,f: material design,c: proposal,team-design,triaged-design

## Explaination
Like TextFormField, DropdownButtonFormField is "A convenience widget that makes a DropdownButton into a FormField."
FormField(s) maintains the current state internally, you only pass the initial value (like TextFormField)

& further more in the implementation it's just setting initialValue: value.
I think it's confusing because value mean that you can change the state from outside which is not the case.

So it should be renamed to initalValue ?

## Screenshot of the implementation
![image](https://user-images.githubusercontent.com/23477886/117924018-5fdd4380-b2f5-11eb-916c-0ae212e6aab5.png)


```
[✓] Flutter (Channel stable, 2.0.4, on Microsoft Windows [Version 10.0.19042.928], locale en-US)
    • Flutter version 2.0.4 at C:\flutter
    • Framework revision b1395592de (6 weeks ago), 2021-04-01 14:25:01 -0700
    • Engine revision 2dce47073a
    • Dart version 2.12.2

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.0)
    • Android SDK at C:\Android\Sdk
    • Platform android-30, build-tools 30.0.0
    • ANDROID_HOME = C:\Android\Sdk
    • Java binary at: D:\Setups\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

[✓] Android Studio (version 4.1.0)
    • Android Studio at D:\Setups\Android\Android Studio
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[✓] IntelliJ IDEA Community Edition (version 2019.3)
    • IntelliJ at C:\Program Files\JetBrains\IntelliJ IDEA Community Edition 2019.1.1
    • Flutter plugin version 44.0.3
    • Dart plugin version 193.6911.31

[✓] IntelliJ IDEA Community Edition (version 2020.2)
    • IntelliJ at C:\Program Files\JetBrains\IntelliJ IDEA Community Edition 2020.1.1
    • Flutter plugin version 49.0.4
    • Dart plugin version 202.6397.47

[✓] IntelliJ IDEA Community Edition (version 2021.1)
    • IntelliJ at C:\Program Files\JetBrains\IntelliJ IDEA Community Edition 2020.3.2
    • Flutter plugin version 56.0.5
    • Dart plugin version 211.7233

[✓] VS Code (version 1.56.0)
    • VS Code at C:\Users\kirolous.nashaat\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.22.0

[✓] Connected device (3 available)
    • Android SDK built for x86 (mobile) • emulator-5554 • android-x86    • Android 10 (API 29) (emulator)
    • Chrome (web)                       • chrome        • web-javascript • Google Chrome 90.0.4430.212
    • Edge (web)                         • edge          • web-javascript • Microsoft Edge 90.0.818.56

• No issues found!
```

</details>
Repository: godot
Issue: Stuttering when a Skeleton first appears on the screen on GLES3
Labels: discussion,topic:rendering,topic:3d

**Godot version:** v3.3.stable.official

**OS/device including version:** macOS 11.3.1 / Intel Iris Graphics 6100 1536 MB / GLES3

**Issue description:**

Game stutters when a model with skeleton appears on the screen for the first time.

* This does not happen in GLES2
* This also happens in 3.2.3

**Steps to reproduce:**

Run the MRP.

The model will appear on the second rotation. The first rotation is to make sure the SpatialMaterial is cached (All the MeshInstances are using the same SpatialMaterial from the model).

**Minimal reproduction project:** [Skeleton.zip](https://github.com/godotengine/godot/files/6463706/Skeleton.zip)
Repository: pytorch
Issue: Generate special clear error messages for known common misuses in TorchScript
Labels: module: bootcamp,good first issue,triaged,OSS contribution wanted

There are some common misuse patterns in TorchScript that we should issue clear error messages for instead of generating generic error that doesn't capture root cause of error.

Here are a few examples:

- Attempting to construct a `nn.Module` inside TorchScript. This currently errors out because TorchScript would attempt to compile `__init__()` method of module, which usually contains a call to `super()`, which isn't supported. Instead, TS should really recognize that a call to constructor of `nn.Module` is the real problem.
- Calling into known `torch.*` components that are not scriptable. For example, `torch.distributions` currently is not scriptable. If TS sees a call into `torch.distributions` methods, it should warn users about it and prompt them to use `jit.trace` instead.
- Registering new buffers. This isn't supported because it is effectively modifying type of `nn.Module`. We should also give a better error message here.

cc @gmagogsfm
Repository: pytorch
Issue: Python API binding code generation does not need to pack TensorOptions for `xxx_like` generators
Labels: triaged,module: codegen

## 🚀 Feature
Tensor generators like `zeros_like` have kernels that read tensor options like device/dtype from input tensor. Generated code for Python API bindings does not need to redundantly extract same information from input tensor at binding layer. 

## Motivation

Normally extracting the tensor options early at Python binding is harmless. However, this isn't true when program is executed under `jit.trace` which tracks flow of tensors, not other objects. 

Let's look at currently generated code for `zeros_like`:
```
// aten::zeros_like(Tensor self, *, ScalarType? dtype=None, Layout? layout=None, Device? device=None, bool? pin_memory=None, MemoryFormat? memory_format=None) -> Tensor
  auto self = _r.tensor(0);
  const auto options = TensorOptions()
      .dtype(_r.scalartypeWithDefault(2, self.scalar_type()))
      .device(_r.deviceWithDefault(4, self.device()))
......
......

  return wrap(dispatch_zeros_like(self, options, _r.memoryformatOptional(1)));
```
We can see that `device` is extracted and then passed to dispatcher as an explicit argument when user code doesn't specify a device. This eventually results in `device` attribute baked in as constant when calling underlying `aten::zeros_like` kernels. Thus, `jit.trace` can not correctly capture semantics of calls to `zeros_like`.

## Pitch

TensorOptions should not be generated here, or default value of them should be `None` to avoid early specialization according to tensors used at trace time.
Repository: pytorch
Issue: Save checkpoint error
Labels: module: optimizer,module: serialization,triaged

when I save the lr_scheduler.state_dict() to checkpoint, torch.save will report following error

```
Traceback (most recent call last):
  File "pytorch_imagenet_resnet50.py", line 526, in <module>
    save_checkpoint(epoch)
  File "pytorch_imagenet_resnet50.py", line 311, in save_checkpoint
    torch.save(state, filepath)
  File "/THL5/home/wql17/anaconda3/envs/py36/lib/python3.6/site-packages/torch/serialization.py", line 372, in save
    _save(obj, opened_zipfile, pickle_module, pickle_protocol)
  File "/THL5/home/wql17/anaconda3/envs/py36/lib/python3.6/site-packages/torch/serialization.py", line 476, in _save
    pickler.dump(obj)
_pickle.PicklingError: Can't pickle <class 'horovod.torch.optimizer.SGD'>: attribute lookup SGD on horovod.torch.optimizer failed
```


I need some help to solve this problem！

cc @vincentqb @iramazanli @mruberry
Repository: ant-design
Issue: Is it possible to set ant table column width in percantage (px is work) with scroll={{ x: "max-content" }} and empty data? Is it bug or not?
Labels: help wanted,Inactive

- [ ] I have searched the [issues](https://github.com/ant-design/ant-design/issues) of this repository and believe that this is not a duplicate.

### Reproduction link
[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/basic-usage-antd4155-forked-bg2gs)

### Steps to reproduce
1) Add property scroll={{ x: "max-content" }} to table
2) Set first column width equal "25%",
3) Clear property dataSource

### What is expected?
Width of columns equal with full and empty data

### What is actually happening?
Width of columns not equal with full and empty data

| Environment | Info |
|---|---|
| antd | 4.15.5 |
| React | 16.14.0 |
| System | Windows 10 |
| Browser | Google Chrome 90.0.4430.212 |

---
Hey. I have an ant table with 3 columns. First column has 25% width, second is strech, third - 106px. Table has property scroll={{ x: "max-content" }}
When we have a data width of columns work correct, but if we have a empty data width of first and second column is incorrect. 
Width in px on first column work fine with full or empty data?

Is it bug or not? If not, how it can make work correct? Thanks


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: rust
Issue: Suggest restricting a type parameter with clone when attempting to clone out a ref
Labels: A-diagnostics,T-compiler

Not entirely sure about the title, but the code is simple enough:

```rust
pub struct Wrapper<T>(Option<T>);

impl<T> Wrapper<T> {
    pub fn fail(&self) -> Option<T> {
        self.0.as_ref().map(|x| x.clone())
    }
}
```

Yields this error message:
```
error[E0308]: mismatched types
 --> src/lib.rs:5:9
  |
3 | impl<T> Wrapper<T> {
  |      - this type parameter
4 |     fn fail(&self) -> Option<T> {
  |                       --------- expected `Option<T>` because of return type
5 |         self.0.as_ref().clone()
  |         ^^^^^^^^^^^^^^^^^^^^^^^ expected type parameter `T`, found `&T`
  |
  = note: expected enum `Option<T>`
             found enum `Option<&T>`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0308`.
error: could not compile `bonfire`

To learn more, run the command again with --verbose.
```

if you change  the contents of fail to this:

```rust
self.0.as_ref().map(|x| (*x).clone())
```

you get this actually quite helpful error message:
```
error[E0599]: no method named `clone` found for type parameter `T` in the current scope
 --> src/lib.rs:5:38
  |
5 |         self.0.as_ref().map(|x| (*x).clone())
  |                                      ^^^^^ method not found in `T`
  |
  = help: items from traits can only be used if the type parameter is bounded by the trait
help: the following trait defines an item `clone`, perhaps you need to restrict type parameter `T` with it:
  |
3 | impl<T: Clone> Wrapper<T> {
  |      ^^^^^^^^

error: aborting due to previous error

For more information about this error, try `rustc --explain E0599`.
error: could not compile `bonfire`
```
Repository: youtube-dl
Issue: Support async/await in progress hooks
Labels: request

<!--

######################################################################
  WARNING!
  IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################

-->


## Checklist

<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- First of, make sure you are using the latest version of youtube-dl. Run `youtube-dl --version` and ensure your version is 2021.04.26. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Search the bugtracker for similar feature requests: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Finally, put x into all relevant boxes (like this [x])
-->

- [x] I'm reporting a feature request
- [x] I've verified that I'm running youtube-dl version **2021.04.26**
- [x] I've searched the bugtracker for similar feature requests including closed ones


## Description

<!--
Provide an explanation of your issue in an arbitrary form. Please make sure the description is worded well enough to be understood, see https://github.com/ytdl-org/youtube-dl#is-the-description-of-the-issue-itself-sufficient. Provide any additional information, suggested solution and as much context and examples as possible.
-->

Hi
I want to add support of async/await in progress_hooks function
Telethon has already support this feature.
Example in Telethon
```python
async def callback(current, total):
    await client.send_message(@to_user, "test")
    print('Uploaded', current, 'out of', total,
          'bytes: {:.2%}'.format(current / total))



async def main():
    await client.send_file(@to_other_user, "video.mp4", progress_callback=callback)
with client:
    client.loop.run_until_complete(main())
```
and the codes that handle this is in Telethon:
```python
if progress_callback:
    await helpers._maybe_await(progress_callback(pos, file_size))
```
and refer to this method:
```python
async def _maybe_await(value):
    if inspect.isawaitable(value):
        return await value
    else:
        return value
```
but Youtube-dl's not supported:
```python
def _hook_progress(self, status):
    for ph in self._progress_hooks:
        ph(status)

def add_progress_hook(self, ph):
    # See YoutubeDl.py (search for progress_hooks) for a description of
    # this interface
    self._progress_hooks.append(ph)
```
Please add this features to progress hooks.
Thanks
Repository: material-ui
Issue: [List] ListItemIcon color is too strict
Labels: new feature,component: list

<!-- Checked checkbox should look like this: [x] -->

- [x] The issue is present in the latest release.
- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.

## Current Behavior 😯

![image](https://user-images.githubusercontent.com/39504159/117976990-a7cd8c00-b330-11eb-84bc-fec03950e32e.png)

When hovering on a list item containing: ListItemText, ExpandLess and ListItemIcon, we see that the ListItemText and ExpandLess icon receive a hover color. This is fairly simple: 

![image](https://user-images.githubusercontent.com/39504159/117977206-de0b0b80-b330-11eb-88a6-451505f7492e.png)

This doesn't include the ListItemIcon however
## Expected Behavior 🤔

We want this
![image](https://user-images.githubusercontent.com/39504159/117977355-03981500-b331-11eb-8d48-0d25a8b9c89f.png)


## Steps to Reproduce 🕹
The code for the expected behavior is a bit strange:

https://codesandbox.io/s/material-demo-forked-l8nyn?file=/demo.js

![image](https://user-images.githubusercontent.com/39504159/117977704-65f11580-b331-11eb-8f03-48d779e3ab51.png)

![image](https://user-images.githubusercontent.com/39504159/117978222-f16aa680-b331-11eb-8e82-46f14f26d6f9.png)


-> 

![image](https://user-images.githubusercontent.com/39504159/117977355-03981500-b331-11eb-8d48-0d25a8b9c89f.png)




## Your Environment 🌎

```

System:
    OS: Windows 10 10.0.17763
  Binaries:
    Node: 12.16.0 - C:\Program Files\nodejs\node.EXE
    Yarn: Not Found
    npm: 6.13.4 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 90.0.4430.93
    Edge: Not Found
  npmPackages:
    @material-ui/core: ^4.11.3 => 4.11.3
    @material-ui/icons: ^4.11.2 => 4.11.2
    @material-ui/styles:  4.11.3
    @material-ui/system:  4.11.3
    @material-ui/types:  5.1.0
    @material-ui/utils:  4.11.2
    @types/react:  17.0.3
    react: ^17.0.2 => 17.0.2
    react-dom:
Repository: TypeScript
Issue: "Extract to function": parameter type missing when extracting code that depends on `node_modules`
Labels: Bug,Help Wanted,Domain: Refactorings

# Bug Report

<!--
  Please fill in each section completely. Thank you!
-->

### 🔎 Search Terms

<!--
  What search terms did you use when trying to find an existing bug report?
  List them here so people in the future can find this one more easily.
-->

code action quick fix module scope extract function refactoring

### 🕗 Version & Regression Information

<!-- When did you start seeing this bug occur?

"Bugs" that have existed in TS for a long time are very likely to be FAQs; refer to
  https://github.com/Microsoft/TypeScript/wiki/FAQ#common-bugs-that-arent-bugs

If possible, please try testing the nightly version of TS to see if it's already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly

Note: The TypeScript Playground can be used to try older versions of TypeScript.

Please keep and fill in the line that best applies:
-->
- This is the behavior in every version I tried, and I reviewed the FAQ for entries about refactorings

### ⏯ Playground Link

Not available since this only reproduces with `node_modules`.

### 💻 Code

Reduced test case: https://github.com/OliverJAsh/ts-extract-function-missing-type-bug

Note this code presumes you have ran `npm install io-ts`.

<!-- Please post the relevant code sample here as well-->
`src/state.ts`:
```ts
import * as t from 'io-ts';

export declare const getErrors: () => t.Errors;
```

`src/main.ts`:
```ts
import { getErrors } from './state';

export const fn = () => {
    const state = getErrors();

    const test = { state };
};
```

1. Select `{ state }` in `src/main.ts` and run "Extract to function in module scope"

### 🙁 Actual behavior

The `state` parameter in the extracted function does not have a type.

```ts
import { getErrors } from './state';

export const fn = () => {
    const state = getErrors();

    const test = { state };
};
function newFunction(state) {
    return { state };
}
```

https://user-images.githubusercontent.com/921609/117977115-6933d380-b328-11eb-9097-55240b1a4478.mov

### 🙂 Expected behavior

The `state` parameter in the extracted function should have a type.

```ts
import * as t from 'io-ts';
import { getErrors } from './state';

export const fn = () => {
    const state = getErrors();

    const test = newFunction(state);
};
function newFunction(state: t.Errors) {
    return { state };
}


```
Repository: PowerToys
Issue: Audible Feedback for PowerToys Run
Labels: Idea-Enhancement,Help Wanted,Product-PowerToys Run,Cost-Small

### Provide a description of the new feature / enhancement

When invoking PowerToys Run it would be nice to have audible feedback. The run box is just a black rectangle which can sometimes be lost on a busy screen and can take a while to display.
Repository: rust
Issue: Specialization on associated type
Labels: A-diagnostics,T-compiler,A-specialization,C-bug,F-specialization,D-confusing

Specializing on an associated type doesn't yet work.

```rust
#![feature(specialization)]

trait Tr {
    type X;
    fn f(&self) -> Self::X;
}

// Works
// impl<T> Tr for T {
//     type X = i8;
//     fn f(&self) -> Self::X { 1_i8 }
// }

// Works
// impl<T> Tr for T {
//     type X = i8;
//     
//     default fn f(&self) -> Self::X {
//         1_i8
//     }
// }

// Doesn't work
impl<T> Tr for T {
    default type X = i8;
    
    default fn f(&self) -> Self::X {
        1_i8
    }
}
```
Error:
```
error[E0308]: mismatched types
  --> src/lib.rs:28:5
   |
25 |     default type X = i8;
   |     -------------------- expected this associated type
26 |     
27 |     default fn f(&self) -> Self::X {
   |                            ------- expected `<T as Tr>::X` because of return type
28 |         1_i8
   |         ^^^^ expected associated type, found `i8`
   |
   = note: expected associated type `<T as Tr>::X`
                         found type `i8`

error: aborting due to previous error; 1 warning emitted
```

On `1.54.0-nightly (2021-05-11 5c029265465301fe9cb3)`. [Playground](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=e64fdc0205be7c48f02bfd29d47027eb).
Repository: rust
Issue: simd_shuffle, simd_insert, simd_extract should use const generics
Labels: T-compiler,A-SIMD,A-const-generics,A-intrinsics

`simd_shuffle` requires its last parameter, the array defining the shuffling, to be a constant:
https://github.com/rust-lang/rust/blob/487e27350a16e35f77ca471f368be3da28dac27c/compiler/rustc_codegen_llvm/src/intrinsic.rs#L888

Currently (after https://github.com/rust-lang/rust/pull/85110), this is enforced by an ad-hoc hack in `compiler/rustc_mir/src/transform/lower_intrinsics.rs`.

But I think it'd be better to instead change the type of `simd_shuffle` to make the shuffle array a const generic parameter. I am not doing this yet since const generic arrays require enabling an `incomplete_feature` which is not great, but once const generic arrays are sufficiently stable we could use them as a more principled way to ensure that `simd_shuffle` is called in the right way.

**Update (2024-02-17):** A const-generic version of simd_shuffle now exists, but using it in stdarch would require generic_const_exprs and that's too experimental for such uses.

Cc @rust-lang/project-const-generics
Repository: pytorch
Issue: [docs] Strange torch.unique function signature
Labels: module: docs,module: bootcamp,triaged

`torch.unique(*args, **kwargs)` - haven't seen any other functions with signatures not listing the arguments inline

![image](https://user-images.githubusercontent.com/1041752/117996212-40203c80-b342-11eb-9eb9-519e139c0345.png)

UPD: still the case, https://pytorch.org/docs/master/generated/torch.unique.html#torch.unique

cc @brianjo @mruberry
Repository: ant-design
Issue: Progress Step size
Labels: help wanted,Inactive

- [x] I have searched the [issues](https://github.com/ant-design/ant-design/issues) of this repository and believe that this is not a duplicate.

### What problem does this feature solve?
When "steps" are enabled, the progress bar uses a fixed with of 14px per step.  Other progress bars have a width 100% (by default).  

The ability to resize the "Progress" component in "step" mode would be helpful in fitting this element into various designs.

### What does the proposed API look like?
Ideally it would just leverage the standard css `style` properties.  However, I imagine this implementation might be challenging around responsive design.

It would at least be better if we had the ability to set the `stepWidth` to a fixed px value.


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->