Scripts to the nth
I wrote up several paragraphs for Leigh on relative and absolute links question. Greg challenged one of my claims, so I'll have to research the issue further on Monday. I worked with Greg on revising Remedy so users are forced to enter hours worked and so that the division and branch names for users are fetched from ldap. The latter required modifying my ldapfield.pl script, as it did not match the information currently stored in Remedy. My webspider.pl script failed to complete running, as it overflowed memory. I have to figure out a work around for that problem. Greg also suggested that I only report errors that are not on the production site, as the purpose of the script is to testthe poskey error fix. I changed the code, but there are still some errors in the modification which will need to be fixed.
Posted on Fri, 15 Jul 2005 Tags: poskey ldap remedy
This and That
I moved the change to repairMetadata into CVS and wrote up a test plan for it. I tested Leigh's conference registration form. It passed. Then I reworked Mike's metrics scripts to support the POSKey testing.
Posted on Thu, 23 Jun 2005 Tags: poskey repairmetadata
Back to the Grind
I'm back at work after a week and a half vacation. I spent a lot of time going through old email. We met and discussed Anne's memo on Zope risk assessment as well as meeting and talking about the proposed poskey error. Greg pointed out a possible problem with repairMetadata that I will have to investigate.
Posted on Thu, 16 Jun 2005 Tags: poskey repairmetadata zope
More Poskey
Craig reported my permissions fix didn't pass the test. I checked and it had not been checked out of CVS. We'll need to discuss and document our CVS procedures. I worked with Greg some more on the Poskey problem. We outlined our proposed solution and then started working on a new, more conservative solution.
Posted on Fri, 03 Jun 2005 Tags: poskey
A Problem solved
I worked with Greg today on two problems. The first was configuring the development and test versions on remedy, which was pretty straightforward. The second was figuring out a way to fix the last stubborn poskey error. We finally hit on a method that copies the contents of the object to a new object, clears the object and copies it back. So now we're ready to fix the production database.
Posted on Thu, 02 Jun 2005 Tags: poskey remedy
Zope Debugging
I debugged the GenericLog class in the morning and worked with Greg on Poskey error repair in the afternoon.
Posted on Tue, 24 May 2005 Tags: poskey
Poskey Problems
I located and ran my poskey checking script. Unfortunately, it doesn't print enough information to locate the errors. I looked at the other Zope utilities and ran fsdiff, which doesn't report errors. I got a request for an ldap management screen that only contains the essential fields. I said it would be easy to create and forwarded a list of fields I thought were essential.
Posted on Wed, 18 May 2005 Tags: ldap zope poskey
Zope and Badlinks
I copied the production database over to battra and restarted it in hopes of finding the poskey errors. That didn't work. Running the zope utilities showed that we have a number of hard errors in the database, we are trying to locate them. Our current strategy is to find the hard errors, fix them, and pray this resolves the problem. My last attempted fix of the badlinks script was to force the base url to the contents of the base tag where it exists. That seems to have resolved the problem, so I put the script backinto operation. Bobby Edwards reported a problem updating a user's record in ldap. My guess is that the problem happened because the user doesn't have a divisional administrator. I am still investigating. I need to find the tools I wrote for the poskey tiger team so we can do further investigation.
Posted on Tue, 17 May 2005 Tags: poskey ldap zope
Poskey Errors
I installed the latest version of ext on the science cluster and then worked with Greg and tried to debug the new poskey errors Mike Wiggs reported.
Posted on Mon, 16 May 2005 Tags: poskey
Today's Work
I helped Mike with the POSKey repairs, which unfortunately left some stuff unfixed. I also started work on Lynn performance monitoring tool and wrote one of two major classes, Timerange, which does all the date manipulation.
Posted on Wed, 21 Jul 2004 Tags: poskey