Awesome; thank you!

After D15424, arc fails when failing to push the staging area.

I've marked D15424 as fixing this, although I don't have a detailed understanding of exactly what goes on in the git protocol and which heuristics it is using. In particular, I haven't been able to trick it into doing too much work locally (maybe it also looks at parents?).

This is on a daily cron, I think you missed the update by a couple of hours. Link works OK for me now.

Hi! How can we reproduce this behavior?

Please describe the root problem you're facing when requesting features. See Contributing Feature Requests and Describing Root Problems for details.

This indeed looks fresh and cleaner, good job.

Calendar is the expected application to use for this need, not Countdown. We don't have any plans to implement new features into Countdown since they'd directly overlap with features already existing in Calendar. I doubt this is something the upstream will ever build, but I'll leave it open in case someone want to contribute a patch.

Ah, makes sense.

That's because the symbols db on this install aren't always up-to-date; utils.php was updated recently, but the db still points to the old location...

Oups used ref txxx instead of fix txxxx

Calendar doesn't have the advantage of a countdown, and it is an advantage to create a calendar and a countdown event. I don't think a CC bar makes Countdown really more complex, it would only look a bit more like some other appilcations.

I'm not sure how making Countdown more complex solves anything. It seems your root problem is already solved by Calendar?

In some cases countdowns are more useful, because

• It is very simple
  • You got only the start date, for exmaple for a product release
  • You got not a lot of data, e.g. invitees, duration, end date, so you just have to set date and description, and you can use it

That's why in some situation countdown is better. This doesn't means, that I don't use calendar, but for some things countdown is better, because it is simple, and fast.

My problem at the moment, is that I'm using countdown for events.

You may be able to moot this issue by removing the copyright headers entirely.

@20after4 : I did the same remark in D15396#177349 but according to chad answer, content are just splited, and upstream have not actually designed side bar and main coulmn yet so things will change.

This looks amazing

@chad Got it - thank you. Sorry I missed that comment.

Also, I'm not sure that forcing people to select the preview tab is the optimal choice.

@chad Thank you for the clarification and the link. That mockup looks pretty good to me (though I couldn't decode the implied functionality of the "+" icon in the left top corner of the area (to the left of "Add Action"). Also, I'm not sure that forcing people to select the preview tab is the optimal choice - not only it's an extra click each time, but also doesn't give the user an idea about the fit / layout of the text in a horizontal dimension. Just my two cents.

We have one form display library and it powers all forms. Sometimes we build bespoke forms, but not often. Some future explorations in M1461

@epriestley @chad [This comment is not specific to the above-mentioned changes, but rather general.]

+1 for having the second column position:fixed

test

test

Thanks for the report! This was a bug.

I believe this wouldn't solve your problem: I could add two files, A.c and B.c, and add a header to only one. This would pass the rule but fail what you intend to enforce, I think.

Not sure if related to this task or not, but I'd love the ability to have Herald rules act on countdowns. Sometimes we have tasks that fan out to many teams and we'd like the ability to assign it to the team, but add a project or change assignee once a countdown expires.

oh, you also have to put an interface on the device in order to bind it

Create any device, create any service, bind the service to the device, then click "Details":

How do I get to this page? I have a diff ready, just need to fire it up somewhere.

Drydock and Almanac are now available in the cluster. Here's a rough guide to configuring them -- I'll turn this into something formal once things work a little more smoothly.