Closed Bug 26700 Opened 26 years ago Closed 26 years ago

mozbot-generated UUIDs are not always liked by xpidl

Categories

(Webtools Graveyard :: Mozbot, defect, P3)

Product:
Webtools Graveyard
Component:
Mozbot
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: adam, Assigned: blizzard)

Details

Today I asked mozbot for some shiny fresh UUIDs. One it gave me, for example, was c7786a4-1dd2-11b2-9fbe-c59d742de59b xpidl complained thusly: sIMovemailIncomingServer.idl:36: Error: IID c7786a4-1dd2-11b2-9fbe-c59d742de59b is the wrong length It wanted the UUID padded with zeros, I believe, hence: 0c7786a4-1dd2-11b2-9fbe-c59d742de59b The latter form worked. Assigned to blizzard by request. Cheers, --Adam
Dawn, where is the code for the uuidgen program that I gave you? Did it make into cvs?
Status: NEW → ASSIGNED
I don't remember. It doesn't look like it. Terry added the uuid command to mozbot. Maybe he remembers.
mozbot is using stuff checked in under mozilla/webtools/mozbot/uuidgen.
Are you use you didn't paste this incorrectly? I've gotten mozbot to give me properly give me zero padded uuids. The code looks right, too. I'm going to guess you did or else it was a fluke... <blizzard> uuid <mozbot> 037fd390-1dd2-11b2-94be-bb9b70d69d62
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Perhaps you're right, but I got 'bad' UUIDs on several sittings which were rejected by xpidl until I 0-padded them. Maybe the problem got fixed, or maybe I have no co-ordination. I'm not so sure. I have six UUIDs in a row here gotten from mozbot when I filed the report which came through as 3-2-2-2-6 bytes rather than 4-2-2-2-6 bytes and were hence rejected by xpidl until I added a leading 00. --Adam
Please ignore the spam. Changing address.
Assignee: blizzard → blizzard
Status: RESOLVED → NEW
bustage from my reassign
Status: NEW → RESOLVED
Closed: 26 years ago → 26 years ago
verified
Status: RESOLVED → VERIFIED
QA Contact: mozbot
Target Milestone: --- → 1.0
Version: other → 1.x
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.