sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: attempting to encode an image causes widget test to hang
Labels: a: tests,engine,a: images,has reproducible steps,P2,found in release: 3.3,found in release: 3.6,team-engine,triaged-engine

## Steps to Reproduce

1. Run `flutter create bug`.
2. Update the files as follows: 
replace the contents of `test/widget_test.dart` with:
```
import 'dart:ui';

import 'package:flutter/material.dart';
import 'package:flutter/rendering.dart';
import 'package:flutter_test/flutter_test.dart';

void main() {
  testWidgets('test image encoding', (WidgetTester tester) async {
    final GlobalKey _globalKey = GlobalKey();
    await tester.pumpWidget(
      Directionality(
        child: RepaintBoundary(
          key: _globalKey,
          child: Text('Test'),
        ),
        textDirection: TextDirection.ltr,
      ),
    );

    expect(find.byType(RepaintBoundary), findsOneWidget);

    final b =
        _globalKey.currentContext.findRenderObject() as RenderRepaintBoundary;
    final image = await b.toImage();
    await image.toByteData(format: ImageByteFormat.png);
  });
}
```
3. run `flutter test`
**Expected results:** test completes successfully
**Actual results:** test hangs, never times out. I can see its hanging on the last line as removing that line allows the test to complete successfully.

<details>
  <summary>Logs</summary>

```
flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, v1.14.4-pre.25, on Linux, locale en_AU.UTF-8)
 
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
[✓] Android Studio (version 3.5)
[✓] VS Code (version 1.41.1)
[✓] Connected device (1 available)

```
NOTE: I also see same results on stable v1.12.13+hotfix.5 which is where I first noticed this issue.

</details>
Repository: vscode
Issue: Soft-wrap JSON following a newline \n in a string
Labels: feature-request,editor-wrapping

Given JSON like the following I would like to be able to opt-into soft-wrapping following any `\n` within a JSON string. Such that this:

