sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: [Godot Physics] Box-Cylinder collision issues with move_and_slide()
Labels: bug,topic:physics

**Godot version:**
3.3.rc.custom_build.dae319355

**OS/device including version:**
N/A

**Issue description:**

Box-cylinder collisions behave erratically with move_and_slide()

**Steps to reproduce:**

* Use `move_and_slide()` with a box collision shape to walk over a cylinder collision shape.


https://user-images.githubusercontent.com/79001820/111470464-9c684500-8773-11eb-8ec3-72e684b51935.mp4

Seems to work fine when walking across the top of a slanted cylinder

**Minimal reproduction project:**

MRP: https://github.com/godotengine/godot/files/6175149/cylinder-collision-bug.zip (press z to toggle collision shape)
Also for further testing: https://github.com/e344fde6bf/godot-physics-sandbox
Repository: godot
Issue: [Godot Physics] ConvexPolygonShape-Cylinder collision issues with move_and_slide()
Labels: bug,topic:physics

**Godot version:**
3.3.rc.custom_build.dae319355

**OS/device including version:**
N/A

**Issue description:**

ConvexPolygonShape-Cylinder collisions behave erratically with move_and_slide()

**Steps to reproduce:**

* Use `move_and_slide()` with a ConvexPolygonShape collision shape to walk over a cylinder collision shape.


https://user-images.githubusercontent.com/79001820/111471551-bc4c3880-8774-11eb-8769-ccbc4ecb5eeb.mp4

**Minimal reproduction project:**
MRP: https://github.com/godotengine/godot/files/6175149/cylinder-collision-bug.zip (press z to toggle collision shape)
Also for further testing: https://github.com/e344fde6bf/godot-physics-sandbox
Repository: PowerToys
Issue: Navigate Windows Using PowerToys Run.
Labels: Idea-Enhancement,Product-PowerToys Run,Run-Plugin

Want to navigate and preview directories using just power toys run?

