More Changes to Support EVM-based Networks #216
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The component is no longer relevant.
Now that we're not dealing with the faucet, the name doesn't need to be qualified. This also excludes the EVM node from being queried for status, since EVM nodes are not using `safenode-manager`.
Since we changed the uploader setup to use different users, we also had to adapt the upgrade process for that. The amount of services to restart are determined by the number of `safeX` users.
With the faucet gone, there is no need to qualify the version name.
This will be for starting nodes in a more controlled fashion, if an upgrade fails.
jacderida
force-pushed
the
feat-upgrades_with_evm_payments
branch
from
dfb9e4f to
756fc26
Compare
RolandSherwin
approved these changes
Nov 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
7788aac chore: revert upload file size to 15mb
Yesterday we increased this to 150mb to get some more data flowing through the production network,
but it contributed to a development comparison filling up its disk space quite quickly.
For now we will revert back to 15, but shortly we can make it a configurable value.
e4c0ed7 chore: remove the faucet from the upgrade process
The component is no longer relevant.
7aea6ff chore: rename
force-safenodeflag toforceNow that we're not dealing with the faucet, the name doesn't need to be qualified.
This also excludes the EVM node from being queried for status, since EVM nodes are not using
safenode-manager.e0cdc47 feat: use new mechanism for uploader upgrades
Since we changed the uploader setup to use different users, we also had to adapt the upgrade process
for that. The amount of services to restart are determined by the number of
safeXusers.9519990 chore: rename
safenode-versionarg toversionWith the faucet gone, there is no need to qualify the version name.
b677fdb feat: add
intervalarg to thestartcommandThis will be for starting nodes in a more controlled fashion, if an upgrade fails.
dfb9e4f feat:
startcommand supports custom inventory