sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Controlling vertical space between output elements.
Labels: ux,polish,under-discussion,notebook-output

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
[Friendly](https://github.com/friendly-traceback/friendly) is a program that can be used to help users understand the cause of tracebacks. A recent addition allows the insertion of interactive html buttons inside Jupyter notebooks to selectively show parts of the information available. Currently this is done by doing multiple calls to `display(HTML(...))`. This results in significant vertical white space between various output elements as shown in the following image.

![image](https://user-images.githubusercontent.com/629698/128565440-b7b1b411-f197-471c-a193-bed641c9f6ba.png)

The ideal output is that of Google Colab; the output for Visual Studio is the least desirable.  

Here is what is shown when one of the button is clicked to show the information.
![image](https://user-images.githubusercontent.com/629698/128566229-d2bb7f15-257f-4a27-b348-281916a82f59.png)


**Ideally, there should be a way to control/reduce/collapse the amount of vertical space between output elements in Visual Studio Code.**
Repository: excalidraw
Issue: PWA not installing on Samsung Browser 14.2.3.14
Labels: pwa

Hey folks!

I am trying to install the PWA on my Samsung Android devices and keep getting a "Download Error" and nothing happens. Other PWAs install fine, such as Photopea. I tried to clear my personal data and it still didn't work. Any ideas?

Tested devices:

- Samsung Galaxy M30 - Android 10 - Samsung Browser 14.2.3.14
- Samsung Galaxy Tab S6 Lite - Android 11 - Samsung Browser 14.2.3.14.

Thanks!
Repository: node
Issue: Node.js' repl should support source maps
Labels: source maps

<!--
Thank you for suggesting an idea to make Node.js better.

Please fill in as much of the template below as you're able.
-->

**Is your feature request related to a problem? Please describe.**

Source maps are not currently supported in the node console.

**Describe the solution you'd like**
Please describe the desired behavior.

When an exception happens while using Node.js in a repl, it should apply source maps to the stack trace.

**Describe alternatives you've considered**
Please describe alternative solutions or features you have considered.

N/A
Repository: rust
Issue: Inconsistent treatment of different kinds of trait bounds with GATs
Labels: T-compiler,GATs-triaged,A-GATs

I tried this code:

```rust
#![feature(generic_associated_types)]

trait Collection {
    type Iter<'a>: IntoIterator
    where
        <Self::Iter<'a> as IntoIterator>::Item: std::fmt::Debug;
}
```

This fails to compile with:

```
   Compiling playground v0.0.1 (/playground)
error[E0277]: the trait bound `<Self as Collection>::Iter<'a>: IntoIterator` is not satisfied
 --> src/lib.rs:4:5
  |
4 | /     type Iter<'a>: IntoIterator
5 | |     where
6 | |         <Self::Iter<'a> as IntoIterator>::Item: std::fmt::Debug;
  | |________________________________________________________________^ the trait `IntoIterator` is not implemented for `<Self as Collection>::Iter<'a>`
  |
help: consider further restricting the associated type
  |
3 | trait Collection where <Self as Collection>::Iter<'a>: IntoIterator {
  |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

error[E0277]: the trait bound `<Self as Collection>::Iter<'a>: IntoIterator` is not satisfied
   --> src/lib.rs:4:20
    |
4   |       type Iter<'a>: IntoIterator
    |                      ^^^^^^^^^^^^ the trait `IntoIterator` is not implemented for `<Self as Collection>::Iter<'a>`
    |
help: consider further restricting the associated type
    |
3   | trait Collection where <Self as Collection>::Iter<'a>: IntoIterator {
    |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

For more information about this error, try `rustc --explain E0277`.
error: could not compile `playground` due to 2 previous errors
```

[Playground](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=08b8ddfa747edd9690e7b0853446422f)

`aka/rrevenantt` on Discord discovered the following workaround, which to me seems like it should be treated the same as above. The only difference is the location of the bound - one using "inheritance style", the other as part of a where clause:

```rust
#![feature(generic_associated_types)]

trait Collection {
    type Iter<'a>
    where
        Self::Iter<'a>: IntoIterator,
        <Self::Iter<'a> as IntoIterator>::Item: std::fmt::Debug;
}
```

It's worth noting that the same issue exists without GATs. But `where` clauses on associated types are also feature gated under `generic_associated_types`.

This fails to compile:

```rust
#![feature(generic_associated_types)]

trait Collection {
    type Iter: IntoIterator
    where
        <Self::Iter as IntoIterator>::Item: std::fmt::Debug;
}
```

However this works on stable (lifting the bound to the trait itself):

```rust
trait Collection
where
    <Self::Iter as IntoIterator>::Item: std::fmt::Debug,
{
    type Iter: IntoIterator;
}

```
Repository: pytorch
Issue: [Testing] memory_format decorator
Labels: module: tests,triaged,module: memory format

## 🚀 Feature
We currently have decorators that allow us to parameterize tests on dtypes, devices, etc., but I don't see one for memory formats (i.e. torch.channels_last and torch.contiguous_format).

## Motivation

There are multiple operators where we want to check support for and propagation of these memory formats. There were some recent issues where [BatchNorm2D](https://github.com/pytorch/pytorch/pull/62773) and fused [conv2d_relu, conv2d_add_relu](https://github.com/pytorch/pytorch/pull/62482) aren't propagating them or are setting them incorrectly for the result Tensor which can cause performance regressions or errors. Having this decorator allows us to write separate tests for them and increase coverage.

## Pitch

Add ```@memoryFormat``` decorator to our suite of test decorators

## Alternatives

The usual copy-pasting for for-loops within tests.

## Additional context

N/A


cc @mruberry @VitalyFedyunin @walterddr @jamesr66a @ppwwyyxx
Repository: TypeScript
Issue: Provide Grammar Errors for JavaScript Files
Labels: Suggestion,Meta-Issue,Domain: JavaScript,Experimentation Needed,Fix Available,Rescheduled

Recently, [we started reporting high-confidence errors for typos as suggestions in the language service](https://github.com/microsoft/TypeScript/issues/41582). We believe that there is a set of grammar issues that are worth erroring on as well that are not reported today (e.g. duplicate block-scoped variables, extending multiple classes, rest parameters occurring before regular parameters, etc.)

Open questions:

* How do we implement this as part of our API?
* What sorts of errors are acceptable here?
* Would we be giving errors that run against the expectations of any popular runtimes, build tools, or syntax extensions?
Repository: youtube-dl
Issue: I cant get video format of mp3
Labels: question

<!--

######################################################################
  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:
- Look through the README (http://yt-dl.org/readme) and FAQ (http://yt-dl.org/faq) for similar questions
- Search the bugtracker for similar questions: http://yt-dl.org/search-issues
- Finally, put x into all relevant boxes (like this [x])
-->

- [x] I'm asking a question
- [x] I've looked through the README and FAQ for similar questions
- [x] I've searched the bugtracker for similar questions including closed ones


## Question

<!--
Ask your question in an arbitrary form. Please make sure it's worded well enough to be understood, see https://github.com/ytdl-org/youtube-dl#is-the-description-of-the-issue-itself-sufficient.
-->

in the docs it says
youtube-dl.exe --audio-format mp3 "https://www.youtube.com/watch?v=f2xGxd9xPYA&ab_channel=NoCopyrightSounds"
should download the mp3 format but anyways it saves it as webm file...
Repository: node
Issue: Support TLS session resumption in accordance with TLS 1.3 specs (using PSK)
Labels: tls

<!--
Thank you for suggesting an idea to make Node.js better.

Please fill in as much of the template below as you're able.
-->

**Is your feature request related to a problem? Please describe.**
Need support for TLS session resumption in accordance with the TLS 1.3 specs, which makes both Session IDs and Session Tickets obsolete in favor of in-band PSK.

Currently it appears that only the obsoleted methods are available within Node. It is possible that this is simply a documentation issue, but I don't see anything that indicates the ability to exchange the key in-band from the `ServerHello`. The documentation of PSK within the TLS module appears to only deal with out-of-band PSK only secure connections. 

Unfortunately the current documentation indicates that session tickets are compatible with TLS 1.3. Being unfamiliar with the spec it took a great deal of digging before I discovered that is not in line with the TLS 1.3 specification. At the very least it is a documentation issue, but I can't find anything that indicates in-band PSK exchange is supported within Node at all.

I understand that session resumption is simply a nice to have in HTTP land, but it appears that it is much more crucial for an FTP server which is what I am working to implement (via `ftp-srv`). The lack of session resumption can lead to a variety of issues with FTPS, the most obvious being a stern warning from Filezilla but more worrying is inconsistent behavior, timeouts, and transmission failures.

**Describe the solution you'd like**
Simplified integration of PSK based session resumption within the TLS module. Simpler said than done I'm sure, and I'm fairly ill equipped to tackle it myself without guidance. That said, I am willing to try if some pointers could be provided.

**Describe alternatives you've considered**
Writing the custom FTP server in another language, not a very appealing option since everything is already implemented in Node.
Repository: vscode
Issue: Suggestion Preview: Support previews that don't just insert text
Labels: feature-request,ghost-text

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes/No

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.59.0
- OS Version: win10 20h2

Steps to Reproduce:

https://user-images.githubusercontent.com/26390254/128575222-fc8347e0-8f4f-47e7-b7bb-660f7808ca88.mp4
Repository: pytorch
Issue: Compilation error with gcc11 and libstdc++11 (thread_id != operator removed)
Labels: triaged,module: mkldnn

## 🐛 Bug
Error originates from mkl-dnn which uses != operator on thread_id 
the != operator on thread_id has been removed in c++20 (was deprecated earlier)

A simpler fix is to do !( thread_id() == key.thread_id())


## To Reproduce

Steps to reproduce the behavior:

1. Build on fedora 34 with gcc11.2 and libstdc++11
1. python setup.py bdist_wheel

```
../third_party/ideep/mkl-dnn/src/common/primitive_cache.cpp:155:60: error: no match for ‘operator!=’ (operand types are ‘const std::thread::id’ and ‘const std::thread::id’)
  155 |     if (it == cache_mapper_.end() || it->first.thread_id() != key.thread_id())
      |                                      ~~~~~~~~~~~~~~~~~~~~~ ^~ ~~~~~~~~~~~~~~~
      |                                                         |                  |
      |                                                         |                  const std::thread::id
      |                                                         const std::thread::id
In file included from /usr/include/c++/11/utility:70,
                 from /usr/include/c++/11/tuple:38,
                 from /usr/include/c++/11/mutex:38,
                 from /usr/include/c++/11/future:38,
                 from ../third_party/ideep/mkl-dnn/src/common/primitive_cache.hpp:20,
                 from ../third_party/ideep/mkl-dnn/src/common/primitive_cache.cpp:17:
/usr/include/c++/11/bits/stl_pair.h:496:5: note: candidate: ‘template<class _T1, class _T2> constexpr bool std::operator!=(const std::pair<_T1, _T2>&, const std::pair<_T1, _T2>&)’
  496 |     operator!=(const pair<_T1, _T2>& __x, const pair<_T1, _T2>& __y)
      |     ^~~~~~~~
      
```
## Expected behavior

Builds successfully

## Environment

Please copy and paste the output from our
[environment collection script](https://raw.githubusercontent.com/pytorch/pytorch/master/torch/utils/collect_env.py)
(or fill out the checklist below manually).

You can get the script and run it with:
```
wget https://raw.githubusercontent.com/pytorch/pytorch/master/torch/utils/collect_env.py
# For security purposes, please check the contents of collect_env.py before running it.
python collect_env.py
```

 - PyTorch Version (e.g., 1.0):
 - OS (e.g., Linux):
 - How you installed PyTorch (`conda`, `pip`, source):
 - Build command you used (if compiling from source):
 - Python version:
 - CUDA/cuDNN version:
 - GPU models and configuration:
 - Any other relevant information:

## Additional context

<!-- Add any other context about the problem here. -->


cc @gujinghui @PenghuiCheng @XiaobingSuper @jianyuh @VitalyFedyunin
Repository: godot
Issue: 4.0 Vulkan run error
Labels: bug,topic:rendering

### Godot version

4.0.dev

### System information

Windows 10, 64bit, Intel HD 630 - Dell XPS 9575

### Issue description

I am unable to get 4.0 editor to start correctly, the Project Select window shows a black screen and the console is full of repeated vulkan errors.

Errors are as follows:
```
Godot Engine v4.0.dev.custom_build - https://godotengine.org
Vulkan API 1.2.162

WARNING: GENERAL - Message Id Number: 0 | Message Id Name: Loader Message
        ReadDataFilesInRegistry: Registry lookup failed to get layer manifest files.
        Objects - 1
                Object[0] - VK_OBJECT_TYPE_INSTANCE, Handle 2150701919728
     at: VulkanContext::_debug_messenger_callback (drivers\vulkan\vulkan_context.cpp:154)

Using Vulkan Device #1: AMD - Radeon RX Vega M GL Graphics


ERROR: Error (-3) creating shader module for stage: Compute
   at: (drivers\vulkan\rendering_device_vulkan.cpp:5163)
ERROR: Condition "!shader" is true. Returning: RID()
   at: RenderingDeviceVulkan::compute_pipeline_create (drivers\vulkan\rendering_device_vulkan.cpp:6470)
ERROR: Error (-3) creating shader module for stage: Compute
   at: (drivers\vulkan\rendering_device_vulkan.cpp:5163)
ERROR: Condition "!base_singleton->particles_shader.shader.version_is_valid(version)" is true.
   at: RendererStorageRD::ParticlesShaderData::set_code (servers\rendering\renderer_rd\renderer_storage_rd.cpp:5278)
ERROR: Condition "!shader" is true. Returning: RID()
   at: RenderingDeviceVulkan::uniform_set_create (drivers\vulkan\rendering_device_vulkan.cpp:5395)
ERROR: Error (-3) creating shader module for stage: Compute
   at: (drivers\vulkan\rendering_device_vulkan.cpp:5163)
ERROR: Error (-3) creating shader module for stage: Compute
   at: (drivers\vulkan\rendering_device_vulkan.cpp:5163)
ERROR: Error (-3) creating shader module for stage: Compute
   at: (drivers\vulkan\rendering_device_vulkan.cpp:5163)
ERROR: Error (-3) creating shader module for stage: Compute
   at: (drivers\vulkan\rendering_device_vulkan.cpp:5163)
ERROR: Condition "!shader" is true. Returning: RID()
   at: RenderingDeviceVulkan::compute_pipeline_create (drivers\vulkan\rendering_device_vulkan.cpp:6470)
ERROR: Condition "!shader" is true. Returning: RID()
```
These errors are constantly being pushed to the console. Does anyone have any idea what and why creating shader module for stage is generating an error

### Steps to reproduce

Nightly build - run

### Minimal reproduction project

_No response_
Repository: pytorch
Issue: `tools/autograd/derivatives.yaml` doesn't support methods on optional tensor
Labels: module: autograd,triaged,actionable,module: codegen

## 🐛 Bug

We should be able to access attributes from optional tensor in derivatives.yaml.

e.g.
```
- name: fwd_func(Tensor self, Tensor? bias) -> (Tensor)
  self, bias: bwd_func(self, bias.has_value()? bias.value().scalar_type() : self.scalar_type())
```

This is very similar to what we have there for optional ScalarType.
```
- name: cumprod(Tensor self, int dim, *, ScalarType? dtype=None) -> Tensor
  self: cumprod_backward(grad.to(self.scalar_type()), self, dim, result)
  result: "cumprod_jvp(self_t, self_p, result, dim).to(dtype.has_value() ? *dtype : self_p.scalar_type())"
```

However, this doesn't work with optional tensor. In generated code, we seem to be treating `bias` inconsistently.
1. In `torch/csrc/autograd/generated/Functions.cpp`, it's taking bias as an at::Tensor , so it doesn't like `has_value` / `value`.
2. Meanwhile, `torch/csrc/autograd/generated/VariableType_2.cpp` is generating code for bias as `optional<at::Tensor>`.

So in the end I can't access any tensor wrapped as an optional.

## Additional context

The motivation is to update `native_layer_norm_backward`. Currently we are taking `bias` as an input here, but we are only using `bias.scalar_type()`.

https://github.com/pytorch/pytorch/blob/e6a3154519721eec323b227ea8dfbd05409cfe37/aten/src/ATen/native/native_functions.yaml#L2393

note that even though `bias` should have the same scalar_type as with `weight`, it is possible for `weight` to be `None` while `bias` is present, so we can't get rid of `bias`.

So we would like to update the API to take a ScalarType instead of optional tensor. Where we would need to update autograd to pass the scalar_type of an optional tensor

https://github.com/pytorch/pytorch/blob/e6a3154519721eec323b227ea8dfbd05409cfe37/tools/autograd/derivatives.yaml#L1013


cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7
Repository: rust
Issue: LLVM ERROR: Do not know how to split the result of this operator!
Labels: A-LLVM,I-ICE,T-compiler,C-bug,A-target-feature

<!--
Thank you for finding an Internal Compiler Error! 🧊  If possible, try to provide
a minimal verifiable example. You can read "Rust Bug Minimization Patterns" for
how to create smaller examples.

http://blog.pnkfx.org/blog/2019/11/18/rust-bug-minimization-patterns/

-->

Greetings!

I'm currently trying to compile my code on a bare metal target. However I get a LLVM error when I do so.
The problem seems to come from libcore.

### Compilation command

```
RUSTFLAGS='-Zmacro-backtrace -Clink-dead-code' cargo +nightly build --verbose --target /home/luc/Desktop/dev/maestro/arch/x86/target.json --bin kernel
```

### Code

The full code is here: [https://github.com/llenotre/maestro/tree/module](https://github.com/llenotre/maestro/tree/module)

Cargo.toml:
```toml
[package]
name = "maestro"
version = "0.1.0"
authors = ["llenotre <llenotre@student.42.fr>"]
edition = "2018"

[lib]
name = "abi"
path = "src/mod_abi.rs"
crate-type = ["dylib", "rlib"]

[[bin]]
name = "kernel"
path = "src/kernel.rs"
```

arch/x86/target.json:
```
{
        "arch": "x86",
        "data-layout": "e-m:e-i32:32:32-f32:32:32-S16-p:32:32:32",
        "disable-redzone": true,
        "dynamic-linking": true,
        "executables": true,
        "features": "-mmx,-sse,+soft-float",
        "linker": "i686-elf-ld",
        "linker-flavor": "ld",
        "llvm-target": "i686-unknown-none",
        "os": "none",
        "panic-strategy": "abort",
        "target-c-int-width": "32",
        "target-endian": "little",
        "target-pointer-width": "32"
}
```


### Meta
<!--
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.
-->

`rustc --version --verbose`:
```
rustc 1.56.0-nightly (a6ece5615 2021-08-03)
binary: rustc
commit-hash: a6ece56152d8eb11e049e9fcce147b2859e12c92
commit-date: 2021-08-03
host: x86_64-unknown-linux-gnu
release: 1.56.0-nightly
LLVM version: 12.0.1
```

### Error output

```
LLVM ERROR: Do not know how to split the result of this operator!

error: could not compile `core`

Caused by:
  process didn't exit successfully: `rustc --crate-name core --edition=2018 /home/luc/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C debuginfo=2 -C metadata=5e0a9d73c690e322 -C extra-filename=-5e0a9d73c690e322 --out-dir /home/luc/Desktop/dev/maestro/target/target/debug/deps --target /home/luc/Desktop/dev/maestro/arch/x86/target.json -Z force-unstable-if-unmarked -L dependency=/home/luc/Desktop/dev/maestro/target/target/debug/deps -L dependency=/home/luc/Desktop/dev/maestro/target/debug/deps --cap-lints allow -Zsymbol-mangling-version=v0 -Zmacro-backtrace -Clink-dead-code` (exit status: 101)
```


</p>
</details>
Repository: terminal
Issue: User should be able to select a different color for the background at runtime (via the tab context menu?)
Labels: Help Wanted,Area-UserInterface,Product-Terminal,Issue-Task

### Right clicking on the tab windows to change color only changes color for the tab itself.  
Not the tab window background as claimed in your documentation here: https://docs.microsoft.com/en-us/windows/terminal/tips-and-tricks#color-a-tab
Repository: godot
Issue: View Frame Time FPS counter is not working on macOS on Intel IGP or when using Metal
Labels: bug,platform:macos,topic:rendering,topic:editor,topic:porting,confirmed

### Godot version

4.0.master

### System information

MacOS

### Issue description

Using the latest MoltenVK I'm not getting an FPS counter which works in master/4.0

I haven't ever seen it working.

### Steps to reproduce

1. Open master on Mac
2. Open viewport info
3. FPS counter will show the wrong values.


### Minimal reproduction project

_No response_
Repository: rust
Issue: Invalid syntax suggested when missing lifetime coincides with const generic
Labels: A-diagnostics,T-compiler

```rust
struct Foo<const BAR: usize> {
    foobar: &i32
}
```

On nightly 2021-08-06 the compiler suggests

```
help: consider introducing a named lifetime parameter
  |
1 | struct Foo<const 'a, BAR: usize> {
2 |     foobar: &'a i32
  |
```

The `const 'a, BAR: usize` has the `'a` inserted at the wrong place. It should be

```
help: consider introducing a named lifetime parameter
  |
1 | struct Foo<'a, const BAR: usize> {
2 |     foobar: &'a i32
  |
```