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

devops(tooling): Fix path to README.md in driver downloader #2992

Closed

Conversation

RenderMichael
Copy link
Contributor

I followed the directions in CONTRIBUTING.md and ran ./build.sh --download-driver.

When it ran dotnet run --project ./src/tools/Playwright.Tooling/Playwright.Tooling.csproj -- download-drivers --basepath . I got this following exception:

WARNING: Could not update the browser versions in the README file.
This is usually due to the readme file not yet existing for 1.46.0.
Could not find a part of the path 'D:\Code\RenderMichael\playwright\README.md'.

This fixes the issue for me. I assume it hasn't been hit before because everyone else also has the upstream playwright project as well.

I followed the directions in `CONTRIBUTING.md` and ran `./build.sh --download-driver`.

When it ran `dotnet run --project ./src/tools/Playwright.Tooling/Playwright.Tooling.csproj -- download-drivers --basepath .` I got this following exception:

```bash
WARNING: Could not update the browser versions in the README file.
This is usually due to the readme file not yet existing for 1.46.0.
Could not find a part of the path 'D:\Code\RenderMichael\playwright\README.md'.
```

This fixes the issue for me. I assume it hasn't been hit before because everyone else also has the upstream `playwright` project as well.
@mxschmitt
Copy link
Member

This would end being a noop, since it would read from the same README.md like it writes it to.

We could add a flag like --update-readme and only use this flag internally when rolling a new version via ./build.sh --roll 1.46.0.

@RenderMichael
Copy link
Contributor Author

Ah got it. Sorry I didn't look closely enough at what the code was doing. My bad.

I can add a flag for that, or to avoid disruptions to flow I can add the inverse --no-update-readme flag, and add guidance to use that in CONTRIBUTING.md. Whatever y'all think is best.

@mxschmitt
Copy link
Member

I'll close it since it seem stale. Its just a non-user facing warning, so I think we don't need to perform any action. We could change the text of it if you are interested in making it more clear.

@mxschmitt mxschmitt closed this Nov 5, 2024
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.

2 participants