search

projectcypress / cypress

An open source tool for testing electronic Clinical Quality Measure calculation
http://www.healthit.gov/cypress
Apache License 2.0
84 stars 52 forks source link

exception class/object expected on /lib/cypress/js_ecqm_calc.rb:44:in `raise' version cypress 4.0.2 #1115

Open Basaveswarr opened 5 years ago

rbclark commented 5 years ago

Could you provide more information about how you have installed Cypress and what you did to see this error?

Basaveswarr commented 5 years ago

Hello robert, I have installed the cypress using VM. I downloaded the VM from github and uploaded to my AWS S3 and from there I imported as AMI using VM-Import and hosted it in AWS. image

rbclark commented 5 years ago

Could you verify the instance type that the imported VM has on AWS? Also please note that we have an AWS VM that we provide for Cypress v4.0.1. If you install the Cypress v4.0.1 VM you can then upgrade it using the upgrade instructions provided on our wiki which may provide you with an easier experience for getting cypress up and running in AWS.

Basaveswarr commented 5 years ago

Its t2-small. While we are using the AMI of cypress we encountered with error. So thats why we used this method to do so. The version we are using now is 4.0.2

rbclark commented 5 years ago

Just to clarify, did you receive the same error when using the provided AMI or a different error?

Basaveswarr commented 5 years ago

We are not able to host from the ami. Actually the guy who hosted this is no more with us. So at present we are having this issue.

rbclark commented 5 years ago

Can you try upgrading the type to a t2-large, reboot and see if that works? I believe this is a case of the VM not having enough resources to handle running all of cypress.

Basaveswarr commented 5 years ago

sure I will try.

On Thu, Mar 7, 2019 at 10:26 AM Robert Clark notifications@github.com wrote:

Can you try upgrading the type to a t2-large, reboot and see if that works? I believe this is a case of the VM not having enough resources to handle running all of cypress.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/projectcypress/cypress/issues/1115#issuecomment-470569963, or mute the thread https://github.com/notifications/unsubscribe-auth/AuA2f8lwsud-zKS56MOOfjP66fVTbiILks5vUS-9gaJpZM4belCB .

-- Thanks & Regards, Basaveswar Rao Ramu, AWS Administrator, bramu@edaris.com bramu@edaris.com .

rbclark commented 5 years ago

@Basaveswarr just wanted to check in and see if this worked for you?

Basaveswarr commented 5 years ago

No robert, It doesn't work.

On Tue, Mar 19, 2019 at 9:02 AM Robert Clark notifications@github.com wrote:

@Basaveswarr https://github.com/Basaveswarr just wanted to check in and see if this worked for you?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/projectcypress/cypress/issues/1115#issuecomment-474354466, or mute the thread https://github.com/notifications/unsubscribe-auth/AuA2fx9j6w68FGKjJaJQpcWm5bxKE2Nbks5vYN_agaJpZM4belCB .

-- Thanks & Regards, Basaveswar Rao Ramu, AWS Administrator, bramu@edaris.com bramu@edaris.com .

rbclark commented 5 years ago

Could you elaborate on the error that was encountered previously from trying to use the AMI? Our AMI build is a supported method that should work, converting an AMI to a VM is completely untested by us and also might open you up to other issues. For example the VM is built with a default username and password login over SSH, meaning there is a chance anyone can SSH into your VM -> AMI conversion. This is not the case with the public AMI.