sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Physics bodies can collide with tile seams
Labels: bug,topic:physics,topic:2d

### Tested versions

4.3 dev4 and earlier

### System information

Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1060 (NVIDIA; 31.0.15.4633) - Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 Threads)

### Issue description

There is an issue with TileMap where a body can sometimes detect a wall collision on a completely flat surface. This causes bugs like projectile bouncing backwards instead of being reflected or characters turning at random point as if they hit something. Unfortunately the bug is very random - it depends on body shape, position and movement velocity. Sometimes I can reproduce it reliably in one very specific spot, but some time later it can fix itself and happen elsewhere.

Since it's so random, I didn't report it until now, because I though the issue is fixed multiple times. Apparently it's not and I just have another of these "reliable" cases.

Bug in action. Notice how the orange enemy turns for no reason, while the other enemy (which has a different shape) walks normally:

https://github.com/godotengine/godot/assets/2223172/edea97f4-b459-41f1-a118-baf0804ce943

Here I replaced the TileMap with a flat StaticBody2D and moved the TileMap below:

https://github.com/godotengine/godot/assets/2223172/a82c8e8a-7149-416a-a76b-d264132fe569

I suspect that it's caused by the fact that the TileMap is composed of multiple collision shapes and due to some physics glitches it's possible to hit corner of a tile. Related to #84163 and I assume solution would be merging the tiles into polygons (AFAIK navigation already does that).

### Steps to reproduce

1. Use TileMap
2. It might happen

### Minimal reproduction project (MRP)

The bug is too random to create a reliable MRP.
Repository: pytorch
Issue: DISABLED test_torch_to (__main__.TestTEFuserDynamic)
Labels: triaged,module: flaky-tests,skipped,NNC,oncall: pt2,module: dynamo

Platforms: dynamo

This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_torch_to&suite=TestTEFuserDynamic&limit=100) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/22633226106).

Over the past 3 hours, it has been determined flaky in 14 workflow(s) with 14 failures and 14 successes.

**Debugging instructions (after clicking on the recent samples link):**
DO NOT ASSUME THINGS ARE OKAY IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_torch_to`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.


Test file path: `test_jit_fuser_te.py`

cc @clee2000 @wdvr @EikanWang @jgong5 @chauhang @penguinwu @voznesenskym @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @amjames @ezyang @msaroufim @bdhirsh @anijain2305 @zou3519
Repository: pytorch
Issue: DISABLED test_torch_to (__main__.TestTEFuserStatic)
Labels: triaged,module: flaky-tests,skipped,NNC,oncall: pt2,module: dynamo

Platforms: dynamo

This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_torch_to&suite=TestTEFuserStatic&limit=100) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/22633226106).

Over the past 3 hours, it has been determined flaky in 14 workflow(s) with 14 failures and 14 successes.

**Debugging instructions (after clicking on the recent samples link):**
DO NOT ASSUME THINGS ARE OKAY IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_torch_to`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.


Test file path: `test_jit_fuser_te.py`

cc @clee2000 @wdvr @EikanWang @jgong5 @chauhang @penguinwu @voznesenskym @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @amjames @ezyang @msaroufim @bdhirsh @anijain2305 @zou3519
Repository: flutter
Issue: Add support to macOS text replacements
Labels: a: text input,c: new feature,platform-mac,c: proposal,a: desktop,P3,team-text-input,triaged-text-input

### Use case

MacOS supports configuring system-wide text replacements on the settings:

![CleanShot 2023-08-17 at 13 02 51@2x](https://github.com/superlistapp/super_editor/assets/31278849/bc09f8b3-8468-4924-89cb-4e1809735050)

After typing a configured replacement, the text is highlighted and a popover is displayed, so the user can accept the replacement:

https://github.com/flutter/flutter/assets/7597082/6ab8ffa8-163d-43c1-b5d3-00dfb9bf5dfc

Flutter `TextField` doesn't seem to support that:

https://github.com/flutter/flutter/assets/7597082/2e9a9299-5c22-42eb-83dc-8db4b5e56d0c




### Proposal

Implement support for that feature.
Repository: rust
Issue: Misleading error on tuple struct field with docstring
Labels: A-diagnostics,A-parser,C-bug,D-confusing,S-has-mcve

<!--
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: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=48a7a316c9d4825be960974fd87a8d8d

```rust
struct Foo {
    a: Vec<(
        /// Docstring
        f32,
        f32,
    )>,
}
```

I expected to see this happen: Add docstring to field in tuple struct

Instead, this happened: Misleading second error "constant provided when a type was expected".

```
   Compiling playground v0.0.1 (/playground)
error: expected type, found doc comment `/// Docstring`
 --> src/lib.rs:3:9
  |
3 |         /// Docstring
  |         ^^^^^^^^^^^^^ expected type
  |
help: expressions must be enclosed in braces to be used as const generic arguments
  |
2 ~     a: Vec<{ (
3 |         /// Docstring
4 |         f32,
5 |         f32,
6 ~     ) }>,
  |

error[E0747]: constant provided when a type was expected
 --> src/lib.rs:2:12
  |
2 |       a: Vec<(
  |  ____________^
3 | |         /// Docstring
4 | |         f32,
5 | |         f32,
6 | |     )>,
  | |_____^
```

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.76.0 (07dca489a 2024-02-04)
binary: rustc
commit-hash: 07dca489ac2d933c78d3c5158e3f43beefeb02ce
commit-date: 2024-02-04
host: aarch64-apple-darwin
release: 1.76.0
LLVM version: 17.0.6
```
Repository: flutter
Issue: [Impeller] GLES shader functions are just raw strings.
Labels: P2,e: impeller,team-engine,triaged-engine

This makes it so that pipelines that share shader stages have to recompile the shader over and over. We should ideally only pay the price of a link in such cases.
Repository: rust
Issue: catch_unwind docs are unclear about panic hook
Labels: T-libs-api,A-docs

### Location

std::panic::catch_unwind



### Summary

The docs for [std::panic::catch_unwind](https://doc.rust-lang.org/std/panic/fn.catch_unwind.html) [notes section](https://doc.rust-lang.org/std/panic/fn.catch_unwind.html#notes): 

> # Notes

> Note that this function might not catch all panics in Rust. A panic in Rust is not always implemented via unwinding, but can be implemented by aborting the process as well. This function only catches unwinding panics, not those that abort the process.

> Note that if a custom panic hook has been set, it will be invoked before the panic is caught, before unwinding.

> Also note that unwinding into Rust code with a foreign exception (e.g. an exception thrown from C++ code) is undefined behavior.

The second paragraph says "if a custom panic hook has been set".  This implies a simple program like the following will not print a panic message, but it does:
```
fn main() {
    let _ = std::panic::catch_unwind(|| panic!());
}
// output
thread 'main' panicked at src/main.rs:2:41:
explicit panic
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
```
This is the default hook, there is no need to set a custom one.

The text could be changed to something like "if a panic hook is set", as well as further discussion of the panic hook, which is covered in the `panic!` docs, but none of the docs for `panic!`, `set_hook`, or `take_hook` mention `catch_unwind`. There's no discussion in the parent `panic` module.

In typical usage `catch_unwind` will involve `set_hook` and `take_hook`, so the docs should cover this.
Repository: rust
Issue: Tracking Issue for wasm exception-handling architecture intrinsics
Labels: T-libs-api,C-tracking-issue

Feature gate: `#![feature(wasm_exception_handling_intrinsics)]`

This is a tracking issue for wasm exception-handling architecture intrinsics; currently, only the `throw` instruction is implemented as a platform intrinsic.

### Public API

```rust
// core::arch::wasm32

pub unsafe fn throw<const TAG: i32>(ptr: *mut u8) -> !;
```

### Steps / History

- [x] Implementation: rust-lang/stdarch#1542
- [ ] Final comment period (FCP)[^1]
- [ ] Stabilization PR

### Unresolved Questions

- Needs better support from LLVM before merging. At the moment, LLVM only accepts a tag value of `0`, signifying a C++ exception. Ideally one would be able to somehow declare a tag in a similar way to a `static`, and pass that as the TAG to the intrinsic.

[^1]: https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html
Repository: material-ui
Issue: [material-ui][Text Field] Multiline variant cannot be made to scroll horizontally
Labels: component: text field,package: material-ui,enhancement

### Summary

The `TextareaAutosize` when rendered by a `TextField` with multiline applies `overflow: hidden` to the resulting textarea dom element as an inline style in the [current implementation](https://github.com/mui/material-ui/blob/master/packages/mui-base/src/TextareaAutosize/TextareaAutosize.tsx#L135).

This prevents the usecase I have, which is a textarea form input element that can grow vertically based on the size of the text contents, while also respecting whitespace and scrolling in the horizontal direction.

The fix should be as simple as splitting the `overflow` into `overflow-x` and `overflow-y` and applying these as css instead of inline styles so they can be overwritten.

### Examples

https://github.com/mui/material-ui/blob/master/packages/mui-base/src/TextareaAutosize/TextareaAutosize.tsx#L135 (existing implementation)

```
import { TextField } from '@mui/material';

...
<TextField
  error={!!errors?.someInput}
  label="Some label"
  InputLabelProps={{
    shrink: true
  }}
  multiline
  fullWidth
  minRows={6}
  variant="outlined"
  InputProps={{
    sx: {
      ['textarea']: {
        whiteSpace: 'pre',
        overflowX: 'auto' // requires !important, cannot be accessed or overwritten otherwise
      }
    }
  }}
  helperText={errors?.someInput?.message}
  {...register('someInput')}
/>
...
```

Desired configurable behavior in in mp4 format:
![Desired behavior](https://github.com/mui/material-ui/assets/40526638/0fba0e90-863d-4288-8e37-0b7aae2c6144)


### Motivation

I am trying to make a`Textfield` that renders as a textarea, while allowing me to scroll horizontally while respecting whitespace. Preserving the behavior of: expanding vertically dynamically based on the users input, as many lines as necessary without restriction (the same as the current `TextareaAutosize` implementation).

I know I could assign a max number of rows. But I think there is a valid usecase with the want to expand vertically in an unlimited fashion within a scroll container, while also being able to override the inline overflow style.

**Search keywords**: textfield textarea mui core
Repository: godot
Issue: Missing texture on a single Decal causes clustering artifacts to appear on other decals
Labels: bug,topic:rendering,topic:3d

### Tested versions

4.3dev4

### System information

Godot v4.3.dev4 - Debian GNU/Linux trixie/sid trixie - Wayland - Vulkan (Forward+) - dedicated AMD Radeon RX 5600 XT (RADV NAVI10) () - AMD Ryzen 5 2600X Six-Core Processor (12 Threads)

### Issue description

When a decal has a missing texture, other decals affecting the same mesh (or maybe all other decals? -- I only have one mesh so I haven't tested thoroughly) flicker.  Sometimes they are rendered correctly.  Other times, they are only partly rendered.

I'm using the forward_plus rendered -- this does not seem to be a result of the 7-decal limit for the mobile renderer, and it works fine when I replace the missing texture.

### Steps to reproduce

I noticed this when I forgot to create one of my decal textures, and suddenly the rendering was wrong.
![Screenshot from 2024-03-13 23-15-38](https://github.com/godotengine/godot/assets/77003/c4512ca8-0128-4479-b444-c072befee786)

In the MRP, you can use the mouse to spin the shape.  When you do, you'll notice that the decals flicker.

If you replace temp-26.png (just copy any of the other ones), the flicker goes away entirely.

### Minimal reproduction project (MRP)

[flicker.zip](https://github.com/godotengine/godot/files/14596218/flicker.zip)
Repository: angular
Issue: Automatic migration for RouterTestingModule to provideRouter([]) or RouterModule
Labels: area: router

### Which @angular/* package(s) are relevant/related to the feature request?

router

### Description

If a project upgrades to Angular 17.3.0, RouterTestingModule's deprecation (#54466) will cause a ton of warnings/errors if that project has linter rules against deprecated APIs.  Can Angular provide an official migration for this?

### Proposed solution

Automatically migrate from this:

```ts
imports: [
  ...
  RouterTestingModule.withRoutes([]),
  ...
],
```

to this if the component is not standalone:

```ts
imports: [
  ...
  RouterModule.forRoot([]),
  ...
],
```

or to this if the component is standalone:

```ts
providers: [
  ...
  provideRouter([]),
  ...
],
```

and fix the relevant import statements.

### Alternatives considered

Manually migrate everything.
Repository: material-ui
Issue: [joy-ui][Circular/Linear Progress] soft (default) variant is hard to see in dark mode
Labels: design,package: joy-ui,component: progress

### Steps to reproduce

Link to live example: (required)
https://mui.com/joy-ui/react-circular-progress/
https://mui.com/joy-ui/react-linear-progress/
Please switch to dark mode
Steps:
1. Circular progress or linear progress
2. Soft variant (default setting)
3. dark mode


### Current behavior

The track is nearly invisible, and the moving blue progress is too dark.
![图片](https://github.com/mui/material-ui/assets/61173768/b2e72fa6-b4fc-49cc-bc53-a178b132f62f)
![图片](https://github.com/mui/material-ui/assets/61173768/2e6244ea-f772-4cd6-9964-702c34f8c865)
![图片](https://github.com/mui/material-ui/assets/61173768/11bc1359-d131-45df-b57e-3001f2f9835f)

It becomes even worse if it is shown on a modal:
![图片](https://github.com/mui/material-ui/assets/61173768/bb496219-685f-4028-9dcd-d3130bbaac55)


### Expected behavior

Previously I used 5.0.0-alpha.84 and the color was easier to identify.
![图片](https://github.com/mui/material-ui/assets/61173768/3034ce05-2e4a-42a9-90ea-2ba2c53b78f7)

Not sure if this change is intended.

### Context

_No response_

### Your environment

_No response_

**Search keywords**: joy-ui progress soft dark
Repository: rust
Issue: `error: cycle detected ` on latest rust nightly for windows build.
Labels: A-type-system,T-compiler,C-bug,T-types,S-needs-repro

```
error[: cycle detected when type-checking `x86_64::sse2::<impl at index.crates.io-6f17d22bba15001f\ppv-lite86-0.2.17\src\x86_64\sse2.rs:301:1: 301:80>::rotate_each_word_right20::{constant#0}`
   --> index.crates.io-6f17d22bba15001f\ppv-lite86-0.2.17\src\x86_64\sse2.rs:293:21
    |
293 |                     _mm_srli_si128(self.x, $i as i32),
    |                     ^^^^^^^^^^^^^^
...
307 |     rotr_128!(rotate_each_word_right20, 20);
    |     --------------------------------------- in this macro invocation
    |
note: ...which requires computing type of `x86_64::sse2::<impl at index.crates.io-6f17d22bba15001f\ppv-lite86-0.2.17\src\x86_64\sse2.rs:301:1: 301:80>::rotate_each_word_right20::{constant#0}`...
   --> index.crates.io-6f17d22bba15001f\ppv-lite86-0.2.17\src\x86_64\sse2.rs:293:21
    |
293 |                     _mm_srli_si128(self.x, $i as i32),
    |                     ^^^^^^^^^^^^^^
...
```
The problem occurred only for windows on recent nightly build after 1.78.0-nightly (2024-03-10)
Repository: tensorflow
Issue: tf.transpose lead to program abortion on a normal value while the perm contains -1 
Labels: stat:awaiting tensorflower,type:bug,comp:ops,TF 2.15

### Issue type

Bug

### Have you reproduced the bug with TensorFlow Nightly?

Yes

### Source

source

### TensorFlow version

2.15.0

### Custom code

Yes

### OS platform and distribution

_No response_

### Mobile device

_No response_

### Python version

_No response_

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

Hi, the tf.transpose will lead to a program abortion when receiving an empty input and perm is [-1, -2].
The traceback indicate a check fail:
```
tensorflow/core/framework/tensor_shape.cc:356] Check failed: d >= 0 (0 vs. -1)
```


### Standalone code to reproduce the issue

```shell
import tensorflow as tf

input = tf.constant([[]])
dim0 = -2
dim1 = -1
tf.transpose(input, perm=[dim1, dim0])
```


### Relevant log output

_No response_
Repository: vscode
Issue: VS Code Remote Tunnel don't load PHP files
Labels: bug,remote-tunnel

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.87.2
- OS Version: Win 11 with Arch on WSL

Steps to Reproduce:

1.  Create a Tunnel and lunch a php local server with php -S localhost:8000

![image](https://github.com/microsoft/vscode/assets/44122620/2f482319-98a8-4c6c-9c65-12ab073295ac)

2. Redirect port on host:

![image](https://github.com/microsoft/vscode/assets/44122620/2de3e83e-4e02-4306-9c72-3f1f4bd79e73)

3. Navigate to url on browser:
![image](https://github.com/microsoft/vscode/assets/44122620/e220bb4d-8766-4515-a204-d732a0c2d0b7)
 
4. If change the file to html works fine:

![image](https://github.com/microsoft/vscode/assets/44122620/ffc54c5f-2d68-42de-be57-aab950ddf051)

5. Test file:

![image](https://github.com/microsoft/vscode/assets/44122620/ae6e09ae-a95b-49ac-a479-43fd42f9478e)
Repository: tensorflow
Issue: tf.raw_ops.DatasetToTFRecord: Aborted (core dumped)
Labels: stat:awaiting tensorflower,type:bug,comp:ops,TF 2.15

### Issue type

Bug

### Have you reproduced the bug with TensorFlow Nightly?

Yes

### Source

binary

### TensorFlow version

tf 2.15

### Custom code

Yes

### OS platform and distribution

Ubuntu 20.04

### Mobile device

_No response_

### Python version

3.9

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

Under specific input, `tf.raw_ops.DatasetToTFRecord` encounters "Aborted (core dumped)".

### Standalone code to reproduce the issue

```shell
import tensorflow as tf

input_data = [[1, 2], [3, 4], [5, 6]]

input_data_strings = [[str(d) for d in inner_list] for inner_list in input_data]

dataset = tf.data.Dataset.from_tensor_slices(input_data_strings)

filename = "output.tfrecord"

tf.raw_ops.DatasetToTFRecord(input_dataset=dataset._variant_tensor, filename=filename, compression_type="")
```


### Relevant log output

```shell
2024-03-14 05:41:32.476705: F tensorflow/core/framework/tensor.cc:852] Check failed: 1 == NumElements() (1 vs. 2)Must have a one element tensor
Aborted (core dumped)
```
Repository: tensorflow
Issue: tf.raw_ops.ExperimentalDatasetToTFRecord: Aborted (core dumped)
Labels: stat:awaiting tensorflower,type:bug,comp:ops,TF 2.16

### Issue type

Bug

### Have you reproduced the bug with TensorFlow Nightly?

Yes

### Source

binary

### TensorFlow version

tf 2.15

### Custom code

Yes

### OS platform and distribution

Ubuntu 20.04

### Mobile device

_No response_

### Python version

3.9

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

Under specific input, `tf.raw_ops.ExperimentalDatasetToTFRecord` encounters "Aborted (core dumped)".

### Standalone code to reproduce the issue

```shell
import tensorflow as tf

input_data = tf.data.Dataset.range(10).map(lambda x: tf.strings.as_string(x))
input_data = input_data.batch(2)  

filename = tf.constant("output.tfrecord")
compression_type = tf.constant("GZIP")
tf.raw_ops.ExperimentalDatasetToTFRecord(input_dataset=input_data._variant_tensor, filename=filename, compression_type=compression_type)
```


### Relevant log output

```shell
2024-03-14 05:47:55.415453: F tensorflow/core/framework/tensor.cc:852] Check failed: 1 == NumElements() (1 vs. 2)Must have a one element tensor
Aborted (core dumped)
```