Manuel Rigger

>SQLancer on my local mechine ran 0 queries and 0 was succesful, resulting the build success. It seems like some kind of deadlock is triggered?

According to https://github.com/sqlancer/sqlancer/blob/1f80de16e38c4a144e8dabbcef00d07cd15470f9/test/sqlancer/dbms/TestMariaDB.java#L18, it seems expected that we don't generate any queries. I remember that queries often crashed MariaDB, so this might be the reason why we disabled it. So...

In this case, what about disabling `OPTIMIZE` for now using the pattern described in https://github.com/sqlancer/sqlancer/blob/main/CONTRIBUTING.md#unfixed-bugs?

> > In this case, what about disabling `OPTIMIZE` for now using the pattern described in https://github.com/sqlancer/sqlancer/blob/main/CONTRIBUTING.md#unfixed-bugs? > > So in this case, we need to report this issue to...

> You disabled the `TRUNCATE` statements? I meant adding expected errors to the generator of `TRUNCATE1 Does this statement result in a deadlock? If so, we might want to avoid...

@bajinsheng could you please review this PR, since you have recently worked on the logic for writing out query plans?

Thanks a lot for your quick response and sorry for my delayed one. Applying `LLVM-fix-sanitizer-build-with-modern-glibc.txt` solved the build issue that I encountered. Thanks! However, I encountered another build error: ```...

Are there any updates how DangSan could be built on Ubuntu 18.04?

I think it would be helpful to further reduce the test case to figure out what causes the conversion (e.g., is it the cast to `BIGINT`?). @hanyisong, do you have...

Just checking - this is still WIP, as it is marked as a draft PR?