Build fail when cache enabled

Open
#646 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
java

Research direction

No source file or test is named. Start by reproducing the Java extender cache sequence: enable LOCAL caching, build, delete /extender/cache/data/*, restart the macOS extender, and build again. Done means the subsequent build succeeds instead of reporting that the cached object was not found.

Written by the indexing model from the issue text.

Description

extender
Configuration:

extender-frontend (2.8.5) -> extender-macos (2.8.5)

extender-frontend:

extender:
      cache:
        enabled: true
        type: LOCAL
        local:
          basedir: "/extender/cache/data"
        file-size-threshold: 65536

extender-macos:

      cache:
        enabled: true
        type: LOCAL
        local:
          basedir: "/extender/cache/data"
        file-size-threshold: 65536
Problem

when extender macos cache is emptied after successful build, next build fail with following error

2025-01-29 17:14:56.847 ERROR [extender,5ae32a7dfb910214db0c791f356408d3,73134ef7f53fe0a9] 1846 --- [job11157173485277139441] com.defold.extender.Ex
tenderController   : Failed to build extension: Cache object defold-spine/commonsrc/spine/Animation.c (74d2f4691f24e636f1a2500397f78b2b57cafa70a57c2
068f71417ee113277ee) was not found
steps to reproduce:
  1. enable cache
  2. build ios app
  3. stop macos extender
  4. rm -rf /extender/cache/data/*
  5. start macos extender
  6. run build again
  7. got error
Dominant language
Java
Stars
67
Forks
25
Avg merge
1d 1h
Merged PRs (30d)
16

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from defold/extender

All issues in defold/extender

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.