-
Notifications
You must be signed in to change notification settings - Fork 190
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
Avatar is not being sent when there's an ongoing file transfer to contact #39
Comments
@kehugter I believe avatars are just another form of file transfers. Since the previous api break (the new tox api from quite a while ago, not the toxav api that was merged recently), there can only be one filetransfer to one contact in one direction at a time. So that means your avatar will get sent only after the filetransfer is done. tl;dr - toxcore "works as intended" behavior |
and there is no rush to get new avatar, when file sending ends then avatar goes. |
This is incorrect. uTox will support 64 active file transfers, with 32 in each direction. @kehugter I've read your issue a few times and I'm having trouble understanding what the problem with uTox is... Is uTox not sending the avatar when there's a FT in progress? Or is qTox simply not accepting the FT? |
works as it should in uTox, this is a qTox only issue... If I'm wrong I need some more information as I couldn't dup this one. |
Ok, tried it from uTox to uTox and could reproduce. Both instances in Linux, the Steps:
I couldn't get more than one active. |
@kehugter I'm going to need the debug output from both... |
Test scenario for the original issue, ie, sending a file and updating the avatar.
Some unrelated info from other friends in Perhaps interesting fact: after pausing, all pending avatars are updated, one after the other. |
OH... yeah... I understand what's going on. @LittleVulpix is correct, toxcore tries to finish files in order, and an avatar is just a file as far as toxcore is concerned, so it just waits until it's turn... Open this issue at https://github.com/irungentoo/toxcore/issues/ |
Ok, thanks all! |
Fom qTox/qTox#1702:
Tested with the latest uTox binaries against latests qTox binaries and can reproduce.
Could you confirm that this is indeed not a uTox bug?
The text was updated successfully, but these errors were encountered: