Skip to content

Fix pagerank typo#5545

Open
LorentzFactor wants to merge 3 commits into
rapidsai:mainfrom
LorentzFactor:fix-pagerank-typo
Open

Fix pagerank typo#5545
LorentzFactor wants to merge 3 commits into
rapidsai:mainfrom
LorentzFactor:fix-pagerank-typo

Conversation

@LorentzFactor

Copy link
Copy Markdown

This is a tiny PR to fix a typo ("verties" $\to$ "vertices") in the comments of the pagerank tests.

@LorentzFactor LorentzFactor requested a review from a team as a code owner June 8, 2026 19:45
@copy-pr-bot

copy-pr-bot Bot commented Jun 8, 2026

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@seunghwak seunghwak left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM

@ChuckHastings

Copy link
Copy Markdown
Collaborator

/ok to test ca05fa7

@ChuckHastings ChuckHastings added improvement Improvement / enhancement to an existing function non-breaking Non-breaking change labels Jun 8, 2026
@ChuckHastings

Copy link
Copy Markdown
Collaborator

/ok to test a56ffa6

@ChuckHastings

Copy link
Copy Markdown
Collaborator

/ok to test 4ea3e36

@ChuckHastings

Copy link
Copy Markdown
Collaborator

/okay to test 93f361e

@copy-pr-bot

copy-pr-bot Bot commented Jun 10, 2026

Copy link
Copy Markdown

/okay to test 93f361e

@ChuckHastings, there was an error processing your request: E2

See the following link for more information: https://docs.gha-runners.nvidia.com/cpr/e/2/

@ChuckHastings

Copy link
Copy Markdown
Collaborator

/ok to test 9ef361e

@LorentzFactor

Copy link
Copy Markdown
Author

Hey @ChuckHastings - apologies for the continuous cycle of approvals to run... it looks like main is being updated rather frequently, so I'm struggling to remain up to date with it before you approve the branch for another run through the checks.

I'll try to watch this repo throughout the day and continue to merge as changes come in... so hopefully next time it'll be up-to-date with main and can finally be merged and closed.

@ChuckHastings

Copy link
Copy Markdown
Collaborator

No worries.

FYI - We can let main drift a bit without constantly remerging. You'll see a warning when they start to drift, but it will still merge correctly unless there is a conflict. When it has drifted too far you'll see the warning change to an actual blockage.

I'm going to try and get this merged today.

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

Labels

improvement Improvement / enhancement to an existing function non-breaking Non-breaking change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants