| Age | Commit message (Collapse) | Author |
|---|
|
The sync option adds the POSIX O_SYNC flag to the open system call on
platforms that support the flag or its equivalent, e.g.,
FILE_FLAG_WRITE_THROUGH on Windows. For platforms that don't support it,
file:open/2 returns {error, enotsup} if the sync option is passed in.
The semantics of O_SYNC are platform-specific. For example, not all
platforms guarantee that all file metadata are written to the disk along
with the file data when the flag is in effect. This issue is noted in the
documentation this commit adds for the sync option.
Add a test for the sync option. Note however that the underlying OS
semantics for O_SYNC can't be tested automatically in any practical way, so
the test assumes the OS does the right thing with the flag when
present. For manual verification, dtruss on OS X and strace on Linux were
both run against beam processes to watch calls to open(), and file:open/2
was called in Erlang shells to open files for writing, both with and
without the sync option. Both the dtruss output and the strace output
showed that the O_SYNC flag was present in the open() calls when sync was
specified and was clear when sync was not specified.
|
|
|
|
* bsmr-erlang/fix_gen_fsm_example/OTP-11472:
fixed small typo (missing right parenthesis) in gen_fsm example
|
|
* fredrik/doc/syntax_highlight/OTP-11237:
erl_docgen: fix code highlighting and warning and note parts in erl_docgen
|
|
|
|
If a request handler terminates abnormally (terminate reason not
normal), the error-log entry was a bit obtuse ("Internal Server Error").
This has been improved so that the log entry now also include the
actual terminate reason.
|
|
Sometimes the size of a response could be as a string.
|
|
Remove logging when fo keep-alive connection timeout. This is
a normal event (feature) not an error.
|
|
|
|
|
|
|
|
* sverk/valgrind-added-leak-check:
erts: Prevent valgrind from repeating same memory leaks reports
|
|
* klyr/ssl_sni_client/OTP-11460:
Update documentation
Add a new server_name_indication option to ssl:connect
Add SSL Server Name Indication (SNI) client support
|
|
|
|
* robertoaloi/eunit/surefire-printable-chars/OTP-11467:
Do not attempt to detect lists of printable characters in Data
|
|
* asterite/atan2_spec/OTP-11465:
Spec for atan2 should be atan2(Y, X), not atan2(X, Y)
|
|
* lukas/cerl_dump/OTP-11468:
erts: Add cerl -dump and dumping in z_SUITE
|
|
|
|
This is to avoid outputting something like "\"%\f" instead of [34,37,12] in the XML.
|
|
* richcarl/sasl-dont-add-undefined-handler/OTP-11464:
Don't try to add the log_mf_h handler in sasl unless configured to do so.
|
|
|
|
|
|
- Set to disable to explicitly disable SNI support.
- Set to a hostname when upgrading from TCP to TLS.
|
|
See RFC 6066 section 3
|
|
maint
* richcarl/xmerl-avoid-code-server-serialization/OTP-11463:
Avoid serialization on code_server in xmerl:export()
|
|
into maint
* danielwhite/xmerl-xpath-resolve-context-namespaces/OTP-11461:
xmerl: Use context namespace declarations to resolve prefix node tests
xmerl: Look up unknown prefixes in xmlContext when matching attributes
xmerl: Add tests for XPath queries that resolve the context namespace
|
|
The inheritance mechanism in xmerl used to use 'catch apply(M,F,Args)' to
try different modules M until one was found that had a function F/A.
However, when M:F/A does not exist, apply/3 will trap to
error_handler:undefined_function/3, which will call code:ensure_loaded(M),
making a synchronous request to the code server process. If many processes
tried to use xmerl:export() concurrently, they would get serialized waiting
for the code server process. This patch uses erlang:function_exported/3
instead to check if M:F/A exists. If M exists, it should already have been
loaded at that point due to the inheritance checking in the
xmerl:callbacks/1 function.
|
|
* sverk/monitor-memory-leak/OTP-11410:
erts: Fix memory leak for distributed monitors
|
|
by using the macro VALGRIND_DO_ADDED_LEAK_CHECK if it exists
for system_info({error_checker,memory})
|
|
Previously, a match would not be found if the namespace prefix in the
XPath query was not contained in the original document. This allows
the `namespace' option to provide a prefix that will be resolved to a
namespace URI.
See Section 2.3 of the XPath 1.0 specification for the behaviour of
'NCName:*' node tests.
|
|
The core use case is a query where the original prefix in the scanned
document is unknown (or varying). For example:
xmerl_xpath:scan("//@ns:name", Doc, [{namespace, [{"ns", Uri}]}])
Previously, this would only return a result if the namespace prefix
was an exact match.
|
|
Ensures that both the original namespace prefix and a namespace prefix
provided to the xmlContext will both return the same sets of nodes.
|
|
* klyr/fix-ssl-npn-doc-2/OTP-11457:
Fix client_preferred_next_protocols documentation
|
|
* cmeiklejohn/csm-fix-memsup-problems/OTP-11454:
Fix incorrect reporting of memory on OS X via memsup.
|
|
* Tonkpils/typo-fix/OTP-11455:
Update primary bootstrap
Typo fix ambigous -> ambiguous
|
|
|
|
* anders/diameter/patch_release/OTP-11459:
Update appup, vsn -> 1.4.4
Fix handling of 5014, DIAMETER_INVALID_AVP_LENGTH
Fix broken DWA
|
|
|
|
anders/diameter/patch_release/OTP-11459
* anders/diameter/5014_failure/OTP-11395:
Fix handling of 5014, DIAMETER_INVALID_AVP_LENGTH
|
|
anders/diameter/patch_release/OTP-11459
* anders/diameter/broken_dwa/OTP-11367:
Fix broken DWA
|
|
The error was detected as 5004 (DIAMETER_INVALID_AVP_VALUE) for
stringish Diameter types, in which case an AVP length that pointed past
the end of a message resulted in encode failure of the suggested
Failed-AVP.
Should have been fixed in commit 4ce2d3a6.
|
|
|
|
|
|
|
|
* lukas/erts/openbsd-posix-memalign-fix/OTP-11371:
erts: Add max alignment posix_memalign configure check
|
|
On some OSs posix_memalign exists, but it does not allow for alignment
greater than the current page size. So we have to do a runtime check for
alignment size and also add cross compile options.
|
|
* tsloughter/ssh_doc_fix/OTP-11449:
fix private_key type documentation in ssh_server_key_api
|
|
Application memsup should be calculating free memory using the
speculative pages, in the same manner that the Activity Monitor and top
programs on OS X do. In addition, correct page size to 4096, based on
verification of available memory between top, vm_stat and Activity
Monitor.
|
|
* gomoripeti/pgo-cover-export-all/OTP-11439:
tools: Fix compile_beam_opts testcase
Take compiler options from beam in cover:compile_beam
|
|
|
