bug: GHA backend uses fragile string interpolation to construct URLs

[JadedBlueEyes]

Describe the bug

opendal/core/services/ghac/src/core.rs

Line 108 in 1755db1

"{}{CACHE_URL_BASE}/cache?keys={}&version={}",

results in incorrect URL construction when the base URL is missing a trailing /. This means access fails.

Steps to Reproduce

Set ACTIONS_CACHE_URL to a base URL without a trailing slash

Expected Behavior

A safe URL manipulation function is used that correctly constructs a relative URL

Additional Context

This has been an issue on some self-hosted forgejo actions runners.

Are you willing to submit a PR to fix this bug?

• Yes, I would like to submit a PR.

[dosubot]

Hi @JadedBlueEyes! I'm Dosu and I’m helping the opendal team.

Confirmed — this affects 7 places in core/src/services/ghac/core.rs where self.cache_url is concatenated with path constants via format! [1] [2] [3] [4] [5] [6].

The root cause is that CACHE_URL_BASE is defined as "_apis/artifactcache" without a leading slash [7], and cache_url is used as-is from the environment variable or user config with no trailing-slash normalization [8]. So when ACTIONS_CACHE_URL is e.g. https://host/id instead of https://host/id/, you get https://host/id_apis/artifactcache/... instead of the correct path.

The simplest fix would be to normalize cache_url to always end with / when it's first stored in the backend config — for example by trimming any existing trailing slash and re-appending one. That way all downstream format! calls work correctly regardless of what the environment provides.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.