[vcpkg_cmake_config_test] Add function to test the exported cmake configurations #15173

JackBoosY · 2020-12-17T02:24:28Z

This function will replace vcpkg_test_cmake, have the following features:

Usage:

vcpkg_cmake_config_test(
    USAGE        Curl CONFIG
    TARGET_NAMES CURL::libcurl
    HEADERS      curl/curl.h
    FUNCTIONS    curl_global_init
)

To test the header file path and function symbols, we can create vcpkg-test.cpp/vcpkg-test.c in PORT_DIR and add test code to it. Example:
vcpkg-test.cpp:

#include <stdio.h>
#include <curl/curl.h>

int main()
{
    return curl_global_init();
}

For further testing of cmake export variables, we can also create vcpkg-test.cmake in PORT_DIR and write test cmake code.

For exmaple:
Add vcpkg_cmake_config_test() to ports/cjson/portfile.cmake, install cjson with --debug, the expected error will shows (known bug):

Make Error at installed/x64-windows/share/vcpkg-cmake-config/vcpkg_cmake_config_test.cmake:167 (message):
    Test cmake configuration failed, please check cmake configuration file!
    Error code: 1
    See logs for more information:
        G:/15173/vcpkg/buildtrees/cjson/config-test-cmake-debug-out.log
        G:/15173/vcpkg/buildtrees/cjson/config-test-cmake-debug-err.log

log details:

CMake Error at G:/15173/vcpkg/packages/cjson_x86-windows/share/cjson/cjson.cmake:68 (message):
  The imported target "cjson" references the file

     "/debug/lib/cjson.lib"

  but this file does not exist.  Possible reasons include:

  * The file was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and contained

     "G:/15173/vcpkg/packages/cjson_x86-windows/share/cjson/cjson.cmake"

  but not all the files it references.

Call Stack (most recent call first):
  G:/15173/vcpkg/packages/cjson_x86-windows/share/cjson/cJSONConfig.cmake:14 (include)
  G:/15173/vcpkg/scripts/buildsystems/vcpkg.cmake:788 (_find_package)
  CMakeLists.txt:4 (find_package)

…figurations

JackBoosY · 2020-12-17T03:06:18Z

@BillyONeal @strega-nil Any suggestions are good.

strega-nil · 2020-12-17T17:58:12Z

I do like this feature a lot. I'm not sure what suggestions you're looking for?

JackBoosY · 2020-12-18T02:25:49Z

@strega-nil I think this type of testing should only be carried out in two situations:

editable mode
CI mode

Most post checks should follow this policy, because for users, they have been tested in the PRs before being merged into the master, so there is no need to waste more time.

JackBoosY · 2021-02-07T02:36:21Z

Close this PR temporary.

JackBoosY · 2021-05-25T07:38:22Z

/azp run

azure-pipelines · 2021-05-25T07:38:26Z

Pull request contains merge conflicts.

…/JackBoosY/vcpkg into dev/jack/vcpkg_test_cmake_config

dg0yt · 2021-05-25T08:12:45Z

Will this be move to a new port, or merged into an existing vcpkg-cmake... port? I suppose it would also shorten CI runs to not touch ports.cmake.

JackBoosY · 2021-05-28T09:23:35Z

@strega-nil I think all the ports whose called vcpkg_fixup_cmake_targets or vcpkg_cmake_config_fixup should automaticly call this function. What do you think about?

dg0yt · 2021-05-28T11:31:38Z

all the ports whose called vcpkg_fixup_cmake_targets or vcpkg_cmake_config_fixup should automaticly call this function.

Can you perhaps test with port geos? I added a usage file recently because the default instructions were somewhat misleading. And now I wonder if automated testing might fail to identify the canonical use in a similar way.

JackBoosY · 2021-05-31T07:46:04Z

@dg0yt No errors.
This function will only automatically detect the generated cmake configuration file, and cannot identify the content in the usage and test it.

JackBoosY · 2021-10-26T00:26:43Z

@dg0yt Please note we should test the following contents:

cmake targets.
cmake macros provided by *-[Cc]onfig.cmake.
include headers (test the path).
function symbols.

And I noticed you've done only part of them.

For more, we also should allow the maintainer to provide a custom test code to test the binary.

dg0yt · 2021-10-26T04:32:12Z

@dg0yt Please note we should test the following contents:

cmake targets.

cmake macros provided by *-[Cc]onfig.cmake.

