We don't show a specific amount of history: we show all activity since your last activity.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Nov 10 2015
I think this is the kind of interaction that many people with have an opinion about, and they will vary wildly. What's better for some, is decidedly worse for others. Arbitrarily changing it doesn't really solve the problem enough, and the entire interaction probably needs rethought.
What about having the number shown be proportional to the total number of stories?
I can't think of a concrete number that will satisfy this case of "on long lived diffs". Either you want the full history or you don't. Not sure 5 more stories will be enough (and creates significant clutter for everyone else).
Seems to work nicely
email reply test
Misa luvs zis fichoor! ❤️
Very helpful!
D14452 and similar seem nearly certain to obsolete this.
(I'd also like to be able to subscribe to Almanac devices/services/networks too)
We now have execute as well.
We might build this as a side effect, but there's been no actual interest in it.
We now have better behavior in general, and no other reports of this in a couple years. The underlying use case also isn't clear to me; build artifacts should be .gitignored.
They now sort by date and have some options.
Any chance this could be speeded up if we were to sponsor some of the development on this?
This was directly obsoleted by the removal of arcanist projects.
The future of these pipelines in the upstream is server-side, not client-side. See T9530.
This hasn't really surfaced to the upstream in the last couple years.
I've done some work on this and I do intend to continue working on it, but have been somewhat time constrained as of late. The foundations for this task are already in place and many unit tests engines just need to be modernized to work with the .arcunit specification.
Haven't seen more issues here in several years.
This is now meaningfully achievable through Drydock as a repository operation, but we've seen very little interest in it.
We'll continue down this path, but I don't think there's much value in keeping this task around -- more modern tasks like T5447 cover the same ground more usefully.
We haven't seen further interest in this in several years.
No upstream use case in years.
The use case I'm trying to cover is to create notifications for open tasks that are past their Due Date (custom date field that we use).
Presuming no one cares anymore.
Given the modern realities of support, I don't actually think we'd be better off by making it easier to submit stack traces. We also explicitly don't want surprise patches.
Big yes, please to this. I came across this task when looking into a way to exclude our Python tests when creating diffs when only our front-end JS code has been touched, for instance. It seems this feature will allow just that?
Thank you for your answer, this helps me understanding the issue better.
Pretty sure this is just a bug, auth and conduit auth have each gone through a major rewrite since the last time the log was touched.
T9212 better explains why we're not able to handle very specific support needs (for free) on a day to day basis.
You have basically two options:
What I would like to understand is why the directory for the local file storage is cluttered so fast with empty directories and especially why the empty folders are not removed.
Why do you need to understand this, and what are you attempting to do. Generally it's not a good use of upstream time to explain the underpinnings of Phabricator unless you are another Phabricator developer.
Yes, see Paid Prioritization. Shoot us an email at contact@phacility.com if you'd like to move forward.
Can we get this prioritized? The feature request is open for some time now and letting us know its fate would be much appreciated.
Now the upload of large files (> 8Mb) works by splitting in chunks via git push. Apparently, the changes for local file storage were not saved before.
I just tried pushing a new branch "test" and it worked, there is no master yet, but that push he attempts to do should work
This is hosted by phabricator itself, but repository is actually pretty clean, nobody ever pushed any commit to it in past.