Closed
Bug 435113
Opened 16 years ago
Closed 16 years ago
audit cgis in old and new repos to ensure consistency
Categories
(Webtools Graveyard :: Graph Server, defect)
Webtools Graveyard
Graph Server
Tracking
(Not tracked)
RESOLVED
FIXED
0.3
People
(Reporter: anodelman, Assigned: laura)
References
Details
Attachments
(1 file)
1.50 KB,
patch
|
anodelman
:
review+
|
Details | Diff | Splinter Review |
The copy of graphs/server/getdata.cgi in hg has a non-operational copy of getdata.cgi (it contains a bad sql query that breaks). The problem hasn't been noticed yet because our currently up versions of the new graph server front end uses the old cvs code for accessing the database - nobody is currently using the new hg db interaction code. A fresh copy should be pulled from cvs to replace the broken version and get us back to a working state.
Updated•16 years ago
|
Assignee: nobody → laura
Target Milestone: --- → 0.3
Reporter | ||
Comment 1•16 years ago
|
||
Looking over this, I think that there are also changes to bulk.cgi/collect.cgi/graphsdb.py that are only in cvs and not in hg. We need to get this server code lined up so that we'll be able to run a standalone version of the hg code without having to intermix bits and pieces of cvs server code.
Assignee | ||
Updated•16 years ago
|
Summary: hg repository of graph server contains bad copy of getdata.cgi → audit cgis in old and new repos to ensure consistency
Comment 2•16 years ago
|
||
Here's the fix for getdata.cgi
Attachment #328581 -
Flags: review?(anodelman)
Reporter | ||
Updated•16 years ago
|
Attachment #328581 -
Flags: review?(anodelman) → review+
Assignee | ||
Comment 3•16 years ago
|
||
Note: rdoherty's fix has been committed (by alice I presume). At least it's in hg.
Assignee | ||
Comment 4•16 years ago
|
||
On review, the remainder of the differences are around the change in link format, and new additions to hg. Calling this done.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Updated•8 years ago
|
Product: Webtools → Webtools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•