sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: create-react-app
Issue: support to use resourceQuery to match `css module` css rule.
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?

<!--
  Provide a clear and concise description of what the problem is.
  For example, "I'm always frustrated when..."
-->

It is not a problem but an idea.
CRA support use file extension such like `.module.css` or `.module.scss` to enable css module.
I think using `resourceQuery` is also a good choice.

### Describe the solution you'd like

<!--
  Provide a clear and concise description of what you want to happen.
-->

```javascript
import style from 'app.module.css'
import style from 'app.css?css_module'
```
The two above are both ok to enable css module.

When css rules match resource query `css_module`, css module will be enabled.

### Describe alternatives you've considered

It is easier to help the projects which not obey the file extension rule to use CRA, because we could use babel plugin to add query at import statement.
So, we could enable css module automaticly without change file name.
```javascript
import 'common.css'
import style from 'app.css'

// after babel plugin

import 'common.css' // no need to add query
import style from 'app.css?css_module'
```

### Additional context 

It is easy to add a babel plugin, but change webpack rule is not without `eject`.
Repository: rust
Issue: "cannot borrow a constant which may contain interior mutability" for local variable inside constant evaluation
Labels: T-lang,T-compiler,C-bug,A-const-eval

This code [(playground link)](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=9eaf4438991432c41b272b35023cdc82):
```rust
#![feature(const_raw_ptr_deref)]
use std::cell::UnsafeCell;
const FOO: u32 = {
    let x = UnsafeCell::new(42);
    unsafe { *x.get() }
};
```
produces on latest nightly:
> error[E0492]: cannot borrow a constant which may contain interior mutability, create a static instead

However, following the advice to create a static simply results in a "constants cannot refer to statics" error.

The limitation seems unnecessary.  We're not really borrowing a constant; `x` only exists during constant evaluation and will not be emitted into the binary, so there's no reason it would be problematic to mutate it.

[This issue affects `memoffset`.](https://github.com/Gilnaa/memoffset/issues/37)
Repository: ant-design
Issue: Sizing class suffixes are inconsistent
Labels: help wanted,Inactive,improvement

- [x] I have searched the [issues](https://github.com/ant-design/ant-design/issues) of this repository and believe that this is not a duplicate.

### Reproduction link
[https://gist.github.com/romu70/6f56ecace444fc68c02d309b06f4c0c0](https://gist.github.com/romu70/6f56ecace444fc68c02d309b06f4c0c0)

### Steps to reproduce
Just inspect a Ant html.

### What is expected?
Same naming convention for components sizes. Bootstrap suffixes are great: -sm and -lg everywhere.

### What is actually happening?
For layout naming, Ant uses Bootstrap suffixes: xs, sm, md, lg, xl, xxl. But for components, those suffixes are inconsistent:

    button, list, input, select use the same Bootstrap suffixes, great!
    steps, switch, DataPicker, TimePicker, Progress (and maybe ohers) use "-small" and "-large" suffixes.
    there is no size class for the circular progress component

IMHO, those latter ones should be changed to use the same convention (-sm and -lg).

| Environment | Info |
|---|---|
| antd | 4.0.1 |
| React | doesn't matter |
| System | doesn't matter |
| Browser | doesn't matter |


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: opencv
Issue: Error loading ONNX model (FasterRCNN50 from Torchvision)
Labels: category: dnn,category: dnn (onnx)

I am trying to load FasterRCNN model of torchvision but facing some errors. Here is the code for the model:-
```
import torch
import torchvision

model = torchvision.models.detection.fasterrcnn_resnet50_fpn(pretrained=True)
x = [torch.rand(3, 300, 400), torch.rand(3, 500, 400)]
model.eval()
predictions = model(x)
torch.onnx.export(model, x, "fasterrcnn50.onnx", opset_version=11)
```
And loading my model using :
```
import cv2 as cv
net = cv.dnn.readNet('fasterrcnn50.onnx')
```
Here I am getting an error which is:
```
cv2.error: OpenCV(4.2.0-dev) /Users/adityakumar/opencv/modules/dnn/src/graph_simplifier.cpp:79: error: (-212:Parsing error) Input node with name 2780 not found in function 'getInputNodeId'
```
torch==1.4.0
torchvision==0.5.0
OpenCV==4.2.0-dev

Here is the link of model: [model](https://drive.google.com/open?id=1WvsBv9gsAulTL-SOivfAgNWn7ZGvsmM3)

Please check, how can I resolve this error?
Repository: TypeScript
Issue: No error with Partial<Record<number, {}>> in object spreading
Labels: Needs Investigation

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Even if you think you've found a *bug*, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs section!

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ

Please fill in the *entire* template below.
-->

<!--
Please try to reproduce the issue with the latest published version. It may have already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly
-->
**TypeScript Version:**  3.8.3

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** [type inference], [partial], [record], [object spreading]

**Code**

```ts
type Point = {
  x: number
  y: number
}

type Space = Partial<Record<number, Point>>


function addPointReducer(point: Point, pointId: number, prevSpace: Space): Space {
  const prevPoint = prevSpace[pointId]

  return {
    ...prevPoint,
    [pointId]: point,
  }
}

```

**Expected behavior:**
Should throw an error on `...prevPoint` because `Point` doesn't equal to `Space`.

**Actual behavior:**
No error.

**Playground Link:** https://www.typescriptlang.org/play/?ssl=1&ssc=1&pln=17&pc=1#code/C4TwDgpgBACg9gSwHbCgXigbwFBSgDwC4okBXAWwCMIAnXKEYsq27AX221EigGUwAhgGNoGGAJrAEAgDYAeAEoQhcGgBM5zajQA0sRCgB8hztgBmpJEKlwkUAWrXxkwJWtIiaACjAHgxZxQ9XxcASTUmCm1gmggAN35hCGJEkQBKFMERLHoVJABnVDBYuMDUDGL41IgAbRCUcIBdTjxY4FIaOxw8PAA6fsrSvx16PDq-JuJ64BG8Dg4gA

**Related Issues:** <!-- Did you find other bugs that looked similar? -->
Repository: opencv
Issue: How to call a saved_model formatted model via opencv
Labels: feature,priority: low,category: dnn

We know that saved_model is often used for tfserving for model deployment. It has the following structure：
`assets/
assets.extra/
variables/
    variables.data-?????-of-?????
    variables.index
saved_model.pb|saved_model.pbtxt`

Now I want to call the saved_model format model through opencv，How can I do this, thank you very much.

I know that the .pb model exported by tf1.x can be imported through the structure file .pbtxt，but what should be done with saved_model

The platform is c ++,ubuntu 18.04，opencv4.1
Repository: rust
Issue: Can't use anonymous functions with calling conventions other than Rust
Labels: A-closures,T-lang,C-feature-request

Hi all

Compiler refuses to compile functions when other than "Rust" calling convention used.

I tried this code:

```rust
#![feature(abi_vectorcall)]

type Dyad = unsafe extern "fastcall" fn(u32, u32) -> u32; // DOES NOT WORK
// type Dyad = unsafe extern "vectorcall" fn(u32, u32) -> u32; // DOES NOT WORK
//type Dyad = fn(u32, u32) -> u32;  // WORKS as expected

fn f(t:u32, x:u32, y:u32) -> u32 {
  let d:Dyad = match t {
    1 => |x,y| x+y,
    _ => unimplemented!()
  };
  d(x, y)
}

fn main() {
  println!("{}", f(1, 10, 20));
}
```
### Meta
`rustc --version --verbose`:
```
rustc 1.43.0-nightly (3dbade652 2020-03-09)
binary: rustc
commit-hash: 3dbade652ed8ebac70f903e01f51cd92c4e4302c
commit-date: 2020-03-09
host: x86_64-unknown-linux-gnu
release: 1.43.0-nightly
LLVM version: 9.0
```
Repository: TypeScript
Issue: Call hierarchy becomes infinitely nested on derived class methods using super call 
Labels: Bug,Help Wanted,Domain: Signature Help

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Even if you think you've found a *bug*, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs section!

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ

Please fill in the *entire* template below.
-->

<!--
Please try to reproduce the issue with the latest published version. It may have already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly
-->
**TypeScript Version:**  3.8.3

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**
call hierarchy, call tree, find references, function calls
**Code**

```ts
// A *self-contained* demonstration of the problem follows...
// Test this by running 'Show Call Hierarchy' command on the line marked below

class A {
   foo() {
   }
}

class B extends A {
   foo() { <-- show call hierarchy
      super.foo();
   }
}

function bar() {
   let a: A = new B();
   a.foo();
}
```

**Expected behavior:**

Run the 'Show Call Hierarchy' command in vscode on the line marked above. Resulting call tree should look like this:

![Capture](https://user-images.githubusercontent.com/4710322/76430284-d19bc380-63b8-11ea-89ba-5aa81532e4a0.JPG)

**Actual behavior:**

Instead, an infinitely nested call tree is generated:

![Capture](https://user-images.githubusercontent.com/4710322/76430121-a022f800-63b8-11ea-8f65-dfb9143d5f25.JPG)

NOTE: if the line with the `super.foo()` call is commented out, the call tree is displayed as expected.


**Playground Link:** <!-- A link to a TypeScript Playground "Share" link which demonstrates this behavior -->

**Related Issues:** <!-- Did you find other bugs that looked similar? -->
Repository: TypeScript
Issue: @description JSDoc tag interferes with callback parameter documentation
Labels: Bug,Help Wanted,checkJs,PursuitFellowship

**TypeScript Version:**  3.8.3

**Search Terms:** jsdoc param

**Expected behavior:**
Below code creates no errors, type of `x` is recognized as `(value: number) => boolean`

**Actual behavior:**
Type of `x` is `() => boolean`, the invocation creates a type error.

Removing the `@description` tag makes the code work as expected.

My interpretation of https://jsdoc.app/tags-description.html is that you should be able to place `@description` anywhere in the comment without interfering with other tags:

> By using the @description tag, you can place the description anywhere in the JSDoc comment.

<!-- Did you find other bugs that looked similar? -->
**Related Issues:** Ran into a crash #37265 while trying to repro this with template parameters.

**Code**
```ts
// @ts-check

/**
 * @callback IterablePredicate
 * @description return true if given element of iterable matches an internal condition
 * @param {number} value the current item being evaluated
 * @returns {boolean} true if the entry satisfies given condition
 **/

/**
 * @type {IterablePredicate}
 */
let x;
x(3) // Expected 0 arguments, but got 1.
```




<details><summary><b>Compiler Options</b></summary>

```json
{
  "compilerOptions": {
    "noImplicitAny": true,
    "strictFunctionTypes": true,
    "strictPropertyInitialization": true,
    "strictBindCallApply": true,
    "noImplicitThis": true,
    "noImplicitReturns": true,
    "alwaysStrict": true,
    "esModuleInterop": true,
    "checkJs": true,
    "allowJs": true,
    "declaration": true,
    "experimentalDecorators": true,
    "emitDecoratorMetadata": true,
    "moduleResolution": 2,
    "target": "ES2017",
    "jsx": "React",
    "module": "ESNext"
  }
}
```


</details>

**Playground Link:** [Provided](https://www.typescriptlang.org/v2/en/play?useJavaScript=true#code/FAehAIAEBcGcFoDGALApog1sUAqHxwcpEBDAGzICMTNwBJaVAJxMrNQAUnUATAS1KMCRSD1SxETPgAdofAPYA7cN2gBXJsuhM1qcHwBm4AOZ8AbqmWp2AW0vRw8o30Ys2emyWgpx4Esr5FV0VycEQlfjklYShpEhYbcABvRTUbSmYAX3Azcl1waDQwjW4g-UZEjMDjcFRcsjUvXhjIVQ1FWGTKeXl2f2ztfMMCovsmAE9wWC8+WAM+X1MLZXDFSIVFYRwQbBA8Fuhx6T0khmZWdi5eASbM4R32BwAPAG5gJ4AKAGYASiA)
Repository: go
Issue: x/pkgsite: searching by smartcontractkit and chainlink does not show github.com/smartcontractkit/chainlink
Labels: NeedsInvestigation,pkgsite,pkgsite/search

There's a fairly active Go project on GitHub that's not found on go.dev so there might be others.

[smartcontractkit/chainlink](https://github.com/smartcontractkit/chainlink) has 6 releases this year, 42 contributors, and 9,372 commits.
 
![image](https://user-images.githubusercontent.com/57072051/76448037-b5d3f580-6397-11ea-8a55-c8057e16ed17.png)

Just a hunch: could this be related to the project install using `git clone` instead of `go get`?

### What did you expect to see?

smartcontractkit/chainlink existing on go.dev.

### What did you see instead?

smartcontractkit/chainlink is not found in go.dev.
Repository: kubernetes
Issue: Cannot set the eventTime field when creating/updating Events
Labels: kind/bug,sig/api-machinery,lifecycle/frozen,triage/accepted

<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!

If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->


**What happened**:

We cannot create/update an `Event` resource if we set the `eventTime` field to a valid value, e.g., `"2020-03-05T19:40:14.000000Z"`. The Kubernetes API responds with HTTP 422 and the following error:

```
events "istio-ingressgateway.15f97fc1c9cd685f" was not valid:
* reportingController: Required value
* reportingController: Invalid value: "": name part must be non-empty
* reportingController: Invalid value: "": name part must consist of alphanumeric characters, '-', '_' or '.', and must start and end with an alphanumeric character (e.g. 'MyName',  or 'my.name',  or '123-abc', regex used for validation is '([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9]')
* reportingInstance: Required value
* action: Required value
```

If the `eventTime` field is `null`, the `Event` resource is created/updated successfully. In both cases, the `Event` resource does have a name.

**What you expected to happen**:

The `Event` resource should be created/updated, and it should have the provided value in its `eventTime` field.

**How to reproduce it (as minimally and precisely as possible)**:

In a Kubernetes cluster, choose a random event and edit it with `kubectl edit events <event>`. In the editor window, change `eventTime` to `"2020-03-05T19:40:14.000000Z"`. The update will fail with the aforementioned message.

**Anything else we need to know?**:

We see that the same applies to v1.15.

**Environment**:
- Kubernetes version (use `kubectl version`):
```
Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.2", GitCommit:"c97fe5036ef3df2967d086711e6c0c405941e14b", GitTreeState:"clean", BuildDate:"2019-10-15T19:18:23Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"14+", GitVersion:"v1.14.10-gke.22", GitCommit:"be6e649e67f82e64e43e32119b2b14250a7f9542", GitTreeState:"clean", BuildDate:"2020-01-30T19:02:16Z", GoVersion:"go1.12.12b4", Compiler:"gc", Platform:"linux/amd64"}
```
- Cloud provider or hardware configuration: GKE
- OS (e.g: `cat /etc/os-release`): Ubuntu 18.04.4 LTS 
- Kernel (e.g. `uname -a`): `Linux hostname 4.15.0-1052-gke #55-Ubuntu SMP Tue Feb 11 21:45:20 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux`
- Install tools:
- Network plugin and version (if this is a network-related bug):
- Others:
Repository: go
Issue: cmd/go: "+build comment … blank line" warning not produced by "go run" or "go build"
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>
$ go version
go version go1.14 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/wolf/.cache/go-build"
GOENV="/home/wolf/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GONOPROXY="go.showmax.cc"
GONOSUMDB="go.showmax.cc"
GOOS="linux"
GOPATH="/home/wolf/go"
GOPRIVATE="go.showmax.cc"
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/lib/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/tmp/ww/go.mod"
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-build147562273=/tmp/go-build -gno-record-gcc-switches"

</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.
-->
```
+$ tree .
.
├── a.go
├── b.go
├── c.go
└── go.mod

0 directories, 4 files
+$ cat a.go
package main

import "fmt"

func main() {
        fmt.Println(value)
}
+$ cat b.go
// +build !windows
package main

var value = "POSIX"
+$ cat c.go
// +build windows
package main

var value = "WIN"
+$ cat go.mod
module test

go 1.14
+$ go run .
# test
./c.go:4:5: value redeclared in this block
        previous declaration at ./b.go:4:5
```


### What did you expect to see?

```
# test
./b.go:1:1: +build comment must appear before package clause and be followed by a blank line
./c.go:1:1: +build comment must appear before package clause and be followed by a blank line
```

### What did you see instead?

```
# test
./c.go:4:5: value redeclared in this block
        previous declaration at ./b.go:4:5
```
Repository: pytorch
Issue: Multiple CMake target errors ever since commit 0e52627358
Labels: module: build,triaged

## 🐛 Bug

Building pytorch on platform `ppc64le`, since Feb 28, has resulted in a flurry of CMake Error
messages partway through the build.  An example of the error message appears below, though the error will repeat with some variations and different target names:

```core header install: /home/jenkins/pytorch/build/aten/src/ATen/core/TensorBody.h
core header install: /home/jenkins/pytorch/build/aten/src/ATen/core/TensorMethods.h
CMake Error at cmake/Codegen.cmake:207 (add_custom_target):
  add_custom_target cannot create target "ATEN_CPU_FILES_GEN_TARGET" because
  another target with the same name already exists.  The existing target is a
  custom target created in source directory "/home/jenkins/pytorch/caffe2".
  See documentation for policy CMP0002 for more details.
Call Stack (most recent call first):
  caffe2/CMakeLists.txt:2 (include)
```

To see a full log with the varying CMake errors, here is an example CI output on ppc64le:
https://powerci.osuosl.org/job/pytorch-linux-cuda92-cudnn7-py3-mpi-build-only-gpu/518/consoleFull

## To Reproduce

Steps to reproduce the behavior:
1. Run the build scripts for pytorch on a `ppc64le` system.  In my case, it is a docker container
running ubuntu and using cuda10.2 (or 10.1 or 10.0) but i'm doubtful the OS or CUDA level matters.  Wait a few minutes; the errors seem to start occuring in under 5 min.

NOTE:
I manually tried different builds with different levels of pytorch master until I narrowed it
down to the exact pull request on which the problem started to happen:  The commit ID
where it starts failing is `0e52627358` -- this corresponds to PR #338669.  The errors
don't appear if I simply build from the prior commit.  
Reference:  https://github.com/pytorch/pytorch/commit/0e52627358c4ec60243f9d8e19b722b7b2265ffc

Not being an expert in this, I haven't determined what it is in this commit that triggered the error,
but it has happened continuously in every CI run since that change was included.
I'll continue to look a bit closer, but I wanted to get the issue documented.  Perhaps @kimishpatel has some suggestions or thoughts on what to look at (as user who made the aforementioned commit)?

## Environment

Ubuntu 18.04.4
CUDA 10.2 (also reproduces on 10.1 and 10.0).
Build using current master branch of pytorch, or any since 0e52627358
Built on ppc64le in a docker container, but I don't know if this is necessarily tied to
the one platform or not.
Repository: kubernetes
Issue: Kubelet has no rate controls after a pod was evicted
Labels: sig/node,kind/feature,needs-triage

There is no mechanism today to prevent abusive eviction loops (controller recreates a pod that was just evicted).  #89067 seems to indicate that the kubelet and the controller will just fight until the controller stops.  It seems reasonable that an eviction decision should perform some rate limit on subsequent pods from that controller, namespace, or name, although this could be tricky.

/sig node
Repository: rust
Issue: VecDeque should support splice / extend_front
Labels: A-collections,T-libs-api,C-feature-request

`VecDeque` should support `splice` for convenience.
([`SliceDeque`](https://docs.rs/slice-deque/0.3.0/slice_deque/struct.SliceDeque.html#method.splice) supports it, but it doesn't build on wasm and seems kind of abandoned (several unmerged PRs with no updates).)

`VecDeque` should also support `extend_front` (like repeated `push_front` from an iterator. Compared to calling `q.splice(..0, iter)`, the elements added with `q.extend_front(iter)` would be in reverse order).

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

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

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: pytorch
Issue: A better way to show users all build options
Labels: module: build,triaged

We currently have build options enumerated at the top of setup.py. This, however, is redundant (as the info is largely available in CMakeLists.txt) and is pretty fallible and confusing. We should make it more user-friendly, say, `python setup.py help` should list the options extracted from `CMakeLists.txt`.

---

This dates back to discussion long time ago with @ezyang , but was never written down as a formal issue.