Need to refresh to reply
-
I remember someone talking somewhere about needing to refresh before they could reply. It just happened to me and I couldn't find a topic in Bugs, so here one is.
I opened up the js console and saw this error:
-
@boomzilla said in Need to refresh to reply:
I remember someone talking somewhere about needing to refresh before they could reply. It just happened to me and I couldn't find a topic in Bugs, so here one is.
I opened up the js console and saw this error:
Yup, the need to refresh to reply happens to me every 30-70 topics or so. I can always tell it is going to happen too, because the reply form takes MUCH longer than usual to load, and/or I have to press "reply" twice.
-
If you guys just opened topics in new tabs, the way that nature intended, you wouldn't have these problems. :P
-
Flag for trolling without a toll trigger warning.
-
@abarker said in Need to refresh to reply:
If you guys just opened topics in new tabs, the way that nature intended, you wouldn't have these problems. :P
-
@abarker said in Need to refresh to reply:
If you guys just opened topics in new tabs, the way that nature intended, you wouldn't have these problems. :P
I always do that. I still had to CTRL-F5 in order to make this reply.
-
Happens a lot for me.
-
@Lorne-Kates I got it a few times today, and noticed some occasional sluggishnesh. Was awful a little bit ago. I complained to @ben_lubar on IRC and he ssh'd into the server. One NodeBB process was using 25% of total RAM for some reason so he restarted it and now it seems snappy again.
-
@boomzilla said in Need to refresh to reply:
@Lorne-Kates I got it a few times today, and noticed some occasional sluggishnesh. Was awful a little bit ago. I complained to @ben_lubar on IRC and he ssh'd into the server. One NodeBB process was using 25% of total RAM for some reason so he restarted it and now it seems snappy again.
I would make a quip about nodeBB being trwtf, but frankly .NET worker threads cause the exact same issues sometimes.
Sidenote, I had to reload to post this :D
-
WTF are you all doing to run into this issue? I've never once had to refresh to post.
-
I think I had this in official likes topic, and it also applied to hamburger menu and all other buttons.
[edit] and now it works in this topic.... I wonder if it has to do with people posting while you are replying or editing. Too lazy to test...
[edit2] nope. But some nice jellypotato.
[edit3] but also on iPad, so that's different.
-
@abarker said in Need to refresh to reply:
WTF are you all doing to run into this issue? I've never once had to refresh to post.
Nothing. I load up a page, read it as per usual, and sometimes when I click reply, it does nothing. When I click it again, it loads up, slowly, but the submit button does nothing. Only reloading the page fixes it.
-
-
@abarker said in Need to refresh to reply:
I've never once had to refresh to post.
I've had it happen maybe once or twice, where the submit button goes inactive because something timed out. Other people have mentioned it before--I'm not sure it's the same thing is what's going on in this thread.
-
I suspect it's probably related to the cooties we were having yesterday (and possibly on other days, of course).
-
Usually happens on mobile for me. Also, it does seem to work eventually but it takes a good minute for it to respond usually.
-
@abarker said in Need to refresh to reply:
WTF are you all doing to run into this issue?
All I'm doing is opening threads in new windows, the way nature intended.
-
@PJH said in Need to refresh to reply:
@abarker said in Need to refresh to reply:
WTF are you all doing to run into this issue?
All I'm doing is opening threads in
newwindows, the way nature intended.When I do that the police gets called.
-
More debug from a page where clicking edit on a post failed to do anything (yes, I know not all of these refer to nodebb)
In text form:
TypeError: e.topic is undefined nodebb.min.js:14:1 TelemetryStopwatch: requesting elapsed time for nonexisting stopwatch. Histogram: "FX_PAGE_LOAD_MS", key: "null" TelemetryStopwatch.jsm:297:0 mutating the [[Prototype]] of an object will cause your code to run very slowly; instead create the object with the correct initial [[Prototype]] value using Object.create nodebb.min.js:9:26109 Use of getPreventDefault() is deprecated. Use defaultPrevented instead. 184 scheduling request of counters... index.php:346:150 ?op=rpc&method=getAllCounters&seq=1925&last_article_id=316712 index.php:347:65 This site makes use of a SHA-1 Certificate; it's recommended you use certificates with signature algorithms that use hash functions stronger than SHA-1.[Learn More] shabble.co.uk PluginHost::run 9 index.php:626:79 TypeError: e.topic is undefined nodebb.min.js:14:1 scheduling request of counters... index.php:346:150 ?op=rpc&method=getAllCounters&seq=1926&last_article_id=316712 index.php:347:65 TypeError: e.topic is undefined nodebb.min.js:14:1 PluginHost::run 9 index.php:626:79 TypeError: e.topic is undefined nodebb.min.js:14:1 Use of attributes' nodeValue attribute is deprecated. Use value instead. base.js:1261:0 TypeError: e.topic is undefined nodebb.min.js:14:1 : cb=gapi.loaded_0:88:0 scheduling request of counters... index.php:346:150 ?op=rpc&method=getAllCounters&seq=1927&last_article_id=316712 index.php:347:65 PluginHost::run 9 index.php:626:79 TypeError: e.topic is undefined nodebb.min.js:14:1
-
Still happening, this time I got a stack trace in the error console.
TypeError: e.topic is undefined
a()
nodebb.min.js:14
[38]</i.prototype.emit()
nodebb.min.js:5
[34]</p.prototype.onevent()
nodebb.min.js:5
[34]</p.prototype.onpacket()
nodebb.min.js:5
[37]</t.exports/<()
nodebb.min.js:5
[38]</i.prototype.emit()
nodebb.min.js:5
[32]</d.prototype.ondecoded()
nodebb.min.js:5
[37]</t.exports/<()
nodebb.min.js:5
[15]</i.prototype.emit()
nodebb.min.js:4
[47]</p.prototype.add()
nodebb.min.js:5
[32]</d.prototype.ondata()
nodebb.min.js:5
[37]</t.exports/<()
nodebb.min.js:5
[15]</i.prototype.emit()
nodebb.min.js:4
[3]</</p.prototype.onPacket()
nodebb.min.js:4
[3]</</p.prototype.setTransport/<()
nodebb.min.js:4
[15]</i.prototype.emit()
nodebb.min.js:4
[4]</r.prototype.onPacket()
nodebb.min.js:4
[8]</u.prototype.onData/n()
nodebb.min.js:4
[19]</</n.decodePayloadAsBinary/<()
nodebb.min.js:5
forEach()
self-hosted:232
[19]</</n.decodePayloadAsBinary()
nodebb.min.js:5
[19]</</n.decodePayload()
nodebb.min.js:5
[8]</u.prototype.onData()
nodebb.min.js:4
[7]</</l.prototype.doPoll/<()
nodebb.min.js:4
[15]</i.prototype.emit()
nodebb.min.js:4
[7]</</u.prototype.onData()
nodebb.min.js:4
[7]</</u.prototype.onLoad()
nodebb.min.js:4
[7]</</u.prototype.create/t.onreadystatechange()
-
@mott555 Also, seems like I have to refresh anytime I want to post anything. However, once I have a successful post that tab is good to post again without a refresh. But I Tab All The Links™ so I run into this all the time.
I'm using Waterfox 46.0.1 which is just Firefox compiled for 64-bit.
-
@mott555 said in Need to refresh to reply:
Also, seems like I have to refresh anytime I want to post anything. However, once I have a successful post that tab is good to post again without a refresh. But I Tab All The Links™ so I run into this all the time.
Having actually looked for when this happens, this is exactly what I run into - I cannot post unless the page has been refreshed since opening.
-
I have once again confirmed this happens (to me) more often than not.
There's nothing in the console.
-
@PJH I find it sometimes happens to me if I try to use the keyboard shortcut, but I don't recall any time when clicking the button didn't work
-
E_REPRO
-
@boomzilla said in Need to refresh to reply:
I remember someone talking somewhere about needing to refresh before they could reply
It might have been me.
@boomzilla said in Need to refresh to reply:
It just happened to me and I couldn't find a topic in Bugs,
It happens to me every single time. I don't always have the error in the console that you have but sometimes I do.
-
@abarker said in Need to refresh to reply:
If you guys just opened topics in new tabs, the way that nature intended, you wouldn't have these problems
That's a lie! I do open topics in new tabs.
Incidentally, it seems the second reply without a reload works okay. At least, it did for this reply.
-
As I noted elsewhere, this also seems to affect the FF <details> shim, in that it won't work until the page is refreshed.