Skip to content

Conversation

@hendrikmuhs
Copy link
Contributor

@hendrikmuhs hendrikmuhs commented Jul 15, 2025

Migrate to boost process v2, fixes compile problems on newer versions of boost.

In addition:

  • fix autowrap API breakage
  • fix doc build
  • fix concurrency issue in keyvi index which appeared after boost process update on Mac

#else
#include <sys/resource.h>

#include <string>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why is it needed?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

string is used on line 39. However it obviously worked before, because it is implicitly included from on of the other includes.

The reason why this pops up now: The code is checked with cpplint, a static code checker. It produces an error called "include what you use". cpplint must pass as part of the checkstyle workflow run on the PR. checkstyle runs only on files that change. So with other words: Because I made a change to this file, cpplint forced me to cleanup.

#include <chrono> // NOLINT
#include <string>
#include <thread> // NOLINT
#include <vector>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same here

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same answer: string and vector are used in this file, however this file hasn't been touched since the introduction of cpplint as CI workflow.

@hendrikmuhs hendrikmuhs merged commit 7ce97cb into KeyviDev:master Jul 18, 2025
17 checks passed
@hendrikmuhs hendrikmuhs deleted the boost-process-v2 branch July 18, 2025 06:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants