Earlier quoted context omitted.
Seems to be more than that. Even slack.com in an incognito browser fails.
What does an incognito browser have to do with anything?
That means it's not a user auth error
Slack is down
151–160 of 840 posts
Re: Slack is down
#152Earlier quoted context omitted.
I would bet it's just the influx of traffic post holiday with systems that haven't been updated in so long maybe some annoying memory leaks have crept up and gone unnoticed or some other bad state that was exacerbated by return to work day for most NA folks. Code freezes were good at identifying bugs that only show up after long periods. Doubt anyone releasing big changes Monday morning.
I haven't worked at Slack, so I can't speak with high confidence. A traffic spike is a possible reason, but I'm willing to bet that it's not the reason: > Doubt anyone releasing big changes Monday morning. This is definitely an engineering best practice, and by best practice, I mean something that Uber's, I mean Slack's SRE team strongly pushed for, and got politely overruled on. After a code freeze is lifted, it's q…
In my experience it's not promotion-eager engineers that want to push after a code freeze, it's antsy product managers. YMMV tho.
Re: Slack is down
#153Earlier quoted context omitted.
Seems to be more than that. Even slack.com in an incognito browser fails.
What does an incognito browser have to do with anything?
An incognito browser would ignore all client-side cookies, so the Slack web client would not try to - say - resume a previous user's session or re-use any previously saved data.
Likewise, incognito mode will also ignore most cached web content, meaning all assets on the Slack web app will get loaded again from scratch. This "clean state" start could, theoretically, get around issues with old - potentially incorrect/outdated - assets being loaded, even though that really shouldn't happen under most circumstances.
Re: Slack is down
#154oh good, it's not just me and my already bad first day of the year... is it too early to start drinking?
You should probably ask Jimmy Buffett
Re: Slack is down
#155Maybe we can chat with coworkers here. Is there a Carl around?
I have tried to sell my organisation on a shared Google Chat doc for 90s style realtime ICQ chat in times like these, but there has been little uptake.
Re: Slack is down
#156Earlier quoted context omitted.
I would bet it's just the influx of traffic post holiday with systems that haven't been updated in so long maybe some annoying memory leaks have crept up and gone unnoticed or some other bad state that was exacerbated by return to work day for most NA folks. Code freezes were good at identifying bugs that only show up after long periods. Doubt anyone releasing big changes Monday morning.
I haven't worked at Slack, so I can't speak with high confidence. A traffic spike is a possible reason, but I'm willing to bet that it's not the reason: > Doubt anyone releasing big changes Monday morning. This is definitely an engineering best practice, and by best practice, I mean something that Uber's, I mean Slack's SRE team strongly pushed for, and got politely overruled on. After a code freeze is lifted, it's q…
You just don't deploy something major the first day after a 2 weeks vacation, it does not makes any sense.
Re: Slack is down
#157It's funny that this isn't considered an "Outage" by their status page's standards.
Re: Slack is down
#158Earlier quoted context omitted.
> Maybe status threads are discouraged now They always have been, since they clearly don't fit the guidelines for what a good submission is and usually leave little for interesting discussions. (unlike postmortems of past outages, which often are good)
Yet they are usually incredibly useful for most people here. They should be allowed at least while the event is ongoing.
Agreed, when a major service goes down HN is the most accurate overview, often a useful sanity check when its AWS or Slack size orgs before I open an incident with whichever party.
Re: Slack is down
#159Re: Slack is down
#160Earlier quoted context omitted.
I would bet it's just the influx of traffic post holiday with systems that haven't been updated in so long maybe some annoying memory leaks have crept up and gone unnoticed or some other bad state that was exacerbated by return to work day for most NA folks. Code freezes were good at identifying bugs that only show up after long periods. Doubt anyone releasing big changes Monday morning.
I haven't worked at Slack, so I can't speak with high confidence. A traffic spike is a possible reason, but I'm willing to bet that it's not the reason: > Doubt anyone releasing big changes Monday morning. This is definitely an engineering best practice, and by best practice, I mean something that Uber's, I mean Slack's SRE team strongly pushed for, and got politely overruled on. After a code freeze is lifted, it's q…
Does Uber/Slack not release in CI/CD? At least in backend?
I don't see any need to deploy a big change at once in the software world today. At worst feature gate the thing you want to do and run it in a beta environment, but still push the actual code down the pipeline.