Skip to content

Conversation

patrickbkr
Copy link
Member

No description provided.

@AlexDaniel AlexDaniel requested a review from jnthn April 23, 2020 19:26
@AlexDaniel

This comment has been minimized.

@AlexDaniel
Copy link
Member

jnthn
jnthn previously approved these changes Apr 23, 2020
Implementation in Rakudo
------------------------

The serialization of the arguments happens in Rakudo. Backends are expected to not touch the single arument string they receive from Rakudo on Windows in any way.
Copy link
Contributor

Choose a reason for hiding this comment

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

This is probably good for backend consistency. I'm an iota concerned about reproducing a quoting algorithm, which has security implications, but relieved that there's tests covering this.


[Node.js](https://github.com/nodejs/node/blob/382e859afc7e66600dccfadd4125088444e063c3/lib/child_process.js#L486) exposes a `shell` flag which wraps the call in `cmd.exe /d /s /c "<command>"` by hand and enables `UV_PROCESS_WINDOWS_VERBATIM_ARGUMENTS`.

[Java](https://codewhitesec.blogspot.com/2016/02/java-and-command-line-injections-in-windows.html)s `ProcessBuilder` has a very sophisticated and complex processing of arguments. e.g. it detects whether the user called a `.bat` file or `.cmd` file and acts on that.
Copy link
Contributor

Choose a reason for hiding this comment

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

I'm glad we didn't go this way.

Copy link
Contributor

@JJ JJ left a comment

Choose a reason for hiding this comment

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

This makes sense. Approved!

@AlexDaniel
Copy link
Member

@patrickbkr so is this PR ready now?

@patrickbkr
Copy link
Member Author

@AlexDaniel: I think this PR is ready. But IIUC it still needs to go through the review period.

@patrickbkr
Copy link
Member Author

patrickbkr commented May 17, 2020

@AlexDaniel: 13 days have passed. I think the two week review period is meant for people to look at this and give feedback. I think barely anyone looked at this. What shall we do?

Edit: It seems someone needs to add all the reviewers. I don't have permission to add reviewers. AlexDaniel, can you?

@lizmat
Copy link
Collaborator

lizmat commented May 17, 2020

I think (I hope I'm wrong) that @AlexDaniel is taking a break from Raku.

As an admin I will merge this tomorrow: I don't see a point in adding reviewer at this point in time, as that would only delay the process.

@patrickbkr
Copy link
Member Author

I'm fine with a review period. But someone needs to add the reviewers...

Copy link
Contributor

@jnthn jnthn left a comment

Choose a reason for hiding this comment

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

Thought I'd put an approve on this long ago; it's fine.

@jnthn jnthn merged commit dd5529c into Raku:master Jun 3, 2020
@AlexDaniel
Copy link
Member

AlexDaniel commented Jun 4, 2020

I'm fine with a review period. But someone needs to add the reviewers...

I was adding reviewers simply to generate email spam so that the reviewers are notified. You can also do that by simply tagging their names (by copying the list from https://github.com/Raku/problem-solving#reviewers). I also hope that reviewers will check the PRs at least once a month, or ideally at least once every 14 days.

@AlexDaniel is taking a break from Raku.

That is correct.

@patrickbkr patrickbkr deleted the problem-solving20 branch March 8, 2021 09:02
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.

6 participants