sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Improve task debugging by giving more context
Labels: feature-request,tasks

<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
Most of this text comes from an email. The context is that I got on a phone call with a customer who was experiencing issues debugging an Azure Function App.


#### The issue

F5 debugging of a Function App would show:
```
> Executing task: func host start <
```

And then something saying that the last exit code was 1.

It wasn’t clear what the problem was, why it was failing, and we found that this would fail on `func extensions install` and `func host install`… running the func commands in the PowerShell Integrated Console or outside of VS Code in any terminal worked just fine…

#### The resolution

Then we realized that the customer's default shell…….. was WSL.

As you know, tasks use the default shell to run in by default. Which means that the `func` commands were being run in WSL which didn’t have the Core Tools installed in it so the Task threw an exit code of 1 because the command wasn’t found.

Once Aleksandar changed his default shell back to PowerShell, everything started working again.

#### The problem

The lack of warning on tasks as to what went wrong is very hard to debug… see above. It took an hour and a half to make this realization... And even more of the customer's time to get to the point where they asked to get on a call... 

#### The ask

Show the shell being used to run tasks or give more than just an exit code if possible. We need more context as what's actually going on when a task is being run.

I think this is a generic problem with any extension that relies on tasks and not just the Azure Functions extension.
Repository: flutter
Issue: Material Colors stored in a Map are not const and cannot be used as constructor defaults
Labels: framework,f: material design,c: proposal,team-design,triaged-design

## Use Case

**Reproduction**
Code up a ```Widget``` which uses a default value for a ```Color```.  For example

```Dart
class DisplayArray extends StatelessWidget {
  final Color onColor;

  DisplayArray({
      this.onColor = Colors.red.shade900,

// and so on
```
**Expected**
The code complies because the ```Color``` constructor is a ```const``` constructor.  So, ```Colors.red.shade900``` should likewise be ```const```.

**Actual**
The code does not compile.  The color ```Colors.red.shade900``` is stored in a ```Map```.    The complier seems to be unable to work out that ```Colors.red.shade900``` is ```const```.

**Workaround**
I found that I had to redefine the ```Color``` from the ```Colors``` class in my own project as as 

```Dart
const Color RED_SHADE_900 = const Color(0xFFB71C1C);
```
This approach seems a bit messy to me.  Code is duplicated simply for the sake of making Colors.red.shade900 appear as ```const```.

## Proposal

Define the material colors as ```const```.

**Futter Doctor**

```
➜  ~ flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, v1.12.13+hotfix.5, on Mac OS X 10.15.2 19C57,
    locale en-CA)
 
[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 11.3)
[✓] Android Studio (version 3.5)
[✓] IntelliJ IDEA Community Edition (version 2019.3)
[!] VS Code (version 1.32.3)
    ✗ Flutter extension not installed; install from
      https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter
[✓] Connected device (1 available)

! Doctor found issues in 1 category.
```
Repository: angular
Issue: Property getter/setter behavor difference when using @angular/elements
Labels: type: bug/fix,area: elements,state: confirmed,P3

# 🐞 bug report

### Affected Package
The issue is related to the package @angular/elements

### Is this a regression?
No

### Description
In the demo below you will see a (common?) pattern of initializing data in an angular component.  There are many ways to do this but essentially it is common (for me at least) to initialize data in a property setter.  This works fine in angular components, however, when the component is used in a custom element via angular/elements (as you will see) the property setter is not called if the attribute value is the same as the value returned from the getter.

Putting it another way...  In angular components, during initialization, the property value is set regardless of the current property value.  However, in angular elements, the value is first retrieved and only set if the new value is different from the current value.

Obviously, there are many ways to refactor the code to avoid this issue but is surprizing at a minimum and very frustrating if you don't know what's going on (my experience).

## 🔬 Minimal Reproduction
https://stackblitz.com/edit/angular-elements-demo-fnulni

## 🔥 Exception or Error
No error.  This can result in unexpected behavior for angular element users that expect property setters to be called during initialization.

## 🌍  Your Environment

**Angular Version:**
Tested in both v8 and v9-rc.
Repository: flutter
Issue: Show back button instead of the menu button when both are used.
Labels: framework,f: cupertino,c: proposal,team-design,triaged-design

<!-- Thank you for using Flutter!

     If you are looking for support, please check out our documentation
     or consider asking a question on Stack Overflow:
      * https://flutter.dev/
      * https://api.flutter.dev/
      * https://stackoverflow.com/questions/tagged/flutter?sort=frequent

     If you have found a bug or if our documentation doesn't have an answer
     to what you're looking for, then fill our the template below. Please read
     our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports
-->

## Use case
On iOS there is no way to go back when you both have a route below and a drawer, as the menu button overwrites the back button.
<!--
     Please tell us the problem you are running into that led to you wanting
     a new feature.

     Is your feature request related to a problem? Please give a clear and
     concise description of what the problem is.

     Describe alternative solutions you've considered. Is there a package
     on pub.dev/flutter that already solves this?
-->

## Proposal
Show the back button instead of the menu button in the app bar when both a drawer and a route below is used. The drawer can always be opened with a swipe gesture, but you cannot always go back on iOS as there are no hardware/software back buttons.
<!--
     Briefly but precisely describe what you would like Flutter to be able to do.

     Consider attaching images showing what you are imagining.

     Does this have to be provided by Flutter directly, or can it be provided
     by a package on pub.dev/flutter? If so, maybe consider implementing and
     publishing such a package rather than filing a bug.
-->
Repository: TypeScript
Issue: Useless scary elaboration on all overloads in JSX
Labels: Suggestion,Experience Enhancement


```
git clone https://github.com/React95/React95/
git checkout 57dc66d8a087792fd8fa0f1cfb7c7560767e8520
yarn
```

1. Open up VS Code in the base
1. Open up the file packages/core/components/Checkbox.jsx
1. Go to line 100
1. Make a change

   ```
   - <Label {...style} checked={checked} disabled={disabled}>
   + <Label style={style} checked={checked} disabled={disabled}>
   ```

Observe the error message:

```
No overload matches this call.
  Overload 1 of 2, '(props: Pick<Pick<Pick<DetailedHTMLProps<LabelHTMLAttributes<HTMLLabelElement>, HTMLLabelElement>, "form" | ... 255 more ... | "htmlFor"> & { ...; }, "form" | ... 256 more ... | "htmlFor"> & Partial<...>, "form" | ... 256 more ... | "htmlFor"> & { ...; } & { ...; }): ReactElement<...>', gave the following error.
    Type '{ children: Element[]; style: any; checked: any; disabled: any; }' is not assignable to type 'IntrinsicAttributes & Pick<Pick<Pick<DetailedHTMLProps<LabelHTMLAttributes<HTMLLabelElement>, HTMLLabelElement>, "form" | ... 255 more ... | "htmlFor"> & { ...; }, "form" | ... 256 more ... | "htmlFor"> & Partial<...>, "form" | ... 256 more ... | "htmlFor"> & { ...; } & { ...; }'.
      Property 'checked' does not exist on type 'IntrinsicAttributes & Pick<Pick<Pick<DetailedHTMLProps<LabelHTMLAttributes<HTMLLabelElement>, HTMLLabelElement>, "form" | ... 255 more ... | "htmlFor"> & { ...; }, "form" | ... 256 more ... | "htmlFor"> & Partial<...>, "form" | ... 256 more ... | "htmlFor"> & { ...; } & { ...; }'.
  Overload 2 of 2, '(props: StyledComponentPropsWithAs<"label", any, {}, never>): ReactElement<StyledComponentPropsWithAs<"label", any, {}, never>, string | ... 1 more ... | (new (props: any) => Component<...>)>', gave the following error.
    Type '{ children: Element[]; style: any; checked: any; disabled: any; }' is not assignable to type 'IntrinsicAttributes & Pick<Pick<Pick<DetailedHTMLProps<LabelHTMLAttributes<HTMLLabelElement>, HTMLLabelElement>, "form" | ... 255 more ... | "htmlFor"> & { ...; }, "form" | ... 256 more ... | "htmlFor"> & Partial<...>, "form" | ... 256 more ... | "htmlFor"> & { ...; } & { ...; }'.
      Property 'checked' does not exist on type 'IntrinsicAttributes & Pick<Pick<Pick<DetailedHTMLProps<LabelHTMLAttributes<HTMLLabelElement>, HTMLLabelElement>, "form" | ... 255 more ... | "htmlFor"> & { ...; }, "form" | ... 256 more ... | "htmlFor"> & Partial<...>, "form" | ... 256 more ... | "htmlFor"> & { ...; } & { ...; }'.ts(2769)
```

![image](https://user-images.githubusercontent.com/972891/71563215-cb947880-2a40-11ea-8147-b510b2555a5e.png)
Repository: flutter
Issue: [in_app_purchase] Support for test billing on Android?
Labels: c: new feature,platform-android,p: in_app_purchase,package,c: proposal,dependency: android,P3,team-android,triaged-android

I'm trying to submit a test purchase with id of 'android.test.purchased' but receiving an error: 
_Unhandled Exception: PlatformException(NOT_FOUND, Details for sku android.test.purchased are not available. Has this ID already been fetched?, null)_

Is this use case supported?
https://developer.android.com/google/play/billing/billing_testing

[√] Flutter (Channel stable, v1.12.13+hotfix.5, on Microsoft Windows [Version 10.0.18362.535], locale en-US)
    • Flutter version 1.12.13+hotfix.5 at D:\_Development\_mobile\flutter
    • Framework revision 27321ebbad (3 weeks ago), 2019-12-10 18:15:01 -0800
    • Engine revision 2994f7e1e6
    • Dart version 2.7.0

[√] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at C:\Users\Shawn\AppData\Local\Android\sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 28.0.3
    • Java binary at: C:\Program Files\Android\Android Studio New\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)
    • All Android licenses accepted.

[√] Android Studio (version 3.5)
    • Android Studio at C:\Program Files\Android\Android Studio New
    • Flutter plugin version 40.2.2
    • Dart plugin version 191.8593
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)

[√] VS Code (version 1.41.1)
    • VS Code at C:\Users\Shawn\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.7.1

[√] Connected device (1 available)
    • AOSP on IA Emulator • emulator-5554 • android-x86 • Android 9 (API 28) (emulator)

• No issues found!
Repository: TypeScript
Issue: Can't evaluate equality of symbols made by Symbol.for
Labels: Suggestion,Awaiting More Feedback

This is also an obstacle of branded types and ghost types. I think resolving this problem is easy because these types are just a new literal type similar to string literal types.

<!--
Please try to reproduce the issue with the latest published version. It may have already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly
-->
**TypeScript Version:**  3.7.x-dev.20191228

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**

**Code**

```ts
const a = Symbol.for('');
const b = Symbol.for('');
const c: typeof b = Symbol.for(''); // error
a === b; // error
```

**Expected behavior:**
no error
**Actual behavior:**
Type 'typeof b' is not assignable to type 'typeof a'.
This condition will always return 'false' since the types 'typeof a' and 'typeof b' have no overlap.
**Playground Link:** https://www.typescriptlang.org/play/index.html?ts=3.8.0-dev.20191228&ssl=1&ssc=1&pln=4&pc=18#code/MYewdgzgLgBAhjAvDAygTwLYCMQBsB0AZiAE4AUA5BQJQDcAUKJLFkqpjgceVXY+NBjAAXDChoADgFMQhGK2TpseIqUo1aMAPRaYUkiVL0EiU-M069B0kA

**Related Issues:** #35200
Repository: angular
Issue: When using the Unified Angular Location Service, AngularJS useHash paths have their leading slashes removed
Labels: type: bug/fix,area: common,freq1: low,area: upgrade,state: confirmed,P3

# 🐞 bug report

### Affected Package
The issue is caused by package @angular/common/upgrade

### Is this a regression?
I don't think so.  The Unified Location Service was introduced in 8.x and I think it's always behaved this way.

### Description

When:
- The Unified Location Service is being used
- The `{ useHash: true }` mode is active
- AngularJS code sets the path via `$location.path()`
- The path has a leading slash, such as `/mypath'

I expect the URL to be: 
```
http://mydomain.com/index.html#/mypath
```
But instead, the leading slash is removed before it's applied to the location's hash:
```
http://mydomain.com/index.html#mypath
```

## 🔬 Minimal Reproduction
[This stackblitz](https://stackblitz.com/edit/angular-hybrid-uniified-location?file=angularjs.module.ts) shows a matrix of scenarios:

||useHash: true|useHash: false|
|-|-|-|
|`$location.path('/slash')` (AngularJS $locationShim)|❌|✅|
|`$locationpath('noslash')` (AngularJS $locationShim)|✅|✅|
|`location.go('/slash')` (Angular Location)|✅|✅|
|`location.go('noslash') (Angular Location)|✅|✅|


## 🌍  Your Environment

**Angular Version: 8**
with @angular/upgrade

**Anything else relevant?**
This was reported to me by a UI-Router Hybrid user trying to enable the Unified Angular Location Service. https://github.com/ui-router/angular-hybrid/issues/320

A simple workaround is to continue to use the AngularJS `$location` service for URL management and upgrade it via ngUpgrade to be used in Angular services.
Repository: TypeScript
Issue: Support Type Acquisition From Npx Shebang
Labels: Suggestion,Awaiting More Feedback

Originally filed under https://github.com/microsoft/vscode/issues/87834.

## Search Terms
shebang, npx, type acquisition

## Suggestion
When authoring JS scripts that are to be invoked using `npx`, it would be great if the typing information could be inferred from the package that `npx` will call.

## Use Cases
I'm currently building a library, where primary use case is to be consumed as executable scripts, with `npx` as the shebang command (this allows for global execution without the need for prior installation). And since all of the needed functionality is automatically injected into the global scope there is no need for external references.  This is intended for portability and ease of authoring.

When authoring these scripts, the desire is to leverage the typings provided by the library called by `npx`. The assumption here is that the toolchain would detect the `npx` invocation in the shebang, and load the appropriate typings (local if library is previously installed, or downloaded if not).

## Examples
```javascript
#!/usr/bin/npx @arcsine/nodesh
stdin
  .sort()
  .unique()
  .stdout
```

In the sample above, `stdin` is a global variable that should be picked up via intellisense, and the methods it exposes should be searchable (with the associated docs).

## Considerations
Alternatively, one thought was to leverage a triple-slash directive, but that is limited as it cannot:
* point to global node modules (without an absolute path)
* reference ephemeral libraries as loaded by npx

## Checklist
My suggestion meets these guidelines:
* [ ] This wouldn't be a breaking change in existing TypeScript/JavaScript code 
* [x] This wouldn't change the runtime behavior of existing JavaScript code
* [x] This could be implemented without emitting different JS based on the types of the expressions
* [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).
Repository: rust
Issue: Support TCP_FASTOPEN in TcpStream and TcpListener
Labels: T-libs-api,C-feature-request

## Background

`TcpStream` and `TcpListener` in `libstd` doesn't support [TCP Fast Open (TFO)](https://en.wikipedia.org/wiki/TCP_Fast_Open). Because (in Linux)

1. `TcpListener` must call `setsockopt` with `TCP_FASTOPEN` after `listen(..)`
2. `TcpStream`
    * Kernel >= 4.11, call `setsockopt` with `TCP_FASTOPEN_CONNECT` before `connect`
    * Otherwise, call `sendto` with flag `MSG_FASTOPEN`

Since libraries out there (`mio`, `tokio`, `async_std`, ...) use `net::TcpStream` and `net::TcpListener` inside there implementation, supporting TFO in `libstd` would be the best solution for all.

## Cross Platform

1. Linux (as mentioned above)
2. OS X
    - `TcpListener` calls `setsockopt` with `TCP_FASTOPEN` after `listen(...)`
    - For TCP clients, uses `connectx` instead of `connect`
        - `associd`: `SAE_ASSOCID_ANY`
        - `flags`: `CONNECT_RESUME_ON_READ_WRITE | CONNECT_DATA_IDEMPOTENT`
