dc/datacontroller.io
6
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feed: add a support diagnostics post (browser_info, browser_url_vars) #24

Merged
allan merged 2 commits from feed/support-diagnostics into main 2026-09-27 20:51:01 +00:00
Conversation 0 Commits 2 Files Changed 2
+158
hermes commented 2026-09-27 20:31:50 +00:00
Collaborator
Copy Link
Copy Source

Feed post: Support Diagnostics (browser_info and browser_url_vars)

New feed post for the browser_info / browser_url_vars feature (dc/dc PR #326), at /support-diagnostics/.

content/feed/support-diagnostics/index.md plus the cover support-diagnostics.jpeg.

No screenshots: the two tables have no UI surface - they are SAS-side input tables plus a job-log dump - so the post uses markdown tables for the column definitions and SAS code examples for the hook reads. That was the agreed approach.

What the post covers

  • the two tables and their columns
  • which services receive them, and why the high-frequency viewer calls do not
  • reading them from a hook, with the %sysfunc(exist()) guard
  • the MPEINIT dump in the job log, including the _debug values per path
  • the editors/loadfile caveat (the adapter's multipart upload carries no input tables)

Every claim is taken from the dc/dc PR #326 source: client/src/app/services/sas.service.ts (the DIAGNOSTICS_SERVICES list, the payload shape, collectBrowserUrlVars), sas/sasjs/macros/mpeinit.sas (the log dump and the _debug=128 addition) and sas/sasjs/macros/mpe_loader.sas.

The docs counterpart is dc/docs.datacontroller.io PR #9, which documents the same feature on the troubleshooting page.

Cover

The cover is a PIL placeholder - there is no image-generation model on this box. The generation prompt is in the trailing Image prompt: comment of the post. Overwrite content/feed/support-diagnostics/support-diagnostics.jpeg with the generated file, or say the word and I will drop the placeholder from the PR instead.

Verification

  • rm -rf .cache public && npm run build - clean, page generated at /support-diagnostics/
  • npm run typecheck - clean
  • npm run lint - the same 8 pre-existing prettier warnings (src/pages/*, src/templates/blog-*); no file of mine is touched
  • rendered checks: 3 tables, both language-sas code blocks, og:image -> https://datacontroller.io/static/<hash>/support-diagnostics.jpg, post in /feed/ and in rss.xml, category page under /feed/category/announcements/
  • visible body is ASCII-only (the only non-ASCII in the built page is pre-existing site chrome: the SAS registered sign, and an em dash in the compiled .blockquote-footer:before rule and the RSS link title)
## Feed post: Support Diagnostics (browser_info and browser_url_vars) New feed post for the `browser_info` / `browser_url_vars` feature (dc/dc PR #326), at `/support-diagnostics/`. `content/feed/support-diagnostics/index.md` plus the cover `support-diagnostics.jpeg`. No screenshots: the two tables have no UI surface - they are SAS-side input tables plus a job-log dump - so the post uses markdown tables for the column definitions and SAS code examples for the hook reads. That was the agreed approach. ### What the post covers - the two tables and their columns - which services receive them, and why the high-frequency viewer calls do not - reading them from a hook, with the `%sysfunc(exist())` guard - the `MPEINIT` dump in the job log, including the `_debug` values per path - the `editors/loadfile` caveat (the adapter's multipart upload carries no input tables) Every claim is taken from the dc/dc PR #326 source: `client/src/app/services/sas.service.ts` (the `DIAGNOSTICS_SERVICES` list, the payload shape, `collectBrowserUrlVars`), `sas/sasjs/macros/mpeinit.sas` (the log dump and the `_debug=128` addition) and `sas/sasjs/macros/mpe_loader.sas`. The docs counterpart is dc/docs.datacontroller.io PR #9, which documents the same feature on the troubleshooting page. ### Cover The cover is a **PIL placeholder** - there is no image-generation model on this box. The generation prompt is in the trailing `Image prompt:` comment of the post. Overwrite `content/feed/support-diagnostics/support-diagnostics.jpeg` with the generated file, or say the word and I will drop the placeholder from the PR instead. ### Verification - `rm -rf .cache public && npm run build` - clean, page generated at `/support-diagnostics/` - `npm run typecheck` - clean - `npm run lint` - the same 8 pre-existing prettier warnings (`src/pages/*`, `src/templates/blog-*`); no file of mine is touched - rendered checks: 3 tables, both `language-sas` code blocks, `og:image` -> `https://datacontroller.io/static/<hash>/support-diagnostics.jpg`, post in `/feed/` and in `rss.xml`, category page under `/feed/category/announcements/` - visible body is ASCII-only (the only non-ASCII in the built page is pre-existing site chrome: the SAS registered sign, and an em dash in the compiled `.blockquote-footer:before` rule and the RSS link title)
hermes added 1 commit 2026-09-27 20:31:50 +00:00
feed: add a support diagnostics post (browser_info, browser_url_vars) 6469ad00a3
hermes added 1 commit 2026-09-27 20:47:53 +00:00
feed: a worked URL-parameter example for the hook read, and the generated cover b61ec07c87
allan merged commit b75e0bb38e into main 2026-09-27 20:51:01 +00:00
allan deleted branch feed/support-diagnostics 2026-09-27 20:51:01 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
allan (Allan) dcbot hermes (hermes) mihajlo sead trevor Yury
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dc/datacontroller.io#24