Ambrose Robinson

I'm also struggling with the same issue. Without empty there's no real way to make a streamlit app properly dynamic without lots on ugly lapsed elements

This error occurs when an error is raised inside the fragment, not because of a bug with fragments themselves (although not propagating the bug properly could be considered a bug)....

I'd like to bump this I'm running into the this issue on my project and it's causing significant delays. Does this branch solve the issue but is not tested enough...

I'm also running into this error but only when quantising the model. I made an edit much like the one referenced here by @ylacombe > Hey @ArthurZucker ! I'm facing...

Just want to bump a bunch of the issues I've mentioned in #761 but specifically the problem with `requires_grad` reproducable in [this repo](https://github.com/ambroser53/peft_error_reprod)

I would also like to know this!

Thanks for your response. I have implemented everything you said into my project but still finding LMQL in async to be creating a lot of problems and I cannot get...

Thanks for the quick reply. Re 2, so if all different workloads share the same decoding method then they should naturally have pretty well optimised scheduling and performance? Are there...

OK so because I was optimising so much and running the repo in absolutely tiny conditions where it must have performed quickly I think this isn't a speed issue but...

Running with the toy environment with `EleutherAI/pythia-70m` on cpu with `nest_asyncio.apply()` gave the following new error: `To avoid this, please make sure to not call lmql.model(..., inprocess=True) on the top...