Skip to content
This repository has been archived by the owner on Jul 29, 2020. It is now read-only.

Sample push exception capturing #254

Conversation

charles-cowart
Copy link
Contributor

Added logging to PushQiitaHandler. This should resolve the immediate need, but it could be done across the board with a little bit of time. Logging is being reported on screen and in the log file. Curiously, I did not encounter an exception while testing the code, and all pushes were successful. I will issue a second PR to catch a broader range of exceptions.

Charles Cowart added 4 commits March 18, 2019 14:55
Propose we remove this TODO, as it's already been discussed in mail
Logging for all methods within PushQiitaHandler has been added.
@charles-cowart
Copy link
Contributor Author

It looks like in the Travis build, the pushed Ids are not being set to 'Y' afterward. A little strange because it's passing in my local build. Looking into it.

Charles Cowart added 3 commits March 18, 2019 18:18
Local testing confirms marking SQL statement is not raising an Error.
Speculating whether there needs to be time between the POST, and the
immediate call afterward to the database directly.
Locally, I can see the value for the sample ID are changing from N to Y,
however, this unittest continues to fail. Increasing the wait time, or
perhaps ensuring a commit occurs will change the result.
As requested by Daniel. Confirm or deny an exception is going unseen
@wasade
Copy link
Member

wasade commented Apr 9, 2019

Superseded by #255

@wasade wasade closed this Apr 9, 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.

2 participants