You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This was after trying something to address this error:
None of the “sha512” hashes in the integrity attribute match the content of the subresource.
(I reverted but) Why am I seeing errors about sha512 hash? I'm sure this is a really interesting part of web technology but why is Ember build giving me issues here?
In Chrome, it throws a bunch of console errors about broken links to asset files. Yes, I suspect I can address this problem by... what is it? Update rootURL? Add the prepend property to fingerprints in ember-cli-build?
Is there an implicit step that's missing from the README that we should add to avoid this? Sometimes I just want to push up a prototype of something to GH pages, but somehow I end up missing some hidden step. I just cannot see where I am failing to follow the instructions. This is not an org page or a user page (which I assume means the page that appears when you go to the user root page).
Please advise and I will be happy to PR an extra note to the README which I believe followed faithfully, thanks.
The text was updated successfully, but these errors were encountered:
I spun up an ember app today, I want to push it to GH pages, however, in Firefox, it redirects to the same route:
https://allthesignals.github.io/labs-upad-validate/labs-upad-validate/ (<- WHAT?!?!?!)
This was after trying something to address this error:
(I reverted but) Why am I seeing errors about sha512 hash? I'm sure this is a really interesting part of web technology but why is Ember build giving me issues here?
In Chrome, it throws a bunch of console errors about broken links to asset files. Yes, I suspect I can address this problem by... what is it? Update rootURL? Add the prepend property to
fingerprints
in ember-cli-build?Here's my repo now: https://github.com/allthesignals/labs-upad-validate.
Is there an implicit step that's missing from the README that we should add to avoid this? Sometimes I just want to push up a prototype of something to GH pages, but somehow I end up missing some hidden step. I just cannot see where I am failing to follow the instructions. This is not an org page or a user page (which I assume means the page that appears when you go to the user root page).
Please advise and I will be happy to PR an extra note to the README which I believe followed faithfully, thanks.
The text was updated successfully, but these errors were encountered: