[object Object]. Break it too.
-
Composer window:
After resizing and entering some text:Chrome 43.0.2357.134 m, Windows 8.1
Hard refresh hasn't fixed it
-
Chrome 43 in Windows 7, no repro.
Are you using the desktop version or the app-metro-whatever version?
-
it looks like your browser had on to many feminine cocktails ...
-
-
Hey guess what
Clearly it's a triggered thing. I blame replying to Accalia
-
me too. Chrome Version 43.0.2357.134 m
-
Clearly it's a triggered thing. I blame replying to Accalia
i cause jellypotato?
(also i get this as well now. not good!)
-
-
-
-
My tab that's been open since ~ an hour ago doesn't have this, but I just opened a new tab and the composer is broken. So yeah, probably upgrade.
-
-
Also happens in Discourse default
-
Double-yoo-tea-eff?
-
Also likely upgrade related:
'd
-
doing a hard refresh seems to fix it...
maybe?
-
Oh come on.
-
@PJH just posted the latest update notes to the Docker thread
-
Sounds like some kind of weird song?
-
Changelog: jellypotato?
-
It seems that the structure of the UI has changed (again!), and the upgrade process didn't make the switch clean
-
Do a hard refresh; it seems to have sorted itself out now
-
It fixed itself without hard refreshing so I thought it may have had to do with live-updating posts, but they seem fine now as well. Must have been a temporal bug.
-
-
I would even say I got
-
Upgrade (eventually, after a restart) finished.
Try hard-refresh, and..
"Five to one against and falling..." she said, "four to one against and falling...three to one...two...one...probability factor of one to one...we have normality, I repeat we have normality." She turned her microphone off — then turned it back on, with a slight smile and continued: "Anything you still can’t cope with is therefore your own problem."
Or ours.
-
Ahh, that explains all the "Blah it too" links appearing: they are no longer supported, and it's all folded into that button. Would've been nice to ... something, I dunno, trigger a hard refresh server-side, or at least not break the client during the update?
-
Would've been nice to ... something, I dunno, trigger a hard refresh server-side, or at least not break the client during the update?
That's like expecting Discourse to work
-
didn't discourse used to put a modal up when it upgraded asking if you wanted to refresh to the new version?
-
It used to put it off as long as possible, waiting for you to change topics or onblur or some other context switch and automatically refresh at that time, only popping up that modal when you've been active on a tab without changing topics for several hours.
In this case, "as long as possible" was "less than a few minutes", but no modal appeared.
-
I've seen that modal appear without having to do anything; I guess the trigger came over messagebus. Didn't see it at all this time though.
-
I was just going to report this. A hard-refresh of the page didn't make it go away. It wasn't all posts either, just most of them.
I had to close and reopen Firefox, I have about 800 tabs open and there is probably another Discourse one among those, would that do it?
-
that would be the period where the server is on the new code, but the new JS files are still being compiled, bundled, and minified. The "asset-version update" message is only sent after that's complete.
-
Surely the compilation, bundling, and minification should be done before the new HTML is served? That would avoid the mismatch we had in the last upgrade.
-
-
Goldblum?
-
Well, he is known for writing a piece of software that destroyed an entire alien invading force.
-
Well, he is known for writing a piece of software that destroyed an entire alien invading force.
No, his software just took down their shields. The fighter squadrons still had to find a weak point.
-
that would be the period where the server is on the new code, but the new JS files are still being compiled, bundled, and minified. The "asset-version update" message is only sent after that's complete.
Interesting, thanks for the explanation.
-
that would be the period where the server is on the new code, but the new JS files are still being compiled, bundled, and minified. The "asset-version update" message is only sent after that's complete.
umm...... why is the new server code brought online before the client side stuff is ready where there is always in my experience a breaking change for the previous client version.
-
I.. good question, it's possible I explained it wrong. the processes aren't supposed to restart until it's all done.