The corresponding config_receive() also doesn't receive them. While patterns and size filters are primarily client-side concerns (they filter files before scanning), the server is unaware of which patterns were used, which could be useful for logging or future features.
Location
src/shared/config.c:94-134
Suggested Fix
Consider whether these fields need to be transmitted. If not needed on the server side, add a comment explaining why they are intentionally excluded. If they should be transmitted for logging/debugging, add serialization for them.
For now, at minimum document why patterns are not sent to the server (they are only used for client-side scanning).
Severity
Low
Category
Quality
## Description
In `src/shared/config.c`, the `config_send()` function (lines 94-134) transmits the config over the wire, but it does NOT send:
1. `exclude_patterns` and `exclude_count`
2. `include_patterns` and `include_count`
3. `max_size` and `min_size`
4. `show_progress`, `dry_run`, `ssh_port`, `transport`, `ssh_destination`
The corresponding `config_receive()` also doesn't receive them. While patterns and size filters are primarily client-side concerns (they filter files before scanning), the server is unaware of which patterns were used, which could be useful for logging or future features.
## Location
`src/shared/config.c:94-134`
## Suggested Fix
Consider whether these fields need to be transmitted. If not needed on the server side, add a comment explaining why they are intentionally excluded. If they should be transmitted for logging/debugging, add serialization for them.
For now, at minimum document why patterns are not sent to the server (they are only used for client-side scanning).
## Severity
Low
## Category
Quality
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Description
In
src/shared/config.c, theconfig_send()function (lines 94-134) transmits the config over the wire, but it does NOT send:exclude_patternsandexclude_countinclude_patternsandinclude_countmax_sizeandmin_sizeshow_progress,dry_run,ssh_port,transport,ssh_destinationThe corresponding
config_receive()also doesn't receive them. While patterns and size filters are primarily client-side concerns (they filter files before scanning), the server is unaware of which patterns were used, which could be useful for logging or future features.Location
src/shared/config.c:94-134Suggested Fix
Consider whether these fields need to be transmitted. If not needed on the server side, add a comment explaining why they are intentionally excluded. If they should be transmitted for logging/debugging, add serialization for them.
For now, at minimum document why patterns are not sent to the server (they are only used for client-side scanning).
Severity
Low
Category
Quality