12/19/2023 0 Comments Github actions doxygenissue 9399 XML / perlmod fortran output, the type of a parameter of function is set to the name of the parameter CMake Build for Doxygen 1923: Pull request 9400 opened by albert-github. I guess I could open an issue with the Doxygen developers, but the thing is that the Travis CI badge works fine in an tag, while the GitHub badge doesn’t. Coverity for doxygen Coverity for doxygen 170: Scheduled. It seems like previous versions of Doxygen used tags for SVG images instead of tags, and that didn’t cause any problems with the GitHub Actions badge (see older version of the same page here, generated with a previous version of Doxygen). If you look at the page source (CTRL+U), you can see that the HTML code is not actually empty: Build Statusĭoxygen automatically inserts the SVG image in an tag, which is not that uncommon, AFAIK. The reason for the empty html inside of the object tag is that the HTTP request failed. The HTML code is automatically generated by Doxygen. In the console, it shows the warning: “_Content Security Policy: Ignoring ‘x-frame-options’ because of ‘frame-ancestors’ directive”.Ĭontent-type : image/svg+xml charset=utf-8Įtag : W/“8c87d7f45bb5dc1a50a49df94105790a” An error occured during a connection to ” In Firefox, it shows an image saying: “Blocked by Content Security Policy. GET /tttapa/Control-Surface/workflows/CI%20Tests/badge.svg HTTP/1.1 Set-Cookie : logged_in=no Path=/ Domain= Expires=Sun, 23:08:02 GMT HttpOnly Secure Set-Cookie : _octo=XXX Path=/ Domain= Expires=Sun, 23:08:02 GMT Secure Set-Cookie : _gh_sess=XXX Path=/ HttpOnly Secure Strict-transport-security : max-age=31536000 includeSubdomains preloadĮxpect-ct : max-age=2592000, report-uri=“ ”Ĭontent-security-policy : default-src ‘none’ base-uri ‘self’ block-all-mixed-content connect-src ‘self’ github-cloud.s3. github-production-repository-file-5c1aeb.s3. github-production-upload-manifest-file-7fdce7.s3. github-production-user-asset-6210df.s3. wss:// font-src form-action ‘self’ frame-ancestors ‘none’ frame-src img-src ‘self’ data: github-cloud.s3. *. manifest-src ‘self’ media-src ‘none’ script-src style-src ‘unsafe-inline’ Vary : X-PJAX, Accept-Encoding, Accept, X-Requested-With In the console, it shows the error: “Refused to display ‘ ’ in a frame because an ancestor violates the following Content Security Policy directive: “frame-ancestors ‘none’””. The same README.md file is also used to generate the Doxygen homepage for the documentation on GitHub Pages, but since a couple of days or maybe weeks, the badge no longer shows up on the GitHub Pages homepage.Īny idea how this can be solved? Is this a deliberate choice of GitHub not to allow it? This works fine when viewing the README of the repository on GitHub. I added a GitHub Actions Badge to my README.md as per these instructions: ()]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |