Updates on Issues
At this stage of the project, I have received updates on issues, and have some thoughts on how to write pull requests to solve most issues.
IBM Issue
This issue is about creation of a customized jinja tag to insert a specific markdown content header. I have found two useful tutorials, https://github.com/dldevinc/jinja2-simple-tags and https://michaelabrahamsen.com/posts/jinja2-custom-template-tags/. With customized tag, the Python library jinja can have new functionality unique to your own project.
This issue is pretty similar to what we did about static site generator for generating a complete HTML web site from raw data and files. Jinja doesn't have the functionality that IBM wants. So this issue is about to create a jinja annotation for developers to use.
I have left the comment below this issue and communicated with the project maintainer. Turned out that, even though this issue currently shows open on the board, it actually was being fixed in another issue.
In this case, I was not be able to get this issue assigned to me.
Microsoft Issue
This issue[https://github.com/microsoft/qlib/issues/691] is a bug fixing issue for qlib. The module_path is wrong. This is a pretty simple issue. After contacting the project maintainer, it turned out this issue has been resolved in another issue as well. So that I couldn't get a chance to work on it as well.
Telescope Issues
Telescope issue - 01:
This issue[https://github.com/Seneca-CDOT/telescope/issues/2521] is about to fix the backend end point url. Now the url has ":4000" inside, and it's expected to be changed into "/deploy" to the places where we are acting as a consumer of the deploy routes vs. defining them.
Telescope issue - 02:
This issue[https://github.com/Seneca-CDOT/telescope/issues/2511] is to fix a bug of an uncaught type error.
Top comments (0)