Integration Tests - Lit Protocol tests failing with fetch error

[MantisClone]

Problem

The Lit Protocol integration tests are consistently failing in CI with a network connectivity error:

FAIL test/lit-protocol.test.ts
✕ should handle encryption errors gracefully
✕ should handle decryption errors gracefully

Failed to initialize Lit client: fetch failed

CircleCI: build #165196, job test-integration-with-request-node

Investigation

• Test file: packages/integration-test/test/lit-protocol.test.ts
• 4 tests failing, all related to Lit Protocol client initialization
• Error indicates network request to Lit Protocol's external service is failing

Questions to Answer

1. What external Lit Protocol endpoints are the tests trying to reach?
2. Is the Lit Protocol network/service experiencing issues?
3. Should these tests be mocked to avoid external dependencies in CI?
4. Has something changed in the Lit Protocol SDK or their network infrastructure?

Considerations

• These tests depend on external Lit Protocol infrastructure
• External service dependencies can cause flaky/failing CI
• May need to mock Lit Protocol calls or skip in CI if service is unreliable

[coderabbitai]

🔗 Related PRs

#1512 - feat: refactor lit protocol provider [merged]
#1536 - feat: lit session domain and statement [merged]

---

Enable issue planning

_{To enable issue planning, add the following to your .coderabbit.yaml:}

issue_enrichment:
  planning:
    enabled: true

_{You can then request a plan by commenting @coderabbitai plan on any issue.}

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[MantisClone]

Optionally skip the tests if fixing them is too dificult.