Subtle changes, bugs and feedback

@motter, @Velocio, keep getting this error message everytime I try and upload a photo

Server Error
We're sorry, there was a temporary error when we tried to process your request.

The error has been logged. Please try again later.

Click here to go back to the homepage.

using Chrome Version 37.0.2062.124 m on a windows 7 machine

Think I've found a bug with iPhone 6 / ios8 - the burger menu doesn't highlight your choice any more so it looks as if you haven't tapped on it. Same for all pages but I can't remember if they were like that before.

Edit: so in the photo, I've tapped on 'following' and it's loading but the highlight hasn't moved.

1 Attachment

How can bugs be appearing a few weeks in when it worked fine to begin with? Is it just the extra traffic?

^^no photo as I got the same message as above!

There will a few seconds of downtime while I reconfigure the environment.

Edit: looks like attachments work again.

1 Attachment

How can bugs be appearing a few weeks in when it worked fine to begin with? Is it just the extra traffic?

We had issues with timeouts which most of you noticed at some point in the last week. To try and resolve that we had to perform experiments at various levels of our stack, and unfortunately a few of those experiments introduced their own side effects.

Specifically, we use a Python package called requests to make HTTP requests from the front-end to the back-end, and we use a package called grequests to speed this up by making multiple HTTP requests simultaneously.

We updated the grequests at 13:17 on Friday, thinking that this was a likely contender for where the timeout issue was occurring, and the side effect of this is that the version of grequests we updated to failed to send the Content-Type header when attachments were added to multipart forms.

The attachments bug came from that, without the Content-Type we couldn't tell what type a file was, and so couldn't do some essential things (like ensuring we stored the correct mimetype).

Ergo... the timeouts issue led to other changes which had unintended side-effects which then caused new bugs to appear.

We've now rolled those changes back.

As a side note... our unit tests didn't catch this, as our tests that call the API continued to do so with the Content-Type set.

The code is under constant development.

Two separate but related things:

• Why are outgoing links rewritten via http://microcosm.app/out/blah ? What purpose does it serve?

• Could the title HTML attribute of the links include the ultimate target? With the rewriting, you obviously can't tell the "real" href from your browser status bar - including it in the title would bring back part of that.

Why are outgoing links rewritten via http://microcosm.app/out/blah ? What purpose does it serve?

This has been addressed previously, but one benefit is that it allows centralised blocking of malicious urls.

Why can't I post on this thread? It won't give me a reply box.

http://www.lfgss.com/conversations/255868/#reply

Edit, I see that it is a locked thread.

Yup. @arrowplum closed it 15 minutes after starting it.

@Velocio @dancing james what? No I didn't.

what? No I didn't.

Audit log disagrees.

Did you really not?

It's a drop-down on the right-hand side and the process is fairly explicit:

1. Choose "Close" and submit.
   
2. New page loads asking you to confirm by submitting a form, hit submit.
   
   

So it's a two-step "Are you sure?" process, and it definitely used your credentials to close it.

@Velocio I don't even see the option to do that. Where is it? I will unclose it forthwith.

For sure didn't do that... anyway can you open it again?

I've opened it again.

Spooky

This is actually the 2nd time someone didn't close something but something did get closed.

There must be something amiss.

What browser do you use?
And what extensions do you have installed?

https://addons.mozilla.org/closing-threads-about-casual-sexism

looks like attachments work again.

yay

1 Attachment

If you could let me know what browser + extensions you use, that would be great.

@Velocio my browser is chrome Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/38.0.2125.77 Safari/537.36

I still don't see a close option just edit conversation which just allows editing the title.

List of extensions:

• Advanced REST client 3.1.7
  
• Any.do 2.5
  
• Auto Refresh Plus 2.0.6
  
• Bitcasa Everywhere 1.1.1
  
• Caret 1.4.33
  
• Chrome Logger 4.1.0
  
• Clear Cache 1.1.1
  
• DHC - REST HTTP API Client 0.7.1
  
• Disconnect 5.18.14
  
• EXIF Viewer 2.3.1
  
• feedly 34
  
• feedly Mini 34
  
• Google Calendar (by Google) 1.4.7.2
  
• Google Drive Client Native Proxy 1.0
  
• Google Translate 2.0.0
  
• hckr news 1.8.2
  
• Hola Better Internet 1.4.694
  
• JSON Editor 3.1.1.1
  
• JSONView 0.0.32.2
  
• Last.fm Scrobbler 1.40
  
• Markdown Here 2.11.2
  
• MeasureIt! 1.1.3
  
• ModHeader 1.2.4
  
• Mymail-Crypt for Gmail™ 31
  
• New Tab Redirect 3.1.2
  
• Page Benchmarker 1.3.4.0
  
• PageSpeed Insights (by Google) 2.0.4.3
  
• PHP Console 3.0.21
  
• Postman - REST Client 0.8.4.9
  
• Proxy Switchy! 1.6.3
  
• Readability 3.0.15
  
• REST Console 4.0.2
  
• Search by Image (by Google) 1.5.1
  
• Secure Shell 0.8.30
  
• Speed Tracer (by Google) 0.27
  
• Stealthy 3.0.1
  
• Web Developer 0.4.6
  
• WebPG 0.9.4
  
• Xdebug helper 1.4.2
  
• YSlow 3.1.2
  

That is daunting... I suspect one of those to be the cause (silently visiting links behind the page to speed things up perhaps?)... but so many to test!

And when you view the conversation, if it's one you started you'll notice at the bottom of the right-hand bar it says "[Close] [Go]".

I would like to ask / mention again:
When I click on a thread title on my following page, it does not take me to the first unread post of the thread (as it should I think), but "somewhere towards the end", in the middle of a reply I already read - like:

1 Attachment