Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

I've read the intro docs and went through the tutorial and was trying out some Prefect Tasks.  First off was MySqlFetch because, well MySql....  I feel like I've got things setup right but I'm running into an unexpected error in the task runner trying to do a `MySqlFetch.run()`.  :
```ERROR:prefect.TaskRunner:Unexpected error: AttributeError('__enter__',)```
So I didn't want to get into debugging this because my code could be totally wrong.  I was hoping to find some examples of using this and other Prefect Tasks.  Are there examples for how to use this and other tasks?

Hi <@U0189LTLW8G> - I can take a look at the code for that particular task, but a large portion of our tasks are community contributed (including `MySqlFetch`) so the documentation varies

Hey there <@U0189LTLW8G> — looking at the `MySqlFetch` task’s code, it looks like it attempts to enter two different context managers to open a transaction - is it possible that it’s failing to connect, so `conn` is an object like None? That code is <https://github.com/PrefectHQ/prefect/blob/ddd3e685d92b458cf35b4d39a38e6e4865ead1d3/src/prefect/contrib/tasks/mysql/mysql.py#L187|here>.

I’m not sure what pymysql returns as `conn` if the connection fails

Thanks guys for the clues.  It clarifies a lot.

Yes, that is where it's raising the exception.  So it makes sense that something happened on the connection.

Okay, so sorry for the python question here but if I wanted to go ahead and fork/clone/develop the package so I can more cleanly debug...  (and maybe contribute back), what's the trick?

check out these docs on contributing: <https://docs.prefect.io/core/development/overview.html>

Feel free to ask any questions if you get stuck; we also have a channel <#C0106HZ1CMS|prefect-contributors> dedicated to helping both new and seasoned contributors!

Heh!  Thanks Chris!  I had realized I cloned the whole repo setting up the tutorial!  So, I'm off to the races debugging.  That the one exception is handling both pymysql errors AND any other Exception, causes the amgibuity.  It appears the conn is created just fine, but it's got no `__enter__` !  Why not?  Maybe I've got version issues...

Not looking awesome...  <https://stackoverflow.com/questions/31214658/can-i-use-pymysql-connect-with-with-statement>

Lol, Commented out the outer context manager and at least with a valid connection, it's working!

Nice <@U0189LTLW8G>! Sounds like we need to remove the outer context manager - if you’d like to make a PR for this let me know 

I can give it a shot! My hacking is pretty good, my polishing...  Well, that's the hard part!  :slightly_smiling_face:

Haha no worries - we can work with you and provide suggestions :+1:

<@UKNSNMUE6> Hey, so I'm stepping into this very very lightly as I'd love to help but I've got a lot going on...  I went ahead and forked and branched and tweaked the code a bit.   I tried to push for more coverage and built dummies rather than mocks (for pymysql), and I've run black and mypy on it.  I also realized that in core, you've got the postgres version which looks identical.  If you want, I can make a PR (to what branch) or you can review and or take it from here or whatnot?  If there's no rush, then let me know and I'll see when I've got another shot at responding to comments!  :slightly_smiling_face: Thanks for the nudge.  <https://github.com/PrefectHQ/prefect/compare/master...ijames:contrib-mysql-fix-context-manager?expand=1>