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

Improve error messages #177

Merged
merged 4 commits into from
Jun 9, 2024
Merged

Improve error messages #177

merged 4 commits into from
Jun 9, 2024

Conversation

john-hen
Copy link
Collaborator

@john-hen john-hen commented Jun 9, 2024

Related discussions/issues: #170, #173, #174.

john-hen added 4 commits June 9, 2024 19:22
In some of the log and/or error messages in `discovery.py` we referred
to Comsol's configuration file of its Java VM (which we parse) as the
"Java bridge". This is confusing as the actual (Python-to-)Java bridge
is JPype, and we call it that elsewhere in the docs.
The old error message ("Could not locate any Comsol installation.") was
often misunderstood to mean that MPh somehow failed to find any
installed Comsol whatsoever, when in fact it did, but discarded it for
one reason or another.

This usually happens if the folder structure of the Comsol installation
is different from what we expect. Whether it's an old Comsol version or
a new CPU architecture. We don't even want to try and start those
unfamiliar installations.

Relates to issue MPh-py#174.
The old error message ("Only one client can be instantiated at a time.")
was misunderstood to mean that if users hard-deleted the Python client
object (with `del client`), they could hope to work around this
limitation. The documentation already has plenty of information on that,
but the error message is clearer if we once again emphasize that the
limitation applies to the entire Python session.

Relates to discussion MPh-py#173.
@john-hen john-hen merged commit 240b500 into MPh-py:main Jun 9, 2024
@john-hen john-hen deleted the improve-errors branch June 9, 2024 18:04
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