Skip to content
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

fix source report artifact error #31

Merged
merged 4 commits into from
Nov 17, 2016

Conversation

malaskowski
Copy link
Contributor

Fixed error at report on source comparison report:

/report/assets/libs/angular/angular.js:13550 SyntaxError: Unexpected token < in JSON at position 0
    at JSON.parse (<anonymous>)
    at fromJson (/report/assets/libs/angular/angular.js:1321)
    at defaultHttpResponseTransform (/report/assets/libs/angular/angular.js:10393)
    at /report/assets/libs/angular/angular.js:10484
    at forEach (/report/assets/libs/angular/angular.js:322)
    at transformData (/report/assets/libs/angular/angular.js:10483)
    at transformResponse (/report/assets/libs/angular/angular.js:11278)
    at processQueue (/report/assets/libs/angular/angular.js:15961)
    at /report/assets/libs/angular/angular.js:15977
    at Scope.$eval (/report/assets/libs/angular/angular.js:17229)(anonymous function) @ /report/assets/libs/angular/angular.js:13550
artifacts.service.js:62 Failed to load artifact! Object SyntaxError: Unexpected token < in JSON at position 0(…)handleFailed @ artifacts.service.js:62

The reason is invalid content type of source artifact (which was set to application/json - fixed also).
It is also not necessary downloaded which was also fixed.


I hereby agree to the terms of the AET Contributor License Agreement.

@malaskowski malaskowski self-assigned this Nov 17, 2016
@wiiitek
Copy link
Contributor

wiiitek commented Nov 17, 2016


I hereby agree to the terms of the AET Contributor License Agreement.

@wiiitek wiiitek merged commit f1a3b06 into release/2.0.1 Nov 17, 2016
@wiiitek wiiitek deleted the bugfix/source-report-artifact-error branch November 17, 2016 22:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants