docs(comments): correct 7 stale 'later task/milestone' comments (stillpending §9)
This commit is contained in:
@@ -863,12 +863,12 @@ public sealed class GalaxyDriver
|
||||
if (_dataWriter is null)
|
||||
{
|
||||
// Mirror the IReadable fallback: production write path runs on top of
|
||||
// GalaxyMxSession (PR 4.2 skeleton; PR 4.4 wires the live session). Until
|
||||
// that lands, deployments selecting Galaxy:Backend=mxgateway can't write.
|
||||
// GatewayGalaxyDataWriter, which is wired by InitializeAsync when the gRPC session
|
||||
// connects. This guard fires only if the driver is called before initialization completes.
|
||||
throw new NotSupportedException(
|
||||
"GalaxyDriver.WriteAsync requires GatewayGalaxyDataWriter wired against a connected " +
|
||||
"GalaxyMxSession (PR 4.4). Until that lands, route writes through the legacy-host " +
|
||||
"backend (Galaxy:Backend=legacy-host).");
|
||||
"GalaxyMxSession. Call InitializeAsync and wait for a successful connection before " +
|
||||
"issuing writes.");
|
||||
}
|
||||
|
||||
return _dataWriter.WriteAsync(writes, ResolveSecurity, cancellationToken);
|
||||
@@ -887,7 +887,7 @@ public sealed class GalaxyDriver
|
||||
{
|
||||
throw new NotSupportedException(
|
||||
"GalaxyDriver.SubscribeAsync requires a connected GalaxyMxSession + GatewayGalaxySubscriber. " +
|
||||
"PR 4.W wires the production session; until then route subscriptions through the legacy-host backend.");
|
||||
"Call InitializeAsync and wait for a successful connection before subscribing.");
|
||||
}
|
||||
|
||||
var pump = EnsureEventPumpStarted();
|
||||
@@ -1103,7 +1103,7 @@ public sealed class GalaxyDriver
|
||||
{
|
||||
throw new NotSupportedException(
|
||||
"GalaxyDriver.AcknowledgeAsync requires GatewayGalaxyAlarmAcknowledger wired against a connected " +
|
||||
"GalaxyMxSession (PR B.2). InitializeAsync must run before alarm acknowledgements can flow.");
|
||||
"GalaxyMxSession. InitializeAsync must complete successfully before alarm acknowledgements can flow.");
|
||||
}
|
||||
|
||||
// Acks are issued one-by-one — the gateway RPC accepts a single alarm
|
||||
|
||||
Reference in New Issue
Block a user