Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / va-big-data-genomics/trellisdata issues and pull requests
#9 - Investigate neo4j.Record: can be used to split results?
Issue -
State: open - Opened by pbilling over 1 year ago
- 4 comments
#8 - Moving from unittest to pytest
Issue -
State: open - Opened by pbilling over 1 year ago
Labels: Design
#7 - Should I update QueryResponse to support multiple relationships?
Issue -
State: open - Opened by pbilling over 1 year ago
Labels: Design
#6 - Refactor message classes to be more intuitive
Issue -
State: open - Opened by pbilling over 1 year ago
- 16 comments
Labels: enhancement, Design
#5 - JobRequest: Figure out how to handle different patterns: unconnected nodes vs related nodes.
Issue -
State: open - Opened by pbilling over 1 year ago
- 11 comments
#4 - Create a JobRequest trellisdata class for job requests handled by job-launcher function
Issue -
State: open - Opened by pbilling over 1 year ago
- 3 comments
Labels: enhancement
#3 - AttributeError: 'DatabaseQuery' object has no attribute 'job_request'
Issue -
State: closed - Opened by pbilling about 2 years ago
- 1 comment
Labels: bug
#2 - Create a JobLauncher trellisdata class
Issue -
State: open - Opened by pbilling about 2 years ago
- 2 comments
Labels: enhancement
#1 - Only include result of Query in operation graph if published to triggers
Issue -
State: closed - Opened by pbilling over 2 years ago
- 1 comment
Labels: enhancement