Class: Multi AI Agent Systems with crewAI
The class uses Jupyter notebooks with additional text files. Those text files that the code needs to access are NOT supplied. Can you upload those files to the class lectures for users to access.
Specifically: In the lecture, “Tools for a customer outreach campaign (code)” there are instructions files missing. Please upload them and for all the other lectures as well.
I was able to run the notebook associated with that lecture, without any issues.
What files do you feel are missing? Please be specific.
I’m not sure how to answer your question, because I had no problem running the code cells in the notebook on the left side of the course window.
See below:
I had to let the video play in the right pane for about 40 seconds, then the notebook opened up on the left side.
Then I just ran each code cell in sequence, (I circled the first two in red), and everything ran without me having to make any changes or load any other files.
Nothing was missing.
L2: Multi AI Agent Systems with crewAI
I am running the lab locally using Jupyter Notebooks and have created a separate folder for my project and saved all related files in that folder. Also edited the utils.py file to pass the OPENAI API KEY and SERPER API KEY of my own. But when I run the Jupyter Notebook file, I get the following error messages:
Do I need to have dotenv file in my directory? Because I am using this function as default in the utils.py file:
import load_dotenv, find_dotenv
Moreover, my directory looks like the following: Do I need to upload .env file or is it missing? Or is there any other problem with my code or project?
Sorry, but I cannot answer. I have no experience with making the labs run locally.
@Deepti_Prasad Can you please guide me on this issue?
Best regards,
Ahmed
hi @mtsahmed2
in the metadata if you check the requirements file, this will provide the module version the codes were run down, so check in your local environment if the version matches.
As per your error stated, it clearly states you are not using your own api keys, resulting in the error.