Vinícius Dantas
Vinícius Dantas
I acknowledge that the server is initialized at libFunq/funq.cpp, which uses qDebug for logging messages. I tried running: ``` QT_LOGGING_RULES='*.debug=true' funq --host 0.0.0.0 --port 9000 YourApp ``` But I didn't...
Just checked its source code. So it neither stores the original headers nor uses them on exporting. Exporting uses slugs only, as I can see on `rows/plugins/utils.py`'s `prepare_to_export` function. Thoughts...
Did you figure it out? I am having the same problem, I've been trying for a day already without much progress
> Hi, this same issue ... any progress or ideas ? Nothing from my side :/ I haven't tried to debug it yet; I will try to give it some...
I am currently struggling switching among different databases. A per-database history would be neat
How are you reaching the conclusion the build failed? I don't see any error message
Interesting. FYI the output of my `cmake -S .` is the same as yours, but my target test works just fine, i.e., all tests run Is your brew x86 or...
> > Is your brew x86 or arm? > > It is arm64. If I'm not mistaken, all M series are arm-based. > Yep, but the M series supports x86...
I just happened to make a mistake that might have been yours. I was just going over the ubpf compilation again, and I did: ```shell cmake -S . -B build...
Yeah, `test` runs the tests, but it assumes binaries have been compiled before. **_tl;dr_** I am getting the same as you on the last 2 tests, I am ignoring that...