sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: storybook
Issue: [Feature Request]: Ability to use dynamic styleUrls
Labels: feature request,needs triage

### Is your feature request related to a problem? Please describe

For our Angular application we are using a dynamically set stylesheet URL based on an environment variable in our components. This gives us the ability to have multiple stylesheets with completely different styling in one codebase. This does not work for storybook. As soon as I try to do any operation storybook does not seem to find the stylesheet anymore. For instance, this works:
`@Component({
  selector: 'app-button',
  templateUrl: './button.component.html',
  styleUrls: ['./button.component.scss']
})`
But this does not:
`@Component({
  selector: 'app-button',
  templateUrl: './button.component.html',
  styleUrls: ['./button.component.' + environment.scssExtension]
})`
This does not work either:
`@Component({
  selector: 'app-button',
  templateUrl: './button.component.html',
  styleUrls: ['./button.component.'+'scss']
})`

It seems that any operation does not work when running storybook.

### Describe the solution you'd like

I would like Storybook to work with dynamically set stylesheet URL's. This would mean we can use environment variables in our stylesheet URL's. When running storybook, we can set different environment variables to change the styling storybook uses.

### Describe alternatives you've considered

_No response_

### Are you able to assist to bring the feature to reality?

no

### Additional context

_No response_
Repository: go
Issue: cmd/gofmt: -r strips some comments when pattern matching
Labels: NeedsInvestigation

<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
rski@rski ~/C/g/go (master)> go version                                                                  
go version go1.19.4 linux/amd64
</pre>

### Does this issue reproduce with the latest release?
yup, tried gofmt built from 9955a7e9bb40d28502fbb8fd6ef1f2f10e18a519

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/rski/.cache/go-build"
GOENV="/home/rski/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/rski/Code/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/rski/Code/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/nix/store/a7875alzpnr46z6mv4ssymfdwmvr6xbq-go-1.19.4/share/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/nix/store/a7875alzpnr46z6mv4ssymfdwmvr6xbq-go-1.19.4/share/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.19.4"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build158369519=/tmp/go-build -gno-record-gcc-switches"
</pre></details>

### What did you do?
input file:
```
package main

import "errors"

func errorWithOneArg1(a func() error, v int) error { return a() }
func errorWithOneArg2(a func() error) error        { return a() }

func layer(f func() error, s string) error { return f() }

func anotherLayer() error {
	return layer(
		func() error {
			return errorWithOneArg1(func() error {
				// This comment is erased
				return errors.New("abc")
			}, 30)
		}, "test")
}
```
command and result:
```
gofmt -r 'errorWithOneArg1(a,b) -> errorWithOneArg2(a)' test.go                      
package main

import (
	"errors"
)

func errorWithOneArg1(a func() error, v int) error { return a() }
func errorWithOneArg2(a func() error) error        { return a() }

func layer(f func() error, s string) error { return f() }

func anotherLayer() error {
	return layer(
		func() error {
			return errorWithOneArg2(func() error {

				return errors.New("abc")
			})

		}, "test")
}
```
Note how the comment was replaced with a blank line. 

This doesn't happen when not doing matching i.e.
```
gofmt -r 'errorWithOneArg1 -> errorWithOneArg2' test.go  | grep -En "return errorWith|com
ment"
15:			return errorWithOneArg2(func() error {
16:				// This comment is erased
```
the code is rewritten and the comment is kept
Repository: flutter
Issue: Add validation to check that an extension is in the same AppGroup as the Flutter iOS app
Labels: c: new feature,platform-ios,tool,c: proposal,P3,team-ios,triaged-ios

## Use case

Flutter apps can pass data to app extensions (such as a home screen widget) using [App Groups](https://developer.apple.com/documentation/xcode/configuring-app-groups).

However, this is only required if the parent Flutter app needs to share information with the extension.

## Proposal

To ensure that the parent app can successfully pass information to the extension, App Groups need to be configured on for both the app target and the extension target, and the App Group identifier must be the same string. There are several steps in this process, and it's pretty easy to miss something / not understand why your app can't find the data. 

We might consider adding validation into the Flutter tooling that gives developers a warning when they have an extension target in the same Xcode project as the Flutter app, if they both aren't configured to the same App Group. 

This is likely a lower priority, as we should first document the steps for using an App Extension with Flutter. But adding it here for tracking purposes.
Repository: flutter
Issue: Support for Android RISC-V
Labels: c: new feature,platform-android,engine,c: proposal,P3,team-android,triaged-android

## Use case

Google recently announced the [android risc-v porting](https://youtu.be/70O_RmTWP58) (article [here](https://arstechnica.com/gadgets/2023/01/google-announces-official-android-support-for-risc-v/))
and `dart` already has [beta support](https://dart-review.googlesource.com/c/sdk/+/217289) for `risc-v`

## Proposal

Support `flutter` on `android-riscv`

## Related issues

- https://github.com/flutter/flutter/issues/99963
- https://github.com/dart-lang/sdk/issues/38587
Repository: PowerToys
Issue: PowerRename remove all text after blank space
Labels: Needs-Triage

### Description of the new feature / enhancement

For example 
original: TEXT 1
renamed: TEXT 

### Scenario when this would be used?

When batch renaming 

### Supporting information

_No response_
Repository: TypeScript
Issue: Reordering variable declarations of Promise<any> and Promise<unknown> changes behavior
Labels: Suggestion,Needs Proposal

# Bug Report


### 🔎 Search Terms

`Promise<any>` `Promise<unknown>` instantiation order 

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ 

### ⏯ Playground Link

[Playground link with relevant code](https://www.typescriptlang.org/play?target=99&ts=4.0.5#code/PTAECUFMHsCcBNK1AFwBaQM6VQd2gLABQiAxgDYCGsO5kKoArgFygAKs0AtgJbYA8jAHYBrIdFxCAfMTJUaoOg0qsO3PpH6UhATxlFiIUAEFMmHgHMhkeKG2hIADwAONMz2hDUaSgz7tOXgFtPVAAHwD1AWExCWlDMAAjRgZ0X1BcHnJyJkRYC2hQTEZElB1nHBp4RlIUDyEE0AAVDFRynGgAMyYhetBECqF4TFBPDIxfDGRKUeRGDMoRuWobUE6eWEwUYiUevoBeUABZSYA6WG14bgAKAEpQKVAABlOAVmJQT9AAfkigyHOkAAVpBalpdFI7h8vqpAhpASCwTFxJJIbcANzEYjCeqndCQITXABuoH2jyJeOgAGUULAeEILHcMcQgA)

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
// Reorder these two
declare let u: Promise<unknown>
declare let a: Promise<any>

// Assigned an expression that is Promise<any> | Promise<unknown>
// but that will undergo subtype reduction
// The type of union depends on whether a or u was declared first
let union = Math.random() > 0.5
    ? Promise.reject<any>()
    : Promise.reject<unknown>();

union.then(v => v.toString());
```

### 🙁 Actual behavior

Reordering the unrelated variables `u` and `a` will cause the type of `union` to change between `Promise<unknown>` and `Promise<any>` (both in declarations and in the type of `v`, although tooltips still show `union` as `Promise<any>`)

### 🙂 Expected behavior

The type of `union` should not be impacted
Repository: pytorch
Issue: Add vmap support for torch.linalg.vander
Labels: good first issue,triaged,module: functorch

## Tasks
Add vmap support for the following PyTorch operations. That is, each one needs a batching rule.
- [ ] torch.linalg.vander

## Expected behavior
Currently, when one does vmap over them, they raise a warning suggesting the batching rule is not implemented:
```py
import torch
from functorch import vmap
x = torch.randn(4, 3, 2)
z = vmap(torch.linalg.vander)(x)
#  UserWarning: There is a performance drop because we have not yet implemented the batching rule
```
We expect to not see a warning

## Read this!

See this note for more context https://github.com/pytorch/pytorch/blob/master/functorch/writing_batching_rules.md

If you're new to developing PyTorch and/or function transforms, we would recommend reading through https://github.com/pytorch/pytorch/wiki/Core-Frontend-Onboarding#unit-8-function-transforms-optional

Should likely be similar to the `view_as_complex` operator here
https://github.com/pytorch/pytorch/blob/master/aten/src/ATen/functorch/BatchRulesUnaryOps.cpp#L64-L72
using the macro here
https://github.com/pytorch/pytorch/blob/master/aten/src/ATen/functorch/BatchRulesUnaryOps.cpp#L94

Please reach out on this issue if there's any questions!

## Testing

`pytest test/functorch/test_vmap.py -v -k "op_has_batch_rule and vander"` should pass (currently, it is an expected failure).


cc @zou3519 @Chillee @soumith
Repository: opencv
Issue: VideoWriter not working with 4.7.0.68
Labels: bug,category: python bindings,incomplete

### System Information

// example for python user
OpenCV python version: 4.7.0.68
Operating System / Platform: Ubuntu 20.04
Python version: 3.6.15

### Detailed description

Writing a video with VideoWriter now prints some GStreamer error logs:
```
GStreamer-CRITICAL **: 16:14:00.768: gst_element_make_from_uri: assertion 'gst_uri_is_valid (uri)' failed
[ WARN:0@17.055] global cap_gstreamer.cpp:2563 open OpenCV | GStreamer warning: cannot link element
```
It doesn't raise any Exception in Python but no video file has been created.

Downgrading to 4.6.0.66 fixes the problem

### Steps to reproduce

```
>>> import cv2
>>> writer = cv2.VideoWriter("test.mp4", )
>>> fourcc = cv2.VideoWriter_fourcc(*'mp4v')
>>> writer = cv2.VideoWriter("test.mp4", fourcc, 10, (100, 100))
[ WARN:0@59.608] global cap_gstreamer.cpp:2563 open OpenCV | GStreamer warning: cannot link elements
```

### Issue submission checklist

- [X] I report the issue, it's not a question
- [X] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [ ] I updated to the latest OpenCV version and the issue is still there
- [X] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: TypeScript
Issue: Uncapitalize seems to not working within a type helper
Labels: Bug,Help Wanted

# Bug Report

<!--
  Please fill in each section completely. Thank you!
-->

### 🔎 Search Terms

<!--
  What search terms did you use when trying to find an existing bug report?
  List them here so people in the future can find this one more easily.
-->
Uncapitalize

### 🕗 Version & Regression Information

<!-- When did you start seeing this bug occur?

"Bugs" that have existed in TS for a long time are very likely to be FAQs; refer to
  https://github.com/Microsoft/TypeScript/wiki/FAQ#common-bugs-that-arent-bugs

If possible, please try testing the nightly version of TS to see if it's already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly

Note: The TypeScript Playground can be used to try older versions of TypeScript.

Please keep and fill in the line that best applies:
-->
- This is the behavior in every version I tried, and I reviewed the FAQ for entries about Uncapitalize

### ⏯ 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?ssl=25&ssc=14&pln=25&pc=26#code/C4TwDgpgBAwghgWwgG3gZwgRgDwCgpQDKUEAHsBAHYAmaUawATgJaUDmANPlADInlVa9JqzZQAvLwD2AdwiMAxnAzZCAPi4EAShDpkKNOgxbsJUAETncas332C6l7gH4oAVUpKwzYHGTMALwhsHTQ1bgAuXn4DIQADABIAb1YAM3koAAkAXwB9ZLSMgBVsuJdYRBR0LGxKCAA3eQ4oIubEpNDs5PhvX38g7Ey1UvCCKPgkVGUausbGZss25M7uuF6-QOCeYbi1AG5cXFBICsnqgCY8AmJ7Q2ETTm47ATvjUVtZeSUVdU0oUJiDnu70kThskmesUcVgIrlCkWit3iBUo6UYWTyKLRLVK5QmVWml1mTRaSw6ui6SR6Pg2AyGIwR+KmGCJDRJiyg7RWVLWNP6Wx2+0OR3A0AoDEwZiZF2w5gAYgB5BUAIQAglpzOEAPRaghQAB6zkOxzFumA5zMHi8fM22GlhNlipV6s12t1BENQA)

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
type CamelCase1<
  S extends string,
  L extends string = Lowercase<S>,
  Res extends string = ""
> = L extends ""
  ? Uncapitalize<Res>
  : L extends `${infer H}_${infer T}`
  ? CamelCase1<never, T, `${Res}${Capitalize<H>}`>
  : CamelCase1<never, "", `${Res}${Capitalize<L>}`>;

type test1 = CamelCase2<"FOOBAR">
//   ^? type test1 = "Foobar"

type CamelCase2<
  S extends string,
  L extends string = Lowercase<S>,
  Res extends string = ""
> = L extends ""
  ? Res
  : L extends `${infer H}_${infer T}`
  ? CamelCase2<never, T, `${Res}${Capitalize<H>}`>
  : CamelCase2<never, "", `${Res}${Capitalize<L>}`>;

type test2 = Uncapitalize<CamelCase2<"FOOBAR">>
//   ^? type test2 = "foobar"
```

### 🙁 Actual behavior

First letter is uppercase

### 🙂 Expected behavior

<!-- What you expected to happen instead, and why -->
First letter should be lowercase
Repository: bitcoin
Issue: listreceivedbyaddress is empty for descriptor (but not legacy) wallets
Labels: Bug

https://bitcoincore.org/bin/bitcoin-core-24.0.1/bitcoin-24.0.1-x86_64-linux-gnu.tar.gz

Problem: listreceivedbyaddress always returns an empty array for a watch-only wallet when it's of type descriptor (not legacy). This problem doesn't occur with a legacy watch-only wallet, only a descriptor watch-only wallet.

Apparent reason: bitcoind thinks the addresses are for change.

Work-around: When importing descriptors, set active=true.

Thanks to achow101 on IRC Libera Chat #bitcoin-core-dev, 2023-01-04.

```
$ cat $HOME/data1/bitcoin.conf 
printtoconsole=1
regtest=1
txindex=1
[regtest]
port=18444
rpcport=18443

$ $HOME/bitcoin-24.0.1/bin/bitcoin-qt -datadir=$HOME/data1 -server -fallbackfee=0.00001 &

$ cat bcli.sh 
#!/bin/bash
$HOME/bitcoin-24.0.1/bin/bitcoin-cli -datadir=$HOME/data1 "$@"


$ bcli.sh createwallet w1
$ bcli.sh createwallet w2 true true
$ bcli.sh -rpcwallet=w1 listdescriptors
...
    {
      "desc": "wpkh([577ce3ca/84'/1'/0']tpubDCNwCevBBSLGZm5d2urnpLDD2B4s5dWf7TRigFngte9M7sijNQg6QVjq1K7Nb7uLAP7xLn2h4X1MoiT3JmMP3sQYuKsY1qnPj1HR63hQDuT/0/*)#cw6xz6mx",
      "timestamp": 1672848018,
      "active": true,
      "internal": false,
      "range": [
        0,
        999
      ],
      "next": 0
    },
...

$ bcli.sh -rpcwallet=w2 importdescriptors "[{\"desc\": \"wpkh([577ce3ca/84'/1'/0']tpubDCNwCevBBSLGZm5d2urnpLDD2B4s5dWf7TRigFngte9M7sijNQg6QVjq1K7Nb7uLAP7xLn2h4X1MoiT3JmMP3sQYuKsY1qnPj1HR63hQDuT/0/*)#cw6xz6mx\", \"timestamp\": 0, \"range\": 999}]"

$ bcli.sh -rpcwallet=w1 getnewaddress
bcrt1qxu3fl6lyqydvtgxsdpeu69gyywy2dya5a4kray

$ bcli.sh -rpcwallet=w1 generatetoaddress 101 bcrt1qxu3fl6lyqydvtgxsdpeu69gyywy2dya5a4kray

$ bcli.sh -rpcwallet=w2 listreceivedbyaddress 1 true true "" true
[
]
```
Repository: material-ui
Issue: "disableCloseOnSelect" and disable modifying the value manually
Labels: support: question,component: select

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Summary 💡

I don't know if it's possible to make a dropdown-like control where we can select a value from a list (and manually typing the value is disabled) and we can also "disableCloseOnSelect".

### Examples 🌈

The "disableCloseOnSelect" is possible with [autocomplete of Material UI](https://mui.com/material-ui/react-autocomplete) like illustrated in the code: 
https://codesandbox.io/s/zealous-herschel-gw3bq4?file=/demo.tsx. However, I would like to disable the possibility to modify the value manually; people can only select the value from the list. 

By contrast, [Select of Material UI](https://mui.com/material-ui/react-select/) and [DropDownMenu](https://stackblitz.com/edit/drop-down-menu-material-ui?file=index.js) disable the possibility of modifying the value manually. However, I tried to add `disableCloseOnSelect`, it did not work.

### Motivation 🔦

Both of the two features are useful. I don't understand why we cannot have both in one control.
Repository: storybook
Issue: [Bug]: Height calculation for embedded stories is incorrect in Firefox
Labels: bug,needs triage

### Describe the bug

Stories embedded in MDX from other files always render with a `Canvas` with a fixed height of 70 in Firefox. 

#### Discovered while trying to debug

When stories are embedded in MDX from other files the resulting wrapping that the Canvas does will use different mechanics to decide content size in different browser.

When the zoom css property is available it will be used. When it isn't, height is decided [based on the size of the component the story renders](https://github.com/storybookjs/storybook/blob/next/code/ui/components/src/Zoom/ZoomElement.tsx#L66). However that seems to not be working correctly, as on Firefox this always result to the wrapping div having a height property of 20 and the css height property for it being set to 70 ([this](https://github.com/storybookjs/storybook/blob/next/code/ui/components/src/Zoom/ZoomElement.tsx#L17) seems to just add 50px to the height)

### To Reproduce

- [repository](https://github.com/kunev/storybook-ff-zoom-issue-demo)

- [deployed on gh-pages](https://kunev.github.io/storybook-ff-zoom-issue-demo/?path=/docs/demo-embeding-stories--inlined-demo) explaining the issue with a demo


<details>
<summary>Screenshots</summary>

Looks OK in Chrome
![Screenshot from Chrome](https://raw.githubusercontent.com/kunev/storybook-ff-zoom-issue-demo/main/screenshots/chrome.png)

Does not look OK in Firefox
![Screenshot from Firefox](https://raw.githubusercontent.com/kunev/storybook-ff-zoom-issue-demo/main/screenshots/firefox.png)
</details>

### System

```shell
Environment Info:
(node:362359) ExperimentalWarning: The Fetch API is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)

  System:
    OS: Linux 6.1 Arch Linux
    CPU: (16) x64 AMD Ryzen 7 PRO 5850U with Radeon Graphics
  Binaries:
    Node: 18.0.0 - ~/.nvm/versions/node/v18.0.0/bin/node
    Yarn: 1.22.15 - ~/.nvm/versions/node/v18.0.0/bin/yarn
    npm: 8.6.0 - ~/.nvm/versions/node/v18.0.0/bin/npm
  Browsers:
    Firefox: 108.0.1
  npmPackages:
    @storybook/addon-actions: ^6.5.15 => 6.5.15 
    @storybook/addon-essentials: ^6.5.15 => 6.5.15 
    @storybook/addon-interactions: ^6.5.15 => 6.5.15 
    @storybook/addon-links: ^6.5.15 => 6.5.15 
    @storybook/builder-webpack5: ^6.5.15 => 6.5.15 
    @storybook/manager-webpack5: ^6.5.15 => 6.5.15 
    @storybook/node-logger: ^6.5.15 => 6.5.15 
    @storybook/preset-create-react-app: ^4.1.2 => 4.1.2 
    @storybook/react: ^6.5.15 => 6.5.15 
    @storybook/testing-library: ^0.0.13 => 0.0.13
```


### Additional context

_No response_
Repository: neovim
Issue: The "search hit BOTTOM, continuing at TOP" warning is not displayed
Labels: bug-vim,needs:vim-patch

### Neovim version (nvim -v)

v0.6.1

### Vim (not Nvim) behaves the same?

no, vim 8.2.4919

### Operating system/version

ubuntu 22.04 

### Terminal name/version

gnome-terminal 3.36.2

### $TERM environment variable

xterm-256color

### Installation

system package manager

### How to reproduce the issue

nvim --clean
:edit /etc/fstab
?file

### Expected behavior

Vim displays "search hit TOP, continuing at BOTTOM".

### Actual behavior

Neovim displays the "file" search string instead of the "search hit TOP, continuing and BOTTOM" warning.

There is no init.vim file, no plugins installed and no other changes to the defaults. The same behavior is present since neovim v0.2.2.

A gdb breakpoint on `give_warning` in nvim does get reached, `VV_WARNINGMSG` gets set but instead of the warning, the searched string is displayed even when wrapping (unlike in vim, where the warning is displayed instead of the string).

Without this red warning, I can't tell when the search wraps, and I keep hitting `n` in an endless loop.
Repository: storybook
Issue: [Feature Request]: Babel Transform In CSF3
Labels: feature request,needs triage

### Is your feature request related to a problem? Please describe

Now that SB 7 doesnt allow dynamic titles, could there be an option for a static babel transform, so that we can inject titles from the filesystem conventions or something similar.


### Describe the solution you'd like

Really dirty example
```js
//Developers would somehow need to be able to inject/specify this transform in the storybook main.js or something
function createTransform() { 
  const sourceRegex = /\.stories\.(j|t)sx?$/;
  const getStoryTitle = (filename) => `some title based on ${filename}`;
  
  return (code, filename) => {
    if (filename){          
          if (filename.includes("node_modules")) {
            return;
          }
    
          if (!sourceRegex.test(filename)) {
            return;
          }
    
          return code.replace(/%{path}%/, getStoryTitle(filename));
    }
    return code;
  }
}
//--------------------------------

transforms.push(importMe.createTransform());

function transform(code, filename){
     for(var t of transforms) {
        code = t(code, filename);
     }
     
     return code;
}

var babelParse = (code, filename) => {    
    code = transform(code, filename);
    return parser.parse(code, {
      sourceType: "module",
      plugins: [        
        "jsx",
        "typescript",
        ["decorators", { decoratorsBeforeExport: !0 }],
        "classProperties",        
      ],
      tokens: !0,
    })};
```

```tsx
const meta = {
  title: "%{path}%",
  component: Component
} satisfies Meta<typeof Component>;
```

### Describe alternatives you've considered

_No response_

### Are you able to assist to bring the feature to reality?

no

### Additional context

_No response_
Repository: godot
Issue: Black screen on Android devices not supporting GLES3
Labels: enhancement,platform:android,topic:porting

### Godot version

v4.0.beta10.official [d0398f62f]

### System information

Android 7.1 - armeabi-v7a

### Issue description

Exporting a project to Android using the renderer `gl_compatibility` results on a black screen on Android 7.1 (armeabi-v7a)

May be related to #63943 



### Steps to reproduce

Setup a project with `gl_compatibility` renderer for mobile, export to Android (armeabi-v7a , debug).

Opening the app on Android 7.1 will result on a black screen after the loading screen.

### Minimal reproduction project

[BlackScreen.zip](https://github.com/godotengine/godot/files/10346567/BlackScreen.zip)