Skip to content

Conversation

@kennytv
Copy link
Member

@kennytv kennytv commented Mar 7, 2023

First step of #8948, assuming we actually decide to remove timings entirely.

After an explicit announcement and some more time passes, we can also add runtime warnings.

@kennytv kennytv requested a review from a team as a code owner March 7, 2023 12:46
@kashike kashike mentioned this pull request Mar 7, 2023
4 tasks
@UntouchedOdin0
Copy link

I fully understand why you guys are removing timings, but as mentioned please bring in spark to replace it so we have something to use for timings.

@Warriorrrr
Copy link
Member

Replacing timings with spark is the idea yeah, see the issue linked in the pr description.

@codebycam
Copy link

LGTM

@EterNityCH
Copy link
Member

I am EterNity and I approve this message.

Copy link
Member

@EterNityCH EterNityCH left a comment

Choose a reason for hiding this comment

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

LGTM 🍡

Copy link
Member

@kashike kashike left a comment

Choose a reason for hiding this comment

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

I am kashike and I approve this message.

@kashike kashike self-assigned this Mar 28, 2023
@kashike kashike merged commit 9940019 into master Mar 28, 2023
@kashike kashike deleted the timings branch March 28, 2023 02:58
@UntouchedOdin0
Copy link

Replacing timings with spark is the idea yeah, see the issue linked in the pr description.

Sorry! Didn't see that part, forgot my glasses! 🧐😅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants