sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Only sends a `textDocument/documentHighlight` request when on an identifier
Labels: feature-request,editor-contrib

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.57.1

VSCode doesn't seem to send a `textDocument/documentHighlight` request when the cursor isn't on an identifier(whatever this means to vscode). The LSP documentation doesn't state that this request should only be sent in that case though.
> The document highlight request is sent from the client to the server to resolve a document highlights for a given text document position.
> https://microsoft.github.io/language-server-protocol/specifications/specification-current/#textDocument_documentHighlight

We ran into this in rust-analyzer when trying to highlight exit points, which in rust can have the form of a simple `?` character. So having the cursor on this character currently can't trigger the highlight. https://github.com/rust-analyzer/rust-analyzer/pull/9375
Repository: go
Issue: x/text/transform: Writer returns n < len(p), no error
Labels: NeedsInvestigation

<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.16.2 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What did you do?

- Created a transformer that almost always requires more data.
- Setup a `transformer.NewWriter` and called`Write()` with largish buffers.

```golang
type problemTransform []byte

func (problemTransform) Reset() {}

func (t problemTransform) Transform(dst, src []byte, atEOF bool) (nDst, nSrc int, err error) {
	// if we don't have an EOF, progress only 5 bytes at a time whilst asking for more data
	if !atEOF && len(src) > 5 {
		n := copy(dst, src[:5])
		err = transform.ErrShortSrc
		if n < 5 {
			err = transform.ErrShortDst
		}
		return n, n, err
	}

	// if we're at EOF or there's less than 5 bytes available, copy everything
	n := copy(dst, src)
	if n < len(src) {
		err = transform.ErrShortDst
	}
	return n, n, err
}

func TestNBelowLenP(t *testing.T) {
	w := transform.NewWriter(ioutil.Discard, problemTransform{})

	write := func(p []byte) {
		n, err := w.Write(p)
		if err != nil {
			t.Error(err)
		}

		if n != len(p) {
			t.Errorf("n %d below len(p) %d", n, len(p))
		}
	}

	write(append([]byte("1111111111"), make([]byte, 2048)...))
	write(make([]byte, 2048))

	if err := w.Close(); err != nil {
		t.Error(err)
	}
}
```

### What did you expect to see?

Everything written and `n == len(p)`

### What did you see instead?

`t.Error` raises `n 2043 below len(p) 2048`

I suspect this is to with the internal buffer size used, however, is this expected? The transformer is making progress, I would have expected everything to still be copied or an `err` when `n != len(p)`.

Writing the same amount of data but breaking it up over multiple `Write()` calls does work.

/cc @mpvl Do you have any ideas?
Repository: youtube-dl
Issue: Add "download_date" to info.json metadata to record when the video/metadata was downloaded
Labels: 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 2021.06.06. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Search the bugtracker for similar feature 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 feature request
- [x] I've verified that I'm running youtube-dl version **2021.06.06**
- [x] I've searched the bugtracker for similar feature requests including closed ones


## Description

<!--
Provide an explanation of your issue in an arbitrary form. Please make sure the description is worded well enough to be understood, see https://github.com/ytdl-org/youtube-dl#is-the-description-of-the-issue-itself-sufficient. Provide any additional information, suggested solution and as much context and examples as possible.
-->

The `.info.json` metadata files should include a `download_date` field that records the date and time the video and metadata was downloaded.  I think this is necessary and useful because many of the other fields in the file (such as `view_count` and `rating`) can be expected to change over time, so knowing the date and time they were recorded helps interpret them.  For instance, if I create a search database and want to sort by view count, I could use the download date to calculate a normalized "views_per_day", so videos that were downloaded soon after their upload aren't unfairly penalized.

Given the `download_date` would be taken from the clock of the user's system, time zone information should also be recorded.
Repository: rust
Issue: Confusing error message when associated type has same name as other type
Labels: C-enhancement,A-diagnostics,A-associated-items,T-compiler,D-newcomer-roadblock

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.

If you cannot produce a minimal reproduction case (something that would work in
isolation), please provide the steps or even link to a repository that causes
the problematic output to occur.
-->

Given the [following code](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=aef6f119c9dcc97483132fad2eed4a46): <!-- Please provide a link to play.rust-lang.org -->

```rust
use std::str::FromStr;

struct Foo;

enum MyErrors {
    FooFromStrError
}

impl FromStr for Foo {
    type Err = MyErrors;
    
    fn from_str(_s: &str) -> Result<Self, Self::Err> {
        Err(Err::FooFromStrError)
    }
}
```

The current output is:

```
   Compiling playground v0.0.1 (/playground)
error[E0433]: failed to resolve: `Err` is a variant, not a module
  --> src/lib.rs:13:13
   |
13 |         Err(Err::FooFromStrError)
   |             ^^^ `Err` is a variant, not a module

error: aborting due to previous error

For more information about this error, try `rustc --explain E0433`.
error: could not compile `playground`

To learn more, run the command again with --verbose.
```

<!-- The following is not always necessary. -->
Ideally the output would include a suggestion that `Err` is an associated type, that can be accessed as `Self::Err`, something like:
```
   Compiling playground v0.0.1 (/playground)
error[E0433]: failed to resolve: `Err` is a variant, not a module
  --> src/lib.rs:13:13
   |
13 |         Err(Err::FooFromStrError)
   |             ^^^ `Err` is a variant, not a module
help: There is an associated type with a similar name:
  --> src/lib.rs:13:13
   |
13 |         Err(Self::Err::FooFromStrError)
   |

error: aborting due to previous error

For more information about this error, try `rustc --explain E0433`.
error: could not compile `playground`

To learn more, run the command again with --verbose.
```
I ran into this while working with a relative newcomer to the language, and it would be nice as a guide. The suggestion would still be useful when there's no conflicting name (there is no suggestion in either case right now),  but the main source of confusion is the error message that what the user believes to be a type is instead a variant but not a module. It may be possible to use stronger phrasing ("try this") in a case like the one shown, where a variant of the type is being used that makes it clear what the intent was, as well.
Repository: next.js
Issue: Custom .babelrc file not being loaded after upgrading to Next.js 11
Labels: bug,Webpack

### What version of Next.js are you using?

11.0.1

### What version of Node.js are you using?

12.16.1

### What browser are you using?

Chrome

### What operating system are you using?

macOS

### How are you deploying your application?

Other platform

### Describe the Bug

