sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: node
Issue: fs.watch Does Not Work For WSL2 File Paths
Labels: fs,windows,wsl

* **Version**: v15.12.0, and I've tested on v14.16.0 and v12.13.1 (leading me to assume it is a v15.12.0<)
* **Platform**: Microsoft Windows NT 10.0.19041.0 x64
* **WSL2 Subsystem**: (Ubuntu) Linux DESKTOP-**** 4.19.84-microsoft-standard #1 SMP Wed Nov 13 11:44:37 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
* **Subsystem**: fs

### What steps will reproduce the bug?

Currently I am able to reproduce the without any special edge cases or circumstance. There are requirements for getting WSL2 up, and I am using (Ubuntu) Linux DESKTOP-**** 4.19.84-microsoft-standard #1 SMP Wed Nov 13 11:44:37 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux. 

*Create a file located someplace on the WSL2 file system. I chose to use ~/test.txt, and put some sample data in there. Then on the Windows System, have installed Node version ones listed above, and run the node REPL with the following commands. 
````javascript
const fs = require('fs');
fs.watch('\\\\wsl$\\Ubuntu\\home\\{WSL2_USERNAME}\\test.txt');
```` 
You will get back the following error:
````
Error: EISDIR: illegal operation on a directory, watch '\\wsl$\Ubuntu\home\{WSL2_USERNAME}\test.txt'
    at __node_internal_captureLargerStackTrace (node:internal/errors:415:5)
    at __node_internal_uvException (node:internal/errors:472:10)
    at FSWatcher.<computed> (node:internal/fs/watchers:244:19)
    at Object.watch (node:fs:1593:34) {
  errno: -4068,
  syscall: 'watch',
  code: 'EISDIR',
  path: '\\\\wsl$\\Ubuntu\\home\\{WSL2_USERNAME}\\test.txt',
  filename: '\\\\wsl$\\Ubuntu\\home\\{WSL2_USERNAME}\\test.txt'
}
````

### Additional information
I thought this might have to do with the UPC paths, however, I do see fs does have UPC validation, and this is happening more on the actual syscall for watch. I might be able to pull out some more debugging info on the node_internal code, but that could lead this to be a libuv issue. I'm posting here, as it is happening while I was using node... But if someone can confirm this is actually a libuv issue, then  I can move the issue to that project.
Repository: ant-design
Issue: Select component in Popover resulted in unexpected behaviors if open prop is controlled (incorrect initial positioning, permanently hidden dropdown, focus not working after the first one)
Labels: Inactive

- [x] I have searched the [issues](https://github.com/ant-design/ant-design/issues) of this repository and believe that this is not a duplicate.

### Reproduction link
[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/antd-reproduction-template-forked-g3gbt?file=/index.js)

### Steps to reproduce
Click on the `<span>` element inside the popover to show the dropdown. Click it again (or select something, or click outside the dropdown) to close it. Repeat as needed. 



   

### What is expected?
No incorrect initial position of the dropdown. Subsequent clicks should make the dropdown appear again. Focus should work. 

### What is actually happening?
1. Initially, the dropdown appears on the top corner left of the screen before adjusting to the right position. Auto focus also works in this initial click. 
2. On the subsequent click: 
     - Dropdown doesn't show. After inspecting the html, it appears that the width is set to 0. (Note: setting `dropdownMatchSelectWidth` = some integer seems to fix the issue). 
     - The focus is also not working as expected. 

| Environment | Info |
|---|---|
| antd | 4.14.1 |
| React | React@17.0.2 |
| System | MacOS Catalina 10.15.7 |
| Browser | Chrome Version 89.0.4389.90  |

---
To illustrate the desired result:
Comment out the Popover code. Uncomment the code above it. Without the popover component, the controlled `open` prop seems to work properly (i.e. the dropdown works), no incorrect initial position, and focus works as desired.


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: rust
Issue: Failure to infer closure argument type under some circumstances
Labels: A-closures,T-compiler,A-inference,C-bug

<!--
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.
-->

I tried this code:

```rust
trait Foo<P> {
    fn foo(&self, p: P);
}

impl<F: FnMut(&u8) -> bool> Foo<F> for [u8] {
    fn foo(&self, _f: F) {}
}

impl Foo<u8> for [u8] {
    fn foo(&self, _c: u8) {}
}

fn main() {
    b"abc".foo(|b| match b { b' ' => true, _ => false});
}
```

This fails to compile with:
```
error[E0631]: type mismatch in closure arguments
  --> src/main.rs:14:12
   |
14 |     b"abc".foo(|b| match b { b' ' => true, _ => false});
   |            ^^^ ----------- found signature of `fn(u8) -> _`
   |            |
   |            expected signature of `for<'r> fn(&'r u8) -> _`
   |
   = note: required because of the requirements on the impl of `Foo<[closure@src/main.rs:14:16: 14:55]>` for `[u8]`
```

This builds fine if you remove the `impl Foo<u8> for [u8]`.
It also builds fine with an explicit type for the closure argument: ` b"abc".foo(|b: &u8| match b { b' ' => true, _ => false});`

The error changes when using `b"abc".foo(|b| *b == b' ');`, to:
```
error[E0282]: type annotations needed
  --> src/main.rs:14:17
   |
14 |     b"abc".foo(|b| *b == b' ');
   |                 ^ consider giving this closure parameter a type
   |
   = note: type must be known at this point
```

Again, in that case, it builds fine without the `impl Foo<u8> for [u8]`.

You can get yet another error message with `b"abc".foo(|&b| b == b' ');`:
```
error[E0308]: mismatched types
  --> src/main.rs:14:12
   |
14 |     b"abc".foo(|&b| b == b' ');
   |            ^^^ one type is more general than the other
   |
   = note: expected type `for<'r> FnMut<(&'r u8,)>`
              found type `FnMut<(&u8,)>`
note: this closure does not fulfill the lifetime requirements
  --> src/main.rs:14:16
   |
14 |     b"abc".foo(|&b| b == b' ');
   |                ^^^^^^^^^^^^^^
```

And yet again, it builds fine without the `impl Foo<u8> for [u8]`.

This is all reproducible with the current stable and nightly on the rust playground.
Repository: flutter
Issue: Make it obvious if there are disabled platforms in `flutter doctor`
Labels: c: new feature,tool,P3,team-tool,triaged-tool

I think it's possible that users may disable some of the currently supported platforms without realizing it. Flutter config does display what is/isn't enabled, but this isn't a very frequently run command.

Instead we should put some additional context in doctor, maybe something like:

Summary:
```
[✓] Flutter (Channel master, 2.1.0-13.0.pre.283, on Mac OS X 10.15.7 19H512 darwin-x64, locale en-US)
...
[✓] Supported Platforms (3 enabled, 1 disabled, 2 unavailable)
```

Verbose:
```
[✓] Flutter (Channel master, 2.1.0-13.0.pre.283, on Mac OS X 10.15.7 19H512 darwin-x64, locale en-US)
    • Flutter version 2.1.0-13.0.pre.283 at /Users/jonahwilliams/Documents/flutter
    • Framework revision 5b95cb75d2 (3 days ago), 2021-03-25 16:27:01 -0700
    • Engine revision b5e15d055d
    • Dart version 2.13.0 (build 2.13.0-162.0.dev)

...

[✓] Supported Platforms (3 enabled, 1 disabled, 2 unavailable)
    • macOS (desktop) | enabled
    • Chrome (web)  | disabled (To enable run flutter config --enable-web)
    • iOS (mobile)  | enabled
    • Android (mobile)  | enabled
    • Windows (desktop)  | unavailable
    • Linux (desktop)  | unavailable
```

We should only show platforms that _could_ be enabled for the user's current channel. (which is mostly all of them...)
Repository: godot
Issue: can_instance error when using third party nuget packages with .NET Standard 2.1 and 2.0
Labels: topic:dotnet

**Godot version:**
3.2.3.stable.mono.official


**OS/device including version:**
Windows 10 21H1 19043.906


**Issue description:**
When trying to use the Microsoft.AspNetCore.SignalR.Client nuget package with a Godot project, any scripts that use anything from the library cause the error: can_instance: Cannot instance script because the class 'ClassNameHere' could not be found. This error does not occur if targeting .NET 4.8. I also disabled nullable reference types to confirm that was not the cause of the issue either. Microsoft.AspNetCore.SignalR.Client targets netstandard2.0 and should work without issue in netstandard2.0, netstandard2.1, and net5.0 (which Godot does not yet support).


**Steps to reproduce:**

1. Create a new Godot project and add a C# script to a node
2. Change the target framework to netstandard2.1 (netstandard2.0 has the same issue)
3. Add the following package reference: PackageReference Include="Microsoft.AspNetCore.SignalR.Client" Version="5.0.4"
4. In your script for the node, add the property "public HubConnection Connection { get; set; }" and in the _Ready() method add the following line: "Connection = new HubConnectionBuilder() .WithUrl("http://localhost:53353/ChatHub").Build();"
5. Attempt to run the scene with the node and attached script, you should receive the same error.


**Minimal reproduction project:**
[GodotSignalR.zip](https://github.com/godotengine/godot/files/6219241/GodotSignalR.zip)
Repository: go
Issue: reflect: StructOf allows fields with inconsistent export information
Labels: NeedsInvestigation,compiler/runtime

The `StructField.PkgPath` field should only be populated if the field is unexported. Currently in Go, this can only occur if the [first character is an uppercase letter](https://play.golang.org/p/1oSgom3fIGx). Thus, an exported `Name` should not be allowed with `PkgPath` also being specified. However, this is [currently permitted](https://play.golang.org/p/TUeY7qNQvgR):
```go
t := reflect.StructOf([]reflect.StructField{{
	Name:    "Field",                   // exported field
	PkgPath: "some.bogus/package/path", // should only be specified for unexported fields
	Type:    reflect.TypeOf(0),
}})                                         // expect this to panic, but it doesn't
f := t.Field(0)
fmt.Printf("%q.%s\n", f.PkgPath, f.Name)    // "some.bogus/package/path".Field
```

I expect the snippet above to panic.
Repository: flutter
Issue: Correct the devicePixelRatio doc 
Labels: framework,d: api docs,P2,team-framework,triaged-framework

Hi Guys,
I am using Flutter to develop an app that have a ruler inside
By definition it should be correct:
Flutter’s unit is DP or dip (aka density independent px https://developer.android.com/training/multiscreen/screendensities#TaskUseDP ). it's independent from the screen pixel ratio.

Converting mm>dp or dp>mm is similar to mm>inch/inch>mm.
The relationship between them is fairly simple : 1 inch = 25.4 mm = 160.0 DP Which means 1 mm = 6.299 DP.

So I have a code to convert like this:
```
double fromMMToFlutterUnit(double mm) {
  return mm * 6.299;
}
```
it should be correct but in some big screen like iPad or tablet it become wrong.

is there any corrected way to convert millimeter to Flutter unit?

Thanks and regards,
Viet
Repository: transformers
Issue: Please implement DUMA: Reading Comprehension with Transposition Thinking
Labels: New model

# 🚀 Feature request

<!-- A clear and concise description of the feature proposal.
     Please provide a link to the paper and code in case they exist. -->
This one is on the race leaderborad top, will you guys consider implement this?

## 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. -->

## Your contribution

<!-- Is there any way that you could help, e.g. by submitting a PR?
     Make sure to read the CONTRIBUTING.MD readme:
     https://github.com/huggingface/transformers/blob/master/CONTRIBUTING.md -->
Repository: youtube-dl
Issue: Playlist thumbnail, Python package
Labels: question

<!--

######################################################################
  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:
- Look through the README (http://yt-dl.org/readme) and FAQ (http://yt-dl.org/faq) for similar questions
- Search the bugtracker for similar questions: http://yt-dl.org/search-issues
- Finally, put x into all relevant boxes (like this [x])
-->

- [x] I'm asking a question
- [x] I've looked through the README and FAQ for similar questions
- [x] I've searched the bugtracker for similar questions including closed ones


<!--
Ask your question in an arbitrary form. Please make sure it's worded well enough to be understood, see https://github.com/ytdl-org/youtube-dl#is-the-description-of-the-issue-itself-sufficient.
-->


### youtube_dl version
```
>pip show youtube_dl

Name: youtube-dl
Version: 2021.3.25
Summary: YouTube video downloader
Home-page: https://github.com/ytdl-org/youtube-dl
Author: Ricardo Garcia
Author-email: ytdl@yt-dl.org
License: Unlicense
Location: \venv\lib\site-packages
Requires:
Required-by:
```

### Python script
```
from json import dump
from youtube_dl import YoutubeDL

url = 'https://www.youtube.com/playlist?list=OLAK5uy_lR-TqR-DobKiF9DtVzELCPz7_v-bUr5fM'
info_filename = './info.json'

info =  YoutubeDL({}).extract_info(url, download=False)
with open(info_filename, 'w') as info_file:
    dump(info, info_file, indent=4)
```

### Result info.json
```
{
    "_type": "playlist",
    "entries": [
        ...
    ],
    "id": "OLAK5uy_lR-TqR-DobKiF9DtVzELCPz7_v-bUr5fM",
    "title": "LAUNCH",
    "extractor": "youtube:tab",
    "webpage_url": "https://www.youtube.com/playlist?list=OLAK5uy_lR-TqR-DobKiF9DtVzELCPz7_v-bUr5fM",
    "webpage_url_basename": "playlist",
    "extractor_key": "YoutubeTab"
}
```
### Question

Does it possible to retrieve playlist thumbnails urls with current youtube_dl python package?
Does it possible to download playlist thumbnails with current youtube_dl python package?
Repository: storybook
Issue: Controltype repeater field
Labels: feature request,addon: controls

Hi,

It would be nice if the controls would enhance a controll called: "repeater field"

This would be nice for reactive add or remove items in a array (or even object).
This would be handy for showing a menu list:
```js
    { name: 'item1, url: 'item1' },
    { name: 'item2, url: 'item2' },
```

would look something like this:
![afbeelding](https://user-images.githubusercontent.com/6578052/112820334-cb40be00-9085-11eb-89db-473cadacec72.png)

This gives you a nice UI to add or remove a array or string, very UI friendly.
Repository: TypeScript
Issue: Source files being ignored from symlink directories
Labels: Bug,Help Wanted

# Bug Report

Source files are being ignored from symlink directories when `tsconfig.json` contains a configuration such as `"include": ["**/file", "src/**/*]`

### 🔎 Search Terms

symlink, listFiles

### 🕗 Version & Regression Information

- This changed between versions 3.3.4000 and 3.4.1

Works well on 3.3.4000
Doesn't work from 3.4.1
Doesn't work on typescript@next (4.3.0)

### 💻 Code

Reproduction repository: https://github.com/bvallee-thefork/tsc-bug-symlink

### 🙁 Actual behavior

With `"include": ["src/**/*]`, `src/symlink/file2.ts` is correctly listed in the output of: `npx tsc -p tsconfig-valid.json --listFiles`

With `"include": ["**/file", "src/**/*]`, `src/symlink/file2.ts` is not listed in the output of: `npx tsc -p tsconfig.json --listFiles`

### 🙂 Expected behavior

`src/symlink/file2.ts` should be listed in the output of `npx tsc -p tsconfig.json --listFiles` with the following tsconfig:
`"include": ["**/file", "src/**/*]`
Repository: pytorch
Issue: Not possible to save dataloader in C++
Labels: module: dataloader,triaged,enhancement

## 🐛 Bug

There are no built-in functions for saving dataloaders to file in C++. `torch::save(dataloader, "path/dataloader.pt")` throws an error.

## To Reproduce

Steps to reproduce the behavior:

1. Create dataloader instance
```
  auto train_set =
      CustomDataset(data.first).map(torch::data::transforms::Stack<>());
  auto train_size = train_set.size().value();
  auto train_loader =
      torch::data::make_data_loader<torch::data::samplers::SequentialSampler>(
          std::move(train_set), options.train_batch_size);
```
2. User ```torch::save``` to save it to a file
```
  torch::save(dataloader, "path/dataloader.pt");
```
3. Error
```
/home/USER/pytorch/include/torch/csrc/api/include/torch/serialize.h: In instantiation of ‘void torch::save(const Value&, SaveToArgs&& ...) [with Value = std::unique_ptr<torch::data::StatelessDataLoader<torch::data::datasets::MapDataset<CustomDataset, torch::data::transforms::Stack<torch::data::Example<> > >, torch::data::samplers::SequentialSampler>, std::default_delete<torch::data::StatelessDataLoader<torch::data::datasets::MapDataset<CustomDataset, torch::data::transforms::Stack<torch::data::Example<> > >, torch::data::samplers::SequentialSampler> > >; SaveToArgs = {std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&}]’:
[build] ../trainGTSRB.cpp:200:47:   required from here
[build] /home/USER/pytorch/include/torch/csrc/api/include/torch/serialize.h:43:11: error: no match for ‘operator<<’ (operand types are ‘torch::serialize::OutputArchive’ and ‘const std::unique_ptr<torch::data::StatelessDataLoader<torch::data::datasets::MapDataset<CustomDataset, torch::data::transforms::Stack<torch::data::Example<> > >, torch::data::samplers::SequentialSampler>, std::default_delete<torch::data::StatelessDataLoader<torch::data::datasets::MapDataset<CustomDataset, torch::data::transforms::Stack<torch::data::Example<> > >, torch::data::samplers::SequentialSampler> > >’)
[build]    43 |   archive << value;
[build]       |   ~~~~~~~~^~~~~~~~
```


## Expected behavior

Expect to save the dataloader in a similar way to what is possible in Python, as mentioned in this forum thread https://discuss.pytorch.org/t/how-to-save-dataloader/62813 .

## Environment
- OS: Ubuntu 20.04.2 LTS (x86_64)
- GCC version: (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
- CMake version: version 3.18.2
- CUDA runtime version: 11.2.67
- GPU models and configuration: GPU 0: GeForce RTX 2060
- Nvidia driver version: 460.27.04

- PyTorch 1.9.0
- Installed PyTorch from source (https://github.com/pytorch/pytorch#from-source)
- Build with CMake

## Additional context
I need to create a file that loads the dataloader from a file, and tests.


cc @SsnL @VitalyFedyunin @ejguan
Repository: godot
Issue: Stuttering audio on Chrome 89.0+ (upstream Chrome regression in ScriptProcessorNode)
Labels: bug,platform:web,confirmed,topic:thirdparty,topic:audio

**Godot version:**
3.2.3 stable, 3.3 RC 6
Not a Godot regression, it's a Chrome update that triggered the issue for pre-existing builds which worked fine.


**OS/device including version:**
Windows 10 Home Build 19042
Mageia 9 x86_64 as of March 29

Affected browser versions:
- Chrome Stable 89.0.4389.90 (both Windows and Linux)
- Chrome Canary 91.0.4462.0 (Windows, not tested on Linux)
- Strangely enough, [I couldn't reproduce it with any Chromium version](https://github.com/godotengine/godot/issues/43210#issuecomment-809250197).


**Issue description:**
Since Chrome 89.0.4389.90 (possibly older 89.0.x builds too), there's severe audio stuttering in most Godot web exports when playing music.
This appears to be a Chrome regression as the same exports were working fine prior to a recent update.

This is likely this upstream bug report: https://bugs.chromium.org/p/chromium/issues/detail?id=1187016
Which is the consequence of security fixes in ScriptProcessorNode.

The upstream bug report is supposed to have been fixed a few days ago in Chrome Canary, but I could still reproduce it with @3p0ch-NG's reproduction project. I'll report it upstream. *Edit:* Done: https://bugs.chromium.org/p/chromium/issues/detail?id=1187016#c66

*Edit 2:* New upstream issue: https://bugs.chromium.org/p/chromium/issues/detail?id=1193494

(Moved this report from https://github.com/godotengine/godot/issues/43210#issuecomment-808514120 which is a different issue from what #43210 initially handled.
CC @rcbotCheeseh @CedLec @3p0ch-NG who initially commented on that other issue.)


**Steps to reproduce:**
- This test project can be used to reproduce the issue: https://www.newgrounds.com/portal/view/project/1594770
  There should be significant stuttering at the start and possibly throughout the whole playback (though I've also had times where it didn't stutter reliably).
- Make sure to click the game window to start the audio playback, as per browser policy.

**Minimal reproduction project:**
https://www.newgrounds.com/portal/view/project/1594770
Repository: vue
Issue: <v-show>  style.display is incorrect when reusing the elm
Labels: bug,has workaround

### Version
2.6.11

### Reproduction link
[https://jsfiddle.net/CasperDai/mred18vo/7/](https://jsfiddle.net/CasperDai/mred18vo/7/)







### Steps to reproduce
click 'change'

### What is expected?
el.style.display is 'flex'

### What is actually happening?
el.style.display is ''

<!-- generated by vue-issues. DO NOT REMOVE -->
Repository: flutter
Issue: package assets declared under dev_dependency shouldn't be included in release bundle
Labels: tool,a: assets,a: size,c: proposal,a: build,a: release,P3,team-tool,triaged-tool

## Steps to Reproduce

See example project https://github.com/rh-id/example_dev_dependency_fi for the steps

**Expected results:** Flutter should ignore package assets declared under `dev_dependency` on release bundle / version

**Actual results:** Flutter include the package assets declared under `dev_dependency` on release bundle / version

<details>
  <summary>Logs</summary>
<!-- Finally, paste the output of running `flutter doctor -v` here. -->

```
[✓] Flutter (Channel stable, 2.0.2, on Linux, locale en_US.UTF-8)
    • Flutter version 2.0.2 at /home/rubyh/Flutter/flutter
    • Framework revision 8962f6dc68 (3 weeks ago), 2021-03-11 13:22:20 -0800
    • Engine revision 5d8bf811b3
    • Dart version 2.12.1

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /home/rubyh/Android/Sdk
    • Platform android-30, build-tools 30.0.3
    • ANDROID_HOME = /home/rubyh/Android/Sdk
    • ANDROID_SDK_ROOT = /home/rubyh/Android/Sdk
    • Java binary at: /usr/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.10+9-Ubuntu-0ubuntu1.20.04)
    • All Android licenses accepted.
```
</details>

## Related Issues:
Do not create plugins from dev_dependencies #56591
Don't include dev_dependencies in native build scripts #45714
integration_test embedded in shipping iOS apps when added to pubspec #74274