Of course, thanks for the project proper :).
I'm not really up to speed on who's maintaining this stuff actively but thanks for looking, hopefully another maintainer will swing by.

Currently nobody is very active here. If you have any interest into digging into this it would be much appreciated.

Well I would like file uploads... I will have to find some time to tinker with the test suite.
Unfortunately I'm totally new to using tox so I have a bit of reading to do I think.

@jacobtomlinson So I think I figured out why the test suite is bombing out completely(or at least narrowed it down)
Something in the latest minor of pytest-asyncio breaks the pytest suite. pinning it to <0.22.0 allows the test suite to run again.
However now that I've figured that out I've uncovered some more info about slack file uploads....
https://github.com/slackapi/python-slack-sdk/releases/tag/v3.19.0
So it seems that the old way of file uploading is going away. There's this new three endpoint dance you have to do to upload the file...great.

   1. Call WebClient#files_getUploadURLExternal() method to receive a URL to use for each file
   2. Perform an HTTP POST request to the URL you received in step 1 for each file
   3. Call WebClient#files_completeUploadExternal() method with the pairs of file ID and title to complete the whole process, plus share the files in a channel

they've provided a wrapper method for this whole dance called files_upload_v2
So I guess my question at this point is what is your expectation here, should I be adding the explicit calls for each step(plus tests) to perform the file upload? Or if I can utilize the wrapper, would it be sufficient to create a mock for the method and assert the parameters are correct?

So I went through the bother of setting up a test workspace for slack and I'm running my opsdroid build from this branch and it seems like the v2 file upload thing works, at least for simple text snippets. I'm still trying to figure out how to get the thread reply working though

In many projects I've switched from pytest-asyncio to pytest-anyio and just disabled the trio backend. It should just be a case of changing which package is installed and then adding a fixture to configure the backend.

haven't heard of anyio before...more reading :)

@jacobtomlinson so the anyio swap was a little more work than adding a fixture but...ci is almost all green.
I am not sure why the windows builds don't pass yet though unfortunately.

I made some decisions to avoid fully reworking all the event loop references in the project into anyio friendly code for the sake of trying to keep this PR to a reasonable size, but I did have to do something to stop the yelling about accessing the event loop.

This probably still needs a bit of cleanup and I guess I also have docs to update too now assuming this is a step in the right direction

Thanks for taking the time and pushing things forwards here.

I'm also not sure what is going on with the Windows failures.

For the docs builds it looks like the config for ReadTheDocs is out of date. Hopefully it should be a small config tweak to get it working again.

Read the docs stuff was deprecated, what a surprise :)... Recommonmark project recomends transitioning to myst parser so...I transitioned to myst parser. There may be some slight differences I haven't noticed but the latest _build output I looked at seemed alright.

Alright read the docs is green

🥳