make posix timer family functions reject itimer timer ids
we provide two sets of similar apis:
* BSD itimer api (setitimer, ITIMER_xxx, and friends)
* posix timer api (timer_create and friends)
for some reason, some of posix timer functions
(namely timer_settime, timer_gettime, timer_getoverrun,
timer_delete) are allowed to operate on timer_id=2,
which actually belongs to the BSD itimer. (ITIMER_PROF)
it seems that it has always been this way since they were
introduced on the nathanw_sa branch in 2001.
10 years later, in 2011, it got a bit worse by the addition
of ITIMER_MONOTONIC, which is also accepted by the posix
timer functions.
as there seems to be no reasons to give the special
[2 lines not shown]
regal: Update to 0.39.0
Changes:
v0.39.0
We're happy to announce Regal v0.39.0, featuring 3 new linter rules,
many language server improvements, and much faster linting!
- New Rule: `use-array-flatten`
- New Rule: `use-object-union-n`
- New Rule: `equals-over-count`
- Initial support for the rq engine has been added - thanks charlesdaniels!
- Various imprevements
- Bug fixes
- Dependencies updates, in particular OPA v1.14.0
opa: Update to 1.14.1
Changes:
v1.14.1
This is a patch release collecting two bug fixes and various dependency
updates for Golang standard library and common package
vulnerabilities.
These bug fixes include a revert of the rule indexer tweaks shipped in
1.14.0, which had caused unexpected lookup failures for some users. (We
expect to properly fix the issue in 1.15.0, but for now, a revert is
the quicker choice.)
v1.14.0
This release contains a mix of new features, performance improvements,
and bugfixes. Notably:
- Improved rule indexing of variable assignments and `x in {...}` expressions
[22 lines not shown]
[clang-tidy] Adds do-while support to performance-inefficient-string-concatenation (#186607)
Closes #186362
---------
Co-authored-by: Victor Chernyakin <chernyakin.victor.j at outlook.com>
Co-authored-by: EugeneZelenko <eugene.zelenko at gmail.com>
