Skip to content

PR to resolve Issue #133#134

Merged
gustavodemorais merged 8 commits intoHTTP-APIs:developfrom
PrathamDogra:pratham-dev
Feb 5, 2020
Merged

PR to resolve Issue #133#134
gustavodemorais merged 8 commits intoHTTP-APIs:developfrom
PrathamDogra:pratham-dev

Conversation

@PrathamDogra
Copy link
Copy Markdown
Contributor

Fixes #

Checklist

  • My branch is up-to-date with upstream/develop branch.
  • Everything works and tested for Python 3.5.2 and above.

Description

This PR resolves Issue #133

Change logs

Due to upgradation of pip we were getting error while python3 setup.py install as pip.req changed to pip._internal.req and the way we import the dependencies from the requirements.txt has changed. This PR resolves this issue.

Mec-iS and others added 7 commits July 8, 2019 17:18
* Adding python-socketio to requirements

* Sending correct parameter to GraphOperations

* Adding Socket to Agent and Defining sync Rules

* Adjusting Docstrings

* Adjusting tests to Mock Socket Connect

* Typo and Coding Standards

* Removing unused import and leftover comment

* Restart Agent when it's too outdated

* Adding Docstrings

* Better naming and PEP8

* Receiving updates through socket packages

* Connecting to hydrus

* Updating Test Doc with changes from Hydra Core

* Changing socket URL to use hydrus URL by default

* Modifying empty modification table check to status code

* Migrating from HTTP Table-Diff to Socket packages

* Changing connection/reconnecting method using socket data

* Adjusting Redis Graph Docker Hub Image

* Dealing with warning use cases

* Adjusting Agent's gitignore

* Adjusting Agent's Graph Initialization routine 

That way the function can also be used to provide the ApiDoc to the GUI

* Formatting embedded resources link and adjusting tests
* Adding python-socketio to requirements

* Sending correct parameter to GraphOperations

* Adding Socket to Agent and Defining sync Rules

* Adjusting Docstrings

* Adjusting tests to Mock Socket Connect

* Typo and Coding Standards

* Removing unused import and leftover comment

* Restart Agent when it's too outdated

* Adding Docstrings

* Better naming and PEP8

* Receiving updates through socket packages

* Connecting to hydrus

* Updating Test Doc with changes from Hydra Core

* Changing socket URL to use hydrus URL by default

* Modifying empty modification table check to status code

* Migrating from HTTP Table-Diff to Socket packages

* Changing connection/reconnecting method using socket data

* Adjusting Redis Graph Docker Hub Image

* Dealing with warning use cases

* Adjusting Agent's gitignore

* Adjusting Agent's Graph Initialization routine 

That way the function can also be used to provide the ApiDoc to the GUI

* Formatting embedded resources link and adjusting tests

* Documentation major update (HTTP-APIs#128)

* Adding small summary

* Updating installation instructions

* Updating description

* Changing order, writing, layout and Porting details to internal README

* Adjusting  redis_setup comments writing
Organization has moved from gitter to slack.
Copy link
Copy Markdown
Contributor

@gustavodemorais gustavodemorais left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Everything looks good to me. Gj 👍

* Read this [how-to about writing a PR](https://github.com/blog/1943-how-to-write-the-perfect-pull-request) and this [other how-to about writing a issue](https://wiredcraft.com/blog/how-we-write-our-github-issues/)

* **first ask in chat**: if you find a problem, first ask for [help in the chat](https://gitter.im/HTTP-APIs/Lobby), then consider opening a issue.
* **first ask in chat**: if you find a problem, first ask for [help in the chat](https://hydraecosystem.slack.com/), then consider opening a issue.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A good addition here would be: first ask in chat and search previous issues

Copy link
Copy Markdown
Contributor Author

@PrathamDogra PrathamDogra Feb 2, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Guttz, if you want then I can change that in my branch pratham-dev and have them in this PR.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup, that's what I would recommend. It's not exactly related to the PR but I would appreciate if you did so (: Thx

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants