Release test v6.115.0 #8603

Closed rafaelromcar-parabol closed 1 year ago

The basics

Run through this list at least once at staging:

[x] Smoke tested the Demo, unauthenticated
[x] Created an account
[x] Verified invite via mass link works (Team > Invite Button > Invite Link, visit URL in an incognito window)
[x] Verified invite via email works
[x] Added Slack, verified meeting notifications (use #t_product_actiontime)
[x] Added Mattermost, verified meeting notifications (check the test webhook in Parabol Mattermost)
[x] Added GitHub, verified issue created (use ParabolInc/publictestrepo)
[x] Added Jira, verified issue created (use parabol-2)
[x] Added GitLab, verified issue created
[ ] Added JiraServer, verified issue created
[x] Smoke tested the Retro meeting with 2 players
[x] Smoke tested the Sprint Poker meeting with 2 players
[x] Smoke tested the Team Check-in meeting with 2 players
[x] Smoke tested the Standup meeting with 2 players
[x] Smoke tested cards on the dashboard
[x] Created a 2nd team
[x] Created a 2nd organization
[x] Upgraded to Team (Credit card number: 4242 4242 4242 4242, expiration date: any month in the future, CVC: 123)
[x] Smoke tested the app on a mobile device (e.g. navigate between views, smoke test a Retro meeting, etc.)
[x] Test previously existed meetings to make sure that existing data is not corrupted
[x] Create a task in the discussion thread of a meeting
[x] Create a comment in the discussion thread of a meeting

What’s changed

At your discretion, complete the tests for any merged PRs:

Update enterprise advantages #8577
Fix open pgtyped connections after running #8583
AL: Roll out Activity Library to all new users #8574
Remove and ignore pg.d.ts #8587
Add emoji insights #8563
AI Summary: Replace GPT-3 with GPT-3.5 for aiSummary #8227
Do not trust invites sent to emails from the untrusted domains #8584
Humanize count down timer #8596
Activity library reduce #8599

Error on the meetings screen. When clicking on a team's name, it shows the existing meetings, but if you click again on the name, it then shows an error. If you switch between teams, the error is also present. If you come back to tasks/history/meetings and then to a team, if works again, but only if you do not click again on it.

Today's Sentry Staging issues

https://www.loom.com/share/37b9dd16621844e0b495d14d9fc21742?sid=8192d9e2-96a4-4d45-92b8-b4c6d26cfc63

JIRA added to Thomas' Test project

In the discussion thread of a Retro I tried to smileys and also to change the responsibility of a task created on that thread. Some times I couldn't see other people on the team to switch the responsibility and the smileys didn't show when clicking on them. I had to refresh the browser to see the changes on the smileys and to be able to see other people and switch the owner of the task.

https://www.loom.com/share/26771bfd8c754250a2f3d0aa6aefcd11?sid=b46f28bb-54ee-410e-a4ca-1a515b0f70e8

This error was not observed on the discussion thread of a Sprint Poker nor during a Check-In meeting.

The new ready button is shown for the facilitator during the Icebreaker, but the participants do not see any "click when you are ready", they only see the sign ? for the Tips.

Mobile version tested. Error on the meetings screen reproduced. Error on retros tasks and comments couldn't be reproduced.

Found design bug (I cannot take a screenshot or screen record because it says there might be personal information...). Whenever I create a new activity (start, stop, continue), the screen where you have to select the settings is showing the settings on top of the rest of the screen. As if there were two layers and the description of the activity was the layer on the background and the settings were, aligned to the right, on the top layer (hiding part of the background layer).

The new ready button is shown for the facilitator during the Icebreaker, but the participants do not see any "click when you are ready", they only see the sign ? for the Tips.

That's the existing behavior before the ready button change so it's expected.

The issue found on the Retro (smileys that do not show up and responsibility switch problems) cannot be reproduced anymore on Staging. No explanation about why is this.

The issue on switching teams' views cannot be reproduced on a fresh environment, deployed in Kubernetes from the latest image built from the staging branch.

On the actual Staging environment, there are error logs on the browser's console:

GET https://action-staging.parabol.co/static/manifest.json 401
manifest.json:1 Manifest: Line: 1, column: 1, Syntax error.
instrument.js:109 TypeError: Cannot destructure property 'isConnected' of 't' as it is undefined.
    at DashboardAvatars.tsx:109:14
    at Array.forEach (<anonymous>)
    at DashboardAvatars.tsx:107:17
    at Object.useMemo (react-dom.production.min.js:172:115)
    at t.useMemo (react.production.min.js:23:113)
    at z (DashboardAvatars.tsx:104:25)
    at aa (react-dom.production.min.js:157:137)
    at Ws (react-dom.production.min.js:267:460)
    at kl (react-dom.production.min.js:250:347)
    at Ol (react-dom.production.min.js:250:278)
    at wl (react-dom.production.min.js:250:138)
    at yl (react-dom.production.min.js:243:163)
    at react-dom.production.min.js:123:115
    at t.unstable_runWithPriority (scheduler.production.min.js:18:343)
    at Zi (react-dom.production.min.js:122:325)
    at Wi (react-dom.production.min.js:123:61)
    at M (scheduler.production.min.js:16:224)
    at E.port1.onmessage (scheduler.production.min.js:12:346)
(anonymous) @ instrument.js:109
(anonymous) @ trackConsoleError.js:25
V @ internalMonitoring.js:80
console.error @ trackConsoleError.js:24
cs @ react-dom.production.min.js:216
o.componentDidCatch.r.callback @ react-dom.production.min.js:217
ho @ react-dom.production.min.js:131
gs @ react-dom.production.min.js:220
Pl @ react-dom.production.min.js:259
t.unstable_runWithPriority @ scheduler.production.min.js:18
Zi @ react-dom.production.min.js:122
Dl @ react-dom.production.min.js:252
yl @ react-dom.production.min.js:243
(anonymous) @ react-dom.production.min.js:123
t.unstable_runWithPriority @ scheduler.production.min.js:18
Zi @ react-dom.production.min.js:122
Wi @ react-dom.production.min.js:123
M @ scheduler.production.min.js:16
E.port1.onmessage @ scheduler.production.min.js:12
instrument.js:109 TypeError: Cannot destructure property 'isConnected' of 't' as it is undefined.
    at DashboardAvatars.tsx:109:14
    at Array.forEach (<anonymous>)
    at DashboardAvatars.tsx:107:17
    at Object.useMemo (react-dom.production.min.js:172:115)
    at t.useMemo (react.production.min.js:23:113)
    at z (DashboardAvatars.tsx:104:25)
    at aa (react-dom.production.min.js:157:137)
    at Ws (react-dom.production.min.js:267:460)
    at kl (react-dom.production.min.js:250:347)
    at Ol (react-dom.production.min.js:250:278)
    at wl (react-dom.production.min.js:250:138)
    at yl (react-dom.production.min.js:243:163)
    at react-dom.production.min.js:123:115
    at t.unstable_runWithPriority (scheduler.production.min.js:18:343)
    at Zi (react-dom.production.min.js:122:325)
    at Wi (react-dom.production.min.js:123:61)
    at M (scheduler.production.min.js:16:224)
    at E.port1.onmessage (scheduler.production.min.js:12:346)
(anonymous) @ instrument.js:109
(anonymous) @ trackConsoleError.js:25
V @ internalMonitoring.js:80
console.error @ trackConsoleError.js:24
_ @ ErrorComponent.tsx:35
aa @ react-dom.production.min.js:157
Ws @ react-dom.production.min.js:267
kl @ react-dom.production.min.js:250
Ol @ react-dom.production.min.js:250
wl @ react-dom.production.min.js:250
yl @ react-dom.production.min.js:243
(anonymous) @ react-dom.production.min.js:123
t.unstable_runWithPriority @ scheduler.production.min.js:18
Zi @ react-dom.production.min.js:122
Wi @ react-dom.production.min.js:123
M @ scheduler.production.min.js:16
E.port1.onmessage @ scheduler.production.min.js:12
manifest.json:1     GET https://action-staging.parabol.co/static/manifest.json 401
manifest.json:1 Manifest: Line: 1, column: 1, Syntax error.
manifest.json:1     GET https://action-staging.parabol.co/static/manifest.json 401
manifest.json:1 Manifest: Line: 1, column: 1, Syntax error.
Access to fetch at 'https://action-files.parabol.co/staging/build/v6.115.0-rc.1/35890f6a29c562e979eb.css' from origin 'https://action-staging.parabol.co' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
sw.js:1        Uncaught (in promise) TypeError: Failed to fetch
    at sw.js:1:35168
(anonymous) @ sw.js:1
manifest.json:1     GET https://action-staging.parabol.co/static/manifest.json 401
manifest.json:1 Manifest: Line: 1, column: 1, Syntax error.

Regarding the static/manifest.json, I can get the document https://action-staging.parabol.co/static/manifest.json directly on the browser without any trouble.

There is one CORS error.

And then there is two more that look a bit different: instrument.js:109 TypeError: Cannot destructure property 'isConnected' of 't' as it is undefined.

None of these errors are shown on the fresh environment.

live in prod

ParabolInc / parabol

Release test v6.115.0 #8603

The basics

What’s changed