> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:owner-hackystat-dev- > [EMAIL PROTECTED] On Behalf Of Aaron Akihisa Kagawa > Sent: Tuesday, November 16, 2004 1:51 PM > To: [EMAIL PROTECTED] > Subject: [HACKYSTAT-DEV-L:330] Re: Need help deciphering log > > Cedric, Philip, I had a little summit meeting about issue. We discussed a > couple of things: > > 1) Regarding the setProperty method, we are still a little unsure why the > CVS sensor would work and JIRA sensor won't. > 2) We are still aren't totally sure that if you adding this setProperty > method would solve the problem. Even though AutoSend is not enabled you > should still be able to force a send by calling the send method. > > To conclude, this AutoSend problem doesn't seem like a show stopper and > there must be some other problems that is causing it not to work. > Therefore, we think you should wait to solve this AutoSend problem. >
In my last email I said " The sensor data is now sent successfully to both my local hackystat server and the live server." Therefore the problem of sending/receiving sensor data has been resolved. The setProperty suggestion that I had only pertained to enabling SensorShell autosend. The JiraSensor does not need this property to be enabled but future sensors might. Thanks, Burt > > thanks, aaron > > > > > > > > -----Original Message----- > > > From: Aaron Akihisa Kagawa [mailto:[EMAIL PROTECTED] > > > Sent: Tuesday, November 16, 2004 11:54 AM > > > To: [EMAIL PROTECTED] > > > Subject: Re: [HACKYSTAT-DEV-L:327] Re: Need help deciphering log > > > > > > Take a look at Cedric's hackyVCS code. I'm pretty sure he has a > > > sensorshell > > > map that works for the Commit Sensor. > > > > > > thanks, aaron > > > > > > At 03:53 AM 11/16/2004 -1000, you wrote: > > > >Hello Aaron, > > > > > > > >Thank you very much for your email. > > > > > > > >I don't have a full reply yet but for #3 I believe the reason is > because > > > I > > > >am dynamically instantiating the SensorProperties for each user > mapped. > > > > > > > >The relevant code in SensorShellMap: > > > >SensorShell userShell = new SensorShell( > > > > new SensorProperties(this.hackystatHost, userKey), false, > this.tool); > > > > > > > >The SensorShellMap cannot simply parse the > .hackystat/sensor.properties > > > file > > > >on the computer. It must dynamically instantiate a unique instance > for > > > every > > > >mapped user. > > > > > > > >Unfortunately this means that there is no way to set the auto-send > > > property. > > > >If a "setProperty" method were added to SensorProperties then I could > do > > > so. > > > > > > > >Is there another suggestion you might have? > > > > > > > >Thanks again, > > > >Burt > > > > > > > > > > > > > -----Original Message----- > > > > > From: [EMAIL PROTECTED] [mailto:owner-hackystat- > dev- > > > > > [EMAIL PROTECTED] On Behalf Of Aaron Kagawa > > > > > Sent: Tuesday, November 16, 2004 2:18 AM > > > > > To: [EMAIL PROTECTED] > > > > > Subject: [HACKYSTAT-DEV-L:326] Re: Need help deciphering log > > > > > > > > > > > > > 3) Something looks weird in your log file.. > > > > > > > > > > >>AutoSend not enabled. > > > > > >>Server not available; offline data not recovered this session. > > > > > > > > > > Why is AutoSend not enabled? I forget what AutoSend really > indicates, > > > > > however all the other sensors we have the following in the log. > > > > > > > > > > #> AutoSend [10] > > > > > AutoSend OK (set to 10 minutes) > > > > > AutoSend enabled every 10 minutes. > > > > > Checking for offline data to recover. > > > > > No offline data found. > > > > > #> Activity [setTool, Eclipse] > > > > > setTool OK > > > > > > > > > > Yours is different for some reason. Why? > > > > > > > > > > > > > > > > > thanks, aaron > > > > > > > > > > At 05:02 PM 11/15/2004 -1000, you wrote: > > > > > >Hello Everyone, > > > > > > > > > > > >The story goes that today I was up on hackydev trying to install > the > > > Jira > > > > > >Sensor. It constantly gave a SOAP invocation error upon the > > > SensorShell > > > > > >send. At the end I decided that it had something to do with the > SDT > > > and > > > > > went > > > > > >back home. > > > > > > > > > > > >When I got back home I did a cvsUpdateAll and freshStart. I tried > to > > > > > >reproduce the error using my local Hackystat host (LHS) without > > > success! > > > > > In > > > > > >other words sending of Jira sensor data and receiving of it was > > > > > successful > > > > > >on my personal computer. > > > > > > > > > > > >So as a debugging step I tried editing my sensor.properties file > to > > > point > > > > > to > > > > > >the official hackystat server (OHS) instead of my LHS. However, I > got > > > a > > > > > >strange log entry. As can be seen from the below excerpt the > initial > > > ping > > > > > of > > > > > >OHS indicates that the server is online and that the key is > valid. > > > > > However, > > > > > >upon subsequent SensorShell send attempts it says that "Server > not > > > > > >available. Storing commands offline." > > > > > > > > > > > >Does anyone have any input on this contradictory log entry? > > > > > > > > > > > >Thanks! > > > > > >Burt > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >Hackystat Version: 6.3.1115 (November 15 2004 16:24:03) > SensorShell > > > > > started > > > > > >at: 11/15/2004 16:54:27 Type 'help' for a list of commands. > > > > > >Host: http://hackystat.ics.hawaii.edu/ is available and key is > valid. > > > > > >Defined shell command: Issue > > > > > >Defined shell command: Perf > > > > > >Defined shell command: FileMetric > > > > > >Defined shell command: ReviewIssue > > > > > >Defined shell command: Activity > > > > > >Defined shell command: Cli > > > > > >Defined shell command: ReviewActivity > > > > > >Defined shell command: Coverage > > > > > >Defined shell command: BuffTrans > > > > > >Defined shell command: Commit > > > > > >Defined shell command: UnitTest > > > > > >Defined shell command: Build > > > > > >AutoSend not enabled. > > > > > >Server not available; offline data not recovered this session. > > > > > >#> Issue [setTool, Jira] > > > > > >setTool OK > > > > > >#> Issue [add, bug 1216, Bug, Major, ISSUE_WORKSTARTED, , > > > > > > > > > >reporter=bleung;assignee=bleung;project=10000;workflowId=10021;status=In > > > > > >Progress] Issue add OK (1) #> send Server not available. Storing > > > commands > > > > > >offline. > > > > > > >>
