-
Notifications
You must be signed in to change notification settings - Fork 101
Add runner context interrupting #256
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -13,6 +13,7 @@ import ( | |
| "path/filepath" | ||
| "strings" | ||
| "sync" | ||
| "sync/atomic" | ||
|
|
||
| "github.com/go-python/gpython/py" | ||
| "github.com/go-python/gpython/stdlib/marshal" | ||
|
|
@@ -44,6 +45,7 @@ type context struct { | |
| closed bool | ||
| running sync.WaitGroup | ||
| done chan struct{} | ||
| interrupt int32 // atomic; non-zero means KeyboardInterrupt pending | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Using atomic.Int32 here saves mistakes
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Go 1.8, not support this type of atomics @ncw
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good point! I forgot we are still on 1.8. Maybe we should upgrade the minimum requirements. What do you think? |
||
| } | ||
|
|
||
| // NewContext creates a new gpython interpreter instance context. | ||
|
|
@@ -192,6 +194,16 @@ func (ctx *context) ResolveAndCompile(pathname string, opts py.CompileOpts) (py. | |
| return out, nil | ||
| } | ||
|
|
||
| // See interface py.Context defined in py/run.go | ||
| func (ctx *context) SetInterrupt() { | ||
| atomic.StoreInt32(&ctx.interrupt, 1) | ||
| } | ||
|
|
||
| // See interface py.Context defined in py/run.go | ||
| func (ctx *context) CheckInterrupt() bool { | ||
| return atomic.SwapInt32(&ctx.interrupt, 0) != 0 | ||
| } | ||
|
|
||
| func (ctx *context) pushBusy() error { | ||
| if ctx.closed { | ||
| return py.ExceptionNewf(py.RuntimeError, "Context closed") | ||
|
|
@@ -208,6 +220,7 @@ func (ctx *context) popBusy() { | |
| func (ctx *context) Close() error { | ||
| ctx.closeOnce.Do(func() { | ||
| ctx.closing = true | ||
| ctx.SetInterrupt() | ||
| ctx.running.Wait() | ||
| ctx.closed = true | ||
|
|
||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This won't work on windows I think.
We probably only need os.Interrupt anyway, INT and TERM are not generated by the keyboard.
Perhaps see what python3 does with those signals?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"
INT and TERM are not generated by the keyboard." You sure? I thought that INT was called by pressing CTRL+C.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You are right of course. However os.Interrrupt is the same as sigint on Unix machines, so it should cover everything we need