logdetective 0.4.0__py3-none-any.whl → 2.11.0__py3-none-any.whl

logdetective-2.11.0.dist-info/METADATA

@@ -0,0 +1,568 @@
+Metadata-Version: 2.4
+Name: logdetective
+Version: 2.11.0
+Summary: Log using LLM AI to search for build/test failures and provide ideas for fixing these.
+License: Apache-2.0
+License-File: LICENSE
+Author: Jiri Podivin
+Author-email: jpodivin@gmail.com
+Requires-Python: >=3.11,<4.0
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Natural Language :: English
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Internet :: Log Analysis
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Classifier: Topic :: Software Development :: Debuggers
+Provides-Extra: server
+Provides-Extra: server-testing
+Provides-Extra: testing
+Requires-Dist: aiohttp (>=3.7.4,<4.0.0)
+Requires-Dist: aiolimiter (>=1.0.0,<2.0.0) ; extra == "server"
+Requires-Dist: aioresponses (>=0.7.8,<0.8.0) ; extra == "testing"
+Requires-Dist: alembic (>=1.13.3,<2.0.0) ; extra == "server" or extra == "server-testing"
+Requires-Dist: asciidoc[testing] (>=10.2.1,<11.0.0) ; extra == "testing"
+Requires-Dist: asyncpg (>=0.30.0,<1.0.0) ; extra == "server" or extra == "server-testing"
+Requires-Dist: backoff (==2.2.1) ; extra == "server" or extra == "server-testing"
+Requires-Dist: drain3 (>=0.9.11,<0.10.0)
+Requires-Dist: fastapi (>=0.111.1,<1.0.0) ; extra == "server" or extra == "server-testing"
+Requires-Dist: flexmock (>=0.12.2,<0.13.0) ; extra == "testing"
+Requires-Dist: huggingface-hub (>=0.23.0,<1.4.0)
+Requires-Dist: koji (>=1.35.0,<2.0.0) ; extra == "server" or extra == "server-testing"
+Requires-Dist: llama-cpp-python (>0.2.56,!=0.2.86,<1.0.0)
+Requires-Dist: matplotlib (>=3.8.4,<4.0.0) ; extra == "server" or extra == "server-testing"
+Requires-Dist: numpy (>=1.26.0)
+Requires-Dist: openai (>=1.82.1,<2.0.0) ; extra == "server" or extra == "server-testing"
+Requires-Dist: pydantic (>=2.8.2,<3.0.0)
+Requires-Dist: pytest (>=8.4.1,<9.0.0) ; extra == "testing"
+Requires-Dist: pytest-asyncio (>=1.1.0,<2.0.0) ; extra == "testing"
+Requires-Dist: pytest-cov[testing] (>=7.0.0,<8.0.0) ; extra == "testing"
+Requires-Dist: pytest-mock (>=3.14.1,<4.0.0) ; extra == "server-testing"
+Requires-Dist: python-gitlab (>=4.4.0)
+Requires-Dist: pyyaml (>=6.0.1,<7.0.0)
+Requires-Dist: responses (>=0.25.7,<0.26.0) ; extra == "server-testing"
+Requires-Dist: sentry-sdk[fastapi] (>=2.17.0,<3.0.0) ; extra == "server" or extra == "server-testing"
+Requires-Dist: sqlalchemy (>=2.0.36,<3.0.0) ; extra == "server" or extra == "server-testing"
+Project-URL: homepage, https://github.com/fedora-copr/logdetective
+Project-URL: issues, https://github.com/fedora-copr/logdetective/issues
+Description-Content-Type: text/markdown
+
+Log Detective
+=============
+
+[![PyPI - Version](https://img.shields.io/pypi/v/logdetective?color=blue)][PyPI Releases]
+
+[PyPI Releases]: https://pypi.org/project/logdetective/#history
+
+A tool, service and RHEL process integration to analyze logs using a Large Language Model (LLM) and a [Drain template miner](https://github.com/logpai/Drain3).
+
+The service that explains logs is available here: https://logdetective.com/explain
+
+Note: if you are looking for code of website logdetective.com it is in [github.com/fedora-copr/logdetective-website](https://github.com/fedora-copr/logdetective-website).
+
+Installation
+------------
+
+**Fedora 41+**
+
+    dnf install logdetective
+
+**From Pypi repository**
+
+The logdetective project is published on the [Pypi repository](https://pypi.org/project/logdetective/). The `pip` tool can be used for installation.
+
+First, ensure that the necessary dependencies for the `llama-cpp-python` project are installed. For Fedora, install `gcc-c++`:
+
+    # for Fedora it will be:
+    dnf install gcc-c++
+
+Then, install the `logdetective` project using pip:
+
+    pip install logdetective
+
+**Local repository install**
+
+Clone this repository and install with pip:
+
+    pip install .
+
+Usage
+-----
+
+To analyze a log file, run the script with the following command line arguments:
+- `file` (required): The path or URL of the log file to be analyzed.
+- `--model` (optional, default: "Mistral-7B-Instruct-v0.3-GGUF"): The path or Hugging space name of the language model for analysis. For models from Hugging Face, write them as `namespace/repo_name`. As we are using LLama.cpp we want this to be in the `gguf` format. If the model is already on your machine it will skip the download.
+- `--filename_suffix` (optional, default "Q4_K.gguf"): You can specify which suffix of the file to use. This option is applied when specifying model using the Hugging Face repository.
+- `--summarizer` DISABLED: LLM summarization option was removed. Argument is kept for backward compatibility only.(optional, default: "drain"): Choose between LLM and Drain template miner as the log summarizer. You can also provide the path to an existing language model file instead of using a URL.
+- `--n_lines` DISABLED: LLM summarization option was removed. Argument is kept for backward compatibility only. (optional, default: 8): The number of lines per chunk for LLM analysis. This only makes sense when you are summarizing with LLM.
+- `--n_clusters` (optional, default 8): Number of clusters for Drain to organize log chunks into. This only makes sense when you are summarizing with Drain.
+- `--skip_snippets` Path to patterns for skipping snippets (in YAML).
+
+Example usage:
+
+    logdetective https://example.com/logs.txt
+
+Or if the log file is stored locally:
+
+    logdetective ./data/logs.txt
+
+Examples of using different models. Note the use of `--filename_suffix` (or `-F`) option, useful for models that were quantized:
+
+    logdetective https://example.com/logs.txt --model QuantFactory/Meta-Llama-3-8B-Instruct-GGUF --filename_suffix Q5_K_S.gguf
+    logdetective https://kojipkgs.fedoraproject.org//work/tasks/3367/131313367/build.log --model 'fedora-copr/granite-3.2-8b-instruct-GGUF' -F Q4_K_M.gguf
+
+Example of altered prompts:
+
+     cp ~/.local/lib/python3.13/site-packages/logdetective/prompts.yml ~/my-prompts.yml
+     vi ~/my-prompts.yml # edit the prompts there to better fit your needs
+     logdetective https://kojipkgs.fedoraproject.org//work/tasks/3367/131313367/build.log --prompts ~/my-prompts.yml
+
+
+Note that streaming with some models (notably Meta-Llama-3) is broken and can be worked around by `no-stream` option:
+
+    logdetective https://example.com/logs.txt --model QuantFactory/Meta-Llama-3-8B-Instruct-GGUF --filename_suffix Q5_K_M.gguf --no-stream
+
+Choice of LLM
+-------------
+
+While Log Detective is compatible with a wide range of LLMs, it does require an instruction tuned model to function properly.
+
+Whether or not the model has been trained to work with instructions can be determined by examining the model card, or simply by checking if it has `instruct` in its name.
+
+When deployed as a server, Log Detective uses `/chat/completions` API as defined by OpenAI. The API must support both `system` and `user` roles, in order to properly work with a system prompt.
+
+Configuration fields `system_role` and `user_role` can be used to set role names for APIs with non-standard roles.
+
+> **Note:**
+> In cases when no system role is available, it is possible to set both fields to the same value. This will concatenate system and standard prompt.
+> This may have negative impact coherence of response.
+
+Real Example
+------------
+
+Let's have a look at a real world example. Log Detective can work with any logs though we optimize it for RPM build logs.
+
+We're going to analyze a failed build of a python-based library that happened in Fedora Koji buildsystem:
+```
+$ logdetective https://kojipkgs.fedoraproject.org//work/tasks/8157/117788157/build.log
+Explanation:
+[Child return code was: 0] : The rpm build process executed successfully without any errors until the 'check' phase.
+
+[wamp/test/test_wamp_component_aio.py::test_asyncio_component] : Pytest found
+two tests marked with '@pytest.mark.asyncio' but they are not async functions.
+This warning can be ignored unless the tests are intended to be run
+asynchronously.
+
+[wamp/test/test_wamp_component_aio.py::test_asyncio_component_404] : Another
+Pytest warning for the same issue as test_asyncio_component.
+
+[-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html] :
+This line is not related to the error, but it is a reminder to refer to Pytest
+documentation for handling warnings.
+
+[=========================== short test summary info
+============================] : This section shows the summary of tests that
+were executed. It shows the number of tests passed, failed, skipped,
+deselected, and warnings.
+
+[FAILED wamp/test/test_wamp_cryptosign.py::TestSigVectors::test_vectors] : A
+failed test is reported with the name of the test file, the name of the test
+method, and the name of the test case that failed. In this case,
+TestSigVectors::test_vectors failed.
+
+[FAILED
+websocket/test/test_websocket_protocol.py::WebSocketClientProtocolTests::test_auto_ping]
+: Another failed test is reported with the same format as the previous test. In
+this case, it is WebSocketClientProtocolTests::test_auto_ping that failed.
+
+[FAILED websocket/test/test_websocket_protocol.py::WebSocketServerProtocolTests::test_interpolate_server_status_template]
+: A third failed test is reported with the same format as the previous tests.
+In this case, it is
+WebSocketServerProtocolTests::test_interpolate_server_status_template that
+failed.
+
+[FAILED websocket/test/test_websocket_protocol.py::WebSocketServerProtocolTests::test_sendClose_reason_with_no_code]
+: Another failed test is reported. This time it is
+WebSocketServerProtocolTests::test_sendClose_reason_with_no_code.
+
+[FAILED websocket/test/test_websocket_protocol.py::WebSocketServerProtocolTests::test_sendClose_str_reason]
+: Another failed test is reported with the same test file and test method name,
+but a different test case name: test_sendClose_str_reason.
+
+[==== 13 failed, 195 passed, 64 skipped, 13 deselected, 2 warnings in 6.55s
+=====] : This is the summary of all tests that were executed, including the
+number of tests that passed, failed, were skipped, deselected, or produced
+warnings. In this case, there were 13 failed tests among a total of 211 tests.
+
+[error: Bad exit status from /var/tmp/rpm-tmp.8C0L25 (%check)] : An error
+message is reported indicating that the 'check' phase of the rpm build process
+failed with a bad exit status.
+```
+
+It looks like a wall of text. Similar to any log. The main difference is that here we have the most significant lines of a logfile wrapped in `[ ] : ` and followed by textual explanation of the log text done by mistral 7b.
+
+
+Contributing
+============
+
+Contributions are welcome! Please submit a pull request if you have any improvements or new features to add. Make sure your changes pass all existing tests before submitting.
+For bigger code changes, please consult us first by creating an issue.
+
+We are always looking for more annotated snippets that will increase the quality of Log Detective's results. The contributions happen in our website: https://logdetective.com/
+
+Log Detective performs several inference queries while evaluating a log file. Prompts are stored in a separate file (more info below: https://github.com/fedora-copr/logdetective?tab=readme-ov-file#system-prompts). If you have an idea for improvements to our prompts, please open a PR and we'd happy to test it out.
+
+To develop Log Detective, you should fork this repository, clone your fork, and install dependencies using pip:
+
+    git clone https://github.com/yourusername/logdetective.git
+    cd logdetective
+    pip install .
+
+Make changes to the code as needed and run pre-commit.
+
+Tests
+-----
+
+Tests for code used by server must placed in the `./tests/server/` path, while tests for general
+code must be in the `./tests/base/` path.
+
+The [tox](https://github.com/tox-dev/tox) is used to manage tests. Please install `tox` package into your distribution and run:
+
+    tox
+
+This will create a virtual environment with dependencies and run all the tests. For more information follow the tox help.
+
+To run only a specific test execute this:
+
+    tox run -e style # to run flake8
+
+or
+
+    tox run -e lint # to run pylint
+
+Tox environments for base and server tests are separate, each installs different dependencies.
+
+Running base tests:
+
+    tox run -e pytest_base
+
+Running server tests:
+
+    tox run -e pytest_server
+
+To run server test suite you will need postgresql client utilities.
+
+    dnf install postgresql
+
+Visual Studio Code testing with podman/docker-compose
+-----------------------------------------------------
+
+- In `Containerfile`, add `debugpy` as a dependency
+
+```diff
+-RUN pip3 install llama_cpp_python==0.2.85 sse-starlette starlette-context \
++RUN pip3 install llama_cpp_python==0.2.85 sse-starlette starlette-context debugpy\
+```
+
+- Rebuild server image with new dependencies
+
+```
+make rebuild-server
+```
+
+- Forward debugging port in `docker-compose.yaml` for `server` service.
+
+```diff
+     ports:
+       - "${LOGDETECTIVE_SERVER_PORT:-8080}:${LOGDETECTIVE_SERVER_PORT:-8080}"
++      - "${VSCODE_DEBUG_PORT:-5678}:${VSCODE_DEBUG_PORT:-5678}"
+```
+
+- Add `debugpy` code in a logdetective file where you want to stop at first.
+
+```diff
++import debugpy
++debugpy.listen(("0.0.0.0", 5678))
++debugpy.wait_for_client()
+```
+
+- Prepare `.vscode/lunch.json` configuration for Visual Studio Code (at least the following configuration is needed)
+
+```json
+{
+  "version": "0.2.0",
+  "configurations": [
+    {
+      "name": "Python Debugger: Remote Attach",
+      "type": "debugpy",
+      "request": "attach",
+      "connect": {
+        "host": "localhost",
+        "port": 5678
+      },
+      "pathMappings": [
+        {
+          "localRoot": "${workspaceFolder}",
+          "remoteRoot": "/src"
+        }
+      ]
+    }
+  ]
+}
+```
+
+- Run the server
+
+```
+podman-compose up server
+```
+
+- Run Visual Stdio Code debug configuration named *Python Debug: Remote Attach*
+
+Visual Studio Code CLI debugging
+--------------------------------
+
+When debugging the CLI application, the `./scripts/debug_runner.py` script can be used
+as a stand in for stump script created during package installation.
+
+Using `launch.json`, or similar alternative, arguments can be specified for testing.
+
+Example:
+
+```
+{
+    "version": "0.2.0",
+    "configurations": [
+        {
+            "name": "Python: Debug Installed Module",
+            "type": "debugpy",
+            "request": "launch",
+            "console": "integratedTerminal",
+            "program": "${workspaceFolder}/scripts/debug_runner.py",
+            "args": [<URL_OF_A_LOG>]
+        }
+    ]
+}
+```
+
+Server
+======
+
+FastApi based server is implemented in `logdetective/server.py`. In order to run it in a development mode,
+simply start llama-cpp-python server with your chosen model as described in llama-cpp-python [docs](https://llama-cpp-python.readthedocs.io/en/latest/server/#running-the-server).
+
+Afterwards, start the logdetective server with `fastapi dev logdetective/server.py --port 8080`.
+Requests can then be made with post requests, for example:
+
+    curl --header "Content-Type: application/json" --request POST --data '{"url":"<YOUR_URL_HERE>"}' http://localhost:8080/analyze
+
+For more accurate responses, you can use `/analyze/staged` endpoint. This will submit snippets to model for individual analysis first.
+Afterwards the model outputs are used to construct final prompt. This will take substantially longer, compared to plain `/analyze`
+
+    curl --header "Content-Type: application/json" --request POST --data '{"url":"<YOUR_URL_HERE>"}' http://localhost:8080/analyze/staged
+
+We also have a Containerfile and composefile to run the logdetective server and llama server in containers.
+
+Before doing `podman-compose up`, make sure to set `MODELS_PATH` environment variable and point to a directory with your local model files:
+```
+$ export MODELS_PATH=/path/to/models/
+$ ll $MODELS_PATH
+-rw-r--r--. 1 tt tt 3.9G apr 10 17:18  mistral-7b-instruct-v0.2.Q4_K_S.gguf
+```
+
+If the variable is not set, `./models` is mounted inside by default.
+
+Model can be downloaded from [our Hugging Space](https://huggingface.co/fedora-copr) by:
+```
+$ curl -L -o models/mistral-7b-instruct-v0.3.Q4_K.gguf https://huggingface.co/fedora-copr/Mistral-7B-Instruct-v0.3-GGUF/resolve/main/ggml-model-Q4_K.gguf
+```
+
+Filtering snippet analysis by relevance
+---------------------------------------
+
+When using `/analyze/staged` API, it is possible to enable filtering analyzed snippets by their estimated relavance, submitting only those with highest meansure of relevance for final analysis.
+
+**Note**: This feautre requires LLM provider with support for JSON structured output. Smaller models, even though techically capable of providing structured output, may not be able to appropriatelly estimate snippet relevance.
+
+Filtering is disabled by default and must be enabled by setting value of `top_k_snippets` field in `general` section of server configuration. Value indicates number of snippets with highest estimated relavance that will be submitted for final analysis.
+
+Example:
+
+```
+general:
+  devmode: False
+  packages:
+    - .*
+  excluded_packages:
+    - ^redhat-internal-.*
+  top_k_snippets: 10
+```
+
+If all snippets are rated the same, the filtering is skipped and warning raised in logs.
+Values higher than total number of snippets, as set by `max_clusters` in the `extrator` section of config, also result in filtering being skipped.
+
+Generate a new database revision with alembic
+---------------------------------------------
+
+Modify the database models (`logdetective/server/database/model.py).
+
+Generate a new database revision with the command:
+
+**Warning**: this command will start up a new server
+and shut it down when the operation completes.
+
+```
+CHANGE="A change comment" make alembic-generate-revision
+```
+
+Our production instance
+-----------------------
+
+Our FastAPI server and model inference server run through `podman-compose` on an
+Amazon AWS intance. The VM is provisioned by an
+[ansible playbook](https://pagure.io/fedora-infra/ansible/blob/main/f/roles/logdetective/tasks/main.yml).
+
+You can control the server through:
+
+```
+cd /root/logdetective
+podman-compose -f docker-compose-prod.yaml ...
+```
+
+The `/root` directory contains valuable data. If moving to a new instance,
+please backup the whole directory and transfer it to the new instance.
+
+Fore some reason, we need to manually run this command after every reboot:
+
+```
+nvidia-ctk cdi generate --output=/etc/cdi/nvidia.yaml
+```
+
+HTTPS certificate generated through:
+
+```
+certbot certonly --standalone -d logdetective01.fedorainfracloud.org
+```
+
+Certificates need to be be placed into location specified by the`LOGDETECTIVE_CERTDIR`
+env var and the service should be restarted.
+
+Querying statistics
+-------------------
+
+You can retrieve statistics about server requests and responses over a specified time period
+using either a browser, the `curl` or the `http` command (provided by the `httpie` package).
+
+When no time period is specified, the query defaults to the last 2 days:
+
+You can view requests, responses and emojis statistics
+ - for the `/analyze` endpoint at http://localhost:8080/metrics/analyze
+ - for the `/analyze-staged` endpoint at http://localhost:8080/metrics/analyze-staged.
+ - for the requests coming from gitlab: http://localhost:8080/metrics/analyze-gitlab.
+
+You can retrieve single svg images at the following endpoints:
+ - http://localhost:8080/metrics/analyze/requests
+ - http://localhost:8080/metrics/analyze/responses
+ - http://localhost:8080/metrics/analyze-staged/requests
+ - http://localhost:8080/metrics/analyze-staged/responses
+ - http://localhost:8080/metrics/analyze-gitlab/requests
+ - http://localhost:8080/metrics/analyze-gitlab/responses
+ - http://localhost:8080/metrics/analyze-gitlab/emojis
+
+Examples:
+
+```
+http GET "localhost:8080/metrics/analyze/requests" > /tmp/plot.svg
+curl "localhost:8080/metrics/analyze/staged/requests" > /tmp/plot.svg
+```
+
+You can specify the time period in hours, days, or weeks.
+The time period:
+ - cannot be less than one hour
+ - cannot be negative
+ - ends at the current time (when the query is made)
+ - starts at the specified time interval before the current time.
+
+Examples:
+
+```
+http GET "localhost:8080/metrics/analyze/requests?hours=5" > /tmp/plot_hours.svg
+http GET "localhost:8080/metrics/analyze/requests?days=5" > /tmp/plot_days.svg
+http GET "localhost:8080/metrics/analyze/requests?weeks=5" > /tmp/plot_weeks.svg
+```
+
+System Prompts
+--------------
+
+Prompt templates used by Log Detective are stored in the `prompts.yml` file.
+It is possible to modify the file in place, or provide your own.
+In CLI you can override prompt templates location using `--prompts` option,
+while in the container service deployment the `LOGDETECTIVE_PROMPTS` environment variable
+is used instead.
+
+Prompts need to have a form compatible with python [format string syntax](https://docs.python.org/3/library/string.html#format-string-syntax)
+with spaces, or replacement fields marked with curly braces, `{}` left for insertion of snippets.
+
+Number of replacement fields in new prompts, must be the same as in originals.
+Although their position may be different.
+
+
+Skip Snippets
+-------------
+
+Certain log chunks may not contribute to the analysis of the problem under any circumstances.
+User can specify regular expressions, matching such log chunks, along with simple description,
+using Skip Snippets feature.
+
+Patterns to be skipped must be defined yaml file as a dictionary, where key is a description
+and value is a regular expression. For example:
+
+```
+child_exit_code_zero: "Child return code was: 0"
+```
+
+Special care must be taken not to write a regular expression which may match
+too many chunks, or which may be evaluated as data structure by the yaml parser.
+
+Example of a valid pattern definition file: `logdetective/skip_patterns.yml`,
+can be used as a starting point and is used as a default if no other definition is provided.
+
+
+Extracting snippets with csgrep
+-------------------------------
+
+When working with logs containing messages from GCC, it can be beneficial to employ
+additional extractor based on `csgrep` tool, to ensure that the messages are kept intact.
+Since `csgrep` is not available as a python package, it must be installed separately,
+with a package manager or from [source](https://github.com/csutils/csdiff).
+
+The binary is available as part of `csdiff` package on Fedora.
+
+```
+dnf install csdiff
+```
+
+When working with CLI Log Detective, the csgrep extractor can be activated using option `--csgrep`.
+While in server mode, the `csgrep` field in `extractor` config needs to be set to `true`.
+
+```
+csgrep: true
+```
+
+Both options are disabled by default and error will be produced if the option is used,
+but `csgrep` is not present in the $PATH.
+
+The container images are built with `csdiff` installed.
+
+
+License
+-------
+
+This project is licensed under the Apache-2.0 License - see the LICENSE file for details.
+

logdetective-2.11.0.dist-info/RECORD

@@ -0,0 +1,40 @@
+logdetective/__init__.py,sha256=VqRngDcuFT7JWms8Qc_MsOvajoXVOKPr-S1kqY3Pqhc,59
+logdetective/constants.py,sha256=aCwrkBrDdS_kbNESK-Z-ewg--DSzodV2OMgwEq3UE38,2456
+logdetective/drain3.ini,sha256=ni91eCT1TwTznZwcqWoOVMQcGEnWhEDNCoTPF7cfGfY,1360
+logdetective/extractors.py,sha256=vT-je4NkDgSj9rRtSeLpqBU52gIUnnVgJPHFbVihpCw,5993
+logdetective/logdetective.py,sha256=S0abGrAQH2oi0MRisCV64Sa1UXdQLIfXFBA4tYAYqhM,6896
+logdetective/models.py,sha256=uczmQtWFgSp_ZGssngdTM4qzPF1o64dCy0469GoSbjQ,2937
+logdetective/prompts-summary-first.yml,sha256=kmyMFQmqFXpojkz7p3CyCWCPxMpFLpfDdMGisB4YwL0,808
+logdetective/prompts-summary-only.yml,sha256=8U9AMJV8ePW-0CoXOXlQoO92DAJDeutIT8ntSkkm6W0,470
+logdetective/prompts.yml,sha256=i3z6Jcb4ScVi7LsxOpDlKiXrcvql3qO_JnLzkAKMn1c,3870
+logdetective/remote_log.py,sha256=28QvdQiy7RBnd86EKCq_A75P21gSNlCbgxJe5XAe9MA,2258
+logdetective/server/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
+logdetective/server/compressors.py,sha256=y4aFYJ_9CbYdKuAI39Kc9GQSdPN8cSJ2c_VAz3T47EE,5249
+logdetective/server/config.py,sha256=cKUmNCJyNyEid0bPTiUjr8CQuBYBab5bC79Axk2h0z8,2525
+logdetective/server/database/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
+logdetective/server/database/base.py,sha256=HSV2tgye7iYTDzJD1Q5X7_nlLuTMIFP-hRVQMYxngHQ,2073
+logdetective/server/database/models/__init__.py,sha256=zoZMCt1_7tewDa6eEIIX_xrdN-tLegSiPNg5NiYaV3o,850
+logdetective/server/database/models/exceptions.py,sha256=4ED7FSSA1liV9-7VIN2BwUiz6XlmP97Y1loKnsoNdD8,507
+logdetective/server/database/models/koji.py,sha256=HNWxHYDxf4JN9K2ue8-V8dH-0XY5ZmxqH7Y9lAIbILA,6436
+logdetective/server/database/models/merge_request_jobs.py,sha256=MxiAVKQIsQMbFylBsmYBmVXYvid-4_5mwwXLfWdp6_w,19965
+logdetective/server/database/models/metrics.py,sha256=4xsUdbtlp5PI1-iJQc5Dd8EPDgVVplD9hJRWeRDn43k,15443
+logdetective/server/emoji.py,sha256=zSaYtLpSkpRCXpjMWnHR1bYwkmobMJASZ7YNalrd85U,5274
+logdetective/server/exceptions.py,sha256=WN715KLL3ya6FiZ95v70VSbNuVhGuHFzxm2OeEPWQCw,981
+logdetective/server/gitlab.py,sha256=putpnf8PfGsCZJsqWZA1rMovRGnyagoQmgpKLqtA-aQ,16743
+logdetective/server/koji.py,sha256=LG1pRiKUFvYFRKzgQoUG3pUHfcEwMoaMNjUSMKw_pBA,5640
+logdetective/server/llm.py,sha256=bmA6LsV80OdO60q4WLoKuehuVDEYq-HhBAYcZeLfrv8,10150
+logdetective/server/metric.py,sha256=wLOpgcAch3rwhPA5P2YWUeMNAPsvRGseRjH5HlTb7JM,4529
+logdetective/server/models.py,sha256=AJyycAEEl2o6TH4eAqVMlt5woqAB5M8ze2L575leA_I,19835
+logdetective/server/plot.py,sha256=8LERgY3vQckaHZV2PZfOrZT8CjCAiji57QCmRW24Rfo,14697
+logdetective/server/server.py,sha256=JueU-5c8t9h1CZy4gtoEeT8VSEirpeS0K3wrfqTPvAc,25381
+logdetective/server/templates/base_response.html.j2,sha256=BJGGV_Xb0Lnue8kq32oG9lI5CQDf9vce7HMYsP-Pvb4,2040
+logdetective/server/templates/gitlab_full_comment.md.j2,sha256=4UujUzl3lmdbNEADsxn3HVrjfUiUu2FvUlp9MDFGXQI,2321
+logdetective/server/templates/gitlab_short_comment.md.j2,sha256=2krnMlGqqju2V_6pE0UqUR1P674OFaeX5BMyY5htTOQ,2022
+logdetective/server/utils.py,sha256=0BZ8WmzXNEtkUty1kOyFbBxDZWL0Icc8BUrxuHw9uvs,4015
+logdetective/skip_snippets.yml,sha256=reGlhPPCo06nNUJWiC2LY-OJOoPdcyOB7QBTSMeh0eg,487
+logdetective/utils.py,sha256=yalhySOF_Gzmqx_Ft9qad3TplAfZ6LOmauGXEJfKWiE,9803
+logdetective-2.11.0.dist-info/METADATA,sha256=SdXBkYlSoiVXhgPiM23luYQa0Y_BCX_el_mxTdJc0Zw,23273
+logdetective-2.11.0.dist-info/WHEEL,sha256=zp0Cn7JsFoX2ATtOhtaFYIiE2rmFAD4OcMhtUki8W3U,88
+logdetective-2.11.0.dist-info/entry_points.txt,sha256=3K_vXja6PmcA8sNdUi63WdImeiNhVZcEGPTaoJmltfA,63
+logdetective-2.11.0.dist-info/licenses/LICENSE,sha256=z8d0m5b2O9McPEK1xHG_dWgUBT6EfBDz6wA0F7xSPTA,11358
+logdetective-2.11.0.dist-info/RECORD,,

{logdetective-0.4.0.dist-info → logdetective-2.11.0.dist-info}/WHEEL

@@ -1,4 +1,4 @@
 Wheel-Version: 1.0
-Generator: poetry-core 2.1.1
+Generator: poetry-core 2.2.1
 Root-Is-Purelib: true
 Tag: py3-none-any