Skip to content

Missing library for Azure in Duck CLI #17012

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
turekbar opened this issue Apr 3, 2025 · 2 comments · Fixed by #17027
Closed

Missing library for Azure in Duck CLI #17012

turekbar opened this issue Apr 3, 2025 · 2 comments · Fixed by #17027
Assignees
Labels
azure Azure Protocol Implementation bug cli Command Line Interface windows
Milestone

Comments

@turekbar
Copy link

turekbar commented Apr 3, 2025

Describe the bug
Duck CLI is unable to connect to Azure Blob Storage

missing‐library problem when the Azure code attempts to load its XML parser (Woodstox).

• “Provider ch.cyberduck.core.azure.AzureProtocol not found”
• “javax.xml.stream.FactoryConfigurationError: Provider for class javax.xml.stream.XMLOutputFactory cannot be created”
• “Provider com.ctc.wstx.stax.WstxOutputFactory not found”

To Reproduce
Steps to reproduce the behavior:

  1. Install recent duck cli using msi or exe
  2. Try to list/upload anything to Azure Blob storage
  3. example of syntax: duck --username kahy9boj3eib --list azure://kahy9boj3eib.blob.core.windows.net/ (Use --debug for detals about error)
  4. confirm username, enter Azure Access keys, confirm saving credentials
  5. Error occurs: "Fatal error null" (version 9.1.2), "Unknown." in (version 9.1.3)

Expected behavior

Exact same command works from ubuntu. Tested on two Windows 10 machines, both have the same error. CyberDuck Gui works as expected.

Desktop:

  • OS: Windows 10

Image

@dkocher dkocher added bug cli Command Line Interface azure Azure Protocol Implementation windows labels Apr 3, 2025
@dkocher dkocher added this to the 9.1.4 milestone Apr 9, 2025
@AliveDevil
Copy link
Contributor

Duplicate woodstox Jar in Cli and Protocols-DLL, thus class service loader tries to find it in Cli (alphabetically before Protocols), doesn't find the class in Cli, and fails.

@dkocher
Copy link
Contributor

dkocher commented Apr 9, 2025

Regression from #16566.

dkocher added a commit that referenced this issue Apr 10, 2025
Remove artifacts merged into Cli-Dll, to reduce interference with ServiceLoader
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
azure Azure Protocol Implementation bug cli Command Line Interface windows
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants