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

Fix saga error should not result in unhandled exception #2421

Merged
merged 1 commit into from
Oct 29, 2019

Conversation

compulim
Copy link
Contributor

Fixes #2420

Changelog Entry

Fixed

  • Fix #2420. Fix saga error should not result in an unhandled exception, by @compulim in PR #2421

Description

Saga error is currently resulted in unhandled exception. Once that is fixed, it become disconnected, instead of keeping at saga error.

Specific Changes

  • Modified connectivityStatus.js
    • Fixed null reference exception
    • Should not change connectivity status once it become sagaerror

  • Testing Added
    • We currently do not have tests to check how many console errors

Copy link
Contributor

@tdurnford tdurnford left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

@corinagum corinagum left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@compulim compulim force-pushed the fix-2420 branch 2 times, most recently from 66e1659 to 0271367 Compare September 25, 2019 07:08
@coveralls
Copy link

coveralls commented Sep 25, 2019

Coverage Status

Coverage increased (+0.04%) to 65.336% when pulling 5e6f7d2 on compulim:fix-2420 into fab7cd8 on microsoft:master.

@corinagum
Copy link
Contributor

Ping

@corinagum
Copy link
Contributor

ping...

1 similar comment
@tdurnford
Copy link
Contributor

ping...

@compulim compulim merged commit 028e36a into microsoft:master Oct 29, 2019
@compulim compulim deleted the fix-2420 branch October 29, 2019 02:45
@compulim compulim mentioned this pull request Oct 29, 2019
55 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

When saga error occurred, it should not turn into disconnect
4 participants