SHA hash and moment not defined errors (participant analytics and contact pages)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12
- Forks
- 21
- Avg merge
- 5d 19h
- Merged PRs (30d)
- 5
Description
On the `develop` branch, there are console errors on the participant analytics (`/exp/studies/analytics`) and participant contact (`exp/studies//contact`) pages saying that
1. None of the “sha512” hashes in the integrity attribute match the content of the subresource.
2. Uncaught ReferenceError: moment is not defined.
Local develop branch:
Staging:
The production site does not show these errors. Although it does show the same warning about failing to load the gtag file that occurs on staging.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the console errors on /exp/studies/analytics and /exp/studies//contact using the develop branch, then inspect the page resources and their integrity attributes. Done means the reported sha512 mismatch and “moment is not defined” errors no longer occur on those pages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100