ci: indentation #175
Annotations
40 errors and 23 warnings
|
Build-StandaloneWindows-2019.3.15f1
<color=#997A00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/Typical_2D_platformer_example/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
|
|
Build-StandaloneWindows-2019.3.15f1
<color=#997A00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Tests/Misc/TestEntityImportInterface/TestEntityImportInterface/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
|
|
Build-StandaloneWindows-2019.3.15f1
<color=#997A00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/Entities/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
|
|
Build-StandaloneWindows-2019.3.15f1
<color=#997A00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Tests/Misc/OtherTechTests/TestAllFieldsLevels/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
|
|
Build-StandaloneWindows-2019.3.15f1
<color=#997A00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Tests/Misc/OtherTechTests/Test_file_for_API_showing_all_featuresLevels/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
|
|
Build-StandaloneWindows-2019.3.15f1
<color=#997A00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/WorldMap_Free_layout/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
|
|
Build-StandaloneWindows-2019.3.15f1
<color=#997A00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/WorldMap_Free_layout/NuclearBlaze_by_deepnight.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
|
|
Build-StandaloneWindows-2019.3.15f1
<color=#997A00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/Typical_TopDown_example/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
|
|
Build-StandaloneWindows-2019.3.15f1
<color=#997A00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/AutoLayers_5_Advanced/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
|
|
Build-StandaloneWindows-2019.3.15f1
<color=#997A00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Tests/Misc/OtherTechTests/TestAllFields/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
|
|
Build-StandaloneWindows-2019.4.40f1
<color=#FFCC00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/Typical_2D_platformer_example/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
|
|
Build-StandaloneWindows-2019.4.40f1
<color=#FFCC00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Tests/Misc/TestEntityImportInterface/TestEntityImportInterface/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
|
|
Build-StandaloneWindows-2019.4.40f1
<color=#FFCC00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/Entities/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
|
|
Build-StandaloneWindows-2019.4.40f1
<color=#FFCC00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Tests/Misc/OtherTechTests/TestAllFieldsLevels/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
|
|
Build-StandaloneWindows-2019.4.40f1
<color=#FFCC00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Tests/Misc/OtherTechTests/Test_file_for_API_showing_all_featuresLevels/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
|
|
Build-StandaloneWindows-2019.4.40f1
<color=#FFCC00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/WorldMap_Free_layout/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
|
|
Build-StandaloneWindows-2019.4.40f1
<color=#FFCC00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/WorldMap_Free_layout/NuclearBlaze_by_deepnight.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
|
|
Build-StandaloneWindows-2019.4.40f1
<color=#FFCC00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/Typical_TopDown_example/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
|
|
Build-StandaloneWindows-2019.4.40f1
<color=#FFCC00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/AutoLayers_5_Advanced/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
|
|
Build-StandaloneWindows-2019.4.40f1
<color=#FFCC00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Tests/Misc/OtherTechTests/TestAllFields/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
|
|
Build-WebGL-2019.3.15f1
<color=#997A00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/Typical_2D_platformer_example/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
|
|
Build-WebGL-2019.3.15f1
<color=#997A00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Tests/Misc/TestEntityImportInterface/TestEntityImportInterface/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
|
|
Build-WebGL-2019.3.15f1
<color=#997A00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/Entities/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
|
|
Build-WebGL-2019.3.15f1
<color=#997A00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Tests/Misc/OtherTechTests/TestAllFieldsLevels/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
|
|
Build-WebGL-2019.3.15f1
<color=#997A00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Tests/Misc/OtherTechTests/Test_file_for_API_showing_all_featuresLevels/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
|
|
Build-WebGL-2019.3.15f1
<color=#997A00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/WorldMap_Free_layout/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
|
|
Build-WebGL-2019.3.15f1
<color=#997A00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/WorldMap_Free_layout/NuclearBlaze_by_deepnight.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
|
|
Build-WebGL-2019.3.15f1
<color=#997A00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/Typical_TopDown_example/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
|
|
Build-WebGL-2019.3.15f1
<color=#997A00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/AutoLayers_5_Advanced/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
|
|
Build-WebGL-2019.3.15f1
<color=#997A00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Tests/Misc/OtherTechTests/TestAllFields/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
|
|
Build-WebGL-6000.0.23f1
<color=#FFCC00>LDtk:</color> Tried to build the internal icons "Internal_Icons", But the internal icons was not assigned in Unity's project settings. You can add the texture by going to Edit > Project Settings > LDtk To Unity
|
|
Build-WebGL-6000.0.23f1
<color=#FFCC00>LDtk:</color> Tried loading an aseprite file "NuclearBlaze_by_deepnight.aseprite", but the aseprite importer is not installed or below version 1.0.0. Add: com.unity.2d.aseprite. Requires Unity 2021.3.15 or newer
|
|
Build-WebGL-6000.0.23f1
AssetImporter is referencing an asset from the previous import. This should not happen.
|
|
Build-WebGL-6000.0.23f1
<color=#FFCC00>LDtk:</color> Tried to build the internal icons "Internal_Icons", But the internal icons was not assigned in Unity's project settings. You can add the texture by going to Edit > Project Settings > LDtk To Unity
|
|
Build-WebGL-6000.0.23f1
AssetImporter is referencing an asset from the previous import. This should not happen.
|
|
Build-WebGL-6000.0.23f1
<color=#FFCC00>LDtk:</color> Tried to build the internal icons "Internal_Icons", But the internal icons was not assigned in Unity's project settings. You can add the texture by going to Edit > Project Settings > LDtk To Unity
|
|
Build-WebGL-6000.0.23f1
AssetImporter is referencing an asset from the previous import. This should not happen.
|
|
Build-WebGL-6000.0.23f1
<color=#FFCC00>LDtk:</color> Tried to build the internal icons "Internal_Icons", But the internal icons was not assigned in Unity's project settings. You can add the texture by going to Edit > Project Settings > LDtk To Unity
|
|
Build-WebGL-6000.0.23f1
AssetImporter is referencing an asset from the previous import. This should not happen.
|
|
Build-WebGL-6000.0.23f1
<color=#FFCC00>LDtk:</color> Tried to build the internal icons "Internal_Icons", But the internal icons was not assigned in Unity's project settings. You can add the texture by going to Edit > Project Settings > LDtk To Unity
|
|
Build-StandaloneWindows-2020.3.48f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4.2.3, actions/checkout@v4.1.4, actions/upload-artifact@v4.3.3, game-ci/unity-builder@v4.3.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build-StandaloneWindows-2020.3.48f1
'AudioListener' is not supported because the module Audio is disabled in the build.
|
|
Build-StandaloneWindows-2022.3.43f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4.2.3, actions/checkout@v4.1.4, actions/upload-artifact@v4.3.3, game-ci/unity-builder@v4.3.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build-StandaloneWindows-2022.3.43f1
'AudioListener' is not supported because the module Audio is disabled in the build.
|
|
Build-StandaloneWindows-2022.3.43f1
GfxDevice renderer is null. Unity cannot update the Ambient Probe and Reflection Probes that the SkyManager generates. Run the Editor without the -nographics argument or generate lighting for your scene.
|
|
Build-StandaloneWindows-2019.3.15f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4.2.3, actions/checkout@v4.1.4, actions/upload-artifact@v4.3.3, game-ci/unity-builder@v4.3.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build-StandaloneWindows-2019.4.40f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4.2.3, actions/checkout@v4.1.4, actions/upload-artifact@v4.3.3, game-ci/unity-builder@v4.3.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build-StandaloneWindows-2019.4.40f1
'AudioListener' is not supported because the module Audio is disabled in the build.
|
|
Build-StandaloneWindows-2021.3.45f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4.2.3, actions/checkout@v4.1.4, actions/upload-artifact@v4.3.3, game-ci/unity-builder@v4.3.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build-StandaloneWindows-2021.3.45f1
'AudioListener' is not supported because the module Audio is disabled in the build.
|
|
Build-StandaloneWindows-2021.3.45f1
GfxDevice renderer is null. Unity cannot update the Ambient Probe and Reflection Probes that the SkyManager generates. Run the Editor without the -nographics argument or generate lighting for your scene.
|
|
Build-StandaloneWindows-2021.3.45f1
Activation failed, attempting retry #2
|
|
Build-StandaloneWindows-2021.3.45f1
Activation failed, attempting retry #1
|
|
Build-StandaloneWindows-6000.0.64f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4.2.3, actions/checkout@v4.1.4, actions/upload-artifact@v4.3.3, game-ci/unity-builder@v4.3.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build-StandaloneWindows-6000.0.64f1
'AudioListener' is not supported because the module Audio is disabled in the build.
|
|
Build-StandaloneWindows-6000.0.64f1
Activation failed, attempting retry #2
|
|
Build-StandaloneWindows-6000.0.64f1
Activation failed, attempting retry #1
|
|
Build-StandaloneWindows-6000.3.2f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4.2.3, actions/checkout@v4.1.4, actions/upload-artifact@v4.3.3, game-ci/unity-builder@v4.3.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build-StandaloneWindows-6000.3.2f1
'AudioListener' is not supported because the module Audio is disabled in the build.
|
|
Build-WebGL-2019.3.15f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4.2.3, actions/checkout@v4.1.4, actions/upload-artifact@v4.3.3, game-ci/unity-builder@v4.3.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build-WebGL-6000.0.23f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4.2.3, actions/checkout@v4.1.4, actions/upload-artifact@v4.3.3, game-ci/unity-builder@v4.3.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build-WebGL-6000.0.23f1
'AudioListener' is not supported because the module Audio is disabled in the build.
|
|
Build-WebGL-6000.0.23f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
Build-StandaloneWindows-2019.3.15f1
Expired
|
18.2 MB |
sha256:d868a3708f067c4813ff93c93a8725f25eb41ea2fc5f3da780bfef602aa719bd
|
|
|
Build-StandaloneWindows-2019.4.40f1
Expired
|
18.3 MB |
sha256:4f9572679b314af5aa6f9b352de32db04071cce7647e450b7f53cf83a8bfe70e
|
|
|
Build-StandaloneWindows-2020.3.48f1
Expired
|
20 MB |
sha256:b9f561a4781c175e1becb650ba6c93cee4d10af120e819d56ff85490b1ab72fb
|
|
|
Build-StandaloneWindows-2021.3.45f1
Expired
|
22.3 MB |
sha256:ae73a824f34c8750cbffc4cd6bc0c06f5efa8255dc0798609b993d345043c96c
|
|
|
Build-StandaloneWindows-2022.3.43f1
Expired
|
22.2 MB |
sha256:c90caa740e581ae85efd8a0051f6f076c72b56eb3a875f6bbc8e882485d99bda
|
|
|
Build-StandaloneWindows-6000.0.64f1
Expired
|
25.9 MB |
sha256:0d66327f225d4935ff2c36e47c6405287945969fb7d8871f2aaaac5f08abd32d
|
|
|
Build-StandaloneWindows-6000.3.2f1
Expired
|
27.4 MB |
sha256:c0e7ecadc85a212940f6ddbce3b3b8ed3a95cc6e49819437a594b526f7eea30c
|
|
|
Build-WebGL-2019.3.15f1
Expired
|
3.62 MB |
sha256:2d93a6e7d0a60b8899df9a9d072f4504bc0f43565904376a9fdd93c33cd33b8f
|
|
|
Build-WebGL-6000.0.23f1
Expired
|
3.87 MB |
sha256:a605f3095b416c89d0ed65ee1e35ed89745e03705cfe4bf0f963eff8c100b224
|
|