Skip to content

Conversation

PatStiles
Copy link
Contributor

Add Retry Logic to IsOperatorRegistered

Description

#closes 1415

How to test

In devnet

  1. make anvil_start_with_block_time
  2. make aggregator_start
  3. make operator_full_registration CONFIG_FILE=config-files/config-operator-1.yaml
  4. make operator_start CONFIG_FILE=config-files/config-operator-1.yaml
  5. make batcher_start_local
  6. make telemetry_full_start

Once you have the system running, send proofs

  1. make batcher_send_burst_groth16
  2. Go to jaeger http://localhost:16686/search
  3. You should see the traces correctly created and task verified
image

Type of change

  • New feature

Checklist

  • [https://github.com/feat(operator): Operator Retries #1415] Linked to Github Issue
  • This change depends on code or research by an external entity
    • Acknowledgements were updated to give credit
  • Unit tests added
  • This change requires new documentation.
    • Documentation has been added/updated.
  • This change is an Optimization
    • Benchmarks added/run
  • Has a known issue
  • If your PR changes the Operator compatibility (Ex: Upgrade prover versions)
    • This PR adds compatibility for operator for both versions and do not change batcher/docs/examples
    • This PR updates batcher and docs/examples to the newer version. This requires the operator are already updated to be compatible

@PatStiles PatStiles changed the base branch from 1401-1414-aggregator-retry-improvements to staging November 19, 2024 17:24
@PatStiles PatStiles force-pushed the 1415-is-operator-registered branch from e5b9f00 to 9109f60 Compare November 19, 2024 19:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants