sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: TypeScript
Issue: Docs: Incorrect option in wiki doc JavaScript Language Service in Visual Studio
Labels: Docs

Looking at https://github.com/microsoft/TypeScript/wiki/JavaScript-Language-Service-in-Visual-Studio#-support-for-es6-and-beyond it states `enableAutoDiscovery` as an option in a `tsconfig.json` file.

But looking at https://www.typescriptlang.org/tsconfig it does not seem to be an option available at all. Not on https://www.typescriptlang.org/docs/handbook/compiler-options.html either.

I thus wonder if this is incorrect in that wiki, and if in general the docs in the wiki article are quite outdated and could use an overhaul? They do not seem to be exactly described the same as in https://code.visualstudio.com/docs/nodejs/working-with-javascript#_global-variables-and-type-checking and https://code.visualstudio.com/docs/languages/jsconfig#_jsconfig-options
Repository: godot
Issue: `OS.get_time_zone_info()` doesn't return complete information on HTML5
Labels: bug,platform:web,topic:porting

### Godot version

 v3.3.stable.official

### System information

Ubuntu 20.04.2 LTS

### Issue description

When running from the editor, OS.get_time_zone_info() returns:
`{bias:-180, name:-03}`
when exporting to html the same function in the same machine returns:
`{bias:-180, name:}`

calling timedatectl on the terminal returns:
```
Local time: ter 2021-07-13 09:07:31 -03   
Universal time: ter 2021-07-13 12:07:31 UTC   
RTC time: ter 2021-07-13 12:07:31       
Time zone: America/Sao_Paulo (-03, -0300)
System clock synchronized: yes                           
NTP service: active                        
RTC in local TZ: no                            
```

it would be good to have the same return in both cases and if possible with the correct time zone name

### Steps to reproduce

write

`print(OS.get_time_zone_info())`

on any script

### Minimal reproduction project

_No response_
Repository: godot
Issue: WorldEnvironment node in Canvas mode causes visual streaks in editor when Canvas Max Layer is negative
Labels: bug,topic:editor,confirmed

### Godot version

3.3.2 stable (also 3.3 stable)

### System information

Windows 10, GLES2/GLES3

### Issue description

In a WorldEnvironment node, setting the background mode to "canvas" and then setting the canvas max layer to be a negative value causes lasting visual streaks upon zooming or panning the editor view (fixed upon restarting project). Also the background is black upon playing the scene.

![image](https://user-images.githubusercontent.com/8592222/125463910-07c5492c-7ed2-47e6-8c24-a21ea2bcefd2.png)


### Steps to reproduce

The reproduction project will show the glitch when the 3D editor view for the main node is zoomed or panned.

There is a Sprite3D and a camera for demonstration, but these are not necessary for the problem to occur. The coordinate lines will glitch even if everything else is deleted.

### Minimal reproduction project

[canvas_mode_bug.zip](https://github.com/godotengine/godot/files/6809352/canvas_mode_bug.zip)
Repository: rust
Issue: "expect slice, found Vec" error is unrelated to the actual issue
Labels: C-enhancement,A-diagnostics,T-compiler,D-newcomer-roadblock

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.

If you cannot produce a minimal reproduction case (something that would work in
isolation), please provide the steps or even link to a repository that causes
the problematic output to occur.
-->

Given the following code: https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=80af81f48a03fb52f7c948a4fd4c686e

```rust
fn takes_slice(_: &mut [u8]) {}

fn main() {
    let mut v = vec![0_i32];
    takes_slice(&mut v);
}
```

The current output is:

```
error[E0308]: mismatched types
 --> src/main.rs:5:17
  |
5 |     takes_slice(&mut v);
  |                 ^^^^^^ expected slice `[u8]`, found struct `Vec`
  |
  = note: expected mutable reference `&mut [u8]`
             found mutable reference `&mut Vec<i32>`
```

<!-- The following is not always necessary. -->
Ideally the output should look like:

```
error[E0308]: mismatched types
 --> src/main.rs:5:17
  |
5 |     takes_slice(&mut v);
  |                 ^^^^^^ expected slice `[u8]`, found slice `[i32]`
  |
  = note: expected mutable reference `&mut [u8]`
             found mutable reference `&mut [i32]`
```

<!--
If the problem is not self-explanatory, please provide a rationale for the
change.
-->

The compiler seems to only perform Deref coercion if the types match exactly - that makes sense if the code compiles, but for diagnostic, I think it should try harder to perform deref coercion if it makes the types match more closely.

<!--
If dramatically different output is caused by small changes, consider also
adding them here.

If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions. The output might also be
different depending on the Edition.
-->
Repository: flutter
Issue: [intl] NumberFormat big with FontWeight 
Labels: framework,a: internationalization,a: typography,has reproducible steps,P2,found in release: 2.2,found in release: 2.4,team-framework,triaged-framework

## Steps to Reproduce

1. Run `flutter create bug`.
2. Update the files as follows: ... 
Add a custom font in pubspec.yaml 
```
  fonts:
    - family: "Jost"
      fonts:
        - asset: "assets/fonts/google/Jost/Jost-Regular.ttf"
          weight: 400
        - asset: "assets/fonts/google/Jost/Jost-Medium.ttf"
          weight: 500
        - asset: "assets/fonts/google/Jost/Jost-SemiBold.ttf"
          weight: 600
        - asset: "assets/fonts/google/Jost/Jost-Bold.ttf"
          weight: 700
    - family: "JostBold"
      fonts:
        - asset: "assets/fonts/google/Jost/Jost-Bold.ttf"
          weight: 700
```

3. Display text with :
```
Text(
  NumberFormat().format(10000),
  style: const TextStyle(
    fontFamily: 'Jost',
    fontWeight: FontWeight.bold,
  ),
)
```
(my Locale was Fr_FR)

**Expected results: (10<visible space>000) **
<img width="98" alt="Capture d’écran 2021-07-13 à 16 21 06" src="https://user-images.githubusercontent.com/1594035/125468693-082c87ce-2cb3-4671-ac6d-0bb9f74e7e7c.png">

**Actual results:**
<img width="94" alt="Capture d’écran 2021-07-13 à 16 20 55" src="https://user-images.githubusercontent.com/1594035/125468794-b6047c69-cabf-4597-bba4-7b06e1a23696.png">
=> space separator was swallowed

So :
 - Number format outputs non breakable spaces
 - When using fontWeight to override the FontWeight, flutter chooses the right font variant file from pubspec.yaml BUT inject somehow a bug by not respecting the letter spacing (here non secable spaces)
 - This can be verified easily because the output is as expected (visible space) when using : 
 ```
Text(
  NumberFormat().format(10000).toString(),
  style: const TextStyle(
    fontFamily: 'JostBold'
  ),
)
```
- So this bug seems to prevent the use of FontWeight totally for me, and I must use fontFamily to properly switch font variant

Video showing the problem :
- step 1 : `fontFamily:'Jost'` = ok
- step 2 : `fontFamily:'Jost', fontWeight: FontWeight.bold` = KO
- step 3: `fontFamily:'JostBold'` = ok

https://user-images.githubusercontent.com/1594035/125472587-4f290d02-f3f2-45f9-b7c3-bc841ede1663.mov



Or Am i missing something ? Thanks :)

<details>
 ```
Flutter 2.2.2 • channel stable • https://github.com/flutter/flutter.git
Framework • revision d79295af24 (5 weeks ago) • 2021-06-11 08:56:01 -0700
Engine • revision 91c9fc8fe0
Tools • Dart 2.13.3
```
</details>
Repository: rust
Issue: Compiler should warn if "unused" shadowed variable is actually used in inner block
Labels: A-lints,T-lang,C-feature-request

Given the following code: https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018

```rust
pub fn main() {
    let mut iter = [1u8, 3, 5, 7].iter().zip([2u8, 4, 6, 8].iter());
    while let Some((a,b)) = iter.next() {
        println!("a: {}, b: {}", a, b);
        if let Some((_a,b)) = iter.next() {
            println!("a: {}, b: {}", a, b);
        }
    }
}
```

The current output is: no warnings.

Ideally the output should look like:

```
Line 5: variable `_a` is marked as unused but shadows variable `a` from line 3.

Did you forget to change `_a` back to `a`?

If not, use `_` instead of `_a` in line 5.
```
Rationale: This might happen if initially `a` from Line 5 wasn't used in the inner block (e.g. it was just `println!("b: {}", b);`). In that case the compiler warns about the unused variable `a` and tells me to change it to `_a` to indicate that it's not used. Equally, the compiler should tell me now if I start using it again and forget to change it back!

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

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

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: flutter
Issue: Calling TextEditingController.clear() does not call formatEditUpdate of formatter 
Labels: a: text input,framework,has reproducible steps,P2,found in release: 2.2,found in release: 2.4,team-framework,triaged-framework

Calling `TextEditingController.clear()` does not call `formatEditUpdate` of TextInputFormatter's.
This makes it difficult to keep the formatter state in sync with TextEditingController. 

Example case:

Some TextInputFormatter allows you to format the phone number in something like (555) 333-44-55, but it also has a method to get the phone in its original form without formatting like 555334455. There is also a field clear button that calls the method TextEditingController.clear(). When you click on this button, the text field will be erased, but this will not call the method formatEditUpdate, so it is still possible to get the value from the formatter. 

There is a way out to force the programmer to also call some cleanup method on the formatter itself, but it is quite difficult to keep track of this.
Repository: godot
Issue: Version control diff viewer doesn't display changes for already staged files
Labels: bug,topic:editor

### Godot version

3.4.beta

### System information

Windows 10

### Issue description

![image](https://user-images.githubusercontent.com/17108460/125482384-fb6a7648-d957-469f-8942-ec7e9ab6e24d.png)

Expected to display diff for staged files like in VS Code:

![image](https://user-images.githubusercontent.com/17108460/125482527-e67aa240-c780-491b-8725-9882cde9850b.png)

The issue may be specific to [Git plugin](https://github.com/godotengine/godot-git-plugin) itself and not the editor, so feel free to transfer the issue if this is the case.

### Steps to reproduce

1. Install [Git plugin](https://github.com/godotengine/godot-git-plugin) and set it up.
2. Stage all files (or one file).
3. Click on the file in the commit dock.
4. See diff window is empty.

### Minimal reproduction project

N/A
Repository: pytorch
Issue: Many reduction operators do not support reducing over multiple dimensions
Labels: triaged,module: numpy,module: reductions,module: python array api

The following reduction operators should be updated to allow reducing over multiple dimensions.

- [ ] [torch.all](https://pytorch.org/docs/master/generated/torch.all.html#torch.all)
- [ ] [torch.any](https://pytorch.org/docs/master/generated/torch.any.html#torch.any)
- [ ] [torch.prod](https://pytorch.org/docs/master/generated/torch.prod.html#torch.prod)
- [ ] [torch.quantile](https://pytorch.org/docs/master/generated/torch.quantile.html#torch.quantile)
- [ ] [torch.nanquantile](https://pytorch.org/docs/master/generated/torch.nanquantile.html#torch.nanquantile)
- [ ] [torch.aminmax](https://pytorch.org/docs/master/generated/torch.aminmax.html#torch.aminmax)

For the following operators, adding support for reducing over multiple dimensions is blocked on the following issue https://github.com/pytorch/pytorch/issues/61490

- [ ] [torch.max](https://pytorch.org/docs/master/generated/torch.max.html#torch.max)
- [ ] [torch.min](https://pytorch.org/docs/master/generated/torch.min.html#torch.min)
- [ ] [torch.median](https://pytorch.org/docs/master/generated/torch.median.html#torch.median)
- [ ] [torch.nanmedian](https://pytorch.org/docs/master/generated/torch.nanmedian.html#torch.nanmedian)
- [ ] [torch.mode](https://pytorch.org/docs/master/generated/torch.mode.html#torch.mode)

**Related Issues**
- [ ] https://github.com/pytorch/pytorch/issues/56586
- [ ] https://github.com/pytorch/pytorch/issues/53900
- [ ] https://github.com/pytorch/pytorch/issues/61453

cc @mruberry @rgommers @heitorschueroff @pmeier @asmeurer @leofang @AnirudhDagar @asi1024 @emcastillo @kmaehashi
Repository: go
Issue: cmd/go: document system setup for cross compiling between linux architectures
Labels: Documentation,NeedsFix

<!--
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
1.16.6
</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="arm64"
GOBIN=""
GOCACHE="/root/.cache/go-build"
GOENV="/root/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="arm64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_arm64"
GOVCS=""
GOVERSION="go1.16.6"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build1439812787=/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.
-->

Trying to cross compile a simple program that uses `github.com/mattn/go-sqlite3` (which requires CGO) from `linux/arm64` to `linux/amd64` using docker on an M1 macbook, fails due to an incorrect flag passed to `gcc`

#### Some extra info:
Host OS: macOS 11.4 
Host processor: Apple M1
Docker desktop version: `3.5.2 (66501)`
Docker engine version: `20.10.7`
gcc version: `gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424`

The program

```go
package main

import (
	"database/sql"

	_ "github.com/mattn/go-sqlite3"
)

func main() {
	db, err := sql.Open("sqlite3", "tmp.sqlite3")
	if err != nil {
		panic(err)
	}
	_, err = db.Exec("SELECT 1")
	if err != nil {
		panic(err)
	}
}
```

The dockerfile

```dockerfile
FROM golang:1.16.6-alpine3.14

WORKDIR /app

RUN apk --no-cache add gcc libc-dev

COPY . .
RUN go mod download

RUN GOOS=linux GOARCH=amd64 CGO_ENABLED=1 go build -o main .
```

### What did you expect to see?

The compilation succeed

### What did you see instead?
 > [6/6] RUN GOOS=linux GOARCH=amd64 CGO_ENABLED=1 go build -o main .:                                                                                    
#10 0.294 # runtime/cgo
#10 0.294 gcc: error: unrecognized command-line option '-m64'
Repository: pytorch
Issue: Proposal: allow using axis, axes, dim and dims interchangeably 
Labels: triaged,needs design,module: ux,module: python array api

From offline discussion with @mruberry, we should allow axis, axes, dim and dims to be used interchangeably so we can keep BC while implementing the Python Array API Standard which uses axis instead of dim. And since many operators take a list of dimensions, axes and dims are a natural extension.

cc @mruberry @rgommers @pmeier @asmeurer @leofang @AnirudhDagar @asi1024 @emcastillo @kmaehashi @heitorschueroff
Repository: pytorch
Issue: Add `map_location` arg for c10d collective comms
Labels: oncall: distributed,triaged

## 🚀 Feature
<!-- A clear and concise description of the feature proposal -->
Following #61539, we can add a `map_location` argument to the other c10d collective communications that use `_tensor_to_object()`. This includes `all_gather_object()`, `gather_object()`, and `scatter_object_list()`. The `map_location` argument is forwarded to `torch.load()` and specifies where to load tensors contained in the communicated object upon being received. If `map_location=None`, then the default behavior is to load the tensors to the device on which they were saved.

## 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 -->
The default behavior is not ideal when using NCCL backend since then contained tensors are loaded to the source device instead of the destination device or destination CPU, inevitably requiring an extraneous data transfer. This issue primarily manifested through `broadcast_object_list()` since NCCL supports `broadcast()`. Nonetheless, it may be beneficial to have this `map_location` argument generally to avoid such extraneous data transfers.

## Pitch

<!-- A clear and concise description of what you want to happen. -->
We can follow the `broadcast_object_list()` example. The change would involve adding the `map_location` argument to `all_gather_object()`, `gather_object()`, and `scatter_object_list()` and to augment their respective tests, similar to `test_broadcast_object_list_map_location()` in `distributed_test.py`.


cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @agolynski @SciPioneer @H-Huang @mrzzd @cbalioglu @gcramer23
Repository: vscode
Issue: [semantic highlighting] Source language suffix should be added to semantic token fallback scopes when looked up
Labels: feature-request,semantic-tokens

Version: 1.58.0 (user setup)
Commit: 2d23c42a936db1c7b3b06f918cde29561cc47cd6
Date: 2021-07-08T06:54:55.083Z
Electron: 12.0.13
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: 8.9.255.25-electron.0
OS: Windows_NT x64 10.0.19043

This is based on the following issue reported against the C/C++ Extension: https://github.com/microsoft/vscode-cpptools/issues/7773

Themes can provide colorization specific to a language, using the language ID as a suffix on the TextMate scope.  (i.e. `storage.type.cs` or `variable.language.wildcard.java` - examples taken from default themes).  However, when VS Code looks up [fallback TextMate scopes for semantic tokens](https://code.visualstudio.com/api/language-extensions/semantic-highlight-guide#semantic-token-scope-map), it does not appear to append the language ID to that scope.  Providing separate scopes for each language ID supported by the C/C++ Extension (including for all default fallback scopes) in our `package.json`, appears to work around the issue (an example in [this comment](https://github.com/microsoft/vscode-cpptools/issues/7773#issuecomment-876705521)).  However, the proper fix would seem to be for VS Code to always append language ID's when looking up semantic token fallback scopes.
Repository: flutter
Issue: Intermittent failures in web_tool_tests due to failure to connect to chrome
Labels: team,tool,P2,team-tool,triaged-tool

The failures happened in HHH flutter web bot (running heads of engine, flutter, and dart SDK) that runs flutter web_tool_tests.

Related: flutter/flutter#85043
Example: https://ci.chromium.org/ui/p/dart/builders/ci.sandbox/flutter-engine-linux/13586/overview
```
  Failed to establish connection with the application instance in Chrome.
  This can happen if the websocket connection used by the web tooling is unable to correctly establish a connection, for example due to a firewall.
  
  #0      throwToolExit (package:flutter_tools/src/base/common.dart:10:3)
  #1      ResidentWebRunner.run (package:flutter_tools/src/isolated/resident_web_runner.dart:328:7)
  <asynchronous suspension>
  #2      AppDomain.launch.<anonymous closure> (package:flutter_tools/src/commands/daemon.dart:595:9)
  <asynchronous suspension>
  #3      AppDomain.launch (package:flutter_tools/src/commands/daemon.dart:593:5)
...
```
Repository: TypeScript
Issue: Auto import option to make imports relative only within current directory
Labels: Suggestion,Awaiting More Feedback

# Suggestion

<!--
  Please fill in each section completely. Thank you!
-->

## 🔍 Search Terms

<!--
  💡 Did you know? TypeScript has over 2,000 open suggestions!
  🔎 Please search thoroughly before logging new feature requests as most common ideas already have a proposal in progress.
  The "Common Feature Requests" section of the FAQ lists many popular requests: https://github.com/Microsoft/TypeScript/wiki/FAQ#common-feature-requests

  Replace the text below:
-->

`import relative`

## ✅ Viability Checklist

<!--
   Suggestions that don't meet all these criteria are very, very unlikely to be accepted.
   We always recommend reviewing the TypeScript design goals before investing time writing
   a proposal for ideas outside the scope of the project.
-->
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, new syntax sugar for JS, etc.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).


## ⭐ Suggestion

<!-- A summary of what you'd like to see added or changed -->
An option added to the `importModuleSpecifier` preference to make imports absolute if and only if their relative path would begin with `../`.

## 📃 Motivating Example

<!--
  If you were announcing this feature in a blog post, what's a short explanation that shows
  a developer why this feature improves the language?
-->
At my workplace, our least favourite relative imports are the ones that venture out of the current directory (i.e. they begin with any number of `../`). But there are times where we want relative imports within the current directory (i.e. beginning with `./`). I don't see any existing options that support this exact style of import, including `project-relative`.

In general, the motivation for not using relative imports beginning with `../` is that it makes moving code files around more difficult.

## 💻 Use Cases

<!--
  What do you want to use this for?
  What shortcomings exist with current approaches?
  What workarounds are you using in the meantime?
-->
`shortest` and `relative` are obviously not correct since they have no qualms about this issue.
`non-relative` is my current workaround, which only adds absolute imports.
`project-relative` I tried, but based on what I discovered and my understanding of the description in the tooltip, my guess is that it only adds absolute imports for files that are located outside of the workspace folder.
Repository: excalidraw
Issue: Support "Zoom To Fit All elements" as a UI action
Labels: enhancement,BLOCKED ON spec/design

This is a useful feature especially when the drawing gets larger and the user wants to fit all in the viewport. Instead of having it behind a shortcut(Shift+1) only, having a UI action as well would be great.

Note: requires speccing out in terms of UI/UX.