include headers (test the path).

function symbols.

And I noticed you've done only part of them.

Yes, because I had a different focus (older versions of cmake). So apart from the pure find_package it is more a complementary effort than an overlap.

But given your function's arguments, why not cover find modules? Do you need a proof-of-concept?

For more, we also should allow the maintainer to provide a custom test code to test the binary.

I agree.

JackBoosY · 2021-10-26T08:18:03Z

But given your function's arguments, why not cover find modules? Do you need a proof-of-concept?

Because some ports do not actively provide the find modules and use cmake one, we must add additional parameters to achieve this.
This PR is intended to check all the generated files, especially the generated cmake configuration files.

ports/vcpkg-cmake-config/vcpkg_cmake_config_test.cmake

dg0yt · 2021-10-27T07:19:06Z

Because some ports do not actively provide the find modules and use cmake one, we must add additional parameters to achieve this.

Many ports provide wrappers which need to be tested and which can be discovered.
You cannot completely rely on auto-discovery anyway (mostly due to handling of upper vs. lower case).
The existing parameters are almost okay.
- What doesn't match is CONFIG_NAME. There could be an MODULE_NAME instead.
- In absence of a TARGET_NAME, the build should use the <MODULE_NAME>_... variables.

There could also be a unified signature like this:

vcpkg_cmake_package_test(
    USAGE Curl CONFIG
    TARGET_NAMES CURL::libcurl
    HEADERS     curl/curl.h
    FUNCTIONS   curl_global_init
)
vcpkg_cmake_package_test(
    USAGE Curl
    TARGET_NAMES CURL::libcurl
    HEADERS     curl/curl.h
    FUNCTIONS   curl_global_init
)

where USAGE is passed to the find_package call literally.

dg0yt

I feel like this needs a clearer separation of package name and folder name.

dg0yt · 2021-10-27T07:23:48Z

ports/vcpkg-cmake-config/vcpkg_cmake_config_test.cmake

+    endif()
+
+    if (arg_CONFIG_NAME)
+        set(target_folder "${arg_CONFIG_NAME}")


A config for Pkg can be found in different target folders:

Pkg (as Pkg/PkgConfig.cmake)

pkg (as pkg/pkg-config.cmake)

But a config for Pkg is different from a config for pkg. (Side effects: setting Pkg_FOUND, Pkg_LIBRARIES etc.)

For CONFIG mode, we should use the target name, now I think it's correct.

For MODULE mode, we need to use the Find module provided cmake macros, we still need to extend this function to add additional option TARGET_LIBRARIES, TARGET_INCLUDES, TARGET_DEFINITIONS and TARGET_OPTIONS. Also, we need to consider whether these options are just "extend" cmake test code or "replace" cmake test code. That's why I set up the ability to use the extended cmake test code.

ports/vcpkg-cmake-config/vcpkg_cmake_config_test.cmake

github-actions

This is a new experimental fast check for PR issues. Please let us know if this bot is helpful!

After committing all other changes, the version database must be updated

git add -u && git commit
git checkout 078f3e51efd5ea6072d0ba28d11baa946519a2ce -- versions
./vcpkg x-add-version --all

Diff

diff --git a/versions/c-/curl.json b/versions/c-/curl.json
index 5ba5d000..335aaebe 100644
--- a/versions/c-/curl.json
+++ b/versions/c-/curl.json
@@ -1,7 +1,7 @@
 {
   "versions": [
     {
-      "git-tree": "b43d25f9b63c3be9d9b67ef81cb4cfc18c75a848",
+      "git-tree": "a6939590c8a4af6b772b6a0a40bf107451e9475e",
       "version": "7.79.1",
       "port-version": 1
     },
diff --git a/versions/v-/vcpkg-cmake-config.json b/versions/v-/vcpkg-cmake-config.json
index 801f78c0..3ae01541 100644
--- a/versions/v-/vcpkg-cmake-config.json
+++ b/versions/v-/vcpkg-cmake-config.json
@@ -1,7 +1,7 @@
 {
   "versions": [
     {
-      "git-tree": "4d873c8d4d63892838c407e1b7eb1c297377a8b6",
+      "git-tree": "da185d09123093850dd27c8775df33c20df88ce3",
       "version-date": "2021-10-19",
       "port-version": 0
     },

JackBoosY · 2021-10-27T09:03:59Z

ports/vcpkg-cmake-config/vcpkg_cmake_config_test.cmake

+    set(extern_header_checks "")
+    set(extern_symbol_checks_base "")
+    set(extern_symbol_check_symbol "")


These macros are strings, so we shouldn't use vcpkg_list.

JackBoosY · 2021-10-28T02:01:51Z

Ping @dg0yt for review again.

dg0yt

Now here is a lot more.
Disclaimer: I'm not a native English speaker.

ports/vcpkg-cmake-config/vcpkg_cmake_config_test.cmake

dg0yt · 2021-10-28T03:31:10Z

ports/vcpkg-cmake-config/vcpkg_cmake_config_test.cmake

+    list(LENGTH target_folders folder_size)
+
+    if (target_size EQUAL 0 OR folder_size EQUAL 0)
+        message(WARANING "Found the following cmake configuration file but not found the target.")


WARNING
... but did not find the target.

Note that the warning text doesn't match the case of folder_size == 0.

I keep wondering if it would be better to start with a glob for *-config.cmake *Config.cmake (otherwise: error "No config file found"), generate the list of package names and directories from this config file list, and only then start collecting targets from these directories (otherwise: error "No targets found for config Xyz").

This is for installing other cmake files instead of cmake configuration entry files.
Please note that the *Cconfig.cmake file does not provide add_library in most cases.

dg0yt · 2021-10-28T03:48:07Z

ports/vcpkg-cmake-config/vcpkg_cmake_config_test.cmake

+    endif()
+
+    if (NOT folder_size EQUAL 1 AND NOT arg_USAGE)
+        message(FATAL_ERROR "More than one folder contains cmake configuration files, please set \"TARGET_NAMES\" to select the certain target name")


Is there an example case? I don't think this can be assumed to be an error. There can be folder PROJ4 providing PROJ4::PROJ4 (legacy), and there can be folder PROJ, providing PROJ::PROJ (modern).
But probably it is a limitation of the current implementation which would be resolved by splitting identifying folders from processing folders, instead of doing this simultaneously.

In some ports, the upstream provides many targets, and these targets independently generate the corresponding targets.cmake file. These files may be installed in different folders (named after the target name).
We should avoid this situation.

Your are talking about deep trees within a single package. Here you statement makes sense.
But my focus was separate cmake packages.
This cannot be improved while iterating simultaneously over multiple cmake packages. In my previous comment, I should have used the words "splitting identifying package names from ...". Or better write pseudo code:

Collect package names by non-recursive looking for */*Config.cmake */*-config.cmake.
(This step could be skipped in case of arg_USAGE.)

For each package name, collect targets from the cmake files (maybe recursively).
(This step could be skipped in case of arg_TARGET_NAMES, assuming a single package name.)

ports/vcpkg-cmake-config/vcpkg_cmake_config_test.cmake

dg0yt · 2021-10-28T04:09:04Z

ports/vcpkg-cmake-config/vcpkg_cmake_config_test.cmake

+endmacro()
+
+function(vcpkg_cmake_config_test)
+    if (NOT _VCPKG_EDITABLE)


I'm not sure if this is the right indicator for controlling the test.

I expect this test to run in edit mode or CI mode to reduce user build time.

I understand the argument about build time, But edit mode is somewhat exceptional in my personal use, and it is propably inactive during CI.

I hope the ci command will pass a special VCPKG_ variable to cmake to enable this function.
But for now I think it can be enabled in edit mode first.

ports/vcpkg-cmake-config/vcpkg_cmake_config_test.cmake

github-actions

This is a new experimental fast check for PR issues. Please let us know if this bot is helpful!

After committing all other changes, the version database must be updated

git add -u && git commit
git checkout 078f3e51efd5ea6072d0ba28d11baa946519a2ce -- versions
./vcpkg x-add-version --all

Diff

diff --git a/versions/c-/curl.json b/versions/c-/curl.json
index 5ba5d000..335aaebe 100644
--- a/versions/c-/curl.json
+++ b/versions/c-/curl.json
@@ -1,7 +1,7 @@
 {
   "versions": [
     {
-      "git-tree": "b43d25f9b63c3be9d9b67ef81cb4cfc18c75a848",
+      "git-tree": "a6939590c8a4af6b772b6a0a40bf107451e9475e",
       "version": "7.79.1",
       "port-version": 1
     },
diff --git a/versions/v-/vcpkg-cmake-config.json b/versions/v-/vcpkg-cmake-config.json
index 801f78c0..cd4fcce4 100644
--- a/versions/v-/vcpkg-cmake-config.json
+++ b/versions/v-/vcpkg-cmake-config.json
@@ -1,7 +1,7 @@
 {
   "versions": [
     {
-      "git-tree": "4d873c8d4d63892838c407e1b7eb1c297377a8b6",
+      "git-tree": "b53769d6f8e96ae25f0f8d619cf97e08ad270120",
       "version-date": "2021-10-19",
       "port-version": 0
     },

ports/vcpkg-cmake-config/vcpkg_cmake_config_test.cmake

dg0yt · 2021-10-28T11:59:25Z

ports/vcpkg-cmake-config/vcpkg_cmake_config_test.cmake

+        return()
+    endif()
+
+    if (NOT folder_size EQUAL 1 AND NOT arg_USAGE)


ATM this function is called only for NOT arg_USAGE.

You might actually make use of arg_USAGE, by picking out the package name Pkg (first item) and using that to limit the globbing to Pkg/PkgConfig.cmake and pkg/pkg-config.cmake. But this is not urgent as for now arg_USAGE implies arg_TARGET_NAMES.

Can you please describe more?
As I know, some ports have generated pkg[Cc]onfig.cmake files corresponding to different targets, so here we should prompt the maintainer for the usage.

dg0yt · 2021-10-28T12:10:38Z

ports/vcpkg-cmake-config/vcpkg_cmake_config_test.cmake

+    endif()
+
+    if (NOT folder_size EQUAL 1 AND NOT arg_USAGE)
+        message(FATAL_ERROR "More than one folder contains cmake configuration files, please set \"TARGET_NAMES\" to select the certain target name")


Your are talking about deep trees within a single package. Here you statement makes sense.
But my focus was separate cmake packages.
This cannot be improved while iterating simultaneously over multiple cmake packages. In my previous comment, I should have used the words "splitting identifying package names from ...". Or better write pseudo code:

Collect package names by non-recursive looking for */*Config.cmake */*-config.cmake.
(This step could be skipped in case of arg_USAGE.)

For each package name, collect targets from the cmake files (maybe recursively).
(This step could be skipped in case of arg_TARGET_NAMES, assuming a single package name.)

dg0yt · 2021-10-28T12:14:17Z

ports/vcpkg-cmake-config/vcpkg_cmake_config_test.cmake

+endmacro()
+
+function(vcpkg_cmake_config_test)
+    if (NOT _VCPKG_EDITABLE)


I understand the argument about build time, But edit mode is somewhat exceptional in my personal use, and it is propably inactive during CI.

dg0yt · 2021-10-28T12:27:15Z

ports/vcpkg-cmake-config/vcpkg_cmake_config_test.cmake

+        endforeach()
+    endif()
+
+    foreach(target_name IN LISTS target_names)


That's the loop which is actually limiting us to the single cmake package case.

Ah yes, but it doesn't matter, this function will only be enabled in the official triplet which doesn't include the single configuration triplet yet.

…jack/vcpkg_test_cmake_config

github-actions

This is a new experimental fast check for PR issues. Please let us know if this bot is helpful!

After committing all other changes, the version database must be updated

git add -u && git commit
git checkout a91bc0c2d4af9a9e521cda0e39a1f108a8d17def -- versions
./vcpkg x-add-version --all

Diff

diff --git a/versions/baseline.json b/versions/baseline.json
index 24c52c1f..f00e2849 100644
--- a/versions/baseline.json
+++ b/versions/baseline.json
@@ -1702,7 +1702,7 @@
     },
     "curl": {
       "baseline": "7.80.0",
-      "port-version": 0
+      "port-version": 1
     },
     "curlpp": {
       "baseline": "2018-06-15",
@@ -7105,7 +7105,7 @@
       "port-version": 0
     },
     "vcpkg-cmake-config": {
-      "baseline": "2021-12-01",
+      "baseline": "2021-12-17",
       "port-version": 0
     },
     "vcpkg-gfortran": {
diff --git a/versions/c-/curl.json b/versions/c-/curl.json
index a73767ce..97a8f51b 100644
--- a/versions/c-/curl.json
+++ b/versions/c-/curl.json
@@ -1,5 +1,10 @@
 {
   "versions": [
+    {
+      "git-tree": "847baeeb1e54716212cb71f724be3c0df71a4f43",
+      "version": "7.80.0",
+      "port-version": 1
+    },
     {
       "git-tree": "8e13da05c975cb6f5bed6cf3b8054a817a00b45d",
       "version": "7.80.0",
diff --git a/versions/v-/vcpkg-cmake-config.json b/versions/v-/vcpkg-cmake-config.json
index dda29410..de6de278 100644
--- a/versions/v-/vcpkg-cmake-config.json
+++ b/versions/v-/vcpkg-cmake-config.json
@@ -1,5 +1,10 @@
 {
   "versions": [
+    {
+      "git-tree": "ca4fd79144060953c1a7ec689ccf3feb18b98650",
+      "version-date": "2021-12-17",
+      "port-version": 0
+    },
     {
       "git-tree": "51df1bbddb22782b9e7f23f9b3588674184e991a",
       "version-date": "2021-12-01",

github-actions

This is a new experimental fast check for PR issues. Please let us know if this bot is helpful!

After committing all other changes, the version database must be updated

git add -u && git commit
git checkout a91bc0c2d4af9a9e521cda0e39a1f108a8d17def -- versions
./vcpkg x-add-version --all

Diff

diff --git a/versions/baseline.json b/versions/baseline.json
index 68bb36ba..02bd3657 100644
--- a/versions/baseline.json
+++ b/versions/baseline.json
@@ -1702,7 +1702,7 @@
     },
     "curl": {
       "baseline": "7.80.0",
-      "port-version": 0
+      "port-version": 1
     },
     "curlpp": {
       "baseline": "2018-06-15",
@@ -7109,7 +7109,7 @@
       "port-version": 0
     },
     "vcpkg-cmake-config": {
-      "baseline": "2021-12-01",
+      "baseline": "2021-12-17",
       "port-version": 0
     },
     "vcpkg-gfortran": {
diff --git a/versions/c-/curl.json b/versions/c-/curl.json
index a73767ce..97a8f51b 100644
--- a/versions/c-/curl.json
+++ b/versions/c-/curl.json
@@ -1,5 +1,10 @@
 {
   "versions": [
+    {
+      "git-tree": "847baeeb1e54716212cb71f724be3c0df71a4f43",
+      "version": "7.80.0",
+      "port-version": 1
+    },
     {
       "git-tree": "8e13da05c975cb6f5bed6cf3b8054a817a00b45d",
       "version": "7.80.0",
diff --git a/versions/v-/vcpkg-cmake-config.json b/versions/v-/vcpkg-cmake-config.json
index dda29410..a9a78510 100644
--- a/versions/v-/vcpkg-cmake-config.json
+++ b/versions/v-/vcpkg-cmake-config.json
@@ -1,5 +1,10 @@
 {
   "versions": [
+    {
+      "git-tree": "d6b915f72cc87630c9bd0476314942ef17b2ba44",
+      "version-date": "2021-12-17",
+      "port-version": 0
+    },
     {
       "git-tree": "51df1bbddb22782b9e7f23f9b3588674184e991a",
       "version-date": "2021-12-01",

dg0yt · 2021-12-24T10:03:17Z

I experiment with a modified variant of this PR which also covers testing CMake Find modules (eventually replacing the cmake-user test port). I think I can turn this into a proper PR in the next days.

With regard to control over enabling certain tests, I would suggest to use a directory like share/vcpkg-tests/enabled/. Tests might be enabled by manual install commands on the maintainer's workstation (interactive), or by directly copying files from vcpkg repo to the installed tree on CI systems (non-interactively). This avoids build time impact on normal users (e.g. for testing with CMake 3.4), and it also decouples user artifacts from rebuilds due to test improvements. And no change to the tool binary is needed.

JackBoosY · 2022-01-30T03:34:20Z

In favor of #22258.

[vcpkg_test_cmake_config] Add function to test the exported cmake con…

3b9ff10

…figurations

JackBoosY added category:vcpkg-feature The issue is a new capability of the tool that doesn’t already exist and we haven’t committed info:internal This PR or Issue was filed by the vcpkg team. labels Dec 17, 2020

JackBoosY assigned PhoebeHui Dec 17, 2020

Add code to test

0c53ee3

BillyONeal added the requires:discussion label Dec 17, 2020

add doc, add release check.

c25da95

JackBoosY mentioned this pull request Dec 21, 2020

[vcpkg_test_cmake] Reconstruction function #13802

Closed

JackBoosY mentioned this pull request Jan 8, 2021

vcpkg federation stabilization #15381

Closed

JackBoosY closed this Feb 7, 2021

JackBoosY reopened this May 25, 2021

JackBoosY and others added 3 commits May 25, 2021 15:39

Merge branch 'master' into dev/jack/vcpkg_test_cmake_config

f6cd789

format doc

4edfa9a

Merge branch 'dev/jack/vcpkg_test_cmake_config' of https://github.com…

ec96372

…/JackBoosY/vcpkg into dev/jack/vcpkg_test_cmake_config

JackBoosY added 5 commits May 26, 2021 20:10

convert to port vcpkg-cmake-test

d645252

add dependency

28db599

include

5e7d1fc

install

a06d58a

fix TARGET_NAME

d2e91f6

dg0yt mentioned this pull request May 31, 2021

[jemalloc] Generate cmake target files. #10243

Open

JackBoosY requested a review from strega-nil-ms October 27, 2021 02:46

JackBoosY commented Oct 27, 2021

View reviewed changes

ports/vcpkg-cmake-config/vcpkg_cmake_config_test.cmake Outdated Show resolved Hide resolved

JackBoosY added 2 commits October 27, 2021 00:00

Rename options name, fix bug

4a23b84

version

9d4885f

github-actions bot approved these changes Oct 27, 2021

View reviewed changes

dg0yt reviewed Oct 27, 2021

View reviewed changes

Apply suggestions

4ce2fda

github-actions bot requested changes Oct 27, 2021

View reviewed changes

JackBoosY commented Oct 27, 2021

View reviewed changes

dg0yt reviewed Oct 28, 2021

View reviewed changes

Apply suggestions

eab5fed

github-actions bot requested changes Oct 28, 2021

View reviewed changes

dg0yt reviewed Oct 28, 2021

View reviewed changes

PhoebeHui marked this pull request as draft December 2, 2021 06:14

Merge branch 'master' of https://github.com/microsoft/vcpkg into dev/…

7f3283a

…jack/vcpkg_test_cmake_config

github-actions bot requested changes Dec 17, 2021

View reviewed changes

Apply suggestions.

0c9d2c9

JackBoosY marked this pull request as ready for review December 17, 2021 08:48

github-actions bot requested changes Dec 17, 2021

View reviewed changes

dg0yt mentioned this pull request Dec 30, 2021

[vcpkg-cmake-validate,vcpkg-maintainer-options] New ports #22258

Closed

PhoebeHui marked this pull request as draft January 30, 2022 02:10

JackBoosY closed this Jan 30, 2022

PhoebeHui removed the requires:vcpkg-team-review This PR or issue requires someone on the vcpkg team to take a further look. label Jan 30, 2022

[vcpkg_cmake_config_test] Add function to test the exported cmake configurations #15173

[vcpkg_cmake_config_test] Add function to test the exported cmake configurations #15173

Conversation

JackBoosY commented Dec 17, 2020 • edited Loading

JackBoosY commented Dec 17, 2020

strega-nil commented Dec 17, 2020

JackBoosY commented Dec 18, 2020

JackBoosY commented Feb 7, 2021

JackBoosY commented May 25, 2021

azure-pipelines bot commented May 25, 2021

dg0yt commented May 25, 2021

JackBoosY commented May 28, 2021

dg0yt commented May 28, 2021

JackBoosY commented May 31, 2021

JackBoosY commented Oct 26, 2021 • edited Loading

dg0yt commented Oct 26, 2021

JackBoosY commented Oct 26, 2021

dg0yt commented Oct 27, 2021

dg0yt left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

JackBoosY Oct 27, 2021 • edited Loading

Choose a reason for hiding this comment

github-actions bot left a comment

Choose a reason for hiding this comment

JackBoosY Oct 27, 2021 • edited Loading

Choose a reason for hiding this comment

JackBoosY commented Oct 28, 2021

dg0yt left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

github-actions bot left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

github-actions bot left a comment

Choose a reason for hiding this comment

github-actions bot left a comment

Choose a reason for hiding this comment

dg0yt commented Dec 24, 2021

JackBoosY commented Jan 30, 2022

JackBoosY commented Dec 17, 2020 •

edited

Loading

JackBoosY commented Oct 26, 2021 •

edited

Loading

JackBoosY Oct 27, 2021 •

edited

Loading

JackBoosY Oct 27, 2021 •

edited

Loading