Skip to content

Browser keyboard race #4717

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

Merged
merged 2 commits into from
Apr 23, 2025
Merged

Browser keyboard race #4717

merged 2 commits into from
Apr 23, 2025

Conversation

mstoykov
Copy link
Contributor

What?

Fix race on map access in keyboard.

Why?

Races are bad.

Checklist

  • I have performed a self-review of my code.
  • I have commented on my code, particularly in hard-to-understand areas.
  • I have added tests for my changes.
  • I have run linter and tests locally (make check) and all pass.

Checklist: Documentation (only for k6 maintainers and if relevant)

Please do not merge this PR until the following items are filled out.

  • I have added the correct milestone and labels to the PR.
  • I have updated the release notes: link
  • I have updated or added an issue to the k6-documentation: grafana/k6-docs#NUMBER if applicable
  • I have updated or added an issue to the TypeScript definitions: grafana/k6-DefinitelyTyped#NUMBER if applicable

Related PR(s)/Issue(s)

@mstoykov mstoykov added this to the v1.0.0 milestone Apr 21, 2025
@mstoykov mstoykov requested a review from a team as a code owner April 21, 2025 10:20
@mstoykov mstoykov requested review from inancgumus and joanlopez and removed request for a team April 21, 2025 10:20
@mstoykov
Copy link
Contributor Author

Pretty sure that modifiers is also racy, but a quick look at the code didn't make me think that it will be a quick fix there. And I haven't seen it being a problem, so I left it for the future.

@joanlopez
Copy link
Contributor

Pretty sure that modifiers is also racy, but a quick look at the code didn't make me think that it will be a quick fix there. And I haven't seen it being a problem, so I left it for the future.

Yeah, I'm generally in favor of merging something that improves the current situation, even if not perfect, unless there would be a trivial fix for that other one as well, of course, which doesn't seem to be the case. Thanks! 👍🏻

@mstoykov mstoykov merged commit c674c71 into master Apr 23, 2025
26 of 28 checks passed
@mstoykov mstoykov deleted the browserKeyboardRace branch April 23, 2025 16:07
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.

3 participants