04-29-2020, 09:14 PM
Hi. I know you posted one with the following ...
File "/home/apache/tactic/src/pyasm/search/search.py", line 229, in __init__
raise SearchException('This database [%s] does not exist' %self.database)
pyasm.search.search.SearchException: This database [sthpw] does not exist
However, this is not the stack trace that is producing the error: "No module named 'spt'". It is possible that this is an effect of a previous error. This happens sometimes where, for whatever reason, a stack trace causes another cascade of stack traces that get dumped to the console. Usually, it is the first stack trace that matters.
The long output does have the error at the bottom from the get_widget function, but there is no stack trace ... it's just a function output. One of the reasons it's difficult to find is because we have a client side javascript namespace "spt" and also a server one, so searching for it is difficult because of the hundreds of references to the javascript "spt"
File "/home/apache/tactic/src/pyasm/search/search.py", line 229, in __init__
raise SearchException('This database [%s] does not exist' %self.database)
pyasm.search.search.SearchException: This database [sthpw] does not exist
However, this is not the stack trace that is producing the error: "No module named 'spt'". It is possible that this is an effect of a previous error. This happens sometimes where, for whatever reason, a stack trace causes another cascade of stack traces that get dumped to the console. Usually, it is the first stack trace that matters.
The long output does have the error at the bottom from the get_widget function, but there is no stack trace ... it's just a function output. One of the reasons it's difficult to find is because we have a client side javascript namespace "spt" and also a server one, so searching for it is difficult because of the hundreds of references to the javascript "spt"