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 supported0 Subscribers
Add a CodeTriage badge to arcadedb
Help out
- Issues
- The MCP tool-argument census follows only JSONObject accessors within the mcp module, so a JSONException from reading a JSONArray member, or an argument read in another module, escapes its guarantee (sibling of #9772)
- The importer commit-protocol census kept its delegate-helper clause pinned to the integration/importer/ package prefix, so a non-FormatImporter row-loop helper in another module escapes it (sibling of #11388)
- An indexed DATE property accepts a date outside the epoch-millisecond range, then every later insert and range lookup on the index fails with 500 long overflow
- Cypher and SQL: a list index or slice bound beyond the int range wraps around ([1,2,3][4294967296] returns 1)
- SQL: Result.hasProperty answers true for a column excluded by SELECT *, !name
- Cypher: OPTIONAL CALL { ... } that matches nothing leaves the subquery's returned columns out of the row instead of binding them to null
- The missing-object-refusal census ranges over a hardcoded five-type UNCLASSIFIED list, not over the refusal sites, so a missing schema object refused with IllegalArgumentException (or IllegalStateException / ConfigurationException) escapes its guarantee
- Several SQL time-series and collection functions answer HTTP 500 (raw DateTimeParseException / NullPointerException / ClassCastException) for a malformed or null argument, siblings of #11589 not named there
- Fusing consecutive GAV vertex steps drops the per-hop live-record existence check that the non-fused path performs, so a multi-hop traversal over a stale analytical view returns neighbours reachable only through a since-deleted intermediate vertex
- Tracing: a failed HTTP request or a failed query produces an OTel span that is never marked ERROR and never records the exception, because observation.error() is never called on either span
- Docs
- not yet supported