Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Question about exceptions.InvokeTimeoutError #513

Closed
tmr232 opened this issue Jan 6, 2025 · 4 comments
Closed

Question about exceptions.InvokeTimeoutError #513

tmr232 opened this issue Jan 6, 2025 · 4 comments

Comments

@tmr232
Copy link

tmr232 commented Jan 6, 2025

First, just wanted to thank you for this library. It is awesome!

As for the issue - I sometimes get an atproto.exceptions.InvokeTimeoutError when posting, despite the post actually being posted successfully.
As a result, I am currently ignoring this exception. But that might not always work, and I don't know if it always succeeds.
How can I tell whether posting actually succeeded?

Thanks!

@MarshalX
Copy link
Owner

MarshalX commented Jan 6, 2025

Hey @tmr232! My pleasure!

To understand that posting is successful you need to:

  1. pass through send_post without any exception
  2. get the return value from send_post which will contain created post info (URI and CID)

@tmr232
Copy link
Author

tmr232 commented Jan 7, 2025

Thanks for the quick reply!

That's what I thought, so my problem is - the posts get posted even when I get the exception.
Is there a way to avoid duplicate posting in that case? I am really not sure how to approach this.

The exception is visible here - https://github.com/tmr232/cfgbot/actions/runs/12615124139/job/35154824578
And here's the post from that same run - https://bsky.app/profile/cfgbot.bsky.social/post/3lexfq6szgz2j

@MarshalX
Copy link
Owner

MarshalX commented Jan 7, 2025

Oh I see it now. So the request is processed by the server, but client doesn't wait for response anymore. In that case I recommend to increase default timeout for reading. Here is how to do it: #501. And back to the previously described strategy

@tmr232
Copy link
Author

tmr232 commented Jan 7, 2025

Thanks, will do!
I'm closing this issue.
If it still happens, I might reopen.

@tmr232 tmr232 closed this as completed Jan 7, 2025
Repository owner locked and limited conversation to collaborators Jan 22, 2025
@MarshalX MarshalX converted this issue into discussion #525 Jan 22, 2025

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants