v0.0.417

Version 0.0.417 (June 21, 2026)

• Infor OLAP (Infor d/EPM) data source (#425) — a new enterprise connector for the Infor d/EPM OLAP semantic layer (formerly Infor BI / MIS Alea OLAP), the supported path into on-premise Infor OLAP 25.x where native connections are gone and XMLA is mandatory. It speaks the standard XMLA SOAP contract over HTTP with Basic auth: schema discovery via Discover (catalogs, cubes, dimension hierarchies, and measures — each cube surfaced as a Catalog/Cube table whose columns carry their MDX unique_name), and query execution via Execute (Tabular) that runs MDX and flattens the rowset into a DataFrame (decoding XMLA _xHHHH_ escapes). SOAP faults and inline XMLA errors surface as clear errors. Configurable endpoint URL, optional catalog scope, SSL verification, and timeout.
• Agents — connections footer fixes — the bottom-left Connections footer is no longer pushed off-screen (requiring a scroll) when a top banner is shown: the Knowledge Explorer now sizes itself to the viewport minus the banner height. It also shows an explicit "Add connection" CTA in the empty state, and childless connections — created but not yet linked to any agent — now appear in the list instead of being hidden until an agent exists.
• Fix — Tables selector "Save" button hidden until scroll — the Save bar in the tables selector is now pinned (sticky) to the bottom of its scroll container, so it stays visible without scrolling to the end of long table lists (agent Tables panel, schema wizard, onboarding, etc.).
• Fix — report tool card flicker — the edit_instruction tool card no longer rapidly flickers between its rendered document and its v1 → v2 version-diff view during/after an edit stream. The card is keyed on the stable block id so streaming/poll updates no longer remount it.
• Fix — Microsoft Fabric "Login timeout expired" on cold-start endpoints — Fabric Warehouse/Lakehouse SQL endpoints are serverless and can be slow to respond on the first connection after the capacity has been idle, routinely exceeding the ODBC driver's short default login timeout (~15s) and surfacing as HYT00 … Login timeout expired (SQLDriverConnect). The Fabric client now sets a generous 60s login timeout (Connect Timeout + pyodbc timeout), adds driver-level ConnectRetryCount, and retries transient connection-timeout SQLSTATEs (HYT00/HYT01/08001/08S01) a few times with backoff so a cold endpoint gets a chance to wake up. This affects both service-principal and per-user (OBO/Entra) auth.