DPDK CI discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [dpdk-ci] [Bug 207] JS homepage TypeError with Chrome
Date: Tue, 12 Feb 2019 15:38:54 +0000	[thread overview]
Message-ID: <bug-207-149@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=207

            Bug ID: 207
           Summary: JS homepage TypeError with Chrome
           Product: lab
           Version: unspecified
          Hardware: All
                OS: All
            Status: CONFIRMED
          Severity: normal
          Priority: Normal
         Component: dashboard
          Assignee: ci@dpdk.org
          Reporter: jplsek@iol.unh.edu
                CC: jplsek@iol.unh.edu
  Target Milestone: ---

With Chrome [on Windows 10], we get a reported error of: "TypeError: Failed to
fetch" from the Javascript on the homepage.

A similar issue occurred with Firefox a while back, but I was able to reproduce
it and handle it (the error occurred when the user tried to go to a different
page in the middle of the JS requesting a page). From the users perspective,
there was no issue/difference. It was just an unnecessary exception being
thrown.

With this issue, I'm not sure if there is a difference, since I am unable to
reproduce it. It's possible that it's the same issue as above, but for Chrome.

Putting this ticket in, in case some notices it, and can hopefully report on
how to reproduce it.

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2019-02-12 15:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-12 15:38 bugzilla [this message]
2019-11-19 16:28 ` bugzilla

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-207-149@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=ci@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).