| Summary: | MySQL Errors when attempting to add new map file | ||
|---|---|---|---|
| Product: | [Technology] Babel | Reporter: | Matthew Davis <mattadav> |
| Component: | Server | Assignee: | Denis Roy <denis.roy> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | kitlo |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| URL: | URL_TO_THE_STRING | ||
| Whiteboard: | |||
|
Description
Matthew Davis
Denis, can you take a look at this? That was funny. Those mysql errors were in the actual babel database as values, not as an actual connectivity error. The Eclipse projects list is pulled from this web-api: http://www.eclipse.org/projects/web-api/project_release_versions.php At some point that API must have been unavailable, so bad values were inserted. I've removed those bad values; if ever this happens again, I'll make the import more robust. Interesting. Thanks Denis. Still leaves a question - how is the list of releases for a project generated (at ttp://www.eclipse.org/projects/web-api/project_release_versions.php). It shows none for technology.stem, yet we have 4 or 5 releases (and completed) in our project metadata. > yet we have 4 or 5 releases (and completed) in
> our project metadata.
Version information is pulled from Bugzilla. It appears STEM hasn't defined any version information in Bugzilla.
In a perfect world, Bugzilla versions would be pulled from the meta-data so that you don't have to do this twice. Sorry.
Ah ok. Thanks Denis ! |