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
10.10 Beta crash when creating a new user #1961
Comments
Confirmed in nb 0c2ea8b Related crash is: The stack trace doesn't show any involvement of Sequel Pro, though. So I'm not sure this is actually our fault. |
Happens on the release version of Yosemite too |
I can confirm this too, using Maria DB locally on Yosemite release. Every time I add a user it crashes. |
I can reproduce this every time I add a user. Happy to provide further information if any is needed. |
@TheLastCicada it's been already solved. You can download the files, compile it, and it will be working now. |
Are the installation instructions on GitHub the official way to install Sequel Pro now? Are there no more official releases on http://www.sequelpro.com/? It has been 18 months since version 1.0.2 on Github. The "check for updates" in Sequel Pro is no longer useful to get bugfix releases? Any of these options are fine, I'm just finding this really confusing as to what I'm supposed to do as a user at this point. |
As a user: As a software developer: |
a) http://nightly.sequelpro.com/ doesn't work any more. |
It hasn't been touched because it is fixed and closed. |
Apologies again. The newest release is indicated as release-1.0.2, although I see that there are nearly two years' worth of commits since then. Are the updates no longer receiving release numbers? |
The nightly builds indicate that they are not suitable for use in “a production environment”. Could you let me know where I can download the latest stable version please? |
I agree, 1.0.2 is a bit outdated by now, but still the most recent official version. |
OK, thanks for the update. |
I'm experiencing this on
Sequel Pro 1.0.2
. Steps are:#1940 Possibly related, although different stack traces.
My system:
Stack trace:
The text was updated successfully, but these errors were encountered: