Torsten Scholak

> And when I am using the same input/output format like yours, there are still some incomplete sql. Thanks, can you provide a continuations that the model predicted but that...

> A2: For T5-large, 61 incomplete sql in dev (1034 in total). Thank you, this is very useful. I can turn these into test cases.

More like (1), but just for the last step. I want to see which token proposals were rejected when production ended. Thanks!

I took care of the issues with the parser. I believe that what remains are problems with the model(s) or the data.

@DreamerDeo I pushed a fix. Please check :)

I did not observe a slowdown, but I also didn't complete a full evaluation. Please let me know if you observe a regression in accuracy.

Before I try to reproduce, can you confirm please that you are seeing the stalling for the original spider eval set and not your altered one with added table names?

I reopened the issue. We need to find out which examples take a lot of time to generate.

> It works now by clean the docker. Glad to hear it, can you confirm though that it is consistently good now?

> I attempt to predict the dev set in 10 pieces to find which examples take a lot of time to generate. Thank you, this will help a lot. >...