A super annoying bug in SL[Issue Fixed - Sorta]

Question

So I finished writing a 25line explanation for someone in the PHP fix the code thing. And hit post.
I see the post being posted and 2 second later.
[No network connection]
And my post disappears. Wtf?
This is so freaking annoying. I have full network connection (The wifi router is in my room).
This used to happen and still does with saving code in SL and now even with comments.
This is really annoying.
Yeah I know some of are gonna comment "Clear the cache" and all that stuff. That's not what I am supposed to do everytime I am gonna write a comment or post a thread or save a code.
SL please fix it.
I posted about this kind of bug few months ago with the write somethig to your feed thing they introduced and they fixed it. But this age old bug is still here.

I am going to send bug report just wanted to know if you guys still have this issue or not.

Answer 1

Update about the bug:
I logged in and was switching through the tabs and the loading was super smooth and checked the email.
Levon from SL replied that they had fixed the issue. Hope you guys are having no trouble also.

Thanks SL and everyone.

Answer 2

Here's how I handle the bug (android app): immediately after I post a comment, I go to my profile and see if the comment appears in my feed. If it doesn't, it wasn't posted. So I go back to the comment and wait a couple of seconds for a 'try again' button to appear. Hitting the 'try again' button will show your comment again and you can try to post it again (and again and again, until it appears in your feed)

Answer 3

The first thing I do If I am posting a long comment is go copy the comment. After posting I go check on feed if I can see it there. If no I go back and post the copied comment.
But this doesn't work with tagging people...you cannot copy the tags(obvi) ..So i give up after trying 2-3 times.
The bug is extremely annoying.

Answer 4

For me personally, I'm in the habit for composing something first, then copy the entire draft written to clipboard before I submit, this I do for code, Q&A answers and code comments.

And knowing that there's a risk of failed submission I usually waited there (after submitting) for +/- 30 seconds before I leave, just to be sure the submission failure message isn't popping up. So far this works for me.

I'm not sure how SL is doing with the ads or Pro version, are they making "enough" to support the free side of the platform, but I think as a free user (not using Pro feature) I only need to be more patient with things.

Answer 5

SL is facing serious server connection, their server is still not ready for all private message posting, which might take out a lot of bandwidth, they should halt the private message service, until their have a better server, perhaps migrate to cloud server is the better option now.

Answer 6

Calviղ I suspect it's more about the tremendous increase in concurrent requests than it is about bandwidth. This is where scaling strategies would need to be implemented to support spikes in activity and volume.

Answer 7

Copy your msg first before posting, it's what I do.
And yes it's an extremely annoying bug.

Answer 8

This reminds about my old post and it's very unfortunate to see this recurring issue again as it's one of the reason I become less active over here.

The effort required to support the communuties increase every day and I really appreciate those who are willing to contribute their time here. Thank you. 🙇

https://www.sololearn.com/post/6955/?ref=app

Answer 9

Slowlearn

Answer 10

Before you post, copy it. Then if it's not sent, you can paste it. 😃 Until they fix the bug 🐜

Answer 11

Calviղ If only I was able to come in for a top down assessment of the entire software architecture and network topology...

I'm certain there is so much I could do to help.

Building reliable, secure, scalable enterprise applications has been my area of focus for most of my career.

Answer 12

Infinity Top comment.

Answer 13

Sekiro In the android app? That never happened to me (unless I tapped 'cancel')

Answer 14

When I hit back and choose 'save' and it doesn't work, I get the usual 'no connection' message and stay in the code.

That's convenient because it means my code is preserved for the time being; but sometimes I have to repeat the procedure 8, 9 times before it's finally saved.

Answer 15

and the more we post, the less it will be successful :)

Answer 16

yes, I am the same problem on ios and it is really annoying!
Yes ok, as Anna says I can of course do some “tricks” to not loose what I type but it’s not how it should supposed to be and I hope SoloLearn will provide a fix soon.. And it is not limited to only comments, but to code and challenges too, I lost many challenge because of connection problem and even if I gave the right answer the server did not count it...

Answer 17

Calviղ Are you scanning SL network traffic? how did you know the bottleneck issue was triggered by private messages? unless file exchange was allowed (with no size limit), as I understand it text messages don't take that much data (cmiiw).

Answer 18

Ipang The problem is not only how much data the server has to handle. Any time that a client (sl apps) send a request to server (and surely happen on private messages also) a connection between client and server has need to be estabilished. Now, every of that connection estabilishment is not free in resources terms then, adding chat feauture to sl, the sl server is much more loaded respect before (i think)
Thats what Calviղ said

Answer 19

Ipang What I really mean is the concurrent access of the private messages like what David and KrOW mentioned. I found that the network having serious accessible issue since private message started to implement.

David Carroll, if SoloLearn could migrate its server to cloud, it might solve the issue. Cloud server has autoscaling features, which can guarantee the accessibility.

Answer 20

Im ignorant in that field but i think than a client traffic analysis is almost unuseful because it dont get info about how SL handle requests internally... Ergo, for a true analysis of the problem you have to be inside the entire system