| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Some tests are are only run with BER backend. Unless there is a
special reason that the PER and UPER backends will not work, we
should run all tests with all backends to get the best possible
code coverage.
|
|
|
|
in order to be backward compatible with user code that
accesses the members of erlang_pid and friend.
The documentation does not mention the content of these structs,
but we have example code that does. So the safe way it the revert
the node_org_enc field (added in R16A) and instead determine in
runtime which atom encoding to use depending on if the node atom
contains unicode (>255) characters or not.
|
|
|
|
This makes the shell output binaries and list as intended by
the +pc setting.
|
|
|
|
* lukas/erts/file_read_line_opt/OTP-10859:
invoke_read_line now remembers read_ahead settings
|
|
* lukas/erts/writev_osx_fix/OTP-10858:
Do not use writev on osx snow leopard
|
|
* bjorn/asn1/bug-fixes/OTP-10853:
asn1ct: Eliminate use of obsolete size/1
Eliminate use of obsolete size/1 in generated code
BER: Fix broken table constraints inside a SET OF/SEQUENCE OF
Smoke test the 'der' option
der: Correct code generation for checking of empty sets
per,uper: Fix breakage of compilation of InformationFramework
Add NullTest
asn1_SUITE: Shorten the path to case-specific directory
asn1_SUITE: Don't add priv_dir to the code path
asn1 tests: Remove obsolete duplicates of ASN.1 specs
|
|
Because {prim_file,file}:list_dir/1 no longer returns untranslatable
filenames, we must use list_dir_all/1 instead. We also need to use
read_link_all/1 instead of read_link/1.
|
|
It produced the same result as file:read_link/1.
|
|
6d516de001dde82c02fe050db8e3aab47914fa90 added prim_file:list_dir_all/1.
Unfortunately, only the first element in the list would be handled
as intended.
|
|
Add a 'strict' target to compile with -Werror and fix a dependency.
Reorder test suites alphabetically. The two suites that currently take
the longest to run conveniently come last.
|
|
The workaround (commit 57d5564f) was to dialyzer only understanding
nowarn_unused_function on individual functions. This is no longer the
case as of R15B01 (commit 477fd95a).
|
|
* anders/diameter/5xxx_errors/OTP-10759:
Add testcases for application_opt() request_errors = answer
Answer 5xxx errors with application_opt() request_errors = answer
Comments and minor Result-Code fix
|
|
* anders/diameter/result_code/OTP-10761:
Add testcases to 3xxx suite
Minor traffic suite fix
Be less brutal in setting Result-Code/Failed-AVP
|
|
* anders/diameter/3xxx_callback/OTP-10686:
Add 3xxx suite for testing application_opt() request_errors
Minor suite simplification
Add application_opt() request_errors
|
|
pan/unicode_printable_ranges
* hb/stdlib/unicode_corrections/OTP-10820:
Fix some Unicode issues
Conflicts:
lib/stdlib/test/shell_SUITE.erl
|
|
|
|
|
|
Also fixed otp_10302 to test both on a node with +pc unicode and
a node with +pc latin1.
|
|
This means that only UTF-8 characters in binaries that conform
to the printable_range are printed as <<"..."/utf8>> in io_lib_pretty.
|
|
|
|
This makes both io:format("~tp", ...) and
the shell honor the +pc setting and also reverts the shell to
the old behaviour of only interpreting latin1 strings as "strings"
by default. +pc unicode turns on the R16A behaviour. Doing
io:format("~tp~n", [[1024,1025]]).
will show you the difference when starting with +pc unicode.
|
|
This is the base for implementing configurable
~tp printouts, so that the user can define which
characters to view as actually printable in the shell and
by io_lib:format.
The functionality is neither documented nor used in this commit
|
|
|
|
|
|
Also let the Erlang shell use the new function io:printable_range().
|
|
|
|
* ia/odbc/port_info:
odbc: Use erlang:port_info to make sure test cases chooses the correct port
|
|
|
|
|
|
|
|
RFC 3588 allowed only 3xxx result codes in an answer-message (that is,
an answer that sets the E-bit) while RFC 6733 also allows 5xxx result
codes. Setting request_errors = answer tells diameter to answer 5xxx
errors itself. Returning {answer_message, integer()} from a
handle_request callback allows both 3xxx and 5xxx result codes to be
set. {protocol_error, integer()} is retained for 3xxx result codes.
|
|
In particular, don't put an error tuple in the errors field of
a #diameter_packet{} when Result-Code and the E-bit are in conflict, put
{integer(), #diameter_avp{}}.
|
|
|
|
|
|
When receiving a request for which errors have been detected during
decode, diameter previously used the errors list in the decoded
diameter_packet record to unconditionally set Result-Code and Failed-AVP
in the outgoing answer. It wasn't particularly delicate in doing so
however and would happily set a 5xxx Result-Code even if a
handle_request callback returned an answer-message, leading to an encode
error. This behaviour became even less endearing as of commit ac452e28,
which made it possible to handle_request to take place even for protocol
errors. (ie. When a callback typically should return an answer-message.)
This commit fixes the behaviour by only setting a value that's
appropriate for the answer in question, either a 3xxx or a 5xxx,
depending on if the answer's an answer-message or not. It also allows
handle_request to prevent diameter from setting anything by setting
errors = false in a returned diameter_packet. Ideally it should have
been errors = [] but the empty list is the default value for the errors
field and changing the default (ideally there shouldn't have been one)
would require recompilation of all modules including diameter.hrl:
choose the less attractive 'false' to avoid such backwards
incompatibility.
The request reception is also refactored somewhat to shorten some call
chains.
|
|
|
|
|
|
Configuring the value 'callback' all errors detected in incoming
requests to result in a handle_request callback. The default value
'answer_3xxx' is the previous behaviour in which diameter answers
protocol errors without a callback.
|
|
Also teach otp_SUITE:call_to_size/1 that calls to size/1 is no
longer allowed within the asn1 application.
|
|
It is recommended to use byte_size/1 or tuple_size/1 instead of
size/1.
|
|
|
|
|
|
|
|
* lukas/erts/add_sha_to_shell_title/OTP-10838:
Remove could not find warning
|
|
|
