2026/03/03

Tuesday, March 3, 2026 (#62)

Monday Tuesday Wednesday posts: prev < this > next

References Ferreteria/v0.6/clade/Sys/Data/Engine/aux/Schema/MyMar/@removed (← links) Ferreteria/v0.6/clade/IO/Aspect/Connx/run/Starter/Local (← links) Ferreteria/v0.6/clade/IO/Aspect/Connx/run/Starter/Remote/SSH2/@removed (← links) Ferreteria/v0.6/clade/IO/Aspect/Connx/run/Starter/Remote/SSH2/@fx/DoCommand (← links) 2026/03/02 (← links) Ferreteria/v0.6/clade/IO/Aspect/Connx/run/Starter/Local/Proc/@removed (← links) 2026/03/04 (← links)

Policy Note

I think let's say (at least for now) that checking of execution messages (errors etc.) should be invoked by the Schema or Client, not the Eng* classes in [WFe]Sys\Data\Engine\aux\ActionRq\Admin\dbase. (The process of identifying the messages semantically is done by the appropriate Matcher, which is retrieved from <engine client>->MsgMatcher(). Maybe later we'll add a separate method for invoking that, so that applications can override/specialize it if they want.

11:36

Status:

• The local export function is now correctly understanding and reporting the error messages. (This takes care of yesterday's Item 7.)
• It also seems to be silently reading the entire contents of the dump process before beginning to report on writing it to the output file.

Actions:

1. TODO Refactor remote export to work the same way local export does.

2. TODO Revisit imports and see if I can get them working now (starting with local).

15:00

Now I have to figure out how ssh2_* processes work -- specifically how their key functions map against how proc_* processes work:

• lecturer stream? -- tentatively, this is the resource returned from ssh_exec()
• listener stream?
• errors stream? -- ssh2_fetch_stream($rRecv, SSH2_STREAM_STDERR)?
• end-of-process flag?