Closed prescottprue closed 3 years ago
@prescottprue thanks for the detailed bug! Assigning to @abeisgoat who does all things Firepit
@abeisgoat Let me know if there is anything else I can provide to help debug - would really love to get the binary working in actions
Hmm thanks for the report, I'll dig into it and see what's up. We've had bad luck with the CLI in actions for awhile, so I'll see
@abeisgoat Yup, np. Thanks for the update
Interesting to hear you have had other issues with cli in actions, I have not really had any issues even doing relatively complex stuff with it inline (loaded from npm bin since it is a dev dependency of our codebase), it is just when putting it into a custom js action that I have the above listed issue.
Ping
This should have been resolved awhile ago with a bunch of other installer fixes, please reopen if it still exists.
[REQUIRED] Environment info
firebase-tools: 8.4.3
Platform: Ubuntu
[REQUIRED] Test case
Downloading the firebase-tools binary as per the instructions in the docs and trying to call within a custom js Github Action:
Produces:
This tool has encountered an error. Please file a bug on Github (https://github.com/firebase/firebase-tools/) and include firepit-log.txt
[REQUIRED] Steps to reproduce
Use the above logic in a custom github action attempts to run the following command:
NOTE that
/home/runner/work/fireadmin/fireadmin
is theGITHUB_WORKSPACE
for a project named fireadmin (apologies for confusing name)This also happens when calling without the
--only
flag[REQUIRED] Expected behavior
I would expect that calling the binary works in all environments - this same logic works when running on my mac and downloading the binary from
https://firebase.tools/bin/macos/v8.4.3
.I also would expect to be able to get a debug log if passing
--debug
, but it seems like that logic is never being run since no debug logs trigger, and there is nofirebase-debug.log
file created[REQUIRED] Actual behavior
The only two places I saw split in firepit was