Skip to content
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

test/browser/connection: fix hmac extraction #1939

Closed
wants to merge 1 commit into from
Closed

test/browser/connection: fix hmac extraction #1939

wants to merge 1 commit into from

Conversation

Zariel
Copy link
Contributor

@Zariel Zariel commented Jan 7, 2025

Relax the connectionKey hmac extraction and account for the possibilities of multiple - characters.

RAR-655

Summary by CodeRabbit

  • Bug Fixes
    • Improved connection key processing logic in the connection handling mechanism.

Copy link

coderabbitai bot commented Jan 7, 2025

Walkthrough

The pull request modifies the connectionHmac function in the test/browser/connection.test.js file. The change alters how connection keys are processed, specifically in extracting the handleID. The new implementation uses a different approach to find and extract the relevant parts of the connection key by locating the last hyphen and an exclamation mark, changing the previous substring extraction method.

Changes

File Change Summary
test/browser/connection.test.js Updated connectionHmac function logic for processing connection keys

Assessment against linked issues

Objective Addressed Explanation
Fix flaky page_refresh_with_* tests [RAR-655] Unable to definitively determine if this change resolves test flakiness without more context

Possibly related PRs

Suggested reviewers

  • VeskeR
  • SimonWoolf

Poem

🐰 A Rabbit's Ode to Connection Keys 🔑

Hyphens and marks, a cryptic dance,
Slicing strings with algorithmic glance,
Connection's secret, now reborn,
A test that once was weary and worn,
Hops to life with newfound grace! 🌟


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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.

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. (Beta)
  • @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.

@github-actions github-actions bot temporarily deployed to staging/pull/1939/bundle-report January 7, 2025 11:27 Inactive
@Zariel Zariel requested a review from a team January 7, 2025 11:27
@github-actions github-actions bot temporarily deployed to staging/pull/1939/typedoc January 7, 2025 11:27 Inactive
@github-actions github-actions bot temporarily deployed to staging/pull/1939/features January 7, 2025 11:27 Inactive
@Zariel Zariel force-pushed the rar-655 branch 2 times, most recently from 1c3d568 to 079a7dc Compare January 7, 2025 11:28
@github-actions github-actions bot temporarily deployed to staging/pull/1939/bundle-report January 7, 2025 11:29 Inactive
@github-actions github-actions bot temporarily deployed to staging/pull/1939/features January 7, 2025 11:29 Inactive
@github-actions github-actions bot temporarily deployed to staging/pull/1939/typedoc January 7, 2025 11:29 Inactive
Relax the connectionKey hmac extraction and account for
the possibilities of multiple - characters.

RAR-655
@Zariel
Copy link
Contributor Author

Zariel commented Jan 7, 2025

supersedes #1903

@Zariel
Copy link
Contributor Author

Zariel commented Jan 7, 2025

@coderabbitai review

Copy link

coderabbitai bot commented Jan 7, 2025

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

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)
test/browser/connection.test.js (1)

218-218: Document the connection key format.

The comment /* connectionKey has the form <instanceID>!<hmac>-<handleID> */ could be more detailed to explain that the HMAC portion may contain hyphens.

-/* strip instanceID and handleID from connectionKey */
+/**
+ * Extracts the HMAC portion from a connection key.
+ * @param {string} key - Connection key in the format "<instanceID>!<hmac>-<handleID>"
+ *                      where the HMAC portion may contain hyphens.
+ * @returns {string} The extracted HMAC portion.
+ */
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 1d6483a and e2e2f74.

📒 Files selected for processing (1)
  • test/browser/connection.test.js (1 hunks)
🔇 Additional comments (1)
test/browser/connection.test.js (1)

219-224: LGTM! The HMAC extraction logic handles multiple hyphens correctly.

The implementation correctly uses lastIndexOf('-') to handle cases where the HMAC portion contains hyphens, addressing the PR objective.

Let's verify the format assumption with a quick search:

✅ Verification successful

Implementation correctly follows the documented connection key format

The code aligns with the documented format <instanceID>!<hmac>-<handleID> and correctly handles cases where the HMAC portion contains hyphens. The format is consistently used across test files.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Search for connection key format documentation or usage
# Expected: Find references confirming the "<instanceID>!<hmac>-<handleID>" format

# Search for connection key format documentation
rg -l "connection.*key.*format|connectionKey.*format"

# Search for connection key usage patterns
rg "!.*-.*" --type js

Length of output: 618


Script:

#!/bin/bash
# Check ably.d.ts for connection key format documentation
rg -A 3 "connectionKey" ably.d.ts

# Search for any additional connection key usages in test files
ast-grep --pattern 'connectionKey: $_'

Length of output: 74

@jamienewcomb jamienewcomb requested a review from VeskeR January 7, 2025 13:38
Copy link
Member

@SimonWoolf SimonWoolf left a comment

Choose a reason for hiding this comment

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

why go to a lot of effort to parse out the connectionId from the connectionKey rather than just comparing connectionIds? trying to do the former is inherently flaky: the connectionkey format is a secret of the server and the sdk should not depend on it, either in code or tests. the library exposes the connectionId in connection.id, just use that

Copy link
Contributor

@VeskeR VeskeR left a comment

Choose a reason for hiding this comment

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

Agree with Simon on this, ideally we should not depend on some internal realtime knowledge that can change any time when there is an alternative.

It looks like @lawrence-forooghian just opened a PR #1957 that fixes this issue the way Simon suggested - removes parsing of the connection key and compare connection id. I suggest we go with that PR and close this one.

@lawrence-forooghian
Copy link
Collaborator

D'oh, completely missed the existence of this PR, sorry! Will merge #1957.

@Zariel Zariel closed this Jan 23, 2025
@Zariel Zariel deleted the rar-655 branch January 23, 2025 12:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

4 participants