Tyler C Laprade, CFA

Sure thing - here it is @nhedger https://github.com/tylerlaprade/biome_bug

@tjb1019 , does that fix it even for files outside the workspace?

Hmm, I'm not able to repro even in my main project today. I wonder if it's because I changed my `biome.projects` setting.

Hi @erictraut, As per Jelle's [response](https://github.com/python/typeshed/issues/12680#issuecomment-2364599844), those errors should not be showing up. Is there a way I can configure pyright to not show them? I tried various ways of...

Ah, I see where the confusion is. I am _not_ opening `builtins.pyi` and wouldn't even know it exists if it wasn't for these persistent errors. Even with no files open...

Thanks Eric! @StellaHuang95, could this ticket be reopened, please?

@StellaHuang95, I unfortunately cannot share my repo since it's company property, and I haven't seen this repro in a "simple" case. I did include my `pyrightconfig.json` in the original issue....

Sure, good idea. I set the log level to `Trace` and ran the `Pylance: Start Logging` command (as an aside, that command isn't mentioned in the docs linked above). I...

Yes. Although that's different behavior from last week - it was previously reporting errors without opening anything.

It's also possible there's another condition responsible for getting me into the "always error" mode which I'm unaware of. I just forced the trigger for the logging.