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

Merge back rc2024.10.3 #2300

Merged
merged 33 commits into from
Oct 23, 2024
Merged

Merge back rc2024.10.3 #2300

merged 33 commits into from
Oct 23, 2024

Conversation

maqi
Copy link
Member

@maqi maqi commented Oct 23, 2024

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:

  • revert of reverting PR 2224: nothing more. Just need to resolve the high CPU usage issue separately. @joshuef is already on it.
  • revert of reverting PR 2243: nothing more. Related work already merged into main
  • revert of download either file or dir work: @RolandSherwin or @grumbach shall already on it to have a better resolvement of how to support the feature in better way

joshuef and others added 30 commits October 16, 2024 10:17
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.
feat(evmlib): add token allowance and approval functions & set contra…
…refixed_with_network_keys"

This reverts commit 147ba8e, reversing
changes made to 00ad51d.
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

Suspicious comment
@@ -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

Suspicious comment
},
),
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

Suspicious comment
@@ -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

Suspicious comment
@@ -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

Suspicious comment
@maqi maqi force-pushed the merge_back_RC2024-10-3 branch from 344699f to 876beed Compare October 23, 2024 10:09
@maqi maqi force-pushed the merge_back_RC2024-10-3 branch from 876beed to b47fd84 Compare October 23, 2024 10:31
@maqi maqi changed the title Merge back rc2024 10 3 Merge back rc2024.10.3 Oct 23, 2024
@maqi maqi force-pushed the merge_back_RC2024-10-3 branch from b47fd84 to 7341105 Compare October 23, 2024 11:55
approve_to_spend_tokens(
wallet.clone(),
// Check allowance
let allowance = token_allowance(

Check notice

Code scanning / devskim

A "TODO" or similar was left in source code, possibly indicating incomplete functionality Note

Suspicious comment
@maqi maqi removed the DoNotMerge label Oct 23, 2024
@maqi maqi added this pull request to the merge queue Oct 23, 2024
@jacderida jacderida removed this pull request from the merge queue due to a manual request Oct 23, 2024
@jacderida jacderida merged commit bb54425 into maidsafe:main Oct 23, 2024
26 of 27 checks passed
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.

6 participants