PCCS crate - consider adding a timeout to Pccs::ready method

Open
#24 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
58/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust

Research direction

Start by locating the PCCS crate's Pccs::ready method and tracing the pre-warm task that populates the cache from known FSMPCs. Review the linked pull-request discussion for context, then verify that readiness no longer waits indefinitely when pre-warming fails and that the resulting error behavior is covered by the relevant tests.

Written by the indexing model from the issue text.

Description

The PCCS exposes a method to wait for 'readiness', meaning the cache is populated with collateral from all known FSMPCs.

If there is an issue with the 'pre-warm' fetching (eg: the task panics for some reason) this future will wait indefinately.

Consider adding a timeout to return an error if the cache is not filled after some reasonable duration.

See discussion: https://github.com/flashbots/attested-tls/pull/3#discussion_r2974833918

Dominant language
Rust
Stars
6
Forks
3
Avg merge
4d 5h
Merged PRs (30d)
7

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from flashbots/attested-tls

All issues in flashbots/attested-tls

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.