-
-
Notifications
You must be signed in to change notification settings - Fork 567
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
bugfix when loading plugins #92
Conversation
e6fcf7a
to
158e27b
Compare
@normal-cock Awesome. Makes sense, this is much better. But why have you deleted |
@abhinavsingh I remove |
0a7434c
to
d48a947
Compare
@normal-cock I am not sure but do you have to enable actions for your account? GitHub actions is relatively new and unsure if it's available for all, but no reason why you can't check into your repository. What errors do you get when you try to commit to your repo? |
d48a947
to
a47076b
Compare
@abhinavsingh The error message when I keep
|
Signup for actions here https://github.com/features/actions and try again. Github actions is a new feature from Github, its surprising that they are refusing you to push into repo. My guess is since you don't have actions enabled, you are unable to push. Can you try and let me know. Thanks |
I've enable actions and the error is still there. @abhinavsingh |
Reading the error message again My guess is, start in a new branch which still contains |
@abhinavsingh The error is unchanged. The phenomena is that only if I delete |
It seems that some has raise this with Github https://github.community/t5/GitHub-Actions/Refusing-to-allow-an-integration-to-create-or-update/td-p/32472. |
Thanks for the find. From that thread:
Did you close using |
@abhinavsingh Cool, it works after I change my origin from |
a47076b
to
08fd63f
Compare
I've change the pr. @abhinavsingh |
Awesome, can you make sure tests are passing. I haven't used |
12990cd
to
82a8e73
Compare
82a8e73
to
31de953
Compare
Kindly |
* Initialize skeleton electron app * Attempt to open devtools * Electron free * Initialize public/devtools * Add basic support for static file serving and chrome devtools. 1. No cache header management for static file serving yet. 2. No chunked encoded responses for static files yet. 3. Chrome Devtool initialization. * Fix static serving with query params * profile using py-spy * Complete websocket client loop * lint check * Add support for building websocket frames * Remove redundant CDT params * Lint check * Refactor web server base plugin name * Devtools integrated, need more polish * Add START_TIME global var * lint fix * Remove outdated chrome rdp * Add FAQs * Add FAQs * socket_connection decorator + context manager * Defer SSL handshake and plugin initialize until protocol handler thread has started. This is a follow up to this PR #111 * Add tests for new_socket_connection and its friend socket_connection * Address an issue which came back after being fixed in #92 * Lint fixes * uff ye str and bytes * Remove explicit flushes outside of write ready descriptor handlers * add links to import proxy * Only try websocket upgrade if a route is registered * Add plugin_examples.WebServerPlugin and use precision logging for levelname * Remove redundant comments * Add --devtools-ws-path flag * Add on_websocket_open and on_websocket_close callbacks * Add empty stubs for incomplete CDT responses * Ensure client is ready before final flush * Shutdown on write side of socket, may be client is still reading * Since client.closed can be set, explicitly call client.connection.closed * Add ModifyPostDataPlugin example. Was first asked and referenced here #115 * Start adding TestHttpProxyPlugin * Fixes #116
The reason why
except HttpProtocolException as e
doesn't work as expected is that the way we load plugin inproxy.py
is improper. We should not import a module itself in it, instead try to useimportlib.import_module("__main__")
.For example, suppose we have a
test2.py
the content of which is as following. The result of the code isFalse
, and that's whyexcept HttpProtocolException as e
doesn't work.