Fix Database Schema #8
Comments
|
@0x4007 would plaintext include issue body as well or would it just be comment body? So, right now if there's a private repository then the plaintext would become 'CENSORED'. Is that fine? |
|
Issue body as well and no leave null |
So, plaintext's value would issue body + comment body, or do we require a separate column, if that's the case then how should the embedding value be found? Is it just comment body or is it comment body + issue body. |
|
Why do you want to associate and/or combine the embedding of the issue body and the comment body? Can you provide some examples of applications that would require this? |
Case 1: Issue Body + Comment Body:
Case 2: Issue Body and Comment Body Separate columns:
If having two separate embeddings is acceptable, then that's fine. According to the issue's specification, the desired schema was |
|
I don't understand your explanation. Anyways would be great if we can make the following applications:
As I understand with my proposed schema, these applications are possible. I wonder if it makes sense simply to capture every property, excluding the URL properties from the issue and comment objects on GitHub |
Just to be clear, what is plaintext in your schema ? |
|
The source code of the markdown of the comments. I hope that the mark down syntax doesn't negatively affect the LLM's ability to understand. I know that I always must clarify with ChatGPT that the right arrow bracket means it's a block quote from another comment. I suppose we'll need to compare performance of raw marked down source code and something preprocessed/more similar to how we perceive it |
I'll give an example of plaintext let me know if this right ? Is this right ? If not could you please give an example. I am not sure what you mean by |
|
I am not an expert working with embeddings but as I understand we need to generate a single embedding per corpus of text (comment) Otherwise yes you included the markdown syntax which is what I said. |
To clarify, the example I shared involves a single embedding/vector. Currently, this means that a new text corpus(markdown I shared before) will be created for each new issue, and additional comments will be added to that corpus. Currently, we create a new record for each comment and generate an embedding for each one. This approach won't work with the issuededup or Assistant plan you have. |
So, to clarify, should the embedding be created per comment while the plaintext contains the entire markdown syntax I mentioned earlier? Is that the correct approach? I don't think this will work as intended. We need either the comments with their embeddings or the text corpus (markdown) with its embeddings. Please let me know if I've misunderstood anything. |
|
So then if we are clobbering a single embedding to represent an entire issue (and pull) won't the costs increase exponentially? Can't we feed multiple embeddings to an LLM to work with? It doesn't seem like a good approach to clobber |
An alternative approach would be to store each piece of text from issues/comments as separate entities and associate them with their respective node IDs. This would create a large text corpus containing all the content from the organization, which could be identified by a global node ID or by using a type column in the schema. |
To clarify, we don’t provide embeddings directly to the LLM. Instead, we perform a vector or similarity search, apply a ranking technique, and then extract text values that are most relevant to the search subject. This extracted text is then used as context for the LLM. |
|
@gentlementlegen im assuming storing node id won't be sufficient for us to determine which embeddings are associated with eachother. I'm assuming we need to also store the issue id Anyways at this point im starting to think we should just store everything besides the _url properties and then we can optimize later since we seem to not know for sure what to do now. |
ChatGPT: Here are additional use cases for embeddings:
Reviewing the leaderboard and I realize that STS (Semantic Textual Similarity) is the most important for depuplication and task matchmaking. Check the STS tab. Seems significantly better than OpenAI's offering. We may also be able to make a feature that allows contributors to ask product/strategic direction questions to the bot. It can link back to comments that answer their question. Text summarization might be able to improve our relevance scoring of comments (verbose and concise comments may be able to receive similar "quantitative scoring" credit) |
Hi, could you update me on the final database schema? I believe that the global node ID and type should be sufficient. Other parameters might not be relevant to the embedding text corpus and could end up being more of a log dump. |
I can probably write a new adapter for them, but I think their free tier has only 3 RPM (Request per minute), but offer 50M free tokens for new accounts to use ? |
|
Three requests per minute seems acceptable as long as we can have some type of buffer or queue. I believe we had plans to do this anyways with the OpenAI embeddings because it's significantly cheaper. However, can we generate multiple embeddings per request? If not then I imagine this can get more complicated than a cron job. As for schema, I think it's simpler to dump everything and optimize later. This is because we don't know what the next plugins will need and this gives us more flexibility for research. To me it's only a priority to optimize when we start hitting free tier limits. |
So, if we add a payment method, the requests per minute can be increased. I have updated the plugin for support with voyageai |
|
Any name and zip code should work |
|
I've added my payment method. Please delete this information immediately just to be safe or share it through another platform, like Telegram. |
|
It's merchant locked for up to $1 |
|
So, the final schema would be type Comment = {
/**
* AuthorAssociation
* @description How the author is associated with the repository.
* @enum {string}
*/
author_association:
| "COLLABORATOR"
| "CONTRIBUTOR"
| "FIRST_TIMER"
| "FIRST_TIME_CONTRIBUTOR"
| "MANNEQUIN"
| "MEMBER"
| "NONE"
| "OWNER";
/** @description Contents of the issue comment */
body: string;
/** Format: date-time */
created_at: string;
/** Format: uri */
html_url: string;
/**
* Format: int64
* @description Unique identifier of the issue comment
*/
id: number;
/** Format: uri */
issue_url: string;
node_id: string;
performed_via_github_app: null | components["schemas"]["integration"];
/** Reactions */
reactions: {
"+1": number;
"-1": number;
confused: number;
eyes: number;
heart: number;
hooray: number;
laugh: number;
rocket: number;
total_count: number;
/** Format: uri */
url: string;
};
/** Format: date-time */
updated_at: string;
/**
* Format: uri
* @description URL for the issue comment
*/
url: string;
/** User */
user: {
/** Format: uri */
avatar_url?: string;
deleted?: boolean;
email?: string | null;
/** Format: uri-template */
events_url?: string;
/** Format: uri */
followers_url?: string;
/** Format: uri-template */
following_url?: string;
/** Format: uri-template */
gists_url?: string;
gravatar_id?: string;
/** Format: uri */
html_url?: string;
id: number;
login: string;
name?: string;
node_id?: string;
/** Format: uri */
organizations_url?: string;
/** Format: uri */
received_events_url?: string;
/** Format: uri */
repos_url?: string;
site_admin?: boolean;
/** Format: uri-template */
starred_url?: string;
/** Format: uri */
subscriptions_url?: string;
/** @enum {string} */
type?: "Bot" | "User" | "Organization";
/** Format: uri */
url?: string;
} | null;
};Is this schema fine, or is there anything else to be added or removed ? |
|
Looks like there isn't a lot to save from there if we remove the URLs, nested objects like reactions and user details. I'm surprised that's all that's there. Performed via GitHub app should also be removed because we shouldn't be generating embeddings for bot comments. So after all of that, looks like basically we might only be adding author association. |
I took this from octokit's type definition. I think reactions should be kept, as it could be a metric of engagement for comments with abnormally low relevance. Also, should the created_at in the schema be referenced from the comment or when the actual record was created. This is the entire dump of the webhook event |
|
My concern is that I feel we should make everything into its own column. However, for simplicity, we could just save the full reaction object in a single column. |
If we are not going to be using relations and other sql things, we can try with mongoDB or any other document based db ? |
|
I think Supabase is probably fine because there are no planned features for reactions. We unlikely need the performance for querying for a long time. Even if or when we do, we can consider adding those columns later. To be honest I'm not a database expert but seems like Supabase should handle our needs. It has a nice UI which is convenient for debugging |
It should be better. I am skeptical about storing serialized comment objects in Postgres database. It should not affect the performance though. |
|
I asked ChatGPT for a new feature: onboarding new developers, via plaintext q&a. It said we should generate embeddings of an entire repository. How does this affect our schema? Perhaps we should generalize further? Or we can make a new table? Perhaps a new table per GitHub object type is the most manageable. |
that would depend on the onboarding, if onboarding involves explaining the current tickets and comments and the work that's going on, this schema would be enough. If we want to explain the code and other things, for them we do not need embeddings. For General Q&A this should be enough. We could further expand this by adding OpenAI functions, to query the repo based on the serialized object retrieved using vector search. |
|
/start |
Tips:
|
|
| View | Contribution | Count | Reward |
|---|---|---|---|
| Issue | Task | 1 | 200 |
| Issue | Comment | 18 | 0 |
| Review | Comment | 20 | 0 |
Conversation Incentives
| Comment | Formatting | Relevance | Reward |
|---|---|---|---|
@0x4007 would plaintext include issue body as well or would it j… | 0content:
p:
symbols:
\b\w+\b:
count: 33
multiplier: 0
score: 1
multiplier: 0
| 0.7 | - |
So, plaintext's value would issue body + comment body, or do we … | 0content:
p:
symbols:
\b\w+\b:
count: 41
multiplier: 0
score: 1
multiplier: 0
| 0.8 | - |
Case 1: Issue Body + Comment Body: - Only one vector index for … | 0content:
p:
symbols:
\b\w+\b:
count: 6
multiplier: 0
score: 1
ul:
symbols:
\b\w+\b:
count: 106
multiplier: 0
score: 1
li:
symbols:
\b\w+\b:
count: 35
multiplier: 0
score: 1
code:
symbols:
\b\w+\b:
count: 6
multiplier: 0
score: 1
multiplier: 0
| 0.8 | - |
Just to be clear, what is plaintext in your schema ? | 0content:
p:
symbols:
\b\w+\b:
count: 10
multiplier: 0
score: 1
multiplier: 0
| 0.5 | - |
I'll give an example of plaintext let me know if this right ? &… | 0content:
p:
symbols:
\b\w+\b:
count: 27
multiplier: 0
score: 1
pre:
symbols:
\b\w+\b:
count: 62
multiplier: 0
score: 0
code:
symbols:
\b\w+\b:
count: 8
multiplier: 0
score: 1
multiplier: 0
| 0.7 | - |
To clarify, the example I shared involves a single embedding/vec… | 0content:
p:
symbols:
\b\w+\b:
count: 68
multiplier: 0
score: 1
multiplier: 0
| 0.6 | - |
So, to clarify, should the embedding be created per comment whil… | 0content:
p:
symbols:
\b\w+\b:
count: 60
multiplier: 0
score: 1
multiplier: 0
| 0.8 | - |
An alternative approach would be to store each piece of text fro… | 0content:
p:
symbols:
\b\w+\b:
count: 57
multiplier: 0
score: 1
multiplier: 0
| 0.9 | - |
To clarify, we don’t provide embeddings directly to the LLM. Ins… | 0content:
p:
symbols:
\b\w+\b:
count: 47
multiplier: 0
score: 1
multiplier: 0
| 0.8 | - |
@0x4007 Hi, could you update me on the final database schema? … | 0content:
p:
symbols:
\b\w+\b:
count: 44
multiplier: 0
score: 1
multiplier: 0
| 0.7 | - |
I can probably write a new adapter for them, but I think their f… | 0content:
p:
symbols:
\b\w+\b:
count: 32
multiplier: 0
score: 1
multiplier: 0
| 0.3 | - |
So, if we add a payment method, the requests per minute can be i… | 0content:
p:
symbols:
\b\w+\b:
count: 23
multiplier: 0
score: 1
multiplier: 0
| 0.4 | - |
@0x4007 I've added my payment method. Please delete this infor… | 0content:
p:
symbols:
\b\w+\b:
count: 24
multiplier: 0
score: 1
multiplier: 0
| 0.2 | - |
So, the final schema would be `Id (GlobalNodeId), plaintext(… | 0content:
p:
symbols:
\b\w+\b:
count: 14
multiplier: 0
score: 1
code:
symbols:
\b\w+\b:
count: 179
multiplier: 0
score: 1
pre:
symbols:
\b\w+\b:
count: 179
multiplier: 0
score: 0
multiplier: 0
| 0.9 | - |
I took this from octokit's type definition. I think reactions sh… | 0content:
p:
symbols:
\b\w+\b:
count: 56
multiplier: 0
score: 1
pre:
symbols:
\b\w+\b:
count: 1530
multiplier: 0
score: 0
code:
symbols:
\b\w+\b:
count: 1530
multiplier: 0
score: 1
multiplier: 0
| 0.8 | - |
If we are not going to be using relations and other sql things, … | 0content:
p:
symbols:
\b\w+\b:
count: 24
multiplier: 0
score: 1
multiplier: 0
| 0.6 | - |
It should be better. I am skeptical about storing serialized com… | 0content:
p:
symbols:
\b\w+\b:
count: 22
multiplier: 0
score: 1
multiplier: 0
| 0.5 | - |
that would depend on the onboarding, if onboarding involves expl… | 0content:
p:
symbols:
\b\w+\b:
count: 74
multiplier: 0
score: 1
multiplier: 0
| 0.7 | - |
Resolves [#8](https://github.com/ubiquibot/issue-comment-embeddi… | 0content:
p:
symbols:
\b\w+\b:
count: 2
multiplier: 0
score: 1
a:
symbols:
\b\w+\b:
count: 1
multiplier: 0
score: 1
ul:
symbols:
\b\w+\b:
count: 40
multiplier: 0
score: 1
li:
symbols:
\b\w+\b:
count: 4
multiplier: 0
score: 1
code:
symbols:
\b\w+\b:
count: 1
multiplier: 0
score: 1
multiplier: 0
| 1 | - |
This is according to the schema mentioned in the issue spec, cou… | 0content:
p:
symbols:
\b\w+\b:
count: 23
multiplier: 0.2
score: 1
multiplier: 0
| 1 | - |
I’ve retained it in case it can be expanded to support OpenAI's … | 0content:
p:
symbols:
\b\w+\b:
count: 30
multiplier: 0.2
score: 1
multiplier: 0
| 1 | - |
This is the maximum possible length. Even if we switch providers… | 0content:
p:
symbols:
\b\w+\b:
count: 33
multiplier: 0.2
score: 1
multiplier: 0
| 1 | - |
I wanted to keep it consistent with the DB schema. This passed t… | 0content:
p:
symbols:
\b\w+\b:
count: 24
multiplier: 0.2
score: 1
multiplier: 0
| 1 | - |
Its there to ignore, bot comments, and chore issues created. So,… | 0content:
p:
symbols:
\b\w+\b:
count: 38
multiplier: 0.2
score: 1
multiplier: 0
| 1 | - |
I don't think its safe to give codeblock to jsdom. This works fi… | 0content:
p:
symbols:
\b\w+\b:
count: 31
multiplier: 0.2
score: 1
multiplier: 0
| 1 | - |
Replace it with `Markdown-it`. This library is being mai… | 0content:
p:
symbols:
\b\w+\b:
count: 15
multiplier: 0.2
score: 1
code:
symbols:
\b\w+\b:
count: 2
multiplier: 0.2
score: 1
multiplier: 0
| 1 | - |
If a text is empty, instead of calling embedding api on it I am … | 0content:
p:
symbols:
\b\w+\b:
count: 56
multiplier: 0.2
score: 1
multiplier: 0
| 1 | - |
This can be used for issue deduplication and stuff. I think this… | 0content:
p:
symbols:
\b\w+\b:
count: 16
multiplier: 0.2
score: 1
multiplier: 0
| 1 | - |
Fixed | 0content:
p:
symbols:
\b\w+\b:
count: 1
multiplier: 0.2
score: 1
multiplier: 0
| 1 | - |
@0x4007 Updated the schema, comments use `voyageai` for … | 0content:
p:
symbols:
\b\w+\b:
count: 10
multiplier: 0.2
score: 1
code:
symbols:
\b\w+\b:
count: 1
multiplier: 0.2
score: 1
multiplier: 0
| 1 | - |
@0x4007 Could you please check the updated changes ? Have remove… | 0content:
p:
symbols:
\b\w+\b:
count: 23
multiplier: 0.2
score: 1
code:
symbols:
\b\w+\b:
count: 1
multiplier: 0.2
score: 1
multiplier: 0
| 1 | - |
I have removed the changes for the other task. CI Should be pass… | 0content:
p:
symbols:
\b\w+\b:
count: 25
multiplier: 0.2
score: 1
multiplier: 0
| 1 | - |
Right now issue body is in the payload object, this is jsonb, wh… | 0content:
p:
symbols:
\b\w+\b:
count: 18
multiplier: 0.2
score: 1
img:
symbols:
\b\w+\b:
count: 1
multiplier: 0.2
score: 0
multiplier: 0
| 1 | - |
So to sum up, you require two tables one for `comments` … | 0content:
p:
symbols:
\b\w+\b:
count: 44
multiplier: 0.2
score: 1
code:
symbols:
\b\w+\b:
count: 7
multiplier: 0.2
score: 1
multiplier: 0
| 1 | - |
@0x4007 Have Added Two Separate Tables as per the schema mention… | 0content:
p:
symbols:
\b\w+\b:
count: 26
multiplier: 0.2
score: 1
multiplier: 0
| 1 | - |
Yes, it includes a payload. I've retained the type column to dis… | 0content:
p:
symbols:
\b\w+\b:
count: 38
multiplier: 0.2
score: 1
multiplier: 0
| 1 | - |
Removed the `type` from schema. Payload is stored for bo… | 0content:
p:
symbols:
\b\w+\b:
count: 24
multiplier: 0.2
score: 1
code:
symbols:
\b\w+\b:
count: 1
multiplier: 0.2
score: 1
multiplier: 0
| 1 | - |
@0x4007 I have added `markdown` and `plaintext` … | 0content:
p:
symbols:
\b\w+\b:
count: 39
multiplier: 0.2
score: 1
code:
symbols:
\b\w+\b:
count: 1
multiplier: 0.2
score: 1
multiplier: 0
| 1 | - |
[ 114.801 WXDAI ]
@0x4007
Contributions Overview
| View | Contribution | Count | Reward |
|---|---|---|---|
| Issue | Specification | 1 | 16.82 |
| Issue | Comment | 15 | 59.741 |
| Review | Comment | 27 | 38.24 |
Conversation Incentives
| Comment | Formatting | Relevance | Reward |
|---|---|---|---|
This requires changes to the plugin that captures the data, as w… | 16.82content:
h2:
symbols:
\b\w+\b:
count: 21
multiplier: 0.1
score: 1
img:
symbols:
\b\w+\b:
count: 1
multiplier: 0.1
score: 5
p:
symbols:
\b\w+\b:
count: 19
multiplier: 0.1
score: 1
pre:
symbols:
\b\w+\b:
count: 6
multiplier: 0.1
score: 0
code:
symbols:
\b\w+\b:
count: 1
multiplier: 0.1
score: 5
ul:
symbols:
\b\w+\b:
count: 192
multiplier: 0.1
score: 0
li:
symbols:
\b\w+\b:
count: 35
multiplier: 0.1
score: 1
multiplier: 3
| 1 | 16.82 |
Issue body as well and no leave null | 1.17content:
p:
symbols:
\b\w+\b:
count: 8
multiplier: 0.2
score: 1
multiplier: 1
| 0.5 | 0.585 |
Why do you want to associate and/or combine the embedding of the… | 3.6content:
p:
symbols:
\b\w+\b:
count: 30
multiplier: 0.2
score: 1
multiplier: 1
| 0.7 | 2.52 |
I don't understand your explanation. Anyways would be great if … | 8.07content:
p:
symbols:
\b\w+\b:
count: 17
multiplier: 0.2
score: 1
ol:
symbols:
\b\w+\b:
count: 55
multiplier: 0.2
score: 0
li:
symbols:
\b\w+\b:
count: 53
multiplier: 0.2
score: 1
multiplier: 1
| 0.8 | 6.456 |
The source code of the markdown of the comments. I hope that th… | 7.67content:
p:
symbols:
\b\w+\b:
count: 73
multiplier: 0.2
score: 1
multiplier: 1
| 0.4 | 3.068 |
I am not an expert working with embeddings but as I understand w… | 4.21content:
p:
symbols:
\b\w+\b:
count: 36
multiplier: 0.2
score: 1
multiplier: 1
| 0.6 | 2.526 |
So then if we are clobbering a single embedding to represent an … | 4.99content:
p:
symbols:
\b\w+\b:
count: 44
multiplier: 0.2
score: 1
multiplier: 1
| 0.7 | 3.493 |
@gentlementlegen im assuming storing node id won't be sufficient… | 7.04content:
p:
symbols:
\b\w+\b:
count: 66
multiplier: 0.2
score: 1
multiplier: 1
| 0.8 | 5.632 |
OpenAI’s text embeddings measure the relatedness of text strings… | 12.3content:
h2:
symbols:
\b\w+\b:
count: 8
multiplier: 0.2
score: 1
p:
symbols:
\b\w+\b:
count: 103
multiplier: 0.2
score: 1
a:
symbols:
\b\w+\b:
count: 1
multiplier: 0.2
score: 1
code:
symbols:
\b\w+\b:
count: 4
multiplier: 0.2
score: 1
multiplier: 1
| 0.9 | 11.07 |
Three requests per minute seems acceptable as long as we can hav… | 10.79content:
p:
symbols:
\b\w+\b:
count: 109
multiplier: 0.2
score: 1
multiplier: 1
| 0.8 | 8.632 |
![image](https://github.com/user-attachments/assets/eaf5c732-5c8… | 1.05content:
p:
symbols:
\b\w+\b:
count: 7
multiplier: 0.2
score: 1
img:
symbols:
\b\w+\b:
count: 1
multiplier: 0.2
score: 0
multiplier: 1
| 0.1 | 0.105 |
It's merchant locked for up to $1 | 1.17content:
p:
symbols:
\b\w+\b:
count: 8
multiplier: 0.2
score: 1
multiplier: 1
| 0.1 | 0.117 |
Looks like there isn't a lot to save from there if we remove the… | 6.95content:
p:
symbols:
\b\w+\b:
count: 65
multiplier: 0.2
score: 1
br:
symbols:
\b\w+\b:
count: 1
multiplier: 0.2
score: 0
multiplier: 1
| 0.7 | 4.865 |
My concern is that I feel we should make everything into its own… | 3.5content:
p:
symbols:
\b\w+\b:
count: 29
multiplier: 0.2
score: 1
multiplier: 1
| 0.5 | 1.75 |
I think Supabase is probably fine because there are no planned f… | 6.95content:
p:
symbols:
\b\w+\b:
count: 65
multiplier: 0.2
score: 1
multiplier: 1
| 0.6 | 4.17 |
I asked ChatGPT for a new feature: onboarding new developers, vi… | 5.94content:
p:
symbols:
\b\w+\b:
count: 54
multiplier: 0.2
score: 1
multiplier: 1
| 0.8 | 4.752 |
Seems generally okay. Let me see how your database looks | 0.71content:
p:
symbols:
\b\w+\b:
count: 10
multiplier: 0.1
score: 1
multiplier: 1
| 1 | 0.71 |
```suggestion const authorId = payload.comment.use… | 0.52content:
pre:
symbols:
\b\w+\b:
count: 7
multiplier: 0.1
score: 0
code:
symbols:
\b\w+\b:
count: 7
multiplier: 0.1
score: 1
multiplier: 1
| 1 | 0.52 |
Sync with the GitHub metadata of the comment or issue | 0.71content:
p:
symbols:
\b\w+\b:
count: 10
multiplier: 0.1
score: 1
multiplier: 1
| 1 | 0.71 |
```suggestion ``` | 0.1content:
pre:
symbols:
\b\w+\b:
count: 1
multiplier: 0.1
score: 0
code:
symbols:
\b\w+\b:
count: 1
multiplier: 0.1
score: 1
multiplier: 1
| 1 | 0.1 |
```suggestion plaintext = null; ``&#… | 0.64content:
pre:
symbols:
\b\w+\b:
count: 2
multiplier: 0.1
score: 0
code:
symbols:
\b\w+\b:
count: 2
multiplier: 0.1
score: 1
p:
symbols:
\b\w+\b:
count: 6
multiplier: 0.1
score: 1
multiplier: 1
| 1 | 0.64 |
```suggestion plaintext = null; ``` | 0.18content:
pre:
symbols:
\b\w+\b:
count: 2
multiplier: 0.1
score: 0
code:
symbols:
\b\w+\b:
count: 2
multiplier: 0.1
score: 1
multiplier: 1
| 1 | 0.18 |
Should this file be deleted or something? | 0.52content:
p:
symbols:
\b\w+\b:
count: 7
multiplier: 0.1
score: 1
multiplier: 1
| 1 | 0.52 |
Why does it have to be this exact length? | 0.65content:
p:
symbols:
\b\w+\b:
count: 9
multiplier: 0.1
score: 1
multiplier: 1
| 1 | 0.65 |
```suggestion commentObject?: Record<string, un… | 1.5content:
pre:
symbols:
\b\w+\b:
count: 5
multiplier: 0.1
score: 0
code:
symbols:
\b\w+\b:
count: 5
multiplier: 0.1
score: 1
p:
symbols:
\b\w+\b:
count: 17
multiplier: 0.1
score: 1
multiplier: 1
| 1 | 1.5 |
Seems unnecessary. Just delete the trailing zeros. | 0.52content:
p:
symbols:
\b\w+\b:
count: 7
multiplier: 0.1
score: 1
multiplier: 1
| 1 | 0.52 |
We can restore from git history if needed. Its not in use so it … | 1.11content:
p:
symbols:
\b\w+\b:
count: 17
multiplier: 0.1
score: 1
multiplier: 1
| 1 | 1.11 |
If you defined it, then its wrong. If its from another database … | 1.54content:
p:
symbols:
\b\w+\b:
count: 25
multiplier: 0.1
score: 1
multiplier: 1
| 1 | 1.54 |
Why is the default issue on the comments table? Why even add the… | 1.38content:
p:
symbols:
\b\w+\b:
count: 22
multiplier: 0.1
score: 1
multiplier: 1
| 1 | 1.38 |
This seems very error prone. Why dont you use some virtual DOM (… | 1.46content:
p:
symbols:
\b\w+\b:
count: 20
multiplier: 0.1
score: 1
code:
symbols:
\b\w+\b:
count: 2
multiplier: 0.1
score: 1
multiplier: 1
| 1 | 1.46 |
```suggestion model: "voyage-large-2-instru… | 1.02content:
pre:
symbols:
\b\w+\b:
count: 5
multiplier: 0.1
score: 0
code:
symbols:
\b\w+\b:
count: 5
multiplier: 0.1
score: 1
p:
symbols:
\b\w+\b:
count: 7
multiplier: 0.1
score: 1
a:
symbols:
\b\w+\b:
count: 1
multiplier: 0.1
score: 1
multiplier: 1
| 1 | 1.02 |
```suggestion const markdown = payload.issue.body… | 1.92content:
pre:
symbols:
\b\w+\b:
count: 9
multiplier: 0.1
score: 0
code:
symbols:
\b\w+\b:
count: 9
multiplier: 0.1
score: 1
p:
symbols:
\b\w+\b:
count: 20
multiplier: 0.1
score: 1
multiplier: 1
| 1 | 1.92 |
```suggestion logger.debug(`Exiting addIssue&… | 1.71content:
pre:
symbols:
\b\w+\b:
count: 4
multiplier: 0.1
score: 0
code:
symbols:
\b\w+\b:
count: 4
multiplier: 0.1
score: 1
p:
symbols:
\b\w+\b:
count: 22
multiplier: 0.1
score: 1
multiplier: 1
| 1 | 1.71 |
This seems out of scope? | 0.39content:
p:
symbols:
\b\w+\b:
count: 5
multiplier: 0.1
score: 1
multiplier: 1
| 1 | 0.39 |
Still confused about this fill stuff | 0.46content:
p:
symbols:
\b\w+\b:
count: 6
multiplier: 0.1
score: 1
multiplier: 1
| 1 | 0.46 |
Why did you switch to main from development that doesn't seem ri… | 0.88content:
p:
symbols:
\b\w+\b:
count: 13
multiplier: 0.1
score: 1
multiplier: 1
| 1 | 0.88 |
You'll need to cherry pick changes (easy to do with a git UI) an… | 4.58content:
p:
symbols:
\b\w+\b:
count: 90
multiplier: 0.1
score: 1
multiplier: 1
| 1 | 4.58 |
Where's the issue body? You should probably make another table a… | 1.75content:
p:
symbols:
\b\w+\b:
count: 29
multiplier: 0.1
score: 1
multiplier: 1
| 1 | 1.75 |
I'm bad at deciding this sort of thing. Let's go with your sugge… | 1.7content:
p:
symbols:
\b\w+\b:
count: 28
multiplier: 0.1
score: 1
multiplier: 1
| 1 | 1.7 |
Seems mostly good but I didn't see all the headers on the first … | 2.69content:
p:
symbols:
\b\w+\b:
count: 48
multiplier: 0.1
score: 1
multiplier: 1
| 1 | 2.69 |
Yes I think its unnecessary if they are separated by type on dif… | 0.94content:
p:
symbols:
\b\w+\b:
count: 14
multiplier: 0.1
score: 1
multiplier: 1
| 1 | 0.94 |
Thanks for the thorough QA. You don't need to make a new video o… | 7.49content:
p:
symbols:
\b\w+\b:
count: 158
multiplier: 0.1
score: 1
code:
symbols:
\b\w+\b:
count: 1
multiplier: 0.1
score: 1
multiplier: 1
| 1 | 7.49 |
I think that only tier5 subscribers can use right now via API. I… | 1.17content:
p:
symbols:
\b\w+\b:
count: 18
multiplier: 0.1
score: 1
multiplier: 1
| 1 | 1.17 |
|
I'll need to top up the wallet soon |
This requires changes to the plugin that captures the data, as well as the database itself.
This must capture issue bodies.
Perhaps I wasn't explicit with my vision for the database schema, but this needs adjustments.
We only need:
plaintextshould only save if its a public repo, otherwise we have liabilities on our hands storing company private data.The text was updated successfully, but these errors were encountered: