GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

Set is_padding_timer_scheduled to 0

When calling `circpad_send_padding_cell_for_callback()`, the flag
`is_padding_timer_scheduled` was not resetted to 0 which caused an issue
in the circpad simulator.
This commit fixes this problem.

Fixes #32671.
9 jobs for #32671-circpad-padding-timer in 0 seconds (queued for 114 minutes and 30 seconds)
latest
Status Job ID Name Coverage
  Test
failed #4003
debian-disable-dirauth

failed #4004
debian-disable-relay

failed #3999
debian-distcheck

failed #4000
debian-docs

failed #3998
debian-hardened

failed #4001
debian-integration

failed #3997
debian-minimal

failed #4005
debian-nss

failed #4002
debian-tracing

 
Name Stage Failure
failed
debian-nss Test There has been a timeout failure or the job got stuck. Check your timeout limits or try again
No job log
failed
debian-disable-dirauth Test There has been a timeout failure or the job got stuck. Check your timeout limits or try again
No job log
failed
debian-disable-relay Test There has been a timeout failure or the job got stuck. Check your timeout limits or try again
No job log
failed
debian-tracing Test There has been a timeout failure or the job got stuck. Check your timeout limits or try again
No job log
failed
debian-docs Test There has been a timeout failure or the job got stuck. Check your timeout limits or try again
No job log
failed
debian-distcheck Test There has been a timeout failure or the job got stuck. Check your timeout limits or try again
No job log
failed
debian-integration Test There has been a timeout failure or the job got stuck. Check your timeout limits or try again
No job log
failed
debian-minimal Test There has been a timeout failure or the job got stuck. Check your timeout limits or try again
No job log
failed
debian-hardened Test There has been a timeout failure or the job got stuck. Check your timeout limits or try again
No job log