-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HTTP WFID test/fixes #676
HTTP WFID test/fixes #676
Conversation
@@ -224,12 +225,27 @@ export class DBOS { | |||
return DBOSExecutor.globalInstance as DBOSExecutorContext; | |||
} | |||
|
|||
static async launchAppHTTPServer() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do users need to manually invoke this in their app, or is it just for testing?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the current solution for testing purposes.
The HTTP server had been held by testingRuntime, which is not in use.
launch() had been making it under certain conditions; @maxdml changed those. We may clean up a bit after the dust settles there.
I don't see any changes regarding |
Search for |
Way to launch HTTP in unit tests
More unit tests (outside of template)
Fix for WFID in HTTP header
Clarify
withNextWorkflowID
use of ID.