BIDMCDigitalPsychiatry / LAMP-platform

The LAMP Platform (issues and documentation).
https://docs.lamp.digital/
Other
12 stars 10 forks source link

Dashboard-staging TypeError when entering domain name #740

Closed carlan1 closed 1 year ago

carlan1 commented 1 year ago

There is a TypeError that occurs when attempting to enter a server address in dashboard-staging:

Screen Shot 2023-03-09 at 9 11 05 AM

Note that this error does not occur every time. Therefore it might be difficult to consistently reproduce. Usually, it does not occur on the first attempt to enter a server address, and only occurs after logging out and during subsequent log-in attempts.

ZCOEngineer commented 1 year ago

@carlan1 we shall check this

sarithapillai8 commented 1 year ago

@carlan1 We have updated the changes in dashboard-staging. Could you please check and let us know whether this issue is fixed or not?

carlan1 commented 1 year ago

Although the TypeError is no longer present, there are now instance of the following error: (also applicable when clicking on "server address" to enter a domain)

Screen Shot 2023-03-14 at 3 12 23 PM
ZCOEngineer commented 1 year ago

@carlan1, @sarithapillai8 is checking this.

sarithapillai8 commented 1 year ago

@carlan1 Could you please retest? we have updated the fix in staging.

carlan1 commented 1 year ago

Appears fixed in dashboard-staging

carlan1 commented 1 year ago

Unfortunately the Minified react error has returned when entering a domain name in dashboard-staging

sarithapillai8 commented 1 year ago

@carlan1 We are unable to reproduce the issue. Could you try after clearing cache?

carlan1 commented 1 year ago

Will clearing the cache fix the issue permanently? Or, going forward, will users encounter this issue frequently and have to clear the cache frequently to fix it?

sarithapillai8 commented 1 year ago

@carlan1 There is no need to clear the cache frequently. We wanted to confirm whether it appears after clearing cache in your system as we are not able to reproduce it.

carlan1 commented 1 year ago

Clearing the cache fixes the issue for me, at least for now.

If clearing the cache is a permanent fix, then we can close the issue

michaelmenon commented 1 year ago

Ok thanks if you get it again please let us know as this was already fixed and wanted to check if you get it after clearing the cache.