In 0.19.5, they removed the deprecated post_id tag, and replaced it with the post_ids array. If you ran that against an instance still running 0.19.4, it should work.
This is for posts, not comments, and doesn’t affect the comment API.
Serious answer, I’m not sure why someone would run a VM to run just a container inside the VM, aside from the VM providing volumes (directories) to the VM. That said, VMs are perfectly capable of running containers, and can run multiple containers without issue. For work, our Gitlab instance has runners that are VMs that just run containers.
Fun answer, have you heard of Docker in Docker?
Dead by Daylight does the opt-in beta thing. Progress doesn’t transfer from one to the other, but unlocks are handled by just unlocking everything. The bonus of this, as opposed to in-house only, is that players can see what’s coming and give at least some chance for feedback before release. The downside is that there’s only one iteration, beta, then release, and sometimes things that worked in the beta are broken in release. I’m not saying that this should replace an in-house sandbox, but as an addition it helps devs get thousands of eyes on it and lets the community voice issues before they become semi-permanent.
I’ve played maybe 15 rounds since the update, but only found one mission-related bug. We completed both sub-objectives for an ICBM, and it told us that we could extract without launching the missile. And given we had 2 reinforcements left, we sure weren’t looking a gift horse in the mouth.
This may sound silly, but do you have any idea if Magic the Gathering’s elemental otter is inspired by Lutris? It seems like too convenient of a name.
Yeah, you’re right. I didn’t read enough of the docs. The new field is only for posts, not for comments. It looks like
post_idshould still be valid.