Closed jameshilliard closed 3 years ago
It looks like the CI needs to be moved to GitHub actions on this one as well. I can probably help with that.
Hmm, looks like it's already on github actions, I see this error however:
Error : .github#L1
actions/checkout@v2, actions/setup-python@v2, actions/checkout@v2, actions/setup-python@v2, actions/checkout@v2, and actions/setup-python@v2 are not allowed to be used in crossbario/txaio. Actions in this workflow must be: within a repository owned by crossbario.
@om26er Get a chance to look at this?
@jameshilliard unfortunately I don't have the permissions to fix that.
So the error you posted seems similar to https://github.community/t/checkout-v2-error-actions-in-this-workflow-must-within-a-repository-owned-by-organization/136315 -- @oberstet should be able to fix that
fwiw, I've changed the setting, but the failed jobs don't start, and I'm not sure what's actually going on / the status:
@oberstet You need to make the change at the organization level. Specifically on this page https://github.com/organizations/crossbario/settings/actions
Here is a related topic on github forums https://github.community/t/checkout-v2-error-actions-in-this-workflow-must-within-a-repository-owned-by-organization/136315/2
@om26er @oberstet Think we could get a new release with this included sometime soon.
@jameshilliard https://github.com/crossbario/txaio/issues/177
We need to explicitely catch
asyncio.CancelledError
as of python3.8 as it now inherits fromBaseException
instead ofException
.As of python3.9 a message can be passed to
Future.cancel()
, add an optional kwarg for that and pass it toFuture.cancel()
when available.Fixes: #166