Kyle Rush

Just now seeing that #264 broke things mentioned in #266. Will take a look at that tomorrow and hopefully have a PR next week.

There's some active conversation about this in a vitest issue here: https://github.com/vitest-dev/vitest/issues/2028 I think getting `autoload` to actually run in vitest again will not be hard, but the problem I...

@alrramezani - If you use version 5.3.0 of `autoload` your Jest tests should work. You can see that working here: https://github.com/kylerush/vitest-v-tap

cc @AriPerkkio

Yes, the coverage is correct with Jest. The uncovered lines in Jest's report matches TAP's report. The overall % discrepancy I suspect has something to do with how TAP and...

I added the ts-node `register` call in `autoload` in 5.3.0. Since vitest doesn't use ts-node (I think it uses esbuild to compile typescript?) autoload was throwing errors that it couldn't...

I believe there is a [context manager](https://github.com/stanfordnlp/dspy/issues/168#issuecomment-1763406841) for this. ```python with dspy.settings.context(max_tokens=32): result = module1(first_input) with dspy.settings.context(max_tokens=128): result = module2(first_input) ```

Thanks for the thoughtful reply, @arnavsinghvi11! I think this solution could work. I'm also wondering if there is a larger opportunity to evaluate how exceptions are handled in DSPY. I'm...

Just coming back to this to re-emphasize my thought that a new pattern for error handling is probably needed. I'm running into a new error in my code and the...

Just want to note that I'd be happy to work on a pull request that proposes an approach to achieve easier debugging from errors inside of a DSPY program. Just...