pmcannotate: avoid accessing uninitialized local variables
Initialize `tbfl` and `tofl` to NULL, and check whether they are
non-NULL before calling remove(3) on them, to avoid warnings from clang
21 similar to:
usr.sbin/pmcannotate/pmcannotate.c:746:3: error: variable 'tbfl' is uninitialized when used here [-Werror,-Wuninitialized]
746 | FATAL(exec, "%s: Impossible to locate the binary file\n",
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
747 | exec);
| ~~~~~
usr.sbin/pmcannotate/pmcannotate.c:57:9: note: expanded from macro 'FATAL'
57 | remove(tbfl); \
| ^~~~
usr.sbin/pmcannotate/pmcannotate.c:695:12: note: initialize the variable 'tbfl' to silence this warning
695 | char *tbfl, *tofl, *tmpdir;
| ^
| = NULL
usr.sbin/pmcannotate/pmcannotate.c:746:3: error: variable 'tofl' is uninitialized when used here [-Werror,-Wuninitialized]
[13 lines not shown]
bsnmpd: avoid warnings about too-long initializer strings
Mark `UTC` as `__non_string`, to avoid a warning from clang 21 similar
to:
usr.sbin/bsnmpd/tools/libbsnmptools/bsnmptc.c:339:29: error: initializer-string for character array is too long, array size is 3 but initializer has size 4 (including the null terminating character); did you mean to use the 'nonstring' attribute? [-Werror,-Wunterminated-string-initialization]
--- all_subdir_usr.sbin ---
339 | static const char UTC[3] = "UTC";
| ^~~~~
MFC after: 3 days
py-test-jupyter: updated to 0.11.0
0.11.0
Drop 3.8, Start testing on 3.13, 3.14 and 3.14t, update precommit
Improved doc string for jp_fetch to include how to provide query parameters in GET and json data in POST
Restore the ability to override a serverapp's HTTP port
Pull up following revision(s) (requested by kre in ticket #1990):
bin/sh/arithmetic.c: revision 1.6
Fix a bug in syntax of the ?: operator
The ?: operator has 3 sub-expressions. The first (before the ?)
is an "or-list" (generic conditional expression). The third,
after the : is another cond-expr (might be another ?: operator).
Those we handled properly.
The middle expression however, according to the C standard,
which is what the shell is supposed (to the extent it is
required to implement) to support, can be any expression at all.
We had that correct when an assignment was the highest level
(or if you prefer, lowest precedence) operators accepted by the
syntax (which is all that is required by POSIX).
[14 lines not shown]
Pull up following revision(s) (requested by kre in ticket #1211):
bin/sh/arithmetic.c: revision 1.6
Fix a bug in syntax of the ?: operator
The ?: operator has 3 sub-expressions. The first (before the ?)
is an "or-list" (generic conditional expression). The third,
after the : is another cond-expr (might be another ?: operator).
Those we handled properly.
The middle expression however, according to the C standard,
which is what the shell is supposed (to the extent it is
required to implement) to support, can be any expression at all.
We had that correct when an assignment was the highest level
(or if you prefer, lowest precedence) operators accepted by the
syntax (which is all that is required by POSIX).
[14 lines not shown]
py-jupyter_client: updated to 8.7.0
8.7.0
Enhancements made
- allow configuring client_class and client_factory
- Support date serialization in messages
- feat: added `--missing` flag to list and remove subcommands
- Set protocol version to 5.4
Bugs fixed
- don't include link-local addresses (169.254) in public_ips
- jupyter-run: avoid traceback for NoSuchKernel
Maintenance and upkeep improvements
- upgrade pypy
[12 lines not shown]
py-django-tasks: updated to 0.10.0
0.10.0
Breaking changes
Remove enqueue_on_commit functionality
What's Changed
Test against Django 6.0 in CI
Add Python 3.14 support in CI
Set import path of mocked function conditionally
py-testtools: updated to 2.8.2
2.8.2
Changes
Fully migrate away from Launchpad to GitHub.
Improvements
* Support binary contents in ``FileContains`` matcher.
* Allow stream=None to be passed to various TestResult
classes that now support verbosity; fixes a regression
from 2.8.0.
