Serge Matveenko

PR will be welcomed

@ninjia0 what Python version do you have and which OS do you use?

I think this is an issue. Enabling propagating for logger results in a possible false positive result of a test. Say, I would like to ensure a message goes to...

@thisch looks really useful one thing. I'd assume this would work either ```python def test_app_logger_content_catchlog(caplog): logger = logging.getLogger('app') logger.propagate = False caplog.set_level(logging.INFO) with catching_logs(caplog.handler, logger=logger): logger.info('foo') logger.error('err') assert caplog.record_tuples ==...

Also, this fails other way around. Serializing `Vec` results in an array. So, there is no obvious way to serialize `Vec` as `ciborium::value::Value::Bytes`.

I've managed to solve the serialization issue with [serde_bytes](https://crates.io/crates/serde_bytes) crate. Adding `#[serde(with = "serde_bytes")]` (see example below) to a value declaration solves the issue for me. ``` pub struct MyStruct...

I don't thing this a bug. It is more likely is a feature request. Should it be scheduled for 0.10? Behavior described in this bug is documented and well known...

At least, it would be handy now to have a documented way to reproduce an environment which will guarantee the following: * `poetry.lock` exists * `poetry.lock` is up to date...

I would like to provide a simple sample that literally cries for a shorthand. This is a sample from `aiohttp.web` docs https://docs.aiohttp.org/en/stable/web_advanced.html#middleware-factory which when annotated looks like this: ```python import...

The question is how often there is `# type: ignore` in such a place as its almost impossible to guess this correctly or write directly from one's memory.