Skip to content
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

Eva: InvalidStateError after the most latest refactoring #6890

Closed
drew2a opened this issue May 2, 2022 · 0 comments · Fixed by #6891
Closed

Eva: InvalidStateError after the most latest refactoring #6890

drew2a opened this issue May 2, 2022 · 0 comments · Fixed by #6891
Assignees
Milestone

Comments

@drew2a
Copy link
Contributor

drew2a commented May 2, 2022

self = <accdfl.util.eva.transfer.outgoing.OutgoingTransfer object at 0x12192c760>

    def finish(self, *, result: Optional[TransferResult] = None, exception: Optional[TransferException] = None):
        if self.finished:
            return
    
        if exception:
            self.logger.warning(f'Finish with exception: {exception.__class__.__name__}: {exception}|Peer: {self.peer}')
            self.future.set_exception(exception)
    
            # To prevent "Future exception was never retrieved" error when the future is not used
            self.future.exception()
    
            if self.on_error:
                asyncio.create_task(self.on_error(self.peer, exception))
    
        if result:
            self.logger.debug(f'Finish with result: {result}')
>           self.future.set_result(result)
E           asyncio.exceptions.InvalidStateError: invalid state

../../util/eva/transfer/base.py:59: InvalidStateError
@drew2a drew2a added this to the 7.13.0 June milestone May 2, 2022
@drew2a drew2a self-assigned this May 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

1 participant