-
Notifications
You must be signed in to change notification settings - Fork 56
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
Merge back rc2024.10.3 #2300
Merge back rc2024.10.3 #2300
Conversation
uses node control flow to exit a node if we consistently detect high CPU
We will not release these binaries any more.
The `faucet` and `sn_auditor` binaries do not apply to the EVM-based network, so they will be removed.
These targets were not used for a long time and were just cluttering the file with noise.
These crates were not being correctly referenced in some other crates, which meant some release configurations would not build properly.
This is a requirement of the web app.
The node RPC is changed such that the stop event allows shutting the node down with either a success or failure result. Then, in the case of the excessive CPU usage, the node will be shut down with a success result. This allows us to retain an on-failure restart policy for node-based services: with excess CPU usage, they would shut down with a success and so would not be started again.
…ct approval to infinite
feat(evmlib): add token allowance and approval functions & set contra…
feat(launchpad): evm launchpad integration
Using a larger chunk size resulted in the node having a larger memory footprint due to the size of the records cache.
…ds_cache chore: reduce max records cache size
feat: download either a file or dir based based on data
Advice on setting these keys had been removed, but as far as I know, they are still required.
================== Crate Versions ================== autonomi: 0.2.0 autonomi-cli: 0.1.1 evmlib: 0.1.1 evm_testnet: 0.1.1 sn_build_info: 0.1.16 sn_evm: 0.1.1 sn_logging: 0.2.37 sn_metrics: 0.1.17 nat-detection: 0.2.8 sn_networking: 0.19.0 sn_node: 0.112.0 node-launchpad: 0.4.0 sn_node_manager: 0.11.0 sn_node_rpc_client: 0.6.32 sn_peers_acquisition: 0.5.4 sn_protocol: 0.17.12 sn_registers: 0.4.0 sn_service_management: 0.4.0 sn_transfers: 0.20.0 test_utils: 0.4.8 token_supplies: 0.1.55 =================== Binary Versions =================== nat-detection: 0.2.8 node-launchpad: 0.4.0 autonomi: 0.1.1 safenode: 0.112.0 safenode-manager: 0.11.0 safenode_rpc_client: 0.6.32 safenodemand: 0.11.0
Action::StoreDiscordUserName(username.clone()), | ||
Action::OptionsActions(OptionsActions::UpdateBetaProgrammeUsername( | ||
username, | ||
)), // FIXME: Change OptionsActions::UpdateBetaProgrammeUsername name |
Check notice
Code scanning / devskim
A "TODO" or similar was left in source code, possibly indicating incomplete functionality Note
@@ -200,7 +221,8 @@ | |||
|
|||
match self.state { | |||
BetaProgrammeState::DiscordIdAlreadySet => { | |||
// split into 4 parts, for the prompt, input, text, dash , and buttons | |||
self.validate(); // FIXME: maybe this should be somewhere else |
Check notice
Code scanning / devskim
A "TODO" or similar was left in source code, possibly indicating incomplete functionality Note
}, | ||
), | ||
Constraint::Length(if self.discord_username.is_empty() { | ||
41 //TODO: make it dynamic with wallet_not_set |
Check notice
Code scanning / devskim
A "TODO" or similar was left in source code, possibly indicating incomplete functionality Note
@@ -288,6 +291,7 @@ | |||
config.data_dir_path.clone(), | |||
true, | |||
None, | |||
Some(EvmNetwork::ArbitrumSepolia), //FIXME: should come from an UI element. |
Check notice
Code scanning / devskim
A "TODO" or similar was left in source code, possibly indicating incomplete functionality Note
@@ -362,6 +366,7 @@ | |||
config.data_dir_path.clone(), | |||
true, | |||
None, | |||
Some(EvmNetwork::ArbitrumSepolia), //FIXME: Should come from an UI element |
Check notice
Code scanning / devskim
A "TODO" or similar was left in source code, possibly indicating incomplete functionality Note
344699f
to
876beed
Compare
876beed
to
b47fd84
Compare
b47fd84
to
7341105
Compare
Description
With the last three revert commits, there is no conflices to merge back into main.
And followup work for these three revert commits are: