Skip to content
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

Epic: Enable secure, friction-less & reproducible bug reports #444

Open
13 tasks
Tracked by #536
lukekarrys opened this issue Mar 17, 2022 · 3 comments
Open
13 tasks
Tracked by #536

Epic: Enable secure, friction-less & reproducible bug reports #444

lukekarrys opened this issue Mar 17, 2022 · 3 comments
Labels

Comments

@lukekarrys
Copy link
Contributor

lukekarrys commented Mar 17, 2022

We want to accomplish two things:

  1. Not make it necessary to run code on local machines to triage bug reports
  2. Lower the friction for reporters (and maintainers) to create fully encapsulated and reproducible bug reports

Ideas

  • A workspace or separate repo that has the following:
    • Template repository (or just forkable)
    • Minimal tools and templated files for common tasks (managing node versions, npm versions, asserting behavior)
      • package.json
      • nvm
      • tap
      • run npm from source via a registry tarball
    • devcontainer.json for codespace settings
    • Github action workflows that run CI for requested os/version matrix
  • Update bug report with instructions for creating VM/codespace
  • Encapsulate all this in an npx-able bin (npx @npmcli/bug-report --npm 8.5.3 --node 16 ?)

Caveats

@nlf
Copy link

nlf commented Mar 17, 2022

another thing to note here is that codespaces are linux only. virtual machines are nearly trivial for linux guests too. windows and osx, on the other hand, are one or more of: surprisingly slow, annoying to setup, requires the host os to be the same as the guest.

i wonder if we could use github actions for this?

@lukekarrys
Copy link
Contributor Author

another thing to note here is that codespaces are linux only...i wonder if we could use github actions for this?

that's what i was thinking too, and was attempting to describe above. i don't see codespaces as strictly necessary, but just as the easiest way to go from browser -> running the cli. then whatever gets created in a codespace would be run via a github action that would be similar to our ci.yml but with some extra debugging steps like cat debug.log, etc

@ljharb
Copy link

ljharb commented Mar 18, 2022

Also repl.it might be useful (or runkit, if it offered a way to prepopulate the code snippet)

@darcyclarke darcyclarke mentioned this issue Mar 23, 2022
32 tasks
@darcyclarke darcyclarke changed the title Epic: enabling secure and friction-less reproducible bug reports Epic(bugs): enabling secure and friction-less reproducible bug reports Mar 23, 2022
@darcyclarke darcyclarke changed the title Epic(bugs): enabling secure and friction-less reproducible bug reports Epic: enabling secure and friction-less reproducible bug reports Mar 23, 2022
@darcyclarke darcyclarke changed the title Epic: enabling secure and friction-less reproducible bug reports Epic: Enable secure, friction-less & reproducible bug reports Mar 23, 2022
@darcyclarke darcyclarke mentioned this issue Aug 22, 2022
46 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants