Waiting for QuackDB the OSS spin off any second now
I've already created Haybarn which is Query.Farm's distribution of DuckDB:
learn about it here: https://query.farm/haybarn/
If my extension shows as "build failed" on https://query.farm/haybarn/status/v1.5.5/ how do I go about fixing it?
Presumably the issue is Haybarn-specific?
You can get in touch with me, or open an issue or PR as to why.
The CI extension build runs are still public on GitHub, but may have expired, if you bump your git sha ref it will rerun.
Took a bit of searching around to find the repo: https://github.com/Query-farm-haybarn/haybarn-community-exte...
Looks like this is the failed build https://github.com/Query-farm-haybarn/haybarn-community-exte... but logs have expired
I'll kick it off again for you.
Looks like flaky GitHub this time: https://github.com/Query-farm-haybarn/haybarn-community-exte...
DuckDB is still OSS btw. It didn't go proprietary like Redis or ElasticSearch.
For now..
MallarDB
I've already created Haybarn which is Query.Farm's distribution of DuckDB:
learn about it here: https://query.farm/haybarn/
If my extension shows as "build failed" on https://query.farm/haybarn/status/v1.5.5/ how do I go about fixing it?
Presumably the issue is Haybarn-specific?
You can get in touch with me, or open an issue or PR as to why.
The CI extension build runs are still public on GitHub, but may have expired, if you bump your git sha ref it will rerun.
Took a bit of searching around to find the repo: https://github.com/Query-farm-haybarn/haybarn-community-exte...
Looks like this is the failed build https://github.com/Query-farm-haybarn/haybarn-community-exte... but logs have expired
I'll kick it off again for you.
Looks like flaky GitHub this time: https://github.com/Query-farm-haybarn/haybarn-community-exte...
DuckDB is still OSS btw. It didn't go proprietary like Redis or ElasticSearch.
For now..
MallarDB