Skip to content

Conversation

@inancgumus
Copy link
Contributor

@inancgumus inancgumus commented Jun 4, 2025

What?

Fix web-dashboard output conflict.

Why?

Running:

K6_WEB_DASHBOARD=true k6 run --out web-dashboard script.js

Results:

...listen tcp :port: bind: address already in use

Also see #4707.

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

Related PR(s)/Issue(s)

Closes #4707

@inancgumus inancgumus added this to the v1.1.0 milestone Jun 4, 2025
@inancgumus inancgumus self-assigned this Jun 4, 2025
@inancgumus inancgumus added the bug label Jun 4, 2025
@inancgumus inancgumus marked this pull request as ready for review June 4, 2025 22:13
@inancgumus inancgumus requested a review from a team as a code owner June 4, 2025 22:13
@inancgumus inancgumus requested review from codebien and joanlopez and removed request for a team June 4, 2025 22:13
joanlopez
joanlopez previously approved these changes Jun 9, 2025
@codebien codebien added the breaking change for PRs that need to be mentioned in the breaking changes section of the release notes label Jun 9, 2025
Copy link
Contributor

@codebien codebien left a comment

Choose a reason for hiding this comment

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

@inancgumus can you add a unit test for it, please?

As we stop supporting a use case, we should probably add a warning in the case a duplicate is intercepted.

I've marked as breaking change for now, but we will discuss internally if this is really the case or not as we never documented it before.

@inancgumus inancgumus force-pushed the fix/4707-web-dashboard-output-conflict branch 4 times, most recently from 5e9470e to 00d10b0 Compare June 9, 2025 15:08
@inancgumus inancgumus requested review from codebien and joanlopez June 9, 2025 15:19
Running:
K6_WEB_DASHBOARD=true k6 run --out web-dashboard script.js

Results:
listen tcp :port: bind: address already in use
@inancgumus inancgumus force-pushed the fix/4707-web-dashboard-output-conflict branch from 00d10b0 to 42da59e Compare June 9, 2025 15:53
@codebien codebien removed the breaking change for PRs that need to be mentioned in the breaking changes section of the release notes label Jun 9, 2025
Copy link
Contributor

@codebien codebien left a comment

Choose a reason for hiding this comment

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

LGTM, we decided to not mark as a breaking change as this was an undefined case.

@inancgumus
Copy link
Contributor Author

inancgumus commented Jul 28, 2025

Superseeded by #4913.

@inancgumus inancgumus closed this Jul 28, 2025
@codebien
Copy link
Contributor

@inancgumus the linked pull request seems wrong. Are you sure of the link?

@inancgumus
Copy link
Contributor Author

@codebien fixed.

@mstoykov mstoykov deleted the fix/4707-web-dashboard-output-conflict branch August 4, 2025 07:56
@mstoykov mstoykov removed this from the v1.2.0 milestone Aug 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

conflict between 2 config vars in web dashboard

4 participants