| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit polishes a lot of the make system to be more
robust and hopefully user friendly. A new DEVELOPMENT howto
guide has been added with instructions on how to work with
the Erlang/OTP code and the `make test` functionality has
been fixed so that it should work for all applications.
In order to solve the problem of some applications relying
on being tested using a release, each application has been
instrumented in its Makefile so that it knows if a release
has to be done or not.
|
|
|
|
|
|
|
|
|
|
| |
When running tests the state of the system may not always
be able to flush all ports and we do not want the system
to hang when that happens.
An example of this happening is when the peer_SUITE has
connections to dead nodes that have been been disconnected
yet.
|
|\
| |
| |
| |
| | |
garazdawi/lukas/ct/add-file-and-line-to-surefire/OTP-17881/OTP-17882
ct: Add correct file and line to surefire report
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
If a process with a hook lock crashes when it is the
only process with a lock we should return to an unlocked
state and continue as normal.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When running a suite with many processes the cth state
could become very large. Since the state is copied to the
testcase process each time a cth is called that because
very expensive. So instead we create a seperate process
that keeps the state of the surefire cth so that it does
not have to be copied.
|
| | |
|
|\ \ |
|
| |\ \
| | | |
| | | |
| | | |
| | | | |
observer/etop: Calculate field width with available columns
OTP-17880
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The field widths are calculated depending on what the underlying io
driver reports as max column width.
The fields are allowed to use the column width they need if they column
budget allows it. The field widths are deducted in priority order and if
there is space left the calculated width is used otherwise the default
field width is used.
If the underlying io driver can't give any column width, the default
column width budget of 89 characters is used. This is the legacy hard
coded width, plus two spaces between reductions, memory, and msgq
fields.
Fixes #5080
Signed-off-by: Per Andersson <avtobiff@foo.nu>
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
fix param ordering of gen_event crash
OTP-17878
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Currently we get error messages like the following logged:
```
2021-11-09T09:27:03.949055+00:00 error: Generic event handler ... crashed. Installed: .... Last event: {badarg,[{ets,match_object,[...],[{error_info,#{cause => id,module => erl_stdlib_errors}}]}|...]}. State: {event,...}. Reason: {state,...}.
```
This is very confusing (caused us to go on a rabbit hunt through our own
code for transposed `State`/`Reason` in `{stop,...}` return values).
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
* bjorn/peer-fixes/OTP-17720:
peer.xml: Correct since tags
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
* hans/crypto/deprecate_dyn_iv/OTP-17870:
Update deprecations
crypto: Deprecate crypto_dyn_iv_init/3 and crypto_dyn_iv_update/3
|
| | | | | | | |
|
| | | | | | | |
|
|\ \ \ \ \ \ \
| | |_|_|/ / /
| |/| | | | |
| | | | | | |
| | | | | | | |
* maint:
Fix eldap extensibleMatch dnAttributes option
|
| |\ \ \ \ \ \
| | |_|_|_|/ /
| |/| | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Fix eldap extensibleMatch dnAttributes option
OTP-17877
|
| | | |_|_|/
| | |/| | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
According to the ldap ASN1 the dnAttributes should be a bool,
instead it was generated as a string.
Also add a couple of test to verify the filter behaves correctly.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Eliminate confusing `case_clause` exception
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Consider this module:
-module(bug).
-export([foo/0]).
foo() ->
fun(a) -> ok end(b).
The call to the fun will always fail, which will be noted by
the compiler:
1> c(bug).
bug.erl:5:5: Warning: no clause will ever match
% 5| fun(a) -> ok end(b).
% | ^
{ok,bug}
What is unexpected is that the exception that is raised is not
a `function_clause` exception:
2> bug:foo().
** exception error: no case clause matching {b}
in function bug:foo/0 (bug.erl, line 5)
This confusing `case_clause` exception started to appear in OTP 24
because of 72675baaa9fd30 (#4545) that inlines funs that are
immediately used.
Before OTP 24, when the fun was not inlined, the exception would be:
2> bug:foo().
** exception error: no function clause matching bug:'-foo/0-fun-0-'(b) (bug.erl, line 5)
The reason that `function_clause` exceptions are rewritten to
`case_clause` exceptions in inlined code is to avoid the even more
confusing and misleading exception:
2> bug:foo().
** exception error: no function clause matching bug:foo(b) (bug.erl, line 5)
This is confusing because it seems that `foo/0` was called with one argument.
To reduce the confusion, this commmit ensures that `function_clause` exceptions in
inlined code remains `function_clause` exceptions, but with a generated name that
makes it clear that the `function_clause` exception occurred in a fun:
2> bug:foo().
** exception error: no function clause matching bug:'-foo/0-inlined-0-'(b) (bug.erl, line 5)
Fixes #5513
|
|\ \ \ \ \ \ \
| |_|_|_|_|_|/
|/| | | | | | |
Hans/update deprecations script
|
| | | | | | | |
|
| | |_|_|/ /
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
which caused the atom 'undefined' to be the Text in update_deprecations:make_xml_info/2.
According to /home/uabhnil/Projects/OTP/otp1/HOWTO/DEPRECATE.md that 'undefined' should be changed to
"see the documentation for details." by that script.
The internal wiki page has the same opinion as the script.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
erts: Fix ttsl driver xn followed by nl
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
The terminal would incorrectly emit " \b" when the next
wrapping character was a \r|\n.
I think this is the correct behaviour, but it is hard to
test on all terminals.
Closes #5403
|
|\ \ \ \ \ \ \
| |_|/ / / / /
|/| | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
* john/compiler/misc-fixes:
beam_types: Fix silly mistake in external type mapping
beam_ssa_type: Fix cosmetic issue in get_tuple_element
beam_ssa_type: M:F(...) will crash when M or F aren't atoms
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
|\ \ \ \ \ \ \
| | |_|_|/ / /
| |/| | | | | |
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | | |
public_key,ssl: add password fun for decoding keyfiles
OTP-17816
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Implementing password fun option for ssl connect API
This change allows password option to accept as a value
either a string or a fun. Added specific tests and
documentation.
The motivation for this change is to better protect a
private key. If the private key is protected by password the
password may be retreived using user supplied function therefore
enabling storing password in a secure vault or something similar.
|
|\ \ \ \ \ \ \ \
| |/ / / / / / / |
|
| |\ \ \ \ \ \ \ |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
|\ \ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | | |
Fix typos in lib/xmerl
|
| | | | | | | | | | |
|
|\ \ \ \ \ \ \ \ \ \
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | | |
Update Unicode to 14.0.0
OTP-17869
|
| |/ / / / / / / / /
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
This is an automated commit created by the Maintenance project
https://github.com/eksperimental/maintenance
|
|\ \ \ \ \ \ \ \ \ \
| | |/ / / / / / / /
| |/| | | | | | | | |
|
| |\ \ \ \ \ \ \ \ \ |
|