Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

memex-local verify reports loaded view packs as NOT installed: the on-disk probe does not search /app/modules

Closed Beginner friendly
  • Is something wrong?
#6,025 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
csharp
Domain
cli, devtools

Research direction

Start in deploy/homebrew/bin/memex-local at probe_view_packs (around line 932), and trace how it sets the module root and checks on-disk locations. The issue proposes adding /app/modules/*/<name>.dll to the search or relying on the loaded-module check except for pending restarts. Verify with the described /data root and modules under /app/modules; done when loaded packs are not falsely reported missing.

Written by the indexing model from the issue text.

Description

area:hosting bug sev:L

Repository and prior art

  • The defect is in deploy/homebrew/bin/memex-local (function probe_view_packs, line 932 on main at 0cf73dd82). This file is in MeshWeaver core.
  • I searched issues in Systemorph/MeshWeaver for "memex-local verify view pack" and "probe_view_packs". I found no existing issue.

Observed behaviour

On a fresh install (Homebrew memex-local 0.2.16194, portal 3.0.0-ci.9869, self-registry mode), memex-local verify prints:

warn view pack(s) NOT installed: MeshWeaver.Blazor.Graph MeshWeaver.Blazor.EntityViews
     Every control renders as its ToString() …

The portal had loaded both modules. Its log contains:

[ModuleLoad] MeshWeaver.Blazor.EntityViews ← /app/modules/MeshWeaver.Blazor.EntityViews/MeshWeaver.Blazor.EntityViews.dll (source=appsettings, …)
[ModuleLoad] MeshWeaver.Blazor.Graph ← /app/modules/MeshWeaver.Blazor.Graph/MeshWeaver.Blazor.Graph.dll (source=appsettings, …)

The Settings pages rendered real input fields, so EntityViews was active.

Cause

probe_view_packs searches two places:

root="${Modules__Root:-/app}"
ls "$root"/modules/*/"$m".dll … || [ -f "/app/$m.dll" ]

In the pod, Modules__Root=/data, and /data/modules does not exist. The image keeps both modules under /app/modules/<name>/<name>.dll. Neither searched path covers that location, so the probe reports both as missing.

Effect

The warning tells the user that the portal cannot render forms and that it cannot repair itself, and it suggests update --build or a switch to registry mode. Neither is needed. A user who follows the advice loses time, or loses the mounted checkouts by switching to registry mode.

Proposed fix

  1. Also search /app/modules/*/<name>.dll in probe_view_packs.
  2. Or let the [ModuleLoad] check (assert_view_packs_loaded), which reads what the process actually loaded, decide alone, and use the on-disk probe only for the pending-restart case.

Severity

sev:L — a false warning in a developer-only tool; the portal works, and no data or function is affected.

🤖 Generated with Claude Code

Dominant language
C#
Stars
12
Forks
5
Avg merge
4h 1m
Merged PRs (30d)
979

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Systemorph/MeshWeaver

All issues in Systemorph/MeshWeaver

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.