Conversation
|
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
merging with latest staging
Codecov Report
@@ Coverage Diff @@
## staging #1599 +/- ##
===========================================
+ Coverage 58.22% 59.13% +0.91%
===========================================
Files 84 88 +4
Lines 8462 8942 +480
===========================================
+ Hits 4927 5288 +361
- Misses 3535 3654 +119
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
merge with latest staging
|
@pradnyeshjoshi you are getting the same error in the GitHub gpu test as in #1606. Do you know where the error could come from? |
miguelgfierro
left a comment
There was a problem hiding this comment.
You are doing good Pradnyesh, I added some ideas that are taking following our coding guidelines: https://github.com/microsoft/recommenders/wiki/Coding-Guidelines
As much as you can, try to simplify the code. We follow the Zen of Python:
Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
:-)
|
There is an error in the ADO pipeline: https://dev.azure.com/best-practices/recommenders/_build/results?buildId=55820&view=logs&j=5f8f9dfe-6536-5030-a755-a0d185c26462&t=9c790e16-9f7c-5445-8be8-0594d5cf6650&l=87 |
@miguelgfierro This error is resolved now. The |
merge with latest staging
great. The spark issue I think it is related to the memory of the test VM, so I wouldn't worry about it |
…ders into pradjoshi/rbm_cleanup pull latest changes
merge with latest staging
Description
The following changes are made to facilitate better reuse of existing modules and increase readability,
tf_evaluation.py.fitandrecommend_k_itemsfunctions anymore.Related Issues
Checklist:
staging branchand not tomain branch.