Setup Replay recording on CI

[Andarist]

• add a test workspace for this
• add its workspace API key here as REPLAY_API_KEY secret

I tested what I could locally (including uploading the recordings to a sample throwaway workspace).

Note that we can see in the logs things like:

[replay.io]: Failed to add annotation
[replay.io]: Error: page.evaluate: Execution context was destroyed, most likely because of a navigation
[replay.io]: Failed to add annotation
[replay.io]: Error: page.evaluate: Target closed

It works regardless of that. Most likely the offending code is here - but fixing this properly requires further investigation.

[vercel]

@Andarist is attempting to deploy a commit to the Replay Team on Vercel.

To accomplish this, @Andarist needs to request access to the Team.

Afterwards, an owner of the Team is required to accept their membership request.

If you're already a member of the respective Vercel Team, make sure that your Personal Vercel Account is connected to your GitHub account.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@playwright/[email protected]	None	0	25.3 kB	aslushnikov
npm/@replayio/[email protected]	environment, filesystem Transitive: eval, network, shell	+126	9.84 MB	ryanjduffy
npm/[email protected]	Transitive: environment, eval, filesystem, network, shell, unsafe	+1	9.99 MB	aslushnikov

🚮 Removed packages: npm/@playwright/[email protected], npm/[email protected]

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source
Install scripts	npm/@replayio/[email protected]	Install script: postinstall Source: yarn run if:dist -- node ./bin.js first-run	package.json pnpm-lock.yaml

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/@replayio/[email protected]

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
dashboard	✅ Ready (Inspect)	Visit Preview	Apr 16, 2024 3:24pm

[Andarist]

@bvaughn it would be good to have a way to cache replay chromium on CI - we don't make it easy rn to do this. Do you have any opinions on how we could make it happen?

It would be cool if the user wouldn't have to worry about the location that has to be cached. Right now the return value of getRuntimesDirectory in the new CLI varies based on some env variables etc - so I guess we'd have to expose this logic somehow through the CLI (a new command?).

On top of that, we need a stable cache key - that would be what replayio returns (but in a machine-readable format): buildId + forkedVersion (or smth like that).

That means the user would have to invoke replayio twice - it isn't super great but probably OK here.

[bvaughn]

Error: ENOENT: no such file or directory, rename '/home/runner/.replay/runtimes/chrome-linux/replay-chromium' -> '/home/runner/.replay/runtimes/chrome-linux/chrome-linux'

The most recent CLI failure is related to behavior we mimicked from the legacy CLI (without understanding why) replayio/replay-cli@6d9b8b9#r140402329

[Andarist]

It's alive and working :)

[bvaughn]

Awesome!