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 rebased #997

Conversation

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

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

No description provided.

@coveralls
Copy link

@coveralls coveralls commented Apr 30, 2019

Pull Request Test Coverage Report for Build 4918

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage decreased (-62.4%) to 0.0%

Totals Coverage Status
Change from base Build 4913: -62.4%
Covered Lines: 0
Relevant Lines: 0

💛 - Coveralls

* Return true if padding is allowed by torrc and consensus.
*/
STATIC bool
circpad_is_padding_allowed(void)
Copy link
Member

@asn-d6 asn-d6 May 2, 2019

No need to have circpad as a function name prefix since it's a private function to this file.

Copy link
Contributor Author

@mikeperry-tor mikeperry-tor May 7, 2019

a151032 does this (and fixes the CI error)

if (circpad_padding_disabled || !get_options()->CircuitPadding) {
return 0;
}

Copy link
Member

@asn-d6 asn-d6 May 2, 2019

We can also pull in

  /* Don't schedule padding if we are currently in dormant mode. */
  if (!is_participating_on_network()) {
    log_info(LD_CIRC, "Not scheduling padding because we are dormant.");
    return CIRCPAD_STATE_UNCHANGED;
  }

from circpad_machine_schedule_padding in this function.

Copy link
Contributor Author

@mikeperry-tor mikeperry-tor May 7, 2019

I would like to keep this separate as it requires its own log line and is a different mechanism that causes it to happen.

@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