sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: x/pkgsite: packages with stopwords as their name don't show up in search results
Labels: NeedsInvestigation,pkgsite,pkgsite/search

### What is the URL of the page with the issue?
 
https://pkg.go.dev/search?q=is
 
### What is your user agent?
 
> `Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:75.0) Gecko/20100101 Firefox/75.0`

### Screenshot
 
<img width="420" alt="image" src="https://user-images.githubusercontent.com/216265/80716933-4391ae80-8ac6-11ea-8d80-1560a319b590.png">
 
### What did you do?
 
I searched for the package name, "is".
 
### What did you expect to see?
 
 I expected to see a link to this page: https://pkg.go.dev/github.com/matryer/is
 
### What did you see instead?

A page with zero results.
Repository: flutter
Issue: merge separate flags to specify the vm service port for flutter run
Labels: tool,a: quality,c: proposal,P3,team-tool,triaged-tool

We have two separate flags to specify the VM service port to serve debugger traffic on, depending on whether the device you're launching is a mobile device or a flutter web device: `--host-vmservice-port` for mobile devices and `--web-port` for web ones.

This likely makes sense from the POV of the implementations, but less so from the POV of people invoking `flutter run`. I suggest that we merge the flags into one.

Additionally, the name - `--host-vmservice-port` - could take some time for people to work out what it is. When we run a flutter web device, we print `Debug service listening on ...`. Perhaps rename the port flags to something like `--debug-port`? `--debugger-port`? `--debug-service-port`?

(note that `--observatory-port` is the deprecated name for `--host-vmservice-port`)
Repository: go
Issue: x/build: ensure there are accessible ways to test Go pre-release versions in common CI systems
Labels: Builders,NeedsInvestigation,DevExp,Community

The Go project and its users benefit from additional testing of pre-release versions of Go, because it leads to a stable release with fewer issues. When beta and release candidates are released, we encourage everyone to test them as much as possible and report issues that are uncovered.

There are many CI systems that are in use today (Travis CI, Circle CI, GitHub Actions, and many more). Most of them have some level of support for testing Go code with various release versions of Go, but it's not clear whether pre-release versions are supported as well.

We should ensure it's possible and easy for users to start testing against pre-release versions of Go, so that if someone is willing to do it, we can point them to an existing solution rather than hoping they'll invent it themselves.

It is generally the responsibility of the CI solution itself to offer flexibility in the testing capabilities for its users, but perhaps there are things we can do on our side to help facilitate that.

So, the work here is to check whether this is already possible and convenient for various CI systems. If not, we can see if it can and should be made better through changes on our side. The specifics will depend on the CI system and the tools it offers. It might involve coming up with scripts or configurations, taking advantage of the existing [`golang.org/dl/...`](https://pkg.go.dev/golang.org/dl) commands, modifying our existing API endpoints (see #34864, #36898), or something else.

This is the tracking issue for that work.

(This idea was suggested to me by @hyangah, and I was reminded about it when seeing @mvdan's https://github.com/golang/go/issues/36898#issuecomment-621915093.)

/cc @golang/osp-team @rsc @mvdan @lyoness
Repository: rust
Issue: Closure signature hinting doesn't elaborate bounds.
Labels: C-enhancement,A-closures,T-compiler,A-inference

This currently can't infer the type of `s` ([playground](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=8b6126d6c94df72ced9ac92ebb3f1871)):
```rust
trait Foo: Fn(String) {}
impl<F> Foo for F where F: Fn(String) {}

fn hint(_: impl Foo) {}

fn main() {
    hint(|s| {s.len();});
}
```

However, this works as expected when `hint` takes `impl Fn(String)` instead of `impl Foo`.

If we were to elaborate the bounds of `hint`, we'd see `Fn(String)` even if `impl Foo` was used.

cc @nikomatsakis
Repository: rust
Issue: Use of tempfile for lib.def leads to non-reproducible PDBs
Labels: A-debuginfo,P-medium,T-compiler,O-windows-msvc,C-bug,A-reproducibility

I've been working with a rust code base that we are trying to use a shared cache for (Bazel FWIW). As part of that I've been looking at truly bit-identical build outputs for a given set of inputs.

There are plenty of problems with PDB files on Windows (which contain debug info) because they tend to encode absolute paths to the object files and other resources they were created from. I've managed to eliminate most of these by using deterministic build directories across all machines, and using tempdir's that are a hash of something unique. There is just one more bit that I can't control directly, which is this use of `tmpdir.join("lib.def")` https://github.com/rust-lang/rust/blob/0862458dad90a0d80827e22e3f86e33add6d847c/src/librustc_codegen_ssa/back/linker.rs#L720. This ends up putting a few random characters in the path that throws off the PDB.

I'm not entirely sure what a good solution will look like. I'm not familiar enough with compiler internals to know if some deterministic location based on some unique values can be used, or alternatively if this can be exposed as a compiler option.

I tried this code:
I can't share our internal code, but build something like serde_derive on windows and look for the proc macro dll. there should be a pdb next to it.
Next, you'll want to use `ducible` https://github.com/jasonwhite/ducible/ to remove a few other sources of non-determinism like timestamps.

```
ducible <dll> <pdb>
```

I expected to see this happen: Each clean build results in the same DLL and PDB (sha256 or similar).

Instead, this happened: the DLL is identical but the PDBs are not. Use something like https://www.cjmweb.net/vbindiff/ to spot the differences and the only one i noticed was this path to lib.def.


### Meta

(also exists in latest master based on code inspection).
`rustc --version --verbose`:
```
rustc 1.42.0-nightly (212b2c7da 2020-01-30)
binary: rustc
commit-hash: 212b2c7da87f3086af535b33a9ca6b5242f2d5a7
commit-date: 2020-01-30
host: i686-pc-windows-msvc
release: 1.42.0-nightly
LLVM version: 9.0
```
Repository: youtube-dl
Issue: JohnMaxwellAcademy.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 2020.03.24. 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 **2020.03.24**
- [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.johnmaxwellacademy.com/products/15-laws-of-growth/categories/741206/posts/2418867
- Playlist: https://www.johnmaxwellacademy.com/products/15-laws-of-growth

## Description

<!--
Provide any additional information.
If work on your issue requires account credentials please provide them or explain how one can obtain them.
-->

You need an account, and it's free to get one, at least for the next 7 days. all they need is for you to create a username and password. I created an account with a fake email address and it works with a fake email address. (You don't need to click the link in the email to watch the videos on the browser)
Repository: storybook
Issue: Allow for path based routes instead of query param based routes
Labels: feature request,core

**Is your feature request related to a problem? Please describe.**
I understand why the default router uses `?path=/foo` in order to handle routing, I think this allows storybook to work in the most places without a hassle. However, it's not necessarily the most usable/aesthetic way to do routing. I'd love storybook to either support real routes, or routing hooks to allow me to implement this myself.

**Describe the solution you'd like**
In the routing implementation now, routes are built by generating a path as `${currentLocation}?path=/some/path/here` and then calling `replaceState` with this new path.

### Solution 1

We can have a configuration option along the lines of `"routeRewritingSupported": Boolean` (which defaults to false).

We can document an nginx rewrite to support this setup. We'd also need to inject a `<base href=…>` in order to support loading of the static files (and or use a static file path prefix).

### Solution 2

We can expose hooks into the routing functions in order to replace them with any implementation you'd like.

This would make implementing real paths a little more difficult, but would allow for additional remixes on urls for other purposes. I'd essentially implement Solution 1 using Solution 2 if we went that route (pun intended).

**Describe alternatives you've considered**
I could just not care about routes as much, which is fair, but it seems good for a docs site.

**Are you able to assist bring the feature to reality?**
I could implement this if folks agreed that it should exist.

**Additional context**

The nginx config for this rewrite stuff in my playground atm looks like:

```
location / {
  # root
  rewrite    ^/$ /index.html break;
  # paths (things that dont have dots)
  rewrite    ^/([^\.]+)$ /index.html?path=$1 break; # probably not necessary to expose the path but whatever
  # static files
  rewrite ^/(.*)$    /$1 break;
}
```
Repository: go
Issue: hash, crypto: add WriteByte, WriteString method to hash implementations
Labels: Proposal,Proposal-Accepted

This proposal was initially for embedding io.ByteWriter in hash.Hash, or adding a WriteByte() method with the same signature.

This method is already added in the new maphash.Hash. Adding it elsewhere will extend the benefits in performance and usability to the other Hash implementations.

Per feedback of @ianlancetaylor below, I'm instead proposing the addition `WriteByte()` from io.ByteWriter to the standard library hash.Hash implementations, including:

adler32
crc32
crc64
fnv
Repository: pytorch
Issue: NCCL fails to find cuda include dir
Labels: oncall: distributed,triaged,module: nccl

My cuda install is fragmented and not in one folder like its typically installed. I am trying to pass env variables for cuda include and it seems to work, but the makestep for NCCL does not pass in this variable. Just the general "Root" dir. This CUDA include dir needs to make its way down into NCCL,  the build fails because it cannot find the cuda_runtime.h which is there
Pytorch  v1.3.0
cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @xush6528 @osalpekar
Repository: go
Issue: cmd/go: add -debug flag (default true) to control DWARF/etc info in binary
Labels: Proposal,Proposal-Accepted

Many gophers know that they can strip DWARF from their binaries with `-ldflags=-w`. But this is fairly cryptic, and it doesn't give the compiler the opportunity to save time and space by not generating that DWARF in the first place.

I propose we add support directly to cmd/go to say `-debug=false` or `-dwarf=false` or the like. Then cmd/go would translate that into the appropriate compiler and linker flags.
Repository: material-ui
Issue: [Checkbox] You can click through an overlay to check a checkbox
Labels: bug 🐛,on hold,component: checkbox

Paper component (elevation=1) accepts clicks from UI elements underneath. I have the following code:

```
<Popper>
  <Paper>
     <ClickAwayListener>
         // some stuff here
     </ClickAwayListener>
  </Paper>
</Popper>
```

Any elements (buttons, checkboxes, etc) that sit below the popper / paper component above, accept click events. The component should block any click events from flowing to components underneath it.

| Tech        | Version |
| ----------- | ------- |
| Material-UI | v4.9.9  |
| React       | v16.8.0  |
| Browser     | Chrome |
| TypeScript  |         |
| etc.        |         |
Repository: terminal
Issue: Fullscreen: enable revealing the tabs by hovering at the top of the screen
Labels: Help Wanted,Area-UserInterface,Product-Terminal,Issue-Task

Hello,
This terminal is excellent and I would like to propose a suggeestion.

In full screen mode there doesn't seem to be a way to switch or add tabs easily. Perhaps mouse movement could popout from the edge of the screen the tabs and a way to switch between them.

I ultimately would just like to leave this up fullscreen on one of my monitors.
Repository: rust
Issue: Error handling of non references when expecting a references (borrow)
Labels: C-enhancement,A-diagnostics,T-compiler,E-needs-mcve

This is in mostly a re-post of https://github.com/diesel-rs/diesel/issues/2380

I tried this code:

I used the code from: https://docs.diesel.rs/diesel/associations/index.html
```rust
use schema::{posts, users};

#[derive(Identifiable, Queryable, PartialEq, Debug)]
#[table_name = "users"]
pub struct User {
    id: i32,
    name: String,
}

#[derive(Identifiable, Queryable, Associations, PartialEq, Debug)]
#[belongs_to(User)]
#[table_name = "posts"]
pub struct Post {
    id: i32,
    user_id: i32,
    title: String,
}

let user = users.find(2).get_result::<User>(&connection)?;
let users_post = Post::belonging_to(&user)
    .first(&connection)?;
let expected = Post { id: 3, user_id: 2, title: "My first post too".into() };
assert_eq!(expected, users_post);
```

This code works, as it should.
But when changing the line from:
```
let users_post = Post::belonging_to(&user)
```
to (the `&` is removed )
```
let users_post = Post::belonging_to(user)
```

The compiler gives an error that is very hard to figure out:
```
error[E0277]: the trait bound `Post: diesel::BelongingToDsl<User>` is not satisfied
  --> src/main.rs:30:29
   |
30 |     let _users_post: Post = Post::belonging_to(user)
   |                             ^^^^^^^^^^^^^^^^^^ the trait `diesel::BelongingToDsl<User>` is not implemented for `Post`
   |
   = note: required by `diesel::BelongingToDsl::belonging_to`

error: aborting due to previous error
```
This error is not so useful. 
An error like this could be **much** more helpful: (the error below is handcrafted from other errors)
```
error[E0308]: mismatched types
  --> src/main.rs:30:48
   |
30 |     let _users_post: Post = Post::belonging_to(user)
   |                                                ^^^^
   |                                                |
   |                                           expected reference, found struct `User`
   |                                           help: consider borrowing here: `&user`
   |
   = note: expected reference `&_`
                 found struct `User`

error: aborting due to previous error
```

Giving better errors would real help here.

I think this might have something to do with many layers of generic data types. But I am not sure at all. I was unable to reproduce this with shorter code.

### Meta
Sorry but don't want to try this under nightly. (Already spending to much time on this error)

`rustc --version --verbose`:
```
rustc 1.43.0 (4fb7144ed 2020-04-20)
binary: rustc
commit-hash: 4fb7144ed159f94491249e86d5bbd033b5d60550
commit-date: 2020-04-20
host: x86_64-unknown-linux-gnu
release: 1.43.0
LLVM version: 9.0
```
Repository: rust
Issue: Async function leads to a "more general type" error
Labels: A-type-system,T-compiler,C-bug,A-async-await,AsyncAwait-Triaged,T-types

Rustc complains about a type being more general than the other when testing if the `Future` returned by an `async` function is `Send`. The same code without `async` sugar is accepted by the compiler.

This might be related to #60658.

I tried to minimize further, but removing `.flatten()`, the boxing with a trait object or even the mapping to an empty stream makes the code compile.

[Playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=e390e86879b7d131ad619292c2c429e5)

```rust
use futures::{
    future::ready,
    stream::{empty, iter},
    Stream, StreamExt,
};
use std::future::Future;
use std::pin::Pin;

fn is_send<T: Send>(_: T) {}

pub fn test() {
    let _ = is_send(make_future()); // Ok
    let _ = is_send(make_future_2());
}

fn make_future() -> impl Future<Output = ()> {
    iter(Some({
        let s = empty::<()>();
        Box::pin(s) as Pin<Box<dyn Stream<Item = ()> + Send + 'static>>
    }))
    .map(|_| empty::<()>())
    .flatten()
    .for_each(|_| ready(()))
}

// Same as make_future, just async
async fn make_future_2() {
    iter(Some({
        let s = empty::<()>();
        Box::pin(s) as Pin<Box<dyn Stream<Item = ()> + Send + 'static>>
    }))
    .map(|_| empty::<()>())
    .flatten()
    .for_each(|_| ready(()))
    .await
}
```

### Expected result
It compiles successfully -- `is_send(make_future())` and `is_send(make_future_2())` are both accepted by the compiler.

### Actual result
`is_send(make_future_2())` is rejected with the following error:

```
error[E0308]: mismatched types
  --> src/lib.rs:13:13
   |
13 |     let _ = is_send(make_future_2());
   |             ^^^^^^^ one type is more general than the other
   |
   = note: expected type `std::ops::FnOnce<(std::pin::Pin<std::boxed::Box<dyn futures_core::stream::Stream<Item = ()> + std::marker::Send>>,)>`
              found type `std::ops::FnOnce<(std::pin::Pin<std::boxed::Box<dyn futures_core::stream::Stream<Item = ()> + std::marker::Send>>,)>`
```

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"nikomatsakis"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: pytorch
Issue: logging_is_not_google_glog.h:24:11: error: 'const int ERROR' redeclared as different kind of symbol  (v1.3.0)
Labels: module: build,triaged

I have a file in my large project using ERROR as a constant already globally so i cannot change that variable as its used in many places.  When i try to build i get an error from the linker because it finds both variables, whats the best way to edit "logging_is_not_google_glog.h" without breaking anything else? Anyway i could remove it entirely?

cc @malfet
Repository: rust
Issue: Missed optimization: locally constructed arrays are not promoted to constants
Labels: A-LLVM,I-slow,C-enhancement,A-codegen,T-compiler,C-optimization

To reproduce, look at the optimized code for the following program ([godbolt](https://godbolt.org/z/ENtCaE)):
```rust
pub fn f(x: usize) -> i32 {
    const T: [i32; 6] = [4, 8, 15, 16, 23, 42];
    T[x]
}

pub fn f2(x: usize) -> i32 {
    [4, 8, 15, 16, 23, 42][x]
}
```

### Expected result

The array should be placed in the constants section because it's always the same and is not mutable.
These functions should generate the same code.

### Actual result

```asm
; good
example::f:
        push    rax
        cmp     rdi, 5
        ja      .LBB0_2  ; panic
        lea     rax, [rip + .L__unnamed_1]
        mov     eax, dword ptr [rax + 4*rdi]
        pop     rcx
        ret

; bad, the array is placed on the stack
example::f2:
        sub     rsp, 24
        movaps  xmm0, xmmword ptr [rip + .LCPI1_0]
        movups  xmmword ptr [rsp], xmm0
        movabs  rax, 180388626455
        mov     qword ptr [rsp + 16], rax
        cmp     rdi, 5
        ja      .LBB1_2  ; panic
        mov     eax, dword ptr [rsp + 4*rdi]
        add     rsp, 24
        ret
```

### Meta

This reproduces both on godbolt and locally.

`rustc --version --verbose`:
```
rustc 1.45.0-nightly (fa51f810e 2020-04-29)
binary: rustc
commit-hash: fa51f810e5b9254904b92660e7280b7d6a46f112
commit-date: 2020-04-29
host: x86_64-pc-windows-msvc
release: 1.45.0-nightly
LLVM version: 9.0
```
Repository: godot
Issue: 3D CollisionObject: input signals not emitted when the tree is paused
Labels: documentation,topic:physics

**Godot version:**
3.2.1 mono

**OS/device including version:**
MXLinux19 64bits

**Issue description:**
When the tree is paused collision objects don't receive input events.

**Minimal reproduction project:**

[PauseAndInputProblem.zip](https://github.com/godotengine/godot/files/4561925/PauseAndInputProblem.zip)
Repository: PowerToys
Issue: [Run] Search for folders should display shallow folders first
Labels: Idea-Enhancement,Product-PowerToys Run,Cost-Small,Run-Results (Indexer)

# Summary of the new feature/enhancement

Whenever a folder is searched in the launcher, the results are displayed in a seemingly random order.
For example, searching Appdata shows me a list like:
C:\Users\alias\some_path\AppData
.
.
C:\Users\alias\Appdata
                                
I would like the search to return shallow matching results first, since these are likely the ones that I am looking for. 
# Proposed technical implementation details (optional)
In the above example, I would like the search to show C:\Users\alias\Appdata above the other options.
Repository: terminal
Issue: Consider whether we need to support "bold foreground" (like gnome-terminal) as a separate color
Labels: Product-Conhost,Area-VT,Product-Terminal,Issue-Task

Many terminals _optionally_ treat `\e[1;39m` as a separate color.

gnome-terminal has a toggleable "bold foreground" option:

![image](https://user-images.githubusercontent.com/14316954/80772234-e3712b80-8b0a-11ea-99fa-cf96aaf3c7e0.png)


When it's set, `1;39` is different from `39`.

![image](https://user-images.githubusercontent.com/14316954/80772220-dce2b400-8b0a-11ea-8752-11a98cd72747.png)