@chad Like I said I'm aware you guys don't support prototype apps, figured I'd just make someone aware of it, not looking to make it work right now.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Apr 17 2017
Oh, Calendar is a prototype. :/
Do you mind verifying the bug on an up-to-date version of Phabricator?
I'm planning to pursue reliability (T12573) first since it's more immediately actionable (hard stuff is at the end instead of the beginning) and it will take more time to tell if we've actually fixed it.
I don't think we've done a proper sprint since Dashboards.
I suspect this "week" will actually last like two months, but I'm looking forward to sound. 🌵
Yeah I think this is more about "2 person rooms", where email is nice because it's a 1:1 interest ratio rather than general chatrooms. If we had mention email support, I'd turn off emails with the exception of two person rooms.
You are now officially Pay2Win.
Yeah I just wanted to buy myself a badge.
Alright, I'm going to assume this was cache/ghosts until it happens to someone else since it seems like no reproduction case exists anywhere anymore.
No nothing like that but FWIW, it just worked when I tried to reproduce it again.
Maybe a simpler empirical test is, on the "Add Payment Method" page, does this work in the developer console?
(Also, do you run some browser extension like "disable all external Javascript so ads don't work"?)
Yeah.
Does this resource load for you?
Just tried again.
That makes at least some sense. My thinking was something like this:
I think I can fix this in applyFinalEffects anyways.
This costs me time every day. I get emails for some rooms, and I don't think I should have to visit them in the UI to clear the count when I come back to Phabricator. It's even more bothersome when I'm in the room and chatting that the count needs to be cleared.
Done...Thanks
Install the gd extension.
I believe the resolution of T8151 also resolved this.
I think this is basically fine as-is.
I'm going to de-scope this for now since I don't think it's terribly important, but is fairly complicated, and "v4" already has a ton of stuff in it. This should happen after UI-impacting changes like T3597 anyway.