-
-
Notifications
You must be signed in to change notification settings - Fork 10.7k
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
tableau 2024.1.2 #172734
tableau 2024.1.2 #172734
Conversation
@miccal I think the CI IP is blocked. |
@Teko012 It isn't working locally for me either, so it's likely |
@bevanjkay You are right. It actually starts working if you set curl as a user agent, so I guess it's not curl that's blocked, but what brew uses by default as an agent 🤔 |
@bevanjkay Can you check the livecheck now? This actually works locally for me, but not on the CI. |
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.
livecheck's HeaderMatch
strategy will automatically handle the version in the location
header URL (https://www.tableau.com/support/releases/desktop/2024.1.2), so we can simply use strategy :header_match
without a regex or strategy
block. I've pushed a commit to update the livecheck
block accordingly.
That said, livecheck
doesn't support setting a different user agent yet (I have some in-progress work to enable this but some may not agree with the idea of setting a different user agent to work around upstream blocks). If the check works when the livecheck
block is executed locally but not on CI, upstream may be using some sort of system where a dubious IP in combination with a weird user agent may be cause for blocking (i.e., a weird IP or user agent alone may not be enough).
@samford Thanks for the change, this also works for me locally too. |
I found a feed here that might work? But it doesn't have version |
@bevanjkay Nice find, I think this would also get blocked though in the CI if we can't change the user agent which might get implemented by @samford. The current solution actually passes locally, so maybe just skipping the livecheck in the CI for now should solve it. |
@bevanjkay btw, it has |
I pushed another commit to update the |
If we merge this, it will also need to be removed from the |
If we can keep it working with a But, if we are going to remove this, we should remove all
|
|
Updated the other casks. If @samford's change gets implemented, the livecheck could be probably fixed too. |
@Teko012 I accidentally force-pushed this branch, because |
@bevanjkay No worries, I fixed it. Maybe we should merge it finally so it doesn't happen again ;) |
Thank you @Teko012. |
Important: Do not tick a checkbox if you haven’t performed its action. Honesty is indispensable for a smooth review process.
In the following questions
<cask>
is the token of the cask you're submitting.After making any changes to a cask, existing or new, verify:
brew audit --cask --online <cask>
is error-free.brew style --fix <cask>
reports no offenses.