-
Notifications
You must be signed in to change notification settings - Fork 99
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
[Bug]: Unhandled exception. CarbonAware.Exceptions.ConfigurationException: No data sources are configured #426
Comments
This issue has not had any activity in 120 days. Please review this issue and ensure it is still relevant. If no more activity is detected on this issue for the next 20 days, it will be closed automatically. |
Please keep this issue while #450 is opened. See comments from me in above. |
This issue has not had any activity in 120 days. Please review this issue and ensure it is still relevant. If no more activity is detected on this issue for the next 20 days, it will be closed automatically. |
Wait! As I said before, I will start to work for this issue after #450 . |
This issue has not had any activity in 120 days. Please review this issue and ensure it is still relevant. If no more activity is detected on this issue for the next 20 days, it will be closed automatically. |
Sorry for the late for working of this issue. Now I'm working on #450, we have to configure datasource in any cases because CASDK act like an API gateway - it means the SDK should have datasource(s). The error should be reported if datasource is not configured because the SDK would not return the value which the user does not expect. I believe #450 would be merged soon. I close this issue after #450. |
Contact Details
[email protected]
What happened?
First attempt at running
.\caw.exe -h
(as per docs) and received error message.Prior actions:
dotnet publish ./src/CarbonAware.CLI/src/CarbonAware.CLI.csproj -c Release -o [outputPath]
.\ caw.exe -h
fromoutputPath
Full error log:
client
CLI
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: