> The App only allows a single phone to be connected now which is a problem when both me and my wife want access.

Polar opposite of our experience. We have two Nest thermostats in our home and both my wife and I can connect to and manage each one with our respective phones.

> There is also no way to run the fans without switching it on heat or cool.

Also not our experience. We can run the fans independently of heat/cool. That could be a consequence of your HVAC system opposed to the Nest itself.

Is one of you (saidmasoud vs. jandrese) using the Nest app and the other using Google Home maybe? I tried out a Nest thermostat briefly and found it confusing that there were two different apps with different featuresets.

I originally had the Nest app where we could both access it using our phones, but my wife clicked "yes" when the Nest asked her to "upgrade" to the Google interface and there's no way to switch it back.

I don’t know what’s going on with your account, but FYI I can use both Google Home and the Nest app to manage my thermostat.

If you clean shave your face, then a safety razor is probably better as it's easier to glide along a large distance across your face. For me, a straight edge razor allows me to shape my beard better. I do cut myself pretty much every time (since the hairs on my neck go in a million different directions), but that's easily addressed by showering right after a shave + after shave cream. The cost benefits over a safety can't be overstated: the razor is a cheap one-time cost ($13 off Amazon at the time, you don't really need a "high quality" razor IMO), blades are single use but super cheap ($15 ish for 100 blades), and since I shave at most weekly I only have to buy blades once every few _years_. As always YMMV depending on your facial hair style.

> An error has occured while processing this page. Please try again.

Same thing happened to me. I just refreshed the page, confirmed form resubmission, and it worked.

Interesting timing given https://www.lastweekinaws.com/blog/the-aws-managed-nat-gatew... just came out. Does this also apply to NAT Gateways?

Inconvenience is an understatement. I tried to get my kid's birth certificate from our state's health department; waited three weeks for them to send it back because of a minor typo. Ended up spending one morning driving 1.5 hours (one way) to the capitol to get it in person.

Let me tell you about my actual birth date and the birth date the social security administration has on file being different.

I have spent at least a decade trying to get them to correct it but as far as they are concerned I was born one month earlier than the date on my birth certificate.

I gave up and when I retire will enjoy one extra month of social security benefits courtesy of the federal tax payers.

Have you contacted your member of Congress? They have constituent services that help with these kinds of things.

You could also submit a Privacy Act correction request.

Not quite the same but my father misspelled my name on my birth certificate, but spelled it correctly on my as ss application. Didn't find out until it was flagged when I was 16 and getting my driver's license. It has caused me problems several times in background checks and the like.

> I gave up and when I retire will enjoy one extra month of social security benefits courtesy of the federal tax payers.

$10 says that they finally fix the error after you collect your first check, and then prosecute you for fraud.

Just remember, the route prefix you use to define the CloudFront behavior will also be added to the request sent to the origin server. So in this case, all routes defined by the API must be prefixed with `/api/`. This makes it hard to refactor existing APIs with many routes and dependencies, but works great in a greenfield scenario.

(Of course, you can rewrite the URL on the fly via Lambda@Edge but that's a PITA to maintain)

2) was released in October, about six months ago [0]. I'd also like to add: as a user of GitLab for about a year now, their steady rate of feature releases has bene pretty pleasant, even if I can't take advantage of some right away.

[0] https://about.gitlab.com/2018/10/22/gitlab-11-4-released/#ru...

I'm not sure that's what I needed. For example, I wanted to trigger a job only for a merge request, and only if the target branch of the merge request is e.g. master. Is that possible? Trigger a job only for a MR is possible, but I don't know how to further do the later branch filtering.

When using a merge_request pipeline, GitLab defines additional variables for the run. That includes `CI_MERGE_REQUEST_TARGET_BRANCH_NAME`.

So it would look something like this:

  job:
    only:
      refs:
        - merge_requests
      variables:
        - $CI_MERGE_REQUEST_TARGET_BRANCH_NAME == "master"

Oh wow I didn't know you can do conditionals with variable like that. I'll give it a try later, thanks!

We generally only merge into master at my org, but I didn't know you could conditionally trigger jobs using an equality expression on a GitLab-provided variable. I'll have to keep this in the back pocket for future reference, thanks! Any docs that describe this feature in more detail?

FWIW, this is also the case on RHEL-based systems.

+1 regarding RDS. A company I spoke to is moving from GCP to AWS, with their biggest pain point being Cloud SQL is WAY less flexible than RDS. While GCP's k8s offering is better/easier to use, they still have some catching up to do.

To drive the second point home, GCP recently released VPC Flow Logs, while AWS has had it for a good while now.

Have you tried defining a custom network using Docker Compose?