CircleCI: fix go-tests / TestOPCMLiveChain/sepolia/sepolia-v1.8.0-rc.3

[syntrust]

Error log:

        proxy.go:82:                INFO [12-23|06:51:58.333] server started                           module=retryproxy port=43673
        proxy.go:172:               WARN [12-23|06:51:58.422] unexpected status code                   module=retryproxy status=415
        proxy.go:121:               WARN [12-23|06:51:58.422] failed to proxy request                  module=retryproxy err="unexpected status code: 415"
        proxy.go:172:               WARN [12-23|06:51:59.862] unexpected status code                   module=retryproxy status=415
        proxy.go:121:               WARN [12-23|06:51:59.863] failed to proxy request                  module=retryproxy err="unexpected status code: 415"
        proxy.go:172:               WARN [12-23|06:52:02.400] unexpected status code                   module=retryproxy status=415
        proxy.go:121:               WARN [12-23|06:52:02.400] failed to proxy request                  module=retryproxy err="unexpected status code: 415"
        proxy.go:172:               WARN [12-23|06:52:06.944] unexpected status code                   module=retryproxy status=415
        proxy.go:121:               WARN [12-23|06:52:06.944] failed to proxy request                  module=retryproxy err="unexpected status code: 415"
        proxy.go:172:               WARN [12-23|06:52:12.064] unexpected status code                   module=retryproxy status=415
        proxy.go:121:               WARN [12-23|06:52:12.064] failed to proxy request                  module=retryproxy err="unexpected status code: 415"
        proxy.go:135:               ERROR[12-23|06:52:12.064] permanently failed to proxy request      module=retryproxy err="operation failed permanently after 5 attempts: unexpected status code: 415"
        anvil.go:113:               DEBUG[12-23|06:52:12.064] [ANVIL] thread 'main' panicked at /home/runner/work/foundry/foundry/crates/anvil/src/config.rs:1147:57:
        anvil.go:113:               DEBUG[12-23|06:52:12.064] [ANVIL] Failed to get fork block number: Transport(HttpError(HttpError { status: 502, body: "failed to proxy request\n" }))
        anvil.go:113:               DEBUG[12-23|06:52:12.064] "[ANVIL] note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace"
        opcm_test.go:63: 
                Error Trace:    /root/dl/circleci/optimism/op-deployer/pkg/deployer/bootstrap/opcm_test.go:63
/root/dl/circleci/optimism/op-deployer/pkg/deployer/bootstrap/opcm_test.go:33
                Error:          Received unexpected error:
                                context deadline exceeded
                Test:           TestOPCMLiveChain/sepolia-v1.8.0-rc.3

Status code 415 means "Unsupported Media Type" and "http://88.99.30.186:8545" looks cannot handle request without a specified content-type.

CircleCI tests passed with the fix in the latest run.

[dajuguan]

Can we reuse context to set the SEPOLIA_RPC_URL env?

[syntrust]

Can we reuse context to set the SEPOLIA_RPC_URL env?

I'm not certain why Shell is being embedded instead of utilizing a context, but it might be related to the <<parameters.environment_overrides>> section below, and any changes could affect other jobs using this part. So I would prefer to maintain the current approach until necessary.

[blockchaindevsh]

Why doesn't upstream have this issue, are we using the same l1 client as upstream? We can upstream this fix if we know the root reason.

[syntrust]

It could be the different implementation/configuration on the L1 clients.

[dajuguan]

Can we reuse context to set the SEPOLIA_RPC_URL env?

I'm not certain why Shell is being embedded instead of utilizing a context, but it might be related to the <<parameters.environment_overrides>> section below, and any changes could affect other jobs using this part. So I would prefer to maintain the current approach until necessary.

I see. The concern is that our RPC could be exposed to malicious actors, which is why I inquired about it earlier.

[syntrust]

Can we reuse context to set the SEPOLIA_RPC_URL env?

I'm not certain why Shell is being embedded instead of utilizing a context, but it might be related to the <<parameters.environment_overrides>> section below, and any changes could affect other jobs using this part. So I would prefer to maintain the current approach until necessary.

I see. The concern is that our RPC could be exposed to malicious actors, which is why I inquired about it earlier.

Yes, that is a concern, especially if we need to replace the mainnet RPC.