Before upgrading to Next.js 11, my custom `.babelrc` file (which sits in the project's root directory) would be picked up by and used. When I booted up the project, I would always receive this message:

<img width="855" alt="screenshot" src="https://user-images.githubusercontent.com/10833491/123139220-e2f1cd80-d44d-11eb-9e96-ad70f9ef1db2.png">

However, after upgrading to 11, I no longer get this message when booting up the application and Emotion started complaining about some features that require the usage of their `@emotion/babel-plugin` which leads me to believe that the Babel custom configuration is not being picked up. I do have a custom server and my `.babelrc` looks like this:

```
{
  "plugins": ["@emotion/babel-plugin"],
  "presets": [
    [
      "next/babel",
      {
        "preset-react": {
          "runtime": "automatic",
          "importSource": "@emotion/react"
        }
      }
    ]
  ],
  "env": {
    "test": {
      "plugins": ["babel-plugin-dynamic-import-node"]
    }
  }
}
```

### Expected Behavior

Next.js application would pick up the `.babelrc` file like it's stated in its documentation and like it happened in v10.

### To Reproduce

https://stackblitz.com/edit/nextjs-h1ihd3

In here I added a simple custom server that I took directly from your documentation and you can see that the message about the custom `.babelrc` being picked up, does not appear. You just need to run `node server.js` in the terminal.
Repository: vscode
Issue: Create command to resolve one CompletionItem
Labels: feature-request,api,suggest

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

Right now, Live Share does not implement the Completion Resolve language service. This is because the completion service is already slow, and some `CompletionItem`s could have thousands of resolutions. I tested out setting the `vscode.executeCompletionItemProvider` command's `itemResolveCount` to 10 and 50, but the resolutions were often very far down the list that shows up for the guest, rather than on the items the user had selected, and was not worth the extra computation. 

We could solve this issue by creating a new command to return the resolution for a single `CompletionItem`. We would also need to know the display order of the `CompletionItem`s returned from the `vscode.executeCompletionItemProvider`. We could then populate the resolutions for the first few items at the top of list. 

Alternatively, we could only call this new command on the item in the list the user has selected.
Repository: pytorch
Issue: nn.CrossMapLRN2d is missing from docs
Labels: module: docs,module: nn,triaged

## 📚 Documentation

Documentation for `nn.CrossMapLRN2d` is missing from the [torch.nn docs](https://pytorch.org/docs/stable/nn.html).

cc @brianjo @mruberry @albanD @jbschlosser
Repository: rust
Issue: `cargo fix --broken-code` incorrectly applies integer casts
Labels: A-diagnostics,T-compiler,C-bug,D-invalid-suggestion,S-has-mcve

Consider the following:

```rust
fn foo(_: u32) {}

fn main() {
    let v: usize = 10;
    foo(v)
}
```

`cargo fix --broken-code` correctly notices that this code is broken, but it incorrectly applies the fix:

```rust
fn foo(_: u32) {}

fn main() {
    let v: usize = 10;
    foo(v.try_into().unwrap())
}
```

It applies the `try_into` but doesn't import `std::convert::TryInto`, causing the fix to fail

### Meta

`rustc --version --verbose`:
```
rustc 1.52.1 (9bc8c42bb 2021-05-09)
binary: rustc
commit-hash: 9bc8c42bb2f19e745a63f3445f1ac248fb015e53
commit-date: 2021-05-09
host: x86_64-unknown-linux-gnu
release: 1.52.1
LLVM version: 12.0.0
```
Repository: flutter
Issue: Remove `no-shuffle` tags from all framework tests
Labels: team,tool,P2,c: tech-debt,team-tool,triaged-tool

## Description

In https://github.com/flutter/flutter/pull/86793 we turned on shuffling of test order based on a seed in order to root out test state leakage. In the process, we added a testing tag called 'no-shuffle' which was applied to the majority of tests which currently fail with the shuffling turned on.

This issue is to clean up all of those instances of broken tests, and finally to remove the "no-shuffle" tag entirely to turn on shuffling for all tests.

## Related issues

- https://github.com/flutter/flutter/issues/47233
Repository: vscode
Issue: Git - Adding a folder to `.gitignore` should not add every single file
Labels: help wanted,feature-request,git

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: v1.57.1
- OS Version: Win 20H1

Steps to Reproduce:

1. Create an empty repository
2. Do `npm init && npm install whatever`
3. Switch to the SVM view
4. Oops, you have one bajillion changed files in your working copy! Right-click the `node_modules` folder in the SCM view and choose "Add to .gitignore".

Expected behavior:

- `node_modules/` is added to the `.gitignore`.

Actual behavior:

- Every single file in the `node_modules` subtree of the repository is added separately to the `.gitignore` ...
Repository: vscode
Issue: Add "Show all results" button when hitting maxResults
Labels: feature-request,search

When we hit the search maxResults limit, we should show a link to rerun the search without the limit.

Example:
![image](https://user-images.githubusercontent.com/323878/123181686-9c4aa600-d442-11eb-8dd3-b0e3bfe83bf5.png)

When we get too many results, it slows down in the search process, and we need to investigate this first.

Also, can take another look at the perf around calling `setChildren` in the renderer process (#127621)
Repository: godot
Issue: Button shadow render not right
Labels: bug,needs testing,topic:gui

### Godot version

3.3 stable

### System information

windows10 GLES2/GLES3

### Issue description

![image](https://user-images.githubusercontent.com/9168814/123185890-892ee900-d4c9-11eb-9092-8b8d03cf159d.png)
Alpha of center of the button shadow is a bit lower than the edge, you can see there is a slight black line of the shadow . This will cause a light line appear when add a offset to the shadow
![image](https://user-images.githubusercontent.com/9168814/123187062-fd6a8c00-d4cb-11eb-8ddf-635ef45c9e6e.png)
![image](https://user-images.githubusercontent.com/9168814/123252869-54e61780-d51f-11eb-9db6-abc3d89ea967.png)


### Steps to reproduce

Add a button and enable the shadow.

### Minimal reproduction project
[ButtonShadow.zip](https://github.com/godotengine/godot/files/6708667/ButtonShadow.zip)


_No response_
Repository: react
Issue: Inconsistent crossbrowser onBeforeInput paste event behavior
Labels: Type: Bug,Component: DOM,Status: Unconfirmed

### React version: 17.0.2
In Chrome, pasting triggers `onPaste` and `onBeforeInput`, with the `nativeEvent`s `ClipboardEvent` and `TextEvent` respectively.

In Firefox, pasting only triggers `onPaste` with `nativeEvent` `paste`.

If I'm not mistaken, this seems to be the code responsible for not triggering `onBeforeInput` on native `paste` events:
https://github.com/facebook/react/blob/27c9c95e23ddedb9163373950e364dd62038f6c0/packages/react-dom/src/events/plugins/BeforeInputEventPlugin.js#L328-L331

### React version: 17.0.2 and 18.0.0

17.0.2
https://codesandbox.io/s/condescending-cerf-e1qt9?file=/src/App.js
18.0.0
https://codesandbox.io/s/sparkling-sun-fylti?file=/src/App.js
Repository: go
Issue: x/build: configure dashboard builders to test the same configurations that will be shipped in binary releases
Labels: Builders,NeedsInvestigation

#43232 notes a case in which `go test` on a package in `std` fails for a Go toolchain installed from our supported binary distributions, but passes for a Go toolchain built from source.

Even if we fix that issue, we don't currently have a good way to prevent regressions, and it makes me wonder if there are other cases where we're shipping packages and/or tests that work locally but fail for users who use our provided installers.

For the platforms for which we ship official binaries, I think we should have dashboard builders that test the actual bytes that we would ship in a release — either by applying the same transformations that we will apply at release time, or by eliminating differences between the release process and `make.bash`.

(Related: #29205, #29239.)

CC @golang/release
Repository: flutter
Issue: Transform widgets on MaterialButton in a Column will prevent from triggering onPressed
Labels: framework,f: material design,has reproducible steps,found in release: 2.2,found in release: 2.3,team-design,triaged-design

<details> 
<summary>minimal code sample</summary> 

```dart
import 'package:flutter/material.dart';

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.grey,
        primaryColor: Colors.black,
        brightness: Brightness.dark,
      ),
      darkTheme: ThemeData(
        brightness: Brightness.dark,
      ),
      home: MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  MyHomePage({Key? key, required this.title}) : super(key: key);
  final String title;

  @override
  _MyHomePageState createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        leading: Icon(Icons.backspace),
        title: Text('test'),
      ),
      body: Column(
        mainAxisAlignment: MainAxisAlignment.center,
        children: [
          SizedBox(
            height: 60,
          ),

          /// Transform will prevent MaterialButton from triggering onPressed
          Transform.translate(
            offset: Offset(100, 0),
            child: MaterialButton(
              color: Colors.yellow,
              child: Text('Swap'),
              onPressed: () {
                print('this will not print out');
              },
            ),
          ),
        ],
      ),
    );
  }
}
``` 

</details>
Repository: ant-design
Issue: `Popover` causes jagging when `content` is big enough.
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/basic-antd4163-forked-z9ihh)

### Steps to reproduce
1. Go to the code sandbox
2. Hover on the `Hover me` button, you will see the jagging behavior of the scrollbar 
(its state instead of transformed from `hide -> show` it was `hide -> show -> hide -> show`)

![](https://i.stack.imgur.com/OYxfs.png)

### What is expected?
The scrollbar appears smoothly from `hide -> show` instead of jagging like `hide -> show -> hide -> show`)

### What is actually happening?
I guess it's because of `autoAdjustOverflow`

| Environment | Info |
|---|---|
| antd | 4.16.5 |
| React | 17.0.0 |
| System | Windows 10 |
| Browser | Chrome |

---
**I've also asked this question on Stackoverflow** at here: https://stackoverflow.com/questions/68064451/popover-of-ant-design-causes-jagging-when-content-is-big-enough-how-to-fix

You may want to give it a peek in order to see how other people say about it.

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: godot
Issue: Oversensitivity in trackpad scrolling and gestures
Labels: bug,platform:windows,platform:linuxbsd,platform:web,topic:editor,confirmed,usability,topic:input,topic:gui

### Godot version

3.3.2.stable

### System information

Windows 10, GLES3, Intel(R) Iris(R) Xe Graphics

### Issue description

Vertical scrolling with a trackpad is noticeably too sensitive. Each pixel of scrolling input causes a huge jump in movement.

Similar issues suggested disabling Smooth Scrolling or tweaking Text Editor / V Scroll Speed under the Editor Settings, but those only relate to the Text Editor's behavior, and doesn't fix the oversensitivity in the first place.

Interestingly, all horizontal scrolling feels spot-on and smooth. I wouldn't have guessed it uses a totally different system, but I think it must.

The problem is not my trackpad, since other applications scroll just fine.

### Steps to reproduce

Go to any element with vertical scrolling (or create your own with a ScrollContainer or something) and scroll using the trackpad with two fingers. Contrast this with other software's scrolling, or even scrolling horizontally with Godot.

### Minimal reproduction project

Issue can be observed in the editor, as long as a trackpad is being used.

Video showcase: https://youtu.be/HGxDTq8mwT4
Repository: PowerToys
Issue: fancyzone error for everything program
Labels: Issue-Bug,Product-FancyZones,Priority-3,Status-Reproducible

### Microsoft PowerToys version

0.33.1

### Running as admin

- [X] Yes

### Area(s) with issue?

FancyZones

### Steps to reproduce

1. open 'Everything' program(searching application)
2. shift+drag&drop to the fancyzone

![1](https://user-images.githubusercontent.com/86400505/123218924-43911100-d507-11eb-824f-5d171ad881c0.jpg)


### ✔️ Expected Behavior

fit in the zone

### ❌ Actual Behavior

it doesn't fit

### Other Software

nothing special