build from pre any specific land changes associated with Aus PFTs #148

JhanSrbinovsky · 2025-10-07T00:09:35Z

First build PR#148-1 - build from pre any specific land changes associated with Aus PFTs PR#129

comes from UM7:main branch

PR148-2 builds from the head of the main branch as at Oct 7. (a29dc8b934a20872a400a3730d36fb52cff8b37d)

Both versions use:

payu clone [email protected]:ACCESS-NRI/access-esm1.6-configs.git -B test-PIspinup-Sept-C

runs on gadi:

PR#148-1 -> GPP-148-1 at /g/data/p66/jxs599/ESM16/PAYU/Feat/feat-148-GPP-6602d
PR#148-2 -> GPP-148-2 at /g/data/p66/jxs599/ESM16/PAYU/Feat/feat-148-GPP-a29dc

Sept spin up configs used in both ARE seemingly ok EXCEPT the earlier 148-1 does not have the code changes neccessary to deal with the ocean albedo parameter in the namelist, input_atm.nml. Therefore the line is removed in the 148-1 config and for consistency in the 148-2 run it is set to 1

🚀 The latest prerelease access-esm1p6/pr148-2 at 1b2ab93 is here: #148 (comment) 🚀

🚀 The latest prerelease access-esm1p6/pr148-11 at 1f69710 is here: #148 (comment) 🚀

github-actions · 2025-10-07T00:33:54Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr148-1 with commit 35a239e

🖥️ `Gadi` Deployment ✔️

Usage Instructions

access-esm1.6, defined in ./spack.yaml, will be deployed to Gadi as:

2025.09.002 as a Release (when merged).
pr148-1 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr148-1

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-esm1p6-pr148-1 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

access-nri/spack on branch 0.22
access-nri/spack-packages version 2025.09.004
access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

…0d36fb52cff8b37d

github-actions · 2025-10-07T00:59:09Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr148-2 with commit 1b2ab93

🖥️ `Gadi` Deployment ✔️

Usage Instructions

access-esm1.6, defined in ./spack.yaml, will be deployed to Gadi as:

2025.09.002 as a Release (when merged).
pr148-2 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr148-2

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-esm1p6-pr148-2 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

access-nri/spack on branch 0.22
access-nri/spack-packages version 2025.09.004
access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

JhanSrbinovsky · 2025-10-07T01:14:33Z

PR#148-3 -> GPP-148-3 at /g/data/p66/jxs599/ESM16/PAYU/Feat/feat-GPP-148-3-ff752

https://github.com/ACCESS-NRI/UM7/compare/ff7529166a78427ce2d3ff2a7a0caedb64dec421..6602dadd15c190ee37c6644190f52d428bc66917

rml599gh · 2025-10-07T06:02:24Z

@JhanSrbinovsky - you say in the note above that in the 148-2 test you have set the ocean albedo factor to 1, but it still appears to be 0.92 in /g/data/p66/jxs599/ESM16/PAYU/Feat/feat-148-GPP-a29dc/atmosphere/input_atm.nml - or am I missing something?

…27ce2d3ff2a7a0caedb64dec421

JhanSrbinovsky · 2025-10-07T08:35:42Z

@JhanSrbinovsky - you say in the note above that in the 148-2 test you have set the ocean albedo factor to 1, but it still appears to be 0.92 in /g/data/p66/jxs599/ESM16/PAYU/Feat/feat-148-GPP-a29dc/atmosphere/input_atm.nml - or am I missing something?

@rml599gh - bugger - I was told I didn't need to use my user scripts anymore if the appeared in the payu directory. I'll overwrite and restART

actually I think I messed it up. It must've worked in the other run where I rm-ed mention of it completely so it would run

github-actions · 2025-10-07T08:53:58Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr148-3 with commit a8ef344

🖥️ `Gadi` Deployment ✔️

Usage Instructions

access-esm1.6, defined in ./spack.yaml, will be deployed to Gadi as:

2025.09.002 as a Release (when merged).
pr148-3 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr148-3

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-esm1p6-pr148-3 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

access-nri/spack on branch 0.22
access-nri/spack-packages version 2025.09.004
access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

JhanSrbinovsky · 2025-10-07T09:17:40Z

PR#148-3 -> GPP-148-3 at /g/data/p66/jxs599/ESM16/PAYU/Feat/feat-148-GPP-ff752

corresponds to code differences between

PR148-1 v PR148-3

…b5a94d5298a57a116540445b3b

github-actions · 2025-10-07T10:00:11Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr148-4 with commit 4f26f3e

🖥️ `Gadi` Deployment ✔️

Usage Instructions

access-esm1.6, defined in ./spack.yaml, will be deployed to Gadi as:

2025.09.002 as a Release (when merged).
pr148-4 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr148-4

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-esm1p6-pr148-4 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

access-nri/spack on branch 0.22
access-nri/spack-packages version 2025.09.004
access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

JhanSrbinovsky · 2025-10-07T10:12:39Z

PR#148-4 -> GPP-148-4 at /g/data/p66/jxs599/ESM16/PAYU/Feat/feat-GPP-148-4-e4b98

corresponds to code differences between

PR148-3 v PR148-4

albedo factor is added

JhanSrbinovsky · 2025-10-07T10:29:42Z

PR#148-5 -> GPP-148-5 at /g/data/p66/jxs599/ESM16/PAYU/Feat/feat-GPP-5-148-efcfd/

corresponds to code differences between

PR148-4 v PR148-5

github-actions · 2025-10-07T10:39:40Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr148-5 with commit da36fda

🖥️ `Gadi` Deployment ✔️

Usage Instructions

access-esm1.6, defined in ./spack.yaml, will be deployed to Gadi as:

2025.09.002 as a Release (when merged).
pr148-5 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr148-5

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-esm1p6-pr148-5 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

access-nri/spack on branch 0.22
access-nri/spack-packages version 2025.09.004
access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

JhanSrbinovsky · 2025-10-08T00:13:16Z

analysis by @rml599gh indicates difference occurs between PR148-5 and 148-2

corresponding code differences are:

Note: river routing, inland basin changes shoulder be in Claires #129-3 anyway. So test -

PR#148-6 -> GPP-148-6 at /g/data/p66/jxs599/ESM16/PAYU/Feat/feat-GPP-5-148-PR129-3/

that has executable from PR129-3

Also ( assuming this shows up same changes)I will set up tests using executables including step changes. (in PM)

JhanSrbinovsky · 2025-10-08T02:17:25Z

@rml599gh - DOH! I skipped over the code change in the very last merge. I suspect the logic is is error leading to the NP ratio for leaves being

npleafx_coef = 1.0
everywhere. whereas it should be modified for evergreen_broadleaf, aust_mesic, aust_xeric.

As a side, at a glance npleax could be 0, crashing at npleafx_coef=NaN.

I'll test a revised LOGIC strategy in GPP-7. It won't be as succinct and pretty, but it should return the same GPP again I hope.

rml599gh · 2025-10-08T03:15:24Z

@JhanSrbinovsky - not sure I follow your last comment about npleafx_coef. Having been set to 1, it should be modified in the IF (ANY ... block.

JhanSrbinovsky · 2025-10-08T03:18:44Z

@JhanSrbinovsky - not sure I follow your last comment about npleafx_coef. Having been set to 1, it should be modified in the IF (ANY ... block.

@rml599gh

I imagine the ANY should be next to the array. i.e. IF ( scalar == ANY (/ EGBL, AM, AX /)

IF ( ANY( scalar == (/ EGBL, AM, AX /) ) doesn't really make sense. ivt is never == to the array

rml599gh · 2025-10-08T03:30:51Z

I don't know the syntax - but wouldn't it fail to compile if it was wrong? And I thought Claire had confirmed that her re-write of the code in the subroutine gave the same answer when we were trying to track down why the name changing gave a different answer (due to the LAI_THRESH 0.99 change).

github-actions · 2025-10-08T03:41:43Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr148-6 with commit 0e85216

🖥️ `Gadi` Deployment ❌

JhanSrbinovsky · 2025-10-08T03:45:09Z

perhaps not. maybe instead of nothing getting into the loop, everything was. maybe it was evaluating if any ivt(mp) is EGBL etc then do this.

What I should've said was using ANY is usually in the form of IF (scalar == ANY(array) ). which I just realize I copied/pasted and forgot to add IF ivt(np) = EGBL

There is also the problem that we are inside of a DO loop over np, so IDK what it would evaluate it as

IDK what the comparison was to?

no guarantee that this will resolve it, but its worth checking

JhanSrbinovsky · 2025-10-08T03:59:41Z

!redeploy

github-actions · 2025-10-08T04:24:19Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr148-7 with commit 0e85216

🖥️ `Gadi` Deployment ❌

github-actions · 2025-10-08T05:52:16Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr148-8 with commit a1a0643

🖥️ `Gadi` Deployment ❌

github-actions · 2025-10-08T06:18:49Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr148-9 with commit 725f051

🖥️ `Gadi` Deployment ✔️

Usage Instructions

access-esm1.6, defined in ./spack.yaml, will be deployed to Gadi as:

2025.09.002 as a Release (when merged).
pr148-9 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr148-9

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-esm1p6-pr148-9 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

access-nri/spack on branch 0.22
access-nri/spack-packages version 2025.09.004
access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

JhanSrbinovsky · 2025-10-08T06:40:05Z

PR#148-9 -> GPP-7 at /g/data/p66/jxs599/ESM16/PAYU/Feat/feat-GPP-7-148/ - revised conditional

PR builds went up to 9 as I kept making syntax errors. AND mod in casa_ncdf might not be necessary here but it certainly is for FCM build which is generally how I build incrementally. I reverted to FCM build for the very reason that simple build failures here due to syntax have a 20min (at least) turn around to discover. Where as FCM build can incrementally build and reveal a typo (with better error log) within minutes.

revised conditional -

IF ( ivt == ANY (/ EGBL, AM, AX /)

IF ( ANY( ivt == (/ EGBL, AM, AX /) ) doesn't really make sense.

Other mods there are simply formatting as it was difficult to read and be confident of indentation, nesting, etc

rml599gh · 2025-10-08T23:42:36Z

@JhanSrbinovsky - looks like GPP-7 is giving identical answers to 148-2. GPP-6 (129-3) is different from previous cases. Maybe we should test a case where we go back to the original way that casa_feedback was coded and just add in Australian xeric to the original code.

JhanSrbinovsky · 2025-10-09T00:19:26Z

under way. skimming the differences - maybe defining the _coeff = 1 by default stands out

JhanSrbinovsky · 2025-10-09T00:25:01Z

PR#148-10 -> GPP-10 at /g/data/p66/jxs599/ESM16/PAYU/Feat/feat-GPP-10/ - reverted casa_feedback AND updated conditional

github-actions · 2025-10-09T00:34:08Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr148-10 with commit f47842c

🖥️ `Gadi` Deployment ✔️

Usage Instructions

access-esm1.6, defined in ./spack.yaml, will be deployed to Gadi as:

2025.09.002 as a Release (when merged).
pr148-10 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr148-10

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-esm1p6-pr148-10 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

access-nri/spack on branch 0.22
access-nri/spack-packages version 2025.09.004
access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

JhanSrbinovsky · 2025-10-10T01:27:38Z

PR#148-11 -> GPP-11 at /g/data/p66/jxs599/ESM16/PAYU/Feat/feat-GPP-11/ - move initialization of _coef to inside DO loop

github-actions · 2025-10-10T01:41:50Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr148-11 with commit 1f69710

🖥️ `Gadi` Deployment ✔️

Usage Instructions

access-esm1.6, defined in ./spack.yaml, will be deployed to Gadi as:

2025.09.002 as a Release (when merged).
pr148-11 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr148-11

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-esm1p6-pr148-11 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

access-nri/spack on branch 0.22
access-nri/spack-packages version 2025.09.004
access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

JhanSrbinovsky · 2025-10-10T03:41:20Z

PR#148-11 -> GPP-12 at /g/data/p66/jxs599/ESM16/PAYU/Feat/feat-GPP-12/ - use code as in PR148-11 WITH 100%albedo.

If the new formulation is successfully a mere refactoring of the original code (moving the initialization of xnpleaf_coef inside the DO loop) then results from this run should match GPP-10

JhanSrbinovsky · 2025-10-10T04:25:09Z

PR#148-11 -> GPP-13 at /g/data/p66/jxs599/ESM16/PAYU/Feat/feat-GPP-13/ - same as GPP-12 EXCEPT start from restart270 (Sept-B)

access-hive-bot · 2025-10-14T06:09:16Z

This pull request has been mentioned on ACCESS Hive Community Forum. There might be relevant details there:

https://forum.access-hive.org.au/t/esm1-6-spin-up-experiments/4219/1

build from pre any specific land changes associated with PR#129

35a239e

JhanSrbinovsky self-assigned this Oct 7, 2025

JhanSrbinovsky linked an issue Oct 7, 2025 that may be closed by this pull request

test unexpected changes in GPP #147

Open

JhanSrbinovsky temporarily deployed to Gadi Prerelease October 7, 2025 00:10 — with GitHub Actions Inactive

JhanSrbinovsky changed the title ~~build from pre any specific land changes associated with PR#129~~ build from pre any specific land changes associated with Aus PFTs Oct 7, 2025

build from HEAD of UM7 main branch@7th Oct - a29dc8b934a20872a400a373…

1b2ab93

…0d36fb52cff8b37d

JhanSrbinovsky temporarily deployed to Gadi Prerelease October 7, 2025 00:41 — with GitHub Actions Inactive

build corresponding to first Aus PFTs revisiov in main: ff7529166a784…

a8ef344

…27ce2d3ff2a7a0caedb64dec421

JhanSrbinovsky temporarily deployed to Gadi Prerelease October 7, 2025 08:29 — with GitHub Actions Inactive

build from just before 2nd round of PFT changes begins e4b98a18e48012…

4f26f3e

…b5a94d5298a57a116540445b3b

JhanSrbinovsky temporarily deployed to Gadi Prerelease October 7, 2025 09:43 — with GitHub Actions Inactive

builds from efcfd5baaaa9fb2489d05ed998b060a0bbcd1328 just as ocean

da36fda

albedo factor is added

JhanSrbinovsky temporarily deployed to Gadi Prerelease October 7, 2025 10:24 — with GitHub Actions Inactive

revise logic

0e85216

JhanSrbinovsky had a problem deploying to Gadi Prerelease October 8, 2025 03:13 — with GitHub Actions Failure

5db1f4ea2d87a179e610cafadeaf03bcc77c6b15

a1a0643

JhanSrbinovsky had a problem deploying to Gadi Prerelease October 8, 2025 05:36 — with GitHub Actions Failure

build aa023ddbf7662ed592a8ff8c28b8014b4a0cd882

725f051

JhanSrbinovsky temporarily deployed to Gadi Prerelease October 8, 2025 05:58 — with GitHub Actions Inactive

build from UM7@5b674d7330d4e2ed28abd16be34113fc7b3969e3

f47842c

JhanSrbinovsky temporarily deployed to Gadi Prerelease October 9, 2025 00:17 — with GitHub Actions Inactive

builds from 9e65d5b1ee5212d200093c60ae26d10973eb3428

1f69710

JhanSrbinovsky temporarily deployed to Gadi Prerelease October 10, 2025 01:23 — with GitHub Actions Inactive

build from pre any specific land changes associated with Aus PFTs #148

Are you sure you want to change the base?

build from pre any specific land changes associated with Aus PFTs #148

Uh oh!

Conversation

JhanSrbinovsky commented Oct 7, 2025 • edited by github-actions bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Oct 7, 2025

🖥️ Gadi Deployment ✔️

Uh oh!

github-actions bot commented Oct 7, 2025

🖥️ Gadi Deployment ✔️

Uh oh!

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

Uh oh!

Uh oh!

rml599gh commented Oct 7, 2025

Uh oh!

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

Uh oh!

Uh oh!

github-actions bot commented Oct 7, 2025

🖥️ Gadi Deployment ✔️

Uh oh!

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

Uh oh!

Uh oh!

github-actions bot commented Oct 7, 2025

🖥️ Gadi Deployment ✔️

Uh oh!

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

Uh oh!

Uh oh!

JhanSrbinovsky commented Oct 7, 2025

Uh oh!

github-actions bot commented Oct 7, 2025

🖥️ Gadi Deployment ✔️

Uh oh!

JhanSrbinovsky commented Oct 8, 2025

Uh oh!

JhanSrbinovsky commented Oct 8, 2025

Uh oh!

rml599gh commented Oct 8, 2025

Uh oh!

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

Uh oh!

Uh oh!

rml599gh commented Oct 8, 2025

Uh oh!

github-actions bot commented Oct 8, 2025

🖥️ Gadi Deployment ❌

Uh oh!

JhanSrbinovsky commented Oct 8, 2025

Uh oh!

JhanSrbinovsky commented Oct 8, 2025

Uh oh!

github-actions bot commented Oct 8, 2025

🖥️ Gadi Deployment ❌

Uh oh!

github-actions bot commented Oct 8, 2025

🖥️ Gadi Deployment ❌

Uh oh!

github-actions bot commented Oct 8, 2025

🖥️ Gadi Deployment ✔️

Uh oh!

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

Uh oh!

Uh oh!

rml599gh commented Oct 8, 2025

Uh oh!

JhanSrbinovsky commented Oct 9, 2025

Uh oh!

JhanSrbinovsky commented Oct 9, 2025

Uh oh!

github-actions bot commented Oct 9, 2025

🖥️ Gadi Deployment ✔️

Uh oh!

JhanSrbinovsky commented Oct 10, 2025

Uh oh!

JhanSrbinovsky commented Oct 7, 2025 •

edited by github-actions bot

Loading

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

JhanSrbinovsky commented Oct 7, 2025 •

edited

Loading

JhanSrbinovsky commented Oct 7, 2025 •

edited

Loading

🖥️ `Gadi` Deployment ✔️

JhanSrbinovsky commented Oct 7, 2025 •

edited

Loading

🖥️ `Gadi` Deployment ✔️

JhanSrbinovsky commented Oct 7, 2025 •

edited

Loading

🖥️ `Gadi` Deployment ✔️

JhanSrbinovsky commented Oct 8, 2025 •

edited

Loading

🖥️ `Gadi` Deployment ❌

🖥️ `Gadi` Deployment ❌

🖥️ `Gadi` Deployment ❌

🖥️ `Gadi` Deployment ✔️

JhanSrbinovsky commented Oct 8, 2025 •

edited

Loading

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️