Occasional issue: user's folder contents will not always show first time

Submitted by sysmaster01 on Fri, 02/22/2013 - 12:02
Forums: 
Soulseek General Discussion

Well, I wonder if anyone of you guys ever got that issue.

You did as you always did, select a user from your Userlist and browsed him/her.
However, when the Browse window appeared, you might have noticed that some folders appeared empty.

'Ah, simple as that,' you exclaim, 'the folders were just empty on the user's media!'

Hah, no, it's not that simple. Actually, THEY ARE THERE. You just can't see them first time.
Close browse window, and rebrowse same users. Automagically, the folders are now filled up with file entries.

(Vague assumption for the reason of this: user is just at that very moment you're browsing him/her about to get his/her shared folders rescanned. And you're jumping in there in mid-air, hence...)

Submitted by Nir on Sat, 02/23/2013 - 16:38.

I'm unable to reproduce this issue. Is anyone else experiencing it?

thescarletfire's picture

Submitted by thescarletfire on Sat, 02/23/2013 - 18:09.

I'm not able to reproduce this, however sometimes depending on the user's connection, I have to hit browse shares more than once if a timeout occurs. Nothing major, though it always works on the second try.

http://i.minus.com/jQerDBm6HSnV2.JPG

This mainly applies to people who shares a ton of files and I try to browse them over (their) slow connection.

This is not a port issue, it's just probably due to net congestion or some connection hiccup.

Empty folders though I can't say that I've ever seen, sorry.

Submitted by Nir on Sat, 02/23/2013 - 22:37.

Sounds like a timeout issue, i.e. their share doesn't manage to fully transfer before the peer connection times out. There are mechanisms in SoulseekQt that should prevent it from happening between two SoulseekQt clients, but a Soulseek NS client will close its own connection after a while, even if it's still transmitting its own share.

thescarletfire's picture

Submitted by thescarletfire on Sun, 02/24/2013 - 00:20.

Yea, I figured it was somehow NS-related -

People are still using NS - they should be on QT! :)

Submitted by sysmaster01 on Sun, 02/24/2013 - 00:27.

I too think that it only happens with Slsk-NS users.

'Nothing major, though it always works on the second try.'

I can confirm that...never needs a 3rd one or so.