# general


07/26/2023, 11:48 AM
Is there any easy way to debug errors such as this when trying to run a `pulumi up`:
Copy code
  pulumi:pulumi:Stack (service.django-poc-dev-azure):
    error: an unhandled error occurred: program exited with non-zero exit code: 2

    panic: fatal: An assertion has failed: 0xc0004239a0: cannot assign *string to string
    goroutine 1235 [running]:
It's using the azure-native provider in Go. I can post the rest of the stack trace if needed, though the issue is that none of it points to where in my code there's an error. Figured it's a generic enough error, and I can't really pinpoint the specific issue thanks to how vague the error is. I have vaguely narrowed it down by commenting out chunks of code at a time, but it's taken quite some time. I guess more broadly, I've run into a few errors like this which give me a very vague/unhelpful output, some of this is more on the pulumi side, some more from the provider responses, it would be good to know if there are any flags and tools I can use to get some useful debug information (--debug and -v have not been particularly enlightening)