Eloy Lafuente

Hi @ewallah , it seems that there are a few coding-style little changes to apply, plus unit tests are failing with your patch. Is it ok if I amend your...

Oh, @ewallah, I just was adding here a test and confirmed that `FilesystemIterator::SKIP_DOTS` does not skip all dot (hidden) files (.something.txt, .git, ...) but, exclusively, the "." and ".." directories....

Yeah, I can see that Langfuse still has a lot of `pydantic_v1` uses here and there and, in theory, that will work based on the code in [langfuse/api/core/pydantic_utilities.py](https://github.com/langfuse/langfuse-python/blob/main/langfuse/api/core/pydantic_utilities.py#L7-L12). I've confirmed...

I've been able to reproduce it with just this: ``` $ python -m venv .venv $ . .venv/bin/activate $ python --version Python 3.14.0 $ pip install langfuse ... ... 3.8.1...

Hi, really, there isn't anything new when I apply for those 3 lines. Here there are the complete logs with them enabled, apart from some "own" initialisation stuff that I...

For the records a few days ago I proceeded to update out staging bot to v0.7.1 and completely remove the storage (to get a new token and so on). It...

Update: We have 0.7.1 running (after deleting storage) here since a few days ago in prod, and it seems that this problem isn't happening anymore. We are facing #346 a...

For the records, I've just tried with `litellm_stable_release_branch-v1.72.2-stable` and it continues failing with same error reported above. As a temporal workaround, what I've done is to add a fallback from...

I think that **this can be safely closed** as far as `distil-whisper-large-v3-en` was [deprecated and removed](https://console.groq.com/docs/deprecations#august-23-2025-distil-whisper-large-v3-english) in Aug 2025. Also, I can confirm that both `groq/whisper-large-v3` and `groq/whisper-large-v3-turbo` (the [currently...

I'm facing the same here when testing #11325 (Groq's whisper models) on Arm64 docker image (`v1.79.3-stable`) The same version, running on x64 docker image is, apparently, ok. ``` { "error":...