search

bcgov / entity

ServiceBC Registry Team working on Legal Entities
Apache License 2.0
23 stars 59 forks source link

NR UI throws console errors while navigating. #17734

Open riyazuddinsyed opened 1 year ago

riyazuddinsyed commented 1 year ago

Describe the bug in the current situation When the user files for an NR and in the console there are a lot of console error logs.

Steps to reproduce the behavior:

  1. Go to 'https://dev.names.bcregistry.gov.bc.ca/?accountid=2079'
  2. Try filing an NR
  3. Open the Console
  4. See error

Private Zenhub Image

jdyck-fw commented 1 year ago

This is being thrown by the Maximus webchat

severinbeauvais commented 1 year ago

I also note a message in the screenshot above suggesting that Riyaz's network was up and down (changed).

@davemck513 I have a concern about the Maximus webchat scripts. Here's another example of console messages right now in Dev:

Private Zenhub Image

These are new messages. The above strongly suggests that Maxiumus has been changing their scripts without letting us know. This was a risk that we identified a few months ago (since we reference their external scripts). And here we are.

There seems to be no impact to Dev other than lots of useless (to us) console messages, but what about Test and Prod? Will Maximus change the scripts there, after we've already testing everything? Are the scripts intermittently broken there, or generating a lot of messages, or impacting network traffic differently than what we saw initially? Who knows? And who should check that? And how often?

Ideally, Maximus would not change their scripts without letting us know beforehand. And the scripts we use would remain "clean" instead of extremely verbose as above.

severinbeauvais commented 1 year ago

I just had a look at https://www.names.bcregistry.gov.bc.ca/. It shows a ton of console messages as above.

There's a small possibility that Chrome was updated and shows new messages, but I'm not sure.

severinbeauvais commented 1 year ago

There were a couple of recent Chrome updates recently: https://chromereleases.googleblog.com/2023/09/

However, I am usually very quick to update my version of Chrome, and I did not see these errors yesterday (and the most recently update was Sep 12 -- the day before yesterday).