sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: `flutter --no-color doctor -v` and `flutter doctor -v` produce different output
Labels: tool,t: flutter doctor,P3,team-tool,triaged-tool

`flutter --no-color doctor -v` 
https://pastebin.com/UnZEjpaq

`flutter doctor -v`:
https://pastebin.com/W5qWCNHJ

---

EDIT by @christopherfujino 

This bug can also be seen by comparing `flutter doctor -v` and `flutter doctor -vv`, as described in the issue https://github.com/flutter/flutter/issues/53680. I'm copying and pasting @jmagman's repro here for reference:

For example, flutter doctor doesn't show NDK location.

```
$ flutter doctor     
[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
```

flutter doctor -v does.

```
$ flutter doctor -v
[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/magder/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)
    • All Android licenses accepted.
```

flutter doctor -vv doesn't reference NDK location.

```
$ flutter doctor -vv
[  +14 ms] executing: /usr/bin/plutil -convert json -o - /Applications/Android Studio.app/Contents/Info.plist
...
[  +18 ms] executing: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java -version
...
[  +25 ms] executing: /usr/bin/plutil -convert json -o - /Applications/Android Studio.app/Contents/Info.plist
...
[  +99 ms] executing: /usr/bin/plutil -convert json -o - /Applications/IntelliJ IDEA CE.app/Contents/Info.plist
...
[   +5 ms] executing: /usr/bin/plutil -convert json -o - /Applications/IntelliJ IDEA CE.app/Contents/Info.plist
...
[ +284 ms] [✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
...
```
Repository: terminal
Issue: Add more rules to the static analysis ruleset
Labels: Product-Meta,Issue-Task,Area-CodeHealth

There is a ruleset file for static analysis checks at `/src/StaticAnalysis.ruleset` but it currently has only two rules that it checks for. More should be added.
Repository: flutter
Issue: Can't run `flutter packages pub global` outside of a flutter project
Labels: tool,a: quality,P3,team-tool,triaged-tool

From my home directory (not a flutter project):

```bash
~ $ flutter packages pub global activate devtools
Error: No pubspec.yaml file found.
This command should be run from the root of your Flutter project.
Do not run this command from the root of your git clone of Flutter.
```

`pub global` is supposed to be usable from anywhere (hence the global name).  This command does work correctly if you just invoke the pub command directly:

```bash
~ $ pub global activate devtools
Package devtools is currently active at version 0.1.0.
Resolving dependencies... (2.8s)
```

It also works if you use `flutter pub global`:

```bash
flutter pub global activate devtools
Package devtools is currently active at version 0.1.0.
Resolving dependencies...
```
Repository: flutter
Issue: Initial console on Windows wraps poorly
Labels: tool,platform-windows,a: first hour,P2,team-tool,triaged-tool

![Screenshot (16)](https://user-images.githubusercontent.com/551196/58360634-b4543380-7e3e-11e9-9388-b706e806b588.png)

- [ ] it's too tall, you can't see the whole banner
- [ ] the === line is one character too long
- [ ] the last line of text isn't wrapped at all
Repository: node
Issue: test: fixtures key/certs cause failures when openssl security level > 1
Labels: crypto,test

<!--
Thank you for reporting a possible bug in Node.js.

Please fill in as much of the template below as you can.

Version: output of `node -v`
Platform: output of `uname -a` (UNIX), or version and 32 or 64-b
it (Windows)
Subsystem: if known, please specify the affected core module name

If possible, please provide code that demonstrates the problem, keeping it as
simple and free of external dependencies as you can.
-->

* **Version**: v13.0.0-pre 5b8df5e956680dc1a38b631e53f5e70a905fd917
* **Platform**: Linux alexaub.svl.corp.google.com 4.19.37-2rodete1-amd64 #1 SMP Debian 4.19.37-2rodete1 (2019-05-15 > 2018) x86_64 GNU/Linux
* **Subsystem**: test

<!-- Please provide more details below this comment. -->

In Debian testing, the latest openssl sets the default required security level to 2 in `/etc/ssl/openssl.cnf` ([link](https://tracker.debian.org/news/953618/accepted-openssl-111pre6-1-source-into-experimental/)). This requires (among other things, described [here](https://www.openssl.org/docs/man1.1.0/man3/SSL_CTX_get_security_level.html)) that certs/keys be at least of a certain length depending on cipher.

Some of the keys under `test/fixtures/` don't satisfy seclevel 2, and cause tests to fail when node's openssl reads that `openssl.cnf`. 

Here's the [output](https://github.com/nodejs/node/files/3218802/test.log) of `python tools/test.py -J -p tap --logfile=test.log`. 180 tests fail due to errors like `ERR_SSL_EE_KEY_TOO_SMALL`.

The issue can be avoided by changing the line `CipherString = DEFAULT@SECLEVEL=2` to `CipherString = DEFAULT@SECLEVEL=1` in `/etc/ssl/openssl.cnf`. However beware that this is globally reducing the required security on your machine.

I figure that this issue can be solved by regenerating the troublesome keys/certs with a greater size -- probably 2048 bits for RSA/DSA/DH and 256 for ECC. I've been looking into this, and I would be happy to take a crack at it! The changes would be similar to #3759, and I think that it would also be good to move the certs under `test/fixtures/` to be under `test/fixtures/keys/` and generate them in the Makefile.
Repository: rust
Issue: cleaner output when dbg!() is given a literal value
Labels: C-enhancement,T-libs-api

Hello!  I'm unsure if this should be an RFC but it seems similar to #57845, so I'll start by filing an issue here.

## The problem

Often I end up writing `dbg!` code with constant values, usually strings, to trace control flow.

```Rust
dbg!("Start loop");
while condition {
   dbg!("Phase 1");
   unsafe { libc::do_something() }
   ...
   dbg!("Phase 2");
   ...
}
```

The output is a bit noisier than I'd like.
`[lib/emscripten/src/syscalls/unix.rs:826] "Start loop" = "Start loop"`

## The solution

Detect if the argument to the macro is a literal value (assuming this is possible) and make the output just:
`[lib/emscripten/src/syscalls/unix.rs:826] "Start loop"`

## Alternatives considered:
- `eprintln!`: doesn't have line and file info.  It's a separate macro, so it's less aesthetically pleasing and less intuitive in my opinion.
- `debug!`: usually I'm already using these for other tasks and filtering them out is harder and less convenient than `dbg!`;  `dbg!` is nice because it's explicitly a temporary debugging tool
- a custom macro: it'd be nice to be able to use this consistently anywhere
Repository: terminal
Issue: Guidance around const by-value function parameters
Labels: Issue-Docs,Product-Meta,Area-CodeHealth

Clarification is needed around const by-value function parameters.   I noticed in a lot of the code, by-value function parameters are marked const.  Some code doesn't follow this rule though. 

Examples in interactivity/win32/Clipboard.cpp

void Clipboard::Copy(bool fAlsoCopyHtml)

void Clipboard::StoreSelectionToClipboard(bool const fAlsoCopyHtml)

In the CppCoreGuidelines
[Con.1: By default, make objects immutable](https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#con1-by-default-make-objects-immutable)

They have an exception 
Exception
Function arguments are rarely mutated, but also rarely declared const. To avoid confusion and lots of false positives, don't enforce this rule for function arguments.

> void g(const int i);        // pedantic

What is the team's stance on this?

This issue is just a reminder when we create the styleguide in #890 to include something around the team's rule.
Repository: godot
Issue: TextEdits with borders have a small sub-pixel gap.
Labels: bug,topic:gui

**Godot version:**
v3.1.1.stable.official

**OS/device including version:**
Ubuntu 18.04.2 LTS
Geforce GTX 1060
NVIDIA Driver: 418.56

**Issue description:**
Left container contains a panel container, right container contains a text edit with the same style.
They seem to get sqooshed slightly.
![textedit](https://user-images.githubusercontent.com/4351098/58363294-47a15f00-7e67-11e9-8adf-396bdfaff9f1.png)


**Steps to reproduce:**
Add a TextEdit to a container, style it with a 1px border and set size flags to expand.

**Minimal reproduction project:**
[textedit.zip](https://github.com/godotengine/godot/files/3219022/textedit.zip)
Repository: rust
Issue: Cannot infer type should state how to specify the type
Labels: C-enhancement,A-diagnostics,T-compiler,A-inference,A-suggestion-diagnostics,D-verbose

[For example](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=d544b677c3662f6d7120337e2df30d86):

```
error[E0282]: type annotations needed
  --> src/os_str_join.rs:54:43
   |
54 |         assert_eq!(OsString::from(""), [].join("-".as_ref()));
   |                                           ^^^^ cannot infer type
```

Without googling, I have no way of understanding how to annotate my empty array with a type.
Repository: go
Issue: proposal: spec: support read-only and practical immutable values in Go
Labels: LanguageChange,Proposal,LanguageChangeReview

The full proposal is here: https://github.com/go101/immutable-value-proposal/blob/master/README-v9.a.md

Please note, the new syntax in this proposal is not the core of the proposal. I know it is not perfect, welcome to suggest any alternative better ones for the syntax.

This propsoal is not intended to be accepted, at least soon. It is more a documentation to show the problems and possible solutions in supporting immutable and read-only values in Go.
Repository: react
Issue: Controlled input makes browser not saving submitted value (for autocomplete)
Labels: Type: Bug,Component: DOM

**Bug** (behaves different per browser, but generally inconsistent to uncontrolled inputs)

**Current behavior**
Reproduce with https://jsfiddle.net/bootleq/hos4r6qd/
1. Type `a` in *name* field, and `b` in *uncontrolled* field.
2. Submit.
3. Re-run the fiddle.
4. Focus input fields to see if browser "saves" previous input.

**Expected behavior**
Browser provides `a` suggestion for *name* and `b` for *uncontrolled* field.
Controlled and uncontrolled elements should behave the same.

**Actual result**
Uncontrolled input has `b` suggestion, but controlled input (*name*) has **no** suggestion.
Tested on Windows 7, Google Chrome 74.0.3729.169.
And on Firefox 68.0b4, we can click the *workaround* button before submit, by reset the `value` DOM attribute it behaves as expected.
Repository: svelte
Issue: Build Error if multiple incompatible versions of svelte are detected
Labels: feature request

I ran into [strange issues](https://github.com/sveltejs/svelte/issues/2862) that were due to multiple versions of svelte (3.4.2 & 3.2.2) being built.

It would be useful to have a build error if multiple incompatible versions of svelte are being used.
Repository: go
Issue: encoding/gob: Encoder.Encode fails to encode maps with keys of type url.URL
Labels: NeedsInvestigation

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.12.5 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/xxx/.cache/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/xxx/gocode"
GOPROXY=""
GORACE=""
GOROOT="/home/xxx/go"
GOTMPDIR=""
GOTOOLDIR="/home/xxx/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build478246212=/tmp/go-build -gno-record-gcc-switches"
</pre></details>

### What did you do?

https://play.golang.org/p/8-8Qws7ogyH

### What did you expect to see?

Gob encoder successfully encodes a value of type `map[url.URL]something`.

### What did you see instead?

There's an error: `gob: unaddressable value of type *url.URL`, despite the fact that the map keys are of type `url.URL`, not `*url.URL`.
Repository: rust
Issue: rustdoc: Primitive data type methods like min/max/clamp are not discoverable
Labels: T-rustdoc,C-enhancement

Currently, searching the rust stdlib docs for, as an example, 'i32 min', will not find any info at all, and the the `i32` page (https://doc.rust-lang.org/std/primitive.i32.html) is not searchable with standard CTRL-F in some browsers like Firefox, since `min`/`max`/`clamp` are hidden under the by-default-collapsed section on `Ord`. This lack of searchability/discoverability extends to Google results.

I'm not sure what the bets method to remedy this is, but fixing the on-site search to know about these is probably a good start.
Repository: rust
Issue: Error about missing `From` impl when using `try_from`
Labels: C-enhancement,A-diagnostics,A-trait-system,T-compiler,F-on_unimplemented

There are probably some generic trait implementations that cause rustc to follow this line of reasoning.

```rust
use std::convert::TryFrom;

fn main() {
    f64::try_from(4usize);
}


```

([Playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=9d9a573c294b1348419e5b59caaa1ca8))

Errors:

```
   Compiling playground v0.0.1 (/playground)
error[E0277]: the trait bound `f64: std::convert::From<usize>` is not satisfied
 --> src/main.rs:4:5
  |
4 |     f64::try_from(4usize);
  |     ^^^^^^^^^^^^^ the trait `std::convert::From<usize>` is not implemented for `f64`
  |
  = help: the following implementations were found:
            <f64 as std::convert::From<f32>>
            <f64 as std::convert::From<i16>>
            <f64 as std::convert::From<i32>>
            <f64 as std::convert::From<i8>>
          and 3 others
  = note: required because of the requirements on the impl of `std::convert::Into<f64>` for `usize`
  = note: required because of the requirements on the impl of `std::convert::TryFrom<usize>` for `f64`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0277`.
error: Could not compile `playground`.

To learn more, run the command again with --verbose.

```
Repository: TypeScript
Issue: Arobases in an example section of a jsdoc is considered a jsdoc section
Labels: Bug

Issue Type: <b>Bug</b>

1. Create a `foo.ts` file
2. Add the following code into it:

```javascript
class Foo {
  protected baz: boolean;

  public constructor() {
    this.baz = true;
  }

  /**
    * Set baz to false.
    * @return {Foo}
    * @example
    * import { Foo } from "@khalyomede/foo";
    * 
    * const foo = new Foo();
    *
    * foo.bar();
    * @since 0.1.0
    */
  public bar(): this {
    this.baz = false;

    return this;
  }
}

export default Foo;
```
3. Pass your mouse over the `bar` method: you should see that `@khalyomede` is considered a jsdoc section

I made a screenshot of the issue: [https://i.ibb.co/dkKbMqV/vscode-arobases-in-comment-issue.png](https://i.ibb.co/dkKbMqV/vscode-arobases-in-comment-issue.png)

VS Code version: Code 1.34.0 (a622c65b2c713c890fcf4fbf07cf34049d5fe758, 2019-05-15T21:59:37.030Z)
OS version: Windows_NT x64 10.0.17763

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 x 2808)|
|GPU Status|2d_canvas: enabled<br>checker_imaging: disabled_off<br>flash_3d: enabled<br>flash_stage3d: enabled<br>flash_stage3d_baseline: enabled<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>native_gpu_memory_buffers: disabled_software<br>rasterization: enabled<br>surface_synchronization: enabled_on<br>video_decode: enabled<br>webgl: enabled<br>webgl2: enabled|
|Load (avg)|undefined|
|Memory (System)|15.89GB (8.84GB free)|
|Process Argv||
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (14)</summary>

Extension|Author (truncated)|Version
---|---|---
vscode-new-file|dku|4.0.2
apacheconf-snippets|eim|1.2.0
vsc-material-theme|Equ|2.8.2
vsc-material-theme-icons|equ|0.12.0
prettier-vscode|esb|1.9.0
php-intellisense|fel|2.3.10
sftp|lix|1.12.7
php-namespace-resolver|Meh|1.1.8
vetur|oct|0.21.0
laravel5-snippets|one|1.5.0
sass-indented|rob|1.5.1
stylelint|shi|0.49.0
open-in-browser|tec|2.0.0
lorem-ipsum|Tyr|1.2.0


</details>
<!-- generated by issue reporter -->
Repository: godot
Issue: ResourceSaver duplicates items in all arrays
Labels: bug,topic:gdscript,confirmed

<!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->

**Godot version:**
3.1


**OS/device including version:**
Windows 10

**Issue description:**
ResourceSaver duplicates items in all arrays upon saving

**Minimal reproduction script:**
```js
extends Node2D

class Save:
	extends Resource

	export var version : String = "1.0"
	export var save_name : String = "Whatever"
    
	export var arr1: Array = []
	export var arr2: Array = []
	export var arr3: Array = []

func _ready():
	var save := Save.new()
	
	save.arr1.push_back({"name": "Plane"})
	save.arr2.push_back({"name": "Human"})
	save.arr3.push_back({"name": "Cat"})
	
	ResourceSaver.save("res://test.tres", save)
```

test.tres:

```ini
[gd_resource type="Resource" load_steps=2 format=2]

[sub_resource type="GDScript" id=1]

[resource]
script = SubResource( 1 )
version = "1.0"
save_name = "Whatever"
arr1 = [ {
"name": "Plane"
}, {
"name": "Human"
}, {
"name": "Cat"
} ]
arr2 = [ {
"name": "Plane"
}, {
"name": "Human"
}, {
"name": "Cat"
} ]
arr3 = [ {
"name": "Plane"
}, {
"name": "Human"
}, {
"name": "Cat"
} ]
```
Repository: youtube-dl
Issue: Site Support Request: animenewsnetwork.com
Labels: site-support-request

<!--

######################################################################
  WARNING!
  IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################

-->


## Checklist

<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- First of, make sure you are using the latest version of youtube-dl. Run `youtube-dl --version` and ensure your version is 2019.05.20. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Make sure that all provided video/audio/playlist URLs (if any) are alive and playable in a browser.
- Make sure that site you are requesting is not dedicated to copyright infringement, see https://yt-dl.org/copyright-infringement. youtube-dl does not support such sites. In order for site support request to be accepted all provided example URLs should not violate any copyrights.
- Search the bugtracker for similar site support requests: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Finally, put x into all relevant boxes (like this [x])
-->

- [x] I'm reporting a new site support request
- [x] I've verified that I'm running youtube-dl version **2019.05.20**
- [x] I've checked that all provided URLs are alive and playable in a browser
- [x] I've checked that none of provided URLs violate any copyrights
- [x] I've searched the bugtracker for similar site support requests including closed ones


## Example URLs

<!--
Provide all kinds of example URLs support for which should be included. Replace following example URLs by yours.
-->

- Single video: https://www.animenewsnetwork.com/video/159/


## Description

<!--
Provide any additional information.
If work on your issue requires account credentials please provide them or explain how one can obtain them.
-->
Repository: rust
Issue: Warning for when a `pub use x::*` statement excludes something already imported privately
Labels: C-enhancement,A-lints,A-diagnostics,A-resolve,T-lang,T-compiler

Ran into this today when refactoring visibility of tons of things in a library crate. In part of my refactoring, I added `pub use inner_mod::*;` statements to many of my modules. Confusingly, this didn't always re-export everything.

Consider this situation:

```rust
mod my_lib {
    mod inner_mod {
        mod inner_level {
            pub struct A;
            pub struct B;
            pub struct C;
        }
        
        use self::inner_level::B;
        
        pub use self::inner_level::*;
    }
    
    pub use self::inner_mod::*;
}

fn main() {
    // works fine
    let _a = my_lib::A;
    // errors with 'error[E0425]: cannot find value `B` in module `my_lib`'
    let _b = my_lib::B; 
    //               ^ 
}
```

The line `pub use inner_level::*;` does not include `inner_level::B`, because that has already been imported. But since it's imported _privately_, it still can't be accessed.

Reading my own code, it took quite a while before I realized I had this conflict. I've included my nested-module situation above as it was in my code, as that produced the error "does not exist". (rather than "this is private", which is what occurs when only one mod level deep).

If there was a way to warn against "wildcard pub use not re-exporting item already previously imported", I think it could help in the future? Or, this might be a super niche situation not worth helping.
Repository: vscode
Issue: [themes] Allow to set a background color for settings / webview editors
Labels: feature-request,themes

[Feature Request]
Set background color for generic windows.

[Suggestions]
window.bgColor, settings.bgColor, extensions.bgColor

[Reason]
I love my background color and all, but it only goes well with code.. Because I'm extremely used to a certain color set, but I'd rather separate code and information.
Repository: pytorch
Issue: official libtorch static build zip file error
Labels: module: binaries,module: build,triaged

## ❓ Questions and Help

I download libtorch static zip file from https://download.pytorch.org/libtorch/cpu/libtorch-static-with-deps-latest.zip

but I find that libtorch-static-with-deps-latest.zip version still has .so files, 
IT is The same as shared version from https://download.pytorch.org/libtorch/cpu/libtorch-shared-with-deps-latest.zip

I want to release my app without any .so files, and I do not  want to build from source, Can anyone help me with The above question. many thanks