41–50 of 225 posts
Slack is unusable, but it did get me to restart Docker which had ballooned to 16 GB memory and a bazillion processes. Modern software development is something else
Earlier quoted context omitted.
The message is in a light grey colour until it's confirmed. I'm not saying it's amazingly obvious but at least the information's there. In fact I'm mostly posting this comment so others know what to look for. (I know this because I just spent 60 seconnds staring at my message trying to figure out why the formatting was off before it told me it wasn't sent. It sent immediately when I retried though.)
I’ve had messages that were black for at least one minute turn gray and only then notify me that they failed to send
Slack is unusable, but it did get me to restart Docker which had ballooned to 16 GB memory and a bazillion processes. Modern software development is something else
Good reminder that I needed to do this. Docker for me had gotten up to 13GB even though I have it supposedly limited to 8.
This backend outage reveals how horrible the Slack UI is implemented. You post a message.... you think it got sent. Then 1min later, it tells you it was not.
Doesn’t work for me either. Of course, the calendar says “100% uptime” even as there’s an outage right below it: https://status.slack.com/calendar
Well, in their defence, you can't really know how much the uptime is going to be affected by until the incident is resolved. If it was a live counter then you'd see the uptime go up as the month progresses!
* Messages are shown as sent (not grey), then, after several minutes, a "Try to send again" message appears. Or the message turns grey. Or both.
* The webapp randomly reloads. Sometimes already typed messages are preserved, sometimes they disappear. ( I assume a reload happens when a new version is deployed with some "force reload" flag )
* Threads and channels just show a loading spinner forever.
* After switching channels, all fonts disappear and just the menu background remains. No remedy except reload.
Outages happen. They get resolved. That's live, and it's fine.
What is not fine is how ill-equipped the frontend is to deal with such failures.
Doesn’t work for me either. Of course, the calendar says “100% uptime” even as there’s an outage right below it: https://status.slack.com/calendar
Well, in their defence, you can't really know how much the uptime is going to be affected by until the incident is resolved. If it was a live counter then you'd see the uptime go up as the month progresses!
Basically time "down" / total time elapsed during $period. At the beginning of the month/quarter/period you'd be at 100% (if they are up at that moment). Or even simpler, just have it be a measurement of a rolling window X days in the past.
I'm seeing slow performance switching/joining channels, and it's not clear whether DMs or @mentions are working consistently. Messages I send are frequently coming back as 'could not send message'. I'm not delighted by their use of might/may language and lack of detail in the status messages. Slack is pretty clearly not working well for a large number of users, and based on the above IDK what can be attributed to deg…
Also check their status page in a month or so, and you'll see "October 5, 2020" with some message like "no issues".