-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fatal error: systemstack called from unexpected goroutine #34
Comments
Get the same errors, FWIW |
Any resolution for this? I am facing the same issue. |
I punted on using this.
I started using https://dbeaver.io/ which has a feature for comparing databases.
And then when it didn’t do what I wanted. I wrote my own.
Ken
From: Umer Khan <[email protected]>
Reply-To: joncrlsn/pgdiff <[email protected]>
Date: Wednesday, August 15, 2018 at 7:31 AM
To: joncrlsn/pgdiff <[email protected]>
Cc: "Ken Chambers (kchamber)" <[email protected]>, Author <[email protected]>
Subject: Re: [joncrlsn/pgdiff] fatal error: systemstack called from unexpected goroutine (#34)
Any resolution for this? I am facing the same issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#34 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AHKnPOZVStQDV0B08tHR88i7WnseHENfks5uRAaKgaJpZM4TzD-M>.
|
Hi Guys, If somebody has the resolution to this issue, please share. VK |
Facing same issue here :( |
Hello all, did anyone fine any solution for this yet? |
same issue here |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm hitting this error as well. Just pulled down the Macos binary, pgdiff-osx-1.0b1.tar
And updated the shell script, and launched.
fatal error: systemstack called from unexpected goroutine
fatal error: systemstack called from unexpected goroutine
<<1800 lines of the above>>
MacOS High Sierra 10.13.3
psql (PostgreSQL) 10.3 (but doubt this is an issue b/c doesn't look like its even getting to the point of talking to Postgres
Any tips greatly appreciated. I know nothing of 'go'.
Ken
The text was updated successfully, but these errors were encountered: