sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: angular
Issue: support URL type in http client method 
Labels: feature,area: common/http,state: has PR,good first issue,feature: under consideration

### Which @angular/* package(s) are relevant/related to the feature request?

common

### Description

It's good practice to use [URL](https://developer.mozilla.org/en-US/docs/Web/API/URL/URL) type beside string for URLs in JavaScript. and all browsers support [it](https://caniuse.com/url).
In my app, I get an error when trying to use URL type as parameter in the httpClient post.
```
error TS2345: Argument of type 'URL' is not assignable to parameter of type 'string'.
```
I know I can fix it make it a string and call the `toString` method of URL, I know this. Please read the proposed solution 

### Proposed solution

It's good practice to use URL type beside string for URLs in JavaScript. It seemed to me to add an overload for all http method client that supports URL as a parameter like this 
```
/**
     * Constructs a `POST` request that interprets the body as a
     * JSON object and returns the response body as a JSON object.
     *
     * @param url The endpoint URL.
     * @param body The content to replace with.
     * @param options HTTP options
     *
     * @return An `Observable` of the response, with the response body as a JSON object.
     */
    post(url: URL, body: any | null, options?: {
        headers?: HttpHeaders | {
            [header: string]: string | string[];
        };
        context?: HttpContext;
        observe?: 'body';
        params?: HttpParams | {
            [param: string]: string | number | boolean | ReadonlyArray<string | number | boolean>;
        };
        reportProgress?: boolean;
        responseType?: 'json';
        withCredentials?: boolean;
    }): Observable<Object>;
```
to support this. 


### Alternatives considered

don't change any things
Repository: pytorch
Issue: Generate source location information in TS LTC backend
Labels: oncall: jit

### 🚀 The feature, motivation and pitch

Currently, it appears that `jit::Node`s contained in the `jit::Graph` by the `TSLoweringContext` are missing source location information, which makes it difficult to debug.

To test this, the following block was added before [this line of code](https://github.com/pytorch/pytorch/blob/master/torch/csrc/lazy/ts_backend/ts_lowering_context.h#L107):
```cpp
for (auto node : graph_->nodes()) {
    auto flc = node->sourceRange().file_line_col();
    if (flc) {
        const std::string &file = std::get<0>(*flc);
        std::cout << "Filename: " << file << std::endl;
    } else {
        std::cout << "No source!" << std::endl;
    }
}
```

Python test case:
```python
import torch
import torch._lazy
import torch._lazy.ts_backend

torch._lazy.ts_backend.init()

device = 'lazy'
inputs = torch.tensor([[1, 2, 3, 4, 5]], dtype=torch.float32, device=device)

print(inputs @ inputs.T)

torch._lazy.mark_step()
```

Output:
```
No source!
No source!
No source!
No source!
tensor([[55.]], device='lazy:0')
```

Ideally, we would be able to map a `jit::Node` to the location in the Python code where it was created.

cc: @silvasean @wconstab @antoniojkim

### Alternatives

_No response_

### Additional context

_No response_
Repository: next.js
Issue: SSR performance problem, slow processHTML
Labels: Upstream

### Verify canary release

- [X] I verified that the issue exists in Next.js canary release

### Provide environment information

```
Operating System:
  Platform: darwin
  Arch: x64
  Version: Darwin Kernel Version 21.3.0: Wed Jan  5 21:37:58 PST 2022; root:xnu-8019.80.24~20/RELEASE_X86_64
Binaries:
  Node: 16.13.2
  npm: 8.1.2
  Yarn: 1.22.10
  pnpm: N/A
Relevant packages:
  next: 12.1.4
  react: 17.0.2
  react-dom: 17.0.2
```

### What browser are you using? (if relevant)

Chrome 99.0.4844.51

### How are you deploying your application? (if relevant)

next start

### Describe the Bug

Hello!

Was checking stream rendering performance with react 18, and noticed a problem with react 17.
For every request for SSR page, the `processHTML` method is called, which takes as much CPU time as from `renderToString`.
Also, I see after each request a large number of unclear callbacks related to streams.

The situation with React 18 and stream rendering is even worse, but since this is an experimental mode, I'm not focusing on it.

### Expected Behavior

I expect every request to have a minimum overhead in addition to `renderToString`

### To Reproduce

Reproduction repo - https://github.com/SuperOleg39/next-ssr-perf-test

You can run load tests or CPU profiling on this example.

CPU profile snapshot:
[CPU-next-react-17.cpuprofile.zip](https://github.com/vercel/next.js/files/8393112/CPU-next-react-17.cpuprofile.zip)

<img width="1792" alt="Снимок экрана 2022-04-01 в 00 26 32" src="https://user-images.githubusercontent.com/15360667/161152096-380cee72-d5a5-4c5e-9c3a-bb12694374b0.png">
Repository: flutter
Issue: Text Editing Gestures/Intents/Actions
Labels: a: text input,framework,f: material design,a: fidelity,a: quality,P3,team-design,triaged-design

Currently, gestures related to text editing are handled by `TextSelectionGestureDetectorBuilder`, with no way to override these gestures practically without using `IgnorePointer` which blocks all default gestures defined on the text editing widget. The goal here is to build something analogous to the current keyboard shortcuts -> intents -> action system, with defaults that can be practically overwritten by the user. 

☔️ To complete this issue we need:
  - [ ] All pointer-related text editing interactions ported to Intents/Actions, like tapping, long pressing, etc. #75004
  - [x] Support selection all text on triple click #63576
  - [x] Support double tap drag gesture to select a block of text on iOS #64550
  - [x] Single tap on text field to display toolbar #48434
  - [x] Hide selection toolbar when moving caret/handles #62193
  - [ ] Selection toolbar/handle should disappear when clicking outside of it #72029
  - [x] Textfield context menu does not show after focus switch #99707

Other issues of note:
 -  [ ] Textfield should receive callbacks from `TextSelectionGestureDetector` #35187
Repository: go
Issue: x/build: Linux distribution too old on some builders
Labels: Builders,NeedsInvestigation

At least on some builders (e.g. linux-arm64-aws, linux-ppc64le-buildlet), it currently has Debian buster, which seems currently "oldstable". It seems still supported, but it causes `apt-get update` command to fail. This is inconvenient for gomote uses, also causes cmd/racebuild script to fail.

A workaround is `apt-get --allow-releaseinfo-change update`. But I'm not sure if it is a good idea for long term.
Repository: PowerToys
Issue: I think something is wrong with powerrename.
Labels: Idea-Enhancement,Product-PowerRename,Needs-Triage

### Description of the new feature / enhancement

when i want to rename some files.not just choose them with checkbox,but must use search box,otherwise can't apply it.
appologize for my bad English.

### Scenario when this would be used?

when i want rename some files/folders

### Supporting information

_No response_

这个重命名的工具，有复选功能，也带有搜索功能。复选比较精准，准确选择要批量重命名的文件。搜索框是为了应对大量文件设计的。如果用户使用复选了，并且“替换为”文本框输入了对应的文本，另外下拉菜单选择“仅文件名|仅扩展名|文件名+扩展名”已经可以精准进行重命名。实际使用中，不使用搜索框输入关键词，压根不让应用此更改。当然为了避免重复名称，可以限定复选+仅扩展名 然后填写替换文本。
以上是因为按照我的使用思路发现的问题。
Repository: storybook
Issue: add object inside an array with specified keys in controls
Labels: feature request,needs triage

if I have  a select  component that takes options for an array of objects each object with 2 keys 
`{
label:"label",
onClick:()=>{}
}`

if I want to increase the number of options in storybook controls I will have an array with one object and when I press the + button next to it it will give me input for one value as it is an array instead of giving me input for an object with 2 keys and put each key with the value needed 

Are you able to assist to bring the feature to reality?**
no
Repository: neovim
Issue: wrong display with Unicode
Labels: bug,platform:windows,tui,unicode  💩

### Neovim version (nvim -v)

NVIM v0.7.0-dev

### Vim (not Nvim) behaves the same?

not test

### Operating system/version

wsl2

### Terminal name/version

wsl2

### $TERM environment variable

xterm-256color

### Installation

apt

### How to reproduce the issue

nvim --clean
enter insert mode
input： ☻รูปแบบ☻ห่อ☻เหมือนกับ☻ดอกไม้ไฟ☻ที่☻หัก☻ที่อยู่☻ใน☻โดม
then insert ‘------------------’ before text

### Expected behavior

correct display

### Actual behavior

![image](https://user-images.githubusercontent.com/19503791/161177725-0419f2a0-509d-4376-83dd-3527dbd75eae.png)
Repository: storybook
Issue: Add clarifcation in Docs regarding `Magic` bahvior when using Vue & `action`
Labels: bug,vue,has workaround

**Is your feature request related to a problem? Please describe**
A clear and concise description of the problem. E.g. I'm always frustrated when [...]

When using `Vue` with `storybook`
the storybook is automatically adding 'on' prefix to emitted events.
Is this behavior offically documented anywhere?
If not, I think it should be more explicitly documented.

For example,
I am making a component that emits
```
const emit = defineEmits<{(e: "click"): void; (e: "delete"): void }>();
```

defining story
```
export default {
  title     : "Example/tag",
  ...
  argTypes : {
    ...
    click  : { action: "click" },
    delete : { action: "delete" },
  },
};
```
like this does not work.

I have to add `on` and make it camelCase

```
export default {
  title     : "Example/tag",
  ...
  argTypes : {
    type : {
      control : { type: "inline-radio" },
      options : [undefined, ...Object.values(TAG_TYPE)],
    },
    onClick  : { action: "click" },
    onDelete : { action: "delete" },
  },
};
```
like this. To actually connect actions to `click` and `delete` event.

Is storybook doing this by default?
This may lead to strange cases like below.
```
const emit = defineEmits<{(e: "onClick"): void; (e: "onDelete"): void }>();

export default {
  title     : "Example/tag",
  ...
  argTypes : {
    type : {
      control : { type: "inline-radio" },
      options : [undefined, ...Object.values(TAG_TYPE)],
    },
    onOnClick  : { action: "click" },
    onOnDelete : { action: "delete" },
  },
};
```

Please let me know if I missed something.

Thanks

**Describe the solution you'd like**
What would you like to see added to Storybook to solve problem?

**Describe alternatives you've considered**
Any alternative solutions or features you've considered.

**Are you able to assist to bring the feature to reality?**
no | yes, I can...

**Additional context**
Add any other context or screenshots about the feature request here.
Repository: go
Issue: proposal: runtime: Expose a function to enable GODEBUG="tracebackancestors=N" on runtime 
Labels: Proposal

I'm making a lib to detect goroutine leaks, if we don't enable `tracebackancestors` it will be impossible to detect goroutine leaks in testing when `testing.T.isParallel` is enabled.

If we can add a function in `runtime`, such as `runtime.TracebackAncestors(n int)` then we don't have to add protection code like this:

https://github.com/ysmood/gotrace/blob/03c1fdd54f28e0778ae12534167858777a00ddcd/utils.go#L31-L38
Repository: yt-dlp
Issue: Merge video & audio file metadata when merging files
Labels: bug,triage,core:post-processor

### Checklist

- [X] I'm reporting a feature request
- [X] I've looked through the [README](https://github.com/yt-dlp/yt-dlp#readme)
- [X] I've verified that I'm running yt-dlp version **2022.03.08.1**. ([update instructions](https://github.com/yt-dlp/yt-dlp#update))
- [X] I've searched the [bugtracker](https://github.com/yt-dlp/yt-dlp/issues?q=) for similar issues including closed ones. DO NOT post duplicates
- [X] I've read the [guidelines for opening an issue](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#opening-an-issue)

### Description

Currently when separate video & audio files are merged, any pieces of non-matching metadata are lost; the only thing that remains is the truly common data (like length). So while the video has info on frame width/height, and audio has info on the bit rate, the output contains neither of these fields.

It'd be great if these could be stitched together so metadata isn't lost. Admittedly I'm not familiar with the merging process at all, so I'm not sure how big/small of an undertaking this would be (assuming it's possible, of course). 

Below is a picture of the 3 file properties side-by-side: on the left is separate video, middle is separate audio, and the right is the merged file. As you can see, some data has been lost in the merge.

![File properties of separate video, separate audio, and merged file](https://user-images.githubusercontent.com/33403762/161191357-94948d27-197a-4927-85d0-c4ae84a4b6cf.PNG)
Repository: rust
Issue: Awkward parse error for macro_rule repetition missing its `*`/`+`/`?`
Labels: A-diagnostics,T-compiler

Given the following code: <https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=99c47e5e030aa3460464df5c45097a9b>

```rust
macro_rules! checked_sum {
    ( $first:expr $(, $rest:expr ) $(,)? ) => {
        [$($rest),*].into_iter().try_fold($first, |a, b| a.checked_add(b))
    }
}
```

(where I forgot the `*` after the `)`)

The current output is:

```
error: expected one of: `*`, `+`, or `?`
 --> src/main.rs:2:37
  |
2 |     ( $first:expr $(, $rest:expr ) $(,)? ) => {
  |                                     ^^^

error: `$first:expr` may be followed by `?`, which is not allowed for `expr` fragments
 --> src/main.rs:2:40
  |
2 |     ( $first:expr $(, $rest:expr ) $(,)? ) => {
  |                                        ^ not allowed after `expr` fragments
  |
  = note: allowed there are: `=>`, `,` or `;`

error: `$rest:expr` is followed by `?`, which is not allowed for `expr` fragments
 --> src/main.rs:2:40
  |
2 |     ( $first:expr $(, $rest:expr ) $(,)? ) => {
  |                                        ^ not allowed after `expr` fragments
  |
  = note: allowed there are: `=>`, `,` or `;`

error: could not compile `playground` due to 3 previous errors
```

Because that error `^^^`'d the `(,)` part, I thought I got the "optional trailing comma" part wrong, and ended up looking that up again before realizing that it wasn't the problem at all.

(Would be nice if the grammar here made it easier to resync, but maybe whitespace can help hint.  Or hopefully most people aren't doing `$(...)$+`...)


<!-- The following is not always necessary. -->
Ideally the output should look like:

```
  |
2 |     ( $first:expr $(, $rest:expr ) $(,)? ) => {
  |                                  ^ help: did you forget a repetition operator?
```



<!--
If the problem is not self-explanatory, please provide a rationale for the
change.
-->

<!--
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: pytorch
Issue: extend torch.distributed's `--tee` to log the nodename
Labels: oncall: distributed,enhancement,oncall: r2p

### 🚀 The feature, motivation and pitch

I'm currently using pt-1.11

This is a request to improve `--tee 3` logging, Here is an example of the current log:

```
[default3]:python: src/psm2_nccl_net.c:756: mq_progress_loop: Assertion `r->used' failed.
[default3]:Fatal Python error: Segmentation fault
```

Currently `--tee 3` is somewhat useful by prefixing each log with `[default{local_rank}]` when used in:
```
export LAUNCHER="python -u -m torch.distributed.run \
    --nproc_per_node $GPUS_PER_NODE \
    --nnodes $NNODES \
    --rdzv_endpoint $MASTER_ADDR:$MASTER_PORT \
    --rdzv_backend c10d \
    --tee 3 \
    "
```

This is a great step towards more usable logging and troubleshooting, but more is needed please:

Please make it log: `nodename:rank: `via a new flag or the existing one.

Of course, any way you choose is satisfactory, but if I had a say I'd format it as: `f"{node}:{rank}: "` (note the trailing space:). Explanation:
- the `[]` is just noise and waste of horizontal space
- there is no whitespace separation at the moment between the prefix and the actual log line. the whitespace adds a bit of breathing space is needed to improve readability. 
- the `default` is a waste of horizontal space and contributes no useful information.

then the current log:

```
[default3]:python: src/psm2_nccl_net.c:756: mq_progress_loop: Assertion `r->used' failed.
[default3]:Fatal Python error: Segmentation fault
```
becomes:

```
r12i0n8:3: python: src/psm2_nccl_net.c:756: mq_progress_loop: Assertion `r->used' failed.
r12i0n8:3: Fatal Python error: Segmentation fault
```
and now we know the exact node:rank that caused the problem and one can act on it. Currently I am debugging a segfault and I don't know how to find the node it crashed on since the whole c10d logging vanishes completely on segfault. No `Root cause`, no any other logging appears, which is normally there when there is a python assertion. It just ends with:
```
WARNING:torch.distributed.elastic.multiprocessing.api:Sending process 269614 closing signal SIGTERM
ERROR:torch.distributed.elastic.multiprocessing.api:failed (exitcode: -6) local_rank: 1 (pid: 269615) of binary: /gpfswork/rech/six/commun/conda/py38-pt111/bin/python
```

And a bonus request: could the `--tee` option be documented at https://pytorch.org/docs/stable/elastic/run.html and/or https://pytorch.org/docs/stable/distributed.html? 

Thank you so much!

@cbalioglu 

cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @SciPioneer @H-Huang
Repository: go
Issue: cmd/objdump: does not understand ARMv8 SHA-3 instructions
Labels: NeedsInvestigation,compiler/runtime

<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.18 darwin/arm64
</pre>

### Does this issue reproduce with the latest release?

This is the latest release.

### 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="/Users/eric/gopath/bin"
GOCACHE="/Users/eric/Library/Caches/go-build"
GOENV="/Users/eric/Library/Application Support/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="arm64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/eric/gopath/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/eric/gopath"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_arm64"
GOVCS=""
GOVERSION="go1.18"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/eric/git/arch/go.mod"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/2f/2_yz21b92h94_pvr2m00gzh80000gn/T/go-build4092429902=/tmp/go-build -gno-record-gcc-switches -fno-common"
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on go.dev/play is best.
-->
Ran `go tool objdump` on a binary using SHA-3 instructions like XAR (VAXR) and EOR3 (VEOR3).


### What did you expect to see?

It output valid Go (and GNU) assembly

### What did you see instead?

`?`
Repository: pytorch
Issue: torch.fx deepcopy bug
Labels: triaged,module: fx

### 🐛 Describe the bug

import torch
import torch.fx
from types import MethodType
from copy import deepcopy

class Student(torch.nn.Module):
    def __init__(self):
        super().__init__()
        self.bn = torch.nn.BatchNorm2d(3)
        self.gamma = torch.nn.BatchNorm2d(3)
    def forward(self, x):
        return self.bn(x)
    def set_score(self, score):
        self.score = score

s = Student()
func = getattr(s.__class__, "set_score")
fx_s = torch.fx.symbolic_trace(s)
setattr(fx_s, "set_score", MethodType(func, fx_s))

fx_s_copy = deepcopy(fx_s)


Bug: RecursionError: maximum recursion depth exceeded while calling a Python object

### Versions

pytorch=1.8.0
Repository: flutter
Issue: OpenMoji fonts do not render correctly (no color)
Labels: platform-android,engine,a: typography,platform-web,c: rendering,has reproducible steps,P2,found in release: 2.10,found in release: 2.13,team-engine,triaged-engine

## Steps to Reproduce

Different emoji fonts do not render correctly (no color).

This should be a problem as most of these fonts are rendered correctly in the browser, so it should also be rendered correctly in flutter. Sometimes I don't want to use the system default font, so this problem is very annoying.

**Expected results:** All the emoji fonts should render with color.

**Actual results:** Only Noto emoji render with color.

<details>
<summary>Code sample</summary>

```dart
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: Scaffold(
        body: Center(
          child: Column(
            mainAxisAlignment: MainAxisAlignment.center,
            children: const <Widget>[
              Emj('💎🍨🍥', 'Seguiemj'),
              Emj('💎🍨🍥', 'Openmoji'),
              Emj('💎🍨🍥', 'Notoemj'),
              Emj('💎🍨🍥', null),
            ],
          ),
        ),
      ),
    );
  }
}

class Emj extends StatelessWidget {
  const Emj(this._text, this._fontFamily, {Key? key}) : super(key: key);

  final String _text;
  final String? _fontFamily;

  @override
  Widget build(BuildContext context) {
    return Text(
      _text,
      style: TextStyle(
        fontFamily: _fontFamily,
        fontSize: 64.0,
      ),
    );
  }
}
```

</details>

<img width="266" alt="image" src="https://user-images.githubusercontent.com/56141162/161220773-e5354b88-082c-4b4e-9b15-12d63edb6663.png">

As a comparison, you can see that the browser can correctly render fonts other than Openmoji.

<img width="640" alt="image" src="https://user-images.githubusercontent.com/56141162/161221158-31e1603d-537c-4c82-9fda-83e32dfff50d.png">

## `flutter doctor -v`

![image](https://user-images.githubusercontent.com/56141162/161238867-2f469e86-0bd2-4410-9a62-b5a3fec981b9.png)

![image](https://user-images.githubusercontent.com/56141162/161238987-30ef8f10-0953-4ff8-b29d-4c555453f894.png)
Repository: PowerToys
Issue: Bigger image thumbs in explorer for small screen high DPI devices
Labels: Idea-New PowerToy

### Description of the new feature / enhancement

Winows 10 has a major shortcoming in Windows Explorer when it comes to showing image thumbnails on small screen/high DPI devices. The option "Extra large icons" produces thumbs of equal size to the "Large icons" option in the View settings.

![image](https://user-images.githubusercontent.com/65452159/161223664-3045a8a6-73bd-4c18-8059-942f16bd60a4.png)

Could PowerToys maybe correct/enhance this?

### Scenario when this would be used?

Thumbnail view of images in Explorer: showing larger thumbnails on small screen/high DPI devices, like for instance the One Notebook Yoga 3Pro with its 8 inch 2560x1600 screen.

### Supporting information

_No response_