Psyduck is the greatest pokemon of all time.
- User Since
- Feb 8 2011, 1:28 AM (327 w, 6 d)
I don't think that's a very desirable behavior.
How can I reproduce the issue you're encountering?
What behavior would you expect arc to have if git commit ... produces 5GB of output (hypothetically, from a hook which prints 2.5GB of header and footer context and puts the important part in the middle)?
(You are also almost 8 months out of date; we only support recent versions of Phabricator.)
Click on logout then tried to login using google authentication and getting the error.
Looks good to me, do you want to give PHUITagView a mode for it and I'll rebase this on top of that?
Please follow all the instructions when submitting a bug report. In particular, we need:
I'm going to close this; there are two possible followups -- each of which is better focused on a more specific set of problems -- but I'm not merging it into either one since I think there's a lot of general ambiguity about problems and use cases here. If you're interested in this, feel free to follow either or both.
This was basically just a work log for an earlier iteration on Nuance focused on bi-directional bridging with GitHub. We're pursuing Nuance again now, but not with the same focus, so I'm going to close this and reorganize things. Some similar task will likely fall out at the end, but with a better focus on where we're actually headed.
Sat, May 20
- The persistent header should now select more intuitive changesets.
- The scrollbar annotation is now disabled for trackpad "aesthetic" scrollbars (like the 0-width scrollbar on OSX if you don't have a mouse connected to your laptop). If we retain the element, I plan to enable it eventually, it just requires us to move content around and generally make a larger change.
- The scrollbar annotation is now disabled unless phabricator.show-prototypes is enabled.
- The scrollbar annotation should generally work better and be more useful now.
- I've deployed these changes to this host.
- Make it conditional on "show-prototypes" instead.
Sure, I'll update D17983.
Basically, I'm fine with a "turn it off for a while until we have more time to consider things" approach if you'd feel better about that, since it kind of snuck in an hour before release cut.
If you want to accept all the other stuff I can land them and land D17983 to hide it, then you can comment out the "always hide it line" locally. I don't think any of them do anything bad/complex so even if we rip it out eventually it isn't making a big mess to land 'em.
I think I like the element, but I'm happy to table it until you have more time to look at things since it sounds like your initial impressions are less positive. D17983 just hides it -- once you have a chance to spend some time on it, we can either turn it back on in master and land all the followups if it seems OK, or pursue something else if you have different ideas, if that sounds good?
Sure, I'll nuke this.