Skip to content
This repository has been archived by the owner on Jan 14, 2021. It is now read-only.

"Sources" link on https://apps.fedoraproject.org/packages/cups/overview/ yields an "Oops! Something Went Wrong" if JavaScript is blacklisted #141

Closed
shlomif opened this issue Mar 29, 2015 · 2 comments
Closed

"Sources" link on https://apps.fedoraproject.org/packages/cups/overview/ yields an "Oops! Something Went Wrong" if JavaScript is blacklisted #141

shlomif opened this issue Mar 29, 2015 · 2 comments

Comments

@shlomif
Copy link

shlomif commented Mar 29, 2015

Hi all,

if I go to https://apps.fedoraproject.org/packages/cups/overview/ with Firefox with the NoScript extension ( https://noscript.net/ ) installed and set to blacklist JavaScript from all domains by default (with the ability to whitelist it), then if I click on the "Sources" link, then I get an "Oops! Something Went Wrong" / Radioactive Panda / 500 code error instead of something more meaningful. Please look into making it more user-friendly.

Otherwise, I should note that going to https://apps.fedoraproject.org/packages/cups/overview/ takes a very long time to load - in both Firefox with NoScript and in Google Chromium without it. I'm located in Tel Aviv, Israel and use Bezeq International as my ISP (ADSL).

Best regards,

-- Shlomi Fish
@pypingou
Copy link
Member

The Sources tab of cups does not work at all for me and firebug shows:
"NetworkError: 500 Internal Server Error - https://apps.fedoraproject.org/packages/_w/package_sources?subpackage_of=&package_name=cups"
Which explains the 500 error code you're seeing, noscript is for nothing in there, there is most likely a problem.

Loading the overview page is also taking a while here.

@shlomif
Copy link
Author

shlomif commented Mar 29, 2015

@pypingou : hi! Thanks for the insights in your comment.

ralphbean added a commit that referenced this issue Nov 20, 2015
@ralphbean
Fix git scraping.
6d9dd0d 
The issue was that it was always looking for the third line of the log..
but if the latest commit was a *merge* commit, then you need to look on
the fourth line.

This approach considers only the 'Date:' lines, of which we just take
the first.

Fixes #141.
@ralphbean ralphbean mentioned this issue Nov 20, 2015
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@shlomif @pypingou