Grain 🌾 v0.4.0 release !

There's a lot here. πŸ‘‡

https://github.com/0ceanSlim/grain/releases/tag/v0.4.0

#dev #relay #nostr

Reply to this note

Please Login to reply.

Discussion

nostr:nprofile1qqst6jhruelzn9jdf9qhyfsac3fetjyld0fwwary9cmxzfchrhacragpz4mhxue69uhk5etvd3ukv6tndqhxcctwvshszrnhwden5te0dehhxtnvdakz7qghwaehxw309a5kuer90qhxs7njvscngwfwvdhk6uv5t08 here is what I came up with for my logging solution. All standard library. Print in log or json, define components, suppress components, set backup interval, number of backups and max file size.

Great job! I'll take a look at it soon. πŸ‘€

nostr:nprofile1qqs99d9qw67th0wr5xh05de4s9k0wjvnkxudkgptq8yg83vtulad30gprpmhxue69uhhyetvv9ujumn0wdmksetjv5hxxmmdqyxhwumn8ghj7mn0wvhxcmmvqy2hwumn8ghj76rfwd6zumn0wd68ytnvv9hxgj24yzk did I fix it?

will check

checking

approved

πŸŽ‰

testing 2...

lgtm (~377ms connect, 133ms write from event cannon)

Perfect. Thanks so much. I'll be working on tests myself for the future.

nice work man, clean well structured code πŸ™‡β€β™‚οΈ

main is awfully large and untestable - recommend delegating it all to another abstraction, make main minimal and focused on runtime/config concerns πŸ‘

have you had any thoughts how to approach testing all wait/sync/gofunc core 🫨 I haven’t yet πŸ˜” circled back yet to relays but will join you soon hopefully, focused on platform and revenue first then 😁

Making main smaller with a startup routine was actually my next step! Then some testing! I still don't know where to begin on it... But at least with logging I'll be able to debug was wat quicker.

I've made a few clients now as well so the idea now is to make a reference client implementation in grain. So the client package is getting redone entirely soon.

GM