Get a valid certificate or configure your system to trust your self-signed certificate. This is not a problem with Phabricator and I do not plan to support insecure SSL configurations in the upstream.

(I never tried to reproduce with Command + Enter because I always use Tab, Enter, and the symptoms seem identical.)

Hmm, it is possible.

@joshuaspence, is it possible that this was causing the issue you were seeing in T10004?

Great, thanks much for the incredible responsiveness 😄

At HEAD:

I think chunked files shouldn't have produced errors on reads -- at least, the --dry-run was still clean for me on both hosts before D14981.

Testing has been completed successfully.

Oh! Well that would make perfect sense, then. I'll update D14984 to just clear all the headers that remarkup can emit.

I think h2 is the largest remarkup header? I've never seen an h1 in use.

I'm going to merge this into T5155, since the root issue here is philosophical opposition to the use of IAM Roles to manage credentials in the upstream. Two possible pathways forward outside of upstream support are:

I've realigned this around support for IAM Roles, because we now use a first-party client after D14982.

In T10110#152970, @chad wrote:

maybe just hr and h2

This request does not describe a root problem. See Contributing Feature Requests and Describing Root Problems for help describing root problems.

The error output was not from the script, it was just errors. I think I remember looking into this a long while ago and it's because the migrate script (incl dry run) actually reads all of the files. The act of reading the file is what generated the error. I should have described this a little better than "dry run shows some files are going to fail", and instead described it as "dry run shows errors for some of the files".

Pass with points and faces.

Oh, the comment was a screenshot. Inline + width should work on this host now.

D14983 fixes the interaction between inline and width. I'll push it to this server and wipe the cache now, and the comment above should start working.

Doing a bit more digging here... layout=inline doesn't work if coupled with size=xx.

@epriestley Are you sure inline works?

{F60 width=160, layout=inline}  {F60 width=160, layout=inline} {F60 width=160, layout=inline}

You can look up the PHID with phid.lookup.

We should be in good shape to move forward here after changes in T5155. My plan is roughly:

maybe just hr and h2

Can't you do this yourself?

See the Git documentation:

I do think we could reasonably put clear: both on hr and probably headers. I think it used to run into some problems with tables of contents, but we never (I think?) put them inline anymore (maybe in readmes in Diffusion?) so we should be in the clear, now.

Yeah. I think:

you're using layout=inline

Wait this works now. Huh?

Yep, table works, thanks for the idea!

My expectation would be this floats forever given current syntax. The only solution I can think of is a new Remarkup rule for clearing, which you can place anywhere down the line, which is what it sounds like you're suggesting.

Need a way to clear a float e.g. "clear:both"

Is there any markup command to "clear the float"?

Some of the Pholio stuff is motivated by thinking about v2 sometime down the road. Like having a "workboard" view of my designs and their status could be handy (shipped, needs more work, planned).

Points look great.

Blocking is T5353
Mock is roughly T9520
Diff ... can't locate the task offhand.

I'd like to put off building customization for as long as possible. I think we'll want it eventually to give custom fields broader support, but we can call all of that part of T418.