sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: deno
Issue: Proposal: Enhance custom inspect API
Labels: cli,suggestion

*Edit: the current proposal is here https://github.com/denoland/deno/issues/8099#issuecomment-757434256*

---

Probably should have thought of this when we did `Deno.customInspect` but we didn't.  As our console output has evolved, it makes it really hard to implement the same rich output.  For example if you have the following code:

```js
const h = new Headers();
h.append("key", "value");
console.log(h);
```

You would get something like the following output:

<img width="157" alt="a non coloured output string" src="https://user-images.githubusercontent.com/1282577/97069044-d6944700-1618-11eb-87f7-37365013b3ac.png">

Where as if you did:

```js
console.log({ key: "value" });
```

You would get:

<img width="115" alt="a coloured output string" src="https://user-images.githubusercontent.com/1282577/97069063-017e9b00-1619-11eb-940d-35428f56c4d9.png">

Which takes advantage of all the other benefits of the output algorithm.

Therefore if we had another symbol that returned a more structured set of information, we could use the same algorithms to colourise the output and otherwise pretty print it.  I would propose that we create `Symbol("Deno.richCustomInspect")` which would require a return of a tuple value of two strings.  The first string would be the _name_ for the inspector and the second value would be a JSON string, which would be parsed by the inspector.



So for example if I wanted a rich output for `Headers`, I would do something like this:

```js
class Headers {
  [Symbol.for("Deno.richCustomInspect]() {
    const output = {};
    for (const [key, value] of this[headersData]) {
      output[key] = value;
    }
    return [ "Headers", JSON.stringify(output) ];
  }
}
```

This would allow complex modelling of the internals, but ensure serialisation to a consistent format that can be handled by the inspector.
Repository: pytorch
Issue: Compile Pytorch with MAGMA Issue
Labels: needs reproduction,module: build,triaged

I tried to compile pytorch from source with magma. I compiled magma from source and it is installed in `/usr/local/magma` The following compilation log shows that magma lib can be found:

```
-- Compiling with MAGMA support
-- MAGMA INCLUDE DIRECTORIES: /usr/local/magma/include
-- MAGMA LIBRARIES: /usr/local/magma/lib/libmagma.so
-- MAGMA V2 check: 1
```

But when I tried `torch.svd(torch.rand(3,3).cuda())`, I received `RuntimeError: svd: MAGMA library not found in compilation. Please rebuild with MAGMA.` Any help on it is very appreciated.

cc @malfet @seemethere @walterddr
Repository: pytorch
Issue: Including AdaBound in the list of Optimizers. 
Labels: module: optimizer,triaged,enhancement

### 🚀 Feature
<!-- A clear and concise description of the feature proposal -->
Hello all, 
I would like to add Adabound to the list of existing optimizers in the torch.optim module. 
Here is the link to the paper - https://openreview.net/pdf?id=Bkg3g2R9FX 

### Motivation

<!-- Please outline the motivation for the proposal. Is your feature request related to a problem? e.g., I'm always frustrated when [...]. If this is related to another GitHub issue, please link here too -->
In most of my models, I realized Adam started off good but never converged or got stuck even after scheduling the learning rate, and if I started with SGD, the loss turned into NaNs soon. Out of curiosity, I changed the optimizer from Adam to SGD in the middle of the training and noticed better results, and upon researching more I came across the paper mentioned above. Therefore I believe it would be good to have the optimizer listed in PyTorch by default

### Pitch

<!-- A clear and concise description of what you want to happen. -->
I have already implemented the optimizer, once I get the green flag from your side, I will send the pull request. 

cc @vincentqb
Repository: flutter
Issue: [in_app_purchase] How to get transaction date of auto-renewed subscription 
Labels: d: api docs,p: in_app_purchase,package,team-ecosystem,P3,triaged-ecosystem

Hi there,

i am curious about how to get the date of when the subscription is renewed.

When i try to debug the plugin, i am only supposed to see the initial transaction date. 
And when the subscription is renewed the transaction date stays the same.


Am i supposed to handle this in my app or is there a way to see this?


Kind regards 

attex
Repository: opencv
Issue: Can not build macOS framework
Labels: question (invalid tracker),category: build/install,platform: ios/osx,incomplete

- OpenCV current master
- macOS Catalina 10.15.7
- Python 2.7.16
- cmake version 3.18.4
- Xcode 12.1 Build version 12A7403


I clone the repo, try to build the osx framework and get following error 

```
** BUILD FAILED **

The following build commands failed:
	CompileC platforms/osx/build/build/build-x86_64-macosx/modules/world/OpenCV.build/Release/opencv_world.build/Objects-normal/x86_64/opencv-onnx.pb.o modules/dnn/misc/onnx/opencv-onnx.pb.cc normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler
(1 failure)
============================================================
ERROR: Command '['xcodebuild', 'MACOSX_DEPLOYMENT_TARGET=10.13', 'ARCHS=x86_64', '-sdk', 'macosx', '-configuration', 'Release', '-parallelizeTargets', '-jobs', '16', '-target', 'ALL_BUILD', 'build']' returned non-zero exit status 65
============================================================
Traceback (most recent call last):
  File "/Volumes/Dev/XCode-openCV/please/opencv/platforms/ios/build_framework.py", line 148, in build
    self._build(outdir)
  File "/Volumes/Dev/XCode-openCV/please/opencv/platforms/ios/build_framework.py", line 122, in _build
    self.buildOne(target[0], target[1], main_build_dir, cmake_flags)
  File "/Volumes/Dev/XCode-openCV/please/opencv/platforms/ios/build_framework.py", line 255, in buildOne
    execute(buildcmd + ["-target", "ALL_BUILD", "build"], cwd = builddir)
  File "/Volumes/Dev/XCode-openCV/please/opencv/platforms/ios/build_framework.py", line 44, in execute
    retcode = check_call(cmd, cwd = cwd)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/subprocess.py", line 190, in check_call
    raise CalledProcessError(retcode, cmd)
CalledProcessError: Command '['xcodebuild', 'MACOSX_DEPLOYMENT_TARGET=10.13', 'ARCHS=x86_64', '-sdk', 'macosx', '-configuration', 'Release', '-parallelizeTargets', '-jobs', '16', '-target', 'ALL_BUILD', 'build']' returned non-zero exit status 65
```

seems to be same issues as [13759](https://github.com/opencv/opencv/issues/13759) so i fiddle with MACOSX_DEPLOYMENT_TARGET in platforms/osx/build_framework.py. same errors no matter the target

##### Steps to reproduce
git clone opencv
cd platforms/osx
python build_framework.py  build
Repository: create-react-app
Issue: installation error
Labels: stale

i am trying to install create-react-app using npx but it shows
![Capture123](https://user-images.githubusercontent.com/68518091/97087732-d1032500-1649-11eb-85b4-50c6d2fda035.JPG)
Repository: vscode
Issue: Add ability for extensions to have "checked" commands
Labels: feature-request,api,menus

I would like the ability to have a command in a menu show a checkmark, similar to:

![image](https://user-images.githubusercontent.com/641685/97088121-bbb3d980-15fc-11eb-9708-e7506f99757c.png)

We currently have an `enablement` "when clause" to control enable/disable, so maybe we can add a `checked` "when clause" that would work the same way.
Repository: go
Issue: runtime: deadlock at _cgo_wait_runtime_init_done
Labels: OS-Windows,NeedsInvestigation,compiler/runtime

<!--
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.15.3 windows/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
set GO111MODULE=
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\nguyenha\AppData\Local\go-build
set GOENV=C:\Users\nguyenha\AppData\Roaming\go\env
set GOEXE=.exe
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOMODCACHE=C:\Users\nguyenha\go\pkg\mod
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=C:\Users\nguyenha\go
set GOPRIVATE=
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=c:\go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=c:\go\pkg\tool\windows_amd64
set GCCGO=gccgo
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=D:\work\projects\mimic\mimic-core\go.mod
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0 -fdebug-prefix-map=C:\Users\nguyenha\AppData\Local\Temp\go-build126925810=/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.
-->

set CGO_ENABLED=1
set CC=clang
go build -buildmode=c-archive -o bin/libcrawler.lib -v core/export

Go side:
package main
import "C"

//export Init
func Init() {
	print("something")
}
// Required by CGO
//
func main() {

}


From C++ side:
#include <iostream>
#include "libcrawler.h"
#include <cstring>

using namespace std;

int main() {
  cout << "Hello, world1!" << endl;

 // x_cgo_notify_runtime_init_done(NULL);
  Init();
  cout << "Hello, world!" << endl;
  return 0;
}

I use clang-cl to compile c++ project
### What did you expect to see?
Can call Go function (Init()) from C++


### What did you see instead?
A deadlock at _cgo_wait_runtime_init_done. I tried to test by calling  x_cgo_notify_runtime_init_done(NULL); then I could pass the loop but crash later.
Repository: create-react-app
Issue: Autoprefixer doesn't work out of the box 
Labels: needs triage,issue: bug report

### Describe the bug
In the [Create React App doc](https://create-react-app.dev/docs/post-processing-css), it says 
> This project setup minifies your CSS and adds vendor prefixes to it automatically through Autoprefixer so you don’t need to worry about it.

This doesn't seem to be true however.

### Steps to reproduce 
```
npx create-react-app my-app
cd my-app
npm run build
```

When I inspect `build/static/css/main.xxx.chunk.css`, I expect to see
```css
.App-header {
  display: -webkit-box;
  display: -ms-flexbox;
  display: flex;
```

but I get
```css
.App-header {
  display: flex;
```
Repository: PowerToys
Issue: FancyZones: Drag to snap a window to multiple zones should use window position instead of mouse cursor
Labels: Idea-Enhancement,Product-FancyZones

## Currently FancyZones uses the mouse cursor position to determine whether a window should be snapped to multiple zones.  I suggest the center of the window be used instead.

When dragging a window to snap, it should snap to multiple zones if the window center is near an edge between zones.  Currently it depends on the mouse cursor position, which can be a little confusing.  It would also be more intuitive in scenarios where a window is dragged to clearly lie within one zone but the mouse cursor happens to lie near an edge.

---

If you'd like to see this feature implemented, add a 👍 reaction to this post.
Repository: go
Issue: x/pkgsite: surface module version release notes
Labels: NeedsInvestigation,FeatureRequest,pkgsite,UX

I review module release notes to decide whether I should upgrade a particular module now, later, or maybe never.

There is currently no standard way to represent release notes for module versions in the Go ecosystem (commit logs are a poor substitute for the first pass). Developers need to hunt around to work out how a particular module provides release notes (if at all). Eg:
- Github release notes (eg, [gRPC](https://github.com/grpc/grpc-go/releases)), or via some other hosting provider
- Changelog, CHANGES, and/or NEWS files
- README sub-section
- Separate project website
- ...
- Commit logs

Ideally there should be a simple, integrated way for module authors to make their release notes available on pkg.go.dev. For example, pkgsite currently integrates `README.md` (very useful). The version page (eg, https://pkg.go.dev/google.golang.org/grpc?tab=versions) could highlight actual changes for each version which quick links to jump to a particular module.

Providing a standard way (eg, file/format) for describing module version changes via pkg.go.dev would incentivise the community to adopt a single standard. This would make it a little easier for developers to decide which module or module version they should use. Good release notes might even be considered an indicator of module health.
Repository: flutter
Issue: Unable to load asset  from relative asset import outside of project directory on Android/web
Labels: platform-android,tool,a: assets,platform-web,has reproducible steps,P2,team-tool,triaged-tool,found in release: 3.19,found in release: 3.22

## Steps to Reproduce

If I try to use assets from a folder that's not within the project directory, the android app throws an error 'Unable to load asset' the first time that the app loads up. After a hot restart, the problem goes away.

Pubspec.yaml:
```
flutter:
  assets:
    - ../assets/

```

The app doesn't throw an error if I build it on iOS.

This seems to be a very weird bug, and I've tried everything from renaming every single thing, to running flutter clean dozens of times, to googling every possible solution.

Simply putting the assets folder inside the project directory seems to fix the error, but I need the assets to be outside of the project directory so I can access those assets for different applications.

Any help would be greatly appreciated!

`Flutter (Channel master, 1.24.0-4.0.pre.55, on Mac OS X 10.15.2 19C57 darwin-x64)`
Repository: flutter
Issue: Provide efficient way to access ui.Image in native platform code
Labels: c: new feature,framework,a: images,c: proposal,P3,team-framework,triaged-framework

need for ui.Image image data type for flutter channel which can get converted to bitmap in android.
Repository: PowerToys
Issue: [Run] Improve touch input. (scrolling, ...)
Labels: Product-PowerToys Run,Area-User Interface,Cost-Small,External Dependency-WinUI 3

Can't scroll with touch
Repository: rust
Issue: Internal lint: Warn unnecessary `{Hir,LocalDef,Def}Id` converts
Labels: C-enhancement,A-lints,T-compiler

Inspired by https://github.com/rust-lang/rust-clippy/pull/6222#issuecomment-716126347.
Consider this code:
```rust
let local_did = hir_id.owner.to_def_id().expect_local();
```

This is redundant since `hir_id.owner` is `LocalDefId` already.
It'd be great if we could detect and warn such a case as an internal lint.
Repository: pytorch
Issue: Specify input dimensions where they are not obvious
Labels: module: docs,triaged

## 📚 Documentation

It would be great if all modules where input dimensions are not obvious would specify them explicitly in documentations/docstrings. e.g. `nn.TransformerEncoder` has `src = torch.rand(10, 32, 512)` as part of example, but it took me some time to confirm that input should be (S,N,C).

cc @jlin27 @mruberry
Repository: pytorch
Issue: C++ Optimizer: remove warning on Optimizer::size method
Labels: module: optimizer,triaged,better-engineering

When optimizer groups were implemented in the c++ api,
warnings were placed on Optimizer methods that did not extend to multiple parameter groups,
e.g. in _**api/src/optim/optimizer.cpp**_

```
std::vector<Tensor>& Optimizer::parameters() noexcept {
   TORCH_WARN("Optimizer::parameters() will be removed in PyTorch 1.6");
   return param_groups_.at(0).params();
}
```
The warning makes sense since the returned vector of parameters omits any additional parameter groups.
But for the **_size()_** method, the count of parameters is accurate in the case of multiple parameter groups:

```
size_t Optimizer::size() const noexcept {
  TORCH_WARN("Optimizer::size() will be removed in PyTorch 1.6");
  size_t count = 0;
  for (const auto& group : param_groups_) {
    count += group.params().size();
  }
  return count;
}
```
Thanks

cc @vincentqb
Repository: TypeScript
Issue: `asserts` keyword does not enhance hoisted function type, works on functions assigned to a variable
Labels: Bug,Help Wanted

**TypeScript Version:**  4.0.2, 4.1.0-beta

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**
asserts function 

**Code**

```ts
interface LabelledFunction { label: string; }

function assignLabel(fn: () => unknown, label: string): asserts fn is LabelledFunction {
  Object.assign(fn, { label });
}

function a() { }
assignLabel(a, 'a');
console.info(a.label); // Property 'label' does not exist on type '() => void'.(2339)

const b = function () { };
assignLabel(b, 'b');
console.info(b.label); // works as expected

const c = () => { };
assignLabel(c, 'c');
console.info(c.label); // works as expected
```

**Expected behavior:**

At least in runtime code coming *after* `assignLabel(a, 'a');`, `a.label` should be accessible.

**Actual behavior:**

> Property 'label' does not exist on type '() => void'.(2339)

**Playground Link:** [link](https://www.typescriptlang.org/play?ts=4.1.0-beta#code/JYOwLgpgTgZghgYwgAgDJwEYQDbYgEwDEBXEBMYAexGQG9ltMcAuZAZzClAHMBuZAL4AoITFLkqNOGzbBuIdFmwAKGCFbKAlMgC8APmSkA1iEoB3EABoGTbKw5cQ3Ta2ltoYNsjXJgXxTh4ROIU1HRCyMgA8hgAVhDkAHRuciCqVnQ2SoKavELCoiGSyHBamcIp8gEqcNYA5HB1uUII1GyUeImgMJTKcImMSrnIAPQjyAAKUJQADh4Ansh1gzh1yPiUEF6mYMgQAB5+u2Fg83NLZfrIAG6UwPh1icoATADMrwCcmiKtIBzIGF03iKYTK9AEeUqClsygw9QwTTyv3anW6vQwA1szRabV2CCBlwM4MhMlS1WUCHqCEROL+HQgXRAPQpmKGvCAA)
Repository: material-ui
Issue: [Breadcrumbs] Collapsed component
Labels: new feature,component: breadcrumbs

<!-- Provide a general summary of the feature in the Title above -->
- Firstly, It appears now that after clicking the collapsed component to expand the breadcrumbs, we don't have any options to back from expand mode to collapsed mode? 
- Secondly, is there anyway to unactive the action onClick on collapsed component (for my project now I want to implement a pop-up when hovering on the collapsed component?).
<!-- Checked checkbox should look like this: [x] -->
- [x] The issue is present in the latest release.
- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.

## Summary 💡

<!-- Describe how it should work. -->

- Add an option (maybe a button) so that we can click to back from expand mode to collapsed mode. 
- Maybe we can pass a custom component as a collapsed component and added a prop (expanded or not) so that we can control the expand/collapsed of breadcrumbs from parent component.

## Benchmark

- https://blueprintjs.com/docs/#core/components/breadcrumbs
Repository: terminal
Issue: LVB Gridlines do not transit ConPTY (Win32 "underline", overline, left/right)
Labels: Help Wanted,Product-Conpty,Area-Output,Issue-Task,Priority-2

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

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!
-->

<!--
This bug tracker is monitored by Windows Terminal development team and other technical folks.

**Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**.
Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue.

If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link.

Please use this form and describe your issue, concisely but precisely, with as much detail as possible.

-->

# Windows 10, Windows Terminal, Version: 1.3.2651.0

```none
Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Windows Terminal version (if applicable):

Any other software?
```

# I use 

-- SetConsoleMode(hStdin, ENABLE_WINDOW_INPUT | ENABLE_LVB_GRID_WORLDWIDE )
-- I do "| COMMON_LVB_UNDERSCORE' on the attributes of CHAR_INFO 'line'
-- WriteConsoleOutput(... line );

I am 95% sure the rest of the code is valid -- because I can do colors, etc.

<!-- A description of how to trigger this bug. -->

# Expected behavior 

-- characters should be underlined.

<!-- A description of what you're expecting, possibly containing screenshots or reference material. -->

# Actual behavior 

-- no underline

<!-- What's actually happening? -->
Repository: rust
Issue: lazy_normalization_consts breaks unsize coercion in rare cases
Labels: T-compiler,C-bug,A-lazy-normalization,requires-nightly,F-generic_const_exprs

```rust
#![feature(lazy_normalization_consts)]
struct P<T: ?Sized>([u8; 1 + 4], T);

fn main() {
    let x: Box<P<[u8; 0]>> = Box::new(P(Default::default(), [0; 0]));
    let _: Box<P<[u8]>> = x;
}
```
This works on stable but fails with the following error when using `lazy_normalization_consts`
```
error[E0308]: mismatched types
 --> src/main.rs:6:27
  |
6 |     let _: Box<P<[u8]>> = x;
  |            ------------   ^ expected slice `[u8]`, found array `[u8; 0]`
  |            |
  |            expected due to this
  |
  = note: expected struct `Box<P<[u8]>>`
             found struct `Box<P<[u8; 0]>>`
```
For this to fail the struct has to contain a type referencing an unevaluated constant, `struct P<T: ?Sized>([u8; 5], T)` does work.

assigning to myself, but won't get to this right away. If you are interested in working on this before that feel free to do so.

cc @nikomatsakis @varkor