Releases: legumeinfo/microservices
Releases · legumeinfo/microservices
[email protected]
- Dependency updates
[email protected]
- Dependency updates
[email protected]
- Dependency updates
[email protected]
- Dependency updates
[email protected]
- Dependency updates, including replacing the various Redis packages with most recent unified Redis package
- Used pip-tools to generated a requirements file which is now being used as a lock file the all (transitive) dependencies
- The service now verifies that the Redis database it connects to is loaded with a version of the GCV schema it is compatible with
- The service now supports setting the log level and specifying an optional log file via command-line flags and/or environment variables
- Exception handling has been made more robust
- The service now shuts down gracefully, including when a stop signal has been received or critical exception has been thrown
[email protected]
- Fixed a bug that was causing the loader to crash when it tried to load a gene that was in a gene family but wasn't itself being loaded
- Dependency updates, including replacing the various Redis packages with the most recent unified Redis package
- Used pip-tools to generated a requirements file which is now being used as a lock file for all (transitive) dependencies
- Foreign keys in RediSearch documents are now represented using tag fields instead of text fields to better support exact matching
- The loader now stores what version of the GCV schema it loaded in a Redis key as well as what schema versions it's compatible with in a Redis set
[email protected]
- Dependency updates, including replacing the various Redis packages with the most recent unified Redis package
- Used pip-tools to generated a requirements file which is now being used as a lock file the all (transitive) dependencies
- The service now verifies that the Redis database it connects to is loaded with a version of the GCV schema it is compatible with
- The service now supports setting the log level and specifying an optional log file via command-line flags and/or environment variables
- Exception handling has been made more robust
- The service now shuts down gracefully, including when a stop signal has been received or critical exception has been thrown
[email protected]
- Dependency updates, including replacing the various Redis packages with most recent unified Redis package
- Used pip-tools to generated a requirements file which is now being used as a lock file the all (transitive) dependencies
- The service now uses RediSearch tag fields for foreign key look-ups
- The service now verifies that the Redis database it connects to is loaded with a version of the GCV schema it is compatible with
- The service now supports setting the log level and specifying an optional log file via command-line flags and/or environment variables
- Exception handling has been made more robust
- The service now shuts down gracefully, including when a stop signal has been received or critical exception has been thrown
[email protected]
- Dependency updates, including replacing the various Redis packages with most recent unified Redis package
- Used pip-tools to generated a requirements file which is now being used as a lock file the all (transitive) dependencies
- The service now uses RediSearch tag fields for foreign key look-ups
- The service now verifies that the Redis database it connects to is loaded with a version of the GCV schema it is compatible with
- The service now supports setting the log level and specifying an optional log file via command-line flags and/or environment variables
- Exception handling has been made more robust
- The service now shuts down gracefully, including when a stop signal has been received or critical exception has been thrown
[email protected]
- Dependency updates, including replacing the various Redis packages with most recent unified Redis package
- Used pip-tools to generated a requirements file which is now being used as a lock file the all (transitive) dependencies
- The service now verifies that the Redis database it connects to is loaded with a version of the GCV schema it is compatible with
- The service now supports setting the log level and specifying an optional log file via command-line flags and/or environment variables
- Exception handling has been made more robust
- The service now shuts down gracefully, including when a stop signal has been received or critical exception has been thrown