data-warehouse

Description: There is no issue template so when someone wants to create an issue there is no section and it can be limiting to properly explain the issue

Desired Behaviour: Create different sections of issues like a bug report, feature request, and questions. Then populate each section to serve as a template for anyone creating an issue.
An example of the content for a bug report:

especially for less obvious but lengthy code snippets!

Sending a rest call to delete a job specification throws 404 where as grpc call works fine. Steps to reproduce

curl -X DELETE "http://localhost:9100/v1/project/my-project/namespace/kush/helloworld" -H  "accept: application/json"

Support copy into queries

https://docs.gethue.com/developer/api/cli/

TODO:

• Auth:
  • On auth, auto select SQL and storage connectors if only one, or select from the list
  • Remember last value used: e.g. dialect/connector, propose last api URL/login as default when relogin..
• Query: select dialect, execute a custom statement reusing Notebook Python lib
• Storage: download, upload

What is the feature request? What problem does it solve?

As employees leave the organization/company or users change mails , eventually the notification list configured for the job would start containing a lot of invalid mails. This causes issues with SMTP relay (e.g postfix) which could be buffering all invalid requests until the queu is full, which cause all mails coming for all jobs to b

When trying to modify a scenarios with a solution, it throws an error saying:

at.ac.iiasa.ixmp.exceptions.IxExceptionPyRaisable: at.ac.iiasa.ixmp.exceptions.IxException: This Scenario has elements in a variable or equation! Use 'removeSolution()' or clone(False)'before editing!

removeSolution() is deprecated. Actual name is remove_sol().