-
Notifications
You must be signed in to change notification settings - Fork 14
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
Add event rule to batch starter lambda #236
Add event rule to batch starter lambda #236
Conversation
logger.setLevel(logging.INFO) | ||
logging.basicConfig(stream=sys.stdout, level=logging.DEBUG) |
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.
Why are these set separately? I think we can get rid of the basicConfig and sys import and put this logger to debug.
logger.setLevel(logging.INFO) | |
logging.basicConfig(stream=sys.stdout, level=logging.DEBUG) | |
logger.setLevel(logging.DEBUG) |
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.
That's how we had in indexer and it's been able to log. I recall batch job logging troublesome. I am testing it on AWS.
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.
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.
Nice work.
…ixed tests with new changes. fixed logging.
10b9493
to
7a641da
Compare
6432f1b
into
IMAP-Science-Operations-Center:dev
Change Summary