sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: rustdoc: Add more test coverage
Labels: A-testsuite,T-rustdoc,C-tracking-issue

### Summary

Currently, [rustdoc](https://github.com/rust-lang/rust/tree/master/src/librustdoc) doesn't have much test coverage, but it _does_ have a lot of edge cases. We would like to have more test coverage, so we can improve the code with less risk of introducing bugs.

It's even helpful to add tests for incorrect behavior since it will help us find, fix, and test the fixes for bugs.

### What to test

- Behavior of re-exports (e.g., `pub use self::foo::bar`) and inlining (some re-exports are rendered as re-exports, while others have their docs copied as if the re-export is the definition)
- Trait implementations, including normal impls, blanket impls (e.g., `impl<T> MyTrait for &T`), and auto impls (like `Sized`, `Send`, and `Sync`)
- Notable traits popup (appears as an `(i)` next to return types); it has some bugs currently that would be good to fix.

### How to test

Here is the documentation for rustdoc's main tests (the tests in `src/test/rustdoc`):

https://github.com/rust-lang/rust/blob/49d42325d0888a27ed50bf918d378fbf7f41a348/src/etc/htmldocck.py#L28-L100

You may also want to look at some existing tests in `src/test/rustdoc`.

Please note that you **do _not_ need to check that rustdoc's behavior is correct**. We will check during code review, and as mentioned earlier, tests for incorrect behavior can be helpful too.

**If you have any questions or get stuck, please ask here or [on Zulip in `#rustdoc`](https://rust-lang.zulipchat.com/#narrow/stream/266220-rustdoc)!**


<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

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

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: godot
Issue: Android screen orientation `sensor_portrait` doesn't work
Labels: bug,platform:android,topic:porting

### Godot version

3.4.stable

### System information

Android

### Issue description

Screen orientation `sensor_portrait` should keep the game in portrait mode, but automatically rotate the screen depending on whether or not the Android device is upside-down. However, currently, when the device is upside-down, the screen does not rotate.

Note: Both `sensor_landscape` and `sensor` modes work as expected. In `sensor_landscape` mode, the game will stay in landscape mode and automatically rotate depending on whether the device is rotated to the left or right. In `sensor` mode the game screen will rotate depending on the orientation of the device. If the device is upside-down, it will rotate as it should do in `sensor_portrait` mode.

### Steps to reproduce

- Set the screen orientation to `sensor_portrait` mode.
- Export to Android and turn the device upside-down.
- Note that the game screen doesn't rotate.
- Note that when setting the screen orientation to either of the other two sensor modes, the game screen rotates as expected.

### Minimal reproduction project

[ScreenOrientation.zip](https://github.com/godotengine/godot/files/7576974/ScreenOrientation.zip)
Repository: rust
Issue: ICE: unstable fingerprints for evaluate_obligation
Labels: I-ICE,T-compiler,A-incr-comp,C-bug

```
   Compiling graphql-parser v0.3.0 (/home/boeckb/code/depot/lang-rust/rust-graphql-parser/src)
   Compiling graphql_client_codegen v0.10.0 (/home/boeckb/code/depot/lang-rust/rust-graphql-client/src/graphql_client_codegen)
error: internal compiler error: encountered incremental compilation error with evaluate_obligation(774342b51f470b6c-5baeb40ee56ea2b3)
  |
  = help: This is a known issue with the compiler. Run `cargo clean -p graphql_client_codegen` or `cargo clean` to allow your project to compile
  = note: Please follow the instructions below to create a bug report with the provided information
  = note: See <https://github.com/rust-lang/rust/issues/84970> for more information

thread 'rustc' panicked at 'Found unstable fingerprints for evaluate_obligation(774342b51f470b6c-5baeb40ee56ea2b3): Ok(EvaluatedToOk)', /builddir/build/BUILD/rustc-1.56.1-src/compiler/rustc_query_system/src/query/plumbing.rs:644:13
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

error: internal compiler error: unexpected panic

note: the compiler unexpectedly panicked. this is a bug.

note: we would appreciate a bug report: https://github.com/rust-lang/rust/issues/new?labels=C-bug%2C+I-ICE%2C+T-compiler&template=ice.md

note: rustc 1.56.1 (Fedora 1.56.1-1.fc34) running on x86_64-unknown-linux-gnu

note: compiler flags: -C embed-bitcode=no -C debuginfo=2 -C incremental --crate-type lib

note: some of the compiler flags provided by cargo are hidden

query stack during panic:
#0 [evaluate_obligation] evaluating trait selection obligation `std::vec::Vec<graphql_parser::query::Directive<'static, std::string::String>>: std::marker::Send`  |  = note: this failure-note originates in the macro `__lazy_static_create` 
(in Nightly builds, run with -Z macro-backtrace for more info)

#1 [check_item_well_formed] checking that `<impl at /home/boeckb/.cargo/registry/src/github.com-1ecc6299db9ec823/lazy_static-1.4.0/src/lib.rs:133:9: 146:10>::deref::__stability::LAZY` is well-formed
end of query stack
error: could not compile `graphql_client_codegen` due to previous error
warning: build failed, waiting for other jobs to finish...
error: build failed
```

I think this has to do with incremental compilation, so a minimal example is unlikely to work out well. Compiling the crate was fine. Once I went to `cargo check` some changes in a local checkout of `graphql-parser` and got that working, coming back to `graphql_client_codegen` ended up with an ICE until I cleaned the `graphql_client_codegen` crate.

I am using `sccache` if that matters.
Repository: material-ui
Issue: [ButtonGroup] CardActions spacing is not working
Labels: component: ButtonGroup,v8.x

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯

Here is a [sandbox](https://codesandbox.io/s/magical-robinson-cvkwt?file=/src/Demo.tsx) where I took [SplitButton example from the documentation](https://mui.com/components/button-group/#split-button) and added it as an action to a card.

<img width="604" alt="Screen Shot 2021-11-21 at 5 08 17 PM" src="https://user-images.githubusercontent.com/989066/142780732-e57f3d6c-c25c-47e7-bbee-3501c18af5a7.png">

On v5 version spacing is not working between a Button and the ButtonGroup. With v4 everything worked fine.

### Expected behavior 🤔

Expect to see a spacing between every action.

### Steps to reproduce 🕹

Please check out a sandbox here: https://codesandbox.io/s/magical-robinson-cvkwt?file=/src/Demo.tsx

### Context 🔦

I'm trying to upgrade from v4 to v5 and facing some issues.

### Your environment 🌎

<details>
  <summary>`npx @mui/envinfo`</summary>

```
❯ npx @mui/envinfo
Need to install the following packages:
  @mui/envinfo
Ok to proceed? (y) y

  System:
    OS: macOS 11.6
  Binaries:
    Node: 17.0.1 - /usr/local/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 8.1.0 - /usr/local/bin/npm
  Browsers:
    Chrome: 96.0.4664.55
    Edge: Not Found
    Firefox: 85.0.2
    Safari: 15.0
  npmPackages:
    @emotion/react: ^11.6.0 => 11.6.0 
    @emotion/styled: ^11.6.0 => 11.6.0 
    @mui/core:  5.0.0-alpha.54 
    @mui/icons-material: ^5.1.0 => 5.1.0 
    @mui/lab: ^5.0.0-alpha.54 => 5.0.0-alpha.54 
    @mui/material: ^5.1.0 => 5.1.0 
    @mui/private-theming:  5.1.0 
    @mui/styled-engine:  5.1.0 
    @mui/styles: ^5.1.0 => 5.1.0 
    @mui/system:  5.1.0 
    @mui/types:  7.1.0 
    @mui/utils:  5.1.0 
    @types/react: ^16.8.0 => 16.14.8 
    react: ^16.8.4 => 16.14.0 
    react-dom: ^16.8.4 => 16.14.0 
    typescript: ^3.9.7 => 3.9.10 
```
</details>
Repository: rust
Issue: Implementors column on trait page is always empty
Labels: T-rustdoc,C-discussion,A-rustdoc-ui

https://github.com/rust-lang/rust/blob/65f3f8b220f020e562c5dd848ff7319257a7ba45/src/librustdoc/html/render/mod.rs#L2328

This leads to 

<img width="1279" alt="image" src="https://user-images.githubusercontent.com/28781354/142785887-d86ec3b8-025f-417e-827a-b8fa0e3b235d.png">

when the Implementors column is empty

This is finiky to implement, cant just find the html id's for a given item cannot be determined from that item, due to the `derive_id` makeing the id dependent on `cx` state.

https://github.com/rust-lang/rust/blob/cebd2dda1d9071f2209079370c412f4ef9ef2b82/src/librustdoc/html/render/mod.rs#L1694-L1703

A way around this would be to add a `HashMap<DefId, String>` to `Context`, but I'm not sure if this is the best way arround this, and would apprecieate other ideas. 

@rustbot claim

@rustbot modify labels: +A-rustdoc-ui  +T-rustdoc

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"aDotInTheVoid"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: godot
Issue: Project closes if there's a broken dependency
Labels: bug,topic:editor,needs testing,crash

### Godot version

3.4.stable

### System information

Linux Manjaro 21.2

### Issue description

I've formated my PC and, as I oppened my project (which I've downloaded) the editor crashed. 

It keeps happening and, after some thougth, I've tried to open it on 3.3.4. It worked, but then I've discovered I've had a broken dependency.

As I fixed, the project then oppened normally on 3.4.

I've broked again, for testing, and yeah, it was that. 

The broken dependencies were .gd and .tres (their names). 

I'm explaining like this because I've tried to repeat the bug with a new project so I could send to you but, saddly, everything worked fine.

By the way, the scene with the broken dependencies doesn't even starts with the editor, the editor look for them still - Is it because they are custom rich text effects? 

### Steps to reproduce

I can't reproduce it unless it is with my specific project. In it it is just like I've said:

Open it > Godot will close without notice before loading it all > fix the dependency names > It will work again > closes > change the dependency name > now you can repeat (only in my project)

### Minimal reproduction project

_No response_
Repository: material-ui
Issue: [Migration] v4 to v5 codemod converts all .js files to CRLF line endings on Windows, ignoring existing line endings
Labels: new feature,package: codemod

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯

The codemod rewrites every JS file in the specified directory using CRLF line endings, even files that aren't otherwise modified by the codemod.

### Expected behavior 🤔

Files that need to be modified to migrate to v5 should be written out with the existing line endings, regardless of which OS the codemod is being run on.  Other files should be left untouched.

### Steps to reproduce 🕹

Steps:

1. On Windows 10, check out a repo with LF line endings.
2. Run `npx @mui/codemod v5.0.0/preset-safe .`

Result: every file will now have CRLF line endings.

### Context 🔦

The repo I'm working with has all files checked in with LF line endings.  The `autocrlf` git setting is set to `input` on my machine, so the files are checked out with unchanged line endings.

I looked at the jscodeshift options, but didn't see anything obvious that would be able to change this behavior.

### Your environment 🌎

<details>
  <summary>`npx @mui/envinfo`</summary>

```
  System:
    OS: Windows 10 10.0.19043
    CPU: (8) x64 Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz
    Memory: 1.43 GB / 15.81 GB
  Binaries:
    Node: 16.13.0 - C:\Program Files\nodejs\node.EXE
    npm: 8.1.4 - ~\AppData\Roaming\npm\npm.CMD
  Managers:
    RubyGems: 3.1.4 - C:\Ruby27-x64\bin\gem.CMD
  Utilities:
    Git: 2.34.0.
  Virtualization:
    Docker: 20.10.8 - C:\Program Files\Docker\Docker\resources\bin\docker.EXE
  SDKs:
    Windows SDK:
      AllowAllTrustedApps: Disabled
  Languages:
    Bash: 5.0.17 - C:\WINDOWS\system32\bash.EXE
    Ruby: 2.7.2 - C:\Ruby27-x64\bin\ruby.EXE
  Browsers:
    Chrome: 95.0.4638.69
    Edge: Spartan (44.19041.1266.0), Chromium (96.0.1054.29), ChromiumDev (97.0.1069.0)
    Internet Explorer: 11.0.19041.1202
```

</details>
Repository: vscode
Issue: With `md.supportHtml = true` and VS Code Remote SSH, a single img tag on compleition items cannot be loaded
Labels: bug,help wanted,markdown

Version: 1.63.0-insider (Universal)
Commit: bedf867b5b02c1c800fbaf4d6ce09cefbafa1592
Date: 2021-11-18T05:17:00.890Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Darwin arm64 20.6.0

Related to #136027

With `md.supportHtml = true` and VS Code Remote SSH, a single img tag on compleition items cannot be loaded. If we write the img tag and markdown images in the same item, the img tag can be loaded.

Steps to Reproduce:

1. Open a remote workspace with VS Code Remote SSH
1. Execute https://github.com/tamuratak/vscode-extension-samples/tree/supporthtml_img_local_2/completions-sample
2. Execute `Trigger Suggest`
3. The image cannot be loaded.

![スクリーンショット 2021-11-22 13 20 32](https://user-images.githubusercontent.com/10665499/142800833-6e79a0ad-0201-46f4-b332-da919de0570f.png)

If I replace the markdown with `1 <img src="${pngPathUriString}"> 2 ![img](${pngPathUriString})`, then the images can be loaded.

![スクリーンショット 2021-11-22 13 21 31](https://user-images.githubusercontent.com/10665499/142800925-022aad49-0add-4716-8c5d-1bb8a861a318.png)

```ts



import * as vscode from 'vscode';
import * as path from 'path';


export function activate(context: vscode.ExtensionContext) {

	const provider1 = vscode.languages.registerCompletionItemProvider('plaintext', {

		provideCompletionItems(document: vscode.TextDocument, position: vscode.Position, token: vscode.CancellationToken, context: vscode.CompletionContext) {

			const pngPath = path.join(__dirname, '..', 'a.png')
			const pngPathUriString = vscode.Uri.file(pngPath).toString()

			const snippetCompletion = new vscode.CompletionItem('Good part of the day');
			snippetCompletion.insertText = new vscode.SnippetString('Good ${1|morning,afternoon,evening|}. It is ${1}, right?');
			const md = new vscode.MarkdownString(`1 <img src="${pngPathUriString}">`);
			md.supportHtml = true
			snippetCompletion.documentation = md

			// return all completion items as array
			return [
				snippetCompletion
			];
		}
	});
	context.subscriptions.push(provider1);
}
```
Repository: vscode
Issue: VSCode opens the wrong folder in Windows 10 start menu when there are folders with the same name
Labels: bug,workbench-history


Issue Type: <b>Bug</b>

1. Make a folder "foo"
2. Make a subfolder "baz" in "foo" 
3. Make a folder "bar"
4. Make a subfolder "baz" in "bar"
Example result:
C:/foo/baz
C:/bar/baz
5. Open both folders at least once in VSCode, doesn't matter how
6. Click start button
7. Type/Search for Visual Studio Code
8. Hover over either of "baz" folders in Recent folders and select it, e.g. foo/baz
9. Close VSCode
10. Click start button
11. Type/Search for Visual Studio Code
12. Select the other "baz" folder in Recent folders, e.g. bar/baz
Expectation:
VSCode opens in C:/bar/baz
Result:
VSCode opens in C:/foo/bar

VS Code version: Code 1.62.3 (ccbaa2d27e38e5afa3e5c21c1c7bef4657064247, 2021-11-17T08:11:14.551Z)
OS version: Windows_NT x64 10.0.19042
Restricted Mode: No


![1](https://user-images.githubusercontent.com/9010650/142830118-d4957ca3-5490-4e6f-90a1-a89d558db751.png)
![2](https://user-images.githubusercontent.com/9010650/142830121-f46cbc23-6332-49c4-a71f-1b054e427a66.png)
![3](https://user-images.githubusercontent.com/9010650/142830127-1f9e0cfd-10de-4120-bba3-bf06470b5dd5.png)

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-4710MQ CPU @ 2.50GHz (8 x 2494)|
|GPU Status|2d_canvas: enabled<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>oop_rasterization: enabled<br>opengl: enabled_on<br>rasterization: enabled<br>skia_renderer: enabled_on<br>video_decode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled|
|Load (avg)|undefined|
|Memory (System)|15.88GB (8.23GB free)|
|Process Argv|--folder-uri file:///d%3A/code/aju/packages/backend --crash-reporter-id a0e1567b-90ab-458b-993b-15785338dad6|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (3)</summary>

Extension|Author (truncated)|Version
---|---|---
go|gol|0.29.0
rest-client|hum|0.24.5
ReactSnippets|xab|2.4.0


</details><details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
pythontb:30283811
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30384386
pythondataviewer:30285071
vscod805:30301674
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
dockerwalkthru:30377721
bridge0723:30353136
pythonrunftest32:30373476
pythonf5test824:30373475
javagetstartedt:30391933
pythonvspyt187:30373474
vsqsis200cf:30402084
vsaa593cf:30376535
vssld246:30401890

```

</details>

<!-- generated by issue reporter -->
Repository: storybook
Issue: Context added in decorator becomes two instances
Labels: question / support,needs triage

**Describe the bug**
Currently, we are running a monorepo setup with react and typescript, where we have the following file structure:
```
.storybook
apps
  - app-which-uses-ui-components
  - app-which-doesnt-use-ui-component
packages
  - ui-components
  - package-which-uses-ui-components
  - package-which-doesnt-use-ui-component
```

Almost all our packages/apps use our `ui-components`-package and those who don't don't suffer if they are wrapped in our global `ThemeProvider` (which is exposed by the `ui-components` package).

This is how our setup looks:
`preview.js`
```js
import {
  GlobalStyle,
  Fonts,
  RootThemeProvider,
} from "../packages/ui-components";

export const decorators = [
  (Story) => (
    <RootThemeProvider>
      <Fonts />
      <GlobalStyle />
      <Story />
    </RootThemeProvider>
  ),
];
```

Everything works fine and we are able to easily create a story in each app/package, except for some of the stories defined in the `ui-components`-package itself. Some of these stories are using help-functionality provided by a context which is rendered in `RootThemeProvider`. 

I've made some investigations, and it seems as when `preview.js` imports `RootThemeProvider` it gets a pre-compiled version from the `dist`-folder of that package, but when the story tries to consume the context it will try to find the context created by the compilation that storybook does (which doesn't exist in the component tree).

So a little bit of a complex case, but is my use case supported? Or should I try to move the responsibility of the decorators closer to the story definition? A drawback with that is that I need to define that decorator in every story which would be a hassle. I would really want to just be able to create a story without knowing the implementation details regarding the whole storybook-setup
Repository: youtube-dl
Issue: Support for Stripchat.com Livestreams
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 2021.06.06. 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 **2021.06.06**
- [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 Livestream: https://stripchat.com/AmiliYan
- Single Livestream: https://stripchat.com/RedAssHottie

## Description

<!--
Provide any additional information.
If work on your issue requires account credentials please provide them or explain how one can obtain them.
-->

Majority of the livestreams are free, without an account, to watch.
Repository: node
Issue: Infinite loop in node_mksnapshot
Labels: build,snapshot,riscv64

### Version

16.13.0

### Platform

riscv64

### Subsystem

v8

### What steps will reproduce the bug?

https://build.opensuse.org/package/live_build_log/openSUSE:Factory:RISCV/nodejs16/standard/riscv64

LD_LIBRARY_PATH=/home/abuild/rpmbuild/BUILD/node-v16.13.0/out/Release/lib.host:/home/abuild/rpmbuild/BUILD/node-v16.13.0/out/Release/lib.target:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH; cd ../.; mkdir -p /home/abuild/rpmbuild/BUILD/node-v16.13.0/out/Release/obj/gen; "/home/abuild/rpmbuild/BUILD/node-v16.13.0/out/Release/node_mksnapshot" "/home/abuild/rpmbuild/BUILD/node-v16.13.0/out/Release/obj/gen/node_snapshot.cc"

### How often does it reproduce? Is there a required condition?

_No response_

### What is the expected behavior?

_No response_

### What do you see instead?

_No response_

### Additional information

_No response_