Seanium commented on code in PR #3102:
URL: https://github.com/apache/hugegraph/pull/3102#discussion_r3642818147


##########
hugegraph-server/hugegraph-dist/src/assembly/static/bin/util.sh:
##########
@@ -25,6 +25,45 @@ function command_available() {
     fi
 }
 
+function configure_riscv64_libatomic() {

Review Comment:
   Fixed in `1c30c1c5`.
   
   `dump-store.sh` now sources `util.sh` and configures `libatomic` before 
starting its
   independent JVM. The launcher also had two pre-existing blockers that 
prevented a real
   smoke test: its classpath variable was passed as a literal, and its default 
graph config
   pointed to the removed `conf/hugegraph.properties` path. Both are corrected, 
while
   explicit config/table/offset/limit arguments remain supported.
   
   The distribution launcher audit found three automatic local-backend openers:
   HugeGraphServer, InitStore, and StoreDumper. All three now use the helper. 
ConfDumper,
   CheckSocket, and Gremlin Console do not automatically open a local RocksDB 
graph, so no
   unrelated preload was added.
   
   The native smoke now stops the Server, runs the no-argument 
`bin/dump-store.sh` with a
   120-second bound, and requires both current-run vertex IDs in the dump 
before restarting
   and verifying persistence. On native RISC-V with Dragonwell 11, the current 
head passed
   the clean 16-project build and the complete 
JNI/init/REST/Gremlin/store-dump/restart
   flow with final process, PID, and port cleanup. The six Apache workflow 
suites for this
   head were automatically scheduled and are currently awaiting maintainer 
approval.
   



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to