Hello! 👋 Thanks for opening your first pull request here! ❤️ We will try to get back to you soon. 🚴

Thanks for the review @larsoner! I fixed the points you mentioned.

1. Below is the example output of make_lcmv in case info and forward contain MEG+EEG channels while covariance is only calculated on MEG. The new logger message is there but gets shown twice since _check_info_inv is currently called twice (once through _check_one_ch_type and once explicitly). There is a XXX note about this behavior in make_lcmv so I suppose that it is out of scope for the current issue/PR. Hopefully it is not too confusing for the user.

Excluding 59 channel(s) missing from the provided forward operator and/or covariance matrices
Excluding 59 channel(s) missing from the provided forward operator and/or covariance matrices
Computing rank from covariance with rank=None
    Using tolerance 3.5e-13 (2.2e-16 eps * 305 dim * 5.2  max singular value)
    Estimated rank (mag + grad): 302
    MEG: rank 302 computed from 305 data channels with 3 projectors
Computing rank from covariance with rank=None
    Using tolerance 3.3e-13 (2.2e-16 eps * 305 dim * 4.8  max singular value)
    Estimated rank (mag + grad): 302
    MEG: rank 302 computed from 305 data channels with 3 projectors
Making LCMV beamformer with rank {'meg': 302}
info["bads"] and noise_cov["bads"] do not match, excluding bad channels from both
Computing inverse operator with 305 channels.
    305 out of 366 channels remain after picking
Selected 305 channels
Whitening the forward solution.
    Created an SSP operator (subspace dimension = 3)
Computing rank from covariance with rank={'meg': 302}
    Setting small MEG eigenvalues to zero (without PCA)
Creating the source covariance matrix
Adjusting source covariance matrix.
Computing beamformer filters for 7498 sources
Filter computation complete

2. Do I need to address the failing Windows CI checks somehow? The test runs locally on Ubuntu for me, but in CI log.getValue() is empty for some reason.

Feel free to suggest any other changes if needed.

@ctrltz you have a conflict, and merging in main (or rebasing) should fix CIs. Let me know if you want help with this or the verbose stuff

Thanks for the help and sorry for the delayed reply @larsoner! Your idea with verbose sounds very nice to me, I will implement it by the end of the week.

I've updated the PR, it should be ready for merge now. The logger message is shown only once now, and failing CI checks are not related to the PR.