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

fs undefined reading createWriteStream #22

Closed
anibe opened this issue Apr 14, 2022 · 9 comments · Fixed by #23
Closed

fs undefined reading createWriteStream #22

anibe opened this issue Apr 14, 2022 · 9 comments · Fixed by #23

Comments

@anibe
Copy link

anibe commented Apr 14, 2022

Hello,

We recently noticed our builds failing the FOSSA scan due to the error below:

Run fossas/fossa-action@main
Error: There was an error fetching FOSSA CLI. TypeError: Cannot read properties of undefined (reading 'createWriteStream')

It appears to have been introduced with v1.2.0.

Could you please consider offering backward compatibility for build agents that don't support the new Node.js syntax?

Details of our GitHub Action runner below:
Operating System:
Ubuntu

LTS
Virtual Environment:
Environment: ubuntu-20.04
Version: 20220410.2

@DavidGoodwin
Copy link

(Same here)

@rayanht
Copy link

rayanht commented Apr 15, 2022

Same here,

As a temporary workaround, you can pin the FOSSA action version like this:

      - name: "Run FOSSA Test"
        uses: fossas/fossa-action@v1.1.0
        with:
          api-key: ${{ secrets.FOSSA_API_KEY }}
          run-tests: true

@shubham1172
Copy link
Contributor

Please check the attached PR. It is working with the change suggested by @anibe. Hope to get it in soon!

@himynameisdave
Copy link
Contributor

Thanks for reporting this! Just testing that PR now.

@tobysmith568
Copy link

tobysmith568 commented Apr 20, 2022

Unless I've missed something, I'm still getting this when targeting v1.3.0 on the GitHub ubuntu-latest agents and node.js 16.

@shubham1172
Copy link
Contributor

@tobysmith568 can you please share the pipeline run link?

@shubham1172
Copy link
Contributor

shubham1172 commented Apr 21, 2022

Actually you are right, I just checked. The tag v1.3.0 does not contain the commit
image

The release v1.3.0 is behind main by 1 commit:
image

@himynameisdave can you please recreate the release/tag with the right commit?

@paulmowat
Copy link

Also getting this on v1.3.0

image

@tobysmith568
Copy link

Thanks guys - 1.3.1 has now resolved this issue for me 🚀

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

Successfully merging a pull request may close this issue.

7 participants