Pre-existing Gitea Actions failures on main that are not caused by any open PR. Observed on run #211 (head 07d9ce4876) before Phase 1b PR #1 was opened. Scope limited to YAML-only changes — no runner-image changes, no new secrets, no submodule surgery.
github/codeql-action/upload-sarif@v2 targets GitHub's code-scanning API, which Gitea does not host.
Fix:continue-on-error: true (ci.yml already had this).
Out of scope — flagged for follow-up
These will still fail after this PR merges; they require actual investigation, not a YAML tweak:
CI/CD Pipeline / Solidity Contracts — lib/dodo-contractV2 pinned commit d946606870b64110218820da44becf2b3e196c8a no longer exists on the remote. Fix options: update the submodule pointer to a new pinned commit, or restore the missing commit on the remote. Likely means pointing the submodule at the Gitea mirror if one exists.
Validation / validate-kubernetes — kubectl apply --dry-run=client fails with connect: connection refused because it tries to contact localhost:8080. The fix is to pass --validate=false (or run --dry-run=server against a kind cluster). Separate design call.
CI/CD Pipeline / Lint and Format — forge fmt --check actually finds formatting issues in contracts/. Real code-style work, not CI-plumbing.
Verification
Inspected logs for master run #211 to confirm the three failure modes above exist independent of any PR.
No submodules touched; the M lib/* flags in local git status are from an existing detached-HEAD checkout and are not staged.
Scope
Diff is 2 files, +27 / −2 lines.
No new secrets required.
No act-runner image changes required.
## Summary
Pre-existing Gitea Actions failures on `main` that are not caused by any open PR. Observed on run #211 (head 07d9ce4876) before Phase 1b PR #1 was opened. Scope limited to YAML-only changes — no runner-image changes, no new secrets, no submodule surgery.
## Failures addressed
1. **Terraform Validation** (`ci.yml::terraform`, `validation.yml::validate-terraform`)
`hashicorp/setup-terraform@v2` / `@v3` fails with:
```
::error::Unable to locate executable file: unzip.
❌ Failure - Main Setup Terraform
```
**Fix:** install `unzip` in-job (idempotent, no-ops if already present). Better than requiring an act-runner image rebuild.
2. **Security Scanning / Container Security Scan** (`ci.yml::security`, `validation.yml::validate-security`)
`aquasecurity/trivy-action@master` fails with:
```
::error::Bad credentials - https://docs.github.com/rest
❌ Failure - Main Checkout install script
❌ Failure - Main Install Trivy
```
Root cause: Gitea Actions injects a Gitea token as `GITHUB_TOKEN`, which `api.github.com/repos/aquasecurity/trivy/releases/latest` rejects.
**Fix:**
- Pin the action to `@0.28.0` + pin `version: v0.51.1` → installer skips the `releases/latest` lookup entirely.
- Clear `GITHUB_TOKEN: ""` in the step env → installer falls back to anonymous.
- Add `continue-on-error: true` on the validation.yml step so a flaky scan does not block PRs (ci.yml already had this).
3. **Upload Trivy results** (`validation.yml::validate-security`)
`github/codeql-action/upload-sarif@v2` targets GitHub's code-scanning API, which Gitea does not host.
**Fix:** `continue-on-error: true` (ci.yml already had this).
## Out of scope — flagged for follow-up
These will still fail after this PR merges; they require actual investigation, not a YAML tweak:
- **`CI/CD Pipeline / Solidity Contracts`** — `lib/dodo-contractV2` pinned commit `d946606870b64110218820da44becf2b3e196c8a` no longer exists on the remote. Fix options: update the submodule pointer to a new pinned commit, or restore the missing commit on the remote. Likely means pointing the submodule at the Gitea mirror if one exists.
- **`Validation / validate-kubernetes`** — `kubectl apply --dry-run=client` fails with `connect: connection refused` because it tries to contact `localhost:8080`. The fix is to pass `--validate=false` (or run `--dry-run=server` against a kind cluster). Separate design call.
- **`CI/CD Pipeline / Lint and Format`** — `forge fmt --check` actually finds formatting issues in `contracts/`. Real code-style work, not CI-plumbing.
## Verification
- Inspected logs for master run #211 to confirm the three failure modes above exist independent of any PR.
- No submodules touched; the `M lib/*` flags in local `git status` are from an existing detached-HEAD checkout and are not staged.
## Scope
- Diff is **2 files, +27 / −2 lines**.
- No new secrets required.
- No act-runner image changes required.
Aligns canonical-tokens FALLBACK_ADDRESSES with smart-contracts-master.json
so /api/v1/report/token-list includes cAUSDT when env overrides are absent.
Made-with: Cursor
- MessageQueue: resetRetryCount and retry({ increment: false }) for shedder/inventory paths
- RelayService: treat bridge_inventory_probe like other soft-failure scopes; wrap inventory check in try/catch
- Token aggregation: catch DB pool lookup errors and fall back to live DODO path
- Mainnet WETH profile: START_BLOCK=latest; extend RELAY_SKIP_MESSAGE_IDS for backlog hygiene
- Extend relay test.js for deferred requeue behavior
Made-with: Cursor
- Archived multiple non-EVM adapters (Algorand, Hedera, Tron, TON, Cosmos, Solana) and compliance contracts (IndyVerifier) to `archive/solidity/contracts/`.
- Updated documentation to reflect the historical status of archived components.
- Adjusted `foundry.toml` and `README.md` for clarity on historical dependencies and configurations.
- Enhanced Makefile and package.json scripts for improved contract testing and building processes.
- Removed obsolete contracts (AlltraCustomBridge, CommodityCCIPBridge, ISO4217WCCIPBridge, VaultBridgeAdapter) from the main directory.
- Updated implementation reports to indicate archived status for various components.
Pre-existing failures observed on main (run #211) before Phase 1b PR #1
existed:
1. Terraform Validation: hashicorp/setup-terraform fails with "Unable
to locate executable file: unzip" on act-runner image. Install
unzip in-job (idempotent, no-ops if already present).
2. Container Security Scan + Run Trivy container scan: aquasecurity/
trivy-action@master emits "Bad credentials - https://docs.github.com/
rest" when installing the Trivy binary. Root cause: Gitea Actions
injects a Gitea token as GITHUB_TOKEN, which api.github.com rejects.
Pin the action to @0.28.0 + trivy binary version to v0.51.1 (skips
the GitHub releases API lookup), and clear GITHUB_TOKEN in the step
env so the installer falls back to anonymous access. Mark the step
continue-on-error so a flaky scan does not block PRs.
3. Upload Trivy results (validation.yml only): github/codeql-action/
upload-sarif targets GitHub's code-scanning API, which Gitea does
not host. Mark continue-on-error so the job does not fail.
Out of scope (not addressable via YAML-only changes):
- lib/dodo-contractV2 pinned commit d946606870b64110218820da44becf2b3e196c8a
no longer exists on the remote; Solidity Contracts job will keep
failing until the submodule pointer is refreshed or the remote is
restored.
- validate-kubernetes kubectl dry-run fails with connection refused
because no local API server is running on the runner; that needs
switching to `kubectl apply --dry-run=client --validate=false` or
a local kubeconfig, which is a separate design choice.
Co-Authored-By: Nakamoto, S <defi@defi-oracle.io>
Tag @0.28.0 does not exist in act-runner's reference resolution
("Unable to resolve 0.28.0: reference not found"). Use @master and
rely on the 'version: v0.51.1' input to pin the Trivy binary so the
installer still skips api.github.com releases/latest.
Co-Authored-By: Nakamoto, S <defi@defi-oracle.io>
This pull request is broken due to missing fork information.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Pre-existing Gitea Actions failures on
mainthat are not caused by any open PR. Observed on run #211 (head07d9ce4876) before Phase 1b PR #1 was opened. Scope limited to YAML-only changes — no runner-image changes, no new secrets, no submodule surgery.Failures addressed
Terraform Validation (
ci.yml::terraform,validation.yml::validate-terraform)hashicorp/setup-terraform@v2/@v3fails with:Fix: install
unzipin-job (idempotent, no-ops if already present). Better than requiring an act-runner image rebuild.Security Scanning / Container Security Scan (
ci.yml::security,validation.yml::validate-security)aquasecurity/trivy-action@masterfails with:Root cause: Gitea Actions injects a Gitea token as
GITHUB_TOKEN, whichapi.github.com/repos/aquasecurity/trivy/releases/latestrejects.Fix:
@0.28.0+ pinversion: v0.51.1→ installer skips thereleases/latestlookup entirely.GITHUB_TOKEN: ""in the step env → installer falls back to anonymous.continue-on-error: trueon the validation.yml step so a flaky scan does not block PRs (ci.yml already had this).Upload Trivy results (
validation.yml::validate-security)github/codeql-action/upload-sarif@v2targets GitHub's code-scanning API, which Gitea does not host.Fix:
continue-on-error: true(ci.yml already had this).Out of scope — flagged for follow-up
These will still fail after this PR merges; they require actual investigation, not a YAML tweak:
CI/CD Pipeline / Solidity Contracts—lib/dodo-contractV2pinned commitd946606870b64110218820da44becf2b3e196c8ano longer exists on the remote. Fix options: update the submodule pointer to a new pinned commit, or restore the missing commit on the remote. Likely means pointing the submodule at the Gitea mirror if one exists.Validation / validate-kubernetes—kubectl apply --dry-run=clientfails withconnect: connection refusedbecause it tries to contactlocalhost:8080. The fix is to pass--validate=false(or run--dry-run=serveragainst a kind cluster). Separate design call.CI/CD Pipeline / Lint and Format—forge fmt --checkactually finds formatting issues incontracts/. Real code-style work, not CI-plumbing.Verification
M lib/*flags in localgit statusare from an existing detached-HEAD checkout and are not staged.Scope
- MessageQueue: resetRetryCount and retry({ increment: false }) for shedder/inventory paths - RelayService: treat bridge_inventory_probe like other soft-failure scopes; wrap inventory check in try/catch - Token aggregation: catch DB pool lookup errors and fall back to live DODO path - Mainnet WETH profile: START_BLOCK=latest; extend RELAY_SKIP_MESSAGE_IDS for backlog hygiene - Extend relay test.js for deferred requeue behavior Made-with: CursorTag @0.28.0 does not exist in act-runner's reference resolution ("Unable to resolve 0.28.0: reference not found"). Use @master and rely on the 'version: v0.51.1' input to pin the Trivy binary so the installer still skips api.github.com releases/latest. Co-Authored-By: Nakamoto, S <defi@defi-oracle.io>View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.