sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Unable to cross-compile to Linux arm platforms (oidn and embree are incompatible)
Labels: bug,platform:linuxbsd,topic:buildsystem

**Godot version:**
3.3


**OS/device including version:**
openSUSE Tumbleweed


**Issue description:**
I am unable to build godot 3.3 on Arm (aarch64, armv7 and armv6) becauseof:
```
[ 4474s] g++ -o thirdparty/oidn/core/device.x11.opt.tools.64.o -c -std=gnu++14 -w -g2 -O2 -mbranch-protection=standard -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -flto=auto -g -flto -pipe -Wall -Wno-misleading-indentation -Wshadow-local -Werror=return-type -w -DDEBUG_ENABLED -DSERVER_ENABLED -DUNIX_ENABLED -DPTRCALL_ENABLED -DTOOLS_ENABLED -DGDSCRIPT_ENABLED -DMINIZIP_ENABLED -DMODULE_BMP_ENABLED -DMODULE_BULLET_ENABLED -DMODULE_CSG_ENABLED -DMODULE_CVTT_ENABLED -DMODULE_DDS_ENABLED -DMODULE_DENOISE_ENABLED -DMKLDNN_THR=MKLDNN_THR_SEQ -DOIDN_STATIC_LIB -D__STDC_CONSTANT_MACROS -D__STDC_LIMIT_MACROS -DDISABLE_VERBOSE -DMKLDNN_ENABLE_CONCURRENT_EXEC -DNDEBUG -Ithirdparty/oidn -Ithirdparty/oidn/include -Ithirdparty/oidn/mkl-dnn/include -Ithirdparty/oidn/mkl-dnn/src -Ithirdparty/oidn/mkl-dnn/src/common -Ithirdparty/oidn/mkl-dnn/src/cpu/xbyak -Ithirdparty/oidn/mkl-dnn/src/cpu -Iplatform/server -I/usr/include/miniupnpc -I. -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/bullet -I/usr/include/opus thirdparty/oidn/core/device.cpp
[ 4474s] In file included from thirdparty/oidn/core/common.h:19,
[ 4474s]                  from thirdparty/oidn/core/device.h:19,
[ 4474s]                  from thirdparty/oidn/core/device.cpp:17:
[ 4474s] thirdparty/oidn/common/platform.h:27:10: fatal error: xmmintrin.h: No such file or directory
[ 4474s]    27 | #include <xmmintrin.h>
[ 4474s]       |          ^~~~~~~~~~~~~
[ 4474s] compilation terminated.
[ 4474s] scons: *** [thirdparty/oidn/core/device.x11.opt.tools.64.o] Error 1
[ 4474s] In file included from thirdparty/oidn/core/common.h:19,
[ 4474s]                  from thirdparty/oidn/core/device.h:19,
[ 4474s]                  from thirdparty/oidn/core/api.cpp:48:
[ 4474s] thirdparty/oidn/common/platform.h:27:10: fatal error: xmmintrin.h: No such file or directory
[ 4474s]    27 | #include <xmmintrin.h>
[ 4474s]       |          ^~~~~~~~~~~~~
[ 4474s] compilation terminated.
[ 4474s] scons: *** [thirdparty/oidn/core/api.x11.opt.tools.64.o] Error 1
[ 4478s] scons: building terminated because of errors.
```
`oidn`  is likely too old. A fix is available upstream: https://github.com/OpenImageDenoise/oidn/commit/1439239a3c9a0fb77bd0feda3ea60a3008b808dd

**Steps to reproduce:**
Try to build on Arm.

**Minimal reproduction project:**
N/A
Repository: rust
Issue: Rustdoc omits source line numbers in diagnostics if they originate in a macro
Labels: A-diagnostics,A-macros,T-compiler,C-bug,A-intra-doc-links

I tried this code:

https://github.com/rust-lang/rust/blob/9d170be94454340e212e186413d1cf738cfef7c7/compiler/rustc_session/src/options.rs#L97-L104

I expected to see this happen: Rustdoc shows the line number of the broken link, like it does normally:

```
warning: unresolved link to `x`
 --> src/lib.rs:1:6
  |
1 | //! [x]
  |      ^ no item named `x` in scope
  |
  = note: `#[warn(rustdoc::broken_intra_doc_links)]` on by default
  = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]`
```

