ocket8888

Oh, so you mean like you switch to a branch where the source is changed and then switch back it still thinks the source is newer? That's true, but it...

I didn't check for a commit where any specific file was modified I just did `~HEAD`, because I thought you meant it would happen *any* time you switch branches.

This still feels like a step backwards, though. Make is doing its level-best to tell if something needs to be rebuilt, but it's just not quite smart enough to do...

Slack user `amc` suggests using `traffic_layout` to determine the ATS file hierarchy, which is related to this and could potentially be implemented at the same time.

I'm not sure this is still true, may need re-investigating

IMO a set of no results in the series is best represented by the empty set (`[]` in JSON, which is actually an Array not a Set) instead of `null`....

> ... this is undocumented behavior, ... [The "Request Structure" section of the `PUT /servers/{{ID}}` documentation](https://traffic-control-cdn.readthedocs.io/en/latest/api/v3/servers_id.html#request-structure) lists `updPending` as a valid payload property, making no mention of it being immutable...

I made that note a long, long time ago - it's much easier when you're learning to use an API to remember how to use one endpoint than it is...

`s/\/status/\/queue_update/g`

Is this resolved by Profile layering?