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

unusable error from puter.fs.write() #793

Open
1 of 4 tasks
ProgrammerIn-wonderland opened this issue Oct 9, 2024 · 2 comments
Open
1 of 4 tasks

unusable error from puter.fs.write() #793

ProgrammerIn-wonderland opened this issue Oct 9, 2024 · 2 comments

Comments

@ProgrammerIn-wonderland
Copy link
Contributor

Issue Description
image
image

Steps to Reproduce
write data incorrectly
Expected & Actual Behavior
error would return an object with a .code field

instead it returns a string with Error: [object Object]
Addition Information or Screenshots (if applicable)

Deployment

  • Production (puter.com)
  • Development (npm run start)
  • Docker (via docker run)
  • Docker (via docker-compose)

Puter version (if accessible)

Click the profile button on the top-right, then "Settings". The version number will be printed at the bottom
master

@ProgrammerIn-wonderland
Copy link
Contributor Author

ProgrammerIn-wonderland commented Oct 9, 2024

issue was being in an iframe and the blob being the iframe's Blob() and not the parents blob. Since i was doing window.parent.puter.fs.write(), and instance types aren't carried over the frame boundary, this fails

That isn't a bug with puter, what I was doing was totally unexpected and not normal behavior, what is, is the error reported not giving context

@KernelDeimos
Copy link
Contributor

I created an internal issue to track this. The first step to debug this is to determine whether this is happening in puter.js or backend.

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

No branches or pull requests

2 participants