@balaji.ambresh there is no issue with notebook, when I told to make change for another error, he encountered this error and when I looked at his codes, seemed like he extra code line added, so I advised him to get first fresh copy.
I am sharing the linked error to this error which was encountered first, just in case any learner encountered similar error. The IOPub data rate limit error is usually because of incorrect recalling of dataset when text and labels were recalled separately, but in case dataset was recalled correct and still model shows incorrect parameters, then next lookout was fit label encoder, where for this learner I suspected there was editing/addition of codes lines which got transferred to the dataset codes.
preprocess_dataset is used to create train_proc_dataset and validation_proc_dataset. Since the learner output doesn’t match the expected output in the markdown, test_preprocess_dataset should catch the mistake as well.
But I cannot raise this yet until I see the learner has followed the instructions as per given in assignment as I saw the codes, there were addition of 2 extra code lines and as you know a unittest might not catch an error for hard-coded path, it will throw an error in the following test cell.
if unittest didn’t catch the test even after following the instructions then i will report to repo.
Sorry Balaji I keep tagging the wrong person as that name appears first
In the preprocess data, basically there are 3 call arguments already assigned for this grade cell.
one is dataset for you to preprocess
next text_vectorizer which is function recall to convert your text data into vector
and lastly label_encoder which you recalled in the previous grade cell will be used to encode data labels here in this cell, preparing your preprocess data to be model trained.
You need to define this in single code line using map keys( ) to the argument dataset.
Hope this resolves your issue as per our DM discussion.