task_manager | task manager system by zend framework3

If you look at the diff of the version you've used before vs. the version you're using now (https://github.com/seuros/capistrano-puma/compare/v3.1.1...v5.0.2), you can see that the puma:start command (together with others) was apparently removed from the main puma.rake and instead moved to the the pluggable adapters for daemonization and systemd respectively. Judging by the readme (https://github.com/seuros/capistrano-puma#usage), Puma 5+ only allows systemd (see https://github.com/puma/puma/pull/2170), so you'll have to add install_plugin Capistrano::Puma::Systemd to your Capistrano setup (and of course make sure that your setup runs systemd properly).

If you can't/don't want to use systemd and want to stick with Puma's classic daemonization, you'll have to go with Puma 4 (gem 'puma', '< 5' in your Gemfile) until you're ready to upgrade.

The issue was one of my containers was "pending" since it depended on another container with an incorrect healthCheck command. The command always failed, causing an unhealthy state on that container, so the pending container never actually started.

error is due to

You're passing it incorrectly

You need to import models, or conforming to your other field definitions, prefix it with models. like so:

QuerySet.get() will raise an exception if the queryset does not contain exactly one object. Either an DoesNotExist or an MultipleObjectsReturned. This is by design.

You can handle this by using a try, except, of by calling another QuerySet method (.first() to get first object, for instance).

Forking only results in the calling thread being active in the fork, not all threads.. Most of the pitfalls related to forking in a multi-threaded program are related to mutexes being held by other threads that will never be released in the fork. When you're using Popen, you're going to launch some unrelated process once you execv, so that's not really a concern. There is a warning in the Popen docs about being careful with multiple threads and the preexec_fn parameter, which runs before the execv call happens:

Warning The preexec_fn parameter is not safe to use in the presence of threads in your application. The child process could deadlock before exec is called. If you must use it, keep it trivial! Minimize the number of libraries you call into.

I'm not aware of any other pitfalls to watch out for with Popen, at least in recent versions of Python. Python 2.7's subprocess module does seem to have flaws that can cause issues with multi-threaded applications, however.

Task_Manager::register_task creates a reference to a local variable plugin and pushes that reference to a container that outlives the local variable.

The other thing that is going on is move from plugin, twice. This makes little sense. Either your move is useless (the second one is, because there is no move construction or assignment involved), or your move destroys the variable (if there is move construction/assignment) and you cannot meaningfully refer to it afterwards.

You need to set it for the user. These documentation links give you more insight.

1. https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Security.APIRole.html
2. https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Security.IAMPermissions.html

You need to create these roles in advance, or create in CloudFormation template.

Edit: It appears that sometimes the new AWS Console fails to create both of these IAM roles automatically. So you may need to create them manually.