Skip to content

fix: updated lc handbook 01 #469

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 25, 2025
Merged

fix: updated lc handbook 01 #469

merged 1 commit into from
Jun 25, 2025

Conversation

jamescalam
Copy link
Collaborator

Had to change the example from prompting the LLM to make jokes in response to serious questions, to a Markdown formatting task, as newer LLMs are too good at following orders and the supposedly bad responses were not actually bad.

Problem

Describe the purpose of this change. What problem is being solved and why?

Solution

Describe the approach you took. Link to any relevant bugs, issues, docs, or other resources.

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update
  • Infrastructure change (CI configs, etc)
  • Non-code change (docs, etc)
  • None of the above: (explain here)

…templates.ipynb to Work with LangChain 0.3 (#451)

Used newer models and new HuggingFaceEndpoint() class (instead of the,
now deprecated, HuggingFaceHub() class. Changed the LLM from
text-davinci-003 to gpt-3.5-turbo, since the former is deprecated. Had
to change the example from prompting the LLM to make jokes in response
to serious questions, to a Markdown formatting task, as newer LLMs are
too good at following orders and the supposedly bad responses were not
actually bad.

## Problem

Describe the purpose of this change. What problem is being solved and
why?

## Solution

Describe the approach you took. Link to any relevant bugs, issues, docs,
or other resources.

## Type of Change

- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update
- [ ] Infrastructure change (CI configs, etc)
- [ ] Non-code change (docs, etc)
- [ ] None of the above: (explain here)

## Test Plan

Describe specific steps for validating this change.

---------

Co-authored-by: James Briggs <[email protected]>
@jamescalam jamescalam self-assigned this Jun 25, 2025
Copy link

Check out this pull request on  ReviewNB

See visual diffs & provide feedback on Jupyter Notebooks.


Powered by ReviewNB

@arjunpatel7
Copy link
Contributor

Lol I've ran into similar issues with generations now. Will review soon.

@arjunpatel7 arjunpatel7 self-requested a review June 25, 2025 18:32
Copy link
Contributor

@arjunpatel7 arjunpatel7 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, no filepath changes, package versions exist, and doesn't use Pinecone so we don't need to worry about source tags. Thanks!

@arjunpatel7
Copy link
Contributor

LGTM, passes our run test so can be run as well.

@arjunpatel7 arjunpatel7 merged commit ef746dc into master Jun 25, 2025
9 checks passed
@arjunpatel7 arjunpatel7 deleted the james/lc-01-update branch June 25, 2025 18:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants