[coverage] Conformance findings: LOGGING-002

Bắt đầu bằng việc xem xét các kiểm thử xfail LOGGING-002 trong tests/ ở PR #1224, sau đó tìm DBSQLLogger và cơ chế truyền tải tệp của nó trong repository này. Tái hiện trường hợp đích là một thư mục và so sánh với hành vi tham chiếu trong PR #234; được xem là hoàn tất khi các kiểm thử tuân thủ đều chuyển sang trạng thái đạt mà không xảy ra lỗi EISDIR không đồng bộ.

Summary

Surfaced by the multi-language coverage fan-out while conformance-testing these SPEC-IDs against databricks/databricks-sql-nodejs. Each finding is committed as an expected-failure (xfail) test in the coverage PR — the test asserts the CORRECT (post-fix) behavior and stays red until THIS driver (databricks/databricks-sql-nodejs) is fixed, then flips green as a tripwire.

Findings

• LOGGING-002 [thrift, sea]: DBSQLLogger passes filepath straight to its file transport with no directory-vs-file resolution, so a directory log destination yields no log file inside it and raises an async EISDIR on the transport stream instead of degrading to less/no output
  • failing test: directory log destination resolves to a log file inside it [thrift], directory log destination resolves to a log file inside it [sea] (see the coverage PR diff under tests/)
• LOGGING-002: DBSQLLogger passes filepath directly to its file transport with no directory-vs-file resolution, so a log destination naming an existing directory is opened as a file: no log file is created inside it, an EISDIR surfaces asynchronously on the transport stream (uncaught, can abort the host process) instead of degrading to less/no output, and the caller gets no logs — the file-path form works correctly

Context

• The behavior was first fixed in a DIFFERENT driver — reference PR: https://github.com/databricks/databricks-sql-kernel/pull/234 — which seeded the shared language-neutral spec. This issue tracks the same conformance gap in databricks/databricks-sql-nodejs; the reference PR is for cross-referencing the intended behavior, NOT a change to this repo.
• Coverage PR carrying the reproducing xfail test(s): https://github.com/databricks/databricks-driver-test/pull/1224