| View Issue Details [ Jump to Notes ] [ Related Changesets ] | [ Issue History ] [ Print ] |
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 017 | Source Integration | [All Projects] General | public | 2009-04-12 22:02 | 2009-04-13 06:14 |
|
| Reporter | David Hicks | |
| Assigned To | John Reese | |
| Priority | normal | Severity | block | Reproducibility | always |
| Status | resolved | Resolution | fixed | |
| Product Version | | |
| Target Version | 0.14 | Fixed in Version | 0.14 | |
|
| Summary | 017: Infinite change-set importing as a result of changes made in ticket 014 |
| Description | Fix 014 (commit 1e92fc01b352ea646e5adc0e306b3848f9dcf6ed) introduced the ability to poll the WebSVN/GitWeb/etc plugins for change-sets in a batch mode. A memory limit will be reached if too many change-sets are imported at once.
The problem is that the plugins currently:
a) Don't know how many change-sets to import per batch (this should be user configurable, or based on the PHP memory limit + maximum script execution time)
b) Don't know how many batches have already been read (and thus they currently import everything... infinite times)
It may also be necessary to refresh the import page multiple times (one refresh per 200 changesets for example) to avoid hitting the script execution time limit in place on many servers.
Additionally, the event EVENT_SOURCE_IMPORT_FULL should really be renamed to something more appropriate such as EVENT_SOURCE_IMPORT_BATCH_FIRST and EVENT_SOURCE_IMPORT_BATCH_NEXT. The current IMPORT_FULL event hook no longer does a full import. The same is applicable for EVENT_SOURCE_IMPORT_LATEST. |
| Tags | No tags attached. |
|
| Attached Files | |
|
Relationships 
Relationships 
(007)
