changelog(unreleased): pi-task fallback covers the task children the AWS SSO keeper leaves alone
The keeper (pi-extensions aws-sso.ts, entry by pi@mbp-m1-2020 in eb70928) acts
only in interactive sessions: ctx.hasUI in the code, and the troubleshooting row
in docs/aws-sso.md. A pi-task child that hits an ended SSO session is the case
the new fallback handles, so the two entries now point at each other. The keeper
entry itself is unchanged.
This commit is contained in:
+4
-1
@@ -87,7 +87,10 @@ Pre-v1.0.0 tags followed the pi npm version (`v{pi_version}[letter]`).
|
|||||||
such a failure only inside its JSON stream: `stopReason=error`, rc 0. Before
|
such a failure only inside its JSON stream: `stopReason=error`, rc 0. Before
|
||||||
this, an expired Bedrock session failed every task as "no fenced json
|
this, an expired Bedrock session failed every task as "no fenced json
|
||||||
envelope". The `fork` tool does not read this key. Documented in pi-toolkit's
|
envelope". The `fork` tool does not read this key. Documented in pi-toolkit's
|
||||||
README.
|
README. It complements `/aws-sso` (below), which by design acts only in
|
||||||
|
interactive sessions (`ctx.hasUI`; pi-extensions `docs/aws-sso.md`,
|
||||||
|
troubleshooting). A `task` child that meets an ended SSO session gets no help
|
||||||
|
from the keeper.
|
||||||
|
|
||||||
- **Long Bedrock runs no longer die at "Token is expired" when the AWS SSO
|
- **Long Bedrock runs no longer die at "Token is expired" when the AWS SSO
|
||||||
session ends: `/aws-sso` (pi-extensions `aws-sso.ts`) runs `aws sso login` for
|
session ends: `/aws-sso` (pi-extensions `aws-sso.ts`) runs `aws sso login` for
|
||||||
|
|||||||
Reference in New Issue
Block a user