-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
crash report #11
Comments
Thank you for posting it here! Is it possible to tell what version of the plugin they used? It doesn't appear that we ever pushed a v0.5.1 as indicated in the trace there. The latest v0.6.0 release includes the Py3 changes that you submitted to the repository and was released here in early June 2020. |
It is in the last line of the report. |
It looks like that is an old release. Possible to ask the user to attempt an update to v0.6.0 and report directly in this thread? I can work with them on a fix. |
The current version is 0.5.1-51. and the code at that location is not fixed |
What is the current Py environment jn the release of the editor reported here? |
Has the path to this Glyphs file been changed? |
My understanding is that this is a default file distributed with releases, no? Is this a situation where the user deleted it or should it not be there in some distributions? In any case, it looks like we just need to catch the missing file path issue and raise a warning. |
The file is created the first time the user changes the filters. |
ty! |
Still not fixed?? |
I got this from a user:
The text was updated successfully, but these errors were encountered: