...
| Issue | Ref | Workaround | Expected to be resolved |
|---|---|---|---|
| Creating a new voxel using the GXVOX API will result in an assertion when your program closes its GX context. The voxel file is created correctly and the assertion is only triggered on loss of the GX context. This only affects stand-alone programs that create a Geosoft context and close or release the context before the program ends. | #54 | Once a Geosoft context is created, keep a reference to the context through the life of your program. This is most easily accomplished by assigning the context to a global variable or reference. | Platform 9.3.1 |
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 we would have fixed them. But writing new code and using the API in new ways can reveal problems we have not seen and thus trigger as assertion. | #55 | Execute your code outside of a test to trigger the assertion, which will create a aborl log file. Report the abort to Geosoft so we can fix it in a future platform release and use the log information to debug your script. There is most likely something wrong with the way the script is calling the API. | Platform 9.4 |