Oddbean new post about login | logout it’s windows tho so feel free to clown me 💀
No, sir. I have a Thinkpad X1 Carbon (hence, shawn@carbon above) running Linux. Runs wonderfully.
did you make the switch to Linux the moment you got it ? I’m scared af to make the switch
It was acquired exclusively for that purpose. 😉 You can go with a dual-boot setup. Ubuntu is super straightforward to start with.
👀 I forgot completely about that 🤣 I’m on it!! https://i.nostr.build/pyBGmfainDSHH9Rd.png
or use WSL. I use mostly WSL for everything, and use windows only for things my employer requires me to. It's completelly seemless, even for GUI apps.
my issue with WSL is certain dependencies I can’t add
seriously? i never got this issue.
Have you had success compiling Lume ?
Wait nvm it wasn’t Lume it was Gossip
trying now.
followed instructions, compiled ok. seems to be working. https://image.nostr.build/f27f93349cbfbd9386a91285ebc080f497ee2db4aae459dc3e6cc97869caaa4c.png
👀 it’s either that I’m retarded or ARM64 based pc issues @Mike Dilger 👀
oh.. probably arm64... i have plenty of issues with dependencies in my raspberry pi's...
gossip seems to use LMDB. LMDB has issues with arm, that need some fine tunning to work. this might be the issue here.
I didn't know LMDB has issues on ARM. If you have compile failures, or runtime issues with LMDB data corruption, please file an issue on github so I can try to find the problem https://github.com/mikedilger/gossip Also, gossip compiles on windows without needing WSL. You just need a git-bash shell to run the commands from.
alignment matters on arm if doing zero copy flatbuffer stuff, on intel its just a performance hit. this has nothing to do with lmdb tho, we use lmdb on ios and it works fine.
Yes ok alignment matters. LMDB data is just a sequence of bytes so it is not doing any alignment, and I presume each LMDB value starts aligned. I'm using speedy for most of the data, and I see zero issues on the speedy repository about anybody getting alignment errors. That is why I'd love to see an error message, so I can know this issue is real and then chase it down, rather than trying to fix something that might not be broken.
I’m gonna hop on @HiveTalk in like 20 mins to try doing it again I’ll share my screen n see if anyone can help walk me thru it
ok i'll join
Not specific to gossip. I had problems with both stfry and khatru. It's usually at runtime, when initializing the DB it complains of "out of memory" (i suspect it is actually complaining of low disk space). I'ts usually solvable by lowering the size limit for the DB. (strfry has a param for that, but in kathru i had to fork and change the source). I haven't tried gossip in arm yet, i'll try it tomorrow and if i run into troubles, i 'll post an issue.
Ah yes. You have to tell it how big the database might eventually become ... a max size... when you create it. If you don't have that much space it would fail.
it doesn't fail on linux-amd64 though. But it fails in other platforms.
Has something to do with sparse file support I'm guessing.
Anyway, the problem @sersleepy is getting is quite different, from his other posts. It seems he has problems with the C compiler: nostr:note1yekq0lmw8fjkdtee6s3appxzwqn7vaqrr2xyk007twneeyt6rp7syj7vv9
We use 24GB. I could make a launch option to set it smaller I suppose.
