Skip to content

Fix to start the NGINX plus scraper #1072

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

Merged
merged 2 commits into from
May 1, 2025
Merged

Fix to start the NGINX plus scraper #1072

merged 2 commits into from
May 1, 2025

Conversation

dhurley
Copy link
Collaborator

@dhurley dhurley commented Apr 30, 2025

Proposed changes

Fix to start the NGINX plus scraper.

Checklist

Before creating a PR, run through this checklist and mark each as complete.

  • I have read the CONTRIBUTING document
  • I have run make install-tools and have attached any dependency changes to this pull request
  • If applicable, I have added tests that prove my fix is effective or that my feature works
  • If applicable, I have checked that any relevant tests pass after adding my changes
  • If applicable, I have updated any relevant documentation (README.md)
  • If applicable, I have tested my cross-platform changes on Ubuntu 22, Redhat 8, SUSE 15 and FreeBSD 13

@dhurley dhurley added the v3.x Issues and Pull Requests related to the major version v3 label Apr 30, 2025
@dhurley dhurley self-assigned this Apr 30, 2025
@dhurley dhurley requested a review from a team as a code owner April 30, 2025 15:46
@github-actions github-actions bot added bug Something isn't working chore Pull requests for routine tasks labels Apr 30, 2025
@dhurley dhurley merged commit 8bfaf2c into v3 May 1, 2025
20 checks passed
@dhurley dhurley deleted the fix-plus-scraper branch May 1, 2025 14:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working chore Pull requests for routine tasks v3.x Issues and Pull Requests related to the major version v3
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants