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

[BUG]: my first example piece (Gelato) fails to run (followed docs) #4323

Closed
ahmad-swanblocks opened this issue Apr 1, 2024 · 6 comments
Closed

Comments

@ahmad-swanblocks
Copy link

I am trying to create Gelato piece following the documentation here: https://www.activepieces.com/docs/developers/building-pieces/create-action

Then I ran the app and when I create connection and click on save, it raises an error as below.
Any idea please?

Screenshot 2024-04-01 122518

Screenshot 2024-04-01 122519

@abuaboud
Copy link
Contributor

abuaboud commented Apr 1, 2024

Hi @ahmad-swanblocks

is gelato in your AP_PIECES_DEV environment variable?

@ahmad-swanblocks
Copy link
Author

ahmad-swanblocks commented Apr 1, 2024 via email

@ahmad-swanblocks
Copy link
Author

@abuaboud
I think most probably it is a cache issue as when looking at the logs while executing (validating) the connection, it generates cache files and then it looks for the modules in the cache (e.g. \dev\cache\sandbox\NONE-apId-2gQi7cJ0Nhm7H1tJaDRRS\node_modules@activepieces\pieces-framework") and does not find them and also the same for @activepieces\pieces-gelato

And when I go to this path, I found it empty.
Is there a way to skip the cache? or is it a known issue with known solution? Thanks!

@ahmad-swanblocks
Copy link
Author

ahmad-swanblocks commented Apr 2, 2024

@abuaboud
Update:
I've tried it in GitHub CodeSpaces and it works fine (after pulling the latest release), but when running the app locally or on dev containers it raises the error that I mentioned.

My local machine:
Windows 11 Pro
Node v18.20.0
npm 10.5.0

@abuaboud
Copy link
Contributor

Hi @ahmad-swanblocks

I think it's seems permission issue, can you please run it as admin, and that should fix it, or use dev container as they are reliable.

Closing this issue, please reopen If you still face the issue.

@abuaboud abuaboud closed this as not planned Won't fix, can't repro, duplicate, stale Apr 13, 2024
Copy link

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If this issue is continuing with the latest stable version of Activepieces, please open a new issue that references this one.

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

No branches or pull requests

2 participants