No scrap stations causes warning and aborts deleting log contents
This warning occasionally occurs and aborts Therion compilation, despite it only being a warning. In addition the therion log file also only contains the warning. All other information is removed and no other output is produced. "C:\Program Files (x86)\Therion\therion.exe: warning -- error deleting temporary directory -- C:\Users\Bruce\AppData\Local\Temp\th7272" Sometime back, 5.3.16-ish I think, this type of warning was just that, a warning that did not impact on the project being compiled. After a while Therion, or the user, would successfully delete the temporary folder and all would be well. This time around this project would not get past the error, even though I manually deleted all the temporary folders. Other projects compiled OK. As is often the case, it was my own fault, I was busy drawing, and had created a new scrap, but had forgotten to add any 'point stations'. As I had not scaled the scrap either, Therion quite rightly did not know where to put it or what size to make it. The result being Therion aborts with the above warning and deletes all log information that the user could have used to debug the situation. I seem to recall that this scenario used to cause a different error message, but one that was a little more helpful to the user. Maybe this could be trapped and a useful message provided in a future release? Thanks Bruec
I got the same "red" warning (error deleting temporary directory) today. The scrap was fine, but I forgot to insert "data normal from to compass clino tape" before all measurements in the centreline part. Torstein Den 17.09.2017 03.12, skrev Bruce Mutton via Therion:
This warning occasionally occurs and aborts Therion compilation, despite it only being a warning.
In addition the therion log file also only contains the warning. All other information is removed and no other output is produced.
“C:\Program Files (x86)\Therion\therion.exe: warning -- error deleting temporary directory -- C:\Users\Bruce\AppData\Local\Temp\th7272”
Sometime back, 5.3.16-ish I think, this type of warning was just that, a warning that did not impact on the project being compiled.
After a while Therion, or the user, would successfully delete the temporary folder and all would be well.
This time around this project would not get past the error, even though I manually deleted all the temporary folders. Other projects compiled OK.
As is often the case, it was my own fault, I was busy drawing, and had created a new scrap, but had forgotten to add any ‘point stations’. As I had not scaled the scrap either, Therion quite rightly did not know where to put it or what size to make it. The result being Therion aborts with the above warning and deletes all log information that the user could have used to debug the situation.
I seem to recall that this scenario used to cause a different error message, but one that was a little more helpful to the user.
Maybe this could be trapped and a useful message provided in a future release?
Thanks
Bruec
_______________________________________________ Therion mailing list Therion@speleo.sk https://mailman.speleo.sk/listinfo/therion
Pure Therion, how it has to understand you what you want from it? m.s.
23. 9. 2017 v 17:56, torstein finnesand via Therion <therion@speleo.sk>:
I got the same "red" warning (error deleting temporary directory) today. The scrap was fine, but I forgot to insert "data normal from to compass clino tape" before all measurements in the centreline part.
Torstein
<idoimkbjmdpllfjl.png>
Den 17.09.2017 03.12, skrev Bruce Mutton via Therion:
This warning occasionally occurs and aborts Therion compilation, despite it only being a warning. In addition the therion log file also only contains the warning. All other information is removed and no other output is produced.
“C:\Program Files (x86)\Therion\therion.exe: warning -- error deleting temporary directory -- C:\Users\Bruce\AppData\Local\Temp\th7272”
Sometime back, 5.3.16-ish I think, this type of warning was just that, a warning that did not impact on the project being compiled. After a while Therion, or the user, would successfully delete the temporary folder and all would be well.
This time around this project would not get past the error, even though I manually deleted all the temporary folders. Other projects compiled OK.
As is often the case, it was my own fault, I was busy drawing, and had created a new scrap, but had forgotten to add any ‘point stations’. As I had not scaled the scrap either, Therion quite rightly did not know where to put it or what size to make it. The result being Therion aborts with the above warning and deletes all log information that the user could have used to debug the situation.
I seem to recall that this scenario used to cause a different error message, but one that was a little more helpful to the user. Maybe this could be trapped and a useful message provided in a future release?
Thanks Bruec
_______________________________________________ Therion mailing list Therion@speleo.sk <mailto:Therion@speleo.sk> https://mailman.speleo.sk/listinfo/therion <https://mailman.speleo.sk/listinfo/therion>
_______________________________________________ Therion mailing list Therion@speleo.sk <mailto:Therion@speleo.sk> https://mailman.speleo.sk/listinfo/therion <https://mailman.speleo.sk/listinfo/therion>
yes, You've got a point there :-) T Den 23.09.2017 18.03, skrev Martin Sluka via Therion:
Pure Therion, how it has to understand you what you want from it?
m.s.
23. 9. 2017 v 17:56, torstein finnesand via Therion <therion@speleo.sk <mailto:therion@speleo.sk>>:
I got the same "red" warning (error deleting temporary directory) today. The scrap was fine, but I forgot to insert "data normal from to compass clino tape" before all measurements in the centreline part.
Torstein
<idoimkbjmdpllfjl.png>
Den 17.09.2017 03.12, skrev Bruce Mutton via Therion:
This warning occasionally occurs and aborts Therion compilation, despite it only being a warning. In addition the therion log file also only contains the warning. All other information is removed and no other output is produced. “C:\Program Files (x86)\Therion\therion.exe: warning -- error deleting temporary directory -- C:\Users\Bruce\AppData\Local\Temp\th7272” Sometime back, 5.3.16-ish I think, this type of warning was just that, a warning that did not impact on the project being compiled. After a while Therion, or the user, would successfully delete the temporary folder and all would be well. This time around this project would not get past the error, even though I manually deleted all the temporary folders. Other projects compiled OK. As is often the case, it was my own fault, I was busy drawing, and had created a new scrap, but had forgotten to add any ‘point stations’. As I had not scaled the scrap either, Therion quite rightly did not know where to put it or what size to make it. The result being Therion aborts with the above warning and deletes all log information that the user could have used to debug the situation. I seem to recall that this scenario used to cause a different error message, but one that was a little more helpful to the user. Maybe this could be trapped and a useful message provided in a future release? Thanks Bruec
_______________________________________________ Therion mailing list Therion@speleo.sk https://mailman.speleo.sk/listinfo/therion
_______________________________________________ Therion mailing list Therion@speleo.sk <mailto:Therion@speleo.sk> https://mailman.speleo.sk/listinfo/therion
_______________________________________________ Therion mailing list Therion@speleo.sk https://mailman.speleo.sk/listinfo/therion
The real issue is that Therion should give meaningful and helpful compilation logs and error messages. In Torstein’s example, it should be perhaps something like “unexpected option ‘2.0’ in file xxx on line yyy” and it should exit gracefully while retaining the contents of the therion.log file. The error should be trapped before Therion gets to the point of reporting a subsequent state of chaos that is somewhat unrelated to what should be an anticipated and reasonably expected user error. Bruce From: Therion [mailto:therion-bounces@speleo.sk] On Behalf Of torstein finnesand via Therion Sent: Sunday, 24 September 2017 5:31 AM To: therion@speleo.sk Cc: torstein finnesand <torstein.finnesand@gmail.com> Subject: Re: [Therion] No scrap stations causes warning and aborts deleting log contents yes, You've got a point there :-) T Den 23.09.2017 18.03, skrev Martin Sluka via Therion: Pure Therion, how it has to understand you what you want from it? m.s. 23. 9. 2017 v 17:56, torstein finnesand via Therion <therion@speleo.sk <mailto:therion@speleo.sk> >: I got the same "red" warning (error deleting temporary directory) today. The scrap was fine, but I forgot to insert "data normal from to compass clino tape" before all measurements in the centreline part. Torstein <idoimkbjmdpllfjl.png> Den 17.09.2017 03.12, skrev Bruce Mutton via Therion: This warning occasionally occurs and aborts Therion compilation, despite it only being a warning. In addition the therion log file also only contains the warning. All other information is removed and no other output is produced. “C:\Program Files (x86)\Therion\therion.exe: warning -- error deleting temporary directory -- C:\Users\Bruce\AppData\Local\Temp\th7272” Sometime back, 5.3.16-ish I think, this type of warning was just that, a warning that did not impact on the project being compiled. After a while Therion, or the user, would successfully delete the temporary folder and all would be well. This time around this project would not get past the error, even though I manually deleted all the temporary folders. Other projects compiled OK. As is often the case, it was my own fault, I was busy drawing, and had created a new scrap, but had forgotten to add any ‘point stations’. As I had not scaled the scrap either, Therion quite rightly did not know where to put it or what size to make it. The result being Therion aborts with the above warning and deletes all log information that the user could have used to debug the situation. I seem to recall that this scenario used to cause a different error message, but one that was a little more helpful to the user. Maybe this could be trapped and a useful message provided in a future release? Thanks Bruce
participants (3)
-
Bruce Mutton -
Martin Sluka -
torstein finnesand