You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
CI: examples run only against arcadedb-jvm; the native package (the default install) never runs them #192
test-python-examples.yml runs examples/ (32 scripts) against the arcadedb-jvm wheel on Linux x86-64 and aarch64, macOS arm64 and Windows x64, with Python 3.11 to 3.14. test-native.yml builds the native wheel on the same four platforms and runs the full tests/ parity suite against the installed wheel, but no example.
uv add arcadedb installs the native package, so the examples a new user copies are never run on what they install. A breakage that only shows in an example (an API the example uses but no test covers, a path, an import) would ship unnoticed for the default install.
Proposal: an examples job in test-native.yml on the wheels that workflow already builds (four platforms, Python 3.12 and 3.14, the same Pythons as the parity runs), using the same runner logic as the JVM examples job. An example that only works with the JVM package goes on an explicit list that the job prints with its reason, so nothing is skipped silently.
Activity
native: a query row nested in a value reaches Python as a map, not a …
ci: native examples skip list: the JVM-only examples and the engine-2…
ci: run examples/ against the installed native wheel (#192) (#193)