sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: [Web][Html]: ShaderMask's `blendMode: BlendMode.dstIn` property not rendering correctly.
Labels: engine,a: fidelity,platform-web,c: rendering,e: web_html,has reproducible steps,P2,found in release: 2.2,team-web,triaged-web

I found this issue when using flutter stable, 2.2.1. It shows correctly on desktop and shows the wrong result on mobile devices. 

## Steps to Reproduce

1. Use the following code to build flutter web application  with canvaskit web renderer

<details>
<summary>minimal reproducible code</summary>
<br>

```dart
import 'package:flutter/material.dart';

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        body: ShaderMask(
            shaderCallback: (rect) {
              return const RadialGradient(
                radius: 0.4,
                colors: [Colors.black, Colors.transparent],
              ).createShader(Rect.fromLTRB(0, 0, rect.width, rect.height));
            },
            blendMode: BlendMode.dstIn,
            child: Container(color: Colors.red,),
        ),
      ),
    );
  }
}
```
</details>

**Expected results:**

- flutter build web --web-renderer canvaskit
![canvaskit](https://user-images.githubusercontent.com/67259829/121334527-507d0480-c94c-11eb-9cd7-53e63b3bb023.PNG)

**Actual results:**

- flutter build web --web-renderer html
![html](https://user-images.githubusercontent.com/67259829/121334573-5a066c80-c94c-11eb-8ae8-07e1f2146ccb.PNG)


<details>
<summary>flutter doctor -v</summary>
<br>
[√] Flutter (Channel stable, 2.2.1, on Microsoft Windows [Version 10.0.19042.985], locale zh-TW)
    • Flutter version 2.2.1 at C:\src\flutter
    • Framework revision 02c026b03c (12 days ago), 2021-05-27 12:24:44 -0700
    • Engine revision 0fdb562ac8
    • Dart version 2.13.1

[√] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at C:\Android\sdk
    • Platform android-30, build-tools 29.0.3
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6842174)
    • 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 C:\Program Files\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 11.0.8+10-b944.6842174)

[√] Connected device (2 available)
    • Chrome (web) • chrome • web-javascript • Google Chrome 91.0.4472.77
    • Edge (web)   • edge   • web-javascript • Microsoft Edge 91.0.864.41


</details>
Repository: node
Issue: Change in node v14.17.0 broke the mtimeMs comparison for source/target files in gulp-changed
Labels: fs,libuv

<!--
Thank you for reporting an issue.

This issue tracker is for bugs and issues found within Node.js core.
If you require more general support please file an issue on our help
repo. https://github.com/nodejs/help


Please fill in as much of the template below as you're able.

Version: output of `node -v`
Platform: output of `uname -a` (UNIX), or output of `"$([Environment]::OSVersion | ForEach-Object VersionString) $(if ([Environment]::Is64BitOperatingSystem) { "x64" } else { "x86" })"` in PowerShell console (Windows)
Subsystem: if known, please specify affected core module name
-->

* **Version**: v14.17.0
* **Platform**: Darwin gav-mbp 19.6.0 Darwin Kernel Version 19.6.0: Tue Nov 10 00:10:30 PST 2020; root:xnu-6153.141.10~1/RELEASE_X86_64 x86_64
* **Subsystem**: not known

### What steps will reproduce the bug?

<!--
Enter details about your bug, preferably a simple code snippet that can be
run using `node` directly without installing third-party dependencies.
-->

Please see issue https://github.com/sindresorhus/gulp-changed/issues/83

### How often does it reproduce? Is there a required condition?

It reproduces 100% of the time

### What is the expected behavior?

<!--
If possible please provide textual output instead of screenshots.
-->

### What do you see instead?

<!--
If possible please provide textual output instead of screenshots.
-->

### Additional information

<!--
Tell us anything else you think we should know.
-->
Repository: ant-design
Issue: @ant-design/compatible 与 Upload 组件使用疑问
Labels: 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/relaxed-mirzakhani-40y93)

### Steps to reproduce
如复现链接，在antd4.5.4版本时候
**不上传文件**
点击提交能正常运行 validateFieldsAndScroll

切换至 antd 4.6.0 版本时候
**不上传文件**
点击提交不能正常运行，且控制台报错。

### What is expected?
功能如4.5.4一致，或者改动的建议

### What is actually happening?
无法运行validateFieldsAndScroll 并且控制台报错

| Environment | Info |
|---|---|
| antd | 4.6.0 |
| React | 16.8 |
| System | Mac 10.14.3  |
| Browser | Chrome 90.0.4430.212 |

---
旧有业务，原先可行。


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: rust
Issue: Debuginfo type names: Clarify how to handle impl-prefixed paths 
Labels: A-debuginfo,T-compiler,C-bug

Currently paths in stringified type names emitted to debuginfo are generated [by simply concatenating the components of corresponding `DefPath`s](https://github.com/rust-lang/rust/blob/a50d72158e08e02cfc051b863017bdbd2c45b637/compiler/rustc_codegen_ssa/src/debuginfo/type_names.rs#L289-L298). For paths involving `impls` this leads to a rendering that is out of sync with how such paths are presented in error messages and symbol demangling. For example we get something like:
```
foo::bar::{impl#2}::baz
```
where we would actually like to have something like:
```
<foo::bar::SomeType>::baz // if this an inherent impl
<foo::bar::SomeType as xyz::SomeTrait>::baz // if this is a trait impl
```
or in the case of the more machine-oriented/C++-like names generated for MSVC debuggers:
```
impl$<foo::bar::SomeType>::baz // if this an inherent impl
impl$<xyz::SomeTrait, foo::bar::SomeType>::baz // if this is a trait impl
```

Open questions are:
- Should the path to the impl be included, as in `abc::def::impl$<foo::bar::SomeType>::baz` vs just `impl$<foo::bar::SomeType>::baz`? 
- Do we need a disambiguator for impls so we can avoid ambiguous names in case of specialization. Or is that too much detail in this context? (see the [equivalent for symbol mangling](https://rust-lang.github.io/rfcs/2603-rust-symbol-name-mangling-v0.html#items-within-generic-impls)).
- Is there value (in particular for this feature) in porting debuginfo type name generation to the `ty::print::Printer` framework?
- How exactly does this interact with the DWARF namespace tree that we generate in debuginfo?
Repository: flutter
Issue: [web] canvas.drawShadow sometimes creates only outline
Labels: engine,dependency: skia,platform-web,c: rendering,e: web_canvaskit,has reproducible steps,P3,found in release: 2.2,found in release: 2.5,team-web,triaged-web


## Steps to Reproduce

<!-- You must include full steps to reproduce so that we can reproduce the problem. -->

1. Run this Code in DartPad

``` import 'package:flutter/material.dart';

final Color darkBlue = Color.fromARGB(255, 18, 32, 47);

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      theme: ThemeData.dark().copyWith(scaffoldBackgroundColor: darkBlue),
      debugShowCheckedModeBanner: false,
      home: Scaffold(
        body: Center(
          child: MyWidget(),
        ),
      ),
    );
  }
}

class MyWidget extends StatefulWidget {
  @override
  _MyWidgetState createState() => _MyWidgetState();
}

class _MyWidgetState extends State<MyWidget> {
  
  int counter = 10;
  
  @override
  Widget build(BuildContext context) {
    return Container(
      child: Column(
        children: [
          Spacer(),
          Container(
            width: counter*10, 
            height:counter*10,
            color: Colors.white,
            child: CustomPaint(
              painter: MyPainter(),
              child:  SizedBox.shrink()
            ),
          ),
          Row(
            children: [
              Spacer(),
              IconButton(icon: Icon(Icons.remove), onPressed: () {setState(() {counter--;});}),
              Text("$counter"),
              IconButton(icon: Icon(Icons.add), onPressed: () {setState(() {counter++; });}),
              Spacer(),
            ],
          ),
          Text("Shadow is ok at values 0 and 7-11"),
          Spacer(),
        ],
      ),
    );
  }
}

class MyPainter extends CustomPainter {

  @override
  void paint(Canvas canvas, Size size) {
        Path path = Path();
    path.moveTo(30, 30);
    path.lineTo(size.width - 30, 30);
    path.lineTo(size.width - 30, size.height - 30);
    path.lineTo(size.width/2 - 30, size.height/2 - 30);
    path.lineTo(30, size.height - 30);
    path.close();
      canvas.drawShadow(path.shift(Offset(10.0,10.0)), Colors.black, 1.0, true);
      canvas.drawPath(path, Paint()..color = Colors.red..style = PaintingStyle.fill);
  }

  @override
  bool shouldRepaint(CustomPainter oldDelegate) => true;
}

```

2. Change the size of the Container with the + to 12 or more

**Expected results:** 
A Shadow like the one at value "10"
![Bildschirmfoto zu 2021-06-09 15-51-43](https://user-images.githubusercontent.com/10772789/121367617-bd879e80-c93a-11eb-8a9f-9186e05d642a.png)


**Actual results:** 
A broken shadow like the one at value "15"
![Bildschirmfoto zu 2021-06-09 15-52-01](https://user-images.githubusercontent.com/10772789/121367706-d1330500-c93a-11eb-95f7-8a1113c58dbe.png)
Repository: godot
Issue: TouchScreenButton ConcavePolygonShape2d doesn't work
Labels: bug,topic:core,topic:editor,usability

### Godot version

3.3.2

### System information

osX 11.4

### Issue description

TouchScreenButton ConcavePolygonShape2d doesn't work.

In the Godot editor, the Shape property can be selected but you can't use the Scale mode to shape the TouchScreenButton. 

The handle appear moving them doesn't create or display the button fields. 

### Steps to reproduce

Create a TouchScreenButton node.

Select the Shape: ConcavePolygonShape2d in the Inspector.

Try to Scale the Field. 

### Minimal reproduction project

_No response_
Repository: terminal
Issue: Adopt VT extension "Unscrolling the screen" from Kitty
Labels: Issue-Feature,Area-VT,Product-Terminal

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement.
2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement.
3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement.
5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement.

All good? Then proceed!
-->

# Description of the new feature/enhancement

Kitty has recently shipped an awesome VT extension to the SD (Pan up) escape code from the VT-420 terminal to tackle the issues with text being lost under the cursor.  I'd like to see this added in Windows Terminal as well. See https://sw.kovidgoyal.net/kitty/protocol-extensions.html#unscrolling-the-screen. As there have been several issues raised in the past surrounding this issue, this appears to be the perfect solution to prevent further issues from being raised about it. Also, since Windows Terminal adopted private extensions from ConEmu to address other issues, I see no reason why we can't also adopt some of Kitty's protocol extensions as well.

<!-- 
A clear and concise description of what the problem is that the new feature would solve.
Describe why and how a user would use this new functionality (if applicable).
-->

# Proposed technical implementation details (optional)

<!-- 
A clear and concise description of what you want to happen.
-->
Repository: flutter
Issue: flutter test --name not accepting lookahead syntax due to SETLOCAL ENABLEDELAYEDEXPANSION in batch entrypoint
Labels: a: tests,tool,a: quality,P2,team-tool,triaged-tool

Hi, I was just trying to ignore some of my golden tests, whose name starts by `Golden` and decided to use this:

```sh
flutter test --name "^(?!Golden).+"
```

What I receive from the CLI is this instead: `Couldn't parse --name "[(?Golden).+]": Invalid group(?Golden).+`

Note that the `!` from the lookahead is gone.

I've tried to review the code but I can't see any kind of sanitizer process. I've also seen that [you're using the args package](https://github.com/dart-lang/test/blob/cd91c38f184fe7162ecbab8bfa2f15d2a335015d/pkgs/test_core/lib/src/runner/configuration/args.dart#L184) and I did a quick test of that library without success. It works as expected. So there may be another place where this substitution of the `!` is taking place.

Maybe I'm missing something obvious. If you could point me in the right direction I would create a PR in order to fix this.
Repository: flutter
Issue: Support running devtools in machine mode for IDEs
Labels: tool,P3,c: tech-debt,team-tool,triaged-tool

This would allow us to simplify some of the IDE plugin code for intellij: https://github.com/flutter/flutter-intellij/issues/5560
Repository: angular
Issue: Cannot bind `undefined` to safe resource URL property
Labels: area: core,core: sanitization,P3

# Bug Report

### Affected Package
The issue is eventually caused by this code:

https://github.com/angular/angular/blob/3de774e778b4619050ce1dc407c53caeed8b6c92/packages/core/src/sanitization/sanitization.ts#L111-L121


### Is this a regression?

Probably not. However, Angular 11 compiled to ES5 (old-style config for legacy browsers, without differential loading) behaves differently.

### Description
This template HTML compiles on strict mode:

```html
<iframe [src]="undefined"></iframe>
```

It will, however, throw an exception at runtime or in tests at `fixture.detectChanges();`.

I believe `undefined` is not an unsafe value. However, it probably should not be tested with the sanitizer in the first place.

## Minimal Reproduction

https://github.com/fuzzykiller/ng-sanitizer-problem

Run `npm i` and `ng test` to see error.

## Exception or Error
<pre><code>Error: unsafe value used in a resource URL context (see https://g.co/ng/security#xss)
    at ɵɵsanitizeResourceUrl (http://localhost:9876/_karma_webpack_/webpack:/node_modules/@angular/core/__ivy_ngcc__/fesm2015/core.js:5984:1)
    at elementPropertyInternal (http://localhost:9876/_karma_webpack_/webpack:/node_modules/@angular/core/__ivy_ngcc__/fesm2015/core.js:10000:1)
    at ɵɵproperty (http://localhost:9876/_karma_webpack_/webpack:/node_modules/@angular/core/__ivy_ngcc__/fesm2015/core.js:14760:1)
    at AppComponent_Template (ng:///AppComponent.js:6:21)
    at executeTemplate (http://localhost:9876/_karma_webpack_/webpack:/node_modules/@angular/core/__ivy_ngcc__/fesm2015/core.js:9575:1)
    at refreshView (http://localhost:9876/_karma_webpack_/webpack:/node_modules/@angular/core/__ivy_ngcc__/fesm2015/core.js:9441:1)
    at refreshComponent (http://localhost:9876/_karma_webpack_/webpack:/node_modules/@angular/core/__ivy_ngcc__/fesm2015/core.js:10612:1)
    at refreshChildComponents (http://localhost:9876/_karma_webpack_/webpack:/node_modules/@angular/core/__ivy_ngcc__/fesm2015/core.js:9238:1)
    at refreshView (http://localhost:9876/_karma_webpack_/webpack:/node_modules/@angular/core/__ivy_ngcc__/fesm2015/core.js:9491:1)
    at renderComponentOrTemplate (http://localhost:9876/_karma_webpack_/webpack:/node_modules/@angular/core/__ivy_ngcc__/fesm2015/core.js:9555:1)</code></pre>


## Your Environment

**Angular Version:**
<pre><code>Angular CLI: 12.0.3
Node: 14.17.0
Package Manager: npm 6.14.8
OS: win32 x64

Angular: 12.0.3
... animations, cli, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1200.3
@angular-devkit/build-angular   12.0.3
@angular-devkit/core            12.0.3
@angular-devkit/schematics      12.0.3
@schematics/angular             12.0.3
rxjs                            6.6.7
typescript                      4.2.4</code></pre>

**Anything else relevant?**

Not that I can think of.
Repository: flutter
Issue: [Camera] Support touch focus
Labels: c: new feature,p: camera,package,c: proposal,team-ecosystem,P3,triaged-ecosystem

Camera doesn't support touch focus yet, it only supports the auto and locked focus.

This is a critical feature for social media applications like snapchat, instagram, tiktok and the likes.
Repository: rust
Issue: Compile error: static lifetime not satisfied but it is
Labels: A-lifetimes,P-high,T-compiler,regression-from-stable-to-stable,C-bug,WG-async

I tried this code:
```rust
use std::{
    future::Future,
    marker::PhantomData,
    {pin::Pin, sync::Arc},
};

fn validate_signature() -> impl Future<Output = ()> + Send {
    let certificate_store = Cache::<CertificateRetriever>::new();
    let res = Box::pin(async move {
        certificate_store.get().await;
    });
    fn foo<T: 'static>(_c: &T) {}
    res
}

type CertificateRetriever =
    Arc<dyn Retrieve<Future = Pin<Box<dyn Future<Output = ()> + Send + 'static>>>>;

trait Retrieve: Send + Sync {
    type Future: Future<Output = ()> + Send + 'static;

    fn get(&self) -> Self::Future;
}

impl<R: Retrieve + ?Sized> Retrieve for Arc<R> {
    type Future = R::Future;

    fn get(&self) -> Self::Future {
        todo!()
    }
}

struct Cache<R: Retrieve> {
    marker: PhantomData<R>,
}

impl<R> Cache<R>
where
    R: Retrieve + 'static,
{
    fn new() -> Self {
        todo!()
    }
    async fn get(&self) {
        self.get_value().await
    }

    fn get_value(&self) -> R::Future {
        todo!()
    }
}

```
[Playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=264bf5dbdc598ac4a0e4aed54ff64a34)

I expected to see this to compile fine, minor changes to the code cause it to compile.

Instead, I get this error:
```
error[E0477]: the type `Pin<Box<dyn Future<Output = ()> + Send>>` does not fulfill the required lifetime
 --> src/lib.rs:7:28
  |
7 | fn validate_signature() -> impl Future<Output = ()> + Send {
  |                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  |
  = note: type must satisfy the static lifetime

error: aborting due to previous error
```

This may be a duplicate of #80052 but as it involves no associated constants I'm keeping it separate for now.
Compiled with rustc 1.52.1
Repository: ant-design
Issue: Carousel with centerMode, slidesToShow, infinite={false}, can't reach last elements
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.

### Reproduction link
[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/antd-reproduction-template-forked-i71gt?file=/index.js)

### Steps to reproduce
When `centerMode` is on, `infinite` is set to `false`, `slidesToShow` is set to `k`, the last `n - k  + 1` elements are unreachable
例子里，最后一页只能看到5th element

### What is expected?
http://jsfiddle.net/6dL340pv/
This is an example from react-slick, where each element corresponds to a dot and is reachable with the same settings.
我想实现的是在centerMode on, infinite off时，n个element应该对应n个dot/page，每个element都可以被center，像jsfiddle例子里一样

### What is actually happening?
I'm not sure why the page/dot number would be `(n-k+1)` with these settings
我不知道为什么最多向后翻`(n-k+1)`页

| Environment | Info |
|---|---|
| antd | 4.8.6 |
| React | 17.0 |
| System | macOS Mojave 10.14.6 |
| Browser | Chrome 91.0.4472 |

---
If you enable arrow, arrowNext is actually doesn't work once you reach `n - k + 1`th element. In the example, `beforeChange(from, to) => {console.log(from, to)}` would just output `2, 2`. And `.slick-current` class won't reach later elements either.


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: flutter
Issue: Cannot create Chrome Extensions using flutter with canvaskit due to CSP violation
Labels: engine,platform-web,e: web_canvaskit,P3,team-web,triaged-web

Hi, pretty much the statement above. I realised this when I tried to compile it for Chrome today. Attached is a screenshot to show the issue. Have not attached any code to reproduce it
![flutter_extension_error](https://user-images.githubusercontent.com/71311548/121416068-03b61f80-c986-11eb-9bda-147a99f78414.PNG)

Any way to mitigate this soon?
Repository: go
Issue: cmd/compile: no debug information emitted for type used only as initializer
Labels: NeedsInvestigation,compiler/runtime

### What version of Go are you using (`go version`)?

<pre>
$ go version
1.16.3
</pre>

### Does this issue reproduce with the latest release?
Yes, and at tip.

### What did you do?

Debug the following program:
```
package main

import "fmt"

type inner struct{ val string }

type outer struct {
        val interface{}
}

var g = outer {
        val: inner{val: "val"},
}

func main() {
        fmt.Println(g) // breakpoint here and inspect g
}
```

### What did you expect to see?
A legible value for g.

### What did you see instead?
An error: `val: (unreadable interface type "main.inner" not found for 0x555a68: no type entry found, use 'types' for a list of valid types),}`

I think the problem is that because the `inner` type is only used in an initializer, there's never a need to reference its runtime type symbol in code. Because of that, the linker is able to prune the type symbol, and therefore never generates DWARF for the type.

cc @thanm