Skip to content

The system automatically updates the time, resulting in event loss #13494

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

mayunhai
Copy link

@mayunhai mayunhai commented Jun 18, 2025

When the system automatically updates the time to the time before assigning the value to 'invoker. attached', 'e.vts<=invoker. attached' will cause the function to always jump out, resulting in listening failure

demo

image

Summary by CodeRabbit

  • Refactor
    • Improved event timestamp accuracy by switching from Date.now() to performance.now() for all event-related timing.
    • Updated documentation to reflect the change in timestamping method.

…ausing registered listeners to become invalid

When the system automatically updates the time to the time before assigning the value to 'invoker. attached', 'e.vts<=invoker. attached' will cause the function to always jump out, resulting in listening failure
Copy link

coderabbitai bot commented Jun 18, 2025

Walkthrough

The code replaces all instances of Date.now() with performance.now() for event timestamping and updates related comments to reflect this change. The logic and control flow remain the same, with only the timestamp source being altered.

Changes

File(s) Change Summary
packages/runtime-dom/src/modules/events.ts Replaced Date.now() with performance.now() for event timestamps; updated comments accordingly

Poem

A tick, a tock, a time anew,
Now performance leads the view.
Events are stamped with greater care,
Precision timing everywhere!
The rabbit hops with nimble glee—
Fast and smooth, as time should be.

✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
packages/runtime-dom/src/modules/events.ts (1)

86-92: Adopt monotonic timer for invoker attachment timestamps
The new getNow correctly uses performance.now() with a per-tick cache to replace Date.now(), ensuring monotonic behavior and reducing calls.

Consider splitting the comma‐operator expression into two statements for clarity:

- const getNow = () =>
-   cachedNow || (p.then(() => (cachedNow = 0)), (cachedNow = performance.now()))
+ const getNow = () => {
+   if (cachedNow) return cachedNow
+   p.then(() => { cachedNow = 0 })
+   cachedNow = performance.now()
+   return cachedNow
+ }
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5f8314c and 0b2270d.

📒 Files selected for processing (1)
  • packages/runtime-dom/src/modules/events.ts (2 hunks)
🔇 Additional comments (1)
packages/runtime-dom/src/modules/events.ts (1)

110-113: Assign monotonic timestamps to events on first dispatch
Replacing Date.now() with performance.now() for e._vts guarantees that event timestamps aren’t affected by system clock changes. Implementation is correct.

@edison1105 edison1105 added ready to merge The PR is ready to be merged. 🍰 p2-nice-to-have Priority 2: this is not breaking anything but nice to have it addressed. labels Jun 19, 2025
Copy link

Size Report

Bundles

File Size Gzip Brotli
runtime-dom.global.prod.js 101 kB (+14 B) 38.3 kB (+4 B) 34.5 kB (-1 B)
vue.global.prod.js 159 kB (+14 B) 58.5 kB (+3 B) 52 kB (+42 B)

Usages

Name Size Gzip Brotli
createApp (CAPI only) 46.5 kB (+14 B) 18.2 kB 16.7 kB (-5 B)
createApp 54.5 kB (+14 B) 21.2 kB 19.4 kB (+1 B)
createSSRApp 58.7 kB (+14 B) 22.9 kB (-1 B) 20.9 kB (+2 B)
defineCustomElement 59.5 kB (+14 B) 22.8 kB (+1 B) 20.8 kB (+5 B)
overall 68.6 kB (+14 B) 26.4 kB (+1 B) 24 kB (-28 B)

Copy link

pkg-pr-new bot commented Jun 19, 2025

Open in StackBlitz

@vue/compiler-core

npm i https://pkg.pr.new/@vue/compiler-core@13494

@vue/compiler-dom

npm i https://pkg.pr.new/@vue/compiler-dom@13494

@vue/compiler-sfc

npm i https://pkg.pr.new/@vue/compiler-sfc@13494

@vue/compiler-ssr

npm i https://pkg.pr.new/@vue/compiler-ssr@13494

@vue/reactivity

npm i https://pkg.pr.new/@vue/reactivity@13494

@vue/runtime-core

npm i https://pkg.pr.new/@vue/runtime-core@13494

@vue/runtime-dom

npm i https://pkg.pr.new/@vue/runtime-dom@13494

@vue/server-renderer

npm i https://pkg.pr.new/@vue/server-renderer@13494

@vue/shared

npm i https://pkg.pr.new/@vue/shared@13494

vue

npm i https://pkg.pr.new/vue@13494

@vue/compat

npm i https://pkg.pr.new/@vue/compat@13494

commit: 0b2270d

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🍰 p2-nice-to-have Priority 2: this is not breaking anything but nice to have it addressed. ready to merge The PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants