dohertj2/lmxopcua
1
0
Fork 0
Code Issues 5 Pull Requests Actions Packages Projects Releases Wiki Activity

Historian docs: wrong SQL Server password in HISTORIAN_SQL_TEST_CONNECTION example; no QuestDB fixture on the shared host #822

New Issue
Closed
opened 2026-11-11 00:05:58 -05:00 by dohertj2 · 1 comment
dohertj2 commented 2026-11-11 00:05:58 -05:00
Owner
Copy Link
Copy Source

Found during #810. The example connection string in docs/Historian.md uses a password that doesn't work on the shared host 10.100.0.35,14330 (the repo's dev appsettings value does). There is also no /opt/otopcua-questdb stack on 10.100.0.35 — #810 ran a throwaway questdb/questdb:10.0.1 container. Fix the doc and either add a labelled QuestDB fixture stack (documented in infra/README.md) or document that there isn't one.

Found during #810. The example connection string in `docs/Historian.md` uses a password that doesn't work on the shared host 10.100.0.35,14330 (the repo's dev appsettings value does). There is also no `/opt/otopcua-questdb` stack on 10.100.0.35 — #810 ran a throwaway `questdb/questdb:10.0.1` container. Fix the doc and either add a labelled QuestDB fixture stack (documented in infra/README.md) or document that there isn't one.
dohertj2 added the type:docspriority:p3 labels 2026-11-11 00:05:58 -05:00
dohertj2 commented 2026-11-11 05:24:31 -05:00
Author
Owner
Copy Link
Copy Source

Fixed (8d64db67). Pushed to master in d1b6cad2. Historian docs use the right SQL password; labelled QuestDB fixture at /opt/otopcua-questdb on 10.100.0.35 (PG 8812). CI decision in #841.

Fixed (`8d64db67`). Pushed to master in `d1b6cad2`. Historian docs use the right SQL password; labelled QuestDB fixture at `/opt/otopcua-questdb` on 10.100.0.35 (PG 8812). CI decision in #841.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
auto-managed
queue management
 blocked
Blocked by dependency or external hold
 cross-driver
queue management
 cross-repo
Needs coordinated change in another family repo (wire contract etc.)
 driver/abcip
queue management
 driver/ablegacy
queue management
 driver/focas
queue management
 driver/mqtt
MQTT / Sparkplug B broker-subscribe driver
 driver/opcuaclient
queue management
 driver/s7
queue management
 driver/twincat
queue management
 migrated
Migrated from a markdown backlog (2026-11 standardization)
 phase/1
queue management
 phase/2
queue management
 phase/3
queue management
 phase/4
queue management
 phase/5
queue management
 phase/6
queue management
 priority:p0
Must-have / blocking
 priority:p1
High priority
 priority:p2
Normal priority
 priority:p3
Low priority / nice to have
 queue/blocked
queue management
 queue/done
queue management
 queue/failed
queue management
 queue/in-progress
queue management
 queue/queued
queue management
 type:bug
Defect in shipped behaviour
 type:debt
Technical debt / hygiene
 type:deploy-gate
Rollout/deploy/migration step not yet done on an environment
 type:docs
Documentation work
 type:feature
Feature implementation
 type:followup
Follow-up deferred from a plan, PR or gate
 type:infra
Infrastructure and scaffolding
 type:review-finding
Unfixed finding from an architecture/code review
 type:test
Test work
No Label priority:p3 type:docs
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
dohertj2 (dohertj2)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dohertj2/lmxopcua#822
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?