sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: proposal: net: UDPAddr/TCPAddr AddrPort should map 4in6 addresses to IPv4 netip.Addrs
Labels: Proposal,NeedsInvestigation,Proposal-Hold

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.18.3 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

It does with `go version devel go1.19-d3ffff2790 Tue Jun 28 13:01:41 2022 +0000 linux/amd64`, haven't tried a more recent one.

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE="on"
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/ainar/.cache/go-build"
GOENV="/home/ainar/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/ainar/go/pkg/mod"
GONOPROXY="REMOVED"
GONOSUMDB="REMOVED"
GOOS="linux"
GOPATH="/home/ainar/go"
GOPRIVATE="REMOVED"
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/home/ainar/go/go1.18"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/ainar/go/go1.18/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.18.3"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/dev/null"
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 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build1722739114=/tmp/go-build -gno-record-gcc-switches"
</pre></details>

### What did you do?

```go
c, err := net.ListenUDP("udp", &net.UDPAddr{
	IP:   net.IPv4zero,
	Port: 10000,
})
if err != nil {
	panic(err)
}

var buf [64]byte
_, raddr, err := c.ReadFromUDPAddrPort(buf[:])
if err != nil {
	panic(err)
}

fmt.Println(raddr)
fmt.Println("is4:", raddr.Addr().Is4())
fmt.Println("is6:", raddr.Addr().Is6())
fmt.Println("is4in6:", raddr.Addr().Is4In6())

_, oldRAddr, err := c.ReadFromUDP(buf[:])
if err != nil {
	panic(err)
}

raddr = oldRAddr.AddrPort()
fmt.Println(oldRAddr.Network())
fmt.Println(raddr)
fmt.Println("is4:", raddr.Addr().Is4())
fmt.Println("is6:", raddr.Addr().Is6())
fmt.Println("is4in6:", raddr.Addr().Is4In6())
```

<https://go.dev/play/p/9qs4KxGRPjq>

```sh
go run ./main.go
```

```sh
echo 'hello' | nc -4 -u -w 1 127.0.0.1 10000
echo 'world' | nc -4 -u -w 1 127.0.0.1 10000
```

**Note:** the requests are sent using `-4` and an IPv4 address.



### What did you expect to see?

```none
127.0.0.1:58848
is4: true
is6: false
is4in6: false
udp
127.0.0.1:38564
is4: true
is6: false
is4in6: false
```

### What did you see instead?

```none
[::ffff:127.0.0.1]:58848
is4: false
is6: true
is4in6: true
udp
[::ffff:127.0.0.1]:38564
is4: false
is6: true
is4in6: true
```

I haven't tried the TCP ones, but looking at the code, they probably have the same issue.
Repository: flutter
Issue: Mac_ios external_ui_integration_test_ios is 3.00% flaky
Labels: engine,P2,c: flake,team-engine,triaged-engine

<!-- meta-tags: To be used by the automation script only, DO NOT MODIFY.
{
  "name": "Mac_ios external_ui_integration_test_ios"
}
-->

The post-submit test builder `Mac_ios external_ui_integration_test_ios` had a flaky ratio 3.00% for the past (up to) 100 commits, which is above our 2.00% threshold.

One recent flaky example for a same commit: https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_ios%20external_ui_integration_test_ios/4724
Commit: https://github.com/flutter/flutter/commit/bbdf617034171ab1128a594fb24e1c72a09e072e

Flaky builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_ios%20external_ui_integration_test_ios/4724
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_ios%20external_ui_integration_test_ios/4713
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_ios%20external_ui_integration_test_ios/4690

Recent test runs:
https://flutter-dashboard.appspot.com/#/build?taskFilter=Mac_ios%20external_ui_integration_test_ios

Please follow https://github.com/flutter/flutter/wiki/Reducing-Test-Flakiness#fixing-flaky-tests to fix the flakiness and enable the test back after validating the fix (internal dashboard to validate: go/flutter_test_flakiness).
Repository: ant-design
Issue: Make tree focusable after click and add autofocus
Labels: 💡 Feature Request,Inactive

### What problem does this feature solve?

It is not obvious that key navigation is possible in tree. If there are a lot of components you should press tab multiple times to access tree.
Also after clicking somewhere in tree, focus is lost and you should again press tab to access key navigation here.

### What does the proposed API look like?

<Tree autofocus clickFocusable ... />

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: rust
Issue: Const associated items behave differently than module const declarations, "cannot evaluate destructors" error
Labels: T-compiler,C-bug,A-const-eval

<!--
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.
-->

[I tried this code (Rust Playground link)](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=1b17588e165e1e8f1a628fa120d0e082)

```rust
use std::borrow::Cow;

struct T { doesnt_matter: Cow<'static, str> }

const FOO: T = T { doesnt_matter: Cow::Borrowed("foo") }; // OK as long as decl is const
const BAR: T = T { ..FOO }; // OK

trait SomeTrait {
  const ASSOC_CONST: T;
}

impl SomeTrait for usize {
  const ASSOC_CONST: T = T { ..BAR }; // OK
}

const BAZ: T = T { ..usize::ASSOC_CONST }; // ERROR: "value is dropped here", "constants cannot evaluate destructors"

const USIZE_CONST: T = usize::ASSOC_CONST; // OK

const BAZ_TAKE_TWO: T = T { ..USIZE_CONST }; // ERROR: "value is dropped here", "constants cannot evaluate destructors"
```

I expected to see this happen: the declaration of BAZ and BAZ_TAKE_TWO should work, just as the declaration of BAR and the impl of SomeTrait worked.

Instead, this happened: compiler error.

Trait associated constants seem to lack some bit/flag set that denotes that no destructor is required when dropping them. Constants at the module level however can be used just fine.

The declaration of `USIZE_CONST` shows that this seems to break referential transparency. That value seems to "know" that it is different, in some way, than FOO and BAR, and it cannot be used in the same way as those two constants.

### Meta

`rustc --version --verbose`:
```
rustc 1.61.0 (fe5b13d68 2022-05-18)
binary: rustc
commit-hash: fe5b13d681f25ee6474be29d748c65adcd91f69e
commit-date: 2022-05-18
host: x86_64-unknown-linux-gnu
release: 1.61.0
LLVM version: 14.0.0
```
Repository: vscode
Issue: Provide speech feedback when commenting or uncommenting a line.
Labels: feature-request,accessibility,editor-core,under-discussion

<!-- ⚠️⚠️ 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. -->
When pressing ctrl+/ to comment a line, everything works as expected. However, I'm a screen reader user, and so in order to see the result, I have to press my screen reader's read line command to read the line. This isn't necessarily ideal. Its not a deal breaker, but it would be nice if we could get some sort of speech feedback. For example, commented line: (line content), or uncommented line: (line content).
Repository: flutter
Issue: Tree status is not refreshed on old PRs
Labels: team-infra,P2,triaged-infra

For example: https://github.com/flutter/flutter/pull/101834

Tree has been green since yesterday, but the `luci-flutter` status is still red.
<img width="1033" alt="Screen Shot 2022-06-29 at 9 50 26 AM" src="https://user-images.githubusercontent.com/54558023/176492299-31e8c11c-8b71-43bd-a0a1-0427d57d301b.png">

Culprit: [pull list api ](https://docs.github.com/en/rest/pulls/pulls#list-pull-requests)returns 30 PRs by default. We should extend the number to cover relatively old PRs.
Repository: pytorch
Issue: [Prims+NVFuser] Prims with missing NVFuser ops
Labels: triaged,module: nvfuser,module: primTorch

These prims are missing NVFuser implementations. They were found by running https://github.com/pytorch/pytorch/compare/bahuang/nvfuser_e2e with additional decompositions.

- [ ] cat
- [ ] maximum
- [ ] transpose

cc @ezyang @mruberry @ngimel
Repository: go
Issue: x/build/internal/gomote/protos: change ListDirectoryResponse to include buildlet.DirEntry like response
Labels: Builders,NeedsFix

The ListDirectoryResponse output would be much more useful if it provided the same data that `buildlet.DirEntry` contains. We should change the output to match `buildlet.DirEntry` instead of vanilla directory listing strings.


@golang/release
Repository: pytorch
Issue: Allow parameterization of Layouts
Labels: module: sparse,feature,triaged,module: python frontend

### 🚀 The feature, motivation and pitch

Some layouts can be arbitrarily parameterized. Block sparse layouts, for example require block sizes to completely specify the layout. 

If we were to implement a way of parameterizing such layouts, then passing the layout in any context would be fully specified without the need for additional arguments. 



### Alternatives

- All interfaces accepting a layout would strictly support a subset of layouts.
   - This would make the adoption of any "parameterized" layout more difficult.
- All interfaces accepting a `layout` would have to accept any additional parameters required to perform any possible conversions.
   - These interfaces would need to be updated when new layouts are introduced.
   - Specification of a parameter with a `layout` option that it does not pertain to would need to be detected and handled (Warning/Error), or ignored (potentially problematic)

### Additional context

A key example (see #80542). 

If the `Tensor.to` method were to support layout conversions a `blocksize` parameter would need to be accepted, but ignored for most layouts. If the `blocksize` was instead a parameter attached to the layout itself that interface (and all others accepting a `layout`) could safely be ignorant of the additional details for those layouts. The parameter need only be accessed at the point where the real format conversion function gets involved. 

```python
x = torch.Tensor(...)
y = x.to(layout=torch.sparse_bsr(blocksize=(...)))
z = x.to(layout=torch.sparse_coo)
```
vs

```python
x = torch.Tensor(...)
y = x.to(layout=torch.sparse_bsr, blocksize=(...))
z = x.to(layout=torch.sparse_coo, blocksize=(...))
```

The handling of the last case in above would be tedious, and get worse as more formats introduce additional specialty parameters. 

 

cc @nikitaved @pearu @cpuhrsch @amjames
Repository: pytorch
Issue: NVFuser should extend caching to remove necessity for PrimTorch's executor to Provide Tensor Contiguity Info
Labels: triaged,module: nvfuser,module: primTorch

### 🚀 The feature, motivation and pitch

Currently, PrimTorch's executor provides contiguity and tensor rank size information in the `FusionDefinition` for each fusion group sent to NVFuser.  This should be removed in favor of NVFuser receiving this information at runtime and caching the graph appropriately.

Therefore, the only information NVFuser should be provided in the Tensor Definition is the number of ranks of each Tensor. @mruberry does this match your understanding?

### Alternatives

_No response_

### Additional context

CC @csarofeen @jjsjann123 @ngimel @IvanYashchuk

cc @ezyang @mruberry @ngimel
Repository: tauri
Issue: [bug][macOS] After exiting the fullscreen, read window still is fullscreen
Labels: type: bug,platform: macOS

### Describe the bug

After exiting the fullscreen, below to the code print `true`

```rust
tauri::WindowEvent::Resized(_) => {
   println!("is_fullscreen {:?}", event.window().is_fullscreen());
}
```

<img width="712" alt="Screen Shot 2022-06-30 at 01 58 20" src="https://user-images.githubusercontent.com/3841872/176505099-4e9332d3-639f-4535-b00d-418e4cd81933.png">

Similarly, JS API does not meet expectations:

```ts
await window.__TAURI__?.window.getCurrent().isFullscreen()
```


### Reproduction

1. clone https://github.com/mantou132/tauri-app-test
2. cargo tauri dev
3. enter fullscreen and exiting fullscreen
4. view console

### Expected behavior

print: 
```
is_fullscreen Ok(true)
is_fullscreen Ok(false)
```

### Platform and versions

```shell
Environment
  › OS: Mac OS 12.4.0 X64
  › Node.js: 18.3.0
  › npm: 8.11.0
  › pnpm: 6.11.0
  › yarn: 1.22.15
  › rustup: 1.24.3
  › rustc: 1.63.0-nightly
  › cargo: 1.63.0-nightly
  › Rust toolchain: nightly-x86_64-apple-darwin 

Packages
  › @tauri-apps/cli [NPM]: 1.0.0
  › @tauri-apps/api [NPM]: 1.0.0-rc.7
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: pytorch
Issue: Nonliner conjugate gradient optimizer + Hager-Zhang line search
Labels: feature,module: optimizer,triaged,needs research

### 🚀 The feature, motivation and pitch

The nonlinear conjugate gradient (CG) method is a good alternative to the L-BFGS optimizer. Features of nonlinear CG:

1. It theoretically converges faster than gradient-descent methods (including most derived variants), and the memory footprint is just slightly higher than that of gradient-descent methods.
2. It is theoretically able to converge to machine precision, which may be important for regression-type problems when using single-precision floats.
3. Though it converges slower than L-BFGS does, it needs much less memory.
4. The specific CG method from Hager and Zhang automatically falls back to the vanilla gradient descent method (but with an auto-determined learning rate) if the conjugate direction does not perform better.
5. No need for configuring the learning rate. The step size (i.e., the learning rate) on the conjugate/gradient direction is determined by an inexact line search.
6. Hager and Zhang also proposed a companion inexact line-search algorithm for the proposed CG method.

I already have a working implementation of Hager and Zhang's nonlinear CG as a derived `torch.optim.Optimizer` class, including the inexact line search algorithm. I have been using this implementation for my own research. However, in terms of code tests, I only have two simple cases that can be used for code tests. But at least if this feature request is approved, we don't have to start from scratch.

This is directly related to #1359.

**Reference**
[1] W. W. Hager and H. Zhang, “Algorithm 851: CG_DESCENT, a conjugate gradient method with guaranteed descent,” ACM Trans. Math. Softw., vol. 32, no. 1, pp. 113–137, Mar. 2006, doi: 10.1145/1132973.1132979.

### Alternatives

_No response_

### Additional context

There are some issues mentioning implementing CG, like #53441 and #17902. However, I think they are more about linear CG, which is a special case of nonlinear CG. And I feel like linear and nonlinear CG solvers usually are implemented separately. So I don't think this feature request will resolve the issues requesting linear CG.

cc @vincentqb @jbschlosser @albanD
Repository: go
Issue: cmd/internal/obj: rework stack unwind metadata on LR machines
Labels: NeedsFix,compiler/runtime

On LR machines, our function prologue generally looks like (stack bounds check and frame pointer handling omitted): store the LR at `-frame_size(SP)`, then decrement SP to `SP-frame_size` (if they cannot be done on the same instruction, either due to the lack of the instruction on the architecture or the stack frame too large).

If we decrement the SP first, if a signal arrives immediately after the instruction before saving the LR, the runtime will see the junk value at the LR slot and will fail to unwind the stack. So we store the LR first then decrement the SP.

This generally works. But in some cases if the signal stack is not set (e.g. #53374 , also iOS doesn't support `sigaltstack`), the signal will arrive on the current stack and the kernel will push the signal frame immediately below the SP, clobbering our saved LR. In those cases we have to store the LR _again_ after decrementing the SP. This makes our function prologue a bit inefficient.

We can avoid the problem if we expand the stack unwind metadata to express "the SP has decremented but the return address is still in the LR register". Currently, the metadata is just about SP delta and the runtime always assumes the return address can be found at `0(SP)` (for non-leaf functions). With the expanded metadata, we can decrement SP and then store the LR.

This also makes our prologue more similar to C functions.

I plan to do it in Go 1.20.
Repository: yt-dlp
Issue: Don't use .webp in MKV attachments
Labels: bug,external issue,triage,core:post-processor

### Checklist

- [X] I'm reporting a bug unrelated to a specific site
- [X] I've verified that I'm running yt-dlp version **2022.06.29** ([update instructions](https://github.com/yt-dlp/yt-dlp#update)) or later (specify commit)
- [X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
- [X] I've checked that all URLs and arguments with special characters are [properly quoted or escaped](https://github.com/ytdl-org/youtube-dl#video-url-contains-an-ampersand-and-im-getting-some-strange-output-1-2839-or-v-is-not-recognized-as-an-internal-or-external-command)
- [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

When downloading thumbs, sometimes they come in .webp format.

Using `--embed-thumbnail` with a final format of MKV results in embedding the .webp directly into the MKV file as an attachment. Everything about how it's attached is fine, however various players (including VLC) are unable to render the .webp thumbnail, expecting it to be in JPEG or PNG format, per the [MKV attachment spec](https://matroska.org/technical/attachments.html) for cover thumbnails. It does say `SHOULD`, though if one were to want the widest compatibility, one `should` probably implement it that way.

I'd suggest a step of converting the webp to jpg or png (which ffmpeg can do).

### Verbose log

```shell
[EmbedThumbnail] ffmpeg: Adding thumbnail to "Bad Attraction! #Shorts [U3wL7_G3r8w].mkv"
[debug] ffmpeg command line: ffmpeg -y -loglevel "repeat+info" -i "file:Bad Attraction! #Shorts [U3wL7_G3r8w].mkv" -map 0 -dn -ignore_unknown -c copy -attach "Bad Attraction! #Shorts [U3wL7_G3r8w].webp" "-metadata:s:2" "mimetype=image/webp" "-metadata:s:2" "filename=cover.webp" -movflags "+faststart" "file:Bad Attraction! #Shorts [U3wL7_G3r8w].temp.mkv"
```
Repository: deno
Issue: deno_emit fails depending on whether or not a breakpoint is set.
Labels: bug

Not sure if this is a Deno issue, or a deno_emit issue, but it seems like debugging shouldn't affect the code like this so I'm assuming this is an issue with Deno.

**To reproduce:**

- create `emit.js`
```js
import {emit} from "https://deno.land/x/emit@0.3.0/mod.ts";

const result = await emit(new URL("https://deno.land/std@0.145.0/path/mod.ts"));
console.log(result);
```

- Run `deno run -A --unstable --inspect-brk emit.js`
- Connect a debugger (I'm using vscode since Chrome DevTools can't place breakpoints on files that haven't been run yet)
- place a breakpoint at the `console.log` line.
- Resume the debugger.

**Actual result**
`Uncaught (in promise) TypeError: WebAssembly.compile(): Argument 0 must be a buffer source`

**Expected result**
The code runs without any errors.

Some things to note:
- removing the breakpoint seems to make the code run, but when the process is done it keeps hanging rather than exiting automatically.
- removing `--inspect-brk` make the code run like normal.
- Enabling 'break on caught/uncaught exceptions' doesn't actually pause the debugger when the promise rejects, though I think I've seen this happen before with promises so this might be intended.
Repository: godot
Issue: Opening resources in the inspector makes ResourceSaver unable to rewrite variables containing subresources.
Labels: bug,topic:editor

### Godot version

3.4.4

### System information

W10

### Issue description

Inside a resource I have a subresource. When writing to disk using the ResourceSaver opening the resource on the inspector or having it open at runtime retains the value of the variable "permanently" until the whole project is restarted or the file is erased and recreated.  If instead of a variable with a single resource you have an array all the indexes that were occupied will be locked from being modified at runtime with ResourceSaver but making the array bigger will let you add new values to the array.

using integers, strings or arrays (that doesn't hold resources) didn't have any problems.


### Steps to reproduce

Add a resource to another resource and save it to disk using ResourceSaver
Open the file created in the inspector at runtime, once opened you don't need to keep it open the subresources will be locked until you restart the project.


https://user-images.githubusercontent.com/72952945/176541179-5e626fcd-852e-479e-8088-bb2653c1d731.mp4






### Minimal reproduction project


[Bug_ResourceSaver - minimal.zip](https://github.com/godotengine/godot/files/9014320/Bug_ResourceSaver.-.minimal.zip)
Repository: puppeteer
Issue: No documented way to measure TTFB
Labels: feature

### Bug description

```
    const browser = await puppeteer.launch(launchOptions);
    const page = await browser.newPage();
    await page.setDefaultNavigationTimeout(getDefaultTimeoutSeconds());
    const response = await page.goto(url);
    const { status,timing } = response;
    console.log(timing());
```

The `ResourceTiming` API expose some values, but not sure if they can be used calculate the TTFB.

### Puppeteer version

13.7.0

### Node.js version

16.15.1

### npm version

8.11.0

### What operating system are you seeing the problem on?

Linux

### Relevant log output

_No response_
Repository: pytorch
Issue: `bmm_sparse_cuda` kernel for `bfloat16`
Labels: module: sparse,module: cuda,triaged,module: bfloat16

### 🚀 The feature, motivation and pitch

The kernel would be useful for sparse attention with `bfloat16` weights

### Alternatives

```python
torch.bmm(
    sparse_matrix.float(),
    dense_matrix.float()
).to(torch.bfloat16)
```

### Additional context

_No response_

cc @nikitaved @pearu @cpuhrsch @amjames @ngimel
Repository: flutter
Issue: [flutter_tools] Have pub roller bot create a PR description with summary of changes
Labels: tool,P2,team-tool,triaged-tool

Related to https://github.com/flutter/flutter/issues/106371

It would be nice if the PR description for the auto-generated pub rolls, summarizing which packages were updated, and also the output of `dart pub outdated --json`.

In addition, we should add an allowlist of pub package owners who wish to be cc'd when an update rolls.