-
Notifications
You must be signed in to change notification settings - Fork 194
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
Cache temporary redirections in the original location (#4459) #4547
Conversation
Test Results 606 files 606 suites 4h 11m 57s ⏱️ For more details on these failures, see this check. Results for commit 77b643c. ♻️ This comment has been updated with latest results. |
We get various other errors, but not this one :( Running locally I get these three:
|
This usually means something is messed up (e.g. redirection do not work anymore, mirrors not working runtime exception occurs and so on). The best way then is to run
this way you can debug one individual test. Sometimes it also helps to change the test to dump the output to a file, then compare the output of |
@laeubi this test was actually for an invalid repository mirror. The test is verifying the error message, which after my changes I get a different one (but still the same reason - the repository is invalid). So I would say the test still "passes" but we just now get a different error message. |
@kysmith-csg could you adjust the test then for the new message? |
58aba7c
to
77b643c
Compare
Never trust Github to update your fork... sorry for the noise. Updated the test message. |
@laeubi this test failure doesn't seem related to my change. Even your latest commit failed because of this :) |
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
Thank you @laeubi for handling this. Any chance of making a 4.0.11 release for this? It's currently impacting our organization and at least one other (the original author of the issue). We would greatly appreciate it. |
@kysmith-csg thanks for the fix and patience! In general it is always useful to use I think we have some important bugfixes already included so I will perform a release maybe next month but wanted to see some things settled, will this work for you? |
@laeubi I will try the snapshot build at some point and report back, thanks. |
@laeubi tested 4.0.11-SNAPSHOT (which I had to build locally because for some reason it wasn't using the snapshot repo) and confirmed it works. A jar file download (https://my-site.com/files/foo.jar) that was redirected to a long url (https://my-very-very-long-site.com/qwertyuiop/files/foo.jar) site was cached in the directory for the original location from target-platform ( Confirmed by checking the |
Some p2 sites can temporarily redirect to another location. In the case of JFrog Artifactory, these redirection URLs are too long to make as a file path, so the build would fail in this case. For temporary redirects, we save the artifact in the original location instead, since it's likely the redirection might change in the future. Permanent redirects will get their own cache entry as before.