-
Notifications
You must be signed in to change notification settings - Fork 141
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
JDC parse incoming mining messages from upstream after SetupConnection #1080
Merged
GitGab19
merged 1 commit into
stratum-mining:dev
from
plebhash:patch-jdc-upstream-setup-connection
Aug 1, 2024
Merged
JDC parse incoming mining messages from upstream after SetupConnection #1080
GitGab19
merged 1 commit into
stratum-mining:dev
from
plebhash:patch-jdc-upstream-setup-connection
Aug 1, 2024
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
plebhash
force-pushed
the
patch-jdc-upstream-setup-connection
branch
from
August 1, 2024 18:52
49041ac
to
1e8aca8
Compare
`Upstream::parse_incoming` only calls `handle_message_mining`, which is not able to handle a `SetupConnection.Success` (because it belongs to the "Common Messages" category, not "Mining Messages")
plebhash
force-pushed
the
patch-jdc-upstream-setup-connection
branch
from
August 1, 2024 18:53
1e8aca8
to
df6b94a
Compare
Bencher
🚨 2 ALERTS: Threshold Boundary Limits exceeded!
Click to view all benchmark results
Bencher - Continuous Benchmarking View Public Perf Page Docs | Repo | Chat | Help |
Bencher
Click to view all benchmark results
Bencher - Continuous Benchmarking View Public Perf Page Docs | Repo | Chat | Help |
Bencher
🚨 1 ALERT: Threshold Boundary Limit exceeded!
Click to view all benchmark results
Bencher - Continuous Benchmarking View Public Perf Page Docs | Repo | Chat | Help |
Bencher
🚨 8 ALERTS: Threshold Boundary Limits exceeded!
Click to view all benchmark results
Bencher - Continuous Benchmarking View Public Perf Page Docs | Repo | Chat | Help |
GitGab19
approved these changes
Aug 1, 2024
Merged
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.
fix #1079
this PR simply reorders the sequence between
upstream_sv2::Upstream::parse_incoming
andupstream_sv2::Upstream::setup_connection
insideJobDeclaratorClient::initialize_jd
Upstream::parse_incoming
only callshandle_message_mining
, which is not able to handle aSetupConnection.Success
(because it belongs to the "Common Messages" category, not "Mining Messages")