Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

frontend UI error on a fresh install

See original GitHub issue

On a fresh installation with docker, once I connect to the frontend UI, I get the following error:

We encountered an error
SyntaxError: Unexpected token < in JSON at position 2

Where can I look for it? I used the commit from last week, before the jaas was added.

The error is appearing directly on the UI, it’s not from the frontend logs.

This is from the frontend log:

wherehows-frontend_1       | 2018-08-04 02:38:25 INFO  application:114 - Creating DAO factory: wherehows.dao.DaoFactory
wherehows-frontend_1       | 2018-08-04 02:38:27 ERROR application:257 - Piwik site ID must be an integer
wherehows-frontend_1       | 2018-08-04 02:38:31 ERROR application:257 - Piwik site ID must be an integer
wherehows-frontend_1       | 2018-08-04 02:38:31 ERROR application:257 - Piwik site ID must be an integer
wherehows-frontend_1       | 2018-08-04 02:38:35 ERROR application:216 - 
wherehows-frontend_1       | 
wherehows-frontend_1       | ! @78ngoe5f2 - Internal server error, for (GET) [/api/v2/platforms] ->
wherehows-frontend_1       |  
wherehows-frontend_1       | play.api.UnexpectedException: Unexpected exception[UnsupportedOperationException: Operation not implemented]
wherehows-frontend_1       |    at play.api.http.HttpErrorHandlerExceptions$.throwableToUsefulException(HttpErrorHandler.scala:261) ~[com.typesafe.play-play_2.10-2.4.11.jar:2.4.11]
wherehows-frontend_1       |    at play.api.http.DefaultHttpErrorHandler.onServerError(HttpErrorHandler.scala:191) ~[com.typesafe.play-play_2.10-2.4.11.jar:2.4.11]
wherehows-frontend_1       |    at play.api.GlobalSettings$class.onError(GlobalSettings.scala:179) [com.typesafe.play-play_2.10-2.4.11.jar:2.4.11]
wherehows-frontend_1       |    at play.api.DefaultGlobal$.onError(GlobalSettings.scala:212) [com.typesafe.play-play_2.10-2.4.11.jar:2.4.11]
wherehows-frontend_1       |    at play.api.http.GlobalSettingsHttpErrorHandler.onServerError(HttpErrorHandler.scala:94) [com.typesafe.play-play_2.10-2.4.11.jar:2.4.11]

Issue Analytics

State:
Created 5 years ago
Comments:11 (1 by maintainers)

Top GitHub Comments

2reactions

arthur78commented, May 10, 2019

I switched to v1.0.0 tag and could log in.

Here’s the list of things I also did:

created ~/.bowerrc file and added into it: {"allow_root": true, "registry": "https://registry.bower.io"} otherwise the sudo ./build.sh 1 was failing
created a test user within a mysql container: INSERT INTO wherehows.users (name, email, username, password_digest, password_digest_type, authentication_type) VALUES ('test', 'test@email.com', 'test', SHA1('test'), 'SHA1', 'default')
modified wherehows-docker/wherehows-frontend/Dockerfile, added: ENV JAVA_OPTS -Djava.security.auth.login.config=/application/conf/jaas.conf

0reactions

keremsahin1commented, Dec 20, 2019

Dear issue owner,

Thanks for your interest in WhereHows. We have recently announced DataHub which is the rebranding of WhereHows. LinkedIn improved the architecture of WhereHows and rebranded WhereHows into DataHub and replaced its metadata infrastructure in this direction. DataHub is a more advanced and improved metadata management product compared to WhereHows.

Unfortunately, we have to stop supporting WhereHows to better focus on DataHub and offer more help to DataHub users. Therefore, we will drop all issues related to WhereHows and will not accept any contribution for it. Active development for DataHub has already started on datahub branch and will continue to live in there until it’s finally merged to master and project is renamed to DataHub.

Please check the datahub branch to get familar with DataHub.

Best, DataHub team