• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

decentraland / world-storage-service / 32751312762
97%

Build:
DEFAULT BRANCH: main
Ran 24 Aug 2026 04:32PM UTC
Jobs 1
Files 59
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

24 Aug 2026 04:31PM UTC coverage: 98.683% (+0.004%) from 98.679%
32751312762

push

github

web-flow
fix: accept the legacy signed payload so explorer scenes can reach storage (#117)

Every signed request from a scene is answering 401, and the storage delegation
it carries is never even looked at.

The explorers still sign the pre-6.0.0 payload -- in bevy,
`format!("{method}:{path}:{ts}:{meta}").to_lowercase()` in
`crates/wallet/src/lib.rs` -- while delivering the metadata header verbatim.
Since 6.0.0 the metadata is joined into the signed payload as-is, so the two
disagree for any metadata carrying uppercase. The delegated request metadata
bevy builds in `crates/wallet/delegation.rs` is full of it: `isGuest`,
`realm.serverName`, `realmName`, `sceneId`. So the signature fails, and it
fails in `signedFetchMiddleware`, which runs before `authorizationMiddleware` --
the delegation is valid and never consulted.

Declares the metadata keys this service authorizes on, which makes the older
payload verify again while keeping the delivered bytes bound for everything
that decides an outcome: `signer` for the scene gate, `realmName` and
`realm.serverName` for the world, `parcel` for the placeId that scopes storage
and quota, and `sceneId`, which authorization-middleware matches against the
delegation claim.

The version bump is load-bearing, not housekeeping. `canonicalMetadataKeys`
landed in 6.2.0; on the 6.1.0 this pinned, the option parses and is ignored, so
adding it alone changes nothing. Confirmed by reproducing against both.

Property values stay unbound, and cannot be bound here -- the fold hides them
as well as keys. That is why the signer check must remain `rejectIfSigner`
rather than a bare equality comparison, and it stays refused under every
spelling.

Extracts the policy so the spec asserts the wiring rather than a copy of it.
That was not cosmetic: the first version of this test reconstructed the options
from an exported key list and passed happily with the fallback stripped out of
routes.ts. Now removing it fails 8 of the 9 cases, which is what... (continued)

424 of 438 branches covered (96.8%)

Branch coverage included in aggregate %.

5 of 5 new or added lines in 2 files covered. (100.0%)

1149 of 1156 relevant lines covered (99.39%)

71.24 hits per line

Jobs
ID Job ID Ran Files Coverage
1 32751312762.1 24 Aug 2026 04:32PM UTC 118
98.89
GitHub Action Run
Source Files on build 32751312762
  • Tree
  • List 59
  • Changed 34
  • Source Changed 1
  • Coverage Changed 34
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #32751312762
  • 93cac60a on github
  • Prev Build on main (#32378180676)
  • Next Build on main (#32895581585)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc