Description
On the RC-run page at https://dex.penumbra.zone/explore, the pair ATOM/stATOM does not appear. When I run in local dev, however, I see it just fine:
screenshot
Why is stATOM not displaying on the hosted frontend? @VanishMax reported that he's seeing very outdated cache info:
registry GET response headers
Headers {
'accept-ranges': 'bytes',
'access-control-allow-origin': '*',
'cache-control': 'max-age=300',
connection: 'keep-alive',
'content-encoding': 'gzip',
'content-length': '12650',
'content-security-policy': "default-src 'none'; style-src 'unsafe-inline'; sandbox",
'content-type': 'text/plain; charset=utf-8',
'cross-origin-resource-policy': 'cross-origin',
date: 'Wed, 18 Dec 2024 07:15:03 GMT',
etag: 'W/"786fa45b232661b594dffe7d7736ef782a0280029e9449c397cfc794bcd6bdec"',
expires: 'Wed, 18 Dec 2024 07:20:03 GMT',
'source-age': '139',
'strict-transport-security': 'max-age=31536000',
vary: 'Authorization,Accept-Encoding,Origin',
via: '1.1 varnish',
'x-cache': 'HIT',
'x-cache-hits': '6',
'x-content-type-options': 'nosniff',
'x-fastly-request-id': '3dca6be15f3121129ec0ac61d18129c62dd3b819',
'x-frame-options': 'deny',
'x-github-request-id': 'A956:1C1A54:24C7E:4B117:67623FC8',
'x-served-by': 'cache-dxb1470021-DXB',
'x-timer': 'S1734506104.968369,VS0,VE0',
'x-xss-protection': '1; mode=block'
}
Notably I do not see the same outdated cache info, neither locally nor on the hosted frontend. What I see is about what I'd expect:
registry GET response headers
HTTP/2 200
cache-control: max-age=300
content-security-policy: default-src 'none'; style-src 'unsafe-inline'; sandbox
content-type: text/plain; charset=utf-8
etag: W/"4bbccdbfb826a6d40d3891cd7f92e20e97fcc192197fab8af912be90634343e1"
strict-transport-security: max-age=31536000
x-content-type-options: nosniff
x-frame-options: deny
x-xss-protection: 1; mode=block
x-github-request-id: 62BE:290660:1256F8B:139522B:67AE389E
content-encoding: gzip
accept-ranges: bytes
date: Thu, 13 Feb 2025 19:24:56 GMT
via: 1.1 varnish
x-served-by: cache-sjc1000134-SJC
x-cache: HIT
x-cache-hits: 1
x-timer: S1739474697.507758,VS0,VE59
vary: Authorization,Accept-Encoding,Origin
access-control-allow-origin: *
cross-origin-resource-policy: cross-origin
x-fastly-request-id: 353c3c4966d5f57f35739b67febbea12ad9c0b4a
expires: Thu, 13 Feb 2025 19:29:56 GMT
source-age: 0
content-length: 18959
X-Firefox-Spdy: h2
Given that I'm seeing the same behavior as @VanishMax without the reported caching problems, I suspect that the cache problem is a red herring. @VanishMax can you try rm -rf node_modules/ && pnpm install && pnpm dev and see if you can replicate the cache problem?
Even if you can, I don't think that's relevant for the missing stATOM, because the /explore page isn't naively reading out of the registry JSON to render that page—or so I assume. This'll be difficult to debug without backend access to the RC deployment, but let's do our best.
Activity