blythed
blythed
@kartik4949 @jieguangzhou to provide ideas/ feedback on how to design workflow file. https://github.com/blythed/superduper/tree/feature/plugins Difficulty: finding a precise diff so that only changed plugins are detected and tested.
- [x] #2299 - [x] #2300 - [x] #2320 - [x] #2301 - [x] #2302 - [x] #2303 - [ ] #2304 - [x] #2315 - [x] #2346
- [x] #2257 - [ ] #2329 - [x] https://github.com/superduper-io/superduper/issues/2336 - [x] #2344
If a developer changes a component, whether by configuration file (JSON/ YAML) or by performing surgery on a python object's attributes, these changes should be handled in a way which...
- Every plugin gets its own `pip` destination - Credentials for each plugin - Guide for developers - Workflow file triggered when keywords in commit message
- [x] #2242 - [x] #2345 - [x] #2243 - [x] #2244 - [x] #2245 - [x] #2296 - [x] #2347 - [x] #2370 - [x] #2382 - [ ]...
Design to be provided.
Following this design somewhat: https://github.com/blythed/superduper/tree/feature/plugins
- [ ] Caching of environment - [ ] Making base testing environment faster - [ ] Make sure workflow triggered only when needed - [ ] Make sure workflow...
https://github.com/SuperDuperDB/superduper-services - compute - servers - cdc - scheduler - rest - vector-search - cronjobs - ... This task is basically finished, but there is unnecessary clutter in both `superduper`...