|
1 | 1 | # Frequently Asked Questions
|
2 | 2 |
|
3 |
| -A compiled list of FAQs that may come in handy. |
| 3 | +A compiled list of frequently asked questions that may come in handy. |
4 | 4 |
|
5 |
| -## Import ot found? |
| 5 | +## Import not found? |
6 | 6 |
|
7 |
| -If you are getting an "import not found" error, it is likely because the base folder is always `src`. Always run the program from the `src` folder or use the commands inside the Makefile. |
| 7 | +If you are encountering an "import not found" error, it is likely because the base folder is always `src`. Make sure to run the program from the `src` folder or use the commands inside the Makefile. |
8 | 8 |
|
9 |
| -If you have something in `src/lib` and want to use it, import it as follows: |
| 9 | +If you have something in `src/lib` and want to use it, import it as shown below: |
10 | 10 |
|
11 | 11 | ```python
|
12 | 12 | import lib # or
|
13 | 13 | from lib import ...
|
14 | 14 | ```
|
15 | 15 |
|
| 16 | +# Why use POST call to retrieve recommendations and aggregated recommendations? |
| 17 | + |
| 18 | +For these calls, we require a JSON type body with at least `{}`. This allows us to handle nested filters such as `task_id` and `severity` inside the filters. Using query parameters and GET calls would be less suitable for this purpose. However, one can modify the pathname, like changing `get-`, to make it more convenient. |
| 19 | + |
16 | 20 | # Why are env.docker and .env different?
|
17 | 21 |
|
18 |
| -If you are only running the program using Docker, then you only need to worry about `.env.docker`. |
| 22 | +If you are running the program exclusively using Docker, then you only need to concern yourself with `.env.docker`. |
19 | 23 |
|
20 |
| -As the addresses tend to be different in a Docker environment compared to a local environment, you need different values to resolve the addresses. |
| 24 | +Since the addresses can differ between a Docker environment and a local environment, you need different values to resolve the addresses. |
21 | 25 |
|
22 |
| -For example, if you have your program outside Docker (locally) and want to access a database, you may use: |
| 26 | +For example, if your program is outside Docker (locally) and you want to access a database, you may use: |
23 | 27 |
|
24 | 28 | ```
|
25 | 29 | POSTGRES_SERVER=localhost
|
@@ -50,3 +54,7 @@ We have a predefined structure that input must adhere to called `Content`. You c
|
50 | 54 |
|
51 | 55 | Inside the db model called `Findings`, there is a method `from_data` which can be modified to adapt the changes.
|
52 | 56 | `VulnerablityReport` also has `create_from_flama_json` that must be adjusted accordingly to make sure the Generation side also works.
|
| 57 | + |
| 58 | +# Does it make sense to Mock LLM? |
| 59 | + |
| 60 | +While we don't strive for accuracy, it would still make sense to mock LLM methods to ensure that methods for finding and interacting properly with LLM class methods work correctly. Nevertheless, it is still difficult to extract meaningful test outputs based on only prompts as input. |
0 commit comments