sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: test_autograd failures on Power
Labels: module: autograd,module: cuda,module: tests,triaged,module: POWER,module: linear algebra

## 🐛 Bug

I have some tests failing on a Power system. As MKL is not (easily?) available there I'm using the automatic fallback to Eigen/OpenBlas.
The failing tests are:
- test_solve_batched_broadcast_A_cpu
- test_solve_batched_broadcast_b_cpu
- test_solve_batched_cpu
- test_solve_batched_dims_cpu

Those are only 4 out of 1961 which fail

## To Reproduce

Steps to reproduce the behavior:

1. `python setup.py install`
1. `cd tests`
1. `python run_tests.py`

<!-- If you have a code sample, error messages, stack traces, please provide it here as well -->

## Expected behavior

Tests pass

## Environment

PyTorch Version: 1.5.1 and 1.6rc3

OS: Red Hat Enterprise Linux Server release 7.6 (Maipo)
GCC version: (GCC) 8.3.0
CMake version: version 3.15.3

Python version: 3.7
Is CUDA available: N/A
CUDA runtime version: 10.1.243
GPU models and configuration: 
GPU 0: Tesla V100-SXM2-32GB
GPU 1: Tesla V100-SXM2-32GB
GPU 2: Tesla V100-SXM2-32GB
GPU 3: Tesla V100-SXM2-32GB
GPU 4: Tesla V100-SXM2-32GB
GPU 5: Tesla V100-SXM2-32GB

Nvidia driver version: 440.64.00
cuDNN version: 7.6.4.38

Versions of relevant libraries:
[pip3] numpy==1.17.3


## Additional context

The failed tests output look like this:

```
RuntimeError: Jacobian mismatch for output 0 with respect to input 0,
numerical:tensor([[ 1.3259e+00,  0.0000e+00,  0.0000e+00,  ...,  3.9608e+06,
          0.0000e+00,  0.0000e+00],
        [ 0.0000e+00,  1.3259e+00,  0.0000e+00,  ...,  0.0000e+00,
          0.0000e+00,  0.0000e+00],
        [ 0.0000e+00,  0.0000e+00,  1.3259e+00,  ...,  0.0000e+00,
          0.0000e+00,  0.0000e+00],
        ...,
        [ 0.0000e+00,  0.0000e+00,  0.0000e+00,  ..., -2.3575e-02,
          0.0000e+00,  0.0000e+00],
        [ 0.0000e+00,  0.0000e+00,  0.0000e+00,  ...,  0.0000e+00,
         -2.3575e-02,  0.0000e+00],
        [ 0.0000e+00,  0.0000e+00,  0.0000e+00,  ...,  0.0000e+00,
          0.0000e+00, -2.3575e-02]])
analytical:tensor([[ 1.3259,  0.0000,  0.0000,  ...,  0.0000,  0.0000,  0.0000],
        [ 0.0000,  1.3259,  0.0000,  ...,  0.0000,  0.0000,  0.0000],
        [ 0.0000,  0.0000,  1.3259,  ...,  0.0000,  0.0000,  0.0000],
        ...,
        [ 0.0000,  0.0000,  0.0000,  ..., -0.0236,  0.0000,  0.0000],
        [ 0.0000,  0.0000,  0.0000,  ...,  0.0000, -0.0236,  0.0000],
        [ 0.0000,  0.0000,  0.0000,  ...,  0.0000,  0.0000, -0.0236]])

```


cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer @ngimel @jianyuh @mruberry @heitorschueroff @walterddr @IvanYashchuk @VitalyFedyunin
Repository: rust
Issue: Missed optimization: Loop with decreasing index does not elide bounds check
Labels: A-LLVM,I-slow,C-enhancement,T-compiler,C-optimization

I tried code very similar to the code below. The expected produced code would perform one bounds check at the start of the function and none inside the loop. `offsets` is first asserted to be valid for the initial index. This should be enough to also find that it is valid for all smaller indices. No loop iteration can increase the index so the index correctness is a loop invariant.

```rust
fn problematic(buf: &mut [u8], offsets: &[u8], mut idx: usize) {
    let offsets = &offsets[..=idx];
    for b in buf {
        *b = idx as u8;
        idx = idx.saturating_sub(usize::from(offsets[idx]));
    }
}
```

Instead we get this:

<details>

<pre>
playground::problematic:
	push	rax
	cmp	r8, -1
	je	.LBB0_3
	mov	r9, rsi
	lea	rsi, [r8 + 1]
	cmp	r8, rcx
	jae	.LBB0_2
	test	r9, r9
	je	.LBB0_8
	xor	r10d, r10d
	mov	rcx, r8

.LBB0_6:
	mov	byte ptr [rdi + r10], cl
;; The critical jump and cmp we don't want to have, costs ~5-10% loop perf
	cmp	rcx, r8
	ja	.LBB0_9
	movzx	eax, byte ptr [rdx + rcx]
	sub	rcx, rax
	mov	eax, 0
	cmovb	rcx, rax
	add	r10, 1
	cmp	r9, r10
	jne	.LBB0_6

.LBB0_8:
	pop	rax
	ret

.LBB0_9:
	lea	rdx, [rip + .Lanon.9b054490e6ade753ffe504f874525a87.2]
	mov	rdi, rcx
	call	qword ptr [rip + core::panicking::panic_bounds_check@GOTPCREL]
	ud2

.LBB0_3:
	lea	rdi, [rip + .Lanon.9b054490e6ade753ffe504f874525a87.1]
	call	qword ptr [rip + core::slice::slice_index_overflow_fail@GOTPCREL]
	ud2

.LBB0_2:
	lea	rdx, [rip + .Lanon.9b054490e6ade753ffe504f874525a87.1]
	mov	rdi, rsi
	mov	rsi, rcx
	call	qword ptr [rip + core::slice::slice_index_len_fail@GOTPCREL]
	ud2

.Lanon.9b054490e6ade753ffe504f874525a87.0:
	.ascii	"src/lib.rs"

.Lanon.9b054490e6ade753ffe504f874525a87.1:
	.quad	.Lanon.9b054490e6ade753ffe504f874525a87.0
	.asciz	"\n\000\000\000\000\000\000\000\002\000\000\000\024\000\000"

.Lanon.9b054490e6ade753ffe504f874525a87.2:
	.quad	.Lanon.9b054490e6ade753ffe504f874525a87.0
	.asciz	"\n\000\000\000\000\000\000\000\005\000\000\000.\000\000"
</pre>
</details>
Repository: pytorch
Issue: test_upsampling_not_recompute_scale_factor fails with Eigen/OpenBLAS
Labels: module: tests,triaged

## 🐛 Bug

I'm getting a test failure of test_upsampling_not_recompute_scale_factor

## To Reproduce

Steps to reproduce the behavior:

1. python setup.py install
1. cd test
1. python run_tests.py

<!-- If you have a code sample, error messages, stack traces, please provide it here as well -->

```
======================================================================
FAIL: test_upsampling_not_recompute_scale_factor (__main__.TestNN)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "test_nn.py", line 7199, in test_upsampling_not_recompute_scale_factor
    self.assertEqual(out_t, expected_out_t)
  File "/tmp/easybuild-tmp/eb-lWK_ii/tmpPLa9_o/lib/python3.7/site-packages/torch/testing/_internal/common_utils.py", line 884, in assertEqual
    assertTensorsEqual(x, y)
  File "/tmp/easybuild-tmp/eb-lWK_ii/tmpPLa9_o/lib/python3.7/site-packages/torch/testing/_internal/common_utils.py", line 850, in assertTensorsEqual
    self.assertLessEqual(max_err, prec, message)
AssertionError: tensor(1.57356e-05, dtype=torch.float32) not less than or equal to 1e-05 : 

```

## Expected behavior

Tests pass

## Environment

PyTorch version: 1.5.1

OS: Red Hat Enterprise Linux Server release 7.8 (Maipo)
GCC version: (GCC) 8.3.0
CMake version: version 3.15.3

Python version: 3.7
Is CUDA available: N/A
CUDA runtime version: 10.1.243
cuDNN version: 7.6.4.38

Versions of relevant libraries:
[pip3] numpy==1.17.3

cc @mruberry
Repository: go
Issue: dev.boringcrypto: crypto/internal/boring: consider splitting up into smaller packages based on math/big requirement
Labels: NeedsInvestigation

As discussed in [golang.org/cl/241442](https://go-review.googlesource.com/c/go/+/241442/1#message-bb399544c64ab073e5adf50eef6a961dc798ab5e), this is a tracking issue to look into breaking `crypto/internal/boring` up into distinct packages, splitting out RSA and ECDSA—which require `math/big`—away from the rest which do not.

/cc @FiloSottile @katiehockman
Repository: TypeScript
Issue: Problematic Ternary-Expression Formatting Inside JS String Interpolation
Labels: Bug,Domain: Formatter

*TS Template added by @mjbvz*

**TypeScript Version**: 4.0.0-dev.20200708

**Search Terms**
- format
- template string

---

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->
<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: https://code.visualstudio.com/insiders/ -->

<!-- Use Help > Report Issue to prefill these. -->
- VSCode Version: 1.46.1
- OS Version: Fedora 32, Linux x64 5.6.19-300.fc32.x86_64

Steps to Reproduce:

1. manual breaking of a long line of a ternary expression within template string interpolation  `${ condition ? true : false }`
2. running native formatter messes up the indentation for every possible correct format

Code
```JS
var query = `
  SELECT
    entry.id,
    entry.event_type as type,
    entry.object, entry.creator,
    UNIX_TIMESTAMP(entry.time_created) as timeCreated
    ${
      isActive ?
        'FROM entry INNER JOIN active ON entry.id = active.id' :
        'FROM entry LEFT JOIN active ON entry.id = active.id WHERE active.id IS NULL'
    }
    LIMIT ${20 * (page > 1 ? page - 1 : 0)}, 20;`;
```

Screenshots

Before:
<img src="https://user-images.githubusercontent.com/34912861/87024388-536df300-c1d9-11ea-9038-fe95b415e5aa.png" width="650">

After:
<img src="https://user-images.githubusercontent.com/34912861/87024448-6bde0d80-c1d9-11ea-87c7-991250ca42b7.png" width="650">

Before:
<img src="https://user-images.githubusercontent.com/34912861/87024682-ba8ba780-c1d9-11ea-9d5c-448986ada731.png" width="650">

After:
<img src="https://user-images.githubusercontent.com/34912861/87024728-caa38700-c1d9-11ea-81af-d2120fa8301a.png" width="650">

So, the problem specifically seems to be in the way the formatter determines the indentation level to which it normalizes the rest of ternary expression body. The above screenshots show that it ignores the indentation level of the opening brace, and even the lines before it, adjusting itself to the first line indentation level.

<!-- Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes
Repository: storybook
Issue: Addon-controls: Add custom user-defined controls
Labels: feature request,addon: controls

We are currently documenting our React components in Storybook, and decided to go straight to version 6.0 to make use of the new Args and Controls addons. During that work, we realised that the [choice of controls](https://github.com/storybookjs/storybook/blob/next/addons/controls/README.md#control-annotations) is very limited.

Here are some examples:
- We want users to select from a pre-defined list of colors. The `"select"` control can only display text but we want to preview the color next to it.
- We want users to select from a list of icons. The control should display a list of all icons and clicking on an icon selects it.
- One prop may allow for `string[]`, so we want to allow the user to add strings to the list, or remove existing strings.

Any chance to allow users to specify custom controls in `argTypes` that are not built into `addon-controls`?

Here's how this could look like in React code, where `ColorPicker` is a custom control we'd build:

```tsx
const ColorPicker = ({ value, setValue }) => {
  return (
    <select value={value} onChange={setValue}>
      <option>red</option>
      <option>blue</option>
    </select>
  );
}

export default {
  title: "ExampleComponent",
  component: ExampleComponent,
  argTypes: {
    color: {
      control: ColorPicker,
    },
  },
};
```
Repository: TypeScript
Issue: Generic Type Alias Overloading
Labels: Suggestion,In Discussion

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker.

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ, especially the "Common Feature Requests" section: https://github.com/Microsoft/TypeScript/wiki/FAQ

-->

## Search Terms

<!-- List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily -->

- variadic type alias
- Generic variadic Type Alias
- Generic Overload
- Generic Type Alias Overloading

## Suggestion

<!-- A summary of what you'd like to see added or changed -->
Ability to either:
- overload generic type definitions
  _or_
- define variadic type parameters for generic type aliases. (not sure how this would work)

## Use Cases

My specific, immediate need is to create a generic variable number of input type alias for `Intersection`. I could see other use cases though, and imagine others would find it useful.

The closest work around is if I define default type parameters, like:
```
type Intersection<A, B, C = {} , D = {}, E = {}, F = {}> = A & B & C & D & E & F;

// and use like
let foo: Intersection<{ prop1: number}, {prop2: string}>;

// it evaluates to
{ prop1: number } &
{ prop2: number } &
{ } &
{ } &
{ } &
{ }
```

## Examples

With overloads, the above type could be declared like:
```
type Intersection<A , B> = A & B;
type Intersection<A , B , C> = A & B & C;
type Intersection<A , B , C , D> = A & B & C & D;
type Intersection<A , B , C , D , E> = A & B & C & D & E;
type Intersection<A , B , C , D , E , F > = A & B & C & D & E & F;
```

I am not sure of a good syntax for the variadic type, it also seems like it would have a more limited use.


## Checklist

My suggestion meets these guidelines: ( I think )

* [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [x] This wouldn't change the runtime behavior of existing JavaScript code
* [x] This could be implemented without emitting different JS based on the types of the expressions
* [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).
Repository: TypeScript
Issue: Variable "name" in VSCode editor(intelli-sense) is showing incorrect information
Labels: Suggestion,Needs Proposal

*TS Template added by @mjbvz*

**TypeScript Version**: 4.0.0-dev.20200708

**Search Terms**
- javascript
- lib.dom
- globals

---

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->
<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: https://code.visualstudio.com/insiders/ -->

<!-- Use Help > Report Issue to prefill these. -->
- VSCode Version: 1.46.1
- OS Version: Windows 10

Steps to Reproduce:

1.  Add the following javascript code 

var name = "Hi";
console.log(name);
name = "Hello";
console.log(name);

2.  Hover over(Mouseover) the variable "name" (in any of the console log statements given above).......picture attached.

3. Expected: During mouse/hover over, variable "name" on the console statement should display "name" as a variable.
         
    Actual:   During mouse/hover over, variable "name" on the console statement is showing it as constant. (actually, it's not a constant). Because I'm able to modify the value of the variable "name" from "Hi" to "Hello". This explains "name" is implemented as a variable.

<!-- Launch with `code --disable-extensions` to check. -->

Does this issue occur when all extensions are disabled?: Yes

![VSCode bug](https://user-images.githubusercontent.com/68074514/87070866-07519b80-c237-11ea-8cd3-e8cb64c933cf.jpeg)
Repository: godot
Issue: GridMap is visible only on the first cull_mask layer
Labels: bug,topic:rendering,confirmed

<!-- Please search existing issues for potential duplicates before filing yours:	
https://github.com/godotengine/godot/issues?q=is%3Aissue	
-->

**Godot version:**
Godot Engine v3.2.2.stable.custom_build


**OS/device including version:**
5.7.0-3-MANJARO, OpenGL ES 3.0 Renderer: GeForce GTX 1050 Ti/PCIe/SSE2


**Issue description:**
GridMap is only visible on the first Camera's `cull_mask` layer. Once the first bit of the camera's `cull_mask` is disabled the entire grid disappears. Since it's not extending `VisualInstance` wouldn't it make more sense to not react to `cull_mask` layers?


**Steps to reproduce:**
1. Launch the project below
2. Press the checkbox to toggle camera's first `cull_mask` bit

**Minimal reproduction project:**
<!-- A small Godot project which reproduces the issue. Drag and drop a zip archive to upload it. -->
[gridmap-cull-master.zip](https://github.com/godotengine/godot/files/4899435/gridmap-cull-master.zip)
Repository: TypeScript
Issue: Suggestion: Add a way to hint typescript about basic function flow (call orders)
Labels: Suggestion,Awaiting More Feedback

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker.

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ, especially the "Common Feature Requests" section: https://github.com/Microsoft/TypeScript/wiki/FAQ

-->

## Search Terms

"control flow logic", "function call order", "static flow analysis"

## Suggestion
Add `flow` type, for statically declaring some flow logic (order of function calls)

## Use Cases
For example, we could tell typescript that the `constructor` of a React Component will be called before the `render`, and the render will be called before `componentDidMount`.

## Examples

```javascript
flow F;

let test: undefined | string;
F1~function first() { //the number of the flow indicates the order.
	test = 'wow';
}

F2~function second() {
	console.log(test.length); // <== ok, second() must come after first() so we know for sure that test was initialized.
}  
```

example2:

```javascript
flow LifeCycle;

class Test extends React.Component {
  LifeCycle1~constructor(){...}
  LifeCycle3~componentDidMount(){...}
  LifeCycle2~render(){...}
}
```

## Checklist

My suggestion meets these guidelines:

* [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [x] This wouldn't change the runtime behavior of existing JavaScript code
* [x] This could be implemented without emitting different JS based on the types of the expressions
* [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).
Repository: flutter
Issue: Scrolling jank in ListView when semantics are enabled
Labels: framework,engine,c: performance,a: accessibility,f: scrolling,customer: crowd,perf: speed,has reproducible steps,P2,found in release: 3.7,team-engine,triaged-engine

Hi i am following flutter and keep in touch with testing different apps developed in flutter.

But one major issue which is continuously under the ignorance and no thread i found on internet for now.. here is what i feel since 6 months of testing different apps.

Listview kind of scrolling jerks, specially when we have images posters like content with it. you can try this by doing create a list with image and some content list view must have content 3x of screen size.

just scroll it in medium speed, you will clearly feel jerks on screen, beside this the same test did on react native and its super smooth.

here is an example app on playstore (Flutter demo: CINEMA) you can download and test, but that i am sure its flutter bug  because all similar apps or with long list views this happens.

More examples in flutter official app: Flutter Gallery

1. Flutter Gallery -> (Crane A personalized travel app) -> vertical scroll listview in bottom (Jerk is clearly visible)
2. Flutter Gallery -> (Rally A personalized finance app) -> Login -> vertical scroll it (choppy scrolling Jerks)

Above examples are not debug all are on production playstore, on stackoverflow this is under discussion but everyone is doing just tricks which is not appropriate way to develop an production grade application.

beside this i also tested horizontal listviews and they work fine.

I am expecting senior flutter teams will take this issue serious and resolve this bug on high priority.
@ianloic @anaisbetts @sgraham @gmoothart @sethladd
Repository: flutter
Issue: Scrollable Hint Text
Labels: a: text input,platform-ios,framework,f: material design,a: accessibility,c: proposal,P3,team-text-input,triaged-text-input

<!-- 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 our the template below. Please read
     our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports
-->

## Use case

If the hint text of a textfield is larger than the space available, it cuts off the text with ellipses. In normal use-cases this is reasonable enough, but there are some where this isn't - particularly when dealing with accessibility & large text sizes.

If the hint text were to be scrollable in the same way that the non-hint-text is, that would eliminate this issue.

### With accessibility features off:
![image](https://user-images.githubusercontent.com/3103484/87099836-a064c000-c1ff-11ea-8a70-ed2847c5c740.png)

### With accessibility features on (large text + bold on iOS):
![image](https://user-images.githubusercontent.com/3103484/87099810-9478fe00-c1ff-11ea-8796-e5c5fba03b82.png)

(Note that these are the exact same application, and that pretty much any flutter app using textfields w/ hintText would display the same issue).

<!--
     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 alternative solutions you've considered. Is there a package
     on pub.dev/flutter that already solves this?
-->

## Proposal

For multi-line text fields this isn't as much as an issue, but for single-line ones this user experience could be improved by making the hint text scrollable horizontally.


<!--
     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: pytorch
Issue: libTorch cpp docs missing for Tensor::item()
Labels: module: docs,module: cpp,triaged

## 📚 Documentation

https://pytorch.org/cppdocs/api/classat_1_1_tensor.html#_CPPv4NK2at6Tensor4itemEv
and
https://pytorch.org/cppdocs/api/classat_1_1_tensor.html#_CPPv4I0ENK2at6Tensor4itemE1Tv

are both missing descriptions.

--------

I am trying to get a `float` out of a `Tensor` (that is a single element, kFloat32) on the GPU.

e.g.
`float x = x_tensor.item()`
However, this gives a compile-time error:
`error: cannot convert ‘c10::Scalar’ to ‘double’ in assignment`

Using `float x = x_tensor<float>.item()` compiles just fine, doesn't work either (program spins forever, probably waiting for CUDA kernel to end after a bad memory access or something).

What is the proper way to get the float out of the tensor (and back into main memory)? It prints just fine, so it must be doable.
I'd prefer to do it without printing and parsing or moving the entire tensor back to the CPU.

cc @yf225 @glaringlee @jlin27