Skip to content

Conversation

@Freso
Copy link

@Freso Freso commented Feb 16, 2024

The current traceback on a bad known_package_places file doesn’t make it immediately obvious that it’s a local file’s JSON that has been garbled rather than a response from AURweb or elsewhere that’s gone awry.

This commit adds a single message to the JSON decode error to note which file the error is happening in and the user can then either delete the file or try and fix it, depending on the state of the file in question.

The current traceback on a bad known_package_places file doesn’t make it
immediately obvious that it’s a local file’s JSON that has been garbled
rather than a response from AURweb or elsewhere that’s gone awry.

This commit adds a single message to the JSON decode error to note which
file the error is happening in and the user can then either delete the
file or try and fix it, depending on the state of the file in question.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant