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

Bug28693+30173+29203 #965

Closed

Conversation

Labels
None yet
Projects
None yet
4 participants
@mikeperry-tor
Copy link
Contributor

@mikeperry-tor mikeperry-tor commented Apr 17, 2019

No description provided.

@coveralls
Copy link

@coveralls coveralls commented Apr 18, 2019

Pull Request Test Coverage Report for Build 4781

  • 12 of 15 (80.0%) changed or added relevant lines in 2 files are covered.
  • 414 unchanged lines in 8 files lost coverage.
  • Overall coverage remained the same at 62.25%

Changes Missing Coverage Covered Lines Changed/Added Lines %
src/core/or/circuitpadding.c 10 11 90.91%
src/app/config/config.c 2 4 50.0%
Files with Coverage Reduction New Missed Lines %
src/feature/hs/hs_common.c 1 83.52%
src/feature/dirauth/shared_random.c 3 85.64%
src/feature/relay/onion_queue.c 8 58.82%
src/feature/dirauth/dirvote.c 9 64.74%
src/feature/dirparse/microdesc_parse.c 10 91.38%
src/feature/nodelist/node_select.c 56 63.21%
src/feature/nodelist/microdesc.c 101 72.11%
src/feature/client/circpathbias.c 226 12.42%
Totals Coverage Status
Change from base Build 4763: 0.0%
Covered Lines: 46203
Relevant Lines: 74222

💛 - Coveralls

Test fixes including memory leak from test allocations.
…arams

Correct and clarify a comment for the reduced_padding_ok flag.
… smaller.

WTF! This passes locally but not in CI... Arg this is so annoying.
@@ -1122,7 +1122,7 @@ circpad_machine_reached_padding_limit(circpad_machine_runtime_t *mi)
* machine condition check happens, but machine checks only happen on
* certain circuit events, and if padding is disabled due to some
* network overload or DoS condition, we really want to stop ASAP. */
if (circpad_padding_disabled) {
if (circpad_padding_disabled || !get_options()->CircuitPadding) {
Copy link
Member

@asn-d6 asn-d6 Apr 25, 2019

Hmm, this seems a bit like overfitting the original purpose of this function, since it was meant to be about rate limiting and not torrc/consensus parameters.

How about we make a new function is_padding_allowed() where we do these new checks, and also call reached_padding_limit() and also call !is_participating_on_network() (see schedule_padding()). Then we can put it on top of circpad_machine_schedule_padding()` and have a cleaner entry check.

Copy link
Contributor Author

@mikeperry-tor mikeperry-tor Apr 30, 2019

Code fixup: cda6178
Test fixup: 8a1fcbc

@torproject-pusher torproject-pusher deleted the branch torproject:master May 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment