I’m getting the following trying to access some handlers in my IDE. Anyone else? It’s not all handlers.
Agreed. Hadn’t made that connection initially.
You seem to think that ST can only break things on Fridays. Shame on you sir… They have the capability to break things on ANY DAY ENDING IN Y!!!
LMAO (sad that we have to even have a running joke about this).
cough Love ya ST! cough <-- karma insurance.
3 Likes
I had a slight panic. I finally got my first commit to work in the IDE - I thought I had blown it up some how 
.
Don’t forget the day that ends in “w”.
It’s coming soon.
1 Like
Tomorrow
1 Like
But tomorrow never arrives because today is always today.
Tomorrow always arrives and you know that because we get emailed an Outage Status from ST.
Free beer all day tomorrow …
I’m on board with that. You picking up the tab?
Sure, as soon as tomorrow arrives.
Beware the Ides of February.
The IDEs have already arrived with 500 errors.
Also down, and reported to support…
Ticket #511913 if it helps anyone.
Glad to see it isn’t just me
Of course I was actually feeling pretty good and motivated to get Shhh done today.
Of course it isn’t ST issue, everything is fine on Dev and ide …see
I noticed that too, lol.
Tried to update from GitHub, and it sat there for ten minutes, nothing happened.
“What we’ve got here is failure to communicate.”
2 Likes
Save yourself some time ( and aggravation) . App keeps " forgetting" any new apps or devices installed today too. Get everything working, go get a drink, come back and all the new devices are in IDE, but missing from app.
1 Like
Already doing that, do you mean a second drink?
2 Likes
Okay, if you insist.