Public Chats
Discover and explore public conversations from the community
Create issue descriptions for Knowledge Graph epic work items
"go through this epic https://gitlab.com/groups/gitlab-org/-/epics/17514 and then give me new issue descriptions for each work item based off the architecture. Make sure each work item is appropriately researched. Make sure to limit to just that epic and sub epics. Give me each description in GitLab Flavored markdown with clear separations. ``` Task,Notes,Theme,Project,Crate/Packages in Project,Applies to Client | Server | Both,Issue,Priority,Owner,Status,Milestone Ruby Parser,"We must implement this Language's parsing and data extraction (through AST). The following needs to be extracted: - Definitions - Modules - Classes - Methods - Constants - References - Imports - relative - module/dependency",Language Support,GitLab Code Parser,Core Parser,Client & Server,,P0,,In progress, Typescript/JS Parser,"We must implement this Language's parsing and data extraction (through AST). The following needs to be extracted: - Definitions - Modules - Classes - Methods - Constants - References - Imports - relative - alias imports - module/dependency Michael Usachenko",Language Support,GitLab Code Parser,Core Parser,Client & Server,https://gitlab.com/gitlab-org/rust/gitlab-code-parser/-/issues/2,P0,,Not started, GoLang Parser,,Language Support,GitLab Code Parser,Core Parser,Client & Server,,P0,,Not started, Python Parser,Jonathan Shobrook,Language Support,GitLab Code Parser,Core Parser,Client & Server,,P0,,Not started, Kotlin Parser,,Language Support,GitLab Code Parser,Core Parser,Client & Server,,P0,,, Unit Testing Framework,,Testing,GitLab Code Parser,Core Parser,Client & Server,,,,, Integration Testing Framework,,Testing,GitLab Code Parser,Core Parser,Client & Server,,,,, Benchmarking/Performance Framework,,Testing,GitLab Code Parser,Core Parser,Client & Server,,,,, Unit Testing Framework,,Testing,Knowledge Graph Indexer,"Core Indexer crate, CLI crate, Language Server Bindings crate",Client & Server,,,,, Integration Testing Framework,,Testing,Knowledge Graph Indexer,"CLI crate, Language Server Bindings crate, Core Indexer crate",Client & Server,,,,, Benchmarking/Performance Framework,,Testing,Knowledge Graph Indexer,"Core Indexer crate, CLI crate",Client & Server,,,,, Client Side Usage Collector Service,Will use the https://github.com/getsentry/sentry-rust package,Observability,Knowledge Graph Indexer,,,,,,, Client Side Error Collector Service,Will use the https://github.com/getsentry/sentry-rust package,Observability,Knowledge Graph Indexer,,,,,,, Server Side Usage Collector Service,TBD - Needs confirmation on how the server will collect and propagate metrics/usage from the indexer,Observability,Knowledge Graph Indexer,,,,,,, Server Side Error Collector Service,TBD - Needs confirmation on how the server will collect and propagate errors from the indexer,Observability,Knowledge Graph Indexer,,,,,,, Abstract Metric Service,"This service will take in a generic ""collector"" service/struct, which should be used throughout the codebase to collect metrics. In this service, we should define ""collect"" and ""flush"" events, which will trigger the metric capturing (either sent to Sentry on the client or Whatever Server will use to collect) ",Observability,Knowledge Graph Indexer,Core Indexer crate,Client & Server,,,,, Abstract Error Service,"Roughly the same as the Abstract Metric Service, but tailored for collecting Errors",Observability,Knowledge Graph Indexer,Core Indexer crate,Client & Server,,,,, Database Connection Service,"A wrapper service that takes in a Kuzu connection/database object and performs common operations (write, read, copy from, etc). ",Indexer Specific Code,Knowledge Graph Indexer,Core Indexer crate,Client & Server,,,,, Database Tables / Schema Service,This service should define the various tables and relationships in a type-safe API that Writer (Bulk or Incremental) service can use,Indexer Specific Code,Knowledge Graph Indexer,Core Indexer crate,Client & Server,,,,, Analysis Service,"This service is responsible for leveraging the gitlab-code-parser. It will input a file path and file content and return the appropriate data depending on the language. This will return the definition, import, reference, and any other nodes along with metadata (like the fully qualified name). We should leverage generic types here (depending on some language Enum), which will return the type depending on the language so that consumers can perform language specific logic (like the relationship builder service)",Indexer Specific Code,Knowledge Graph Indexer,Core Indexer crate,Client & Server,,,,, Relationship Builder Service,"This layer will be responsible for resolving the following relationships - Directory -> Directory - Directory -> File - File -> Definitions (Class, Method, Type, Constant etc) - File -> References - References -> Definitions The final output should be the nodes that adhere to the Database Schema to later be later inserted. This should go to the Writer Service",Indexer Specific Code,Knowledge Graph Indexer,Core Indexer crate,Client & Server,,,,, Writer Service - General,"This layer should determine the strategy for the incoming write (can manually set via arguments, such as ""init""), and pass the write operation to Bulk Writer or Incremental",Indexer Specific Code,Knowledge Graph Indexer,Core Indexer crate,Client & Server,,,,, Writer Service - Bulk Writer,"This layer is a sub-layer of the general Writer Service. This should be responsible for initial imports into the Kuzu Database (leveraging COPY From) and handling large updates (large node deletion, updates, etc)",Indexer Specific Code,Knowledge Graph Indexer,Core Indexer crate,Client & Server,,,,, Writer Service - Incremental,"This layer is a sub-layer of the general Writer Service. This should be responsible for incremental updates for node changes (such as a single file change). This will leverage Cypher queries to mutate data (Merge, Set, etc)",Indexer Specific Code,Knowledge Graph Indexer,Core Indexer crate,Client,,,,, Workspace Management Service,"For the client side, we need a way for the user to point the knowledge graph indexer to multiple repositories (a workspace folder). This will include: - traversing the file system to discover repositories depending on the workspace URI - any other local repository operations (in the future, obtaining git data) - being able to associate the local project with the GitLab/GitHub remote",Indexer Specific Code,Knowledge Graph Indexer,"CLI crate, Language Server Bindings crate",Client,,,,, Language Data Extraction Service,"This layer leverages the GitLab Code Parser to extract definitions and references. This logic will encapsulate the following: - accepting list of files - kicking off worker(s)/threads to iterate over the files - extracting the data via the AST service - extracting the data and send message to ""matcher"" ",Indexer Specific Code,Knowledge Graph Indexer,Core Indexer crate,Client & Server,,,,, Query Service,"This service should contain all logic needed for querying data, including: - Common Cypher Queries (get definitions for X file) - Extracting any node data from a file (can use Analysis Service if needed)",Indexer Specific Code,Knowledge Graph Indexer,Core Indexer crate,Client & Server,,,,, ,- linux (UNIX) first,,,,,,,,, ```"
Michael Angelo RiveraProgress update on code suggestions for Eclipse EPIC
"Give me the progress on the code suggestions for eclipse epic?"
Jean-Gabriel DoyonUnderstanding AddKnowledgeGraphReplicas in Zoekt architecture
"Help me understand how `class AddKnowledgeGraphReplicas` works with the larger Zoekt architecture in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/191162. How are we leveraging the existing Zoekt infrastructure?"
Michael Angelo RiveraOnboarding to GitLab Workflow Catalog team tasks and scope
"I am a fullstack engineer on the Workflow Catalog team at GitLab Here is a link to our issue tracker https://gitlab.com/gitlab-org/ai-powered/workflow-catalog/team-tasks/-/issues I'm trying to get up to speed on what we are tasked with, how it fits into the bigger picture, what is out of scope and what the next steps are."
Lee TickettFQN definition Rust data structure and indexer usage
"for this issue https://gitlab.com/gitlab-org/rust/gitlab-code-parser/-/issues/19, examine the parent epic and its issues also take a look at https://gitlab.com/gitlab-org/rust/knowledge-graph/-/issues/1 and finally look at https://gitlab.com/gitlab-org/rust/gitlab-code-parser/-/merge_requests/1 Let's create a description for - "What is an FQN" (with some code examples) - and that we need to determine what we want the Rust data structure to look like for FQN - and also determine how it will be used in the indexer Here is conversation context: ``` Did we establish a standard for FNQs anywhere? I'm writing the epic and issues for Kotlin and I realize we may not have specified the expected output anywhere? 19 replies Angelo Rivera 15 minutes ago Not yet, but we need to. You're referring to the expected datastructure right? Jean-Gabriel 12 minutes ago both Angelo Rivera 12 minutes ago I was going to comment on the parser epic that we should likely store FQN and as Vec<FQNPart> , where the FQNPart contains the metadata on: node_type - probably language specific node_name any other language specific metadata where the first element is the root node, an the last element is the node in question ```"
Michael Angelo RiveraGenerate Kotlin parser issues and epic description based on research
"researching this epic https://gitlab.com/groups/gitlab-org/-/epics/18028 and this MR https://gitlab.com/gitlab-org/rust/gitlab-code-parser/-/merge_requests/1, help me do the following: help me come up with issues (title and detailed description) similar to typescript and python epics that will go under https://gitlab.com/groups/gitlab-org/-/epics/18028 help me come up with a detailed epic description for https://gitlab.com/groups/gitlab-org/-/epics/18028 tailor the issue descriptions towards a Kotlin parser make sure to break the issues down into logical chunks based off the research and make sure to explain the scope keep the scope limit to under https://gitlab.com/groups/gitlab-org/-/epics/18028, do not search above it"
Jean-Gabriel DoyonCreating AI Feature Evaluation Guidelines for Engineers
"## Problem It can be hard for engineers to know when and how to evaluate AI features. The new AI feature development playbook will provide a high-level overview (https://gitlab.com/gitlab-org/gitlab/-/merge_requests/193250), but it leaves the details to be filled in. Engineers need to know what tools to use, why, when, and how. ## Tasks This is part of https://gitlab.com/groups/gitlab-org/modelops/ai-model-validation-and-research/ai-evaluation/-/epics/53 - Previous task: https://gitlab.com/gitlab-org/modelops/ai-model-validation-and-research/ai-evaluation/prompt-library/-/issues/743 - Current task: https://gitlab.com/gitlab-org/modelops/ai-model-validation-and-research/ai-evaluation/prompt-library/-/issues/674 - Collect the documentation on evaluation tools and processes, and organize them into a set of guidelines covering which tools to use, when, why, and how. - Should cover feature evaluation, prompt evaluation, tool evaluation, model evaluation, and latency evaluation ## References Consider these and linked/related resources for inclusion or as reference material: - All docs within: - https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/development/ai_features - https://gitlab.com/gitlab-org/modelops/applied-ml/code-suggestions/ai-assist/-/tree/main/docs - https://gitlab.com/gitlab-org/modelops/ai-model-validation-and-research/ai-evaluation/evaluation-runner/-/tree/main/docs?ref_type=heads - https://gitlab.com/gitlab-org/modelops/ai-model-validation-and-research/ai-evaluation/prompt-library/-/tree/main/doc?ref_type=heads - https://gitlab.com/gitlab-org/modelops/ai-model-validation-and-research/ai-evaluation/prompt-library/-/tree/main/doc/eli5?ref_type=heads - https://gitlab.com/gitlab-org/modelops/ai-model-validation-and-research/ai-evaluation/datasets/-/tree/main/doc?ref_type=heads - https://gitlab.com/gitlab-org/quality/ai-model-latency-tester/-/tree/main/docs?ref_type=heads Also consider general GitLab docs within https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/development ## Note - The Prompt Library repository includes two projects, the original promptlib, and the updated ELI5. promptlib is obsolete. Both are being replaced by CEF. See https://gitlab.com/gitlab-org/modelops/ai-model-validation-and-research/ai-evaluation/prompt-library/-/merge_requests/1424. Existing documentation might refer to Prompt Library, ELI5, or the CEF. New documentation should refer to the CEF instead of Prompt Library or ELI5"
Mark LapierreSecurely execute Git directly without libgit2 or shell process
"https://gitlab.com/groups/gitlab-org/-/epics/17515 for this epic and MR https://gitlab.com/gitlab-org/rust/gitalisk/-/merge_requests/1, how would we execute git directly (instead of libgit2) and not through shell (like as process) securely? Keep the research scope very small (max 2/3 issues)."
Michael Angelo RiveraGenerate GitLab issues and epic description for Ruby parser static analysis
"researching this epic https://gitlab.com/groups/gitlab-org/-/epics/18028 and this MR https://gitlab.com/gitlab-org/rust/gitlab-code-parser/-/merge_requests/1, help me do the following: help me come up with issues (title and detailed description) similar to typescript and python epics that will go under https://gitlab.com/groups/gitlab-org/-/epics/18028 help me come up with a detailed epic description for https://gitlab.com/groups/gitlab-org/-/epics/18028 tailor the issue descriptions towards the ruby parser MR https://gitlab.com/gitlab-org/rust/gitlab-code-parser/-/merge_requests/1 make sure to break the issues down into logical chunks based off the research and MR make sure to explain the scope of the static analysis supported so far in the MR and note it in the epic description keep the scope limit to under https://gitlab.com/groups/gitlab-org/-/epics/18028, do not search above it"
Michael Angelo RiveraResearch GitLab Epic 17514 Architecture and Work Items
"go through this epic https://gitlab.com/groups/gitlab-org/-/epics/17514 and fully research the architecture according to the work items I'd like to make descriptions for. Make sure each work item is appropriately researched. Keep it the research scoped to just the epic and its children. ``` Task,Notes,Theme,Project,Crate/Packages in Project,Applies to Client | Server | Both,Issue,Priority,Owner,Status,Milestone Ruby Parser,"We must implement this Language's parsing and data extraction (through AST). The following needs to be extracted: - Definitions - Modules - Classes - Methods - Constants - References - Imports - relative - module/dependency",Language Support,GitLab Code Parser,Core Parser,Client & Server,,P0,,In progress, Typescript/JS Parser,"We must implement this Language's parsing and data extraction (through AST). The following needs to be extracted: - Definitions - Modules - Classes - Methods - Constants - References - Imports - relative - alias imports - module/dependency Michael Usachenko",Language Support,GitLab Code Parser,Core Parser,Client & Server,https://gitlab.com/gitlab-org/rust/gitlab-code-parser/-/issues/2,P0,,Not started, GoLang Parser,,Language Support,GitLab Code Parser,Core Parser,Client & Server,,P0,,Not started, Python Parser,Jonathan Shobrook,Language Support,GitLab Code Parser,Core Parser,Client & Server,,P0,,Not started, Kotlin Parser,,Language Support,GitLab Code Parser,Core Parser,Client & Server,,P0,,, Unit Testing Framework,,Testing,GitLab Code Parser,Core Parser,Client & Server,,,,, Integration Testing Framework,,Testing,GitLab Code Parser,Core Parser,Client & Server,,,,, Benchmarking/Performance Framework,,Testing,GitLab Code Parser,Core Parser,Client & Server,,,,, Unit Testing Framework,,Testing,Knowledge Graph Indexer,"Core Indexer crate, CLI crate, Language Server Bindings crate",Client & Server,,,,, Integration Testing Framework,,Testing,Knowledge Graph Indexer,"CLI crate, Language Server Bindings crate, Core Indexer crate",Client & Server,,,,, Benchmarking/Performance Framework,,Testing,Knowledge Graph Indexer,"Core Indexer crate, CLI crate",Client & Server,,,,, Client Side Usage Collector Service,Will use the https://github.com/getsentry/sentry-rust package,Observability,Knowledge Graph Indexer,,,,,,, Client Side Error Collector Service,Will use the https://github.com/getsentry/sentry-rust package,Observability,Knowledge Graph Indexer,,,,,,, Server Side Usage Collector Service,TBD - Needs confirmation on how the server will collect and propagate metrics/usage from the indexer,Observability,Knowledge Graph Indexer,,,,,,, Server Side Error Collector Service,TBD - Needs confirmation on how the server will collect and propagate errors from the indexer,Observability,Knowledge Graph Indexer,,,,,,, Abstract Metric Service,"This service will take in a generic ""collector"" service/struct, which should be used throughout the codebase to collect metrics. In this service, we should define ""collect"" and ""flush"" events, which will trigger the metric capturing (either sent to Sentry on the client or Whatever Server will use to collect) ",Observability,Knowledge Graph Indexer,Core Indexer crate,Client & Server,,,,, Abstract Error Service,"Roughly the same as the Abstract Metric Service, but tailored for collecting Errors",Observability,Knowledge Graph Indexer,Core Indexer crate,Client & Server,,,,, Database Connection Service,"A wrapper service that takes in a Kuzu connection/database object and performs common operations (write, read, copy from, etc). ",Indexer Specific Code,Knowledge Graph Indexer,Core Indexer crate,Client & Server,,,,, Database Tables / Schema Service,This service should define the various tables and relationships in a type-safe API that Writer (Bulk or Incremental) service can use,Indexer Specific Code,Knowledge Graph Indexer,Core Indexer crate,Client & Server,,,,, Analysis Service,"This service is responsible for leveraging the gitlab-code-parser. It will input a file path and file content and return the appropriate data depending on the language. This will return the definition, import, reference, and any other nodes along with metadata (like the fully qualified name). We should leverage generic types here (depending on some language Enum), which will return the type depending on the language so that consumers can perform language specific logic (like the relationship builder service)",Indexer Specific Code,Knowledge Graph Indexer,Core Indexer crate,Client & Server,,,,, Relationship Builder Service,"This layer will be responsible for resolving the following relationships - Directory -> Directory - Directory -> File - File -> Definitions (Class, Method, Type, Constant etc) - File -> References - References -> Definitions The final output should be the nodes that adhere to the Database Schema to later be later inserted. This should go to the Writer Service",Indexer Specific Code,Knowledge Graph Indexer,Core Indexer crate,Client & Server,,,,, Writer Service - General,"This layer should determine the strategy for the incoming write (can manually set via arguments, such as ""init""), and pass the write operation to Bulk Writer or Incremental",Indexer Specific Code,Knowledge Graph Indexer,Core Indexer crate,Client & Server,,,,, Writer Service - Bulk Writer,"This layer is a sub-layer of the general Writer Service. This should be responsible for initial imports into the Kuzu Database (leveraging COPY From) and handling large updates (large node deletion, updates, etc)",Indexer Specific Code,Knowledge Graph Indexer,Core Indexer crate,Client & Server,,,,, Writer Service - Incremental,"This layer is a sub-layer of the general Writer Service. This should be responsible for incremental updates for node changes (such as a single file change). This will leverage Cypher queries to mutate data (Merge, Set, etc)",Indexer Specific Code,Knowledge Graph Indexer,Core Indexer crate,Client,,,,, Workspace Management Service,"For the client side, we need a way for the user to point the knowledge graph indexer to multiple repositories (a workspace folder). This will include: - traversing the file system to discover repositories depending on the workspace URI - any other local repository operations (in the future, obtaining git data) - being able to associate the local project with the GitLab/GitHub remote",Indexer Specific Code,Knowledge Graph Indexer,"CLI crate, Language Server Bindings crate",Client,,,,, Language Data Extraction Service,"This layer leverages the GitLab Code Parser to extract definitions and references. This logic will encapsulate the following: - accepting list of files - kicking off worker(s)/threads to iterate over the files - extracting the data via the AST service - extracting the data and send message to ""matcher"" ",Indexer Specific Code,Knowledge Graph Indexer,Core Indexer crate,Client & Server,,,,, Query Service,"This service should contain all logic needed for querying data, including: - Common Cypher Queries (get definitions for X file) - Extracting any node data from a file (can use Analysis Service if needed)",Indexer Specific Code,Knowledge Graph Indexer,Core Indexer crate,Client & Server,,,,, ,- linux (UNIX) first,,,,,,,,, ````"
Michael Angelo RiveraNew Chat
"What is the current state of https://gitlab.com/gitlab-da/use-cases/ai/ai-workflows/gitlab-duo-workflow/challenges/challenge-cpp-observability-sensor/-/issues/1 ... any MRs that fix it?"
Michael FriedrichStatus and production readiness of GitLab Rust code parser project
"What is the current state of this project? Can I use it in production? https://gitlab.com/gitlab-org/rust/gitlab-code-parser"
Michael Friedrich