This issue was originally created at: 2011-04-16 10:44:49.
This issue was reported by: charlesli.
charlesli said at 2011-04-16 10:44:49

The scons documentation talks about lots of things, but there is no section that
simply says: "if you want to use compiler xxx, located in path yyy with options
zzz, here's how to do that".

Instead there is a lot of talk about environments (you hav

Hello! If I'm not wrong I found a typo in Introduction section.
https://aio-pika.readthedocs.io/en/latest/rabbitmq-tutorial/1-introduction.html
You mentioned several time and listed in code snippet that in sender.py queue must be declared before send a message. But in sender.py code right after channel creating you publish a message and if run a sender.py before receiver.py you will not receive

Based on your documentation, I should be able to force sanic-cors to show only logs at INFO level like this:

cors = CORS(app, resources={r"/static/*": {"origins": "*"}})
logging.getLogger('sanic_cors').level = logging.INFO

This works if the logging level for the app is also set to logging.INFO, but as soon as the app’s log level is set to logging.DEBUG, even with the sec

Referring to #98,

It would be nice if a section of this feature will be available in the documentation.

We need to show an example of setting retry_policy_factory and the circuit_breaker_factory, also stress out as much as possible that there needs to be just ONE instance of FallbackFailsafe per dependency.

STATUS message never appears in journal...

May 17 02:26:46 [redacted] python[1748]: [41B blob data]
May 17 02:26:46 [redacted] python[1748]: [42B blob data]
May 17 02:26:47 [redacted] python[1748]: [42B blob data]

Just get these blob data things. The READY/start STOPPING states appear in the logs as expected. Unit is set to Type=notify of course.

Right now the --concurrency flag for stestr run takes in an integer, if that value is 0 it runs nproc workers, if that value is greater than 0 it runs that many workers. But we don't have a way to specify a value that is a fraction of nproc easily (like nproc/2 or nproc/4). This can be useful for some test suites, especially if they're very resource intensive, where running nproc workers isn't via