sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vue
Issue: `src` attribute of `img` inside `picture` should be set after `img` is appended to `picture` to avoid unnecessary requests
Labels: improvement,browser quirks

### Version
2.6.11

### Reproduction link
[https://codepen.io/CaseJnr/pen/VwvWbPE](https://codepen.io/CaseJnr/pen/VwvWbPE)







### Steps to reproduce
1. Open the codepen link in safari

2. Inspect the element

3. Reduce the view width below 900px and refresh the page

4. You will notice that both the red and blue image is requested.

5. Comment out the vue instance and refresh the page.

6. You will notice only the red image is requested (as expected).




### What is expected?
Only the required picture resource is requested. 

### What is actually happening?
Both of the pictures resources are requested, causing redundant downloads.

---
In Safari, adding a vue instance to any page will cause redundant picture sources to be requested. The picture element will behave correctly if the vue instance is removed.


E.g.


&#x3C;picture&#x3E;
    &#x3C;source media=&#x22;(max-width: 900px)&#x22; srcset=&#x22;small.jpg&#x22;&#x3E;
    &#x3C;img src=&#x22;large.jpg&#x22; alt=&#x22;&#x22;&#x3E;
  &#x3C;/picture&#x3E;



By default, only the small.jpg should be requested when the view width is below 900px. However, if a vue instance is added to the page, then both the small.jpg and large.jpg are requested.

The mobile inspector shows the small.jpg request initiator as the page (expected). The large.jpg initiator is actually the vue instance.

<!-- generated by vue-issues. DO NOT REMOVE -->
Repository: vscode
Issue: Custom editor autosave menubar state not updated properly 
Labels: bug,help wanted,custom-editors

Hi @mjbvz @jrieken,

I've been catching up with the daily updates, thanks for them btw.
While working on our stuff, I've been noticing some issues on VSCode.
Probably they're known issues but I'm sharing here in case they've been missed somehow.
I'm able to reproduce them on both our code and [this](https://github.com/mjbvz/vscode-extension-samples/tree/custom-editor-examples/custom-editor-sample) code.

**Linux and Windows**
- [File -> Auto Save] Auto save enabled: "Save" is not triggered if you quickly (less than 1s) close the editor after making a change.

**Linux-only**
- [File -> Auto Save] The "check" symbol is not shown when you enable "auto save" within the custom editor; however, the operation works.
- [File -> Revert File] Sometimes the menu button is kept disabled when you start VSCode, even after changes.
- [File -> Save All] Same behavior ^
- [File -> Save]     Same behavior ^; Ctrl+S works.
- [File -> Save As]  Same behavior ^; Ctrl+Shift+S works.
_note: the menu buttons become enabled when I open a text editor_

**Windows-only**
- [File -> Revert File] Can't use; always disabled.

Please let me know if you need any further information.

_Originally posted by @caponetto in https://github.com/microsoft/vscode/issues/77131#issuecomment-620571200_
Repository: pytorch
Issue: Log-linear version of cumsum and cumprod
Labels: module: performance,feature,triaged

## 🚀 Feature
Log-linear version of cumsum and cumprod, as the current version has quadratic time-complexity.

## Motivation

The current cumsum and cumprod are too slow for long sequences. They need a faster implementation such as the one I wrote here, which I translated from Jax ([here](https://github.com/google/jax/commit/824ac86620572285b86dd09529f8869ef36883ad)) to Pytorch ([here](https://gist.github.com/AranKomat/be50d1bcee38411681f7218d2b81dede)). This one doesn't utilize a custom CUDA kernel, and it's slower if the sequence length is short. Nevertheless, it's substantially faster than the existing one due to the log-linear time-complexity if it's sufficiently long.   

## Pitch

If you like it, maybe you can add it (maybe just copy mine) to PyTorch possibly along with many variants of this, including logcumsumexp. 


cc @VitalyFedyunin @ngimel
Repository: pytorch
Issue: undefined reference to pthreadpool_compute*
Labels: module: build,triaged,module: xnnpack

## 🐛 Bug

<!-- A clear and concise description of what the bug is. -->

When building with current master 07bb442b240edc8bdc944fb466b1fb56c84fa4ee
with following script
```bash
#!/bin/bash

export REL_WITH_DEB_INFO=1
export USE_CUDA=1

export BUILD_TEST=0
export BUILD_BINARY=0
export BUILD_CAFFE2_OPS=0
export USE_MKLDNN=0
export USE_FBGEMM=0
export USE_NNPACK=0
export USE_QNNPACK=0
export USE_XNNPACK=0

pip install -e . -v

```

```none
    /home/cloudhan/workspaces/pytorch/build/lib/libtorch_cpu.so: undefined reference to `pthreadpool_compute_1d_tiled'
    /home/cloudhan/workspaces/pytorch/build/lib/libtorch_cpu.so: undefined reference to `pthreadpool_compute_3d_tiled'
    /home/cloudhan/workspaces/pytorch/build/lib/libtorch_cpu.so: undefined reference to `caffe2::mobile_pthreadpool()'
    /home/cloudhan/workspaces/pytorch/build/lib/libtorch_cpu.so: undefined reference to `pthreadpool_compute_1d'
    /home/cloudhan/workspaces/pytorch/build/lib/libtorch_cpu.so: undefined reference to `pthreadpool_compute_2d'
    /home/cloudhan/workspaces/pytorch/build/lib/libtorch_cpu.so: undefined reference to `pthreadpool_compute_4d_tiled'
```

similar issue mentioned in https://github.com/pytorch/pytorch/issues/34606#issuecomment-619635665

## To Reproduce

Steps to reproduce the behavior:

1. build the code

<!-- If you have a code sample, error messages, stack traces, please provide it here as well -->

## Expected behavior

<!-- A clear and concise description of what you expected to happen. -->

## Environment

PyTorch version: N/A
Is debug build: N/A
CUDA used to build PyTorch: N/A

OS: Ubuntu 16.04.6 LTS
GCC version: (Ubuntu 5.5.0-12ubuntu1~16.04) 5.5.0 20171010
CMake version: version 3.17.0

Python version: 3.7
Is CUDA available: N/A
CUDA runtime version: Could not collect
GPU models and configuration: 
GPU 0: GeForce RTX 2080 Ti
GPU 1: GeForce RTX 2080 Ti
GPU 2: GeForce RTX 2080 Ti
GPU 3: GeForce RTX 2080 Ti

Nvidia driver version: 418.87.01
cuDNN version: /usr/lib/x86_64-linux-gnu/libcudnn.so.7.6.4

Versions of relevant libraries:
[pip3] numpy==1.16.4
[conda] blas                      1.0                         mkl  
[conda] mkl                       2020.0                      166  
[conda] mkl-service               2.3.0            py37he904b0f_0  
[conda] mkl_fft                   1.0.15           py37ha843d7b_0  
[conda] mkl_random                1.1.0            py37hd6b4f25_0  
[conda] msgpack-numpy             0.4.4.3                  pypi_0    pypi
[conda] numpy                     1.18.3                   pypi_0    pypi
[conda] torch                     1.4.0                    pypi_0    pypi
[conda] torch2trt                 0.0.0                     dev_0    <develop>

<!-- Add any other context about the problem here. -->


cc @malfet
Repository: go
Issue: doc: specify grammar of Deprecated convention
Labels: Documentation,NeedsDecision

This is a follow-up to #10909, which [defined the convention as follows](https://github.com/golang/go/wiki/Deprecated):
> To signal that an identifier should not be used, add a paragraph to its doc comment that begins with `Deprecated:` followed by some information about the deprecation, and a recommendation on what to use instead, if applicable.

This specifies that the convention requires the addition of at least one paragraph, but fails to specify how subsequent paragraphs are to be treated (i.e., are they considered part of the deprecation notice or part of the "regular" documentation). The phrase "followed by some information" is ambiguous as to whether it applies only to the paragraph added or includes subsequent paragraphs.

This has come up with the implementation of tools trying to automatically surface deprecation notices to users during code review.

An example of this:
```go
// ClearAllExtensions clears all extensions from m.
// This includes populated fields and unknown fields in the extension range.
//
// Deprecated: Use RangeExtensions instead to clear all populated extension fields:
//
//	proto.RangeExtensions(m, func(xt protoreflect.ExtensionType, _ interface{}) bool {
//		proto.ClearExtension(m, xt)
//		return true
//	})
//
// The example rewrite above does not clear unknown fields in the extension range,
// which is unlikely to matter in practice.
func ClearAllExtensions(m Message) { ... }
```

In this example, the intent of the deprecation notice is to include all subsequent paragraphs and code blocks as part of the deprecation notice. Should they be considered part of the deprecation message or not? At the present moment, the tool we have only surfaces:

> Use RangeExtensions instead to clear all populated extension fields:

in code review since it only treats the single paragraph as the deprecation warning. The fact that the code block suggesting the alternative is not shown is unfortunate.

\cc @stapelberg @bsiegert @dmitshur @neild @FiloSottile
Repository: terminal
Issue: Add support for Azure Cloud Shell `code` Editor
Labels: Issue-Feature,Area-Extensibility,Product-Terminal,Area-AzureShell

# Environment

```none
Windows build number: Windows 10 Version 1909 Build 18363.657
Windows Terminal version: 0.11.1121.0
```
# Steps to reproduce

1. Open the Windows Terminal
2. Open Azure Cloud Shell
3. Login to Azure
4. Type code . or code file.txt

# Expected behavior

The azure cloud shell editor should open in the background with the provided file like explained here: https://docs.microsoft.com/en-us/azure/cloud-shell/using-cloud-shell-editor.

# Actual behavior

Nothing happens no editor will be opened.
Repository: flutter
Issue: Access to NavigationRequest Headers in webview NavigationDelegate Function
Labels: c: new feature,d: examples,p: webview,package,team-ecosystem,P3,triaged-ecosystem

**Issue -** If I am viewing a page on webview, and a link opens a PDF on the page, then flutter webview can't handle that. We can have a work around to download that file onto user's machine. If its something different than html page. 

I was trying to do this based upon the url and prevent the navigation if the url contains pdf or anything like that. However if the url doesn't contain such texts, and server is masking the file type in the url, then its not possible to download the file on user's device.

Hence in this case if we have access to response headers, which suggest the content-type, things becomes easy.

**Current Code**

```
navigationDelegate: (NavigationRequest request) async {
              print(request.url);
              if (request.url.contains("download")) {
                setState(() {
                  shouldChangeStack = false;
                });
                if (await canLaunch(request.url)) {
                  await launch(request.url);
                }
                return NavigationDecision.prevent;
              } else {
                setState(() {
                  shouldChangeStack = true;
                });
                return NavigationDecision.navigate;
              }
            },
```
Repository: rust
Issue: Tracking Issue for "unsafe blocks in unsafe fn" (RFC #2585)
Labels: B-RFC-approved,T-lang,C-tracking-issue,disposition-merge,finished-final-comment-period,F-unsafe-block-in-unsafe-fn,S-tracking-impl-incomplete

This is a tracking issue for the RFC "unsafe blocks in unsafe fn" (rust-lang/rfcs#2585).
The lint `unsafe_block_in_unsafe_fn` is stable, but the RFC proposes some further things we might want to do.

### About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also uses as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

### Steps

- [x] Introduce an opt-in lint that, when enabled, causes unsafe blocks in unsafe functions to be considered required, and warns if they are absent when an unsafe operation is performed.
- [x] Stabilization PR in Rust 1.52.0 (#79208)
- [x] Include a suggestion with the lint that can insert required unsafe blocks. This could be as simple as adding a block across the entire function, though more granular insertion is probably better. (#112017)
- [ ] Adjust documentation to describe the (somewhat unusual) effect of the lint, and to describe the possibility that the lint will be enabled default ([see instructions on rustc-dev-guide][doc-guide])
- [ ] Write a blog post describing the change, perhaps?

[stabilization-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#stabilization-pr
[doc-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#documentation-prs

### Unresolved Questions

* What is the timeline for adding the lint, and cranking up its default level?
* Should the default level depend on the edition?
* Should we ever make this deny-by-default or even a hard error, in a future edition?
* Should we require `cargo fix` to be able to do *something* about this warning before making it even warn-by-default?  And how precise should it be?

### Implementation history

* Implemented in #71862
* Stabilized in https://github.com/rust-lang/rust/pull/79208
* Fixable suggestion added in #112017
* Made warn-by-default for 2024 edition in #112038
Repository: rust
Issue: Why implementation of iterator is not generic enough in async context?
Labels: A-diagnostics,T-compiler,C-bug,A-async-await,AsyncAwait-Triaged,D-confusing

[Cross posting stackoverflow](https://stackoverflow.com/questions/61491070/why-implementation-of-iterator-is-not-generic-enough-in-async-context) because it's look like a compiler bug/limitation.

---

Given the [following][1] snippet:

```rust
use futures::stream::{self, StreamExt};

async fn from_bar(bar: &[Vec<&u8>]) {
    let x = bar.iter().flat_map(|i| i.iter().map(|_| async { 42 }));
    let foo: Vec<_> = stream::iter(x).collect().await;
}

#[tokio::main]
async fn main() {
    for bar in vec![] {
        tokio::spawn(async {
            from_bar(bar).await;
        });
    }
}
```

I get the following errors:

```none
error[E0308]: mismatched types
  --> src/main.rs:11:9
   |
11 |         tokio::spawn(async {
   |         ^^^^^^^^^^^^ one type is more general than the other
   |
   = note: expected type `std::ops::FnOnce<(&&u8,)>`
              found type `std::ops::FnOnce<(&&u8,)>`

error: implementation of `std::iter::Iterator` is not general enough
    --> src/main.rs:11:9
     |
11   |           tokio::spawn(async {
     |           ^^^^^^^^^^^^ implementation of `std::iter::Iterator` is not general enough
     |
     = note: `std::iter::Iterator` would have to be implemented for the type `std::slice::Iter<'0, &u8>`, for any lifetime `'0`...
     = note: ...but `std::iter::Iterator` is actually implemented for the type `std::slice::Iter<'1, &u8>`, for some specific lifetime `'1`
```

I was expecting no error because the lifetimes seem to be correct to me. Note that removing `main()` or removing the code inside `from_bar()` *both* eliminate the errors. Not only that, the error messages are also very strange. They may be related to [a regression in the compiler][2], though more than that they seem to be in the wrong place ([maybe related][3]).

Version `rustc 1.43.0 (4fb7144ed 2020-04-20)`:

```toml
[dependencies]
futures = '0.3.1'

[dependencies.tokio]
version = '0.2'
features = ['full']
```

---

Maybe related https://github.com/rust-lang/rust/issues/64650

  [1]: https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=bece604aa99c31dc710f5f3129296f1f
  [2]: https://stackoverflow.com/questions/54341465/rust-expected-type-error-prints-mismatched-types-that-are-exactly-the-same/54344401#54344401
  [3]: https://github.com/rust-lang/rust/issues/54326
Repository: flutter
Issue: [camera] Add byte streaming capability for the camera
Labels: c: new feature,p: camera,package,c: proposal,team-ecosystem,P3,triaged-ecosystem

```startImageStream``` was added to Flutter camera but this isn't sufficient.

We really need ```startByteStream``` which also includes audio, and is much faster.

Many of us are trying to create live streams from our apps and at the moment it's impossible.

```startVideoRecording``` locks the file, soon as for example ```FlutterFFmpeg``` tries to read the file for live RTMP streaming it stops the camera.
Repository: vscode
Issue: QuickPick in web with VoiceOver does not read anything
Labels: bug,accessibility,quick-pick,web

1. yarn web
2. VoiceOver
3. Cmd + P, use keyboard navigation to change focus -> VoiceOver does not read anything

I can repro with Safari and Chrome.
Does not repro on Linux and Win. So might be a VoiceOver issue.
Repository: flutter
Issue: Font size is different on Physical Device and  Simulator/Emulator
Labels: framework,f: cupertino,a: quality,a: typography,has reproducible steps,found in release: 3.3,found in release: 3.7,team-design,triaged-design

## Steps to Reproduce
After building the project and install it on a physical device (iPhone 7, XR and XR MAX), I realized that font size is different.

**Expected results:** <!-- what did you want to see? -->
Same font size on device and simulator.

**Actual results:** <!-- what did you see? -->


---
- Font size is **bigger** on an iPhone 7 (and XR):
![font_iPhone 8](https://user-images.githubusercontent.com/1607281/80603894-48f0e980-8a31-11ea-91cd-224f56e723f0.jpg)
---
- Font size is **smaller** on an iPhone XR Max:
![font_iPhone_11ProMax](https://user-images.githubusercontent.com/1607281/80603904-4d1d0700-8a31-11ea-91b2-db00a6902b59.jpg)




<details>

flutter doctor -v
[✓] Flutter (Channel stable, v1.12.13+hotfix.9, on Mac OS X 10.15.4 19E287, locale en-US)
    • Flutter version 1.12.13+hotfix.9 at /Users/peruho/Developer/flutter
    • Framework revision f139b11009 (4 weeks ago), 2020-03-30 13:57:30 -0700
    • Engine revision af51afceb8
    • Dart version 2.7.2

 
[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/peruho/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 28.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.4.1, Build version 11E503a
    • CocoaPods version 1.9.0

[✓] Android Studio (version 3.6)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 44.0.2
    • Dart plugin version 192.7761
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)

[✓] VS Code (version 1.44.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.9.1

[✓] Connected device (3 available)

• No issues found!

</details>
Repository: godot
Issue: Can't assign mouse buttons or mouse wheel to editor shortcuts
Labels: enhancement,topic:editor,usability

**Godot version:**
All versions including v4.0.dev.custom_build.1d45a269f
**OS/device including version:**
W10 1903
**Issue description:**
Can't assign mouse button inputs to editor shortcuts
**Steps to reproduce:**
Editor Settings > Shortcuts > Try to set any mouse button, can't
**Minimal reproduction project:**
None

Some related issues:
#6366
#26999

The editor settings only allows key inputs, as shown below, where the event is cast to InputEventKey.
https://github.com/godotengine/godot/blob/f6e29addd433130100061935b9a2b8f6de38254b/editor/settings_config_dialog.cpp#L318-L330

I think being able to assign BUTTON_XBUTTON1 and BUTTON_XBUTTON2 would be helpful, especially for back/forward editor navigation. In order to not let people mess up the general usage of the editor, I think it may be a case of only allowing the above 2 mouse button input types to be assigned... i.e. not allowing rebinding of MB1, MB2, scroll, etc (unless they are modified...? e.g. with shift, alt, ctrl).

Making this change would be relatively simple (I think - haven't looked into it too deep), but it would require changing a decent amount of existing code within the file above, since `last_wait_for_key` would need it's type altered.

Happy to work on a PR if the general consensus is that this is worthwhile.
Repository: godot
Issue: Unable to perform a headless Android build (with custom builds) without first opening the GUI
Labels: enhancement,platform:android,topic:editor,topic:export

**Godot version:**
3.2.1+

**OS/device including version:**
Android

**Issue description:**
The headless version of godot can be used to export projects without opening the editor. This is important for Continuous Delivery & automation of development.
Since Godot 3.2.1, we have been able to use a custom android export when exporting our Android games. In a newly checked out project, one has to go to the Project>"Install Android Build Template" in order to begin exporting for android. However, there is no way to do this with the headless version of godot. Because of this, you are unable to perform an initial build of a godot Android game with the headless version, without first opening it in the GUI.

I think there should be a godot command to run this gradle setup from the command line, to keep this tool consistent.
Repository: flutter
Issue: FocusPointer for GestureDetection
Labels: c: new feature,framework,f: gestures,c: proposal,P3,team-framework,triaged-framework

## Use case

It's come to my attention that it is possible for a Widget to be impervious to gestures. (`Ignore-` and `AbsorbPointer`). Except it actually isn't possible to easily write a widget with a second `GestureDetector` and have the `Gesture`s not be considered by parent widgets.

## Proposal

A `FocusPointer`, which when detected in the WidgetTree on `Gesture` only passes the event through to the Widgets within, ignoring Widgets higher up in the WidgetTree, (Would allow things like having a map <with vertical and horizontal gestures> within a container).
Repository: flutter
Issue: Service worker caching should be smarter
Labels: tool,c: performance,platform-web,P3,team-web,triaged-web

There is a reported hit to IPL when using the service worker caching on the new gallery https://github.com/flutter/gallery . The current caching strategy is optimized for small applications, but larger ones will need a more sophisticated strategy to avoid downloading absolutely everyone on first load. Some ideas:

- Part files should not be part of the initial cache, since this defeats the goal of deferred loading. These should be cache on demand
- assets _might_ not need to be part of the initial cache - instead these could be moved into cache on demand. Fonts might cause some issues here, since I think the engine still eagerly loads them.
- Should install cache everything? My gut says yes but it isn't quite clear.
- Are there any assets that absolutely must be cached during the initial load? Probably main JavaScript, html, manifest?
Repository: node
Issue: http: ServerRequest & ServerResponse does not set destroyed false
Labels: http

https://github.com/nodejs/node/pull/33131 and https://github.com/nodejs/node/pull/33120 fix this for client side, we should do the same thing server side and ensure that streams that have emitted `'close'` also have `destroyed` set to `false`