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

Show traceback / call trace of failed transactions when running tests #62

Closed
iamdefinitelyahuman opened this issue Apr 11, 2019 · 1 comment
Labels
code structure Refactoring, reformatting, cleanup

Comments

@iamdefinitelyahuman
Copy link
Member

The design is poor and the logging settings in config.json are very confusing. This area can be improved upon greatly.

@iamdefinitelyahuman iamdefinitelyahuman added the code structure Refactoring, reformatting, cleanup label May 1, 2019
@iamdefinitelyahuman iamdefinitelyahuman added this to the 1.0.0 milestone May 8, 2019
@iamdefinitelyahuman
Copy link
Member Author

I think the best approach here is:

  • remove logging from the config file, do not allow any permanent verbosity modifications in this way
  • expand the --verbose flag - it should be possible to automatically output the traceback and/or call trace on failed transactions, especially when running tests (include a note that this will come at a time expense because of debug_traceTransaction)

@iamdefinitelyahuman iamdefinitelyahuman changed the title Rethink how logging is handled Show traceback / call trace of failed transactions when running tests Jun 30, 2019
@iamdefinitelyahuman iamdefinitelyahuman modified the milestones: 1.0.0, Testing Improvements Jun 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code structure Refactoring, reformatting, cleanup
Projects
None yet
Development

No branches or pull requests

1 participant