Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Chore]: Add an env var for polling operations #1113

Closed
3 tasks done
hozzjss opened this issue Dec 12, 2024 · 0 comments · Fixed by stacks-network/sbtc-bridge#83
Closed
3 tasks done

[Chore]: Add an env var for polling operations #1113

hozzjss opened this issue Dec 12, 2024 · 0 comments · Fixed by stacks-network/sbtc-bridge#83
Assignees
Labels

Comments

@hozzjss
Copy link
Collaborator

hozzjss commented Dec 12, 2024

Chore - Add polling env var

1. Description

some operations like the deposit and reclaim take time to complete and the data need to be polled to get the current status of the operation, however currently in deposit and reclaim the polling interval in milliseconds is hardcoded which means that to change them we'll need to commit changes and rebuild the image

3. Execution Checklist

  • Add env var in .env.sample for all polling operations
  • Read the env var and pass to the bridge config aciton
  • Add the polling ms variable to the deposit and reclaim status hooks
@hozzjss hozzjss added the chore label Dec 12, 2024
@hozzjss hozzjss moved this to Todo in sBTC Dec 12, 2024
@hozzjss hozzjss added this to sBTC Dec 12, 2024
@hozzjss hozzjss added this to the sBTC 0.9, mainnet release milestone Dec 12, 2024
@hozzjss hozzjss self-assigned this Dec 12, 2024
@hozzjss hozzjss linked a pull request Dec 20, 2024 that will close this issue
@hozzjss hozzjss moved this from Todo to In Review in sBTC Dec 20, 2024
@github-project-automation github-project-automation bot moved this from In Review to Done in sBTC Dec 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants