sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: material-ui
Issue: [docs] Demo EnhancedTable crashes
Labels: docs,component: table

<!-- Please make sure you have fullfilled the following items before submitting -->
<!-- Checked checkbox should look like this: [x] -->
- [x] I have [searched for similar issues](https://github.com/mui/material-ui/issues?q=is%3Aissue%20%5Bdocs%5D%20Demo%20EnhancedTable%20crashes) in this repository and believe that this is not a duplicate.

## Steps to Reproduce
1. Visit https://mui.com/material-ui/react-table/
2. Move to [Sorting & selecting](https://mui.com/material-ui/react-table/#sorting-amp-selecting)
3. Translate to Japanese with a built-in function in Microsoft Edge
4. Click the "Select All" checkbox
5. Click the "Deselect All" checkbox
6. demo *EnhancedTable* crashes

## Your Environment
| Tech         | Version |
|--------------|---------|
| MUI  | v5.11.15  |
| Netlify deploy | https://6422e66b59efb500087f6463--material-ui-docs.netlify.app |
| Browser      | Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.0.0 Safari/537.36 Edg/112.0.1722.15 |
Repository: godot
Issue: Script Error: Autoload singletons conflict resource preloading
Labels: bug,topic:gdscript

### Godot version

beta14 up to 4.1 stable (probably happens from earlier too)

### System information

Artix (Arch Linux)

### Issue description

There is a very sneaky error which has halted my project (as I cannot test my multiplayer game with anyone)

The editor works alright, the following issue is not present in the editor (hence sneaky), but once I run any exported build, I get script parsing errors because of some sort of race condition between loading resources and autoload singletons.

Every resource I have, has a .gd attached with the same name, and inside I declare its class_name e.g. Monster1.tres has attached Monster1.gd, and Monster1.gd starts with
```gdscript
extends Resource
class_name Monster1

var power: int
var movement_speed: int
```

When an autoload script references to Monster1, there is a parse error. For example, if an autoload singleton has the following code, it causes a script error in exported builds:
```gdscript
func display_monster() -> Monster1:
```
"Parse Error: Could not parse global class "Monster1" from "res://_path_/Monster1.gd"

### Steps to reproduce

1. Open the MRP
2. Export the project (Server Template, basically default choice with all resources/scenes loaded lol)
3. Open the project (./Server.x86_64)
4. Quit (Super+Q in my case)
5. The errors of the error log uploaded below display. That's a lot of script errors which I cannot fix in any way. They do not appear in the editor (if they do, its on opening so they are ignored), only on exported builds.

### Minimal reproduction project

**MRP**: [MRP.tar.gz](https://github.com/godotengine/godot/files/11130187/MRP.tar.gz)

**Error Log**: [error-log.txt](https://github.com/godotengine/godot/files/11130189/error-log.txt)

**Executable Build (X11 linux)**: 
[ConflictResourceConflictExecutable.tar.gz](https://github.com/godotengine/godot/files/11130191/ConflictResourceConflictExecutable.tar.gz)
Repository: godot
Issue: _get_line_syntax_highlighting(line) in SyntaxHighlighter return result is Order Sensitive
Labels: enhancement,topic:gui

### Godot version

v4.0.1.stable.official [cacf49999]

### System information

Windows 10

### Issue description

I'm building a main screen plugin that uses CodeEdit Node, and a custom (extended) SyntaxHighlighter.

when implementing the virtual function:
_get_line_syntax_highlighting(line: int) of SyntaxHighlighter
the expected return is a Dictionary with key = starting character position, and value = the color to apply starting that position.

Because the result is dictionary, it could be assumed that the resulting highlight is not order sensitive.
However, it is.

For example, if you have the following in the CodeEdit:
```
abc
```

and return:
```
{
 1: {
      "color": Color(1,0,0)
    },
  0: {
     "color": Color(0,1,0)
  }
}
```

entire string "bc" will be colored red, but "a" would be ignored and would remain a default color.

if you update the return value to :
```
{
 0: {
      "color": Color(0,1,0)
    },
  1: {
     "color": Color(1,0,0)
  }
}
```
the string will correctly be highlighted with "a" being green and "bc" being red.


### Steps to reproduce

1. Setup scene with CodeEdit node.
2. Add new SyntaxHighlighter in CodeEdit -> TextEdit -> Syntax Highlighter
3. "Edit" the SyntaxHighlighter and attach a Script  ("sorted_highlighter.gd" in the example) with the following content:
```
extends SyntaxHighlighter

func _get_line_syntax_highlighting(line):
	return {
		0: {
			"color": Color(1,0,0)
		},
		1: {
			"color": Color(0,1,0)
		}
	}
```
4. Run the Project and type in the editor, and see the highlight is as expected wit first character being Red, and the rest of the characters in each line being green.
5. "Edit" the SyntaxHighlighter and attach a Script ("unsorted_highlighter.gd" in the example) with the following content:
```
extends SyntaxHighlighter

func _get_line_syntax_highlighting(line):
	return {
		1: {
			"color": Color(0,1,0)
		},
		0: {
			"color": Color(1,0,0)
		}
	}
```
6. Run the Project and type in the editor. The Highlight is done incorrectly where the first character is uncolored (default color), and the rest is Green.

### Minimal reproduction project

[BugReproduce.zip](https://github.com/godotengine/godot/files/11130874/BugReproduce.zip)
Repository: terminal
Issue: mouse events are sent incorrectly in win32-input-mode
Labels: Product-Conhost,Help Wanted,Product-Conpty,Area-Input,Area-VT,Issue-Bug

### Steps to reproduce

1. Compile this test app using gcc under WSL:

```
#include <termios.h> 
#include <assert.h>
#include <errno.h>
#include <signal.h>
#include <fcntl.h>
#include <sys/ioctl.h>
#include <stdlib.h> 
#include <stdio.h> 
#include <unistd.h> 


int main()
{
    struct termios _ts = {};
	int _ts_r = tcgetattr(1, &_ts);
	if (_ts_r == 0) {
		struct termios ts_ne = _ts;
		//ts_ne.c_lflag &= ~(ECHO | ECHONL);
		cfmakeraw(&ts_ne);
		if (tcsetattr(1, TCSADRAIN, &ts_ne ) != 0) {
			perror("TTYBackend: tcsetattr");
		}
	}

	fprintf(stderr, "\x1b[?1049h");
	fprintf(stderr, "\x1b[?1000h");
	fprintf(stderr, "\x1b[?1001h");
	fprintf(stderr, "\x1b[?1002h");

	fprintf(stderr, "\x1b[?9001h");

	for (;;) {
		char ch = 0;
		if (read(0, &ch, 1) <= 0) break;
		if (ch <= 0x20 || ch == 0x7f) {
			if (ch == 0x1b) fprintf(stderr, " ");
			fprintf(stderr, "\\x%02x", (unsigned int)(unsigned char)ch);
		} else {
			fprintf(stderr, "%c", ch);
		}
		if (ch == 0x0d) break;
    	if (ch == 0x0a) break;
	}
	fprintf(stderr, "\x1b[?1049l");
	fprintf(stderr, "\x1b[?1000l");
	fprintf(stderr, "\x1b[?1001l");
	fprintf(stderr, "\x1b[?1002l");

	fprintf(stderr, "\x1b[?9001l");

	if (tcsetattr(1, TCSADRAIN, &_ts ) != 0) {
		perror("TTYBackend: tcsetattr");
	}
}
```

2. Run it under Windows Terminal

3. Move mouse over the terminal window.


### Expected Behavior

We should see mouse movement escape sequences (`\x1b[M...` format)

### Actual Behavior

We see win32-input-mode escape sequences (`\x1b[A;B;C;D;E;F_` format)

![изображение](https://user-images.githubusercontent.com/1151423/229324322-11b546ed-8f84-40d1-8e13-a1930edef110.png)
Repository: TypeScript
Issue: Class properties cannot be initialized within constructor if the property key comes from a static class property (e.g. [Symbol.iterator])
Labels: Needs Investigation,Rescheduled

# Bug Report

<!--
  Please fill in each section completely. Thank you!
-->

### 🔎 Search Terms

symbol property constructor 2564

### 🕗 Version & Regression Information

- This changed between versions 4.6.4 and 4.7.4

### ⏯ Playground Link

<!--
  A link to a TypeScript Playground "Share" link which shows this behavior

  The TypeScript Workbench can be used for more complex setups, try
  https://www.typescriptlang.org/dev/bug-workbench/

  As a last resort, you can link to a repo, but these will be slower for us to investigate.
-->
[Playground link with relevant code](https://www.typescriptlang.org/play?ts=5.1.0-dev.20230401#code/MYewdgzgLgBNCGYAm8A24CmBlAngWwCMRUYBeGXQ4gCgCIFk1NaBKAbgCgPhV4IIK+IqgDCvfjADeHGLLhR4UAJbAYAJwzwk4VDnmKVlYWUFVUdBMuCtOAXy5KwUDGoBm8YBhgBJABLwAN2whYgFpORgAbQYUdDBgswBdAC4YMABXQhdOCMijYjE+CAA6S0MQ1BS0zIJsjntucQF-IIAFNRAABxcoHG8wJWU0JQAvDCR81AElPE7UDDwMJwE-QIThMJk5aIVGOPXiRJMARhztycL+UoUrSaPyACY7Lh4imBaMAHkgtTUlJCQS0mAgwAA9nMhmmt2l0en0BkNUKNxsCpFtZKBIFA1OlgFAQGpqCw0REIhB0t1Cex0aSoAALJQQHaIWKYO4mADMZ1JMHpjLyFUuJTKwHZ5AALNyYPYGq8JB8ROBoDi8QT+oMlMMxhMKtNZvNFssfB9UeFtjEmPE7qkMlk1FKBWYhdcDKKKlVbbV7TTMcrcfiqSSebyGUyLfsxTAuTSInymRcmi7bu6TJKaTKOEA)

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
const standaloneSymbol = Symbol("standalone");

class SymbolClass {
    static readonly staticSymbol = Symbol("static");
}

interface IHaveSymbols {
    [standaloneSymbol]: number;
    [SymbolClass.staticSymbol]: number;
}

class HavePropertyInitializedSymbols implements IHaveSymbols {
    [standaloneSymbol] = 1;
    [SymbolClass.staticSymbol] = 2;
}

class HaveOverriddenSymbols extends HavePropertyInitializedSymbols {
    constructor() {
        super();
        this[standaloneSymbol] = 3;
        this[SymbolClass.staticSymbol] = 4;
    }
}

class HaveConstructorInitializedSymbols implements IHaveSymbols {
    [standaloneSymbol]: number;
    [SymbolClass.staticSymbol]: number;
    constructor() {
        this[standaloneSymbol] = 3;
        this[SymbolClass.staticSymbol] = 4;
    }
}
```

### 🙁 Actual behavior

<!-- What happened, and why it was wrong -->

```
Property '[SymbolClass.staticSymbol]' has no initializer and is not definitely assigned in the constructor.(2564)
(property) SymbolClass.staticSymbol: typeof SymbolClass.staticSymbol
```

It's wrong because the property is definitely assigned in the constructor

### 🙂 Expected behavior

<!-- What you expected to happen instead, and why -->

No error, because the property is definitely assigned in the constructor
Repository: godot
Issue: [3.x, 4.x] GodotPhysics 2D `test_move` doesn't always work with concave static body
Labels: bug,topic:physics

### Godot version

3.5.2.stable, 4.0.1.stable

### System information

Arch on 6.2.8-arch1-1

### Issue description

At 0:08, 0:15

https://user-images.githubusercontent.com/14253836/229333360-87521d92-909a-4ac2-863e-3157df1d937e.mp4


### Steps to reproduce

Run MRP

### Minimal reproduction project

4.0.1 [test1_LATEST.zip](https://github.com/godotengine/godot/files/11131225/test1_LATEST.zip)
3.5.2 [test2_LTS.zip](https://github.com/godotengine/godot/files/11131226/test2_LTS.zip)
Repository: neovim
Issue: API Info: introduce union types
Labels: enhancement

Consider `nvim_create_autocmd`'s first parameter:
```json
{
    "name": "nvim_create_autocmd",
    "since": 9,
    "parameters": [
      [
        "Object",
        "event"
      ],
      [
        "Dictionary",
        "opts"
      ]
    ],
    "return_type": "Integer",
    "method": false
  }
```
The parameter is described as an `Object`. This is because the first argument can be either a `String` or an `ArrayOf(String)`.

Client API generators could generate nicer APIs if the two possible types were explicitly described, e.g. `String|ArrayOf(String)` or `Union(String,ArrayOf(String))`. I don't care much about syntax (especially since I also opened https://github.com/neovim/neovim/issues/22858 ) :).
Repository: rustdesk
Issue: Android/iOS compatibility issues
Labels: bug

# Unresolved
- [ ] https://github.com/rustdesk/rustdesk/issues/3532
- [ ] https://github.com/rustdesk/rustdesk/issues/3611
- [ ] https://github.com/rustdesk/rustdesk/issues/816
- [ ] https://github.com/rustdesk/rustdesk/issues/2941
- [ ] https://github.com/rustdesk/rustdesk/issues/465
- [ ] https://github.com/rustdesk/rustdesk/issues/1038
- [ ] https://github.com/rustdesk/rustdesk/issues/849
- [ ] https://github.com/rustdesk/rustdesk/issues/1729
- [ ] https://github.com/rustdesk/rustdesk/issues/2738
- [ ] https://github.com/rustdesk/rustdesk/issues/3908
- [ ] https://github.com/rustdesk/rustdesk/issues/4023
- [ ] https://github.com/rustdesk/rustdesk/issues/4285
- [ ] https://github.com/rustdesk/rustdesk/issues/4534
- [ ] https://github.com/rustdesk/rustdesk/issues/4690
- [ ] https://github.com/rustdesk/rustdesk/issues/4743
- [ ] https://github.com/rustdesk/rustdesk/issues/4778
- [ ] https://github.com/rustdesk/rustdesk/issues/5044
- [ ] https://github.com/rustdesk/rustdesk/issues/5105
- [ ] https://github.com/rustdesk/rustdesk/issues/5389
- [ ] https://github.com/rustdesk/rustdesk/issues/5421
- [ ] https://github.com/rustdesk/rustdesk/issues/5943
- [ ] https://github.com/rustdesk/rustdesk/issues/5995
- [ ] https://github.com/rustdesk/rustdesk/issues/6004
- [ ] https://github.com/rustdesk/rustdesk/issues/6216
- [ ] https://github.com/rustdesk/rustdesk/issues/6546
- [ ] https://github.com/rustdesk/rustdesk/issues/6809
- [ ] https://github.com/rustdesk/rustdesk/issues/7081
- [ ] https://github.com/rustdesk/rustdesk/issues/7101
- [ ] https://github.com/rustdesk/rustdesk/issues/7291
- [ ] https://github.com/rustdesk/rustdesk/issues/7311
- [ ] https://github.com/rustdesk/rustdesk/issues/7372
- [ ] https://github.com/rustdesk/rustdesk/issues/7379
- [ ] https://github.com/rustdesk/rustdesk/issues/7553
- [ ] https://github.com/rustdesk/rustdesk/issues/7621
- [ ] https://github.com/rustdesk/rustdesk/issues/7615
- [ ] https://github.com/rustdesk/rustdesk/issues/7749
- [ ] https://github.com/rustdesk/rustdesk/issues/7790
- [ ] https://github.com/rustdesk/rustdesk/issues/7816
- [ ] https://github.com/rustdesk/rustdesk/issues/7828
- [ ] https://github.com/rustdesk/rustdesk/issues/8151
- [ ] https://github.com/rustdesk/rustdesk/issues/8359
- [ ] https://github.com/rustdesk/rustdesk/issues/8671
- [ ] https://github.com/rustdesk/rustdesk/issues/8448
- [ ] https://github.com/rustdesk/rustdesk/issues/8818
- [ ] https://github.com/rustdesk/rustdesk/issues/9148
- [ ] https://github.com/rustdesk/rustdesk/issues/9152
- [ ] https://github.com/rustdesk/rustdesk/issues/9892
# Resolved
- [x] https://github.com/rustdesk/rustdesk/issues/8670
- [x] https://github.com/rustdesk/rustdesk/issues/9748
- [x] https://github.com/rustdesk/rustdesk/issues/4118
Repository: pytorch
Issue: forward AD implimentation : _scaled_dot_product_efficient_attention 
Labels: triaged,module: forward ad

### 🚀 The feature, motivation and pitch

Hi there,

I encountered an error message that requests me to file an issue regarding a feature implementation. The error message is as follows:

NotImplementedError: Trying to use forward AD with _scaled_dot_product_efficient_attention that does not support it because it has not been implemented yet.
Please file an issue to PyTorch at https://github.com/pytorch/pytorch/issues/new?template=feature-request.yml so that we can prioritize its implementation.
Note that forward AD support for some operators require PyTorch to be built with TorchScript and for JIT to be enabled. If the environment var PYTORCH_JIT=0 is set or if the 
library is not built with TorchScript, some operators may no longer be used with forward AD.

I would appreciate it if you could prioritize the implementation of this feature. Thank you for your help.

### Alternatives

_No response_

### Additional context

I ran forward AD of Stable-Diffusion with diffusers library, dtype = torch.float32, device=cuda.
Repository: next.js
Issue: @next/font + font-feature-settings do not work with next@13.2.4
Labels: Font (next/font)

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
❯ npx --no-install next info

    Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.3.0: Mon Jan 30 20:38:37 PST 2023; root:xnu-8792.81.3~2/RELEASE_ARM64_T6000
    Binaries:
      Node: 16.0.0
      npm: 7.10.0
      Yarn: 1.22.17
      pnpm: N/A
    Relevant packages:
      next: 13.2.5-canary.26
      eslint-config-next: 13.2.4
      react: 18.2.0
      react-dom: 18.2.0
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

App directory (appDir: true), Font optimization (@next/font)

### Link to the code that reproduces this issue

private repo but is easy to reproduce

### To Reproduce

Setup appDir with RSC and stitchesjs. 

### Describe the Bug

Font features do not appear to be working when used with @next/font.

Given the following
```typescript
export const Inter = InterFont({
	subsets: ['latin'],
	display: 'swap',
});
```

and 

```typescrip
body: {
		fontSize: '$fontSize$14',
		fontFamily: `${Inter.style.fontFamily},  -apple-system,BlinkMacSystemFont,"Segoe UI","Noto Sans",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji"`,
		fontFeatureSettings: 'ss01',
		WebkitFontSmoothing: 'antialiased',
```

I expect `ss01` to work font the Inter font.

### Expected Behavior

Expect `ss01` to be added to fontfeatures. This works when the font is installed natively or locally.

### Which browser are you using? (if relevant)

firefox

### How are you deploying your application? (if relevant)

_No response_
Repository: next.js
Issue: Navigating to rewritten path results in hard navigation when deployed on Vercel (appDir)
Labels: 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: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.3.0: Mon Jan 30 20:38:37 PST 2023; root:xnu-8792.81.3~2/RELEASE_ARM64_T6000
    Binaries:
      Node: 16.13.2
      npm: 9.2.0
      Yarn: 1.22.17
      pnpm: N/A
    Relevant packages:
      next: 13.2.5-canary.26
      eslint-config-next: 13.2.4
      react: 18.2.0
      react-dom: 18.2.0
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

App directory (appDir: true)

### Link to the code that reproduces this issue

https://github.com/yn5/next-app-home-rewrite

### To Reproduce

1. Navigate to https://next-app-home-rewrite.vercel.app/en/about.
2. Click on the link to the home page in the menu.

Please not that the link to home is actually a link to `/en/home` but shown as `/en` with the `as` property of `next/link`. Also `/en` is rewritten to `/en/home` for direct navigation to the URL.

### Describe the Bug

A hard navigation to the homepage occurs, only for the deployment on Vercel. When served locally using `npm run build && npm run start` it works as expected.

### Expected Behavior

The home page is loaded with a soft navigation.

### Which browser are you using? (if relevant)

Chrome 111.0.5563.146 (Official Build) (arm64)

### How are you deploying your application? (if relevant)

Vercel
Repository: pytorch
Issue: The operator 'aten::_weight_norm_interface' is not currently implemented for the MPS device.
Labels: feature,triaged,module: mps

### 🐛 Describe the bug

NotImplementedError: The operator 'aten::_weight_norm_interface' is not currently implemented for the MPS device. If you want this op to be added in priority during the prototype phase of this feature, please comment on https://github.com/pytorch/pytorch/issues/77764. As a temporary fix, you can set the environment variable `PYTORCH_ENABLE_MPS_FALLBACK=1` to use the CPU as a fallback for this op. WARNING: this will be slower than running natively on MPS.


### Versions

NotImplementedError: The operator 'aten::_weight_norm_interface' is not currently implemented for the MPS device. If you want this op to be added in priority during the prototype phase of this feature, please comment on https://github.com/pytorch/pytorch/issues/77764. As a temporary fix, you can set the environment variable `PYTORCH_ENABLE_MPS_FALLBACK=1` to use the CPU as a fallback for this op. WARNING: this will be slower than running natively on MPS.


cc @kulinseth @albanD @malfet @DenisVieriu97 @razarmehr @abhudev
Repository: stable-diffusion-webui
Issue: [Bug]: Img2Img batch directory If some text file in directory - SD identify it as image :)
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?

Traceback (most recent call last):
  File "G:\stable-diffusion\modules\call_queue.py", line 56, in f
    res = list(func(*args, **kwargs))
  File "G:\stable-diffusion\modules\call_queue.py", line 37, in f
    res = func(*args, **kwargs)
  File "G:\stable-diffusion\modules\img2img.py", line 166, in img2img
    process_batch(p, img2img_batch_input_dir, img2img_batch_output_dir, img2img_batch_inpaint_mask_dir, args)
  File "G:\stable-diffusion\modules\img2img.py", line 49, in process_batch
    img = Image.open(image)
  File "G:\stable-diffusion\venv\lib\site-packages\PIL\Image.py", line 3283, in open
    raise UnidentifiedImageError(msg)
PIL.UnidentifiedImageError: cannot identify image file 'Z:\\images\\9aba26abdf\\20230402151740\\163048286.txt'

### Steps to reproduce the problem

1. IMI2IMG
2. Batch Directory



### What should have happened?

Ignor none img extantions.

### Commit where the problem happens

1

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

_No response_

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

_No response_

### Command Line Arguments

```Shell
1
```


### List of extensions

1

### Console logs

```Shell
Traceback (most recent call last):
  File "G:\stable-diffusion\modules\call_queue.py", line 56, in f
    res = list(func(*args, **kwargs))
  File "G:\stable-diffusion\modules\call_queue.py", line 37, in f
    res = func(*args, **kwargs)
  File "G:\stable-diffusion\modules\img2img.py", line 166, in img2img
    process_batch(p, img2img_batch_input_dir, img2img_batch_output_dir, img2img_batch_inpaint_mask_dir, args)
  File "G:\stable-diffusion\modules\img2img.py", line 49, in process_batch
    img = Image.open(image)
  File "G:\stable-diffusion\venv\lib\site-packages\PIL\Image.py", line 3283, in open
    raise UnidentifiedImageError(msg)
PIL.UnidentifiedImageError: cannot identify image file 'Z:\\images\\9aba26abdf\\20230402151740\\163048286.txt'
```


### Additional information

_No response_
Repository: godot
Issue: PointLight2D acting as fully occluded at Compatibility rendering mode on android
Labels: bug,platform:android,topic:rendering,topic:2d

### Godot version

4.0

### System information

Honor 10, android 10,mali-G72

### Issue description

The scene has pointLight2d with the shadow enabled (in the example it is green) and lightoccluder2d, entering the range of pointlight2d. In any mode on the PC and in Forward plus and mobile modes on the smartphone, everything works as it should.
![Screenshot_20230402_153828_org godotengine as](https://user-images.githubusercontent.com/93824521/229355558-8800bfed-77d5-4ecb-8fde-36a70c93b6fd.jpg)

 But in compatibility mode on android, the shadow completely covers the light, no matter what I do.
![Screenshot_20230402_153613_org godotengine as](https://user-images.githubusercontent.com/93824521/229355986-812a3249-cc82-4ebd-9206-8e864f0b5c4a.jpg)



### Steps to reproduce

Create node2d, add pointlight2d and lightoccluder2d to it so that pointlight2d can cast a shadow, enable the shadow, try it on different render modes on android.

### Minimal reproduction project

[asd.zip](https://github.com/godotengine/godot/files/11132301/asd.zip)