test: Scenario that replicates the crash in production#19071
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Skipped Deployments
|
|
Hariom Balhara seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
|
Hey there and thank you for opening this pull request! 👋🏼 We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted. Details: |
| organizerTimeZone: eventTimeZone, | ||
| datesOutOfOffice: !isTeamEvent ? allUsersAvailability[0]?.datesOutOfOffice : undefined, | ||
| datesOutOfOffice: { | ||
| "2020-06-01": { |
There was a problem hiding this comment.
This is a an old date before current time causing the error.
|
Hi @hariombalhara I'd love to merge this test if it passes when the cause of crash is reverted. So we cover this scenario the next time. |
ddb8312 to
9d16070
Compare
Graphite Automations"Add consumer team as reviewer" took an action on this PR • (02/07/25)1 reviewer was added to this PR based on Keith Williams's automation. "Add ready-for-e2e label" took an action on this PR • (02/07/25)1 label was added to this PR based on Keith Williams's automation. |
|
@emrysal Done |
E2E results are ready! |
* Add a case that crashes * Add proper crash test case --------- Co-authored-by: Hariom Balhara <hariombalhara@gmgmail.com> Co-authored-by: Alex van Andel <me@alexvanandel.com>
What does this PR do?
Adds a test that identifies the crash scenario due to which we had to revert https://github.com/calcom/cal.com/pull/18054/files#diff-3bcd8b09138a03622b300b58836dfed0598874aed41ff92f57c2b2700f30f4b5