sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: move_and_slide() crashing the game when CharacterBody3D collides with MeshInstance3D
Labels: bug,topic:physics,needs testing,crash,topic:3d

### Godot version

4.0beta3

### System information

Windows 11 (22H2)

### Issue description

While creating a normal project, I added a MeshInstance3D and a static body to it with the new "automatic" system with the mesh button, after that i added a CharacterBody3D with the template script for basic first person movement.
When i started the project after that, i noticed that everything froze up, tried again and after some trial and error i finally found out that move_and_slide() crashes everything when CharacterBody3D and MeshInstance3D collide.
I also tried to turn off move_and_slide() and to just collide them in the editor, didn't crash.
Also tried to move the CharacterBody3D really high, and the game didn't crash until it hit the MeshInstance3D. 

Note: after testing even more, i found out that this bug only occurs when using a converted project from a previous version.

### Steps to reproduce

- Create a 3D project
- Create a MeshInstance3D and add a Trimesh Static Body from the mesh button,
- Create a CharacterBody3D and add a MeshInstance3D, then from the mesh button, create a Simplified Convex Collision Sibling
- Place the CharacterBody3D so that when it falls it collides with the MeshInstance3D
- Add the movement template script to the CharacterBody3D
- Run the scene

### Minimal reproduction project

[Unnamed.zip](https://github.com/godotengine/godot/files/9862606/Unnamed.zip)

_No response_
Repository: go
Issue: os/exec: test timeout in TestCredentialNoSetGroups with goroutines blocked on syscall.ForkLock on aix-ppc64
Labels: NeedsInvestigation,OS-AIX

```
#!watchflakes
post <- builder == "aix-ppc64" && pkg == "os/exec" && `^os/user\.lookupUnixUid`
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/611fd6464d9c020795b5d99c655ccc67b71543e0)):

    SIGQUIT: quit
    PC=0x9000000005b8290 m=2 sigcode=0
    
    r0   0xffffffffffffffff	r1   0x1102ea0f0
    r2   0xffffffffffffffff	r3   0xffffffffffffffff
    r4   0xffffffffffffffff	r5   0xffffffffffffffff
    r6   0xffffffffffffffff	r7   0xffffffffffffffff
    r8   0xffffffffffffffff	r9   0xffffffffffffffff
    r10  0xffffffffffffffff	r11  0xffffffffffffffff
    r12  0xffffffffffffffff	r13  0x1102f2800
    ...
    	/ramdisk8GB/workdir-host-aix-ppc64-osuosl/go/src/os/user/lookup.go:15 +0x24 fp=0xa0001000005ada8 sp=0xa0001000005ad88 pc=0x100145cf4
    sync.(*Once).doSlow(0x11020b9d0?, 0xa0001000005ae50?)
    	/ramdisk8GB/workdir-host-aix-ppc64-osuosl/go/src/sync/once.go:74 +0x124 fp=0xa0001000005ae10 sp=0xa0001000005ada8 pc=0x10007c064
    sync.(*Once).Do(...)
    	/ramdisk8GB/workdir-host-aix-ppc64-osuosl/go/src/sync/once.go:65
    os/user.Current()
    	/ramdisk8GB/workdir-host-aix-ppc64-osuosl/go/src/os/user/lookup.go:15 +0x50 fp=0xa0001000005ae68 sp=0xa0001000005ae10 pc=0x100144e00
    os/exec_test.TestCredentialNoSetGroups(0xa0001000022a340)
    	/ramdisk8GB/workdir-host-aix-ppc64-osuosl/go/src/os/exec/exec_posix_test.go:45 +0x38 fp=0xa0001000005af30 sp=0xa0001000005ae68 pc=0x1002b2c18
    testing.tRunner(0xa0001000022a340, 0x110085dd8)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: runtime: TestNeedmDeadlock failures
Labels: NeedsInvestigation,compiler/runtime

```
#!watchflakes
post <- pkg == "runtime" && test == "TestNeedmDeadlock"
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/9d1b4e08565f8aaadb972953c6096daff3cc10e8)):

    --- FAIL: TestNeedmDeadlock (5.11s)
        testenv.go:459: [/data/golang/workdir/tmp/go-build4218498514/testprogcgo.exe NeedmDeadlock] exit status: exit status 1
        crash_cgo_test.go:714: want OK
            , got Hung for 5 seconds


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: storybook
Issue: Turbopack Builder
Labels: feature request,nextjs

### Is your feature request related to a problem? Please describe

Large Storybook projects using webpack can be slow to build and load

### Describe the solution you'd like

Create a new [builder](https://storybook.js.org/blog/first-class-vite-support-in-storybook/) based on [Turbopack](https://vercel.com/blog/turbopack)

### Describe alternatives you've considered

The [Vite builder](https://storybook.js.org/blog/first-class-vite-support-in-storybook/) makes sense if your app is on Vite, but for apps on NextJS, the Turbopack builder would be super useful.

### Are you able to assist to bring the feature to reality?

no

### Additional context

_No response_
Repository: PowerToys
Issue: Move mouse automatically to focused windows when using multiple screens
Labels: Idea-Enhancement,Needs-Triage

### Description of the new feature / enhancement

Hi, I use multiple screens daily and would like to get a way to move automatically to the windows opened recently, it is in the task bar minimized and when you clicked to focused on it you need to move the mouse to the screen where is the window recentrly focused, this feature would improve efficiency with multiple monitors. 

### Scenario when this would be used?

Every time you clicked in a minimized app, and every time you open a new one and are using multiple monitors, It would be less mouse movements. 

### Supporting information

_No response_
Repository: rust
Issue: Use a faster linker by default in the compiler profile
Labels: A-linkage,T-bootstrap

By default for the compiler profile, we use the default system linker to compile the compiler. While this is the easiest solution that will work in the most cases, it's usually rather slow.

There is a `rust.use-lld` option in `config.toml` which can significantly speed up incremental builds and should be on by default.

This will work fine on Linux and should also work fine on Windows, but LLD on MacOS isn't well maintained and has issues so it should not be used by default. A better option here would be [zld](https://github.com/michaeleisel/zld) (there are two zlds out there, this is the right one). On Linux (and on MacOS once it's released), we may also be able to use `mold`, which is even faster and could make another difference.
Repository: kubernetes
Issue: Supporting feature gates on CRDs for configuring usage & validation of fields
Labels: sig/api-machinery,kind/feature,triage/accepted

When introducing a new alpha or beta-level field to a CRD, validation needs to be used to ensure that the field cannot be set unless the administrator has explicitly 'enabled' a new feature, in a similar manner to upstream Kubernetes resources.

To do this today, we must either:

* create a validating webhook and add some form of feature gating configuration there
* not include the field altogether, i.e. have a variant of the CRD (or some kind of overlay) that gets added on top
* have users manually deal with it/do nothing

After chatting with @jpbetz, the idea of supporting feature gates on a CRD would allow for CRD authors to make it easier to give administrators toggles/tools to enable & disable different features, without CRD authors needing to produce a different variants of CRDs for different combinations of features being enabled.

Some form of top level `featureGates` fields could then be exposed via CEL (or similar) to allow for conditional validation based on configuration.

Users could then enable and disable feature gates using simple overlays/changes to configuration, perhaps applied using SSA.

cc @jpbetz @sttts
Repository: vscode
Issue: Server process leaks after closing VS Code with Remote Tunnel Access On
Labels: bug,remote,remote-tunnel

Testing #164392

* on machine1, Turn Remote Tunnel Access On on Linux
* on machine2, connect from another VS Code desktop to machine1
* quit VS Code on machine1
* do `ps aux | grep server-insiders` and observe that the vscode server process is still running
Repository: stable-diffusion-webui
Issue: [Bug]: IOT instruction (core dumped)
Labels: bug-report

### Is there an existing issue for this?

- [x] I have searched the existing issues and checked the recent builds/commits

### What happened?

When trying to launch the Web UI, the program crashes and dumps core.

### Steps to reproduce the problem

1. Run `TORCH_COMMAND='pip install torch torchvision --extra-index-url https://download.pytorch.org/whl/rocm5.1.1' python launch.py --precision full --no-half` with disabled CUDA check


### What should have happened?

The program should have launched normally

### Commit where the problem happens

3e15f8e0f5cc87507f77546d92435670644dbd18

### What platforms do you use to access UI ?

Linux

### What browsers do you use to access the UI ?

Mozilla Firefox

### Command Line Arguments

```Shell
--skip-torch-cuda-test
--precision full
--no-half
```


### Additional information, context and logs

Using AMD GPU and followed the install instructions as given [https://github.com/AUTOMATIC1111/stable-diffusion-webui/wiki/Install-and-Run-on-AMD-GPUs](here).
Repository: go
Issue: proposal: x/exp/mmap: implement io.WriterTo and io.ReadSeeker
Labels: Proposal

A naive implementation of `io.WriterTo` in `mmap.ReaderAt` seems to bring the following performance improvement when using code that relies on `io.Copy` (e.g. `http.ServeContent`).


```
name        old time/op    new time/op    delta
MmapCopy-8     126µs ± 7%     106µs ±16%  -16.09%  (p=0.000 n=8+10)

name        old speed      new speed      delta
MmapCopy-8  16.9GB/s ± 6%  20.4GB/s ±15%  +20.30%  (p=0.000 n=8+10)

name        old alloc/op   new alloc/op   delta
MmapCopy-8    33.7kB ± 0%     0.2kB ±14%  -99.40%  (p=0.000 n=9+10)

name        old allocs/op  new allocs/op  delta
MmapCopy-8      2.00 ± 0%      1.00 ± 0%  -50.00%  (p=0.000 n=10+10)
```

<details>
<summary>Benchmark code</summary>

```go
func BenchmarkMmapCopy(b *testing.B) {
	// mmap some big-ish file; will only work on unix-like OSs.
	f, err := Open("/proc/self/exe")
	if err != nil {
		b.Fatalf("Open: %v", err)
	}

	type sectionReaderWithWriterTo struct {
		*io.SectionReader
		*ReaderAt
	}
	reader := &sectionReaderWithWriterTo{
		SectionReader: io.NewSectionReader(f, 0, int64(f.Len())),
		ReaderAt:      f,
	}

	// Sanity check: ensure we will run into the io.Copy optimization when using the NEW code above.
	var _ io.WriterTo = (*sectionReaderWithWriterTo)(nil)

	buf := &bytes.Buffer{}
	// "Hide" the ReaderFrom interface by wrapping the writer.
	// Otherwise we skew the results by optimizing the wrong side.
	writer := struct{ io.Writer }{buf}

	b.ReportAllocs()
	b.ResetTimer()

	for i := 0; i < b.N; i++ {
		_, _ = reader.Seek(0, io.SeekStart)
		buf.Reset()

		n, _ := io.Copy(writer, reader)
		b.SetBytes(n)
	}
}
```
</details>

This proposal would probably also solve #20642, as [suggested](https://github.com/golang/go/issues/20642#issuecomment-492519200).

**Update 2022-10-27**: since repeated uses of `WriteTo()` should behave like other readers (i.e.: keep state to avoid re-writing the whole `mmap.ReaderAt`), this proposal also implies an implementation of `io.ReadSeeker`.
Repository: react
Issue: [DevTools Bug]: Not seeing source / file path
Labels: Type: Bug,Status: Unconfirmed,Component: Developer Tools

### Website or app

[Any](https://reactjs.org/)

### Repro steps

Open react dev tools in browser
Select a react component from the tree
Notice that no Source (file path) is printed in the bottom right panel (see description screenshot in https://github.com/facebook/react/pull/17567)



### How often does this bug happen?

Every time

### DevTools package (automated)

_No response_

### DevTools version (automated)

_No response_

### Error message (automated)

_No response_

### Error call stack (automated)

_No response_

### Error component stack (automated)

_No response_

### GitHub query string (automated)

_No response_
Repository: go
Issue: x/build/cmd/gomote: gomote create, run, etc timeout after 2 hours
Labels: Builders,NeedsFix

After two hours, gomote create and run (and presumably other commands) timeout with an error like:

```
Error running create: failed to create buildlet: stream terminated by RST_STREAM with error code: INTERNAL_ERROR
```

This is rather annoying, particularly for gomote run. gomote create can be manually retried, but gomote run doesn't have a good workaround [1].

We believe this is because the load balancer has a [2 hour timeout](https://github.com/golang/build/blob/master/deploy/build-ingress.yaml#L150), after which the gRPC connection is closed.

As a short term mitigation, I propose increasing this timeout, perhaps to 24 hours.

However the [GCP docs](https://cloud.google.com/load-balancing/docs/https#timeouts_and_retries) note that connections with long timeout are at risk of disconnecting due to maintainence restarts of the load balancer. Longer term, it would probably be better to make the operations retry-able. e.g., perhaps GomoteServer.ExecuteCommand immediately returns an execution ID, and a new GomoteServer.StreamOutput could be used to stream output from that execution? If that is closed, the client can simply reconnect and continue streaming. Alternatively, maybe `gomote ssh` should be more featureful and could replace `gomote run`, since it also seems to avoid timeout issues.

[1] At the moment I have a terrible hack to scrap the ssh command out of `gomote ssh`, and then fake a PTY to feed commands into it.

cc @cagedmantis @golang/release
Repository: godot
Issue: DAE Importing Broken in Godot 4
Labels: bug,needs testing,topic:import,topic:3d

### Godot version

v4.0.beta3.mono.official [01ae26d31]

### System information

Windows 11, Vulkan renderer

### Issue description

I have a project which is mostly made of dozens of DAE characters. I started it on Godot 3.4, and intended to one day make something of it. I thought that by starting it on 3.4 I was mostly future-proofing it, but Godot 4 broke everything: the models are all distorted and the bones are twisted in bizarre ways. The models were exported from 3ds max 2021 using the OpenCollada plugin. Is there a chance this will solve itself or should I get started re-exporting everything as glbs? It's really important to support more than one format, in my opinion. I've attached a Darth Vader dae with suffers from this issue. Thanks in advance.
[Vader.zip](https://github.com/godotengine/godot/files/9863578/Vader.zip)

### Steps to reproduce

Import this file.

### Minimal reproduction project

_No response_
Repository: next.js
Issue: <title> tag renders a html comment causing a webpack warning
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

$ npx next info

    Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.1.0: Sun Oct  9 20:14:30 PDT 2022; root:xnu-8792.41.9~2/RELEASE_ARM64_T8103
    Binaries:
      Node: 16.13.0
      npm: 8.1.4
      Yarn: 1.22.17
      pnpm: 6.30.0
    Relevant packages:
      next: 13.0.0
      eslint-config-next: 13.0.0
      react: 18.2.0
      react-dom: 18.2.0

    warn  - Latest canary version not detected, detected: "13.0.0", newest: "12.3.2-canary.43".
        Please try the latest canary version (`npm install next@canary`) to confirm the issue 
    still exists before creating a new issue.
        Read more - https://nextjs.org/docs/messages/opening-an-issue

### What browser are you using? (if relevant)

Chome

### How are you deploying your application? (if relevant)

_No response_

### Describe the Bug

I have a page title set like this

    <title>{post.title} | Website Name</title>

But with Next 13 it renders like so:

    <title>Some title<!-- --> | Website Name</title>

And prints the following warning in the terminal:

```
Warning: A title element received an array with more than 1 element as children. In browsers title Elements can only have Text Nodes as children. If the children being rendered output more than a single text node in aggregate the browser will display markup and comments as text in the title and hydration will likely fail and fall back to client rendering
    at title
    at head
    at Head (webpack-internal:///./node_modules/next/dist/pages/_document.js:279:1)
    at html
    at Html (webpack-internal:///./node_modules/next/dist/pages/_document.js:678:104)
    at MyDocument (webpack-internal:///./src/pages/_document.tsx?__sentry_wrapped__:21:1)
```

### Expected Behavior

It renders without the comment:

    <title>Some title | Website Name</title>

And no warning.

### Link to reproduction

https://github.com/koenpunt/nextjs13-title-issue

### To Reproduce

Run the reproduction application and you'll see the warning when opening http://localhost:3000/example
Repository: vscode
Issue: git.branchPrefix and git.branchProtectionPrompt are unknown settings on vscode.dev
Labels: git,under-discussion

Testing #164518

Following the steps from #164518, in vscode.dev the `git.branchPrefix` and `git.branchProtectionPrompt` settings both seem to be unknown:

![Screen Shot 2022-10-25 at 1 58 55 PM](https://user-images.githubusercontent.com/12821956/197880869-68050819-2292-4ee0-9dd8-5240e0561d8d.png)

They don't show up in the settings ui and are faded out in the settings json
Repository: rust
Issue: Add links to doc items to the Unstable Book
Labels: E-mentor,E-medium,A-docs

Currently the Unstable Book has autogenerated library feature links: https://github.com/rust-lang/rust/blob/4a82c2174a7e986f9a50d9ec806c4c47bd22eed8/src/tools/unstable-book-gen/src/main.rs#L39 but all they do is [link to the tracking issue](https://doc.rust-lang.org/nightly/unstable-book/library-features/arc-unwrap-or-clone.html).

It would be very helpful to have them link to all the individual library items gated behind each feature flag.

cc @jyn514 @alice-i-cecile 

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

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

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: PowerToys
Issue: dynamic zone creation with keyboard/mouse shortcut to evenly split currently selected drop zone
Labels: Idea-Enhancement,Needs-Triage

### Description of the new feature / enhancement

While selecting a zone to drop a window into you can press `ctrl` to select multiple zones. 

I think it would be dandy if we could split the current zone into two, evenly, and then select one. And, if you want, you could split it further.

For example: say you have your monitor setup with 3 column zones:

1. Start moving window
2. Press `shift` to show zones you can drop into
3. You hover over the middle column zone
4. Press `alt` to split the zone horizontally or `caps` to split it vertically in half
5. Move window to newly created dynamic zone and let go of the mouse or go back to step 4

### Scenario when this would be used?

When you want to or need to create and use dynamically created zones.

### Supporting information

_No response_
Repository: pytorch
Issue: FakeTensorMode doesn't support two Scalar inputs, if we use prims' impl as the meta function 
Labels: triaged,module: primTorch,module: fakeTensor

### 🐛 Describe the bug

uncomment following line in _meta_registration.py

```
            # "aten::add.Tensor",  # ValueError: Receive two Number inputs to an elementwise binary operation! inductor/test_torchinductor.py -k test_both_scalars  # noqa: B950
            # "aten::sub.Tensor",  # ValueError: Receive two Number inputs to an elementwise binary operation! inductor/test_torchinductor.py -k test_both_scalars  # noqa: B950
            # "aten::mul.Tensor",  # ValueError: Receive two Number inputs to an elementwise binary operation! inductor/test_torchinductor.py -k test_both_scalars  # noqa: B950
            # "aten::div.Tensor",  # ValueError: Receive two Number inputs to an elementwise binary operation! test_fake_tensor.py -k test_scalar_inputs  # noqa: B950
            # "aten::div.Tensor_mode",  # ValueError: Receive two Number inputs to an elementwise binary operation! inductor/test_torchinductor.py -k test_div8_cpu  # noqa: B950

```

And this will use prims.add as the meta function. 

Further commenting out following line in _refs/__init__.py for `def add` fucntion
```
    # if isinstance(a, Number) and isinstance(b, Number):
    #     raise ValueError(
    #         "Receive two Number inputs to an elementwise binary operation!"
    #     )

```

Repo:

```
with FakeTensorMode():
    out = torch.add(3, 4)
    print(out)
```

Got 
```
Traceback (most recent call last):
  File "/scratch/bahuang/work/repos/pytorch/temp/t.py", line 28, in <module>
    out = torch.add(3, 4)
  File "/scratch/bahuang/work/repos/pytorch/torch/_subclasses/fake_tensor.py", line 831, in __torch_dispatch__
    return self.wrap_meta_outputs_with_default_device_logic(
  File "/scratch/bahuang/work/repos/pytorch/torch/_subclasses/fake_tensor.py", line 866, in wrap_meta_outputs_with_default_device_logic
    return tree_map(partial(wrap), r)
  File "/scratch/bahuang/work/repos/pytorch/torch/utils/_pytree.py", line 195, in tree_map
    return tree_unflatten([fn(i) for i in flat_args], spec)
  File "/scratch/bahuang/work/repos/pytorch/torch/utils/_pytree.py", line 195, in <listcomp>
    return tree_unflatten([fn(i) for i in flat_args], spec)
  File "/scratch/bahuang/work/repos/pytorch/torch/_subclasses/fake_tensor.py", line 879, in wrap
    return converter(self, e, device or common_device)
  File "/scratch/bahuang/work/repos/pytorch/torch/_subclasses/fake_tensor.py", line 268, in __call__
    assert t.device.type == "meta", f"device must be meta, got {t.device.type} instead"
AssertionError: device must be meta, got cpu instead
```

PyTorch eager supports this, and there is a test case in `inductor/test_torchinductor.py -k test_both_scalars` for this.  



### Versions

master


cc @ezyang @mruberry @ngimel @Lezcano @fdrocha @eellison, @ngimel, @ezyang
Repository: flutter
Issue: Print VM service URI after hot reload or hot restart, to enable attachment of an IDE debugger.
Labels: c: new feature,tool,c: proposal,P3,team-tool,triaged-tool

It would really help me when I want to attach to a process to debug an issue.

Often the URI that was printed in the beginning of the execution is hidden by a lot of output, so I have to restart the app and re-click the path to the place where I want to debug it.