Skip to content
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

Adding of Node.JS Domains to Error Handling Broke Simpleworkflow #88

Closed
wants to merge 5 commits into from
Closed

Adding of Node.JS Domains to Error Handling Broke Simpleworkflow #88

wants to merge 5 commits into from

Conversation

cjhanks
Copy link
Contributor

@cjhanks cjhanks commented Mar 28, 2013

It was in #74 that domains were added to exception handling. The existence of a domain is tested by checking the running context (this.domain) in the sequential_executor, however calls are regularly made into the AWS.SequentialExecutor object in which the context is not of the proper object (a problem all to itself), coincidentally the SimpleWorkflow often has a domain object attached to the request. When exceptions are thrown it is not uncommon for it to find this string. Therefore all if statements if (this.domain) have had type-checking added. Since the require('domain') was included in this file on a context-only basis, the same notation was used throughout.

@lsegal
Copy link
Contributor

lsegal commented Mar 28, 2013

Great catch! I'm wondering if maybe we should just solve this by picking a more appropriate name for our internal domain flag. _domain would solve this, wouldn't it?

Otherwise, SWF might not raise an exception, but it will still not function with domain support. Seems like we'd just be obscuring that problem with this patch.

@lsegal lsegal closed this in 136c0ba Mar 29, 2013
lsegal added a commit that referenced this pull request Mar 29, 2013
@lsegal
Copy link
Contributor

lsegal commented Mar 29, 2013

Thanks! I just did a minor refactor since we don't need to require('domain') a whole bunch of times, same thing though.

@lock
Copy link

lock bot commented Sep 28, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.

@lock lock bot locked as resolved and limited conversation to collaborators Sep 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants