Skip to content

test: Scenario that replicates the crash in production#19071

Merged
emrysal merged 5 commits intomainfrom
crash-test
Feb 7, 2025
Merged

test: Scenario that replicates the crash in production#19071
emrysal merged 5 commits intomainfrom
crash-test

Conversation

@hariombalhara
Copy link
Copy Markdown
Member

@hariombalhara hariombalhara commented Feb 4, 2025

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

@vercel
Copy link
Copy Markdown

vercel Bot commented Feb 4, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
cal-com-ui-playground ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 7, 2025 7:32am
2 Skipped Deployments
Name Status Preview Comments Updated (UTC)
cal ⬜️ Ignored (Inspect) Visit Preview Feb 7, 2025 7:32am
calcom-web-canary ⬜️ Ignored (Inspect) Visit Preview Feb 7, 2025 7:32am

@CLAassistant
Copy link
Copy Markdown

CLAassistant commented Feb 4, 2025

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ emrysal
❌ Hariom Balhara


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.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Feb 4, 2025

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:

No release type found in pull request title "Not to be merged - Scenario that replicates the crash in production". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

@hariombalhara hariombalhara changed the title Add a case that crashes Not to be merged - Scenario that replicates the crash in production Feb 4, 2025
@keithwillcode keithwillcode added core area: core, team members only enterprise area: enterprise, audit log, organisation, SAML, SSO labels Feb 4, 2025
organizerTimeZone: eventTimeZone,
datesOutOfOffice: !isTeamEvent ? allUsersAvailability[0]?.datesOutOfOffice : undefined,
datesOutOfOffice: {
"2020-06-01": {
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a an old date before current time causing the error.

@emrysal emrysal changed the title Not to be merged - Scenario that replicates the crash in production test: Scenario that replicates the crash in production Feb 4, 2025
@emrysal
Copy link
Copy Markdown
Contributor

emrysal commented Feb 4, 2025

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.

@hariombalhara hariombalhara marked this pull request as ready for review February 7, 2025 07:23
@graphite-app graphite-app Bot requested a review from a team February 7, 2025 07:23
@hariombalhara hariombalhara requested review from emrysal and removed request for a team February 7, 2025 07:23
@dosubot dosubot Bot added the automated-tests area: unit tests, e2e tests, playwright label Feb 7, 2025
@graphite-app
Copy link
Copy Markdown

graphite-app Bot commented Feb 7, 2025

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.

@hariombalhara
Copy link
Copy Markdown
Member Author

@emrysal Done

Copy link
Copy Markdown
Contributor

@emrysal emrysal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔥 nice one man!

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Feb 7, 2025

E2E results are ready!

@emrysal emrysal merged commit 6ca7670 into main Feb 7, 2025
@emrysal emrysal deleted the crash-test branch February 7, 2025 11:20
MuhammadAimanSulaiman pushed a commit to hit-pay/cal.com that referenced this pull request Feb 25, 2025
* 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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automated-tests area: unit tests, e2e tests, playwright core area: core, team members only enterprise area: enterprise, audit log, organisation, SAML, SSO ready-for-e2e

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants