Segfault on array_fragments call

[kylemann16]

Description

On linux/amd64 architecture, tiledb is failing to access array fragments and handle array creation errors:

• Accessing an array's fragments via tiledb.array_fragments(tdb_dir) leads to a signal 6 abort.
• Attempting to create an array that has already been created leads to a signal 11 segfault

Expected Results

• Correctly access array fragments
• Output an error message without a segfault when I attempt to create an array that already exists

I assume these errors are coming from the base TileDB library, but I'm interacting with them through Python so I'm posting it here. I can move it over to that repo if necessary though!

Reproduction scripts, logs, and environment versions can be found here:
https://gist.github.com/kylemann16/1e4848c48ba81c8fcaa2efb3f0d5fe27

[ihnorton]

Thanks @kylemann16, we'll take a look. I can reproduce this, but it appears to be linux-specific.

---

sc-39124

[ihnorton]

AFAICT this was caused by conda-forge/tiledb-feedstock#228 and is now mitigated via pinning; we'll do our best to get a full fix in ASAP, depending on whether the cause is under our control.

[ihnorton]

• upstream discussion: azure-core-cpp version 1.11.0 introduced a binary breaking change. Azure/azure-sdk-for-cpp#5322 -- there are a number of x-refs there to pinning updates to ensure that (apparently-necessary) rebuilds happen to prevent this in the future.
• further mitigation in tiledb: Lazily initialize the Azure SDK client. TileDB#4703

[ihnorton]

Closing, please let me know if we need to reopen.