Good First Issues in Nim

Nim Version 023bd63, at least 0.9 Description Nim/lib/pure/strutils.nim Line 2557 in 2ac83c7 buf {.noinit.}: array[0..2500, char] It was increased from 80 because of #398, but also the example in #398 doesn't work because the precision argument is limited to a max of 32. Also thanks to #23322 snprintf is now used, which doesn't error if the output does not fit in the buffer. This doesn't seem to be a huge issue but maybe it is still worth shrinking the buffer. Feel free to close otherwise. Current Output Expected Output Known Workarounds No response Additional Information No response

Hello, I think theses features use to be enabled but as it's not working anymore, I am requesting for : • when browsing a list of users (nitter.com/johndoe,johnappleseed,morpheus ...) allow clicking on username (top of page) to go to user's feed • when someone retweet, allow to click on username ("johndoe retweeted") to go to user's feed (nitter.com/johndoe), not the retweeted tweet Thanks !

it would be nice for all interop tests, that are written by nim-libp2p, to have run.sh file that could be used to run test locally and same could be used in ci. this eliminates any possibility for error to happen due to not running some peer from specific directory for this peer+interop test. #2119 (comment)

Tracker issue for all execution-api JSON RPC issues. Most of these are visible / discovered via hive tests, but some are additional ones discovered (and more are likely to be discovered as these get worked on). Some are also just spec / test vector / hive PITAs For latest hive results on rpc-compat: https://hive.ethpandaops.io/#/test/generic/1769753159-b9b9d40703a67f0737e0eb880873ff13 Recurring issues over several methods: block tag not parsing hash Some calls are named "...ByNumber" or "...ByHash" These will parse either: latest/safe/finalized and number block hash Other calls without this specific naming however are often supposed parse latest/safe/finalized + number + hash. Several failures are due to nimbus not implementing the hash part. #3981 null vs omit vs error vs [ ] null vs omitting the fields: Our current JSON flavor is set to NOT omit null fields (= Opt.none(T)). This is because this behavior is actually expected/specified in engine_api (see status-im/nim-json-rpc#238