Repository navigation
update - #431
Open
itsmylife44 wants to merge 3352 commits into
Open
update#431itsmylife44 wants to merge 3352 commits into
itsmylife44 wants to merge 3352 commits into
Conversation
Contributor
|
It is the biggest pull request in one hit that I have ever seen in Github. 🙈 To the moon 🚀. |
|
These changes will work on latest snipa pool if I add them? what is best way to implement them? it will work for Aeon still? I am worried about DB changes |
Contributor
|
It works with Aeon, of course. Aeon is a sibling of Monero, much simpler than other coins. |
MoneroOcean
force-pushed
the
master
branch
2 times, most recently
from
August 11, 2018 07:49
c8f6dd3 to
3f45f35
Compare
MoneroOcean
force-pushed
the
master
branch
2 times, most recently
from
January 10, 2019 18:32
8aa7251 to
054f3e1
Compare
Resolve current release metadata before reusing digest-verified archives, reject unsafe archive links, and support explicitly pinned MoM release tags. Keep Pearl GPU coverage opt-in and fail MoM cases with missing accepted shares. Track and close only owned miner descendants, distinguish forced cleanup from a passing run, and keep raw logs private. Add archive, process identity, cleanup, and privacy regression coverage.
GitHub runners may retain a zombie after a fixture child exits. Assert that the original process identity is no longer running instead of requiring immediate removal from procfs. Capture its birth identity before shutdown so fixture cleanup cannot target a reused PID.
Credit server-normalized work once after all Pearl proof and claim checks pass, scoped to the canonical payout trust key. Trusted shortcuts and rejected or incomplete verification do not earn wallet trust. Guard credit against completed shares, invalid work, overflowing totals, repeated verifier callbacks and replay. Add coverage for payout isolation, full-verification boundaries and subsequent trust invalidation.
This reverts commit 526c20c.
Reuse the existing temporary IP bans for worker-limit rejections and invoke TLS connection handlers only after admission succeeds. Preserve whitelist and loopback exemptions and the original bounded delayed-reply handling. Select direct worker acceptance before forking so the primary cannot queue unbounded accepted sockets while workers are busy. Close final replies after flushing, with a hard deadline to prevent half-open peers retaining sockets. Cover ban propagation, rejected TLS dispatch, session resumption, reply limits, stalled writes, half-open clients, and acceptance policy ordering.
This file contains hidden or 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
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.
No description provided.