Sam Sussman
Sam Sussman
From #209 An issue to discuss the relationship between a child workflow and it's parent and how the logs should be stored/consumed. * Should the cli always return child logs...
```sh [Error: EEXIST: file already exists, mkdir 'my-eventual-app'] { errno: -17, code: 'EEXIST', syscall: 'mkdir', path: 'my-eventual-app' } npm ERR! code 1 npm ERR! path /home/sussmans npm ERR! command failed...
@amildahl pointed out that `tail` traditionally returns the end of a file, while `-f` or `--follow` is what continues to read the end of the file. (or `shift-F` in `less`)....
Would be really cool to use the cli to watch the system for various things: 1. generally watch anything going through the system, with a filter, events, workflow progress, api...
We need to implement retry :-) On definition: ```ts const credit = activity({ retry: { onErrors: [...], backoffFactor: 1.5, initialDelay: 1 } }, async () => {}); ``` On invoke...
Current it is possible to provide a handler for an event, but not for an API. ```ts // provide an implementation of an api handler. env.handlePath(path, method, () => {})...
```ts const workflowMock = env.mockWorkflow(myWorkflow); // and the once counterparts workflowMock.complete(); workflowMock.fail(); workflowMock.timeout(); workflowMock.invoke(() => {}); workflowMock.defer(); ```
Support sending an event or a signal from the workflow with an activity token without starting a workflow. > note: not sure how to make this ergonomic In an example...
`new Rule().addTarget(new EventualServiceTarget(service));` Allow forwarding events from another event bus to the Service.