Alex Gavin

 The name you provided in the sign of and the name in your git config do not match. The above screenshot is taken from the bottom of the DCO...

Changing [this prototype](https://github.com/raspberrypi/pico-sdk/blob/93472b84c6fb08c184af984f948b045e4dba9edc/src/rp2_common/pico_stdio_uart/include/pico/stdio_uart.h#L71) to `void stdio_uart_deinit(void);` should fix the build error

Working on a PR in a forked repo. Multi collection behavior should be working, just need to write a test and update the result caching. I opted for initializing aggregations...

[This line](https://github.com/percona/mongodb_exporter/blob/5c3358c3bab3823588fb801a84f3eb7985d2765c/exporter/exporter.go#L328) is likely to blame for the `--web.telemetry-path` issue. Should be referencing [this field](https://github.com/percona/mongodb_exporter/blob/5c3358c3bab3823588fb801a84f3eb7985d2765c/exporter/exporter.go#L104) instead of hardcoding `"/metrics"`. Can't speak to the other issue.

I don't know that it's necessarily the same issue, but the error message you posted looks familiar. I was having some authentication issues caused by a MongoDB goland driver workaround...

One error to the next haha! If you run in to TLS cert errors again, definitely recommend following [this section](https://www.mongodb.com/docs/manual/appendix/security/appendixA-openssl-ca/) of the MongoDB docs for setting up testing TLS certs....

Updated changes with output of ``gofumpt -w -l ...``

The CI tests for 1.17.x mongo:5.0 and 1.17.x percona/percona-server-mongodb:4.4 appear to be existing pipeline and unrelated to this PR. The 1.17.x mongo:4.4 test does appear related so I am investigating...

Tests for go v1.17 with Mongo 4.4 (aside from the ``... collected before with the same name and label values`` failures which exist on other PRs) are passing on my...

@tshcherban Do you mind approving the workflow to see if the error persists in the CI pipeline?