-
Notifications
You must be signed in to change notification settings - Fork 227
Add support for tornado.web #661
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
Conversation
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.
Great stuff so far!
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.
I like the creates_transactions
flag! Good idea. And great job on adding sorely needed comments to AbstractIntrumentedModule
!
just a couple more comments :) I'll stop reviewing now until you think it's ready for review
Since vscode invokes flake8 with a full path on save, the excludes weren't being observed. The /** format seems to fix the issue
Makes it easier to see my own notes for this PR independent of existing TODOs in the project
Also fix a couple of small typos
This is code complete. I need to work out our support matrix, fix up the test suite (for |
The primary instrumentation point, tornado.web.RequestHandler._execute, is `async def` in 6.0, and `def` with `@gen.coroutine` in 5.0. I'm not sure how to decorate both at the moment, so until a community member asks we can just support 6.0+
This is ready for review! We only support tornado 6.0+ (see reasons here. @beniwohli I'm not sure what's going wrong with the tests -- I added all the exclusions to the jenkins-exclude file, but I'm still getting a bunch of syntax errors in non-3.7 tests due to |
@basepi the SyntaxErrors are due to pytest's test discovery. Even when excluded via Jenkins excludes, pytest will still cause Python to parse the code. You have to tell pytest to ignore the the code. We currently do this for all files that are prefixed with Lines 11 to 13 in 721601e
If you move the Tornado tests into I'll do a proper code review on Monday :) |
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.
Awesome work!
Pretty sure the remaining test failures are the same ones as are failing on |
@basepi I think most failures are due to an import error: https://apm-ci.elastic.co/blue/organizations/jenkins/apm-agent-python%2Fapm-agent-python-mbp/detail/PR-661/19/pipeline/158#step-1296-log-1482 Looks like you might need to move the import of |
Good catch. I saw those client errors and stopped reading before I got to the "good ones." Fixed now, I think. |
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.
Docs look good. Sorry for the delay!
Co-Authored-By: Brandon Morelli <[email protected]>
Co-Authored-By: Brandon Morelli <[email protected]>
Awesome work getting this done @basepi! |
Figured I'd open a draft even though this is barely more than a skeleton so far.
What does this pull request do?
Adds Tornado support (or it will, anyway, once it's done)
Related issues
Refs #598