BUG: IMPO does not seem to yield processor or refresh progress report at the requested intervals
Hardware | None |
Product | None |
Operating System | All |
Component | None |
Version | None |
Severity | normal |
Resolution | Works For Me |
Category
Bugs
Login or
create an account to comment.
Comments
------ 2010-01-26T12:12:40 INFO gvSIGi18n::Importar COMMIT at the begining to change translations catalog allow write flag to False ------ 2010-01-26T12:12:41 INFO gvSIGi18n::Importar COMMIT status report before import. ------ 2010-01-26T12:12:43 INFO gvSIGi18n::Importar 1 COMMITS after 1 changes (total changes 1) Going to sleep 1.0 ------ 2010-01-26T12:12:45 INFO gvSIGi18n::Importar 1 COMMITS after 1 changes (total changes 2) Going to sleep 1.0 ------ 2010-01-26T12:14:05 INFO gvSIGi18n::Importar 10 COMMITS after 500 changes (total changes 502) Going to sleep 1.0 ------ 2010-01-26T12:15:41 INFO gvSIGi18n::Importar 10 COMMITS after 500 changes (total changes 1002) Going to sleep 1.0 ------ 2010-01-26T12:16:04 INFO gvSIGi18n::Importar 3 COMMITS after 133 changes (total changes 1135) Going to sleep 1.0 ------ 2010-01-26T12:17:40 INFO gvSIGi18n::Importar 10 COMMITS after 500 changes (total changes 1635) Going to sleep 1.0 ------ 2010-01-26T12:19:22 INFO gvSIGi18n::Importar 10 COMMITS after 500 changes (total changes 2135) Going to sleep 1.0 ------ 2010-01-26T12:19:53 INFO gvSIGi18n::Importar 3 COMMITS after 133 changes (total changes 2268) Going to sleep 1.0 ------ 2010-01-26T12:19:56 INFO gvSIGi18n::Importar COMMIT FINAL changes ------ 2010-01-26T12:19:56 INFO gvSIGi18n::Importar COMMIT FINAL status ------ 2010-01-26T12:19:56 INFO gvSIGi18n pInicializarModulosYSimbolosCadenasOrdenados::TOTAL milliseconds=156 ------ 2010-01-26T12:19:57 INFO gvSIGi18n::Importar COMMIT FINAL report ------ 2010-01-26T12:19:57 INFO gvSIGi18n::Importar COMMIT pInvalidateSimbolosCadenasOrdenados ------ 2010-01-26T12:19:57 INFO gvSIGi18n::Importar COMMIT at the end to change translations catalog allow write flag to True
Also, count of expected and performed operations differ in the final report and the log: 2010-01-26T12:46:36 INFO gvSIGi18n::Importar 25 COMMITS after 500 changes (total changes 18630) Going to sleep 2.0 ------ 2010-01-26T12:48:43 INFO gvSIGi18n::Importar 25 COMMITS after 500 changes (total changes 19130) Going to sleep 2.0 ------ 2010-01-26T12:51:04 INFO gvSIGi18n::Importar 25 COMMITS after 500 changes (total changes 19630) Going to sleep 2.0 ------ 2010-01-26T12:53:15 INFO gvSIGi18n::Importar 25 COMMITS after 500 changes (total changes 20130) Going to sleep 2.0 ------ 2010-01-26T12:55:20 INFO gvSIGi18n::Importar 25 COMMITS after 500 changes (total changes 20630) Going to sleep 2.0 ------ 2010-01-26T12:57:19 INFO gvSIGi18n::Importar 25 COMMITS after 500 changes (total changes 21130) Going to sleep 2.0 ------ 2010-01-26T12:58:01 INFO gvSIGi18n::Importar 8 COMMITS after 142 changes (total changes 21272) Going to sleep 2.0 ------ 2010-01-26T12:58:05 INFO gvSIGi18n::Importar COMMIT FINAL changes ------ 2010-01-26T12:58:06 INFO gvSIGi18n::Importar COMMIT FINAL status
Current logic to yield processor (by sleeping) or refresh progress report relies in changes effected in the translations catalog, or a period of time. Changes are any of: Creation of languages, modules, strings, or change of a translation or translation history. When languages, modules, strings being imported already exists in the translations catalog, or the imported translations are the same as the translations catalog, then no change is effected, and the logic does not yield or update report until the configured time period is expired.