bichselb

Results 12 comments of bichselb

I am still unable to resolve this issue. Does Soot even support Java 13 (as in, running Soot on Java 13, analyzing code compiled by Java 13, but the analyzed...

After I year, I still was unable to resolve this issue. Any help would be appreciated.

Thanks for the recommendation! Unfortunately, I have not found the analogous file for Java 13. Specifically, there seems to be no file "rt.jar" for Java 13 at all. The closest...

I just noticed that this works, but is extremely slow - much slower in Java 13 than in Java 1.8. Is this expected? The analyzed program is tiny, but the...

Thanks for the quick response! Indeed, the error does not occur for `revtex` or `article`. For example, this works: ```latex \documentclass[a4paper,twocolumn]{revtex4-2} \pdfoutput=1 \usepackage{tikz} \usepackage{lipsum} \begin{document} \title{Template Bug Demonstration} \maketitle \begin{figure*}...

Thanks for investigating! This helped in some cases, but now I ran into an analogous issue: ```latex \documentclass[a4paper,twocolumn]{quantumarticle} \pdfoutput=1 \usepackage{atbegshi} % needed for quantum class (prevents \box255 error) \usepackage{tikz} \usepackage{lipsum}...

Thanks! I have found some workarounds myself, but the bottom line is that this issue keeps popping up, so it would be great if it could be resolved at the...

@ wmkirby1 It has been a while since I used these workarounds, but I think some advice here helped: https://tex.stackexchange.com/questions/402627/using-clearpage-after-figure-in-revtex-gives-error-output-routine-didnt-u

I was able to make the consumer almost as fast as the producer by setting various configuration properties specified by [librdkafka](https://github.com/confluentinc/librdkafka/blob/master/CONFIGURATION.md) (most importantly `fetch.message.max.bytes`). This is my fixed setup: https://github.com/bichselb/confluent-kafka-go-performance/tree/fast

Thanks @OneCricketeer for the hint. However, this is not the reason for the slowness (the client configuration time is negligible compared to sending 1 million messages).