this is now the result after stripping the fek out of my logger library, just got some hassles with go module versions

cpu: AMD Ryzen 5 PRO 4650G with Radeon Graphics

BenchmarkBinaryEncoding

BenchmarkBinaryEncoding/event2.EventToBinary

BenchmarkBinaryEncoding/event2.EventToBinary-12 141 8038303 ns/op

BenchmarkBinaryEncoding/gob.Encode

BenchmarkBinaryEncoding/gob.Encode-12 18 61665344 ns/op

BenchmarkBinaryEncoding/binary.Marshal

BenchmarkBinaryEncoding/binary.Marshal-12 9 111623125 ns/op

BenchmarkBinaryDecoding

BenchmarkBinaryDecoding/event2.BinaryToEvent

BenchmarkBinaryDecoding/event2.BinaryToEvent-12 99 13979812 ns/op

BenchmarkBinaryDecoding/gob.Decode

BenchmarkBinaryDecoding/gob.Decode-12 5 216066451 ns/op

BenchmarkBinaryDecoding/binary.Unmarshal

BenchmarkBinaryDecoding/binary.Unmarshal-12 122 9004904 ns/op

Reply to this note

Please Login to reply.

Discussion

now i can focus on the BinaryToEvent code and remove that difference 😁

i'm getting 400 errors after trying to up a new version, the git http server is reporting bogus packets, then it tries to decode gzip and it also fails because the gzip header is mangled, this is the message being sent by go tool...

not sure what to try now... maybe a different go version, seems like 1.22.3 might be buggy

oof, no beans with 1.22.2 either, what the actual... this was working just days back, now i try to put a new version and suddenly a bug i thought i'd fixed with legit is back again, bogus encoded request from the fucking go tool, or bogus decoding from the

dammmmmitttt

this must be a go.work or go.mod replace error

hmmmm maybe the legit version on my thing is broken...

bah, i wanted to do something else not debug legit again, i swear i fixed this gzip encoding bug before but evidently not

maybe it's time to go have a coffee

more probing shows that the problem seems to be more likely a bugged git repo that has been mangled

the repo clearly shows other tags than the ones go is allowing but it's pooping the cradle on anything later than an old version, which tells me that there might be some glitch with the actual git tags or someshit

gonna come back and fix it after coffee, have not had any problems with bumping new tags until this one, it's special

yes, confirmed, i wiped the existing bare repo on the host, and upped the previous version and the new version with the minimal, fast logging code

yes, worked, directly.

git is buggy, hurrah

also, second check of the other cafe down the road... seems like it hasn't been open in a while

methinks the lady i spoke to yesterday doesn't really know what her offspring is up to these days