Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
Introduces a new bit "Cloud Discovery Service Announcer"
into the PID_VENDOR_BUILTIN_ENDPOINT_SET parameter
send with DATA(P) messages to indicate that the DATA(P) message is
coming from Cloud Discovery Service.
|
|
Build the wsar_html_zip instead of wsar_html and (re-)publish it at
https://www.wireshark.org/download/docs/. Move the doxygen_all job to
the daily schedule section.
|
|
|
|
Fixup some variable names.
|
|
Change-Id: I0096d047fb6eab882ad943090f5c4a6c1864671a
|
|
|
|
N.B. Didn't find the spec for this, but the pipeline warning is as follows
Field 'RDMA Provider Type (RDMA_PRTYPE)' (nvme.cmd.get_logpage.identify.rcrd.tsas.rdma_prtype) has a conflicting entry in its value_string: 3 is at indices 2 (RoCE (v1)) and 4 (iWARP)
|
|
RTO was calculated on the last packet increasing the nextseq,
which ended on not identifying the original right packet later
retransmitted. We now consider the eldest unacked packet as
being likely to be the one to be retransmitted, and it gives a
much more accurate RTO value. Closes #12259.
|
|
|
|
The files we need to submit to Coverity might be too large to upload
over HTTP, so use their URL submission method. We won't have a usable
artifact URL until after each cov-build job runs, so we need to submit
our URLs in separate jobs.
|
|
|
|
There are three ways to reuse configuration blobs in .gitlab-ci.yml: The
"extends" keyword, YAML anchors, and "!reference" tags. As noted in
https://gitlab.com/gitlab-org/gitlab/-/issues/322992, only the last
method works for job rules. Clean up our common rules and apply them
using "!reference".
|
|
|
|
Update manuf, services enterprise numbers, translations, and other items.
|
|
In the MP_REACH_NLRI attribute, break out the Next Hop field into
constituent subfields for different address types. Add a field name
for the NLRI to make it filterable and consistent with the standard
NLRI attribute. Also add a field name for the withdrawn routes for
the MP_UNREACH_NLRI attribute.
Correct a comment about RFC 2545 and the handling of what it allows,
viz. IPv6 next hop addresses being optionally followed by link-local
next hop addresses.
The above has nothing to do with RFC 2283 allowing multiple <afi, safi,
..., NLRI> tuples (which was impossible to implement, and RFC 2858
later explicitly disallowed), so correct the comment about that.
|
|
Partial fix for #16727
|
|
"int argc, char **argv". If you're looping from 1 to argc, the index
should just be an int; there's no advantage to making it a size_t.
|
|
It looks like "extends" and YAML anchors don't work for scheduling
rules, at least for the way we're using them. Use explicit rules for
scheduled jobs.
|
|
|
|
Rules don't seem to support schedule variables.
|
|
|
|
|
|
Track our preferred version of clang using $CLANG_VERSION in
.gitlab-ci.yml. Update validate-clang-check.sh to accept a clang
version.
|
|
|
|
Move commonly-used rules to their own hidden jobs. Use ".if-merged" to
ensure that our production build and test jobs are run automatically in
wireshark/wireshark and can be run manually in forks.
Note the new manual behavior in the Developer's Guide.
|
|
Trying to upload cov-build output on Windows is currently failing
because the file is too large. Expose the build file as an artifact and
submit its URL instead.
|
|
Only run build:ubuntu-dist from pushes, and allow it to be manually
built outside the main repository.
|
|
Switch the recent analysis builds from only/when to rules.
Switch the API reference and VS Code Analysis builds to daily.
Remove a no-longer-useful URL.
|
|
Most of the time, the return value tells us nothing useful, as we've
already decided that we're perfectly willing to live with string
truncation. Hopefully this keeps Coverity from whining that those
routines could return an error code (NARRATOR: They don't) and thus that
we're ignoring the possibility of failure (as indicated, we've already
decided that we can live with string truncation, so truncation is *NOT*
a failure).
|
|
|
|
The packet pool lifetime is too short for data added to the pinfo
structure
Fixes #17367
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Add a "coverity-visual-c++" job which runs Coverity Scan Build on
Windows using Visual C++ and submits the build output to Coverity. Based
on
https://www.synopsys.com/blogs/software-security/integrating-coverity-scan-with-gitlab-ci
|
|
Add a "coverity-gcc" job which runs Coverity Scan Build on Ubuntu using
GCC and submits the build output to Coverity. Based on
https://www.synopsys.com/blogs/software-security/integrating-coverity-scan-with-gitlab-ci
and
https://gitlab.gnome.org/GNOME/glib/-/blob/8f57a5b9/.gitlab-ci.yml#L481
|
|
We don't set rec.rec_header.packet_header.pack_flags, so don't set
WTAP_HAS_PACK_FLAGS in the presence flags. (Copy-and-pasteo?)
|
|
This is needed to get the COL_INFO and COL_PROTOCOL set
from the payload dissector.
Signed-off-by: Stefan Metzmacher <metze@samba.org>
|
|
Signed-off-by: Stefan Metzmacher <metze@samba.org>
|
|
There might be more than one mpa frame in a tcp pdu
or one mpa frame spans more than one tcp pdu.
Signed-off-by: Stefan Metzmacher <metze@samba.org>
|
|
|
|
Fixes #17365
|
|
Fixes CID 1477404
|
|
Fixed crash when dissecting Type Object larger than 100 elements. Added
protocol option for setting up the maxumun number of Type Object elements to show.
|