bitloops / bitloops Goto Github PK

Currently Task nodes that use HTTP interfaces do not forward responses with codes >= 300. (e.g. 401 from Keycloak on AuthWorkflows). As a result the workflow does not continue and client code throws after the timeout passes. We should discuss how to handle these responses, and imo forwarding the response status along with the response body could be helpful.

Describe the bug
When a service is changed the stitched workflow cache doesn't reset

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior

Both the Services cache and the affected workflow caches should be cleared.

Screenshots
If applicable, add screenshots to help explain your problem.

Bitloops Installation:

• Platform e.g. K8s, Docker, Bitloops Managed
• Version [e.g. 1.0.0]

Additional context
Add any other context about the problem here.

when launch yarn start, error bellowing:

bitloops/bitloops-engine/dist/util/stringManipulator.js:5
return str.replace(new RegExp(find, 'g'), replace);
^

TypeError: Cannot read property 'replace' of undefined

Event trigger messages(sent by Console messages tab) do not pass an auth context and they get declined in engine events topic. We could pass by default the auth Context of the parent Workflow, otherwise we need to provide additional input for that in the Bitloops Console.

server engineTopic undefined.undefined
(node:77196) UnhandledPromiseRejectionWarning: NatsError: BAD_SUBJECT
at Function.errorForCode (/Users/theseusyang/Dev/bitloops/bitloops-engine/node_modules/nats/lib/nats-base-client/error.js:98:16)
at NatsConnectionImpl._check (/Users/theseusyang/Dev/bitloops/bitloops-engine/node_modules/nats/lib/nats-base-client/nats.js:104:37)
at NatsConnectionImpl.subscribe (/Users/theseusyang/Dev/bitloops/bitloops-engine/node_modules/nats/lib/nats-base-client/nats.js:116:14)
at NATS. (/Users/theseusyang/Dev/bitloops/bitloops-engine/dist/services/NATS.js:122:33)
at Generator.next ()
at /Users/theseusyang/Dev/bitloops/bitloops-engine/dist/services/NATS.js:8:71
at new Promise ()
at __awaiter (/Users/theseusyang/Dev/bitloops/bitloops-engine/dist/services/NATS.js:4:12)
at NATS.subscribe (/Users/theseusyang/Dev/bitloops/bitloops-engine/dist/services/NATS.js:104:16)
at /Users/theseusyang/Dev/bitloops/bitloops-engine/dist/server.js:93:8
(Use node --trace-warnings ... to show where the warning was created)
(node:77196) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:77196) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

It seems there is an issue when trying to run bitloops on windows. It seems power shell and command prompt cannot run bash scripts which are needed. Thus maybe this should be added in the documentation for windows users: something like:

For Windows: you need to have a terminal which can run sh commands e.g. git bash. And use this to execute the bitloops command


s