fix(connector): better locating and error reporting for connector library

[BugenZhao]

Signed-off-by: Bugen Zhao [email protected]I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

This acts as a preparation step of risingwavelabs/homebrew-risingwave#28.

• Canonicalize the path of current_exe before looking for the sibling libs directory. So it's based on the real path of the binary (like /opt/homebrew/Cellar/risingwave/1.6/bin/risingwave), instead of the symbolic link (/opt/homebrew/bin/risingwave). opt/homebrew/bin/libs will make no sense.

• Use fs_err as the replacement of std::fs to provide better error reporting.

• Use LazyLock::get_or_try_init instead of storing the Err variant into the static variable once the initialization fails. The main motivation is to resolve the error source issue, but the advised behavior appears to make more sense to me as well.
  

  risingwave/src/jni_core/src/jvm_runtime.rs

  Lines 45 to 47 in d616c1c

  	// Note: anyhow!(e) doesn't preserve source
  	// https://github.com/dtolnay/anyhow/issues/341
  	Err(anyhow!(e.to_report_string()).context("jvm not initialized properly"))

---

Preview of the UI:

I run .risingwave/bin/risingwave/playground, which is a symbolic link of target/debug/risingwave

ERROR:  Failed to run the query

Caused by these errors (recent errors listed first):
  1: gRPC request to meta service failed: Internal error
  2: failed to create source worker
  3: failed to create SplitEnumerator
  4: jvm not initialized properly
- 5: CONNECTOR_LIBS_PATH "/Users/bugenzhao/Developer/S/risingwave-opensource/.risingwave/bin/risingwave/./libs" is not a directory
+ 5: failed to read connector libs
+ 6: failed to read directory `/Users/bugenzhao/Developer/S/risingwave-opensource/target/debug/libs`
+ 7: No such file or directory (os error 2)

Checklist

• I have written necessary rustdoc comments
• I have added necessary unit tests and integration tests
• All checks passed in ./risedev check (or alias, ./risedev c)

Documentation

• My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note

If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

[chenzl25]

LGTM