Instead, this happened:

```
 Documenting rustc_session v0.0.0 (/checkout/compiler/rustc_session)
error: unresolved link to `TRACKED`
   --> compiler/rustc_session/src/options.rs:61:12
    |
61  |           $( #[$top_level_attr] )*
...
...
97  | / top_level_options!(
99  | |     ///
99  | |     ///
100 | |     /// For each option, one has to specify how it behaves with regard to the
201 | |     }
202 | | );
    | |__- in this macro invocation
    |
    |
    = note: `-D rustdoc::broken-intra-doc-links` implied by `-D warnings`
    = note: the link appears in this line:
            
            [TRACKED]
             ^^^^^^^
    = note: no item named `TRACKED` in scope
    = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]`
```

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:

_Originally posted by @rust-log-analyzer in https://github.com/rust-lang/rust/issues/84233#issuecomment-829178727_
Repository: vscode
Issue: When touching the button on touch screan, The terminal pannel show new terminal with flashing drop-down menu .
Labels: bug,confirmed,touch/pointer,terminal-tabs

<!-- ⚠️⚠️ 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. -->
- VS Code Version: 1.56.0 , main branch
- OS Version: Windows 10 20H2
- Device: Surface Laptop 3

Steps to Reproduce:

1. When touching the button on touch screan, The terminal pannel  show  new terminal with  flashing  drop-down menu . 

![bug](https://user-images.githubusercontent.com/76699099/116551144-3225f100-a92a-11eb-86de-38c901f08714.gif)



<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: No

<!-- 🪓 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. -->
Repository: vscode
Issue: [folding] region ranges not restored when editor is opened the first time.
Labels: bug,editor-folding

<!-- ⚠️⚠️ 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. -->
I would like it if the editor can remember the folding state of my code so when the file/project is opened the next day, the regions are in the state i left them.
Repository: node
Issue: Http client sometimes returns EPIPE when server does not read request body
Labels: http

* **Version**: v15.12.0
* **Platform**: Darwin Kernel Version 20.3.0

### What steps will reproduce the bug?

``` js
let http = require("http");

let server = http.createServer(async function(req, res)
{
	res.end("ok");
});

(async function()
{
	await new Promise(resolve => server.listen(resolve));
	let buf = Buffer.alloc(50000000);
	for(let i = 0; ; i++)
	{
		let req = http.request({ port: server.address().port, method: "post" }).end(buf);
		let res = await new Promise((resolve, reject) => req.on("response", resolve).on("error", reject));
		let str = "";
		for await (let chunk of res) str += chunk;
		console.log(i, "client received:", str);
	}
}());
```

### How often does it reproduce? Is there a required condition?

Sometimes. It can take a few thousands of iterations or more.

### What is the expected behavior?

No `EPIPE`.

### What do you see instead?

```
85784 client received: ok
node:internal/process/promises:245
          triggerUncaughtException(err, true /* fromPromise */);
          ^

Error: write EPIPE
    at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:94:16) {
  errno: -32,
  code: 'EPIPE',
  syscall: 'write'
}
```

### Additional information

It does not happen on linux (after more than million iterations).
Repository: rust
Issue: Intereleaved text in "cargo test" output
Labels: A-libtest

**Problem**

The following image is two screenshots, side by side, of the output of "cargo test" from two test runs seconds apart with the same code.  As you can see, there seems to be a race (or race-like behavior) causing text written to the stdout buffer to be interleaved together.

This is exclusive to when `--nocapture` is specified.  I cannot reproduce if `--nocapture` is not specified.

![Screenshot from 2021-04-29 00-35-07](https://user-images.githubusercontent.com/2751996/116503142-5e3a6700-a883-11eb-89d4-3082ef0a9f86.png)

Usually it works "correctly" but I can I can do this over and over and continue getting different versions of incorrectly printed output each time.

![Screenshot from 2021-04-29 00-42-25](https://user-images.githubusercontent.com/2751996/116503475-2f70c080-a884-11eb-9df2-085fb60d7cec.png)

Another one

![Screenshot from 2021-04-29 00-48-33](https://user-images.githubusercontent.com/2751996/116503700-bf166f00-a884-11eb-85a0-d29431bf6448.png)


**Notes**

Output of `cargo version`:

cargo 1.53.0-nightly (0ed318d18 2021-04-23)
rustc 1.53.0-nightly (42816d61e 2021-04-24)
Repository: flutter
Issue: Avoid version locking non-SDK packages in Flutter SDK
Labels: framework,P2,team-framework,triaged-framework

In general, we want existing projects to work in newer versions of Flutter (modulo deliberate breaking changes). However, whenever we have an SDK dependency on a package that's not part of the SDK, we create a situation where any project with any transitive dependencies on any of those projects cannot build with the new version of Flutter until all of the dependencies involved have updated. See https://github.com/flutter/flutter/issues/77491 for an example, but it's a general problem.

To the extent possible, we should avoid using external packages, or if at all possible use version ranges instead of specific ranges when we do. We should likely have specific policies about this the way we do for other breaking changes, as in practice updating a pinned version is a breaking change.

(NNBD was a particularly severe instance of this probleme because in practice most packages updated their deps as part of the same change where they did their NNBD migration, meaning it was itself a breaking version change, and so in many cases *all* transitive dependencies in the chain to, e.g., `intl` had to be updated, rather than just the ones that directly included `intl`.)

/cc @Hixie
Repository: pytorch
Issue: Attributes consistency in Sampler and DistributedSampler
Labels: oncall: distributed,triaged

## 🚀 Feature
<!-- A clear and concise description of the feature proposal -->

## Motivation

In [sampler.py](https://github.com/pytorch/pytorch/blob/master/torch/utils/data/sampler.py), the `dataset` attribute is named as `data_source`, while in [distributed.py](https://github.com/pytorch/pytorch/blob/master/torch/utils/data/distributed.py), the `dataset` attribute is named as `dataset`. 

This inconsistency is causing troubles, e.g. when using custom batch sampler, I have to determine if I should call `data_source` or `dataset`.

<!-- 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 -->

## Pitch

Make `data_source` `dataset`.

<!-- A clear and concise description of what you want to happen. -->

## Alternatives

Make `dataset` `data_source`.

<!-- A clear and concise description of any alternative solutions or features you've considered, if any. -->

## Additional context

<!-- Add any other context or screenshots about the feature request here. -->


cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @agolynski @SciPioneer @H-Huang @mrzzd @cbalioglu @gcramer23
Repository: flutter
Issue: Semantics checked attribute breaks scroll behavior
Labels: framework,f: material design,a: accessibility,f: scrolling,has reproducible steps,P2,found in release: 2.3,team-design,triaged-design

When wrapping a widget in a `Semantics` widget and setting the `checked` attribute, the scroll behavior changes while using VoiceOver. With the `checked` attribute set, VoiceOver continues to navigate and announce items; however, the `ListView` does not scroll to the item in focus. This has the additional side effect of preventing the item from being tapped.


To reproduce:
```dart
import 'package:flutter/material.dart';

main() => runApp(MyApp());

class MyApp extends StatefulWidget {
  @override
  MyAppState createState() => MyAppState();
}

class MyAppState extends State<MyApp> with WidgetsBindingObserver {
  @override
  Widget build(context) => MaterialApp(title: 'Semantics bug demo app', home: HomePage());
}

class HomePage extends StatelessWidget {
  @override
  Widget build(context) => Scaffold(
        body: ListView(
          children: [
            ...List.generate(
              25,
              (index) => Row(
                children: [
                  Semantics(
                    checked: true,
                    child: Icon(Icons.help_rounded, semanticLabel: "Test $index", size: 100),
                  ),
                ],
              ),
            ),
          ],
        ),
      );
}

```

I would also note that this issue is not present when using `selected`. Expected behavior for `checked` would match that of `selected`

I have not tested Android.
Repository: godot
Issue: Make Godot Physics 3D constraint solving more deterministic
Labels: enhancement,topic:physics,topic:3d

**Godot version:**
Master

**OS/device including version:**
n/a

**Issue description:**
PR #44112 has improved determinism for constraint solving in Godot Physics 2D.
A similar patch needs to be applied to Godot Physics 3D to make things consistent.

*Note:* Performance needs to be investigated too, as it seems this patch causes some slow down in physics steps in some cases.

**Steps to reproduce:**
n/a

**Minimal reproduction project:**
n/a
Repository: next.js
Issue: `require.context(...).keys()` fails when Webpack 5 is used
Labels: bug,Webpack

### What version of Next.js are you using?

10.2.0

### What version of Node.js are you using?

16.0.0

### What browser are you using?

n/a

### What operating system are you using?

macOS 11.3

### How are you deploying your application?

`next build` and `next start`

### Describe the Bug

Using `require.context(...).keys()` fails when Webpack 5 is used.

It works as expected with Webpack 4, and it works when `.keys()` is not appended.

### Expected Behavior

An error is not thrown when `require.context(...).keys()` is used.

### To Reproduce

1. Clone https://github.com/davidbailey00/nextjs-require-context-bug
2. Run the command: `npm run build` and observe that an error occurs

   To confirm that the issue does not occur when using Webpack 4:

3. Disable Webpack 5 support in `next.config.js` and rerun `npm run build`
Repository: go
Issue: crypto/x509: add a PKITS test
Labels: Testing,help wanted,NeedsFix

PKITS is a large X.509 test suite. Some of the stuff in there we don't actually support, but it would be good to run through it all and explicitly mark the things we don't support.
Repository: excalidraw
Issue: Groups are exited when doing a drag selection
Labels: discussion,UX/UI

As suggested by @vjeux on Twitter I'm opening this issue.

After double clicking to edit a group and doing a drag selection, the group is exited and we're back to the "root level".

See this video:

https://youtu.be/tGzseJQdolw
Repository: neovim
Issue: support different highlight rules for different levels of Folded
Labels: enhancement

Afaik in neovim (as with vim) the only target to style folded segments of code is the [Folded](https://vimhelp.org/syntax.txt.html#hl-Folded) group name. I've found it useful in certain applications to color code nested folds to better track their hierarchy. To do so one would need to define highlight groups based on the [level of fold](https://github.com/neovim/neovim/blob/fbe18d9ca41a419414cb112d0a426aa8803c6236/src/nvim/fold.h#L17), e.g. `Folded1`, `Folded2`, etc. (or some better naming scheme).

I'm happy to work on this, but totally new to the neovim codebase. Please let me know if folks like this idea and/or think this is feasible.
Repository: godot
Issue: If a Viewport inside a ViewportContainer is present in the scene, mouse cursor flickers over any LineEdit
Labels: bug,topic:rendering,confirmed,topic:gui

<!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->

**Godot version:**
3.3 and 3.2.3 stable


**OS/device including version:**
Windows 10, Nvidia 940GT, GLES2 and GLES3


**Issue description:**
If there is any Viewport inside a VIewpotContainer in a scene, mouse caret changes from Arrow to Ibeam on move over LineEdits every frame. This behavior maybe too specific, but the report might help when dealing with related issues.
Possible related issues:
https://github.com/godotengine/godot/issues/23729
https://github.com/godotengine/godot/issues/38633


**Steps to reproduce:**
- Create a ViewportContainer and a Viewport
- Create a LineEdit anywhere on the same scene
- Hover over LineEdit - cursor flickers (repeatedly changes from Arrow to Ibeam)

**Minimal reproduction project:**
<!-- A small Godot project which reproduces the issue. Drag and drop a zip archive to upload it. -->
[GodotTest2.zip](https://github.com/godotengine/godot/files/6401543/GodotTest2.zip)
Repository: TypeScript
Issue: TypeScript: JSDoc tooltips are shared between types and values, but not functions
Labels: Suggestion,Experience Enhancement

*TS Template added by @mjbvz*

**TypeScript Version**: 4.2.4

**Search Terms**
- quickinfo
- jsdoc

---

Issue Type: <b>Bug</b>

## Steps to reproduce

- Create a TypeScript file.
- Create a type alias with some name, and write a JSDoc comment for it.
- For types and functions:
    - Create a function with the same name, write a different JSDoc comment.
    - Hover over the type name. You will see the function’s comment, followed by the type’s comment.
    - Hover over the function. You will only see the function’s comment.
- For types and values:
    - Create a value identifier with the same name, write a different JSDoc comment.
    - Hover over the type name. You will see the type’s comment, followed by the value’s comment.
    - Hover over the value identifier. You will see the type’s comment, followed by the value’s comment.

## Reference file

```ts
/** A */
type X = null
/** B */
let X = null
/** C */
type Y = null
/** D */
function Y() {}
```

### Screenshots

![vscode-jsdoc-issue-type-x](https://user-images.githubusercontent.com/48802534/116614882-cbf59a00-a93a-11eb-82fa-41ad26071870.png)
![vscode-jsdoc-issue-let-x](https://user-images.githubusercontent.com/48802534/116614883-cc8e3080-a93a-11eb-8e90-667fa4042c74.png)
![vscode-jsdoc-issue-type-y](https://user-images.githubusercontent.com/48802534/116614880-cb5d0380-a93a-11eb-9f4e-9ec49dc8134c.png)
![vscode-jsdoc-issue-function-y](https://user-images.githubusercontent.com/48802534/116614887-cd26c700-a93a-11eb-944c-5c26c096ac59.png)

## System and version info

VS Code version: Code - Insiders 1.56.0-insider (0123d26aaa393bccf99f31f1eac07df6c9e218ce, 2021-04-29T05:12:38.091Z)
OS version: Linux x64 5.11.0-7614-generic

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i5-8300H CPU @ 2.30GHz (8 x 2300)|
|GPU Status|2d_canvas: enabled<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>oop_rasterization: disabled_off<br>opengl: enabled_on<br>rasterization: disabled_software<br>skia_renderer: enabled_on<br>video_decode: disabled_software<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled|
|Load (avg)|2, 2, 2|
|Memory (System)|7.64GB (0.18GB free)|
|Process Argv|--no-sandbox --unity-launch --crash-reporter-id dbbd25fe-3f4e-426a-9c89-45e060834124|
|Screen Reader|no|
|VM|0%|
|DESKTOP_SESSION|pop|
|XDG_CURRENT_DESKTOP|Unity|
|XDG_SESSION_DESKTOP|pop|
|XDG_SESSION_TYPE|x11|
</details>  
Extensions: none
<!-- generated by issue reporter -->
Repository: pytorch
Issue: Avoid code repeat in create sample inputs for sort/msort
Labels: module: tests,triaged,module: sorting and selection

_Originally posted by @albanD in https://github.com/pytorch/pytorch/pull/57192#r623359871_

cc @mruberry @VitalyFedyunin @walterddr @heitorschueroff
Repository: flutter
Issue: [Animation] package - Ability to dismiss(pop) Open Container and other transitions along with user finger
Labels: c: new feature,a: animation,package,c: proposal,p: animations,team-ecosystem,P3,triaged-ecosystem

Right now we can pop the detail page by pressing on a back button or something similar.
It would be much more useful if we can swipe down and control the reverse animation with our finger movement. If the finger is released, we can check if it is past  a certain threshold and according to the result we can pop or rollback the animation. 

I am talking about a standard Instagram Story like dismiss transition.
Repository: PowerToys
Issue: "Windows cannot find '[...]/windowsdesktop-runtime.exe'" error when running installer
Labels: Area-Setup/Install,Needs-Repro

### Microsoft PowerToys version

0.35.0

### Running as admin

- [x] Yes

### Area(s) with issue?

Installer

### Steps to reproduce

Install PowerToys. Say "Yes" or "OK" to any errors that come up.

### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

1. .NET Core downloads (progress bar is full the whole time)
2. "Windows cannot find 'C:\Users\waldo\AppData\Local\Temp\windowsdesktop-runtime.exe'. Make sure you typed the name correctly, and then try again."
![image](https://user-images.githubusercontent.com/56197853/116616033-6efae380-a93c-11eb-961b-c92462d08491.png)
3. "Couldn't install .NET Core."
![image](https://user-images.githubusercontent.com/56197853/116616273-d153e400-a93c-11eb-972c-e31eb178abfd.png)
4. Installation wizard continues normally, PowerToys installs successfully.
5. Running PowerToys: 3 errors
![image](https://user-images.githubusercontent.com/56197853/116616825-6b1b9100-a93d-11eb-839f-d9879f52b564.png)
6. [.NET Core 3.1](https://dotnet.microsoft.com/download/dotnet/3.1/runtime/?utm_source=getdotnetcore&utm_medium=referral) installs fine, PowerToys works properly.

### Other Software

_No response_