-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OPENC3_CLOUD environment variable is required (RuntimeError), when building Bridge support in OpenC3\COSMOS #304
Comments
Will better document this and probably make OPENC3_CLOUD have a default value so it will always run for bridges. |
We are also facing a similar issue while trying the bridge solution for the serial port Is there any workaround we can use?, any guidance or HeadsUp on this topic would be highly appreciable since we are students and not well versed with this software! |
Create an environment variable called OPENC3_CLOUD and set it to ‘local’. |
Thanks Jason for your response! I have tried setting the environment variable OPENC3_CLOUD to local but I came across an error with the local_bucket.rb file, although local_bucket.rb is present in the ...cosmos\openc3\lib\openc3\utilities Following is the error message while executing cmd: ruby cosmos/openc3/bin/openc3cli Thanks for your support! |
On unix: No quotes around local. |
Thanks a lot! I am finally up and running!
greetings, Jurgen |
Describe the bug
See issue, #285 that deals with the exact same error, but for the
OpenC3/COSMOS-project
way of installing building and running COSMOS, not theOpenC3/COSMOS
way as is the case here:To Reproduce
C:/openc3/openc3/lib/openc3/utilities/bucket.rb:23:in
getClient': OPENC3_CLOUD environment variable is required (RuntimeError) from ./openc3/bin/openc3cli:47:in
'The previous solution was using an updated OpenC3.bat
Can I safely use the openc3.bat from
OpenC3/COSMOS-project
version 5.1.1 (latest stable) to continue or does this open a new can of worms?Environment (please complete the following information):
Author: ryanmelt [email protected] 2022-11-19 04:19:28
Tags: v5.1.1
The text was updated successfully, but these errors were encountered: