The results are ordered by "match strength", but this is computed at runtime and isn't unique to each result: we can't start with the 100th result and use it to build any sort of clause like WHERE rank > 12345 that starts on the 101st result.

Sorry, this isn't a feature request we can accept. See Support Resources for help understanding what kind of support is available, and Contributing Feature Requests for help with feature requests.

See T10109. I'm going to merge this into T2543.

It's pretty big deal for us because we are using phriction to collect helpdesk FAQ. We have modified TOC to be displayed in the beginning of the page and would like to use ponder are storing questions. Atm using ponder links in phriction as headings also shows toc values as X.

I don't know about that.

You've personally observed a build trigger as the result of a user choosing "Plan Changes"?

The document contains "bash". This behavior seems correct to me.

This is the search that shows the problem: https://secure.phabricator.com/search/query/lOkcMy6H_Jmk/#R

Thanks a lot for this ultra-fast reaction & fix.

I already have an open task on making typeahead-only dialogs simpler, better, so merging into here.

I'm going to close this as resolved, added 9 more icons. I'm going to open a new task to allow any IconSet be extended, which seems a better path for any similar product.

This should be resolved at HEAD of master, thanks for the report!

I was able to reproduce it, sorry for mis-reading.

In T12347#214146, @eliaspro wrote:

Is it possible that symlinks could cause this issue?
libphutil and arcanist are symlinked from their current builds to the location where Phabricator expects to find them.

I assume this is broken for any EditEngine not tasks

Whoops, no my mistake. I tested Task forms, not Projects.

Although our deployment mechanisms should take care of this on their own, I specifically made sure everything is restarted etc. for reproducing this issue and producing the error logs.

I can't reproduce this. Did you recently update and forget to restart the webserver/PHP?

Something like:

I have a bad version that makes a file the first time getDefaultPictureURI is called and one doesn't exist. But it uses unguarded writes and feels hacky,

@epriestley not sure what I need to do next here on this or D17430

I don't think I can close this. Can you please do it?

@chad You're right, should've gone to Conpherence first.

File a new bug report if you're still having issues at HEAD

Anyone knows a any dirty (or not) fix for this, like a ninja mysql management move?

We'll still need reproduction steps to accept this as a bug report. If you just have questions about what to do next or if it's a bug at all, Conpherence and Ponder are community support. See Contributing Bug Reports and Providing Reproduction Steps for more information.

Workaround is to URL-encode the parenthesis (%29) or use the remarkup style

[Back to the Future](https://en.wikipedia.org/wiki/Starship_Troopers_(film%29)
[[ https://en.wikipedia.org/wiki/Starship_Troopers_(film) | Jurassic Park ]]

Results in:
[Back to the Future](https://en.wikipedia.org/wiki/Starship_Troopers_(film%29)
Jurassic Park

One use case for "locking" a task could be:

1. For a release of the software product all tasks which represent the software changes on the version being released require review
2. Reviewer looks over task form fields and if everything looks good, "signs" (locks) the task in a "reviewed" state
3. Tasks can be unsigned prior to release of the version, allowing updates to tasks as necessary but also requiring another review
4. Upon release of the version, tasks can no longer be unsigned

We've implemented a basic version of this, roughly along the lines of the recommendation above. Here's how it works:

Ok, then feel free to dismiss this one… I didn't expect those kind of complexities behind this :)

Yeah any typeahead dialog now that I think about it.

(I think I've used this workflow fewer than 5 times outside of testing, and although similar workflows like "Award Badge" and "Add Project Members" have the same issue, I think they're similarly rare.)

This is also nontrivial: when we display a dialog, we already attempt to focus the first input. But the first input here is a tokenizer, not a real input, and naively focusing it fails because it hasn't activated or rendered yet.

Specifically, I've never used this workflow. So I don't see any obvious benefit to spending upstream time on it, and the task will sit here until others maybe chime in and we can get a sense of it's impact. This seems like an obvious request, but maybe tools like Nuance (help desk) make the workflow you use today, obsolete, so then we'd also not worry about implementing this at all.

We'll take a patch if you like, but if you're filing a feature request, you still need to follow Contributing Feature Requests and Describing Root Problems.

D17452 marks this as resolved and makes these changes:

A basic version of this is now available in HEAD of master. Here's a walkthrough of what we've implemented and a discussion of some areas where we'd like feedback.