|
| 1 | +v0.5.0 |
| 2 | +====== |
| 3 | + |
| 4 | +New Features |
| 5 | +------------ |
| 6 | + |
| 7 | +* HTMap CLI commands that operate on tags can now pattern-match for tags using |
| 8 | + glob syntax. Try adding ``-p "<pattern>"`` to commands like ``htmap remove`` |
| 9 | + or ``htmap release``! |
| 10 | + Issue: https://github.com/htcondor/htmap/issues/159 |
| 11 | +* Component status tracking is now preserved between sessions, so it won't be |
| 12 | + performed from scratch every time. This will only work if the HTCondor Python |
| 13 | + bindings version is 8.9.3 or greater. You can upgrade your bindings version |
| 14 | + roughly-independently of HTMap by running ``pip install --upgrade htcondor``. |
| 15 | + Issue: https://github.com/htcondor/htmap/issues/166 |
| 16 | +* :class:`htmap.Map`, :class:`htmap.MapStdOut`, :class:`htmap.MapStdErr`, |
| 17 | + and :class:`htmap.MapOutputFiles` now all support in the ``in`` operator to check |
| 18 | + if a component index is in the map. |
| 19 | + |
| 20 | + |
| 21 | +Deprecated Features |
| 22 | +------------------- |
| 23 | + |
| 24 | +* The various iteration methods on :class:`htmap.Map` no longer have a |
| 25 | + ``callback`` argument. |
| 26 | + |
| 27 | + |
| 28 | +Bug Fixes |
| 29 | +--------- |
| 30 | + |
| 31 | +* It should now be much harder to accidentally get a dangling, inaccessible map |
| 32 | + due to an interrupted ``remove``. |
| 33 | + Issue: https://github.com/htcondor/htmap/issues/127 |
| 34 | +* When an execution errors occurs, the exception and traceback will be printed |
| 35 | + to stderr execute-side (in addition to being brought back submit-side). This |
| 36 | + should make some debugging patterns work as expected. |
| 37 | + Issue: https://github.com/htcondor/htmap/issues/178 |
| 38 | +* The CLI command ``htmap status --live`` now has much better behavior when |
| 39 | + the table width is nearly the width of the terminal. It should now never wrap |
| 40 | + unless the table is actually wider than the terminal, instead of a few |
| 41 | + characters before the actual width. |
| 42 | +* HTMap now handles late materialized jobs much more smoothly: maps with |
| 43 | + unmaterialized components can be removed, and various CLI commands that output |
| 44 | + color won't fail when acting on maps with unmaterialized components. However, |
| 45 | + unmaterialized components do not show as `IDLE`, which mirrors the behavior |
| 46 | + of `condor_q`. This does make it hard to know how many components are in a |
| 47 | + late-materialized map at a glance; we are thinking about how to address this. |
| 48 | + Issue: https://github.com/htcondor/htmap/issues/158 |
| 49 | + |
| 50 | + |
| 51 | +Known Issues |
| 52 | +------------ |
| 53 | + |
| 54 | +* Execution errors that result in the job being terminated but no output being |
| 55 | + produced are still not handled entirely gracefully. Right now, the component |
| 56 | + state will just show as ``ERRORED``, but there won't be an actual error report. |
| 57 | +* Map component state may become corrupted when a map is manually vacated. |
| 58 | + Force-removal may be needed to clean up maps if HTCondor and HTMap disagree |
| 59 | + about the state of their components. |
| 60 | + Issue: https://github.com/htcondor/htmap/issues/129 |
0 commit comments