Right now I can use  `~`  to start looking for folders, and once in a folder I can use arrow keys to find a subfolder or a file. While hovering a subfolder I can type `\` and it shows me the files and folders in that folder. To navigate backwards, I have to erase the last directory in the path.

This can be optimized using `Tab` and `Shift + Tab` (or other intuitive shortcuts) to move forwards and backwards through the directories, thereby enabling users to quickly navigate their directories and find open files without open an explorer window, or lifting their hands off the keyboard!


https://user-images.githubusercontent.com/26184016/111481735-44244980-8759-11eb-90c9-2987c83e92ed.mp4
Repository: pytorch
Issue: Implement Truly Parallel Ensemble Layers
Labels: feature,module: nn,triaged,module: batching

## 🚀 Feature
Implement a parallel ensemble layer that allows parallelized forward and backward passes through an ensemble of MLPs, as opposed to using a for-loop over individual networks.

## Motivation
Ensembling fully connected networks is still a popular approach to improving generalization; for instance it is commonly used in many state-of-the-art RL algorithms, such as [here](https://papers.nips.cc/paper/2018/hash/3de568f8597b94bda53149c7d7f5958c-Abstract.html), [here](https://arxiv.org/abs/2005.05951), [here](https://arxiv.org/abs/1812.05905), and [here](https://openreview.net/forum?id=AY8zfZm0tDd). Furthermore, ensembling + aleotoric uncertainty estimates are [well-calibrated on out-of-distribution data](https://proceedings.neurips.cc/paper/2019/hash/8558cb408c1d76621371888657d2eb1d-Abstract.html).

At the moment, the most obvious way to implement these networks is to wrap individual networks into a list, and then for-loop over them to get the ensemble prediction. However this is slow, and instead it should be possible to pass a datapoint simultaneously through the entire ensemble. I've implemented a preliminary approach using `torch.baddbmm` and the speedups can be very considerable:
Relative Speedup             |  Direct Comparison
:-------------------------:|:-------------------------:
<img src="https://user-images.githubusercontent.com/15997485/111479874-4d95bd80-8729-11eb-9f12-127968af0c2d.png" alt="drawing" width="300"/>  |  <img src="https://user-images.githubusercontent.com/15997485/111479904-54bccb80-8729-11eb-87d8-f0f74eacbc49.png" alt="drawing" width="300"/>

The results above are for a simple 3 hidden layer MLP with 256 width units trained on MNIST for 1 epoch, with training done on an RTX 2080 Ti.


## Pitch

I propose to implement a parallel ensemble layer.

## Alternatives

Apart from the aforementioned for-loop, it might be possible to do something with grouped convolutional operations, but I've really not looked at this too deeply, i.e., [here](https://stackoverflow.com/questions/58374980/run-multiple-models-of-an-ensemble-in-parallel-with-pytorch/58389075#58389075).

## Additional context

I'm not hugely experienced in OSS development, and already forsee some issues that someone more experienced than me could help out on. For instance, existing operations, such as loss functions and layer initializations wouldn't work natively with my naive implementation; in the above example I wrote custom functions to handle the ensemble cases.

In terms of performance, the two are comparable, and seem reasonable for 1 epoch of MNIST training:
<img src="https://user-images.githubusercontent.com/15997485/111481944-5a1b1580-872b-11eb-8ee9-5d854eb49db1.png" alt="drawing" width="300"/>

cc @albanD @mruberry @jbschlosser
Repository: flutter
Issue: [Linux] keyboard stops working after using some backspacing
Labels: a: text input,e: device-specific,engine,platform-linux,a: desktop,P2,team-linux,triaged-linux

Opening this issue to track the problem of keyboard not working on linux after using backspace a few times as asked by @dkwingsmt in https://github.com/flutter/flutter/issues/44918#issuecomment-800822902...

> At the moment, I only know that the keyboard works and then stops working after using backspace a few times (only backspace keeps working) and that it occurs on Linux (I can only test on Linux and Windows)... The only way to get the keyboard to work is closing and opening the app again...

https://user-images.githubusercontent.com/17789155/111481683-f7695000-8711-11eb-8c01-cae2817e7bfd.mp4

On the above video, at 0:10 the keyboard has stopped already... The video was made on Ubuntu 20.04 in a laptop, but I have successfully reproduced the issue on Fedora 33/34 on a VM too...
Repository: flutter
Issue: [web] Standardized way to preload emoji font using CanvasKit
Labels: c: new feature,engine,a: quality,platform-web,c: proposal,e: web_canvaskit,P2,team-web,triaged-web

## Use case

When using CanvasKit and trying to display emojis, issue https://github.com/flutter/flutter/issues/76248 arises, i.e. "Emojis take a few seconds to render on canvaskit".

This means that when first displaying emojis, **tofu** boxes appear for a few seconds.

## Proposal

It would be great to have an exposed function that allows loading the Noto font **on app start**, so that when the first emojis are displayed, the Noto font is already preloaded.

## Workaround

The way we solve this currently is the following:

```dart
@override
Widget build(BuildContext build) {
  return Stack(
    children: [
      // w/e
      const Opacity(
        opacity: 0,
        // Insert invisible emoji in order to load the emoji font in CanvasKit
        // on startup. Note that this is a *workaround solution* - we want to
        // find a better one :)
        child: Text('✨'),
      ),
    ],
  );
}
```

This is inserted on startup. As soon as we actually display emojis, the Noto font has already been downloaded. However, this really feels like a hack.
Repository: pytorch
Issue: OSS build doesn't hard fail on nodiscard
Labels: triaged,module: build warnings,better-engineering

Our codebase is nodiscard clean because we have internal builds that hard error on it, but it seems in open source we don't hard error on nodiscard errors. It would be helpful if people's regular builds Werror'ed on this as it is almost always an error.
Repository: rust
Issue: Improve attribute list syntax suggestion
Labels: A-diagnostics,A-parser,T-compiler

<!--
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: <!-- Please provide a link to play.rust-lang.org -->

```rust
#[doc(alias = ["foo"])]
fn t() {}
```

The current output is:

```
   Compiling playground v0.0.1 (/playground)
error: expected unsuffixed literal or identifier, found `[`
 --> src/lib.rs:1:15
  |
1 | #[doc(alias = ["foo"])]
  |               ^

error: aborting due to previous error

error: could not compile `playground`
```

<!-- The following is not always necessary. -->
Ideally the output should look like:

```
   Compiling playground v0.0.1 (/playground)
error: expected unsuffixed literal or identifier, found `[`
 --> src/lib.rs:1:15
  |
1 | #[doc(alias("foo"))]
  |               ^

error: aborting due to previous error
help: list syntax is not supported for `alias` attribute
suggestion: use `alias("foo")` instead of `alias = ["foo"]`

error: could not compile `playground`
```


https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=dcc601d35deecf1558b3dd66660bf8d5

Follow up of https://github.com/rust-lang/rust/pull/82846
<!--
If the problem is not self-explanatory, please provide a rationale for the
change.
-->

<!--
If dramatically different output is caused by small changes, consider also
adding them here.

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. The output might also be
different depending on the Edition.
-->
Repository: vscode
Issue: Git - nothing to commit when replace file by symlink 
Labels: bug,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. -->
- VS Code Version: 1.54.3
- OS Version: Ubuntu 18.04

Steps to Reproduce:

1. in a git repo create a file.txt
2. cp file.txt copy.txt
3. commit these two identical files
4. replace copy.txt by a symlink to file.txt (rm copy.txt && ln -s file.txt copy.txt)
5. vscode do not see anything to commit
6. git status does not report the same thing

i suppose this is a bug ?

<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes/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 direct to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
Repository: create-react-app
Issue: Using ES version of library (node_module) is not working
Labels: needs triage,issue: bug report

### Describe the bug

Webpack throws an error when I change my code to use "es" version of libraries

### Environment

![image](https://user-images.githubusercontent.com/15635777/111489199-f0692e80-875f-11eb-9503-725f78b0b9df.png)

### Steps to reproduce

1. Add `@material-ui/core` to your project
2. Use any "es" variant of the code from that library. This particular code uses optional chaining in es version of the code
```js
import TextField from "@material-ui/core/es/TextField";
```
3. Webpack dev `yarn start` or Webpack build `yarn build` both fails with the following error
![image](https://user-images.githubusercontent.com/15635777/111490680-383c8580-8761-11eb-98d6-a361b7e31996.png)



### The fix

* So after digging throught the issue, I have found out that this is happening due to Optional Chaining and Nullish Coalescing not supported in the JS parser `acorn v6.x.x` which is what Webpack 4 uses. [Issue details here](https://github.com/webpack/webpack/issues/10227)
* And on my computer, I edited the webpack config in node_modules and added the two presets to the last module `rules` which processes JS outside of `src`.
![image](https://user-images.githubusercontent.com/15635777/111491313-c4e74380-8761-11eb-9a41-22c616f5bcfc.png)
* This has fixed the issue

---

**If this usecase is generic enough, Can I raise a pull request to make these changes??**

If not, I can use something like `react-app-rewired` to edit it for our usecase. Also this change will be temporary until we move to Webpack 5.
Repository: nvm
Issue: [actions] : Test-Suite action workflow
Labels: testing

Migrating the test-suite which is currently on travis to github actions.

Additional context: 
Build configuration for travis: https://travis-ci.com/github/nvm-sh/nvm/builds/220257244/config
Repository: go
Issue: io/fs: should fs.Sub(fsys, "no such directory") return a file system that fails fstest.TestFS?
Labels: NeedsDecision

<!--
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 freebsd/amd64
</pre>

### Does this issue reproduce with the latest release?

If you mean latest released Go, then yes.
If you mean `tip`, I'm not sure, but I expect so.

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
[output trimmed]
GO111MODULE=""
GOARCH="amd64"
GOHOSTARCH="amd64"
GOHOSTOS="freebsd"
GOOS="freebsd"
GOVERSION="go1.16.2"
CGO_ENABLED="1"
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->
<pre>
    fs, err := fs.Sub(someFS, "noSuchDir")
    err = fstest.TestFS(fs)
</pre>

https://play.golang.org/p/eXsqSUYHWQs

### What did you expect to see?

No error returned.

### What did you see instead?

It fails due to lack of an empty root directory:
<pre>
    prog.go:18: TestFS found errors:
        .: Open: open .: file does not exist
</pre>

This may very well be a "works as intended" issue, and if so I apologise for the noise.

FYI: I ran into this while experimenting with implementing the opposite of `fs.Sub`, a `Prefix(fs.FS, string) (fs.FS, error)`.
I provided a `prefixFS.Sub` as an optimisation where it returns another `prefixFS` with the prefix adjusted or calls `fs.Sub` on it's underlying file system to avoid chaining multiple wrappers. I ended up also implementing an [`EmptyFS`](https://play.golang.org/p/Zdq2JIeHWHx) that I return when the sub-dir isn't within my prefix in order to keep `fstest.TestFS` happy.

I imagine others implementing `fs.SubFS` and trying to test their code would appreciate not having to make their own `EmptyFS` just to satisfy `fstest.TestFS`. Perhaps an empty file system implementation could be provided or `fstest` could be tweaked with respect to what it accepts as a completely emtpy file system.
Repository: tensorflow
Issue: Incompatibility between `set_visible_devices()` and `from_dlpack()`
Labels: stat:awaiting tensorflower,type:bug,comp:gpu,TF 2.4

**System information**
- Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes
- OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 20.10
- TensorFlow installed from (source or binary): binary
- TensorFlow version (use command below): v2.4.0-49-g85c8b2a817f 2.4.1
- Python version: 3.8.8
- CUDA/cuDNN version: 11.2
- GPU model and memory: GTX 1080Ti 11GB

**Describe the current behavior**

After selecting which GPU to use via `tf.config.experimental.set_visible_devices()`, converting external arrays from dlpack with `tf.experimental.dlpack.from_dlpack()` only works for device 0. Using other devices results in the error `InvalidArgumentError: GPU:1 unknown device.`

**Describe the expected behavior**

Converting external arrays from dlpack with `tf.experimental.dlpack.from_dlpack()` should work for all devices.

**Standalone code to reproduce the issue**
```python
import cupy
import random

