Thanks, Peter <3 we had a release at work, so I was focusing there.. will
continue helping with the docs as I already told you. Will check out info
about Wireshark fest as well.
luvluv
Alex
On Wed, Mar 31, 2021, 23:29 Peter Wu wrote:
> Hi Alex,
>
> Thank you for your contributions to the
I would really like to see more of Alex's art at SharkFest, maybe on
T-shirts or mugs, I think attendees would love it.
On Wed, 31 Mar 2021 at 22:29, Peter Wu wrote:
> Hi Alex,
>
> Thank you for your contributions to the documentation! Some components
> have been undocumented for a while. You
gitlab.com/constg2021/wireshark
On 31/03/21 21:00, Gerald Combs wrote:
Hi Constantine,
You receivied the failure notice because:
- You pushed a commit to gitlab.com/constg2021/wireshark. Was this for
a merge request for wireshark/wireshark? From GitLab's perspective it
dosen't matter.
Hi Alex,
Thank you for your contributions to the documentation! Some components
have been undocumented for a while. You did a good job trying to track
down relevant subject matter experts and doing some research on your
own, despite not being familiar in the area.
The results are visible on
Hi Constantine,
You receivied the failure notice because:
- You pushed a commit to gitlab.com/constg2021/wireshark. Was this for a merge
request for wireshark/wireshark? From GitLab's perspective it dosen't matter.
constg2021/wireshark is a separate project.
- CI/CD is enabled in
I was able to replicate this using an opensuse/leap:42.3 docker image with a
default build environment, which includes CMake 3.5.2 and Qt 5.6.2. I also
installed various CMake versions and got the following results:
CMake 3.5.2: CMake succeeded, ninja failed
CMake 3.8.2: CMake succeeded, ninja
Ronnie:
Thank you for taking your time to reply. I think you entirely missed my
point.
The question was not regarding how to fix but about significance of this
build test.
I saw my previous merge requests approved and even merged when this test
failed. I then saw it post factum, and
Hi,
Yesterday I've spent some time figuring out why the http2_tcp heuristic
dissector wasn't working on my particular pcap. Turns out the reason is
that tcpros_tcp was claiming the data before http_tcp could get a turn
(http2_tcp is registered under http despite the _tcp in the name). In
cmake --version
cmake version 3.5.2
qmake-qt5 --version
QMake version 3.0
Using Qt version 5.6.2 in /usr/lib64
This is an old VM that will be retired in around a month when a new machine
arrives.
At the very end of running cmake I was getting this:
- Configuring done
Warning: Source file
It seems like you already know what is wrong and how to solve this.
Why not just change your patch so it does not trigger this compiler
error/warning?
Maybe the compiler is overly sensitive here? Who knows.
Why is this a problem for wireshark developers?
Do this:
* fix your code so it does not
I have a question regarding for a special form of automatic builds that I
do not understand.
Occasionally, I get an email for additional pipeline build that is
different from default pipeline linked to the ticket. It is a wider set of
compilers and distributions.
Several questions:
What is
11 matches
Mail list logo
