Fix autocheck usage in Examples.pod to prevent premature death #404
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes rt.cpan.org #76714
Problem
Two examples in
WWW::Mechanize::Examples.podwere creatingWWW::Mechanizeobjects without explicitly settingautocheck => 0, then attempting to check$mech->successfor success/failure. Sinceautocheckis enabled by default in standaloneWWW::Mechanizeinstances, these examples would die immediately on failed requests and never reach the success check, making the manual check pointless.Changes
Fixed two examples that had this issue:
1. pb-upload example
2. quotes.pl example
Verification
All other examples in the file were reviewed and found to be correctly written:
autocheck => 1are already correct$response->is_successon HTTP::Response objects (not Mechanize objects) are correctPOD syntax validated with
Pod::Simple::Checker.Original prompt
Fixes #83
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.