[BUG] github org account stopped showing correctly

[NavNab]

Describe the bug My org account repos are not visible in my vscode using Alpaca. My personal repos in my account are visible without any problem. P.S: I'm the global admin of my github org.

To Reproduce N/A

Expected behavior List repos in my org account.

Screenshots

System Information

• OS: Windows 11
• COSMO Alpaca Preview. Version: 0.26.0

Additional context It was working as expected few days ago.

[lippertmarkus]

I couldn't reproduce yet:

We retrieve AL-Go repos by filtering repos on language:AL or language:PowerShell and then checking if those repos have the file .github/AL-Go-Settings.json. Does this apply to your org repos? Can you create a new repo via Alpaca and see if that one shows?

[lippertmarkus]

or did you accidentally hide them in settings?

[NavNab]

Yes, I have repos configured with AL-Go. Example:

I disabled all settings related to Alpaca, the issue remains.

I switched between github and azuredevops views. I have the same issue with azuredevops. I can't see my org. But, this is not a big deal for me as I focus on github with Alpaca.

[NavNab]

I tested on a fresh windows 11 sandbox and I have the same issue

• fresh vscode installation
• fresh Alpaca installation
• only Alpaca extension is installed

[lippertmarkus]

In your personal settings under Appllications -> Authorized OAuth Applications -> GitHub for VS Code can you check if you granted access to the orgs?

[NavNab]

I can see both my org and microsoft

[lippertmarkus]

ok then please check if the requests get correct responses

1. add "cosmo-alpaca.debugMode": true to your settings.json
2. Help > Toggle developer tools and in those tools switch to console and clear it
3. Reload the Alpaca tree with expanded repo list underneath the org account
4. Check the console logs (please don't leak your token in the headers)

Do you just get an empty array as a response?

If that doesn't show something I think we need to arrange a debugging session together

[NavNab]

The debugMode is greyed out (not sure if clearly visible in te screenshot below). The setting is not available in my version? I followed the steps; the console is completely empty.

[lippertmarkus]

debugMode worked when changing console to verbose log level

The issue leading to organisational repositories not loading was a trailing comma in the settings file. We'll check if we can adapt our backend to handle this as well.

[lippertmarkus]

We just rolled out an update. Our backend can now handle trailing commas in all JSON files and shows more helpful messages if it has issues parsing a Json file in case of errors.