sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: Investigate Swift Package Manager for Swift plugins
Labels: c: new feature,platform-ios,tool,platform-mac,a: existing-apps,P2,team-ios,triaged-ios

Since Swift has a 'first-party' package manager in the form of Swift Package Manager, it would be interesting to evaluate whether we could use that, instead of CocoaPods, for Swift plugins. That would allow for gradual migration away from CocoaPods over time assuming plugin development eventually shifts toward Swift, rather than having to do an expensive, ecosystem-breaking one-time migration.

According to docs, SPM packages can contain C/ObjC/C++/ObjC++ code, which substantially mitigates the bootstrapping problem; given that people could presumably make SPM packages that wrap existing non-Swift libraries for use in Swift plugins.
Repository: flutter
Issue: Unicode input should be indicated.
Labels: a: text input,c: new feature,framework,f: material design,platform-windows,platform-linux,a: desktop,P3,team-text-input,triaged-text-input

Ctrl+Shift+U (on certain operating systems) normally would bring up an underlined "u" in a text field to indicate it's awaiting a Unicode entry. This is not indicated on Flutter, despite it taking the input.

![Flutter](https://i.imgur.com/5LGa38g.png)
![Play Store, expected behavior.](https://i.imgur.com/JDQ2sZt.png)
Repository: neovim
Issue: Completion item kinds standard
Labels: documentation

I thought this was appropriate since this is a discussion that is in interest of all gui implementations, let me know if that's not the case.

I noticed when [implementing](https://github.com/vhakulinen/gnvim/pull/49) coc.nvim support for completion icons for gnvim, that while there's a brief definition on `|complete-items|` with regard to the kind that is passed, most major implementations do not follow or extend it.

That would not be an issue if all used the same definitions, but that does not seem to be the case.

Currently each plugin must have its logic handled by the GUI.

These are currently the definitions for the major LSP implementations:

- [coc.nvim](https://github.com/neoclide/coc.nvim/blob/909710fddb04d383e5546b0f869c44f395a80d02/src/languages.ts#L143-L167) The only one that sends a single character by default, it highlights a possible issue with this restriction (max 52 kinds on ascii word chars)
- [vim-lsp](https://github.com/prabirshrestha/vim-lsp/blob/3441fa8c2d27b46a510cd9c17cfa1bde04ca4a6e/autoload/lsp/ui/vim/utils.vim#L39-L56)
- [LanguageClient-neovim](https://github.com/autozimu/LanguageClient-neovim/blob/0ac444affdff8db699684aa4cf04c2cb0daf0286/rplugin/python3/denite/lsp/protocol.py#L48-L55)

Not sure how feasible it is to enforce a more thorough standard (or if its something neovim should concern with in the first place), but if achieved would avoid ad-hoc logic for each LSP plugin for GUI developers.
Repository: flutter
Issue: Support Android Development from 32-bit Windows
Labels: platform-android,engine,platform-windows,P3,team-android,triaged-android

At this time we have no plans to add 32-bit support for Windows. I'm filing this bug as a cleaner place to track this request (e.g. upvote if you want this) as well as the blocking issues were someone to want to add support in the future.

We have several other existing 32-bit windows bugs, all of which are closed, e.g. https://github.com/flutter/flutter/issues/22638 https://github.com/flutter/flutter/issues/21169 https://github.com/flutter/flutter/issues/14925

As originally captured in https://github.com/flutter/flutter/issues/14925#issuecomment-415864259, blockers are at least:
1. flutter/engine has no 32-bit build rules currently, including gen_snapshot
2. gen_snapshot is architecture dependent, unclear if a 32-bit gen_snapshot could build for 64-bit Android (which is a requirement for the Play Store as of this August).

Steam stats show 32-bit Windows as less than 2% market share:
https://store.steampowered.com/hwsurvey

Given the low market share numbers and [other vendors dropping support for 32-bit](https://www.extremetech.com/computing/267180-nvidia-ends-support-for-32-bit-operating-systems), it seems highly unlikely we'd add 32-bit Windows development support for Flutter.

I welcome thoughts from others, or additional/new data as to why we should add 32-bit development support?
Repository: flutter
Issue: Driver tests should fail when method channel calls are failed.
Labels: platform-android,engine,t: flutter driver,a: platform-views,P2,team-android,triaged-android

The MethodChannel code swallows exceptions and logs them to an error here:

https://github.com/flutter/engine/blob/661c24e4f359c60915a21c285d1d34777f0ccb30/shell/platform/android/io/flutter/plugin/common/MethodChannel.java#L205

This resulted in a recent regression(fixed in flutter/engine#9185 going unnoticed for over a day, even that we had a driver test triggering the bad code(as the exception was just logged).

We should make sure tests are failing when this happen(same for `IncomingMethodCallHandler#onMessage`).
Repository: flutter
Issue: IOS back gesture dismisses top route instead of its own route
Labels: platform-ios,framework,f: material design,f: cupertino,f: routes,f: gestures,has reproducible steps,P2,found in release: 3.3,found in release: 3.6,team-ios,triaged-ios

When I make a back gesture on IOS and it is not the top route, the top route gets popped instead of the route where the back gesture originated and the back gesture animation gets stuck.

- See  [video](https://drive.google.com/file/d/1BkcxZejNGJHUzazxTb9205c66yunXxwQ/view?usp=sharing)
- After the back gesture animation gets stuck, I'm trying to click everywhere. Nothing responds.
- For more details, see [#28237](https://github.com/flutter/flutter/issues/28237#issue-412698362)

```
[✓] Flutter (Channel beta, v1.6.3, on Mac OS X 10.14.5 18F132, locale en-BR)
 
[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[✓] iOS toolchain - develop for iOS devices (Xcode 10.2.1)
[✓] Android Studio (version 3.4)
[✓] Connected device (2 available)

• No issues found!

```
Repository: PowerToys
Issue: Prevent virtual keyboard from being dismissed when touching physical keyboard
Labels: Idea-Enhancement,Product-Tweak UI Design

Sometimes we need the virtual keyboard for typing in languages that use different scripts such as Korean or Russian, but we still keep using the physical keyboard for shortcuts such as Alt+Tab or for the numbers, etc.

Any time we hit any real key, the virtual keyboard is dismissed (Windows 10)

Maybe a pin function could help. There is plenty of space there to add one more icon
Repository: terminal
Issue: Feature Request: Add tab indicator to show number of panes in tab
Labels: Area-UserInterface,Product-Terminal,Issue-Task

# Summary of the new feature/enhancement

Migrated from ADO. Need some kind of indicator for number of panes in tab. Just throwing an idea out there but why not make it look kinda like this (obviously ignore the fact that this is a browser):
![image](https://user-images.githubusercontent.com/11050425/58923562-0f1a4480-86f5-11e9-97bc-f881b85a69cf.png)

Related to #1000 

Pinging @cinnamon-msft & @zadjii-msft
Repository: rust
Issue: Intrinsic for `type_name_of_id` to power a better `impl Debug for TypeId`?
Labels: T-lang,T-libs-api,needs-fcp

Currently `TypeId`s have uninformative derived `Debug` impls:

```rust
fn main() {
    println!("{:?}", std::any::TypeId::of::<usize>());
}
```

```
   Compiling playground v0.0.1 (/playground)
    Finished dev [unoptimized + debuginfo] target(s) in 0.91s
     Running `target/debug/playground`
TypeId { t: 8766594652559642870 }
```

This results in fairly poor Debug output for dynamic types like `anymap`.

I think it could be quite nice for debugging/logging/etc to allow printing the type name from a `TypeId` in the Debug impl. It would provide an out of the box improvement to debugging existing dynamic typing tools, and IIUC the contents of Debug impls in the standard library are not considered stable so there's neither a breaking change here nor a de facto stabilization of the type_name representation.

I assume this would need to rely on some unstable intrinsic being exposed to get the type_name of an ID at run time, but I'm not really aware what would be needed.

Thoughts? cc @oli-obk as we had discussed this a bit on IRC.
Repository: pytorch
Issue: collect_env ignores conda environment
Labels: module: build,module: docs,low priority,module: collect_env.py,triaged

Hi,
https://github.com/pytorch/pytorch/blob/95eb9339c10ffc4d74312f35ac15fffa61596de1/torch/utils/collect_env.py#L114
I find this function `get_running_cuda_version` ignores the existence of cudatoolkit in conda env, instead it uses `nvcc --version` , the system wide installed CUDA as a reference to get the cuda version. 
This may be confusing if someone has cudatoolkit with a different cuda version installed.
Can it be improved? Thanks.
Repository: flutter
Issue: [go_router] Figure out how to use go_router to pop the target page
Labels: c: new feature,f: routes,package,P3,p: go_router,team-go_router,triaged-go_router

For example 
1. request 1 runs in the background, and a dialog A is displayed after the end of the request 

2. request 2 runs in the foreground and displays dialog B directly. Close the dialog B after ending the request

The problem is that dialog A is displayed after dialog B, but closed dialog A while using Navigator pop, but I needed to close dialog B

So how can i pop the target page?

```dart
import 'dart:async';
import 'package:flutter/material.dart';
import 'package:flutter/cupertino.dart';

void main() async {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: HomePage(),
    );
  }
}

class HomePage extends StatefulWidget {
  @override
  _HomePageState createState() => _HomePageState();
}

class _HomePageState extends State<HomePage> {
  StreamController<bool> sc = StreamController();

  Stream<bool> get stream => sc.stream;

  @override
  void initState() {
    stream.listen((show) {
      if (show) {
        showDialogB();
      } else {
        Navigator.of(context).pop();
      }
    });

    request1();
    request2();
    super.initState();
  }

  void request1() {
    Timer(Duration(seconds: 3), () {
      showDialogA();
    });
  }

  void showDialogA() {
    showDialog(
        context: context,
        builder: (context) {
          return Container(
            height: 100,
            width: 100,
            color: Colors.white,
            child: Center(
              child: Text(
                "新版本",
                style: TextStyle(color: Colors.black),
              ),
            ),
          );
        });
  }

  void showDialogB() {
    showDialog(
        context: context,
        builder: (context) {
          return Container(
            height: 100,
            width: 100,
            color: Colors.white,
            child: Center(
              child: CupertinoActivityIndicator(),
            ),
          );
        });
  }

  void request2() {
    sc.add(true);
    Timer(Duration(seconds: 5), () {
      //dimisssDialogB
      sc.add(false);
    });
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text("111"),
      ),
    );
  }
}
```
Repository: TypeScript
Issue: Show documentation for literals in intellisense
Labels: Suggestion,Awaiting More Feedback


## Suggestion

When filling in a value where the expected type is a union of literals, intellisense is able to suggest the possible values. 

However, it does NOT show the documentation associated with each literal:

![image](https://user-images.githubusercontent.com/664425/58940110-f5badc00-8778-11e9-9a05-e4de000ff747.png)

This makes me tend to use enums instead, which has a more verbose syntax and requires an extra import. 

## Use Cases

Building and documented APIs in typescript will be nicer if we could just document the literals in a union.

## Search Terms

- intellisense for string literals
- documentation for string literals
Repository: pytorch
Issue: how libtorch can work with  tensor data as same as  pytorch
Labels: module: docs,module: cpp,low priority,triaged

 I have a question about data manipulation with the C++ in libtorch.
For example, in pytorch I could deal with tensor like this:
img[:, :10, :] = 0
but with libtorch I don't know how to do as same as pytorch,if I use for circle,then it will be very slow,I want to know if there is any function with libtorch can do this,thank you very much.
Repository: neovim
Issue: Prepend command with range `<,`> when in Visual mode, and with '<,'> when in Visual Line mode.
Labels: enhancement

In Vim/Neovim, when I visually select a word (e.g. in the middle of the line) and start typing command, the editor is kind enough to prepend the range of the visual selection to the command:
```
:'<,'>
```
However, `'<,'>` gives me the range of lines instead of range of the actual visual selection, and I can't operate on the word (e.g. use Unix command `rev` to reverse it), because the operation I do affects the whole line.

To me in this case it would be more sensible if the editor would prepend ``:`<,`>`` instead of `:'<,'>` by default, because I think this would open many new possibilities with fewer keystrokes. At the moment e.g. ``:`<,`>!rev`` doesn't work, for unknown reason to me, but one can still use `` `< `` to jump to the beginning of current or previous visual selection, and `` `> `` to jump to the end of selection.

I think prepending `:'<,'>` to the command would definitely make sense in the visual-line selection.
Repository: ant-design
Issue: Menu组件在vertical模式时，希望可以配置子菜单的展开方向
Labels: 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?
在使用`<DropDown>`组件时，多级的子菜单可以向左展开，以满足不同情况的需求，现在子菜单只能向右展开

### What does the proposed API look like?
```jsx
<Menu mode={'vertical'} unfoldDirection={'left' | 'right'}>
  <Menu.Item>
    xxx
  </Menu.Item>
  ...
</Menu>
```


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: terminal
Issue: Bug Report: ColorTool and changing colours causes strange behaviour since Windows 10 1903
Labels: Product-Colortool,Help Wanted,Issue-Bug,Needs-Tag-Fix

# Environment

```none
Microsoft Windows [Version 10.0.18362.30]
```

# Steps to reproduce

You should be able to use any color scheme, but I'll provide mine specifically below.

**Fotsies Colors.ini**

```ini
[table]
DARK_BLACK = 30,30,30
DARK_BLUE = 0,0,128
DARK_GREEN = 0,128,0
DARK_CYAN = 0,128,128
DARK_RED = 128,75,75
DARK_MAGENTA = 128,0,128
DARK_YELLOW = 238,237,240
DARK_WHITE = 192,192,192
BRIGHT_BLACK = 128,128,128
BRIGHT_BLUE = 0,0,255
BRIGHT_GREEN = 0,255,0
BRIGHT_CYAN = 0,255,255
BRIGHT_RED = 255,75,75
BRIGHT_MAGENTA = 255,0,255
BRIGHT_YELLOW = 255,255,0
BRIGHT_WHITE = 255,255,255

[screen]
FOREGROUND = DARK_WHITE
BACKGROUND = DARK_BLACK

[popup]
FOREGROUND = DARK_CYAN
BACKGROUND = DARK_BLACK
```

1. Open PowerShell as a regular user (I'm using 5.1 that comes with Windows 10)
2. Obtain the latest ColorTool release and extract it
3. Place the scheme above in the schemes sub-directory under ColorTool.exe
4. Load the scheme: `.\ColorTool.exe 'Fotsies Colors.ini'`
5. Notice the scheme is not applied correctly and that colors are not consistent as they should be

# Expected behavior

As per the previous stable Windows release, colors should be applied correctly and continue to function while using the terminal

# Actual behavior

Best way to demonstrate this is with some screenshots:

![image](https://user-images.githubusercontent.com/1811813/58951600-e2d5f500-87d4-11e9-8fe7-b64155970648.png)

I tested this with a completely fresh install of windows 10 1903 just now to confirm it's nothing that I've done wrong.  I can confirm that everything works perfectly in the previous October 2018 Windows 10 release.

Honestly, the terminal in this new release is unusable for me given all the problems I've been finding and I don't really have much choice but to reinstall the older Windows release as I depend on PowerShell.  Unless of course any workarounds may be suggested?

Any help is greatly appreciated.
Repository: vscode
Issue: Expect minimap functionality and similar to xcode 11
Labels: feature-request,editor-minimap

### The function definition is all suspended, which can be located quickly.


![](https://i.loli.net/2019/06/05/5cf7a892590b853392.png)
Repository: go
Issue: proposal: x/crypto/blake2b,x/crypto/blake2s: Implement personalisation and salting
Labels: Proposal,Proposal-Crypto

The current implementations of BLAKE2b and BLAKE2s support both variable output lengths and keyed BLAKE2 ([blake2b](https://github.com/golang/crypto/blob/20be4c3c3ed52bfccdb2d59a412ee1a936d175a7/blake2b/blake2b.go#L107-L108), [blake2s](https://github.com/golang/crypto/blob/20be4c3c3ed52bfccdb2d59a412ee1a936d175a7/blake2s/blake2s.go#L72-L73)), but do not yet enable setting the personalisation and salt sections of the parameter block. Personalisation in particular is becoming more commonplace in BLAKE2's usage within cryptographic protocols. It would be beneficial both inherently and for interoperability if the BLAKE2 implementations provided an interface for instantiating the digest state with a personalisation string and/or a salt.
Repository: pytorch
Issue: Implementation of Group equivariant convolutions
Labels: feature,module: nn,low priority,triaged

## 🚀 Feature
An implementation of group-equivariant convolutions defined by Cohen et. al in the paper 'Group equivariant convolutions' - in ICML 2016.
Specifically, an implementation of the group-convolution over the group of translations and rotations of multiples of 90 degrees at any centre, and the same group extended by reflections.  

## Motivation
Group-equivariant convolutions (g-cnns) extend the equivariance of convolutions to beyond translations. Cohen et. al argue in their paper that the parameter-sharing in g-cnns allow for more efficient use of parameters.
Further, limited experiments conducted by Adam Bielski in his github repository https://github.com/adambielski/pytorch-gconv-experiments, suggest that g-cnns improve upon the performance of regular cnn networks in at least some cases.
I'm not sure if the existing pytorch implementations are efficient as they take considerably more time to run than nn.Conv2d. 

To sum up, it would be awesome if you guys could create nn.GConv2d() for group-equivariant convolutions on at least the two groups mentioned before.

## Additional context
TS cohen's original implementation of group-equivariant convolutional networks: https://github.com/tscohen/GrouPy
Repository: flutter
Issue: Focus/RawKeyboardListener widgets don't receive events in some cases
Labels: customer: fuchsia,framework,P2,team-framework,triaged-framework

I tried to create a simple flutter app which used a RawKeyboardListener. It worked well under the android emulator using the non-Fuchsia flutter workflow, but when I moved it to Fuchsia and ran it as a Fuchsia app, it did not receive keyboard events.
Repository: rust
Issue: Lint control attributes (allow/deny/etc) have no effect on lifetime and const parameters
Labels: A-attributes,A-lints,T-compiler,C-bug

```rust
fn f<#[allow(warnings)] foo>() {} // warning: type parameter `foo` should have an upper camel case name
```
Expected behavior - no warning, actual behavior - warning.

cc https://github.com/rust-lang/rust/issues/61238, which is a similar issue
Repository: TypeScript
Issue: expando fields not added to symbol exports 
Labels: Needs Investigation

**TypeScript Version:**  3.4.0, 3.5.0, master (7dc1f40dc15132ba87a70a3bec6d63317cb5b91e)

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**
expando, iife, umd, exports

**Code**

Given the following code, similar to an UMD file:

```javascript
(function(){
    var A = (function () {
        function A() {}
        return A;
    }());
    A.expando = true;
}());
```

**Expected behavior:**

The `ts.Symbol` of the outer `A` should have `expando` in it.

**Actual behavior:**

The `ts.Symbol` of the outer `A` does not have `expando` in it. When the declaration of `A` is at the top-level, without the "UMD wrapper", it works properly:

```javascript
var A = (function () {
    function A() {}
    return A;
}());
A.expando = true;
```

I have researched what is preventing the `expando` static prop to be added to exports, and it is due to when a `ts.Symbol` is considered for expando properties, here:

https://github.com/microsoft/TypeScript/blob/3d2af9ff332fca6c5db2390be0b1f08bba8402a1/src/compiler/binder.ts#L2649-L2678

Specifically, the symbol's flag of `A` inside the UMD wrapper are not sufficient to take the early-return in the first statement, whereas with `A` at the top-level it has been assigned appropriate flags.

Because the appropriate flags are not present, the code structure is analyzed to determine if the symbol should be classified as expando. Specifically, the relevant code is in `getExpandoInitializer`:

https://github.com/microsoft/TypeScript/blob/3d2af9ff332fca6c5db2390be0b1f08bba8402a1/src/compiler/utilities.ts#L1873-L1896

From this function, it becomes clear why the symbol fails to be recognized as expando symbol: the used IIFE syntax deviates from the syntax that is accounted for in `getExpandoInitializer`. When changing the sample into the following, it does indeed work as expected:

```javascript
(function(){
    var A = (function () {
        function A() {}
        return A;
    })(); // <-- The difference is here
    A.expando = true;
}());
```

Unfortunately however, downleveled ES5 code does use the syntax that is _not_ accounted for.

**Playground Link:** <!-- A link to a TypeScript Playground "Share" link which demonstrates this behavior -->

Can't be replicated in the playground, but copying the code into https://ts-ast-viewer.com, setting the script kind to JS and inspecting the Symbol of the outer `A` declaration shows that its `exports` are empty. The alternative IIFE syntax does have the proper `exports`.

**Related Issues:** <!-- Did you find other bugs that looked similar? -->
n/a

**Background info**
This is an issue for Angular's Compatibility Compiler, which uses the TypeScript compiler to parse JavaScript bundles in various formats and uses the symbol information to reason about the code. PR https://github.com/angular/angular/pull/30795 now contains a hack to patch TS's `getExpandoInitializer`, which does indeed resolve the issue.