Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Test config files contain typos that silently disable them

Open Beginner friendly
  • Is something wrong?
#331 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
85/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
cpp, github-actions
Domain
backend, testing

Research direction

The two bad settings are in testing/lslcfgs/ipv4_lsl100.cfg and ipv6_lsl100.cfg (use_protocol_version under [tuning], which should be UseProtocolVersion) and in testing/lslcfgs/default.cfg (KnownPeers without braces). Read parse_set in src/api_config.cpp to confirm the accepted list syntax and the exact key spelling, then fix the three lines. Done when the protocol-1.00 configs select 1.00, KnownPeers parses to a non-empty list, and the unit tests pass in the cppcmake.yml workflow.

Written by the indexing model from the issue text.

Description

bug

liblsl ignores unknown keys silently, and two of the test configurations in testing/lslcfgs/ don't do what they intend:

  • ipv4_lsl100.cfg and ipv6_lsl100.cfg set use_protocol_version=100 under [tuning], but the key is UseProtocolVersion (keys are case-sensitive). Tests meant to run with data protocol 1.00 run with 1.10.
  • default.cfg sets KnownPeers=127.0.0.1 without braces. parse_set (src/api_config.cpp) only accepts {...}, so the list is empty. CI copies this file into the working directory before the unit tests (cppcmake.yml).

Fix the two keys. It might also be worth logging a warning for unknown keys and for list values without braces.

Dominant language
C++
Stars
179
Forks
90
Avg merge
1d 3h
Merged PRs (30d)
27

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sccn/liblsl

All issues in sccn/liblsl

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.