Skip to content

ChatWalaʻau v0.116.2

Choose a tag to compare

View all tags
@motojinc25 motojinc25 released this 29 Jul 00:10
v0.116.2
d255ddf

This release fixes declarative workflows being rejected on Linux deployments: the container image pointed DOTNET_ROOT at a directory that does not exist, so Power Fx could not load and every workflow using a = expression was blocked.

✅ No breaking changes. Rebuild or re-pull the container image to pick up the fix; no configuration change is required.

Highlights

Fixed: = expressions rejected on Linux even with .NET installed (v0.116.2)

  • Symptom: opening or running a workflow reported "this workflow uses N Power Fx expression(s) ... but the Power Fx engine is unavailable on this deployment", on an image that does install the .NET runtime. The same workflow worked on Windows.
  • Cause: the image installed the runtime from packages.microsoft.com, which lands in /usr/share/dotnet, but exported DOTNET_ROOT=/usr/lib/dotnet -- the path Debian's own .NET packages use. Pointing at a non-existent directory made clr_loader fail with Failed to create a .NET runtime (coreclr), so the powerfx package was unimportable.
  • Fix: DOTNET_ROOT now matches the real install location. Verified by building the image both ways: the corrected build loads Power Fx successfully, the old value reproduces the reported error exactly.
  • If you set DOTNET_ROOT yourself, point it at the directory that actually contains shared/Microsoft.NETCore.App.

The image verifies Power Fx at build time (v0.116.2)

  • The build now constructs a real Power Fx engine and parses an expression. If the .NET wiring is wrong the build fails instead of publishing an image where declarative workflows silently cannot run.
  • Power Fx availability depends on the environment (runtime location, host resolver, ICU), which no unit test can cover -- so the check runs where the environment is actually assembled.

"Power Fx unavailable" now explains itself (v0.116.2)

  • The blocking warning quotes the underlying engine-load error and names DOTNET_ROOT, instead of only stating that the engine is missing.
  • The backend logs the full failure at WARNING the first time Power Fx is needed, so the cause is visible in the deployment logs.

Included in this release

This release includes implementation work from:

  • v0.116.2 through v0.116.2

Notes

  • Internal design management content and architecture control artifacts are intentionally omitted from this release note.

Installation

See the repository README for setup and usage instructions.

Version

  • Release version: 0.116.2
  • Previous release: 0.116.1
Assets 2
Loading