Anyone else noticed issues while pulling PermissionSetGroup using SFDX?

In metadata coverage, it says that PermissionSetGroups are supported in Unlocked Packages as long as the package does not have a namespace, but if I create a permission set group in my scratch org and try to pull it, then I get an error saying that some permission set cannot be found ("Entity of type 'PermissionSet' named 'Test' cannot be found.").

My investigation showed that when we create PermissionSetGroup named 'Test' then in Salesforce created a PermissionSet named exactly the same, but it cannot be manually found (via list of permission sets), but it is still found in Setup search (when I try to open it I get insufficient permissions error). Also if we create Permission Set Group named 'Test', we cannot create permission set named 'Test' as we will get error that his name is already used (works both ways - same with using name for Permission Set Group that is already used by Permission set).

Steps to reproduce:

1. Create a scratch org.

2. Create Permission Set Group named 'Test' in it.

3. Pull changes using "sfdx force:source:pull"