rdalbuquerque / azdoext

MIT License
10 stars 0 forks source link

panic: exit status 1 #4

Closed hoppalazi closed 2 months ago

hoppalazi commented 2 months ago

Hey, after installation i can successfully run azdoext -version with output v0.0.1. But running just azdoext after setting the environment variable AZDO_PERSONAL_ACCESS_TOKEN leads to following error stack:

panic: exit status 1

goroutine 71 [running]:
azdoext/pkgs/gitexec.Config()
/home/runner/work/azdoext/azdoext/pkgs/gitexec/gitexec.go:32 +0x198
main.(*model).Init.getAzdoConfig.func1()
/home/runner/work/azdoext/azdoext/main.go:68 +0x25
github.com/charmbracelet/bubbletea.(*Program).handleCommands.func1.1()
/home/runner/go/pkg/mod/github.com/charmbracelet/bubbletea@v0.25.0/tea.go:294 +0x29
created by github.com/charmbracelet/bubbletea.(*Program).handleCommands.func1 in goroutine 69
/home/runner/go/pkg/mod/github.com/charmbracelet/bubbletea@v0.25.0/tea.go:293 +0x139
rdalbuquerque commented 2 months ago

Hi, are you running from an initiated git repo with an azure devops remote origin? If not, please do so, I still need better error handling for that.

hoppalazi commented 2 months ago

No, i was just in my user directory. I somehow missed that i have to be in a Azure DevOps repository. Edit: After being in Azure DevOps repository, it does start without a problem. Edit2: Seems not entirely resolved, since it seems not to detect Azure DevOps pipelines

rdalbuquerque commented 2 months ago

I've also added better error handling in 20a13722eb08dad0facdd6b5f017f8d6df6bb0c5

rdalbuquerque commented 2 months ago

No, i was just in my user directory. I somehow missed that i have to be in a Azure DevOps repository. Edit: After being in Azure DevOps repository, it does start without a problem. Edit2: Seems not entirely resolved, since it seems not to detect Azure DevOps pipelines

note that only yaml pipelines are supported, the classic release pipelines are not. There is also a filter so you are only shown the ones from your repository.

hoppalazi commented 2 months ago

If you're fine with that, i'd close this isse since the original issue is resolved and open another issue regarding the missing pipelines.

rdalbuquerque commented 2 months ago

Sure, we can do that