Ecosystem metrics

New Repos
5
up 150.0%
Commits
374
down 16.9%
Releases
2
up 100.0%
Contributors
32
down 8.6%
Merges
11
up 120.0%

Repository Explorer

7826 commits in all time Aug 20, 2026 10:35 – Nov 18, 2026 10:35 UTC
giuliop go-algorand
Merge f686e0dab7661cce10da77237663344b0b9a43df into e46aea5466a1152af6e08f83555ed16cfcd89f49
Git Commit 78115c21 Branch pull/6828/merge Document 3/176 ++ 1 --
giuliop go-algorand
agreement: do not block the demux loop on a failed crash-state write
When the crash-state write for an attest action fails, checkpointAction.do sends the error on persistStateDone, an unbuffered channel. Its only receiver, pseudonodeVotesTask.execute, reads it only when the node has verified votes for the step, and stops reading on quit or context cancellation. On a participating node whose keys were not selected, which is the usual case for small accounts, nothing ever received it, and the send blocked the demux goroutine for good. The node stopped voting, proposing and processing agreement messages, did not recover when the storage did, and Service.Shutdown, which algod calls on SIGTERM, never returned.

persistStateDone now has room for that one error. At most one value is sent before the channel is closed, and a votes task still receives the error and drops its votes, whether it reads the channel before or after the send.

TestAgreementPersistenceFailureUnselectedNode runs four nodes, gives node 0 a participation key but no stake, and closes node 0's crash database after one round. Once node 0 has logged the failed write, the test requires it to complete the round, go quiet and shut down; it fails without this change. TestPseudonodeVotesDroppedAfterFailedCheckpoint checks that a selected node sends no votes when checkpointAction.do has already sent the error and closed the channel before the votes task reads it.
Git Commit f686e0da Branch pull/6828/head Document 3/176 ++ 1 --
ipaleka frontend
Bugfix for check authorization transaction routine reading a list error
Git Commit effd9d60 Branch main Document 3/80 ++ 129 --
Merge 631fee0994d1c8a52117f44e25d3e646fda4b5bc into 682f57e25226d5858da5c639227921c7fe33cdb0
Git Commit 44aa65e8 Branch pull/603/merge Document No file changes
Merge 54248189ea773619d23fe14c9c9f588c6da6a612 into 682f57e25226d5858da5c639227921c7fe33cdb0
Git Commit 331bc746 Branch pull/592/merge Document No file changes
Merge efcd68e0a144be0b969e4997c12ec9395a9d1166 into 682f57e25226d5858da5c639227921c7fe33cdb0
Git Commit cbf8e2a5 Branch pull/589/merge Document 2/5 ++ 5 --
Merge 4ef7b5842e56da52fc9e6ab7488d7f7a29f42704 into 682f57e25226d5858da5c639227921c7fe33cdb0
Git Commit 0c67c4c7 Branch pull/588/merge Document 2/607 ++ 16 --
urtho algokit-lora
Merge af76eecce824757ba96a7ad345bab2fda91a6b18 into 682f57e25226d5858da5c639227921c7fe33cdb0
Git Commit c654a6a6 Branch pull/548/merge Document 5/100 ++ 1 --
renovate[bot] use-wallet
Merge 17e15e8a308c4a5b25120b49a13a8a2d5bf4e38e into 68cedfc5d27179fce2657038a7814174c0dc9335
Git Commit 593bf729 Branch pull/476/merge Document 14/1,342 ++ 749 --
renovate[bot] use-wallet
chore(deps): update non-major dependencies
Git Commit 17e15e8a Branch renovate/non-major-dependencies Document 14/1,342 ++ 749 --
Merge 93ef58d0f689471da368e5acf2bc43d7c721b27b into 31883696f74799aa501420f226b9c442d395c0d5
Git Commit 45c42492 Branch pull/473/merge Document 4/37 ++ 6 --
joe-p go-algorand
Merge e40a2306d620f2e972e255af6667f553d9103037 into e46aea5466a1152af6e08f83555ed16cfcd89f49
Git Commit 2096fb1c Branch pull/6752/merge Document 14/6,640 ++ 24 --
JBScaled devportal
Merge pull request #695 from algorandfoundation/docs/lora-naming
docs: use "LORA" consistently on hand-written pages
Git Commit ccce1b81 Branch main Document 10/35 ++ 35 --
joe-p go-algorand
simulate: report override failures as requests and finish the API docs
Return only "simulation panicked" when a panic is recovered in Simulate,
so the 500 body no longer echoes the recovered Go value; the value still
goes to the log. Fix the StartEvaluator comment to list LatestTotals
instead of the always-erroring LookupLatest.

Report an account whose pending rewards cannot be settled as an invalid
override rather than a 500, matching the other checks that reject state
the evaluator cannot handle. The "params not found for creator" cases
keep returning internal errors: both sides of the comparison read the
raw ledger, so an override cannot be responsible.

Document the 1024 item limit, and move the semantics that were attached
to $ref siblings (delta shape, box names as keys, allowed box actions,
local-state-schema scope) into the parent type descriptions, which
survive the oas2 to oas3 conversion.

Drop required from SimulateBlockOverride.round and set x-omitempty: false
instead. The generated type keeps the round without omitempty, so an
explicit round 0 survives go-codec's empty-value omission, while the
spec no longer marks an optional field as both required and nullable.
Git Commit e40a2306 Branch feat/state_override Document 7/26 ++ 23 --
acfunk xHD-Wallet-API-ts
Merge 5844bef1fa0a6cb6bf24adee5340b0b08aa92bf3 into c2384e895f6f24251f2fc880c7335658cab2b42e
Git Commit 1ab6ecae Branch pull/37/merge Document 7/79 ++ 74 --
acfunk xHD-Wallet-API-ts
Merge remote-tracking branch 'upstream/main' into refactor/v2-noble-sync
Git Commit 5844bef1 Branch pull/37/head Document 3/18 ++ 3 --
JBScaled devportal
Merge bbdc899610522d26f877b731b17875f01524f3c6 into d01651fef55be744794d876e7f2fa155eed779c5
Git Commit cbe7e652 Branch pull/695/merge Document 10/35 ++ 35 --
JBScaled devportal
Merge branch 'main' into docs/lora-naming
Git Commit bbdc8996 Branch docs/lora-naming Document 99/99 ++ 39 --