Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
sbws
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
juga
sbws
Commits
bef6c7c6
Commit
bef6c7c6
authored
6 years ago
by
Matt Traudt
Browse files
Options
Downloads
Patches
Plain Diff
Ignore an error if a circuit disappears before we try to close it
parent
dc63ad05
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
sbws/lib/circuitbuilder.py
+7
-3
7 additions, 3 deletions
sbws/lib/circuitbuilder.py
with
7 additions
and
3 deletions
sbws/lib/circuitbuilder.py
+
7
−
3
View file @
bef6c7c6
from
stem
import
(
CircuitExtensionFailed
,
InvalidRequest
,
ProtocolError
)
from
stem.control
import
(
CircStatus
,
EventType
)
from
stem
import
CircuitExtensionFailed
,
InvalidRequest
,
ProtocolError
from
stem
import
InvalidArguments
from
stem.control
import
CircStatus
,
EventType
import
random
import
time
import
sbws.util.stem
as
stem_utils
...
...
@@ -175,7 +176,10 @@ class CircuitBuilder:
return
for
circ_id
in
self
.
built_circuits
:
if
c
.
get_circuit
(
circ_id
,
default
=
None
):
c
.
close_circuit
(
circ_id
)
try
:
c
.
close_circuit
(
circ_id
)
except
InvalidArguments
:
pass
self
.
built_circuits
.
clear
()
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment