-
Notifications
You must be signed in to change notification settings - Fork 140
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
Test JDC Pool Fallback #1343
base: main
Are you sure you want to change the base?
Test JDC Pool Fallback #1343
Conversation
Bencher Report
Click to view all benchmark results
|
Bencher Report
Click to view all benchmark results
|
Bencher Report
Click to view all benchmark results
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1343 +/- ##
==========================================
+ Coverage 16.90% 19.11% +2.21%
==========================================
Files 164 166 +2
Lines 10956 11047 +91
==========================================
+ Hits 1852 2112 +260
+ Misses 9104 8935 -169
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
It changes the structuring of the start method, to avoid its blocking nature in case of disconnection from the upstream. Currently, when we are sending the termination signal, during the stance of disconnection from upstream, due of blocking nature of initialize_jd it halts the main thread runtime from executing select block, which listens for any termination signal and channel responses. **Modifications** 1. Addition of new shutdown field, which can be used later in integration test to terminate the instances 2. Change argument type for methods initialize_jd and initialize_jd_solo, to make them movable. 3. Spawning of blocking process as a separate task
.. instead of repeated code
65fcc64
to
5c367cd
Compare
5c367cd
to
b50e256
Compare
Some(vec![InterceptMessage::new( | ||
MessageDirection::ToDownstream, | ||
MESSAGE_TYPE_MINING_SET_NEW_PREV_HASH, | ||
PoolMessages::Mining(Mining::SubmitSharesError(SubmitSharesError { | ||
channel_id: 0, | ||
sequence_number: 0, | ||
error_code: "invalid-nonce".to_string().into_bytes().try_into().unwrap(), | ||
})), | ||
MESSAGE_TYPE_SUBMIT_SHARES_ERROR, | ||
false, | ||
)]), | ||
) |
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.
@Shourya742 @plebhash @GitGab19 I took a different approach here:
Instead of starting a miner and waiting for share submission and then success share submission message and altering it to error share submission, I just altered one of the previous messages(MINING_SET_NEW_PREV_HASH in this case). This is inspired by a discussion I had yesterday with @Shourya742 .
LMKWYT please.
resolves #1207
blocked by #1319 & #1321