<IMG> height attribute doesn't work...
-
Test failed:
Wait a second …
/looks closely
Never mind. It wasn't fixed when I first looked, but the images were correctly scaled by the time I took the screen cap, I wasn't paying attention.
It looks fixed to me, given the original issue was that all three images would end up the same width, even though it's set different on all three images
That's my bad. Apparently there was a sidekiq job issue combined with me not paying attention to changes.
-
Fixed in the serverside bakery but not in the clientside one?
-
The server-side one is more important, as that's what gets stored in the DB
-
The topic on meta has been closed as "This should be fixed".
Read as "is probably fixed".
and they did a complete reset on test
Which should have been happening every 24 hours.
looks at the fix implemented
It took FIVE MONTHS for that simple a fix?
It was a "none of the developers really care all that much" issue.
-
Admittedly, it's a rather contrived scenario
-
@abarker said:
and they did a complete reset on test
Which should have been happening every 24 hours.
Well, they were resetting from test2.discourse.org, I discovered. So I had created an account on test2 and the resets were importing my account so that I didn't need to recreate it every day. Apparently, they decided to wipe out test2 at some point. :/
-
try2 not test2
-
Ah, whatever it was. I was working from memory as I had done it all several months back and then done nothing more than was necessary to activate my account and get to TL1. The odd thing is, my account on try2 still exists, but my account at test doesn't. They must have refreshed test some other way.
-
Fixed in the serverside bakery but not in the clientside one?
What's your os/browser combo? It should be trivial to fix.
-
linux/chrome, linux/firefox, windows/firefox. But I was really making conjecture on @abarker's observations and I don't know his platform.
-
The odd thing is, my account on try2 still exists, but my account at test doesn't. They must have refreshed test some other way.
test.discourse.org was never intended for public consumption, it's part of the build process. looks like we'll be moving it behind the VPN shortly...
-
test.discourse.org was never intended for public consumption, it's part of the build process. looks like we'll be moving it behind the VPN shortly...
Huh. Ok …
-
Seems a bit odd it was ever exposed to the public in the first place
-
Guessing it was a problem with the automated HAProxy config generation? not really sure, no need to look into it anyways
-
You have a pretty thing on http://404.discourse.org/ ...
But why not on http://www.discourse.org/404 ?
-
-
-
Checked that yesterday, all was fine.
-
For posterity.
-
-
It rained today
-
Oh, bonus!!!
Failed to load resource: the server responded with a status of 500 (Domain Not Found)
500 (Domain Not Found)
500 (Domain Not Found)
-
-
I remember this one time when it didn't
-
Snow?
-
That was the other time ;)
-
Snow?
Mere snow does not mean that it does not rain at the same time. Bloody miserable when they occur together it is too.
-
I see you also fell victim to the bogus HSTS redirects, then? The 500 is from Fastly.
To figure out if you're a victim, try to load this page: http://cdn.discourse.org/meta/images/emoji/twitter/sob.png
Expect results similar to this:
-
-
and that is going into my folder of memes for later.
-
-
-
-
Mere snow does not mean that it does not rain at the same time.
But saying that there was a day without rain says that there was no simultaneous snow and rain that day.
-
-
huh.