You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When resuming a multiprocess run, mp_tasks.apportion will wrongly apportion tables in pipeline created in a later phase of single-process execution. This only happens if in the prior run, execution proceeded through a multiprocess step and coalesced the results back into the pipeline - and then the resume_after step specified repeats the apportion step. I will be comitting a fix for this forthwith.
The text was updated successfully, but these errors were encountered:
…cludes everything not elseqhere specified
multiprocess_steps.slice.coalesce list of tables (presumably created by subprocess) to coalesce
fix resume_after issue #374 where apportion wrongly apportions tables to subprocess pipeline that
were created during later steps in the original run.
* abm agnostic multiprocessing support for popsim
* multiprocess_steps.slice.exclude: wildcard 'True' in place of list excludes everything not elsewhere specified
multiprocess_steps.slice.coalesce list of tables (presumably created by subprocess) to coalesce
fix resume_after issue #374 where apportion wrongly apportions tables to subprocess pipeline that
were created during later steps in the original run.
* warn if PERSON_TYPE_MAP setting not found in cdap.yaml
* cached accessibility support
* fix abm injectable registration issue in cli.run
* add expressions back to eval_utilities tracing
When resuming a multiprocess run, mp_tasks.apportion will wrongly apportion tables in pipeline created in a later phase of single-process execution. This only happens if in the prior run, execution proceeded through a multiprocess step and coalesced the results back into the pipeline - and then the resume_after step specified repeats the apportion step. I will be comitting a fix for this forthwith.
The text was updated successfully, but these errors were encountered: