-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
benchmark: make output RFC 4180 compliant #37038
Closed
tniessen
wants to merge
1
commit into
nodejs:master
from
tniessen:benchmark-make-output-rfc-4180-compliant
Closed
benchmark: make output RFC 4180 compliant #37038
tniessen
wants to merge
1
commit into
nodejs:master
from
tniessen:benchmark-make-output-rfc-4180-compliant
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
RaisinTen
approved these changes
Jan 23, 2021
tniessen
added
the
author ready
PRs that have at least one approval, no pending requests for changes, and a CI started.
label
Jan 23, 2021
jasnell
approved these changes
Jan 23, 2021
Trott
approved these changes
Jan 23, 2021
lpinca
approved these changes
Jan 23, 2021
aduh95
approved these changes
Jan 24, 2021
cjihrig
approved these changes
Jan 24, 2021
Just noting for whomever lands this... there don't appear to be any CI tests covering compare.js so a full CI run would be pointless. |
There's no reason for this to wait the full minimum time to land. Please 👍🏻 to fast-track |
Landed in 9da3f21 |
jasnell
pushed a commit
that referenced
this pull request
Jan 25, 2021
PR-URL: #37038 Reviewed-By: Darshan Sen <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Colin Ihrig <[email protected]>
tniessen
removed
the
author ready
PRs that have at least one approval, no pending requests for changes, and a CI started.
label
Jan 25, 2021
targos
pushed a commit
that referenced
this pull request
Feb 2, 2021
PR-URL: #37038 Reviewed-By: Darshan Sen <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Colin Ihrig <[email protected]>
targos
pushed a commit
that referenced
this pull request
May 1, 2021
PR-URL: #37038 Reviewed-By: Darshan Sen <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Colin Ihrig <[email protected]>
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
benchmark
Issues and PRs related to the benchmark subsystem.
fast-track
PRs that do not need to wait for 48 hours to land.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I had trouble importing the generated CSV into other software because it doesn't conform to RFC 4180, the de facto standard for CSV.
Relevant information from the RFC:
Since spaces are considered part of a field, we end up with fields of the form
' "foo"'
(note the space in front of the quoted value), and now the quote isn't the first character within the field, so it violates the RFC.