arcadedb
https://github.com/arcadedata/arcadedb
Triage Issues!
When you volunteer to triage issues, you'll receive an email each day with a link to an open issue that needs help in this project. You'll also receive instructions on how to triage issues.
Triage Docs!
Receive a documented method or class from your favorite GitHub repos in your inbox every day. If you're really pro, receive undocumented methods or classes and supercharge your commit history.
not yet supported1 Subscribers
Add a CodeTriage badge to arcadedb
Help out
- Issues
- PostBatchHandler's forward HttpClient is never released, so every HttpServer start/stop cycle leaks a selector thread
- TrustedHttpClientCache rebuild closes the previous client under its monitor, so a truststore rotation can stall every HTTPS forward for the forward's own deadline
- The bootstrap election's peer fan-out uses an unguarded derived HTTPS address, so an SSL cluster that declares http ports but not https ones elects a baseline from its own answers
- The replicated drop-database apply takes no maintenance slot on the peers, so a drop database tears down every other node's in-flight backup, export or import
- The MCP stdio loop still exits 0 when stdin fails mid-session, so a transport that died on an I/O error is reported to the supervisor as a clean shutdown
- The Studio cluster-readiness gate added for #7538/#7548 refuses to answer on a follower, which is the one limitation #7549 had just removed
- The #7467 edge fix passes the row's property map into newEdge() unconditionally, so a /ws insert of a LIGHTWEIGHT edge is refused for "carrying properties" it did not send
- The #3722 shortfall fallback counts rows the calling transaction has deleted as still available, so a vector search inside such a transaction logs "graph may need rebuilding" and runs a full brute-force scan that finds nothing
- The binary-resource carve-out added to the parent POM does not reach the engine module, because engine's own <resources> block replaces the parent's list wholesale
- The gRPC API-token listing was left out of the #7601 "say which tokens have expired" change, so the one protocol that cannot see the flag is the one whose tokens now linger forever
- Docs
- not yet supported