Reference in New Issue
Block a user
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?
Before deploying OtOpcUa master (≥
0e96dd08) to DEV vd03 or QA vq03/vq04, run three checks against each environment's OtOpcUa ConfigDb. Each covers a change that can turn a currently accepted configuration into a deploy-time error or a behaviour change.VirtualTagNoEffectiveTrigger(blocking): list enabled virtual tags with neither a timer (TimerIntervalMsunset or 0) nor any driver/VT dependency. These now refuse to deploy.VirtualTagDependencyCycle(blocking for cycles): list virtual tags whose script reads another VT (ctx.GetTag("<EquipmentId>/<Name>"), or a bare VT name, which never resolved). These will start producing values where they produced none before. Any loop (A→B→A, self-read, or through a Calculation tag) now refuses to deploy.AppContext,Console.,GCSettings,ProfileOptimization,EncodingProvider,CodePagesEncodingProvider,TypeDescriptor,CryptoConfig,CultureInfo.CurrentCulture/CurrentUICulture/DefaultThreadCurrent*, andTimeZoneInfo.ClearCachedData. Fix any that match first (useCultureInfo.InvariantCulture, for example).Also before upgrading:
Scripting:RunnerstaysInProcessunless set. Don't enableShadow/OutOfProcessthere yet; the installer work for the worker account, pipe ACL and firewall rule is still open.Blocked: the available SQL login (
HISTORIAN_SQL_USER) cannot open theOtOpcUadatabase on wonder-app-vd03 or wonder-sql-vq03, the same block as ScadaBridge#70. This needs a read-only login on the OtOpcUa ConfigDb, or the owner runs the checks.