sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: Inconsistent complex results with NumPy when computing non-positive power of 0
Labels: triaged,module: complex,module: numpy,module: NaNs and Infs

## 🐛 Bug

When calculating non-positive power of complexed 0, the results obtained by PyTorch would inconsistent with NumPy. This phenomenon only occurs with exponent in tensor.

## To Reproduce
```
# Negative exponent
>>> np.array(0j)**np.array(-1)
(nan+nanj)
>>> torch.tensor(0j)**(-1)
tensor(nan+nanj)
>>> torch.tensor(0j)**torch.tensor(-1)
tensor(inf+nanj)

# Zero exponent
>>> np.array(0j)**np.array(0)
(1+0j)
>>> torch.tensor(0j)**(0)
tensor(1.+0.j)
>>> torch.tensor(0j)**torch.tensor(0)
tensor(nan+nanj)
```

## Expected behavior

Consistent complex results with NumPy, like:
```
>>> torch.tensor(0j)**torch.tensor(-1)
tensor(nan+nanj)
>>> torch.tensor(0j)**torch.tensor(0)
tensor(1.+0.j)
```

## Environment

```
Collecting environment information...
PyTorch version: 1.8.0a0+d3b3387
Is debug build: True
CUDA used to build PyTorch: 11.0
ROCM used to build PyTorch: N/A
OS: CentOS Linux 7 (Core) (x86_64)
GCC version: (GCC) 7.5.0
Clang version: Could not collect
CMake version: version 3.14.0
Python version: 3.7 (64-bit runtime)
Is CUDA available: True
CUDA runtime version: Could not collect
GPU models and configuration: GPU 0: GeForce GTX 1050 Ti
Nvidia driver version: 450.51.05
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Versions of relevant libraries:
[pip3] numpy==1.18.5
[pip3] pytorch-sphinx-theme==0.0.24
[pip3] torch==1.8.0a0
[conda] blas                      1.0                         mkl    defaults
[conda] magma-cuda102             2.5.2                         1    pytorch
[conda] mkl                       2020.1                      217    defaults
[conda] mkl-include               2020.1                      217    defaults
[conda] mkl-service               2.3.0            py37he904b0f_0    defaults
[conda] mkl_fft                   1.1.0            py37h23d657b_0    defaults
[conda] mkl_random                1.1.1            py37h0573a6f_0    defaults
[conda] numpy                     1.18.5           py37ha1c710e_0    defaults
[conda] numpy-base                1.18.5           py37hde5b4d6_0    defaults
[conda] pytorch-sphinx-theme      0.0.24                    dev_0    <develop>
[conda] torch                     1.8.0a0                   dev_0    <develop>
```


cc @ezyang @anjali411 @dylanbespalko @mruberry @Lezcano @rgommers @heitorschueroff
Repository: create-react-app
Issue: Retry chunk load without ejecting
Labels: needs triage

Projects built with *create-react-app* `react-scripts build` performs lazy loading without any retry. So, loading failures (e.g. because of slow network) can't be recovered from, without a reload.

