Skip to content
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

Config file with bad provider value fails with NPE and logging doesn't catch it #531

Closed
HEdingfield opened this issue Oct 5, 2020 · 1 comment
Assignees
Milestone

Comments

@HEdingfield
Copy link
Contributor

If you load the attached config file in the latest build, the console shows an NPE, but the log file doesn't record it (I've included in the .zip both the log file and the console output for comparison).

Furthermore, the GUI seems to behave erratically after this has happened (unresponsive CVR Files table, etc.).

Note: The config file is clearly bad because it has "ES&S" as a provider, when it should now be "ess", as well as a few other differences. It also has the version "1.2.0_alpha", so the migration logic isn't triggered. However, even if I change the version to "TEST" or "1.1.0" and the migration logic is triggered, it appears to just freak out when encountering the "ES&S" value.

2013_minneapolis_mayor_config.zip

@HEdingfield
Copy link
Contributor Author

The immediate problem is closed with #532. The problem of logs not picking up the NPE isn't resolved though, and I'm not sure if it's even possible. Might open a future issue on this...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants