The keyboard reticle probably has the same issue but we can figure that out later.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Apr 24 2017
Oh, this actually is the inline reticle, not the keyboard reticle.
Oh, the highlight itself actually is a little off if the reply is threaded. We move the comment up a little bit to make it visually thread a little more cleanly, but the highlight doesn't get a corresponding offset.
I'm going to try putting this on top of everything and using pointer-events: none to fix all the attendant click/hover/select issues.
There are three different highlights at play here, visible in this screenshot:
In T12617#221287, @ftdysa wrote:@nervus70, I use satis to do this and it works fine with phabricator. You should easy be able to use https://secure.phabricator.com/api/diffusion.repository.search to generate the satis config if you have a ton of repos.
Easy changing of a subtype of an existing task would be on my wishlist too. In our worklow it happens fast, that a bug report or a task is tranformed to a story in the next sprint. To edit the subtype in some simple way would greatly help.
Evan, rP52c4715bbcfb solvedthe issue. Losing low-resolution profile images is no problem.
Thanks for the quick solution!
One thing I noticed. All three daemons (Taskmaster, Trigger, PullLocal) are listed as "Waiting" on my install currently, and also show up in the output of phd status. When this problem occurred, I didn't look at the Daemons app in the web UI, but I did notice that Taskmaster was not listed in the phd status output. I'm guessing that behaviour is not normal and perhaps provides a little insight into what's going on here.
I've adjusted my monitoring to just alert me instead of restart the daemons when there's an issue so if/when this happens again I can investigate more fully/provide more information. The code from D17397 had definitely landed when I experienced this, as I saw it in the source code when I investigated. I've upgraded to current stable now.
Apr 23 2017
The Aphlict logs should probably get consolidated here too, they're set up a little weird and don't currently rotate during normal deployments.
After fiddling with some more upgrades, I started to get
It is intentional that daemons shutdown when they aren't doing anything. See T12298. They will be restarted automatically when work becomes ready.
Just faced that problem on my micro hosting. I've updated some software and then started to get the same error as OP when cloning/pulling/pushing mercurial repos. Here is the list of software, that got updated back then: https://paste.kde.org/pqelvuhjf
I made a diff (D17780) that adds bin/phd check which runs the setup check that the web UI runs, writing the result to the console, and exiting with an indicative status. This at least allows the circumstance to be detected and I can fix up the problem with bin/phd restart. This might be good enough. Even though using bin/phd start or having Phabricator self-repair through the Overseer would be better, it's likely too rare to warrant work on more complex options.
This is a bug in the upstream. D17770 (or some similar patch) should be available later today.
I have a rough cut of this one.
Apr 22 2017
Doorkeeper is the correct upstream project to follow for two-way integration in the long run, it's just not on any roadmap currently. You can extend Phabricator yourself today for these things if needed.
Yeah, if you know what information you want.
Tasks, projects, owners packages.
Pick three and I'll spruce them up today/tomorrow.
This is probably the fix:
It looks like the existing test cases in master fail on PHP 7.1, presumably because of T10929, so that needs to be fixed before I can fix this.
This rule is constructed very awkwardly and I'd sort of prefer to remove it entirely, but I think we can technically fix this without really disrupting things.
Extend a Remarkup rule if you want to parse a specific URL pattern into a token like we do for tasks like T5000.
Excuse me, I don't really know how to do this.
Should I create a php file like DifferentialJIRAIssuesCommitMessageField.php?
And Differential would treat some pridicular string as a custom field.
Then how do I add parsing external bug tracker id code?
Please use Conphernce or Ponder if you have questions about Phabricator.