Interesting development, it appears that this is caused by a caching issue with Chrome (latest). switching to a different computer or profile resolves this issue. Suggesting it might be a token issue? odd.
So, nevermind my blabbering. On Thursday, April 21, 2016 at 2:07:21 PM UTC-7, Steve Palacios wrote: > > When using GitLab.com, attempting to visit > https://gitlab.com/gitlab-org/gitlab-ce/issues gives a 500 error. This > seems to be limited to this area only as other links appear to be working > properly. For obvious reasons, a ticket was not created for this. This > issue popped up immediately after the RC1 update applied today. > -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/6bc47790-0656-430e-a2e8-e7f6c8972461%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.