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
added integration with aiohttp #18
added integration with aiohttp #18
Conversation
Hey Alexander, that was fast. Awesome. While I didn't yet review this change, looking at the failed checks, I think many of them because the If Also, pylint is complaining that Thanks |
Thank you for your help @michaelyaakoby. The commented steps solved the issue relative to CI. The code base of the project is cohesing and I would really like to use this feature in an application in my work. |
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.
Hi Alexander,
We are very excited to get this in - its really awesome.
One thing I'm missing is adding aiohttp to the tests/test_pyctuator_e2e.py
.
I've cloned your branch and have added this myself.
Not sure what's the preferred way of sharing this with you so you can add to your branch.
Shoud I create a PR? or send you a patch?
Hi @amenezes , I've created a pull-request to your repo adding aiohttp to E2E test. |
Extend E2E to ru all tests when pyctuator is using aiohttp server
Sorry for delay @michaelyaakoby I made merge with your PR but now some error is happening with the aiohttp tests. |
@amenezes, the failures seem like issues in |
Fix E2E, aiohttp_test_server.pytest used starllet by mistake
Hi @amenezes I'm merging this to a branch where I'll add the E2E fix (which I sent you earlier this week) and we should release shortly. |
Added initial integration with aiohttp #17.
@MatanRubin would you rather I use the notation below to fix the pylint warning or is there any other?