GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — `options` map modified directly · Issue #383 · cloudinary/cloudinary_java

options map modified directly #383

New issue
Copy link
New issue
Copy link
Open
Open
options map modified directly#383
Copy link
Assignees
adimiz1

Description

@janosmeszaros
janosmeszaros
opened on Jul 17, 2025
Issue body actions

Describe the bug in a sentence or two.

When passing in an immutable map to Uploader.uploadLarge it errors out because the method tries to update the same instance that was passed in to it.
AFAICS, in most places a defensive copy is made from the options map, but not here. It caused issues for us as we are using the lib from Clojure interop, and by default, all the collections there are immutable.

Issue Type (Can be multiple)

[ ] Build - Can’t install or import the SDK
[ ] Performance - Performance issues
[x] Behaviour - Functions aren’t working as expected (Such as generate URL)
[ ] Documentation - Inconsistency between the docs and behaviour
[ ] Other (Specify)

Steps to reproduce

Use an immutable map as options for Uploader.uploadLarge when file is a java.util.File.

Versions and Libraries (fill in the version numbers)

Cloudinary Java SDK version - 1.39.0

Reacted by adimiz1

Activity

  1. tommyg-cld commented on Jul 21, 2025

    @tommyg-cld
    tommyg-cld
    on Jul 21, 2025
    More actions

    @janosmeszaros you are using quite an old version, can you please upgrade to the latest version (2.3.0) and let me know if the issue persists there?

  2. janosmeszaros commented on Jul 21, 2025

    @janosmeszaros
    janosmeszaros
    on Jul 21, 2025
    Author
    More actions

    @tommyg-cld thanks for your reply.
    Let me try that, sure. But because the code path what causes the problem (see the link in the description) still exists on the master branch I'm pretty sure it's an issue on the latest version too.

  3. tommyg-cld
    assigned
    tommyg-cld
    and
    adimiz1
    and unassigned
    tommyg-cld
    on Jul 21, 2025
  4. tommyg-cld commented on Jul 24, 2025

    @tommyg-cld
    tommyg-cld
    on Jul 24, 2025
    More actions

    @janosmeszaros we've opened an internal bug for this so will keep you posted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

  • @adimiz1
    adimiz1

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    You are visitor 01402520 — GeezerVison does not store the pages you look up.
    Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.