The [webpack-retry-chunk-load-plugin](https://www.npmjs.com/package/webpack-retry-chunk-load-plugin) resolves this issue, but it can't be used in `create-react-app` generated app without ejecting.

Is there a way to perform retry JS chunk loading, without ejecting?
Repository: storybook
Issue: Default tab is always canvas on first load
Labels: bug,ui

**Describe the bug**
I'm trying to change the default storybook tab following the method described in #12111 .
On initial load of the storybook always land on the canvas page. (locally that would be `http://localhost:6006/?path=/story/<pathToStory>)`. If i click on another story, its defaults to the docs page as intended. eg: 
`http://localhost:6006/?path=/docs/<pathToStory>`


**To Reproduce**
1. Add `viewMode: 'docs',`to parameter in preview.js
2. Run and open storybook. (eg localhost:6006 )
3. See that its defaults to the canvas tab.
4 In you click at any other story after initial load, its defaults to docs as intended. 

**Expected behavior**
Even on initial load, the tab should default to the one set in preview.js

**System**
System:
    OS: macOS 10.15.6
    CPU: (12) x64 Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz
  Binaries:
    Node: 12.18.1 - ~/.nvm/versions/node/v12.18.1/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 6.14.5 - ~/.nvm/versions/node/v12.18.1/bin/npm
  Browsers:
    Chrome: 88.0.4315.5
    Safari: 14.0
  npmPackages:
    @storybook/addon-actions: ^6.0.26 => 6.0.27 
    @storybook/addon-essentials: ^6.0.26 => 6.0.27 
    @storybook/addon-links: ^6.0.26 => 6.0.27 
    @storybook/addons: ^6.0.26 => 6.0.27 
    @storybook/node-logger: ^6.0.26 => 6.0.27 
    @storybook/preset-create-react-app: ^3.1.4 => 3.1.4 
    @storybook/react: ^6.0.26 => 6.0.27
Repository: go
Issue: cmd/go: go env output is unstable/non-deterministic
Labels: NeedsFix,GoCommand

<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version devel +7307e86afd Sun Nov 8 12:19:55 2020 +0000 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/myitcv/.cache/go-build"
GOENV="/home/myitcv/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/myitcv/gostuff/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/myitcv/gostuff"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/home/myitcv/gos"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/myitcv/gos/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build332437426=/tmp/go-build -gno-record-gcc-switches"
</pre></details>

### What did you do?

As you can see from the `go env` output above, `GOGCCFLAGS` includes a temporary build directory path that changes with each invocation of `go env`. 

Whilst putting together a Play with Go guide on installing Go (https://play-with-go.dev/installing-go_go115_en/) I noticed this unstable output. Unfortunately, it makes writing guides that have automated checks to ensure they still work impossible without a custom sanitisation step (c.f. conversation with @bcmills on Slack about the output of `go get` being non-deterministic). 

Can the output of `go env` be made deterministic in the same way?

cc @bcmills @jayconrod 

FYI @mvdan
Repository: PowerToys
Issue: [Run][New Plugin] Start a timer using powertoys run 
Labels: Idea-Enhancement,Product-PowerToys Run,Run-Plugin

# 📝 Description of the new feature
---
It would be useful to start a timer in powertoys run, e.g. by typing `timer 15:00` to start a 15 minute timer. I don't particularly like the new UWP windows 10 timer app, it seems to have been designed with a touchscreen in mind and does not work well with the keyboard. Setting a timer using a selection wheel may work well on a touchscreen, but it is tedious when I have a keyboard right in front of me.

_What is the expected behavior of the proposed feature?  What is the scenario this would be used?_
open the powertoys run prompt, enter `timer h:m:s` to start a new timer in the timer app. If hours or minutes are omitted, they are set to 0.

If you'd like to see this feature implemented, add a 👍 reaction to this post.
Repository: flutter
Issue: Adding a flag to disable the shadow on the cupertino page route
Labels: c: new feature,framework,f: cupertino,f: routes,c: proposal,team-design,triaged-design

In iOS swipe back gesture between screens has no shadow. Now, in Flutter there is an unnecessary shadow

file: packages/flutter/lib/src/cupertino/route.dart, lines: 407-410
```
child: DecoratedBoxTransition(
  decoration: _primaryShadowAnimation,
  child: child,
),
```

Can you please remove this shadow, because, this is the real pain to override it inside the app.

### Flutter info
```
macbook@MacBook-Pro-MacBook-2 ~ % flutter doctor -v
[✓] Flutter (Channel stable, 1.22.4, on macOS 11.0.1 20B29 darwin-x64, locale en-RU)
    • Flutter version 1.22.4 at /Users/macbook/development/flutter
    • Framework revision 1aafb3a8b9 (3 days ago), 2020-11-13 09:59:28 -0800
    • Engine revision 2c956a31c0
    • Dart version 2.10.4

[!] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Users/macbook/Library/Android/sdk
    • Platform android-30, build-tools 30.0.2
    • Java binary at: /Applications/Android Studio 4.2 Preview.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6842174)
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for more details.

[✓] Xcode - develop for iOS and macOS (Xcode 12.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.1, Build version 12A7403
    • CocoaPods version 1.9.3
```

<img width="318" alt="Screenshot 2020-11-16 at 13 39 17" src="https://user-images.githubusercontent.com/5330807/99244074-a05e7780-2812-11eb-83d0-0253c620338e.png">
Repository: go
Issue: cmd/gofmt: incorrect alignment for func prototype parameters comments
Labels: NeedsInvestigation

<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
1.15.5
</pre>

### Does this issue reproduce with the latest release?



### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env

</pre></details>

### What did you do?

just saved file in VSCode - gofmt runs then 

### What did you expect to see?
```
func NewHandler(
	fieldName string,   // field to check
	stringValue string, // value to check
	schema Schema,      // source of fields
) *Handler {
```


### What did you see instead?
```
func NewHandler(
	fieldName string, // field to check
	stringValue string, // value to check
	schema Schema, // source of fields
) *Handler {
```
Repository: rust
Issue: forbid conditional, negative impls
Labels: T-compiler,F-negative_impls

We currently permit negative impls (feature-gated, https://github.com/rust-lang/rust/issues/68318) for both auto- and regular traits. However, the semantics of negative impls are somewhat unresolved. The current trait checker's implementation in particular does not work well with "conditional" negative impls -- in other words, negative impls that do not apply to *all* instances of a type. Further, the semantics of such impls when combined with auto traits are not fully agreed upon.

Consider:

```rust
auto trait Foo { }
struct Bar<T> { }
impl<T: Copy> !Foo for Bar<T> { }
```

The question is, does `Bar<Box<T>>` implement `Foo`? There is some disagreement about what would be expected here.

As a temporary step, the plan is to forbid impls of this kind using similar logic to what we use for `Drop` impls. There was a PR in this direction https://github.com/rust-lang/rust/pull/74648.

Another similar step would be to forbid negative impls for traits that have multiple generic parameters:

```rust
trait Foo<A> { }
impl<A, B> !Foo<A> for B { } // error
```

There is no particular reason that we can't support multiple parameters, but I suspect that the drop logic is not designed to handle cases like this.

Related issues:

- https://github.com/rust-lang/rust/issues/74629

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

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

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: create-react-app
Issue: I am not able to start the react application on Mac.
Labels: stale,needs triage

If you have a general question about Create React App or about building an app with Create React App we encourage you to post in GitHub Discussions instead of this issue tracker. The maintainers and other community members can provide help and answer your questions there: https://github.com/facebook/create-react-app/discussions

If you're looking for general information on using React, the React docs have a list of resources: https://reactjs.org/community/support.html

If you've discovered a bug or would like to propose a change please use one of the other issue templates.

Thanks!
Repository: flutter
Issue: Text Selection not working in Webview when showing in pageview
Labels: platform-android,p: webview,package,has reproducible steps,P2,found in release: 2.2,found in release: 2.5,team-android,triaged-android

When I am showing webview in Pageview builder, text selection doesn't work in Webview

Below is my code to reproduce issue, I am testing it on android device, having android 10 OS
 

<details><summary>my main.dart</summary>

```
import 'dart:io';

import 'package:flutter/material.dart';
import 'package:flutter/widgets.dart';
import 'package:preload_page_view/preload_page_view.dart';
import 'package:webview_flutter/webview_flutter.dart';
import 'package:webview_test/page.dart';

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'PreloadPageView Demo',
      home: PreloadPageViewDemo(),
    );
  }
}

class PreloadPageViewDemo extends StatefulWidget {
  PreloadPageViewDemo({Key key}) : super(key: key);

  @override
  _PreloadPageViewState createState() => _PreloadPageViewState();
}

class _PreloadPageViewState extends State<PreloadPageViewDemo> {

  @override
  void initState() {
    super.initState();
    if (Platform.isAndroid) WebView.platform = SurfaceAndroidWebView();
  }
  @override
  Widget build(BuildContext context) {
    return Scaffold(
        appBar: AppBar(
          title: const Text("PreloadPageView Demo"),
        ),
        body: Container(
            child: PreloadPageView.builder(
          preloadPagesCount: 5,
          itemBuilder: (BuildContext context, int position) => DemoPage(position),
          controller: PreloadPageController(initialPage: 1),
          onPageChanged: (int position) {
            print('page changed. current: $position');
          },
        )));
  }
}
```
</details>

<details><summary>my page.dart</summary>

```
import 'package:flutter/material.dart';
import 'package:webview_flutter/webview_flutter.dart';
import 'dart:io';
class DemoPage extends StatefulWidget {
  DemoPage(this.index);
  final int index;

  @override
  _DemoPageState createState() => _DemoPageState();
}

class _DemoPageState extends State<DemoPage> {
  @override
  void initState() {
    super.initState();
    if (Platform.isAndroid) WebView.platform = SurfaceAndroidWebView();
  }

  @override
  Widget build(BuildContext context) {
    print('Page loaded: ${widget.index}}');

    return Center(
      child: WebView(
          initialUrl: 'https://flutter.dev',
          javascriptMode: JavascriptMode.unrestricted,
          //onWebViewCreated: (controller) => _controller = controller,
        ),
    );
  }
}
```
</details>

Please guide me if I am doing anything wrong
Repository: flutter
Issue: Reduce GC pauses in CanvasKit-based web apps
Labels: c: regression,engine,c: performance,platform-web,perf: speed,e: web_canvaskit,team: benchmark,P2,team-web,triaged-web

After implementing memory management for paths and images the GC pauses increased causing more severe jank when the GC kicks in. The path benchmark caught this right away by showing a regression in web_benchmarks_canvaskit bench_path_recording.canvaskit recordPathConstruction.outlierRatio:

https://flutter-flutter-perf.skia.org/e/?begin=1605218345&end=1605295011&keys=X654b9260c66a559a5d5b12647fa27dfd&num_commits=50&request_type=1&xbaroffset=22519

Likely culprits:

- https://github.com/flutter/engine/pull/22446
- https://github.com/flutter/engine/pull/22459
- https://github.com/flutter/engine/pull/22415

We'd like to keep these changes, because otherwise we'd be leaking memory. However, we might want to find a way to reduce the jank. For example, the GC of the Skia object could be spread out across multiple timers.
Repository: flutter
Issue: Dart VM worker threads priority may be too high and embedder cannot change it
Labels: c: new feature,engine,c: performance,customer: dream (g3),perf: speed,P3,team-engine,triaged-engine

See  b/171917546

TL;DR is that when you call FlutterEnginePostCallbackOnAllNativeThreads, you don't actually get the Dart worker threads - and Dart might create new threads after you call that anyway.

We should be setting this via the --worker-thread-priority argument. While we could expose this to embedders, it'd be better for us to just set it ourselves to some priority lower than the main task runners to prevent GCs from causing jank.
Repository: godot
Issue: GDscript OS.get_system_time_*() not changing value when casting to float
Labels: bug,topic:core,topic:gdscript,needs testing

**Godot version:** 3.2.3.stable.official


**OS/device including version:**
Linux 5.9.8-arch1-1


**Issue description:**
I noticed that when I cast `OS.get_system_time_secs()` or `OS.get_system_time_msecs()` to a `float` it will not change anymore.
I guess that it has something to do with the `const` attribute of the functions.


**Steps to reproduce:**
Execute this simple standalone script, the left timestamp keeps changing, but the right one doesn't:
```gdscript
extends SceneTree

func _init() -> void:
    while true:
        print(OS.get_system_time_msecs(), " ", OS.get_system_time_msecs() as float)

        yield(self.create_timer(0.9), "timeout")
```
Repository: storybook
Issue: Setting inlineStories to false causes the documentation code snippet to be generated incorrectly
Labels: bug,addon: docs,block: source

**Describe the bug**
Setting `{ docs: { inlineStories: false } }` is causing the code snippet on the component DocsPage to be generated incorrectly. Additionally, if I change anything regarding what the story renders (such as parameters, the shape of the rendered output, etc.), it generates correctly until I refresh the page, click on another component and return to this one, or restart Storybook. If I don't set `inlineStories` to `false`, it generates correctly.

**To Reproduce**
Steps to reproduce the behavior:

1. Set the `inlineStories` parameter to `false`.

**Expected behavior**
I expect the component snippet to just contain the component and the parameters passed in; instead, it's rendering the function definition for the story.

**Screenshots**
This is what I expect the output to be (this screenshot is taken when not setting `inlineStories` to false:
![image](https://user-images.githubusercontent.com/4295145/99298909-144b5080-2810-11eb-9628-edd83cb5b891.png)

This is what is generated when `inlineStories` is false:
![image](https://user-images.githubusercontent.com/4295145/99298949-24fbc680-2810-11eb-87a4-6cec83313fc0.png)

**Code snippets**
```javascript
import React from "react";
import { Story, Meta } from "@storybook/react";
import SaveIcon from "@material-ui/icons/Save";

import StyledAppFab, { AppFab, Props as AppFabProps } from "./AppFab";

export default {
  title: "Global/AppFab",
  component: AppFab,
  argTypes: {
    onClick: { action: "click" },
  },
} as Meta;

const Template: Story<AppFabProps> = (args: any) => <StyledAppFab {...args} />;

export const Primary = Template.bind({});
Primary.args = {
  accessibilityLabel: "Button",
  children: <SaveIcon />,
};
Primary.parameters = {
  docs: {
    inlineStories: false,
  },
};
```

**System**
```
Environment Info:

  System:
    OS: Windows 10 10.0.19041
    CPU: (12) x64 Intel(R) Core(TM) i7-9850H CPU @ 2.60GHz
  Binaries:
    Node: 14.12.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.10 - C:\sandbox\projects\internal-admin-web\node_modules\.bin\yarn.CMD
    npm: 6.14.8 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 86.0.4240.193
    Edge: Spartan (44.19041.423.0)
  npmPackages:
    @storybook/addon-actions: ^6.0.28 => 6.0.28
    @storybook/addon-essentials: ^6.0.28 => 6.0.28
    @storybook/addon-links: ^6.0.28 => 6.0.28
    @storybook/node-logger: ^6.0.28 => 6.0.28
    @storybook/preset-create-react-app: ^3.1.5 => 3.1.5
    @storybook/react: ^6.0.28 => 6.0.28
```
Repository: pytorch
Issue: Missing -fopenmp when used in torchvision
Labels: module: build,module: cpp-extensions,triaged,enhancement,module: build warnings,module: openmp

## 🐛 Bug

The issue was originally reported here: 
- https://github.com/pytorch/vision/issues/2783

Forwarded to PyTorch in case this is an upstream issue about CMake.

TorchVision has build warnings about invalid `#pragma omp` used without `-fopenmp`.
I'm think if this could be due to pytorch not providing the flag on CMake interface.

For example, this `PRIVATE` may be insufficient when you have templated openmp in header:
https://github.com/pytorch/pytorch/blob/3d421b313731c98864b26bcec1925c7220f9c71b/caffe2/CMakeLists.txt#L938

## Environment

 - PyTorch Version (e.g., 1.0): master
 - OS (e.g., Linux): Ubuntu 18.04
 - How you installed PyTorch (`conda`, `pip`, source): source
 - Build command you used (if compiling from source): cmake/ninja/gcc-8
 - Python version: 3.6

cc @malfet @seemethere @walterddr @yf225 @glaringlee
Repository: terminal
Issue: Add a setting to configure display of auto detected links, normally and on hover
Labels: Issue-Feature,Area-TerminalControl,Product-Terminal,Area-Schema

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement.
2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement.
3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement.
5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement.

All good? Then proceed!
-->

# Description of the new feature/enhancement
Allow the user to define how detected patterns should be displayed, when hovered and not.

See (see https://github.com/microsoft/terminal/pull/7691#issuecomment-727620804) and [this](https://github.com/microsoft/terminal/pull/8148#issuecomment-721422578)

Wanted to make this an official issue where we can discuss the extent to which this should be implemented (should it just be limited to font style? or also font face? and what about font size? or other effects too)

<!-- 
A clear and concise description of what the problem is that the new feature would solve.
Describe why and how a user would use this new functionality (if applicable).
-->