Skip to content

BugFix - 39399 - Unable To Launch Firefox From Playwright#3747

Merged
Maheshkale447 merged 8 commits into
Releases/Betafrom
BugFix/39399-FireFoxNotLaunched
Jun 13, 2024
Merged

BugFix - 39399 - Unable To Launch Firefox From Playwright#3747
Maheshkale447 merged 8 commits into
Releases/Betafrom
BugFix/39399-FireFoxNotLaunched

Conversation

@IamHarsimranjeet

@IamHarsimranjeet IamHarsimranjeet commented Jun 11, 2024

Copy link
Copy Markdown
Contributor

Thank you for your contribution.
Before submitting this PR, please make sure:

  • PR description and commit message should describe the changes done in this PR
  • Verify the PR is pointing to correct branch i.e. Release or Beta branch if the code fix is for specific release , else point it to master
  • Latest Code from master or specific release branch is merged to your branch
  • No unwanted\commented\junk code is included
  • No new warning upon build solution
  • Code Summary\Comments are added to my code which explains what my code is doing
  • Existing unit test cases are passed
  • New Unit tests are added for your development
  • Sanity Tests are successfully executed for New and Existing Functionality
  • Verify that changes are compatible with all relevant browsers and platforms.
  • After creating pull request there should not be any conflicts
  • Resolve all Codacy comments
  • Builds and checks are passed before PR is sent for review
  • Resolve code review comments
  • Update the Help Library document to match any feature changes

Summary by CodeRabbit

  • New Features

    • Improved error handling for browser launch failures.
    • Added logging for exceptions during driver startup.
  • Bug Fixes

    • Enhanced stability by handling missing browser executable errors.
    • Ensured proper execution of Playwright installation commands.

RC: If the firefox browser is not installed in the user's machine then Playwright is unable to launch it.
Fix: If the browser executable is not found, then execute Playwright's install command to download and install the relevant browser.
@coderabbitai

coderabbitai Bot commented Jun 11, 2024

Copy link
Copy Markdown
Contributor

Walkthrough

The recent updates enhance the robustness of the Playwright driver and the Agent operations in the Ginger framework. Key improvements include better error handling for browser executable issues and enhanced logging for driver startup errors. These changes aim to improve reliability and debugging capabilities.

Changes

File Path Change Summary
.../Playwright/PlaywrightDriver.cs Added error handling for browser executable not found, renamed a method, and introduced a new method for Playwright installation command execution.
.../AgentOperations.cs Added a try-catch block around Driver.StartDriver() and implemented error logging for exceptions.

Sequence Diagram(s)

sequenceDiagram
    participant AgentOperations
    participant Driver
    participant Logger

    AgentOperations->>Driver: StartDriver()
    alt Driver Throws Exception
        Driver-->>AgentOperations: Exception
        AgentOperations->>Logger: Log Error
    else Driver Starts Successfully
        Driver-->>AgentOperations: Success
    end
Loading
sequenceDiagram
    participant PlaywrightDriver
    participant Playwright
    participant System

    PlaywrightDriver->>Playwright: LaunchBrowserWithInstallationAsync()
    alt Browser Executable Not Found
        PlaywrightDriver->>System: ExecutePlaywrightInstallationCommand()
    end
    Playwright-->>PlaywrightDriver: Browser Instance
Loading

Poem

In the land of code, where browsers play,
A rabbit hops with changes today.
Error logs now light the way,
And drivers start without delay.
With Playwright fixed and logs so bright,
Debugging's easier, day or night.
🐰✨🚀


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between a870152 and 03334cf.

Files selected for processing (1)
  • Ginger/GingerCoreNET/Drivers/CoreDrivers/Web/Playwright/PlaywrightDriver.cs (3 hunks)
Additional context used
GitHub Check: Codacy Static Code Analysis
Ginger/GingerCoreNET/Drivers/CoreDrivers/Web/Playwright/PlaywrightDriver.cs

[warning] 156-156: Ginger/GingerCoreNET/Drivers/CoreDrivers/Web/Playwright/PlaywrightDriver.cs#L156
'System.Exception' should not be thrown by user code.

Additional comments not posted (5)
Ginger/GingerCoreNET/Drivers/CoreDrivers/Web/Playwright/PlaywrightDriver.cs (5)

14-20: Added necessary using directives to support new functionality.


27-28: Introduced a constant and a static field to manage browser executable errors and synchronize Playwright installation commands.


48-48: Renamed LaunchBrowserAsync to LaunchBrowserWithInstallationAsync to reflect the new functionality that includes handling installation.


91-111: Refactored LaunchBrowserWithInstallationAsync to handle cases where the browser executable is not found. This method now attempts to install the required browser before retrying the launch.


135-162: Added ExecutePlaywrightInstallationCommand to manage the installation of browsers. This method uses a switch statement to determine the browser type and executes the installation command accordingly. It also properly handles synchronization using AutoResetEvent.

Tools
GitHub Check: Codacy Static Code Analysis

[warning] 156-156: Ginger/GingerCoreNET/Drivers/CoreDrivers/Web/Playwright/PlaywrightDriver.cs#L156
'System.Exception' should not be thrown by user code.

int exitCode = Program.Main(new[] { "install", browserTypeString });
if (exitCode != 0)
{
throw new Exception($"Error occurred while executing playwright installation command, exited with code {exitCode}");

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Avoid throwing generic exceptions.

Consider throwing a more specific exception type or creating a custom exception class to provide more detailed error information.

- throw new Exception($"Error occurred while executing playwright installation command, exited with code {exitCode}");
+ throw new PlaywrightInstallationException($"Error occurred while executing playwright installation command, exited with code {exitCode}");

Committable suggestion was skipped due to low confidence.

Tools
GitHub Check: Codacy Static Code Analysis

[warning] 156-156: Ginger/GingerCoreNET/Drivers/CoreDrivers/Web/Playwright/PlaywrightDriver.cs#L156
'System.Exception' should not be thrown by user code.

@IamHarsimranjeet IamHarsimranjeet changed the title BugFix - 39399 - Unable To Launch Firefox From Playwright. BugFix - 39399 - Unable To Launch Firefox From Playwright Jun 11, 2024
Maheshkale447
Maheshkale447 previously approved these changes Jun 11, 2024

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 03334cf and 71f3969.

Files selected for processing (2)
  • Ginger/GingerCoreNET/Drivers/CoreDrivers/Web/Playwright/PlaywrightDriver.cs (3 hunks)
  • Ginger/GingerCoreNET/RunLib/AgentOperations.cs (1 hunks)
Additional context used
GitHub Check: Codacy Static Code Analysis
Ginger/GingerCoreNET/Drivers/CoreDrivers/Web/Playwright/PlaywrightDriver.cs

[warning] 147-147: Ginger/GingerCoreNET/Drivers/CoreDrivers/Web/Playwright/PlaywrightDriver.cs#L147
'System.Exception' should not be thrown by user code.

Additional comments not posted (3)
Ginger/GingerCoreNET/Drivers/CoreDrivers/Web/Playwright/PlaywrightDriver.cs (2)

21-21: Introduced a constant for error messages which is a good practice for maintainability.


84-104: Refactored method to handle browser installation if the executable is not found. This improves robustness and user experience by attempting an automatic fix.

Ginger/GingerCoreNET/RunLib/AgentOperations.cs (1)

202-209: Enhanced error handling in the StartDriver method by logging exceptions. This ensures that all driver start issues are properly reported, improving debuggability.

Comment on lines +128 to +148
private static void ExecutePlaywrightInstallationCommand(WebBrowserType browserType)
{
string browserTypeString;
switch (browserType)
{
case WebBrowserType.Chrome:
case WebBrowserType.Edge:
browserTypeString = Microsoft.Playwright.BrowserType.Chromium;
break;
case WebBrowserType.FireFox:
browserTypeString = Microsoft.Playwright.BrowserType.Firefox;
break;
default:
throw new ArgumentException($"Unknown browser type '{browserType}'");
}

int exitCode = Program.Main(new[] { "install", browserTypeString });
if (exitCode != 0)
{
throw new Exception($"Error occurred while executing playwright installation command, exited with code {exitCode}");
}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Replace generic exception with a more specific type to improve error handling.

- throw new Exception($"Error occurred while executing playwright installation command, exited with code {exitCode}");
+ throw new PlaywrightInstallationException($"Error occurred while executing playwright installation, exited with code {exitCode}");

Committable suggestion was skipped due to low confidence.

Tools
GitHub Check: Codacy Static Code Analysis

[warning] 147-147: Ginger/GingerCoreNET/Drivers/CoreDrivers/Web/Playwright/PlaywrightDriver.cs#L147
'System.Exception' should not be thrown by user code.

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