sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: ProcessGroup::Work API changes
Labels: module: bc-breaking,feature,triaged,module: c10d,topic: bc breaking

## 🚀 Feature
We are propose changing ProcessGroup's collective communication primitives to return ivalue::Future instead of ProcessGroup::Work to be compatible with TorchScript.

This is a placeholder for reporting issues related to this change, e.g. clients that need support for ProcessGroup::Work functionality that might get deprecated due to this migration.

cc @ezyang @gchanan
Repository: flutter
Issue: Picker widgets aren't using ambient locale, show an info message when not implementing localization in the app 
Labels: framework,f: material design,a: internationalization,f: cupertino,a: quality,c: proposal,team-design,triaged-design

This is what `showDatePicker` looks like in my App:

![image](https://user-images.githubusercontent.com/8120472/95926980-fb282d80-0d93-11eb-9b05-d70d18139a10.png)

As you can see there's `Tue, Oct 13` which is clearly on `en_US`.

The docs say `showDatePicker` can take an optional `locale`, if null it defaults to the ambient locale:

> An optional [locale] argument can be used to set the locale for the date picker. It defaults to the ambient locale provided by [Localizations].

My locale is `pt_BR`, I can confirm this by running `print(Intl.systemLocale);` on `build()`. But `print(Localizations.localeOf(context).toLanguageTag());` prints `en-US`:

```dart
Widget build(BuildContext context) {
    print(Intl.systemLocale); // prints pt_BR
    print(Intl.defaultLocale);  // prints pt_BR
    print(Intl.getCurrentLocale());  // prints pt_BR
    print(Localizations.localeOf(context).toLanguageTag());  // prints en-US
```
Repository: flutter
Issue: InputDatePickerFormField should expose the controller and other parameters so it will resemble more of TextFormField.
Labels: framework,f: material design,f: date/time picker,c: proposal,team-design,triaged-design

`InputDatePickerFormField` has a very limited interface. It should be improved to match a regular `TextFormField`. One of the things to improve is to expose the `controller` so we can change it's text value on runtime.

_____

EDIT:

From what I can see the `TextFormField` differs from the `InputDatePickerFormField` submitted on my PR by these properties:

```dart   
    FocusNode? focusNode,
    InputDecoration? decoration = const InputDecoration(),
    TextInputType? keyboardType,
    TextCapitalization textCapitalization = TextCapitalization.none,    
    TextStyle? style,
    StrutStyle? strutStyle,
    TextDirection? textDirection,
    TextAlign textAlign = TextAlign.start,
    TextAlignVertical? textAlignVertical,    
    bool readOnly = false,
    ToolbarOptions? toolbarOptions,
    bool? showCursor,
    String obscuringCharacter = '•',
    bool obscureText = false,
    bool autocorrect = true,
    SmartDashesType? smartDashesType,
    SmartQuotesType? smartQuotesType,
    bool enableSuggestions = true,
    @Deprecated(
      'Use autoValidateMode parameter which provide more specific '
      'behaviour related to auto validation. '
      'This feature was deprecated after v1.19.0.'
    )
    bool autovalidate = false,
    bool maxLengthEnforced = true,
    int? maxLines = 1,
    int? minLines,
    bool expands = false,
    int? maxLength,
    ValueChanged<String>? onChanged,
    GestureTapCallback? onTap,
    VoidCallback? onEditingComplete,
    FormFieldValidator<String>? validator,
    List<TextInputFormatter>? inputFormatters,
    bool? enabled,
    double cursorWidth = 2.0,
    double? cursorHeight,
    Radius? cursorRadius,
    Color? cursorColor,
    Brightness? keyboardAppearance,
    EdgeInsets scrollPadding = const EdgeInsets.all(20.0),
    bool enableInteractiveSelection = true,
    TextSelectionControls? selectionControls,
    InputCounterWidgetBuilder? buildCounter,
    ScrollPhysics? scrollPhysics,
    Iterable<String>? autofillHints,
    AutovalidateMode? autovalidateMode,
```

This is just a diff, I didn't check which one actually makes sense for the `InputDatePickerFormField`.

The parameters added for the `InputDatePickerFormField` were:

```dart
DateTime? currentDate,
DateTime? firstDate,
DateTime? lastDate,
errorEmptyText,
helperText,
controller,
allowEmptyDate = false,
textInputAction,
```
Repository: PowerToys
Issue: [Build warning] Referenced assembly 'mscorlib.dll' targets a different processor
Labels: Area-Localization,Priority-2,Area-Build

On the build farm, for all the C# projects the following warning appears:
![image](https://user-images.githubusercontent.com/32061677/95929281-7976d680-0d78-11eb-96ab-9312e952db00.png)

After some digging, I found that this seems to occur on any .NET project with more than one resx file, and occurs because of the satellite resource dll generation step. As per https://developercommunity.visualstudio.com/content/problem/95054/alink-still-generates-warning-when-compiling-assem.html this is a bug in .NET and not a bug on our side, however it didn't get fixed since it didn't meet the bar for a fix.
As described https://thorarin.net/blog/post/2019/02/08/al1703-warning-mscorlib and https://stackoverflow.com/questions/25365616/alink-warning-al1073-referenced-assembly-mscorlib-dll-targets-a-different-p, the fix is to add the following snippet

    <Target Name="FixAL1703Warning" BeforeTargets="GenerateSatelliteAssemblies"        Condition="'$(PlatformTarget)' == 'x64'">  
    <Message Text="Adjusting SDK tools directory to use x64 version of AL.EXE">  
        <PropertyGroup>    
            <TargetFrameworkSDKToolsDirectory>$(TargetFrameworkSDKToolsDirectory)$(PlatformTarget)\</TargetFrameworkSDKToolsDirectory>  
        </PropertyGroup>
    </Target>

This would have to be added on all the .NET projects.
Repository: flutter
Issue: Add feature of ComposePathEffect and CornerPathEffect
Labels: framework,f: material design,c: proposal,team-design,triaged-design

## Use case

There is no way or an equivalent solution for path smoothing in flutter. Like in android we have `ComposePathEffect, CornerPathEffect, DashPathEffect, DiscretePathEffect, PathDashPathEffect, SumPathEffect`  but i don't see any equivalent solution for flutter. How do i smooth the path that is drawn ?

## Proposal

Please look at this page and this is what i am imagining to do with flutter too
http://android-coding.blogspot.com/2014/05/composepatheffect-example.html

Google SKIA already has these. You can see from here
https://github.com/google/skia/tree/master/src/effects

and because all flutter renderings are handled by skia backend, so i feel this is not that tough to implement.
Repository: godot
Issue: External editors do not recognize GDScript class names until closing and reopening Godot
Labels: bug,topic:gdscript,topic:editor

**Godot Version:**

3.2.2 Standard Version

**OS/device including Version:**

Mac OS 10.15.7

**Issue description:**

For a better coding experience I've set up GDScript with VisualStudio Code! This works perfectly fine besides one exception.  If I create a new scene with Godot and attach a script and then give the script a class_name

For example:

class_name: Player

Visual Studio Code does not recognize the class name until I close Godot and reopen it. 

**Steps to reproduce:**
See Issue description
Repository: pytorch
Issue: Compile error when use c10::RegisterOperators::Options::kernel with the return type "std::tuple<Tensor&, Tensor&>"
Labels: module: internals,triaged

The code:
https://github.com/pytorch/pytorch/blob/d790ec6de01a61fe81733c41a64b6092bacfb7bd/aten/src/ATen/core/boxing/impl/make_boxed_from_unboxed_functor.h#L366

may use the return_to_ivalue defined here, which requires a l-value tensor as param:
https://github.com/pytorch/pytorch/blob/d790ec6de01a61fe81733c41a64b6092bacfb7bd/aten/src/ATen/core/boxing/impl/make_boxed_from_unboxed_functor.h#L304

The std::move is not compatible for OutputTypes as "Tensor&, Tensor&".

Can we use the "std::forward<OutputType>" instead of "std::move"?

`torch::jit::push(*stack, return_to_ivalue<OutputTypes, AllowDeprecatedTypes>(std::forward<OutputTypes>(std::get<indices>(output)))...);`

cc @ezyang @bhosmer @smessmer @ljk53 @bdhirsh @ailzhang
Repository: storybook
Issue: Don't export hooks with the same names as the core React hooks
Labels: maintenance,BREAKING CHANGE,core

**Describe the bug**

The `@storybook/addons` module exports hooks with the same names as the React core hooks, e.g. `useState`, `useEffect`, etc.

This is a nightmare for coding usability. Previously I could easily start typing `useState`, then use VSCode's auto import suggestion to add the React import. Now, the top suggestion is often the Storybook hook, instead of React's. I often end up importing the wrong one, resulting in a `Storybook preview hooks can only be called inside decorators and story functions` error in my app.

**To Reproduce**

1. Open a `.ts` source file without an existing import of `useState`.
2. Type `useSta`
3. When the import suggestion popover appears, press "enter" to use the top suggestion.

**Expected behavior**

Please consider renaming these hooks to something else.

**Screenshots**

![image](https://user-images.githubusercontent.com/183786/95963659-dd90ad80-0dff-11eb-81b6-d9bf483e8eff.png)

**System**

```
  Binaries:
    Node: 13.8.0 - ~/.nvm/versions/node/v13.8.0/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 6.13.6 - ~/.nvm/versions/node/v13.8.0/bin/npm
  Browsers:
    Chrome: 86.0.4240.80
    Safari: 14.0
```
Repository: react-native
Issue: Changing onViewableItemsChanged on the fly is not supported
Labels: Component: FlatList,Resolution: Backlog,Bug,Tech: React Native Core,Never gets stale

Please provide all the information requested. Issues that do not follow this format are likely to stall.

## Description
Changing onViewableItemsChanged on the fly is not supported

## React Native version:
0.63.3

## Snack, code example, screenshot, or link to a repository:
<FlatList
        ref={FlatListRef}
        data={data}
        inverted={true}
        contentContainerStyle={{
          flexGrow: 1, justifyContent: 'flex-end',
        }}
        renderItem={renderItem}
        keyExtractor={item => item.id}
        viewabilityConfig={{waitForInteraction: true, viewAreaCoveragePercentThreshold: 95}}
        onViewableItemsChanged={(info) => {
          console.log(info)
        }}
/>

![image](https://user-images.githubusercontent.com/16165858/95974124-20c23f00-0e47-11eb-8a7a-94054ffda524.png)
Repository: flutter
Issue: Interactive Selection Popover scrolls over AppBar
Labels: a: text input,framework,f: material design,has reproducible steps,found in release: 3.3,found in release: 3.6,team-design,triaged-design

If I put a TextFormField into a SingleChildScrollView, press a long press to open the context menu, I can scroll with the context menu open. The AppBar is overlaid by the context menu.

![image](https://user-images.githubusercontent.com/20318830/95984067-ef377c80-0e22-11eb-86a2-71b11022da63.png)

![image](https://user-images.githubusercontent.com/20318830/95984060-ea72c880-0e22-11eb-8dff-2eefea3df157.png)


Using a NotificationListener<ScrollNotification> to remove Focus when scrolling prevents from overlaying the appbar, but it's just an ugly workaround, because when typing a text in textformfield and start scrolling, the focus get's lost also.
Repository: godot
Issue: TextureAtlas is not power of 2
Labels: topic:import

**Godot version:**
3.2.3.stable, Windows 10

**Issue description:**
We selected a number of sprites and imported them as a TextureAtlas with the import mode set to Region.
The resulting atlas.png is not power of 2, see image. 

![image](https://user-images.githubusercontent.com/24936603/95984406-6c62f180-0e23-11eb-8460-e65e88051b4b.png)

We are aware that modern graphics cards can handle these None-power-of-two textures without a problem, but our games have to run on very old hardware with integrated graphics cards, so every bit of performance counts.

Good arguments for/against power of 2 textures.
[gamedev should-i-use-textures-not-sized-to-a-power-of-2](https://gamedev.stackexchange.com/questions/7927/should-i-use-textures-not-sized-to-a-power-of-2 )
Repository: rust
Issue: Tracking Issue for -Z codegen-backend
Labels: A-codegen,T-compiler,B-unstable,C-tracking-issue,S-tracking-impl-incomplete,A-CLI

<!--
Thank you for creating a tracking issue! 📜 Tracking issues are for tracking a
feature from implementation to stabilisation. Make sure to include the relevant
RFC for the feature if it has one. Otherwise provide a short summary of the
feature and link any relevant PRs or issues, and remove any sections that are
not relevant to the feature.

Remember to add team labels to the tracking issue.
For a language team feature, this would e.g., be `T-lang`.
Such a feature should also be labeled with e.g., `F-my_feature`.
This label is used to associate issues (e.g., bugs and design questions) to the feature.
-->

This is a tracking issue for the `-Zcodegen-backend` compiler flag.

rustc today only supports one stable backend ("llvm"), but it has many unstable backends.

In the future, it will support multiple stable backends.

Our plan is that the stable backends will all be allowlisted in the compiler. The general pattern will be that every stable backend will be denoted by an identifier with no `.` in its name (e.g. "cranelift", "gcc", "llvm"). When we start reaching a point where one of the alternative backends is getting close to being ready to stabilize, we will then discuss how to offer a stable form of this flag (i.e. `-C codegen-backend` flag).

Meanwhile, the `-Z codegen-backend` flag will always *unstably* support an interface for connecting to an arbitrary backend loaded as a dynamic library, as described below.

----

This flag unstably allows you specify a path to a dynamic library containing a function named `__rustc_codegen_backend` with a signature of `fn() -> Box<dyn  rustc_codegen_ssa::traits::CodegenBackend>` to use as code generation backend at runtime. ([`CodegenBackend` trait](https://doc.rust-lang.org/nightly/nightly-rustc/rustc_codegen_ssa/traits/trait.CodegenBackend.html))

### Example

```rust
use rustc_codegen_ssa::traits::CodegenBackend;

struct MyBackend;

impl CodegenBackend for MyBackend {
   // Implement codegen methods
}

#[no_mangle]
pub fn __rustc_codegen_backend() -> Box<dyn CodegenBackend> {
    Box::new(MyBackend)
}
```

### About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

### Implementation history

<!--
Include a list of all the PRs that were involved in implementing the feature.
-->

- Initial Implementation https://github.com/rust-lang/rust/pull/45684
- Add `codegen-backend` to deps https://github.com/rust-lang/rust/pull/77565
Repository: create-react-app
Issue: react-dev-utils 10.2.1: events.js:291       throw er; // Unhandled 'error' event
Labels: needs triage,issue: bug report

After updating react-dev-utils from:

"react-dev-utils": "^6.1.1",

to:

"react-dev-utils": "^10.2.1",

An error occurs:

events.js:291
      throw er; // Unhandled 'error' event
      ^

Error: read ECONNRESET
    at TCP.onStreamRead (internal/stream_base_commons.js:209:20)
Emitted 'error' event on Socket instance at:
    at emitErrorNT (internal/streams/destroy.js:106:8)
    at emitErrorCloseNT (internal/streams/destroy.js:74:3)
    at processTicksAndRejections (internal/process/task_queues.js:80:21) {
  errno: -4077,
  code: 'ECONNRESET',
  syscall: 'read'
Repository: PowerToys
Issue: [KBM] Select target app from open windows
Labels: Idea-Enhancement,Product-Keyboard Shortcut Manager,Product-Settings

## 📝 Provide a description of the new feature

The user can add a remapping only for specified apps. At the moment they have to know the exe file name.

**It would be great if we have an app selection feature:**
1. The user click the select button on the ui. (Position is above the text box "target app".)
2. The cursor changes to a cross cursor or something else and the user can select an open window by clicking on it.
3. The process name of the selected window will be set as target app.

---

If you'd like to see this feature implemented, add a 👍 reaction to this post.
Repository: material-ui
Issue: [Autocomplete] Icon as startAdornment shifts TextField upwards
Labels: bug 🐛,waiting for 👍,component: autocomplete

<!-- Provide a general summary of the issue in the Title above -->

Using an Material Icon as start adornment in an Autocomplete will move the text field slightly higher.
This does not happen for the end adornment.
It also does not happen with text only instead of an icon.

<!--
  Thank you very much for contributing to Material-UI by creating an issue! ❤️
  To avoid duplicate issues we ask you to check off the following 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 😯

The text field is shifted upwards.

## Expected Behavior 🤔

The text field should not be shifted upwards.

## Steps to Reproduce 🕹

https://codesandbox.io/s/dawn-pine-n2bfn?file=/src/index.js:0-328

<img width="587" alt="Capture d’écran 2021-02-02 à 16 14 53" src="https://user-images.githubusercontent.com/3165635/106620411-d4c01500-6571-11eb-86ca-684a38ee558d.png">

I added several other examples where the text field is still on the correct height.

Steps:

1. Declare an Autocomplete
2. Define a material icon as startAdornment in the InputProps

## Context 🔦

I'm trying to use Autocompletes with and without icon together but they will not look good next to each because of this issue.

## Your Environment 🌎

<!--
  Include as many relevant details about the environment with which you experienced the bug.
  If you encounter issues with TypeScript please include version and tsconfig.
-->

| Tech        | Version |
| ----------- | ------- |
| Material-UI | v4.11.0  |
| Material-UI Icons | v4.9.1 |
| React       |   v16.13.1   |
| Browser     |     Firefox + Chrome    |
Repository: rust
Issue: rustc --print unstable-features
Labels: A-stability,T-compiler,C-feature-request

It would be nice to have a `--print unstable-features` or `-F help`, because an IDE would then be able to offer auto-completions for tailored for the user's toolchain.

The best alternative today seems to be scraping the source code of https://doc.rust-lang.org/unstable-book/the-unstable-book.html.
Repository: pytorch
Issue: Remove header declarations for CPUType/TypeDefault
Labels: module: internals,triaged

Previously, they were necessary because static dispatch would call these functions directly. As static dispatch has been removed, the majority of this codegen is no longer needed.

TypeDefault is still invoked from VariableType and some resolution needs to be found there, but I kind of suspect @ailzhang's work on Math kernels will also obviate the need for explicit TypeDefault invocations in VariableType as well.

cc @ezyang @bhosmer @smessmer @ljk53 @bdhirsh @ailzhang
Repository: flutter
Issue: Possibility to customize day template when using showDatePicker()
Labels: c: new feature,framework,f: material design,c: proposal,team-design,triaged-design

Good morning,

actually our team is facing a problem with Flutter calendar widget.
There is no possibility to change the template of calendar days when using `showDatePicker()`. 

The idea is to have 1 new function in the `showDatePicker()` definition that is called when widget is showed in order to have the possibility to define the day template, something like:

```dart
final DateTime picked = await showDatePicker(
      context: context,
      locale: const Locale("it", "IT"),
      initialDate: _selectedDate,
      firstDate: DateTime.now(),
      lastDate: DateTime(2101),
      selectableDayPredicate: (date) {
        // If not Sunday or Saturday return day as clicable
        if (date.weekday != 6 && date.weekday != 7) {
          return true;
        }
        return false;
      },
      //New function called during single day widget build
      dayTemplateBuilder: (date) {
        //... my custom logic
        return BoxDecoration(); //Decoration();
      }
    );
```
With this implementation Flutter users can simply customize this widget for example to highlight days in which there are some appointments.

Thanks
Repository: angular
Issue: Allow specifying a max age for the index page served by the Service Worker
Labels: feature,help wanted,area: service-worker,state: confirmed,feature: under consideration

Currently the Service Worker will serve the specified index file on navigation requests, checking for updates once the application has started.

While this does provide offline support & improves the TTI, one issue is that there's no expiration date for said index file: a returning user who had visited the site two months back will effectively run a 2-months old version of the app. This is posing an issue for us as, in addition to requiring our API to remain backwards compatible for a long period, said user will not see new features / bug fixes until the next visit, possibly a few weeks after, causing slow upgrade cycles (as confirmed through our analytics)

There is currently not a straightforward way to handle that staleness issue:
- While the app does indeed know that a new version is available, showing an upgrade toast 30 seconds after loading a site one hasn't been to in a month is just weird (e.g. https://github.com/angular/angular/issues/22080#issuecomment-408987881 mention that this was removed from angular.io). Similarly force-refreshing the user isn't great either, especially as he/she can be in the middle of filling a form, since it takes a certain time for the SW to fetch the new app version.
- Preventing the Service Worker from serving navigation requests solves the freshness issue but breaks offline & degrades the TTI.
- Defining a `dataGroup` for the index file with a `maxAge` means the app shell hash isn't checked anymore, which means the app version integrity isn't guaranteed.

An intermediate solution could be to have a customizable maximum age for the app shell (index): if that max age (say a week) has been reached, the service worker would go to the network to re-fetch the shell. This effectively means that if a newer version of the app is available, all the new assets would have to be fetched for the app to load, losing the benefits of the SW background fetching. It would also break offline support for those users as well. However, frequently returning users would not experience that, and this would enforce a maximum staleness for the app.

There might be better ways to address the problem though, but the current situation of unlimited app cache duration isn't ideal.
Repository: PowerToys
Issue: shortcut for night light 
Labels: Idea-New PowerToy

there should be a shortcut fo rnight light as each time when it turns on I have to exit my full screen and go to the action centre and then turn it off . if there will be a shortcut i can toggle it off or on more easily