super-linter: [FATAL] Failed to view version file:[/action/lib/functions/linterVersions.txt]
For last 2 days, I am getting the error
[FATAL] Failed to view version file:[/action/lib/functions/linterVersions.txt]
I am using flake8 for linting and there’s no lint errors locally. In super linter workflow log also, there’s no mention of bug error, but the above specified error. The setup was working before, so is it something related to the project or super-linter ? Is anybody else facing such issue?
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 15
- Comments: 27
Commits related to this issue
- Fixing Super Linter github.com/github/super-linter/issues/2255#issuecomment-1001683799 gybha mn hnaa lsa msh 3arif sha8ala wla la2 — committed to Mohabeldiin/test-scripts by Mohabeldiin 3 years ago
- Update super-linter version to avoid bug https://github.com/github/super-linter/issues/2255 — committed to Apreche/frontrowcrew by Apreche 3 years ago
- Update super-linter version to avoid bug https://github.com/github/super-linter/issues/2255 — committed to Apreche/frontrowcrew by Apreche 3 years ago
- All core models, views, and placeholder templates created and tested. (#53) * All core models, views, and placeholder templates created and tested. * Fix linting to ignore generated file(s) and Dj... — committed to Apreche/frontrowcrew by Apreche 3 years ago
- Fix Github Actions Superlinter CI/CD job Workaround https://github.com/github/super-linter/issues/2255 — committed to laurynas-biveinis/unodb by laurynas-biveinis 2 years ago
- Update main.yml ivm https://github.com/github/super-linter/issues/2255 — committed to geensnor/DigitaleTuin by reithose 2 years ago
- Update main.yml ivm https://github.com/github/super-linter/issues/2255 — committed to geensnor/DigitaleTuin by reithose 2 years ago
- Baby versie 0.1 (#28) * eerste versie * Update baby.md * Update baby.md * Update baby.md * Update baby.md * Update baby.md * Update baby.md * Update baby.md * Update baby.md ... — committed to geensnor/DigitaleTuin by Zuijdam 2 years ago
- Changed super-linter to use v3.17.0 See https://github.com/github/super-linter/issues/2255 for a workaround. for workaround, use uses: github/super-linter@v3.17.0 this issue is because of the hotp... — committed to oslc-op/oslc-specs by jamsden 2 years ago
- fix(github-actions): outdated linter, ref https://github.com/github/super-linter/issues/2255 — committed to signcl/git-auto-commit-action by sparanoid 2 years ago
- Fix linter issue (#18) https://github.com/github/super-linter/issues/2255 — committed to tracetronic/jenkins-library by MartinGroscheTT 2 years ago
- workaround https://github.com/github/super-linter/issues/2255 — committed to chicks-net/aws-iam-rotate by chicks-net 2 years ago
- Fix Linter https://github.com/github/super-linter/issues/2255 — committed to joshcorr/SecretManagement.Hashicorp.Vault.KV by joshcorr 2 years ago
- ci: Fix Github Actions Super Linter https://github.com/github/super-linter/issues/2255#issuecomment-1001683799 — committed to sugarlabs/musicblocks-v4 by meganindya 2 years ago
- lint: Fix Github Actions Super Linter https://github.com/github/super-linter/issues/2255#issuecomment-1001683799 — committed to sugarlabs/musicblocks-v4 by meganindya 2 years ago
- Update linter.yml fix bug, see https://github.com/github/super-linter/issues/2255 — committed to MarcProe/Papierkorb.js-Classic by MarcProe 2 years ago
- Update to newest Dataproc client library version * Switch to v1 API, as v1beta2 API is deprecated. All new features should be released in the v1 API going forward * Update handler test to account f... — committed to GoogleCloudDataproc/jupyterhub-dataprocspawner by deleted user 2 years ago
- Update to newest Dataproc client library version (#74) * Update to newest Dataproc client library version * Switch to v1 API, as v1beta2 API is deprecated. All new features should be released i... — committed to GoogleCloudDataproc/jupyterhub-dataprocspawner by JerryLeiDing 2 years ago
- Issue with current v3 won't be fixed. So upgrade https://github.com/github/super-linter/issues/2255 `[FATAL] Failed to view version file:[/action/lib/functions/linterVersions.txt]` won't be fixed so... — committed to deanwilson/unixdaemon-fpm-cookery-recipes by deanwilson 2 years ago
- Switch to Super-Linter v4 Switching because this bug will not be fixed in v3: https://github.com/github/super-linter/issues/2255 The v4 branch claims to be fully compatible with v3 setups — committed to zeusops/operationbot by Gehock 2 years ago
use
uses: github/super-linter@v3.17.0works, thanksHey all, this issue is because of the hotpatch push of a critical bug fix in 3.x. This will not be fixed and the solution is to move to the 4.x release cycle.
thank you and sorry for any issues this may have caused
Thanks, v4 works for me
This works!
we encountered the same issue
Same worked for me as well. I replaced @v3 with @v3.17.0 and it worked.
Thank You. Changing the @v3 to this @v3.17.0 made it work. Cheers
uses: github/super-linter@v3.17.0Thanks…worked for me too 👍Thank you!
I tried
uses: github/super-linter@v4it works but it caused following failuresit means it is not a simple change to v4
Hey all, the v4 change did introduce a few other small changes but I would assume most users would not hit those small edge cases. v4 allowed for the slim image and some better coding ideas. So please come on over 😃
use
3.17.0should be a temp workaroundWorkaround
https://circleci.com/developer/orbs/orb/circleci/github-super-linter
The default is v3 - so I rolled back to a previous v3 version - pick one here: https://hub.docker.com/r/github/super-linter/tags?page=1&name=v3
Hello,
We are also facing same issue. Please help to resolve the issue.