3. Windows
    - `TcpListener` calls `setsockopt` with `TCP_FASTOPEN` after `listen(...)`
    - For TCP clients, uses `ConnectEx`
        * Call `setsockopt` with `SO_UPDATE_CONNECT_CONTEXT`, otherwise `getpeername` won't work
            > When the ConnectEx function returns, the socket s is in the default state for a connected socket.
            > The socket s does not enable previously set properties or options until SO_UPDATE_CONNECT_CONTEXT is set.
Repository: godot
Issue: AnimationTree Add3's +add and -add act differently
Labels: bug,confirmed,topic:animation

the documentation isn't particularly detailed but I can't see any reason why +add and -add should act any differently for the same animation. I'm also not sure why it appears to act more like blend than add in this instance, shouldn't it move sideways and up/down with both -1 and 1?
tested on 3.1, 3.1.2 and master in linux X11

![out](https://user-images.githubusercontent.com/10767978/71565277-2cd93d80-2a7b-11ea-92f8-a950e4347ac4.gif)

[test_anim2.zip](https://github.com/godotengine/godot/files/4008799/test_anim2.zip)
Repository: godot
Issue: Exceptions when changing focus or completing a process in iOS (Xcode)
Labels: bug,platform:ios,topic:porting,crash

Godot version: 3.1.1
OS/device including version: ANY

If during application launch, unload the application or change focus to another application - it throws an exception

Friends, my hands are falling. I can not find the source of the error.
I no longer know where to look for the cause of the error

A simple 2D game for little children. There is nothing but a third-party “Share” module.
An exception is thrown when the focus changes or the application is suddenly unloaded while the application is still loading. (Users do not notice this error, this is a background bug)

![Image screen1](https://i.imgur.com/NPp03Gm.png)
![Image screen2](https://i.imgur.com/LXDhOpk.png)

TEMPLATE COMPILING IOS:
```
platform=iphone target=release optimize=size tools=no use_lto=no deprecated=no game_center=no minizip=no xaudio2=no disable_advanced_gui=yes disable_3d=yes no_editor_splash=yes builtin_bullet=no builtin_certs=no builtin_enet=no builtin_libvpx=no builtin_libwebp=no builtin_libwebsockets=no builtin_mbedtls=no builtin_miniupnpc=no builtin_opus=no builtin_pcre2=no builtin_recast=no builtin_squish=no builtin_thekla_atlas=no builtin_xatlas=no debug_symbols=no separate_debug_symbols=no module_bullet_enabled=no module_csg_enabled=no module_cvtt_enabled=no module_dds_enabled=no module_enet_enabled=no module_gdnative_enabled=no module_gridmap_enabled=no module_hdr_enabled=no module_jpg_enabled=no module_mbedtls_enabled=no module_mobile_vr_enabled=no module_mono_enabled=no module_opensimplex_enabled=no module_opus_enabled=no module_pvr_enabled=no module_recast_enabled=no module_regex_enabled=no module_squish_enabled=no module_svg_enabled=no module_tga_enabled=no module_thekla_unwrap_enabled=no module_theora_enabled=no module_tinyexr_enabled=no module_upnp_enabled=no module_visual_script_enabled=no module_webm_enabled=no module_webp_enabled=no module_websocket_enabled=no module_xatlas_unwrap_enabled=no config=force
```
Repository: rust
Issue: Allow deny/forbid level lints in macros to cross crate boundaries
Labels: A-lints,A-macros,T-lang,C-feature-request

I'm attempting to add an `assert_ffi_safe!` macro to `static_assertions` by creating an `extern "C"` block with a function that references the input types and marking it with `#[forbid(improper_ctypes)]` (see https://github.com/nvzqz/static-assertions-rs/pull/31). However, while the macro works correctly if used within the same crate, it results in false positives when used externally. This is evidenced by `compile_fail` doc tests passing.

I imagine that `rustc` lints are disabled when calling into a macro that is not defined within the calling crate so that they don't become a nuisance to consumers who have no control over the code within the macro. This is a case where ensuring that lints work across crate boundaries would be beneficial.