sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Area3D with ConcavePolygonShape3D Emits Incorrect Signals
Labels: bug,topic:physics,topic:3d

### Godot version

Godot 4.1.1 stable

### System information

Manjaro Linux - GL Compatibility

### Issue description

When an Area3D is accompanied by a ConcavePolygonShape3D it will emit body_entered and body_exited signals back to back. Given a ConcavePolygonShape3D the Area3D will emit the body_entered signal when the body first touches a face in the ConcavePolygonShape3D. When the body has fully entered the ConcavePolygonShape3D the Area3D will emit the body_exited signal, though the body is actually fully within the bounds of the ConcavePolygonShape3D. Upon exiting the polygon shape the Area3D will again emit the body_entered signal, when the body touches another face on the ConcavePolygonShape3D as it exits the area, then again emit the body_exited signal.

In short, when passing straight through an Area3D using a ConcavePolygonShape3D the Area3D will emit four signals; body_entered, body_exited, body_entered, body_exited, as opposed to just two signals; body_entered, body_exited.

### Steps to reproduce

-Import any mesh from you favorite modelling suite

-Create a new 3D scene in Godot

-Import the mesh into the scene

-Select the Mesh and then select Mesh --> Create Trimesh Collision Sibling

-Create an Area3D node and make the newly created CollisionShape3D a child of it

-Create a script on any of the scene nodes and connect the Area3D's body_entered and body_exited signals to it

### Minimal reproduction project

[AreaCollision.zip](https://github.com/godotengine/godot/files/12337673/AreaCollision.zip)
Repository: go
Issue: x/tools/gopls: document supported postfix snippets
Labels: Documentation,NeedsInvestigation,FeatureRequest,gopls,Tools

https://github.com/golang/go/issues/61763 is adding a `.nn!` postfix, which is not very discoverable. 
Add documentations for supported postfix completions.
Repository: pytorch
Issue: DISABLED test_learnable_forward_per_channel_cpu (quantization.core.test_workflow_ops.TestFakeQuantizeOps)
Labels: triaged,module: macos,skipped

Platforms: macos, mac

This test was disabled because it is failing on main branch ([recent examples](http://torch-ci.com/failure/test_quantization.py%3A%3ATestFakeQuantizeOps%3A%3Atest_learnable_forward_per_channel_cpu)).

cc @malfet @albanD
Repository: go
Issue: x/net/trace: dependency on html/template inhibits dead code elimination
Labels: help wanted,NeedsInvestigation,binary-size,compiler/runtime

Any use of `reflect.Value.MethodByName()` or `reflect.Type.MethodByName()` disables the DCE. The compiler assumes that these functions will look any method up, and cannot remove methods even if they are never called.

`text/template` and `html/template` are very notable offenders in this respect. They call `MethodByName()` on random strings extracted from template texts.

The package `x/net/trace` uses `html/template`, hence any user of `x/net/trace` compiles with DCE disabled. Worse yet, the package's `init()` references `html/template` which disables DCE even if `x/net/trace` is imported, but otherwise unused.

There is a very popular user of `x/net/trace`, namely `google.golang.org/grpc`. Essentially, this means that a lot of networked services in golang are compiled without DCE.

### What did you expect to see?

I expect that a low-level library that is used by almost everyone does not pessimise the code generation by disabling the DCE. I'd avoid `html/template` altogether.
Repository: flutter
Issue: Use a Stack not Navigator for all these showDialog methods
Labels: framework,f: material design,f: routes,c: proposal,P3,team-design,triaged-design

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Use case

We should use Stack and not pop from the navigation stack without ever pushing onto it. Other Dialog libs are used instead of the ones in the core framework because they don't require that BuildContext AND they don't mess with your navigation stack but just insert themselves at the top of the Widget tree using Stack. Way too much in the core framework requires BuildContext when it doesn't have to
https://github.com/flutter/flutter/blob/ec0b7443c42691df6b86cf9bd5d84e3b63cadefe/packages/flutter/lib/src/material/dialog.dart#L1402


### Proposal

example: https://pub.dev/packages/flutter_smart_dialog
Repository: rust
Issue: Suggest `--ignored` when libtest ignores a test
Labels: A-diagnostics,A-libtest

### Code

```Rust
; cat src/lib.rs
#[test]
#[ignore = "takes too long 😩"]
fn i_am_slow() {
    std::thread::sleep(std::time::Duration::from_secs(5));
    println!("it works!");
}
; cargo test --lib --quiet
```


### Current output

```Shell
running 1 test
i
test result: ok. 0 passed; 0 failed; 1 ignored; 0 measured; 0 filtered out; finished in 0.00s

test: i_am_slow, ignore_message: takes too long 😩
```


### Desired output

```Shell
running 1 test
i
test result: ok. 0 passed; 0 failed; 1 ignored; 0 measured; 0 filtered out; finished in 0.00s

test: i_am_slow, ignore_message: takes too long 😩

note: to run ignored tests, use `--ignored`
```


### Rationale and extra context

See https://github.com/rust-lang/cargo/issues/12494; currently this will be confusing for people using cargo so I'd like to fix that issue first.

### Other cases

If no tests are ignored, this help message shouldn't be printed.

### Anything else?

_No response_

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"RickleAndMortimer"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: go
Issue: x/build: LUCI support for plan9
Labels: OS-Plan9,Builders,NeedsInvestigation

In https://github.com/golang/go/issues/61671#issuecomment-1661755492, @millerresearch reported that the plan9 builders don't support python3. The LUCI swarming bot requires python3, which means that we aren't going to be able to test plan9 once we finish our migration. We can probably keep the old infrastructure going through the 1.22 cycle, but after that we'll likely have to declare the ports as broken in 1.23.

 I have no idea how much work it would be to port python3 to plan9. I imagine that if it were easy to do it'd have been done already...? The LUCI team has long-term plans to port the bot to Go but it won't happen on our timeline. (For the record, even with Python supported, the LUCI project has a number of other programs that we'd really like to have working. Fortunately, those are already written in Go and porting them should be pretty easy. Worst case we may be able to work around them.)

Alternatively, maybe it's possible to run it virtualized somehow, say with the bot running under linux, then booting a qemu VM to do its work? The plan9 builders are already kinda slow, though.

cc @golang/plan9 @golang/release
Repository: next.js
Issue: blurDataURL inflates bundle even when not used
Labels: Image (next/image)

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: linux
      Arch: x64
      Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
    Binaries:
      Node: 16.17.0
      npm: 8.15.0
      Yarn: 1.22.19
      pnpm: 7.1.0
    Relevant Packages:
      next: 13.4.15-canary.0
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.3
    Next.js Config:
      output: N/A
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

Image optimization (next/image, next/legacy/image)

### Link to the code that reproduces this issue or a replay of the bug

https://codesandbox.io/p/sandbox/tender-morning-84653l

### To Reproduce

Import a large image into any page while image optimization is enabled for the project. For extra points, and extra bundle bloat, import an animated image. Use the image with `next/image`, but do not enable the blur placeholder.

Build the project and inspect the JS bundle for the page the image is used on.

### Describe the Bug

The Webpack loader for images in Next.js *always* injects a blurDataURL into the JS bundle, even if it is unused in the code. It looks like in 13.4.8 some sort of tree-shaking was added that makes this no longer an issue for the native image tag, but this is still a problem for `next/image`.

For large images, and especially animated images where the "blur" image is just the original image, this massively inflates the JS bundle. There does not appear to be a way to opt-out of this blurDataURL being generated for a specific image, unless you opt the entire project out of using the image optimization, which means without this being tree-shaken correctly, there is no way to escape this bundle inflation if you want to use `next/image`.

https://github.com/vercel/next.js/blob/c4f9c6d492d5daf3b470a755eaf3d0f68dd0df08/packages/next/src/build/webpack-config.ts#L2198-L2220

https://github.com/vercel/next.js/blob/c4f9c6d492d5daf3b470a755eaf3d0f68dd0df08/packages/next/src/build/webpack/loaders/next-image-loader/index.ts#L45-L54

https://github.com/vercel/next.js/blob/c4f9c6d492d5daf3b470a755eaf3d0f68dd0df08/packages/next/src/build/webpack/loaders/next-image-loader/blur.ts#L68-L84 (note that if the image is detected as animated, the entire content is used for the base64 blur image, which then ends up directly in the JS bundle)

### Expected Behavior

For animated images, it probably makes sense to return an empty blurDataURL, rather than trying to use the *entire* animated image as the blurDataURL.

For other images, it'd be nice to see a way to opt-out of the blurDataURL being generated by Webpack (perhaps a query param), or for it to be properly tree-shaken when not used, like it is if you use a native image tag.

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: flutter
Issue: Notify Embedder when a platform channel listener is registered
Labels: c: new feature,engine,e: embedder,P2,team-engine,triaged-engine

Allow the embedder to respond to registering a platform channel listener so it may, for example, enable app lifecycle and graceful exit without needing an explicit message from the framework to do so.
Repository: angular
Issue: Unhandled rejections events not emitted when using DISABLE_WRAPPING_UNCAUGHT_PROMISE_REJECTION
Labels: area: zones

### Which @angular/* package(s) are the source of the bug?

zone.js

### Is this a regression?

No

### Description

Setting `DISABLE_WRAPPING_UNCAUGHT_PROMISE_REJECTION` to true will cause unhandled rejections events to not be emitted because of an exception inside the code that sends the events.

```javascript
__zone_symbol__DISABLE_WRAPPING_UNCAUGHT_PROMISE_REJECTION = true;
// load zone.js
onunhandledrejection = console.dir;
Promise.reject(new Error("forced error"));
```

The above code doesn't call the unhandled rejection handler. Zone.js triggers an internal exception while trying to emit the event and this event is caught and silently ignored.
thrown from: https://github.com/angular/angular/blob/f7cfc3b8fa2c2b2ef0bc2d4086edce70a17944bf/packages/zone.js/lib/browser/browser.ts#L280
Caught and ignore at: https://github.com/angular/angular/blob/f7cfc3b8fa2c2b2ef0bc2d4086edce70a17944bf/packages/zone.js/lib/common/promise.ts#L71

Exception thrown
```
TypeError: Failed to construct 'PromiseRejectionEvent': Failed to read the 'promise' property from 'PromiseRejectionEventInit': Required member is undefined.
```

The issue is that with `DISABLE_WRAPPING_UNCAUGHT_PROMISE_REJECTION` enabled causes the error send to the handler that emits events to be the original error and not the wrapper error. Only the wrapper error has promise and rejection properties that the handler was using to construct the rejection event.
https://github.com/angular/angular/blob/f7cfc3b8fa2c2b2ef0bc2d4086edce70a17944bf/packages/zone.js/lib/common/promise.ts#L52-L69

 The issue doesn't happen for the promise rejection handled handler since it gets both the promise and the rejection.
https://github.com/angular/angular/blob/f7cfc3b8fa2c2b2ef0bc2d4086edce70a17944bf/packages/zone.js/lib/common/promise.ts#L236


### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

_No response_

### Please provide the environment you discovered this bug in (run `ng version`)

_No response_

### Anything else?

_No response_
Repository: ant-design
Issue: Select in multiple mode adds unnecessary height when selecting options with long label
Labels: Inactive

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/multiple-selection-antd-5-8-3-forked-5jq32z?file=/demo.tsx)

### Steps to reproduce

1. Select the first option which is very long

### What is expected?

Select height should not change when selecting one item with long label

### What is actually happening?

Select height doubles

| Environment | Info |
| --- | --- |
| antd | 5.8.3 |
| React | 16.x |
| System | Windows |
| Browser | Chrome |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: godot
Issue: Tilemap autotiling too slow to be updated every frame
Labels: discussion,needs testing,topic:2d,performance

### Godot version

4.1

### System information

Multiple:

- NixOS: Godot v4.1.stable (970459615) - NixOS 23.05 (Stoat) - Vulkan (Compatibility) - AMD Radeon RX 580 Series (polaris10, LLVM 15.0.7, DRM 3.49, 6.1.44) - AMD Ryzen 7 5700X 8-Core Processor (16 Threads)
- macOS (detailed system information not collected)

### Issue description

It seems like there might be a performance issue with `TileMap.set_cells_terrain_connect`.

We have a project in which we are using `TileMap`s to auto-tile a [blob tileset](http://www.cr31.co.uk/stagecast/wang/blob.html), using the "Match Corners and Sides" terrain mode. Each frame, we update the cells of three small `TileMap`s (10x8) by calling `clear()` followed by calling `set_cells_terrain_connect`. This results in an FPS of ~50 on my machine, with the in-engine profiler showing more than 16ms elapsed in "Process time".

Are we using `set_cells_terrain_connect` for a purpose it wasn't designed for?

I glanced at the C++ implementation of `set_cells_terrain_connect` and saw that it's capable of much more than what we were using it for, so I substituted it with specialized tiling logic written in GDScript. Surprisingly, that raised the FPS to over 1000!

It is of course expected that specialized code would be faster, but given the size of the difference, could it be possible that there is a performance issue in `set_cells_terrain_connect`? At the very least, its current performance rules out its use in a real-time game that auto-tiles every frame.


### Steps to reproduce

@sourencho has prepared a demo project, linked below, which compares the FPS of using `set_cells_terrain_connect` and the custom auto-tiling logic. Run the project and use the toggle to switch between the two auto-tiling implementations and observed the displayed FPS. See its README.md for more details.

### Minimal reproduction project

- Git repo: https://github.com/sourencho/godot_tilemap_fps_demo
- Archive of the git repo at issue submission time: [demo_project.zip](https://github.com/godotengine/godot/files/12338999/demo_project.zip)
Repository: next.js
Issue: Redirect function doesnt work inside conditionally rendered parallel route to go up route tree
Labels: bug,Navigation

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Pro
    Binaries:
      Node: 20.2.0
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant Packages:
      next: 13.4.13
      eslint-config-next: 13.4.13
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.6
    Next.js Config:
      output: N/A
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

Routing (next/router, next/navigation, next/link)

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/af-lozano/nextjs-redirect.git

### To Reproduce

Clone git repository and run with npm run dev. Navigate on the browser to /projects/1. The last segment is dynamic so it can be anything. When pushing the create button, a modal with a form renders as a conditional parallel route. When submiting, a server action is handled. In this case, it only contains a redirect to the current route, without the last segment. The expected behaviour should be to close the modal going up to the parent route. If the redirect route inside the redirect function (src/app/projects/[project]/@create/create/page.js) is hardcoded with say 2, or any other dynamic segment, the redirect works as expected, closing the modal and redirecting.

### Describe the Bug

The redirect function doesnt work when its route is the parent of a conditionally rendered parallel route.

### Expected Behavior

The redirect function should navigate to the route above the conditionally rendered parallel route.

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: go
Issue: proposal: crypto/uuid: add API to generate and parse UUID
Labels: Proposal

I would like to suggest the addition to the standard library of a package to generate and parse UUID identifiers, specifically versions 3, 4 and 5.

The main reason I see to include it is that the most popular 3rd-party package ([github.com/google/uuid](https://github.com/google/uuid)) is a staple import in every server/db based Go program, as confirmed by a quick [Github code search](https://github.com/search?q=github.com%2Fgoogle%2Fuuid+language%3AGo&type=code&l=Go).

Additionally:

- UUID is [a standard](https://www.rfc-editor.org/rfc/rfc4122);
- The interface exposed by [github.com/google/uuid](https://github.com/google/uuid) has been stable for years.

**Addendum**

Would like to point out how Go is rather the exception than the norm with regards to including UUID support in its standard library.

- [C#](https://learn.microsoft.com/en-us/dotnet/api/system.guid.newguid?view=net-7.0&redirectedfrom=MSDN#System_Guid_NewGuid)
- [Java](https://docs.oracle.com/javase/8/docs/api/java/util/UUID.html)
- [JavaScript](https://developer.mozilla.org/en-US/docs/Web/API/Crypto/randomUUID)
- [Python](https://docs.python.org/3/library/uuid.html)
- [Ruby](https://ruby-doc.org/stdlib-1.9.3/libdoc/securerandom/rdoc/SecureRandom.html#method-c-uuid)
Repository: neovim
Issue: checkhealth: check for latest perl module is broken
Labels: bug,runtime,provider

### Problem

Older version of nvim correctly detects latest version of Neovim::Ext as 0.06 when using :checkhealth

Current dev version improperly reports current version incorrectly as 5 and with 0.06 installed being out of date as below:

- WARNING Module "Neovim::Ext" is out-of-date. Installed: 0.06, latest: 5
  - ADVICE:
    - Run in shell: cpanm -n Neovim::Ext

From what I can tell, the command to get the string to regex and get current version evaluates to the following on my local machine:

    /usr/bin/perl -MApp::cpanminus::script -e 'my $app = App::cpanminus::script->new; $app->parse_options ("--info", "-q", "Neovim::Ext"); exit $app->doit'

which when run from command line gives an error containing `Can't locate App/cpanminus/script.pm in @INC (you may need to install the App::cpanminus::script`

`cpan -i App::cpanminus::script` fails on the local machine as follows:

    (error): Could not expand [App::cpanminus::script]. Check the module name.
    (info): I can suggest names if you install one of Text::Levenshtein::XS, Text::Levenshtein::Damerau::XS, Text::Levenshtein, and Text::Levenshtein::Damerau::PP
    (info): and you provide the -x option on invocation.
    (error): Skipping App::cpanminus::script because I couldn't find a matching namespace.


Perhaps this is a local perl configuration error, but I wanted to post as a possible bug report as the old way of checking for current Neovim::Ext in nvim 0.6.1 behaves as intended.

### Steps to reproduce

1. Install nvim from latest repo
2. run :checkhealth from within nvim
3. see that incorrect newest version of Neovim::Ext is 5 instead of 0.06

### Expected behavior

Expected behavior would be for current dev version to report that Neovim::Ext 0.06 is installed and is up to date

### Neovim version (nvim -v)

v0.10.0-dev

### Vim (not Nvim) behaves the same?

unknown

### Operating system/version

Linux Mint 21.1

### Terminal name/version

xterm-256color

### $TERM environment variable

screen.xterm-256color

### Installation

built from repo
Repository: PowerToys
Issue: Closing a snapped program
Labels: Idea-Enhancement,Product-FancyZones,Needs-Triage

### Description of the new feature / enhancement

A habit I've had for a long while is being able to smash my mouse to the top right corner to close a program, but since the windows that are snapped are not actually full screen, it doesn't work.

### Scenario when this would be used?

Aggressive productivity scenarios where windows are getting opened and closed quickly and often.

### Supporting information

_No response_
Repository: pytorch
Issue: Surface NCCL and CUDA version incompatibility
Labels: oncall: distributed,better-engineering

When there is an incompatibly of the NCCL version with the CUDA version installed on the system, the user sees an error: 

```
torch.distributed.DistBackendError: NCCL error in: fbcode/caffe2/torch/csrc/distributed/c10d/ProcessGroupNCCL.cpp:1190, invalid usage, NCCL version 2.10.3            
ncclInvalidUsage: This usually reflects invalid usage of NCCL library.
```

Ideally we can surface this as a check earlier or provide a better error message.

cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @kwen2501 @awgu @penguinwu