Steps to reproduce means that we can follow what you've done and see the same error locally. Unfortunately there isn't anything here we can use to reproduce the issue. Please feel free to reopen if you can come up with the complete steps to reproduce the issue. Specifically, the steps should be repeatable and observable. For example "Every time I do X, Y, and Z, this error shows up in my log."

Sry, the relevant steps are:

• metamta.mail-adapter is PhabricatorMailImplementationPHPMailerLiteAdapter

and I got the same settings since more than a half year, (I don't know, if additional e-mail configs are required, if so, please ask) but since a short time (I don't know the exact date, but it is less than one week) there were no emails send, and the daemon throws this error (at the task description). I hope this helps.

We require reproduction steps for bug reports, please. There isn't enough information here for us to make a guess as to the root problem.

Thanks for sharing but I don't think that'll be necessary. The only place this will likely be an issue is on the config screen (and there its mostly moot).

Sorry, if that wasn't clear. "We" means just this install, not Phabricator by default.

It's not the default value, I'm sharing what ours is set to in case you want to use it.

This doesn't appear to be the default value on our install, unless you just meant its what been set here?

Also related is T3278. There is no current means of having different flavors of Remarkup, it's all or nothing. So a "no object" Remarkup would similar to a "object only" Remarkup, and so on. For now installs just should either use a regex like above or the admins should tough it out until T3278.

We set remarkup.ignored-object-names to /^(?:(Q|V)\d|S3)$/ under Config → Core

In the extreme case where you have, say, a million tests, I'd expect there is probably little value in reporting each test into Harbormaster as a "pass", and your harness might want to summarize all passes into "999,998 additional tests passed" and submit two failures and one aggregate-pass.

T9704 also discusses slowness on inserting the tests. That may be unnecessarily slow right now, but I don't expect clients to submit unlimited numbers of tests in one API call. Instead, submit tests in chunks (say, of 1K tests per page or whatever) by calling harbormaster.sendmessage repeatedly with a work status.

We don't currently have a sortable column on the unit message table, since pass, fail, etc., aren't naturally sortable by any key MySQL can construct.

This is probably not a true race in the strict technical sense, I suspect you can reproduce it by doing one of these at walking speed:

Works now; thanks!

Whoops, thanks. This got rebased across 200 years of changes and I didn't re-test creating a credential. D15512 should fix it.

@epriestley I understand you have the setup check - my point is that for RDS users we skip this check when we see we can't do anything about it. And then months later it's forgotten about and we still draw that conclusion.

just convinced that Phab search didn't work and feeling powerless over it

Amazon RDS is incredibly popular so although you haven't seen this request from other installs, my guess is that many are like we have been for the past 1.5 years - just convinced that Phab search didn't work and feeling powerless over it...I understand the squeaky wheel tends to get the oil, but it's worth maybe considering what % of installs use RDS since all of them will have this problem.

This should be fixed in HEAD of master. Let us know if you're still seeing issues after updating. Thanks for the report!

I think this should be fixed in HEAD, let us know if you're still seeing it after updating. Thanks for the report!

@chad False alarm, I've checked wrong link. Problem existed on Maniphest global rules but it seems it is fixed already on upstream.

I'm still able to select stuff fine and use the form, did you try the dropdown? (I do see the error in the console).

Elasticsearch may also be a solution. Also, looks like we might be able to detect RDS installs by querying variables in MySQL.

Yeah -- it's not very clear on its own, but this comment is specifically referring to that issue:

We can resolve this by parsing the query and rewriting the query we submit to the engine as "+x +y" if ft_boolean_syntax has not been adjusted.

Hmm... maybe I'm not explaining my expectation well, but the "issue" I'm referring to is the fact that after steps (1)-(3) I now have a task that is in the "Subproject A" column in my "Project X" workboard but is not *actually* in Subproject A anymore.

T10486 is related; T6027 and T5214 are somewhat related.

Thanks for looking @chad

Does the task go away from the workboard when you refresh? I think that's the missing step here, that you're editing the task on the workboard.

I followed steps listed here but didn't get your same outcome. Can you clarify the steps to reproduce, the expected result, and the version of Phabricator you're using.

I see you already found an existing issue, sorry for the noise.

We don't keep this install at HEAD at all times

I understand, I didn't think this was the case anyway. I just figured I'd let this issue be known so it will at least be fixed.

No problem. We don't keep this install at HEAD at all times, for what it's worth.

We personally are not on any version with the new layout, so I can't say it fixes it.
I just drive-by reported a bug I saw on this instance.

Version information is required for bug reports, as is updating before you file a bug report.

(Nearly every text area in Phabricator can take files via drag and drop.)

This doesn't appear to be a Bug Report

Thank you both for clarifications. Will follow your advice.

for anyone else that runs into this in the future: http://www.gossamer-threads.com/lists/wiki/mediawiki-cvs/626638

I think this isn't tremendously important for Countdown but should definitely be sorted out before we unbeta Calendar.

It might not be bad to always show timezones in email explicitly to deal with cases related to T3025 better (e.g., you fly to the east coast for a conference, get prompted to reconcile your timezone after T3025, and it may not be obvious that this also affects mail you receive until you return and re-reconicle back to PST).

With metamta.one-mail-per-recipient on, we can adjust this to the viewer's preferences.

Unfortunately we can't take bug reports missing required information. Specifically:

Visit /config/module/versions on your install. If it does not exist, you're not running HEAD.

@richardvanvelzen Thank you for your comment. However, I don't have /config/module/versions/ or any Phabricator-related versions file or directory, for that matter, on my system. If you meant /conf/, then this directory contains only the files __init_conf__.php, keys and local. Please clarify.

• You can obtain the versions at /config/module/versions/ on your install
• The max nesting level is set to PHP_INT_MAX (see libphutil/scripts/__init_script__.php:44), so you should never see this error.

Yep, that worked. Thanks.

That one worked OK, yell if you're still seeing an issue?

Test: User Guide: Prototype Applications

Oh -- I misunderstood. The issue isn't that we're getting invalid markup or emitting markup in a text context, but that the link is relative.

This is probably very easy to fix, let me spend 3 seconds on it.

Yes, Phurl provides URL shortening. U10 is the root object providing ((prototype)).

Yeaaah, I would assume this worked for free with Remarkup, but I guess not. Yeah it's Phurl,

So this actually in Phurl (not clear from the link) and not valid itself because Phurl is a prototype?