Skip to content
This repository has been archived by the owner on Nov 8, 2021. It is now read-only.

Unable to launch ROS #413

Closed
joelbourbon opened this issue Feb 13, 2019 · 8 comments
Closed

Unable to launch ROS #413

joelbourbon opened this issue Feb 13, 2019 · 8 comments
Assignees

Comments

@joelbourbon
Copy link

joelbourbon commented Feb 13, 2019

Goals

Install ROS on a brand new VM on Azure.

Expected Results

Able to start the server after a fresh install following this guide.

Actual Results

> [email protected] start /home/(redacted)/realm/realm-mobile-server
> npm run build && node dist/index.js

> [email protected] build /home/(redacted)/realm/realm-mobile-server
> rm -rf dist; ./node_modules/.bin/tsc

node_modules/@types/node/index.d.ts(75,15): error TS2300: Duplicate identifier 'SharedArrayBuffer'.
node_modules/typescript/lib/lib.es2017.sharedmemory.d.ts(24,11): error TS2300: Duplicate identifier 'SharedArrayBuffer'.
node_modules/typescript/lib/lib.es2017.sharedmemory.d

Steps to Reproduce

https://docs.realm.io/server/installation/manual-install#manual-install

Version of Realm and Tooling

  • Realm Object Server Version: 3.18.3
  • Flavor: Self-hosted
  • Server OS & Version: Ubuntu 18.04.2 LTS
  • Client SDK Version: N/A
  • Client OS & Version: N/A

NB: I did the exact same thing last week and it worked. Something apparently changed in the last version of ROS.

@realm-probot
Copy link

realm-probot bot commented Feb 14, 2019

Hey - looks like you forgot to add a T:* label - could you please add one?

@roberhofer
Copy link

@fealebenpae : can you confirm whether this is addressed in the 3.18.4 release?
Seem that Ian had issues installing on his laptop as well.

@joelbourbon
Copy link
Author

Hi @roberhofer,

Thanks for the prompt reply.

I just tested updating ROS to the latest (3.18.4), wiped my project et re-initialized it: same results.
Also tested on a brand new VM with the latest version: same results.

I deployed your solution last week on another VM and everything was great.
Don't hesitate to contact me if you want me to test something.

Thanks,

@fealebenpae
Copy link
Member

Hey @joelbourbon - you can fix this by opening tsconfig.json and deleting esnext from the lib array. We'll be sure to fix this in a new release.

@joelbourbon
Copy link
Author

Thank @fealebenpae! It worked!

I hope you find a way to fix that in your next release 😄

@realm-probot
Copy link

realm-probot bot commented Feb 14, 2019

Hey - looks like you forgot to add a T:* label - could you please add one?

@ayushprashar
Copy link

@fealebenpae I tried doing the same and it resulted in an error message that the feature token is invalid.

@joelbourbon
Copy link
Author

@ayushprashar you forgot to do one step: https://docs.realm.io/server/installation/manual-install#1-add-your-feature-token

cmelchior added a commit to realm/realm-java that referenced this issue Feb 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants