Incremental steps to support Android XR #115

matthargett · 2025-09-28T00:50:36Z

Bump the NDK just below unstable r29 and SDK API level 36 that appear to be necessary for building for Android XR devices. Note that targeting API Level 35 is mandatory for publishing new apps to Google Play since August 2025, so this is a bit overdue for those reasons as well.

The C++20 incompatibility highlighted by newer clang in NDK 28 was highlighted by a similar downstream PR in BabylonNative: BabylonJS/BabylonNative#1552

I tried to also use the Android system-installed v8 library, rather than building from a separate source, so that profile-optimized system version that received security updates keeps apps performant. The performance aspect is key for 3D/XR workloads, and the security aspect is key when BabylonJS is processing user-supplied data by opening and rendering splats, behavior graphs, WGSL shaders, etc. It was not straightforward, and so I'm leaving that as a separate step in the future PR.

This change updates the Azure Pipelines CI for Android to use NDK version 28.2.13676358 and SDK API level 35. The previous configuration used an outdated NDK and SDK, causing the build to fail with an "NDK is not installed" error. This commit addresses the issue by: - Updating the `ndkVersion` variable in `azure-pipelines.yml`. - Modernizing the Android job in `jobs/android.yml` to: - Use the `macos-latest` VM image. - Install the correct NDK and SDK versions. - Create an AVD with the new system image. - Use JDK 17 for the Gradle build.

Fix: Update Android CI to use NDK 28 and API 35

This change updates the Azure Pipelines CI for Android to use NDK version 28.2.13676358 and SDK API level 35. The previous configuration used an outdated NDK and SDK, causing the build to fail. This commit addresses the issue by: - Updating the `ndkVersion` variable in `azure-pipelines.yml`. - Modernizing the Android job in `jobs/android.yml` to: - Use the `macos-latest` VM image. - Install the correct NDK and SDK versions. - Create an AVD with the new system image. - Use JDK 17 for the Gradle build. - Add `_JAVA_OPTIONS` to fix `NoClassDefFoundError` with `sdkmanager` on newer JDKs.

Updated required tools and minimum Android version in README. Added link to Android OS measured usages globally. Note specifically Android-base XR device coverage that Android 10 and up includes. This *does* exclude Oculus Go (which was left on Android 7 before EOL), which we can discuss further if coverage of that device is deemed critical.

…it explicitly now. Update README to be specific about minimums and why.

…ent crashes on shutdown

… clang in NDK 29

…crementally

… size cost to downstream users, as this JSC includes full intl build. It might still be worth it based on the JIT and GC performance improvements that shoudl give noticeable uplift to downstream users.

…cases

… which should also allow some of the explicit VM flags to be eliminated

…lding everything else back. It should be discussed why Chakra support is still needed in the OSS repo.

…g out in CI. this worked okay on my local macbook before, so I'm assuming swap was the problem. this makes it faster on my local macbook, hopefully fixes it in CI.

…simulator. TypedArray test has some endianness specifics, skipping it temporarily. use the globalThis polyfill more consistently.

Core/AppRuntime/V8Inspector/Source/V8InspectorAgent.cpp

CedricGuillemet · 2025-10-07T12:53:03Z

test failing on Android is

10-04 00:11:49.226  3921  4067 I JavaScript: [log]       1) should detect JavaScript engine type
10-04 00:11:49.227  3921  4067 I JavaScript: [error]
10-04 00:11:49.227  3921  4067 I JavaScript: [FAILED] JavaScript Engine Compatibility Engine Detection should detect JavaScript engine type
10-04 00:11:49.228  3921  4067 I JavaScript: [error]   File: unknown
10-04 00:11:49.228  3921  4067 I JavaScript: [error]   Error: expected false to be true
10-04 00:11:49.228  3921  4067 I JavaScript: [error]   Stack: AssertionError: expected false to be true
10-04 00:11:49.228  3921  4067 I JavaScript:              at Context.<anonymous> (app:///Scripts/tests.js:73:84)
10-04 00:11:49.228  3921  4067 I JavaScript:              at callFn (app:///Scripts/tests.js:19712:21)

… apps that are testing deployments of different JS engines can include which runtime is being used in their JS-based telemetry (which is preferable over native telemetry because it can be updated OTA and while native app container is backgrounded), but it's proven to be too volatile. I could delete it, but preferring to leave it skipped here as a placeholder.

Co-authored-by: Gary Hsu <[email protected]>

…around

bghgary · 2025-10-16T17:29:10Z

Core/Node-API/Source/js_native_api_javascriptcore.cc

+    static constexpr int compare(const char_type* s1, const char_type* s2, size_t n) noexcept {
+      for (size_t i = 0; i < n; ++i) {
+        if (s1[i] < s2[i]) return -1;
+        if (s1[i] > s2[i]) return 1;
+      }
+      return 0;
+    }
+
+    static constexpr const char_type* find(const char_type* s, size_t n, const char_type& c) noexcept {
+      for (size_t i = 0; i < n; ++i) {
+        if (s[i] == c) return s + i;
+      }
+      return nullptr;
+    }


This code is adding a template specialization, but it is not a specialization of std::char_traits. This is just a custom struct with some static functions. You can probably just not use templates at all since it's just a simple function call to get the length.

bghgary · 2025-10-16T17:34:45Z

.gitignore

@@ -1 +1,2 @@
 /Build
+/Tests/UnitTests/dist/


I don't know if this is from your PR, but we typically avoid generating files in the source tree. Generated files should go in the CMake binary folder which we typically put in Build.

bghgary · 2025-10-16T21:01:23Z

Tests/UnitTests/Scripts/engine-compat-tests.ts

+        });
+    });
+
+    describe("Unicode and String Encoding", function () {


Maybe I need more context on the sanitizers. What sanitizers are we talking about?

Also, I think you mean something different when you say N-API (or Node-API). Node-API is the contract between C++ and JavaScript, as well as the implementation of Node-API against a JavaScript engine.

If we want to test Node-API, it should be using something in the Node-API contract (i.e., something needs to cross the native to js or js to native bridge). There is actually a good set of tests for Node-API in Hermes when Node-API was introduced there. It would be great to reuse those tests here, but that should be a completely separate PR and is somewhat of a big lift.

Unless I'm missing something, these tests are strictly testing different JavaScript engines which is not necessarily bad in of itself, but they have nothing to do with Node-API. There are already conformance tests for ECMAScript that do this kind of test, such as https://compat-table.github.io/compat-table/es6.

Tests/package-lock.json

…ator. For now, we only have fdsan, ubsan, and tsan, which is still tons better coverage and insight than we had previously.

…gs, but I'll save it for a separate PR.

… like the rest of the repo does. Transfer globalThis test into C++ and don't run on Windows (Chakra). delete the JS version of the compat tests. Update webpack to be more resilient to retargeted build output directory, which I was doing to run AddressSanitizer (asan) builds in parallel with the regular sanitizers, since ASan is mutually exclusive with the others.

…d tests

… due to an unclean shutdown of the AppRuntime's Work Queue. I'm trying not to fix all the sanitizer issues in this PR, but want the test to be a golden example of micro-embedding that doesn't have immediate bugs.

…entation

…ecause it stores wrapped objects in an intermediary void*, the vtpr sanitizer reasonably complains. this macro allows us to sidestep the issue only for those specific problematic calls.

…squash! js_native_api_javascriptcore.cc:1677:34: runtime error: nan is outside the range of representable values of type 'int'

bghgary

Sorry @matthargett for all the comments. We are getting closer though.

bghgary · 2025-10-21T19:57:45Z

Core/Node-API/Include/Shared/napi/napi-inl.h

+#if defined(__clang__) || defined(__GNUC__)
+#define NAPI_NO_SANITIZE_VPTR __attribute__((no_sanitize("vptr")))
+#else
+#define NAPI_NO_SANITIZE_VPTR
+#endif
+


Where did these changes come from? We try to ensure these headers match the original unless it is documented as a change. Search for // [BABYLON-NATIVE-ADDITION]

In the commit message, I noted that this should be upstreamed. When they cast the T down to a void* l, it loses RTTI and that trips a sanitizer. I'll add the local comment and submit a PR upstream as well.

bghgary · 2025-10-21T19:58:52Z

Core/Node-API/Source/js_native_api_javascriptcore.cc

 namespace {
-  // Template specialization to provide char_traits functionality for JSChar (unsigned short)
-  // at compile time, mimicking std::char_traits interface
+  // Minimal char_traits-like helper for JSChar (unsigned short) to compute string length at compile time


This should just be a simple function. There is no reason for the struct or template.

bghgary · 2025-10-21T20:01:37Z

Tests/UnitTests/Android/app/src/main/cpp/CMakeLists.txt

+set(_jsruntimehost_runtime_source "")
+set(_jsruntimehost_runtime_target "")
+
+if(ANDROID)
+    set(_jsruntimehost_sanitizers "")
+    if(DEFINED ENV{JSRUNTIMEHOST_NATIVE_SANITIZERS})
+        set(_jsruntimehost_sanitizers "$ENV{JSRUNTIMEHOST_NATIVE_SANITIZERS}")
+    endif()
+    if(DEFINED ENV{JSRUNTIMEHOST_ENABLE_ASAN})
+        if(_jsruntimehost_sanitizers STREQUAL "")
+            set(_jsruntimehost_sanitizers "address")
+        else()
+            set(_jsruntimehost_sanitizers "${_jsruntimehost_sanitizers},address")
+        endif()
+    endif()
+    if(NOT _jsruntimehost_sanitizers STREQUAL "")
+        string(REGEX REPLACE "[ \t\r\n]" "" _jsruntimehost_sanitizers "${_jsruntimehost_sanitizers}")
+        string(REGEX REPLACE ",+" "," _jsruntimehost_sanitizers "${_jsruntimehost_sanitizers}")
+        string(REGEX REPLACE "^,|,$" "" _jsruntimehost_sanitizers "${_jsruntimehost_sanitizers}")
+        if(NOT _jsruntimehost_sanitizers STREQUAL "")
+            message(STATUS "Enabling sanitizers: ${_jsruntimehost_sanitizers}")
+            add_compile_options("-fsanitize=${_jsruntimehost_sanitizers}" "-fno-omit-frame-pointer")
+            add_link_options("-fsanitize=${_jsruntimehost_sanitizers}")
+            set(_jsruntimehost_sanitizers_list "${_jsruntimehost_sanitizers}")
+            string(REPLACE "," ";" _jsruntimehost_sanitizers_list "${_jsruntimehost_sanitizers_list}")
+            list(FIND _jsruntimehost_sanitizers_list "undefined" _jsruntimehost_has_ubsan)
+            if(_jsruntimehost_has_ubsan GREATER -1)
+                if(ANDROID_ABI STREQUAL "arm64-v8a")
+                    set(_jsruntimehost_san_arch "aarch64")
+                elseif(ANDROID_ABI STREQUAL "armeabi-v7a")
+                    set(_jsruntimehost_san_arch "arm")
+                elseif(ANDROID_ABI STREQUAL "x86")
+                    set(_jsruntimehost_san_arch "i686")
+                elseif(ANDROID_ABI STREQUAL "x86_64")
+                    set(_jsruntimehost_san_arch "x86_64")
+                else()
+                    set(_jsruntimehost_san_arch "")
+                endif()
+                if(_jsruntimehost_san_arch)
+                    get_filename_component(_jsruntimehost_toolchain_dir "${CMAKE_C_COMPILER}" DIRECTORY)
+                    get_filename_component(_jsruntimehost_toolchain_root "${_jsruntimehost_toolchain_dir}" DIRECTORY)
+                    file(GLOB _jsruntimehost_ubsan_runtime
+                        "${_jsruntimehost_toolchain_root}/lib/clang/*/lib/linux/libclang_rt.ubsan_standalone-${_jsruntimehost_san_arch}-android.so")
+                    list(LENGTH _jsruntimehost_ubsan_runtime _jsruntimehost_ubsan_runtime_len)
+                    if(_jsruntimehost_ubsan_runtime_len GREATER 0)
+                        list(GET _jsruntimehost_ubsan_runtime 0 _jsruntimehost_ubsan_runtime_path)
+                        set(_jsruntimehost_runtime_source "${_jsruntimehost_ubsan_runtime_path}")
+                        set(_jsruntimehost_runtime_target "libclang_rt.ubsan_standalone-${_jsruntimehost_san_arch}-android.so")
+                    else()
+                        message(WARNING "UBSan runtime not found for ABI ${ANDROID_ABI}")
+                    endif()
+                endif()
+            endif()
+        endif()
+    endif()
+endif()


I don't know what I'm looking at. Why is it so complex?

Also, is the intent of this PR to add the sanitizer options?

bghgary · 2025-10-21T20:03:41Z

Tests/UnitTests/Android/app/build.gradle

+        ndk {
+            def abiFiltersProp = project.findProperty("abiFilters")?.toString()
+            if (abiFiltersProp) {
+                def propFilters = abiFiltersProp.split(',').collect { it.trim() }.findAll { !it.isEmpty() }
+                if (!propFilters.isEmpty()) {
+                    abiFilters(*propFilters)
+                }
+            } else {
+                // Prefer injected ABI hints and fall back to a host-aware default
+                def requestedAbi = project.findProperty("android.injected.build.abi") ?: System.getenv("ANDROID_ABI")
+                def defaultAbis = []
+                if (requestedAbi) {
+                    defaultAbis = requestedAbi.split(',').collect { it.trim() }.findAll { !it.isEmpty() }
+                }
+                if (defaultAbis.isEmpty()) {
+                    def hostArch = (System.getProperty("os.arch") ?: "").toLowerCase()
+                    if (hostArch.contains("aarch64") || hostArch.contains("arm64")) {
+                        defaultAbis = ['arm64-v8a']
+                    } else {
+                        defaultAbis = ['arm64-v8a', 'x86_64']
+                    }
+                }
+                abiFilters(*defaultAbis)


What is the purpose of this change?

bghgary · 2025-10-21T20:03:59Z

Tests/UnitTests/Scripts/tests.ts

@@ -1095,7 +1095,6 @@ describe("Blob", function () {

 function runTests() {
    // Import the engine compatibility tests after Mocha is set up


Should this comment still be here?

bghgary · 2025-10-21T22:50:39Z

Tests/CMakeLists.txt

+set(JSRUNTIMEHOST_OUTPUT_DIR "${CMAKE_BINARY_DIR}/Tests/UnitTests/dist")
+set(JSRUNTIMEHOST_OUTPUT_DIR "${JSRUNTIMEHOST_OUTPUT_DIR}" CACHE INTERNAL "Output directory for bundled unit test scripts")


Why do we need to set both the cache and local variable?

bghgary · 2025-10-21T22:51:16Z

Tests/CMakeLists.txt

+set(JSRUNTIMEHOST_OUTPUT_DIR "${CMAKE_BINARY_DIR}/Tests/UnitTests/dist")
+set(JSRUNTIMEHOST_OUTPUT_DIR "${JSRUNTIMEHOST_OUTPUT_DIR}" CACHE INTERNAL "Output directory for bundled unit test scripts")
+file(MAKE_DIRECTORY "${JSRUNTIMEHOST_OUTPUT_DIR}")
+file(REMOVE_RECURSE "${CMAKE_CURRENT_SOURCE_DIR}/UnitTests/dist")


Is this a good idea? Seems dangerous to remove a folder in the source folder when running CMake.

bghgary · 2025-10-21T23:02:13Z

Tests/CMakeLists.txt

+file(MAKE_DIRECTORY "${JSRUNTIMEHOST_OUTPUT_DIR}")
+file(REMOVE_RECURSE "${CMAKE_CURRENT_SOURCE_DIR}/UnitTests/dist")
+
+set(ENV{JSRUNTIMEHOST_BUNDLE_OUTPUT} "${JSRUNTIMEHOST_OUTPUT_DIR}")


Sorry, looking at this more. I didn't realize what was happening here. Looks like dist\tests.js is committed to source control, so my original comment about generated files being in the CMake binary folder does not make sense. Can you please revert the changes for this? Also, don't add the dist folder to .gitignore like you had originally. It actually needs to be included in the PR if the ts file changes.

bghgary · 2025-10-21T23:02:53Z

CMakeLists.txt

+    GIT_REPOSITORY https://github.com/matthargett/AndroidExtensions.git
+    GIT_TAG        fix-stale-JNI-ref)


Just noting that this needs to be updated once AndroidExtensions PR is merged

bghgary · 2025-10-21T23:03:26Z

CMakeLists.txt

+if(APPLE)
+    set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -fobjc-arc")
+    if(NOT CMAKE_BUILD_TYPE OR CMAKE_BUILD_TYPE STREQUAL "Debug")
+        if(NOT DEFINED JSRUNTIMEHOST_NATIVE_SANITIZERS)
+            set(JSRUNTIMEHOST_NATIVE_SANITIZERS "address,undefined")
+        endif()
+        if(JSRUNTIMEHOST_NATIVE_SANITIZERS)
+            message(STATUS "macOS sanitizers enabled: ${JSRUNTIMEHOST_NATIVE_SANITIZERS}")
+            add_compile_options("-fsanitize=${JSRUNTIMEHOST_NATIVE_SANITIZERS}" "-fno-omit-frame-pointer")
+            add_link_options("-fsanitize=${JSRUNTIMEHOST_NATIVE_SANITIZERS}")
+        endif()
+    endif()
+endif()


Are sanitizers supposed to be part of this PR?

To some degree, yes, because NDK 28 turns some of them on by default and the crash that occurred is what got me started on that sidequest. We could override the NDK 28 default to turn off default sanitizers, and put the fixes into a separate PR. Up to you :)

I was curious about what could be found with sanitizers so I opened this PR : BabylonJS/BabylonNative#1559

…-jsruntimehost-for-android-xr-compatibility

CedricGuillemet · 2025-11-04T16:46:44Z

Hi @matthargett I'm trying to split the work in parts easier to review and test : #118

…e source tree

…ility

… this directory. ignore it.

…allowed by newer clang in NDK 29

…I by detecting the major version

…ric separators, causing the test to crash. dynamically work around this functional difference.

…he JS engine doesn't support numeric separators. work around a specific compile issue that only affects JSC on Android

matthargett and others added 27 commits September 27, 2025 17:40

Update Android build to NDK 28 and system V8

79e03c1

Improve Android V8 header discovery

43d677a

Improve Android V8 header hint coverage

22d1f96

Improve Android V8 discovery for SDK 35

435c798

Log Android V8 search hints and broaden header discovery

e1d0f2f

Force Android builds to use NDK r28c and API 35

dbef5ba

Relax Android NDK version guard

1159300

Pin Gradle NDK wiring to r28c

39f1536

Improve Android NDK detection for Android tests

82b17e8

Simplify Android NDK environment configuration

2dd6185

Merge pull request #2 from rebeckerspecialties/feat/android-ci-update

02a7dc5

Fix: Update Android CI to use NDK 28 and API 35

New Java doesn't implicitly include bind support, we have to specify …

f98247a

…it explicitly now. Update README to be specific about minimums and why.

work around latent unsafe file descriptor issue that causes intermitt…

7faff92

…ent crashes on shutdown

fix the C++20 libc++ deprecation issue more elegantly

b3480ca

pull in the already-existing upstream fix for compatiblity with newer…

118450b

… clang in NDK 29

revert to using third aprty prebuilt v8 so we can test things more in…

4d9eb96

…crementally

fix another fdsan-found issue that causes intermittent crashes on exit

e5e5648

Add tests for updated JS capabilities from newer JSC. This has an apk…

d205c4a

… size cost to downstream users, as this JSC includes full intl build. It might still be worth it based on the JIT and GC performance improvements that shoudl give noticeable uplift to downstream users.

JSC's results deviate from the standard. for now, let's capture both …

4633fa3

…cases

Use latest Java LTS so that modern commandline options are available,…

465685e

… which should also allow some of the explicit VM flags to be eliminated

skip tests Chakra doesn't support only on win32. Chakra support is ho…

fcc3ce1

…lding everything else back. It should be discussed why Chakra support is still needed in the OSS repo.

See if reducing resource usage of the simulator helps solve the timin…

c1fdff4

…g out in CI. this worked okay on my local macbook before, so I'm assuming swap was the problem. this makes it faster on my local macbook, hopefully fixes it in CI.

Give more specific failure information when tests fail in the device …

a54a121

…simulator. TypedArray test has some endianness specifics, skipping it temporarily. use the globalThis polyfill more consistently.

some of these tests won't work on jsc-android

be1baf6

CedricGuillemet reviewed Oct 7, 2025

View reviewed changes

Core/AppRuntime/V8Inspector/Source/V8InspectorAgent.cpp Outdated Show resolved Hide resolved

matthargett and others added 3 commits October 15, 2025 19:59

Update README.md

2e467dd

Co-authored-by: Gary Hsu <[email protected]>

PR feedback

84005c0

now that Azure pipeline uses JDK 18, we don't need this original work…

9e3cfc9

…around

bghgary reviewed Oct 16, 2025

View reviewed changes

matthargett added 9 commits October 19, 2025 01:09

fix wrong abi being forced. pull in AndroidExtensiosn bug fix branch.

98e80ef

I simply cannot get address sanitizer to run well under Android simul…

499ae36

…ator. For now, we only have fdsan, ubsan, and tsan, which is still tons better coverage and insight than we had previously.

fix macOS build of unit tests, enable sanitizers. they are finding bu…

51f1f45

…gs, but I'll save it for a separate PR.

make globalThis test using ifdefs in consistent way with other skippe…

403b452

…d tests

fix test failure that was an issue in the test rather than the implem…

ebf6950

…entation

this is a change that should be contributed to upstream node-api -- b…

cfb1af6

…ecause it stores wrapped objects in an intermediary void*, the vtpr sanitizer reasonably complains. this macro allows us to sidestep the issue only for those specific problematic calls.

fix ubsan identified issue with invalid nan conversion. great bug to …

d30f735

…squash! js_native_api_javascriptcore.cc:1677:34: runtime error: nan is outside the range of representable values of type 'int'

bghgary reviewed Oct 21, 2025

View reviewed changes

Merge branch 'main' of github.com:BabylonJS/JsRuntimeHost into update…

d23737f

…-jsruntimehost-for-android-xr-compatibility

matthargett added 14 commits November 8, 2025 19:23

merge

ada4a17

minor cleanup

56c1f3e

use latest upstream hash to fix compile error .don't put things in th…

04bcc75

…e source tree

reconcile with merged extractions

78176d0

Merge branch 'main' into update-jsruntimehost-for-android-xr-compatib…

99539a6

…ility

Revert redundant files to match origin/main

a6eb7f5

a default C++ VS code add-in is now creating huge LLVM index files in…

3c25b52

… this directory. ignore it.

use latest AndroidExtensions hash

46b9210

avoid non-standrd template specialization of basic_string that is dis…

a6a6ec0

…allowed by newer clang in NDK 29

don't change CI task name. include a little more context around errors

f704440

merge from main

8fa7d57

fix an MSVC compile error, and support a breaking change in the v8 AP…

f31e9d4

…I by detecting the major version

Chakra and the old JSC in jsc-android-buildscripts don't support nume…

6d5b5e5

…ric separators, causing the test to crash. dynamically work around this functional difference.

have better reporting when there's an eval-level problem, like when t…

38c5d54

…he JS engine doesn't support numeric separators. work around a specific compile issue that only affects JSC on Android

		@@ -1095,7 +1095,6 @@ describe("Blob", function () {

		function runTests() {
		// Import the engine compatibility tests after Mocha is set up

		set(JSRUNTIMEHOST_OUTPUT_DIR "${CMAKE_BINARY_DIR}/Tests/UnitTests/dist")
		set(JSRUNTIMEHOST_OUTPUT_DIR "${JSRUNTIMEHOST_OUTPUT_DIR}" CACHE INTERNAL "Output directory for bundled unit test scripts")

		GIT_REPOSITORY https://github.com/matthargett/AndroidExtensions.git
		GIT_TAG fix-stale-JNI-ref)

Incremental steps to support Android XR #115

Are you sure you want to change the base?

Incremental steps to support Android XR #115

Uh oh!

Conversation

matthargett commented Sep 28, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

CedricGuillemet commented Oct 7, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

bghgary Oct 16, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

bghgary left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

CedricGuillemet commented Nov 4, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

matthargett commented Sep 28, 2025 •

edited

Loading

bghgary Oct 16, 2025 •

edited

Loading