giseldo/neodataset huggingface dataset:
Tags and verify email modal overlap on signup

<!---
Please read this!

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate.
--->

### Summary

Modals overlap on signup, order is not fixed

### Steps to reproduce

Signup with verify codes enabled

### Platform information 

Web

### What is the current *bug* behavior?

Modals overlap

### What is the expected *correct* behavior?

- Given the user has completed the initial signup screen,
- when the user is redirected to the Newsfeed,
- then the email verification modal appears.

and

- Given the email verification modal appears,
- when the user completes the verification modal and the modal closes,
- then the tag selection modal appears.

### Relevant logs and/or screenshots

![image](/uploads/ef0e0a9fd862151f62cc074a4a11fa6e/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 3.0
Button to force staging cookie for admins

<!---
Please read this!

The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate.
--->

## Goal

We should add a utility to the admin panel that allows admins to easily set staging cookies - it's happened a few times where the cookie is incorrectly set because of things like path or exp time.

The benefit of this is that admins testing with the staging cookie is our final safety net before things go out into production - if admins are misconfigured, issues can hit prod and can and have caused superhero events that were entirely avoidable.

## What needs to be done

- Create a new page such as `devtools`
- Simple radio buttons with the environment on you wish to select

## QA

Test staging cookie was set or removed based on selected radio

## UX/Design

Probably not needed too in depth but a general "we should put this here" would be good.

## Personas

Admins

## Experiments

N/A

## Acceptance Criteria

- [ ] Create a new page such as `devtools`
- [ ] Simple radio buttons with the environment on you wish to select
- [ ] Playright tests

## Definition of Ready Checklist

- [x] Definition Of Done (DoD)
- [x] Acceptance criteria
- [ ] Weighted
- [x] QA
- [ ] UX/Design
- [x] Personas
- [x] Experiments

Story points: 3.0
Move festival banner dismissal to local storage

<!---
Please read this!

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate.
--->

### Summary

Festival banner dismissal should be in local storage so that it persists across tags, rather than sessionStorage, which is for page sessions, not user sessions.

### Steps to reproduce

1. Dismiss banner
2. Load a new tab, see banner

### Platform information 

Web

### What is the current *bug* behavior?

Banner shows when you open a new tab

### What is the expected *correct* behavior?

Banned should be in local storage

### Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 1.0
Third party video embeds require pressing play twice

<!---
Please read this!

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate.
--->

### Summary

When viewing an activity post with an embedded third party video (e.g. YouTube, Rumble, Odysee), the user needs to click a play button twice before the video will begin playing.

### Steps to reproduce

- Load the mobile web Minds app on a phone
- View an activity post with an embedded YouTube video
- Click the play button

### Platform information 

- Android + Brave (?)
- iPhone + Chrome

### What is the current *bug* behavior?

- The video thumbnail + play button is replaced with a video embed
- The video embed does NOT begin playing automatically

### What is the expected *correct* behavior?

- The video thumbnail + play button is replaced with a video embed
- The video embed DOES begin playing automatically

### Relevant logs and/or screenshots

[Video recording in this comment](https://gitlab.com/minds/front/-/issues/5585#note_1011070489).

### Possible fixes

YouTube embed code allows for specifying an autoplay state.

Possibly other video services do as well.

----

Note that even if using the autoplay parameter, it's possible the YouTube video will not autoplay because of browser autoplay media permissions. [More info here](https://developer.mozilla.org/en-US/docs/Web/Media/Autoplay_guide).

Story points: 1.0
Event advertisement banner not staying dismissed on refresh

<!---
Please read this!

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate.
--->

### Summary

I've had a handful of users complain about the event advertisement banner:

![image](/uploads/60eee04c9c42cbd46ce1eec7d48cc44d/image.png)

![image](/uploads/bdd8fc430d2d8c543dfe5425cb71fba6/image.png)

![image](/uploads/f48d2df6bd311e83f4db505cc567a39c/image.png)

![image](/uploads/e993a2a7fad6ecec0b78dab5148eea5d/image.png)

It appears as if this is meant to work and use session storage, but it does not https://gitlab.com/minds/front/-/merge_requests/1938/diffs#f756f8e31c23aaa3ec4177e97f669b1d947ddc6c_0_68 

### Steps to reproduce

1. Load site logged in.
2. Dismiss banner.
3. Refresh - banner comes back, despite "dismissed" state being true in settings.

### Platform information 

Web

### What is the current *bug* behavior?

Banner comes back after dismissal

### What is the expected *correct* behavior?

Banner should stay away after dismissal, at least for a good while

### Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 0.0
Clean up common component names and module declarations/exports

<!---
Please read this!

The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate.
--->

## Goal

<!---
Clearly outline the goal of the issue and why we are doing it
--->
Components in the common folder are there because they can be used and reused in multiple modules.  They should be easy to find, reference and maintain.

## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->
- [ ] Compile list of components that will be affected
- [ ] Rename relevant selectors so that they use BEM naming convention
- [ ] Where appropriate, also update css classes to match the component names
- [ ] Move all components and directives into respective constants (e.g. `MINDS_COMMON_COMPONENTS` and `MINDS_COMMON_DIRECTIVES`). Reference these constants in the common module's declarations and exports, instead of referencing each item twice.


## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->
Visual assessment of affected components in list

## UX/Design

<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->
N/A

## Personas

<!---
Who does this user impact and why (optional)
--->
Developers

## Experiments

<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->
None

## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] Common components look exactly the same but are more usable and easier to maintain

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 1.0
Class-level documentation for components from audit phase 1

<!---
Please read this!

The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate.
--->

## Goal

<!---
Clearly outline the goal of the issue and why we are doing it
--->
Each component covered in #5541 should have at least one class-level comment to document its high-level purpose/usage.

e.g. for <m-accordion> component: "creates a re-usable vertical accordion layout. To be used in conjunction with the <m-accordion__pane> component. Used in channel editor."

## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->


Add a class-level comment to each component covered in audit phase 1. 

Spreadsheet is here https://docs.google.com/spreadsheets/d/1CfSLcpmEKjzf-CDqu_aGM3DH1xcRU2_hGjSyC6cPe7Y/edit#gid=647707769 . Components included in phase 1 can be found by filtering the 'Components tab' > 'phase' column.


## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->
None

## UX/Design

<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->
N/A

## Personas

<!---
Who does this user impact and why (optional)
--->
Developers

## Experiments

<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->
None

## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] Components in audit phase 1 should have class level documentation

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
Remove festival banner

<!---
Please read this!

The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate.
--->

## Goal

<!---
Clearly outline the goal of the issue and why we are doing it
--->
A banner promoting the Minds Festival of Ideas was implemented and should be removed after the event on Jun 25th.


## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->
- [x] Remove festival banner experiment service and references (including reference in join banner component)
- [x] Remove festival banner component
- [ ] Delete the `front-5575-festival-banner` experiment from Growthbook

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->
Make sure banner is gone

## UX/Design

<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->


## Personas

<!---
Who does this user impact and why (optional)
--->
All users

## Experiments

<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->
`front-5575-festival-banner` should be removed

## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] festival banner component and experiment are removed

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 1.0
Error messages are not being displayed when clicking on Help in menu

<!---
Please read this!

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate.
--->

### Summary

Error messages are not being displayed when clicking on Help in menu. Zendesk passes messages back in the query string which are [supposed to be parsed here]( https://gitlab.com/minds/front/blob/dcb1406a62f26de588187146f856ca5be8913db0/src/app/modules/newsfeed/feeds/subscribed.component.ts#L168) and displayed in a toaster. 

### Steps to reproduce

Try to visit help with a second account with the same email as an account already registered with Zendesk - an error toast SHOULD appear

Haven't confirmed but this may be an example URL that should trigger the message:

https://www.minds.com/newsfeed/subscribed?kind=error&message=Please+use+one+of+the+options+below+to+sign+in+to+Zendesk.
 
### Platform information 

Web

- John: Windows, Chrome
- Ben: Ubuntu, Firefox

### What is the current *bug* behavior?

Error message doesn't show - confusing.

### What is the expected *correct* behavior?

Error message should show.

### Relevant logs and/or screenshots

![image](/uploads/9eba46d69f4ec53c13bdbf1fd41c204a/image.png)

![image](/uploads/bad869726b40eae77cf73fbb3d925055/image.png)

### Possible fixes

Just an idea, could redirect to latest/top by breaking it?

Story points: 1.0
Component audit phase 2

<!---
Please read this!

The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate.
--->

## Goal

<!---
Clearly outline the goal of the issue and why we are doing it
--->
Continue component audit started in #5541 . 

## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->

Approx. 1/3 of components still need to be evaluated. This second batch should move faster than #5541 because the component list has already been compiled (here https://docs.google.com/spreadsheets/d/1CfSLcpmEKjzf-CDqu_aGM3DH1xcRU2_hGjSyC6cPe7Y/edit#gid=647707769) and the common components (which take longer to evaluate) are completed.  

As I go through them, make sure each of the components (the final 1/3) has at least one class-level comment to document its purpose/usage.

e.g. the <m-accordion> component "creates a re-usable vertical accordion layout. To be used in conjunction with <m-accordion__pane> component. Used in channel editor."

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->
None

## UX/Design

<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->
None

## Personas

<!---
Who does this user impact and why (optional)
--->
Devs

## Experiments

<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->
None

## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] Finish evaluating components in spreadsheet

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 5.0
Create sitewide banner to promote Minds Festival of Ideas

<!---
Please read this!

The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate.
--->

## Goal

Sell tickets to Minds Festival of Ideas.

## What needs to be done

Create a simple banner element that displays on every page of Minds, to both registered and unregistered users, and clicks through to where users can buy tickets.

- Text: Minds LIVE EVENT in NYC on June 25. Tickets on sale now!
- CTA: Buy Tickets
- Link: https://www.ticketmaster.com/event/3B005CB2CF161F8D?utm_source=minds&utm_medium=banner&utm_campaign=festival

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

![image](/uploads/d1303a09354b710605b649aea14db34f/image.png)

## Personas

Everyone on Minds

## Experiments

No experiment

## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] A banner element appears on every page of Minds with the copy defined above.
- [ ] The banner clicks through to the link defined above.
- [ ] The banner is dismissable and stays dismissed for the duration of the user's session.

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 2.0
You must verify your account error when entering phone number

<!---
Please read this!

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate.
--->

### Summary

When entering your phone number, a toast error saying "You must verify your account" is passed back from the engine. This could cause confusion for a user who is trying to verify their phone number.

### Steps to reproduce

1. Make a new account
2. Try to input phone number before verifying email address

### Platform information 

Web

### What is the current *bug* behavior?

Error message is confusing.

### What is the expected *correct* behavior?

- Throw this toast before the modal appears
- Should read something more like `You must confirm your email address` (for both before, and when sent from the engine - requires change to UnverifiedEmailException.
- The error at the bottom saying invalid phone number should not show unless the phone number is invalid.

### Relevant logs and/or screenshots

![image](/uploads/e358747d7e0382557779af903e47fcd9/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
Rewards runner timeouts connecting to Etherscan

<!---
Please read this!

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate.
--->

### Summary

- Reward runner seems to be timing out connecting to Etherscan. 
- Peggy reports her rewards estimates have not updated today.

### Steps to reproduce

- Check pods and watch the pod timeout - possibly a coincidence but it's timing out on my users LP rewards calc. My wallet has had no activity and I haven't changed anything with my account.

### Platform information 

Infra

### What is the current *bug* behavior?

Rewards calc isn't completing

### What is the expected *correct* behavior?

Reward runner seems to be stuck in a crash loop (not reflected as a crash loop in k8s).

### Relevant logs and/or screenshots

![image](/uploads/63324ef4567db016383974f8af4b013a/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
Notifications Not Displaying

<!---
Please read this!

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate.
--->

### Summary
Notifications are not being displayed within the drop down notifications box or within the notifications section.

I have seen two reports of this (related to users: Terribleterry and Tomtomandt) and after going through a diagnostic process with Terribleterry, it seems that this user could be suffering from a database related issue.

### Platform information 

Terribleterry has reported using Mozilla Firefox, SlimBrowser (SlimBrowser has become a Firefox derivative as of August 2019), Google Chrome, Brave and Explorer (I am presuming that this user means Microsoft Edge and not Microsoft Internet Explorer) - Microsoft Windows (unknown version).

### Relevant logs and/or screenshots

![terribleterry-notifications-section](/uploads/69e22a448085c8fe571ff5120a671076/terribleterry-notifications-section.png)<br>
<i>Full page notification section - Terribleterry's account</i>

![terribleterry-notifications-dropdown](/uploads/bda7276278bbb803610606a939714e85/terribleterry-notifications-dropdown.png)<br>
<i>Notifications drop down box - Terribleterry's account</i>

### Sentry 

https://sentry.io/organizations/minds-inc/issues/3237520856/?query=is%3Aunresolved+user.id%3A1113836539374215175&statsPeriod=14d

### Possible Fixes

Could make GUID public and break encapsulation, or alternatively handle wires differently there / don't provide GUID if its not available.

- https://gitlab.com/minds/engine/blob/1b6016b84ffa8e654083a07ea55fabacf0f4515a/Core/Security/ACL.php#L116

Story points: 1.0
EmailConfirmationService error failing in Unit tests

### Summary

EmailConfirmationService error happens in unit tests.

### Steps to reproduce

Run CI pipeline, fails in unit tests pretty often. 

### Platform information 

on Gitlab CI

### What is the current *bug* behavior?

Test fails

### What is the expected *correct* behavior?

Test should pass unless it is a bug

### Relevant logs and/or screenshots

https://gitlab.com/minds/front/-/jobs/2547482231

Story points: 1.0
Seeing "0 latest posts" banner

### Summary

Seeing 0 latest posts blue banner which is not needed as the feed is already up to date. It never disappears.

### Steps to reproduce

1. Login to minds.
2. Navigate to the URL https://www.minds.com/discovery/search?q=&f=latest&t=all.

### Platform information 

All - Firefox - Staging/Canary/Prod

### What is the current *bug* behavior?

Seeing 0 latest posts appears which is not needed

### What is the expected *correct* behavior?

See 0 latest posts should not appear

### Relevant logs and/or screenshots

https://www.minds.com/discovery/search?q=&f=latest&t=all

![image](/uploads/952991ece14871e43fb2e8a94019ee26/image.png)

Story points: 2.0