import tensorflow as tf

# gpu_to_use = 0      # Works
gpu_to_use = 1        # Errors

gpus = tf.config.experimental.list_physical_devices("GPU")
if gpus:
    tf.config.experimental.set_visible_devices(gpus[gpu_to_use], "GPU")

# Converting from TF to CuPy with dlpack works for both devices
tensor = tf.random.uniform((10,))

dltensor = tf.experimental.dlpack.to_dlpack(tensor)
array1 = cupy.fromDlpack(dltensor)

# Converting from CuPy to TF with dlpack only works for device 0
array1 = cupy.array([random.uniform(0.0, 1.0) for i in range(10)], dtype=cupy.float32)
dltensor = array1.toDlpack()
x = tf.experimental.dlpack.from_dlpack(dltensor)

# Using device 1 results in the following error

# Traceback (most recent call last):
#   File "examples/multi-gpu/tf-dlpack-repro.py", line 22, in <module>
#     x = tf.experimental.dlpack.from_dlpack(dltensor)
#   File "/home/karl/miniconda3/envs/nvtabular_dev_11.0/lib/python3.8/site-packages/tensorflow/python/dlpack/dlpack.py", line 66, in from_dlpack
#     return pywrap_tfe.TFE_FromDlpackCapsule(dlcapsule, context.context()._handle)
# tensorflow.python.framework.errors_impl.InvalidArgumentError: GPU:1 unknown device.
```
Repository: PowerToys
Issue: FancyZone Editor toolbar
Labels: Idea-Enhancement,FancyZones-Editor,Product-FancyZones,Priority-1

Shift in how to handle the toolbar

> @niels9001 you think that would be helpful verbiage?

@crutkas @enricogior I think the usability issues in the editor keeps coming back across various issues (especially since it has some non-Windows-standard ways of doing things (e.g. press and hold to select).

Would it make sense to explore a different way of enabling these functions? Here's a toolbar idea what would allow you to switch between different "tools" (e.g. horizontal split tool, vertical split tool, merge tool):

![image](https://user-images.githubusercontent.com/9866362/111451566-da348180-8711-11eb-9a06-5811faea4692.png)

_Originally posted by @niels9001 in https://github.com/microsoft/PowerToys/issues/10230#issuecomment-800962201_
Repository: flutter
Issue: Add a "child" property to the Builder class.
Labels: c: new feature,framework,f: material design,c: proposal,team-design,triaged-design

<!-- Thank you for using Flutter!

     If you are looking for support, please check out our documentation
     or consider asking a question on Stack Overflow:
      * https://flutter.dev/
      * https://api.flutter.dev/
      * https://stackoverflow.com/questions/tagged/flutter?sort=frequent

     If you have found a bug or if our documentation doesn't have an answer
     to what you're looking for, then fill out the template below. Please read
     our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports
-->

## Use case
When using InheritedWidget we often use the `Builder` lower in the widget tree to minimize our build() cost. 

But sometimes we have a big widget inside our Builder which we don't want it to be dependent on the InheritedWidget.


<!--
     Please tell us the problem you are running into that led to you wanting
     a new feature.

     Is your feature request related to a problem? Please give a clear and
     concise description of what the problem is.

     Describe the alternative solutions you've considered. Is there a package
     on pub.dev/flutter that already solves this?
-->



## Proposal
Let the Builder widget take in a child, just like a ValueListenableBuilder.

It's very optimal to use as it can enable us to do what we do with ValueListenableBuilder but instead of Listenables, we use InheritedWidgets.

This is a very simple feature to add. 
Changes to the `Builder` class would look something like this :

```dart
 class Builder extends StatelessWidget {
  /// Creates a widget that delegates its build to a callback.
  ///
  /// The [builder] argument must not be null.
  const Builder({
    Key? key,
    required this.builder,
    this.child, //      <--Add this
  }) : assert(builder != null),
       super(key: key);

  /// doc
  final TransitionBuilder builder; //    <--Change this

  /// doc
  final Widget? child; //     <--Add this

  @override
  Widget build(BuildContext context) => builder(context, child); //     <--Change this
}
```

<!--
     Briefly but precisely describe what you would like Flutter to be able to do.

     Consider attaching images showing what you are imagining.

     Does this have to be provided by Flutter directly, or can it be provided
     by a package on pub.dev/flutter? If so, maybe consider implementing and
     publishing such a package rather than filing a bug.
-->
Repository: excalidraw
Issue: Trying to change stroke color while text is selected hides the text element
Labels: bug,firefox,safari

Double clicking and creating a new text element causes the old one to reappear.

## Demo
![Demo](https://media.giphy.com/media/i0uKPalC3Kg5FwSiJj/giphy.gif)
Repository: flutter
Issue: Bundle asan/tsan/msan runtime into the app bundle when engine is built with those
Labels: platform-android,platform-ios,tool,engine,P2,team-engine,triaged-engine

### For iOS

This requires work on both the engine and the tool side of things.

On the engine side, when `flutter/tools/gn` is run with `--[a,m,t,ub]san` flag set, the produced `Flutter.framework` needs to contain the runtime dylib (e.g, `libclang_rt.asan_ios_dynamic.dylib` for asan).

On the framework side, when building using a local engine we need to check for the sanitizer runtime dylib and then:
1. Code sign it.
2. Bundle it with the app bundle.

https://github.com/flutter/flutter/issues/78076#issuecomment-800671699 has detailed instructions.


### non-iOS platforms

Additional investigation needs to happen to determine the exact steps.
Repository: flutter
Issue: Add asan/msan/tsan support for iOS simulator
Labels: engine,from: sanitizer,P3,team-engine,triaged-engine

See https://github.com/flutter/flutter/issues/78076#issuecomment-800525030 for an attempted run and the failure log.
Repository: flutter
Issue: Convert some of the flutter  e2e driver tests to run on a sanitizer enabled engine build
Labels: engine,P3,team-engine,triaged-engine

This would prevent issues like https://github.com/flutter/flutter/issues/78076 to occur and also would've sped up the debugging process by a lot.
Repository: pytorch
Issue: OSS Mobile Errors Point to fburls
Labels: triaged,enhancement,better-engineering

## 🐛 Bug Error Messages Not Reachable for OSS Users

There are [multiple](https://github.com/pytorch/pytorch/blob/02c0c7a32baa0bb0926a9a96f5fc876af6f20176/aten/src/ATen/core/dispatch/OperatorEntry.cpp#L396) [error](https://github.com/pytorch/pytorch/blob/2c5579702a55757bbe20b3db0152c3f1422aa730/torch/csrc/jit/mobile/import.cpp#L108) [msgs](https://github.com/pytorch/pytorch/blob/02c0c7a32baa0bb0926a9a96f5fc876af6f20176/aten/src/ATen/core/dispatch/OperatorEntry.cpp#L396) in mobile which point the user to an fburl, which obviously OSS users cannot reach.  

At this point we're advertising mobile for OSS users. It would be nice if confidential information was guarded against with `#if def FBCODE` and a similar link with anonymized information published for OSS users.