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

Make rqstats -y fail when PyYAML is not installed #660

Merged
merged 1 commit into from
May 1, 2024
Merged

Make rqstats -y fail when PyYAML is not installed #660

merged 1 commit into from
May 1, 2024

Conversation

SpecLad
Copy link
Contributor

@SpecLad SpecLad commented Apr 13, 2024

Currently, when PyYAML is not installed, rqstats -y prints an error message, but it still exits with a 0 exit code, indicating success. Fix that, along with a few related issues:

  • The error message was printed to stdout rather than stderr.

  • The name of the library in the message was incorrect (LibYAML is a C library; the Python library is PyYAML).

After this change, you need to install PyYAML to run the testsuite, so modify the GitHub workflow accordingly. Also, make sure to install all packages at once, to make sure that later install commands don't overwrite the result of the earlier ones.

Currently, when PyYAML is not installed, `rqstats -y` prints an error
message, but it still exits with a 0 exit code, indicating success. Fix
that, along with a few related issues:

* The error message was printed to stdout rather than stderr.

* The name of the library in the message was incorrect (LibYAML is a C
  library; the Python library is PyYAML).

After this change, you need to install PyYAML to run the testsuite, so
modify the GitHub workflow accordingly. Also, make sure to install all
packages at once, to make sure that later install commands don't overwrite
the result of the earlier ones.
@selwin selwin merged commit 87dd8cf into rq:master May 1, 2024
15 checks passed
@selwin
Copy link
Collaborator

selwin commented May 1, 2024

Thanks!

alaouimehdi1995 pushed a commit to alaouimehdi1995/django-rq that referenced this pull request Sep 3, 2024
Currently, when PyYAML is not installed, `rqstats -y` prints an error
message, but it still exits with a 0 exit code, indicating success. Fix
that, along with a few related issues:

* The error message was printed to stdout rather than stderr.

* The name of the library in the message was incorrect (LibYAML is a C
  library; the Python library is PyYAML).

After this change, you need to install PyYAML to run the testsuite, so
modify the GitHub workflow accordingly. Also, make sure to install all
packages at once, to make sure that later install commands don't overwrite
the result of the earlier ones.
alaouimehdi1995 pushed a commit to alaouimehdi1995/django-rq that referenced this pull request Sep 3, 2024
Currently, when PyYAML is not installed, `rqstats -y` prints an error
message, but it still exits with a 0 exit code, indicating success. Fix
that, along with a few related issues:

* The error message was printed to stdout rather than stderr.

* The name of the library in the message was incorrect (LibYAML is a C
  library; the Python library is PyYAML).

After this change, you need to install PyYAML to run the testsuite, so
modify the GitHub workflow accordingly. Also, make sure to install all
packages at once, to make sure that later install commands don't overwrite
the result of the earlier ones.
alaouimehdi1995 pushed a commit to alaouimehdi1995/django-rq that referenced this pull request Sep 3, 2024
Currently, when PyYAML is not installed, `rqstats -y` prints an error
message, but it still exits with a 0 exit code, indicating success. Fix
that, along with a few related issues:

* The error message was printed to stdout rather than stderr.

* The name of the library in the message was incorrect (LibYAML is a C
  library; the Python library is PyYAML).

After this change, you need to install PyYAML to run the testsuite, so
modify the GitHub workflow accordingly. Also, make sure to install all
packages at once, to make sure that later install commands don't overwrite
the result of the earlier ones.
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 this pull request may close these issues.

2 participants