StackJack 0.1.0.14487+ededdff
StackJack 0.1.0.14487+ededdff
This release fixes several Hudu list tools that were failing outright, lets the Purview row on the Microsoft setup checklist show Ready, and corrects how AI Governance finding totals are counted.
Bug fixes
- Hudu network, VLAN and VLAN zone lists now work. Listing networks, VLANs and VLAN zones from Hudu failed on every call because Hudu rejects paging on these lists. The tools now return the full list in one response and no longer accept page or page size options. The network type filter now takes a number, which matches what Hudu expects. The example for creating a network shows the network type as a number too.
- Hudu network documentation gap analysis now works. It depends on the network and VLAN lists, so it failed along with them. It now reads networks and VLANs in a single request each.
- AI Governance can read networks from Hudu again. AI Governance uses your Hudu networks as a directory source. That lookup used the same failing request and now succeeds.
- Listing items in a Hudu rack storage now works. This list also rejected paging and failed on every call. It now returns all items in one response and no longer accepts page or page size options. The procedure task and rack storage lists still support paging as before.
- AI Governance finding totals no longer double-count. A finding raised on a later day than it was first recorded could be counted on both days. Finding totals were inflated until the earlier day aged out of the reporting window. Each finding is now counted only on the day it was raised.
- AI Governance findings from deeper review are no longer occasionally dropped. When two updates overlapped at the same moment, a finding produced by the deeper review stage could be discarded. These overlaps are now retried, so the finding is kept.
UI & UX changes
- The Purview row on the Microsoft setup checklist can now show Ready. Previously the row could never turn green. It required a per-customer content search consent that the setup wizard has no way to check. The row now shows Ready once the rest of its setup is complete. The consent appears as a note explaining that only the content search tools need it, and it is no longer listed as a to-do. The Purview and Microsoft setup documentation has been updated to match.