Opened 8 years ago
Closed 8 years ago
#52672 closed defect (fixed)
Cc field is getting corrupted by Trac-to-GitHub username conversion
Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | neverpanic (Clemens Lang) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | server/hosting | Version: | |
Keywords: | Cc: | mkae (Marko Käning), raimue (Rainer Müller) | |
Port: |
Description
It looks like the conversion of Trac usernames to GitHub usernames is corrupting the Cc field by concatenating names without leaving a space or comma between them.
For example #11497 where Cc currently is markd@macports.orgryandesignscottm@aero.org
and #51995 where Cc is ryandesignraimueneverpaniclarryv
Change History (7)
comment:1 Changed 8 years ago by mkae (Marko Käning)
Cc: | mkae added |
---|
comment:2 Changed 8 years ago by neverpanic (Clemens Lang)
Owner: | changed from admin@… to neverpanic |
---|---|
Status: | new → accepted |
comment:3 Changed 8 years ago by neverpanic (Clemens Lang)
Cc: | raimue added |
---|
comment:4 Changed 8 years ago by neverpanic (Clemens Lang)
I think I figured the problem out. Now I'll just have to reset the Cc fields to what they were before the dump and re-run the conversion.
We'll loose all changes to Cc fields since yesterday evening, but that's a risk I'm willing to take if the other solution would be modifying thousands of tickets.
comment:5 Changed 8 years ago by ryandesign (Ryan Carsten Schmidt)
Yes. You could probably query the database to get a list of changes made to any Cc field since the switchover. Unless the conversion script triggers that.
comment:6 Changed 8 years ago by neverpanic (Clemens Lang)
The conversion script does not keep a record of the changes, it modifies the fields directly. I'm importing the export from MacOSForge right now and will generate a query that re-sets the Cc fields.
comment:7 Changed 8 years ago by neverpanic (Clemens Lang)
Resolution: | → fixed |
---|---|
Status: | accepted → closed |
Problem fixed, we restored yesterday's Cc fields, fixed the migration plugin and re-run the migration.
Thanks for the notice. I've disabled the automatic migration for now and will look into it.