-
-
Notifications
You must be signed in to change notification settings - Fork 10.9k
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
adobe-dng-converter 16.3 #175619
adobe-dng-converter 16.3 #175619
Conversation
Trying to revert to a previous |
9ca950d
to
0c2c816
Compare
This seems to be working but is failing the Any ideas here @samford? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tinkering around in Utils::Curl
, it looks like the dng_converter_mac
URL needs both a different user agent (e.g., :browser
) and to use a GET
request for the server to return a response with the dmg in the location
header. All the other combinations return a curl: (92) HTTP/2 stream 1 was not closed cleanly: INTERNAL_ERROR (err 2)
error and the dmg isn't in the headers.
It would technically work if we added 92 to the existing special-cased exit statuses that we retry with GET
in #curl_headers
but there would be three failing requests before the one that works (i.e., default user agent + HEAD
, default user agent + GET
, :browser
user agent + HEAD
, then finally :browser
user agent + GET
), which isn't great. This seems to be unique to the adobe checks at the moment and I'm not sure that this exit status is one that makes sense to special case, so checking a different source for now (until we can manually set it to use a different user agent and GET
in the livecheck
block in the future) makes sense.
It took some digging but #audit_livecheck_https_availability
fails for the uptodate.html
URL because it doesn't work with our default user agent and needs :browser
to work. It works in livecheck because #page_content
automatically retries with the :browser
user agent but the audit fails because it only tries with the :default
user agent.
A simple solution is to pass user_agents: [:default, :browser]
to #validate_url_for_https_availability
in #audit_livecheck_https_availability
, to align the audit with livecheck's behavior. I'll just have to remember to remove it if/when I remove the automatic user agent retry logic in livecheck once we can specify a user agent in a livecheck
block (I have a working implementation but I haven't had the brainpower/energy lately to wrap it up, as the PR will likely involve a lot of review/discussion).
Anyway, I'll create a brew PR for the audit change (maybe this evening) and this will be able to move forward if/when it's merged. In the interim time, I'll push a commit here to tweak this regex a bit.
Of course all good to push here. For the regex, I had simply just reverted to an older |
0c2c816
to
165a115
Compare
I finally got around to creating a brew PR with a fix (Homebrew/brew#17512) but there's some discussion in a brew issue (Homebrew/brew#15350) around whether we should be switching user agents at all, so it may or may not move forward. |
/rebase |
This loosens the `livecheck` block regex a bit, to hopefully lower the chance of it failing to match due to text/markup changes in the HTML.
165a115
to
f64c7d1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The brew fix has been merged, so the livecheck audit works as expected and this passes CI now. Thanks for pointing this out, @bevanjkay.
Created with
brew bump-cask-pr
.