GitLab Code Splitter

Split GitLab repository code into manageable chunks
Join our community

Actions9

Overview

The node "GitLab Code Splitter" provides functionality to interact with a GitLab-related API for splitting code and repositories into manageable chunks. Specifically, the System - Health Check operation allows users to verify the health status of the connected API service.

This operation is useful in scenarios where you want to ensure that the external API endpoint is reachable and functioning correctly before performing more complex operations like code splitting or repository processing. For example, before triggering a large batch job to split repository files, you can run this health check to confirm the API is online and responsive.

Properties

Name Meaning
Split Options Collection of options controlling how code is split into chunks:
- Max Tokens: Maximum tokens per chunk (default 800)
- Overlap: Token overlap between chunks (default 50)
- Min Chunk Size: Minimum chunk size in tokens (default 100)
- Preserve Newlines: Whether to preserve newline characters (default true)

Note: Although the "Split Options" property is defined, it is not directly used by the System - Health Check operation but is part of the node's general input properties.

Output

The output JSON from the Health Check operation contains the API health status information as returned by the external API's /health endpoint. This typically includes fields indicating whether the API is operational, uptime, version, or other diagnostic details provided by the API.

Example output structure (illustrative):

{
  "status": "ok",
  "uptime": 123456,
  "version": "1.2.3"
}

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential with access to the GitLab Code Splitter API.
  • Requires the API base URL configured in credentials.
  • The node makes HTTP GET requests to the API’s /health endpoint.
  • No additional environment variables are required beyond the API URL and key.

Troubleshooting

  • Invalid API URL: If the API URL is missing or malformed, the node throws an error "Invalid API URL provided in credentials". Ensure the URL is a valid HTTP/HTTPS URL.
  • Invalid API Key: If the API key is missing, too short/long, contains invalid characters, or is a placeholder value, the node throws "Valid API key is required and must be provided in credentials" or "Invalid API key format...". Provide a proper API key matching the expected format.
  • Network Issues: If the API endpoint is unreachable, the request will fail. Verify network connectivity and that the API server is running.
  • API Errors: If the API returns an error response, it will be propagated. Check the API documentation or logs for details.

Links and References

This summary focuses on the System - Health Check operation of the GitLab Code Splitter node, describing its purpose, inputs, outputs, dependencies, and common troubleshooting points based on static analysis of the source code.

Discussion