![image](https://user-images.githubusercontent.com/452414/72941037-3fb6f900-3d2d-11ea-9012-556ada28dacc.png)

Would render in the text editor similar to this when the feature is enabled:

![image](https://user-images.githubusercontent.com/452414/72941000-257d1b00-3d2d-11ea-9e18-b81bfceb0eef.png)

This feature could be enabled or disabled independent of the existing word wrap feature.
Repository: TypeScript
Issue: Typescript error highlighting not working with project references
Labels: Bug

*TS Template added by @mjbvz*

**TypeScript Version**: 3.8.0-beta

**Search Terms**
- composite
- references
- error reporting
- diagnostics 

---

<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->
<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: https://code.visualstudio.com/insiders/ -->

<!-- Use Help > Report Issue to prefill these. -->
- VSCode Version: 1.41.1
- OS Version: macOS Mojave 1.14.6

Steps to Reproduce:

1. Clone this repo: https://github.com/johnfn/example
2. Open the root folder in vscode as a project
3. Open foo.ts

```
let x: number;

x = "blahsdflhjh"
```

This should be underlined as an error, but it's not. 

Weirdly, if you add an empty .ts file in the topmost directory, everything starts working. 

Additionally, `tsc --watch` outputs it as an error, as expected. 

Does this issue occur when all extensions are disabled?: Yes
Repository: flutter
Issue: Discussion: Alternative way for TextSpan.recognizer?
Labels: framework,f: gestures,a: typography,c: proposal,P2,team-framework,triaged-framework

Currently the _painting_ package depends on the _gestures_ package only by the last stronghold, `TextSpan`. More specifically,
- `TextSpan.recognizer`.
- `InlineSpanSemanticsInformation.recognizer`, which is the semantics information collected from `TextSpan.recognizer`.
- `InlineSpan.recognizer`, which is deprecated and always returns null.

So basically `TextSpan.recognizer`.

If we can instead implement it in the _rendering_ package, then _painting_ will no longer depend _gestures_, allowing _gestures_ to import _services_ and _rendering_. This will at least make the API for the following issues a lot simpler:
- Mouse cursor https://github.com/flutter/flutter/issues/31952, because currently when to change mouse cursor is defined in _gestures_, while how to change mouse cursor (method channel) is defined in _services_.
- Correcting `localPosition` of mouse events https://github.com/flutter/flutter/issues/33675, because the hit test is defined in the _rendering_ package.

Also, I've noticed a few issues with the current design, as some additional incentives:
- `_LinkTextSpan` (which is the only reference of `TextSpan.recognizer` within Flutter) seems not to be very happy with this API
- `TextSpan.describeSemantics` hard-codes the recognizable gesture recognizers, which is not friendly to custom gestures.
Repository: rust
Issue: Diagnostics for mismatched generic types for constructors accessed via Self could show where the mismatch occurs
Labels: C-enhancement,A-diagnostics,A-associated-items,T-compiler,D-confusing,D-papercut

In this code, I used `Self::VariantName` to construct a new enum. However, since `Self` is treated as `Wrapper<T>`, I get an error when I try to populate `Self::There` / `Wrapper<T>::There` with a value of type `U`:

```rust
enum Wrapper<T> {
    There(T),
    NotThere,
}

impl<T> Wrapper<T> {
    fn map<U>(self, f: impl FnOnce(T) -> U) -> Wrapper<U> {
        match self {
            Self::There(v) => Self::There(f(v)),
            Self::NotThere => Self::NotThere,
        }
    }
}
```

([Playground](https://play.integer32.com/?version=stable&mode=debug&edition=2018&gist=d2020ec808cbb3a65df21fb04012ac22))

Errors:

```
error[E0308]: mismatched types
 --> src/lib.rs:9:43
  |
9 |             Self::There(v) => Self::There(f(v)),
  |                                           ^^^^ expected type parameter, found a different type parameter
  |
  = note: expected type `T`
             found type `U`
  = note: a type parameter was expected, but a different one was found; you might be missing a type parameter or trait bound
  = note: for more information, visit https://doc.rust-lang.org/book/ch10-02-traits.html#traits-as-parameters

error[E0308]: mismatched types
 --> src/lib.rs:9:31
  |
7 |     fn map<U>(self, f: impl FnOnce(T) -> U) -> Wrapper<U> {
  |                                                ---------- expected `Wrapper<U>` because of return type
8 |         match self {
9 |             Self::There(v) => Self::There(f(v)),
  |                               ^^^^^^^^^^^^^^^^^ expected type parameter, found a different type parameter
  |
  = note: expected type `Wrapper<U>`
             found type `Wrapper<T>`
  = note: a type parameter was expected, but a different one was found; you might be missing a type parameter or trait bound
  = note: for more information, visit https://doc.rust-lang.org/book/ch10-02-traits.html#traits-as-parameters
```

This threw me for a fair number of minutes, mostly spent saying "no, that function `f` takes a `T` and returns a `U`, not the other way around". 

Technically, the compiler *is* pointing to the entire call of `f` which should have tipped me off to realizing that it's the constructor call that was an issue.

Interestingly, the same problem doesn't occur for structs:

```rust
struct Wrapper<T>(T);

impl<T> Wrapper<T> {
    fn map<U>(self, f: impl FnOnce(T) -> U) -> Wrapper<U> {
        Self(f(self.0))
    }
}
```
Repository: go
Issue: net: document potential values for the "Op" in net.OpError
Labels: Documentation,NeedsInvestigation

The current documentation reads:

```go
// OpError is the error type usually returned by functions in the 
// net package. It describes the operation, network type, and address of an error.

type OpError struct {
    // Op is the operation which caused the error, such as
    // "read" or "write".
    Op string
```

As far as I am aware the only way to determine which "Op"'s exist is by grepping the source code of the `net` package.

In particular I am interested in determining whether an error with an `Op` value of `"dial"` could have ever been returned after a client sent bytes of a request to a remote HTTP server.
Repository: flutter
Issue: Fuchsia Message Loop implementation is susceptible to idle wakes.
Labels: customer: fuchsia,engine,P2,team-engine,triaged-engine

This is being temporarily reverted in https://github.com/flutter/engine/pull/15903. Once the underlying issue (described below) is patched, this patch can be re-landed. The original regression was introduced in https://github.com/flutter/engine/pull/14007.

The message loop implementations may be asked to wake up multiple times at various points in the future. When the implementation is asked to wake up the thread at the new time-point, the previous request must be disregarded. Once the time-point it reached, the implementation must call RunExpiredTasksNow. In the reverted patch, the Fuchsia implementation was scheduling a task to be run in the future for each call to [`MessageLoopImpl::WakeUp`](https://github.com/flutter/engine/pull/14007/files#diff-f2adf5aa8dfbf051d4691e57e091ace9R33). This did not take into account disregarding the previous requests. [Other platforms use timer file descriptors](https://github.com/flutter/engine/blob/973cfbc6cb030526269acc8dc03d524abb199e94/fml/platform/linux/message_loop_linux.cc#L83) that are continuously re-armed to implement this functionality. In the absence of this mechanism on Fuchsia, for each task posted to the target message loop (potentially many thousands), the message loop would wake up and end up doing no work. This would eventually cause CPU usage to spike and cause actual work to be deferred.
Repository: opencv
Issue: Please make an official OpenCV bindings for R
Labels: feature,category: build/install

To whomsoever it may concern,
As an avid R user, I would humbly request if OpenCV.org could create an official bindings of OpenCV for R. R users like me have to migrate to Python to use OpenCV to its full potential.
Please it is a very humble request if this could be made possible.
Thanks
Best Regards
Repository: rust
Issue: Add sanity checking for query keys
Labels: C-cleanup,T-compiler

We frequently see issues where a query parameter ends up containing something that it's not supposed to (an inference variable, a placeholder region, etc): https://github.com/rust-lang/rust/issues/68477 and https://github.com/rust-lang/rust/issues/64964 are recent examples.

Currently, incremental compilation must be enabled to see these crashes, since they only occur when we try to hash the 'bad' type. This presents a number of issues:

1. The playground can't be used to reproduce them, since it (rightly) disables incremental compilation.
2. We may miss these kinds of issues when invoking `rustc` directly (e.g. the `ui` test suite), since `-C incremental=1` is usually not passed.
3. The panic message isn't very helpful - in particular, it doesn't show the original type being hashed.

I think it would be useful to add a `sanity_check` method to `Key`, which would verify that the value is sane (e.g. no inference variances or placeholder regions) regardless of whether or not incremental compilation is enabled.
Repository: godot
Issue: ImageTexture.create_from_image RGB8 black on Android
Labels: bug,platform:android,topic:rendering,confirmed

**Godot version:**
3.2 RC 2
3.2 RC 2 Mono
3.2.3

GLES2, GLES3

**OS/device including version:**
Linux Mint 19.3 Exported -> Working as expected
Google Pixel 3a -> Texture is broken and black

**Issue description:**
Any image, loaded or created dynamically with the format RGB8 (Possibly others) will show up black on Android.

**Android**
![image](https://user-images.githubusercontent.com/14253836/72963623-6ac93900-3d7d-11ea-8a4d-4797e61c7fba.png)

**Desktop**
![image](https://user-images.githubusercontent.com/14253836/72963684-7d437280-3d7d-11ea-8c60-c7f85f102690.png)

**Steps to reproduce:**
Display an image created like so:
```
var img = Image.new()
img.create(64, 64, false, Image.FORMAT_RGB8)
img.fill(Color.red)
img.lock()
print(img.get_pixel(5, 5)) # This prints correctly on all platforms
texture = ImageTexture.new()
texture.create_from_image(img)
```

**Minimal reproduction project:**
[Test2d.zip](https://github.com/godotengine/godot/files/4101743/Test2d.zip)
Repository: pytorch
Issue: Bug in add_param - functionality for tensorboard (scatter matrix view)
Labels: module: tensorboard,oncall: visualization

## 🐛 Bug

The add_param() functionality in torch.utils.tensorboard doesn't keep the type of the hyperparameter when writing them to tensorboard file. As a result the hparams are ordered in a alphabetic order instead of a numeric one (if the hparm type is float for instance). Another resulting behavior is that tensorboard is producing a single tick for each hparam on x-axis. 

## To Reproduce

Steps to reproduce the behavior:

1. Just use the example which is provided in the docu but change the range to 15 i.e.:
from torch.utils.tensorboard import SummaryWriter
with SummaryWriter() as w:
    for i in range(15):
        w.add_hparams({'lr': 0.1*i, 'bsize': i},
                      {'hparam/accuracy': 10*i, 'hparam/loss': 10*i})

2. Start tensorboard and got to hparam section. Then go to scatter plot matrix view and take a look on the x axis of bsize. 



## Expected behavior

Collecting environment information...
PyTorch version: 1.4.0
Is debug build: No
CUDA used to build PyTorch: 10.1

OS: Microsoft Windows 10 Pro
GCC version: (x86_64-posix-seh-rev0, Built by MinGW-W64 project) 8.1.0
CMake version: Could not collect

Python version: 3.6
Is CUDA available: No
CUDA runtime version: No CUDA
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA

Versions of relevant libraries:
[pip] numpy==1.18.1
[pip] numpydoc==0.9.2
[pip] torch==1.4.0
[pip] torchvision==0.5.0
[conda] blas                      1.0                         mkl
[conda] mkl                       2019.4                      245
[conda] mkl-service               2.3.0            py36hb782905_0
[conda] mkl_fft                   1.0.15           py36h14836fe_0
[conda] mkl_random                1.1.0            py36h675688f_0
[conda] pytorch                   1.4.0           py3.6_cuda101_cudnn7_0    pytorch
[conda] torch                     1.0.1                    pypi_0    pypi
[conda] torchvision               0.2.2.post3              pypi_0    pypi
## Additional context

<!-- Add any other context about the problem here. -->
![image](https://user-images.githubusercontent.com/60213215/72966813-15624b80-3dc0-11ea-81a1-0d8c6712921b.png)
Repository: next.js
Issue: TypeError: handler is not a function only when deployed to firebase but not when serve
Labels: good first issue,examples

# Examples bug report

## with-firebase-hosting

## Error: > handler is not a function
- Downloaded the sample using the instructions in the description and ensuring everything works
- Integrated custom `express` server to handle redirection see https://github.com/jojonarte/with-express-firebasehosting-next
- Tested the application okay with `npm run serve` everything in the application works
- Tested with `npm run deploy`, deployment was successful however opening the hosting URL results in `Error: could not handle the request` and in firebase functions log `TypeError: handler is not a function
    at cloudFunction (/srv/node_modules/firebase-functions/lib/providers/https.js:57:9)
    at /worker/worker.js:783:7
    at /worker/worker.js:766:11
    at _combinedTickCallback (internal/process/next_tick.js:132:7)
    at process._tickDomainCallback (internal/process/next_tick.js:219:9)`


## To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

1. Go to https://github.com/jojonarte/with-express-firebasehosting-next
2. follow manual download instructions
3. follow firebase setup instructions
4. `npm install`
5. `npm run serve` should make the app work
5. `npm run deploy`
6. view the URL

## should build and upload to hosting and firebase functions and error shouldn't show just like in `npm run serve`

I expected it should build and deploy the cloud function and hosting properly to firebase just like how it works using `npm run serve`

## System information

- OS: macOS
- Version of Next.js: "^9.1.7"
Repository: vscode
Issue: [css] text-underline-position value completion is wrong
Labels: bug,css-less-scss

https://developer.mozilla.org/en-US/docs/Web/CSS/text-underline-position

![image](https://user-images.githubusercontent.com/4033249/72968813-90c5fc00-3dc4-11ea-8958-0481f94e1681.png)

`under` should be there.
Repository: pytorch
Issue: addition of attention based techniques to pytorch
Labels: module: nn,module: convolution,triaged,function request

## 🚀 Feature
<!-- A clear and concise description of the feature proposal -->
Stand alone self attention and attention augmented convolution networks perform better than standard convolution networks on image classification experiments, I think these two should be added to PyTorch.

## Motivation

<!-- Please outline the motivation for the proposal. Is your feature request related to a problem? e.g., I'm always frustrated when [...]. If this is related to another GitHub issue, please link here too -->
https://arxiv.org/abs/1904.09925
https://arxiv.org/abs/1906.05909
## Pitch

<!-- A clear and concise description of what you want to happen. -->
something like,
nn.AugmentedConv()
nn.StandAloneAttention()

cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki @zhangguanheng66
Repository: TypeScript
Issue: Support `@extends` tag for ES5-style classes
Labels: Suggestion,Awaiting More Feedback

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Even if you think you've found a *bug*, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs section!

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ

Please fill in the *entire* template below.
-->

<!--
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.5 and 3.8.0-dev.20200123

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** extends not attached to a class

I'm currently evaluating if TypeScript can be used to type-check old closure compiler projects which use JSDoc annotations for typing and to generate *.d.ts files for it so the old projects can be easily used within new typescript projects. But unfortunately the `@extends` annotation is not working as expected. I would understand if TypeScript simply didn't support it (Then this would be a feature request) but the error message **error TS8022: JSDoc '@extends' is not attached to a class** thrown by the compiler suggests that there is some support for but it doesn't work as expected.

Please note that the real class inheritance code which actually extends class `Sub` from `Base` is omitted in the code example below because it is irrelevant to the compiler.


**Code**

```ts
// Compile with: tsc --checkJS --allowJS --outDir out test.js

/**
 * @constructor
 * @class
 */
function Base() {}

Base.prototype.foo = function() {}

/**
 * @constructor
 * @class
 * @extends {Base}
 */
function Sub() {}

Sub.prototype.bar = function() {}
```

**Expected behavior:**

Typescript should recognize type `Sub` to be a class which extends class `Base`.

**Actual behavior:**

Compilation fails with this error:

```
$ tsc --checkJS --allowJS --outDir out test.js
test.js:14:10 - error TS8022: JSDoc '@extends' is not attached to a class.

14 function Sub() {}
            ~~~


Found 1 error.
```
Repository: godot
Issue: Memory leak(?) when using "Creation CollisionPolygon2D Sibling"
Labels: bug,topic:core,confirmed

**Godot version: 3.1.2 stable win64 **

**OS/device including version: Windows 10**

**Issue description:** I was playing arroun with the "create CollisionPolygon" sprite tool. I generated one with lots of points, so godot and my game got very laggy. (I did some tests before with more simplification and my program worked fine). Then i went back to the more simplified version of that collisionPolygon but when running my game it was very slow. The game was using arround 500mb of memory. I was super lost, because it worked fine and now it was laggy. I restarted my pc and the game went back to normal (arround 25/30mb of memory usage), so i'm pretty sure this is a memory leak.

**Steps to reproduce:** from an sprite, use the "Create CollisionPolygon" (i have the spanish version, it says something like "create brother of (or for) collisionPolygon2D", i'm not sure about the exact name in english); then at simplification use the default value (2). Attach some movement code to that sprite so you can see if it lags. (spoiler alert, it doesn't). Now generate that collisionPolygon again but at simplification use some ridiculous value like 0.3, run the game, it's going to be laggy (if not, use a lower value). Then generate it again with the first value (2), run the game and you will see it lags a lot. 

**Minimal reproduction project:** I really don't have time to do a demo file rn, sorry!
Repository: go
Issue: net/mail: add helpers for msg-id
Labels: NeedsInvestigation,FeatureRequest

[RFC 5322 section 3.6.4](https://tools.ietf.org/html/rfc5322#section-3.6.4) defines message identification fields which require parsing (e.g. they can contain CFWS). `net/mail` already provides helpers for `Date` and address lists. Would some helpers for `Message-ID` and message identifier lists be a welcome addition?

Ref https://github.com/emersion/go-message/pull/70
Repository: rust
Issue: Severe slowdown when wrapping a [MaybeUninit<T>; N] in a struct
Labels: I-slow,C-enhancement,A-codegen,T-compiler

Consider the following function:

```rust
#![feature(maybe_uninit_extra)]

use std::{mem::MaybeUninit, ops::Range};

const N: usize = 10_000;
const RANGE: Range<u32> = 2500..7500;

fn foo() -> u32 {
    unsafe {
        let mut array = MaybeUninit::<[MaybeUninit<u32>; N]>::uninit().assume_init();
        let mut len = 0;

        for value in RANGE {
            array.get_unchecked_mut(len).write(value);
            len += 1;
        }

        (0..len).map(|i| array.get_unchecked(i).read()).sum()
    }
}
```

This runs as fast as I would expect. But if I put `array` and `len` in a struct, like this:

```rust
struct S {
    array: [MaybeUninit<u32>; N],
    len: usize,
}

pub fn bar() -> u32 {
    unsafe {
        let mut s = S {
            array: MaybeUninit::uninit().assume_init(),
            len: 0,
        };

        for value in RANGE {
            s.array.get_unchecked_mut(s.len).write(value);
            s.len += 1;
        }

        (0..s.len).map(|i| s.array.get_unchecked(i).read()).sum()
    }
}
```

This runs about 15x as slowly using (although these didn't change anything)
```
[profile.bench]
lto = true
codegen-units = 1
```
with the 2020-01-22 nightly toolchain. This difference can be observed with much smaller values of `N`, too, and blackboxing values didn't make a difference.

[Playground with benchmarks](https://play.rust-lang.org/?version=nightly&mode=release&edition=2018&gist=ece1d1e8eea46b962166a27325fb60f8)