You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am curious as to what OS you guys are running this on. Typically I would say it wouldn't matter but I have had a heck of a time getting STF running on centos5. It only took about 15 minutes to have it up and running on a debian box.
I can provide the debug and trace output as needed but the issue is as follows:
When the dispatcher is called from Net::STF::Client I see a 500 error. Upon further investigation I notice that die is getting called in the record function of Entity (line 102 in the current master). I have been adding additional debugging statements to try and track down the issue but all I have been able to see is the hash that gets passed to Entity->store has the storage ID correctly set, and then inside record the die function is invoked. I am not exactly sure what is happening here. I didn't spot where Mouse would be wrapping the args to that function but I was hoping you guys would be able to provide some deeper insight.
Best,
Elliott Davis
The text was updated successfully, but these errors were encountered:
Jesus, where's the button that forces notifications to be sent on every issue filed... grrr
Apologies on the delay to respond.
We actually run STF on Centos5! So am not sure if this is a platform specific issue.
The only thing that I can immediately think of that would be system-specific would be the usage of system perl (i.e. installed via rpm/yum): i.e., maybe you're invoking the wrong perl or something like that.
Did setting STF_DEBUG=1 show any useful debug output?
I am curious as to what OS you guys are running this on. Typically I would say it wouldn't matter but I have had a heck of a time getting STF running on centos5. It only took about 15 minutes to have it up and running on a debian box.
I can provide the debug and trace output as needed but the issue is as follows:
When the dispatcher is called from Net::STF::Client I see a 500 error. Upon further investigation I notice that die is getting called in the record function of Entity (line 102 in the current master). I have been adding additional debugging statements to try and track down the issue but all I have been able to see is the hash that gets passed to Entity->store has the storage ID correctly set, and then inside record the die function is invoked. I am not exactly sure what is happening here. I didn't spot where Mouse would be wrapping the args to that function but I was hoping you guys would be able to provide some deeper insight.
Best,
Elliott Davis
The text was updated successfully, but these errors were encountered: