Skip to content

/object/info is cached and the cache not busted after upserting #728

@psteinroe

Description

@psteinroe

Bug report

  • I confirm this is a bug with Supabase, not with my own application.
  • I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

It seems like the .info() request that calls /object/info is cached and not busted after an upsert on the same path.

I came across this when migrating the existence check in supabase cache helpers to use .exists() + .info() instead of .list() for performance reasons (pr with the fix psteinroe/supabase-cache-helpers#626)

If this is wanted, I would love some documentation on it.

Reproduce

  1. Upload file x
  2. call /info -> returns metadata for file x
  3. Upsert file x with file y
  4. call /info -> returns metadata for file x
  5. call /info?bust=true -> returns metadata for file y

Expected behavior

Should return metadata for file y after the upsert.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions