qcbor: library to expose Qualcomm Security Package #1166

jiaxli-QC · 2025-10-29T07:22:17Z

Add a recipe to build qcbor, library to work with security functionality on Qualcomm platforms.

The libqcbor, which are only available through meta-oe, is depended by Qcom-teec and MinkIPC. Thus add libqcbor recipe to the corresponding dynamic-layers subdir.

The qcbor library is used for decoding and encoding data structures.

jiaxli-QC · 2025-10-29T07:25:54Z

Hi reviewer, this PR has been separated from PR1094. Following our internal discussion, we have decided to share the qcbor, qcom-teec, and minkipc components individually.
Our expected merge order is:

vksharma-oss · 2025-10-29T08:11:13Z

recipes-security/qcbor/qcbor_git.bb

+HOMEPAGE = "https://github.com/laurencelundblade/QCBOR.git"
+SECTION = "libs"
+
+LICENSE = "BSD-3-Clause"


qcbor is using the BSD-3-clause license:
ref: https://github.com/laurencelundblade/QCBOR?tab=License-1-ov-file

Isn't it what is stated here?

BSD 3-Clause License

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:

Redistributions of source code must retain the above copyright notice, this
list of conditions and the following disclaimer.

Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.

Neither the name of the copyright holder nor the names of its
contributors may be used to endorse or promote products derived from
this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

vksharma-oss · 2025-10-29T08:13:00Z

recipes-security/qcbor/qcbor_git.bb

+SRCREV = "7d9f0b787150d739ab50805008bc7142bc9b7822"
+PV = "0.0+git"
+
+EXTRA_OECMAKE = " -DBUILD_QCBOR_TEST=APP"


what is use of -DBUILD_QCBOR_TEST ? enabling this flag means you are generating a unit test client too along with library ?

If intention is to build test application along with the libs, use a PACKAGECONFIG check and use the same in installing the test bin as well as to add ${PN}-test to PACAKGES. Otherwise this recipe will end up with an empty test package and do_install failures when user wants to drop BUILD_QCBOR_TEST from OECMAKE.

The question of using PACKAGECONFIG is orthogonal. No, the user will not end up with an empty package, OE handles it internally. None of the recipes I know check PACKAGECONFIG when populating PACKAGES.

If intention is to build test application along with the libs, use a PACKAGECONFIG check and use the same in installing the test bin as well as to add ${PN}-test to PACAKGES. Otherwise this recipe will end up with an empty test package and do_install failures when user wants to drop BUILD_QCBOR_TEST from OECMAKE.

Updated. PACKAGECONFIG is a boolean variable, so because we have three options (OFF / LIB / APP), we created a custom variable called QCBOR_TEST_MODE.

recipes-security/qcbor/qcbor_git.bb

vksharma-oss · 2025-10-29T08:14:23Z

recipes-security/qcbor/qcbor_git.bb

+    install -m 0755 ${WORKDIR}/build/test/qcbortest ${D}${bindir}/
+}
+
+PACKAGES += "${PN}-test"


in which package the qcbor.so going ?

Hi @lumag , reviewers, what is the recommended way to include qcbor in the image? The build command kas build meta-qcom/ci/qcs6490-rb3gen2-core-kit.yml compiles the core-image-base target, which is defined in the OE-core layer.

Do you mean the library or the test utils?
For the library you don't need to "include" it. Let it be pulled in by the dependencies. For the test utils, please include it into the test image. You had a nice idea of a security-testing packagegroup. I don't understand, why you dropped it .

I indecated the test utils. How can we include the qcbortest into the .img file and flash it onto the device?

In this pull request, qcbor is not required as a dependency, so the packagegroup-secure package has been removed to enable faster code merging, we will add this package in the Minkipc pull request.

lumag · 2025-10-29T08:53:06Z

recipes-security/qcbor/qcbor_git.bb

+
+do_install:append() {
+    install -d ${D}${bindir}
+    install -m 0755 ${WORKDIR}/build/test/qcbortest ${D}${bindir}/


Please patch the CMakeList to use make install instead. Send the patch upstream

lumag · 2025-10-29T08:53:28Z

recipes-security/qcbor/qcbor_git.bb

+    install -m 0755 ${WORKDIR}/build/test/qcbortest ${D}${bindir}/
+}
+
+PACKAGES += "${PN}-test"


What goes to this package?

Updated.

FILES:${PN}-ptest += " ${bindir}/qcbortest"

lumag · 2025-10-29T09:09:04Z

recipes-security/qcbor/qcbor_git.bb

+
+PACKAGES += "${PN}-test"
+
+FILES:${PN}-bin += " ${bindir}/qcbortest"


This package is not defined.

Updated.
FILES:${PN}-ptest += " ${bindir}/qcbortest"

lumag

One the top of that, please write an appropriate commit subject and message. Please use git log to get some examples.

lumag · 2025-10-29T09:14:39Z

recipes-security/qcbor/qcbor_git.bb

+    git://github.com/laurencelundblade/QCBOR.git;branch=master;protocol=https \
+"
+SRCREV = "7d9f0b787150d739ab50805008bc7142bc9b7822"
+PV = "0.0+git"


This is plain wrong. It is not 0.0. There was a 1.8.3 release. Please use the release instead of packaging random git commit (and lying about the version).

Alright, Have updated the version as 1.5.3.
ref: https://github.com/laurencelundblade/QCBOR/releases
PV = "1.5.3+git"

lumag · 2025-10-29T13:51:12Z

recipes-security/qcbor/qcbor_git.bb

+PV = "0.0+git"
+
+# QCBOR_TEST_MODE：OFF / LIB / APP
+QCBOR_TEST_MODE ?= "APP"


What does this mean? Why is it selectable?

lumag · 2025-10-29T13:51:51Z

recipes-security/qcbor/qcbor_git.bb

+EXTRA_OECMAKE += "-DBUILD_QCBOR_TEST=${QCBOR_TEST_MODE}"
+
+do_install:append() {
+    if [ "${QCBOR_TEST_MODE}" = "APP" ]; then


Ignoring review will bring you nowhere. Fold this into make install.

ricardosalveti · 2025-10-30T01:32:58Z

recipes-security/qcbor/qcbor_git.bb

@@ -0,0 +1,35 @@
+SUMMARY = "Qualcomm QCBOR library"


Why Qualcomm? It is just the upstream project.

ricardosalveti · 2025-10-30T01:34:46Z

There is already a qcbor recipe in meta-oe, can't we just use that one instead (and update to a newer rev if required)?

https://git.openembedded.org/meta-openembedded/tree/meta-oe/recipes-extended/qcbor/qcbor_1.5.3.bb

jiaxli-QC · 2025-10-30T02:34:17Z

There is already a qcbor recipe in meta-oe, can't we just use that one instead (and update to a newer rev if required)?

https://git.openembedded.org/meta-openembedded/tree/meta-oe/recipes-extended/qcbor/qcbor_1.5.3.bb

Yes, the QCbor BB file is already present in the EO layer. However, we do not manage meta-EO. If a new version of QCbor is required in meta-QCOM later on, we will need to update it in meta-EO, but the timing for this is uncertain.

Additionally, when compiling qcbor with OE, only the library is produced, and qcbortest is not generated. This will make debugging qcbor challenging for future products that use the meta-qcom branch.

jiaxli-QC · 2025-10-30T03:08:23Z

Hi @lumag , @ricardosalveti, @vksharma-oss, @vkraleti , many thanks for your review and support.
I plan to use the current QCBOR from the meta-openembedded, and will submit any required changes to meta-OE.

vkraleti · 2025-10-30T03:11:27Z

There is already a qcbor recipe in meta-oe, can't we just use that one instead (and update to a newer rev if required)?
https://git.openembedded.org/meta-openembedded/tree/meta-oe/recipes-extended/qcbor/qcbor_1.5.3.bb

Yes, the QCbor BB file is already present in the EO layer. However, we do not manage meta-EO. If a new version of QCbor is required in meta-QCOM later on, we will need to update it in meta-EO, but the timing for this is uncertain.

Well this is not at all correct and right. Doing a parallel development for open source project can lead to fragmentation, long-term maintenance challenges and may end up in Frankenstein.

We should first prioritize reusing the existing recipe in meta-oe. If enhancements are needed, they should be submitted to upstream meta-oe, get them reviewed and merged. During reviews, if some challenges come up due to misalignment with community then only we should consider adding a bbappend in meta-qcom. Without even attempting to upstream, completely replacing the recipe is not an acceptable solution.

jiaxli-QC · 2025-10-30T03:48:26Z

There is already a qcbor recipe in meta-oe, can't we just use that one instead (and update to a newer rev if required)?

https://git.openembedded.org/meta-openembedded/tree/meta-oe/recipes-extended/qcbor/qcbor_1.5.3.bb

There is already a qcbor recipe in meta-oe, can't we just use that one instead (and update to a newer rev if required)?
https://git.openembedded.org/meta-openembedded/tree/meta-oe/recipes-extended/qcbor/qcbor_1.5.3.bb

Yes, the QCbor BB file is already present in the EO layer. However, we do not manage meta-EO. If a new version of QCbor is required in meta-QCOM later on, we will need to update it in meta-EO, but the timing for this is uncertain.

Well this is not at all correct and right. Doing a parallel development for open source project can lead to fragmentation, long-term maintenance challenges and may end up in Frankenstein.

We should first prioritize reusing the existing recipe in meta-oe. If enhancements are needed, they should be submitted to upstream meta-oe, get them reviewed and merged. During reviews, if some challenges come up due to misalignment with community then only we should consider adding a bbappend in meta-qcom. Without even attempting to upstream, completely replacing the recipe is not an acceptable solution.

Hi @vkraleti @lumag @ricardosalveti
In the meta-qcom, it did not add the dependency on meta-oe. therefore the qcbor cannot be found. How can we use qcbor from https://git.openembedded.org/meta-openembedded/tree/meta-oe/recipes-extended/qcbor/qcbor_1.5.3.bb.

Build command: kas build meta-qcom/ci/qcs6490-rb3gen2-core-kit.yml --target qcomtee
Error log:

2025-10-30 11:32:36 - INFO     - kas 4.7 started
2025-10-30 11:32:36 - INFO     - Using /local/mnt2/workspace/K2L/upstream/meta-qcom as root for repository meta-qcom
2025-10-30 11:32:36 - INFO     - Repository oe-core already contains master as commit
2025-10-30 11:32:36 - INFO     - Repository bitbake already contains master as commit
2025-10-30 11:32:36 - INFO     - Repository meta-yocto already contains master as commit
2025-10-30 11:32:36 - WARNING  - Repo oe-core is dirty - no checkout
2025-10-30 11:32:36 - INFO     - Repository bitbake checked out to 35a421cdcafb3595b9de5489ffdc567825400d26
2025-10-30 11:32:36 - INFO     - Repository meta-yocto checked out to fe65e142d0d9ba0e51ff9175ffa82e902f982a20
2025-10-30 11:32:37 - INFO     - /local/mnt2/workspace/K2L/upstream/build$ /local/mnt2/workspace/K2L/upstream/bitbake/bin/bitbake -c build qcomtee
Loading cache: 100% |                                                                                                                 | ETA:  --:--:--
Loaded 0 entries from dependency cache.
Parsing recipes: 100% |################################################################################################################| Time: 0:00:14
Parsing of 1048 .bb files complete (0 cached, 1048 parsed). 2060 targets, 66 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
ERROR: Nothing PROVIDES 'qcbor' (but /local/mnt2/workspace/K2L/upstream/build/../meta-qcom/recipes-security/qcomtee/qcomtee_git.bb DEPENDS on or otherwise requires it)
ERROR: Required build target 'qcomtee' has no buildable providers.
Missing or unbuildable dependency chain was: ['qcomtee', 'qcbor']

Summary: There were 2 ERROR messages, returning a non-zero exit code.

qcomtee comes from PR1067

vkraleti · 2025-10-30T10:34:40Z

Being a BSP layer, meta-qcom is expected to be built standalone using oe-core without dependency on any other layers like meta-oe. If QTEE has dependencies on recipes from meta-oe, may be it can be added to dynamic-layers section to conditionally compile.

ricardosalveti · 2025-10-30T22:00:50Z

Being a BSP layer, meta-qcom is expected to be built standalone using oe-core without dependency on any other layers like meta-oe. If QTEE has dependencies on recipes from meta-oe, may be it can be added to dynamic-layers section to conditionally compile.

Right, let's use it via dynamic-layers for now until we can validate the workflow and the builds, later on we can either propose for oe-core (harder in this scenario as we should have at least a common dependency there), or bring the recipe as part of meta-qcom but syncing it with the recipe available under meta-oe.

What I really want to avoid is multiple versions and variants of the same recipe in multiple layers, because meta-oe is also available with meta-qcom-distro.

Add a recipe to build qcbor, library to work with security functionality on Qualcomm platforms. The libqcbor, which are only available through meta-oe, is depended by Qcom-teec and MinkIPC. Thus add libqcbor recipe to the corresponding dynamic-layers subdir. Signed-off-by: Jiaxing Li <[email protected]>

jiaxli-QC · 2025-10-31T09:15:54Z

Being a BSP layer, meta-qcom is expected to be built standalone using oe-core without dependency on any other layers like meta-oe. If QTEE has dependencies on recipes from meta-oe, may be it can be added to dynamic-layers section to conditionally compile.

Hi @lumag , @vkraleti , @ricardosalveti
Updated the qcbor compilation. Move it to dynamic-layers/openembedded-layer/recipes-extended/qcbor/qcbor_1.5.3.bb, and make consistent with https://git.openembedded.org/meta-openembedded/tree/meta-oe/recipes-extended/qcbor/qcbor_1.5.3.bb.

jiaxli-QC · 2025-10-31T09:42:19Z

After adding qcbor to the dynamic-layers/openembedded-layer/recipes-extended/qcbor/ directory, I ran into a compilation error: ERROR: Nothing PROVIDES 'qcbor'. Could you provide some suggestions? Many thanks.

Command: $ kas build meta-qcom/ci/qcs6490-rb3gen2-core-kit.yml --target qcbor

2025-10-31 17:39:28 - INFO     - kas 4.7 started
2025-10-31 17:39:28 - INFO     - Using /local/mnt2/workspace/K2L/upstream/meta-qcom as root for repository meta-qcom
2025-10-31 17:39:28 - INFO     - Repository oe-core already contains master as commit
2025-10-31 17:39:28 - INFO     - Repository bitbake already contains master as commit
2025-10-31 17:39:28 - INFO     - Repository meta-yocto already contains master as commit
2025-10-31 17:39:28 - WARNING  - Repo oe-core is dirty - no checkout
2025-10-31 17:39:28 - INFO     - Repository bitbake checked out to 35a421cdcafb3595b9de5489ffdc567825400d26
2025-10-31 17:39:28 - INFO     - Repository meta-yocto checked out to fe65e142d0d9ba0e51ff9175ffa82e902f982a20
2025-10-31 17:39:29 - INFO     - /local/mnt2/workspace/K2L/upstream/build$ /local/mnt2/workspace/K2L/upstream/bitbake/bin/bitbake -c build qcbor
Loading cache: 100% |##################################################################################################################| Time: 0:00:00
Loaded 2060 entries from dependency cache.
Parsing recipes: 100% |################################################################################################################| Time: 0:00:01
Parsing of 1047 .bb files complete (1046 cached, 1 parsed). 2059 targets, 66 skipped, 0 masked, 0 errors.
Removing 1 recipes from the armv8-2a sysroot: 100% |###################################################################################| Time: 0:00:00
Removing 1 recipes from the qcs6490_rb3gen2_core_kit sysroot: 100% |###################################################################| Time: 0:00:00
ERROR: Nothing PROVIDES 'qcbor'

Summary: There was 1 ERROR message, returning a non-zero exit code.

lumag · 2025-11-01T09:44:53Z

I think Ricardo meant to drop QCBOR from this layer and use qcbor dynamically from meta-oe.

jiaxli-QC · 2025-11-03T03:09:20Z

Being a BSP layer, meta-qcom is expected to be built standalone using oe-core without dependency on any other layers like meta-oe. If QTEE has dependencies on recipes from meta-oe, may be it can be added to dynamic-layers section to conditionally compile.

I think Ricardo meant to drop QCBOR from this layer and use qcbor dynamically from meta-oe.

Hi @vkraleti , @vksharma-oss , if I use qcbor dynamically from meta-oe, I am unable to build security components standalone with oe-core without relying on other layers such as meta-oe.

Hi @lumag , if I use qcbor dynamically from meta-oe, could you share the compilation command? The README only mentions the kas build meta-qcom/ci/qcs6490-rb3gen2-core-kit.yml command. Many thanks.

vkraleti · 2025-11-03T04:02:32Z

Being a BSP layer, meta-qcom is expected to be built standalone using oe-core without dependency on any other layers like meta-oe. If QTEE has dependencies on recipes from meta-oe, may be it can be added to dynamic-layers section to conditionally compile.

I think Ricardo meant to drop QCBOR from this layer and use qcbor dynamically from meta-oe.

Hi @vkraleti , @vksharma-oss , if I use qcbor dynamically from meta-oe, I am unable to build security components standalone with oe-core without relying on other layers such as meta-oe.

Hi @lumag , if I use qcbor dynamically from meta-oe, could you share the compilation command? The README only mentions the kas build meta-qcom/ci/qcs6490-rb3gen2-core-kit.yml command. Many thanks.

This is inline with expectations. Security features are typically tied to distributions and are not default offerings in BSP layers.
For example, features like SELinux and kernel module signing are enabled through distribution-level configurations but not by default in BSP.

Similarly for this case, you need to :

Remove the qcbor recipe.
Add the qcomtee and minkipc recipes under dynamic-layers in meta-qcom.
To use these, include the meta-qcom-distro layer while building. This will ensure that dependencies from meta-oe are correctly pulled in.

ricardosalveti · 2025-11-04T00:58:44Z

Hi @lumag , if I use qcbor dynamically from meta-oe, could you share the compilation command? The README only mentions the kas build meta-qcom/ci/qcs6490-rb3gen2-core-kit.yml command. Many thanks.

Meta-oe is added when building with meta-qcom-distro, so you will have to use kas build ci/qcs6490-rb3gen2-core-kit.yml:ci/qcom-distro.yml.

jiaxli-QC · 2025-11-05T06:05:26Z

Hi @lumag , if I use qcbor dynamically from meta-oe, could you share the compilation command? The README only mentions the kas build meta-qcom/ci/qcs6490-rb3gen2-core-kit.yml command. Many thanks.

Meta-oe is added when building with meta-qcom-distro, so you will have to use kas build ci/qcs6490-rb3gen2-core-kit.yml:ci/qcom-distro.yml.

How can we include minkipc and qcomtee in the image for validation purposes?

jiaxli-QC · 2025-11-05T06:50:55Z

This is inline with expectations. Security features are typically tied to distributions and are not default offerings in BSP layers. For example, features like SELinux and kernel module signing are enabled through distribution-level configurations but not by default in BSP.

Similarly for this case, you need to :

Remove the qcbor recipe.

Add the qcomtee and minkipc recipes under dynamic-layers in meta-qcom.
To use these, include the meta-qcom-distro layer while building. This will ensure that dependencies from meta-oe are correctly pulled in.

Hi @vkraleti @lumag , why we should move the minkipc and qcbor in dynamic-layer? This two repo is owned by qcom, can we create the recipes-security in the same directory as recipes-bsp directory.
Because in the future we will need to manage a whole set of security-related components. Furthermore, in Mete-oe, recipes-security exists independently of recipes-bsp and recipes-core.

vkraleti · 2025-11-05T12:12:06Z

This is inline with expectations. Security features are typically tied to distributions and are not default offerings in BSP layers. For example, features like SELinux and kernel module signing are enabled through distribution-level configurations but not by default in BSP.
Similarly for this case, you need to :

Remove the qcbor recipe.

Add the qcomtee and minkipc recipes under dynamic-layers in meta-qcom.
To use these, include the meta-qcom-distro layer while building. This will ensure that dependencies from meta-oe are correctly pulled in.

Hi @vkraleti @lumag , why we should move the minkipc and qcbor in dynamic-layer? This two repo is owned by qcom, can we create the recipes-security in the same directory as recipes-bsp directory. Because in the future we will need to manage a whole set of security-related components. Furthermore, in Mete-oe, recipes-security exists independently of recipes-bsp and recipes-core.

Ask is to drop qcbor recipe from meta-qcom and use the one in meta-oe. Since qcomtee and minkipc recipes are dependent on qcbor, which would be available only when meta-oe is parsed, enabling them by default will cause build issues. Keeping them under "dynamic-layers/openembedded-layer/recipes-security" allows to skip these when meta-oe is not present.

jiaxli-QC · 2025-11-06T07:59:59Z

Meta-oe is added when building with meta-qcom-distro, so you will have to use kas build ci/qcs6490-rb3gen2-core-kit.yml:ci/qcom-distro.yml.

Have we confirmed the build target? I'm wondering why the device isn't booting up after flashing the build with no modifications.

vkraleti · 2025-11-06T08:58:06Z

Meta-oe is added when building with meta-qcom-distro, so you will have to use kas build ci/qcs6490-rb3gen2-core-kit.yml:ci/qcom-distro.yml.

Have we confirmed the build target? I'm wondering why the device isn't booting up after flashing the build with no modifications.

Yes, multimedia-image built with 'qcom-distro' is booting fine on rb3gen2-core-kit. This combination is in CI as well.

jiaxli-QC · 2025-11-10T02:27:58Z

Thank you for your attention and for reviewing the code. I will close this PR and use the qcbor library from meta-oe.

jiaxli-QC requested review from lumag, ndechesne, ricardosalveti, sbanerjee-quic and vkraleti as code owners October 29, 2025 07:22

jiaxli-QC mentioned this pull request Oct 29, 2025

qcom-tee: add a library for security feature support #1167

Merged

vksharma-oss reviewed Oct 29, 2025

View reviewed changes

recipes-security/qcbor/qcbor_git.bb Outdated Show resolved Hide resolved

vksharma-oss reviewed Oct 29, 2025

View reviewed changes

lumag requested changes Oct 29, 2025

View reviewed changes

jiaxli-QC force-pushed the QCBOREnable branch from 4df802f to 2947395 Compare October 29, 2025 13:22

lumag reviewed Oct 29, 2025

View reviewed changes

ricardosalveti reviewed Oct 30, 2025

View reviewed changes

jiaxli-QC force-pushed the QCBOREnable branch from 2947395 to a4ac41c Compare October 30, 2025 01:58

jiaxli-QC force-pushed the QCBOREnable branch from a4ac41c to fbacb11 Compare October 31, 2025 09:10

jiaxli-QC changed the title ~~Add qcbor library for security feature support.~~ qcbor: library to expose Qualcomm Security Package Oct 31, 2025

jiaxli-QC closed this Nov 10, 2025


		PACKAGES += "${PN}-test"

		FILES:${PN}-bin += " ${bindir}/qcbortest"

qcbor: library to expose Qualcomm Security Package #1166

qcbor: library to expose Qualcomm Security Package #1166

Uh oh!

Conversation

jiaxli-QC commented Oct 29, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

jiaxli-QC commented Oct 29, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

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!

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!

lumag 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!

ricardosalveti commented Oct 30, 2025

Uh oh!

jiaxli-QC commented Oct 30, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

jiaxli-QC commented Oct 30, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

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

Uh oh!

Uh oh!

jiaxli-QC commented Oct 30, 2025

Uh oh!

vkraleti commented Oct 30, 2025

Uh oh!

ricardosalveti commented Oct 30, 2025

Uh oh!

jiaxli-QC commented Oct 31, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

jiaxli-QC commented Oct 31, 2025

Uh oh!

lumag commented Nov 1, 2025

Uh oh!

jiaxli-QC commented Oct 29, 2025 •

edited

Loading

jiaxli-QC commented Oct 29, 2025 •

edited

Loading

jiaxli-QC commented Oct 30, 2025 •

edited

Loading

jiaxli-QC commented Oct 30, 2025 •

edited

Loading

vkraleti commented Oct 30, 2025 •

edited

Loading

jiaxli-QC commented Oct 31, 2025 •

edited

Loading

jiaxli-QC commented Nov 5, 2025 •

edited

Loading