Description
When a box goes idle after a period of inactivity, file access operations (files.list, files.read) fail immediately instead of automatically waking the box first.
This is a specific case of #110 — while that issue covers snapshots, this one is about basic file I/O on idle boxes.
Steps to reproduce
- Create a box and write files to it
- Wait for the box to become idle
- Call
box.files.list(path) or box.files.read(path)
Expected behavior
File operations should transparently wake the box before executing, so the caller doesn't need to handle idle state.
Actual behavior
files.list returns "Failed to list files" error. files.read similarly fails.
Current workaround
Running box.exec.command('pwd') before any file access to force a wake-up:
const box = await Box.get(id, { apiKey });
await box.exec.command('pwd'); // wake up idle box
const files = await box.files.list(path); // now works
Ideally the SDK should handle this internally so consumers don't need this workaround.
Description
When a box goes idle after a period of inactivity, file access operations (
files.list,files.read) fail immediately instead of automatically waking the box first.This is a specific case of #110 — while that issue covers snapshots, this one is about basic file I/O on idle boxes.
Steps to reproduce
box.files.list(path)orbox.files.read(path)Expected behavior
File operations should transparently wake the box before executing, so the caller doesn't need to handle idle state.
Actual behavior
files.listreturns"Failed to list files"error.files.readsimilarly fails.Current workaround
Running
box.exec.command('pwd')before any file access to force a wake-up:Ideally the SDK should handle this internally so consumers don't need this workaround.