GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Test failed: Phantomas failed: Navigation timeout of 120000 ms exceeded · Issue #408 · YellowLabTools/YellowLabTools

Test failed: Phantomas failed: Navigation timeout of 120000 ms exceeded #408

New issue
Copy link
New issue
Copy link
Open
Open
Test failed: Phantomas failed: Navigation timeout of 120000 ms exceeded#408
Copy link

Description

@dennis-ryan
dennis-ryan
opened on Mar 13, 2024
Issue body actions

seeing this error on a few sites (i.e. jcrew.com, coach.com): Phantomas failed: Navigation timeout of 120000 ms exceeded

Activity

  1. SamiFala commented on Mar 13, 2024

    @SamiFala
    SamiFala
    on Mar 13, 2024
    More actions

    Same here on my website green-id.dev

  2. gmetais commented on Mar 13, 2024

    @gmetais
    gmetais
    on Mar 13, 2024
    Collaborator
    More actions

    Thanks for submitting the issues.

    Regarding green-id.dev, I notice there's a pending HTTP request in my browser:
    image

    When adding api.meexr.fr to the YLT block list setting, the test works.

    Unfortunately I didn't find any similar root cause for jcrew.com or coach.com for the moment.

  3. SamiFala commented on Apr 3, 2024

    @SamiFala
    SamiFala
    on Apr 3, 2024
    More actions

    Hello @gmetais thanks for your reply!

    I modified a bit the source code from apiController.js to add manually my api url 'api.meexr.fr' to the blocking domain at every runs : req.body.blockDomain = "api.meexr.fr";

    To give more context of how I use ylt in private instance
    I've built an API that communicates with YLT to grab source code evaluation and I use this to give an 'eco-score' to the websites through a badge inserted into footers of websites (this is the script mentioned above badge.min.js).

    My question now is why do you think this api domain is blocked (I mean in pending) ? My hypothesis is a recursive call of YLT tests on the same page.

  4. rodrigoalcarazdelaosa commented on May 11, 2024

    @rodrigoalcarazdelaosa
    rodrigoalcarazdelaosa
    on May 11, 2024
    More actions

    Same issue with https://blowfish.page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402520 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.