travelping / pfcplib

79%

master: 79%

LAST BUILD ON BRANCH

branch: SELECT

CHANGE BRANCH

x

• No branch selected
• --abrev-ref bf3c04ab929b67508aef8706eee1699957082b33
• --abrev-ref d49fcf57ed3b883c7d1dcd039830ba5813ac9906
• --abrev-ref dff2520579dd80e27a4dc6347cea66154d0a200c
• 1.0.0
• HEAD
• ci/add_otp_24
• feature/add_github_workflow_and_codeowners
• feature/add_hex_action
• feature/bbf-tr-459
• feature/normalization
• feature/rel16-3-1
• feature/rel16-6-0
• feature/replace_erlando_to_cut
• feature/start_use_semver
• feature/telemety
• feature/update_gh_actions
• fix/dl-count
• fix/edoc
• fix/proper
• fix/user_id
• fix/warnings
• ipfix_policy
• master
• prepare/2.1.2
• prepare/2.3.0
• readme/change_badge_style
• refactoring/remove_erlando
• release/2.0.0
• release/2.0.1
• release/2.0.2

Build # 9642312493

Build Type

push

github

Committed by RoadRunnr

Commit Message

pfcp_packet.hrl: fix type hints for ipv4/ipv6 fields

The types 'inet:ip4_address()' and 'inet:ip6_address()' define tuples
of 4 and 16 integers, respectively;  while the pfcplib API actually
expects the ipv4/ipv6 fields to hold binary() values (raw bytes).

This is confusing and makes Dialyzer go nuts about valid code.

Signed-off-by: Andreas Schultz <andreas.schultz@travelping.com>

Run Details

1506 of 1682 relevant lines covered (89.54%)

788.36 hits per line