Ecosyste.ms: Timeline
Browse the timeline of events for every public repo on GitHub. Data updated hourly from GH Archive.
Askir created a review comment on a pull request on timescale/pgai
```suggestion * **TL;DR**: * [Try out automatic embedding vectorization](/docs/vectorizer-quick-start.md): quicky create embeddings using a pre-built Docker developer environment with a ...
Askir created a review comment on a pull request on timescale/pgai
```suggestion This page shows you how to create a vectorizer in a self-hosted Postgres instance, then use the pgai vectorizer worker to create embeddings from data in your database. To finish of...
Askir created a review on a pull request on timescale/pgai
Leaving a very opinionated review here :D Overall I like the changes though!
jgpruitt pushed 1 commit to jgpruitt/param-names timescale/pgai
- docs: update docs and examples for param changes We removed the leading underscore from all function parameter names... e5c611f
cevian pushed 1 commit to adn/reveal-secrets timescale/pgai
- feat: add role-based permissions for secrets eb68957
jgpruitt pushed 1 commit to jgpruitt/param-names timescale/pgai
- chore!: remove prefixes from ollama function params BREAKING CHANGE: leading underscores have been removed from all ... 942eec3
cevian pushed 1 commit to adn/reveal-secrets timescale/pgai
- feat: add role-based permissions for secrets 37f6f23
Askir pushed 1 commit to jascha/remove-leading-underscores timescale/pgai
- fix: expected function params 5f83375
Askir pushed 1 commit to jascha/remove-leading-underscores timescale/pgai
- fix: expected function params b68f219
billy-the-fish created a comment on a pull request on timescale/pgai
@Askir I've moved the updates in this PR, less the technical implementations under discussion to https://github.com/timescale/pgai/pull/158. Are you ok to close this PR?
billy-the-fish created a comment on a pull request on timescale/pgai
@Askir I've moved the updates in this PR, less the technical implementations under discussion to https://github.com/timescale/pgai/pull/158. Are you ok to close this PR?
cevian pushed 1 commit to adn/reveal-secrets timescale/pgai
- feat: add role-based permissions for secrets 4ec1be0
Askir pushed 1 commit to jascha/remove-leading-underscores timescale/pgai
- chore: fix format cohere 28c8676
billy-the-fish pushed 1 commit to vectorizer-naming-update timescale/pgai
- chore: naming changes, and bring other prs into one. 85b391c
jgpruitt opened a pull request on timescale/pgai
chore!: remove prefixes from openai function params
BREAKING CHANGE: leading underscores have been removed from all openai function parameter names
jgpruitt created a branch on timescale/pgai
jgpruitt/param-names - Bring AI models closer to your PostgreSQL data
Askir created a branch on timescale/pgai
jascha/remove-leading-underscores - Bring AI models closer to your PostgreSQL data
billy-the-fish created a branch on timescale/pgai
vectorizer-naming-update - Bring AI models closer to your PostgreSQL data
cevian pushed 1 commit to adn/reveal-secrets timescale/pgai
- chore: make secrets fallback for api key 4b601b1
Askir created a review comment on a pull request on timescale/pgai
Not sure about this, I prefer to keep it as simple as possible. The more i add to the compose the more complex it makes it look to a potential user. And we want the setup to look and be as trivial ...
Askir created a review comment on a pull request on timescale/pgai
I've switched this again to simply `vectorizer-worker` to avoid the container being called `pgai-pgai-vectorizer-worker` because I've also added the compose namespace (pgai). Is that fine with you?
Askir created a review comment on a pull request on timescale/pgai
I've switched this again to just vectorizer-worker since the namespace of the compose is now pgai and the container is otherwise called `pgai-pgai-vectorizer-worker`. Is that fine with you?