Skip to content
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

Sometimes builds fail due to an apparent filesystem permissions error #1704

Open
paxperscientiam opened this issue Mar 1, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@paxperscientiam
Copy link

paxperscientiam commented Mar 1, 2025

Hello again.

Describe the bug
At times, Game Boy Studio will fail to build a project due to an apparent write permission error.

For example:

Preparing variables... 
Preparing images... 
Preparing tilesets... 
Preparing ui... 
Preparing sprites... 
Preparing avatars... 
Preparing emotes... 
Preparing music... 
Preparing fonts... 
Preparing scenes... 
Preparation complete 
Compiling Events... 
Error: Could not write file /var/folders/mr/c4ql6d651hd110c02qgfsf0m0000gn/T/_gbstools/.vscode/Readme Emulicious debugging.txt: Error: ENOENT: no such file or directory, open '/var/folders/mr/c4ql6d651hd110c02qgfsf0m0000gn/T/.dev.gbstudio.gbstudio.toiP3i' 
Cancelled Build 

Warnings:
Error: Could not write file /var/folders/mr/c4ql6d651hd110c02qgfsf0m0000gn/T/_gbstools/.vscode/Readme Emulicious debugging.txt: Error: ENOENT: no such file or directory, open '/var/folders/mr/c4ql6d651hd110c02qgfsf0m0000gn/T/.dev.gbstudio.gbstudio.toiP3i' 

To Reproduce
I'm sorry. I don't know how to reproduce it. It may involve keeping GBS open for a while, but I don't know.

Expected behavior
I expect for builds to be able to continue without an apparent filesystem permission error.

Screenshots
At bottom.

Platform (please complete the following information):

  • OS: [macOS 15.3.1]
  • App version [4.1.3]

Additional context
I've tried nuking the build cache from the project directory and restarting the application, but that doesn't work. The only solution I've found is restarting my computer :/

Thank you.

Image

EDIT
I noticed a warning about this in the changelog. I see now that there's a builtin workaround in the settings.

EDIT 2
Seems the setting is ignored. Despite customizing the temp dir for the project, GBS still tries to write to $TMPDIR

Image

EDIT 3
A partial amendment to last edit. GBS actually did write something to <PROJECT_DIR>/tmp, though this isn't reflected in the build log.

Image
@paxperscientiam paxperscientiam added the bug Something isn't working label Mar 1, 2025
@paxperscientiam
Copy link
Author

Interesting development. There may be a connection with one of the other applications I had running alongside GBS.

While the above was happening, I had Steam, Aseprite (launched by steam), and Tiled running. After quitting those three and GBS, I started GBS again. I tried building and it worked both with the custom temporary directory and TMPDIR.

I may be close to figuring out how to reproduce this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant