-
Notifications
You must be signed in to change notification settings - Fork 40
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
Wire edgeless in simulation mode for local testnet #1905
Conversation
} | ||
|
||
// only set the pccsAddr env var if it's defined | ||
if d.cfg.pccsAddr != "" { | ||
envs["PCCS_ADDR"] = d.cfg.pccsAddr | ||
} | ||
|
||
// todo - do we need this volume? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@BedrockSquirrel , can you think of any situation where we need the data between different runs of the testnet?
(Other than upgrades, which we don't test locally currently?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a bit confused, yeah it's just for upgrades. But doesn't this code gets used for the main testnets as well as the local testnets?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Worth deleting this then, or want to leave it in case we need to add it back in?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah. there might be scenarios we don't know
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
} | ||
|
||
// only set the pccsAddr env var if it's defined | ||
if d.cfg.pccsAddr != "" { | ||
envs["PCCS_ADDR"] = d.cfg.pccsAddr | ||
} | ||
|
||
// todo - do we need this volume? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Worth deleting this then, or want to leave it in case we need to add it back in?
Why this change is needed
Sqlite doesn't work properly under load. The e2e tests running against a "local testnet" deployment fail with "database locked"
What changes were made as part of this PR
replace sqlite with edgeless for the "local testnet"
PR checks pre-merging
Please indicate below by ticking the checkbox that you have read and performed the required
PR checks