Skip to content

RamyaKappagantu/chaoss-augur-gsoc-22

Repository files navigation

Google Summer of Code - CHAOSS Microtasks

This Readme file provides the details of the microtasks that were successfully completed.

Microtask 0:

Download and configure Augur, creating a dev environment using the general cautions noted here: https://oss-augur.readthedocs.io/en/dev/getting-started/installation.html and the full documentation here: https://oss-augur.readthedocs.io/en/dev/development-guide/toc.html

Status: Downloaded and configured augur with the database schema. Microtask_0_install_success


Microtask_0_augur


Microtask_0_augur_db

Microtask 2:

Identify new issues you encounter during installation.

Status:

Error 1: Encountered an error SSL: CERTIFICATE_VERIFY_FAILED while installing required NLTK word lists for machine learning workers.

Resolution:

I'm using Python 3.7 on Mac OSX and my mac doesn't have any local certificate to validate the SSL connections. I found a file Install Certificates.command in /Applications/Python 3.7 folder and running this file in a terminal installed the certifi python package which helps in validating the SSL connections. After installing the package, it then created a symbolic link from the OpenSSL certificates file to the certificates file installed by certifi. Using this helped in resolving the SSL error and successfully install the required workers. Microtask_2_error_msg


Microtask_2_resolution


Error 2: Encountered database error No Augur API key found. while setting up augur and installing the database schema. Microtask_2_db_error


Resolution:

After the error shows up, it found out an existing key in the database and prompted if the exisiting key needs to be replaced with the new one or not. Since, that was the first time I was setting up the schema, no previous key was generated. To find out if there's any existing api_key in the database, I connected to my created augur database and ran the query: select * from "augur_operations"."augur_settings" where setting='augur_api_key'; and this query returned no rows. So, I went ahead and selected 'y' to replace the existing key and I encountered unique constraint error. Summarizing the issue, no augur api key was found in the database yet it prompted the user that an api key already exists in the database. Cleaning the build files and running make install helped in properly setting up the database schema.

Microtask 4:

Anything you want to show us. Even if you find bugs in our documentation and want to issue a PR for those!

Status:

I found the links provided for pull_request_reports.py, contributor_reports.py and augur worker links as broken and raised PR's for the same:

chaoss/community#340

chaoss/community#342

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published