test: address tests failing locally

[ajbozarth]

Misc PR

Type of PR

• Bug Fix
• New Feature
• Documentation
• Other

Description

• Link to Issue:

An assortment of test fixes to get uv run pytest passing both locally on my Mac and on bluevela.

Testing

• Tests added to the respective file if code was changed
• New code has 100% coverage if code as added
• Ensure existing tests and github automation passes (a maintainer will kick off the github automation when the rest of the PR is populated)

[github-actions]

The PR description has been updated. Please fill out the template for your PR to be reviewed.

[mergify]

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🟢 Enforce conventional commit

Wonderful, this rule succeeded.

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

• title ~= ^(fix|feat|docs|style|refactor|perf|test|build|ci|chore|revert|release)(?:\(.+\))?:

[ajbozarth]

Just merged with main and found that the recent commit from #288 caused mypy errors on Mac since vllm can't be installed (as noted in that PR)

I added the fix in 46ccfcc to address it, it only occurs when running mypy on macOS (darwin) since the vllm dep is not installed and thus the type stubs are not installed for mypy to use

[psschwei]

why are we always skipping this one?

[ajbozarth]

This depends on the langchain_community package to run, but that package conflicts with our current dependencies, if we try to add it, even as a optional dependency, it causes a version conflict that can't be solved unless we don't install other optional dependencies, which would break other tests/examples. This can possibly be solved once we address #453

[psschwei]

could we open an issue for that (or add it to 453), just so we can track why we're skipping somewhere

[jakelorocco]

What is the conflicting package? And can you please add a note in the file as well explaining why it's always skipped.

[ajbozarth]

I ran into it early in my work on this, I'll see if I can recreate the conflict loop I got stuck on and have Bob write up an issue on it and I'll link it to #453

I'll also add a comment linking to that issue once I've opened it, for now I've disabled auto-merge so if everything else looks good feel free to approve and I'll merge once that comment is pushed

[ajbozarth]

So it seems the updates in #288 actually removed the source of the conflicts so I just pushed an update to reenable this and update the optional dependencies to include it

@jakelorocco if you could take a look?

I also noticed #487 and double checked that my update in 46ccfcc was still necessary (it is)