Skip to content

Conversation

@andyrichardson
Copy link

About

Fix #58

@coveralls
Copy link

coveralls commented Dec 7, 2020

Pull Request Test Coverage Report for Build 351

  • 1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 100.0%

Totals Coverage Status
Change from base Build 350: 0.0%
Covered Lines: 22
Relevant Lines: 22

💛 - Coveralls

1 similar comment
@coveralls
Copy link

Pull Request Test Coverage Report for Build 351

  • 1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 100.0%

Totals Coverage Status
Change from base Build 350: 0.0%
Covered Lines: 22
Relevant Lines: 22

💛 - Coveralls

@mdlavin
Copy link
Contributor

mdlavin commented Dec 7, 2020

Would it be possible to detect errors with circular references and only serialize those? I'm not sure about the impact of loosing the original error in the common case of non-circular errors.

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.

Circular structure on error

3 participants