search

visdesignlab / upset2

UpSet - Visualizing Intersecting Sets
https://upset.multinet.app/
BSD 3-Clause "New" or "Revised" License
54 stars 7 forks source link

error in yarn dev #122

Closed hassantarabai closed 1 year ago

hassantarabai commented 1 year ago

Hello,

I am trying to use upset2 for the first time. Installation as instructions went fine but when trying to run it with yarn dev, the browser open for a seconds, show the top of the upset2 page then produce an error. Am also getting this error on the command line: WARNING in ../../node_mo dules/multinet/dist/src/index.js Failed to parse source map from '/home/upset2/node_modules/multinet/src/index.ts' file: Error: ENOENT: no such file or directory, open '/home/upset2/node_modules/multinet/src/index.ts

I do not have a src folder that is mentioned here in my node module.

Kindly any suggestion how to resolve it ?

Thank you

kirangadhave commented 1 year ago

Hi, we have a version of upset deployed here: https://upset.multinet.app/

You can upload your own datasets on there and explore the tool. Is there a specific reason you want to run Upset locally?

hassantarabai commented 1 year ago

@kirangadhave

I tried using multinet link earlier to installation and i was getting an error "Server Error (500)". That was the main reason i wanted to get it locally.

kirangadhave commented 1 year ago

@JackWilb @JakeWags do you know why the deployed version would throw 500 server error?

JakeWags commented 1 year ago

@kirangadhave

I tried using multinet link earlier to installation and i was getting an error "Server Error (500)". That was the main reason i wanted to get it locally.

@hassantarabai Could you please try going to upset.multinet.app again? I have tried using multiple different browsers and haven't been able to replicate the 500 error. If you do get the error again, please provide steps to recreate.

hassantarabai commented 1 year ago

@kirangadhave @JakeWags

Yes the server error 500 is still there.

I go to upset.multinet.app then enter my email and password and directly after that i get the Server Error (500).

I tried with different browsers (chrome, Bing and firefox) but its same error always.

hassantarabai commented 1 year ago

@kirangadhave @JakeWags

Concerning the locally installed Upset i think i pinpointed the error to typescript as i noticed an error "rpt2: config error TS5023: Unknown compiler option 'jsxImportSource'"

JakeWags commented 1 year ago

@hassantarabai Looks like the issue is a login problem with Multinet. I've created an issue (#149) in multinet-api. I didn't have any server errors when logging in with my google account. You could try using a google account.

For local development with your own data, you need to be running the multinet system. To run the multinet system you need multinet-api, multinet-client, and multinet-js. The api and client need to be running for UpSet to run locally with Multinet.

hassantarabai commented 1 year ago

@JakeWags

Thank you for the fast support. Actually i am using my google account but today was first time i signup an account on multinet so can be related to that as you mentioned.

hassantarabai commented 1 year ago

Hello @Jakewags @kirangadhave

The error in logging in to upset2 via multinet is still persistent. I tried signing in with my gmail account, using other gmail, hotmail or institution account. I always end up with "Server error 500".

JakeWags commented 1 year ago

The error in logging in to upset2 via multinet is still persistent. I tried signing in with my gmail account, using other gmail, hotmail or institution account. I always end up with "Server error 500".

@hassantarabai Thanks for reaching out. We just pushed a change to Multinet to bypass the local login and direct straight to google account OAUTH. You should now be able to login with a google account. If you cannot, please try clearing your browser cookies and/or cache.