sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: const array of shader materials produces error
Labels: topic:gdscript,needs testing

### Godot version

4.0 alpha

### System information

Windows 10

### Issue description

Creating an const array of shader materials produces this error

`Line 13:Variant array is not compatible with an array of type "<unresolved type>".
`

changing the array to a var from const fixes the issue. Also changing the material from a shader material to a baseMaterial3D also fixes the error

### Steps to reproduce

Load an array of materials from a .tres file
```
const_materials = [
	preload("../blocks/terrain_material.tres"),
	preload("../blocks/terrain_material_transparent.tres"),
	preload("../blocks/terrain_material_foliage.tres")
]
```
If those are shader materials they will give an error

### Minimal reproduction project

_No response_
Repository: PowerToys
Issue: SVG preview inaccurate color respresentations
Labels: Issue-Bug,Product-File Explorer

### Microsoft PowerToys version

v0.61.0

### Running as admin

- [X] Yes

### Area(s) with issue?

ColorPicker, SVG Preview, SVG Thumbnail

### Steps to reproduce

1. Create SVG with green background (HEX 149911), and white text on top.
2. Preview SVG within file explorer
3. use color picker to pick the background color from the preview
4. color picker gets result that is not the original color defined in the SVG (in my case ~HEX d29b22). - When the SVG is opened, of course the correct color gets displayed again.

### ✔️ Expected Behavior

I expect the SVG preview to display the colors defined in the SVG. So that quickly reusing a color used within an SVG is possible. And i don't have to open up the SVG.

### ❌ Actual Behavior

Color displayed is different to the color defined in the SVG file.

### Other Software

Windows Explorer (Windows 10 build 19044.1826)
Repository: go
Issue: x/net/http2: slow streams can potentially block other faster streams
Labels: NeedsInvestigation

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.18.3 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/ronakj/Library/Caches/go-build"
GOENV="/Users/ronakj/Library/Application Support/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/ronakj/gocode/pkg/mod"
GONOPROXY="none"
GONOSUMDB="*"
GOOS="darwin"
GOPATH="/Users/ronakj/gocode"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GOVCS=""
GOVERSION="go1.18.3"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/ronakj/project/http2-issue-repro/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 x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/4d/2jw_2tc15x339gr53x6k64hm0000gn/T/go-build1453600270=/tmp/go-build -gno-record-gcc-switches -fno-common"
</pre></details>

### What did you do?
I'm using a Go HTTP2 (h2c) server as an Echo server, where the handler writes the request body in the response immediately for requests with the priority header `request-type=priority` otherwise delays the response by 5s. I use the HTTP2 client to dispatch two concurrent requests with a 2MB payload each, and one of them has a priority header set.

### What did you expect to see?
Priority response must arrive immediately. The non-priority response must arrive after a 5s delay. 
According to the RFC, one stream must not block another stream on the same connection.

### What did you see instead?
Both non-priority and priority responses arrived after 5s. This should not have happened as HTTP2 streams on the same connections must not interfere with each other.

Repro-
- [Playground](https://go.dev/play/p/IT7mb_Q2_tH)
- [Detailed repository](https://github.com/jronak/go-issue-repro/tree/main/issue-54330)

# Root Cause
Go HTTP2 server returns client connection flow control bytes back only after the application handler has read the body bytes. This blocks the client from writing the data frame of streams due to a lack of flow control window when a few slow/inactive streams consume the entire window size.
Repository: rust
Issue: Get length of packet from datagram sockets (`UdpSocket`, `UnixDatagram`)
Labels: T-libs-api,C-feature-request

## Summary
Provide an API to peek/get the length of the datagram

The unstable feature `unix_socket_peek` adds methods `peek` and `peek_from` for `UnixDatagram` and `UnixStream`. While they allow to peek at the the data, however, the API returns the number of bytes read on success. To get the length of the datagram instead of the bytes read, in an API similar to `peek`,  `MSG_TRUNC` `or`ed with the `MSG_PEEK` flag can be passed to the `recv` call, which would only `peek` at the data but return the length the next datagram on success.

## Motivation
This can be helpful in use cases for memory usage optimization where we can allocate buffers dynamically with just enough size for reading the data packet. This is helpful when the connections or message are infrequent, for example, an application configuration message.
Repository: godot
Issue: Proximity Fade causes SpatialMaterials to not render in HTML5 with GLES2
Labels: bug,platform:web,topic:rendering,confirmed,topic:3d

### Godot version

3.5.stable, 3.4.5

### System information

Pop!_OS 22.04/Windows 10, GLES2, Firefox/Edge

### Issue description

With the GLES2 backend, SpatialMaterials with Proximity Fade enabled don't render at all in HTML5.

In the web editor, the error `drivers/gles2/rasterizer_storage_gles2.cpp:5665 - MSAA not supported on this hardware.` is printed every time Proximity Fade is toggled in the inspector.

### Steps to reproduce

Export and run the minimal reproduction project in HTML5. The red cube has Proximity Fade enabled and will be invisible in HTML5. The blue cube does not have Proximity Fade enabled and should remain visible.

### Minimal reproduction project

[proximity_fade_bug.zip](https://github.com/godotengine/godot/files/9277718/proximity_fade_bug.zip)
Repository: opencv
Issue: Building XCFramework using build_framework.py with --contrib fails on M1 machines
Labels: category: build/install,platform: ios/osx,incomplete

**Running the command:**
```
python opencv/platforms/apple/build_xcframework.py --contrib opencv_contrib --out opencv_deploy --iphoneos_archs arm64 --iphonesimulator_archs arm64 --macos_archs arm64 --build_only_specified_archs

Fails with errors:

Build all projects

** BUILD FAILED **


The following build commands failed:
	CompileSwift normal arm64 /opencv_deploy/macos/build/build-arm64-macosx/modules/objc_bindings_generator/osx/gen/objc/wechat_qrcode/Wechat_qrcodeExt.swift (in target 'opencv2' from project 'opencv2')
	CompileSwift normal arm64 /opencv_deploy/macos/build/build-arm64-macosx/modules/objc_bindings_generator/osx/gen/objc/xfeatures2d/Xfeatures2dExt.swift (in target 'opencv2' from project 'opencv2')
	CompileSwift normal arm64 /opencv_deploy/macos/build/build-arm64-macosx/modules/objc_bindings_generator/osx/gen/objc/ximgproc/XimgprocExt.swift (in target 'opencv2' from project 'opencv2')
	SwiftCompile normal arm64 Compiling\ Wechat_qrcodeExt.swift,\ Xfeatures2dExt.swift,\ XimgprocExt.swift /opencv_deploy/macos/build/build-arm64-macosx/modules/objc_bindings_generator/osx/gen/objc/wechat_qrcode/

etc

CompileSwift normal arm64 /opencv_deploy/macos/build/build-arm64-macosx/modules/objc_bindings_generator/osx/gen/objc/core/CoreExt.swift (in target 'opencv2' from project 'opencv2')
	CompileC /opencv_deploy/macos/build/build-arm64-macosx/modules/objc/framework_build/opencv2.build/Release/opencv2.build/Objects-normal/arm64/ArucoDetector.o /opencv_deploy/macos/build/build-arm64-macosx/modules/objc_bindings_generator/osx/gen/objc/aruco/ArucoDetector.mm normal arm64 objective-c++ com.apple.compilers.llvm.clang.1_0.compiler (in target 'opencv2' from project 'opencv2')
(35 failures)
============================================================
ERROR: Command '['xcodebuild', 'MACOSX_DEPLOYMENT_TARGET=13.0', 'ARCHS=arm64', '-sdk', 'macosx', '-configuration', 'Release', '-parallelizeTargets', '-jobs', '8', '-target', 'ALL_BUILD', 'build']' returned non-zero exit status 65.
```

Note that trying to build with x86_64 fails as well but that's a different issue.


Looks like this is some paths issue so not sure how to fix it.

I can create: opencv2.xcframework if no --contrib modules are added.
Repository: vscode
Issue: Support displaying inherited members in outline view
Labels: feature-request,outline

<!-- ⚠️⚠️ 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. -->

In most programming languages like Java, a class usually have inherited members. Popular Java IDEs can show those inherited members in the outline views (with a switch button to control whether to display those inherited members):

![image](https://user-images.githubusercontent.com/6193897/183322210-ae77c647-ae5f-4b49-ba63-a535fbc985ba.png)

While this is not feasible in VS Code because the type [DocumentSymbol](https://github.com/microsoft/vscode/blob/afbe9605e56c31538d95365d306e21ddfb951d55/src/vscode-dts/vscode.d.ts#L3239) only has the field to specify range, but no uri. Seems that there is no way to point to a location which is out of current active document.
Repository: youtube-dl
Issue: ERROR: Youku server reported error -6001: ccode参数错误
Labels: incomplete

<!--

######################################################################
  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:
- First of, make sure you are using the latest version of youtube-dl. Run `youtube-dl --version` and ensure your version is 2021.12.17. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Make sure that all provided video/audio/playlist URLs (if any) are alive and playable in a browser.
- Make sure that all URLs and arguments with special characters are properly quoted or escaped as explained in http://yt-dl.org/escape.
- Search the bugtracker for similar issues: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Read bugs section in FAQ: http://yt-dl.org/reporting
- Finally, put x into all relevant boxes (like this [x])
-->

- [ ] I'm reporting a broken site support issue
- [x] I've verified that I'm running youtube-dl version **2021.12.17**
- [ ] I've checked that all provided URLs are alive and playable in a browser
- [ ] I've checked that all URLs and arguments with special characters are properly quoted or escaped
- [ ] I've searched the bugtracker for similar bug reports including closed ones
- [ ] I've read bugs section in FAQ


## Verbose log

<!--
Provide the complete verbose output of youtube-dl that clearly demonstrates the problem.
Add the `-v` flag to your command line you run youtube-dl with (`youtube-dl -v <your command line>`), copy the WHOLE output and insert it below. It should look similar to this:
 [debug] System config: []
 [debug] User config: []
 [debug] Command-line args: [u'-v', u'http://www.youtube.com/watch?v=BaW_jenozKcj']
 [debug] Encodings: locale cp1251, fs mbcs, out cp866, pref cp1251
 [debug] youtube-dl version 2021.12.17
 [debug] Python version 2.7.11 - Windows-2003Server-5.2.3790-SP2
 [debug] exe versions: ffmpeg N-75573-g1d0487f, ffprobe N-75573-g1d0487f, rtmpdump 2.4
 [debug] Proxy map: {}
 <more lines>
-->

```
PASTE VERBOSE LOG HERE
```


## Description

<!--
Provide an explanation of your issue in an arbitrary form. Please make sure the description is worded well enough to be understood, see https://github.com/ytdl-org/youtube-dl#is-the-description-of-the-issue-itself-sufficient. Provide any additional information, suggested solution and as much context and examples as possible.
If work on your issue requires account credentials please provide them or explain how one can obtain them.
-->

WRITE DESCRIPTION HERE
Repository: rust
Issue: Should rustdoc support links in headings?
Labels: T-rustdoc,C-discussion,A-rustdoc-ui,A-markdown-parsing

Markdown allows links to appear in headings, but rustdoc doesn't (properly) support this. @GuillaumeGomez had a PR to implement this: #94360. However, supporting this feature makes other parts of rustdoc's UI worse: Currently, rustdoc makes headers link to themselves (to make grabbing a link to the header easier). If we supported user links in headers, this wouldn't work anymore. We could use “§”, but it presents a small click target and adds visual noise. So, more discussion is needed.

- [ ] Determine rustdoc's status quo for this feature
- [ ] Decide whether it makes sense to support this
  - [ ] If yes, decide how header self-links should be implemented
  - [ ] If no, decide if we should warn when users make links in headers, or if we should maintain the status quo
Repository: godot
Issue: Tileset file (*.tres) changes are only saved on the first save, then require an editor restart to save another change.
Labels: bug,topic:editor,topic:2d

### Godot version

3.5.stable.mono

### System information

Windows 10 64-bit

### Issue description

I changed the collision shapes of two tiles in a tileset file, saving after each individual tile's change. After running the game, I noticed only the first tile had the new collision shape. Git confirmed that no file change was detected. As a test, I opened the tileset *.tres file in Notepad++, edited the tileset, saved, and was prompted by Notepad++ to reload the file because it had changed. I then made another change within Godot, saved, and neither Git nor Notepad++ detected an additional change to the tileset file. Closing the Godot Editor and relaunching allows me to make another saved change on the tileset file, requiring another editor restart to save any further changes.

### Steps to reproduce

1. Create a Tileset resource file.
2. Open the resource file in an application that detects changes to the file contents, such as most source control software or Notepad++.
3. Make a change to it within Godot, then save.
4. Note that the file change is detected.
5. Make another change to it within Godot, then save again.
6. Note that the file change is _not_ detected.

### Minimal reproduction project

_No response_
Repository: godot
Issue: The UI for the Godot editor doesn't display any text (Linux distro package with system freetype without brotli support)
Labels: platform:linuxbsd,topic:editor,topic:thirdparty,topic:gui

### Godot version

3.5.1

### System information

Linux 5.18.16_1, Intel UHD Graphics 620

### Issue description

When i open Godot, the user interface doesn't display any text. Here is an image:
![image](https://user-images.githubusercontent.com/86479460/183326667-01fce918-8b7f-4367-b380-288966621f2f.png)
Occurred after the atulization of godot 3.4 to 3.5


### Steps to reproduce

error shown when running by terminal:
![image](https://user-images.githubusercontent.com/86479460/183327042-06022243-7c1a-49f5-8cde-1ef30be5adcd.png)


### Minimal reproduction project

_No response_
Repository: deno
Issue: `deno-fmt-ignore` behavior in JSONC is unintuitive
Labels: suggestion,deno fmt

`deno fmt` doesn't like trailing commas in JSONC, which is mostly fine since we can just let it ignore them, but the behavior is unintuitive.

This works:

```jsonc
{
  // deno-fmt-ignore
  "tasks": {
    "foo": "echo bar",
  }
}
```

```shellsession
$ deno fmt --check
Checked 240 files
```

But this doesn't work, which places the comment to the desired location:

```jsonc
{
  "tasks": {
    // deno-fmt-ignore
    "foo": "echo bar",
  }
}
```

```shellsession
$ deno fmt --check

from /workspaces/lume/tests/assets/deno.jsonc:
4 | -    "foo": "echo bar",
4 | +    "foo": "echo bar"

error: Found 1 not formatted file in 240 files
```

This doesn't work either, though I'm not sure if other formatters support this comment style:

```jsonc
{
  "tasks": {
    "foo": "echo bar", // deno-fmt-ignore
  }
}
```
Repository: storybook
Issue: 【Vuetify】TypeError: Cannot read property 'styles' of undefined
Labels: bug,needs triage

**Describe the bug**

`yarn storybook` report an error:

```bush
ModuleBuildError: Module build failed (from ./node_modules/vue-loader/dist/index.js):
TypeError: Cannot read property 'styles' of undefined
```

**To Reproduce**

https://github.com/codthing-bug/vuetify-sb-setupbug.git

**System**

```bush
Environment Info:

  System:
    OS: Windows 10 10.0.22000
    CPU: (12) x64 Intel(R) Core(TM) i5-10500 CPU @ 3.10GHz
  Binaries:
    Node: 14.18.3 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 6.14.15 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.22000.120.0), Chromium (104.0.1293.47)
  npmPackages:
    @storybook/addon-actions: ^6.5.10 => 6.5.10
    @storybook/addon-essentials: ^6.5.10 => 6.5.10
    @storybook/addon-interactions: ^6.5.10 => 6.5.10
    @storybook/addon-links: ^6.5.10 => 6.5.10
    @storybook/builder-webpack5: ^6.5.10 => 6.5.10
    @storybook/manager-webpack5: ^6.5.10 => 6.5.10
    @storybook/testing-library: ^0.0.13 => 0.0.13
    @storybook/vue: ^6.5.10 => 6.5.10
```

**Additional context**
Repository: PowerToys
Issue: [keyboard manager] remap shortcuts to multiple key stroke
Labels: Idea-Enhancement,Product-PowerToys Run,Needs-Triage

### Description of the new feature / enhancement

remap shortcuts to multiple keystroke (not sure if my expression is proper)
e.g. `win+r` -> `alt+space`, `>`
![image](https://user-images.githubusercontent.com/107602397/183341860-6688a75b-8914-4c1f-9307-0664b200de66.png)


### Scenario when this would be used?

for example, remap win+r to powertoys run shell plugin

### Supporting information

_No response_
Repository: go
Issue: x/tools/go/analysis/passes/fieldalignment/cmd/fieldalignment: comments are removed
Labels: NeedsInvestigation,Analysis

<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.16.13 darwin/arm64
</pre>

### Does this issue reproduce with 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

</pre></details>

### What did you do?

When I execute the following command, I found that the field comments in the fixed struct are not preserved, you can try it, I don't quite understand why the original comments are removed. Please take a look, thank you.
```bash
$ fieldalignment -fix ./... 
```

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on go.dev/play is best.
-->



### What did you expect to see?

```go

type UserLoginStatus struct {
	Type        uint8  `json:"type"`                   // 1:online，2: offline
	UserID      string `json:"user_id"`                // userid
	DeviceID    string `json:"device_id"`              // IMEI
}
```


### What did you see instead?

```go

type UserLoginStatus struct {
	UserID      string `json:"user_id"`                
	DeviceID    string `json:"device_id"`        
        Type        uint8  `json:"type"`                      
}
```
Repository: TypeScript
Issue: never extends `${infer P}` yield a different result than never extends `${infer P}/`
Labels: Bug

# Bug Report

<!--
  Please fill in each section completely. Thank you!
-->

### 🔎 Search Terms

never extends `${infer P}` yield different result than never extends `${infer P}/`

### 🕗 Version & Regression Information

TS 4.7

type is not what expected

### ⏯ Playground Link

[playground](https://www.typescriptlang.org/play?#code/C4TwDgpgBAhlC8UB2EBuEBOUIA9gSQBMBnKAAwBIBvASyQDNMoAFAXzKgH4WoAuKAIxQoAehHI0mAFBjhUAHqcpoSFABGCCeiy58RUpVoMmbER27M+UAEyjxxYBjoBzGeOGKpy8NBhDEKNrYeAQk5NR0jFiWuqGkDk5IzuxcPPxCsoHSsh5KKtBq-lpMsfrhRlE8pWEJLqxmqZb8trK1SW5ynt6qMLYBkjohZYaRJsF6YUgArgC2apgpFlYZ4lkYHbndBX3FgxMGEcbR43HIs-MY9eZpNnZnc9nuCkpbsADMmmsnw4eVMUOTKYAGyBixuK12G2erzUH36QWqBwqY0RZxBV0aVhaq2BQKhXXysAALJ8Bt8wiMjlUAaQpkQIPQ6BBCGCmoI7mt8XkfOoSfCSjTyqNjqi6YQGUyWQ0ls07mKJShCFyvISYABWUkIwWUv7k0hqAD2BqBEBgSFZyw5A2VhLUGv5e1OOpRgsNxtN5ulN2x6iNJrNyteMAAbJqBfshVT-hG1DRnHRgBb0lbtDaeWpQw69ZHdajY-GkImvWyffmE8qgA)

### 💻 Code
```ts
type a = never extends `${infer P}` ? P : 1  // never
//   ^?
type b = never extends `${infer P}/` ? P : 2 // string
//   ^?

type a1 = never extends `${infer P extends string}` ? P : 1 // never
//   ^?
type b1 = never extends `${infer P extends string}/` ? P : 2 // string
//   ^?

type a2 = never extends `${infer P extends number}` ? P : 1 // never
//   ^?
type b2 = never extends `${infer P extends number}/` ? P : 2 // number
//   ^?

type a3 = never extends `${infer P extends null}` ? P : 1 // never
//   ^?
type b3 = never extends `${infer P extends null}/` ? P : 2 // null
//   ^?

type a4 = never extends `${infer P extends undefined}` ? P : 1 // never
//   ^?
type b4 = never extends `${infer P extends undefined}/` ? P : 2 // undefined
//   ^?

type a5 = never extends `${infer P extends boolean}` ? P : 1 // never
//   ^?
type b5 = never extends `${infer P extends boolean}/` ? P : 2 // boolean
//   ^?

type a6 = never extends `${infer P extends bigint}` ? P : 1 // never
//   ^?
type b6 = never extends `${infer P extends bigint}/` ? P : 2 // bigint
//   ^?
```

### 🙁 Actual behavior

1. never extends `${infer P}/` yield the same result as never extends `${infer P}`
2. never extends `${infer P extends X}/` yield X but never extends `${infer P extends X}` always yield never

### 🙂 Expected behavior

1. never extends `${infer P}/` should yield never like never extends `${infer P}`
2. never extends `${infer P extends X}/`  yield never like never extends `${infer P extends X}`

are these intended behaviors? kind of unintuitive
Repository: rust
Issue: On bin crates with both lib.rs and main.rs, recursion_limit hint is correct only for lib.rs
Labels: A-diagnostics,T-compiler

On bin crates with both lib.rs and main.rs, when the compiler overflows evaluating the requirement of a type, it correctly prints an hint like
```
    = help: consider increasing the recursion limit by adding a `#![recursion_limit = "256"]` attribute to your crate (`foo`)
    = note: required because it appears within the type `Foo`
   [...really long list of type requirements...]
```

If you put it only on main.rs, the error message doesn't change at all, so the first thing the user will think it's the directive has been put on the wrong fiile.
Putting it only on lib.rs changes the error, that loses all the hints and becomes a really concise
```
error: overflow representing the type `Unique<dyn futures_core::stream::Stream<Item = Result<Foo, Bar>> + Send>`

error: could not compile `foo` due to previous error
```

At this point the user is lost, the solution is to put the directive on both main.rs and lib.rs, but it's not obvious, the compilerr should hint it