-
Notifications
You must be signed in to change notification settings - Fork 20
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
Remove sidechain functionality from bc-worker #2660
Conversation
cc @kziemianek @felixfaisal could you please take a look at this PR? Thanks! |
returned back @kziemianek , @Kailai-Wang any tips what else might be addressed within this task? |
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.
Looks good, I ran it locally, able to sync, I'm not very familiar with what all is absolutely required for sidechain functionality and what is not. So I might be missing or overlooking something.
}, | ||
EnclaveMetric::TopPoolSizeSet(pool_size) => { | ||
ENCLAVE_SIDECHAIN_TOP_POOL_SIZE.set(pool_size as i64); | ||
}, | ||
EnclaveMetric::TopPoolSizeIncrement => { | ||
ENCLAVE_SIDECHAIN_TOP_POOL_SIZE.inc(); |
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.
Can this metric be removed together with related code ?
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.
it used at two functions process_top
and remove_top
, so it seems they used at code we utilise.
// Update metric
if let Err(e) = self.ocall_api.update_metric(EnclaveMetric::TopPoolSizeIncrement) {
warn!("Failed to update metric for top pool size: {:?}", e);
}
do you think this metrics irrelevant anymore?
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.
top pool is a sidechain functionality. If we aim for getting rid of sidechain related code from bc-worker it should be removed too.
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.
great then I'll review author functionality and will try to remove as much as possible. Thanks
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.
Hey @kziemianek, I've managed to remove some functionality with one of latest commits but it seems whole Author's logic used across the bitacross project and not sure is it relevant or not. 🤔
Probably I'd finish with only this chunk of work and merge it. What do you think?
Want to get this PR done @Traf333 ? :) |
I have to remove a trusted operations functionality. Should be pretty quick, though I was focused on higher priority tasks |
8ac5463
to
a5dd978
Compare
a5dd978
to
63a881f
Compare
Context
this PR tends to remove redundant code for bc-worker since we don't use sidechain there. In addition it removes a
changelog
folder which uses ruby language and not used at our project