...
| Issue | Ref | Suggestion | Expected to be resolved | |||
|---|---|---|---|---|---|---|
PyCharm users (and possibly other IDE users), if a gxapi function is called that results in an assertion inside Geosoft, the assertion will be lost when running tests. You may see "Process finished with exit code 95867", or some other behaviour in which the process stops and provides no information. If a script that triggers an assertion is run outside of a test scenario you will see an assertion dialog and an assertion log file will be created. Triggering an assertion is most likely caused by using the API incorrectly, either by doing things out of sequence or by passing invalid parameters. The purpose of an assertion is to detect an assumed impossible situation and provide us with the information we need to find and fix the now-proven possible. Geosoft code and tests do not trigger such assertions because if they did they would have would have fixed. But writing new code and using the API in new ways can reveal problems we have not seen and thus trigger an assertion. We usually only need the abort.log file to figure out what went wrong. We and all your fellow developers are thankful if you can send us the file. We do our best to fix any reported assertions in the next monthly maintenance release. | na | Execute your code outside of PyCharm (or your IDE) to trigger the assertion, which will create a abort log file. Submit a support request and attach the abort.log file so we can fix it in a future platform release. You can also review the log information to help debug your script. There is most likely something wrong with the way the script is calling the API. | na
|