sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: Compiler error doesn't show full query chain when evaluating const cycle
Labels: C-enhancement,A-diagnostics,T-compiler,A-const-eval

Consider the following code (both on stable 1.39.0 and nightly)

    trait Const {
        const A: i32 = Self::B;
        const B: i32 = Self::A;
        const C: i32 = Self::A;
    }
    
    impl <T> Const for T {}
    
    pub fn main() -> () {
        dbg!(i32::C);
    }

There's a cycle evaluating the constants `C -> A -> B -> A -> ...`

The `dbg!(i32::C)` line is the offending code which causes this cycle to be evaluated.

However, the emitted error message doesn't actually reference the usage `dbg!(i32::C)` which caused the evaluation, as below:

       Compiling playground v0.0.1 (/playground)
    error[E0391]: cycle detected when const-evaluating `Const::A`
     --> src/main.rs:4:24
      |
    4 |         const A: i32 = Self::B;
      |                        ^^^^^^^
      |
    note: ...which requires const-evaluating `Const::B`...
     --> src/main.rs:5:24
      |
    5 |         const B: i32 = Self::A;
      |                        ^^^^^^^
      = note: ...which again requires const-evaluating `Const::A`, completing the cycle
    note: cycle used when const-evaluating `Const::C`
     --> src/main.rs:6:24
      |
    6 |         const C: i32 = Self::A;
      |                        ^^^^^^^
    
    error: aborting due to previous error
    
    For more information about this error, try `rustc --explain E0391`.
    error: could not compile `playground`.
    
    To learn more, run the command again with --verbose.

This error could probably be improved by having an additional `note:` showing that the cycle was used when evaluating `dbg!(i32::C)`.

cc @oli-obk
Repository: opencv
Issue: Feature Request: 3+ dimension GpuMat
Labels: category: gpu/cuda (contrib),RFC

<!--
If you have a question rather than reporting a bug please go to http://answers.opencv.org where you get much faster responses.
If you need further assistance please read [How To Contribute](https://github.com/opencv/opencv/wiki/How_to_contribute).

Please:

* Read the documentation to test with the latest developer build.
* Check if other person has already created the same issue to avoid duplicates. You can comment on it if there already is an issue.
* Try to be as detailed as possible in your report.
* Report only one problem per created issue.


This is a template helping you to create an issue which can be processed as quickly as possible. This is the bug reporting section for the OpenCV library.
-->

<!-- Example
- OpenCV => 3.1
- Operating System / Platform => Windows 64 Bit
- Compiler => Visual Studio 2015
-->

##### Detailed description

To my knowledge, OpenCV still has no implementation for GpuMats with more than 2 dimensions.
This has been a feature of `cv::Mat` for a long time, but for some reason it has never been applied to `GpuMat`, which creates a disconnect when transferring algorithms from CPU implementations to GPU implementations.

This is an example of a `cv::Mat` function that creates a multi-dimensional matrix:
https://docs.opencv.org/master/d3/d63/classcv_1_1Mat.html#a156df5a1326dd5c30b187b0e721a5f57

<!-- to add code example fence it with triple backticks and optional file extension
    ```.cpp
    // C++ code example
    ```
 or attach as .txt or .zip file
-->
Repository: pytorch
Issue: Improved detection of repeated observers
Labels: oncall: quantization,low priority,triaged

## 🚀 Feature
We currently do not detect if the same observer/fake quant  is reused multiple times during calibration and quantization. This is always an error because observers collect statistics and the statistics are unique for every invocation of a module in the forward call.

## Motivation
Users are seeing this issue: particularly for floatfunctional modules, which are stateless in floating point but become stateful in fixed point.

Possible solution is to detect number of invocations of each observer module in a forward call. If any observer module is invoked more than once, an error should be reported. 

cc @jerryzh168 @jianyuh @raghuramank100 @jamesr66a @vkuzo @dzhulgakov
Repository: flutter
Issue: SemanticsDebugger should use hasEnabledState/isEnabled to determine if something is disabled
Labels: framework,a: accessibility,c: proposal,P3,team-framework,triaged-framework

The semantics debugger currently uses the presence of a tap handler to determine if a textfield or button is enabled/disabled. It should use the SemanticsFlags hasEnabledState/isEnabled to do that:

https://github.com/flutter/flutter/blob/master/packages/flutter/lib/src/widgets/semantics_debugger.dart
https://master-api.flutter.dev/flutter/dart-ui/SemanticsFlag/hasEnabledState-constant.html
https://master-api.flutter.dev/flutter/dart-ui/SemanticsFlag/isEnabled-constant.html
Repository: create-react-app
Issue: A feature to use package.json imports in create-react-app.
Labels: issue: proposal,needs triage

**Problem** : While making an atomic design pattern with create-react-app and a component driven folder structure, i want to use package.json imports to import my components in the app. Currently we can do absolute imports by creating an .env file and use it as from the node tree.
But package.json imports somehow doesn't work in create-react-app

Suppose my folder structure is like follows:
 ```-- components
    -header
      -leftheader.js
      -rightheader.js
      -header.js
      -package.json
```
And in package json:
 ```
 { "name" : "@header" }
```

Let's example in App.js i want to import headerComponent which is under header folder and App.js is in root level. I can do something like : 
```
import Header from "@header/header"
```

Currently this is not supported in create-react-app. I think this feature will be great for large projects where we can have multilevel component tree.
Repository: flutter
Issue: Add focusability to a11y of textfield
Labels: a: text input,c: new feature,framework,f: material design,a: accessibility,P2,team-text-input,triaged-text-input

The Textfield widget should provide information about its focusability to the semantics tree.

/cc @gspencergoog @darrenaustin
Repository: youtube-dl
Issue: Disney Plus
Labels: site-support-request,geo-restricted

<!--

######################################################################
  WARNING!
  IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################

-->


## Checklist

<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- First of, make sure you are using the latest version of youtube-dl. Run `youtube-dl --version` and ensure your version is 2019.11.05. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Make sure that all provided video/audio/playlist URLs (if any) are alive and playable in a browser.
- Make sure that site you are requesting is not dedicated to copyright infringement, see https://yt-dl.org/copyright-infringement. youtube-dl does not support such sites. In order for site support request to be accepted all provided example URLs should not violate any copyrights.
- Search the bugtracker for similar site support requests: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Finally, put x into all relevant boxes (like this [x])
-->

- [ X] I'm reporting a new site support request
- [ X] I've verified that I'm running youtube-dl version **2019.11.05**
- [x] I've checked that all provided URLs are alive and playable in a browser
- [ X] I've checked that none of provided URLs violate any copyrights
- [ X] I've searched the bugtracker for similar site support requests including closed ones


## Example URLs

<!--
Provide all kinds of example URLs support for which should be included. Replace following example URLs by yours.
-->

- Single video: https://www.disneyplus.com/video/79529cd0-f1cf-4eec-8b1d-ea1e1b76043b



## Description

<!--
This is newly launched in the United States
-->

WRITE DESCRIPTION HERE
Repository: pytorch
Issue: [jit] Dict construction fails at runtime
Labels: oncall: jit,triaged

This throws at runtime, it should at least be a compile error.

This is a little confusing since `IValue(std::tuple<Args...>)` is implemented but it's not implemented to recover a `TypePtr` from a `std::tuple<Args...>`
```cpp
#include <torch/script.h>

#include <iostream>
#include <memory>

int main(int argc, const char *argv[]) {
  // Dict[int, Tuple[Tensor, Dict[int, Tuple[Tensor, Tensor]]]]
  auto dict = c10::Dict<
      int64_t,
      std::tuple<
          torch::Tensor,
          c10::Dict<int64_t, std::tuple<torch::Tensor, torch::Tensor>>>>();
  torch::IValue dict_ivalue(dict);
  std::cout << dict_ivalue << "\n";
  return 0;
}
```

cc @suo
Repository: vscode
Issue: Git Merge Resolve Dialog
Labels: feature-request,merge-conflict

Issue Type: <b>Feature Request</b>

This is a request for the ability, when a user resolves all of the merge conflicts in a file, for VS Code to ask whether they would like to mark the entire file as resolved in Git.

VS Code version: Code 1.36.1 (2213894ea0415ee8c85c5eea0d0ff81ecc191529, 2019-07-08T22:56:38.504Z)
OS version: Darwin x64 19.0.0


<!-- generated by issue reporter -->
Repository: flutter
Issue: TimeOfDay.format returns 16:00 instead of 4:00 PM 
Labels: framework,f: material design,f: date/time picker,a: internationalization,f: cupertino,a: quality,customer: solaris,has reproducible steps,P2,found in release: 1.20,found in release: 2.3,team-design,triaged-design

## Steps to Reproduce

With the following sample app and with the time set to 12-hour support, the result of `TimeOfDay.fromDateTime(DateTime(2019, 1, 1, 16)).format(context)` will be `16:00` instead of `4:00 PM` (as expected). If the support locale is changed to `Locale('en', 'US')`, then we get the expect result.

```
import 'package:flutter/material.dart';
import 'package:flutter_localizations/flutter_localizations.dart';

Future<void> main() async {
  runApp(MaterialApp(
    localizationsDelegates: [
      GlobalMaterialLocalizations.delegate,
    ],
    supportedLocales: const [Locale('en', 'GB')],
    home: TimeOfDayFormatIssue(),
  ));
}

class TimeOfDayFormatIssue extends StatelessWidget {
  @override
  Widget build(BuildContext context) => Scaffold(
        body: Center(
          child: Text(TimeOfDay.fromDateTime(DateTime(2019, 1, 1, 16)).format(context)),
        ),
      );
}
```

**Target Platform:** iOS and Android

## Logs

```
flutter doctor -v
[✓] Flutter (Channel unknown, v1.10.7, on Mac OS X 10.14.6 18G95, locale en-NL)
    • Flutter version 1.10.7 at /Users/user/IdeaProjects/hue_blue/dev/flutter
    • Framework revision e70236e36c (6 weeks ago), 2019-10-02 09:32:30 -0700
    • Engine revision 9e6314d348
    • Dart version 2.6.0 (build 2.6.0-dev.0.0 1103600280)

 
[!] Android toolchain - develop for Android devices (Android SDK version 29.0.0-rc3)
    • Android SDK at /Users/user/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.0-rc3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
    ! Some Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses

[✓] Xcode - develop for iOS and macOS (Xcode 11.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.2, Build version 11B52
    • CocoaPods version 1.8.0

[✓] Android Studio (version 3.5)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 38.2.3
    • Dart plugin version 191.8423
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)

[✓] IntelliJ IDEA Community Edition (version 2019.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 35.2.2
    • Dart plugin version 191.6183.88

[✓] Connected device (2 available)
    • Miguel’s iPhone • 98b2b39514d586ebac7ee0537c84a7b23f8e46de • ios • iOS 13.2
    • iPhone X        • 50F6A837-0F74-41F7-BC8E-3B71EFE3DFD8     • ios • com.apple.CoreSimulator.SimRuntime.iOS-13-2 (simulator)

! Doctor found issues in 1 category.
```
Repository: godot
Issue: Unsigned uint64_t overflow in Variant.cpp
Labels: bug,discussion,topic:core

**Godot version:**
3.2.beta.custom_build. 7d836a7cc
**OS/device including version:**
Ubuntu 19.10
**Issue description:**
uint64_t argument is saved to int64_t(_data._int) which have different scope of values(-2^63,2^63-1), (0, 2^64) 
https://github.com/godotengine/godot/blob/62a09a2ee351430f9d55eee337691958e877cc68/core/variant.cpp#L2159-L2163
The overflow can be easily checked with this code:
```
Variant::Variant(uint64_t p_int) {
	if(p_int > 9223372036854775807U)
	{
		p_int--; // Put breakpoint here
		p_int++;
	}
	type = INT;
	_data._int = p_int;
}
```
Overflow seems to happens  mostly in Color functions which return 4 x uint16_t
![Zrzut ekranu z 2019-11-12 21-24-10](https://user-images.githubusercontent.com/41945903/68707855-d67b7280-0592-11ea-9632-8a650af6bc78.png)

To fix this, maybe will  be enough to add to union  _uint variable
```
	union {
		bool _bool;
		int64_t _int;
		uint64_t _uint;
		double _real;
		Transform2D *_transform2d;
		::AABB *_aabb;
		Basis *_basis;
		Transform *_transform;
		void *_ptr; //generic pointer
		uint8_t _mem[sizeof(ObjData) > (sizeof(real_t) * 4) ? sizeof(ObjData) : (sizeof(real_t) * 4)];
	} _data GCC_ALIGNED_8;
``` 



**Minimal reproduction project:**
https://github.com/qarmin/The-worst-Godot-test-project/archive/master.zip - should be enough
Repository: terminal
Issue: `TerminalInputModifierKeyTests` Don't work right on non-EN-US keyboard layouts
Labels: Product-Conhost,Issue-Bug,Area-CodeHealth

#### @j4james:

> Windows Terminal version (if applicable): commit [e2994ff](https://github.com/microsoft/terminal/commit/e2994ff8908f5a8418f24f2e2954a6c163f910b6)
> 
> 
> I'm used to having a few failures in the `TerminalInputModifierKeyTests`, and I know a couple of `TabTests` are blocked, but the rest of the tests I would usually expected to pass.
> 

> 
> In case you care about the `TerminalInputModifierKeyTests` too, I think those are failing for me because I have a UK keyboard - the test dies on the `VK_OEM_3` key. Here's a section of the test output where it fails:
> 
> ```
> Testing Key 0xc0
> Expected, Buffer = "", ""
> Verify: SUCCEEDED(StringCchLengthW(s_pwszInputExpected, STRSAFE_MAX_CCH, &cInputExpected))
> Error: Verify: AreEqual(cInputExpected, records.size()): Verify expected and actual input array lengths matched. - Values (0, 1) [File: C:\Users\James\CPP\terminal\src\terminal\adapter\ut_adapter\inputTest.cpp, Function: Microsoft::Console::VirtualTerminal::InputTest::s_TerminalInputTestCallback, Line: 87]
> TAEF: A crash with exception code 0xC0000409 occurred in module "ConAdapter.Unit.Tests.dll" in process "te.processhost.exe" (pid:13732).
> ```
> 
> This could be resolved by simply skipping that key the same way we skip `VK_OEM_2`, but it wouldn't surprise me if other international keyboards failed on other keys as well. I've been happy to accept that those are just expected failures for my particular setup.

(moved from #3536 )
Repository: flutter
Issue: On iOS, plugins should have access to a UiViewController
Labels: platform-ios,engine,a: existing-apps,P3,a: plugins,team-ios,triaged-ios

In any scenario (add-to-app or greenfield apps), we need to have a way of publishing an appropriate UiViewController to plugins so that they can be used in native APIs that push other native view controllers.

The current solutions are ugly. We either have to ask the app to provide it or we have to write ugly hacks within plugin code: https://github.com/flutter/plugins/blob/master/packages/google_sign_in/google_sign_in/ios/Classes/GoogleSignInPlugin.m#L210-L224.

Let's fix it.
Repository: rust
Issue: Reduce size of `target` directory
Labels: C-enhancement,T-compiler,T-cargo

The size of the `target` directory is becoming a severe problem for me. I use rust at work, and we have many services written in rust. The `target` directory for each service is typically 2-3 GB for a fresh build, and increases without bound due to the lack of GC, so that after a short period you're looking at 4 GB per service.

For reference, the final size of the musl-based statically compiled binaries we deploy is about 100 MB each, or 40x smaller than the intermediate artefacts, and the majority of that is debug info (once we separate out debug info it's down to maybe 30 MB).

I have a decently sized SSD (500GB), but even so, this very quickly gets out of hand. For various reasons I can only really afford to give 10 GB of space dedicated to the rust services, which means I can only do local development on two at a time (the other services are run by pulling prebuilt docker images with no possibility for local changes) and this is assuming I regularly nuke my `target` directories.

If I compress a 4 GB target directory with 7-zip, it compresses to about 700 MB, so even if all of the data is required, there's quite a bit of scope for reducing the disk usage. Also, maybe some intermediate artefacts can be deleted entirely and just recreated as needed?

I've seen elsewhere the suggestion to share the target directory between services, but:
1) I don't think that will actually help much here - the versions of dependencies often differ slightly between services and even a single service can reach the 10 GB limit on its own if left unchecked.
2) Due to the lack of GC, it will become impossible to nuke the target directory for a single service, so the only option will be to nuke *everything* and then rebuild it all from scratch.
Repository: TypeScript
Issue: [navtree] Only a single nameSpan listed for multiple declarations of interface
Labels: Suggestion,In Discussion,Domain: TSServer

<!-- 🚨 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.7.2

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**
- navtree
- tsserver

**Code**
For the TypeScript:

```ts
interface IFoo2 {
    foo: any;
}

interface IFoo2 {
    foo2: any;
}
```

1. Run a `navTree` request

**Bug:**
Two spans for `IFoo2` are returned but there is only a single `nameSpan `

```
{
    "text": "<global>",
    "kind": "script",
    "kindModifiers": "",
    "spans": [
        {
            "start": {
                "line": 1,
                "offset": 1
            },
            "end": {
                "line": 8,
                "offset": 2
            }
        }
    ],
    "childItems": [
        {
            "text": "IFoo2",
            "kind": "interface",
            "kindModifiers": "",
            "spans": [
                {
                    "start": {
                        "line": 1,
                        "offset": 1
                    },
                    "end": {
                        "line": 3,
                        "offset": 2
                    }
                },
                {
                    "start": {
                        "line": 5,
                        "offset": 1
                    },
                    "end": {
                        "line": 7,
                        "offset": 2
                    }
                }
            ],
            "nameSpan": {
                "start": {
                    "line": 1,
                    "offset": 11
                },
                "end": {
                    "line": 1,
                    "offset": 16
                }
            },
            ...
        }
    ]
}
```

For VS Code's tooling, we'd like to have a list of all namespans
Repository: TypeScript
Issue: `!.` after `?.` should be warned
Labels: Suggestion,Awaiting More Feedback

This is an anti-pattern on the current type system. And the compiler must not do quick fix so. `!.` after `?.` is simply replaceable with `?.` and should do so.

<!--
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.7.x-dev.20191105

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**

**Code**

```ts
document.querySelector('_')!.textContent!.split('') // old code
document.querySelector('_')?.textContent!.split('') ?? 0 // string[]
document.querySelector('_')?.textContent?.split('') ?? 0 // string[] | 0
```

**Expected behavior:**

```ts
document.querySelector('_')!.textContent!.split('') // old code
document.querySelector('_')?.textContent!.split('') ?? 0 // unsafe, warning
document.querySelector('_')?.textContent?.split('') ?? 0 // safe
```

**Actual behavior:**

```ts
document.querySelector('_')!.textContent!.split('') // old code
document.querySelector('_')?.textContent!.split('') ?? 0 // unsafe, no warning
document.querySelector('_')?.textContent?.split('') ?? 0 // safe
```

**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: pytorch
Issue: [FR] add generator= kwarg support for torch.randn and torch.rand
Labels: triaged,enhancement,module: random

All stochastic functions should accept `generator=`. These should as well.
Repository: pytorch
Issue: MultiStepLR does not return good lr after load_state_dict
Labels: module: optimizer,triaged

The param_group's lr's cannot be trusted if the optimizer state is not restored (and this can be okay, because optimizer buffers can double the checkpoint size).
In this line they are trusted if last_epoch is between milestones https://github.com/pytorch/pytorch/blob/master/torch/optim/lr_scheduler.py#L389

The closed_form formula is correct, since it does bisect_right to reset the lr value but for some reason it is not called.

I'm not sure if this is a problem with some assumed updated state of optimizer param_groups' lr or a problem with API of schedulers or sth else...

My use case is: I use MultiStepLR to drop learning rate at some #iterations milestones. After loading a checkpoint, the iteration index is restored, but the optimizer state is not, so I was relying on MultiStepLR to recompute the lr from the `last_epoch` field which is way greater than the values in milestones, so lr should be dropped.

cc @vincentqb @ezyang