You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently I made a mistake in renaming the file passed to package-file input: file was renamed to A but package-file accepted another name B (muzimuzhi/tabularray-dev@3ab03da).
Consequently the setup-texlive-action was used with no packages. Due to the existence of cache(s), the job still passed thus my mistake was not uncovered until I checked out the details of job log today.
▼ Run teatimeguest/setup-texlive-action@v3
with:
package-file: .github/tl_package
update-all-packages: true
cache: true
tlcontrib: false
Looking for `package-file`...
No file matched the pattern `package-file`
No packages found
▶ Restoring cache
▶ Updating packages
▶ TeX Live environment details
To catch the problem earlier. Maybe the message "No file matched the pattern package-file" can be raised to warning, and "No packages found" be raised to even error.
The text was updated successfully, but these errors were encountered:
Since the package-file input accepts glob patterns, it is less obvious whether it should be a failure if no match was found, even if there are no special globbing characters. A warning may be acceptable to find potential mistakes, but treating it as an error seems too strict to me.
As a more general approach, it might be possible to have an option like fail-fast to cause the action to fail instead of any warning.
A warning may be acceptable to find potential mistakes, but treating it as an error seems too strict to me.
Agreed.
After reconsideration, it's valid use even when both pacakge-file and packages are not specified or match nothing, so the suggested warning or error can only be achieved by introduction of new inputs or environment variables.
Recently I made a mistake in renaming the file passed to
package-file
input: file was renamed to A butpackage-file
accepted another name B (muzimuzhi/tabularray-dev@3ab03da).Consequently the
setup-texlive-action
was used with no packages. Due to the existence of cache(s), the job still passed thus my mistake was not uncovered until I checked out the details of job log today.To catch the problem earlier. Maybe the message "No file matched the pattern
package-file
" can be raised to warning, and "No packages found" be raised to even error.The text was updated successfully, but these errors were encountered: