Fixed SAR notebooks

[ChuyangKe]

Description

Fixed the error that in SAR notebooks, the TOP_K parameter is not properly supplied to function model.recommend_k_items().

Related Issues

Checklist:

• I have followed the contribution guidelines and code style for this project.
• I have added tests covering my contributions.
• I have updated the documentation accordingly.
• This PR is being made to staging branch and not to main branch.

[review-notebook-app]

Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

---

Powered by ReviewNB

[gramhagen]

looks good, thanks!

[miguelgfierro]

@ChuyangKe congrats for your first PR! Awesome!

[miguelgfierro]

@pradnyeshjoshi this PR has an error with the AzureML credentials, same as #1736, however, this one doesn't have any error: #1739 Do you know what could be happening?

[pradnyeshjoshi]

@pradnyeshjoshi this PR has an error with the AzureML credentials, same as #1736, however, this one doesn't have any error: #1739 Do you know what could be happening?

@miguelgfierro Looks like @ChuyangKe has created a fork of the repo, and GitHub Actions has no way to make secrets available to forks, so it's not able to find the login credentials.

[ChuyangKe]

k of the repo, and GitHub Actions has no way to make secrets available to forks, so it's not able to find the login credentials.

@pradnyeshjoshi Yes I created a fork to my account. Do I need to push in other ways?

[pradnyeshjoshi]

k of the repo, and GitHub Actions has no way to make secrets available to forks, so it's not able to find the login credentials.

@pradnyeshjoshi Yes I created a fork to my account. Do I need to push in other ways?

@ChuyangKe we usually create a feature branch off of staging in the same repo and create a pull request into staging. AzureML tests in this PR are failing because the credentials to log into AzureML (as part of unit test workflow) are stored as repo level secrets. I am looking into how we can support PRs from forks.

[miguelgfierro]

@pradnyeshjoshi the same thing is failing here: #1732 are you sure it is related to the fork?

[miguelgfierro]

@ChuyangKe I have added you to the repo, from now on, you don't have to create a fork, you just need to create a branch from staging and then PR to staging

[pradnyeshjoshi]

@pradnyeshjoshi the same thing is failing here: #1732 are you sure it is related to the fork?

@miguelgfierro In #1732, the error occurs because the group name mentioned in the workflow file does not exist anymore in the test_groups.py script. I will add another task to have the workflow pick up group names dynamically.

[miguelgfierro]

I'm rerunning again all the tests FYI @pradnyeshjoshi @ChuyangKe

[miguelgfierro]

I will merge this because I think with the new PR of @pradnyeshjoshi solved the AzureML issue